Edit weigh pocket modal

As stated below this pr is a big one. #160, #159 and #14 have been implemented here. There's a branch for #14 by @Chebi97 but #160 needs it to work. Both #160 and #159 are related so it made sense to put all three under the same bag.
Full list of changes:
New:

EditPocketModal.js with its Redux Actions, Reducer, selector and corresponding test files. This modal changes the ID of the Pocket, its not functional yet, nor its intended for the purpose of this pr.
EditWeightPocketModal.js with its Redux Actions, Reducer, selector and corresponding test files. This modal changes the  weight of the Pocket, its not functional yet, nor its intended for the purpose of this pr. Read below for details on the implementation of this modal as it defers from the others.
PencilIcon for edit button.

Modified:

Phone-pocket.test.js:

Added missing mocks
Added mocks to the component for its use.
Fixed gramatical errors.

PhoneBale.js

Changed Modal props from optional to neccesary

PocketList.js:

Added all redux dependencies for modals to show
Added all function passing for modals to show.

PhonePocket.js:

Added the pencil button to the pocket component
Added all dependencies for the modals to show. They are passed through its parent component

TabletPocket.js:

Added the pencil button to the pocket component
Added all dependencies for the modals to show. They are passed through its parent component

Pocket/styles.js

Added styles for the button.

User/styles.js

Fixed styles not following eslint configuration

RootReducer.js:

Added all new reducers.

localization/en.js and localization/es.js:

Added several new strings

Removed:

Pocket-List.test.js: This was removed since the test was proving difficult to complete, and its not relevant at the moment. I suggest this being its own story, with a low priority.

Details of implementation:

EditWeightPocketModal: Since the placeholder and title differ based on whether the pocket has weight or not we need either two modals or a way of knowing this information from the component. Because the first option would be an overkill, it was decided that we needed to pass a parameter to the modal. This information is used to determine which strings are shown. The same variable can be used when doing the post method later on.

It would be better for the EditPocket component to be called EditPocketId or EditIdPocket to be more specific about its functionality.

Both modals have a bug when entering a very long number of characters. Limit the number of characters to enter in the space to prevent this bug from happening.

Renamed files as requested. Also, modals input field is capped.


Poor PDO performance over network

I am running a set of tests to compare performance of:
.Net SQL Client / PDO SQLSRV /  SQLSRV
(*last official version of everything+)
With SQL Server and Web Server on same computer:
SQL CLIENT: 1.69s
SQLSRV: 1.8s
PDO_SQLSRV: 1.95s
With SQL Server and Web Server on different VM on the cloud:
SQL CLIENT: 5.22s
SQLSRV: 5.3s
PDO_SQLSRV: 8.5s
The sample test case is just a 5,000 test loop over a SELECT COUNT query.
PHP code being slightly slower than ASP.Net is understandable.
What puzzles me is PDO being about 65% slower when working over the network, and SQLSRV not degrading so much. Something must be wrong.
This is the test script I'm using for the PHP benchmarks:

$conn = $databases['default']['default'];
$host = $conn['host'];
$database = $conn['database'];
$username =  $conn['username'];
$password = $conn['password'];

$cnn = new PDO("sqlsrv:server=$host;Database=$database",  $username, $password);

$start = microtime(TRUE);

for ($x = 0; $x < 5000; $x ++) {
  $result = $cnn->query('SELECT COUNT(*) FROM VARIABLE');
}

$lapsed = microtime(TRUE) - $start;
echo "Lapsed 1 {$lapsed}";

$cnn1 = sqlsrv_connect($host, array("UID"=>$username, "PWD"=>$password, "Database"=>$database));

$start = microtime(TRUE);

for ($x = 0; $x < 5000; $x ++) {
  $result = sqlsrv_query($cnn1, 'SELECT COUNT(*) FROM VARIABLE');
}

$lapsed = microtime(TRUE) - $start;
echo "Lapsed 2 {$lapsed}";

And this is for the ASP .Net:

       SqlDataReader reader;

        SqlConnection cnn = new SqlConnection("Server=;Database=;User Id=;Password=");
        cnn.Open();

        var start = DateTime.Now;

        for (var x = 0; x < 5000; x++)
        {
            SqlCommand cmd = new SqlCommand();

            cmd.Connection = cnn;
            cmd.CommandText = "SELECT COUNT(*) as c FROM VARIABLE";
            reader = cmd.ExecuteReader();
            int result;
            while (reader.Read())
            {
                result = (int)reader["c"];
            }
            reader.Close();

        }

        var lapsed = (DateTime.Now - start).TotalSeconds;

        Response.Write("Lapsed:" + lapsed);

Using direct queries solved the performance degradation....

$cnn->setAttribute(constant('PDO::SQLSRV_ATTR_DIRECT_QUERY'), true);

Like there is no point in using prepared statements if you are not going to reuse them.


Infinite scroll - autoplay issue and Fullscreen issue

In the following link the video is implemented to autoplay play in viewport. When we scroll down the next page loads on downwards scroll (infinite scroll) . When we scroll down to the next page (after unmute the video from the first page)new player loads however the audio from the previous video continuous to play in the background.

http://programmatic.private.wittyfeed.com/relationship-advice-for-newly-weds-66628

Also, when we scroll back to the previous video, there's an entirely new video in display with the previous audio still playing in the background

The video pauses whenever a full screen event is triggered.

I took a look at your page but after scrolling all the way to the bottom I only see one video.js player - has it changed since you initially filed this?

Sorry for the delay in response. It did change, we will implement in a different page and will post it in few days. Thanks for your help

It's been a while since we've heard from you, so I'm going to close this - if you still need help feel free to respond and we'll re-open it. Thanks!


Form is submitted when required checkboxes are not checked

Hi everybody!
I found this bug while I was working with checkboxes, I don't know if the same problem occurs with radio inputs.
Here is a plunker showing the problem, just perform the following steps:

try to submit
check the input
uncheck the input
try again to submit the form

You will notice than from now on, the form is always submitted even if the input is not checked. As you will see, also field-errors are never shown.

Thanks for reporting this. As crazy as it seems...this looks like a legit oversight. :) I'll try to patch it up soon.

In fact, now that I think back, that's how it's implemented on the demo page also:
http://bvaughn.github.io/angular-form-for/#/demo/form-builder-markup
What are your thoughts on the work around?

Yes, the workaround works perfectly, but still remain a workaround.
I was looking at the normal behavior of a checkbox in Angular.js: https://docs.angularjs.org/examples/example-example34/index.html.
As I can see, Angular sets the model object value to undefined every time the checkbox is unchecked. The same should be for the formFor plugin.
I'm debuggin the plunker and i'm trying to understand how (and why) formFor sets the value of the checkbox to true/false instead of true/undefined.

Ok, this is a normal behavior of Angular checkboxes when there's not a required attribute.
That's what I noticed:

if the checkbox has the required attribute, then Angular set the unchecked state to undefined
otherwise Angular set the unchecked state to false

Here is a plunker showing this behavior.

I think there are many options to solve this:

require novalidate attribute to the form and required attribute to the checkbox (plunker)
working on the plugin to wrap this behavior, adding a watcher here

$scope.$watch('model.bindable', function (value) {
   $scope.model.bindable = value || undefined; // or null
});

something similar to point 2, but generalized to all inputs (maybe here?). In this case we must check the input type).

I personally prefer the first one, what do you think about?

I merged in your fix! Although I didn't merge your branch, because you didn't build from source (and so the minified and source-map versions of the dist hadn't been updated). Thank you for the suggestion and the fix though! :)

The fix for this issue has been released in version 4.1.1.

Thank you for supporting me! :+1:


Give the posterior predictive plots free axis or at least free x axis

This should make it much easier to see the information you are interested in

Is this something which has been achieved?
@seabbs would you be able to link to the part of the code you mean?
It'll either be in:

plot_rslts.R
plot_layered.R

This was in reference to the posterior predictive plots in the readme at R/Simulated Data Analysis/README.md, which was resolved in the code for the plots
https://github.com/CDCgov/cfa-respnet-nowcasting-daily/blob/c7e31e6d532c7c1e6e97427d6aaae98ca77eebe7/R/Simulated Data Analysis/plot_rslts.R#L107-L109


Henri/back2py

added a .gitignore and corrected typos

@Vanderscycle You will need to fix the DCO. You need to sign-off all commits to merge into this repo.
In the git workflow it says this,
git commit -m "this is my commit message" --signoff
Thanks.

Through ggp correct?

No -- it's not a gpg key that is needed -- just the signoff (-s is needed, not -S).  See DCO - Developer Certificate of Origin - https://github.com/apps/dco -- you can also click the details.
It's a pain if you miss it -- might be easier to redo :-(.


Better way of Object creation structure

Found this from your blog post : http://www.hydrogen18.com/blog/writing-parquet-records.html
I have to agree, by so far your was the simplest one to understand if someone has to simply write in parquet format in their own system without dealing with other infra like spark, hadoop etc.
I found the object structure creation odd, The class created by avro-maven plugin has a huge code base. Most of the cases business object/pojo structure is already created.
What do you recommend in such case when existing Pojo structure needs to be used as a record  and do not want to generate the same using avro-maven plugin?

Hi,
This isn't really meant to be a discussion space, but I will give you this answer before closing:
I explored the idea of writing Pojos and it would probably be more work and more code than defining an Avro schema. I couldn't find any documentation about how this library is supposed to work together. I didn't want to invest the time into understanding the internals of it.
I don't think this Parquet library is actually meant to be used by 3rd party developers like myself. I'm guessing most of the use cases for it are by developers of the library itself.
Eric


Plug RunCommands as full 2017-12-01

@yugangw-msft This is complete RunCommands in 2017-12-01. IF you can tell me if it works. Just remove the "virtual_machine_run_commands" line in the CLI profile

Codecov Report

Merging #1713 into master will decrease coverage by 0.01%.
The diff coverage is 25.8%.

@@            Coverage Diff             @@
##           master    #1713      +/-   ##
==========================================
- Coverage    53.5%   53.48%   -0.02%
==========================================
  Files        4461     4462       +1
  Lines      107574   107627      +53
==========================================
+ Hits        57553    57563      +10
- Misses      50021    50064      +43

Impacted Files
Coverage Δ

...te/azure/mgmt/compute/compute_management_client.py
58.18% <0%> (-0.51%)
:arrow_down:

.../azure/mgmt/compute/v2017_12_01/models/__init__.py
100% <100%> (ø)
:arrow_up:

...re/mgmt/compute/v2017_12_01/operations/__init__.py
100% <100%> (ø)
:arrow_up:

...rations/virtual_machine_run_commands_operations.py
17.64% <17.64%> (ø)

...t/compute/v2017_12_01/compute_management_client.py
42.3% <50%> (+0.3%)
:arrow_up:

...17_12_01/models/run_command_document_base_paged.py
80% <80%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 27624f4...8edcab6. Read the comment docs.


[stable/postgresql] PostgreSQL enters a crash loop after any restart when persistence is used

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Version of Helm and Kubernetes:
$ helm version --tls
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"archive", BuildDate:"2018-10-20T03:04:33Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.7-gke.6", GitCommit:"06898a4d0f2b96f82b43d9e59fa2825bd3d616a2", GitTreeState:"clean", BuildDate:"2018-10-02T17:32:01Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/postgresql
What happened:
$ cat values-test.yaml
postgresqlUsername: test
postgresqlPassword: test
postgresqlDatabase: test
persistence:
  enabled: true

$ helm install --tls --name test stable/postgresql -f values-test.yaml
NAME:   test
E1029 10:02:17.709582   12598 portforward.go:303] error copying from remote stream to local connection: readfrom tcp4 <IP_ADDRESS>:34065-><IP_ADDRESS>:49854: write tcp4 <IP_ADDRESS>:34065-><IP_ADDRESS>:49854: write: broken pipe
LAST DEPLOYED: Mon Oct 29 10:02:17 2018
NAMESPACE: default
STATUS: DEPLOYED
<snip>

