Add Cellery hub sdk Pages

Codecov Report

Merging #17 into master will decrease coverage by 0.72%.
The diff coverage is 19.23%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   30.47%   29.74%   -0.73%
==========================================
  Files          29       33       +4
  Lines         466      511      +45
  Branches       70       70
==========================================
+ Hits          142      152      +10
- Misses        305      338      +33
- Partials       19       21       +2

Impacted Files
Coverage Δ

...s/portal/src/components/overview/org/MemberList.js
0% <ø> (ø)
:arrow_up:

components/portal/src/components/App.js
36.36% <0%> (-13.64%)
:arrow_down:

...s/portal/src/components/sdk/SDKAppLayout/Header.js
14.28% <14.28%> (ø)

...ts/portal/src/components/sdk/SDKAppLayout/index.js
60% <60%> (ø)

...ents/portal/src/components/sdk/OrgCreateSuccess.js
60% <60%> (ø)

components/portal/src/components/sdk/index.js
9.52% <9.52%> (ø)

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 e20e59e...c81cd66. Read the comment docs.


Embed

How would I do embed text?

please provide more details in regards with the issue

try this https://github.com/FireController1847/embed-creator

@Nyctara That didn't work.

Anyone still know how to do this?


Use Replits for VC examples in the wiki

Description of change
Replace outdated links caused by https://github.com/iotaledger/identity.rs/pull/795 in the wiki and use Replits for VC examples.

I'm not sure if this should be in the changelog, probably not.


Package statistics not updating properly

This is an issue which has been going on for a while, but every time it's fixed it seems like it occurs again but slightly differently 😊
In the past the download stats has been frozen and when navigating to "View full stats" you could see that the date of the last update was old. Now the stats are not updating but the full stats page says the stats have been updated. For example it's been a while since the download stats increased for our main package:
https://www.nuget.org/packages/Piranha
However, nuget.org claims it was updated yesterday.
Given that we have several years of user statistics showing that this never happens it's highly unlikely that there would be zero downloads for a longer period. Also when this has occurred in the past, all of a sudden several hundred downloads are all of a sudden added on the statistics, so it gives the impression that the stats are recorded, but not propagated properly on package level for the site to show.
Best regards

More input. Today the download count increase with 132 from yesterday, which statistically is too high for our project to be one day of downloads, on the other hand it seems too low to be the total of the days the statistics have stood still. Due to the fact that it increased too much for one day and stood still earlier, even though the dates said the statistics was updated somewhat validates the suspicion that stats are recorded somewhere but are not propagated properly through the system.
I've put up an excel where I'll store the values from every day the website says it has been update to see how it continues to behave.
Best regards

Hi, @tidyui. Thank you for noticing us! We met an incident for our statistics pipeline during these days, and it's mitigating now. We are really sorry for the inconvenience. Our current statistics pipeline is not so scalable, but we have scheduled to refresh/improve this pipeline. I think we will provide a much better statistics pipeline soon.

So it sounds like this is a NuGet Statistics issue, and not Covid destroying the number of downloads?

I have the same issue with my project: https://www.nuget.org/packages/ETLBox/
The statistics are updated very randomly after ~7 to 10 days, in between they seem to be frozen (though there are for sure downloads). It's really hard to trust the numbers, as they get updated not more often than once a week with a high number, and then stands still again for quite some time. Looking at other tools and statistics (Google Analytics, Github) I can see more or less a steady amount of traffic.

@daryllabar @roadrunnerlenny  It looks like surely there are some problems in the Nuget download count and sync. The number of downloads it showing after 4 days is not trustable anyway.

Hi, guys. Thank you for the patience here! We have already fed all the downloads counts we missed during the past period, and the statistics data should be the expected one now.
The reason why you notice that the increase of download counts was not steady during the past period is that our pipeline was designed and implemented several years ago, and the pipeline is not scalable enough to handle some very large log files, which will slow the progress of the ingestion, and lead to dead letters. We have to take some actions to feed these failed log files again, and let these log files go through the pipeline.
So that's why you see that the download counts seemed frozen during the period, and increased a lot later, because we were feeding the unprocessed logs, which contained multiple days' download counts.

We apologize for this very bad experience , and it's also hurting us now. We have scheduled to rebuild this pipeline with a much better architecture and implementation, starting from this sprint. And it will replace our legacy statistics pipeline soon.

I see this is closed but is the issue fixed? As a user is is incredibly frustrating to see issues closed without an actual solution implemented or at the bare minimum a reference to a new ticket to track the tick open. This isn't how issue trackers are supposed to work!
For the following package the stats details are:
https://www.nuget.org/packages/SixLabors.ImageSharp/
Last update Statistics last updated at 2020-04-30 16:47:41 UTC
This indicates that the system is broken again.

You mean it’s still broken 😁 I agree that it would be awesome to have somewhere we could follow what’s happening with this or any form of timeline. Right now the stats are just a guessing game

I agree, shouldn’t this be kept open until a fix has been implemented? Someone else is going to just create a new issue thinking this hasn’t been addressed. It would be nice to track this somewhere.
We are all divas and need to know how much people love us via our download counts 😂

Yeah, I mean for us developing completely free software with no additional registration or built in spyware crap, these statistics are the only indicator on which version people are using, how fast people migrate to new versions and so on.
If these numbers don’t start to work we have to look into other ways of tracking usage statistics because it’s extremely important for maintenance.
This, and that I like to update my CV with the download count every day (just kidding) 🤪

the issue is still there, sadly. I wonder why this issue is closed.


Error when parsing a WSDL

When using soap:wsdl2erlang(...). on http://demo-hotelws.touricoholidays.com/HotelFlow.svc?wsdl, I get the following.
** exception error: no function clause matching
                    soap_parse_wsdl:'-services/1-lc$^0/1-0-'(undefined) (src/soap_parse_wsdl.erl, line 116)
     in function  soap_parse_wsdl:get_services/3 (src/soap_parse_wsdl.erl, line 107)
     in call from soap_parse_wsdl:get_services/3 (src/soap_parse_wsdl.erl, line 112)
     in call from soap:wsdl2erlang/2 (src/soap.erl, line 305)

A little investigation shows that erlsom:scan(...) is returning a bunch of undefined elements for the imported document at http://demo-hotelws.touricoholidays.com/HotelFlow.svc?wsdl=wsdl0.
So, it is possible that this is erlsom's problem.  Or, it could be a problem with the model being passed to erlsom:scan.
In any case, could you take a look at this, please?  All help is appreciated.  Thanks!

Bumping this, because of urgency at my end!  My apologies!
Could this be an erlsom issue @willemdj?

I think that it is more likely to be caused by a somewhat unusual structure of the WSDL. You could for example try to replace the bit
<wsdl:import namespace="http://tourico.com/webservices/hotelv3" location="http://demo-hotelws.touricoholidays.com/HotelFlow.svc?wsdl=wsdl0"/> <wsdl:types/>
by the contents (the wsdl:types part) of http://demo-hotelws.touricoholidays.com/HotelFlow.svc?wsdl

Thanks for your quick reply @willemdj!
I have downloaded both WSDLs, modified the main one to include the imported types.  When this modified version is given as input, the referred XSDs are no longer being fetched from the net.
** exception error: no match of right hand side value {error,
                                                       "Include file not found http://demo-hotelws.touricoholidays.com/HotelFlow.svc?xsd=xsd0"}
     in function  soap_parse_wsdl:add_schemas/5 (src/soap_parse_wsdl.erl, line 215)
     in call from soap_parse_wsdl:parse_wsdls/3 (src/soap_parse_wsdl.erl, line 148)
     in call from soap_parse_wsdl:file/4 (src/soap_parse_wsdl.erl, line 80)
     in call from soap_parse_wsdl:get_model/2 (src/soap_parse_wsdl.erl, line 55)
     in call from soap_parse_wsdl:get_namespaces/2 (src/soap_parse_wsdl.erl, line 66)
     in call from soap:wsdl2erlang/2 (src/soap.erl, line 313)

I am still looking into this, but posting the update here!

Same issue here. It looks like the imported types, which are given as remote resources ("http://...") are not downloaded. It appears that soap expects them to be located in the local file system.
Any prognosis on how difficult it would be to produce a fix?

Hi,
I don't think that is the problem, it should get remote resources as well.
I do recognize that there is a problem with the WSDL that the original issue refers to. This is related to the complex structure of that WSDL.  Assuming that you are trying to process a different WSDL, could you let me know what error you are getting, and if possible also provide the files?
Thanks,
Willem

The error that I get is that included XSDs appear to be expected in local file system. I'll open another issue.

Apologies for disappearing!
The problem indeed was with the WSDL.  It got resolved after I upgraded a later version of the API, with an updated WSDL.
Nonetheless, I could make calls using the original WSDL from Python.  So, soap did have some problem fetching the referenced WSDLs.


[Dev]bot gets stuck between following path and moving to fort

Expected Behavior
Follow Path and stop at forts to spin
Actual Behavior
get stuck between moving a fort that is not on the path and following the path. A
Steps to Reproduce
put

  {
    "type": "SpinFort"
  },
{
    "type": "MoveToFort"
  },
  {
    "type": "FollowPath"
  }

into config and wait till the bot wants to spin a fort that's not directly on the path
Other Information
newest DEV commit
Seems like the "move to fort" and the "follow path" algorithm run against each other.

Please don't open bogus issues.

Drop MoveToFort if you're using a path....

Please don't open bogus issues.
Sorry, just hit the enter-button accidentally.

Drop MoveToFort if you're using a path....

Yeah, that works. But I thougt, that FollowPath would be an alternative for FollowSpiral. So that the bot would work at the forts until they are on timeout and then gonna continue following the given path.

You're giving the code too much intelligence. ;)  Right now these are 2 different movement paradigms and therefor are technically mutually exclusive. Basically with both active the movement goes split-brain and if the Stop that the FollowSpiral has latched on to is in opposition to your FollowPath marker then they go back and forth basically arguing over who's right and your bot goes nowhere....

Okay, thanks! I'll take this answer as: "it's not a bug, it's a feature :P" xD
Gonna plan my path more accurate so that it passes all forts that are nearby.

Yeah, I spent a half hour or so with Google Maps to get all the GPS points for my loop. ;)


overlays of the functional volume and the pial surface error

I'm trying to run cifti_vis_fmri with my own data, but there was something wrong with overlays of the functional volume and the pial surface, how can i locate the problems?

