text:
Let config nodes be easily findable

by click on number in config menu

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
It would be useful (occasionally) to be able to find which nodes are using a particular config node. This PR does that by making the number field to the right of the node identifier in the config node window into a button that opens the search window with the result of the search for that config node id.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[X] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

messed up extra file - closing

Coverage decreased (-0.05%) to 76.319% when pulling f484793a271ffba427611435c779b9f10764350a on config-search into 0529eed0c9c1f9c0d60b1f2a1c88fe7c1b6e0d75 on dev.

authors: coveralls dceejay


text:
src: WIP Node.js build pack using ubi images

Initial plumbing for Node.js build pack using
Node.js ubi images, much of which is a stripped
down version of the functions buildpack for
Node.js in https://github.com/boson-project/buildpacks
Signed-off-by: Michael Dawson mdawson@devrus.com

@lholmquist thanks!

source: gharchive/pull-request

repo: nodeshift/buildpacks

license_type: permissive

license_source: github-api


text:
General Ledger

Add Basic Double entry Accounting.
Details
Models
Following models are required for basic GL entries:

[ ] General ledger
The Financial Data

Date
Account
Reference
Description
Debit
Credit
Reconciled

[ ] Chart Of Accounts
Available Accounts

Name
Account Number
Parent
Category (Asset/liability/equity/income/expense)
Sub-Category (Bank/Cash etc)
Type (debit/credit)

[ ] Cost Centers
Cost Center Codes

Requirements

[ ] ALL entries must ensure debit + credit = 0

marked this issue as blocking #96

marked this issue as related to #88

source: gharchive/issue

license: MIT


text:
Usage of Trait::method syntax on globals results in monomorphisation ICE.

Aim
I wanted to have a structure with multiple trait From implementations and use From::from(...) syntax to create a global variable.
Expected Behavior
This code compiles:
struct Struct {
    field: Field
}

impl From<Field> for Struct {
    fn from(field: Field) -> Self {
        Struct { field }
    }
}

impl From<u64> for Struct {
    fn from(num: u64) -> Self {
        Struct { field: num as Field }
    }
}

global s: Struct = From::from(0);

fn main() {
    println(s);
}

Bug
The code above causes compilation panic. I also can't use Struct::from(...) syntax because it causes compiler error: 'Could not resolve 'from' in path'.
To Reproduce

Try to compile the code above.

Project Impact
Nice-to-have
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
Binary (noirup default)
Nargo Version
nargo version = 0.29.0 noirc version = 0.29.0+2da28997dbedce4a00d2162eddb57564bdb23546
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

This is unrelated to multiple implementations of the same trait as I get the same ICE when commenting out either of the trait impls.
Struct::from issue is due to https://github.com/noir-lang/noir/issues/4943#issuecomment-2083486013

For completeness the error is
% nargo compile                                                                                ~/aztec-packages/noir/noir-repo/temp tf/native-recursion tom-box
The application panicked (crashed).
Message:  ICE: missing trait impl - should be caught during type checking
Location: compiler/noirc_frontend/src/monomorphization/mod.rs:1027

This program:
global s: BoundedVec<Field, 2> = From::from([0]);

fn main() {
    println(s);
}

now gives this error:
error: No impl found due to prior type error
  ┌─ src/main.nr:1:34
  │
1 │ global s: BoundedVec<Field, 2> = From::from([0]);
  │                                  ----------
  │
  = Call stack:
    1. src/main.nr:1:34

So at least no panic, but I think it should compile so I'll take a look at this.

authors: Pasifaee TomAFrench asterite

repo: noir-lang/noir


text:
Cannot use hardware back button on another view

Cannot use hardware back button on another view. Its getting app close. I used pushState: true, swipePanel: 'left' params as well.

Push State is supported only by Main view. As for this issue, it is Android-specific. Check the Forum, there were a lot of solutions for that


text:
Swiper autoplay in Tabbar Page

I found that, in Tabbar , View1 change to View2 or View3 , about 5 sec. later,  Timer in View1 had Cleaned , so my Swiper in View1 can not autoplay ,   we must restart timer when Tabbar change to View1.
the method startAutoplay()  include
   if (typeof s.autoplayTimeoutId !== 'undefined') return false;

and  stopAutoplay() include:
   if (!s.autoplayTimeoutId) return;

so can not use to restart timer, but we can use undocument method  pauseAutoplay()
   mySwiper.autoplayPaused = false;
   mySwiper.pauseAutoplay(0);

if i set loop:true ,it don't work,  i think swiper need to add a method to restart timer when switch View.

It won't be added as there are too many ways which can produce this issue which is cased by swiper hidden container. Just use Swiper's stopAutoplay when tab with it becomes hidden and startAutoplay when it becomes visible again.


text:
Diagonal Swipes

Check that this is really a bug

[X] I confirm

Reproduction link
https://swiperjs.com/
Bug description
on iOS devices (tested with Safari & Brave), swiping horizontally also triggers a vertical scroll.
This was not the case with Swiper version ^8.
It seems like the transition ends immediately.
Please check the screen recordings.
Expected Behavior
I should be either swiping horizontally or scrolling vertically, but not both.
Here's an example from macOS Brave (Chromium)
https://user-images.githubusercontent.com/71325531/224348667-cc139c64-19ff-451a-8bce-facd328f027c.mov
Actual Behavior
When I scroll slightly vertically, the swiper.js slide transition starts but almost immediately ends. From there, I start to scroll vertically.
https://user-images.githubusercontent.com/71325531/224347648-757377b4-239d-4a22-95f8-09309bd7f243.mp4
Swiper version
9.1.0
Platform/Target and Browser Versions
ios, Safari
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

Are you on iOS 16.2?

I'm on iOS 16.1.1

Try on 16.2

Try on 16.2

Yes, the issue persists on iOS 16.2 and 16.3 too.

15.5 also

ios 15.7.9
v.10.2.0
the issue persists

Swiper 11.0.4 works near perfectly for me. I managed to trigger one single diagonal swipe but I cannot replicate it no matter how much I try.

authors: DzmitryShamal dkornilove epetousis nolimits4web selcuk-sahin


text:
Hardening the withdrawal mechanism

In the Bitcoin Peg doc, it says:

To disburse funds from the reserve, more than two-thirds of the validator set must sign the Bitcoin transaction (weighted by voting power).

There is a safety mechanism, described here:

[W]e can hold these signatories accountable by creating a rule on the peg network to remove voting power and tokens from any signatory which has signed an unexpected transaction, also known as slashing. The likelihood of collusion is then reduced since potential colluders would be able to gain from reporting malicious signatures to the peg network in a signatory fraud proof transaction.

Taken together, we can assume the funds held in the reserve address are safe if at least 1/3 of the signatories (as weighted by voting power) are honest.
However the system is NOT safe in two specific scenarios:

Where one party controls 2/3+1 voting power, or
Multiple parties collude to control 2/3+1 voting power, for example multiple mining pools.

In both cases it becomes possible for 2/3+1 signatories to ~instantly (within one mainchain block) steal all funds held in the reserve address, with no practical recourse to victims.
Since voting power can be acquired by bitcoin miners for "free" simply by mining bitcoin, the marginal cost of acquiring voting power is near zero making this attack feasible as soon as the discounted value of future fees/demurrage that could be earned by validators for acting honestly is worth less than the value of BTC that could be stolen today (i.e. whenever 2/3+1 signatories decide "a bird in hand is worth two in the bush"). If the voting power tokens take on a secondary market value that miners would be giving up by attacking Nomic, this increases the value of BTC that can be safely held in the peg to be any amount less than the current market value of 2/3+1 voting power (assuming sufficient liquidity to sell that much voting power) plus the discounted value of future fees/demurrage that could be earned by voting honestly.
Hardening the withdrawal mechanism is a problem all two-way bitcoin pegs have to overcome. I've written about some of the techniques used by other two-way pegs here. There are three main ways that other two-way pegs try to harden the withdrawal mechanism:

A withdrawal delay (e.g. Drivechain)
A bond (e.g. tBTC)
Hardware security modules (HSM) or trusted execution environments (TEE) (e.g. RSK, pTokens)

I think it's worth thinking about whether Nomic can implement one or more of these methods to further harden the withdrawal mechanism.
Withdrawal delay
In the case of a withdrawal delay, this method is relying firstly on game theory and should validators ignore the game theory and go ahead with an attack, then secondarily on time and vigilance. The idea here is that if validators do try to steal from the reserves, there is a delay between the time that they start their attack and when the attack is complete. In the case of Drivechain this delay is six months. If users of a drivechain that is under attack notice at any time during these six months that an attack is under way, they can organize user-activated soft fork (UASF) on the bitcoin mainchain that rejects any blocks supporting the attack transaction. The game theory here suggests that as long as this defense is known and plausible, validators will never try the attack in the first place. But if validators do still attempt the attack, then users can organize to stop the attack and most likely won't trust that drivechain going forward, thus validators forfeit any future fees they could have earned from the drivechain had they simply remained honest and not killed the goose that lays golden eggs.
See "Does Drivechain rely on a UASF to prevent a sidechain theft?" in the Drivechain FAQ for more info about this.
Question: Is it possible to build a two-step withdrawal mechanism with a delay, to mimic the type of withdrawal delay implemented by Drivechain? Step one would be to "announce" the withdrawal, so that everyone can observe a withdrawal will happen at some future date (along with the details of the withdrawal, such as which addresses the withdrawal will be sent to). Step two happens much later, when the withdrawal actually becomes valid and withdrawal recipients can actually move the coins that have been withdrawn to their designated addresses.
Bond
In the case of a bond, the idea here is for validators to have some value at stake above and beyond the cost simply to become a validator. In the case of tBTC the bond is equal to 1.5x the value of the BTC held by signatories, and signatories can be individually targeted for slashing if they behave maliciously. 66% of the value of the bond is used to recapitalize the system, and the rest goes to whoever reported the theft attempt. Nomic also has slashing, however slashing cannot be enforced in the 2/3+1 attacker scenario since the attacker could censor any slashing transactions. Some ideas for how Nomic could implement a bond:

Implement a tBTC-like system on Nomic. This would necessarily limit the value of BTC that could be deposited on Nomic to be less than the value of collateral assets at stake. If voting power tokens were used as the collateral asset, then this would also ensure that an attack is (almost) never profitable. More info about the tBTC security model can be found here.
Implement a bond on another chain, with a cryptoeconomic dispute resolution system as "enforcer" of the bond. For example, Nomic signatories could be required to deposit a bond into a smart contract on Ethereum and increase the size of their bond as the value of BTC held in the Nomic reserve address increases. The value of collateral in the bond contract would always have to be greater than the value of BTC held in the reserve address. If the signatories ever tried to steal BTC from the reserve address, then a cryptoeconomic dispute resolution system such as Aragon Court could be used to report the theft and slash the bond. This adds an additional cost to attacking the Nomic peg: the cost of attacking the dispute resolution mechanism used to slash the bond. Not indefeasible, but it does increase the margin of safety of the withdrawal mechanism.

