High Energy Impact

Description
Atom uses 8-10 times as much energy as Chrome on average. I consistently get Avg Energy Impact from 180 to 250. Are we aware of this, and if we are, are we addressing it?
Can I profile it somehow to find out which components are responsible the most?

Versions
Atom
Atom    : 1.7.2
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

Apm
apm  1.9.2
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.6.4

I think it depends mainly on what you're using Atom for and how many files you have open at a time vs Chrome with how many browser tabs you have open...If Atom has linters installed and you're dealing with large files or many files, you could have significant energy consumption; just as if you had half a dozen Chrome tabs open, each running javascript hungry web apps.

If you could supply usage statistics of Atom and Chrome over a period of time, indicating which each was doing, plugins installed, etc, I think that would help clarify this issue, and point us in the right direction.

I have these packages installed: https://gist.github.com/vjancik/4e87eec3d2ba4e6dbbfa933f638d89f4#file-packages-json
And yes I use a linter, but I get the crazy high energy consumption even when I don't.
As for Chrome, I use Chrome to read documentation and such, and have over 50 tabs open.
Under 10 tabs in Atom, only one window, and my linters are configured to run only on current file.

@vjancik Can you see if the high energy impact still happens in safe mode (atom --safe)?  Thanks.

Same here.: average power consumption 43 (Atom) to 23 (chrome). 10.11.4
Analyse of „Atom“.txt
Call this bug atomic meltdown.

@Tobias-Conrad Can you follow my instructions in the comment above yours and report back?

@50Wliu i am not able to use the terminal
problem is not all the time, i would gues it is connected with unsaved tabs.

Is this during active use or idle? I currently have two different projects open, each with many files, and I haven't touched it all day, but my current highest energy user is Slack due to background updates.
I will make edits to all my files, and not save any of them and measure the energy consumption so as to help determine the cause.

This is another facet of https://github.com/atom/atom/issues/1827. Yes, we know that Atom consumes a lot of resources, more than it should in some cases. Yes, we are working on it. Performance is a high priority for us.
We're trying to control the amount of Issues that we have to triage and track. Since this is an Issue that doesn't have a specific goal, I'm going to have to close it. If you want to discuss the problem until specific excesses can be tracked down, please use Discuss, the official Atom message board.

I work mobile, if you close this issues and did not find a solution for the #1827 ticket started 2 years ago, you are failing in my eyes.

I don't need to use --safe mode, I am fairly confident it's the extra packages. And yes it only happens when I'm using the editor, it's passive energy consumption is almost zero. Or when some process in Atom is running in the background.
But this needs to be addressed none the less, because people are using these plugins, that may or may not have rampant JS events / handlers and they reflect on the overall energy consumption of Atom.
So, here's some solutions to consider:

Either separate each installed package (outside of standard Atom ones e.g.) into it's own helper, so the user can easily see which package is causing the high energy consumption, and decide if they want to remove that package.
Or implement some sort of resource limiter runtime atop all of the plugins. Which would let the user / Atom itself monitor & throttle CPU / Memory usage of particular packages.

I know 2. is easier said than done because it's all JS, but it shouldn't be impossible.

@Tobias-Conrad There is no one "solution" for #1827.  We are constantly working on improving performance, as you can see in the release notes.  For example, we just merged a PR that improves performance when clicking on long lines.
@vjancik There's a feature request open to add a "task manager" to Atom to see which packages are using the most resources: you can subscribe to it here.


for comparison: re-implement compute_edges(_new) to limit implicit edges

