text:
Games don't show up

Hi mate, just downloaded your app from F-droid. Somehow my games from ogs don't showup under my games tab. Oneplus device, LineageOS, Android 7.1.2

Can you collect the logcat and send it to me? There have been some other reports of this happening, but I cannot reproduce on my devices.

thanks for the quick reply mate, here is the logcat:
2017-05-26-16-25-54.txt

That log is very strange. It doesn't have all of the traces. For instance, in the source code is this fragment:
        println("NJJJ logger = ${logger}")
        println("NJJJ logger.level = ${logger.level}")
        println("NJJJ logger.name = ${logger.name}")

However your log file only has the last line:
05-26 16:24:34.630 I/System.out(29501): NJJJ logger.name = com.ogs.OgsSocket

I don't know why only some of the traces would show up. Can you try collecting again, or maybe through a different method to see if you get more logs?
I haven't installed the fdroid version of the app yet, so it could be something that fdroid does when it builds that gets rid of the logging. I will try it tonight.

I recorded another log, this time without any filter:
log.txt

Thanks! I see the issue. It should be an easy fix. I am hoping to release a new version tonight if all goes well.

Thanks mate, looking forward to the new version.

authors: Seferi nathanj

repo: nathanj/ogsdroid


text:
Compiled .whl file ?

Friend! For several days I have been trying to build tensorflow according to your instructions. I get different errors. Could you post the finished .whl file? I would be very grateful to you.

Hi Igor-Shabalin, the purpose of compiling tensorflow is to match the compute capabilities of your gpu card and is specific to your system.
So i cannot provide you a .whl.
You could use the prebuilt version of tensorflow or look on the official tensorflow github issue to find your compilation errors.

I have, like you, a video card Geforce 740M, ubuntu 18.04 and an Intel 7 CPU. Prebuilt version of tensorflow-gpu do not work for me because they have capabilities of 3.5. I can’t build it from the sources with GPU support, I get different errors when compiling with different versions of drivers and/or bazel. Maybe you still share the whl file? I will be very grateful to you.

source: gharchive/issue

authors: Igor-Shabalin nathtest

license_type: permissive

license_source: github-api


text:
iOS Safe Area Bottom Drawer Fix

Attempted to fix this issue: https://github.com/nativescript-community/ui-drawer/issues/9 and updated the Vue demo.
Not sure how proper this fix is.
I created an additional height offset that is Application.ios.window.safeAreaInsets.bottom that adds to the height if it is iOS. Also forced rounding up with ceil because if it rounds down you will see a little bit of the view.

@keerl that actually sounds really nice! could you try in landscape before i merge and release this?

Good call, the same issue happens in landscape mode but now with right/left drawers not bottom. The interesting thing is that there are 2 different landscape modes (top of left side and top on right side) and the safe area offset will be different depending on the way the device is being held. I'll have to experiment with this and figure out the best solution.

That turned out to be easier than I thought. The left/right safe area size are the same when in landscape mode which isn't obvious to see visually with a notch on the phone. Anyways, used the left offset value in landscape mode. Let me know if that works for you.

okay how does that look? checking the orientation now

seems good !

source: gharchive/pull-request

authors: farfromrefug keerl

repo: nativescript-community/ui-drawer


text:
ファイル構成の見直し

ファイルのタイトルと内容が不一致になっているので，
ファイル構成の設計書を作成し，まずはリリース対象ファイルに反映する。

指摘事項

license: MIT


text:
Homebrewery Won't Save New Document