HSM & TEE
In the case of HSMs and TEEs the main idea here is that signatories have to use some kind of secure hardware that the signatory is unable to access the contents of. This secure hardware will enable third parties (such as sidechain users and other signatories) to remotely confirm that the signatory is running the correct software using remote attestation. The software running in the secure hardware would ensure that the signatory only signs honest withdrawal transactions. Secure hardware from multiple manufacturers could be used to prevent any single point of failure. The main risk here is new types of side channel and direct attacks that compromise the integrity of the secure hardware, thus rendering it useless and putting users into a false sense of security. I wouldn't consider this a silver bullet solution but rather one component of an overall defense in depth strategy.
Conclusion
Nomic is an interesting system and it does seem that the peg can be defended up to a point, the question is can we harden the system even further to increase the value of BTC that can be held in the system? I think the answer is yes! There is no silver bullet, especially if we are attempting to work within the constraints of the existing bitcoin protocol, but I believe a combination of techniques such as those described above could be used together to strengthen the peg, harden the withdrawal mechanism, and enable even more BTC to safely enter the Nomic system than is possible under the current design.
Disclosure: I work at the Aragon Association, which sponsors the development of the aforementioned Aragon Court protocol. I am not writing officially on behalf of the Association, I am just a sidechain enthusiast who sees a potential use here for the technology I work on at my day job :)