Hey all,
I want to leave this PR here as a draft, first for discussion; secondly because it is a good trigger to start working on regression test suites and benchmark test suites.
I have caught up on history that PR #43 (and its lead-up) intended to address that more edges could be created, in particular around organisations. I will try to detail in an issue the model as I understand it (again before merging this).
However, the eventual code that got merged into production branch overshot the original proposal by inducing combinatorially additional edges for all people (not just organisations).
To better understand the history, I tried to implement also the proposal of #43 see this branch.
Using the example of the readme, the code in this PR creates 858k edges (~50 sec for finding the pruned path). Incidentally this code turned out as almost an exact copy of the original code on dev branch, as I tried to work back from my mental model in the production-dev branch (server_only). Hence consequently I was trying to understand what I was overlooking, which triggered looking into #43.
For comparison (crudely without rigor of a benchmark suite), the current production code produces 1.49M edges, and runs 3x slower because of it. It is worth noting that max-flow algorithm solutions (theoretically) scale linear (at best) in the number of edges, and as such are very sensitive to additional edges.
The other implementation of the proposal of #43 (in the branch linked above, not recommended for merge), produces 890k edges (similar runtime ~50 sec), but adds complexity to the code, and exposes a combinatorial growth of edges as more organizations trust more people - and as such a dangerous growth in runtime for max flow algorithms.
Lastly, I will document in the issue that the path length increases at most by +2 (with max +1 hop-in, and max +1 hop-out) when considering the primary graph versus the additional induced edges around organizations (#43).
I would argue that we are best positioned working with the primary graph, as we really need to bring path finding runtime down to max second(s) (so even 50 seconds is way too long) (and in later work the UX needs to be <100ms).
Hope this gets ample review and criticism, and excited to join all your hard work on Circles
Ben-

the current deployed prodcution code is v0.1.0-server+202307, so compute_edges in deployment is not the current head of current_prod which has further chances of #43 merged into it.
This PR would rework compute_edges to the primary graph; not even induced edges for organizations.


feat: add new admin invitations command to accept bot invites

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rawlingsj
You can assign the PR to them by writing /assign @rawlingsj in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rawlingsj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
2aeb8c2e0fc1f261885ccfdeb60ff72b8fa4193a
link
/test this

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@rawlingsj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
4b4eca35e15e1f228d7e55852468ecd324be38be
link
/test this

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

fixes https://github.com/jenkins-x/jx-admin/issues/68

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Request failed with status code 404

Describe the bug
I deployed memos in vercel. (https://simplememo.vercel.app)
But when I sign up, an error message appears "Request failed with status code 404".
I didn't edit any code.
How can I solve it?
Steps to reproduce

Go to 'https://simplememo.vercel.com'

Screenshots or additional context
No response

I see DEPLOYMENT_NOT_FOUND, Could you please provide the detailed steps to reproduce?

Oh, could you check again ''
I set the root directory to 'web' and got 'succeeded' message.
But when I create admin account, there is an error '404'.
How can I fix it, and how can I deploy memos to vercel?

I am not familiar with the Go language, so I am uncertain about how to deploy a server using it. Could you please review these options from the following link: https://usememos.com/docs/install/cloud

Vercel is mainly using to deploy static website which cannot run docker image.


OETH M-01

Add support to revert when the data feed is outdated.
This PR also adds support to fork test tooling to shorten all the governance actions, since when we advance time normally to comply to governance thresholds all the Oracles are already outdated

@DanielVF did you want to do another pass here maybe or we are ok to merging?

Will do another review


New Feature : Site Approval Process on Site Creation and Dashboards

Hi Paolo,
Is it possible to add the following features in PnP-Partner-Pack 3.0? This way it will become like a product and anyone can use without even customizing the code.

Configurable labels displayed in the forms (app icon, name, footermetc.,)
Site Approval Process before creating a subsite (primary and back approvers kind of)
Dashboard (My Tasks, Sites Requested, Approved, Rejected, Failed)

We are already using PnP-Partner-Pack as our bench mark :)

Thank you Paolo

Hello. Would it be possible to change the PnPProvisioningJobStatus field to add another status option, let's say "Waiting Approval"?
If so, we can allow an external workflow solution( Flow, Logic Apps, Webhooks, Nintex, ... to do whatever the specific implementation requires, and only when approved the status would change to Pending.
What do you think?

Hello guys. I am working on this one. should have an update and maybe a PR by mid next week

Hello.
So, I have something, but I think we are better off waiting for  #171 as the approval / post provisioning is branched from that branch.
code is https://github.com/camiloborges/PnP-Partner-Pack/tree/approval-postprocessing and there are several small changes to allow for easier integration.
@PaoloPia : Do you see problems changing PnPProvisioningStatus to a text field?
I haven't implemented it, but this would allow integration entirely from MS flow (which doesn't currently support updating drop down fields)

We closed this issue as it had not activity within last 180 days. This is a generic process we have decided to perform for issues, which have not been explicitly marked still to be "work in progress" based on tags. We are performing this cleaning to make sure that old issues that have already been solved (but not closed) or are no longer relevant are cleaned out and make the issues more manageable. If this issue still valid, we would ask you to open a new issue and follow the guidance in the issue template related on the recommended location. We do apologize any inconveniences this might cause. Please do remember that issues in the issue lists are also messages for others in the community, so you can also check if you can assist on any of them. “Sharing is caring!”


support destructuring for value specifications

Several times I've wanted to use destructuring when specifying values for existing declarations. It would be nice to support something like:
    String value1;
    String value2;
    [value1, value2] = ["x", "y"];

Use case 1: making specifications in different branches of a control structure, where currently you must:
    String value1;
    String value2;

    if (1==1) {
        value result = identity(["a", "b"]);
        value1 = result[0];
        value2 = result[0];
    }
    else {
        value result = identity(["c", "d"]);
        value1 = result[0];
        value2 = result[0];
    }

Use case 2: when you'd like to annotate the declarations:
    "documentation for value1"
    String value1;

    "documentation for value2"
    String value2;

    value result = identity(["a", "b"]);
    value1 = result[0];
    value2 = result[1];

oops... my first example has a bug. I guess that just helps make my point.

Should this be restricted to definitely unspecified values (as in your examples), or also be allowed for potentially specified but variable values (i. e., everywhere where value1 = ... is allowed)?

Variable values as well... Otherwise it seems kind of arbitrary...

A slightly cleaner alternative for case 1 is:
    [String, String] tmp;
    if (1==1) {
        tmp = identity(["a", "b"]);
    }
    else {
        tmp = identity(["c", "d"]);
    }
    value [value1, value2] = tmp;

As suggested by @jvasileff in discussion of #6446, we could even allow stuff like this:
String value1;
[value1, String value2] = ["x", "y"];

My comments about combined assignment/declaration here: https://github.com/ceylon/ceylon/issues/6446#issuecomment-300552123

I think I agree here with @xkr47. I would like to keep those two separate...


Fix double free of VirDomain

What this PR does / why we need it:
The PR fixes double free of VirDomain object in the case when a domain does not exists and it is created.
Special notes for your reviewer:
If a domain does not exists, l.virConn.LookupDomainByName returns a non-null err and the first time defer dom.Free() is called at
https://github.com/kubevirt/kubevirt/blob/6d745fc5dfa9b7e3d476cfde6ca38ddb8655c369/pkg/virt-launcher/virtwrap/manager.go#L757-L761
Then one more time after the if err != nil { ... } block:
https://github.com/kubevirt/kubevirt/blob/6d745fc5dfa9b7e3d476cfde6ca38ddb8655c369/pkg/virt-launcher/virtwrap/manager.go#L761-L768
Release note:

NONE

/retest

/retest

I'm surprised this doesn't cause a crash. How did you find this?

@davidvossel , I am surprised as well... We build and run Kubevirt with our own containers and in fact after updating to 0.40.0 virt-launcher started crashing with SIGSEGV every time a new VM was created. I tried 0.39.1 and the issue was also there. But somehow 0.38.1 was working fine. I am thinking if that might be because of some compiler flags or build options that are used for our base image and/or Kubevirt. Though for Kubevirt we don not set anything special... apart from building it with native Go instead of Bazel.

/retest

/retest

@davidvossel , I am surprised as well... We build and run Kubevirt with our own containers and in fact after updating to 0.40.0 virt-launcher started crashing with SIGSEGV every time a new VM was created. I tried 0.39.1 and the crash was also reproducible. But somehow 0.38.1 was working fine with this double-free. I am thinking if that might be because of some compiler flags or build options that are used for our base image and/or Kubevirt. Though for Kubevirt we don not set anything special... apart from building it with native Go instead of Bazel.

I think it was introduce here: https://github.com/kubevirt/kubevirt/pull/4685/files#diff-98b8339212e612cd92ce33649e492336892a3ed649f368b181aad9aa2854138cR1354

/cherry-pick release-0.40

/cherry-pick release-0.39

@vasiliy-ul  would you be able to backport this to release 0.39 and 0.40 branches by chance?

@davidvossel , sure


doesn't seem to work with -SNAPSHOT versions

Thanks for creating this provider, it's exactly what I was looking for to grab AWS Lambda functions published in a Maven repo and use them in a Terraform infrastructure!
I ran into an issue, however, when trying to use a -SNAPSHOT version. The provider fails to download the correct file. I think this has to do with the fact that Maven uses an XML manifest to map the -SNAPSHOT version to the actual time-stamped version number that can be downloaded via HTTP (see https://maven.apache.org/ref/3.2.5/maven-repository-metadata/repository-metadata.html).
To support -SNAPSHOT versions, I think the provider needs to first download and parse the maven-metadata.xml file and use the data therein to determine the correct path to the desired artifact.
I have no experience with Go, otherwise I'd take a stab at a PR. I might still give it a shot when I have some more time, but figured I'd file an issue in case you can do it easily.

Well, that was easier than I thought!

@evc-erik I've released v0.1.1, please try it.


Lookup attribute using nix-env

This should improve results especially with finding attributes. Sadly lookups with 'nix-env' are extremely slow. This gives us more accurate results though.

I thought there was something about adding a cache in nix 2.0.

I thought there was something about adding a cache in nix 2.0.

nix search does this but there's not an option to just search by 'name' which is what nix-env -qa can do.

I had lots of success with this method. It should be okay to merge if it looks okay to you.

Looks good! Thanks


[BUG] Variables panel display errors for used properties

Describe the bug
When opening a saved request from a collection, the variables panel displays errors for the properties as they weren't used in the query.
To Reproduce
Steps to reproduce the behavior:

Open a saved request in a collection that uses variables.
Open the variables panel
See error

Expected behavior
The variables panel shouldn't display errors for used properperties.
Screenshots

Desktop (please complete the following information):

OS: macOS Ventura 13.2.1
Browser: Chrome 110
Platform: desktop app
Version: 5.0.17

Additional context
Add any other context about the problem here.

Thanks for reporting this! I'd look into it as soon as I can.


Fixing warning to correctly output error string.

@jhowardmsft
I had incorrectly used err.Error instead of either err or err.Error(), so the message wasn't showing up properly.
Signed-off-by: Stefan J. Wernli<EMAIL_ADDRESS>

LGTM

LGTM

LGTM


SVG Weblink

[ x] I agree to follow the Code of Conduct that this project adheres to.
[x ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I created a svg file with a web link using draw.io.
The web link for the SVG file can be opened with a mouse click.
When I import the SVG file into Dokuwiki, the web link is recognized, but it only works with a right mouse button click and the Open link in new window command.
Is it possible that this can also be opened with a mouse click?
Thanks for the help.
Describe the solution you'd like
The SVG Weblink should be opened with a mouse click.
Describe alternatives you've considered
non
Additional context
non

Please add a link to the Dokuwiki page with the diagram.

https://dimondo.synology.me/dokuwiki/bruchawiki/doku.php/Brucha Wiki
BN:test
PW:test

This is a file: link which is blocked by the browser for security reasons (see https://www.technewstoday.com/not-allowed-to-load-local-resource/).

Is it possible to fix this for every user who log in?

This is a browser limitation, you'd have to ask the browser vendor.

Outside of dokuwiki it works without problems.


How to change "forecasts every n hours" interval?

Currently the forcasts are every 12h. OWM 5 day forecast includes weather data every 3 hours.
How can i change the interval to 6 or 3 hours? I couldn't find anything nether in the scatch nor library.
Regards Joerg

@Burn-In  Would you share your code please? I like the idea of updates on the hour<EMAIL_ADDRESS>thanks


Exec tachikoma update<PHONE_NUMBER>3331

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage remained the same at 67.647% when pulling 88628c09e8f3ed0622c95b5ead795a4a04b8f61f on pazjacket:tachikoma/update-20170604163331 into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

Coverage remained the same at 67.647% when pulling 88628c09e8f3ed0622c95b5ead795a4a04b8f61f on pazjacket:tachikoma/update-20170604163331 into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.


[EDA] EDA Unit Tests Should Use the Chosen Administrative Account Record Type

Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Unit tests in a number of classes currently use logic to retrieve the default value for the Administrative Account Record Type, which does not respect the Administrative Account Record Type specified in EDA Settings.

What is the expected behavior?
Unit tests are updated to retrieve the current value for the Administrative Account Record Type specified by EDA Settings.

What is the motivation / use case for changing the behavior?
The Administrative Account Record Type selected in the Accounts and Contacts tab in EDA Settings is not respected, which may result in unexpected test failures.

Acceptance Criteria

Given: I am a System Administrator
When: I choose which record type counts as an Administrative Account in EDA Settings
Then: I can use EDA with my own org’s terminology and with other packages that require record types on Account

Tracking W-7930276


Update semver for dependency on core-client to be v1.2.1

To make sure we get all the goodness of the latest released version.

Is there any fix that we absolutely need from version 1.2.1? Or is this best effort to ensure we are on latest?

@ramya-rao-a I like to think of all fixes done so far in https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-client/CHANGELOG.md as needed ones. Many were customer reported.

If it is only the matter of getting bug fixes, then we don't really need to update the version because users will get the latest when they install our packages. The cases where we do update the version of core packages is when there is a feature in the newer version that we need to use.
For example, in the case of core-rest-pipeline, Key Vault package needed the new CAE feature and therefore had to update its dependency on core-rest-pipeline. Then, to keep rush happy, we updated the dependency in all other places too.
Unless there is a feature in the newer versions of the core-client that the consuming package relies on, we do not need to make such updates

We had a discussion on the team channel and it seems like it is hard to decide on which approach provides the better customer experience, so I am fine with leaving things as is.


python311Packages.opensensemap-api: 0.3.1 -> 0.3.2

Changelog: https://github.com/home-assistant-ecosystem/python-opensensemap-api/releases/tag/0.3.2
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

4 packages built:

python310Packages.opensensemap-api
python310Packages.opensensemap-api.dist
python311Packages.opensensemap-api
python311Packages.opensensemap-api.dist


End of support for Windows 7.

I do not have a Windows 7 environment, so I cannot confirm that it works on Windows 7.
Therefore, I am considering ending support for Windows 7.

#1

https://github.com/typeling1578/MaterialFox-Plus/commit/4af6d88853bebe10647e25df9251d5fdb731618a

why not try in virtual machine?

My PC does not have enough capacity to run Windows 7 in a virtual machine.
Also, please do not continue to use an OS for which security updates are no longer being distributed.


Loading previous state...

Hello，This happens in experiments：
Using good policy maddpg and adv policy maddpg
Loading previous state...
What is the meaning？

that's literally what it means. you have to annotate the part of code for loading, then you can train your model

tensorflow.python.framework.errors_impl.NotFoundError: Unsuccessful TensorSliceReader constructor: Failed to find any matching files for
[[Node: save/RestoreV2 = RestoreV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, ..., DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/RestoreV2/tensor_names, save/RestoreV2/shape_and_slices)]]
NotFoundError (see above for traceback): Unsuccessful TensorSliceReader constructor: Failed to find any matching files for
[[Node: save/RestoreV2 = RestoreV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, ..., DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/RestoreV2/tensor_names, save/RestoreV2/shape_and_slices)]]

这对我有用。


Feat landing page

WIP

just one overall comment, can you have the svg icons in src/ui/paylink/icons to keep the file clean

Sure
On Thu, May 30, 2024 at 12:48 PM @Jonath-z @.***> wrote:

just one overall comment, can you have the svg icons in
src/ui/paylink/icons to keep the file clean
—
Reply to this email directly, view it on GitHub
https://github.com/Olame-protocol/PayLink/pull/1#issuecomment-2139182085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYCTR7QKF2YXXCM7M4B7GDZE3YWXAVCNFSM6AAAAABIPIOSO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGE4DEMBYGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


A customer reported an issue of a NPE when initializing secret masker

Stack trace of NPE was:
[2019-11-27 01:47:59Z ERR  Program] System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VisualStudio.Services.Agent.Worker.Worker.InitializeSecretMasker(AgentJobRequestMessage message)
at Microsoft.VisualStudio.Services.Agent.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
at Microsoft.VisualStudio.Services.Agent.Worker.Program.MainAsync(IHostContext context, String[] args)

This is the only change to this method in a long time. I don't understand how a variable can have a value of null, but that may be a different problem for a different day.


Fix issues with building on Linux

Currently there are a lot of problems with CMakeLists that prevents Linux users from building the library. Majority of issues stem from linker paths unspecified for Linux based machine.
There's also problem with building Python binding in Linux since there are no implementation for Linux yet.

6f9c90b4e7fb4f000ec5e48e935c9990e399aef3 allows users to build on Linux. However, problem with building Python binding is not yet fixed. This issue stems from wrapper/CMakeList.txt, line 217 from 220 which is only compatible (probably) for Mac OSX.
6f9c90b4e7fb4f000ec5e48e935c9990e399aef3 is tested on Ubuntu 16.04.1 64 bit only. I think I covered 32 bit as well but if someone could test it out it will be great. The only additional package to install is raptor I think (libcurl and libxslt comes with it?)
To do so, run
sudo apt-get install libraptor2-dev

@bbartley : Has Python 3 binding tested?

I've sucssfully built and tested wrappers for python 2.7 and 3.5 but only on Mac OS X so far
Sent from my iPhone

On Oct 19, 2016, at 6:19 PM, Kiri Choi<EMAIL_ADDRESS>wrote:
6f9c90b allows users to build on Linux. However, problem with building Python binding is not yet fixed. This issue stems from wrapper/CMakeList.txt, line 217 from 220 which is only compatible (probably) for Mac OSX.
6f9c90b is tested on Ubuntu 16.04.1 64 bit only. I think I covered 32 bit as well but if someone could test it out it will be great. The only additional package to install is raptor I think (libcurl and libxslt comes with it?)
To do so, run
sudo apt-get install libraptor2-dev
@bbartley : Has Python 3 binding tested?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

f646dd3d150d79a0d258322a4bb442c82ccf0b7d Fixed issues with building Python 2 bindings on 64 bit Linux, but this is not fully tested yet. Still needs to test 32 bit Linux and Python 3 bindings.


WIP: replace moment for date-time filter

:warning: This is Work in Progress

[x] Use date-fns in filter functions
[ ] Use date-fns in entity sub generator
[ ] Import all selected locales/languages selected on generation We don't need them as we do not use any localized functions (yet). Even with moment we do not use anything that requires locaes
[ ] Add needles to add new locales

closes #94
updates #129

@deepu105 Is it possible to overwrite or modify the function generateEntityClientFields in https://github.com/jhipster/generator-jhipster/blob/e5552a6fcf374b6a5560c6089b2c4a2cb8ea28e1/generators/generator-base-private.js#L983? As we don't use moment I need to overwrite tsType for date/time fields.

@atomfrede I think it should be fine. I would suggest changing method signature like this
generateEntityClientFields(pkType, fields, relationships, dto, customDateType = 'Moment') {
...
}

so that you could use the method with your own date type when calling from Vue and in current usages it will remain the same. WDYT?

Yes that's looks perfect. Will do a PR to the main generator.

Before the build can pass we need to merge https://github.com/jhipster/generator-jhipster/pull/8977


Support for sinon sandboxes

Seems that if creating mock through sandbox, the chainable is not assigned.
var sandbox = sinon.sandbox.create();
var Mock = sandbox.mock(MyMongooseObject);
Mock.expect('findOne').chain('populate');

This example fails with error:
TypeError: Mock.expects(...).chain is not a function
Using sandbox is more convenient as you can easily just create as many mocks you like and then do sandbox.restore which will restore all mocks rather than restoring each mock separately.

@jniemin it should work... actually I always use sandbox.
Could you post a complete example?

Here is complete the example @gaguirre. I'm using Mocha 3.2.0, sinon 2.1.0, and sinon-mongoose 1.3.0
roles.js
"use strict";

const mongoose = require('mongoose');
const Schema   = mongoose.Schema;

const ROLES_SCHEMA = new Schema({
  name:{
    type:String
  }
},{
  timestamps: {
    createdAt: 'created_at',
    updatedAt: 'updated_at'
  }
});

const Role = mongoose.model('Role', ROLES_SCHEMA);

module.exports = Role;

roles.spec.js
"use strict";

const Role = require('./roles');
const sinon = require('sinon');
require('sinon-mongoose');
const sinonSandbox = sinon.sandbox;

describe("sinon-mongoose sandbox", function(){
  afterEach(function() {
    sinonSandbox.restore();
  });

  it("Chaining should work when using sinon sandbox", function(){
    // throws error "TypeError: RoleMock.expects(...).chain is not a function"
    const RoleMock = sinonSandbox.mock(Role);
    RoleMock.expects('findOne').chain('populate').resolves({});
  });

  it("Chaining works when using mock not created by sandbox", function(){
    const RoleMock = sinon.mock(Role);
    RoleMock.expects('findOne').chain('populate').resolves({});
    RoleMock.restore();
  })

});

You're missing the sandbox creation. It should be
const sinonSandbox = sinon.sandbox.create()

Tell me if it works!

Ah, copy paste error, when I removed some of the business names etc. So sandbox.create() is in the actual test code. So still no luck

Weird. There is a test using sandbox (https://github.com/underscopeio/sinon-mongoose/blob/master/test/index.js#L116).
Check it out, it may be helpful.

Seems that if I ran sinon-mongoose tests from master there it works. I wonder could it be sinon-mongoose using older versions of sinon (1.17.7) and mocha (2.5.3)? I'm running on my own project sinon 2.1.0 and mocha 3.2.0.

Maybe... Could you try upgrading sinon for the tests and see if it fails.
Then probably it needs a fix for newer sinon versions.
Thanks @jniemin!

It definitely was then new version of Sinon that made the tests break. I created PR to add support for Sinon 2.

Actual implementation was not totally proper. There is now new PR to fix that


Extension host terminated unexpectedly.

 You can find them via F1 > Developer: Show Logs ... > Extension Host

@tirthaguha Can you please share with us the extension host logs? You can find them via F1 > Developer: Show Logs ... > Extension Host

Here you go
[2020-04-06 10:01:23.783] [exthost] [info] extension host started
[2020-04-06 10:01:24.020] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"extensionId":{"value":"vscode.typescript-language-features","_lower":"vscode.typescript-language-features"},"activationEvent":"onLanguage:javascript"}
[2020-04-06 10:01:24.021] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/typescript-language-features/dist/extension
[2020-04-06 10:01:24.065] [exthost] [info] ExtensionService#_doActivateExtension christian-kohler.npm-intellisense {"startup":false,"extensionId":{"value":"christian-kohler.npm-intellisense","_lower":"christian-kohler.npm-intellisense"},"activationEvent":"onLanguage:javascript"}
[2020-04-06 10:01:24.065] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/christian-kohler.npm-intellisense-1.3.0/out/src/extension
[2020-04-06 10:01:24.132] [exthost] [info] ExtensionService#_doActivateExtension wix.vscode-import-cost {"startup":false,"extensionId":{"value":"wix.vscode-import-cost","_lower":"wix.vscode-import-cost"},"activationEvent":"onLanguage:javascript"}
[2020-04-06 10:01:24.132] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/wix.vscode-import-cost-2.12.0/out/src/extension
[2020-04-06 10:01:24.706] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-04-06 10:01:24.706] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-04-06 10:01:24.715] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-04-06 10:01:24.715] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/emmet/dist/extension
[2020-04-06 10:01:24.761] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":"*"}
[2020-04-06 10:01:24.762] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/git/dist/main
[2020-04-06 10:01:24.878] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":true,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"*"}
[2020-04-06 10:01:24.878] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/github-authentication/dist/extension.js
[2020-04-06 10:01:24.888] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-04-06 10:01:24.901] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/extension
[2020-04-06 10:01:24.912] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-04-06 10:01:24.912] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/search-result/dist/extension.js
[2020-04-06 10:01:24.915] [exthost] [info] ExtensionService#_doActivateExtension vscode.vscode-account {"startup":true,"extensionId":{"value":"vscode.vscode-account","_lower":"vscode.vscode-account"},"activationEvent":"*"}
[2020-04-06 10:01:24.915] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/vscode-account/dist/extension.js
[2020-04-06 10:01:24.924] [exthost] [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint {"startup":true,"extensionId":{"value":"dbaeumer.vscode-eslint","_lower":"dbaeumer.vscode-eslint"},"activationEvent":"*"}
[2020-04-06 10:01:24.924] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/dbaeumer.vscode-eslint-2.1.1/client/out/extension
[2020-04-06 10:01:24.938] [exthost] [info] ExtensionService#_doActivateExtension eamodio.gitlens {"startup":true,"extensionId":{"value":"eamodio.gitlens","_lower":"eamodio.gitlens"},"activationEvent":"*"}
[2020-04-06 10:01:24.938] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/eamodio.gitlens-10.2.1/dist/extension
[2020-04-06 10:01:25.056] [exthost] [info] ExtensionService#_doActivateExtension EditorConfig.EditorConfig {"startup":true,"extensionId":{"value":"EditorConfig.EditorConfig","_lower":"editorconfig.editorconfig"},"activationEvent":"*"}
[2020-04-06 10:01:25.056] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/editorconfig.editorconfig-0.14.4/out/editorConfigMain.js
[2020-04-06 10:01:25.139] [exthost] [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker {"startup":true,"extensionId":{"value":"streetsidesoftware.code-spell-checker","_lower":"streetsidesoftware.code-spell-checker"},"activationEvent":"*"}
[2020-04-06 10:01:25.140] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/{USERNAME}/.vscode/extensions/streetsidesoftware.code-spell-checker-1.8.0/dist/extension

@tirthaguha Your issue is contradictory to the log you have attached. In the issue description, you state that "Extensions: none" but in the log there are clearly many user installed extensions activating.
Can you please try to disable all user installed extensions?

Hi,
I have uninstalled all extensions, and still get this error. here are the logs.
[2020-04-16 17:32:34.279] [exthost] [info] extension host started
[2020-04-16 17:32:34.324] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-04-16 17:32:34.325] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-04-16 17:32:34.343] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-04-16 17:32:34.343] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/emmet/dist/extension
[2020-04-16 17:32:34.376] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":"*"}
[2020-04-16 17:32:34.376] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/git/dist/main
[2020-04-16 17:32:34.463] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":true,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"*"}
[2020-04-16 17:32:34.463] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/github-authentication/dist/extension.js
[2020-04-16 17:32:34.469] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-04-16 17:32:34.470] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/extension
[2020-04-16 17:32:34.481] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-04-16 17:32:34.481] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/search-result/dist/extension.js
[2020-04-16 17:32:34.484] [exthost] [info] ExtensionService#_doActivateExtension vscode.vscode-account {"startup":true,"extensionId":{"value":"vscode.vscode-account","_lower":"vscode.vscode-account"},"activationEvent":"*"}
[2020-04-16 17:32:34.484] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/vscode-account/dist/extension.js
[2020-04-16 17:32:34.508] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm {"startup":true,"extensionId":{"value":"vscode.npm","_lower":"vscode.npm"},"activationEvent":"workspaceContains:package.json"}
[2020-04-16 17:32:34.508] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/npm/dist/main
[2020-04-16 17:32:34.612] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.node-debug2 {"startup":false,"extensionId":{"value":"ms-vscode.node-debug","_lower":"ms-vscode.node-debug"},"activationEvent":"onCommand:extension.node-debug.startAutoAttach"}
[2020-04-16 17:32:34.613] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/ms-vscode.node-debug2/out/src/extension
[2020-04-16 17:32:34.623] [exthost] [info] eager extensions activated
[2020-04-16 17:32:34.633] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.node-debug {"startup":false,"extensionId":{"value":"ms-vscode.node-debug","_lower":"ms-vscode.node-debug"},"activationEvent":"onCommand:extension.node-debug.startAutoAttach"}
[2020-04-16 17:32:34.633] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/ms-vscode.node-debug/dist/extension.js

