ORC-7 - (Block Reward Restructure)

The 6 Oxen per block reward for the Chainflip liquidity fund (formally blockswap) is due to end in 8 days and soon after it will be burnt as it is no longer required. I feel that this is a good time to bring up the question of what will the block reward be going forward.
Prior to the chainflip proposal https://github.com/oxen-io/oxen-improvement-proposals/issues/24 it was decided in last block reward discussion https://github.com/oxen-io/oxen-improvement-proposals/issues/20 that the reward would be 21 Oxen per block with service nodes receiving 18.9 (90%) and the foundation receiving 2.1 (10%) respectively. As the Chainflip project has spilt off from the Oxen ecosystem I would expect that we are reverting to the previously decided block reward of 21.
However I would like to make a suggestion and open this up to further discussion.
I propose reducing the 21 Oxen per block to a nice round 20 and splitting the reward not only between service nodes and the foundation but also the Oxen Funding system (formally Loki funding system https://docs.loki.network/Governance/LokiFundingSystem/) and a liquidity fund.
The 20 Oxen block reward would be split as follows; 2 for the foundation, 0.5 for the Oxen funding system, and 17.5 for SNs.
However service nodes should reduce their 17.5 block reward for 4 years to 16.5 and 1 million Oxen be printed immediately to be used in the chainflip Oxen pool with the foundation providing the other side of the liquidity pool pair.
I understand that there is currently an ongoing trial and discussion relating to Liquidity Provider Rewards https://github.com/oxen-io/oxen-improvement-proposals/issues/28. Although we are already halfway through this trial and so far it's falling well shot of the intended goal. My proposal is viable alternative to increase Oxen liquidity.
Also to reduced coin inflation if supply goes over 100 million Oxen then the 20 Oxen block reward should automatically reduce to 10 Oxen. This would reduce coin inflation to 2.5% or less per year.

Currently the direction is that the foundation gets 10% of block reward and that does feel like a large quantity at current prices. So a 10% reward is .10% x 20 BR x 30 blocks an hour x 24 hours x 365 days = 525,600 coins. @ current prices that is $735,840.00 USD. What direction does the LF have with these funds.  However what about the 10% of nodes that the foundation is also allowed to run and pull rewards from the SN piece of the Block Reward. I think we need to work on liquidity in the market place without increasing the emissions. I would vote for a reduction of the LF to ~ 5% of Block reward and still maintain the OPTF's ability to hold 10% of all SN.
I think we need to agree on prioritize. I did not assign a rank below but all these seam rather important in my mind.
Liquidity
Dev funding
Sybil resistance
Incentives
I say make the BR = 18, with 1.5 going to the OPTF and 16.5 to SN. Social contract stays the same, LF gets about 8.33% and we have a reduction in emissions.

I believe the direction of the project has lody  partially from dipping toes into Defi and allocating a portion of the block reward to fund the journey. Now that Chainflip has broken away, Oxen has the opportunity to get back on the low key track.
I don't believe we should be allocating a portion of the block reward for an Oxen Funding system. This should be the role of the Foundation and community.
The Oxen Network should be just that.. A private cryptocurrency. A secure messaging platform. A network anonymity layer. Tools to build a more private future for the Internet. And through its network, blockchain, and tech stack, Oxen provides a variety of open-source tools and libraries to empower the development of third-party decentralized privacy technologies. (https://oxen.io/who-are-we)
Build the environment, let the community interact with it.
I purpose getting back to the fundamentals, allocating the block reward solely to the Foundation and Service Nodes.

Okay we're starting to get some good feedback. I just want to point out that the purpose of the Oxen Funding System it to be able to fund development that the Foundation may not be able to fund for legal reasons.


QPPCT-717: Command line doesn't work on Windows

Information

JIRA story QPPCT-717.

Changes proposed in this PR:

The regex for determining if a path is correct or not only allowed / separators.
This has been changed to allow a path separator based on the supplied FileSystem.

Checklist

[x] All JUnit tests pass (mvn clean verify).
[x] New unit tests written to cover new functionality.
[x] Added and updated JavaDocs for non-test classes and methods.
[x] No local design debt. Do you feel that something is "ugly" after your changes?
[x] Updated documentation (README.md, etc.) depending if the changes require it.

You could use Jimfs to create the windows file systems for testing.. jimfs-#newFileSystem then pass Configuration#windows

@omnivion, the tests actually already do.  JimfsContract supplies a jimfs method (with one of the FileSystems being Windows), and @JimfsTest uses it as a method source.


definition missing: geographical region

This one is tricker, but here is what I came up with so far:
"A geopgraphical entity that is a fiat part of the Earth and that is demarcated by boundary lines specified by a map and which specify at every point a location at or near the bona fide boundary between (1) land or water and (2) the atmosphere."

Guessing it would have to be a closed boundary
Fran?ois Modave, PhD
Associate Professor
Dept. Health Outcomes and Policy
On Jul 18, 2017, at 4:09 PM, Bill Hogan <notifications<EMAIL_ADDRESS>wrote:
This one is tricker, but here is what I came up with so far:
"A geopgraphical entity that is a fiat part of the Earth and that is demarcated by boundary lines specified by a map and which specify at every point a location at or near the bona fide boundary between (1) land or water and (2) the atmosphere."

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ufbmi/geographical-entity-ontology/issues/5#issuecomment-316182633, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALir4f9ZGSWkbINYE38F-FcyWJjhbFisks5sPRELgaJpZM4ObpxJ.

May also want to specify that geographical regions can also be demarcated by boundary lines that are defined by certain physical characteristics. For example, the geographical region of Lake Superior would be defined by both its shoreline, in addition to whatever lines were drawn to distinguish it from the mouths of one of its many tributaries and from the St. Mary's River.

Yes, one or more closed boundaries.  Because if you say the geographical region of U.S., you have lower 48 (one boundary), Alaska (another boundary), Hawaii (another boundary or set of boundaries depending on how it's defined), and Puerto Rico (one or more boundaries as it's more than one island), Guam, American Samoa, etc.

Given the discussion on the definition of 'geographical entity', I propose the following:
A geopgraphical entity that is demarcated at least in part by one or more closed boundaries all of whose lines are part of the planetary surface.

+1


Multiple bots handling in tagui

Hi! I want to know that is there any functionality in TagUI so we can handle multiple bots concurrently, like in UiPath?? Looking for +ve comments

TagUI isn't tested and designed to run multiple scripts in parallel. Though I have tried running on my MacBook Air 2014 model without problem for 4 scripts concurrently in default mode (PhantomJS).
If you use Chrome mode, you can try installing TagUI into different directories and try if that works. Using the same TagUI installation in the same directory probably won't work as the Chrome connections from different scripts will interfere with one another.


Typescript projects: outDir in tsconfig.json forces always rebuild of project

Expected Behavior
Even when "outDir" is used in tsconfig.json, a project shouldn't be rebuilt if there's no change to the source files.
Actual Behavior
.js files in "outDir" (different from a certain srcDir) are not recognized when VS decides whether a project should be rebuild

NTVS Version: 1.4.10918.1
Visual Studio Version: 15.4.4
Node.js Version: 9.2.0

Steps to Reproduce

create a new NodeJS Typescript project
build it, run it; run it again and again - no rebuild occurrs
create an empty folder, e.g. "out" and put >"outDir": "./out"< in tsconfig.json compilerOptions
build it, run it - run it again and again - every  time VS asks whether it should rebuild the project

Thanks for reporting, this is an issue in the TypeScript tools for VS, which should be fixed in a future update of VS 2017. (Probably update 6)

Is there a specific issue I could follow? It's not fixed in Update 6, so I would like to get information about the actual progress happening.

@jeffrson I apologize for the confusion.
The issue has been addressed, but it depends on the version of TypeScript you are targeting (i.e., it was fixed in TypeScript 2.6). In order to get the fix, you will have to retarget your project for TS 2.6 or higher.

@uniqueiniquity thanks for stepping in.
Just to be sure - targetting TS means changing it in VS project properties combobox, right?
I tried with 2.6, 2.7 and "latest available", with (MSBuild) project settings or tsconfig.json. Everytime I run a simple TS (console.log) VS prompts me because the project should be outdated. So actually nothing changed.
Anything else I could try?

Yes, that is what I meant.
I'm not sure I know what you mean by "VS prompts me because the project should be outdated". Could you post a screenshot?

Oh I think I may see what you mean. Let me look into this.

Seems like this is an NTVS issue after all. We will reopen and look into this. Thank you for your feedback!

Seems like this is an NTVS issue after all. We will reopen and look into this. Thank you for your feedback!

I didn't find the time to retest myself but if the bug is still there perhaps you can take a look on my thoughts in #1794 (linked above) and the MSBuild diagnostics log.

Found one issue, don't have a fix (yet)…. we consider the contents of the node_modules folder to determine if we need to rebuild, since those files are never updated we rebuild every time.
There are probably other issues....

The issue reported is completely independent from node_modules.
Say we have this app.ts:
console.log('Hello world')

:-) no dependencies (posted for completness)
{
  "name": "tsc_outdir_test",
  "version": "0.0.0",
  "description": "tsc_outdir_test",
  "main": "app.ts",
  "dependencies": {}
}

and this compiler config (tsconfig.json):
{
  "compilerOptions": {
    "outDir": "build"
  },
  "exclude": [
    "node_modules"
  ]
}

If F5 (start debug) is pressed, the project is reported as being outdated - every time.
As soon as "outDir" is removed, the project is rebuilt only once. And, btw, if I manage to copy output files from build back to where app.ts resides, then there's also no rebuilt.
The issue must be related to failure of localizing app.js, app.js.map.

This looks like it's much more work than I expected. Closing in favor for #1949 which captures more use cases.


Modifier extension methods should be limited to the Layout Scope

To enforce constraining only immediate Composables inside ConstraintLayout.

Seems like this is inherent to the API. Working as intended for Modifier.constraintAs, we could do the same thing to the ConstraintLayout specific layoutId() but since there's a method with the same name in the Compose library, I don't want to create confusion.
Might be best to deprecate the ConstraintLayout layoutId() moidifier with a name change and add it under ConstraintLayoutScope.


fix(visual): do not start on visual mode enter when v is deferred

Description
If the 'v' key is deferred then don't start on visual mode enter. This is needed because vim.opt.keymodel='startsel' will enter visual mode also on shift+motion besides the 'v' key.
Related Issue(s)

Fixes #735

@folke in what way it breaks the defer mode? I would be glad to fix it.

defer mode literally means defering showing the popup.
What you added would simply disable defer completly for v

Just disable opts.modes.x.

disabling opts.modes.x prevents to show any combos inside the visual mode, such as:
+Visual » g
  b ➜  Comment toggle blockwise (visual)
  c ➜  Comment toggle linewise (visual)
  e ➜   Prev end of word
  g ➜   First line
  u ➜   Lowercase
  U ➜   Uppercase
  w ➜  Format
  x ➜ 󰈔 Opens filepath or URI under cursor with the system handler (file explorer, web browser, …)
  % ➜   MatchitVisualBackward)
  [ ➜   Move to left "around"
  ] ➜   Move to right "around"
  ~ ➜  Toggle case