$ kubectl get pods -l release=test
NAME                READY   STATUS    RESTARTS   AGE
test-postgresql-0   1/1     Running   0          1m

$ kubectl delete pods test-postgresql-0
pod "test-postgresql-0" deleted

$ kubectl get pods -l release=test
NAME                READY   STATUS             RESTARTS   AGE
test-postgresql-0   0/1     CrashLoopBackOff   1          56s

$ kubectl logs test-postgresql-0 -p

Welcome to the Bitnami postgresql container
Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql
Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues

nami    INFO  Initializing postgresql
postgre INFO  ==> No injected postgresql.conf file found. Creating default postgresql.conf file...
postgre INFO  ==> No injected pg_hba.conf file found. Creating default pg_hba.conf file...
postgre INFO  ==> Deploying PostgreSQL with persisted data...
postgre INFO  ==> Configuring PostgreSQL...
postgre INFO  ==> Configuring replication parameters...
postgre INFO  ==> Configuring permissions for config files...
postgre INFO
postgre INFO  ########################################################################
postgre INFO   Installation parameters for postgresql:
postgre INFO     Persisted data and properties have been restored.
postgre INFO     Any input specified will not take effect.
postgre INFO   This installation requires no credentials.
postgre INFO  ########################################################################
postgre INFO
nami    INFO  postgresql successfully initialized
INFO  ==> Starting postgresql...
nami    ERROR Unable to start com.bitnami.postgresql: pg_ctl: another server might be running; trying to start server anyway
pg_ctl: could not start server
Examine the log output.