@tirthaguha Thank you for following up. Unfortunately there is nothing out of the ordinary in your log, the built-in extensions are activated and there is no clue as to what might bring the extension host process down.
Is it perhaps something to do with the folder you open? Can you please try opening a new window or a new folder without any files inside of it? Does the extension host crash in that case too?

I have done some experiments around this actually. I've tried this save version in different directories and different OS, like Ubuntu 18/CentOS7/Different-Win10 and it apparently happens in one particular Win10 device only.
There is some level of access control present on this particular device where this keeps occurring. This device is a work issued system, and disk r/w and elevated rights are given on this device conditionally. Could that be causing it. If so, is there anything like any process that I can whitelisted?

Thanks for investigating this further. VS Code does not need administrator privileges to execute. Have you tried downloading the zip variant of VS Code, unpackage it to some folder, and running from there?
You can also try the portable mode explained here -- https://code.visualstudio.com/docs/editor/portable#_enable-portable-mode
Perhaps the process is killed by some software installed on the machine, I have to say I don't quite know what could be doing that.


[Added] Added 10 new quotes

Added 10 new quotes to the quotes.js file

A star ⭐in the repository would be appreciable 🙂


docker daemon (network) problem

Hi,
We are college students in Korea.
We decided to build a private block-chain network based on the embedded system with this graduation work, and your repository was very helpful.
We read the readme you uploaded and followed it, but there was a problem.