@john-light Thank you for the thoughtful analysis.
Withdrawal delay
This mechanism is compelling, but the huge cost of locking BTC for 6 months increases costs and hurts UX in a huge way. We could consider something like this in a future version, where the majority of the reserves are delayed like this (the equivalent of cold storage for the peg), but a portion is kept without a delay in order to rapidly process most withdrawals (assuming the amount of BTC in reserve doesn't fluctuate significantly).
tBTC comparison/Bonds
Thanks for raising the issue of the difference between our slashing model and tBTC's. To reiterate in my own words, while both systems slash signatories for signing unexpected Bitcoin transactions, a consensus takeover of the Nomic chain (which means power to censor transactions) would allow signatories to steal the reserve and still be able to sell off their bonds. Whereas in tBTC, even if signatories had a hashrate majority, they would not be able to reclaim their bond because the owner of the BTC did not close the deposit.
But in our design this is actually a relatively easy fix - we can ensure an attack leads to losing stake (even when censoring fraud proofs) by only unbonding stake after proof that the expected checkpoint transaction was accepted on the Bitcoin blockchain. This means that if signatories steal the reserves by creating an unexpected checkpoint transaction, they will not be able to create a Bitcoin SPV inclusion proof for the expected checkpoint, and their bonds will not be released to them. So even though they can freely censor transactions on Nomic, we assume they cannot pull off a significant reorg of Bitcoin (we can tune the number of confirmations to the required security level).
So thanks for pointing that out, excited to make this even more secure!
HSM & TEE
I very much agree that HSM's are a good best practice for key management on high-profile nodes like signatories. This is already standard in the Cosmos world, we'll just have to ensure we build out the proper tools for doing this with the Bitcoin keys as well as the Tendermint validator keys.
As for TEEs, I'm not currently a huge fan since it seems like it requires a lot of trust in hardware manufacturers (of course we do already trust that they will execute our code correctly, but this goes a step beyond that). If TEEs worked really well, it seems we could do away with PoW and PoS which logically is a pretty big jump. But if there is a way to opt in to adding security with TEEs without any possible downsides then of course it is worth investigating.

the huge cost of locking BTC for 6 months increases costs and hurts UX in a huge way.

The way the UX can be improved while still preserving security is by having exchangers who will ~instantly trade NBTC for BTC. This could even be done in a trust-minimized way with atomic swaps. The cost might be a bit more than going through the normal withdrawal process but that is the price of having the added security of the withdrawal delay plus the convenience of instant exchange via trust-minimized exchangers. That said your proposed method of having most reserves subject to withdrawal delay and some clearing instantly is an interesting middle-ground!

So thanks for pointing that out, excited to make this even more secure!

Nice :sunglasses:

As for TEEs, I'm not currently a huge fan since it seems like it requires a lot of trust in hardware manufacturers (of course we do already trust that they will execute our code correctly, but this goes a step beyond that). If TEEs worked really well, it seems we could do away with PoW and PoS which logically is a pretty big jump. But if there is a way to opt in to adding security with TEEs without any possible downsides then of course it is worth investigating.

Fair enough! I'm also skeptical of TEEs but have seen several projects pull off some black magic using them e.g. pTokens so figured I'd mention in case there's something I'm missing/ something worth considering there.

authors: john-light mappum

repo: nomic-io/bitcoin-peg


text:
[bug] Potential stack overflow on EventLoop.poll()

Here, when the channel successfully sends the records, the poll() function gets called and the current frame stuck in the stack.
Therefore, the stack will keep growing infinitely if the channel kept successfully sending the records
https://github.com/nomisRev/kotlin-kafka/blob/9d7604f1a1d148b14578ae10979a02242a09ed64/src/main/kotlin/io/github/nomisRev/kafka/receiver/internals/EventLoop.kt#L124
https://github.com/nomisRev/kotlin-kafka/blob/9d7604f1a1d148b14578ae10979a02242a09ed64/src/main/kotlin/io/github/nomisRev/kafka/receiver/internals/EventLoop.kt#L173

Hey @lsafer-meemer,
Thank you or the bug report, and your interest in the project! Is there a reproducible snippet? We're missing quite some tests, complex scenarios are not always easy to write..
This should be testable by configuring a very low max.poll.size, and probably low poll time, to pull 20_000 records 1 by 1, successfully. A stack unsafe method should result in StackOverflow after 20_000 recursions, but we can also test 200_000 to be sure.
I'd love a contribution for this if you're interested 🙏

Sorry, I actually don't know how the project works 😥
I just found it when I was randomly exploring and thought it was an issue 😬

authors: lsafer-meemer nomisRev

repo: nomisRev/kotlin-kafka


text:
Handle color keywords

getValues "color" should return a list of color keywords
Same for getValues "background-color" and getValues "border-color"
Please add some tests, don't forget to test transparent and currentColor

I think we should be able to get the color keywords list from csstree.
I just realized there are more *-color css properties, ideally we should use csstree syntax to find out which property accepts <color> value, and return the color keywords in getValues "*-color".

I will be attempting to solve this issue 😄

repo: nonbili/purescript-css-properties


text:
Code [PHP] array to csv

function csvstr(array $fields) : string
{
$f = fopen('php://memory', 'r+');
if (fputcsv($f, $fields) === false) {
return false;
}
rewind($f);
$csv_line = stream_get_contents($f);
return rtrim($csv_line);
}

Deployed: https://onelinerhub.com/php/array_to_csv

repo: nonunicorn/onelinerhub


text:
Fixing db unique enforcement for system store

Signed-off-by: jackyalbo jacky.albo@gmail.com
Explain the changes

As postgres doesn't restrict uniqueness as mongo does. (If part of the key - deleted in our case is not in the new row - it will not throw the insert operation) Will remove deleted from the key, but also will remove all deleted rows from the index so new row with same name can be created if previous one was already deleted.

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

do we need to change also in migration_to_postgres?
https://github.com/noobaa/noobaa-core/blob/31cd9ccf2100fd74e6d38fb05f5246b1958c5fbd/src/upgrade/migration_to_postgres.js#L44-L62
Also, make sure it works after upgrading from previous versions. it should be ok but check that there are no conflicts in names or something else. I don't think there should be a problem with leaving old indexes around, but it's also worth testing

do we need to change also in migration_to_postgres?
https://github.com/noobaa/noobaa-core/blob/31cd9ccf2100fd74e6d38fb05f5246b1958c5fbd/src/upgrade/migration_to_postgres.js#L44-L62
Also, make sure it works after upgrading from previous versions. it should be ok but check that there are no conflicts in names or something else. I don't think there should be a problem with leaving old indexes around, but it's also worth testing

Updated migration_to_db as well - also updated it to have the same order of the fields.
Checked upgrade and it seems to just add a new index - the new one indeed blocks duplicate rows - (tried from psql)

authors: dannyzaken jackyalbo

repo: noobaa/noobaa-core


text:
RPM build updates for downstream builds

Explain the changes

This adds SELinux support to the RPM generation
It stores src.rpm on the system as well
It fixes the syslog and logrotate file locations during the build
It unifies the treatment of the files inside the RPM (via symlinks)

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

Run make rpm on a Fedora host

[ ] Doc added/updated
[ ] Tests added

Are we going to use SRPMs for something?

@tangledbytes Yes, it is used downstream to produce the build, our downstream build system basically consumes the src.rpm. With these changes, I can consume the src.rpm directly. As such, we don't actually need the RPM itself downstream but it is not taking too long so it is OK to have both.
Also, with the src.rpm you can easily produce the build for as many architectures as you desire.

Can we merge this now?

@b-ranto can you please rebase? I will merge it.

Sure, I have rebased it earlier today but rebased it now as well.

authors: b-ranto tangledbytes


text:
fatal error: typeMismatch(Swift.Dictionary<Swift.String, Any>, ...

hexaville deploy <ProjectName>

を実行して、以下のエラーになりました。
どう解決すればよろしいでしょうか？
Uploading code to s3.....
fatal error: typeMismatch(Swift.Dictionary<Swift.String, Any>, Swift.DecodingError.Context(codingPath: [SwiftAWSS3.S3.ListBucketsOutput.(CodingKeys in _32757E5A7EBE8A89819CEB17805ED919).buckets], debugDescription: "Expected to decode Dictionary<String, Any> but found a string/data instead.", underlyingError: nil)): file /Users/yuki/WorkingsPlace/program/oss/Hexaville/Sources/Hexaville/main.swift, line 206
Illegal instruction: 4

@ochim
私の方では再現できませんでした。
SwiftバージョンやOSなどの環境情報と、Hexavillefile.ymlの内容(クレデンシャルはマスクして下さい)をいただくことは出来ますでしょうか？

@noppoMan 返答ありがとうございます。
Swift:4.0
OS:10.12.6
Xcode:9.2
name: NearStations
service: aws
aws:
   credential:
     access_key_id: xxxxxxxxxxxxxxxxxxxxxxxxxx
     secret_access_key: xxxxxxxxxxxxxxxxxxxxxxxxxx
     region: us-east-1
   lambda:
     bucket: hexaville-nearstations-pglda-bucket
     role: xxxxxxxxxxxxxxxxxxxxxxxxxx
#     vpc:
#       subnetIds:
#         - xxxxxx
#         - xxxxxx
#       securityGroupIds:
#         - xxxxxx
#         - xxxxxx
build:
   nocache: false
swift:
  version: 4.0
  build:
     configuration: release # default is debug

になります。

デプロイコマンドを叩いた時のコンソールログも貼っておきます。
Start to build swift...

Docker version
Client:
 Version:      17.09.1-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   19e2cf6
 Built:        Thu Dec  7 22:22:25 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.09.1-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   19e2cf6
 Built:        Thu Dec  7 22:28:28 2017
 OS/Arch:      linux/amd64
 Experimental: true
Sending build context to Docker daemon  77.51MB
Step 1/13 : FROM ubuntu:14.04
 ---> 7c09e61e9035
Step 2/13 : RUN apt-get update -y
 ---> Using cache
 ---> 43e228c673a6
Step 3/13 : RUN apt-get install -y clang   libicu-dev   libbsd-dev   uuid-dev   git   libxml2-dev   libxslt1-dev   python-dev   libcurl4-openssl-dev   wget
 ---> Using cache
 ---> 3c469ccd4331
Step 4/13 : ENV DEST /hexaville-app/.build/x86_64-unknown-linux
 ---> Using cache
 ---> 2aed87fa940f
Step 5/13 : ENV EXECUTABLE_NAME NearStations
 ---> Using cache
 ---> ae38de74e648
Step 6/13 : ENV SWIFT_DOWNLOAD_URL https://swift.org/builds/swift-4.0-release/ubuntu1404/swift-4.0-RELEASE/swift-4.0-RELEASE-ubuntu14.04.tar.gz
 ---> Using cache
 ---> 0966e4838328
Step 7/13 : ENV SWIFTFILE swift-4.0-RELEASE-ubuntu14.04
 ---> Using cache
 ---> 4c7907e62136
Step 8/13 : RUN wget $SWIFT_DOWNLOAD_URL
 ---> Using cache
 ---> 9de4438a2a2e
Step 9/13 : RUN tar -zxf $SWIFTFILE.tar.gz
 ---> Using cache
 ---> cc8c95c025c0
Step 10/13 : ENV PATH $PWD/$SWIFTFILE/usr/bin:"${PATH}"
 ---> Using cache
 ---> f618b5398b4d
Step 11/13 : COPY . hexaville-app
 ---> dee50e14ef07
Step 12/13 : WORKDIR hexaville-app
 ---> 700877dc4bc8
Removing intermediate container f0623c396400
Step 13/13 : CMD /bin/bash ./build-swift.sh
 ---> Running in 3fdc719e4a01
 ---> 17c0ffedd15f
Removing intermediate container 3fdc719e4a01
Successfully built 17c0ffedd15f
Successfully tagged nearstations:latest
Fetching https://github.com/noppoMan/HexavilleFramework.git
Fetching https://github.com/noppoMan/Prorsum.git
Fetching https://github.com/jakeheis/SwiftCLI.git
Fetching https://github.com/noppoman/ProrsumNet.git
Fetching https://github.com/vapor/clibressl.git
Cloning https://github.com/noppoMan/HexavilleFramework.git
Resolving https://github.com/noppoMan/HexavilleFramework.git at 0.1.15
Cloning https://github.com/noppoMan/Prorsum.git
Resolving https://github.com/noppoMan/Prorsum.git at 0.3.1
Cloning https://github.com/jakeheis/SwiftCLI.git
Resolving https://github.com/jakeheis/SwiftCLI.git at 3.1.0
Cloning https://github.com/noppoman/ProrsumNet.git
Resolving https://github.com/noppoman/ProrsumNet.git at 0.1.3
Cloning https://github.com/vapor/clibressl.git
Resolving https://github.com/vapor/clibressl.git at 1.0.0
warning: minimum recommended clang is version 3.6, otherwise you may encounter linker errors.
Compile CLibreSSL xts128.c
Compile Swift Module 'SwiftCLI' (25 sources)
Compile CLibreSSL xcbc_enc.c
Compile CLibreSSL x509type.c
Compile CLibreSSL x509spki.c
Compile CLibreSSL x509rset.c
Compile CLibreSSL x509name.c
Compile CLibreSSL x509cset.c
Compile CLibreSSL x509_vpm.c
Compile CLibreSSL x509_vfy.c
Compile CLibreSSL x509_v3.c
Compile CLibreSSL x509_txt.c
Compile CLibreSSL x509_trs.c
Compile CLibreSSL x509_set.c
Compile CLibreSSL x509_req.c
Compile CLibreSSL x509_r2x.c
Compile CLibreSSL x509_obj.c
Compile CLibreSSL x509_lu.c
Compile CLibreSSL x509_ext.c
Compile CLibreSSL x509_err.c
Compile CLibreSSL x509_def.c
Compile CLibreSSL x509_d2.c
Compile CLibreSSL x509_cmp.c
Compile CLibreSSL x509_att.c
Compile CLibreSSL x_x509a.c
Compile CLibreSSL x_x509.c
Compile CLibreSSL x_val.c
Compile CLibreSSL x_spki.c
Compile CLibreSSL x_sig.c
Compile CLibreSSL x_req.c
Compile CLibreSSL x_pubkey.c
Compile CLibreSSL x_pkey.c
Compile CLibreSSL x_nx509.c
Compile CLibreSSL x_name.c
Compile CLibreSSL x_long.c
Compile CLibreSSL x_info.c
Compile CLibreSSL x_exten.c
Compile CLibreSSL x_crl.c
Compile CLibreSSL x_bignum.c
Compile CLibreSSL x_attrib.c
Compile CLibreSSL x_all.c
Compile CLibreSSL x_algor.c
Compile CLibreSSL wp_dgst.c
Compile CLibreSSL wp_block.c
Compile CLibreSSL v3err.c
Compile CLibreSSL v3_utl.c
Compile CLibreSSL v3_sxnet.c
Compile CLibreSSL v3_skey.c
Compile CLibreSSL v3_purp.c
Compile CLibreSSL v3_prn.c
Compile CLibreSSL v3_pmaps.c
Compile CLibreSSL v3_pku.c
Compile CLibreSSL v3_pcons.c
Compile CLibreSSL v3_pcia.c
Compile CLibreSSL v3_pci.c
Compile CLibreSSL v3_ocsp.c
Compile CLibreSSL v3_ncons.c
Compile CLibreSSL v3_lib.c
Compile CLibreSSL v3_int.c
Compile CLibreSSL v3_info.c
Compile CLibreSSL v3_ia5.c
Compile CLibreSSL v3_genn.c
Compile CLibreSSL v3_extku.c
Compile CLibreSSL v3_enum.c
Compile CLibreSSL v3_crld.c
Compile CLibreSSL v3_cpols.c
Compile CLibreSSL v3_conf.c
Compile CLibreSSL v3_bitst.c
Compile CLibreSSL v3_bcons.c
Compile CLibreSSL v3_alt.c
Compile CLibreSSL v3_akeya.c
Compile CLibreSSL v3_akey.c
Compile CLibreSSL ui_util.c
Compile CLibreSSL ui_openssl.c
Compile CLibreSSL ui_openssl_win.c
Compile CLibreSSL ui_lib.c
Compile CLibreSSL ui_err.c
Compile CLibreSSL txt_db.c
Compile CLibreSSL ts_verify_ctx.c
Compile CLibreSSL ts_rsp_verify.c
Compile CLibreSSL ts_rsp_utils.c
Compile CLibreSSL ts_rsp_sign.c
Compile CLibreSSL ts_rsp_print.c
Compile CLibreSSL ts_req_utils.c
Compile CLibreSSL ts_req_print.c
Compile CLibreSSL ts_lib.c
Compile CLibreSSL ts_err.c
Compile CLibreSSL ts_conf.c
Compile CLibreSSL ts_asn1.c
Compile CLibreSSL tls.c
Compile CLibreSSL tls_verify.c
Compile CLibreSSL tls_util.c
Compile CLibreSSL tls_server.c
Compile CLibreSSL tls_peer.c
Compile CLibreSSL tls_conninfo.c
Compile CLibreSSL tls_config.c
Compile CLibreSSL tls_client.c
Compile CLibreSSL timingsafe_memcmp.c
Compile CLibreSSL timingsafe_bcmp.c
Compile CLibreSSL timegm.c
Compile CLibreSSL tb_store.c
Compile CLibreSSL tb_rsa.c
Compile CLibreSSL tb_rand.c
Compile CLibreSSL tb_pkmeth.c
Compile CLibreSSL tb_ecdsa.c
Compile CLibreSSL tb_ecdh.c
Compile CLibreSSL tb_dsa.c
Compile CLibreSSL tb_digest.c
Compile CLibreSSL tb_dh.c
Compile CLibreSSL tb_cipher.c
Compile CLibreSSL tb_asnmth.c
Compile CLibreSSL tasn_utl.c
Compile CLibreSSL tasn_typ.c
Compile CLibreSSL tasn_prn.c
Compile CLibreSSL tasn_new.c
Compile CLibreSSL tasn_fre.c
Compile CLibreSSL tasn_enc.c
Compile CLibreSSL tasn_dec.c
Compile CLibreSSL t1_srvr.c
Compile CLibreSSL t1_reneg.c
Compile CLibreSSL t1_meth.c
Compile CLibreSSL t1_lib.c
Compile CLibreSSL t1_enc.c
Compile CLibreSSL t1_clnt.c
Compile CLibreSSL t_x509a.c
Compile CLibreSSL t_x509.c
Compile CLibreSSL t_spki.c
Compile CLibreSSL t_req.c
Compile CLibreSSL t_pkey.c
Compile CLibreSSL t_crl.c
Compile CLibreSSL t_bitst.c
Compile CLibreSSL strsep.c
Compile CLibreSSL strnlen.c
Compile CLibreSSL strndup.c
Compile CLibreSSL strlcpy.c
Compile CLibreSSL strlcat.c
Compile CLibreSSL streebog.c
Compile CLibreSSL strcasecmp.c
Compile CLibreSSL str2key.c
Compile CLibreSSL stack.c
Compile CLibreSSL ssl_txt.c
Compile CLibreSSL ssl_stat.c
Compile CLibreSSL ssl_sess.c
Compile CLibreSSL ssl_rsa.c
Compile CLibreSSL ssl_lib.c
Compile CLibreSSL ssl_err2.c
Compile CLibreSSL ssl_err.c
Compile CLibreSSL ssl_ciph.c
Compile CLibreSSL ssl_cert.c
Compile CLibreSSL ssl_asn1.c
Compile CLibreSSL ssl_algs.c
Compile CLibreSSL sha512.c
Compile CLibreSSL sha256.c
Compile CLibreSSL sha1dgst.c
Compile CLibreSSL sha1_one.c
Compile CLibreSSL set_key.c
Compile CLibreSSL s3_srvr.c
Compile CLibreSSL s3_pkt.c
Compile CLibreSSL s3_lib.c
Compile CLibreSSL s3_clnt.c
Compile CLibreSSL s3_cbc.c
Compile CLibreSSL s3_both.c
Compile CLibreSSL s23_srvr.c
Compile CLibreSSL s23_pkt.c
Compile CLibreSSL s23_lib.c
Compile CLibreSSL s23_clnt.c
Compile CLibreSSL rsa_x931.c
Compile CLibreSSL rsa_ssl.c
Compile CLibreSSL rsa_sign.c
Compile CLibreSSL rsa_saos.c
Compile CLibreSSL rsa_pss.c
Compile CLibreSSL rsa_prn.c
Compile CLibreSSL rsa_pmeth.c
Compile CLibreSSL rsa_pk1.c
Compile CLibreSSL rsa_oaep.c
Compile CLibreSSL rsa_none.c
Compile CLibreSSL rsa_lib.c
Compile CLibreSSL rsa_gen.c
Compile CLibreSSL rsa_err.c
Compile CLibreSSL rsa_eay.c
Compile CLibreSSL rsa_depr.c
Compile CLibreSSL rsa_crpt.c
Compile CLibreSSL rsa_chk.c
Compile CLibreSSL rsa_asn1.c
Compile CLibreSSL rsa_ameth.c
Compile CLibreSSL rmd_one.c
Compile CLibreSSL rmd_dgst.c
Compile CLibreSSL reallocarray.c
Compile CLibreSSL rc4_skey.c
Compile CLibreSSL rc4_enc.c
Compile CLibreSSL rc2ofb64.c
Compile CLibreSSL rc2cfb64.c
Compile CLibreSSL rc2_skey.c
Compile CLibreSSL rc2_ecb.c
Compile CLibreSSL rc2_cbc.c
Compile CLibreSSL randfile.c
Compile CLibreSSL rand_lib.c
Compile CLibreSSL rand_key.c
Compile CLibreSSL rand_err.c
Compile CLibreSSL qud_cksm.c
Compile CLibreSSL pvkfmt.c
Compile CLibreSSL pqueue.c
Compile CLibreSSL posix_win.c
Compile CLibreSSL poly1305.c
Compile CLibreSSL poly1305-donna.c
Compile CLibreSSL pmeth_lib.c
Compile CLibreSSL pmeth_gn.c
Compile CLibreSSL pmeth_fn.c
Compile CLibreSSL pkcs7err.c
Compile CLibreSSL pk7_smime.c
Compile CLibreSSL pk7_mime.c
Compile CLibreSSL pk7_lib.c
Compile CLibreSSL pk7_doit.c
Compile CLibreSSL pk7_attr.c
Compile CLibreSSL pk7_asn1.c
Compile CLibreSSL pk12err.c
Compile CLibreSSL pem_xaux.c
Compile CLibreSSL pem_x509.c
Compile CLibreSSL pem_sign.c
Compile CLibreSSL pem_seal.c
Compile CLibreSSL pem_pkey.c
Compile CLibreSSL pem_pk8.c
Compile CLibreSSL pem_oth.c
Compile CLibreSSL pem_lib.c
Compile CLibreSSL pem_info.c
Compile CLibreSSL pem_err.c
Compile CLibreSSL pem_all.c
Compile CLibreSSL pcy_tree.c
Compile CLibreSSL pcy_node.c
Compile CLibreSSL pcy_map.c
Compile CLibreSSL pcy_lib.c
Compile CLibreSSL pcy_data.c
Compile CLibreSSL pcy_cache.c
Compile CLibreSSL pcbc_enc.c
Compile CLibreSSL p8_pkey.c
Compile CLibreSSL p5_pbev2.c
Compile CLibreSSL p5_pbe.c
Compile CLibreSSL p5_crpt2.c
Compile CLibreSSL p5_crpt.c
Compile CLibreSSL p12_utl.c
Compile CLibreSSL p12_p8e.c
Compile CLibreSSL p12_p8d.c
Compile CLibreSSL p12_npas.c
Compile CLibreSSL p12_mutl.c
Compile CLibreSSL p12_kiss.c
Compile CLibreSSL p12_key.c
Compile CLibreSSL p12_init.c
Compile CLibreSSL p12_decr.c
Compile CLibreSSL p12_crt.c
Compile CLibreSSL p12_crpt.c
Compile CLibreSSL p12_attr.c
Compile CLibreSSL p12_asn.c
Compile CLibreSSL p12_add.c
Compile CLibreSSL p_verify.c
Compile CLibreSSL p_sign.c
Compile CLibreSSL p_seal.c
Compile CLibreSSL p_open.c
Compile CLibreSSL p_lib.c
Compile CLibreSSL p_enc.c
Compile CLibreSSL p_dec.c
Compile CLibreSSL ofb64enc.c
Compile CLibreSSL ofb64ede.c
Compile CLibreSSL ofb128.c
Compile CLibreSSL ofb_enc.c
Compile CLibreSSL ocsp_vfy.c
Compile CLibreSSL ocsp_srv.c
Compile CLibreSSL ocsp_prn.c
Compile CLibreSSL ocsp_lib.c
Compile CLibreSSL ocsp_ht.c
Compile CLibreSSL ocsp_ext.c
Compile CLibreSSL ocsp_err.c
Compile CLibreSSL ocsp_cl.c
Compile CLibreSSL ocsp_asn.c
Compile CLibreSSL obj_xref.c
Compile CLibreSSL obj_lib.c
Compile CLibreSSL obj_err.c
Compile CLibreSSL obj_dat.c
Compile CLibreSSL o_time.c
Compile CLibreSSL o_str.c
Compile CLibreSSL o_names.c
Compile CLibreSSL o_init.c
Compile CLibreSSL nsseq.c
Compile CLibreSSL ncbc_enc.c
Compile CLibreSSL names.c
Compile CLibreSSL n_pkey.c
Compile CLibreSSL mem_dbg.c
Compile CLibreSSL mem_clr.c
Compile CLibreSSL md5_one.c
Compile CLibreSSL md5_dgst.c
Compile CLibreSSL md4_one.c
Compile CLibreSSL md4_dgst.c
Compile CLibreSSL malloc-wrapper.c
Compile CLibreSSL m_wp.c
Compile CLibreSSL m_streebog.c
Compile CLibreSSL m_sigver.c
Compile CLibreSSL m_sha1.c
Compile CLibreSSL m_ripemd.c
Compile CLibreSSL m_null.c
Compile CLibreSSL m_md5.c
Compile CLibreSSL m_md4.c
Compile CLibreSSL m_gostr341194.c
Compile CLibreSSL m_gost2814789.c
Compile CLibreSSL m_ecdsa.c
Compile CLibreSSL m_dss1.c
Compile CLibreSSL m_dss.c
Compile CLibreSSL lhash.c
Compile CLibreSSL lh_stats.c
Compile CLibreSSL krb5_asn.c
Compile CLibreSSL inet_pton.c
Compile CLibreSSL i2d_pu.c
Compile CLibreSSL i2d_pr.c
Compile CLibreSSL i_skey.c
Compile CLibreSSL i_ofb64.c
Compile CLibreSSL i_ecb.c
Compile CLibreSSL i_cfb64.c
Compile CLibreSSL i_cbc.c
Compile CLibreSSL hmac.c
Compile CLibreSSL hm_pmeth.c
Compile CLibreSSL hm_ameth.c
Compile CLibreSSL gostr341194.c
Compile CLibreSSL gostr341001.c
Compile CLibreSSL gostr341001_pmeth.c
Compile CLibreSSL gostr341001_params.c
Compile CLibreSSL gostr341001_key.c
Compile CLibreSSL gostr341001_ameth.c
Compile CLibreSSL gost89imit_pmeth.c
Compile CLibreSSL gost89imit_ameth.c
Compile CLibreSSL gost89_params.c
Compile CLibreSSL gost89_keywrap.c
Compile CLibreSSL gost2814789.c
Compile CLibreSSL gost_err.c
Compile CLibreSSL gost_asn1.c
Compile CLibreSSL getentropy_win.c
Compile CLibreSSL getentropy_solaris.c
Compile CLibreSSL getentropy_osx.c
Compile CLibreSSL getentropy_netbsd.c
Compile CLibreSSL getentropy_linux.c
Compile CLibreSSL getentropy_hpux.c
Compile CLibreSSL getentropy_freebsd.c
Compile CLibreSSL getentropy_aix.c
Compile CLibreSSL gcm128.c
Compile CLibreSSL fcrypt.c
Compile CLibreSSL fcrypt_b.c
Compile CLibreSSL f_string.c
Compile CLibreSSL f_int.c
Compile CLibreSSL f_enum.c
Compile CLibreSSL explicit_bzero.c
Compile CLibreSSL explicit_bzero_win.c
Compile CLibreSSL ex_data.c
Compile CLibreSSL evp_pkey.c
Compile CLibreSSL evp_pbe.c
Compile CLibreSSL evp_lib.c
Compile CLibreSSL evp_key.c
Compile CLibreSSL evp_err.c
Compile CLibreSSL evp_enc.c
Compile CLibreSSL evp_asn1.c
Compile CLibreSSL evp_aead.c
Compile CLibreSSL err.c
Compile CLibreSSL err_prn.c
Compile CLibreSSL err_all.c
Compile CLibreSSL eng_table.c
Compile CLibreSSL eng_pkey.c
Compile CLibreSSL eng_openssl.c
Compile CLibreSSL eng_list.c
Compile CLibreSSL eng_lib.c
Compile CLibreSSL eng_init.c
Compile CLibreSSL eng_fat.c
Compile CLibreSSL eng_err.c
Compile CLibreSSL eng_dyn.c
Compile CLibreSSL eng_ctrl.c
Compile CLibreSSL eng_cnf.c
Compile CLibreSSL eng_all.c
Compile CLibreSSL encode.c
Compile CLibreSSL enc_writ.c
Compile CLibreSSL enc_read.c
Compile CLibreSSL ede_cbcm_enc.c
Compile CLibreSSL ecs_vrf.c
Compile CLibreSSL ecs_sign.c
Compile CLibreSSL ecs_ossl.c
Compile CLibreSSL ecs_lib.c
Compile CLibreSSL ecs_err.c
Compile CLibreSSL ecs_asn1.c
Compile CLibreSSL ecp_smpl.c
Compile CLibreSSL ecp_oct.c
Compile CLibreSSL ecp_nist.c
Compile CLibreSSL ecp_mont.c
Compile CLibreSSL eck_prn.c
Compile CLibreSSL ech_lib.c
Compile CLibreSSL ech_key.c
Compile CLibreSSL ech_err.c
Compile CLibreSSL ecb3_enc.c
Compile CLibreSSL ecb_enc.c
Compile CLibreSSL ec2_smpl.c
Compile CLibreSSL ec2_oct.c
Compile CLibreSSL ec2_mult.c
Compile CLibreSSL ec_print.c
Compile CLibreSSL ec_pmeth.c
Compile CLibreSSL ec_oct.c
Compile CLibreSSL ec_mult.c
Compile CLibreSSL ec_lib.c
Compile CLibreSSL ec_key.c
Compile CLibreSSL ec_err.c
Compile CLibreSSL ec_cvt.c
Compile CLibreSSL ec_curve.c
Compile CLibreSSL ec_check.c
Compile CLibreSSL ec_asn1.c
Compile CLibreSSL ec_ameth.c
Compile CLibreSSL e_xcbc_d.c
Compile CLibreSSL e_rc4.c
Compile CLibreSSL e_rc4_hmac_md5.c
Compile CLibreSSL e_rc2.c
Compile CLibreSSL e_old.c
Compile CLibreSSL e_null.c
Compile CLibreSSL e_idea.c
Compile CLibreSSL e_gost2814789.c
Compile CLibreSSL e_des3.c
Compile CLibreSSL e_des.c
Compile CLibreSSL e_chacha20poly1305.c
Compile CLibreSSL e_chacha.c
Compile CLibreSSL e_cast.c
Compile CLibreSSL e_camellia.c
Compile CLibreSSL e_bf.c
Compile CLibreSSL e_aes.c
Compile CLibreSSL e_aes_cbc_hmac_sha1.c
Compile CLibreSSL dso_openssl.c
Compile CLibreSSL dso_null.c
Compile CLibreSSL dso_lib.c
Compile CLibreSSL dso_err.c
Compile CLibreSSL dso_dlfcn.c
Compile CLibreSSL dsa_vrf.c
Compile CLibreSSL dsa_sign.c
Compile CLibreSSL dsa_prn.c
Compile CLibreSSL dsa_pmeth.c
Compile CLibreSSL dsa_ossl.c
Compile CLibreSSL dsa_lib.c
Compile CLibreSSL dsa_key.c
Compile CLibreSSL dsa_gen.c
Compile CLibreSSL dsa_err.c
Compile CLibreSSL dsa_depr.c
Compile CLibreSSL dsa_asn1.c
Compile CLibreSSL dsa_ameth.c
Compile CLibreSSL digest.c
Compile CLibreSSL dh_prn.c
Compile CLibreSSL dh_pmeth.c
Compile CLibreSSL dh_lib.c
Compile CLibreSSL dh_key.c
Compile CLibreSSL dh_gen.c
Compile CLibreSSL dh_err.c
Compile CLibreSSL dh_depr.c
Compile CLibreSSL dh_check.c
Compile CLibreSSL dh_asn1.c
Compile CLibreSSL dh_ameth.c
Compile CLibreSSL des_enc.c
Compile CLibreSSL d2i_pu.c
Compile CLibreSSL d2i_pr.c
Compile CLibreSSL d1_srvr.c
Compile CLibreSSL d1_srtp.c
Compile CLibreSSL d1_pkt.c
Compile CLibreSSL d1_meth.c
Compile CLibreSSL d1_lib.c
Compile CLibreSSL d1_enc.c
Compile CLibreSSL d1_clnt.c
Compile CLibreSSL d1_both.c
Compile CLibreSSL cversion.c
Compile CLibreSSL cts128.c
Compile CLibreSSL ctr128.c
Compile CLibreSSL cryptlib.c
Compile CLibreSSL cpt_err.c
Compile CLibreSSL conf_sap.c
Compile CLibreSSL conf_mod.c
Compile CLibreSSL conf_mall.c
Compile CLibreSSL conf_lib.c
Compile CLibreSSL conf_err.c
Compile CLibreSSL conf_def.c
Compile CLibreSSL conf_api.c
Compile CLibreSSL comp_lib.c
Compile CLibreSSL comp_err.c
Compile CLibreSSL cmll_ofb.c
Compile CLibreSSL cmll_misc.c
Compile CLibreSSL cmll_ecb.c
Compile CLibreSSL cmll_ctr.c
Compile CLibreSSL cmll_cfb.c
Compile CLibreSSL cmll_cbc.c
Compile CLibreSSL cmac.c
Compile CLibreSSL cm_pmeth.c
Compile CLibreSSL cm_ameth.c
Compile CLibreSSL chacha.c
Compile CLibreSSL chacha-merged.c
Compile CLibreSSL cfb64enc.c
Compile CLibreSSL cfb64ede.c
Compile CLibreSSL cfb128.c
Compile CLibreSSL cfb_enc.c
Compile CLibreSSL ccm128.c
Compile CLibreSSL cbc128.c
Compile CLibreSSL cbc_enc.c
Compile CLibreSSL cbc_cksm.c
Compile CLibreSSL camellia.c
Compile CLibreSSL c_zlib.c
Compile CLibreSSL c_skey.c
Compile CLibreSSL c_rle.c
Compile CLibreSSL c_ofb64.c
Compile CLibreSSL c_enc.c
Compile CLibreSSL c_ecb.c
Compile CLibreSSL c_cfb64.c
Compile CLibreSSL c_all.c
Compile CLibreSSL by_mem.c
Compile CLibreSSL by_file.c
Compile CLibreSSL by_dir.c
Compile CLibreSSL buffer.c
Compile CLibreSSL buf_str.c
Compile CLibreSSL buf_err.c
Compile CLibreSSL bss_sock.c
Compile CLibreSSL bss_null.c
Compile CLibreSSL bss_mem.c
Compile CLibreSSL bss_log.c
Compile CLibreSSL bss_file.c
Compile CLibreSSL bss_fd.c
Compile CLibreSSL bss_dgram.c
Compile CLibreSSL bss_conn.c
Compile CLibreSSL bss_bio.c
Compile CLibreSSL bss_acpt.c
Compile CLibreSSL bsd-asprintf.c
Compile CLibreSSL bs_cbs.c
Compile CLibreSSL bs_cbb.c
Compile CLibreSSL bs_ber.c
Compile CLibreSSL bn_x931p.c
Compile CLibreSSL bn_word.c
Compile CLibreSSL bn_sqrt.c
Compile CLibreSSL bn_sqr.c
Compile CLibreSSL bn_shift.c
Compile CLibreSSL bn_recp.c
Compile CLibreSSL bn_rand.c
Compile CLibreSSL bn_print.c
Compile CLibreSSL bn_prime.c
Compile CLibreSSL bn_nist.c
Compile CLibreSSL bn_mul.c
Compile CLibreSSL bn_mpi.c
Compile CLibreSSL bn_mont.c
Compile CLibreSSL bn_mod.c
Compile CLibreSSL bn_lib.c
Compile CLibreSSL bn_kron.c
Compile CLibreSSL bn_gf2m.c
Compile CLibreSSL bn_gcd.c
Compile CLibreSSL bn_exp2.c
Compile CLibreSSL bn_exp.c
Compile CLibreSSL bn_err.c
Compile CLibreSSL bn_div.c
Compile CLibreSSL bn_depr.c
Compile CLibreSSL bn_ctx.c
Compile CLibreSSL bn_const.c
Compile CLibreSSL bn_blind.c
Compile CLibreSSL bn_asm.c
Compile CLibreSSL bn_add.c
Compile CLibreSSL bio_ssl.c
Compile CLibreSSL bio_pk7.c
Compile CLibreSSL bio_ndef.c
Compile CLibreSSL bio_md.c
Compile CLibreSSL bio_lib.c
Compile CLibreSSL bio_err.c
Compile CLibreSSL bio_enc.c
Compile CLibreSSL bio_cb.c
Compile CLibreSSL bio_b64.c
Compile CLibreSSL bio_asn1.c
Compile CLibreSSL bf_skey.c
Compile CLibreSSL bf_ofb64.c
Compile CLibreSSL bf_null.c
Compile CLibreSSL bf_nbio.c
Compile CLibreSSL bf_enc.c
Compile CLibreSSL bf_ecb.c
Compile CLibreSSL bf_cfb64.c
Compile CLibreSSL bf_buff.c
Compile CLibreSSL b_win.c
Compile CLibreSSL b_sock.c
Compile CLibreSSL b_print.c
Compile CLibreSSL b_posix.c
Compile CLibreSSL b_dump.c
Compile CLibreSSL asn1_par.c
Compile CLibreSSL asn1_lib.c
Compile CLibreSSL asn1_gen.c
Compile CLibreSSL asn1_err.c
Compile CLibreSSL asn_pack.c
Compile CLibreSSL asn_moid.c
Compile CLibreSSL asn_mime.c
Compile CLibreSSL arc4random.c
Compile CLibreSSL arc4random_uniform.c
Compile CLibreSSL ameth_lib.c
Compile CLibreSSL aes_wrap.c
Compile CLibreSSL aes_ofb.c
Compile CLibreSSL aes_misc.c
Compile CLibreSSL aes_ige.c
Compile CLibreSSL aes_ecb.c
Compile CLibreSSL aes_ctr.c
Compile CLibreSSL aes_core.c
Compile CLibreSSL aes_cfb.c
Compile CLibreSSL aes_cbc.c
Compile CLibreSSL a_verify.c
Compile CLibreSSL a_utf8.c
Compile CLibreSSL a_type.c
Compile CLibreSSL a_time.c
Compile CLibreSSL a_time_tm.c
Compile CLibreSSL a_strnid.c
Compile CLibreSSL a_sign.c
Compile CLibreSSL a_strex.c
Compile CLibreSSL a_set.c
Compile CLibreSSL a_print.c
Compile CLibreSSL a_octet.c
Compile CLibreSSL a_object.c
Compile CLibreSSL a_mbstr.c
Compile CLibreSSL a_int.c
Compile CLibreSSL a_i2d_fp.c
Compile CLibreSSL a_enum.c
Compile CLibreSSL a_dup.c
Compile CLibreSSL a_digest.c
Compile CLibreSSL a_d2i_fp.c
Compile CLibreSSL a_bytes.c
Compile CLibreSSL a_bool.c
Compile CLibreSSL a_bitstr.c
Compile CHTTPParser http_parser.c
Compile Swift Module 'ProrsumNet' (24 sources)
Compile Swift Module 'Prorsum' (36 sources)
Compile Swift Module 'HexavilleFramework' (16 sources)
Compile Swift Module 'NearStations' (4 sources)
Linking ./.build/x86_64-unknown-linux/release/NearStations
Build swift done.
Starting zip package........
  adding: NearStations (deflated 60%)
  adding: byline.js (deflated 59%)
  adding: index.js (deflated 67%)
  adding: libFoundation.so (deflated 68%)
  adding: libXCTest.so (deflated 67%)
  adding: libdispatch.so (deflated 74%)
  adding: libswiftCore.so (deflated 75%)
  adding: libswiftGlibc.so (deflated 75%)
  adding: libswiftRemoteMirror.so (deflated 67%)
  adding: libswiftSwiftOnoneSupport.so (deflated 80%)
  adding: libbsd.so.0 (deflated 51%)
  adding: libicudata.so.52 (deflated 60%)
  adding: libicui18n.so.52 (deflated 60%)
  adding: libicuuc.so.52 (deflated 59%)
  adding: assets/ (stored 0%)
  adding: assets/.keep (stored 0%)
  adding: assets/station20171109free.csv (deflated 69%)
Zip package done.
Uploading code to s3.....
fatal error: typeMismatch(Swift.Dictionary<Swift.String, Any>, Swift.DecodingError.Context(codingPath: [SwiftAWSS3.S3.ListBucketsOutput.(CodingKeys in _32757E5A7EBE8A89819CEB17805ED919).buckets], debugDescription: "Expected to decode Dictionary<String, Any> but found a string/data instead.", underlyingError: nil)): file /Users/yuki/WorkingsPlace/program/oss/Hexaville/Sources/Hexaville/main.swift, line 206
Illegal instruction: 4

情報ありがとうございます。
調査しますので、少々お待ちください。

S3のバケット内容に依存したエラーであったため、#91 で↑のエラーが出ないように修正してみました。
version@0.5.6に修正を載せていますので、
https://github.com/noppoMan/Hexaville#how-to-update-hexaville-cli-version
を参考にHexaville CLIを最新バージョンへ更新をお願いします。
更新後、hexaville deployをもう一度試していただけますでしょうか？

@noppoMan ありがとうございます。
更新して試したのですが、別のエラーが出て困っております。
Uploading code to s3.....
Fatal error: AWSResponseError(errorCode: "InvalidLocationConstraint", message: Optional("The specified location-constraint is not valid")): file /Users/yuki/WorkingsPlace/program/oss/Hexaville/Sources/Hexaville/main.swift, line 206
Illegal instruction: 4

hexavilleのversionはhexaville versionで0.5.6と確認しました。

Hexavillefile.ymlはこうです。
name: NearStations
service: aws
aws:
  credential:
     access_key_id: xxxxxxxxxxxxxxxxxxxxxxxxxx
     secret_access_key: xxxxxxxxxxxxxxxxxxxxxxxxxx
     region: us-east-1
  lambda:
     bucket: hexaville-nearstations-pglda-bucket
     role: xxxxxxxxxxxxxxxxxxxxxxxxxx
#     vpc:
#       subnetIds:
#         - xxxxxx
#         - xxxxxx
#       securityGroupIds:
#         - xxxxxx
#         - xxxxxx
build:
  nocache: false
swift:
  version: 4.0
  build:
     configuration: release # default is debug

@ochim
regionがus-east-1となっているのが問題かと思います。
おそらくtokyoリージョン用のアカウントで試されているかと思いますので、regionをap-northeast-1に変更することでデプロイが完了するかと思います！

あと、regionのネストを一段階あげて下さい。
regionはcredentialではなく、awsセクションのプロパティとなります。

@noppoMan ありがとうございます！無事デプロイできました。
awsについては話を聞くばかりで、使用経験はまだ少ないもので。
また、Hexavilleを使った記事を書いたので、よろしかったら読んでみてください。
https://qiita.com/ochim/items/7857d04d923816f80ced

hexavilleでは、高度なAWSの知識は要求されないので、ぜひ引き続きご利用ください！
記事も書いていただきありがとうございます😊
デプロイの記事も楽しみに待っています。

authors: noppoMan ochim

repo: noppoMan/Hexaville

license: mit

license_source: bigquery


text:
Metrics instances should be grouped hierarchically

NB internal APIs have some support for aggregating metrics registry views.
This should be used to logically group metrics instances into named registries so that individual activities can each have a specific and cohesive view of metrics. This would allow users to see metrics only for the activities they are interested in, during a session ,or in reports. It would also allow for saner logical grouping metrics when displayed.

This is done and working well in MB 5.21. It might not be exactly as described but poper labeling of metrics allows for this separation.

repo: nosqlbench/nosqlbench


text:
Can leading widget for PullDownMenuHeader be further customized?

First, phenomenal work on this.  Its quite slick package.
The leading widget right now will always put your items in a grey box in iOS style.  But in the future, iOS style may change, so we should have the ability to customize that leading widget.  For example, no grey box with drop shadow, etc...
Or at the very least make the leading widget optional so we are not forced to put something there

Hi @mark8044,

But in the future, iOS style may change, so we should have the ability to customize that leading widget.

Yes, this might be a problem in the future as I no longer actively maintain this package since I don't have access to any Apple products anymore so I can't even verify if UI-related stuff is correct since most in-depth design docs they provide are in Sketch which is MacOS exclusive app 😞
This is a valid request and I'll try to come up with some update for this soon

Or at the very least make the leading widget optional so we are not forced to put something there

Wouldn't making the leading widget optional be redundant? You might as well use the normal PullDownMenuItem, no? But I guess that might also be nice to have

Hi @mark8044,

But in the future, iOS style may change, so we should have the ability to customize that leading widget.

Yes, this might be a problem in the future as I no longer actively maintain this package since I don't have access to any Apple products anymore so I can't even verify if UI-related stuff is correct since most in-depth design docs they provide are in Sketch which is MacOS exclusive app 😞
This is a valid request and I'll try to come up with some update for this soon

Or at the very least make the leading widget optional so we are not forced to put something there

Wouldn't making the leading widget optional be redundant? You might as well use the normal PullDownMenuItem, no? But I guess that might also be nice to have

You know of course you are right!  Im an idiot.  I did not realized that PullDownMenuItem still gave you the options of the subtitle and icon, so yes that is a better implementation for my use case.
I still like the idea of being able to update the icon on the left, but this is now very low priority :)
Thanks so much!

Hi @mark8044
Update 0.10.0 is live with leadingBuilder added to PullDownMenuHeader. This should be good enough as it allows for complete freedom of choosing what the leading widget will look like.
Snippet from examples:
PullDownMenuHeader(
  leadingBuilder: (context, constraints) => ConstrainedBox(
    constraints: constraints,
    child: const FlutterLogo(),
  ),
  title: 'Title',
)


text:
Refactor collections

Fixes #9
Moves Collection Creation to a factory / job. Wraps the job in a lock to ensure collections get created before works.
I've had a bit of trouble testing the OAI 'All' import (my docker solr keeps crashing) but I believe this is now working. For 'All' we create collections for each set and add items into them. This only works effectively if the OAI record headers contain the setSpecs, which they should (but I found an example where they didn't).
This could do with some more tests.