and others...
so it's not a good solution.


Pydantic frozen models as keys for dictionaries

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
This seems a fairly fundamental issue, so I was really surprised to run into this, but after spending some time with google I really didn't find anything. I'd like to be able to use a frozen pydantic model as a key for a dictionary. In itself, this actually works, but (de)serializing from/to json doesn't work.
Sort of a minimal example to illustrate what I'm after:
from pydantic import BaseModel

class A(BaseModel):
    a: str

    class Config:
        frozen = True

class B(BaseModel):
    z: dict[A, float]

b = B(z={A(a='a'): 1.0})

json_b = b.model_dump_json()  # works
b.model_validate_json(json_b)  # fails

I can sort of work around the issue by creating a list, validating its items to be unique and add a get method to AWithValue, but this feels a fundamental enough requirement to discuss natively supporting it?
class AWithValue(BaseModel):
    a: A
    value: float

class C(BaseModel):
    y: list[AWithValue]

    # Skipped over validation code

    def get(self, a_value) -> Optional[float]:
         return next(iter(el.value for el in self.y if el.a == a_value), None)

c = C(y=[AWithValue(a=A(a='a`'), value=1.0)])

json_c = c.model_dump_json()
c.model_validate_json(json_c)  # This works

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[X] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Thanks for the response.
I had not realized that my request is actually not allowed under the JSON spec, so I do see the logic of not supporting this. From that perspective, an error message will definitely help. Note that on the deserialization you get an error message, but even that error message could (imho) be a bit clearer to clarify that the json is actually invalid as the current error message gave me the impression this was a pydantic limitation.
Something that could potentially add value for end-users (but definitely ventures into the realm of syntactic sugar) is the following: on a frozen base model (frozen is required to have a hashable dictionary key), automatically use the hash of the object as the key for dictionaries.
class KeyProperty(BaseModel):
    some_value: str
    another_value: str

    class Config:
          frozen=True

class Data:
    my_data: dict[KeyProperty, float]

Then, serializing an item Data(my_data={KeyProperty(some_value='a', another_value='b'): 3.0}) could be turned into something like (I'm not writing valid json here, but I guess the point is clear):
{
    {
          _my_data_mapped: { 'my_data_hash_as_string' : 3.0 }
          _my_data_mapping: {
               'my_data_hash_as_string': { _json for the KeyProperty datum_ }
          }
    }
}

And then deserialization could automagically turn this back into the objects as defined.
My thoughts here:
- First I was thinking about automatically generating an id field seperate from the hash, but then you lose value equality semantics as objects with all the same values, but different ids will actually have a different hash (unless that id field is excluded when determining the object hash, but this feels shaky)
- For relatively small/dumb data objects that serve as key, the functionality of having automagically the possibility to serialize where dictionary keys are stored in a seperate data item is maybe a bit like some syntactic sugar, but I think it's actually nice to not have to implement this yourself and I also would assume this is a somewhat common use case?

Hashes aren't guaranteed to be unique, so wouldn't be safe to use as keys in general, and also aren't "invertible" so couldn't be used for deserialization.
I think it's not crazy to have some way to support arbitrary objects being converted to/from dictionary keys, but I'm not sure what a good API would be.
If there's broader interest in this as a feature I'd be open to proposals but I think realistically, erroring might be the least controversial choice.

I just ran into this problem.
My recommendation is to use the key's model_dump_json() to convert the pydantic class into a string instead of __str__() like now:
{
  "z": {
    "{\"a\":\"a\"}": 1.0
  }
}


datetime , 6 digits for the year

Hi,
I cannot find if this was posted before, Do anyone else find this same? I found this on running automated testing .... but then I reproduce it by typing manually the year value too.

Hi! It looks like that is a native <input> component rather than one of our text fields. If there's an issue with our text field, please post a reproduction and we can re-open!

ok, Thanks


Align the topics page to the designs

Update the Topics page header to be in sync with the designs. The warning icon will always show zero as for the moment we don't have the count of topics that are in-sync and under replicated.
Connect the search input to search in the topic names.
Add a switch to show/hide internal topics (hide is the default). not in sync. Part of #165.
Add a status column to show the in-sync or under replicated state of a topic. This is done by looking for a replica amongst all partitions that hold the topic that is flagged as not in sync.
Reorder the columns.
Change the "Edit properties" action to "Edit configuration". Part of #142.
Change the column name "Messages" to "Record count".
Add the right empty states for when there are no topics and for when a search doesn't produce results.

I don't think that record count will intuitively be clear to customers who are looking for their messages. Maybe we should keep it as "messages" and add a tooltip that explains what are we basing the numbers.

Updated to also allow for search by topic ID

The icons for status should be:
fa-check-circle/ fa-exclamation-triangle

Updated icons

We'll need to add some help tooltips to the columns, but that's probably a separate PR.
other than that LGTM.


Fixed auth by service account json file

I just submitted the CLA.

Thanks! I'm a bit concerned about the naming - let me check there aren't any routes where you get files with the old format still. May be that we need to support both.

Ended up merging #524 which handled both versions, so this functionality should be in. Sorry  for the delay, thanks though!


Document setting context of Stache data helper

As mentioned in #1619, this documents setting the context of the data helper explicitly.
Does the "optional argument" syntax work in that @signature?
Closes #1619

Isn't context here more the data that are being set?

I might misunderstand how it works.  I thought the optional argument was to allow setting another key as an alternative to the current scope.  Maybe it should just say key instead of context?

Well I mean basically what you do with <div {{data 'person' person2}}> is $(div).data('person', person2) so it's simply just the value that you are setting. I find the word context potentially confusing here.

This was fixed by commit b7c8769b26c4b56e866f5d5804c353693bd55ad3


Issuer cannot grant to a multisig prefix

Currently, an issuer cannot directly grant to a multisig prefix.
This is demonstrated in PR #184, I had three clients where client0 is an issuer while client1 and client2 are a multisig receiver. client0 has resolved the multisig group's OOBI, and I tried to send a grant the credential to the multisig prefix as follow.
// This doesn't work
await client0.exchanges().sendFromEvents('delegator', 'credential', grant, gsigs, end, [multisigPrefix]);

This doesn't work, but the script below works.
// This works
await client0.exchanges().sendFromEvents('delegator', 'credential', grant, gsigs, end, [aid1['prefix'], aid2['prefix']]);

I have had the same issue. See discord conversation here: https://discord.com/channels/1148629222647148624/1148734044545228831/1184175010517098586

Question about OOBIing with a multisig AID. I was trying to implement multisig admit using signify. Most often when resolving oobis, we use the oobis().get("alias", "agent") function to get the OOBI endpoint for the agent of the AID. When I use this OOBI to add the holder contact, the IPEX grant message only reaches one of the holder members.
I noticed in signifypy, https://github.com/WebOfTrust/signifypy/blob/development/scripts/multisig-holder.py#L113, that OOBI url is manually created and it does not point to a specific agent. This is what I had to do as well to get it working in signify-ts.
Currently, it seems like the KERIA endpoint used to generate an oobi for an AID only allows to get OOBI urls for agent or witness, i.e. the role parameter. Any thoughts on this? Currently I am just constructing the OOBI manually  /oobi/.

I have currently worked around it by constructing the OOBI url "manually" as done in signifypy. But there is probably another fix out there.

@lenkan Thank you for the suggestion. If we change the default role for the oobis.get, would it not affect the default behavior of all OOBI implementations for single-signature AIDs?

I forgot to mention that I have tried @lenkan's suggestion to manually edit the OOBI URL and it works!
However, I don't really understand how KERIA internally resolves OOBI, and I am not sure if changing the default behavior will break something. So I will leave that task to someone more knowledgeable than me.

Just adding to this that it is also what is being done in the new multisig-holder.test.ts file. See here: https://github.com/WebOfTrust/signify-ts/blob/c64e00695e1f2a767b946dcaa84e3864eb6cd8f7/examples/integration-scripts/multisig-holder.test.ts#L396

I will close the issue for now. I will instead create an issue in Keria.


objects won't stop moving

See https://codepen.io/anon/pen/rvGVQa for a consistent repro.
Pretty sure in real world it would have stopped much sooner. How can we tweak it so that it's more realistic?

In this case, try increasing the body.slop e.g.
var boxProperty = {
      friction: 0.7,
      frictionStatic: 10,
      restitution: 0.2,
      slop: 0.2
    };

Also, I'd say your static friction value is too high (the default is 0.5). Balancing all of these values though is always a bit of trial and error! Other things to try: increase the density of the lower down bodies, since placing heavy bodies on top of lighter ones can be unstable. In the complex cases, sometimes you need to increase the engine iterations.

Thank you @liabru! That's very helpful

They don't actually stop moving if you add slop: 0.2 but keep moving very very slowly. After a minute or two the rectangles on the top fall down because they kept moving slowly to the right (without any reason).
Please re-open this issue.

This still seems to be an issue, I have a rectangle on an inclined static body and the object moves vert slowly, even on 1-degree inclined bodies.

@milan090 thanks for reporting, would you happen to be able to provide a minimal example? Specific test cases would help with improving this if possible.

I have been working on this physics simulation project. You can check the example I use here.
The code for it is here
The part of the code to focus:
  const slide = Bodies.rectangle(0, sizes.height, slideLength, 5, {
    isStatic: true,
    friction,
    frictionStatic,
    slop: 0.5,
    angle: angleOfInclinationInRadians,
    render: {
      fillStyle: "#fff",
    },
  });

  const boxPosY =
    sizes.height - (sizes.width / 2) * Math.tan(-angleOfInclinationInRadians);

  const box = Bodies.rectangle(
    sizes.width / 2,
    boxPosY - size - 50,
    size,
    size,

    {
      angle: angleOfInclinationInRadians,
      friction,
      frictionStatic,
      // restitution: 0.2,
      density: 0.5,
      slop: 0.5,
    }
  );

The variables used here can be adjusted on the public website link I provided earlier.

@milan090 thanks could you tell me the input values tested and the expected behaviour?

@liabru I used angle 5 degrees with max static friction and friction above 10 and it kept moving even after slowing down

@milan090 much appreciated, it often is that case that the friction values require some trial and error to get right for a given effect, which is usually what I'd recommend in games, but this does show limitations I'd love to improve.
Until then for your usage I'd recommend enabling sleeping to help bring the bodies to a full stop, or otherwise implement something similar by detecting a small velocity and then stopping the body.


support for more windows editions

Please add support for:

Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2016
Windows 10

see #17

I've added Facter 2.x and 3.x facts for these platforms in #46

Fixed in #46.


Replace plug_cowboy with bandit as integration test server.

This was easier than thought. Payback day.

🤷 I don't know. I'd leave it there, since it can happen with any elixir dep that depends on an erlang package.

No even sure that it is worth it switching to bandit, now that we know what is going on

No even sure that it is worth it switching to bandit, now that we know what is going on

I know... but I figured why not try something new for a change.

Living on the edge 🚀


Update toml decode errors to be more precise

Hey, this is just a small change to increase the customer satisfaction and abort with a more meaningful error in case of configuration issues.

lgtm!

Codecov Report

Merging #2172 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master    #2172   +/-   ##
=======================================
  Coverage   31.46%   31.46%
=======================================
  Files          76       76
  Lines        6770     6770
=======================================
  Hits         2130     2130
  Misses       4522     4522
  Partials      118      118

/lgtm
/test kata-containers

/test kata-containers

/test kata-containers


Running wine in docker

Hi all, I trying to run some Windows console utility in docker using wine and everything is OK when i run container locally(ArchLinux, kernel 4.2.1, docker 1.8.2).
But, on my digital ocean Ubuntu server(14.04, linux 3.13.0, docker 1.8.2) i have many wine-specific errors. As i can see, the difference between local machine and server is kernel version. Is it docker issue, kernel issue or wine issue(I doubt it)?
My Dockerfile:
FROM ubuntu
MAINTAINER Gleb Sinyavsky<EMAIL_ADDRESS>
RUN dpkg --add-architecture i386 && apt-get update -y && apt-get upgrade -y &&\
    apt-get install -y software-properties-common && add-apt-repository -y ppa:ubuntu-wine/ppa && apt-get update -y &&\
    apt-get install -y wine1.7 && apt-get purge -y software-properties-common && apt-get autoclean -y

COPY filterforge4 /filterforge4
ADD dbghelp-xfw.dll /filterforge4/Bin/
ADD run.sh /

VOLUME ["/input", "/output"]

cmd /run.sh

run.sh:
#!/bin/sh
wine /filterforge4/Bin/FFXCmdRenderer-x86.exe Z:\\input\\tasks.xml
chmod -R 777 /output

As you can see the Windows console utility is FilterForge 4 cmd renderer.
last error messages from wine
...(hundreds of same message as below)
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
wine: Invalid parameter.
Failed to execute target process
(Error code 87)

When i trying to run container locally i see standard filterforge error message, because volume with task is not mounted. Also, i will try to run the container on Ubuntu 14.04 desktop and report here. Another attempt: build image on server instead of copying it from local machine, i will report too. Thanks!

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Built on server image has same result: wine errors

Ubuntu Dekstop 14.04 on local machine: same issue
Ubuntu Desktop 15.04 on local machine(Linux 3.16.0, docker 1.6.2) - WORKS!

UPDATE: Ubuntu server(and desktop) 15.04 with docker.io from repos: works, but app can't exit, some other wine errors, unusable(don't notice it before). With latest docker and latest kernel <IP_ADDRESS> i have same errors from original issue.
So, i have many different situations: different ubuntu versions, different kernels, different docker versions and NO ONE USABLE COMBINATION. It only works on my laptop(described above). Any info on your request.