If we run "docker swarm init" on the master node, we can see that the network status changes as shown in the figure.
As with other nodes, entering the "docker swarm join - token SWMTKN-1-xxxxxxxx 192.168.1.xxx:2377" command changes the network status.
However, if you wait for a while, it will be ready as below.

However, on the master node, type "docker network create -d overlay --attachable hyperledger-fabric" and type "docker stack deploy --compose-file docker-compose-cli.yaml Hyperprov && docker ps" It shows how network status fluctuates in blocking and forward state.
And if you type "docker node ls", no container is up, and the status is down.
What's the problem?
I am waiting for your answer. Thank you.

Hi,
I have seen these messages about entering promiscuous mode, blocking/forwarding/disabled state previously. They did in my experience not limit or prevent the system from functioning as far as i'm aware.
But your containers not starting up is weird. What does it say if you run docker stack ps Hyperprov --no-trunc on main node?
Also check these things as they may prevent your containers from starting correctly:

Is the repository placed in "/data/Hyperprov" or as otherwise specified in docker-compose-cli.yaml on all nodes?
Does the "node.hostname" variables in docker-compose-cli.yaml match your node names when you run docker node ls on swarm master?
Is your Docker, Docker-compose and Golang versions correct? (18.09.1, 1.22.0 and 1.11.1 for HLF1.4 i think)