PostgreSQL remains in this crash loop until the PersistentVolume{,Claim} is deleted.
What you expected to happen:
I expected the pod to restart correctly.
How to reproduce it (as minimally and precisely as possible):
See above.
Anything else we need to know:
This problem appears to be caused by a stale postmaster.pid. The following patch (don't mind the k8s/... subpath) is a workaround:
diff --git a/k8s/chart/charts/postgresql/templates/statefulset.yaml b/k8s/chart/charts/postgresql/templates/statefulset.yaml
index 1d76e0a6..8b7d032d 100644
--- a/k8s/chart/charts/postgresql/templates/statefulset.yaml
+++ b/k8s/chart/charts/postgresql/templates/statefulset.yaml
@@ -57,6 +57,13 @@ spec:
       - name: {{ template "postgresql.fullname" . }}
         image: {{ template "postgresql.image" . }}
         imagePullPolicy: "{{ .Values.image.pullPolicy }}"
+        command:
+          - /bin/bash
+          - -c
+          - |
+            #!/bin/bash
+            rm -vf /bitnami/postgresql/data/postmaster.pid
+            exec /app-entrypoint.sh /run.sh
         resources:
 {{ toYaml .Values.Resources | indent 10 }}
         env:

However, if this patch is applied, another error manifests:
$ kubectl logs test-postgresql-0
<snip>
nami    ERROR Unable to start com.bitnami.postgresql: pg_ctl: could not start server
<snip>

The second above-mentioned issue (bitnami/bitnami-docker-postgresql#79) describes both problems in detail. The final workaround is:
diff --git a/k8s/chart/charts/postgresql/templates/statefulset.yaml b/k8s/chart/charts/postgresql/templates/statefulset.yaml
index 1d76e0a6..834dbaac 100644
--- a/k8s/chart/charts/postgresql/templates/statefulset.yaml
+++ b/k8s/chart/charts/postgresql/templates/statefulset.yaml
@@ -57,6 +57,17 @@ spec:
       - name: {{ template "postgresql.fullname" . }}
         image: {{ template "postgresql.image" . }}
         imagePullPolicy: "{{ .Values.image.pullPolicy }}"
+        command:
+          - /bin/bash
+          - -c
+          - |
+            chmod -R go-rwx /bitnami/postgresql/data
+            rm -vf /bitnami/postgresql/data/postmaster.pid
+            exec /app-entrypoint.sh /run.sh
+        lifecycle:
+          preStop:
+            exec:
+              command: [ '/bin/bash', '-c', 'nami stop postgresql' ]
         resources:
 {{ toYaml .Values.Resources | indent 10 }}
         env:

Yes, we will also take a look at the logging issue!

@intelfx At the moment we have just released a new image fixing https://github.com/bitnami/bitnami-docker-postgresql/issues/79.
Once we check the logging issue we will update bitnami/bitnami-docker-postgresql#88

I have same environment, but another error:
nami    INFO  Initializing postgresql
postgre INFO  ==> No injected postgresql.conf file found. Creating default postgresql.conf file...
postgre INFO  ==> No injected pg_hba.conf file found. Creating default pg_hba.conf file...
postgre INFO  ==> Deploying PostgreSQL with persisted data...
postgre INFO  ==> Configuring PostgreSQL...
postgre INFO  ==> Configuring replication parameters...
postgre INFO  ==> Configuring permissions for config files...
postgre INFO
postgre INFO  ########################################################################
postgre INFO   Installation parameters for postgresql:
postgre INFO     Persisted data and properties have been restored.
postgre INFO     Any input specified will not take effect.
postgre INFO   This installation requires no credentials.
postgre INFO  ########################################################################
postgre INFO
nami    INFO  postgresql successfully initialized
INFO  ==> Starting postgresql...
nami    ERROR Unable to start com.bitnami.postgresql: pg_ctl: could not start server
Examine the log output.

@okgolove That's the second problem with similar symptoms. See here for more details: https://github.com/bitnami/bitnami-docker-postgresql/issues/79#issuecomment-409599880

@intelfx thank you for the link, I've used workaround with lifecycle!

I have this exact issue, but I cannot see any progress after the last @tompizmor comments


Request: Solo raid frames

current addon I use for this has some errors ( https://www.curseforge.com/wow/addons/blizzard-raid-frames-solo-frame )
I think it would be a great optional extra in this addon and to cut down the number of add-ons and raid frame errors.

I've already looked into this and I'm sorry to say that it is really, really hard to get the raid frames to show full time. Every time I've tried to make it work it just ends up with non-stop taint errors. This is a behavior that Blizzard really doesn't want to happen, and they've put a lot of code in place to prevent it for whatever reason. Unfortunately, knowing that there's no solution here, at least for now, my hands are tied. I'm not going to implement anything that is overly hacky and prone to errors. 😕


Trigger-Warning-App

I think this would be a very useful app, as I`ve been looking for something like that for a long while now.

Hello everyone 👋
I hope this message finds you well. As you may know, the original repository for app ideas has not been updated in a while and is no longer actively maintained. However, I'm excited to let you know that a new repository has been created to continue this project (https://github.com/vincent0426/app-ideas).
The new repository aims to provide a comprehensive list of practical and achievable app ideas that developers of all levels can work on to improve their skills and build their portfolios. We welcome contributions from anyone who wants to add their own app ideas or improve the existing ones, and we are also looking for volunteers who can help maintain the repository and keep it up to date.
If you are interested in contributing or maintaining this project, please head over to the new repository (https://github.com/vincent0426/app-ideas) ⭐ and take a look at the existing issues and pull requests. Feel free to open a new issue if you have an app idea to suggest or if you have any questions about the project.
Thank you for your attention, and I hope to see you in the new repository soon! 💖

⚠ This message was generated by a robot 🤖, if this message reached you, consider leaving a star for this robot, repository link
⭐ https://github.com/aldairandre/github-bot ⭐


Some colombiaTV channels not watchable

Hi Diego,
I cannot watch some of the channels listed in the addon, for example, Señal Colombia. After clicking on the channel, the blue wheel appears for a short time and nothing else happens. The same occurs for other channels. They were working fine time ago...  I hope you can manage some time to check what's wrong
Env: Kodi Leia 18.9 on Ubuntu 18 and fire tv stick

Hello,
Please update to the 1.7.0 version Señal Colombia is working right now.

Hi @diegofn , I updated to kodi 19, tried to install the add-on but I'm getting "dependency on xmbc.python 2.14.0 could not be satisfied", any idea?

Hello, you need to install the 1.7.0 with python3 support


Build errors after upgrading to @ngneat/elf 1.5.0

Which @ngneat/elf-* package(s) are the source of the bug?
store
Is this a regression?
Yes
Description
Elf 1.5.0 seems to incorrectly import filterand take from rxjs. Root cause of the isse seems to be:

in index.esm.js being used here:

Downgrading to 1.4.0 solves the issue.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
./node_modules/@ngneat/elf/index.esm.js:22:55-61 - Error: export 'filter' (imported as 'filter') was not found in 'rxjs' (possible exports: ArgumentOutOfRangeError, AsyncSubject, BehaviorSubject, ConnectableObservable, EMPTY, EmptyError, GroupedObservable, NEVER, Notification, NotificationKind, ObjectUnsubscribedError, Observable, ReplaySubject, Scheduler, Subject, Subscriber, Subscription, TimeoutError, UnsubscriptionError, VirtualAction, VirtualTimeScheduler, animationFrame, animationFrameScheduler, asap, asapScheduler, async, asyncScheduler, bindCallback, bindNodeCallback, combineLatest, concat, config, defer, empty, forkJoin, from, fromEvent, fromEventPattern, generate, identity, iif, interval, isObservable, merge, never, noop, observable, of, onErrorResumeNext, pairs, partition, pipe, queue, queueScheduler, race, range, scheduled, throwError, timer, using, zip)

./node_modules/@ngneat/elf/index.esm.js:22:90-94 - Error: export 'take' (imported as 'take') was not found in 'rxjs' (possible exports: ArgumentOutOfRangeError, AsyncSubject, BehaviorSubject, ConnectableObservable, EMPTY, EmptyError, GroupedObservable, NEVER, Notification, NotificationKind, ObjectUnsubscribedError, Observable, ReplaySubject, Scheduler, Subject, Subscriber, Subscription, TimeoutError, UnsubscriptionError, VirtualAction, VirtualTimeScheduler, animationFrame, animationFrameScheduler, asap, asapScheduler, async, asyncScheduler, bindCallback, bindNodeCallback, combineLatest, concat, config, defer, empty, forkJoin, from, fromEvent, fromEventPattern, generate, identity, iif, interval, isObservable, merge, never, noop, observable, of, onErrorResumeNext, pairs, partition, pipe, queue, queueScheduler, race, range, scheduled, throwError, timer, using, zip)

Please provide the environment you discovered this bug in
Angular 13 with Elf

Anything else?
No response
Do you want to create a pull request?
Yes

That's because you're using Rxv6


Add Blind_call call type

This PR adds the Blind_call call type. To compare the call semantics of this with the others:

Call repesents a plain call, conveying permission to the child (and potentially it's children, via delegate call) to use the token_id derived from the caller's account ID
Delegate_call represents a call as if this node was not in the stack, passing permission to use the token_id given to this node down to its child
Blind_call is a call that conveys no permission to its children to use its token_id

the current proposed semantics are that this also resets the stack of callers visible to the zkApp. Do we also need a No_token_call that also doesn't pass token_id, but doesn't reset the stack?

This builds upon #12450.
Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me

Can the above description be added to where the data type is defined in the code, for easy future reference?

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


failed to start application

Compiler message:
../../Flutter_SDK/.pub-cache/hosted/pub.dartlang.org/flushbar-1.9.1/lib/flushbar_route.dart:273:8: Error: The method 'FlushbarRoute.install' has more required arguments than those of overridden method 'OverlayRoute.install'.
void install(OverlayEntry insertionPoint) {
^
../../Flutter_SDK/packages/flutter/lib/src/widgets/routes.dart:40:8: Context: This is the overridden method ('install').
void install() {
^
../../Flutter_SDK/.pub-cache/hosted/pub.dartlang.org/flushbar-1.9.1/lib/flushbar_route.dart:281:18: Error: Too many positional arguments: 0 allowed, but 1 found.
Try removing the extra positional arguments.
super.install(insertionPoint);

I found that upgrading flushbar to ^1.10.4 fixes it.
flushbar: ^1.10.4

I found that upgrading flushbar to ^1.10.4 fixes it.
flushbar: ^1.10.4

thanks


Proxifier for Mac 3.12

Simple to use and configure macOS application designed from the ground up to help any app to connect to the Internet through an HTTPS or SOCKS proxy. Proxifier is designed to allow network applications that are not able to work through proxy servers to operate through a SOCKS or HTTP proxy server or a chain of proxy servers.


-p command-line switch does not disable plugin-manager installed architectures

-p on the command-line is supposed to disable all plugins. It appears to disable all plugins except any architecture plugins or BinaryView plugins installed via the plugin manager. All other plugin manager plugins are disabled, and all plugins in the user folder are disabled.

Easy work-around is of course to just manually disable plugins but still annoying that it's required.


VIM-1287 fix di,cs TextObject processing when carret is inside "string"

This align behavior with VIM of di and cs inside strings.
Without this invoking di on:
{"{foo, "<caret>bar", baz}"}
Wiil result in only:
{}
When in VIM version result is:
{"{}"}
Same behavior is observed in surround plugin processing.
This is not elegant fix but it is minimal.
Please let me know if anything should be done additionally.
Also, thank you for maintaining such amazing project.

Thank you for a feedback.
Looks like i will need to add a lot more test scenarios to root this problem out and create correct fix.

Closing this one in favor of #130.


Positions in Hyperbolic Plots

I have added an offset of +nu_limit to nu_values . Issue #295  is addressed.

Could you send a couple of screenshots with the before and the after behavior? Like this: https://github.com/poliastro/poliastro/issues/111#issuecomment-355731620

Please rebase!

There is a problem in this approach. When we add an offset of "+nu_limit" to "nu_values" the values in "nu_values" become form 0 to 2nu_limit. Now this goes to a function nu_to_F which in turn computes a logarithmic value, which does not get computed when we give 0 to 2nu_limit

I thought about this carefully. The error is a bit obscure, but probably due to the fact that there are NaN values appearing in the array:
In [3]: Time.now() + 1 * u.h
Out[3]: <Time object: scale='utc' format='datetime' value=2018-02-23 11:06:07.789386>

In [4]: (0 * u.h) / (0 * u.h)
/home/juanlu/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/quantity.py:641: RuntimeWarning: invalid value encountered in true_divide
  *arrays, **kwargs)
Out[4]: <Quantity nan>

In [5]: Time.now() + (0 * u.h) / (0 * u.h)
/home/juanlu/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/quantity.py:641: RuntimeWarning: invalid value encountered in true_divide
  *arrays, **kwargs)
---------------------------------------------------------------------------
UnitConversionError                       Traceback (most recent call last)
~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/time/core.py in __init__(self, val, val2, format, scale, copy)
   1534                 try:
-> 1535                     val = val.to(u.day)
   1536                     if val2 is not None:

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/quantity.py in to(self, unit, equivalencies)
    843         unit = Unit(unit)
--> 844         return self._new_view(self._to_value(unit, equivalencies), unit)
    845

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/quantity.py in _to_value(self, unit, equivalencies)
    815         return self.unit.to(unit, self.view(np.ndarray),
--> 816                             equivalencies=equivalencies)
    817

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/core.py in to(self, other, value, equivalencies)
    978         """
--> 979         return self._get_converter(other, equivalencies=equivalencies)(value)
    980

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/core.py in _get_converter(self, other, equivalencies)
    912
--> 913             raise exc
    914

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/core.py in _get_converter(self, other, equivalencies)
    898             return self._apply_equivalencies(
--> 899                 self, other, self._normalize_equivalencies(equivalencies))
    900         except UnitsError as exc:

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/units/core.py in _apply_equivalencies(self, unit, other, equivalencies)
    882             "{0} and {1} are not convertible".format(
--> 883                 unit_str, other_str))
    884

UnitConversionError: '' (dimensionless) and 'd' (time) are not convertible

During handling of the above exception, another exception occurred:

ValueError                                Traceback (most recent call last)
~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/time/core.py in __add__(self, other)
   1373             try:
-> 1374                 other = TimeDelta(other)
   1375             except Exception:

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/time/core.py in __init__(self, val, val2, format, scale, copy)
   1540                                      'be used to initiate {0} instances .'
-> 1541                                      .format(self.__class__.__name__))
   1542                 format = 'jd'

ValueError: Only Quantities with Time units can be used to initiate TimeDelta instances .

During handling of the above exception, another exception occurred:

OperandTypeError                          Traceback (most recent call last)
<ipython-input-5-19cbc565acb7> in <module>()
----> 1 Time.now() + (0 * u.h) / (0 * u.h)

~/.miniconda36/envs/poliastro36/lib/python3.6/site-packages/astropy/time/core.py in __add__(self, other)
   1374                 other = TimeDelta(other)
   1375             except Exception:
-> 1376                 raise OperandTypeError(self, other, '+')
   1377
   1378         # Tdelta + something is dealt with in TimeDelta, so we have

OperandTypeError: Unsupported operand type(s) for +: 'Time' and 'Quantity'

The reason why we have NaN values is because we are going above the maximum true anomaly for which the hyperbolic orbit makes sense. Therefore, we have to discard the offset solution (I'm updating the original issue with this information).
The current code "selects a sensible limiting value":
https://github.com/poliastro/poliastro/blob/44dbc6e26f2d0a6b395a910c39c9e8131c8946b2/src/poliastro/twobody/orbit.py#L296-L300
But this value might be lower than the actual anomaly of the point we're plotting!
https://github.com/poliastro/poliastro/issues/111#issuecomment-355746579
Therefore, the sensible value has to be the maximum between r = 3p and r = current_r. @shreyasbapat could you please try this approach instead?

And also, we have to remove the assumtion that the first point is the current point in the plotting code, as I said in #295.

Then what would be the first point? Won't we specify some point?

I will try this approach tonight itself :)

On second thought, perhaps we can do something like this:
nu_limit = # ...
nu_values = np.linspace(-nu_limit, nu_limit, values)
nu_values = np.insert(nu_values, 0, current_nu)

what do you think?

What is this current_nu?

The nu of the orbit that we're plotting.

Okay! Let's give it a try!

Something like this!

Nice! Now the plot appears where it is supposed to appear. Still it's not the output that I would like, but I will take care of that in a future pull request :)
This needs at least one test to pass.

I will take care of the test cases!

Yeah! It's not very exact :/

According to codecov, this code is not being covered:
https://codecov.io/gh/poliastro/poliastro/compare/36379a98f19dda2e037de6dc2547084450fec93a...0146c12ac973c86116894afad6c550a85f6f7b18
And it makes sense, because for tests to run, the function name has to start with test_ :)
However, I went to the Travis build and saw that the test names are not there. I will fix that myself on another PR.


Introduce COMPONENT labels, improving conda build support

This is cmake-only continuation of #562, which fixes cmake/conda build problems.
Labels are needed for convenient splitting of the installation files into different packages.
@pearu I hope I have not missed your comments in this PR.

a kind ping, @alexbaden @pearu


BoxfitSerializer unresolved

I've done a clean/rebuild project and gradle sync but still do not see this class.  Im using Kotlin, although I couldnt get it to work in Java either.  For Kotlin I switch to kapt instead of annotationProcessor.  Any advice?

ah got it, I wasn't annotating @BoxClass so it wasn't generating.  doh

@ManueGE I am having same issue as above but can not get it through.
My setup: kotlin with objectbox and retrofit.
I added all annotation in my entity class from objectbox:  @BoxfitClass and @BoxfitField but the BoxfitSerializer class is not generated. Tried to rebuild/invalidate cache/clean nothing works.
Any idea how I could debug that issue and find out why the class is not generated?


add language server support for brightscript

I am not quite sure what is failing on the docs checking.  Can I get any help on this one?

Don't edit the server_configurations.md file it auto generate by ci.

open a new pr only with brightscript file .don't edit the server_configruations.md file


shell: modules: kernel: include EXTRAVERSION when printing version

Include the full version in the output of the "kernel version" shell subcommand. Previously, EXTRAVERSION was not included, causing e.g. "3.6.0-rc1" to be printed as "3.6.0".

IMO the test is wrong and should be using the version API instead of just relying on KERNEL_VERSION_STRING.
This code in the shell module existed since 2016, the test just came in the last release.
Oh well

Labeling as "hotfix" since this is blocking us from tagging v3.6.0-rc1 in https://github.com/zephyrproject-rtos/zephyr/pull/68575.


SSL support in MongoDB

Goal
Support SSLMode for MongoDB databases deployed by KubeDB.
Motivation
x509 is the recommended clusterAuthMode for replicaSet or sharding. So, while providing x509 certificates, it's possible to configure the connectionmodes. To be specific,

Value
Description

disabled
The server does not use TLS/SSL.

allowSSL
Connections between servers do not use TLS/SSL. For incoming connections, the server accepts both TLS/SSL and non-TLS/non-SSL.

preferSSL
Connections between servers use TLS/SSL. For incoming connections, the server accepts both TLS/SSL and non-TLS/non-SSL.

requireSSL
The server uses and accepts only TLS/SSL encrypted connections.

Now, some users may prefer requireSSL, whereas some users preferSSL. So, it's better to give the users the ability of configurations through CRD specs.
Required Spec Fields

enableSSL (default, true)
ClusterAuthMode for replicaset or sharding. (default will be x509 if enableSSL is true.)
SSLMode for standalone or clusters. (default, preferSSL if enableSSL is true.)
Certificate Secret Name: Certificate Secret will hold tls.crt and tls.key (or .pem file).

Development Cycle:

Ensure both x509 and KeyFile support in ReplicaSet.
Add Sharding.
Ensure both x509 and KeyFile support in Sharding.
Ensure SSL support in Standalone Mode.
Ensure snapshots to work all configurations.
Finally, add docs.

SSL with official mongodb docker image example: https://github.com/docker-library/mongo/issues/250#issuecomment-370981032

mongodump when sslMode is requireSSL. https://www.grainger.xyz/backup-and-restore-mongodb-with-x-509-authorisation/


The automatic generator-feathers update does not work.

Run the generator. Says generator is out of date. Accept generator update. Rerun the generator.  Says generator is out of date.

This must be an old version of feathers-cli since the update check has been removed in v2. feathers --version should show something around 2.3.5.

Were you able to verify? I definitely want to bring the update check back but the current version shouldn't show it at all.


Provide "Empty project" intended as base for new app project.

To further simplify starting a new app project in Evothings Workbench, provide a simple project called e.g. "Empty project". This is a part of work involving adding a new section of the workbench containing all examples in contrast to the project list.

Consider adding New and Copy buttons instead.


FI-1698: Presets with options

Summary
Testing Guidance

Codecov Report
Base: 73.62% // Head: 73.69% // Increases project coverage by +0.07% :tada:

Coverage data is based on head (bf01761) compared to base (ac2cb37).
Patch coverage: 95.00% of modified lines in pull request are covered.

:exclamation: Current head bf01761 differs from pull request most recent head 22b4274. Consider uploading reports for the commit 22b4274 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #304      +/-   ##
==========================================
+ Coverage   73.62%   73.69%   +0.07%
==========================================
  Files         190      191       +1
  Lines        9270     9296      +26
  Branches      767      771       +4
==========================================
+ Hits         6825     6851      +26
  Misses       2037     2037
  Partials      408      408

Flag
Coverage Δ

backend
94.21% <95.00%> (+0.04%)
:arrow_up:

frontend
63.55% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/inferno/entities/test_group.rb
98.03% <ø> (-0.04%)
:arrow_down:

lib/inferno/repositories/test_sessions.rb
93.33% <50.00%> (+0.15%)
:arrow_up:

dev_suites/dev_options_suite/options_suite.rb
96.49% <100.00%> (+0.06%)
:arrow_up:

...ferno/apps/web/controllers/test_sessions/create.rb
89.47% <100.00%> (ø)

...rollers/test_sessions/session_data/apply_preset.rb
95.65% <100.00%> (ø)

lib/inferno/config/boot/db.rb
75.00% <100.00%> (ø)

lib/inferno/repositories.rb
100.00% <100.00%> (ø)

lib/inferno/utils/preset_processor.rb
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Optional subtitle

Optionally, provide a subtitle, typeset in the header, in smaller font.
Not very happy with how it looks when the menu is reduced to burger, but cannot figure out where to control positioning when responsive'ing for a narrow screen. Please help.

What do you mean by subtitles?
You mean text under the description in the main banner as the date in a post?

Please see here http://deg.iit.demokritos.gr, a site using a modified Type-on-Strap, where I am using an earlier version of this PR that doesn't correct the margin. It has a smaller subtitle under the "Robotics activity" title. The current PR improves the placement relative to the avatar, but only when the menu is shown, not when the burger is shown.

Ok I will take a look at it later then ;)

After looking at it, I prefer not to add this one on the theme.
Thanks for the pull request.


[WIP] Interface for zulip bot server and slack's outgoing webhooks

Automated message from Dropbox CLA bot
@vabs22, it looks like you've already signed the Dropbox CLA. Thanks!

@robot-dreams my main concern in this PR is interface for slack. I have took the keys info from slack's documentation and added it here, but I haven't been able to test it for real i.e. sending requests to actual outgoing webhooks and receiving successful response. This is the reason for WIP.
About UI changes, I have created this PR which contains the required UI, but has only generic interface. So depending upon which PR gets merged first, I will update the other one appropriately.

@robot-dreams I have updated this PR by changing to tuple instead of dictionary.
Next if you and @timabbott think the slack's interface is fine, we can go ahead and remove "WIP".

@vabs22 I took a look, and the Slack implementation looks reasonable, though I think it's really important that we test that before merging.  What is blocking testing that implementation?
I have two major questions about this implementation:

I don't understand why you have both the Generic format and ZulipBotServer format; those seem like duplicates?
I don't understand why you have the response_required field?  It seems to me like we should just handle a response if the bot returned one, and have some default return value that doesn't contain a response that bots should use in the event that they don't want to send a response.  That puts the control over whether to respond on the bot code side, so bot authors can customize.

We added 'response_required' primarily to eliminate 2 response messages to the user, one from the bot itself and other from outgoing webhook system. With this, bot would be able to indicate that he would be sending the response itself, so the system doesn't need to give one. Else he can give the system the response to send to the user. Also as a special customization bot would be able to skip any response message.
At the moment, interface for zulip not server is almost same as generic interface. The difference is the response required is no. I am fine with dropping it at the moment and have some other fix to prevent 2 response messages, but I would prefer to keep it this away, to facilitate changes related to zulip bot server easily.
I had tried to find a third party service which services a slack's outgoing webhook, but was unable to, I will try again to try to test it at the earliest. One thing I observed was, slack also sends these values as form post variables as well.

@timabbott @robot-dreams I have tested the slack's interface in real time and it is working. I have now updated the PR and removed WIP. Please take a look.

@vabs22 @robot-dreams what's the status of this effort?  Are there pieces that I should review for merge at this point, or are you two still iterating together?

@vabs22 there's a lot of refactoring in these commits that should really have been split out into independent, smaller changes.  E.g. the change of interface for get_service_profile from passing email+realm_id to passing user_profile_id is good, but it should be its own smaller commit.

This looks generally sane, but doesn't have any tests.  @vabs22 can you add tests that show what format requests will be sent by the Slack format outgoing webhook?

Merged via #5896, thanks @vabs22!


Is it possible to save the widget view as an html?

Hi !
Was wondering if we can save the view as an HTML for later use?

Hi, yes its possible
If you use jupyter notebooks you can do so using nbconvert
You may have to save the widget state first (in jupyter lab: Settings > Save Widget State Automatically)
then convert to html with jupyter nbconvert --to html filename.ipynb


t3-rosecurrency

Transaction IDs and time period when the transactions were sent is at 3fadef3
Account addresses is at 7a478d5

confirmed:T3
address:35yNvw6Q3rqNfoeWa7h1ZDi2fP3o7MGWC7dvGhP3s38eTyRiF9

confirmed:T3
address:35yNvw6Q3rqNfoeWa7h1ZDi2fP3o7MGWC7dvGhP3s38eTyRiF9


HLS level restart after loop

Browser: any browser
OS: any os
Clappr Version: latest
Description:
Clappr will restart HLS level to 0 after loop even if higher level was loaded during video playback. Check fiddle for more info (http://jsfiddle.net/jL66pops/)
Steps to reproduce:

Check the issue here or follow the steps below: http://jsfiddle.net/jL66pops/
Load any .m3u8 HLS playlist with at least 2 levels
Set HLS config to load level 0 at start and loop to true
Wait until clappr fetches next level
After video loops, level will jump back to 0 instead staying on level 1

Issue is reproduced on http://cdn.clappr.io/

+1

I have the same problem, any word on this?

It should be possible to partially fix this issue, but keep in mind that it will be only if player is using HJSJS playback. For native playback (iphone for example) i am not sure we can change the default behaviour.

Tried without clappr using only HLSJS
http://jsfiddle.net/jL66pops/1/
Same issues... How to configure HLSJS to continue playing loaded level?

@hlozancic there is a startLevel configuration option and a property in HLSJS which allow you to configure default star level. Since Clappr is listening to hls LEVEL_SWITCH event, i think it is possible to create a feature to keep current level and then set it as start level if Clappr Player loop option is set to true.

I'm already using startLevel config... Will try to listen on level_switch and set level manually to higher when switched or something... Will send fiddle later today

using startLevel config isn't enough, you have to lisent to LEVEL_SWITH event.
For example, let's suppose you set start level to 1, then video play, and for an XYZ reason player switch to level 0 at end, then on loop video will start from level 1 instead of level 0.
This is why i think a solution is to listen to LEVEL_SWITCH event to store the current level, and set it as startLevel only if player loop option is set to true.


Should always query the latest checkin info from InstanceID.

This fixes a bug that when we delete IID, IID refreshes new checkin info and FCM didn't query the checkin because it stops query if checkin exists.
There was a check to see if a valid checkin info existed before query checkin. This is not a proper check because when checkin is refreshed, checkin info do existed, but we still need to perform the query to get the latest checkin. So remove the check.
Also remove some extra tryToLoadValidCheckinInfo check since the function it's called after that will trigger the tryToLoadValidCheckinInfo check anyway.

Should fix the CLA again. Kicking a new run.

File a new PR (https://github.com/firebase/firebase-ios-sdk/pull/1170) and will close this one because the CLA is not setup right.


Doesn't build on windows 10 for target electron (7.1.11 and 8.0.0)

Since there are no prebuild binaries for electron libxmljs gets rebuilt during yarn install.
This used to work with electron 4, not sure why or why it stopped working.
The error message is
LINK : fatal error LNK1194: cannot delay-load 'node.exe' due to import of data symbol '"__declspec(dllimport) const v8::ArrayBuffer::Allocator::vftable'" (_imp??_7Allocator@ArrayBuffer@v8@@6B@)'; link without /DELAYLOAD:node.exe [c:\Work\vortex\node_module s\libxmljs\build\xmljs.vcxproj]`
Now with electron afaik it has to be delay-loaded because electron.exe has nodejs statically linked in so it takes over that role.
Besides, the export of ArrayBuffer::Allocator shouldn't be necessary as far as I understand.
After a lot of digging I found that in the binding.sln file that node-gyp generates, the macro BUILDING_NODE_EXTENSION isn't defined which (as far as I understand it) is supposed to be defined and it would have suppressed the export of ArrayBuffer allowing the build to work.
Unfortunately I have no clue why that macro isn't defined, I thought node-gyp was supposed to do that automatically (through addon.gypi) - no clue why it doesn't do it for libxmljs (or at least for the Release build because the macro is defined in the debug build).

I'm also facing the same issue.

My fork should work on windows electron. (https://github.com/marudor/libxmljs2)

@marudor , with libxmljs2 I see the same errors when running electron-rebuild.

[deleted]

The error message is
LINK : fatal error LNK1194: cannot delay-load 'node.exe' due to import of data symbol '"__declspec(dllimport) const v8::ArrayBuffer::Allocator::vftable'" (_imp??_7Allocator@ArrayBuffer@v8@@6b@)'; link without /DELAYLOAD:node.exe [c:\Work\vortex\node_module s\libxmljs\build\xmljs.vcxproj]`

[deleted]

After a lot of digging I found that in the binding.sln file that node-gyp generates, the macro BUILDING_NODE_EXTENSION isn't defined which (as far as I understand it) is supposed to be defined and it would have suppressed the export of ArrayBuffer allowing the build to work.

Thanks, @TanninOne . I fix this problem by modifying binding.gyp and adding BUILDING_NODE_EXTENSION define for OS=="win".
https://github.com/MrMYHuang/libxmljs/blob/c12974c30ece15075dcfacc92a84b8d35f88ba7c/binding.gyp#L82-L86


Add Void type and expect_no_error method

As discussed in #476.
Went with the name Void for now, but as far as I can see we have the following choices:

Haskell: Void (could be confusing for people coming from C-like languages?)
Elm: Never (works nicely for the error case IMO, smth can  "never" fail)
Scala: Nothing (subtype of every other type, referring to the bottom of the OO type hierarchy)
Type Theory: Bottom

I also added a combinator method expect_no_error that can be used to convert existing cases of Future<Error=()> into Future<Error=Void>. It might also make sense to add a function going the other way, e.g. Future<Error=Void> into Future<Error=()> in order to conform with existing APIs expecting Error=(). I'm also happy to remove this from the PR for now and open a separate one once we landed the Void type.
Let me know what you think!

I don't really know if this crate wants to add a Void type. If using some sort of Void type is something that the lib really wants to do, then it probably should be provided by a 1.x crate entirely dedicated to this type so that other crates can also depend on it.

Worth pointing out that this crate already exists as void, with nearly 4k daily downloads, and being dependent on by crates like unreachable, nix and rotor.
I'd be happy to change the PR to use this crate. Curious what @alexcrichton thinks.
FWIW I think there are also good arguments for Void being part of this crate. The futures/tokio ecosystem is the first place where I have seen a major use-case for Void being part of a public API (as documented by the linked futures and tokio issues).
I'll do some more research into how the existing void crate is used by it's dependents, and also in which ways other language ecosystems use uninhabitable types.

I've been feeling lately that the futures ecosystem needs to canonicalize around some definition of an empty type. Fundamentally not all futures need type Error;, and we're just seeing that pop up from time to time, and I think everyone who doesn't need type Error; should be interacting with the futures crate in similar fashions.
I also don't really see a huge amount of benefit in sharing a an empty type with other crates in the Rust ecosystem. It seems like the type will never really need to unify as the whole point is to "get out of the world of Result" as quickly as possible. In that sense I don't see a need here personally that it's critical to pick up an existing abstraction.
The most valuable thing here, though, I believe is how you interact with Future<Error = Void>. Right now this adds expect_no_error which is sort of like "unwrap for futures" but I'd like to also see combinators along the lines of an infallible wait if the error type is Void, an infallible poll, etc. @srijs would you mind gaming out these areas?

Not at all! Couple of questions/thoughts on my mind:

Some of the cases you mention (infallible wait and poll) as well as potentially others (e.g. infallible then/and_then) could also be covered by some sort of InfallibleResultExt extension trait. Any thoughts on that?

Should the set of infallible methods live in the top level futures trait? If yes, does it make sense to agree on a standard naming convention?

Alternatively, I was reading Alexis RFC on fallible/infallible allocation in collections, and it got me thinking: How about a method like Future::infallible(self) -> InfallibleFuture<Self> where Self: Future<Error=Void>, where InfallibleFuture<F> can implement the infallible method variants w/o any name clashes, and also implements IntoFuture<Future=F>?

Let me know what you think. Also happy to explore multiple avenues.

Hm good questions! I'm not really sure what the best answers are though or what this should look like in the long run. The idea of an InvallibleFuture<F> seems plausible but I'm not sure what the relative costs and such would be to alternate strategies.
My thinking originally was that the methods and extensions would live on the Future trait itself, but it's a good point that maybe they shouldn't! If you wanna play around locally with various solutions are and see what the ergonomics are, maybe that'd help guide us? I could also try to generate some use cases for infallible futures and see if that helps.

@alexcrichton just pushed the result of my experimentation to the branch.
I have experimented with three approaches; the InfallibleFuture struct, an InfallibleFutureExt extension trait, as well as adding the combinators directly to the Future trait. I've stuck with the latter, since the first had slightly weird ergonomics and could be confusing (for instance, does an infallible async function now return InfallibleFuture<impl Future<...>> or impl Future<...>), and the second seemed was making things more cumbersome by requiring an additional import at every point where you want to e.g. chain another future with some infallible future.
The most important combinators for both streams and futures are expect_infallible and infallible_cast_err. These two combinators are duals of each other, in a sense; the former converts a future with an arbitrary error into an infallible future, while the latter converts an infallible future into a future with an arbitrary error type.
I also added a few convenience combinators that make it easier to combine infallible futures with fallible ones, w/o requiring the use of infallible_cast_err in lots of places.
Additionally, both Future and Stream now have an infallible variant of wait, which returns a simple value instead of a result.
Please let me know what you think so far, if I should remove combinators, or add different ones, etc!

@alexcrichton Friendly ping, would appreciate some feedback. Let me know if you're busy currently, then I'll back off a little :)

Oh oops sorry I thought I commented on this...
In any case, thanks for the investigation here! This is looking pretty nifty to me. My main thought is that this seems like it may be biasing a bit much towards creating a Future with an error type of Never. I'd imagine, for type inference reasons, that we'd instead want to go the other way and get futures to play nicely with other types in the world without Never.
For example this adds an async_fn future with an error type of Never, but I think the equivalent poll_fn should also work, right? That is, if you use poll_fn and don't actually constrain the error type, then it's a generic type variable that could then also get bound to Never? Although I could imagine in some circumstances this'd require an explicit type annotation to give it some value which can certainly be annoying.
Similarly though I'm wary of a combinator like expect_infallible as it's essentially "unwrap for futures", but the return value still has an error type in it. For example Result::unwrap discards the error and lets you work with a T, but Future::expect_infallible forces you to still work with a future and the possibility of an error (it doesn't statically remove the error type).
Some other combinators I'd expect to sort of fall out of the various parts of other combinators, for example:
a.infallible_cast_err() => a.map_err(|e| e.never())

I was thinking that infallible_then may fall into this category but I think it may not quite be the case...
I guess in general, I wonder if we can possibly trim this down to be a little more conservative? We've always got the option of adding more combinators and types and such in the future, but removing things tends to be pretty hard...

Thanks for the feedback @alexcrichton!
I appreciate that the number of new combinators added here is quite high, and am happy to cut back.

My main thought is that this seems like it may be biasing a bit much towards creating a Future with an error type of Never. I'd imagine, for type inference reasons, that we'd instead want to go the other way and get futures to play nicely with other types in the world without Never.

I agree in so far that when a generic combinator exists that will work for futures of any error type, and thus works for Never as well, a specialised variant is probably not necessary (async_fn probably falls into this camp). Furthermore if the future is already generic, there might be less need for using infallible_cast_err often, which is a good thing.
However I believe that in some cases this results in having to stick a lot of manual type arguments on function calls. But for these cases it's probably okay to not include specialised variants for now and just see what issues crop up in practice and need fixing.

Some other combinators I'd expect to sort of fall out of the various parts of other combinators

I guess if you took it to the extreme, literally all combinators presented here can be emulated via already existing ones:

a.infallible_cast_err() as you pointed out is a.map_err(|e| e.never())
async_fn(f) is poll_fn::<_, Never, _>(|| Ok(f()))
a.expect_infallible() is a.then(|r| ok::<_, Never>(r.expect("...")))
a.infallible_then(f) is a.then(|r| f(r.unwrap()))
a.infallible_poll() is a.poll().unwrap()
a.infallible_wait() is a.wait().unwrap()

Although all of these combinators provide a somewhat less-noisy way of achieving the same outcome compared to existing combinators, broadly speaking it seems they fall into two camps:

The type of combinator mentioned earlier that assists type inference in some cases / might require less explicit type annotations in some cases (infallible_cast_err, async_fn and expect_infallible)
The type of combinator that provides a safe way of unwrapping (infallible_then, infallible_poll and infallible_wait)

Going back to what you said in an earlier comment:

The most valuable thing here, though, I believe is how you interact with Future<Error = Void>. Right now this adds expect_no_error which is sort of like "unwrap for futures" but I'd like to also see combinators along the lines of an infallible wait if the error type is Void, an infallible poll, etc.

The combinators you reference here fall into the latter camp, so would it be fair to say that this is where you see the bigger value?
If that's the case, I think I agree. Having "safe" variants for result unwrapping helps a lot in writing safe code, and prevents me from hitting false positives when grepping for unwrap to identify places in a code-base where an error might lead to panic.
So my proposal would be to remove infallible_cast_err, async_fn and expect_infallible and retain infallible_then, infallible_poll and infallible_wait.
An alternative could be to expose the InfallibleResultExt extension trait so e.g. .infallible_poll() becomes .poll().unwrap_infallible(), however I believe infallible_poll to be more ergonomic since it doesn't require importing an additional extension trait.
Let me know what you think!

@srijs that sounds great to me! I agree that the most value from this is avoiding the false positive of "I need to audit this unwrap". I'm slightly worried that it's more ergonomic to unwrap than it is to call infallible_foo, but that's something we can perhaps smooth out over time.

I agree w/ @alexcrichton that all the combinators should be punted on. They can always be added later but not removed. It also adds a bunch of noise to the docs and presents decision points.

@alexcrichton Updated the PR to only include poll and wait variants. I've also decided to remove  infallible_then, since I realised it's unnecessary if the future is already universally quantified over Error.
I do believe once we change traits like Receiver/UnboundedReceiver to impl Future/Stream with type Error = Never, we might see a stronger need for a combinator like infallible_cast_err for ergonomic reasons (perhaps with a better name though).
In terms of ergonomics for the poll and wait variants, do you have other ideas how we could make them more ergonomic to use? Is it the conciseness of the name, or something else that is bothering you?
@carllerche Not sure if I understand what you are saying. Are you proposing to drop all combinators for now?

I also have a slightly different proposal I've been thinking about for a bit. If you feel it's to complex, I'm happy to table it, but I thought I'd just put it out there.
The goal of the proposal would be to safely take advantage of infallibility for things like Receiver/UnboundedReceiver as well as some of the cases in other crates (primarily tokio), without forcing a breaking change.
I'm thinking along the lines of this (and a similar setup for Stream):
trait InfallibleFuture {
  type Item;
  fn poll_infallible(&mut self) -> Async<Self::Item>;
}

impl<F: Future<Error=Never>> InfallibleFuture for F {
  type Item = <F as Future>::Item;
  fn poll_infallible(&mut self) -> Async<Self::Item> {
    self.poll().infallible()
  }
}

This should then allow us to then implement the infallible trait for existing structs:
impl<T> InfallibleStream for Receiver<T> {
  type Item = T;
  fn poll_infallible(&mut self) -> Option<Async<T>> {
    ...
  }
}

As soon as we change Receiver to impl Stream<Error=Never> in a future breaking release, we could simply remove the custom impl forInfallibleFuture.
An alternative to that which would be more in-line with the current approach in this branch would be  to introduce new structs such as InfallibleReceiver that implements Stream<Error=Never>, move the logic from Receiver to InfallibleReceiver, change Receiver to wrap InfallibleReceiver to re-use the logic, and then expose a method like Receiver::infallible that returns InfallibleReceiver.

I've gamed out the alternative strategy in #591

Friendly ping, @alexcrichton. Apologies if you are occupied at the moment!

Hey @srijs sorry for the delay, I've been super busy and haven't had a chance to get back to this yet :(
I haven't forgotten about it though!

Ok! We've started working on 0.2 and we've got a Never type there. I'm going to close this for now in favor of future work on that branch.


Speed up STRING ingest

Luca said he might want to try speeding up STRING ingest, possibly by parallelization.
Here is the ingest in question.
Possibly could parallelize here while reading lines, or maybe as @deepakunni3 said, this utility fxn could be sped up

Some questions on the utility: is there any reason why it returns None?

Some questions on the utility: is there any reason why it returns None?

No reason, other than to return a type of some kind for type-checking. Could refactor to return a boolean I guess?

Though it is possible to parse the lines using multiprocessing it is not possible to write the lines in the same way, how much memory do you think would it take to keep them in memory and write them all after the first read has finished?

Though it is possible to parse the lines using multiprocessing it is not possible to write the lines in the same way, how much memory do you think would it take to keep them in memory and write them all after the first read has finished?

Not sure, but you could get some idea by running:
python run.py transform -s StringTransform
then looking at the size of the files generated:
ls  -lh data/transformed/STRING/
At least a few gigs I bet

The file size is at 122M. So ingesting that into an in-memory data structure shouldn't be a problem at the moment. But note that we are dealing with just a subset of the original data by restricting to human PPIs.
The actual master file is 68GB (compressed). I doubt we will ever need to parse all of the file. Just highlighting the upper bounds of memory requirements.

Hi @LucaCappelletti94 - for clarity, can you confirm you are working on this? @deepakunni3 said he could handle this if you are not. Just trying to avoid duplicating effort

Yes, it should be done by the end of the morning.

I see that the same "seen" list is used for check for both the already seen proteins and genes: could this cause a name clash?

I'm working on this issue here.

I have refactored the code and replaced the lists with sets, so now that aspect should run a bit faster. I am not sure if parallelizing the I/O can add a significant speedup as the remaining data elaboration is minimal. What do you think?

@LucaCappelletti94 There shouldn't be a name clash for seen. The identifiers are mutually exclusive for gene and protein

I have refactored the code and replaced the lists with sets, so now that aspect should run a bit faster. I am not sure if parallelizing the I/O can add a significant speedup as the remaining data elaboration is minimal. What do you think?

Thanks Luca! A very dramatic speed-up, STRING ingest is now down to 2m!
(venv) ~/PycharmProjects/kg-emerging-viruses *speed_up_string $ time python run.py transform -s StringTransform
WARNING:ToolkitGenerator:class "pairwise interaction association" slot "interacting molecules category" does not reference an existing slot.  New slot was created.
WARNING:ToolkitGenerator:Unrecognized prefix: SEMMEDDB
[snip]
INFO:root:Parsing StringTransform
[transform.py][           transform] INFO: Parsing StringTransform

real    2m19.998s
user    2m14.680s
sys     0m2.388s

It almost leaves me with the doubt that I haven't done something wrong with the code: the output file looks okay? I think that other than the pythonification of the code the only real source of speed up was replacing the list with a set.

If this helps:
edges.tsv produced from your branch and from master is exactly the same (see m5 hash below, bak/ dir is produced from master).
Your nodes.tsv has fewer entries than master, but the few I checked out are just extra ENSEMBL ids not mentioned in edges.tsv
(venv) ~/PycharmProjects/kg-emerging-viruses $ ls -l  data/transformed/STRING/*.tsv data/transformed/STRING/bak/*tsv
-rw-r--r--  1 jtr4v  staff<PHONE_NUMBER> Apr  3 11:57 data/transformed/STRING/bak/edges.tsv
-rw-r--r--  1 jtr4v  staff     2456430 Apr  3 11:57 data/transformed/STRING/bak/nodes.tsv
-rw-r--r--  1 jtr4v  staff<PHONE_NUMBER> Apr  5 09:12 data/transformed/STRING/edges.tsv
-rw-r--r--  1 jtr4v  staff     2391930 Apr  5 09:12 data/transformed/STRING/nodes.tsv
(venv) ~/PycharmProjects/kg-emerging-viruses $ md5 data/transformed/STRING/*.tsv data/transformed/STRING/bak/*tsv
MD5 (data/transformed/STRING/edges.tsv) = c960835ae79f6235d8b4a7be6ce4372f
MD5 (data/transformed/STRING/nodes.tsv) = 21ea74367b01086301f4a9dfba6e1bb9
MD5 (data/transformed/STRING/bak/edges.tsv) = c960835ae79f6235d8b4a7be6ce4372f
MD5 (data/transformed/STRING/bak/nodes.tsv) = 408ed8393fbce7abcf20864cee5bbd77

Ok! That seems promising, I was worried that the speedup was caused by some coding mistake such as an if-condition that was never met. Out of curiosity, how much time was it required on the same machine before?

Out of curiosity, how much time was it required on the same machine before?

14 hours on my laptop - a very dramatic speed-up

Wow, @LucaCappelletti94 This is amazing! A simple change made all the difference!
For posterity: In Python, lists are slow in lookup for membership. Whereas, sets are dramatically faster because of the way set stores its values: hash tables.

For posterity: In Python, lists are slow in lookup for membership. Whereas, sets are dramatically faster because of the way set stores its values: hash tables.

Good to know - I didn't realize either how much quicker sets are

Should I proceed with the pull request?

@LucaCappelletti94 Yes, the output looks proper. Feel free to make a PR


doginals drc-20 wallet api support?

Hi, does okx wallet support inscription operations (deploy, mint, transfer, psbt, etc,.) for doginals drc-20, similar to the brc20 operations on btc (https://www.okx.com/cn/web3/build/docs/sdks/chains/bitcoin/provider#mint)?
Thanks!

You can refer to the test cases here
https://github.com/okx/js-wallet-sdk/blob/main/packages/coin-bitcoin/tests/doginals.test.ts

In the shared doginals test case, Here the private key is provided. Any document for its use with okx web3 wallet? Thanks!

You can refer to the test cases here https://github.com/okx/js-wallet-sdk/blob/main/packages/coin-bitcoin/tests/doginals.test.ts


deprecation: remove _allow_background_volume_commits experimental flag

Describe your changes
🧹 clean up.

Check these boxes or delete any item (or this section) if not relevant for this PR.

[x] Client+Server: this change is compatible with old servers
[x] Client forward compatibility: this change ensures client can accept data intended for later versions of itself

Changelog

The experimental allow_background_volume_commits argument, previously deprecated, is now removed.

@prbot approve


Added Scarf gateway to DevLake Docker Compose downloads

⚠ Pre Checklist
Please complete ALL items in this checklist, and remove before submitting
[ x ] I have read through the Contributing Documentation.
[ x ] I have added relevant tests.
[ x ] I have added relevant documentation.
[ x ] I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.
Summary
What does this PR do?
This PR updates the Merico DevLake Docker Compose configuration to fetch DevLake containers via a Scarf endpoint, so that DevLake maintainers can collect basic de-identified download and adoption metrics. It does not affect where the containers are being hosted, as Scarf is only redirecting traffic back to Docker Hub.
Does this close any open issues?
This does not close any open issues.
Other Information
This change was suggested by Merico and DevLake maintainers/team members in direct discussions, and is Scarf's first code contribution to DevLake! We have a separate PR up for the DevLake helm charts.

@Startrekzky Let's consider scheduling this into v0.19.

@hezyin v0.20 or later.
Hi @arjundevarajan , I have two questions.

Is this only for image downloading metrics? What other stats can I see?
What else should we do after merging this PR and the PR in helm chart repo?

Hi @Startrekzky sure, happy to help answer.

Scarf helps to collect with a variety of de-identified aggregate metrics: unique downloads, version distribution, device type distribution, method of installation, OS distribution, arch distribution, etc. Some further information can be found here: https://docs.scarf.sh/data-export/

After merging the two PRs, there's nothing else that needs to be done from a technical standpoint to start collecting data. This represents the simplest form of a Scarf integration, so it's possible that there are additional pieces of instrumentation that could be useful in the future, but for now this would be sufficient to collect some basic analytics.

@ZhangNing10 Arjun is OOO today so filling in with the v.0.17.0 docker compose change as requested. Please let me know if anything else is needed there!


Do you have a shell script to build protobuf-c.a for the ESPHost library?

To cross-compile protobuf-c some number of environment variables have to be set right.
so I guess you have a shell script somewhere?
is it available please?
I write Mbed EMAC for ESPHost and I want to make it work with Nano RP2040 Connect.

it is just another maidnl strangeness. the ESPhost/src/cortex-m33/libprotobufc.a has only protobuf-c.c which added to ESPhost/src/protobuf-c folder compiles fast with the rest of the library. I wasted so much time on this.

With #213 being merged, I'd say this issue can be considered closed - not by providing the build script, but by eliminating the need for it altogether.


php5enmod in php5.3.10 not available (Ubuntu 12.04)

"php5enmod was introduced in Debian in version 5.4.0~rc6-2 of the package php5" fkraiem at askubuntu.com
The exec of php5enmod in extensions.pp could be bypassed for php5.3.10 installations. Since 5.3.10 is the default apt package version for php in Ubuntu 12.04, we got an "Could not find command '/usr/sbin/php5enmod'" when installing modules.
Is there a clean way to get the installed version of php from within your module as bypass condition?
Other (dirty) workarounds to find an bypass condition could be to which php5enmod or grep in php -v.
Thank you,
Fabian

We removed PHP 5.3 support intentionally to make people use a supported PHP version (#44). Please upgrade to a newer version to receive security fixes and not be attackable. This module should have everything in place to do this from the ops side and if something is missing or needs fixing we'll be happy to assist.


implemented button to copy definition link

Closes #417
What new changes did you make? Tick all applicable boxes

[ ] Added new abbreviation
[ ] Fixed something in the source code
[x] Added a new feature
[ ] Fixed the docs (README.md, CONTRIBTUING.md, etc)

Created the button to copy the link and share definition. Tried to stay consistent with the rest of the website in terms of design. Let me know if you want to change.
Describe the new changes you added.

Share a screenshot of new changes

Apologies. I hadn't worked with tailwind before so it seemed a little messier at first but certainly is a lot more concise! It seems to be working as expected on the preview. LMK if anything else needs changing.

This looks splendid! Thank you so much for this feature.One tiny thing, and I hope I'm not nagging hehe. When someone copies, the link, for me it doesn't show like a 'copied to clipboard' or anything to indicate that I did copy the link for that abbreviation. Is there something we could do to fix this?

I still feel it's not obvious enough that the link icon is for copying an abbreviation. Instead of changing to another icon, what if we could make it simple by adding some indicative text that says 'copied'? So when the user clicks the link, just like you've implemented for the icon to change, let that small text pop up instead and then you use setTimeOut like you did to replace the text after a few secs. I'm also open to any better suggestions if you have

Is this closer to what you were thinking?

Yes, this is perfect! I no longer want to bother you with this PR, seeing as you've done so much work on it. I'll merge this, and then we can always fix alignment issues etc as some other contribution. Thank you very much again for the neat feature!

Sounds good, I will revisit the code over the weekend with a fresh mind and cleanup anything I can find. I learned a lot so thank you for the opportunity!


Bookie OOM

Describe the bug
Pulsar v2.8.1
cluster: 3 zks、5 brokers、5 bookies
topics: 14
topic partitions: 40

To Reproduce
Steps to reproduce the behavior:

Start bookies and brokers with direct memory 80GB
Start producers

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]

Additional context
Add any other context about the problem here.

Closing as stale. If it's still relevant to maintained versions, feel free to open a new issue


Navbar misbehaves when movies section gets hovered

The navbar shifts upward when the movies section get hovered up. This occurs when the dropdown gets active. It feels like a glitch to the user.
I can solve the issue if assigned.
This is regarding to Gssoc'23

I'd like to work upon this issue if this hasn't been done yet.Pls assign it to me


Undefined step using simple Go example

👓 What did you see?
I used the simple Godogs example code in VSCode and it runs fine.  The extension is working as I see the feature file with the cucumber icon and syntax is correctly colored.  However, my step definitions are underlined (error) and reporting "Undefined step".  I do not have this problem with Java.
The extension says it supports Go, but I am wondering if the extension cannot actually find the step definitions.  I tried to put the step definitions in the same "features" folder as the feature as well as in the root folder.
Here is the feature file:
Feature: eat godogs
  Scenario: Eat 5 out of 12
    Given there are 12 godogs
    When I eat 5
    Then there should be 7 remaining

Here is the step definition:
func TestFeatures(t *testing.T) {
  suite := godog.TestSuite{
    ScenarioInitializer: InitializeScenario,
    Options: &godog.Options{
      Format:   "pretty",
      Paths:    []string{"features"},
      TestingT: t, // Testing instance that will run subtests.
    },
  }

  if suite.Run() != 0 {
    t.Fatal("non-zero status returned, failed to run feature tests")
  }
}

func InitializeScenario(sc *godog.ScenarioContext) {
  sc.Given(`^there are (\d+) godogs$`, thereAreGodogs)
  sc.When(`^I eat (\d+)$`, iEat)
  sc.Then(`^there should be (\d+) remaining$`, thereShouldBeRemaining)
}

Any help would be appreciated!
✅ What did you expect to see?
I should be able to jump from the step to the step definition.
📦 Which tool/library version are you using?
vscode: 1.91.1
go: 1.21.0
godog: 0.14.1
🔬 How could we reproduce it?
No response
📚 Any additional context?
No response

@smelzer, this appears to relate to #234 I'm afraid; if you would be willing to downgrade to VSCode 1.89 and confirm?

Would also add to my previous comment that https://github.com/cucumber/language-service seems to resolve step definitions correctly in the main branch. That is, I ran tests for ExpressionBuilder#build with the test file substituted with foo.go I linked in the archive above and it does find the following expression in the glue file
[
  {
    expression: CucumberExpression {
      expression: 'there are 12 godogs',
      parameterTypeRegistry: [ParameterTypeRegistry],
      parameterTypes: [],
      ast: [Node],
      treeRegexp: [TreeRegexp]
    },
    locationLink: {
      targetRange: [Object],
      targetSelectionRange: [Object],
      targetUri: 'file:///Users/[REDACTED]/src/language-service/test/language/testdata/go/StepDefinitions.go'
    }
  }
]

The tests above fail in<EMAIL_ADDRESS>which<EMAIL_ADDRESS>uses in dependencies. Hence why I see the 'undefined-step' errors in VSCode. AFAICT, this is due to tree-sitter queries not matching methods(only functions) containing step definitions. https://github.com/cucumber/language-service/commit/0d28333c8118a601bff3345b9d9d81ba91910584 seems to have fixed this, however this commit haven't yet landed in any release.
@kieran-ryan how hard would it be to propagate this fix from https://github.com/cucumber/language-service up to the cucumber vscode extension? Should I submit an issue in the language-service repo for this?


[upstream] upstream log: Allow upstream filter state in upstream_log.

Currently in the context of an upstream Http request, we cannot add upstream specific filter state
data to access log.  This change addresses this issue by introducng a new format tag for http router's
upstream_log component - UPSTREAM_FILTER_STATE. This allows upstream compoents (for example, transport socket)
to add filter state which then gets propagated to the access log.
Additional changes:
Changed visiblity rule for extensions/transport_sockets to enable integration testing with
passthrough sockets.
Signed-off-by: Jojy George Varghese<EMAIL_ADDRESS>Risk Level: Medium
Testing: Unit tests, Integration tests
Docs Changes: To be done
Release Notes: To be done
Platform Specific Features: N/A

/retest

@alyssawilk @yanavlasov PTAL. The CI issues dont look to be related to the PR.

/retest

/retest

/retest

ping @yanavlasov @alyssawilk

It is expected that changing the interface would result in a larger diff. I think it is cleaner though.
To resolve CI timeout, please merge main.
/wait

/wait

It is expected that changing the interface would result in a larger diff. I think it is cleaner though. To resolve CI timeout, please merge main.
/wait

Thanks @yanavlasov . Wondering if we need changes in docs.

/retest


REST api for meta tx infos

Similar to how we have an endpoint to get informations on current gas price and nonce we should have an endpoint like that for meta transaction. So far this would only include the meta transaction nonce.

It's unclear to me what this issue is about. Can you be a bit more specific?

We need an endpoint similar to https://github.com/trustlines-network/relay/blob/develop/docs/RelayAPI.md#transaction-infos-for-user
to get the next nonce from the relay server to prepare the meta transaction in the client,  and later maybe the gas cost set by the delegator.
Possible endpoints

reuse the one we have
use something like /identities/<address> and there return infos about the identity contract including the last used nonce.
use a dedicated endpoint, somthing like /meta-transaction-infos/<address where we also later would make the gasPrice set by the delegator available.

ok, thanks for the clarification. I would choose the second option.

okay


How to download a playlist?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Instructions advise to paste playlist URL but I am getting "no matches found"
user@MacBook-Air ~ % yt-dlp https://youtube.com/playlist?list=PLPA49Pz3BAxMDFKmtvn9MlPUKmEz2q1D1
zsh: no matches found: https://youtube.com/playlist?list=PLPA49Pz3BAxMDFKmtvn9MlPUKmEz2q1D1
what am I doing wrong?
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

found the problem - URL contains non-standard characters and has to be closed in question marks:
yt-dlp "https://youtube.com/playlist?list=PLPA49Pz3BAxMDFKmtvn9MlPUKmEz2q1D1"


Not posting all kills.

Hello again and thanks for the code!
Everything seems to work fine but some kills are missing for some reason.
I've disabled battles/rankings because my guild is very small so I just want kill info.
From what I've tested most of the kills that are skipped are those involving many players at once, so I guess you have coded queries in a way to split battles from single kills so it doesnt spam both of them? Sorry I'm new to this, could you point me the direction to go?
I just want it to post every single kill from the guild no matter if it was battle or not.

I'll notice a lot of 502 errors and 999% (this mean that data was invalid) when polling for new events.
The problem is that Albion API is returning a lot of errors. Most probable reason is that due to corona, there is a peak of players that is overloading their servers, which causes some downtime. Also, the API isn't oficially supported so we cannot complain about these downtimes nor ask for solutions. They stated that they tolerate the use of API. but don't support it.

I'm totally aware of it. If you go to the endpoint and refreshpage a few times there's more than 50% chance of getting 502 errors. But I don't think this is the problem. This should delay and maybe miss few kills at active play times, but this isn't the case.
The reason I'm sure it's because there is a guy who made a paid albion killbot that manages to post every single kill succesfully, with big delays sometimes but it works. I've been using it in my guild for a while. I've spoken with the developer and he said he's using database to store already posted kills and just check if they've been already posted to avoid spam, so it works even if the bot crashs or on bad API connections. He told me it is capable to get at least 1 hour worth of kills, so it means if it crashes or server returns bad connections and stays like that for more than 1h it will definitely miss some kills, but thats really efficient enough!
I'm really curious on how he's doing it because from what I've seen the endpoint is max 50 kills at once so... no idea how he's done. The discord of the developer if you wanna check it yourself, its very simple to setup: https://discord.gg/S7Hf9cC.
Anyways, your bot is great and I really appreciate for making it public! I've been learning a lot from it and learning javascript/async stuff that I've never used before, I've been a C++ developed for a while so I struggled a bit but this quarantine has given me some time ahaha thank you!

Well, if he can, than there must be a way. I'll reopen this issue as an experiment and see if I can solve the issue.

Good news: I've completely reworked the events notification system.
It is now split into 2 phases:

get events: poll albion api every x seconds for events. We want to bring all events to our database as unread events (and delete older events so we don't run out of space). This run every 8 seconds (could be lower, but I don't want SBI blocking us :P)
scan events: poll our database for unread events and display them, marking as read. this can be more relaxed and does not depend on the get function

The new approach will make the bot poll the endpoint a lot more, and make use of data, no matter if it's new or old: it just needs to be there for consumption.
Let's see how this approach works out.

Very nice! I'm glad you took some time to take a look at it.
I've been testing it since you updated and it looks better, but it's still missing a few kills still comparing to the kill log in website. But I very have good news.
I figured out how to fetch last 1000 kills! It's actually simple. The offset parameter allows you to go down up to 1000 kills in batchs of 51. So you can loop it through limit=51 offset=0 up to offset=1000 so you can keep searching further down until you find the last kill posted, so it basically means you wont skip a single kill! Awesome!!

Oh, i see. I will implement this, thank you.

Awesome!!! I'm glad I could be usefull somehow. I've been testing and it's working 100%, thank you for the good work ;)


[mwc-list] Safari webpage crash when using  +

Describe the bug
When using directly the <slot> element inside the light dom + using a
 it makes Safari crash.
At first I thought about a Safari bug because it works fine with Chrome but it seems to happen with the slot="graphic" only.
To Reproduce
Steps to reproduce the behavior:

Go to https://typescript-mwc-list-safari-slot-bug.stackblitz.io with Safari (stackblitz project)
See Safari crashes
Remove the second <mwc-list-item> in the stackblitz
See Safari doesn't crashes anymore

Expected behavior
It should not make the page crash like that.
Browser Version (please complete the following information):

OS: MacOS 10.15.4
Browser: Safari
Version: 13.1 (156<IP_ADDRESS>.8) and Release 105 (Safari 13.2, WebKit 15610.1.10)

Additional context
Removing the <slot> does fix the issue but I originally took the example from the mwc-list example page.

I just tried to set the twoline property on the list item that was making Safari crash and it now works. https://typescript-mwc-list-safari-slot-bug-qghurr.stackblitz.io (stackblitz project)
My guess is that Safari doesn't like <slot> distributed in a <slot> at the top level of a shadow host, i noticed the twoline attribute adds a wrapper around the default <slot> of the <mwc-list-item> .
Maybe we should issue a bug to Webkit Bugzilla and meanwhile update the documentation?

woah that's gnarly!

Interesting observation, but on the note about top-level slot:
It actually is already wrapped. A single-line renders like so
<mwc-list-item graphic="icon">
  # shadow root

      <slot name="graphic"></slot>

      <slot></slot>

  # /shadow root
  <slot></slot>

edit

</mwc-list-item>

so the slot is already not at root

may not be exactly what you want, but wrapping the slot with default content inside of a <slot>default</slot> seems to prevent the crash. This is indeed a WebKit bug and filed it here:
https://bugs.webkit.org/show_bug.cgi?id=211159
Closing this issue since it's not inherent to this library and has a workaround. Will reopen if we get a significant amount of reports

Well, you perfectly understood my observations that were totally wrong 😂 you are right, I am sorry I went too fast in conclusions.
Thank you for taking the time to issue the bug to Webkit.
Actually I worked around by simply removed the <slot> in the light dom, i just copied and pasted the mwc-list example that uses <slot> and I don't think I need it.
Can I suggest to update the mwc-list documentation to remove the <slot> usage? Or is it really required? (I bet it does, just curious to know why)

update: Apple seems to have picked up the issue

Issue seems to be fixed in the WebKit bug tracker.
I guess it will be in the next version of Safari Technology Preview.
https://bugs.webkit.org/show_bug.cgi?id=211159#c4

Hell yeah! Thanks again guys 😇


Fixing apparent newline bug with list type question.

Hello,
I was looking for a CLI package for Python and found yours to be suitable for my needs. I installed it but came across an error—whenever I ran your script examples/list.py, the prompt ended up printing a bunch of newlines before printing the actual options.
In this pull request, I replaced the layout variable from the implementation of the list question with the one present in the rawlist implementation. This seems to have fixed the issue.
I am not well-versed in this project's implementation, so please test this out on your own computer to confirm the bug and fix are valid.

#5

Thanks for your contribution. I'll look into it and run it against many use cases and environment. :+1:

After some testing, it doesn't quite work on some terminals and environments. Like it didn't fix mine. I still don't know why but I am looking it.

For reference, I'm on Windows 10 with an instance of PowerShell in VSCode (no admin permissions).

Its been merged to both dev and master branch

@CITGuru thanks for merging this! Would you be able to update the tags so that we can get the latest bugfix changes when we pip install?


Flow sidebar jumps when choosing different annotations and the page formatting is not user friendly

Preconditions:

Extraction with several different categories is annotated.
There is a document which is imported with annotations

Steps:
Case1

Open the Extraction from precondition 1
In the Files tab choose the annotated document and open
Go through the tabs on the bottom

Case2

Open the Document from precondition 2
Tap on different annotations in the main part of the screen
Go through the tabs on the bottom

AR
Flow sidebar jumps when choosing different annotations and the page formatting is not user friendly
ER
No jumping
Formatting is more readable.
https://user-images.githubusercontent.com/98399603/226650678-fee65ef9-9a78-4ae2-8408-516c0ac6b4aa.mp4

Fixed.


Move Shelley commands to the top-lvl and deprecate "shelley" subcommand

This PR moves Shelley-related commands from under the "shelley" subcommand to the top-level of the CLI.
We still maintain support for the "shelley" subcommand (i.e. all of the commands still work), but its help text is hidden. However, the help text can still be accessed by running cardano-cli shelley or cardano-cli shelley --help:
$ cardano-cli shelley
Usage: cardano-cli shelley COMMAND
  Shelley specific commands (deprecated)

Available options:
  -h,--help                Show this help text

Available commands:
  ...

Additionally, a warning message is written to stderr when one attempts to run a command under the "shelley" subcommand. Example:
$ cardano-cli shelley address key-gen --verification-key-file /dev/null --signing-key-file /dev/null
WARNING: The "shelley" subcommand is now deprecated and will be removed in the future. Please use the top-level commands instead.

We should also think about how we are going to update the cli tests

bors merge

bors r+


ValidatorSet: Reject preimages that are too distant to the prev one

Fixes #2248
This will make sure that an attacker can't fool us into hashing
excessively. The genuine case where a node may want to reveal a
preimage too early is now discouraged since that preimage will not
be accepted and may cause the validator to be slashed.

Wasn't https://github.com/bosagora/agora/pull/2469 a bit more complete ? Not only did it make the value configurable, but it also let the door open for the node to add far pre-images by itself ?

Also the problem mentioned here: https://github.com/bosagora/agora/pull/2469#issuecomment-914311529 still applies.

Also the problem mentioned here: #2469 (comment) still applies.

But we now include preimages in the header, so catchup should work just fine. Am I right?

That's right, indeed.


Hrtim master

@burrbull thanks a lot for this

Check "Memory map comparison" for correctness, please.

Check "Memory map comparison" for correctness, please.

I will do that as soon as possible

Looks like some issues still present. Especially with HRTIM_Common:
https://stm32-rs.github.io/stm32-rs/STM32G484xx.html#HRTIM_Common:FLTINR2

Also ISR is supposed to be read only from what I can tell (27.5.58 in RM0440)

...more reading
https://stm32-rs.github.io/stm32-rs/STM32G484xx.html#HRTIM_Common:BMCR:BMSTAT
27.5.64

Bit 31 BMSTAT: Burst mode status
This bit gives the current operating state.
0: Normal operation
1: Burst operation on-going. **Writing this bit to 0 causes a burst mode early termination**

So does this mean that this should default to 1 when writing unless the user has explicitly cleared it? Should this also not be possible to set to 1 by the user?

Lots of errors in BMTRGR should be TFCMP1 according to the RM under 27.5.65

Bit 23 should be TFCMP1
Bit 21 should be TFREP
Bit 18 should be TFRST

BDTAUPR has a lot of TIMx-prefixes that could probably be removed. There is also the field TIMx_DTxR where we might want to strip the last x?
Same thing for all registers BDTxUPR where x=A..F

Looks like some issues still present. Especially with HRTIM_Common: https://stm32-rs.github.io/stm32-rs/STM32G484xx.html#HRTIM_Common:FLTINR2

If you mean things like FLT6SRC being split over FLT6SRC_0(bit 0) and FLT6SRC_1(bit 1).
Same thing with FLT1SRC being split between two different registers FLT[1]SRC (bit 0) in FLTINR1 and FLT1SRC_1 (bit 1) in FLTINR2. From what I can tell from reading RM0440, that is just how weird the hardware is.
When comparing with rm0364 for F334, that processor seems to only have one src bit so probly some attempt at backwards compat?


Remove 3.6 from matrix

I'm going to close this as I've just done this as well.
I also remove python 3.7 as it is EoL and included python 3.10 and 3.11

https://github.com/pyepye/django-amplitude/blob/master/.github/workflows/test.yaml#L14
https://github.com/pyepye/django-amplitude/blob/master/tox.ini#L8-L9


please， review #663

please， review #663

Please stop creating a new issue just for asking a review for another issue.
We appreciate your contribution, but we are volunteers and need time to review certain changes.
Thank you for your understanding.