looks like this is coming along - one thing that presents problems currently is that collections all need to be made before any works are created, otherwise the works can not attach to them and if you do the collection creation and work creation time you end up with duplicates (as works of the same collection are mostly bundled together).
I think if we have this in a background job, there may need to be some sort of lock that prevents works from creating if there are any pending collection creations.

@orangewolf I have gotten into a habit of running rubocop against my code and I realise now that it makes reviewing PRs harder, and creating inconsistency across the codebase. I think we just need to decide on our code standards and at this stage it doesn't have to be rubocop/bixby.

@orangewolf latest commit addresses a lot of the above and includes an alternative to the lock. I'm not convinced the existing lock mechanism is the right thing. What I've put in instead is a check that the collections exist, and a job reschedule if they don't.
This PR has turned into a bit of a monster, for what seems like a simple change and I'm worried it's turning into a time sync.

@orangewolf I have gotten into a habit of running rubocop against my code and I realise now that it makes reviewing PRs harder, and creating inconsistency across the codebase. I think we just need to decide on our code standards and at this stage it doesn't have to be rubocop/bixby.

I definitly think Rubocop is the right thing. It should really be part of our base pattern and often isn't. @smcfarlane made a big push for it for a while, but it seems like it kind of fell off again. Maybe we can do a breakfast and learn on it for the N8 team?