That looks like a major realignment failure during the pipeline run (i.e. it's not cifti_vis_fmri, your preprocessed outputs are actually that bad - and the functional data was not sampled to the correct surface locations).
I had a problem like this with one dataset, where the anatomical image had a high resolution and (after trying for weeks) the only way I could fix the problem was by rerunning fmriprep with the --no-submm-recon flag. (this could also be done by rerunning fmriprep_ciftify with --fmriprep-args="--no-submm-recon")
you can visualize the problem interactively by opening the files in wb_view
wb_view sub-<subid>/MNINonLinear/fsaverage_LR32k/sub-<subid>.32k_fs_LR.wb.spec

(then inside the viewer, open the fail fmri dtseries.

I have a problem in compiling newmesh, MSM,.... The error is default.mk, not found! Anyone who can help me?


Avoid errors on non-existent files.

Generally, be more careful about assumed existence. '*.h' glob results in error
even if directory exists...

LGTM


CKEditor toolbar widget not working as expected

When trying to add the ckeditor widget following error occurs in console of firefox 65.01 (64-bit):
TypeError: this.document.getWindow(...).$ is undefined[Läs mer] ckeditor.js:448:29

    getNative ckeditor.js:448 selection ckeditor.js:446 getSelection ckeditor.js:443 Image ckeditor.js:1080 save ckeditor.js:1075 init ckeditor.js:1071 n ckeditor.js:10 fire ckeditor.js:12 fire ckeditor.js:13 setData ckeditor.js:275 updateValueHandler surveyjs-widgets.js:1340 fireCallback survey.ko.js:3104 set survey.ko.js:3356 setDefaultValue survey.ko.js:3473 updateValueWithDefaults survey.ko.js:3464 onSetData survey.ko.js:3313 setSurveyImpl survey.ko.js:1833 setSurveyImpl survey.ko.js:2630 onAddElement survey.ko.js:6368 <anonym> (index):977 push survey.ko.js:1666 addElement survey.ko.js:6628 dragDropFinish survey.ko.js:10728 doDrop surveyeditor.js:6329 doDrop surveyeditor.js:6562 ondrop surveyeditor.js:6440

Steps to reproduce:

git clone https://github.com/surveyjs/surveyjs_vue_quickstart.git
Add <script src="https://cdn.ckeditor.com/4.7.3/standard/ckeditor.js"></script> to index.html <head> element
npm i
npm run dev
Open firefox (version 65.0.1 64-bit) and go to localhost:8080
Try to drag a ckeditor question to the surveybuilder.
Error is displayed in console

@hekin1 Please look at this example.
I have just tried it on FireFox, 66 (64-bit), it works fine.
Thank you,
Andrew

@andrewtelnov Yes, but I am refering to ckeditor as a toolbar widget for question types, not property editor.. Your link works OK, but thats because you use it as a question property editor.
Try using ckeditor (latest version) with surveyjs-widgets (latest version).
Best regards Henrik

@hekin1 Does this example help you?
Thank you,
Andrew

@andrewtelnov Not really, because the problem is with ckeditor (later versions) not functioning properly with survejs-widgets.
The problem occurs when using ckeditor version greater than 4.3.5. (I tried all versions above and they all fail)
I didnt spend too much time investigating, but maybe it has something to do with the ckeditor iframe when manipulating the DOM.
I found this which was quite interesting
https://dev.ckeditor.com/ticket/12258
Status of this ticket is wont fix and a suggestion to use inline editor instead.

@hekin1 Hello! I've tried to reproduce it with the steps above and without success. (Chrome and Firefox)
Also I've created an example for you https://codesandbox.io/s/0y63986m4v Could you please check and modify it to reproduce the problem?

Ok I recreated it with your sandbox here: https://codesandbox.io/s/zr5w26znwm
Note that the only thing I did was removing all widgets except for the ckeditor:
changed this:
import * as SurveyEditor from 'surveyjs-editor'
import 'surveyjs-editor/surveyeditor.css';

import * as SurveyKo from "survey-knockout";
import * as widgets from "surveyjs-widgets";

import "inputmask/dist/inputmask/phone-codes/phone.js";

widgets.icheck(SurveyKo);
widgets.select2(SurveyKo);
widgets.inputmask(SurveyKo);
widgets.jquerybarrating(SurveyKo);
widgets.jqueryuidatepicker(SurveyKo);
widgets.nouislider(SurveyKo);
widgets.select2tagbox(SurveyKo);
widgets.signaturepad(SurveyKo);
widgets.sortablejs(SurveyKo);
widgets.ckeditor(SurveyKo);
widgets.autocomplete(SurveyKo);
widgets.bootstrapslider(SurveyKo);

to this:
import * as SurveyEditor from 'surveyjs-editor'
import 'surveyjs-editor/surveyeditor.css';

import * as SurveyKo from "survey-knockout";
import * as widgets from "surveyjs-widgets";

widgets.ckeditor(SurveyKo);

@hekin1 I do not see jQuery in your import. ckEditor requires it.
Thank you,
Andrew

I did not remove jQuery from the sandbox @dmitrykurmanov created. So I dont know about that.. It works fine.

@hekin1 Yes, you are right. We will investigate it.
Thank you,
Andrew

I don't manage to reproduce this error:

TypeError: this.document.getWindow(...).$ is undefined[Läs mer] ckeditor.js:448:29

but anyway if we add two ckeditor's and try to drag and drop them we will see many console errors and the builder will break. I will investigate it.

@hekin1 @andrewtelnov I believe that I fixed all problems with ckEditor via the https://github.com/surveyjs/widgets/commit/688fde713a6995e482430ef4f016c9b266f9c70d .
Fix will be available in the next minor update


falco-exporter: Add PSP, ClusterRole and ClusterRoleBinding Helm templates to the chart

Hi there,
Motivation
I'm currently working in a quite restrictive K8s environment and unfortunately wasn't able to deploy falco-exporter until now since the falco-exporter Helm chart only comes with a ServiceAccount "falco-exporter" but without any configuration about the required PSP privileges.
Feature
Since the falco-exporter DaemonSet uses a hostPath volume (see https://github.com/falcosecurity/charts/blob/master/falco-exporter/templates/daemonset.yaml#L64-L67) it's sometimes required to explicitly allow this behavior via separate PSP, ClusterRole & ClusterRoleBinding.
A possible PSP probably could look like this:
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  labels:
    app: falco-exporter
  name: falco-exporter
spec:
  fsGroup:
    rule: RunAsAny
  runAsUser:
    rule: RunAsAny
  seLinux:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  volumes:
  - 'hostPath'
  allowedHostPaths:
  - pathPrefix: "/var/run/falco"
    readOnly: true

But what's with the ClusterRole? I mean which permissions need to be configured inside it? Since falco-exporter is able to add a ServiceMonitor and/or a Grafana Dashboard ConfigMap I don't think something like to following will be sufficient:
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: falco-exporter
  labels:
    app: falco-exporter
rules:
  - apiGroups:
      - extensions
    resources:
      - podsecuritypolicies
    resourceNames:
      - falco-exporter
    verbs:
      - use
... what else here?

If you can tell me the exactly required ClusterRole permissions I could implement this change via PR (if you want)..
Thanks!
Regards,
Philip

Hey,
good questions. TBH, I have not found the time to dig into that, anyways:

falco-exporter really needs just the hostPath to work properly
falco-exporter does not add a ServiceMonitor and/or a Grafana Dashboard ConfigMap, the helm chart does that on installation
the Grafana Dashboard ConfigMap is not used by falco-exporter itself, Grafana should consume it
same for the ServiceMonitor, it describes the target to be monitored by Prometheus
finally, the pod exposes a service and annotations (that can be configured here) consumed by Prometheus

Thus, if I didn't forget anything, the PSP and ClusterRole examples may be already complete.
WDYT?

Hi @leogr,
Ahright, of course 💡! Helm deploys the Grafana and ServiceMonitor stuff so the ServiceAccount does not need this privileges. I was able to bring falco-exporter UP using the following objects:
---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  labels:
    app: falco-exporter
  name: falco-exporter
spec:
  allowPrivilegeEscalation: true
  allowedHostPaths:
  - pathPrefix: /var/run/falco
    readOnly: true
  fsGroup:
    rule: RunAsAny
  runAsUser:
    rule: RunAsAny
  seLinux:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  volumes:
  - hostPath
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: falco-exporter
  labels:
    app: falco-exporter
rules:
  - apiGroups:
      - extensions
    resources:
      - podsecuritypolicies
    resourceNames:
      - falco-exporter
    verbs:
      - use
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: falco-exporter
  labels:
    app: falco-exporter
subjects:
  - kind: ServiceAccount
    name: falco-exporter
    namespace: <falco-exporter-ns-here>
roleRef:
  kind: ClusterRole
  name: falco-exporter
  apiGroup: rbac.authorization.k8s.io

If you want I could add these to the templates and create a PR within the nest few days. Would you be interested in this?
Thanks!
Regards,
Philip

Yes, it would be great! :+1:
Thank you @PhilipSchmid

Currently on wait until https://github.com/falcosecurity/falco-exporter/issues/42 is resolved. I first need to know which PSP properties can be set to which values.

Currently on wait until falcosecurity/falco-exporter#42 is resolved. I first need to know which PSP properties can be set to which values.

I have replied to the other issue. Btw, I think allowPrivilegeEscalation can be set to false.

Hi,
please re-open the issue.
The PSP is missing secret as allowed volume.
The daemonset might explicitly need a secret: https://github.com/falcosecurity/charts/blob/master/falco-exporter/templates/daemonset.yaml#L74
And even when not explicitly needed, the Service Account secret is automounted:
$ kubectl -n falco exec -ti  pod/falco-exporter-gtk9j -- mount | grep secret
tmpfs on /run/secrets/kubernetes.io/serviceaccount type tmpfs (ro,relatime)

Hi @czunker,
Why re-open? The volume type secret PSP issues should already be fixed with https://github.com/falcosecurity/charts/pull/117
Try falco-exporter chart version 0.3.7. There it's working justs fine - even with a configured imagePullSecret.
Regards,
Philip

Thanks @PhilipSchmid Didn't see this one.
And thanks for already fixing it.


Fix examples to use dtreeviz

In new examples  the trees are displayed using the default sklearn not dtreeviz ;)  This is for @tlapusan :)

In new examples the trees are displayed using the default sklearn not dtreeviz ;) This is for @tlapusan :)