Seens like it works on Debian 8.1 with docker 1.6.2 and kernel 3.16.0-4


Dev Test: Masses and Springs 1.0.0-dev.109

After discussion with @ariel-phet, we thought it would be good to have this sim go through one more quick spot check. Some changes and bug fixes were made to the period trace recently and may affect performance.
This dev test should be focused on the period trace and performance on low-end devices. It would be worth doing a quick run through to make sure performance is acceptable. Please report any issues to https://github.com/phetsims/masses-and-springs/issues.
URL to Test: https://bayes.colorado.edu/dev/html/masses-and-springs/1.0.0-dev.109/phet/masses-and-springs_all_phet.html
Assigning @ariel-phet for priority and tagging @arouinfar for any input that may be needed.

Looks like nothing else has a priority label currently, so giving this top billing!

@JRomero0613 and I tested the performance on the following:

iPad 2, iOS 9.3.5, Safari
Windows 7, all browsers
Windows 8, all browsers
Android tablet, Chrome

The performance was acceptable on all devices, and we haven't seen any new bugs.
Passing over to @Denz1994.

Thank you very much, QA team for the work. Closing this issue.


Refactor fetching iana http status codes to use caching

Refactored iana status codes test provider to use locally cached file instead of downloading them on each tests run.
Also fixed failing tests, replaces #366

I've rebased your commit off of current master, and will merge if the tests pass. Thanks, @Xerkus !


Allow non-top-level ES6 import declarations

See #903 for rationale. #944 makes it possible to use Esprima-harmony's tolerant mode which allows such imports to parse, but it does still report them as an error. However, this error is very specific and thus amenable to being specifically ignored.
JSCS ought to ignore this particular "error" since it's a semantic/correctness issue rather than a stylistic issue.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Allowing import to be everywhere sounds like side-effect of transpiling, otherwise it seems weird for ES6 to forbid it but for transpiler to allow it.
Why is that? Could you provide links to relevant topics?

Well, yes, the transpiler can be permissive like this because the CJS module system (and probably UMD too) don't impose any such constraint, and those are what it uses when transpiling to ES5.

Thanks again!

Thanks! I look forward to re-enabling the next release of JSCS on my ES6 project :smile:


chore: fix all contrubutors badge

:tada: This PR is included in version 1.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix for Long Error Message when Downscaling Method checkboxes are all unselected

This PR is an attempt to improve the behavior of when the Downscaling Method checkboxes are all unselected in selections.show()
Although not a true fix, this PR at the moment does away with the long error message and the selections behave as if the Dynamical checkbox is checked even though no checkboxes are checked. If someone has an idea how to recheck the checkbox that would be great!
Let me know if this is an improvement...

@elehmer I like that the error isn't produced when neither are selected and that it defaults to the dynamical settings. For error tracking, is there anyway we can ensure that if a user goes to retrieve data but "forgets" to have a selection for dynamical or statistical selected it will not retrieve anything and will return some sort of statement of "Please select a downscaling method"? As an alternative, I suppose we could add a "Dynamical and Statistical" option for downscaling method and change the check boxes into radio buttons where something must be selected

@elehmer I like that the error isn't produced when neither are selected and that it defaults to the dynamical settings. For error tracking, is there anyway we can ensure that if a user goes to retrieve data but "forgets" to have a selection for dynamical or statistical selected it will not retrieve anything and will return some sort of statement of "Please select a downscaling method"? As an alternative, I suppose we could add a "Dynamical and Statistical" option for downscaling method and change the check boxes into radio buttons where something must be selected

Ooo that's a good idea. Let me look into implementing radio buttons that way...

Now getting this error @elehmer on using the statistical+dynamical option :
ValueError: COULD NOT RETRIEVE DATA: For the provided data selections, there is not sufficient data to retrieve. Try selecting a larger spatial area, or a higher resolution. Returning None.

Now getting this error @elehmer on using the statistical+dynamical option :
ValueError: COULD NOT RETRIEVE DATA: For the provided data selections, there is not sufficient data to retrieve. Try selecting a larger spatial area, or a higher resolution. Returning None.

Yes, I am deep in the ramifications of changing how downscaling_method works...

I think the change to Radio buttons is successful now! The GUI appears to work just like it did before (but of course without the issues where no checkboxes were checked). @vicford Can you give it a test run again?


User cannot proceed with the normal checkout after authenticating with Amazon

Hi,
The merchant http://www.gatsbylady.com/ is live with the new plugin and so far we haven't seen any issues except for the following.
-A user clicks on "Pay with Amazon" and authenticates.
-The user will see the widgets.

The user goes back to the cart and decides to proceed with the normal checkout instead of paying with Amazon. However, the user will still be forwarded to the widgets instead of being forwarded to the standard checkout.

I was able to reproduce this in my test shop in the sandbox. Could you please take a look at it?
Thank you.

I just talked with Nathan and he explained to me that this is the expected behavior.


inconsistent require-schema versions

~/dev/my repos/blade(master ✔) grep -r Require-Schema *
bndtools/blade.servicebuilder.svc/bnd.bnd:Require-SchemaVersion: 1.0.0
liferay-gradle/blade.servicebuilder.svc/bnd.bnd:Require-SchemaVersion: 2.0.0
maven/blade.servicebuilder/blade.servicebuilder.svc/pom.xml:						<Require-SchemaVersion>3.0.0</Require-SchemaVersion>

sure , I made it different just for test :)


Dead link on wiki mainpage

after resolving #773 the link to the "Builing from Eclipse" page on the wiki's mainpage (https://github.com/forkhubs/android/wiki) should be removed too

Solved.


check max and min temp limit

Check max_temp_limit is larger than min_temp_limit. If it is not so, throw the exception.
Error publish is throttled because fps of boson is high (60Hz)

Error message example

related Asana task

@garaemon
To pass the lint check, I changed many parts in this code. But the main part is this commit
Could you tell me if there is a better way to check between the max limit and min limit like this situation?


Fix regclient.WithRegOpts

Fixes issue
Fixes #410

Describe the change
The input validation was done on the wrong variable resulting in WithRegOpts always returning without making changes.

How to verify it
regclient.WithRegOpts should now work.

Changelog text

Please verify and check that the pull request fulfills the following requirements

[ ] Tests have been added or not applicable
[X] Documentation has been added, updated, or not applicable
[X] Changes have been rebased to main
[X] Multiple commits to the same code have been squashed

I'll merge this after adding some tests later today.


Markdown goes wrong when interprets some CJK characters

I have found that some formats (like bold, italic, deleting line) can't be shown well when these special characters are between certain CJK characters.
I have tested in some situations and the testing results are as below.

Code
Preview in Code
Result
Notes

~~aaa~~
aaa
OK
All letters

~~（~~
（
OK
Chinese bracket

aa~~（~~
aa~~（~~
Failed
Chinese bracket and letter

aa~~aa~~
aaaa
OK
Both letters

符号~~aa~~
符号aa
OK
Chinese characters and letters

符号~~符号~~
符号~~符号~~
Failed
All Chinese characters. And it can be shown by Github Markdown but failed in VSCode Markdown.

Other grammers have the similar errors too. Test results about them are omitted.
I use strapdown.js to interpret the markdown codes above and they are shown well. So I think the Markdown interpreter in VSCode may have some bugs.

VSCode Version: 1.44.0 (user setup)
OS Version: Windows_NT x64 6.1.7601

Steps to Reproduce:

Create a new Markdown file.
Write the codes.
Click the 'preview' button and check the results.

Does this issue occur when all extensions are disabled?: Yes

The markdown preview uses markdown-it for rendering and I believe I see the same behavior in the markdown-it demo
Please file this issue upstream against markdown-it since we cannot fix this on the VS Code side

@mjbvz I found the same issue on 'markdown-it'. Thanks for your answer!


No sane way to use zfs boot environments in nixos