@orangewolf latest commit addresses a lot of the above and includes an alternative to the lock. I'm not convinced the existing lock mechanism is the right thing. What I've put in instead is a check that the collections exist, and a job reschedule if they don't.
I've done more testing with this, and unearthed a few bugs, now fixed.
This PR has turned into a bit of a monster.
Questions:

set a default collection and use it when OAI 'All' and OAI record doesn't include setSpec
use Hyrax::Lockable, or my collections_created? && reschedule (add a wait to that?)

I like both the Lockable and the new solution, but I'm leaning on the new one for 2 reasons. It is very specific - we don't create works until the collection exists... "oh your collection exists now? then go right ahead and build". That seems good to me. Also it means Bulkrax doesn't care about Redis, though I've been digging around more and I think that Hyrax may have a couple hidden dependencies on Redis that are not very clearly laid out.
Let's talk about the default collection thing tomorrow. I'm in and going at a humane hour and not in unavoidable meetings until high noon.

authors: geekscruff orangewolf


text:
Minimize file-open suppression

This update allows hovered editors to be included in normal recent-file tracking, provided that you either manually focus the popup (not autofocused) or opened another popup from it and then returned focus to it.  If a popup is autofocused it will not be treated as the file being opened for purposes of the quick switcher or other plugins monitoring file-open unless you switch focus away and back again.