Thanks for reply.
But blocking/forwarding/disabled state continously on present. I think it is docker problem. How did you fix the problem?

I'm not sure, but if it does not affect functionality it's not too bad.
I see someone here experienced something similar due to a restarting Docker container.
Does it only happen on swarm master? Maybe it's the tools or orderer containers automatically restarting due to some error.

Thanks for your time. I am trying to solve it based on what you have helped me with. Finally, I would like to ask you one more question. I'm working on not only 64-bit architecture but also 32-bit os tutorial. (Your ./hyperledger-pi-composer reposiotory) I succeeded in running the chain code on the 32bit OS using only Raspberry Pie 4. However, during the tutorial, I run ca-server from the ./client folder and get a network error. The docker image in the docker-compose-cli.yaml file in the ./hyperledger-pi-composer folder is 32bit. However, the docker image in the docker-compose.yaml file in ca-server in the ./fabric-ca folder is amd64bit. Is it possible to install ca-server on Raspberry Pi 32bit debian OS when referring to this? Or is CA server running only on Ubuntu 1604 64bit OS?

During my work with this i used a regular desktop machine as CA, and did not need fabric-ca images for ARM.
However, it should be absolutely fine running CA on Raspberry Pi but you would need the fabric-ca docker image built for armv7l for HLFv1.0 on 32 bit (or arm64 on HLFv1.4 for 64-bit project). For this you can search dockerhub or build your own images from the fabric-ca repository. For the latter you may find some helpful information in this document.


inveniogc: missing recurse parameter for dir deletions

The following rules in inveniogc.py miss out the fact that they actually find a directory and not a file. Thus they have to use -rf for deletion and not only -f:

websubmit_icon_creator_*
websubmit_file_stamper_*

This should affect maint-1.1 and maint-1.2 and can amount to quite some space used depending on the input files.

Closed by #3716.


Can't resize the window opened by vscode-web-test

from https://github.com/microsoft/vscode-internalbacklog/issues/2414
This is just a little strange, maybe there is a reason for it, but the vscode window does not adapt to resizing the browser window

Just my observation... but, if:

the call to await page.setViewportSize({ width, height }) is removed (src/index.ts#222), and
the viewport option is set to null when calling browser.newContext(): (src/index.ts#199),

const context = await browser.newContext({
  viewport: null
});

The VS Code window is created using the entire screen as viewport, and it does adapt to resizing the browser window.
(note: only tested on Chromium 94.0.4595.0)

@IronGeek Thanks for the tip!


Delivery API no longer compatible with create-react-app?

Since the upgrade of Parse5 from v3 to v5 - https://github.com/Enngage/kentico-cloud-js/commit/47417f1b502aa2e4a610f9511071e27dc973238a
create-react-app/webpack is no longer able to create a build when running yarn build:
yarn run v1.7.0
$ react-scripts build
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

        ./node_modules/parse5/lib/utils/mixin.js:3

Read more here: http://bit.ly/2tRViJ9

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'm assuming this is expected since the package is now using ES6 rather than ES5?
This also happens in the sample react application: https://github.com/Kentico/cloud-sample-app-react

You are right.. seems like the parse5 does not publish code in ES5. The workaround I was able to get away with is to use browser umd bundle as the main entry point of delivery js sdk. Basically I went to node_modules/kentico-cloud-delivery/package.json and used this as main:
 "main": "./_bundles/kentico-cloud-delivery-sdk.browser.umd.min.js"
React build works fine with this. Do you know if there is a better way of aliasing this? Or if react has some sort of build configuration option for this?

Imho, this sounds like something that React should address. Also, I found an issue in Parse5 library where the maintainer said that he wants to target modern code rather than ancient ES5 :-)
I would still like to have a better solution for handling this other than what I mentioned above so any comments are welcomed.

Yeah I agree with you - it should be React that resolves it, but it does look like they're recommending putting code on npm as ES5 for at least the next couple years.
On the other hand, they are actively working on the 'next' release of react-scripts, currently "2.0.0-next.a671462c".  I've just tested updating my test site to use it, and it seems to be building production code with no problems.  I haven't given it a thorough test yet, so not sure how stable it is - but it does look like they've recently updated with security fixes.  Looks like it's still 68% way through development, so a while before full release yet.

@Enngage @liamgold  is this something that consumers of this SDK that use it in React projects will regularly be running into? If yes, can it be easily worked around?

@petrsvihlik, yes, it causes build to fail with 1.x.y react scripts because react tries to minify it on its own. It would work fine if react enabled developers to disable minification for selected 3rd party libraries. I don't think I'll be able to address this in SDK myself. I would have to take Parse5 dependency, fix it on my own and use that instead.

I guess another alternative would be if it's reasonable to just leave the SDK as it is, and just add a warning/disclaimer that it should only be used with react-scripts 2.x.y.
At the same time upgrade the react sample application to use 2.x.y alpha version of react-scripts.

@liamgold yeah, I would go down this road as well. I'll likely prepare some sort of FAQ / Common issues page and try to address it there for the time being. Thanks you for creating this issue and bringing this to our attention :-)

@Enngage please do.
wasn't the upgrade to ES6 premature? didn't this change effectively prevent people using react 1.x from building their sites with KC JS SDK?

ok, i get it now, thanks :)

Well, I'll be merging these branches (likely Today) so yeah.. There are quite a few changes in the separation itself so I will create a new branch for CM api only once the master is updated and potentially the v5 released.

ok, thx


Contiv/k8s -- upstream contrib/ansible repo changes.

The ansible for bringing up k8s cluster with contiv networking is in a private fork right now. Need to upstream this to the public repo.

part of k8s contrib.


artisan queue restart does not restart the queue

Laravel Version: 5.4.36
PHP Version: 7.0.20
Database Driver & Version: MySQL 5.6.35

Description:
We are using a queue worker to convert pdf files to a image which normally runs fine, but the moment we deploy our project and we need to restart the queue worker it doesn't work.
it does not restart the queue worker which means our queue is not being processed anymore.
We have looked through some of the issue's on github but we did not find any solution.
We managed to hardkill the queue worker process with the following command : kill -9 {PID ID} but this isn't iddeal.
Steps To Reproduce:

Run one of the following commands : ps aux | grep queue:work (mac) or ps faux | grep queue:work (linux)
Make sure a queue worker is running : artisan queue:work --deamon.
Open a new terminal window and run the following command artisan queue:restart.
Check if the queue process is still active with one of the commands at ( point number 1 ).

Can't replicate, calling artisan queue:restart kills the process if no jobs are running, if a job is running the process won't die unless the worker finishes whatever jobs its working on.

Your issue is unclear. Are you reporting that it doesn't start up again, or that it doesn't stop at all?
The name of queue:restart does indeed suggest an actual restart, but that isn't what it does. It only stops processing jobs, and expect a process manager like supervisor or systemd to start it again.
Internally queue:restart sets a flag in the cache that tells all workers that sees it to restart. This means that your workers need to use the cache that the artisan command is using. It also means that it will restart all workers that uses the same cache, in case of a shared redis/memcached setup and several workers.
The documentation under Queues > Supervisor Configuration has an example setup.

Given:

We managed to hardkill the queue worker process with the following command : kill -9 {PID ID} but this isn't iddeal.

I assumed the issue is that it doesn't kill the worker process, and yes it won't if the process is busy.

@wotta try changing the cache driver to redis


Please provide toolchain with c++ RTTI enabled (IDFGH-1180)

I would like to request that you please provide a version of the toolchain that has C++ RTTI enabled by default. RTTI is an essential part of most C++ development and having to build a custom toolchain is cumbersome. Thank you!

I wouldn't say that RTTI is essential to most of C++ development, nevertheless, ESP-IDF supports it, just configure your compiler.
Create a component.mk file in your main directory and in all components (if you use them) are with the contents:
CPPFLAGS += -frtti

Checked with:
class Person
  {
    public:
       virtual ~Person() {}
  };

 class Employee : public Person
 {
 };

#include <esp_log.h>
#include <typeinfo>
extern "C" void app_main(void) {
   Person person;
   Employee employee;
   Person* ptr = &employee;
   Person& ref = employee;
   // The string returned by typeid::name is implementation-defined
   ESP_LOGI("RTTI", "%s", typeid(person).name());   // Person (statically known at compile-time)
   ESP_LOGI("RTTI", "%s", typeid(employee).name()); // Employee (statically known at compile-time)
   ESP_LOGI("RTTI", "%s", typeid(ptr).name());      // Person* (statically known at compile-time)
   ESP_LOGI("RTTI", "%s", typeid(*ptr).name());     // Employee (looked up dynamically at run-time because it is the dereference of a pointer to a polymorphic class)
   ESP_LOGI("RTTI", "%s", typeid(ref).name());      // Employee (references can also be polymorphic)
}