I was so excited to have zfs-on-root with nixos that I made this script to bootstrap my systems in a very quick way, but now I am slightly disappointed by the fact that utilizing the idea of "boot environments" and tools like beadm (such as this linux port https://github.com/TemptorSent/beadm ) is not a very practical idea at this time in NixOS.
I suppose it is partly due to the feature overlap, there may be a lack of interest to support  zfs boot environments in general. I'm not saying it can't be done, but here is what I have tried:
1. Using the bootfs property with "beadm activate" and using grub.
This would be ideal, and is the typical workflow i'm familiar with in FreeBSD. You use beadm create/rename/destroy and when you want to reboot into the new boot environment, you "activate" it and then reboot the computer. Of course, without activating, the boot environment should still be available on the boot loader. The problem I run into using this method, is that it plain doesn't work in nixos, because nix only supports legacy mounts-- on top of that, in all linux distros it is not good either, because grub does not use the bootfs property when loading a kernel and initramfs-- so even if you set, root=zfs or root=ZFS (depending on your initramfs), grub still requires a hardcoded location to find the kernel and initramfs, and this is bad-- because it can create scenarios where kernels and modules are mismatched-- at this point, you might as well hardcode which boot environment to load using e.g. root=zfs:zroot/ROOT/my-boot-env.
2. Not using the bootfs property and using grub.
Doing it this way, you need to hardcode the path to not only the kernel and initramfs, but also to the boot environment dataset with the root filesystem on it. As previously mentioned, it could look like as follows as a kernel parameter: root=zfs:zroot/ROOT/my-boot-env
Now this actually works quite well, and was my original idea that I used in funtoo (gentoo derivative), https://github.com/a-schaefers/grubbe-mkconfig , all i did was use a simple menu entry stanza generator and update my grub.cfg file every single time i ran beadm, and it worked quite well. Every time i rebooted my grub contained zfs boot environments to choose from. The script is incomplete and needs some TLC, but "it worked."
My plan was to improve the "grubbe-mkconfig" script to auto detect our nixos kernels on a per-boot-environment basis which generates a list of each boot environment and a boot entry for each kernel, and slip it into a custom beadm fork, and then have it trigger "nixos-rebuild boot" as needed, and finally slam the bios-boot partitions with "grub-install" every_single_time in order to update all stages of the boot loader with the latest information as much as necessary. The boot loader would contain nix builds AND zfs boot environments to choose from.
One benefit of such an approach would be such that if a nix install gets borked, it still is possible to restore quickly at a lower level using a zfs snapshot. However, the benefits of this quickly begin to dissipate when one considers already this is a reproduceable nixos system (which is now also installable using only "one command"),  so even the worst of doomsday scenarios, the "let's just reinstall and reproduce our setup" is still quite painless-- and on normal sunny days, we can just use the already-complete nix build grub menuentries. This has me scratching my head, "why am I trying so hard to achieve boot environments freebsd or solaris style?"
I still tried. I created a boot environment with the beadm script, but am unable to get them to load from the GRUB menu, and the irc chat room seems to have nobody in it who knows how to do it. I begin searching through the nix and perl sources trying to figure out what in the world is going on, and I still am not entirely sure how nix knows which zfs dataset is the root dataset! I suspect the nixos-generate-config generated file hardware-configuration.nix is used by nixos-rebuild boot to build an initramfs that knows where to find the root dataset, that is my hunch, and I'm too lazy to keep searching at this point.
3. Possible workaround: switch boot environments from a live disk?
So, I try a new approach, what if i create a boot environment with beadm, and then import the pool from a rescue disk, and then mount a root dataset to /mnt, and nixos-enter (chroot) it, then create a quick /etc/resolv.conf and finally run "nixos-generate-config" && grub-install /dev/sdX && "nixos-rebuild boot", then exit and export pool, reboot, surely this would reboot into the previously created boot environment, no? No it does not. This method has worked for me in the past, but today it is failing and I cannot get nixos-rebuild boot to build anything at all! So this method is unreliable. I didn't want to pursue further in this direction, this is already more manual procedure than I want to do or recommend for people.
I now believe I was a bit naive to think it would simple to utilize boot environments in nixos, I underestimated how opinionated nixos is about using legacy mounts, and declaring where everything should be and how everything thing should load beginning from GRUB on. As it is, I cannot recommend boot environments in nixos, or even figure out how to get them working in a reliable manner for an everyday user. On the bright side, they are much less needed in nixos, as nixos already provides a builtin rollback method on the bootloader!
4. Conclusion.
Until NixOS allows for explicitly declaring which root dataset we want to boot from the GRUB edit menu as a kernel parameter (e.g.  root=zfs:zroot/ROOT/my-root-dataset), and allows non-legacy zfs mounts / bypassing the hardware-configuration.nix file , then I don't see zfs-on-root "boot environments" being a viable option. Because of this, it is now my recommendation to mount /nix outside of the root dataset. Themelios does this by default now by setting zfs_dataset_slashnix_no_root="true" in configuation.sh.
We can keep zfs-auto-snapshot enabled for root (still keeping nice zfs snapshots of /etc/ and .e.g. /nix-config is still useful, for example, but snapshotting the /nix and nix-store is probably just a waste of disk space, and if you want a full system rollback, just use the nixos supported method of choosing nix builds from the grub menu, or reinstall your operating system in one command using themelios, (Note: If you choose to keep the /nix on the ROOT dataset, you can still roll it back using a rescue disk e.g. "zfs rollback zroot/ROOT/nixos@snap_shot_name"-- but this would be considered a destructive action, I mean there is no going back to the future after the rollback, it would be permanent.)

I guess this is not really a themelios issue.


Added ZeroMQ http://zeromq.org/

I thought the zeroMq lib should not be missing here. There are c++ bindings available: CppBinding
Github

ZeroMq is allready included under the category "Inter-process communication"


Seems to rely on behavior related to known soundness bug

This crate (and also similarly polonius-the-crab) work with a
pub trait HKT
where
    Self: for<'any> WithLifetime<'any>,
{ }
pub trait WithLifetime<'lt> {
    type T;
}

trait, and dyn for<'a> WithLifetime<'a, T = Foo<'a>> trait objects that implement it.
However, such trait objects currently are able to implement the trait in ways that a manual implementation never could. E.g. try replicating dyn for<'a> WithLifetime<'a, T = &'a T> for some type T that does not fulfill T: 'static.
Code example and error message (click to expand)…

pub trait HKT
where
    Self: for<'any> WithLifetime<'any>,
{ }
pub trait WithLifetime<'lt> {
    type T;
}

use std::convert::Infallible;
use std::marker::PhantomData;

struct HktRef<T>(PhantomData<fn() -> T>, Infallible);

impl<'a, T> WithLifetime<'a> for HktRef<T> {
    type T = &'a T;
}

error[E0309]: the parameter type `T` may not live long enough
  --> src/lib.rs:15:14
   |
15 |     type T = &'a T;
   |              ^^^^^ ...so that the reference type `&'a T` does not outlive the data it points at
   |
help: consider adding an explicit lifetime bound...
   |
14 | impl<'a, T: 'a> WithLifetime<'a> for HktRef<T> {
   |           ++++

For more information about this error, try `rustc --explain E0309`.

And such impossible-to-implement-manually examples are used throughout the crate, e.g. in the implementation of .map_to_ref to name just the first example I could find.
The relevant soundness issue is demonstrated here.
I’m not saying that typical usage of polonius-the-crap or lending-iterator as intended is necessarily prone to being unsound (though I haven’t really thought too deeply yet about whether or not that’s the case). However, the heavy usage of such trait objects seems “risky” at least in the sense that an eventual bugfix of rust-lang/rust#84533 might break these crates.
I think these crates have enough potential for being useful, so that this risk of breakage might eventually apply to a large number of crates that depend on them, which seems like something we should try to avoid.

IMO, with the current status of soundness issues, the “safest” approach would be to try and avoid using trait objects alltogether, even though I admit the trait-object-types-as-HKTs hack is highly convenient (every manual-trait-impls approach would presumably involve the need for listing free variables as well as their relevant trait bounds in a HKT! macro).

polonius-the-crap

😭

Thanks for the report, I have to admit I was initially surprised the first time I noticed that dyn for<'a> WithLifetime<'a, T = &'a T> would work without the need for "upper bounds" 😅. But, in practice, this is indeed what managed to make these crates —especially lending-iterator!— actually usable, since without 'static bounds in many places, as you said, we'd have to be carrying upper bounds around.
FWIW, I've transposed your PoC of the unsoundness using WithLifetime & HKT:

use ::lending_iterator::higher_kinded_types::*;

trait ConversionProof<'a, 'b> : Sized {
    fn convert<T> (
        proof: [Self; 0],
        x: &'a T,
    ) -> &'b T
    ;
}

impl<'a, 'b> ConversionProof<'a, 'b>
    for &'b &'a ()
{
    fn convert<T> (
        _proof: [Self; 0],
        x: &'a T,
    ) -> &'b T
    {
        x
    }
}