Error: Service Unavailable
Error: Service Unavailable
    at Request.<anonymous> (https://homebrewery.naturalcrit.com/homebrew/bundle.js:71831:19)
    at Request.Emitter.emit (https://homebrewery.naturalcrit.com/homebrew/bundle.js:1764:20)
    at XMLHttpRequest.xhr.onreadystatechange (https://homebrewery.naturalcrit.com/homebrew/bundle.js:72140:10)
{
  "status": 503,
  "method": "POST",
  "url": "/api/newGoogle/"
}

Take a look at the help info in discussion #1580 -- if that doesn't do it for you, come back here and the issue can be re-opened. For now, closing as duplicate.

repo: naturalcrit/homebrewery


text:
🛑 natureBook (natureBalance Logos) is down

In 091781b, natureBook (natureBalance Logos) (https://pdfs.naturebalance.net/v4/bundle/de/6ef29db1750534282d2441d610fb997c/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: natureBook (natureBalance Logos) is back up in 46ec24a.

repo: natureOffice-GmbH/upptime


text:
🛑 Basic is down

In 1952586, Basic (https://www.gemeinsam-ist-es-klimaschutz.de) was down:

HTTP code: 500
Response time: 972 ms

Resolved: Basic is back up in dc07729.


text:
VorbisWaveReader gets misaligned

I've found that the reader position gets misaligned, especially when seeking is involved.
Apparently, it's caused by VorbisWaveReader using time-based properties (TotalTime, DecodedTime) of underlying Vorbis reader to determine length and position, instead of sample-based ones (TotalSamples, DecodedSamples).
I copy-pasted the VorbisWaveReader code to my project and changed Length and Position definitions to the following:
public override long Length
{
    get { return _reader.TotalSamples * _waveFormat.BlockAlign; }
}

public override long Position
{
    get
    {
        return _reader.DecodedPosition * _waveFormat.BlockAlign;
    }
    set
    {
        if (value < 0 || value > Length) throw new ArgumentOutOfRangeException("value");

        _reader.DecodedPosition = value / _waveFormat.BlockAlign;
    }
}

It did the job for me - I got a fully functional and correctly aligned reader with that.
Could you please update the VorbisWaveReader accordingly? I'd go through with all the forking and PRing procedure, but the change is so small it's probably not worth it.

If you'd like to send me a pull request, I'll look it over and merge it.

This should now be fixed.

authors: Alphish ioctlLR

repo: naudio/Vorbis


text:
Epic: Jobs Improvements (2.X)

This will likely extend through the 2.1-2.3 milestone but tracking a "super epic" here.
TODO

[ ] Allow Jobs to "output" a File (ie Download to Browser)
[ ] #2830
[ ] Review plugin API to create new tab for specific job results page (storing tab data in database), e.g. stdout, command outputs, etc.
[ ] Job code can be mismatched between Nautobot and its workers (pain for both development and production)
[ ] Chain Job Executions

If succeed, call X
If fail, call Y

[ ] Job Multi-threading

Another one that would be nice would be the ability to render out HTML at the end of a job execution. Something along the lines of how template_content.py works currently:
class JobWithOutput(Job):
    def run(self, data, commit):
        do things
        output_tab(data_from_job_run)

    template_name = "example_plugin/panel.html"
    def output_tab(self, data_from_job_run):
        return self.render(
            self.template_name,
            extra_context={
                "results":  data_from_job_run,
            },
        )

And that would get called at the end of the job to "fill in" the output tab.

authors: brobare bryanculver

repo: nautobot/nautobot


text:
🛑 BarefootEdu is down

In db0755d, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in 44482ae after 7 minutes.

repo: navadhiti/upptime


text:
🛑 Harmony Bot Website is down

In 7110672, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in d2f03fc.


text:
🛑 Harmony Bot Website is down

In 0073485, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in fc58185.


text:
🛑 Harmony Bot Website is down

In 18f32e0, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in c20e3bd.


text:
🛑 Harmony Bot Website is down

In edd9f4c, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in e312d5e.


text:
🛑 Harmony Bot Website is down

In 1f0f9d0, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 4318e96.


text:
🛑 Harmony Bot Website is down

In 0e8f9a2, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in e92b79d.

Resolved: Harmony Bot Website is back up in e92b79d.


text:
🛑 Harmony Bot Website is down

In 8596b18, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in c9ba69c.


text:
Add support for pgvector via make

This is an earlier draft approach of https://github.com/navapbc/template-infra/pull/631 -- looking for feedback here on the approach (adding a new step to the set up) -- not on code style yet.

Closing in favor of https://github.com/navapbc/template-infra/pull/631

repo: navapbc/template-infra


text:
Master solo

Hi, in Faderport V2, when master track is selected, if you solo it, you can't unsolo it whith the button.
Thanks for your work!

Will put this on the list

authors: albornocero navelpluisje

repo: navelpluisje/reasonus-install


text:
test(PanoImageRenderer): added test for automatic high dpi support

Issue
#70
Details
added test for automatic high dpi support

Coverage increased (+0.2%) to 45.253% when pulling da3e5659b2993da278d2bdd17e42bfea51406796 on PanoImageRenderer#70 into 286f355e53dcd69fb732b38fb968b65963ccac5d on master.

authors: coveralls happyhj


text:
java 1.8 error

I hava some errors when I use java 1.8.
so I change java version to 1.7，it can run.
do you want to support java 1.8?

Java 1.8 is not support. but we preparing for the support.

Actually it was quite difficult job because underlying spring 3.X doesn't
support java 1.7.
However Last year, I've upgraded ngrinder spring version to 4.0 and have
the patch.  So it's a matter of time. We will merge it soon.
2016-03-16 10:58 GMT+09:00 권기수 notifications@github.com:

Java 1.8 is not support. but we preparing for the support.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/naver/ngrinder/issues/91#issuecomment-197110733

I'd like to have the patch. I need to run ngrinder in java 8, so please upload it to another branch?

In my PC. :-(

jdk 1.8 support version is pushed in the master. U can now clone the master and make a package. using
./install_maven_lib.sh && mvn package -Dmaven.test.skip=true

authors: GwonGisoo chengaomin junoyoon svenkost

repo: naver/ngrinder

license_source: bigquery


text:
web, fix getAgentList

The from query parameter is not used to filter agent.
And the default getAgentList API for the agent statistics should use the from/to version for better performance. The current one will return too much data, in our case, 800MB data returned from /getAgentList.pinpoint and unable to be displayed.

Codecov Report

Merging #7199 into master will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #7199   +/-   ##
=======================================
  Coverage   38.98%   38.98%
=======================================
  Files        3296     3296
  Lines       95966    95975    +9
  Branches    11968    11971    +3
=======================================
+ Hits        37408    37416    +8
  Misses      55583    55583
- Partials     2975     2976    +1

Impacted Files
Coverage Δ

...p/pinpoint/web/controller/AgentInfoController.java
0.00% <0.00%> (ø)

...pc/server/LoggingServerMessageListenerFactory.java
90.00% <0.00%> (-10.00%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
70.00% <0.00%> (-3.34%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75.00% <0.00%> (-3.13%)
:arrow_down:

...vercorp/pinpoint/web/vo/ApplicationAgentsList.java
66.66% <0.00%> (-2.57%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
18.60% <0.00%> (-1.17%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
80.28% <0.00%> (-0.71%)
:arrow_down:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
74.16% <0.00%> (+1.66%)
:arrow_up:

...cluster/zookeeper/ZookeeperClusterDataManager.java
54.83% <0.00%> (+1.93%)
:arrow_up:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
88.74% <0.00%> (+4.63%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

@yjqg6666 Thank you for your contribution
This patch makes sense.
However, it seems that this API is not being used.
Can you tell me where you are using it? Do you use it internally?

We made some change, let https://github.com/naver/pinpoint/blob/master/web/src/main/java/com/navercorp/pinpoint/web/controller/AgentInfoController.java#L61-L62 to call getAgentList(from,to), default to some time period. It's would be better to update UI part, the user can select a time period until now or time range.
http://125.209.240.10:10123/config/agentStatistic

authors: codecov-commenter emeroad yjqg6666

repo: naver/pinpoint


text:
Bygg av 20200422181427-ed382f7

Kommenter med /promote cluster, hvor cluster er et gyldig clusternavn

Cluster
dev-sbs
dev-gcp
prod-gcp

/promote dev-gcp

/promote dev-sbs

repo: navikt/engangsstonad


text:
Bygg av 20200618080817-871f3ae

Kommenter med /promote 20200618080817-871f3ae cluster, hvor cluster er et gyldig clusternavn

Cluster
dev-sbs
prod-sbs

/promote dev-gcp

/promote dev-sbs

repo: navikt/foreldrepengeoversikt


text:
Parameterize test

Junit 5 gjør det mulig å bruke Parameterized Tests. Siden testene for AAPVilkårsvurdering og DagpengerVilkårsvurdering i praksis var helt like, gjorde jeg et forsøk på å parametrisere disse. Usikker på om det ble mer lesbart, dog...

gjennomgått med Richard

repo: navikt/tiltakspenger-vedtak


text:
MacOS?

Metal has long worked on macos. Is it safe to remove the compiletime arch checks, or is there something that could go wrong implicitly?

@KTRosenberg I haven't worked with Metal on macOS I'm afraid, so not sure if checks can be just removed, or if any other checks are needed instead.  Sorry for not being active on this repo — I haven't touched it in a while, but if you would like to submit a PR that would be of huge help.

authors: KTRosenberg navoshta

repo: navoshta/MetalRenderCamera


text:
Auto-updating platform support should update CHANGELOG.md in pull request

This would be nice so I don't have to do it by hand each time 👀

Closing as changing the changelog by hand is not too much work.

authors: nbadal paul-dingemans

repo: nbadal/ktlint-intellij-plugin


text:
🛑 ESTAT is down

In 9cb2d8c, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 85999da.

repo: nbbrd/sdmx-upptime


text:
🛑 ESTAT is down

In 1fd1c42, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 7940179.


text:
🛑 ISTAT is down

In 9ed4aad, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 9b1d5df.


text:
🛑 ISTAT is down

In 54e8dd2, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 82b715d after 18 minutes.


text:
🛑 ESTAT is down

In cb43ab0, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in f272e18 after 15 minutes.


text:
🛑 ISTAT is down

In ad0c498, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 5a1c797 after 32 minutes.


text:
🛑 ISTAT is down

In 4c0909a, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in dd48e21 after 23 minutes.


text:
🛑 ISTAT is down

In 4081341, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 3213f48 after 5 minutes.


text:
🛑 IMF is down

In 9f51477, IMF (http://dataservices.imf.org/REST/SDMX_XML.svc/Dataflow) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IMF is back up in 28b6ee2 after 12 minutes.


text:
🛑 ESTAT is down

In 3aa1b4a, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 52491a2 after 6 minutes.


text:
🛑 ESTAT is down

In b5002a5, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 81b00cd after 23 minutes.


text:
🛑 NBB is down

In 05da963, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 553 ms

Resolved: NBB is back up in de9b700 after 7 minutes.


text:
🛑 NBB is down

In 2807520, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 653 ms

Resolved: NBB is back up in 5b5689b after 12 minutes.


text:
🛑 NB is down

In efd8443, NB (https://data.norges-bank.no/api/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NB is back up in 683dfd3 after 44 minutes.


text:
🛑 NBB is down

In 0474686, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 581 ms

Resolved: NBB is back up in 988e4c9.


text:
🛑 ISTAT is down

In a623fe8, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in dda0ec5 after 4 minutes.


text:
🛑 ISTAT is down

In cbbbee7, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 30357da after 4 minutes.


text:
🛑 NBB is down

In bc5f900, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 563 ms

Resolved: NBB is back up in 677a384 after 9 minutes.


text:
🛑 INSEE is down

In 3272571, INSEE (https://bdm.insee.fr/series/sdmx/dataflow/all/all/latest/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: INSEE is back up in 8b7cb70.


text:
🛑 ISTAT is down

In 00414ad, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 1123f6a after 2 hours, 13 minutes.


text:
🛑 NBB is down

In c09e2ab, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 661 ms

Resolved: NBB is back up in b663f1a.


text:
🛑 File access is down

In 1363288, File access (https://fyle.uk/file/fish) was down:

HTTP code: 0
Response time: 0 ms

Resolved: File access is back up in abecdc4 after 23 minutes.

repo: nbitzz/status


text:
Positional Arguments

Introduction
This PR introduces the ability to pull unparsed arguments from a flag via the DispatchWithArgs trait. This is accomplished by transforming all Evaluatable implementations to return a Value type. For now this ValueType simply contains a parameterized value and it's corresponding span data, This can be used to associate all inputs to their corresponding matches.
A example has been provided via dispatch_with_args.rs.
Linked Issues
resolves #48
Dependencies
Test

[x] Tested Locally
[x] Documented

Review

[x] Ready for review
[ ] Ready to merge

Deployment

Open Questions

Should the args as returned by DispatchableWithArgs be Value<String> to capture their positional metadata?

Should this be broken into two trait methods?

One that provides this as strings and one as args?

Should return_unused_args return Value<String>?

repo: ncatelli/scrap


text:
proposal for ACL objects with specified claim behavior

A short proposal that describes API objects to provide a safely ACLed catalog for resource creation.

I've created a slightly more specified version of the proposal that restructures the objects, controllers, and RESTStorage.   These changes allow ACL control to remain at the layers we need it, more completely specifies how claims are handled, provides an extension point for OpenShift types, and allows for additional modes to satisfy the instantiation of a claim.
@pweil- @ncdc @smarterclayton @kubernetes/rh-cluster-infra @liggitt @sjenning

cc @derekwaynecarr

@derekwaynecarr

I have been considering saying that all provisioners, including the "local" one, implement a provisioner API that is invoked as external HTTP calls. This would replace any in-process provisioning controllers with external ones (deployed using DeploymentConfigs?). The benefit of this is that we don't have one way to do in-process provisioning and another way to do out-of-process (dynamic) provisioning. WDYT?

That also brings the question of how we represent provisioners, and how we indicate in a posting that it should use provisioner X vs Y.

That also brings the question of how we represent provisioners, and how we indicate in a posting that it should use provisioner X vs Y.

I resolved that here by having a curated set of things and then an extensions section run by another controller.  Doing a remote call bring ups authentication questions: which user is performing this action and how do I identify as him to the remote endpoint?

repo: ncdc/kubernetes


text:
openstreetmapgeocoder throws error instead of callback (error)

Hi,
Im using  node-geocoder/lib/geocoder/openstreetmapgeocoder.js
line 108 has throw err; so instead of calling passed callback it throws an error.
If you dont want to crash the app you need to put geocoder.reverse() in try catch.
Defeats the purpose of callback.
Can you set it to call callback (err, null)

fixed in 2.20.2

authors: nchaulet wespen

repo: nchaulet/node-geocoder

license: mit


text:
document how to use --expression in HTTP Check

Document how to use the --expression and --path options in the HTTP Check. Also general cleanup and updating of the HTTP Check README.
Resolves #173

LGTM

authors: jkerry quaggoth

repo: ncr-devops-platform/nagios-foundation


text:
--version should not fail due to rclone.conf

What is your rclone version (eg output from rclone -V)

rclone v1.39-DEV

os/arch: freebsd/amd64
go version: go1.9.3

Which OS you are using and how many bits (eg Windows 7, 64 bit)

FreeBSD

Which cloud storage system are you using? (eg Google Drive)

n/a

The command you were trying to run (eg rclone copy /tmp remote:tmp)

My rclone.conf is owned by root for some reason.
ls -l $HOME/.rclone.conf
-rw-------  1 root  kcwu  937 Feb 26 14:19 /home/kcwu/.rclone.conf

Then rclone -V will fail with normal user permission.
$ rclone -V
2018/02/26 14:55:38 Failed to load config file "/home/kcwu/.rclone.conf": open /home/kcwu/.rclone.conf: permission denied

I expect "-V" should never fail for any reason.

Sounds like a reasonable request, the binary should report a version without a config accessible I guess.
Makes extra sense when you consider my recent PR forces rclone to do a version declaration to print at the end of the script. In your example this would fail on a fresh install of the install.sh (assuming it can't write a default rclone.conf in the ~/.config/rclone/ path.

I agree, version should never fail.  I expect this to be annoyingly difficult to fix though as it will involve lots of shuffling init sequences about :-(

authors: daniel-loader kcwu ncw

repo: ncw/rclone


text:
drive: TestObjectRemove integration test is failing

The first instance of this in the integration tests is
v1.39-217-g0861207a the previous OK run was v1.39-211-g572ee5ec
The only commit which touched the drive backend in that range was 70f07fd3ac2bc6e98dbf19b43da28d168e261aab but the changes in that are very localised to the dirchange
=== RUN   TestObjectRemove
--- FAIL: TestObjectRemove (73.07s)
	fstest.go:293: Sleeping for 1s for list eventual consistency: 1/6
	fstest.go:296: Flushing the directory cache
	fstest.go:293: Sleeping for 2s for list eventual consistency: 2/6
	fstest.go:296: Flushing the directory cache
	fstest.go:293: Sleeping for 4s for list eventual consistency: 3/6
	fstest.go:296: Flushing the directory cache
	fstest.go:293: Sleeping for 8s for list eventual consistency: 4/6
	fstest.go:296: Flushing the directory cache
	fstest.go:293: Sleeping for 16s for list eventual consistency: 5/6
	fstest.go:296: Flushing the directory cache
	fstest.go:293: Sleeping for 32s for list eventual consistency: 6/6
	fstest.go:296: Flushing the directory cache
	fstest.go:300:
			Error Trace:	fstest.go:300
			            				fstest.go:329
			            				fstests.go:938
			Error:      	Should be true
			Test:       	TestObjectRemove
			Messages:   	listing wrong, want
			            	  hello? sausage/êé/Hello, 世界/ " ' @ < > & ? + ≠/z.txt (100) or
			            	  hello_ sausage/êé/Hello, 世界/ _ ' @ _ _ & _ + ≠/z.txt (100) got
			            	  dir/file2 (100), dir/file3 (0), dir/file4 (0), hello? sausage/êé/Hello, 世界/ " ' @ < > & ? + ≠/z.txt (100)
	fstest.go:181:
			Error Trace:	fstest.go:181
			            				fstest.go:303
			            				fstest.go:329
			            				fstests.go:938
			Error:      	Should be true
			Test:       	TestObjectRemove
			Messages:   	Unexpected file "dir/file2"
	fstest.go:181:
			Error Trace:	fstest.go:181
			            				fstest.go:303
			            				fstest.go:329
			            				fstests.go:938
			Error:      	Should be true
			Test:       	TestObjectRemove
			Messages:   	Unexpected file "dir/file3"
	fstest.go:181:
			Error Trace:	fstest.go:181
			            				fstest.go:303
			            				fstest.go:329
			            				fstests.go:938
			Error:      	Should be true
			Test:       	TestObjectRemove
			Messages:   	Unexpected file "dir/file4"

Using the magic of git bisect...
git bisect start
git checkout 572ee5ec
( cd backend/drive && go test -v ) # check it is OK
git bisect good
git checkout master
git bisect bad
git bisect run bash -c 'cd backend/drive && go test -v'

finds after 20 mins or so...
70f07fd3ac2bc6e98dbf19b43da28d168e261aab is the first bad commit
commit 70f07fd3ac2bc6e98dbf19b43da28d168e261aab
Author: Remus Bunduc <remus.bunduc@gmail.com>
Date:   Thu Mar 8 22:03:34 2018 +0200

    fs: add ChangeNotify and backend support for it (#2094)

    * fs: rename DirChangeNotify to ChangeNotify

    * cache: switch to ChangeNotify

    * ChangeNotify: keep order of notifications

:040000 040000 0ee981de0101de07aded6234cd1704e483faa6a2 934751a8b231980958ee95941fe57e922cfaf646 M	backend
:040000 040000 dbc6dafe66c78822c25a0cd79e9d41e7bcdfe2d5 c1100dab8d7d46fedcb68dacd5ca7f0b0af2eb2d M	cmd
:040000 040000 7a91b0c9ffbbc285d38e5f457c8bfafbafdaee7e cb4e1cceaf245fa1d574f7470204737188993197 M	fs
:040000 040000 0b05dd6847fda1c49123c5b07a945537ca7d3ca6 b621023526f9c4724ed8f3c4bc000c1bf955641a M	fstest
:040000 040000 641a2df2a18a6fff662ace4c36d59bbdf75af577 a9a4081e1e796da8392ac918563218b0bcf639c7 M	vfs
bisect run success

70f07fd3ac2bc6e98dbf19b43da28d168e261aab was the commit we identified above so this isn't a big suprise.
Why though?
It seems the ChangeNotify test is leaving extra files lying around...


text:
rclone ncdu - Invalid argument

What is the problem you are having with rclone?
running
rclone ncdu myremote:
causes:
2018/09/05 15:20:39 invalid argument

and fails.
all other rclone functions with that remote are working well, including the rclone serve.`
What is your rclone version (eg output from rclone -V)
rclone v1.43
- os/arch: linux/amd64
- go version: go1.11

Which OS you are using and how many bits (eg Windows 7, 64 bit)
Arch Linux 64-bit
Which cloud storage system are you using? (eg Google Drive)
Google Drive
(also replicated with OneDrive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone ncdu myremote:
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
2018/09/05 15:23:42 DEBUG : rclone: Version "v1.43" starting with parameters ["rclone" "-vv" "ncdu" "myremote:"]
2018/09/05 15:23:42 DEBUG : Using config file from "/home/user/.config/rclone/rclone.conf"
2018/09/05 15:23:42 invalid argument

I'm closing this issue as the problem seems be resolved. The fixed error message should should be much clearer and point to the source of the problem.
Feel free to reopen this or create a new issue if the problem persists.


text:
Theme Fun Times

This is not ready for review or merging yet.
Theme Fun Times - Draft 2
Description
I made colors change with theme and sustain on refresh.
We can change things up plenty, but this is another starting point. :)
Type of change

[x] Bug fix
[x] New feature

This was a draft and will not be used.


text:
Preview

Merge master and write rspec tests for CreateBeehiveURL

Coverage increased (+0.13%) to 93.01% when pulling 4b327901cbdd78f57acc0e8110976fd1ecb64021 on preview into 380c4b5354f7066cfdd7f8dd47c8af49dd2654cf on master.

authors: coveralls danthewolfe

repo: ndlib/honeycomb


text:
"Running test..." takes up a lot of space

I'm running ghcid with a -T thing -W, where thing is a function that prints no output:
> thing
>

However, ghcid gives a ton of screen real estate for this test for some reason. My terminal currently looks like:
 18 | import Data.Text
    | ^^^^^^^^^^^^^^^^
Running test...

...done

The warning(s) here were mostly pushed off of the screen by thing running! If I don't pass -W, I see them all, of course.
Any idea what might be going on? Thanks!

It's deliberate. I try and clear the screen before running a test, but I can't remember exactly why. I'll have to take a look at the code for any hints...

I remember - you want the warning message (or All good) message to appear at the top of the screen, and you want to clear any previous stale messages that might be around still. The only way that ghcid has to do that is emit a page full of blank lines and leave the cursor at the bottom.
I'll try using cursorUp from the ANSI terminal and see if that helps.

This space messes up following the newest output in emacs compile mode because it works by always going to the end of the file. Is your use case something like that @mitchellwrosen ?
It would be nice to have a flag to disable emitting those spaces... or maybe I just need some more custom elisp to find the last non-space character :)

@codygman No, my use case was just the normal ghcid rapid feedback loop, plus re-running the application (via the repl) on every save

authors: codygman mitchellwrosen ndmitchell

repo: ndmitchell/ghcid


text:
Qualifies use of (!?) in order to build against extra 1.7.10

Running cabal build against master fails with
src/Hint/Fixities.hs:65:38: error:
    Ambiguous occurrence ‘!?’
    It could refer to
       either ‘Data.List.Extra.!?’,
              imported from ‘Data.List.Extra’ at src/Hint/Fixities.hs:22:1-22
           or ‘Data.Map.!?’,
              imported from ‘Data.Map’ at src/Hint/Fixities.hs:23:1-15
              (and originally defined in ‘Data.Map.Internal’)
   |
65 |     case compareFixity <$> (fixities !? occNameString lop) <*> (fixities !? occNameString rop) of
   |                                      ^^

src/Hint/Fixities.hs:65:74: error:
    Ambiguous occurrence ‘!?’
    It could refer to
       either ‘Data.List.Extra.!?’,
              imported from ‘Data.List.Extra’ at src/Hint/Fixities.hs:22:1-22
           or ‘Data.Map.!?’,
              imported from ‘Data.Map’ at src/Hint/Fixities.hs:23:1-15
              (and originally defined in ‘Data.Map.Internal’)
   |
65 |     case compareFixity <$> (fixities !? occNameString lop) <*> (fixities !? occNameString rop) of
   |                                                                          ^^

since Data.Map and Data.List.Extra are both open imports.  This patch simply qualifies the uses of (!?).  With this patch, the build succeeds.

Thanks! I've added a hackage package revision for 3.3.2 to require extra < 1.7.10, and added your patch in for a 3.3.3 release.

authors: GambolingPangolin ndmitchell

repo: ndmitchell/hlint


text:
Monospaced text is higher than regular text

Example:

(that last letter is a 't' if it bothers you)
This might be MacType's doing again, but I have MacType off for Notepad++.

This is just a style issue; you could adjust the appearance by adding some Custom CSS. This will be different based on the fonts available. Try, for example:
body {
  font: 15px helvetica, arial, sans-serif;
}

pre, code {
  font: 14px consolas, monaco, monospace;
}

It might be nice for a more complete default stylesheet to be included, but meanwhile the custom CSS provides a nice way to apply your own. (Note that there are currently some issues with custom CSS that you might need to be aware of).

Thanks for the CSS, but the same problem still happens.

Hi @heydojo
Do you have a concrete Markdown example text to reproduce?
Thanks

@nea please see below:

Some text ```some("code");``` some more text

(placed in a quote box so that it can be copied and pasted straight into a markdown document.)
Ensure that the preview is open and look at the output.
Thanks.

That's because HTMLRenderer cannot properly apply vertical-align: baseline to the monospaced element. The height of the element with monospaced text is smaller than its line box. When this is the case, HTMLRenderer always pushes (actually just leaves it there) the element to the upper side of the line box.
I've created some stupid hack to make baseline alignment work:
https://github.com/monoblaine/HTML-Renderer/commit/124ccb61f19c41b1f5590e45578b15a43cf39157

It works if the monospaced element's height is smaller than the line box. But it won't work for the opposite case.

i also suffer from this issue... but IMHO the code highlighting could/should be improved in general, as it is really hard to distinguish it from normal text (especially if it will be at the same hight :stuck_out_tongue_winking_eye:).
e.g. the highlighting as it is done at Gitlab (resp. have a look at the screenshot from @monoblaine: https://github.com/nea/MarkdownViewerPlusPlus/issues/41#issuecomment-389329448) or even as NppMarkdownPanel does it, would be quite nice.
btw: also blockquotes could use a little bit more obvious highlighting (e.g. the usual vertical line) to be much easier distinguishable.

authors: DJCrashdummy heydojo monoblaine nea oldmud0 stezmi

repo: nea/MarkdownViewerPlusPlus


text:
Modals should open with minWidth

See the history modal, on click it starts small, and expands to minWidth:

Smooth out the modal opening to a set width. Do this for all modals

This was not fixed as intended -- we will post pone fixing with an overall standardization of modals

repo: near-everything/canvas

license: Unlicense


text:
Display platform release notes / what's new?

Description
Consistent feedback from developers have been lack of awareness to new features that have been shipped. In efforts to help resolve this we can increase user awareness of recent changes made to near-discovery by displaying release notes as they happen.
Fortunately, we have existing design work and an example implementation that was created for NEAR Wallet.
Completion Requirements

[ ] Determine release notes format & content
[ ] Create simple landing page for current & archival release notes
[ ] Create toast notification or similar
[ ] Create visible link on near.org to recent updates

Resources
Previous implementation in Wallet -> https://github.com/near/near-wallet/issues/2074
Example:

Related: https://github.com/near/near-discovery/issues/546

@thisisjoshford we now have release notes auto created on each production release for near-discovery and near-discovery-components. Perhaps that's good enough for now and this can be closed?

I am happy to close the related issue https://github.com/near/DX/issues/18, but I still think there should be some way of notifying a logged-in near.org user of platform changes/updates. I would argue that a very small percentage of near.org logged-in users subscribe to near-discovery releases, and visibility is still low.
For me its still two parts:

[x] create regular releases w/ clear updates
[ ] surface this information to end users

authors: Ishatt charleslavon thisisjoshford

repo: near/near-discovery


text:
change license from dual apache/MIT to GPL as it uses nearcore

Fixes #333

Does GPL allows building contracts without revealing the source code? If not what's the crates from nearcore that we use that requires GPL?
I'd be against using GPL if we can avoid it. This is worst license than iTunes

Ok, it looks like we'll be able to get out of GPL once nearcore is out of GPL which should be high-pri, because it GPL is terrible and most software companies avoid it for a reason. They can't use it internally and that why can't contribute to the open source of the given GPL software

authors: evgenykuzyakov mikedotexe

repo: near/near-sdk-rs


text:
Batch export to Sender extension

Presentaion:
https://youtu.be/GX8Wr3SjlnI
Sender batch import build:
https://github.com/SenderWallet/sender-build/blob/main/sender-batch-import.zip

@AmazingBeerBelly this is looking good! I added a comment regarding a minor refactor and wanted to confirm the following:

We can address this in a followup but is it not possible to detect the extension and call it directly from the wallet app? Seems like this would be better UX
When importing the accounts on your side are you adding a new key and deleting the one that's passed to you? Is it possible to link to this code?

@AmazingBeerBelly this is looking good! I added a comment regarding a minor refactor and wanted to confirm the following:

We can address this in a followup but is it not possible to detect the extension and call it directly from the wallet app? Seems like this would be better UX
When importing the accounts on your side are you adding a new key and deleting the one that's passed to you? Is it possible to link to this code?

I recommended against it as that would put too much logic in the wallet codebase specific to sender I didn't want to introduce.  Logic like:

Is extension installed?
Did the user attempt to export?
Is user attempting to export?

I'd rather this logic live on their specific SPA versus ours, this will be for all other wallets that wallet.near.org supports exports to.

@AmazingBeerBelly  I added a refactor in AmazingBeerBelly/near-wallet#1 to resolve above comments. Aside from this please make sure we are adding new keys and deleting the passed in keys and we should be good to go 👍

@AmazingBeerBelly In my testing I was only able to import one account unfortunately. Please make sure all accounts in the payload are added to Sender and also make sure ledger accounts are supported via the ledger hd path passed in the payload

Thanks for your refactor @esaminu and I have merged this PR into my branch.
In my testing I can import multiple accounts. Could you provide some sample test case?
At present, the function of ledger accounts are still under development, so the import of ledger accounts are not yet supported.

@AmazingBeerBelly It's happening when some of my accounts are ledger accounts - maybe it's a parsing issue. I put some parsing code in this repl that you could reuse to make sure you are parsing the payload and disregarding hd paths correctly.
We should also add a isLedgerSupported to WALLET_OPTIONS in this case and not list ledger accounts in the "We found X active accounts" modal in this case
Finally, can we submit a transaction to delete the passed in key and add a new NEAR full access key to the account and use that in the Sender app?

@esaminu I can import these three accounts.
I have uploaded the latest Sender version to github. Maybe you need reinstall the Sender extension to make sure the code is latest.
https://github.com/SenderWallet/sender-build/blob/main/sender-batch-import.zip
Then open this link:
https://sender.org/transfer?keystore=NDQsMjksMzUsMiwxMDksMTExLDE0MiwxODUsMTc1LDIyMywyMjMsMTk5LDE0Nyw0NCwyMjUsNzMsMjMwLDEwNywxMjksOTcsMTY2LDc3LDExOCwyLDE4OCwxMjYsMzcsMjU0LDE5MiwxNTgsMjE0LDIyNiw1MiwyNTEsMjMyLDE3NiwyMzIsMjMyLDExLDI0NywxNjksMTEzLDE4NSwyNDAsMTg4LDEzNywxNTIsNTEsNzQsMTM0LDU0LDEwMSwxMDgsMTEzLDg3LDE1MCwxMjYsMTgwLDcxLDQyLDE3MCwyOCwxMjUsNTEsMTEzLDkwLDEzOCwxNDIsNTMsMTU1LDE1NCw2Myw5OCwyMTQsMTg0LDIzOSwyMjAsMjAxLDEyMSw0NywzMywxMDMsMTkwLDk2LDEyNSwyNDgsNjUsNTksMTE3LDE1NCwyMTgsNjcsNDUsMTU2LDE5NywxODAsMTY3LDM1LDc3LDIwMiwxOTEsMTE2LDE1NCwxMDcsMTIsMjIzLDE4MCwxNTMsMTY3LDE3NCwxNjIsMzYsMjMwLDc5LDQwLDIwNSw2NCwyNyw2MCw2MSw3MCwyOCwyMjEsMTAxLDMxLDI1MSwyOSw5OSwxMTcsMTQsOTUsMjksMTQ2LDIxMCwxMTEsMTgzLDc0LDgwLDExNyw0NiwxNzEsMTc2LDE3NiwyMzMsMjUwLDIwMCw0LDE4NSwyNywxNTYsNjAsMjIxLDIwOSwxMjUsMjQ0LDEwMSwyMTgsMTE2LDgwLDE0NSwxMiwxMiw0MCwyNDYsMjE4LDIxOCw1OCw2OSwxODgsMTUzLDM4LDIxLDcxLDIyMiwxMzUsMTI4LDQ0LDM2LDg4LDg2LDExOSw5LDE5MCwxODAsMTQ2LDU3LDE0MywxOTAsMjM0LDE4OCwxNjEsMCwzMSwwLDExNiw0MiwyNTEsMTU2LDQ2LDIzLDE5NSwyMzMsMTg4LDIyLDE2Nyw4OCwyMDIsMzMsMTIwLDEyLDk3LDE3MSwyMzIsNDAsMTQ3LDEzNyw3Myw3LDE1NCwxMjYsMTA0LDI0OSw5NSwxOTYsNjAsMjMxLDY2LDIwMywxNTUsMjIxLDE1MCw0LDExNSw1MiwxOSw1MywxMTEsMjI4LDk4LDIyNywxMjIsMjUyLDg5LDQ3LDExMywyMjksMTEsMTI3LDczLDE4MCwxMjksMTg3LDQ1LDcsMjE4LDEwMCwyMDMsNzYsMjI2LDExMCw2NCw3Nyw3NywxMjIsMTg4LDE5Miw4OSwxOTMsMTEzLDQ4LDc4LDE1NywxMzIsOTUsMjI1LDI0NiwyMDcsMTMzLDI1MywxMTQsMjQ0LDE3OSw0OCwxNzgsMjYsNjYsMTE5LDIwOSwxNjYsMjExLDEwLDIwLDE2NSwxODMsMTQ2LDE0MCwyNTAsMjUyLDE0Myw4LDM4LDIzLDIxMCwyNTEsMTgsNCwxMDksNjMsMTE2LDI1MiwxNTQsMTE4LDE2NCwyMjUsMTQ0LDU5LDU1LDg3LDE4MiwyMDgsMTE3LDExNCwxODAsOTYsMTIwLDIyOSwyMTAsMTc5LDYwLDEwNiwxMjAsMjMzLDIzNywxMzgsMTQyLDY5LDIyOCwyMiwxNzEsOTMsMTk2LDEzNSwxMDQsMTgyLDE2NiwxNDk=&network=testnet
Import the key, and import success.
Here is my test screen shot:

And for last question, Sender is not support to send transaction to delete the passed in key and create new full access key to the account. If you think it's a important feature, we can add this feature as soon as possible.

authors: AmazingBeerBelly agileurbanite esaminu

repo: near/near-wallet


text:
minor fix neth not show on metamask mobile

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Type of change.

[x] FIX - a PR of this type patches a bug.
[ ] FEATURE - a PR of this type introduces a new feature.
[ ] BUILD - a PR of this type introduces build changes.
[ ] CI - a PR of this type introduces CI changes.
[ ] DOCS - a PR of this type introduces DOCS improvement.
[ ] STYLE - a PR of this type introduces style changes.
[ ] REFACTOR - a PR of this type introduces refactoring.
[ ] PERFORMANCE - a PR of this type introduces performance changes.
[ ] TEST - a PR of this type adds more tests.
[ ] CHORE - a PR introduces other changes than the specified above.

Hi @andreapn , thanks for your effort with this PR.
Unfortunately, Neth supports only desktop browser extension, so it's better do stay hidden from mobile UI.
You can access Neth from mobile on this link if you want to confirm this.

authors: DamirSQA andreapn

repo: near/wallet-selector


text:
[NEAT-256] test issue

test

comment on GH

repo: neat-run/linear-to-github


text:
[ENH] Re-enable QHUB_SECRETS

We need to re-enable this tooling cited in the docs. Which was originally created to solve #13.

Did we ever consider using sops?
I've used it before and it's a pretty decent way to handle secrets.

But I am really open, and I think the other would be as well, to add something as sops, due to its huge compatibility to a variety of resource (such as Vault)

superseded by #787

authors: trallard viniciusdc

repo: nebari-dev/nebari


text:
[BUG] - Contributor workflow comment trigger does not work properly

Describe the bug
By commenting /bot run tests as a maintainer on a PR, we should be able to trigger some workflows that are usually not run for regular contributors. This is done through this workflow
https://github.com/nebari-dev/nebari/blob/6b38c8c3215b3ce7683b4c83fe2ecb9aa79c34ac/.github/workflows/contributor.yaml#L1-L5
The trigger works fine until it comes to checking the permissions of the user sending the comment. We currently check for these roles
https://github.com/nebari-dev/nebari/blob/6b38c8c3215b3ce7683b4c83fe2ecb9aa79c34ac/.github/workflows/contributor.yaml#L31
They are correct according to the documentation:

author_association string Required
How the author is associated with the repository.
Can be one of: COLLABORATOR, CONTRIBUTOR, FIRST_TIMER, FIRST_TIME_CONTRIBUTOR, MANNEQUIN, MEMBER, NONE, OWNER

However, I and @iameskild as well, are listed as CONTRIBUTOR, although we should have MAINTAINER permissions.
Expected behavior
Being able to trigger contributor tests as maintainer.
OS and architecture in which you are running Nebari
GitHub repository
How to Reproduce the problem?
Comment /bot run tests on a PR, e.g. #1725. Curious to see what the bot spits out for people with elevated permissions.
Command output
No response
Versions and dependencies used.
No response
Compute environment
None
Integrations
No response
Anything else?
No response

There is this discussion https://github.com/orgs/community/discussions/18690 where people seem to have the same issue. @aktech Do you have any additional insights on this since your comment?

Looking at my settings, I'm listed as "moderator"

Meaning, maybe GHA is not wrong here, but our permissions are setup wrong?

Hey @pmeier (and @iameskild) you'd need to change your Organisation visibility to Public, for it to identify both of you as MEMBER as described in the comment I made there.

Here is mine:

You can change the toggle here (next to your username): https://github.com/orgs/nebari-dev/people

authors: aktech pmeier


text:
Update concurrency settings for Integration tests

Reference Issues or PRs
#2386

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

ref. for working config https://github.com/nebari-dev/nebari/actions/runs/8651753113


text:
Board never closes

Using this library with johnny-five. However, when I finish and go to shutdown the connection to the raspberry pi I get a message in the console Board Closing but this just hangs forever.
I've been just manually going in and running a kill -9 on the process. This isn't ideal but I couldn't find other ways to more gracefully close the connection.
Any suggestions?

Can you tell me how you're attempting to close the app?
Normally, I use process.exit() when I want the app to exit.

When I ran in repl mode, I used process.exit(), but it still just hung.
Now I'm running out of repl mode and I'm just sending it a termination signal (CTRL-C).
Any other suggestions for closing it?

That's strange, ctrl-c works for me, as does process.exit(). Can you tell me the following?

Node version
Node architecture (e.g. armv6 or armv7)
npm version
Raspberry Pi version
Which OS and version (e.g. Raspbian 2016-03-18)
Wiring Pi version, from gpio -v

Node version 4.2.1
npm 2.14.7
Pi 2 B v1.1
Raspian (should be latest version, I ran sudo apt-get upgrade)
GPIO 2.32
I have a few other boards of the same type lying around so I can test it on another one

One thing I'm realizing is a confounding variable is I'm also listening for events on a HID device (a USB RFID reader). So maybe somehow that's the thing that's still lingering and preventing the process from closing?
I'll run a few tests. The only reason I suspected the raspio is because it hangs at the "Board Closing" line with no other info.

Can you figure out which kernel you have? uname -r IIRC. Running sudo apt-get upgrade doesn't necessarily upgrade to the latest release, just like how running it won't upgrade Ubuntu 14.04 to 15.10.
I'm not sure that really matters anymore though, I bet it's the HID device. Raspi IO doesn't do any sort of cleanup code, and doesn't make use of the beforeExit event. Raspi IO doesn't make a connection to anything, unlike say the Arduino, so there's nothing to close or cleanup.

Ah Ok, so potentially I need to figure out how handle device.close() during shutdown. Sounds like that's my issue. I'll go ahead and close this issue since it's likely not your issue.
You're saying that johnny-five though has a beforeExit that I could potentially work with?

You're saying that johnny-five though has a beforeExit that I could potentially work with?

It's built in to Node.js itself: https://nodejs.org/dist/latest-v5.x/docs/api/process.html#process_event_beforeexit
Best of luck!

authors: nebrius wannabeCitizen

repo: nebrius/raspi-io


text:
docs: fix emphasis in source.rst

Hi. I was going over the docs for lib and noticed wrong markup for emphasis. Thought I'd drop this quick fix.
Thanks for the work by the way.

Thanks!

authors: nedbat tigarmo

repo: nedbat/cog


text:
Some tests fail with ifort-2021.10 and ifx-2023.2

Based off the main branch, the library now builds fine with both ifort and ifx (thanks!). Running the tests, however, some fail. There are more failures with ifort than with ifx. This is built with fpm and the debug profile which enables various diagnostics. Running in the release mode simply turns these into segfaults. So I attach the outputs of
FPM_FC=ifort fpm test >& athena-fpm-test-log-ifort-2021.10.txt
FPM_FC=ifx fpm test >& athena-fpm-test-log-ifx-2023.2.txt

My full compiler versions are:
ifort --version
ifort (IFORT) 2021.10.0 20230609
Copyright (C) 1985-2023 Intel Corporation.  All rights reserved.

ifx --version
ifx (IFX) 2023.2.0 20230721
Copyright (C) 1985-2023 Intel Corporation. All rights reserved.

athena-fpm-test-log-ifx-2023.2.txt
athena-fpm-test-log-ifort-2021.10.txt
In support of https://github.com/openjournals/joss-reviews/issues/6492

FWIW, all tests seem to pass with gfortran-12 in both debug and release modes.

Resolved in commit a8f0d619b0cdef6f3b1064367b400f7b16ab6772

Merged into main

authors: milancurcic nedtaylor

repo: nedtaylor/athena


text:
Run checkdoc/package-lint

Both of these programs will bring your code more in line with Elisp convetions/requirements for publishing in repositories such as MELPA.
package-lint
161 issues found:

1:0: error: package.el cannot parse this buffer: Search failed: ";;; color-tools.el ends here"
1:64: warning: You should depend on (emacs "24.1") if you need lexical-binding.
7:3: warning: You should include standard keywords: see the variable `finder-known-keywords'.
9:0: error: Expected (package-name "version-num"), but found dash.
9:0: error: Expected (package-name "version-num"), but found hsluv.
18:10: error: You should depend on (emacs "24.1") if you need `color'.
22:0: error: Aliases should start with the package's prefix "color-tools".
23:0: error: Aliases should start with the package's prefix "color-tools".
24:0: error: Aliases should start with the package's prefix "color-tools".
26:0: error: "ct/always-shorten" doesn't start with package's prefix "color-tools".
26:0: error: `ct/always-shorten' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
31:0: error: "ct/shorten" doesn't start with package's prefix "color-tools".
31:0: error: `ct/shorten' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
36:7: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
37:8: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
40:0: error: "ct/maybe-shorten" doesn't start with package's prefix "color-tools".
40:0: error: `ct/maybe-shorten' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
46:0: error: "ct/name-to-lab" doesn't start with package's prefix "color-tools".
46:0: error: `ct/name-to-lab' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
49:5: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
50:12: error: You should depend on (emacs "24.1") if you need `color-srgb-to-xyz'.
52:12: error: You should depend on (emacs "24.1") if you need `color-xyz-to-lab'.
54:0: error: "ct/lab-to-name" doesn't start with package's prefix "color-tools".
54:0: error: `ct/lab-to-name' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
57:12: error: You should depend on (emacs "24.1") if you need `color-lab-to-xyz'.
58:12: error: You should depend on (emacs "24.1") if you need `color-xyz-to-srgb'.
61:12: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
64:0: error: "ct/is-light-p" doesn't start with package's prefix "color-tools".
64:0: error: `ct/is-light-p' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
67:0: error: "ct/greaten" doesn't start with package's prefix "color-tools".
67:0: error: `ct/greaten' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
71:7: error: You should depend on (emacs "24.1") if you need `color-lighten-name'.
72:7: error: You should depend on (emacs "24.1") if you need `color-darken-name'.
74:0: error: "ct/lessen" doesn't start with package's prefix "color-tools".
74:0: error: `ct/lessen' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
78:7: error: You should depend on (emacs "24.1") if you need `color-darken-name'.
79:7: error: You should depend on (emacs "24.1") if you need `color-lighten-name'.
81:0: error: "ct/iterations" doesn't start with package's prefix "color-tools".
81:0: error: `ct/iterations' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
92:0: error: "ct/iterate" doesn't start with package's prefix "color-tools".
92:0: error: `ct/iterate' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
96:0: error: "ct/tint-ratio" doesn't start with package's prefix "color-tools".
96:0: error: `ct/tint-ratio' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
103:0: error: "ct/luminance-srgb" doesn't start with package's prefix "color-tools".
103:0: error: `ct/luminance-srgb' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
110:16: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
116:0: error: "ct/contrast-ratio" doesn't start with package's prefix "color-tools".
116:0: error: `ct/contrast-ratio' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
123:0: error: "ct/lab-change-whitepoint" doesn't start with package's prefix "color-tools".
123:0: error: `ct/lab-change-whitepoint' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
127:0: error: "ct/name-distance" doesn't start with package's prefix "color-tools".
127:0: error: `ct/name-distance' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
131:10: error: You should depend on (emacs "24.1") if you need `color-cie-de2000'.
134:0: error: "ct/transform-lab" doesn't start with package's prefix "color-tools".
134:0: error: `ct/transform-lab' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
141:0: error: "ct/transform-lch" doesn't start with package's prefix "color-tools".
141:0: error: `ct/transform-lch' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
147:14: error: You should depend on (emacs "26.1") if you need `color-lch-to-lab'.
150:36: error: You should depend on (emacs "26.1") if you need `color-lab-to-lch'.
151:60: error: You should depend on (emacs "26.1") if you need `color-lab-to-lch'.
157:0: error: "ct/transform-hsl" doesn't start with package's prefix "color-tools".
157:0: error: `ct/transform-hsl' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
159:8: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
160:12: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hsl'.
174:12: error: You should depend on (emacs "24.1") if you need `color-hsl-to-rgb'.
175:12: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
178:0: error: "ct/transform-hsluv" doesn't start with package's prefix "color-tools".
178:0: error: `ct/transform-hsluv' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
181:12: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
191:0: error: "ct/transform-prop" doesn't start with package's prefix "color-tools".
191:0: error: `ct/transform-prop' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
200:0: error: "ct/transform-hsl-h" doesn't start with package's prefix "color-tools".
200:0: error: `ct/transform-hsl-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
201:0: error: "ct/transform-hsl-s" doesn't start with package's prefix "color-tools".
201:0: error: `ct/transform-hsl-s' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
202:0: error: "ct/transform-hsl-l" doesn't start with package's prefix "color-tools".
202:0: error: `ct/transform-hsl-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
204:0: error: "ct/transform-hsluv-h" doesn't start with package's prefix "color-tools".
204:0: error: `ct/transform-hsluv-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
205:0: error: "ct/transform-hsluv-s" doesn't start with package's prefix "color-tools".
205:0: error: `ct/transform-hsluv-s' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
206:0: error: "ct/transform-hsluv-l" doesn't start with package's prefix "color-tools".
206:0: error: `ct/transform-hsluv-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
208:0: error: "ct/transform-lch-l" doesn't start with package's prefix "color-tools".
208:0: error: `ct/transform-lch-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
209:0: error: "ct/transform-lch-c" doesn't start with package's prefix "color-tools".
209:0: error: `ct/transform-lch-c' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
210:0: error: "ct/transform-lch-h" doesn't start with package's prefix "color-tools".
210:0: error: `ct/transform-lch-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
212:0: error: "ct/transform-lab-l" doesn't start with package's prefix "color-tools".
212:0: error: `ct/transform-lab-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
213:0: error: "ct/transform-lab-a" doesn't start with package's prefix "color-tools".
213:0: error: `ct/transform-lab-a' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
214:0: error: "ct/transform-lab-b" doesn't start with package's prefix "color-tools".
214:0: error: `ct/transform-lab-b' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
216:0: error: "ct/getter" doesn't start with package's prefix "color-tools".
216:0: error: `ct/getter' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
225:0: error: "ct/get-lab" doesn't start with package's prefix "color-tools".
225:0: error: `ct/get-lab' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
226:0: error: "ct/get-lab-l" doesn't start with package's prefix "color-tools".
226:0: error: `ct/get-lab-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
227:0: error: "ct/get-lab-a" doesn't start with package's prefix "color-tools".
227:0: error: `ct/get-lab-a' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
228:0: error: "ct/get-lab-b" doesn't start with package's prefix "color-tools".
228:0: error: `ct/get-lab-b' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
230:0: error: "ct/get-hsl" doesn't start with package's prefix "color-tools".
230:0: error: `ct/get-hsl' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
231:0: error: "ct/get-hsl-h" doesn't start with package's prefix "color-tools".
231:0: error: `ct/get-hsl-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
232:0: error: "ct/get-hsl-s" doesn't start with package's prefix "color-tools".
232:0: error: `ct/get-hsl-s' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
233:0: error: "ct/get-hsl-l" doesn't start with package's prefix "color-tools".
233:0: error: `ct/get-hsl-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
235:0: error: "ct/get-hsluv" doesn't start with package's prefix "color-tools".
235:0: error: `ct/get-hsluv' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
236:0: error: "ct/get-hsluv-h" doesn't start with package's prefix "color-tools".
236:0: error: `ct/get-hsluv-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
237:0: error: "ct/get-hsluv-s" doesn't start with package's prefix "color-tools".
237:0: error: `ct/get-hsluv-s' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
238:0: error: "ct/get-hsluv-l" doesn't start with package's prefix "color-tools".
238:0: error: `ct/get-hsluv-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
240:0: error: "ct/get-lch" doesn't start with package's prefix "color-tools".
240:0: error: `ct/get-lch' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
241:0: error: "ct/get-lch-l" doesn't start with package's prefix "color-tools".
241:0: error: `ct/get-lch-l' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
242:0: error: "ct/get-lch-c" doesn't start with package's prefix "color-tools".
242:0: error: `ct/get-lch-c' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
243:0: error: "ct/get-lch-h" doesn't start with package's prefix "color-tools".
243:0: error: `ct/get-lch-h' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
246:0: error: "ct/lab-lighten" doesn't start with package's prefix "color-tools".
246:0: error: `ct/lab-lighten' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
249:0: error: "ct/lab-darken" doesn't start with package's prefix "color-tools".
249:0: error: `ct/lab-darken' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
252:0: error: "ct/pastel" doesn't start with package's prefix "color-tools".
252:0: error: `ct/pastel' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
264:0: error: "ct/gradient" doesn't start with package's prefix "color-tools".
264:0: error: `ct/gradient' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
269:31: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
270:12: error: You should depend on (emacs "24.1") if you need `color-gradient'.
271:14: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
272:14: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
276:26: error: You should depend on (emacs "24.1") if you need `color-rgb-to-hex'.
277:7: error: You should depend on (emacs "24.1") if you need `color-gradient'.
278:9: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
279:9: error: You should depend on (emacs "24.1") if you need `color-name-to-rgb'.
283:0: error: "ct/make-color-meta" doesn't start with package's prefix "color-tools".
283:0: error: `ct/make-color-meta' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
288:0: error: "ct/make-hsl" doesn't start with package's prefix "color-tools".
288:0: error: `ct/make-hsl' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
289:0: error: "ct/make-hsluv" doesn't start with package's prefix "color-tools".
289:0: error: `ct/make-hsluv' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
290:0: error: "ct/make-lab" doesn't start with package's prefix "color-tools".
290:0: error: `ct/make-lab' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
291:0: error: "ct/make-lch" doesn't start with package's prefix "color-tools".
291:0: error: `ct/make-lch' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
293:0: error: "ct/rotation-hsluv" doesn't start with package's prefix "color-tools".
293:0: error: `ct/rotation-hsluv' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
298:0: error: "ct/rotation-hsl" doesn't start with package's prefix "color-tools".
298:0: error: `ct/rotation-hsl' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).
303:0: error: "ct/rotation-lch" doesn't start with package's prefix "color-tools".
303:0: error: `ct/rotation-lch' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).

checkdoc
 color-tools.el    12     info            Name emacs should appear capitalized as Emacs (emacs-lisp-checkdoc)
 color-tools.el    22     info            You should have a section marked ";;; Code:" (emacs-lisp-checkdoc)
 color-tools.el    32     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el    41     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el    41     info            Argument ‘color’ should appear (as COLOR) in the doc string (emacs-lisp-checkdoc)
 color-tools.el    47     info            Argument ‘white-point’ should appear (as WHITE-POINT) in the doc string (emacs-lisp-checkdoc)
 color-tools.el    55     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el    55     info            Argument ‘white-point’ should appear (as WHITE-POINT) in the doc string (emacs-lisp-checkdoc)
 color-tools.el    65     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el    68     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el    68     info            Argument ‘percent’ should appear (as PERCENT) in the doc string (emacs-lisp-checkdoc)
 color-tools.el    75     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el    75     info            Argument ‘percent’ should appear (as PERCENT) in the doc string (emacs-lisp-checkdoc)
 color-tools.el    97     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   104     info            You should convert this comment to documentation (emacs-lisp-checkdoc)
 color-tools.el   117     info            You should convert this comment to documentation (emacs-lisp-checkdoc)
 color-tools.el   124     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   124     info            First line should be capitalized (emacs-lisp-checkdoc)
 color-tools.el   124     info            Argument ‘name’ should appear (as NAME) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   128     info            You should convert this comment to documentation (emacs-lisp-checkdoc)
 color-tools.el   135     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   135     info            Argument ‘color’ should appear (as COLOR) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   142     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   142     info            Argument ‘c’ should appear (as C) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   157   1 warning         Use of deprecated ((lambda (hsl) ...) ...) form (emacs-lisp)
 color-tools.el   157   1 warning         Use of deprecated ((lambda (hsl) ...) ...) form (emacs-lisp)
 color-tools.el   158     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   158     info            Argument ‘transform’ should appear (as TRANSFORM) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   179     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   179     info            Argument ‘c’ should appear (as C) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   192     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   200     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   201     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   202     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   204     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   205     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   206     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   208     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   209     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   210     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   212     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   213     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   214     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   216   1 warning         argument ‘_’ not left unused (emacs-lisp)
 color-tools.el   217     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   225     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   226     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   227     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   228     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   230     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   231     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   232     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   233     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   235     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   236     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   237     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   238     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   240     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   241     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   242     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   243     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   247     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   250     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   265     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   265     info            Argument ‘with-ends’ should appear (as WITH-ENDS) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   284     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   288     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   289     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   290     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   291     info            All variables and subroutines might as well have a documentation string (emacs-lisp-checkdoc)
 color-tools.el   294     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   294     info            First line should be capitalized (emacs-lisp-checkdoc)
 color-tools.el   294     info            Argument ‘c’ should appear (as C) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   299     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   299     info            First line should be capitalized (emacs-lisp-checkdoc)
 color-tools.el   299     info            Argument ‘c’ should appear (as C) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   304     info            First sentence should end with punctuation (emacs-lisp-checkdoc)
 color-tools.el   304     info            First line should be capitalized (emacs-lisp-checkdoc)
 color-tools.el   304     info            Argument ‘c’ should appear (as C) in the doc string (emacs-lisp-checkdoc)
 color-tools.el   308     info            The footer should be: (provide 'color-tools)\n;;; color-tools.el ends here (emacs-lisp-checkdoc)
 color-tools.el   309   1 warning         the function ‘-rpartial’ is not known to be defined. (emacs-lisp)

@progfolio thanks, that's very helpful. TIL the / separator is considered an error-level raise (for package-lint, anyway)

@progfolio do you know how I can set the prefix to ct rather than color-tools?

ah, it's derived from the provide

ah, it's derived from the provide

authors: neeasade progfolio


text:
TypeError: Object # has no method 'createGain'

Hi,
On Android 4.3 I get the following error:
TypeError: Object #<AudioContext> has no method 'createGain'
Any ideas?
Karens

According to MDN, createGain requires webkit prefix for older browsers (e.g webkitCreateGain) however latest Chrome has already removed it so I can't test it yet. Can you check if webkitCreateGain exists?

I only have the ability to test on 4.4 through BrowserStack
createGain is available there.

I've pushed an update which will bypass the gain node if createGain() is not available.
Let me know how it goes. (Probably also slack off on the test case for this one. Will be a bit hairy to produce a non-flaky test case)

Nice. Thanks for the super fast response. I added the code. Let's see and wait if the error returns.

The error did not come back any more. Thanks

authors: karensg nehz

repo: nehz/ngWebAudio


text:
Added ability to use of custom attributes

Added ability to use of custom attributes on form elements (for example
'v-model' attribute for Vue). Attributes can be assigned via config
file. Also added ability to use of groups of custom attributes by
defining it via allowed prefixes array.

@syberon can you fix the two review comments. After that, I will merge your PR.
Thank you

No problem. I fixed this.

authors: neilime syberon

repo: neilime/zf-twbs-helper-module


text:
Blocks.txt

https://unicode.org/Public/UCD/latest/ucd/Blocks.txt

Implemented in https://github.com/nektro/zig-unicode-ucd/commit/af185fe4e1496189fd90f6649f133ae171eadd96

repo: nektro/zig-unicode-ucd


text:
Improve PROD_URL vs DEV_URL switching

We can probably make the PROD_URL and DEV_URL switch automatically by adding a gitignored file to populate the DEV_URL that we keep present on our local clones.

Can't really get the idea of a gitignored file to work, but we can use a URL parameter to determine "dev" mode. I think that would be tollerable.


text:
TG. How to display TG into Aggregate Transaction.

some transaction is wrap into aggregate transaction

Metadata / Restriction

Duplicate: #556

authors: AnthonyLaw OlegMakarenko

repo: nemgrouplimited/symbol-explorer


text:
MAINNET

Does this work with Mainnet?

No, the nem2-sdk works with the protocol layer latest version, Catapult, which isn't available in Main Net yet.

authors: MalcyX aleixmorgadas


text:
Documentation improvement - elevate conditions section so it's visible in the ToC

 Issue by davidoliverSP2
Friday Sep 20, 2019 at 10:58 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/1295

If a user is looking at the APOC documentation table of contents, the conditionals section is not surfaced.
This is buried a little too deeply within section 14 here:
https://neo4j.com/docs/labs/apoc/current/cypher-execution/conditionals/
Originally entered as a card on the Team-Documentation trello wall by @InverseFalcon
https://trello.com/c/5dmdDq1R/2322-apoc-labs-documentation-improvement-elevate-conditions-section-so-its-visible-in-the-toc

 Comment by conker84
Thursday May 13, 2021 at 13:09 GMT

@jexp is this still valid?

This can be closed once https://github.com/neo4j/docs-apoc/pull/347 is merged.

authors: hvub neo-technology-build-agent


text:
Multiple pattern match

Support for mutliple patterns in a match:
new Cypher.Match(new Pattern(), new Pattern())

MATCH ()-[]-(), ()-[]-()

This solution is incompatible with assignToPath

Alternatively, allow for concatenated matches:
new Match().match()

which should result in an equivalent Cypher

Will it be possible to go with matches this way ?
new Cypher.Match()
    .match()
    .where()
    .optionalMatch()

I'm exploring this library and am running into a similar issue. I was able to use Cypher.concat to get the cypher I wanted, but it wasn't very ergonomic. I think what @Eclegv mentioned above would do the trick.
MATCH (person:Person)-[:ACTED_IN]->(m:Movie)
WHERE person.name = $param0
OPTIONAL MATCH (person)-[:DIRECTED)-(directedMovie:Movie)
RETURN person, m, directedMovie

  const match1 = new Cypher.Match(pattern).where(person, {
    name: new Cypher.Param(name),
  });
  const match2 = new Cypher.Match(pattern2).optional();
  return Cypher.concat(match1, match2, Cypher.Return(person, movie, directedMovie);

Hi @Eclegv
Yeah, that option seems to be the way to go with this issue.
Until that is available the best solution at the moment is the one mentioned by @jhanggi

authors: Eclegv angrykoala jhanggi


text:
Add GCN on CORA example notebook

Based on #173

Probably easiest to review by checking out the branch and rendering the notebook :)


text:
Updated from 1.3 to 1.5 - reference dlls missing in output folder?

We have multiple projects and one project has the neo4j nuget package and reference. When referencing this project from other projects the neo4j dll is copied to the outputfolder of the other projects.
In version 1.3 all other referencing dlls that are used by the neo4j are also copied.
In version 1.5 only the neo4j dll is copied.
This creates problems when trying to create our setup files since the dlls are missing in these folders.
I guess this is now intended?

Hi @MPasadu,
Since version 1.4.2, we explicitly started supporting .NET Framework 4.5.2+ and if you're developing on .NET Framework rather than .NET Core, the driver no longer requires those references.
Ali

Thank you for the fast response.
We will get rid of the references and push .NET Framework 4.5.2 as lowest requirement!

authors: MPasadu ali-ince


text:
question regarding version 5

Hi devs.
I just started using your lib and was happy to find out you're supporting async.
I used your example as reference: https://github.com/neo4j-examples/movies-python-bolt
But soon I found out async is to be supported in v5.
Now I am in doubt whether to switch over to threading based model of wait for v5 to arrive.
So looking for a bit of advise here:
And not wanting to put any pressure on this, but could you give a clue when you expect v5 to be out ?

Thanks for reaching out. 5.0 is planned to be release in summer. There is not exact release date yet. Also note that the asyncio support of the driver is very new. So far we've received a lot of positive feedback and it seems quite stable but while we have a lot of tests there might still be some minor bugs in the async implementation we've missed.
Personally, I'd make it dependent on what you want from the driver. If you need maximum stability, you're probably better off using threading. If you don't plan on running a service that needs the most stability possible, async should be good enough (but you'd have to wait for 5.0 to release to get a maintained driver version with async support).
I'll close the issue as it's a support request and not a bug with the driver. Please feel free to keep commenting here if you have more questions.


text:
Some improvements on Migrations

This pull introduces/changes:

add_index and add_constraint helpers
A populate_id_property helper, as a replacement for the legacy AddIdProperty task
Splits migration helpers in submodules

Pings:
@cheerfulstoic
@subvertallchris

[Current coverage][cc-pull] is 97.26%

Merging [#1204][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master      #1204   diff @@
==========================================
  Files           182        184     +2
  Lines         10972      11005    +33
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          10678      10703    +25
- Misses          294        302     +8
  Partials          0          0

Powered by Codecov. Last updated by [f399fbf...76e9003][cc-compare]
[cc-base-branch]: https://codecov.io/gh/neo4jrb/neo4j/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/neo4jrb/neo4j/compare/f399fbfea267bde39bb8bd30522bdec14dc14a18...76e900382514802aca93a938ba649fc82c3f11a3
[cc-pull]: https://codecov.io/gh/neo4jrb/neo4j/pull/1204?src=pr

LGTM!  @subvertallchris ?

authors: ProGM cheerfulstoic codecov-io


text:
Implement docker auth for vm-builder

Problem description / Motivation
vm-builder might fail if we send too many requests to docker hub from our hosts:
2024/02/19 15:57:36 Setup docker connection
2024/02/19 [15](https://github.com/neondatabase/neon/actions/runs/7960954540/job/21732689596#step:5:16):57:36 Build docker image for virtual machine (disk size 1G): 369495373322.dkr.ecr.eu-central-1.amazonaws.com/vm-compute-node-v15:7960954540
Step 1/53 : FROM debian:bullseye-slim as libcgroup-builder
bullseye-slim: Pulling from library/debian
2024/02/19 15:57:38 toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Ref https://github.com/neondatabase/neon/actions/runs/7960954540/job/21732689596
To avoid this, we, usually, use authorised access to docker hub, but it seems docker go SDK doesn't pick up auth from DOCKER_CONFIG directory automatically (https://github.com/moby/moby/issues/39377#issuecomment-503589708), so we need to make it possible to pass docker user/password as additional vm-builder parameters.
Feature idea(s) / DoD

vm-builder has --docker-user/--docker-password parameters

Implementation ideas

Use https://docs.docker.com/engine/api/sdk/examples/#pull-an-image-with-authentication
Please note, that we're going to set these parameters from GitHub Secrets, so we should never print them in logs/error messages

Since we're doing docker login in CI (and locally), maybe it's better to rely on the credentials stored in the docker cli config (~/.docker/config.json)? As shown in the example in this comment.

Since we're doing docker login in CI (and locally), maybe it's better to rely on the credentials stored in the docker cli config (~/.docker/config.json)? As shown in the example in this comment.

Nice! Added it to the Issue description as an idea for implementation

Assigning to @bayandin, as there is a draft PR from him.

Just hit this here, I think: https://github.com/neondatabase/autoscaling/actions/runs/9574058662/job/26396646325?pr=974
Unassigning @bayandin ; the PR has been closed for now.

authors: Omrigan bayandin cicdteam sharnoff

repo: neondatabase/autoscaling


text:
vm-runner: arm support

Modify qemu arguments to run VM on arm machine
#1080

Perhaps, PR should be named something like "enable e2e tests on arm", with multiple commits, 1 per each component?

@Omrigan I am hesitant towards that title, because the PR does what it says - enables vm-runner to run ARM vms. There is one test modified to reflect that change. Plus there actually separate issue and PR about e2e tests on ARM.

@Omrigan @sharnoff what is the current state of review?


text:
Export NeonDbError

Can NeonDbError be included in the package exports to allow for instanceof narrowing in catch blocks like this.
import { NeonDbError } from '@neondatabase/serverless';
...
catch (e: unknown) {
  if (e instanceof NeonDbError) {
     // Do something
  }
}
...

Absolutely! I thought I'd done this already, but it must have slipped through the net. I'll release a new driver version shortly.

This is now in @neondatabase/serverless@0.5.7. Do let me know if you have any trouble with it.

Thank you!

repo: neondatabase/serverless


text:
Falha ao listar usuários

Ao clicar no botão de listar usuários na tela inicial o servidor retorna um erro 500

Este erro foi da API e já estão normalizado.

authors: icaromh neondotta

repo: neondotta/ProcureServicos


text:
trust_remote_code=True ??

docker compose logs --follow ...
image_to_text_generator  | 2024-11-18 01:11:31,018 - INFO - INFO: instantiating model...
image_to_text_generator  | 2024-11-18 01:11:31,021 - DEBUG - Starting new HTTPS connection (1): huggingface.co:443
image_to_text_generator  | 2024-11-18 01:11:31,281 - DEBUG - https://huggingface.co:443 "HEAD /vikhyatk/moondream2/resolve/2024-08-26/config.json HTTP/11" 200 0
image_to_text_generator  | 2024-11-18 01:11:31,437 - DEBUG - https://huggingface.co:443 "HEAD /vikhyatk/moondream2/resolve/2024-08-26/configuration_moondream.py HTTP/11" 200 0
image_to_text_generator  | 2024-11-18 01:11:31,658 - DEBUG - https://huggingface.co:443 "HEAD /vikhyatk/moondream2/resolve/2024-08-26/moondream.py HTTP/11" 200 0
image_to_text_generator  | PhiForCausalLM has generative capabilities, as `prepare_inputs_for_generation` is explicitly overwritten. However, it doesn't directly inherit from `GenerationMixin`. From 👉v4.50👈 onwards, `PreTrainedModel` will NOT inherit from `GenerationMixin`, and this model will lose the ability to call `generate` and other related functions.
image_to_text_generator  |   - If you're using `trust_remote_code=True`, you can get rid of this warning by loading the model with an auto class. See https://huggingface.co/docs/transformers/en/model_doc/auto#auto-classes
image_to_text_generator  |   - If you are the owner of the model architecture code, please modify your model class such that it inherits from `GenerationMixin` (after `PreTrainedModel`, otherwise you'll get an exception).
image_to_text_generator  |   - If you are not the owner of the model architecture class, please contact the model code owner to update it.

END OF LINE

Yes, this setting is required by the current tiny image-to-text generator / model we use.  See their repo here.
This isn't a carte blanche setting that allows code download from anywhere - but model weight downlaod from huggingface.

authors: Fuckingnameless neonwatty


text:
Implementation: Event handling

Background
I think there are 3 sub-topics to be discussed (we can move those to separate tickets if it gets out of hand):

Event Handler resolution
Event deserialization
Event replay

My take on it (WIP):
Event Handler resolution
If an event is published the corresponding handler need to be invoked.
In other frameworks that's often done via explicit handler registration, but IMO that's a part were we can provide some better integration with Flow and I like the current way we solve this:
By implementing some marker interface (EventListenerInterface) every public method that starts with on and expects an EventInterface as 1st parameter will be registered as handler for the respective event type (using compiled reflection, so it doesn't have a negative effect on runtime performance).
I'd like the aggregate and process manager event handling to use similar mechanics internally but I'm not yet sure how we could solve the requirement that they would have to register for a specific set of events, not just by their type (see https://github.com/neos/Neos.EventStore/issues/1 for a related issue).
Event (de)serialization
The current implementation uses zumba/json-serializer in together with a custom TypeConverter to reconstitute an event object from the serialized data in the store.
I like the idea of using the PropertyMapper to convert events from class to array vice versa but I don't understand why we need a 3rd party package for the type resolution as we should have all that information in the store anyways.
Event replay
Probably not relevant for plain CQRS based apps, but a fortiori for event-sourced systems is the requirement to replay certain events in order to update/initiate the read model state, i.e. when a projection was introduced/changed.
This feature is missing from the current implementation and IMO it plays together with the Event handler resolution

how we could solve the requirement that they would have to register for a specific set of events, not just by their type

Why not go a similar route as in the EventStore. A simple DTO that describes the filter and make that either a static property of the handler or a static method return value (in that case implementations could even go really fancy with static compilation themself).

Event (de)serialization

+1 for using PropertyMapper instead of third party dependency.

Event replay

Wouldn't that just resolve to "declare Read Models to replay -> find event types the Read Models are listening to (Reflection) -> query EventStore for those event types -> push events to Read Models". The hardest part is probably a good declarative syntax to define the read models to replay (some wildcard matching required).

I like the idea of using the PropertyMapper to convert events from class to array vice versa but I don't understand why we need a 3rd party package for the type resolution as we should have all that information in the store anyways.

Lazy, that's the only reason currently. And 👍 for a fully PropertyMapper based solution.

This feature is missing from the current implementation and IMO it plays together with the Event handler resolution

Need more time to think about this ...

Regarding the replay functionality, I started a bit in that direction yesterday while working on a Todo app implemented in both Mvc and Cqrs to get a better feeling for the differences and how they play together.
I don't think the Event Handler resolution plays a big (if any) role - after all you normally want to replay one or more Projections and not an Event type. So you end up reflecting one or more Listeners for the events they listen to and then just directly call the methods after querying the EventStore.
I therefore introduced a new interface and a trait and created a CLI CommandController:
interface ReplayableProjectionInterface
{
    // drop the projection and start from scratch
    public function drop();

    // get the list of Events this projection listens to
    public function projectedEvents(): array;
}

The trait implements projectedEvents() through static compilation.
Possibly an interface method "commit();" or the like would also be needed, because the replay command needs to finally persist the projection at some point.
Only thing I'm unsure about is where to put that - my feeling was that it should come with the EventStore with the current structuring: it has a hard dependency on the EventStore and it's querying mechanism and the Node.Cqrs package currently lies more downstream.

All working. Replayable Projections are covered with #47

authors: albe bwaidelich dfeyer


text:
Add test/conftest.py to PyPI sdist

Fixes https://github.com/neovim/pynvim/issues/367

To really fix #367, we should release a 0.3.3 after merging this.

repo: neovim/pynvim


text:
Resolution decreases during rendering

Resolution decreases during rendering
Thank you very much, I encountered a bug while using the CityGaussian viewer.
This viewer is based on VISER.  I set the resolution to 1920, the photo quality to 100, and the moving resolution to 1920, the photo quality to 100.
1.During my movement, there was a noticeable decrease in resolution. When I finished moving and stopped pressing the keyboard, the rendering result suddenly became clear.
For example ,from 28 seconds to 31 seconds in the video. This phenomenon is abnormal, theoretically the resolution should remain unchanged when moving.
2.When I finish moving and no longer press the keyboard, the rendering result is unclear.
For example ,within 1 minute and 38 seconds of the video and beyond. This phenomenon is abnormal, theoretically the resolution should remain unchanged after the movement is completed.
Note: At other times, the resolution remains unchanged after the movement ends.
I'm not sure if this is a bug in Viser or GSPlat, can you help me? thank you.
the vedio:https://www.youtube.com/watch?v=KvWrNXg3BeA

Hello! Looks like you made some progress on this in https://github.com/DekuLiuTesla/CityGaussian/issues/16, this doesn't look like a viser problem but please feel free to re-open if you're still having problems!

Hello! Looks like you made some progress on this in DekuLiuTesla/CityGaussian#16, this doesn't look like a viser problem but please feel free to re-open if you're still having problems!

thankyou
CityGaussian developer said they meet similar performance(https://github.com/DekuLiuTesla/CityGaussian/issues/16#issuecomment-2301189111)
So we guess these phenomenons are mainly attributed to VISER itself.(https://github.com/DekuLiuTesla/CityGaussian/issues/16#issuecomment-2297951437)

So we guess these phenomenons are mainly attributed to VISER itself

Viser isn't responsible for any rendering or resolution logic so this seems not possible!
It looks like you're running the viewer supplied by CityGaussian, which is based on gaussian-splatting-lightning and has a lot of logic for changing the resolution dependent on movement. If you're seeing unexpected resolution behavior that seems like the natural place to debug: https://github.com/DekuLiuTesla/CityGaussian/blob/main/viewer.py

repo: nerfstudio-project/viser


text:
fix(contract): change metadata judgement of epoch number

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:

Codecov Report

Merging #154 (6e2635c) into main (3d1149d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #154   +/-   ##
=======================================
  Coverage   37.12%   37.12%
=======================================
  Files          78       78
  Lines        5349     5349
=======================================
  Hits         1986     1986
  Misses       3363     3363

authors: ashuralyk codecov-commenter

repo: nervosnetwork/axon


text:
feat(rpc): add a rpc method

add the rpc method of estimateFeeRate to get the estimated fee rate for transaction commit in
expected blocks

Should we give an example of sendCapacity with estimating transaction fee which includes transaction size and estimating transaction fee rate ?

Should we give an example of sendCapacity with estimating transaction fee which includes transaction size and estimating transaction fee rate ?

I'll make it clear and update the example later.

authors: Keith-CY duanyytop

repo: nervosnetwork/ckb-sdk-js