I'll fix it soon


Read Escrow events from Redis queue and decide if we need to send a reward

After Blockscout starts pushing Escrow events to a Redis queue, we need a server to read from that queue and decide if the inviter has earned a reward or not.
The server could be a new standalone one or we could reuse the blockchain-api

Closed in favor of the new implementation. See https://www.notion.so/clabsco/Invite-and-Sign-Up-based-Rewards-d8f5e637e2b94ad8ac7f501b227f68df for details


Soduku (Ideation)

Make a new folder in games directory and add Markdown file with idea

Assign me this issue.

@TusharAMD pls assign me this isssue

@TusharAMD Hey, I would like to work on this for gssoc 22, kindly assign to me

Assigned

@TusharAMD plss close this issue as pr is merged


419 irods icommand 41

Part of the fix to large file upload in conjunction with a django_irods merge pull request. My testing reveals upgrading to icommands 4.1 fixed large file uploading issue. Asking to be merged into develop.

@hyi - As of last night it looks like the iRODS team has pushed the official v4.1.0 release files here: ftp://ftp.renci.org/pub/irods/releases/4.1.0/ubuntu14/. Will want to update the Dockerfile references to point here instead of to the preview release location.

@mjstealey Agreed. I don't have my work laptop with me, and will have to do so first thing on Monday. If it is easier for you to just update the link to the official v4.1 release files in Dockerfile before then for merging purposes, it'd be great.


Slim down installer and have it use a final schema instead of migrations

Following the same pattern we took with Solid Cache. This entails collapsing all the migrations into a premade queue_schema.rb and switching the default configuration to use a database configuration under the queue key. This configuration can now be set in config/solid_queue.yml, just like it's possible to do with Solid Cache. Drop all mentions and focus on running SQ off the same database.

If we would like to keep SolidQueue tables on a separate database server from the main app, how would we do that now?

That's now the default. The schema is independent, you point solid queue to the database you want to use with config.solid_queue.connects_to = { database: { writing: :your_db_name } } and match that in config/database.yml.


oha: 0.5.4 -> 0.5.5

Description of changes

Things done
https://github.com/hatoo/oha/compare/v0.5.4...v0.5.5
changelog

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 191918 run on x86_64-linux 1

1 package built:

oha

Thank you!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_45a3ctwvcv/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_45a3ctwvcv/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_45a3ctwvcv/clone/recipe/meta.yaml:49: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_45a3ctwvcv/clone/recipe/meta.yaml:49: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1cbokjlwsh/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_1cbokjlwsh/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_1cbokjlwsh/clone/recipe/meta.yaml:49: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_1cbokjlwsh/clone/recipe/meta.yaml:49: missing_description: The recipe is missing a description
Errors were found


Fetched inputs from request headers and code restructured

This PR completes the basic cache filter requirements as I've added the code to fetch inputs from the request headers and restructured for easy type identification from the singleton side of keys. Please let me know if you find any mistakes that I overlooked. Thanks! :)
Note: Only the last commit is relevant because reset of them came automatically as I updated my local fork during the creation of this PR.

I am creating a new PR without previous commits that are already merged. I'll close this one and apply the patch consisting of the last commit.


Error handling: Consider switching from thiserror to anyhow crate

Currently, we use thiserror crate to create different types of errors and return them inside our methods. It seems this way of handling errors adds unnecessary overhead (more boilerplate code) and makes sense when building libraries.
It looks like the anyhow crate provides an easy and idiomatic way of handling errors in rust applications.
This blog post describes well library vs application error handling in Rust:
https://nick.groenen.me/posts/rust-error-handling/#libraries-versus-applications

'm not remembering exactly, but @ogenev did you once mention that there is some reason we can't entirely switch all our errors over from thiserror to anyhow?

I had in mind mainly OverlayRequestError in overlay_service because we are passing some errors between handlers/channels and I think refactoring them will be a more involving process.
Other than this, I guess we can easily switch to anyhow in other parts of the code where the error handling is more encapsulated.

Personally, I'd agree with the switch over to anyhow but only in the case that it can fully replace thiserror. Using two different error handling libraries seems fuzzy and confusing where one should use which one. Though, I guess we're currently already using both of them...

Closing - CONTRIBUTING.md has been updated with new error guidelines


Update aws-java-sdk-bundle to 1.12.461

About this PR
📦 Updates com.amazonaws:aws-java-sdk-bundle from 1.12.460 to 1.12.461
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2679.


write TrackEvent protos to generate visual tracks like ftrace CPU tasks

Hi,
I successfully write TrackEvent protos as described https://perfetto.dev/docs/reference/synthetic-track-event. However, I can't find any descriptions to describe how to generate visual tracks like cpu-level tasks in ftrace, as shown below in attachment. Is it possible to write these trackevent protos directly to show such visual effects?

This is not possible at the moment unless you want to try and reverse engineer how the ftrace protos work (which I really wouldn't recommend they are quite complicated).
However in general we plan on adding a bunch of easy to synthesise protos for all the sorts of data Perfetto can generate in the coming months (including an easier to generate format than track event for slices/counters). Protos for generating scheduling data will be one of the things we add as part of this.

Thanks. There is always something new. Waiting for you update.

Does process-scoped (async) slices support show thread time, by extra_counter_track_uuids stuff? I tried to add thread information to track_descriptor, seems not working.

if __name__ == '__main__':
    trace = Trace()

    packet = trace.packet.add()
    packet.track_descriptor.uuid = 48948
    packet.track_descriptor.name = "My special track"
    packet.track_descriptor.process.pid = 1234
    packet.track_descriptor.process.process_name = "My process name"

    packet = trace.packet.add()
    packet.timestamp = 200
    packet.track_event.type = TrackEvent.TYPE_SLICE_BEGIN
    packet.track_event.track_uuid = 48948
    packet.track_event.name = "My special parent A"
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 250
    packet.track_event.type = TrackEvent.TYPE_SLICE_BEGIN
    packet.track_event.track_uuid = 48948
    packet.track_event.name = "My special child"
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 290
    packet.track_event.type = TrackEvent.TYPE_SLICE_END
    packet.track_event.track_uuid = 48948
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 300
    packet.track_event.type = TrackEvent.TYPE_SLICE_END
    packet.track_event.track_uuid = 48948
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.track_descriptor.uuid =<PHONE_NUMBER>
    packet.track_descriptor.name = "My special track"
    # add tid
    packet.track_descriptor.thread.pid = 1234
    packet.track_descriptor.thread.tid = 5678
    packet.track_descriptor.thread.thread_name = 'aaaaa'
    packet.trusted_packet_sequence_id = 3903809

    packet.track_descriptor.parent_uuid = 48948

    packet = trace.packet.add()
    packet.timestamp = 230
    packet.track_event.type = TrackEvent.TYPE_SLICE_BEGIN
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.track_event.name = "My special parent A"
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 260
    packet.track_event.type = TrackEvent.TYPE_SLICE_BEGIN
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.track_event.name = "My special child"
    packet.trusted_packet_sequence_id = 3903809

    # third one
    packet = trace.packet.add()
    packet.track_descriptor.uuid =<PHONE_NUMBER>
    packet.track_descriptor.name = "My special track"
    # add tid
    packet.track_descriptor.thread.pid = 1234
    packet.track_descriptor.thread.tid = 5678
    packet.track_descriptor.thread.thread_name = 'aaaaa'
    packet.trusted_packet_sequence_id = 3903810
    packet.track_descriptor.parent_uuid = 48948

    packet = trace.packet.add()
    packet.timestamp = 265
    packet.track_event.type = TrackEvent.TYPE_SLICE_BEGIN
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.track_event.name = "My special 3 child"
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 270
    packet.track_event.type = TrackEvent.TYPE_SLICE_END
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 270
    packet.track_event.type = TrackEvent.TYPE_SLICE_END
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.trusted_packet_sequence_id = 3903809

    packet = trace.packet.add()
    packet.timestamp = 295
    packet.track_event.type = TrackEvent.TYPE_SLICE_END
    packet.track_event.track_uuid =<PHONE_NUMBER>
    packet.trusted_packet_sequence_id = 3903809

    with open("trace_output.pb", "wb") as f:
        f.write(trace.SerializeToString())

I am looking for some visual feature of mouse selecting and draging and make use of perfetto ui's aggragation feature, which can show associated internal values with these slices. Is this feature in your roadmap?
Thanks.

In general making aggregation work flexibly and consistently is very much on our roadmap yes.


Support options for machine types

Description of problem
Unable to specify options for machine types in configuration file
Expected result
Qemu command line should have options for the machine type
qemu ... -machine virt,accel=kvm,gic-version=host,usb=off

where gic-version=host,usb=off are the options
Actual result
qemu ... -machine virt,accel=kvm ....

Solution
add machine_options in configuration file

I'm not 100% clear on this. Currently, the runtime supports a machine_accelerators= config option. Those values get added to the accel= qemu option by the govmm package, so you could add gic-version=host, there I think?
@markdryan - or would we need (also) need changes to https://github.com/intel/govmm dyt?

@jodh-intel We've just merged a related change to go-vmm.
https://github.com/intel/govmm/pull/9

Thanks @markdryan, @devimc - I love it when that happens! :smile:

@devimc working on this :)


chore(release): v0.9.1 🎉

:robot: I have created a release beep boop
0.9.1 (2024-07-06)
Bug Fixes

errors: support bad request errors from any package (dca5539)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/simple-lambda-handlers/releases/tag/v0.9.1 :sunflower:


[BEAM-2166] Cherry-pick #2930 onto release-2.0.0

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @lukecwik, @davorbonaci

Changes Unknown when pulling 9dd1b59a7a71fcf63b7a26c8ebd86dcc46ec4c15 on robertwb:coders-context-sizes-release into ** on apache:release-2.0.0**.

This requires new workers, Jenkins is happy otherwise.

Looks equivalent to PR #2930 and #2933 on apache/master

Merged, please close at your leisure


Automator: update istio/istio@master

Generated by Automator - 2020-01-06T19:14:50+00:00

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
359e30de9b090abafa901cb185a3531b202097f8
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
359e30de9b090abafa901cb185a3531b202097f8
link
/test lint_istio