fn convert<'a, 'b, T, O : HKT> (
    x: &'a T,
) -> &'b T
where
    Apply!(O<'a>) : ConversionProof<'a, 'b>,
{
    O::T::convert([], x)
}

pub
fn extend_lifetime<'a, 'b, T> (
    x: &'a T,
) -> &'b T
{
    convert::<_, HKT!(&'b &'_ ())>(x)
}

(I've skipped the T : ?Sized loosening to keep the snippet more lightweight, but it would also work with that unbound)

Regarding potential breakage in the future

polonius-the-cra{b,p} used not to rely on this dyn trick, so we could make a revert, although it would require the extra "please provide the generics in scope" lack of ergonomics.
In general, since that cra{te,p} hides the dyn for<'a> WithLifetime<'a under the rug of the polonius…! macros, I do suspect that slapping an upper-bound to limit the for<'a quantification would be doable (I think I had this at some draft stage; imagine the polonius function taking an extra upper-bound lifetime like thread::scoped() does).
All that to say that I'm quite confident I could make a patch update of that crate to dodge the issue (or even better, we could go and try to anticipate it!).

lending-iterator is definitely a pickle, in this regard, since we do have to expose direct HKT! usage to users, and that usage currently does not expect them to provide "upper bounds for the universal quantification", and luckily so, since at that point the API would become unintelligible but for the most lifetime-savy people, thence killing the whole crate altogether, I'd say (but for a standalone windows_mut, I guess).
My hope, in this regard, thus, is for generic_associated_types and/or properly-quantified for<…> bounds and/or existential parameters (here, the upper-bound lifetime) to be available —before that soundness bug is patched in a way that would make dyn for<'a> Trait… : for<'a> Trait… no longer hold (or the type altogether to no longer exist!)—, so as to be able to fix this crate with a patch update. But I'd be keen to hear what @nikomatsakis or other lang people working on lifetimes would have to say about this case: maybe the necessary higher-order abstraction to be able to soundly express LendingIterator::map semantics concisely will never be made available to Rust?

Assuming HKT!(<'a> => &'a T) to still exist, but for it to implement, for<'a where 'T : 'a> WithLifetime<'a> = HKT<'T> (assuming 'T to be a thing, at least existentially), then we could envision LendingIterator::map's signature to become:
fn map<'upper, Ret : HKT<'upper>, F>…
where
     F : for<'n> FnMut([&'n (Self, &'upper ()); 0], Self::Item<'n>) -> A!(Ret<'n>),

and thanks to lifetime inference I'd imagine this to be compatible with the most frequent currently-written call-sites that we have now (I guess I could try to conservatively introduce 'upper and tweak the array parameter to include it, just in case?).
In this scenario, I do see a way forward almost no breakage 🙏

polonius-the-crap

sob

OMG, sorry, what a typo 🤣


Create multiple templates for displaying products

Could also be as simple as creating multiple landing pages for a category of products


Are you Interested in integrating XSQL into Scriptis and Linkis?

Hi, Your project is particularly great, but there are certain thresholds for analysis users. Are you Interested in integrating XSQL into Scriptis and Linkis? .
Scriptis: https://github.com/WeBankFinTech/Scriptis
Linkis: https://github.com/WeBankFinTech/Linkis
I look forward to your reply. Thank you very much.

@wushengyeyouya  do you want to use hive thriftserver2 jdbc？

Linkis support spark engine, and we can implement a new EngineHook to get the ability of XSQL.
Scriptis can show the metadata of XSQL holded, and submit sql to linkis.

How does Scriptis&Linkis use spark now? xsql usage is all the same as spark

Linkis use spark repl to obtain the ability of spark. So we think Scriptis&Linkis is pretty easy to integrate XSQL.

You can configure spark.sql.catalogImplementation=xsql in spark-defaults.conf，so that spark-shell、spark-sql、spark-submit will enable XSQL syntax. But above configuration only works in bin version, spark.sql.catalogImplementation=xsql is not allowed in raw spark.


Support in browser

It seems like Ganache core is close to being able to run in-browser. It's dependency 'leveldown' require a node environment, this could be swapped out for level-js when in a browser environment. There may be other issues when I dig into this.
Expected Behaviour
Ganache-core runs on html5
Actual Behaviour
Ganache throws an exception when required(), cannot initialize it's leveldown dependency.
Context
It'd be nice to run a private chain in-browser to allow users to testdrive a dapps functionality without using a test network and with minimal or no network usage. Alternatives are to run a websocket to a node server running ganache, or to abstract over the web3 layer entirely.
I'm going to tinker with this idea soon.

@Tristyn this is a great request - something I'd definitely like to see happen. If you'd like to assist with this effort, please have a look at the webpack branch... give the web target a shot and let me know how it works - I haven't had a chance to test it myself yet.

I was just trying the https://github.com/pnpm/pnpm node package manager and it was also throwing an error related to this:
Error: Cannot find module 'abstract-leveldown'
    at Function.Module._resolveFilename (module.js:555:15)
    at Function.Module._load (module.js:482:25)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/onetom/github.com/trufflesuite/ganache-core/lib/database/filedown.js:2:25)
    at Module._compile (module.js:660:30)
...

The fix is to add "abstract-leveldown": "2.7.2" explicitly as a dependency.
I will submit a PR about this later.

Hey @Tristyn @benjamincburns,
Did either of you get anywhere with this?

@yahgwai I didn't investigate any further

I've been experimenting with this and hope to make it a priority soon.

done in<EMAIL_ADDRESS>


Missing symlinks for Android with shlib_variant

We use OpenSSL on Android with multiple architectures. So we need to rename the filename to support that und uses shlib_variant for this. But after that the default settings of CMake of our application cannot find it because OpenSSL 3 misses symlinks libssl.so and libcrypto.so. This works in OpenSSL 1.1.1
How can I enable that symlinks?
diff --git x/Configurations/15-android.conf y/Configurations/15-android.conf
index fd5cd3f478..8a8683b4e4 100644
--- x/Configurations/15-android.conf
+++ y/Configurations/15-android.conf
@@ -225,12 +225,14 @@ my %targets = (
         bn_ops           => add("RC4_CHAR"),
         asm_arch         => 'armv4',
         perlasm_scheme   => "void",
+        shlib_variant    => '_armeabi-v7a',
     },
     "android-arm64" => {
         inherit_from     => [ "android" ],
         bn_ops           => add("RC4_CHAR"),
         asm_arch         => 'aarch64',
         perlasm_scheme   => "linux64",
+        shlib_variant    => '_arm64-v8a',
     },

     "android-mips" => {
@@ -261,12 +263,14 @@ my %targets = (
         bn_ops           => add("RC4_INT"),
         asm_arch         => 'x86',
         perlasm_scheme   => "android",
+        shlib_variant    => '_x86',
     },
     "android-x86_64" => {
         inherit_from     => [ "android" ],
         bn_ops           => add("RC4_INT"),
         asm_arch         => 'x86_64',
         perlasm_scheme   => "elf",
+        shlib_variant    => '_x86_64',
     },

     ####################################################################

Configuring OpenSSL version 3.0.0 for target android-arm
Using os-specific seed configuration
Creating configdata.pm
Running configdata.pm
Creating Makefile.in
Creating Makefile

**********************************************************************
***                                                                ***
***   OpenSSL has been successfully configured                     ***
***                                                                ***
***   If you encounter a problem while building, please open an    ***
***   issue on GitHub <https://github.com/openssl/openssl/issues>  ***
***   and include the output from the following command:           ***
***                                                                ***
***       perl configdata.pm --dump                                ***
***                                                                ***
***   (If you are new to OpenSSL, you might want to consult the    ***
***   'Troubleshooting' section in the INSTALL.md file first)      ***
***                                                                ***
**********************************************************************
[ 66%] Performing configdata step for 'openssl'

Command line (with current working directory = .):

    /usr/bin/perl ../openssl/Configure --prefix=/home/andre/hg/libs/a515/dist --libdir=lib --debug no-camellia no-bf no-aria no-seed no-poly1305 no-srp no-gost no-idea no-mdc2 no-rc2 no-rc4 no-rc5 no-srtp no-sm2 no-sm3 no-sm4 no-ct no-dgram no-cast no-chacha no-blake2 no-rmd160 no-scrypt no-siphash no-whirlpool no-md4 no-des no-tls1 no-tls1-method no-tls1_1 no-tls1_1-method no-tls1_3 no-ssl3 no-ssl3-method no-dtls no-dtls1-method no-dtls1_2-method no-engine no-async no-dso no-comp no-ts no-makedepend no-tests no-legacy shared no-stdio android-arm -fstack-protector-strong -mfloat-abi=softfp -D__ANDROID_API__=23

Perl information:

    /usr/bin/perl
    5.34.0 for x86_64-linux-thread-multi

Enabled features:

    asm
    autoalginit
    autoerrinit
    autoload-config
    bulk
    cached-fetch
    cmac
    cmp
    cms
    deprecated
    dh
    dsa
    ec
    ec2m
    ecdh
    ecdsa
    err
    filenames
    multiblock
    nextprotoneg
    ocb
    ocsp
    pic
    pinshared
    posix-io
    psk
    rdrand
    rfc3779
    secure-memory
    shared
    siv
    sock
    sse2
    ssl
    ssl-trace
    static-engine
    threads
    tls
    ui-console
    tls1_2
    tls1_2-method

Disabled features:

    acvp-tests          [cascade]                OPENSSL_NO_ACVP_TESTS
    afalgeng            [cascade]                OPENSSL_NO_AFALGENG
    aria                [option]                 OPENSSL_NO_ARIA (skip crypto/aria)
    asan                [default]                OPENSSL_NO_ASAN
    async               [option]                 OPENSSL_NO_ASYNC
    bf                  [option]                 OPENSSL_NO_BF (skip crypto/bf)
    blake2              [option]                 OPENSSL_NO_BLAKE2
    buildtest-c++       [default]
    camellia            [option]                 OPENSSL_NO_CAMELLIA (skip crypto/camellia)
    capieng             [cascade]                OPENSSL_NO_CAPIENG
    cast                [option]                 OPENSSL_NO_CAST (skip crypto/cast)
    chacha              [option]                 OPENSSL_NO_CHACHA (skip crypto/chacha)
    comp                [option]                 OPENSSL_NO_COMP (skip crypto/comp)
    crypto-mdebug       [default]                OPENSSL_NO_CRYPTO_MDEBUG
    ct                  [option]                 OPENSSL_NO_CT (skip crypto/ct)
    des                 [option]                 OPENSSL_NO_DES (skip crypto/des)
    devcryptoeng        [default]                OPENSSL_NO_DEVCRYPTOENG
    dgram               [option]                 OPENSSL_NO_DGRAM
    dso                 [option]                 OPENSSL_NO_DSO
    dtls                [option(dtls)]           OPENSSL_NO_DTLS
    dynamic-engine      [cascade]
    ec_nistp_64_gcc_128 [default]                OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]                OPENSSL_NO_EGD
    engine              [option]                 OPENSSL_NO_ENGINE (skip engines, crypto/engine)
    external-tests      [default]                OPENSSL_NO_EXTERNAL_TESTS
    fips                [default]
    fips-securitychecks [cascade]                OPENSSL_NO_FIPS_SECURITYCHECKS
    fuzz-afl            [default]                OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]                OPENSSL_NO_FUZZ_LIBFUZZER
    gost                [option]                 OPENSSL_NO_GOST
    idea                [option]                 OPENSSL_NO_IDEA (skip crypto/idea)
    ktls                [default]                OPENSSL_NO_KTLS
    legacy              [option]
    loadereng           [cascade]                OPENSSL_NO_LOADERENG
    makedepend          [option]
    md2                 [default]                OPENSSL_NO_MD2 (skip crypto/md2)
    md4                 [option]                 OPENSSL_NO_MD4 (skip crypto/md4)
    mdc2                [option]                 OPENSSL_NO_MDC2 (skip crypto/mdc2)
    module              [cascade]
    msan                [default]                OPENSSL_NO_MSAN
    padlockeng          [cascade]                OPENSSL_NO_PADLOCKENG
    poly1305            [option]                 OPENSSL_NO_POLY1305 (skip crypto/poly1305)
    rc2                 [option]                 OPENSSL_NO_RC2 (skip crypto/rc2)
    rc4                 [option]                 OPENSSL_NO_RC4 (skip crypto/rc4)
    rc5                 [option]                 OPENSSL_NO_RC5 (skip crypto/rc5)
    rmd160              [option]                 OPENSSL_NO_RMD160 (skip crypto/ripemd)
    scrypt              [option]                 OPENSSL_NO_SCRYPT
    sctp                [default]                OPENSSL_NO_SCTP
    seed                [option]                 OPENSSL_NO_SEED (skip crypto/seed)
    siphash             [option]                 OPENSSL_NO_SIPHASH (skip crypto/siphash)
    sm2                 [option]                 OPENSSL_NO_SM2 (skip crypto/sm2)
    sm3                 [option]                 OPENSSL_NO_SM3 (skip crypto/sm3)
    sm4                 [option]                 OPENSSL_NO_SM4 (skip crypto/sm4)
    srp                 [option]                 OPENSSL_NO_SRP (skip crypto/srp)
    srtp                [option]                 OPENSSL_NO_SRTP
    stdio               [option]                 OPENSSL_NO_STDIO
    tests               [option]                 OPENSSL_NO_TESTS
    trace               [default]                OPENSSL_NO_TRACE
    ts                  [option]                 OPENSSL_NO_TS (skip crypto/ts)
    ubsan               [default]                OPENSSL_NO_UBSAN
    unit-test           [default]                OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch]         OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]                OPENSSL_NO_WEAK_SSL_CIPHERS
    whirlpool           [option]                 OPENSSL_NO_WHIRLPOOL (skip crypto/whrlpool)
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [option(ssl3-method)]    OPENSSL_NO_SSL3
    ssl3-method         [option]                 OPENSSL_NO_SSL3_METHOD
    tls1                [option(tls1-method)]    OPENSSL_NO_TLS1
    tls1-method         [option]                 OPENSSL_NO_TLS1_METHOD
    tls1_1              [option(tls1_1-method)]  OPENSSL_NO_TLS1_1
    tls1_1-method       [option]                 OPENSSL_NO_TLS1_1_METHOD
    tls1_3              [option]                 OPENSSL_NO_TLS1_3
    dtls1               [option(dtls1-method)]   OPENSSL_NO_DTLS1
    dtls1-method        [option]                 OPENSSL_NO_DTLS1_METHOD
    dtls1_2             [option(dtls1_2-method)] OPENSSL_NO_DTLS1_2
    dtls1_2-method      [option]                 OPENSSL_NO_DTLS1_2_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "qc",
    CC => "gcc",
    CFLAGS => "-Wall -O0 -g",
    CXX => "g++",
    CXXFLAGS => "-Wall -O0 -g",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    asm_arch => "armv4",
    bin_cflags => "-fPIE",
    bin_lflags => "-pie",
    bn_ops => "BN_LLONG RC4_CHAR",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-pthread  -target armv7a-linux-androideabi -gcc-toolchain \$(ANDROID_NDK)/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64 --sysroot=\$(ANDROID_NDK)/platforms/android-23/arch-arm",
    cppflags => "-D__ANDROID_API__=23 -isystem \$(ANDROID_NDK)/sysroot/usr/include/arm-linux-androideabi -isystem \$(ANDROID_NDK)/sysroot/usr/include",
    cxxflags => "-std=c++11 -pthread  -target armv7a-linux-androideabi -gcc-toolchain \$(ANDROID_NDK)/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64 --sysroot=\$(ANDROID_NDK)/platforms/android-23/arch-arm",
    defines => [ "OPENSSL_BUILDING_OPENSSL" ],
    disable => [  ],
    dso_ldflags => "-Wl,-z,defs",
    dso_scheme => "dlfcn",
    enable => [  ],
    ex_libs => "-ldl -pthread",
    includes => [  ],
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DOPENSSL_USE_NODELETE",
    lib_defines => [  ],
    module_cflags => "-fPIC",
    module_cxxflags => undef,
    module_ldflags => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    perl_platform => "Unix",
    perlasm_scheme => "void",
    shared_cflag => "-fPIC",
    shared_defflag => "-Wl,--version-script=",
    shared_defines => [  ],
    shared_extension => ".so",
    shared_ldflag => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,-soname=",
    shared_target => "linux-shared",
    shlib_variant => "_armeabi-v7a",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    BUILDFILE =
    CC = clang
    CFLAGS =
    CPPFLAGS =
    CROSS_COMPILE =
    CXX = clang++
    CXXFLAGS =
    HASHBANGPERL =
    LDFLAGS =
    LDLIBS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = llvm-ar
    ARFLAGS         = rs
    CC              = clang
    CFLAGS          = -Wall -O0 -g -fstack-protector-strong -mfloat-abi=softfp
    CPPDEFINES      = __ANDROID_API__=23
    CPPFLAGS        =
    CPPINCLUDES     =
    CXX             = clang++
    CXXFLAGS        = -Wall -O0 -g -fstack-protector-strong -mfloat-abi=softfp
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = /usr/bin/perl
    RANLIB          = :
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    ../openssl/Configurations/common0.tmpl
    ../openssl/Configurations/unix-Makefile.tmpl