A follow-up note, here: it seems that not triggering file-open has some other negative consequences other than recent files.  The outline, backlinks, outgoing links, local graph, etc. all depend on the file-open event.  I'm beginning to wonder if perhaps the recent files plugin and quick switcher should be handled specially, rather than suppressing the file-open event entirely.
At the moment, what was done in this PR is more precisely targeted than previously, and a future PR could maybe narrow things down even more, by hooking Workspace.recordMostRecentOpenedFile() and the recent files plugin's shouldAddFile() methods.  Then all plugins except those would respond normally to the pane receiving focus.
So, that's what I'm going to try next -- patch those instead of trigger(), using the same criteria for when to do it -- and see if it's less clunky in use before submitting another PR.

repo: nothingislost/obsidian-hover-editor


text:
Refactor guards for service calls

Related to #8 and also fixing #2 :

In Notifiex.Services.Slack add optional parameters to documentation
Add typespec documentation for Notifiex.Services.Slack and Notifiex.Services.Discord
Return {:error, {:missing_required_params}, nil} if any required parameters are missing

@andreascm Could you please resolve the merge conflict in slack.ex?

Hi @burntcarrot all done!

Thank you for your contribution! @andreascm
There's a pending PR (#7) which I had put on hold previously; if you're willing to take some pieces up from that and implement something which resembles the expected usage in #7, I'd be happy to assign you to the relevant issue.

Yes sure! I can look into it. However, I think it still needs further details on what would happen in the following cases:

If we are sending notification to both slack and discord, but the one of the required params for discord is missing

What is the expected behaviour in send sync and async? Should it only send to slack in both cases?
Should it return :ok with additional notes on missing params for discord? Or should it return :error with additional notes on success for slack?
Would the behaviour be the same if we receive error from slack or discord API?

Should we validate against sending multiple of the same notification to the same channel?
How does this differ from the current send_multiple/1 and send_multiple_async/1? Would this deprecate those 2 functions?

Sure! I've added additional notes in #10. Please feel free to ask any questions there!

authors: andreascm burntcarrot

repo: notifiex/notifiex


text:
bag8 dns connection error

when trying to run bag8 dns, it looks like bag8 is trying to connect to the dnsdock server to check if it's already running. if it does, I think it does nothing. but if it's not running, there's an untrapped connection error:
$ bag8 dns
No config found at: /home/novapost/.config/bag8.yml.
Loads default values.
Traceback (most recent call last):
  File "/home/novapost/.virtualenvs/TEST/bin/bag8", line 10, in <module>
    sys.exit(bag8())
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/click/core.py", line 664, in __call__
    return self.main(*args, **kwargs)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/click/core.py", line 644, in main
    rv = self.invoke(ctx)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/click/core.py", line 991, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/click/core.py", line 837, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/click/core.py", line 464, in invoke
    return callback(*args, **kwargs)
  File "/home/novapost/Projets/TEST/figfiles/src/bag8/bag8/cli.py", line 88, in dns
    result = Tools().dns()
  File "/home/novapost/Projets/TEST/figfiles/src/bag8/bag8/tools.py", line 100, in dns
    if not inspect('dnsdock')['State']['Running']:
  File "/home/novapost/Projets/TEST/figfiles/src/bag8/bag8/utils.py", line 63, in inspect
    return client.inspect_container(container)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/docker/utils/decorators.py", line 20, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/docker/client.py", line 474, in inspect_container
    self._get(self._url("/containers/{0}/json".format(container))),
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/docker/clientbase.py", line 86, in _get
    return self.get(url, **self._set_request_timeout(kwargs))
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/requests/sessions.py", line 477, in get
    return self.request('GET', url, **kwargs)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/requests/sessions.py", line 465, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/home/novapost/.virtualenvs/TEST/local/lib/python2.7/site-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(111, 'Connection refused'))

It may sound a bit silly: to run/restart a service, it's okay to check if it's running, but it's not okay to FAIL if it doesn't.

cf.: #47

authors: brunobord toopy


text:
Governance. Delegate. Your Delegation state won't update when switch between wallets

Description
When user switch between wallets (multishard->walletconnect) the Your Delegation state won't be updated.
https://github.com/user-attachments/assets/e08b1af3-105e-47e1-ae56-1c586c992865
Steps to Reproduce

Select multishard wallet
Add new delegation for 2 accounts
Switch to WalletConnect wallet
Open your delegations

Expected Behavior
New state for new wallet
Actual Behavior
Will be shown state for multishard wallet with 2 accounts
Environment
https://github.com/novasamatech/nova-spektr/commit/79488c9a756ec07402056b351ea2aca2e43b47ac

Status verification: ✅

repo: novasamatech/nova-spektr


text:
Code restructure required in NovelCamera due to a messy "it just works" implementation with Lazy.

Due to how I've implemented the UBO changes as per #73 some janky code has crept in.
We need to reorganise this so its less terrible.

Resolved as of #98 . Closing.

repo: novelrt/NovelRT


text:
Combo box unexpected resizing and flickering on current item changing

See video:
https://www.youtube.com/watch?v=xsOf9IKryDs
I detected some flickering and size changing when selecting combobox items.
Regards, Alexey Knyshev