integ-galley-k8s-tests_istio
359e30de9b090abafa901cb185a3531b202097f8
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[TW#13569] I2C API uses portBASE_TYPE /  BaseType_t instead of portTICK_TYPE / TickType_t for timeouts; I2C implementation does not account for OS ticks overflow and could block for 500 days; and I2C API documentation does not relate to the tick base

The I2C API uses portBASE_TYPE (which is supposed to be signed and defined as int for ESP32 IDF)
here, here and here to represent a number of OS ticks, which would better be represented by portTICK_TYPE (old) / TickType_t (new) in the context of the FreeRTOS API -- negative values don't make sense anyway.

While FreeRTOS itself takes care of tick overflows, the I2C implementation does not.
With ticks @ 100 Hz  and TickType_t as unsigned 32 bit, applications may see unexpected results after roughly 500 days of CPU uptime. All it needs is a relatively generous timeout and an API call shortly before the tick counter overflow. Maybe someone even experimets with a 16 bit tick count, which is an option for FreeRTOS and would increase the likelihood drastically.
The other weakness of the implementation lies in the task synchronisation in combination with the computation of the destination tick count. If the functions have to wait longer for the first semaphore than the delay provided via the call, then the subtraction will underflow and the call timeout will effectively be around 500 days.
This scenario can occur if the task acessing I2C is interrupted or the semaphore is held by higher priority tasks "for long enough".
Both problems could be easily fixed at the same time by using vTaskDelayUntil() instead of vTaskDelay().

The documentation, e.g. here, simply refers to ticks. Since I2C has to be configured with a clk_speed, it might be helpful for the user if it was made clear that these are really OS ticks, maybe with e reference to portTICK_PERIOD_MS.

Could https://github.com/espressif/esp-idf/issues/680 be related to this?

@tdesmet It could be the case that you suffer from the "other weak aspect" I described, with the likelihood depending on you using one or two cores, having higher priority tasks which can let your I2C calls wait, etc. But the symptoms you mention go beyond what the bug I mentioned can do (unless timeout handling would be broken, which I didn't check).
Having a quick glance, it seems to me that one more code line in i2c_master_cmd_begin() might be suspicious. There, the semaphore is polled (instead of being waited for) and the return value ignored (xTicksToWait is 0). This means that if the semaphore cannot be obtained, the later xSemaphoreGiveFromISR() calls in i2c_master_cmd_begin_static() will have no match.
Interestingly, while FreeRTOS requires that a semaphore must be taken before it can be given from a non-ISR context, the same is not mentioned for the ISR case. But I would assume that the rule must still be obeyed, because FreeRTOS maps semaphores to queues, and the command simply sends an item to the queue, this might get the semaphore mechanism out of balance.
Whether or not this is a bug depends on FreeRTOS details and a potential assertion that the semaphore can always be obtained without waiting (which would be worth a comment in the source code).
If I were you I'd probably try to replace that by `res = xSemaphoreTake(p_i2c->cmd_sem, ticks_to_wait); if (res == pdFALSE) { return ESP_ERR_TIMEOUT; } and see what happens. ;)

@tdesmet My above suggestion probably won't fix your problem, but it could help reduce problems. The assumption that p_i2c->cmd_sem can successfully be taken on entry to i2c_master_cmd_begin() is in principle valid if the other code is robust.
But in the sense of a more robust code, I believe this line should be chaged to res = xSemaphoreTake(p_i2c->cmd_sem, 0); if (res == pdFALSE) { return ESP_FAIL; }. This suggestion is valid for a case where timeout handling can be cleanly under control such that the semaphoe will definitely be available immediately after i2c_master_cmd_begin() detects a timeout and releases the p_i2c->cmd_mux mutex. Regarding handle_timeout(), see below.
While the priority of the task calling i2c_master_cmd_begin() is lifted to avoid conflicts with other tasks calling the same function, this does not necessarily help much against the race conditions in the code, which I described initially. E.g. if the execution of i2c_master_cmd_begin() "starves" between [portTickType ticks_end = xTaskGetTickCount() + ticks_to_wait;](https://github.com/espressif/esp-idf/blob/master/components/driver/i2c.c#L937) and ticks_to_wait = ticks_end - xTaskGetTickCount(); and the timeout is tight, then a timeout will be signalled although it does not necessarily occur.
My question would be, is timeout handling cleanly implemented? Upon a timeout "detection", i2c_master_cmd_begin() simply sets p_i2c->status = I2C_STATUS_DONE; which also tells i2c_master_cmd_begin_static() to do nothing if more data is signalled via interrupt. -- not even give back p_i2c->cmd_sem.
I think there are two problems with this. First, again, there is a race condition between waiting for p_i2c->cmd_sem and setting p_i2c->status = I2C_STATUS_DONE;, and second, after the first timeout occurs, p_i2c->cmd_sem is in trouble.
You could try the following modification, but be aware that if it does anything good then it would only solve the behaviour after a first timeout:
res = xSemaphoreTake(p_i2c->cmd_sem, ticks_to_wait);
if (res == pdFALSE) {
    (void)xSemaphoreGive(p_i2c->cmd_sem);   /* <---- ADD THIS LINE */
    ret = ESP_ERR_TIMEOUT;
} else if (p_i2c->status == I2C_STATUS_ACK_ERROR) {

I'd recommend also making the other modification to be warned about problems when taking the semaphore:
if (res == pdFALSE) {
    return ESP_ERR_TIMEOUT;
}
/* vvv replaced vvv */
res = xSemaphoreTake(p_i2c->cmd_sem, 0);
if (res == pdFALSE) {
    return ESP_FAIL;
}
/* ^^^ replaced ^^^ */
i2c_reset_tx_fifo(i2c_num);
i2c_reset_rx_fifo(i2c_num);

This issue should have been solved on the latest IDF, if it is not, please feel free to reopen it.


State not working

Describe the bug
I use the setting for state:
state: {
types: ['local_storage'],
filters: true,
page_number: true,
page_length: true,
sort: true,
columns_visibility: true,
filters_visibility: true
},
Reproduction steps:
Steps to reproduce the behavior:

I filter something
I reload the site
The filtering is gone

Expected behavior
I thought the filtering should be still there
Observed behavior:
No filtering is vissible
TableFilter version: 0.7.2
Browser and version: Newest Chrome, Safari, Firefox
OS and version: Mac Newest
Device: iMac

Problem can be reliably reproduced, doesn't happen randomly: [Yes]

With this setting it works:
types: ['hash', 'local_storage'],
no Ideo why?!?

And it is only working if i load the same site.  Do you have ideas?

It works, I had no table id and so the id was every time another one. Hope it helps someone


Random showcase

Hackathon Git Labs Project PR 🎉🎉
PR contains:

Doesn't add any features.
I've refactored the JavaScript to use templates for both showcase and community sections.
Refactored to download emojis once.
Reordered the code a bit.

If this is too much reordering of working code feel free to reject.
Hacktoberfest 2022:

[x] Does this PR follow the intermediate.md guide and submitted as part of Hacktoberfest 2022?

Breaking changes

None

Screenshots

None

@auxfuse There's a fair amount in this, I have reviewed thoroughly, tested and am happy to merge. I'll give it an hour before I do so in case you have any comments. Otherwise I'll go ahead.


Remove channel id from exec response in blocking mode

Fixes #140

LGTM 👍

Codecov Report

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

@@            Coverage Diff            @@
##             master     #142   +/-   ##
=========================================
  Coverage          ?   94.46%
=========================================
  Files             ?        9
  Lines             ?      668
  Branches          ?        0
=========================================
  Hits              ?      631
  Misses            ?       37
  Partials          ?        0

Continue to review full report at Codecov.

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

Do we have to bump up the release version now?

So the plan for stable release is for next Wednesday. I think this change was small and I will wait till Sunday to see if we find anything else. I will do a release on Sunday or early Monday to be prepared for Wednesday stable release. Please keep testing :)


.editorconfig

Hi,
it would be nice if you added an .editorconfig to the project, otherwise it's hard not to overwrite the settings you prefer.
Regards
Stefan

Trivial enough.


Add gltf sample viewer

Shadowing #1962, adding golden images.

Doesn't look like we'll need this branch.


Update service manual team page re reduced team

Update date for message re reduced team

In branch sept-release


[Prototype] Have ContainerRuntime wait to process until it sees the whole batch

[do not check in]
This would allow a follow-up change to switch PSM to be totally batch-based instead of individual messages.

We actually did this!


usability: significant performance/usability issues with fleetctl batch unit processing and slow etcd storage

probably relates to this issue and #1344, #1433 PRs.
When etcd datadir is located on slow storage (i.e. hdd), fleetctl acts really slow. when you move etcd storage into tmpfs - it works really fast.
CoreOS: 955.0.0
each CoreOS node:
etcd2: 2.2.5
fleet: latest master
512 Mb RAM
1 CPU
Cluster of 3 etcd member nodes and three fleet machines:
$ fleetctl list-machines
MACHINE         IP              METADATA
0903835b...     <IP_ADDRESS> hostname=coreos1
78b98c5d...     <IP_ADDRESS> hostname=coreos3
f8f4ec94...     <IP_ADDRESS> hostname=coreos2

$ etcdctl member list
4c32b6c5bcf8cfd4: name=78b98c5dfe468973b93e098a5a5829ea peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379
92b755ba67be7f8b: name=0903835ba13faf7f62cf5d8ddc7812de peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379
cafc731b5b471889: name=f8f4ec94d4193d2f160e8bd22ed360be peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379

ping time between etcd members: ~0.469 ms
fleetd configuration:
# /etc/systemd/system/fleet.service.d/10-extra-options.conf
[Service]
Environment=FLEET_ETCD_REQUEST_TIMEOUT=2 # I used that to avoid etcd registry timeouts.
# /etc/systemd/system/fleet.service.d/10-opt-bin.conf
[Service]
ExecStart=
ExecStart=/opt/bin/fleetd
# /run/systemd/system/fleet.service.d/20-cloudinit.conf
[Service]
Environment="FLEET_METADATA=hostname=coreos1"
Environment="FLEET_PUBLIC_IP=coreos1"

Template unit file<EMAIL_ADDRESS>[Unit]
Description=My Service

[Service]
TimeoutStartSec=0
ExecStart=/bin/sh -c "trap 'exit 0' INT TERM; while true; do echo Hello World %i; sleep 10; done"

Steps to reproduce:
$ fleetctl submit<EMAIL_ADDRESS>Unit<EMAIL_ADDRESS>inactive
$ time fleetctl start<EMAIL_ADDRESS>Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive
Unit<EMAIL_ADDRESS>inactive on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on f8f4ec94.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 78b98c5d.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 78b98c5d.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 78b98c5d.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on f8f4ec94.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on f8f4ec94.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 0903835b.../<IP_ADDRESS>
Unit<EMAIL_ADDRESS>launched on 0903835b.../<IP_ADDRESS>

real    0m26.688s
user    0m0.057s
sys     0m0.007s

26 seconds to schedule 10 units? Is it by design: at first submit all units, then start them? I thought that fleetctl should just submit unit with desired state, but not submit unit, then change desired state.
Then... Why for some units we can see additional info like Unit<EMAIL_ADDRESS>inactive on 0903835b.../<IP_ADDRESS>?
Another example without template:
$ for i in {1..10}; do sed "s/%i/$i/g"<EMAIL_ADDRESS>> hello$i.service; done
$ time fleetctl start hello{1..10}.service
Unit hello1.service inactive
Unit hello2.service inactive
Unit hello3.service inactive
Unit hello4.service inactive
Unit hello5.service inactive
Unit hello6.service inactive
Unit hello7.service inactive
Unit hello8.service inactive
Unit hello9.service inactive
Unit hello10.service inactive
Unit hello2.service launched
Unit hello3.service launched
Unit hello4.service launched on 78b98c5d.../<IP_ADDRESS>
Unit hello5.service launched on 0903835b.../<IP_ADDRESS>
Unit hello1.service launched on 0903835b.../<IP_ADDRESS>
Unit hello7.service launched on f8f4ec94.../<IP_ADDRESS>
Unit hello10.service launched on 78b98c5d.../<IP_ADDRESS>
Unit hello6.service launched on 0903835b.../<IP_ADDRESS>
Unit hello8.service launched on 0903835b.../<IP_ADDRESS>
Unit hello9.service launched on f8f4ec94.../<IP_ADDRESS>

real    0m29.444s
user    0m0.050s
sys     0m0.011s

We can see that there is no difference.
Here is the script which submits units directly into etcd registry with desired state and it doesn't wait for etcd response:
$ time ./units_submiter.sh
... ... ...
... ... ...
... ... ...
real    0m11.895s
user    0m0.279s
sys     0m0.151s

This example shows how we can improve fleet performance by three times (in case when we have slow etcd storage).
I suggest to use something like "parallel connections" limit. We can create N parallel tasks to submit units. Go channels should help. And in addition we have to make sure that fleetctl uses single TCP connection with etcd for all queries.
P.S. Just in case, command to remove all unit files: fleetctl list-unit-files --no-legend | awk '{print "/usr/bin/fleetctl destroy "$1}' | sh -s
/cc @jonboulle @tixxdz

Also fleetctl status<EMAIL_ADDRESS>fails when we don't have stored fingerprints for remote hosts inside .fleetctl/known_hosts
Error running remote command: timed out while initiating SSH connection

When we explicitly add fingerprints inside this file - status works.

This report would be mostly true, as we have been already seeing it from time to time. Yes it could be slow, especially when etcd is not able to respond immediately.
Though I would say, that's just how it is. It's rather a design issue.
The only alternative would be to get rid of dependency on etcd as much as possible. For example, turn on enable_grpc & use etcd3.
So I'll close this issue. Though thanks for the precise report!


Support vh and vw units

Hi,
I think we should be able to support vh and vw units by replacing Xvh by X * Dimensions.get('window').height / 100 and Xvw by X * Dimensions.get('window').width / 100, can't we?

Check this out: https://github.com/DriveWealth/gulp-react-native-stylesheet-css/issues/2

I'm guessing this issue more asking for vw/vh support in styled components. There's not much this library can do to add support there - it's up to styled components to add support for it in their runtime
My styled-components clone supports it (https://jacobp100.github.io/cssta/css-support/) - so it is definitely possible for support to be added!
I'll close this issue as there's nothing we can do here to support it, but feel free to continue the discussion or ask any other questions

Oh, sorry then, I thought it was the right project to target. Ok, I'll move it there.

There’s probably an issue already. It’s a common feature request

Yeah, I found it. Seems on stand by for now. I'll try to understand exactly how it should be done, see if I can give it a try.


Customer Feedback: Getting access tokens from Azure AD for AKS API server is not documented.

Customer feedback (that I agree with):
Customer is accessing the API server in their AKS cluster via C# code, and needs to create an access token manually.  Nowhere in our docs do we describe the scope the customer is supposed to use (6dae42f8-4368-4678-94ff-3960e28e3630 -- literally this GUID).
The only place it is documented is on the GitHub page for kubelogin.  I had to figure out the problem for the customer by manually examining the cached token from kubelogin.

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

ID: 0edc2c1c-7504-0c03-4d90-ff3270b5136b
Version Independent ID: 5ae58a63-a08b-bf15-a017-bbc1031cd793
Content: AKS-managed Azure Active Directory integration - Azure Kubernetes Service
Content Source: articles/aks/managed-azure-ad.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: miwithro

@jaspecla
Thanks for your feedback! We will investigate and update as appropriate.

@jaspecla
Thank you for bringing this to our attention.
I've delegated this to content author @MGoedtel, who will review it and offer their insightful opinions.

This information is delivered in the following article. I'll create a work item to link the articles together so that someone else doesn't encounter the same experience. Thanks.
Addressing in PR
#please-close.


The number of exported issues is underreported

Describe the problem
The export tool is underreporting the number of items it exported. It's not a big issue, but I find myself verifying the actual number of json files often. Currently it is reporting this:
[I][15:43:50] Processing 70/70 - 'ISSUE-10152'.
[I][15:43:50] Export complete. Exported 70 items (0 errors, 114 warnings) in 00:03:36.

However, because my import-config.json contains "download-options": 7 it has actually downloaded 423 files\issues because it also successfully exported parents, epics and sub-tasks.
I would suggest reporting the actual number like this:
I][15:43:50] Processing 70/70 - 'ISSUE-10152'.
[I][15:43:50] Export complete. Exported 423 items (0 errors, 114 warnings) in 00:03:36.

That way you have both numbers in view, the number of issues selected by the query (70), and the actual number exported (423).
Tool version
master

@moerketh Finally got around to merging this one. Thanks for the great contribution!


Automatic URL encoding

Thank you for nock, it's been a huge help!
I'm currently testing some http calls and had some problem when they contain spaces (or any non-ASCII characters).
The following script will log "The call was intercepted".
const nock = require('nock');
const axios = require('axios');

const host = "http://localhost";
const resource = "/resource/with space";

nock.disableNetConnect();

const scope = nock(host)
    .get(encodeURI(resource))
    .reply(200);

axios.get(host + resource)
    .then(res => {
        console.log("The call was intercepted");
    });

However, the next script won't log anything, because nock doesn't automatically encode the URI:
const nock = require('nock');
const axios = require('axios');

const host = "http://localhost";
const resource = "/resource/with space";

nock.disableNetConnect();

const scope = nock(host)
    .get(resource) // We only changed this line
    .reply(200);

axios.get(host + resource)
    .then(res => {
        console.log("The call was intercepted"); // Doesn't happen
    });

I'm not 100% sure if the HTTP spec requires clients to URL encode the request path, so it might be that axios is overzealous about it. But it would, regardless of axios behaviour, be convenient if nock could handle URL encoded paths behind the scenes somehow.

Almost two years later I have run into a similar problem with overzealous Axios and I am not sure the best way to proceed.

@THoisington the best next step would be to create a notebook on RunKit that reproduces the problem, e.g. like this one https://runkit.com/gr2m/node-nock-nock-768
Once we have that you (or someone else) can use the code to create a test and start a pull request with it. And then finally someone can use that (unless you want to try of course) to figure out how to get the failing test pass :)

So I will say I eventually found out the best way for me to make my test work was to use Node's Stringify to build my request URL instead of using any sort of Encoding function or library on a string. This is probably obvious to most here.
So my working jest test ended up being:
it("correctly builds getEntries() request", async () => {
            expect.assertions(1);

            const givenParameters = {
                ...
            };
            const expectedParameters = {
                time_since: "2017-08-18 00:00:00",
                time_until: "2018-02-09 00:00:00",
                "filter[billable]": 2,
            };

            // Basically just standard code to create the Nock Object (passing in the path)
            const nockObj = getNock("/entries?" + stringify(expectedParameters));

            await userClockodo.getEntries(givenParameters);

            expect(nockObj.isDone()).toBe(true);
        });


Progress event

Hi, Can someone inform me what I'm doing wrong here.
I'm trying to use the 'progess' event to indicate the percentage of progress of GETting this json file.
I thought that e.percent was emitted to the progress event, however it appears undefined.
https://github.com/visionmedia/superagent/blob/master/lib/client.js#L923
request
  .get('https://gist.githubusercontent.com/chrisbuttery/6f2aac24c25e389e0e3e/raw/8f97e20f01a77ad4d7b47d8f1ef51b07e624b943/demo.json')
  .on('progress', function(e) {
    console.log('e', e);

    // 1st pass
    // e XMLHttpRequestProgressEvent {}
    // loaded: 32768
    // position: 32768
    // total: 0
    // totalSize: 0

    // 2nd pass
    // e XMLHttpRequestProgressEvent {}
    // loaded: 59042
    // position: 59042
    // total: 0
    // totalSize: 0

  })
  .end(function(err, res){
    if (err) console.log('err: ', err);
    console.log('res: ', res);
  });

Not sure what I was doing wrong, but this is working now.


Migration from Homebrew/homebrew Pt2

Lilypond caused everything to time out in #3, so trying splitting the PRs in half this time.

From the error messages on these longer builds I think this is failing because Homebrew's brew test bot cmd doesn't write anything to the output unless there's a problem, so on bigger builds which don't error out (Like Lilypond) Travis thinks nothing is happening, whereas the test-bot just happily compiles quietly. Any thoughts @mikemcquaid @xu-cheng?

Could run brew test-bot --verbose I think?

Nice. I'll give it a try shortly. Fingers crossed. The timeout isn't at least till the hour mark - I've build Qt with Travis before now, so it's happening way too quickly for Travis to kick us off in that regards. Hopefully a more verbose output will keep it happy.

@DomT4 Let's put pdfjam.rb into a separate PR. As for lilypond, there's another related PR in homebrew core: https://github.com/Homebrew/homebrew/pull/37021

Sure, good idea, will do that shortly. Re Lilypond I may cherry-pick that PR's commit so we can actually test it - Given the test-bots in Homebrew/homebrew can't test TeX stuff.

Alright, that's everything aside Lilypond moved across to Homebrew/tex successfully.

Hmm, no dice. Still didn't print the output :anguished:

You need to rename and try again.

Done.

New error, sigh.
The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over).

The job has been terminated

That's annoying. Let's review all of its dependencies and bottle them as many as possible.

It looks like everything aside  t1utils,  the internal guile18 and the custom fontforge => "with-x11" deps are bottled already. FontForge is a long and noisy compile, and is what caused the failure apparently.

t1utils at least will be bottled after https://github.com/Homebrew/homebrew/pull/39115 is merged.

Discovered this piece of upstream documentation that allows for longer, silent builds. Have pushed it here to see whether it works. Verbose is too verbose, and normal is too quiet, so perhaps the upstream variable buys us enough time. We'll see.
Otherwise we may need to look at altering the --verbose bit on the test-bot to make everything compile as silently as usual except for the formula compile itself.

Apparently, a 30 minute compile window is still not enough for this particular formula. I'm not really sure what to do beyond this. My temptation is to add fontforge with x11 by default to Homebrew/x11, for us to bottle that, and then use that dependency here - But that provides a crappy UX.
The Fontforge with x11 compile is usually at least a ~15 minute job, so that's already half the build period taken up. The internal guile18 can easily take ~10-15 minutes as well sometimes, and Lilypond isn't a small compile either.
We may be forced to accept we just can't test Lilypond for the foreseeable. We can't test it in Homebrew/homebrew either, so we could always move it sans test without losing anything, even if we don't gain much in this single formula situation.

CC @mikemcquaid for comment on the above.

We may be forced to accept we just can't test Lilypond for the foreseeable. We can't test it in Homebrew/homebrew either, so we could always move it sans test without losing anything, even if we don't gain much in this single formula situation.

Yeh, I'd consider just doing that.

https://github.com/Homebrew/homebrew/pull/39973


[FLINK-9799] Generalize and unify state meta info snapshot

What is the purpose of the change
This PR generalizes and unifies the de/serialization of state meta information in backends. We replace the snapshots and reader/writers of the individual state types with a general StateMetaInfoSnapshot and the corresponding StateMetaInfoSnapshotReadersWriters. Backwards compatibility is maintained.
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

CC @azagrebin

@sihuazhou @azagrebin thanks guys for the fast reviews! Will address the comments and merge.


Script availability in conda recipe

Hey,
There is a bioconda package for mccortex, which is great. But the scripts, such as make-pipeline.pl are not on PATH. If I (or yourselves) were to update the bioconda recipe to add these to the package, which scripts do you think would be necessary?

Glad to hear that the conda package has found other users than myself!
Why not at all the scripts? I didn't include them at the time because i had no use for them, but others might.

Sure. I guess the only thing will be updating the dependencies for the recipe. At a quick glance some scripts needs Perl, some need graphviz, some need python (and associated libraries), some need R...

Yikes, sounds like a mess, but doable. It's only start with the scripts that are necessary.
I don't know which ones are absolutely necessary. @kvg?

I mean, i have used the mccortex conda package for years without any need for scripts. Why not create a separate conda package just for the scripts? It could depend on the package with the binary.

My personal use case was that I wanted to use the make-pipeline.pl script inside the biocontainer image that is built from the bioconda package. In hindsight I could just download that script and use it inside a conda env with mccortex installed... Maybe that is a better way of doing it rather than creating a new recipe?

I think you should be just fine composing conda packages with the mccortex cons package. That package is just a binary if i recall correctly.


How to Open File

Hello Everyone Im Need Help It Very Important Im Needed To Open But It Not Work

It Named Run.bat And It Dont Work


Saddle Finance: update dependency versions, fix inputTokens order

#556
All fields related to pool.inputTokens should now be fixed, protocol.totalPoolCount should now match actual pool count.

Thanks for the fixes. Can you update https://github.com/messari/subgraphs/blob/master/deployment/deployment.json#L603-L615 to true so it'll deploy?


[dotnet library] activate misc system tests

Description
Activate number of system tests that work without any change to the tracer.
Workflow

⚠⚠ Create your PR as draft (we're receiving lot of PR, it saves us lot of time) ⚠⚠
Follows the style guidelines of this project (See how to easily lint the code)
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

NOTE:  By default in PR only default scenario tests will be launched. Please refer to the documentation to run all scenarios in your PR if needed.

Once your PR is reviewed, you can merge it ! :heart:

Still a lot of failures, but dotnet all passing now, so I guess they're flake?


creating NSR in openbaton on an openstack instance giving error "imageubuntu is not contained into the images of the vimInstance chosen"

I am installing OpenBaton on an instance on a private network in OpenStack (Pike release). The screenshot of the network-topology is attached below

On changing the routing table of my OpenStack machine I can ping as well as ssh into this instance from my OpenStack machine terminal. I can also ping my OpenStack machine from this instance
Now I created a POP in OpenBaton as follows
{
   "name":"pop",
   "authUrl":"http://<openstack-server-ip>/identity/v3",
   "tenant":"673bf2477d4a48eeb32433b175dd1c19",
   "username":"admin",
   "password":"xxxxx",
   "keyPair":"openbatonkeypair",
   "securityGroups":[
      "default"
   ],
   "type":"openstack",
}

Now I am trying to create the iPerf Network Service as given here. I am using this JSON as my Network Service Descriptor.
But I am always getting an error as

Exception was thrown -> Return message: Regarding the VirtualNetworkFunctionDescriptor iperf-client: in one of the VirtualDeploymentUnit, imageubuntu is not contained into the images of the vimInstance chosen. Please choose one from: [] or from []

I am attaching a screenshot of the images in my OpenStack project

I have uploaded openbaton.log and generic-vnfm.log

hi @sipian could you please provide also the logs of the openstack4j vim driver/plugin? if you have used the bootstrap (binary) installation, they should also be located somewhere in /var/log/openbaton/.
My assumption is that your OpenStack setup uses glance v3 APIs, which probably are not supported by the openstack4j vim driver (but there were other users making that work..).

Hi @gc4rella ,
These are the log files that I are there in /var/log/openbaton/plugins
plugin-openstack_2017-12-09_10-50-03.log
plugin-test_2017-12-09_10-44-42.log
plugin-test_2017-12-09_10-45-40.log
plugin-test_2017-12-09_10-50-02.log

The problem went away after I installed OpenStack Newton release.
Thanks @gc4rella for your help.

OK, as said the problem should be due to the new version of the glance APIs. We are working on it, and we'll make sure they will be supported by default in upcoming versions of the plugin.


Upload using browse button.

After image upload with browse button, second time(or 3 time) browse button doesn't work(i mean method doesn't called)

It won't let you upload the same image twice in a row, if that's what you intend you have to clear the first image.

No, i am limited file count to 1. and upload on image receive success from server, and browse another image for upload but it doesn't work.
i have profile picture. on hover i am showing browse button and user can chage picture , but second time he cant. after refresh he can change again 1 time

If you've set max to 1 this sounds like the correct behaviour?
Maybe provide a snippet of your code.

HTML
<image-upload
          [max]="1"
          [maxFileSize]="5242880"
          [url]="'http://---------/update-profile-picture'"
          [headers]="uploadHeader"h
          [partName]="'file'"
          [buttonCaption]="'browse'"
          [dropBoxMessage]="''"
          [extensions]="[]"
          [preview]="false"
          [fileTooLargeMessage]="'Wow, this is a one large file. Can you please make sure it is 5MB max?'"
          (onFileUploadFinish)="imageUploaded($event)"
          (dragover)="dragImage = true" (dragleave)="dragImage = false"
  ></image-upload>

TS
  imageUploaded(event: any) {
        this.dragImage = false;
        if (event.serverResponse.status !== 200) {
            this._snackBar.openFromComponent(ErrorComponent, ErrorComponent.getConfigs(5000));
        } else {
            const resp = JSON.parse(event.serverResponse._body);
            this.hideButtons();
            if (resp.success) {
                this._sharedDataService.companyLogoId = resp.response.profilePictureId;
                this._sharedDataService.companyInfo.profilePictureId = this.companyInfo.profilePictureId = resp.response.profilePictureId;
                this._companyService.getCompanyLogo(resp.response.profilePictureId).then((response) => {
                    this._sharedDataService.companyLogoURL = response;
                })
                    .catch((e) => {
                        this._snackBar.openFromComponent(ErrorComponent, ErrorComponent.getConfigs(5000));
                    });
            } else {
                for (const key in resp.errors) {
                    if (key === 'USER_PROFILE_IMAGE_UNSUPPORTED_TYPE' || key === 'USER_PROFILE_IMAGE_INVALID_FILE') {
                        this.imagePatterError = key;
                    }
                }
            }
        }

    }

Why you decided close this??

Because this behavior is expected and it's not a bug.

Actually you closed this.

And yes, if you set max to 1 it won't let the user upload a second - what are you trying to accomplish by setting max to 1?

No i doesn't closed this. :)
Ok, i understand what you say.
I want set user profile picture, second time browse should change that picture. how i can do that

I believe that there is no way to do that in the current version. We can add something like [replace]=true input to make this behavior possible. What do you think @UncleDave?

@UncleDave I think that it'll mean that new images just push old images out of the array. I even think that we can use Observable to make new interface more convinient 'cos all that onUpload onRemove hooks become a real mess.


Fix duplicated order by clause

Currently, the Limit query filter is applying an ORDER BY clause in addition to LIMIT. This is causing a SQL syntax error, since GetReconciliations() adds another ORDER BY clause by default.
Unfortunately, simply removing the order clause from the filter doesn't resolve this, because the end result is also a syntactically incorrect statement. In this case the LIMIT clause comes before the ORDER BY clause which is incorrect.
Also, applying the order by clause before the filter will break other queries using different filters. For example, in cases where the query is using a WHERE filter, the final query would have an order by clause before the where clause.
This PR implements the least invasive fix to resolve the issue.
https://github.com/kyma-project/control-plane/issues/1307

/retest


Call reserve on decoded->extra_channels()

This prevents the pointers that we keep in extra_channels from being
invalidated by reallocation.

That looks perhaps a bit fragile - can we do resize instead?

That looks perhaps a bit fragile - can we do resize instead?

I looked it up when coming up with the fix, and (https://stackoverflow.com/a/46132842):

No reallocation shall take place during insertions that happen after a call to reserve() until the time when an insertion would make the size of the vector greater than the value of capacity()

If we really want to avoid any such risk, how about populating the two vectors in separate passes? One for decoded->extra_channels(), and then one for extra_channels once we know that we are not going to touch the former any further.

That looks perhaps a bit fragile - can we do resize instead?

I looked it up when coming up with the fix, and (https://stackoverflow.com/a/46132842):

No reallocation shall take place during insertions that happen after a call to reserve() until the time when an insertion would make the size of the vector greater than the value of capacity()

If we really want to avoid any such risk, how about populating the two vectors in separate passes? One for decoded->extra_channels(), and then one for extra_channels once we know that we are not going to touch the former any further.

The advantage of doing a resize first is that there is no push_back() in the loop, and it makes it more obvious (and likely easier to catch) that we are relying on the resize being called with the correct size.

uugh, keeping raw pointers to vector elements sounds a recipe for bugs. Could we keep indices into the array instead?

uugh, keeping raw pointers to vector elements sounds a recipe for bugs. Could we keep indices into the array instead?

They are in the same order, so the way that things are at the moment, we can instead pass the additional data separately, as a parallel array. How is this?


Consider less intrusive cargo manifest updating

#3 brought in the ability to edit cargo manifest files directly. However, extra fields are written to Cargo.lock and existing fields get reordered (see https://github.com/justinrubek/bomper/commit/12572aeec767a91dacd7ee7a406fea1c93138dfd#diff-13ee4b2252c9e516a0547f2891aa2105c3ca71c6d7a1e682c69be97998dfc87e).
I'm not sure how much work it would be to prevent this from happening, but I anticipate that it could be a non-trivial change. In the meantime it should be sufficient to either

Use by_file replacement (just like how was done in 0.5.0)
Accept the modified files. It doesn't break them but just makes them more explicit

I'm not entirely against leaving things as they are but it is something worth considering

I just ran into this as an issue. I had a proc macro crate that had like this:
[lib]
proc-macro = true

When running bomper, it added crate-type = ["rlib"] which is not accurate. That wasn't the only change I found annoying.
Some goals I think should be accomplished as a result of this:

Provide for the ability to not add any fields that were not set previously
Ensure fields that were set are not changed. For example, is the package entry has version = { workspace = true }, it should not be overridden with an explicit value, but instead it should keep inheriting it from the workspace

I should add that it likely isn't enough to try to ensure that a field such as crate-type is already specified. For the proc-macro, setting crate-type = ["proc-macro"] will trigger a clippy lint.

It seems that this is due to calling from_path which calls complete_from_path to fill in missing implicit data. Instead, from_slice can be used to retrieve only the included data.

I'm leaving this open despite #9. It seems that comments may be removed. I think stopping implicit data from being added is a big win, but further efforts may be a good idea.


feat(wallet): set default address type to Bech32

Description:
Set default address type to Bech32
Motivation and Context:
Address type is now configurable via the settings page. Users that don't want to use Bech32 can switch if they like.
How Has This Been Tested?
Manually
Types of changes:
Enhancement
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 20.497% when pulling c627c69b9bfabd82164440f1be02e8f3bad7e30b on mrfelton:feat/bech32 into 9454facf80abdd14d7a4359a1c3797d981d01621 on LN-Zap:next.

Coverage remained the same at 20.497% when pulling c627c69b9bfabd82164440f1be02e8f3bad7e30b on mrfelton:feat/bech32 into 9454facf80abdd14d7a4359a1c3797d981d01621 on LN-Zap:next.


Vattenfall S34U18 (Sanxing SX631) change

For the S23U18 model (Sanxing SX631) that Vattenfall is distributing now you have to increase the buffer slightly.
I tried with #define BUF_SIZE 60 and it seems sufficent.

Cool, I will add it to the main branch and update the README with info about the Sanxing SX631 meter 👍

Yes, please do that. I have been running mine fine since a week ago now with no issues whatsoever.

@Spitfire69 Hi! I have a few questions for you :-)
First of all, did you have any problems with getting this to work except from the buffer? I cant get it to work, i get the data from the meter but i get crc fail. What hardware are you using?
And iam interrested in what data you get from the meter as i dont get very much from my sanxing (dont have it in front of me right now) but i only think its like 8 lines and no voltages och individual phase data at all.
Looking forward for you answer :-)

Hi, I’m using a Wemos D1 mini and it has been working flawlessly for over a month now. As mentioned the only thing needed was to extend the buffer. However before I did that I got CRC errors so my suggestion is to just add more bytes and test. Good luck!

Ok, iam using D1 mini, tried increasing buffer to 100 (was 60, but i dont know what it was when you made yours) and still no luck with crc :-(
So for now i bypassed the crc check and now i get data to home assistant but the energy dashboard is still blank.. well well..

Hi, I’m using a Wemos D1 mini and it has been working flawlessly for over a month now. As mentioned the only thing needed was to extend the buffer. However before I did that I got CRC errors so my suggestion is to just add more bytes and test. Good luck!

@Spitfire69
What does your sanxing output?
this is what i get from mine, would like to compare your output with mine
[21:43:03][D][data:265]: /AUX5
[21:43:03][D][data:265]: 1-3:0.2.8(50)
[21:43:03][D][data:265]: 0-0:1.0.0(220119214300W)
[21:43:03][D][data:265]: 0-0:96.1.1(SANXING SMART ELECTRIC)
[21:43:03][D][data:265]: 1-0:1.8.1(031189.251kWh)
[21:43:03][D][data:265]: 1-0:1.8.2(000000.000kWh)
[21:43:03][D][data:265]: 1-0:2.8.1(000000.000kWh)
[21:43:03][D][data:265]: 1-0:2.8.2(000000.000kWh)
[21:43:03][D][data:265]: 0-0:96.14.0(RATE1)
[21:43:03][D][data:265]: 1-0:1.7.0(04.407kW)
[21:43:03][D][data:265]: 1-0:2.7.0(00.000kW)
[21:43:04][D][data:265]: !8B77
[21:43:04][I][crc:276]: Telegram read. CRC: E7C2 = 8B77. PASS = NO

Yours is not even close…has Vattenfall installed your or is it a standard Sanxing? If that is the case I guess they have different firmware.
Here’s my output:
[21:46:43][I][crc:276]: Telegram read. CRC: 84C3 = 84C3. PASS = YES
[21:46:43][D][sensor:113]: 'Cumulative Active Import': Sending state 1905.56995 kWh with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Cumulative Active Export': Sending state 6.24500 kWh with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Cumulative Reactive Import': Sending state 0.00100 kvarh with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Cumulative Reactive Export': Sending state 761.00598 kvarh with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Import': Sending state 2.46200 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Export': Sending state 0.00000 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Import': Sending state 0.00000 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Export': Sending state 0.74100 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Import Phase 1': Sending state 0.11300 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Export Phase 1': Sending state 0.00000 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Import Phase 2': Sending state 0.12500 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Export Phase 2': Sending state 0.00000 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Import Phase 3': Sending state 2.22300 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Active Export Phase 3': Sending state 0.00000 kW with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Import Phase 1': Sending state 0.00000 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Export Phase 1': Sending state 0.16300 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Import Phase 2': Sending state 0.02600 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Export Phase 2': Sending state 0.00000 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Import Phase 3': Sending state 0.00000 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Momentary Reactive Export Phase 3': Sending state 0.60500 kvar with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Voltage Phase 1': Sending state 231.89999 V with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Voltage Phase 2': Sending state 232.00000 V with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Voltage Phase 3': Sending state 227.89999 V with 3 decimals of accuracy
[21:46:43][D][sensor:113]: 'Current Phase 1': Sending state 0.90000 A with 3 decimals of accuracy

@Spitfire69 Can you please paste the meter output instead of what asphome sends to home assistant? :-)


MM-20989: Ensuring keyboard doesn't dismiss while submitting post

Summary
This PR makes sure that while a user is writing a post, they won't need to dismiss the keyboard before being able to tap any of the buttons in the post draft area.
Ticket Link
https://mattermost.atlassian.net/browse/MM-20989
Device Information
This PR was tested on:

iPhone 11 Simulator

@enahum Can you please help me by building an app for this PR? Thank you.

@jgilliam17 this PR is part of a feature branch and the feature still needs work, and I fear you are going to start highlighting known issues hehheheehhee

@jgilliam17 this PR is part of a feature branch and the feature still needs work, and I fear you are going to start highlighting known issues hehheheehhee

😄 You're probably right.
Please ping me here when the feature is ready. Thanks.


[Bug] After some time of inactivity bot leaves the channel and does not response to summon

Hello.
This happens on both machines: remote ubuntu 16.04 machine and raspberry pi.
After some time of inactivity (nothing playing for hour or so) bot leaves the channel, but is still online on server. When that happens bot cannot be summoned back by command and needs to be restarted by !restart command.
This issue is present for about half a year to a year now and wasnt fixed yet.
My bot settings seems not be the reason for it to happen.
Any help?

Have you tried using the review branch which contains developmental updates to MusicBot? You can switch to it using the command git checkout review. Make sure the bot is not running first.

No, I was running master branch, switched to review now.
I'll update you with log if problem occurs again

Do you have your bot's role allowed to enter that particular voice channel? Also check your overall server permissions. If you restrict something your bot won't work as expected.

@ccodykid My bots have highest role with Admin permissions and have no problems joining all channels or whatsoever. So far it was 6 hours on review branch without single bot leaving. I have good feeling about it, but I'll give it full 24 hours of inactivity to check if it really works without issues now.

I am having the same issue

It have been 2 days so I think I can post my feedback already:
Here is an error when bot leaves the channel:
discord.errors.ConnectionClosed: WebSocket connection is closed: code = 4015, reason = Voice server crashed..
(+a bit of random python errors - always something different so I'm not posting it)
BUT upgrading bot to review branch fixed my issue. now if bot gets disconnected(due to the error i just posted) it reconnects to the voice channel and it reacts once again to the commands.
tl:dr it's all dandy now.

should we still update to the review branch if we installed this bot only a couple months ago?


Crash on linux / X11, unable to create GlContext

Hello,
I compiled and ran successfully all the examples, but I failed to run a simple test program. The crash occurs inside bgfx::init(). The active threads are:
Thread-1
#0  0x00007ffff7bca320 in sem_wait () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x000000000042c98e in bx::Semaphore::wait (this=0x7ffff117e020, _msecs=-1) at ../../../../bx/include/bx/sem.h:173
#2  0x00000000004343f1 in bgfx::Context::renderSemWait (this=0x7ffff117e020) at ../../../src/bgfx_p.h:3156
#3  0x000000000042094f in bgfx::Context::frame (this=0x7ffff117e020) at ../../../src/bgfx.cpp:1120
#4  0x000000000041fe6c in bgfx::Context::init (this=0x7ffff117e020, _type=bgfx::RendererType::Count) at ../../../src/bgfx.cpp:971
#5  0x0000000000422726 in bgfx::init (_type=bgfx::RendererType::Count, _callback=0x0, _allocator=0x0) at ../../../src/bgfx.cpp:1966
#6  0x000000000041d55e in main () at /home/alex/sources/dont-stop-running/sandbox/main.cpp:8

Thread-2
#0  0x00007ffff757a3c9 in XLockDisplay () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x000000000043b71c in bgfx::GlContext::create (this=0x7fffec8a4928, _width=1280, _height=720) at ../../../src/glcontext_glx.cpp:65
#2  0x00000000004637f9 in bgfx::RendererContextGL::setRenderContextSize (this=0x7fffec0008c0, _width=1280, _height=720, _msaa=0, _vsync=false) at ../../../src/renderer_gl.cpp:1916
#3  0x000000000045f069 in bgfx::RendererContextGL::init (this=0x7fffec0008c0) at ../../../src/renderer_gl.cpp:887
#4  0x000000000044cf8e in bgfx::rendererCreateGL () at ../../../src/renderer_gl.cpp:2500
#5  0x00000000004212ae in bgfx::rendererCreate (_type=bgfx::RendererType::OpenGL) at ../../../src/bgfx.cpp:1434
#6  0x0000000000421405 in bgfx::Context::rendererExecCommands (this=0x7ffff117e020, _cmdbuf=...) at ../../../src/bgfx.cpp:1470
#7  0x0000000000420ce3 in bgfx::Context::renderFrame (this=0x7ffff117e020) at ../../../src/bgfx.cpp:1180
#8  0x000000000042fd23 in bgfx::Context::renderThread (_userData=0x7ffff117e020) at ../../../src/bgfx_p.h:1871
#9  0x000000000042ce56 in bx::Thread::entry (this=0x7ffff117e060) at ../../../../bx/include/bx/thread.h:146
#10 0x000000000042ce78 in bx::Thread::threadFunc (_arg=0x7ffff117e060) at ../../../../bx/include/bx/thread.h:165
#11 0x00007ffff7bc40a5 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007ffff6a6c88d in clone () from /lib/x86_64-linux-gnu/libc.so.6

The problem seems to be that s_display from XLockDisplay(s_display); is null.
Breakpoint 3, bgfx::GlContext::create (this=0x7fffec8a4928, _width=1280, _height=720) at ../../../src/glcontext_glx.cpp:65
65			XLockDisplay(s_display);
(gdb) p s_display
$1 = (Display *) 0x0

This is the compile command (as ran by the Clion ide):
/usr/bin/c++ -std=c++11 -Wall -Wno-unknown-pragmas -g CMakeFiles/sandbox.dir/main.cpp.o  -o /home/alex/sources/dont-stop-running/bin/sandbox -rdynamic -lbgfxDebug -lpthread -lGL -lX11 -ldl

Did you create window? bgfx doesn't deal with windowing and input, and you have to create window and provide window handle. Examples are using entry harness that provide that functionality:
https://github.com/bkaradzic/bgfx/blob/master/examples/common/entry/entry_x11.cpp#L297

No, I did not create a window. I also didn't notice the examples were implementing _main_ instead of main. I think I now understand how initialization happens, thanks.


Extension keeps reinstalling itself

Hi there!
I've tried removing the extension via :CocUninstall coc-prettier, but the next time I close and open neovim, it reinstalls itself. Any ideas what could be causing this or how to stop it?

Can't reproduce, try minimal vimrc.


Where is Total Cancelled Commitment applied?

Hi
According to the documentation, "Total cancelled commitment can't exceed 50,000 USD in a 12-month rolling window. ".
Question is where is this applied - EA or subscription?
Just need clarity on how refunds are processed and where does that total cancelled commitment apply? It is a subscription? An EA enrolment? Or somewhere else?
Thanks,
Amanjeet

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

ID: 3f0af130-6b0a-0a7e-5fd9-e67810f66b45
Version Independent ID: 445b1c77-472a-e0f7-45fc-168f4a2454f3
Content: Self-service exchanges and refunds for Azure Reservations
Content Source: articles/cost-management-billing/reservations/exchange-and-refund-azure-reservations.md
Service: cost-management-billing
GitHub Login: @yashesvi
Microsoft Alias: banders

@amanjeetsingh Thanks for the comment. We are looking into this and will get back to you shortly.

@amanjeetsingh For EA, it’s the enrollment. For MCA, it’s the billing account. We will update the article with these details and we will also add additional context to the article.
Stay tuned for the updates to roll out in a day or two. Let me know if you don't find the updated information.

Thank you @SadiqhAhmed-MSFT.
Please feel free to close this Issue.

@amanjeetsingh Thanks for confirming. Closing this issue for now.


Update the scripts to remove 8.x references

We are going to stop maintaining 8.x branches, so we need to update the scripts by removing all the references to 8.x branches from examples.

https://github.com/nodeshift-starters/scripts/pull/5


Renamed events folder to match GitHub username

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

It seems you created a new folder and now have 2 folders, please remove the older folder in this pull request also
https://github.com/EddieHubCommunity/LinkFree/blob/f7bfa039be7b812c6bc40bc341dcb6ce9dbf6fbd/data/wasiqb/events/2022-12-20-webinar.json

@eddiejaoude , thanks for pointing it out, the old folder was not showing up on my local, but it was there in my fork, so I deleted the old one from the repository directly.

Changes are done.


Delete .DS_Store

You might want to add .DS_Store to your global gitignore

Will be added on the next version update. also, working on some new features.


🎨 T - Language selector

For language selection in the header area of documentation pages, we have a custom-styled dropdown. See below:

Existing problems
The first downside between the current implementation and simply using a standard browser select element is that

It uses additional CSS and JavaScript to mimic a select element's dropdown behavior
There is not functional parity between it and a standard select and so, we lose some accessibility benefit we get for free when using a standard platform element

There is also a known problem on pages where there is a lot of available languages. As can be seen below, the dropdown extends beyond the viewport and a user needs to scroll the document to see all languages:

One of the possible reasons we decided to use a custom dropdown is to accommodate the "Add a translation" option.

Proposal
Use a standard select element for the languages, and provide move "Add a translation" to a button(this might be a feature we will loose entirely once the move to Github is complete)
For example:

Expanded

Benefits

Simple to implement
Easy to maintain
Less CSS
Smaller DOM
Less JavaScript
Greater accessibility

I'm all for it, one of my life missions is fighting for standard dropdowns in places where custom ones don't add value (and have not been given the time+care to reach parity, like you said).
We could also have "add language" as an option inside the select, maybe with a divider: https://jsfiddle.net/ahv8zL5k/1/
Or alternatively using <optgroup>.

We could also have "add language" as an option inside the select, maybe with a divider: https://jsfiddle.net/ahv8zL5k/1/
Or alternatively using <optgroup>.

For shizzle! I was thinking if we want to "detach" that functionality from the drop down, the button is an option.

+1 to @Gregoor's suggestion. Keeping all the options in the dropdown looks cleaner to me.

@Gregoor @schalkneethling @tobinmori
Agree with Gregor's suggestion here, it keeps the breadcrumb area lighter. Here's how it could look like on Desktop:

Thank you @malqinneh. Desktop looks good. I just need to double-check whether we are potentially causing any accessibility issues here. The more I think of it, the more I am second-guessing my own recommendation here 😄
I just might have a different suggestion here all together. Will get back to you ASAP.

Ok, I have done some additional thinking, research and chatted with Marco Zehe. My recommendation then stands as initially proposed:

Change the language selector to be a standard HTML select element
Add a simple link to the right-hand side of the select field that links to "Add a Translation"

Reasons for separating out "Add translation" from the select dropdown

The way screen reader users use a select drop is not conducive to discovery and as such, they are more likely than not to completely miss the "Add a translation" option
The way the select element will be described to screen readers is a means to select your preferred language. This again does not indicate that there is a separate option to potentially add a translation if your preference is not available.
Selecting an item will for all but one option reload the current page and change the locale to the chosen locale. "Add a translation" on the other hand redirects the users to a completely different page
As we move forward with the new infrastructure of MDN we might have a static list of available languages that are machine translated but, we will definitely not keep the functionality of adding a new translation. Having the UI, styling, and JS for these two "features" separate makes a simpler to remove one and keep the other.

I hope this all makes sense. If everyone agrees with this, I reckon we are ready to solidify the final design and then move onto the implementation phase. Thank you o/\o

Thanks so much @schalkneethling -- especially sold on no. 4 in your list of reasons for separating out [add translation] from the select dropdown. On that note; would it be OK if we don't support [add translation] on mobile?

would it be OK if we don't support [add translation] on mobile?

100% - Our current system for this is definitely not usable/not meant for use on mobile devices. It is definitely a task that is done on desktop computers.

Got it. @schalkneethling just to confirm;

Add language selector (desktop)
Add language selector (mobile)
Add [Add translation] link next to language selector dropdown (desktop only)

Assuming we want to allow users to use the language dropdown on mobile. Is this correct?

Is this correct?

Correct.

@malqinneh Thoughts?

Keeping the original functionality of table of contents intact -- how about one these?

Thanks, @malqinneh
I am torn between 3 and 7 😄 Leaning towards 3.

When comparing the two; there are no advantages to 7 (they both take up the same space / push content down the same distance).

@schalkneethling added some info under implementation decisions and next steps section in the description. Happy to revise as needed, let me know.

Note that in terms of implementation, we will currently only implement this change in Kuma as Yari does not currently support any l10n.