[ 77%] Performing build step for 'openssl'
llvm-ar: warning: creating libssl.a
llvm-ar: warning: creating providers/libdefault.a
llvm-ar: warning: creating libcrypto.a
llvm-ar: warning: creating providers/libcommon.a
[ 88%] Performing install step for 'openssl'
created directory `/home/andre/hg/libs/a515/dist/lib'
*** Installing runtime libraries
install libcrypto_armeabi-v7a.so -> /home/andre/hg/libs/a515/dist/lib/libcrypto_armeabi-v7a.so
install libssl_armeabi-v7a.so -> /home/andre/hg/libs/a515/dist/lib/libssl_armeabi-v7a.so
*** Installing development files
created directory `/home/andre/hg/libs/a515/dist/lib/engines-3'
created directory `/home/andre/hg/libs/a515/dist/lib/ossl-modules'
created directory `/home/andre/hg/libs/a515/dist/bin'
created directory `/home/andre/hg/libs/a515/dist/include'
created directory `/home/andre/hg/libs/a515/dist/include/openssl'
*** Installing modules
*** Installing engines
*** Installing runtime programs
install ../openssl/include/openssl/aes.h -> /home/andre/hg/libs/a515/dist/include/openssl/aes.h
install ../openssl/include/openssl/asn1_mac.h -> /home/andre/hg/libs/a515/dist/include/openssl/asn1_mac.h
install ../openssl/include/openssl/asn1err.h -> /home/andre/hg/libs/a515/dist/include/openssl/asn1err.h
install ../openssl/include/openssl/async.h -> /home/andre/hg/libs/a515/dist/include/openssl/async.h
install ../openssl/include/openssl/asyncerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/asyncerr.h
install ../openssl/include/openssl/bioerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/bioerr.h
install ../openssl/include/openssl/blowfish.h -> /home/andre/hg/libs/a515/dist/include/openssl/blowfish.h
install ../openssl/include/openssl/bn.h -> /home/andre/hg/libs/a515/dist/include/openssl/bn.h
install ../openssl/include/openssl/bnerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/bnerr.h
install ../openssl/include/openssl/buffer.h -> /home/andre/hg/libs/a515/dist/include/openssl/buffer.h
install ../openssl/include/openssl/buffererr.h -> /home/andre/hg/libs/a515/dist/include/openssl/buffererr.h
install ../openssl/include/openssl/camellia.h -> /home/andre/hg/libs/a515/dist/include/openssl/camellia.h
install ../openssl/include/openssl/cast.h -> /home/andre/hg/libs/a515/dist/include/openssl/cast.h
install ../openssl/include/openssl/cmac.h -> /home/andre/hg/libs/a515/dist/include/openssl/cmac.h
install ../openssl/include/openssl/cmp_util.h -> /home/andre/hg/libs/a515/dist/include/openssl/cmp_util.h
install ../openssl/include/openssl/cmperr.h -> /home/andre/hg/libs/a515/dist/include/openssl/cmperr.h
install ../openssl/include/openssl/cmserr.h -> /home/andre/hg/libs/a515/dist/include/openssl/cmserr.h
install ../openssl/include/openssl/comp.h -> /home/andre/hg/libs/a515/dist/include/openssl/comp.h
install ../openssl/include/openssl/comperr.h -> /home/andre/hg/libs/a515/dist/include/openssl/comperr.h
install ../openssl/include/openssl/conf_api.h -> /home/andre/hg/libs/a515/dist/include/openssl/conf_api.h
install ../openssl/include/openssl/conferr.h -> /home/andre/hg/libs/a515/dist/include/openssl/conferr.h
install ../openssl/include/openssl/conftypes.h -> /home/andre/hg/libs/a515/dist/include/openssl/conftypes.h
install ../openssl/include/openssl/core.h -> /home/andre/hg/libs/a515/dist/include/openssl/core.h
install ../openssl/include/openssl/core_dispatch.h -> /home/andre/hg/libs/a515/dist/include/openssl/core_dispatch.h
install ../openssl/include/openssl/core_names.h -> /home/andre/hg/libs/a515/dist/include/openssl/core_names.h
install ../openssl/include/openssl/core_object.h -> /home/andre/hg/libs/a515/dist/include/openssl/core_object.h
install ../openssl/include/openssl/crmferr.h -> /home/andre/hg/libs/a515/dist/include/openssl/crmferr.h
install ../openssl/include/openssl/cryptoerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/cryptoerr.h
install ../openssl/include/openssl/cryptoerr_legacy.h -> /home/andre/hg/libs/a515/dist/include/openssl/cryptoerr_legacy.h
install ../openssl/include/openssl/cterr.h -> /home/andre/hg/libs/a515/dist/include/openssl/cterr.h
install ../openssl/include/openssl/decoder.h -> /home/andre/hg/libs/a515/dist/include/openssl/decoder.h
install ../openssl/include/openssl/decodererr.h -> /home/andre/hg/libs/a515/dist/include/openssl/decodererr.h
install ../openssl/include/openssl/des.h -> /home/andre/hg/libs/a515/dist/include/openssl/des.h
install ../openssl/include/openssl/dh.h -> /home/andre/hg/libs/a515/dist/include/openssl/dh.h
install ../openssl/include/openssl/dherr.h -> /home/andre/hg/libs/a515/dist/include/openssl/dherr.h
install ../openssl/include/openssl/dsa.h -> /home/andre/hg/libs/a515/dist/include/openssl/dsa.h
install ../openssl/include/openssl/dsaerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/dsaerr.h
install ../openssl/include/openssl/dtls1.h -> /home/andre/hg/libs/a515/dist/include/openssl/dtls1.h
install ../openssl/include/openssl/e_os2.h -> /home/andre/hg/libs/a515/dist/include/openssl/e_os2.h
install ../openssl/include/openssl/ebcdic.h -> /home/andre/hg/libs/a515/dist/include/openssl/ebcdic.h
install ../openssl/include/openssl/ec.h -> /home/andre/hg/libs/a515/dist/include/openssl/ec.h
install ../openssl/include/openssl/ecdh.h -> /home/andre/hg/libs/a515/dist/include/openssl/ecdh.h
install ../openssl/include/openssl/ecdsa.h -> /home/andre/hg/libs/a515/dist/include/openssl/ecdsa.h
install ../openssl/include/openssl/ecerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/ecerr.h
install ../openssl/include/openssl/encoder.h -> /home/andre/hg/libs/a515/dist/include/openssl/encoder.h
install ../openssl/include/openssl/encodererr.h -> /home/andre/hg/libs/a515/dist/include/openssl/encodererr.h
install ../openssl/include/openssl/engine.h -> /home/andre/hg/libs/a515/dist/include/openssl/engine.h
install ../openssl/include/openssl/engineerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/engineerr.h
install ../openssl/include/openssl/esserr.h -> /home/andre/hg/libs/a515/dist/include/openssl/esserr.h
install ../openssl/include/openssl/evp.h -> /home/andre/hg/libs/a515/dist/include/openssl/evp.h
install ../openssl/include/openssl/evperr.h -> /home/andre/hg/libs/a515/dist/include/openssl/evperr.h
install ../openssl/include/openssl/fips_names.h -> /home/andre/hg/libs/a515/dist/include/openssl/fips_names.h
install ../openssl/include/openssl/hmac.h -> /home/andre/hg/libs/a515/dist/include/openssl/hmac.h
install ../openssl/include/openssl/http.h -> /home/andre/hg/libs/a515/dist/include/openssl/http.h
install ../openssl/include/openssl/httperr.h -> /home/andre/hg/libs/a515/dist/include/openssl/httperr.h
install ../openssl/include/openssl/idea.h -> /home/andre/hg/libs/a515/dist/include/openssl/idea.h
install ../openssl/include/openssl/kdf.h -> /home/andre/hg/libs/a515/dist/include/openssl/kdf.h
install ../openssl/include/openssl/kdferr.h -> /home/andre/hg/libs/a515/dist/include/openssl/kdferr.h
install ../openssl/include/openssl/macros.h -> /home/andre/hg/libs/a515/dist/include/openssl/macros.h
install ../openssl/include/openssl/md2.h -> /home/andre/hg/libs/a515/dist/include/openssl/md2.h
install ../openssl/include/openssl/md4.h -> /home/andre/hg/libs/a515/dist/include/openssl/md4.h
install ../openssl/include/openssl/md5.h -> /home/andre/hg/libs/a515/dist/include/openssl/md5.h
install ../openssl/include/openssl/mdc2.h -> /home/andre/hg/libs/a515/dist/include/openssl/mdc2.h
install ../openssl/include/openssl/modes.h -> /home/andre/hg/libs/a515/dist/include/openssl/modes.h
install ../openssl/include/openssl/obj_mac.h -> /home/andre/hg/libs/a515/dist/include/openssl/obj_mac.h
install ../openssl/include/openssl/objects.h -> /home/andre/hg/libs/a515/dist/include/openssl/objects.h
install ../openssl/include/openssl/objectserr.h -> /home/andre/hg/libs/a515/dist/include/openssl/objectserr.h
install ../openssl/include/openssl/ocsperr.h -> /home/andre/hg/libs/a515/dist/include/openssl/ocsperr.h
install ../openssl/include/openssl/opensslconf.h -> /home/andre/hg/libs/a515/dist/include/openssl/opensslconf.h
install ../openssl/include/openssl/ossl_typ.h -> /home/andre/hg/libs/a515/dist/include/openssl/ossl_typ.h
install ../openssl/include/openssl/param_build.h -> /home/andre/hg/libs/a515/dist/include/openssl/param_build.h
install ../openssl/include/openssl/params.h -> /home/andre/hg/libs/a515/dist/include/openssl/params.h
install ../openssl/include/openssl/pem.h -> /home/andre/hg/libs/a515/dist/include/openssl/pem.h
install ../openssl/include/openssl/pem2.h -> /home/andre/hg/libs/a515/dist/include/openssl/pem2.h
install ../openssl/include/openssl/pemerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/pemerr.h
install ../openssl/include/openssl/pkcs12err.h -> /home/andre/hg/libs/a515/dist/include/openssl/pkcs12err.h
install ../openssl/include/openssl/pkcs7err.h -> /home/andre/hg/libs/a515/dist/include/openssl/pkcs7err.h
install ../openssl/include/openssl/prov_ssl.h -> /home/andre/hg/libs/a515/dist/include/openssl/prov_ssl.h
install ../openssl/include/openssl/proverr.h -> /home/andre/hg/libs/a515/dist/include/openssl/proverr.h
install ../openssl/include/openssl/provider.h -> /home/andre/hg/libs/a515/dist/include/openssl/provider.h
install ../openssl/include/openssl/rand.h -> /home/andre/hg/libs/a515/dist/include/openssl/rand.h
install ../openssl/include/openssl/randerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/randerr.h
install ../openssl/include/openssl/rc2.h -> /home/andre/hg/libs/a515/dist/include/openssl/rc2.h
install ../openssl/include/openssl/rc4.h -> /home/andre/hg/libs/a515/dist/include/openssl/rc4.h
install ../openssl/include/openssl/rc5.h -> /home/andre/hg/libs/a515/dist/include/openssl/rc5.h
install ../openssl/include/openssl/ripemd.h -> /home/andre/hg/libs/a515/dist/include/openssl/ripemd.h
install ../openssl/include/openssl/rsa.h -> /home/andre/hg/libs/a515/dist/include/openssl/rsa.h
install ../openssl/include/openssl/rsaerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/rsaerr.h
install ../openssl/include/openssl/seed.h -> /home/andre/hg/libs/a515/dist/include/openssl/seed.h
install ../openssl/include/openssl/self_test.h -> /home/andre/hg/libs/a515/dist/include/openssl/self_test.h
install ../openssl/include/openssl/sha.h -> /home/andre/hg/libs/a515/dist/include/openssl/sha.h
install ../openssl/include/openssl/srtp.h -> /home/andre/hg/libs/a515/dist/include/openssl/srtp.h
install ../openssl/include/openssl/ssl2.h -> /home/andre/hg/libs/a515/dist/include/openssl/ssl2.h
install ../openssl/include/openssl/ssl3.h -> /home/andre/hg/libs/a515/dist/include/openssl/ssl3.h
install ../openssl/include/openssl/sslerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/sslerr.h
install ../openssl/include/openssl/sslerr_legacy.h -> /home/andre/hg/libs/a515/dist/include/openssl/sslerr_legacy.h
install ../openssl/include/openssl/stack.h -> /home/andre/hg/libs/a515/dist/include/openssl/stack.h
install ../openssl/include/openssl/store.h -> /home/andre/hg/libs/a515/dist/include/openssl/store.h
install ../openssl/include/openssl/storeerr.h -> /home/andre/hg/libs/a515/dist/include/openssl/storeerr.h
install ../openssl/include/openssl/symhacks.h -> /home/andre/hg/libs/a515/dist/include/openssl/symhacks.h
install ../openssl/include/openssl/tls1.h -> /home/andre/hg/libs/a515/dist/include/openssl/tls1.h
install ../openssl/include/openssl/trace.h -> /home/andre/hg/libs/a515/dist/include/openssl/trace.h
install ../openssl/include/openssl/ts.h -> /home/andre/hg/libs/a515/dist/include/openssl/ts.h
install ../openssl/include/openssl/tserr.h -> /home/andre/hg/libs/a515/dist/include/openssl/tserr.h
install ../openssl/include/openssl/txt_db.h -> /home/andre/hg/libs/a515/dist/include/openssl/txt_db.h
install ../openssl/include/openssl/types.h -> /home/andre/hg/libs/a515/dist/include/openssl/types.h
install ../openssl/include/openssl/uierr.h -> /home/andre/hg/libs/a515/dist/include/openssl/uierr.h
install ../openssl/include/openssl/whrlpool.h -> /home/andre/hg/libs/a515/dist/include/openssl/whrlpool.h
install ../openssl/include/openssl/x509err.h -> /home/andre/hg/libs/a515/dist/include/openssl/x509err.h
install ../openssl/include/openssl/x509v3err.h -> /home/andre/hg/libs/a515/dist/include/openssl/x509v3err.h
install ./include/openssl/asn1.h -> /home/andre/hg/libs/a515/dist/include/openssl/asn1.h
install ./include/openssl/asn1t.h -> /home/andre/hg/libs/a515/dist/include/openssl/asn1t.h
install ./include/openssl/bio.h -> /home/andre/hg/libs/a515/dist/include/openssl/bio.h
install ./include/openssl/cmp.h -> /home/andre/hg/libs/a515/dist/include/openssl/cmp.h
install ./include/openssl/cms.h -> /home/andre/hg/libs/a515/dist/include/openssl/cms.h
install ./include/openssl/conf.h -> /home/andre/hg/libs/a515/dist/include/openssl/conf.h
install ./include/openssl/configuration.h -> /home/andre/hg/libs/a515/dist/include/openssl/configuration.h
install ./include/openssl/crmf.h -> /home/andre/hg/libs/a515/dist/include/openssl/crmf.h
install ./include/openssl/crypto.h -> /home/andre/hg/libs/a515/dist/include/openssl/crypto.h
install ./include/openssl/ct.h -> /home/andre/hg/libs/a515/dist/include/openssl/ct.h
install ./include/openssl/err.h -> /home/andre/hg/libs/a515/dist/include/openssl/err.h
install ./include/openssl/ess.h -> /home/andre/hg/libs/a515/dist/include/openssl/ess.h
install ./include/openssl/fipskey.h -> /home/andre/hg/libs/a515/dist/include/openssl/fipskey.h
install ./include/openssl/lhash.h -> /home/andre/hg/libs/a515/dist/include/openssl/lhash.h
install ./include/openssl/ocsp.h -> /home/andre/hg/libs/a515/dist/include/openssl/ocsp.h
install ./include/openssl/opensslv.h -> /home/andre/hg/libs/a515/dist/include/openssl/opensslv.h
install ./include/openssl/pkcs12.h -> /home/andre/hg/libs/a515/dist/include/openssl/pkcs12.h
install ./include/openssl/pkcs7.h -> /home/andre/hg/libs/a515/dist/include/openssl/pkcs7.h
install ./include/openssl/safestack.h -> /home/andre/hg/libs/a515/dist/include/openssl/safestack.h
install ./include/openssl/srp.h -> /home/andre/hg/libs/a515/dist/include/openssl/srp.h
install ./include/openssl/ssl.h -> /home/andre/hg/libs/a515/dist/include/openssl/ssl.h
install ./include/openssl/ui.h -> /home/andre/hg/libs/a515/dist/include/openssl/ui.h
install ./include/openssl/x509.h -> /home/andre/hg/libs/a515/dist/include/openssl/x509.h
install ./include/openssl/x509_vfy.h -> /home/andre/hg/libs/a515/dist/include/openssl/x509_vfy.h
install ./include/openssl/x509v3.h -> /home/andre/hg/libs/a515/dist/include/openssl/x509v3.h
install libcrypto.a -> /home/andre/hg/libs/a515/dist/lib/libcrypto.a
install libssl.a -> /home/andre/hg/libs/a515/dist/lib/libssl.a
created directory `/home/andre/hg/libs/a515/dist/lib/pkgconfig'
install libcrypto.pc -> /home/andre/hg/libs/a515/dist/lib/pkgconfig/libcrypto.pc
install libssl.pc -> /home/andre/hg/libs/a515/dist/lib/pkgconfig/libssl.pc
install openssl.pc -> /home/andre/hg/libs/a515/dist/lib/pkgconfig/openssl.pc
[100%] Completed 'openssl'
[100%] Built target openssl

$ ll dist/lib
insgesamt 20M
drwxr-xr-x 2 andre users 4,0K 14. Sep 14:09 engines-3
-rwxr-xr-x 1 andre users 9,6M 14. Sep 14:09 libcrypto_armeabi-v7a.so
-rwxr-xr-x 1 andre users  11M 14. Sep 14:09 libssl_armeabi-v7a.so
drwxr-xr-x 2 andre users 4,0K 14. Sep 14:09 ossl-modules
drwxr-xr-x 2 andre users 4,0K 14. Sep 14:09 pkgconfig

A point is that for Android shared_extension does not contain .$(SHLIB_VERSION_NUMBER), thus sharedlib_simple returning undef regardless of shlib_variant.
A quick workaround is shown below:
--- openssl-3.0.0/Configurations/platform/Unix.pm.orig
+++ openssl-3.0.0/Configurations/platform/Unix.pm
@@ -63,7 +63,7 @@
 }

 sub sharedlib_simple {
-    return undef if $_[0]->shlibext() eq $_[0]->shlibextsimple();
+    #return undef if $_[0]->shlibext() eq $_[0]->shlibextsimple();
     return platform::BASE::__concat($_[0]->sharedname_simple($_[1]),
                                     $_[0]->shlibextsimple());
 }

Note that this is not a decent fix because it definitely does not work when shlib_variant is not defined (or is empty).

@misery have you tried the multilib attribute?  That one is specifically designed for what you're trying to solve, i.e. it's a bit like shlib_variant, but the string is added on to the library installation directory name instead of on the library name itself.  That's generally seen as a safer way to do what you're trying to do.

If you insist on using shlib_variant this way, @xtkoba got it almost right...  at least they chose a good spot.  Here's the more proper fix:
diff --git a/Configurations/platform/Unix.pm b/Configurations/platform/Unix.pm
index c7d7d9eb80..a2ee99710b 100644
--- a/Configurations/platform/Unix.pm
+++ b/Configurations/platform/Unix.pm
@@ -63,7 +63,9 @@ sub sharedname_simple {
 }

 sub sharedlib_simple {
-    return undef if $_[0]->shlibext() eq $_[0]->shlibextsimple();
+    return undef
+        if ($_[0]->sharedname($_[1] eq $_[0]->sharedname_simple($_[1]))
+            && $_[0]->shlibext() eq $_[0]->shlibextsimple());
     return platform::BASE::__concat($_[0]->sharedname_simple($_[1]),
                                     $_[0]->shlibextsimple());
 }

Thank you very much. I will look in multilib later. But this requires to refactor our system.
I tried your patch... but it doesn't work here. Still no symlinks and I get some warnings now.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.

The parentheses are wrong in the patch. It should be $_[0]->sharedname($_[1]) eq $_[0]->sharedname_simple($_[1])

Thanks, it works. But still some warnings.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.
Use of uninitialized value in string eq at /.../src/openssl/Configurations/platform/Unix.pm line 67.

This should be a better patch.
See #16608
diff --git a/Configurations/platform/Unix.pm b/Configurations/platform/Unix.pm
index c7d7d9eb80..efa3fdc84f 100644
--- a/Configurations/platform/Unix.pm
+++ b/Configurations/platform/Unix.pm
@@ -63,7 +63,9 @@ sub sharedname_simple {
 }

 sub sharedlib_simple {
-    return undef if $_[0]->shlibext() eq $_[0]->shlibextsimple();
+    return undef
+        if ($_[0]->sharedname($_[1]) eq $_[0]->sharedname_simple($_[1])
+            && $_[0]->shlibext() eq $_[0]->shlibextsimple());
     return platform::BASE::__concat($_[0]->sharedname_simple($_[1]),
                                     $_[0]->shlibextsimple());
 }


Can't download from mangareader.net

Thx. Try now, please.

use
pip install -U manga-py

for update package


feat: integrate yen and add support to ignore file patterns

Hi! I was looking at pycify and packaged, awesome projects!
I have added

support to ignore certain file patterns, primarily because setup.py kept getting replaced and also to ignore some other python files that need not be replaced
added yen so that pycify can allow compiling with different versions if a python version is provided (Please check my PR on packaged for a use-case)

Do let me know if anything needs to be changed 🙇

eek forgot about mypy, will check. Maybe wanna use a pre-commit hook?

I'm going to add tests to this, since the logic is now complex enough, and I was not actually expecting this to be used by anyone seriously.


I have to press enter to change the value, even though the editor shows the value I entered at all times

Operating system or device - Godot version:
current master branch commit id: afbe013ba12d68f20ef1dfe2d7a895105a440bd9
Issue description (what happened, and what was expected):
I was trying to change the FPS of an animated script and when I typed in 10 instead of 5 and hit play it didn't change anything. I later understood it's because I never pressed Enter after changing the value. Now I believe if there is no save button some where that I can press then I expect my setting to be applied right after I type in the value. Having to press Enter wasn't really obvious to me, I thought it was a bug and kept trying to fix it. especially that the value I entered does not change back when I leave the screen or click away or play the game or whatever.
So what do you guys think?
Steps to reproduce:
Try to change the value of any property without pressing enter.
Link to minimal example project (optional but very welcome):

I agree.
Strangely enough, some values can actually be changed without pressing Enter while others can't.
Example: Rotation and Opacity can be changed without pressing Enter, while Position and Scale needs the Enter button pressed in order to change.

@jesperkondrup Not strange at all, this just shows it affects only Vector2 and similar types of properties.

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

This issue is still relevant in 3.1

Tested in 3.1.1 stable. When you press outside the box, the value is stored, which means the issue is fixed.


Upgrade HttpClient to a module

HttpClient is an opinionated wrapper around fetch.
I'm going to move this to its own repo/npm module.   There's more I'd like to do with and lots more tests.
Because it has usefulness outside this repo, we're going to set it free.

Oh noes, not another npm module dependency, the world will end

Came up with this:   https://github.com/skellock/apisauce
Next step:  bring in a PR to show how it works.  See if y'all like it enough to include.

Status update.
There's an incoming patch for React Native which will bestow XMLHttpRequest the power to user ontimeout and onerror.  I'm hoping for 0.24.  They're just doing the rebase dance right now.
Once that's in master.  I'd be comfortable declaring apisauce ready for ignite-worthy.
Tracking here:  https://github.com/skellock/apisauce/issues/7

Ok, that PR just landed in master.  I'll get to work on this integration.

https://github.com/infinitered/ignite/pull/62
The PR for the ontimeout and onerror will be arriving in 0.25.  I'll circle back when 0.25 lands and make sure everything is working as you'd expect.

YES!  Looking great!


Add of partner page

Fixes issue #30
Features

Responsive in for all screen width
Gives a list of all organization, partner with HospitalRun

cc: @tangollama @jglovier

@jglovier Thanks for your review. It is really helpful .I will start working on the suggested changes as soon as possible.

@jglovier @tangollama Sorry for the delay. I have worked on the suggested changes and made required modifications. Kindly review the PR once again and let me know if it requires improvements.

@jglovier I have made the modifications. Kindly verify if it needs further modifications.


The example Heroku app doesn't apply cors (Allows everything)

To reproduce it just open the devtools. Click on any request and check the response headers...

Hello, the example seems to be working as it was built. All the examples allow all origins except the one that is supposed to fail. You cam find the source code here: https://github.com/troygoode/node-cors-server/blob/master/server.js

@dougwilson Which is the origin that it is supposed to fail for the DELETE /complex-cors endpoint?

Probably I'm getting CORS wrong, but the thing is that you can define on the backend which domains can receive a response from the endpoint.
Example:
If you setup CORS to respond to requests coming from https://www.test.com any request not coming from that origin would fail. Even if you make a request directly from the browser (in the case of GET requests, without any CORS header defined).

The example app is set up to allow all origins.


Setting up local dev with plone-react

I've just started on setting up plone-react locally right after the sprint and I seem to encountering a few issues and doubts.
Since I already have Plone installed, I'm using a Plone 5.1 instance running on localhost:8080 as the backend api rather than the one provided with the project.
On running yarn dev, it seems to load up fine but there's no content displayed and I'm unable to login, giving error message JWT auth plugin not installed
Screenshot:

@tisto @robgietema @sneridagh Any help would be appreciated!

It seemed to be an issue with the Plone instance I had running. I built a new one using the buildout config in the api folder and it's working fine now. Thanks anyway and closing the issue.


safari push notification not working

hello
Web push notification working on chrome and fire fox but in safari browser it not working how to do anyone please help me

It doesn't work for me either. Android, Linux and Windows work, but ios and macos don't work.


Add ability to create code-snippets from the UI

Now that metadata instance can be managed via the REST API, we should minimally add the ability for users to create, update, and delete code-snippets from the web frontend.

Here are a couple ideas for the UI of creating / editing / deleting code-snippets:

Edit snippets / snippet info within the widget without a dialog:

There would be a "save" button near the other action buttons.
At the top of the code snippets widget, there would be an "Add snippet" button that would create a blank snippet

name: 'untitled'
coding language: ''
empty code snippet preview, but it has a code editor embedded in it for easy changes to code snippets

Right click the name of the snippet to show a context menu that allows you to rename the snippet or change the coding language (in a dialog)

Open a dialog that prompts for all fields (name, language, code), and autofills these fields when editing a snippet

Though I like the idea of editing directly in the current UI, I believe the cleaner UX would be the second option:

Open a dialog that prompts for all fields (name, language, code), and autofills these fields when editing a snippet
which would be opened via an edit button or add new button (in the header) like you described.

My only ask is that users not feel like they're filling in an array when typing each line of their code since that's how it gets stored.  The code portion should feel as natural as possible.
I think it would be ideal if they could also have language-sensitive contexts (highlighting, perhaps even IntelliSense) during their creation and perhaps that's something someone can contribute downstream if it's really difficult.  (I have no idea really.)

Agree with @ajbozarth on the second option, with add new button in the header, and edit/delete buttons on each snippet item.
Also agree with @kevin-bates about not making the user construct the array of lines themselves. Maybe the codemirror option can come later as an enhancement since that's what's planned for the preview box as well.


PR for issue #18617

PR for issue #18617

/close
because I don't think this is the right fix, and I didn't see any follow up.


pipeline_readqc

To do (not urgent)
Remove dependency on path set in ini file to fastqc contamiants list for automatic removal of non-NoHit sequences when not using a custom contaminants list

Fixed in:
https://github.com/CGATOxford/CGATPipelines/pull/287
Thanks!