The compiler supports it, yes, but the standard libraries included in the pre-built toolchain do not.

And, actually, it appears the cmake build system does not, in fact, allow me to specify -frtti... this entry in build.cmake appears to not be overridable:
list(APPEND cxx_compile_options "-std=gnu++11"
                                "-fno-rtti")

Closing this as a duplicate of an older issue, https://github.com/espressif/esp-idf/issues/1684. To receive further updates, please follow the link and click the "Subscribe" button. Thanks.


How to make so bot will connect with different ip?

Title say it all

Title doesn't really say much... What do you mean different IP? If you want the server to think you're connecting from a different IP than your real one, you'll need to use a proxy.

Yes, I mean so the bot will connect using a different ip than the real one. Do you know any tutorial for using proxy and stuff?

It always said connection timed out for no reason. This is my code to create the proxy
public static Proxy connectToVpn() { 		SocketAddress socket = new InetSocketAddress("<IP_ADDRESS>", 8080); 		return new Proxy(Proxy.Type.SOCKS, socket); 	}

It says timed out because the proxy you are using is slow

Really?. Can I know any fast proxy?
I've tried 10 or maybe 20 proxy on this website https://www.socks-proxy.net ,  but none of them seems to be working


Create tables in the specified schema to avoid moving the tables afterwards

This solves #18

@musically-ut I have made some changes so that the schema is considered when creating the tables. Thus, it is not necessary to have the moveTableToSchema function.

The changes look good to me. Just tested the default execution from the README to ensure that we don't need to bump up the psychopg2 versions.
I'll update the Acknowledgements section of the README. :)


CmiCheckAffinity causes hang with UCX build on Summit

On Summit, CmiCheckAffinity in _initCharm routine (src/ck-core/init.C) causes a hang when run on two nodes.
Observed with the UCX and PAMILRTS builds.
Runs fine when these routines are commented out.
Charm++ with UCX machine layer built with:
./build charm++ ucx-linux-ppc64le smp openpmix -j --with-production --basedir=$HOME/pmix-3.1.5/install --basedir=$HOME/ucx-1.11.1/install
Test program (1darray/hello) run with:
jsrun -n2 -a1 -c2 -K1 -r1 ./hello +ppn 1 +pemap L0 +commap L1

Still hangs on Summit.


I can't make it work with my existing configurations of angular-4 app!

Hi,
I'm trying to use this component in my app...
I had angular 4.2.4 , cli 1.4.9 and typescript 2.3.3, and was getting:

Tried upgrading to angular 4.4.6 with same cli 1.4.9 and typescript 2.5.3 but it didn't help. and now I'm getting:

this is my pakcage.json
Can you please advice...

This issue is displayed when you have two version of angular. My package require angular ^5.2.x., so you have to upgrade your application package.json.


Error detected while processing function 7_nvim_cb[1]..7_job_cb[4]..7_job_out_cb[10]..7_log[2]..7_logpos:

Explain the problem here ...
I always got errors like this:
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E727: Start past end
Press ENTER or type command to continue
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E714: List required
Press ENTER or type command to continue
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E727: Start past end
Press ENTER or type command to continue
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E714: List required
Press ENTER or type command to continue
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E727: Start past end
Press ENTER or type command to continue
Error detected while processing function <SNR>7_nvim_cb[1]..<SNR>7_job_cb[4]..<SNR>7_job_out_cb[10]..<SNR>7_log[2]..<SNR>7_logpos:
line    1:
E714: List required
Press ENTER or type command to continue

NVIM v0.3.8
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/neovim-Bljd1N/neovim-0.3.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=1 -DDISABLE_LOG
 -Wdate-time -D_FORTIFY_SOURCE=1 -Wconversion -O2 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack
-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/build/neovim-Bljd1N/neovim
-0.3.8/build/config -I/build/neovim-Bljd1N/neovim-0.3.8/src -I/usr/include -I/build/neovim-Bljd1N/neovim-0.3.8/build/src/nvim/auto -I/build/neovim-Bljd1N/neovim-0.3.8/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv -jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Type:

[x] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[x] Linux
[ ] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[x] Neovim

Do you have a minimal vimrc to replicate this?

Hello @janlazo Yes, it's here.
https://github.com/GopherJ/cfg/blob/master/vim/.vimrc

Does the problem happen (or become something else) after the latest change?

@janlazo  I cannot see the error messages anymore but there is still a problem I think, because I cannot see the downloading process.

The strange thing here is that after running :PlugInstall it shows me a list of plugins and two plugs haven't been installed, then this list disappear and after some minutes it doesn't come back but I can see again Installing plugins (64/65)
These two plugins are Youcompleteme and langugeclient_neovim, they are heavy, but a few days ago I can install them correctly with vim-plug, while installing ycm it jumps out of vim and show me it's running git submodule update....etc
but now I cannot see these messages anymore, after running :PlugInstall it gave me a list and then this list disappears for a while and then it comes back with a message Installing Plugins but I don't know what happened and which plugins are installing.

Ok. I'll investigate. Thanks for the response.

Hello, @janlazo any news on this?

No news. I haven't encountered it myself yet.

69c69
< syntax enable
---
> " syntax enable
196,197c196,197
< Plug 'Valloric/YouCompleteMe'
< Plug 'autozimu/LanguageClient-neovim', { 'branch': 'next', 'do': 'bash install.sh' }
---
> " Plug 'Valloric/YouCompleteMe'
> " Plug 'autozimu/LanguageClient-neovim', { 'branch': 'next', 'do': 'bash install.sh' }
205c205
< Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': './install --all' }
---
> " Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': './install --all' }
218c218
< Plug 'iamcco/markdown-preview.nvim', { 'do': 'cd app & yarn install' }
---
> " Plug 'iamcco/markdown-preview.nvim', { 'do': 'cd app & yarn install' }
234c234
< autocmd VimEnter * if argc() == 0 && !exists("s:std_in") | NERDTree | endif
---
> " autocmd VimEnter * if argc() == 0 && !exists("s:std_in") | NERDTree | endif
301,302c301,302
< filetype plugin indent on
< autocmd Filetype * AnyFoldActivate
---
> " filetype plugin indent on
> " autocmd Filetype * AnyFoldActivate
356c356
< autocmd FileType * call tagbar#autoopen(0)
---
> " autocmd FileType * call tagbar#autoopen(0)

If you apply the following changes, what happens?

@janlazo finally It seems if I comment all things related to anyfold then the errors went away. Thanks

https://github.com/pseewald/vim-anyfold/issues/32


Bump sentry-core to 0.29

Checklist

[x] I have read the Contributor Guide
[x] I have read and agree to the Code of Conduct
[x] I have added a description of my changes and why I'd like them included in the section below
[x] (thought up myself) I have tested the changes :wink:

Description of Changes
Everyone wants to use the latest version of Sentry :tada:

@Jake-Shadle :eyes: - force-pushed to see if the CI is still happy with this, we'd love to upgrade our Sentry :)


Google geocoder

This PR includes:

Add google geocoder logic
Refactored the python library to change to a services mode due we are going to start including more services like routing

retest this please

retest this please

retest this please

@rafatower check this out

retest this please

In general ok, my comments are just small details
Sorry about commenting on generated files. Small suggestion: add
--DO NOT MODIFY THIS FILE, IT IS GENERATED AUTOMATICALLY FROM SOURCES

to the header template file.

You are talking about the cdb_geocoder_server--x.y.z.sql files aren't you?

I was talking about adding that line to these files:
https://github.com/CartoDB/geocoder-api/blob/master/server/extension/sql/0.1.0/00_header.sql
https://github.com/CartoDB/geocoder-api/blob/master/client/sql/0.1.0/00_header.sql

Are you sure? That files are not automatically generated...

retest this please


get a json format going

make a example json for what our database info would look like, fill it with sample code

50


OpenCV Android SDK redownloading

Currently OpenCV Android SDK is downloaded into a CMake build folder. This causes it to be downloaded for each Android ABI separately, which currently results into four downloads instead of one.

I see two ways to fix this:

Create a cache variable in CMake for OpenCV install dir, then a common directory (somewhere inside build directories) could be specified though Gradle.
Install OpenCV in user's home directory.

The first way seems better to me as it dosn't create files outside of a build directory.

Now OpenCV is build from sources


Add "response_format" to allow for json_object responses in chat completions

OpenAI recently added a new response_format property to the request body for chat completions requests endpoint. See here: https://platform.openai.com/docs/api-reference/chat/create#chat-create-response_format
This allows "JSON mode" for models that allow it.
I've not looked at all the code in detail so it may not work, but is hopefully a starting point.