Most of these (except the segfault) should have been solved in really recent commits (yesterday night)
Please update and report back if they persist

Should be fixed in d42ff46

Done, Thx a lot!

authors: alexeyknyshev novembermonk

repo: novembermonk/kiui

license: Zlib


text:
ZHtwinkle patch 1

增加 Zeabur 部署方式，解决新注册 Github 账号不能使用 Railway 进行无服务器部署的问题

感谢，我合并到dev分支验证下

authors: ZHtwinkle novicezk

repo: novicezk/midjourney-proxy


text:
Add Steps on how to make a PR.

Add proper steps from forking to creating a PR in the main Readme of the project.

Hey, can I work on this?

@SRADHA-SURESH12 feel free to pitch in!
But please keep in mind that if you want your contributions to be counted for the Hacktoberfest, they must be made in October only.

Hey there, can i participate in this issue as well? you can choose whichever PR with the most detailed guide.

@SRADHA-SURESH12 @donheshanthaka both of you can collaborate too! :handshake:
Feel free to ask for any doubts if you have. :+1:

@SRADHA-SURESH12 since there were no updates from you side, @donheshanthaka has worked on this issue.
If you still want to contribute, you can add more details or may be some other methods for the same.
Feel free to contact me for any doubts. :yellow_heart:
:rocket:

authors: SRADHA-SURESH12 donheshanthaka noviicee

repo: noviicee/Banque-De-Questions


text:
Update to .Net 8

Update to .Net 8
Update dependencies
C# 12 code style

The build pipeline needs to be updated to use .Net 8 SDK

repo: novotnyllc/NuGetKeyVaultSignTool


text:
fix(links): Change color to match npm branding