⚠ GitLab Server has degraded performance

In c0ebe6e, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6847 ms

Resolved: GitLab Server performance has improved in 5097a6d.


Add "Donate" button to project description

I'd like to see a "Donate" button here in this awesome project and surely would like to donate to keep development going.

Thanks for offering to donate @solus-hq!
As you found, an issue for this already exists under #243 so I'll close this off to reduce duplicates.


[PDI-17423] - PDI REST Client Not Sending Content-Length(setting chunked)

@pentaho-lmartins
@pentaho/tatooine
The problem reported is related with a bug in Jersey and Apache Client Implementation.
When a ClientRequest is converted to a HttpUriRequest a private method getHttpEntity() is called that returns a HttpEntity. Unfortunately, this returns a HttpEntity whose getContentLength() always returns a -1.
When the Apache http client creates the request it will consult the HttpEntity object for a length and since it returns -1 no Content-Length header will be set.
The solution was add an implementation of Apache Http Client 3.5 for Jersey instead of 4.x.

:white_check_mark: Build finished in 17m 29s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3624, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 18m 5s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3624, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 23m 12s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3624, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

Can't downgrade Jersey.


[region-isolation] Take into account that Swift's RPO order doesn't include blocks that are dead.

When we run RegionAnalysis, since it uses RPO order, we do not visit dead blocks. This can create a problem when we emit diagnostics since we may merge in a value into the region that was never actually defined. In this patch, if we actually visit the block while performing dataflow, I mark a bit in its state saying that it was live. Then when we emit diagnostics, I do not visit blocks that were not marked live.
rdar://124042351

@swift-ci smoke test


Remove modal "Autenticazione effettuata!"

Delete this step in the process because it is redundant: the user will already have received a positive feedback within the IT Wallet/ app IO.
--> This is a NEW requirement

For the highest level of security I have decided to not allow JS to automatically redirect the authenticated user back to the RP, the the "authentication successful" message must be provided with a link/button that takes the user will to continue the flow
this decision is led by the security of the cookie, that in this implementation is configured as httponly, then if the RP authenticates the browser according to a cookie, disallowing the use/access to the cookie with JS (and then Ajax) the request would be done to the RP without the cookie and then the RP would make the authentication fails
this is true for the cross device flow


eink: currently selected menu item whited out

Is the bug present when using the default Obsidian theme?
Yes
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
7.6.3
Describe the bug
When scrolling a menu, the currently selected item is whited out / invisible

Debug info
SYSTEM INFO:
Obsidian version: v1.6.0
Installer version: v1.4.13
Operating system: Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 23.4.0
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Base theme: light
Community theme: Minimal v7.6.3
Snippets enabled: 0
Restricted mode: off
Plugins installed: 28
Plugins enabled: 26
1: Dataview v0.5.64
2: Extract PDF Annotations v1.0.4
3: Kanban v1.5.3
4: Obsidian better Internal Link Inserter v1.0.0
5: Omnisearch v1.21.1
6: Omnivore v1.9.4
7: Zotero Integration v3.1.7
8: Minimal Theme Settings v7.3.1
9: Style Settings v1.0.8
10: Pane Relief v0.5.3
11: Copy Block Link v1.0.4
12: Templater v2.2.3
13: BRAT v0.8.4
14: Outliner v4.8.0
15: Zoom v1.1.2
16: Commentator v0.1.4
17: Chat View v1.6.0
18: Strange New Worlds (SNW) v1.2.5
19: Multiple Notes Outline v0.5.1
20: PDF++ v0.37.15
21: Hover Editor v0.11.17
22: Breadcrumbs v4.0.86-beta
23: Continuous Mode v1.1.0
24: Grappling Hook v1.1.1
25: Novel word count v3.9.0
26: Link Nodes In Canvas v0.0.5
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Go to Minimal Theme Settings and change the Light mode background contrast to Default or Low contrast mode rather than All white which is not supported in eink mode.

Fixed in 7.6.4


merge/overwrite only parsed values to existing moment

hey i hope this is the right place for a feature request.
eventually it is already possible to accomplish this - but i did not find the right way.
if i have a valid moment - is it possible to merge a user .format(UserInput, formatstring, strict_parsing)?
so that only the parts that are given in the formatstring and successfully parsed are merged?
that would make it easier if you want to merge two user-inputs to one date object.
(for example in this angular.js date/time input formater directive)

Sorry, but I'm not sure I am fully understanding the request.
It sounds like you just want to do something like this?
var s1 = '2015-07-17';
var s2 = '12:34:55';

var f1 = 'YYYY-MM-DD';
var f2 = 'HH:mm:ss';

var moment = moment(s1 + ' ' + s2, f1 + ' ' f2, true);

If so, I'm not sure why we need a function for that built-in.  Or is there more to your request?

@mj1856  Well, if you have multiple YYYY in the formats, what will happen? It is a reasonable hack, that might work in some cases, though :)
@s-light this feature that you're describing is pretty specific. Maybe if you patch the parser (it should be .parse, not .format btw), and expose information about what got parsed, you can then proceed and merge them. But what if they conflict? What if one is in week-weekday-weekyear, and the other is in month-day-year and they mismatch? What if there are conflicting token values (YYYY with 2015 and 2016). All of these you should ultimately decide for yourself, and I don't think this has place in moment.
Making the parser a bit more abstract and usable standalone -- this is something I might merge, but you have to implement it, and it has to not make the existing code smell.

@ichernev you are right - parsing is the right word and there are some more things to consider...
i have done a version with fixed merging:
// global definition (example for date input type - differs for time input type)
    var mergeParts = ['year', 'month', 'date'];
// in my userinput parsing function
    // momentjs with strict parsing
    var tempDate = moment(viewValue, formatString, true);
    angular.forEach(mergeParts, function(value, key) {
        modelValueMoment.set(value, tempDate.get(value));
    });

this is working. but with this merging only works for date OR time and is not based on the user formating string.
the idea was be able to do something like this:
// global definitions/declarations
var formatDate = 'YYYY-MM-DD';
var formatTime = 'HH:mm:ss';
// initialize to now
var myDate = moment();

// for example in a onClick handler
// merge userinput for date
var userInputDate = '2015-07-17';
myDate.mergeIn(userInputDate, formatDate, true);

// different event/part of code
// merge userinput for time
var userInputTime = '12:34:55';
myDate.mergeIn(userInputTime, formatTime, true);

the merge will overwrite only the parts that are given in the format string and only do this if the userInput can be parsed successfully.
so 'internally' something like (pseudo code)
// Method Signature could be the same as
// http://momentjs.com/docs/#/parsing/string-format/
function merge(input, format, strict) {
    // parsing
    ...
    // now set date with parsed parts:
    if(parsed_parts contain 'year')
        internalDate.set('year', parsed_year);
    if(parsed_parts contain 'month')
        internalDate.set('month', parsed_month);
    ..
    if(parsed_parts contain 'millisecond')
        internalDate.set('millisecond', parsed_millisecond);
    // some finalizing
    ...
}

hopefully i have made it in someway clearer what i try to do?

You can expose info about what got parsed. And then use it in your custom merge fn.

Closing due to age. Please re-open if you still have questions.


Reset sync stream on retry

When the sdk issued an automatic retry, we neglected to reset the data stream in the sync case. This would cause us to send a payload of 0s in the retried request. By resetting the stream on each subscription, we guarantee we'll send the correct data again.

👋  We're running into the issue of empty/corrupt blobs being created when writing block blobs. This PR gives me hope that this might be the underlying problem, it doesn't look like these changes made it to 12.7.0-beta.1? Is there a plan to cut another release soon or maybe you can point me to the release plan if there's one already that i can follow along.

Hi, @mbellani. We're sorry you are hitting that issue, and hopefully you are correct that this PR will resolve that!
We should be doing a release hopefully tomorrow or early next week--we're a little late on our official GA release this month. If your environment allows for it, I could give you directions on how to install the version in master locally to try it out in the meantime

@mbellani You can also try getting a build from our nightly feed by following instructions here

thanks @rickle-msft for the pointers. At the moment the problem seems to consistently surface itself at a larger volume of writes, is there a predictable test case that you'd suggest to test our theory that this change will actually fix our problem?

I can think of a couple options:

Calculate the MD5 before you stage a block and include that in your call into the SDK. If you start seeing MD5 mismatch errors, that's a good sign it'll be addressed by this PR. This is how we originally found this issue.
Check for retries. Either enable logging at at least the warning level and see if there are retries. If it looks like the number of retries about equals the number of corrupted blocks, that's a sign that it's the same root cause.
You could wrap the InputStream you are passing in a thin wrapper which auto-resets the underlying stream once it's been read all the way. If this fixes your issue, then it will again likely be resolved by this PR.

I appreciate the quick responses @rickle-msft , I'll try those suggestions, re:

You could wrap the InputStream you are passing in a thin wrapper which auto-resets the underlying stream once it's been read all the way. If this fixes your issue, then it will again likely be resolved by this PR.
I'm currently passing in ByteArrayInputStream already which supports mark() and reset(), so that ought to be fine ?

Yea the issue this PR resolved is that we weren't resetting the stream on retries, so you'll have to kind of fake that yourself by wrapping your ByteArrayInputStream in a custom type you write like AutoResettingInputStream which, as soon as it sees the internal stream returns -1 from a read, resets the underlying stream. Then when we go to try to read the stream again, it's already reset and will give us the correct data again for the retry. Does that make sense?

Just to clarify, if you are pulling the nightly build that I linked to, you simply need to try it out and see if it works. You only need to take one of those other options I mentioned if you want more information about whether this PR will help without using the new package.

Yea the issue this PR resolved is that we weren't resetting the stream on retries, so you'll have to kind of fake that yourself by wrapping your ByteArrayInputStream in a custom type you write like AutoResettingInputStream which, as soon as it sees the internal stream returns -1 from a read, resets the underlying stream. Then when we go to try to read the stream again, it's already reset and will give us the correct data again for the retry. Does that make sense?

I am a little bit confused here, when reading the documentation for the stageBlock it says:

@param data The data to write to the block. The data must be markable. This is in order to support retries. If the data is not markable, consider using {@link #getBlobOutputStream()} and writing to the returned OutputStream. Alternatively, consider wrapping your data source in a {@link java.io.BufferedInputStream} to add mark support.

So my understanding is that both  BufferedInputStream and ByteArrayInputStream are both markable, however, when you say:

so you'll have to kind of fake that yourself by wrapping your ByteArrayInputStream in a custom type you write like AutoResettingInputStream which, as soon as it sees the internal stream returns -1 from a read, resets the underlying stream.

doesn't that go beyond  making sure that your stream is markable? It kind of makes it sound like your stream has to be resettable?  Sorry for all the silly questions, but I'm trying to make sure that i understand this so that i can make a correct decision about what kind of stream i pass in.
Also  as a side note, it would be great to get this in sdk docs at some point with examples.

Just to clarify, if you are pulling the nightly build that I linked to, you simply need to try it out and see if it works. You only need to take one of those other options I mentioned if you want more information about whether this PR will help without using the new package.

Sure, i upgraded the dependency to the latest nightly build,  I'll see how that fares.

Sorry for the confusion. I think we got a little out of sync on which version we were talking about. It looks like the docs you're citing are from the nightly build, so I'm going to assume you're using that. In that case, it is sufficient that your stream is markable, and we will do the reset internally (that's what this PR fixed).
Everything else I said about autoresetting was just a hack to investigate the behavior you're seeing in the event you didn't want to try the nightly build, but since you are using the nightly build, you can forget all of that and just let me know if the update fixes your issue.
Hopefully that clarifies things a bit?

Sorry for the confusion. I think we got a little out of sync on which version we were talking about. It looks like the docs you're citing are from the nightly build, so I'm going to assume you're using that. In that case, it is sufficient that your stream is markable, and we will do the reset internally (that's what this PR fixed).
Everything else I said about autoresetting was just a hack to investigate the behavior you're seeing in the event you didn't want to try the nightly build, but since you are using the nightly build, you can forget all of that and just let me know if the update fixes your issue.
Hopefully that clarifies things a bit?

Aah, that makes a lot of sense. Thanks for the clarification.

@rickle-msft just to close the loop here, we're no longer experiencing the problem of corrupt/empty files. Thanks for all the help.


Refactor get_model() function to support multiple models

It will allow use to easly incorporate more models as the request increase.
When you want to add a model:

If this is with a new framework, then add the fw to args_mapping, with the ChatFW func and the args you have to put in.
Then add the name of the model with the framework associated to the model_mapping dictionary.

That's it! Simplier, prettier, cleaner.
To complete that I will refactor the load_api_key() in order to pass though parameter the model to associate the key search to template model and therefore not having one "main" model but a universal application which you can use which ever model to help you.

Another thing to see here is that we can incorporte a APIGetter class to easily adapt to model change with a practical template that adapt when a request is triggered.

If merged, then I'll be integrating multiple models.

Thank you so much.

 That's a pleasure!


Fix a head of line blocking issue in the C++ server

Previously we needed to wait for a registered_call to know if we needed to read payload.
This resulted in serialization of starting to read payloads.
Now, begin the payload read immediately, and once it's ready, try to match it up with a requested call.

Green

LGTM


Feature Request: Infinite Scrolling/Scroll Loading Support

Would it be possible to add similar methods to FlatList to enable infinite scrolling support? E.g., onEndReached
Thanks!

It would be great to see infinite scroll add up in the Accordion component.

As a workaround it would be great to use Scrollview's onScroll event as in https://stackoverflow.com/questions/41056761/detect-scrollview-has-reached-the-end.

As a workaround it would be great to use Scrollview's onScroll event as in https://stackoverflow.com/questions/41056761/detect-scrollview-has-reached-the-end for now.


expose expand functionality

expose the expand functionality of libpostal

Hey @dominikkukacka,
Thanks for the PR. We don't actually want to expose the full functionality of libpostal here, because the text-analyzer module is designed to provide and interface for parsing geocoder inputs but hide the details of how it does it. That way we can slowly switch from using addressit to libpostal,  and in the future possibly use or add other libraries.
If you're looking to use libpostal in your own projects, you want to use the node-postal module directly. If you were going to make a pull request to pelias/api that uses the expand functionality, that should probably also use node-postal directly. Let us know if you have any questions or ideas of how that functionality could be used.


Update Glide and Gradle versions

Hello,
I'm trying to use your lib, but the problem is dependencies are really old.
The last version of Glide is 4.7 and you are using 3.8.
With gradle happens the same, you are using 3.2.1 while the last is 4.4.
I'm having collision between your dependencies and mines, because im using 4.5 Glide and you need 3.8.
Gradle shows the error:
Failed to find byte code for com/bumptech/glide/request/target/GlideDrawableImageViewTarget
This class was removed from >=v4 from Glide.
Could you please, update this repo with latest dependencies.
Thanks.

Thanks for reaching out. We are working on this and expect it will take a
bit of time for the update to go out. We will update this thread once it's
live.
On Wed, Apr 25, 2018 at 7:37 AM, Christian Olcina<EMAIL_ADDRESS>wrote:

Hello,
I'm trying to use your lib, but the problem is dependencies are really old.
The last version of Glide is 4.7 and you are using 3.8.
With gradle happens the same, you are using 3.2.1 while the last is 4.4.
I'm having collision between your dependencies and mines, because im using
4.5 Glide and you need 3.8.
Gradle shows the error:
Failed to find byte code for com/bumptech/glide/request/tar
get/GlideDrawableImageViewTarget
This class was removed from >=v4 from Glide.
Could you please, update this repo with latest dependencies.
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Tenor-Inc/tenor-android-core/issues/4, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADWKHLQ936_qL7UM1z8Tv9gWQJyj3CH7ks5tsIpAgaJpZM4TjjqO
.

No problem. Two months is likely.
On Fri, Apr 27, 2018 at 1:24 AM, Christian Olcina<EMAIL_ADDRESS>wrote:

Perfect!,
Do you know the stimated time? maybe 1 month?, 2? more? less?
Just to know and planning our project.
Thanks you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Tenor-Inc/tenor-android-core/issues/4#issuecomment-384901518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADWKHMKBsfAyNao7L53g8YgGstlGqTQBks5tstWkgaJpZM4TjjqO
.

@ctrl-alt-del Thank's!
I will try

Hello friend, Are you planning to use the v4 do Glide library?

Hello friend, Are you planning to use the v4 do Glide library?

Hi @wvmoreira, the message above (here https://github.com/Tenor-Inc/tenor-android-core/issues/4#issuecomment-404341211) remains the best course of action

Hello @gwlove
Are you all right?
Could you tell me if you still have plans to upgrade to version 4 of Glide?

Hello @wvmoreira! No changes from the last comment.


Improvements on version_tracker

Currently, version_tracker has a few issues:

It checks if any active step depends on an archive step. If so, it raises an error. But if you simply delete dependencies of active steps (instead of moving them to the archive) it doesn't complain. A better logic would be to raise an error whenever an active step doesn't find its dependencies.

Additionally, the error raised is not easy to understand. If you have moved multiple steps to the archive, it can be cumbersome to find out which steps need to be recovered.

It checks if an active step can safely be archived. If so, it raises a warning. Once you have archived that step, it raises another warning if the dependencies of that step can be archived, and so on. A better logic would be to raise a warning that includes all steps that can safely be archived (so, the list of archivable steps should be calculated recursively).

Don't close.