Change link color from blue to npm red
BREAKING CHANGE: This will affect all links and should be tested carefully.
[Finishes #119321553]

First thing noticed:
on forms:

Next up:
@jerrygabra do you want to keep this as the inverse link color, or move to a red as well?

@jefflembeck we don't really use that paradigm on npm; that being said i'd change it if we're not removing it from the style guide; cc @stubbornella

Cool. Let's remove that inverse one then, since we don't use it. And then I'll fix the select issue above.

ok, selects/options are back to normal.
Let's update: links, forms, and tooltips to match the new link color.

wow, red is really bad on the form elements. It looks like an error state. Perhaps @jerrygabra can suggest another color?

never mind, that's perfect @jefflembeck!

Awesome. publishing, pushing a publish commit up, and here we go.

authors: jefflembeck jerrygabra stubbornella

repo: npm/pivotal-ui


text:
ツリー画面に拡大、縮小、リセットボタンを追加

ref #892
ツリー画面に拡大、縮小、リセットボタンを追加しました。

zoom パラメータの初期値は 1.0
1.0以上に拡大することはできない
拡大は zoom を 1.1倍
縮小は zoom を 1.1で割る
リセットすると zoom が 1.0 に戻る
zoom パラメータが変化すると、ツリーの表示位置はリセットされる

それ以上拡大できないとき、拡大ボタンを disable するよう改良しました。
この内容でマージします。

repo: npocccties/chibichilo


text:
OSError: [Errno 2] No such file or directory

    (mapturner)>>$ mapturner -r test.yaml output.json
Redownloading ne_10m_populated_places_simple.zip...
Processing neighbors
No such file or directory
Traceback (most recent call last):
  File "/Users/me/.virtualenvs/mapturner/lib/python2.7/site-packages/envoy/core.py", line 214, in run
    out, err = cmd.run(data, timeout, kill_timeout, env, cwd)
  File "/Users/me/.virtualenvs/mapturner/lib/python2.7/site-packages/envoy/core.py", line 93, in run
    raise self.exc
OSError: [Errno 2] No such file or directory```

Nevermind.  I was missing the topojson dependency

repo: nprapps/mapturner


text:
Integration tests

Added edgesec integration test.
Please check with the git rebase. It seems that there are problems.

I'm not even sure what's happened with your git history again!
Did you do some sort of command to sign your commits? My gut feeling is that you did a git rebase --gpg-sign or something? But somehow, you even have some commits in triplicate, so I really don't know how you managed this :laughing:
GitHub is only showing that you've changed a few files, which seems wrong, so I'll try to review only once the commits are fixed up.
To fix, can you try doing a git rebase --interactive --sign-off origin/main, then drop every commit that's already in main.
E.g., something like:

Git docs here: https://git-scm.com/docs/git-rebase#_interactive_mode in case it helps.

Commits have been rebased. @mereacre, can you review my changes? I slightly modified your code. I'll do a full review tomorrow.

Hi @mereacre, before you merge, can you run:
git rebase -i --autosquash 7cc308177d57e237c0dae7a5cf4808af641c5bd5 --rebase-merges

(no need to edit anything too)
It should automatically combine the feat: Added execute firewall for uci commit with fixup! feat: Added execute firewall for uci (plus, it will allow you to sign all your commits since then and remove my face as the committer)

Hi @mereacre, I might need to wait until Monday to git rebase this PR again.
I'm swear there must be something different with your git config that is unusual!
Doing a git reset --hard eb708cce43f9f5bd17d69bd2dd5ec36facbde760 might help, since https://github.com/nqminds/edgesec/pull/339/commits/eb708cce43f9f5bd17d69bd2dd5ec36facbde760 looks like the last good commit (most of everything after that looks like mistaken/broken commits).

@mereacre, it looks like the test_edgesec is failing due to ERROR runctl.c:440: load_crypt_service fail on the linux-with-crypt preset.

authors: aloisklink mereacre

repo: nqminds/edgesec


text:
controls are unusually small on mobile

It makes impossible to do anything useful
Xiaomi redmi 4, android 6.0.1 MMB29M

Could you try another browser? Opera, Chrome...

That's probably because I did not make any extra efforts on supporting mobile.
If it's for viewing changesets, Changeset Map might now be the better option anyway.

In my case I wanted to find out which changeset caused certain object to be deleted.

Could you try another browser? Opera, Chrome...

Result is the same

Adding a viewport meta tag to index.html would be a start:
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />
But then the layout gets messed up, so supporting mobile would be a bit more involved.
Like with other issues, it would probably make sense to switch to Leaflet or Mapbox GL JS first. Not sure if and when I will get to this though.

authors: HolgerJeromin matkoniecz nrenner

repo: nrenner/achavi


text:
[nrf noup] mcuboot: Only include pcd.h if the nRF53 network core is being upgraded

Only include pcd.h in mcuboot when CONFIG_NRF53_UPGRADE_NETWORK_CORE is defined
ref: NCSDK-7433
Signed-off-by: Ole Sæther ole.saether@nordicsemi.no

Is not sauce tag missing here?

manifest?

manifest?

https://github.com/nrfconnect/sdk-nrf/pull/5068

authors: jfischer-no nvlsianpu osaether

repo: nrfconnect/sdk-mcuboot


text:
[nrf noup] boot: zephyr: Boot even if EXT_ABI is not provided

This removes the return; to ensure that the application is booted even if EXT_ABI is not provided to the application because it does not include FW_INFO.
Added a bit more description to the error messages when FW_INFO is not found and EXT_ABI is not able to be provided to the next image.
Ref. NCSDK-24132

Manifest PR here: https://github.com/nrfconnect/sdk-nrf/pull/12732

Is this ready to merge?

@cvinayak Yes it is now.

authors: cvinayak de-nordic sigvartmh


text:
[nrf fromlist] modules: hal_nordic: Add global domain power request service

Service for powering peripherals that use GPIO pins in the global power domains:

Active Main
Active Slow
Main Fast

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_nordic
https://github.com/zephyrproject-rtos/hal_nordic/commit/d4030afcc0befef645eda11e82c0d7c0e1d604f1
https://github.com/zephyrproject-rtos/hal_nordic/pull/224
zephyrproject-rtos/hal_nordic#224/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.

Closing in favor of #2075

authors: 57300 NordicBuilder Rafal-Nordic

repo: nrfconnect/sdk-zephyr


text:
Rebase PR#19 over PR#20 branch "bump supported ansible versions"

This is a rebase of changes in
PR https://github.com/nsg/ansible-inventory/pull/19
over the branch PR https://github.com/nsg/ansible-inventory/pull/20.

Perfect! :+1:

authors: nflx nsg

repo: nsg/ansible-inventory


text:
[#18] Add object attributes test

Update boto3 to 1.24.4
close #18
Signed-off-by: Denis Kirillov denis@nspcc.ru

Added using version 1.23.10 and checked in docker. It should work now


text:
Retainers Organize

Heya!
First of all thanks for your work. I want to report that retainers organize isn't working.
i.e. I have 25 copper on retainer A and 30 copper on retainer B, it doesn't merge like Retainers Organize from the old llamalibrary did before and the option doesn't exist on the setup.

The organizing part was removed when it went to the retainers section of llama utility. TuckMeIntoBread made a whole botbase to handle organizing retainers which encompasses that function now https://github.com/TuckMeIntoBread/AutoRetainerSort

Nvm. I've found it within the repository. But I must insist. Retainers Organize it's way superior.
Anyways, as I said before. Ty for your hard work!


text:
Issue with reading xacro file in UAV demo on ROS-Melodic

I had an issue where the UAV demo did not want to launch. It turned out that ROS-melodic had an error with xacro. The maintainer of the xacro package is aware of this and has triggered a release, but it is not yet synced.
As a fix I ended up changing to the the testing repository of ROS-Melodic. Here a newer version of xacro is available, which I simply downloaded/updated through "sudo apt-get ros-melodic-xacro".
The release that was triggered by the xacro maintainer has yet to be synced due to a lot of regression in melodic.
Please see the links for more context:
https://github.com/ethz-asl/rotors_simulator/issues/695#issue-113445556
https://github.com/ros/xacro/issues/316#issue-1155057122
https://github.com/ros/rosdistro/issues/32236
http://wiki.ros.org/TestingRepository
Error received:
RLException: while processing /home/daniel/gbplanner2_ws/src/sim/rotors_simulator/rotors_gazebo/launch/spawn_mav.launch: Invalid <param> tag: Cannot load command parameter [robot_description]: command [['/opt/ros/melodic/lib/xacro/xacro', '/home/daniel/gbplanner2_ws/src/sim/rotors_simulator/rotors_description/urdf/rmf_obelix.gazebo', 'enable_logging:=false', 'enable_ground_truth:=true', 'enable_mavlink_interface:=false', 'log_file:=rmf_obelix', 'wait_to_record_bag:=false', 'mav_name:=rmf_obelix', 'namespace:=rmf_obelix']] returned with code [2].
Param xml is <param command="     $(find xacro)/xacro '$(arg model)'     enable_logging:=$(arg enable_logging)     enable_ground_truth:=$(arg enable_ground_truth)     enable_mavlink_interface:=$(arg enable_mavlink_interface)     log_file:=$(arg log_file)     wait_to_record_bag:=$(arg wait_to_record_bag)     mav_name:=$(arg mav_name)     namespace:=$(arg namespace)" name="robot_description"/>

Hello,
Thank you for pointing this out. I will add a section about this in the Wiki - bug fixes.
Best,
Mihir

authors: MihirDharmadhikari danielvennestrom


text:
Using ConvertUPCEtoUPCA, compile error

Hello,
using MSVC I'm trying to use the function
ZXing::OneD::UPCEANCommon::ConvertUPCEtoUPCA
defined in
ZXing/oned/ODUPCEANCommon.h
so in my project I included
#include <ZXing/oned/ODUPCEANCommon.h>
but the latter includes
#include "ODUPCEANReader.h"
which in turn includes
#include "oned/ODRowReader.h"
which fails because files "ODUPCEANReader.h" and "ODRowReader.h" are in the same directory.
Thank you.

It was indeed a mistake, to include folder in relative path.
I'm going to fix it.

authors: enzo-simone huycn

repo: nu-book/zxing-cpp


text:
🛑 Secret Site BIS is down

In ea8c567, Secret Site BIS ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site BIS is back up in 0647e3b after 25 minutes.


text:
🛑 Secret Site BIS is down

In d032c05, Secret Site BIS ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site BIS is back up in ef8b7af.


text:
🛑 Affari Esteri e Cooperazione Internazionale is down

In 78314a7, Affari Esteri e Cooperazione Internazionale (http://www.esteri.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Affari Esteri e Cooperazione Internazionale is back up in 2d8c3c5.


text:
🛑 Università e ricerca is down

In 134476d, Università e ricerca (https://www.mur.gov.it/it) was down:

HTTP code: 403
Response time: 899 ms

Resolved: Università e ricerca is back up in 9628502.


text:
Fix example code in README.md

fixes #13

Thanks again, @vladimir-e!

authors: null-null-null vladimir-e

repo: null-null-null/ember-keyboard


text:
how to load LoRA ?

I can't find the node loading lora. and also no support for comfyui's lora loading mode

Negative prompt don't seem to be supported either.

Yes, I think it is possible, but not with current implementation, of course. I will look into it, but give me several days as a lot of code should be reviewed and rewritten.

Check new version, please

Check new version, please

Thank you very much. I'll try

Last version supports both LoRA and negative prompts.

repo: nullquant/ComfyUI-BrushNet


text:
np.arange seems to be unsupported with exact dtype argument

Hi,
I noticed that the following simple test fails to run if Numba is used in nopython mode.
The issue seems to be related to a call to np.arange with dtype specified as an argument.
I was using Numba:
numba                     0.46.0dev0      np116py37h6538335_82    numba/label/dev
The test itself:
    def test_numba_arange_with_dtype(self):
        def test_impl(n):
            arr = np.arange(n, dtype=np.int64)
            return arr
        jitted_func = numba.njit(test_impl)
        n = 11
        np.testing.assert_array_equal(jitted_func(n), test_impl(n))

The exact error is:

Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\hpat\hpat\tests\test_serie
s.py", line 1710, in test_numba_arange_with_dtype
np.testing.assert_array_equal(jitted_func(n), test_impl(n))
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\envs\HPAT\lib\site-package
s\numba\dispatcher.py", line 376, in _compile_for_args
error_rewrite(e, 'typing')
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\envs\HPAT\lib\site-package
s\numba\dispatcher.py", line 343, in error_rewrite
reraise(type(e), e, None)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\envs\HPAT\lib\site-package
s\numba\six.py", line 658, in reraise
raise value.with_traceback(tb)
numba.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function() with argument(s) of type(s): (int
64, dtype=class(int64))

parameterized
In definition 0:
AssertionError:
raised from C:\Users\akozlov\AppData\Local\Continuum\anaconda3\envs\HPAT\lib\site
-packages\numba\typing\npydecl.py:632
In definition 1:
AssertionError:
raised from C:\Users\akozlov\AppData\Local\Continuum\anaconda3\envs\HPAT\lib\site
-packages\numba\typing\npydecl.py:632
This error is usually caused by passing an argument of a type that is unsupported by
the named function.
[1] During: resolving callee type: Function()
[2] During: typing of call at C:\Users\akozlov\AppData\Local\Continuum\anaconda3\hpat
\hpat\tests\test_series.py (1706)

Can you please fix that?
Best Regards,
Alexey.

Thanks for the report. What you are doing (dtype kwarg in np.arange) is not supported, so this is a feature request. I just took a look at the np.arange code in Numba, it's using the old APIs and needs an update. FWIW, making the call in this specific manner will work:
In [10]: @njit
    ...: def foo():
    ...:     return np.arange(1, 10, 1, np.uint8)

that is, all of start, stop, step supplied, and the dtype supplied as an arg not a kwarg.

Hi @stuartarchibald, the old API is @lower_builtin? And the new one would be @overload?

@guilhermeleobas yes, well, "old" may be a little excessive, it's more that the numba.extending.* API is preferred.

Closing, fixed in #4770

repo: numba/numba


text:
Consider Using Bounties

(I prefer issue-trackers, so not using "discourse" or "gitter". Possibly enable the "Discussions" within the repo, for people who avoid chat-systems)
I noticed the following situation:

Many Issues and PRs within numba
Aanaconda looking for more people (https://www.anaconda.com/careers)

"Dynamic company that rewards high-performers"
"Equal Opportunity Employer"
"Nervous system condition for example, migraine headaches" (sidenote, I have a disability and didn't even know it...)

The suggestion is to use bounties (high profile, similar to those of IBM), in order to:

get some issues done
identify talent for specific tasks/work/positions (for more bounties, freelance hire, or fixed employment).

Dear @abebeos, that you for your suggestions I have marked this issue as 'discussion' accordingly.

Dear @abebeos, that you for your suggestions I have marked this issue as 'discussion' accordingly.

authors: abebeos esc


text:
[WIP] Option to disable jit (#1084)

This is work-in-progress, but I'm opening the PR in order to solicit feedback about how to proceed. Currently:

Setting NUMBA_DISABLE_JIT=1 causes the JIT decorator and the compile functions to return the original Python function instead of a compiled one
However, various tests fail with the disabled JIT. At the moment, there are 112 failures and 102 errors in the tests (2020 tests run in total).
I started going through making changes to tests to get them to pass again, but there may well be a fair bit of work to get them all passing/skipping as appropriate.

I initially approached this hoping to get all tests to pass, in order to prove (to the extent possible with a unit test suite) that behaviour with JIT enabled is the same as with JIT disabled. However, I'm wondering if that's practical at the moment. I don't mind spending a bit of time working through the other tests, but are there other opinions on what would be better to do instead?
Additionally, I was planning that the same configuration option would be used to turn cudasim on and off when it is integrated into Numba, in order to be consistent between CPU and GPU targets.

I don't mind spending a bit of time working through the other tests, but are there other opinions on what would be better to do instead?

I think that's too much work for too little benefit. The test suite needn't pass with unexpected settings. We already have enough issues to care about when adding tests (such as failures under Windows :-)).
So we should only have a couple specific tests for NUMBA_DISABLE_JIT=1.

Thanks for the thoughts - I'll undo those original changes to the test suite and add some specific jit-disabled tests.

Closing, superseded by #1102.

authors: gmarkall pitrou


text:
Provide a way to define a default test suite.

Just what the title implies.

This looks good on the principle.

authors: pitrou stefanseefeld


text:
Deprecation warnings

This is ~WIP.~ ready to review, work on deprecations for version 0.44.0.
TODO:

Docs on:

[x] deprecation of List and Set reflection.
[x] deprecation of Object mode fallback.
[x] deprecation of SmartArray.
[x] how to suppress warnings

New unit tests:

[x] to check warnings are working correctly.
[x] to check warnings are easily handled and suppressed.

Other tasks:

[x] Fix URL placeholders to point to real locations
CUDA:

[x] Issue warnings for use of NUMBAPRO envvars
[x] Tests for the above.
[x] Documentation for the above.

Closes: https://github.com/numba/numba/issues/3866
xref: https://github.com/numba/numba/issues/3907

OK, I think this is ready to merge now.

authors: seibert stuartarchibald


text:
Vertical offset required for (resizable) matrix input when used as a gapfill

When the option to allow students to change the size of a matrix is used as a gapfill, inline with other expressions, the additional height taken up by the resize box results in the matrix being misaligned vertically with the rest of the line. I can fix this in a single question using the following jQuery
$(".matrix-input").has(".matrix-size").css( "margin-top", "-50px" );
$(".type-matrix").has(".matrix-size").css( "padding-top", "50px" );
I don't think there would be any harm adding something to the stylesheet long these lines.
The issue is illustrated here: https://numbas-editor.mas.ncl.ac.uk/numbas-previews/question-1931-matrix-size-as-an-inline-gapfill/index.html

I've had a go at this and it's just too hard! To do what Chris asks, we need the .part.type-matrix element to know it's going to allow resizing, but that information isn't available until we're inside that element.
We tried a couple of other options for resizing the matrix, without that bar:

always add an additional row and column, and automatically shrink back when the last row or column is empty: it always looks like you've got a row/column left to fill in. The blank state looks like a fixed (m+1)x(n+1) layout, unless you style the additional cells differently, in which case it's not obvious you're supposed to type in them.
buttons at the end of each row/column to add another column/row. We couldn't find a set of symbols and styling that made them look obviously clickable without explanation.

Fixed in #932

authors: chrismgraham christianp

repo: numbas/Numbas


text:
Broken help link

In the Extensions tab of a user's profile (file accounts/templates/profile/extensions.html), the help link points to {{HELP_URL}}extensions.html but it should point to {{HELP_URL}}extensions/index.html.
Thanks for the great work!

True, Reproducible on the editor hosted at https://numbas.mathcentre.ac.uk which redirects to https://docs.numbas.org.uk/en/latest/extensions.html instead of https://docs.numbas.org.uk/en/latest/extensions/. I am fixing this and sending a PR 😄

repo: numbas/editor


text:
High severity vulnerability affecting this repo

Hi there,
We noticed that your repo has a high severity vulnerability:

Regular Expression Denial of Service
Affected package: negotiator<= 0.6.0

Here is the test report for this repo.
If you’d like to fix this vulnerability, Snyk lets you generate a pull request that recommends the best upgrade path - there’s a link to fix this vulnerability on the test report.
Stay secure :-)
Ben from the Snyk team

This repo will be shut down.

authors: rhyolight snyk-community


text:
Support pre-push githook natively

#18 provides for use cases of pre-push hooks specifically. https://github.com/numtide/devshell/issues/16#issuecomment-700149605 provides analysis for why a lightweight implementation is superior beyond the mere benefit of being leightweight.
That means, the consolidated intended use case does not require git workdir management. What's worse, providing such would induce misinterpretations about the consolidated intended use case.
Therefore, it is proposed for devshell to arrange for:

A simple command sequence

that is defined in devshell's standard interfaces
and that is executed in order
in the context of the repo's root and within debshell env
by a devshell library facility
which is symlinked to .git/hooks/pre-push.

The facility is capable of detecting modified files against the reference git ref,

which in the case of pre-push
is origin's HEAD.

The facility passes the modified files list

as last variadic argument
to each command in the list.

The command itself needs to arrange for

handling this variadic last argument (discarding if necessary),
filtering on file types against this variadic last argument

devshell may provide a configurable generic wrapper script for filtering, that supports configurable matching through:

regex include
regex exclude
as well as identify

The git.hooks extra module now allows to build on top of it.

authors: blaggacao zimbatm

repo: numtide/devshell


text:
Increase test timeout for multiple URL sources.

This change increases the timeout if there are many URL sources, because
each one needs time to get an HTTP response back.
This PR was created so that #50 would pass tests.

build failure was a coveralls problem. all tests passed.

repo: nupic-community/river-view