Connected to PIA but returning original IP?

Hi, so i've set all this up but my testing is showing that it's not working at all.

I think I have my "/dev/net/tun" set up (Genuinely not 100% sure, not familiar with it)
A network has been created "vpnnet"
The file auth.conf has been created, and is being read properly as the logs show it connecting to PIA.
Your run command was used, with the only exception being the location of auth.conf changed (On the host side) and the network name changed to "vpnnet", and the location changed to New York.

So the container is declaring itself as unhealthy, and i've also attached a python-alpine container to it and have been running python commands, and that is also returning my original IP.
Is it possible that you could help me find out what is wrong? Thanks. Let me know if you need anything else and i'll hook you up.
Attached is the log from the container. Apologies about the formatting it was copied and pasted from Portainer.
log.txt

Hi there,
The /dev/net/tun seems created from the log so that's good. All the vpn
creation/connection seems good too!
The network vpnnet is only used to proxy ports so that you can access them
(i. e. a web ui).
Please test with:
docker run --rm --network=container:pia alpine:3.8 wget -qO-
https://ipinfo.io/ip
Does this retun the same IP address as running
wget -qO- https://ipinfo.io/ip
on the host machine?
I'm travelling until tonight so I'll test out the container this evening to
check everything works correctly if you're still having the issue. The
unhealthy problem shouldn't happen though I'll check that anyway.
Thanks!
Quentin
On Sun, Nov 4, 2018, 7:31 AM LDShadowLord<EMAIL_ADDRESS>wrote:

Hi, so i've set all this up but my testing is showing that it's not
working at all.

I think I have my "/dev/net/tun" set up (Genuinely not 100% sure,
not familiar with it)
A network has been created "vpnnet"
The file auth.conf has been created, and is being read properly as
the logs show it connecting to PIA.
Your run command was used, with the only exception being the
location of auth.conf changed (On the host side) and the network name
changed to "vpnnet", and the location changed to New York.

So the container is declaring itself as unhealthy, and i've also attached
a python-alpine container to it and have been running python commands, and
that is also returning my original IP.
Is it possible that you could help me find out what is wrong? Thanks. Let
me know if you need anything else and i'll hook you up.
Attached is the log from the container. Apologies about the formatting it
was copied and pasted from Portainer.
log.txt
https://github.com/qdm12/private-internet-access-docker/files/2545595/log.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/qdm12/private-internet-access-docker/issues/9, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AO7gRAPFUEWJ3xR-dZieju5PJRsjwHcbks5urnumgaJpZM4YNJp1
.

try with
docker run --rm --net=container:pia alpine:3.8 wget -qO-
https://diagnostic.opendns.com/myip
ipinfo.io might be blocked as a malicious hostname perhaps, I'll change
that...
The container can't access standard HTTP(s) using your original IP due to
the firewall (iptables) normally. What host OS are you using?
On Sun, Nov 4, 2018, 4:27 PM LDShadowLord<EMAIL_ADDRESS>wrote:

Unfortunately that specific command does not work, it throws a "bad
address" error
root@cynra:/home/docker# docker run --rm --network=container:pia
alpine:3.8 wget -qO- https://ipinfo.io/ip
wget: bad address 'ipinfo.io'
But the Python container I have attached to that container is returning my
original IP, so i'm very confident that it's not proxy-ing data correctly
through to PIA.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/qdm12/private-internet-access-docker/issues/9#issuecomment-435674120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AO7gRL1gri8KG28ViPTd1gZPToAjTpbkks5urvljgaJpZM4YNJp1
.

That command gives the same error, bad address.
I'm running Ubuntu 18.04.1 LTS, it's running as a virtual machine on ESXi.

That's likely to be the container not having internet access for an external reason. I unfortunately can't verify the latest version works until tomorrow, sorry about that (I'm missing my PIA credentials...).

I have tested it with US New York City with auth.conf in read-only mode as your log shows, on a fresh Linux install with the latest container and it works. It returns two different IP addresses as expected. Your container log seems also correct. So it's likely not related to the container but to your setup. Do you have a host firewall in place? I will close the issue for now.


Translate labels and dropdown items for settings dialogs

Think I got all or most of them this time.

Wow. Thanks a bunch @douglaselee!

Happy to help @travist!


Use lightweight ajax handler in GitHub

I'm sure that BitBucket has a similar event but I don't know its name

Awesome!. Thanks. This pull request make source code more readable and solve issue #4


error[E0603]: module rust is private

    Updating crates.io index
  Downloaded protobuf v1.7.4
  Downloaded protobuf-codegen-pure v1.6.0
  Downloaded protobuf-codegen v1.6.0
   Compiling protobuf v1.7.4
   Compiling protobuf-codegen v1.6.0
error[E0603]: module `rust` is private
 --> /home/maciej/.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-codegen-1.6.0/src/field.rs:5:15
  |
5 | use protobuf::rust;
  |               ^^^^

error[E0603]: module `rustproto` is private
 --> /home/maciej/.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-codegen-1.6.0/src/customize.rs:1:15
  |
1 | use protobuf::rustproto;
  |               ^^^^^^^^^

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0603`.
error: Could not compile `protobuf-codegen`.

To learn more, run the command again with --verbose.

What are you building exactly? What project? What command? What Rust version?
(Also, you are using ancient version of rust-protobuf)

I have the same problem, building an internal project, same protobuf-codegen-pure version.
rustc 1.32.0-nightly (14997d56a 2018-12-05)

(Also, you are using ancient version of rust-protobuf)

This seems to be the one protobuf-codegen-pure is using


Replace 'Self Service' for 'Service UI' text

Sooo it was pointed out 👉 : September 28, 2017 5:52 AM we're still throwing out 'Self Service' in some places, this does not align with da past edict which state,

Thou shal now be the Service UI, sans all self

This pr fulfills that edict.
Flagging ux to check that the words are alright.

Fixing name typo.  No UX review needed.


Required pandas version 1.0.3. conflicts with other packages

Describe the bug
On some machines pip install cape-privacy doesn't work and it says conflicting versions of pandas. Whereas, on others with pandas==1.0.3 DatePerturbation gives an error
ImportError: cannot import name 'values_from_object' from 'pandas._libs.lib' (/usr/local/lib/python3.7/dist-packages/pandas/_libs/lib.cpython-37m-x86_64-linux-gnu.so)
After uninstalling pandas 1.0.3 and installing the newest version of pandas, the method work
Screenshots

Desktop (please complete the following information):

OS: [Linux]
OS Version [21.04]
Python 3.9.5
Installed pip packages

Please loosen up pandas and numpy versions in setup.py and requirements.txt  @justin1121
I am using this package for my project.

If you also have installation problem, first
pip install cape-privacy==0.3.0 --no-deps
Then, copy the requirements.txt and change numpy and pandas versions in there. After, install the requirements.
pip install -r requirements.txt


[history-bash] remote unused export call; cleanup history.bash file

there is no point to call export HISTCONTROL="ignoredups" since it gets over-written by the next statement; so removed it and mentioned in comment
small cleanup of the comments

Thanks!


My solutions not showing in "Solutions section"

Hi,
My solutions no longer show up in the "solutions" section even thought i complete katas.
When i click "Compare with my solution" it shows up but it doesnt show up in the solutions.
I have had this problem for 2 days now and have no idea how or why it happened.
Any help ?
Codewars username : COLONELBIHI

I have the same problem, for 2 days too. And my Honor is not updated during these two days, no matter how many kata I solve...

Yep, I got the same problem for https://www.codewars.com/kata/597770e98b4b340e5b000071
It also didn't give any award for completion

I'm facing the same problem: Honor and "My Solutions" don't get updated since yesterday.
Site-events page gets updated.

Same here. Neither My Solutions nor Honour are updated.

+1

Here is a script to prove that I indeed should got more honor in kata-solving than I current have.

Same for me: my solutions and honor are not updated since yesterday.
The honor does still change here when solving a solution though: https://www.codewars.com/users/freeman42x/site-events

+1, this is also happening to me.

Seems like it's fixed 🎆

@kazk I think this is also fixed now.

The issue with background processing queue is resolved now (#1329) and I'm assuming this is also fixed. Feel free to let me know if it's not.

Thanks, it is indeed fixed for now.


Then how to watch jsx babel by grunt

Support questions are better asked on StackOverflow:
http://stackoverflow.com/questions/tagged/gruntjs
Paste in the link to the question here so others can follow ;)


Make SubredditFlair instances callable

This makes SubredditFlair work like SubredditRelationship. Includes redditor
argument. Deprecates SubredditFlair.__iter__.
Fixes #693

Thanks for tackling this issue! 🎆


Choosing stat files from file system

Working on fixed data sets is nice for development, but users would need to load their own data. It should be possible to read and visualize webpack stats "uploaded" by file input, according to order of builtAt timestamps. No file count or size restrictions for now. No persistence as well. RAM is the limit.

Done!


Add localStorage mock support

Fixes #43. Sorry for the delay in getting to this! 😅

Thanks for the quick review! 😄 I've addressed your comments in 34dc75d.

@alisdair thank you!
I'll try to add/update some other things over the weekend, and will cut a new release then!


Failed to parse (TRUE) because: The constructor TRUE is unknown.

I'm following along with the README and noticed a weird interaction between coalton and ASDF, whereby coalton gets confused if I try to reload it after restarting my inferior lisp (sbcl). For example:
First run, A-OK
On the first compile/load, everything is fine:
CL-USER> (ql:quickload :coalton)
To load "coalton":
  Load 1 ASDF system:
    coalton
; Loading "coalton"
..................................................
[package coalton].................................
[package coalton-user]............................
[package coalton-impl]............................
[package coalton-global-symbols]..................
......
(:COALTON)
CL-USER> (in-package :coalton-user)
#<COMMON-LISP:PACKAGE "COALTON-USER">
COALTON-USER> (coalton-toplevel
                (define (gg x) (if x (left 1) (right x))))
COMMON-LISP:NIL

Second run
But if I then slime-restart-inferior-lisp and reload, coalton gets confused.
CL-USER> (ql:quickload :coalton)
To load "coalton":
  Load 1 ASDF system:
    coalton
; Loading "coalton"
.
(:COALTON)
CL-USER> (in-package :coalton-user)
#<COMMON-LISP:PACKAGE "COALTON-USER">
COALTON-USER> (coalton-toplevel
                (define (gg x) (if x (left 1) (right x))))
; Evaluation aborted on #<COALTON-IMPL:COALTON-PARSE-ERROR {10040AF5A3}>.

The exact error is
Failed to parse (TRUE) because: The constructor TRUE is unknown.
   [Condition of type COALTON-IMPL:COALTON-PARSE-ERROR]

Restarts:
 0: [RETRY] Retry SLIME REPL evaluation request.
 1: [*ABORT] Return to SLIME's top level.
 2: [ABORT] abort thread (#<THREAD "repl-thread" RUNNING {10023F9B63}>)

Backtrace:
  0: (COALTON-IMPL::ERROR-PARSING (TRUE) "The constructor ~S is unknown." TRUE)
  1: ((COMMON-LISP:LABELS COALTON-IMPL::PARSE :IN COALTON-IMPL::PARSE-FORM) (MATCH X (TRUE (LEFT 1)) (FALSE (RIGHT X))))
  2: ((COMMON-LISP:LABELS COALTON-IMPL::PARSE :IN COALTON-IMPL::PARSE-FORM) (FN (X) (IF X (LEFT 1) (RIGHT X))))
  3: (COALTON-IMPL::PARSE-DEFINE-FORM-FUNCTION GG (X) (IF X (LEFT 1) (RIGHT X)))
  4: (COALTON-IMPL::PROCESS-TOPLEVEL-VALUE-DEFINITIONS ((DEFINE (GG X) (IF X # #))))
  5: ((COMMON-LISP:MACRO-FUNCTION COALTON-TOPLEVEL) (COALTON-TOPLEVEL (DEFINE (GG X) (IF X # #))) #<unused argument>)
  6: ((COMMON-LISP:FLET SB-IMPL::PERFORM-EXPANSION :IN COMMON-LISP:MACROEXPAND-1) #<FUNCTION (COMMON-LISP:MACRO-FUNCTION COALTON-TOPLEVEL) {52E143BB}> COMMON-LISP:NIL)
  7: (COMMON-LISP:MACROEXPAND (COALTON-TOPLEVEL (DEFINE (GG X) (IF X # #))) #<NULL-LEXENV>)
  8: (SB-INT:SIMPLE-EVAL-IN-LEXENV (COALTON-TOPLEVEL (DEFINE (GG X) (IF X # #))) #<NULL-LEXENV>)
  9: (COMMON-LISP:EVAL (COALTON-TOPLEVEL (DEFINE (GG X) (IF X # #))))

Workarounds
Any of the following workarounds can be used immediately after restarting sbcl.

Manually LOAD the file library.lisp after loading the system: (ql:quickload :coalton) (load (asdf:system-relative-pathname :coalton "src/library.lisp"))
Use (asdf:load-system :coalton :force t) instead of (ql:quickload :coalton)
Remove cached FASL files and recompile

In shell: $ rm ~/.cache/common-lisp/sbcl-1.4.16-linux-x64/home/ma/src/repos/coalton/src/*.fasl
In REPL: (ql:quickload :coalton)

I think maybe the side-effecty stuff at the top of compile-toplevel-define-type-form that appears to be registering the tycon and it's constructors needs to be pushed down into the macro expansion, possibly within an eval-when?
Proof-of-concept PR coming soon (hopefully)...

Thinking about this a bit more, perhaps things are not so simple as I had hoped (they never are!).
There seem to be at least three competing concerns here:

Definitions inside a single coalton-toplevel form need to be visible to each other at macro-expansion time.
Definitions should also be visible at :load-toplevel time, so that loading a precompiled FASL does the right thing.
Definitions should be re-definable, ideally without gratuitous warnings in the common case of compiling, then loading a file.

The corollary to (3) is that the definitions should only be registered in the global environment once, probably inside the macro form and possibly wrapped in an (eval-when (:compile-toplevel :load-toplevel :execute) ...). (I suspect the :compile-toplevel is not needed which means the eval-when is not needed, but, as usual, staring at the hyperspec section for Processing Toplevel Forms has left me less than certain...).
But pushing the tycon and ctor registrations down into the macro form means that the macro expander needs some other provision to know about in-process definitions. The current implementation already tracks an extra-tycons parameter for this purpose, and parse-type-expression is smart enough to lookup stuff in extra-tycons before trying the "global environment." Perhaps similar provisions could be made for ctors and the like. So far I have been ignoring other toplevel definition forms like define and declare, which may need similar treatment (haven't looked yet).
Maybe instead of just extra-tycons any of the process-toplevel-* functions (and whatever functions they call) could get passed some kind of environment object that tracks all type/ctor/value definitions, similar to the &environment defmacro parameter.
tl;dr - Not quite as simple as I had hoped. I should probably read and understand the coalton source (and maybe the MACROEXPAND-ALL chapter of this Dick Waters paper) before proceeding further :). I have other stuff I want to work on first, but will circle back to this eventually (famous last words).

This is a good thing to pick up on. I've felt uneasy about the compile-time side effects Coalton does. There needs to be a better way to manage it all.

Probably what needs to happen is side effects need to happen at macroexpansion time, but they also need to be put in the macroexpansion as well so the FASL loader catches them.
It seems to be "working" when I do that, e.g.
diff --git a/src/toplevel-define-type.lisp b/src/toplevel-define-type.lisp
index b016280..9e56c55 100644
--- a/src/toplevel-define-type.lisp
+++ b/src/toplevel-define-type.lisp
@@ -101,6 +101,14 @@ where
     ;; TODO: Structs? Vectors? Classes? This should be thought
     ;; about. Let's start with classes.
     `(progn
+       ;; Make sure database side effects are maintained.
+       (eval-when (:compile-toplevel :load-toplevel :execute)
+         (setf (find-tycon ',tycon-name) ,tycon)
+         ,@(loop :for (_ name ty) :in ctors
+                 :collect `(unless (var-knownp ',name)
+                             (forward-declare-variable ',name))
+                 :collect `(setf (var-declared-type ',name) ,ty)))
+
        ;; Define types. Create the superclass.
        ;;
        ;; TODO: handle special case of 1 ctor.

Note: PR in progress https://github.com/stylewarning/coalton/pull/14

The diff in #14 looks similar to what I did in #12. I'm struggling to remember now why I abandoned that PR. Can't remember if I stumbled on a bug or if I was just vaguely unsatisfied with it.


matplotx: init at 0.3.10

Description of changes
Package Matplotx, a Python library that provides a number of quality-of-life and quality-of-output features to users of Matplotlib.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

ciate your
reviews of other pull requests, especially simple package updates. Just leave a
comment describing what you have tested in the relevant package/service.
Reviewing helps to reduce the average time-to-merge for everyone.
Thanks a lot if you do!
List of open PRs: https://github.com/NixOS/nixpkgs/pulls
Reviewing guidelines: https://nixos.org/manual/nixpkgs/unstable/#chap-reviewing-contributions
-->

It looks fine except that imageio and pytest-cov are not needed.

@ofborg build python311Packages.matplotx


(BKR-1124) Pass info text to summary logger to print on file

[skip ci]
Spec test breaking here
summary_logger is the instance that logs the summary to terminal and the file.
print_test_result was passing the test_cases that failed to be notified using @logger instance here
I changed it to return the string and then am notifying it using the summary_logger instance.

@rishijavia if I'm understanding this right, it looks like you're losing the functionality of the error printouts if things aren't successful for the test, is that right? Have you looked at what the error/failure cases for this printing looks like before & after?
I'm wondering if maybe rather than swapping out the logger instead of using the convenience method, if the summary_logger should be passed into the convenience method, so we can keep the same functionality we had before, but we could now be able to rely on the summary_logger to write things down in both places?
Of course another question for this is whether or not we can change summary_logger's signature. Are these the only uses of it? Either way, this wouldn't be the worst, as it seems we could provide a default value that allows old signature use for the method anyway...

@kevpl you are right, we loose the color scheme we have defined for the @logger instance for terminal output. A thing to note though is that with the original code, we are using the same color for all the messages (for skip, failed, errored and pending) as we are using the .notify method for all which results to blue color.
Anyways, before submitting the PR I tried sending the summary_logger to the convenience method and was able to retain the color scheme of the @logger instance and was able to print the output on the file too, but whenever you call summary_logger.notify it would output on terminal too. And in this way we would have duplicate test cases printed on terminal:

By the @logger instance in blue
By the summary_logger instance in normal font color

I have yet to look into changing the summary_logger's signature and play around with that.

@kevpl so if I turn on color notifications for summary_logger from it's signature, I was able to get color scheme we have on @logger instance and was able to get the terminal output with the color scheme. But on the other hand, each of the line in file output starts with the terminal color code for the line for e.g.:
[00;00m[00;34mSkipped Tests Cases:
[00;00m[00;34m  Test Case acceptance/tests/cowsay.rb

Feel like leaving color off on summary_logger is the call to make .txt file more readable.
The other option I was able to come up is that we can make summary_logger quite at its signature so it doesn't output to terminal and let @logger instance take care of terminal output and summary_logger would print to file. But for this option, each message would have to be saved in a variable so we can notify it on both of our logger instances (doesn't seem like a good practice).

@rishijavia I agree, it seems that leaving color off on the summary_logger is the simpler option to make the text file usable, so let's go with that one for now.

ok to test

test this please

test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3842/

@rishijavia these changes still remove the ability to have errors have their stacktraces printed out, since we're not using the print_test_result method. I'm not seeing that addressed in our earlier conversation, am I just missing that?

@kevpl summary_logger is a Logger instance that prints at both terminal and the .txt summary file. I changed the functionality such that print_test_result returns a string and when I call  summary_logger.notify print_test_result(test_case) it logs it on terminal stacktrace and the .txt summary file.

@rishijavia ah, thanks for clearing that up for me! Everything looks good! 👍


Shareable link

With the new wasm frontend I lost the shareable link feature. I should add that back somehow.

Done with #79


Unknown type name 'esp_event_handler_instance_t' / implicit declaration of function 'esp_event_handler_instance_register'

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am using the latest version of esp32-wifi-manager
[x] I have searched open and closed issues to ensure it has not already been reported

Description
When compiling the default application or an own application using esp32-wifi-manager, the following error messages are issued:
wifi_manager.c:892:5: error: unknown type name 'esp_event_handler_instance_t'; did you mean 'esp_event_handler_t'?
wifi_manager.c:894:21: error: implicit declaration of function 'esp_event_handler_instance_register'
Steps to Reproduce

Clone esp-idf 4.1 (branch release/v4.1 or branch v4.1-rc)
Clone esp32-wifi-manager as per documentation. Branch: v3.2
cd esp32-wifi-manager/examples/default_demo
source export.sh
idf.py build

System Configuration
Ubuntu 20.04 AMD64
ESP IDF as specified above
esp32-wifi-manager v3.2
Additional information: Compilation works with the esp idf master .

Very very interesting. Something didn’t make the cut in the 4.1 release candidate but it’s unclear what it is.
Thank you for the report.
I’ll open an incident at esp-idf and see what they say.

Update.
As per usual, the answer often lies in the documentation.
Looking at:
https://docs.espressif.com/projects/esp-idf/en/v4.1-rc/api-reference/system/esp_event.html
or
https://docs.espressif.com/projects/esp-idf/en/release-v4.1/api-reference/system/esp_event.html
It appears 4.1 does not support esp_event_handler_instance_register yet and this is a feature that will come in 4.2.
I will update the README accordingly. As 4.2 is yet to release esp32-wifi-manager will only work with the master tree for now.

Updated documentation -- see https://github.com/tonyp7/esp32-wifi-manager/commit/87e1f7b5fdf5a138794121ca2965badc4a64b30a
Thank you again for the report

I'm facing the same issue when working with ESP-IDF 4.1.
 error: unknown type name 'esp_event_handler_instance_t'; did you mean 'esp_event_handler_t'?
Is there anyway to get around this build error while still using the 4.1 version.


[pugixml] Fix pkgconfig file

Describe the pull request

What does your PR fix? Fixes #

Add missing vcpkg_fixup_pkgconfig(), which was detected in
https://github.com/microsoft/vcpkg/pull/12151#issuecomment-651581440
Fix debug POSTFIX in pugixml.pc file using
pugixml-v1.10_fix_debug_pkgconfig.patch
based on upstream: https://github.com/zeux/pugixml/pull/363
This results in the following contents of pugixml.pc:
Release:
  Libs: -L${libdir} -lpugixml
Debug:
  Libs: -L${libdir} -lpugixml_d

Which triplets are supported/not supported? Have you updated the CI baseline?
All official triplets are supported

Does your PR follow the maintainer guide?
Yes

Awesome PR, thanks for also doing the legwork to get it fixed upstream!


Default system output volume is too low

I recently reduced the system output volume from a default of 100 to 75%, on the basis that if you're using some DACs, the output volume is far too loud and may cause damage to some systems.
As a result of that the standard Pi output is too low, and although it can be corrected by using the SYSTEM_OUTPUT_VOLUME env var, we should figure out some way to reduce the volume for affected DACs only and return the default to 100%.
 Front conversations

@chrisys we can write a script which checks the RESIN_HOST_CONFIG. Do you know some devices which are affected?

@AlexProgrammerDE I'll have to check again to be sure but I think it was the justboom-dac.

@chrisys I had the same problem. If you are you using the balenaCloud just go to your device and add a "Device Variable".
name: SYSTEM_OUTPUT_VOLUME
value: 99
that all! enjoy your music

btw: with the variable BLUETOOTH_DEVICE_NAME you can change the device name for Bluethooth/Spotify (its the same variable)

I have a similar issue, I changed the SYSTEM_OUTPUT_VOLUE to 100 and I hear the change and volume gets loud for like 2 seconds and the connection drops and then the volume drops back to the standard value. It is the change doesn't get saved

@pojashad  What do you use? Raspberry Pi 3+? or something else?

I have exactly the same issue as @pojashad, on a Raspberry Pi 3.

@pojashad What do you use? Raspberry Pi 3+? or something else?

Raspberry Pi 4 Model B

hey @pojashad are you streaming via bluetooth?

Possibly related forum thread here: https://forums.balena.io/t/balena-sound-low-output/61927
@tmigone do you know if either of the snapcast containers exert any control over the volume?

I think it might be this bug: https://github.com/balenalabs/balena-sound/issues/78

hey @pojashad @stef-1 are you streaming via bluetooth?

Yes I tried both bluetooth and airplay, same issue.

[sradevski] This issue has attached support thread https://jel.ly.fish/#/21dc01c9-4022-4d45-911e-e65126e3552b

[sradevski] This issue has attached support thread https://jel.ly.fish/#/ea051a55-afd5-4843-aac3-8adaa2bb1f74

@chrisys what about setting it to 100 and warning the user that it can get extremly loud on a DAC?

Alex that's my initial approach too, but if the user misses the warning it might end up damaging their speakers, I would be mad :P
I think this could be solved with 3.x because of how pulseaudio deals with volumes. @chrisys do you remember what DAC you experienced this with? We can try and see if it's better.

this solution is......
the container balena-sound_audio and balena-sound_bluetooth have the volumen at 75%. that reduce at 50% total
command for verifications is apk add alsa-utils alsa-utils-doc alsa-lib alsaconf and execute alsamixer and up volumen pleace excuse my english I'm noob

this solution is......
the container balena-sound_audio and balena-sound_bluetooth have the volumen at 75%. that reduce at 50% total
command for verifications is apk add alsa-utils alsa-utils-doc alsa-lib alsaconf and execute alsamixer and up volumen pleace excuse my english I'm noob

I've seen this happening when using the built-in sound output of the Raspberry. The SYSTEM_OUTPUT_VOLUME variable seems to be ignored (mine's set to 100), the alsamixer command shows 75%

I've seen this happening when using the built-in sound output of the Raspberry. The SYSTEM_OUTPUT_VOLUME variable seems to be ignored (mine's set to 100), the alsamixer command shows 75%

This was addressed back then with 3.0 release. Note that SYSTEM_OUTPUT_VOLUME was deprecated in favour of SOUND_VOLUME.


difference between master and published package in PyPi

I ask because there are features in master that I would like to use in one of my projects. For example AWSCognitoAuthentication.get_user_info

Hi @ybenitezf thanks for your interest. I'm not a developer anymore at cgauge so can't do much with it. Maybe @cpersico can look into this (cc @customergauge)

Ok, thanks


Source Control icon, the badge is periodically shown briefly

I have never experienced this before.
The left-side icon for "Source Control" periodically flashes a badge, that looks like a blue clock icon. The flash lasts for less than 0.5 seconds. Here is a screenshot.

The flash frequency was around every 5 seconds (loose estimate).
Now as I'm writing this, the flashing seems to have stopped. Maybe it lasted between 5 and 10 minutes.
It happened so many times, that I'm now sending a report to you.
I have no pending changes to my repo, so there should be no badge. IMHO a badge should only be shown if there is something severely wrong, and it takes focus away from my own coding project.

/needsMoreInfo including whether the problem still occurs if you temporarily disable all extensions.

The guidelines says how to If you want to quickly disable all installed extensions, there is a Disable All Installed Extensions command in the Command Palette and More Actions (...) drop-down menu., but I can't seem to figure out to follow these quick instructions. Perhaps make it more verbose.

Aha SHIFT+CMD+P opens a the Command Palette. It would be helpful if the instructions showed this keyboard combo, or that the gear icon in the bottom left corner.

With all extensions disabled, I once did see the a flash with blue clock badge. I think a badge should only be shown if something is very wrong. I'm clueless to what a blue clock symbol indicates.

The clock badge is a progress indicator that appears if some long-running code asks for it to be displayed. You will see this on the gear icon (bottom left) after you have used its menu to check for updates. If no update is available the clock only appears briefly. But if an update is found the clock displays while downloading.
I guess your SCM provider (maybe the git default one) is requesting a progress indicator while it performs some operations.

Aha SHIFT+CMD+P opens a the Command Palette. It would be helpful if the instructions showed this keyboard combo, or that the gear icon in the bottom left corner.

I think it is reasonable for most instructions to assume the reader knows what Command Palette is and how to access it. This is a fundamental feature of VS Code and is documented in the User Interface section of GET STARTED.
The upcoming "Getting Started" experience (previewing in Insiders, where it can be accessed from the Help menu) puts Command Palette as the first item in its "Learn the Fundamentals" section.

Yes, I use git. When a badge is briefly flashing, it takes attention away from programming. IMHO the brief flashing clock badge is not good ux.

Does the Git channel on the Output tab of the Panel area of the UI reveal what is happening at the time the clock appears?

I will keep the Source Control open and look out for what happens.
I have never used the Source Control tools. I use SourceTree for my many repos.

While the blue clock is shown, there is a blue bar that animates from left to right.
The flash is less than 0.5 seconds. Here is a screenshot.

Sometimes it happens as I'm typing. Sometimes it happens when I'm not doing any changes to the code. Sometimes it happens after I have been recompiling my Rust project from commandline and switches focus back to Visual Studio Code.
Maybe SourceTree touches the .git dir, causing Visual Studio Code to wake up.

Since you aren't using it, maybe use the context menu on the Source Control icon in the Activity Bar to hide it.

Thanks, I have now hidden the Source Control icon. However it doesn't fixes the brief flashes.

Thanks, I have now hidden the Source Control icon. However it doesn't fixes the brief flashes.

I'm not clear where you are seeing the brief flashes now that you have hidden the icon on which the blue clock was appearing. Can you paste a short recording (animated GIF or an MP4 file)?

For me concerned it's fixed, the Source Control icon is hidden, and I no longer see anything flashing, spoiling my focus on coding.
IMHO, it's not fixed, since hiding the Source Control icon is not a fix the deeper problem, that it's possible for a badge flash without providing a text message explaining what the issue seems to be.

/assign @eamodio


As the OD REST API, I want to make pre-warm calls to the SPS REST API

These calls should be independent of the actual SPS implementation/technology.
This will be (for release 23.1) the basic form of the call, which only includes node_count in the request.
A prerequisite of this ticket, is having the SPS API deployed.

Done see: https://github.com/unity-sds/unity-on-demand/blob/main/CHANGELOG.md#unity-release-231---2023-04-07


Add Fiscally sponsored organisations to the website - mvp

https://we-are-ols.org/open-incubator.html#fiscal-hosting is a little thin right now. We've already encountered one scenaro where
This issue is for a minimum viable representation, adding the RSE-AUNZ logo and link to their site and a short description to their site.

Thanks, @yochannah!
A thought - We also have a /fiscal-sponsorship page on the website.
Rather than fattening the thin section, would it make sense to:

add a "Current Partners" (or {{ improved_name }}) section to the bottom of this page, and
link more visibly to the fiscal-sponsorship page from /open-incubator?

What do you think?

yes! :)


Resetting the previous screen's state works only once

Using the Git master's version and react-native 0.43.
Basically I have those defined screens:
const myNavigator = StackNavigator({
    Members: { screen: MembersList },
    Chat: { screen: Chat }
});

My expected behavior is the following:

Opening the app, Members' list page by default, loading 300 members.
Clicking on one member in the list open the Chat page.
Clicking on back button should reset the whole MembersList component and therefore reload those 300 members (bad UX experience to force a refresh but I expect it since it's a conceptual example).
Clicking again on any member in the list to reach Chat page.
Clicking back button should AGAIN reset the Members' list state.

I managed to make the steps from 1 to 3 work with the following code within Chat component (I'm using Typescript):
export default class Chat extends Component<Props, State> {

    static navigationOptions = ({ navigation }) => ({
        title: 'Chat',
        headerLeft: (<Button title='click' onPress={() => Chat.goBack(navigation)} />)
    });

    private static goBack(navigation) {
        const resetAction = NavigationActions.reset({
            index: 0,
            actions: [NavigationActions.navigate({ routeName: 'Members'})]
        });
        navigation.dispatch(resetAction);
    }

    //........

However, in the step 5, state is not resetted.
I struggle to figure out the reason.
To sum up, my goal is to avoid caching a particular React component associated to a route.
Is it a known bug or did I misuse the reset feature?
Has anyone experienced it?

I noticed through the logs that the first "key" of Members' route is Init (when the app is launched).
Then, after each reset it goes to the same Init0 each time, maybe explaining this caching...
Weird...

@mica16 do you know how to fix it? I'm having same issue right now... 😃

I found the way to fix it by update the navReducer
const navReducer = (state, action) => {
    console.log('navReducer', state, action);
    try {
       ...
      if (action.type === 'Navigation/RESET') {
        const navAction = action.actions[0];
        return {
          ...state,
          routes: [{
            routeName: navAction.routeName,
            params: navAction.params,
            key: Utilities.uniqueId(), // write your function to generate route it
          }],
          index: 0,
        };
      }

      newState = AppNavigator.router.getStateForAction(action, state);
      return newState || state;
    } catch (e) {
      console.log('nav reducer error', e);
      return state;
    }
  };

Hi  @phuochau and @mica16, I am facing the same issue. Is possible to work around it without redux integration?
thanks in advance.

@rsavignon just tried react-navigation the first time for redux. The problem is when reseting the route, the route key is always Init0, so without redux, you just find the way to generate new route key for every RESET.

Pinging OP @mica16 since this issue is quite old and related to an old version of the lib. If no answer I'll close in 7 days.

Hi there @mica16,
In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it.
If you are still having the issue (especially if it's a bug report) please open a new issue that uses the new Issue Template to provide some more details to help us solve it.


Installer with 64-bit GHC should contain 64-bit Stack executable

As of now, the 64-bit installer contains the 32-bit stack.exe. If you create a new Stack configuration with stack init and then try to build it, Stack will tell you that it expects 32-bit GHC, which cannot be found. To build your project you have to call Stack with --arch x86_64 every time or add the setting to your stack.yaml manually.
This is because Stack always tries to use the same GHC architecture it was built with itself by default.

I'm testing a fix for this now

Can you test out the installers at:
https://github.com/fpco/minghc/releases/edit/untagged-b886736e205f1ac220b5
Pinging @3noch

The link doesn't lead to anything for me.

Alright, try this please: https://github.com/fpco/minghc/releases/tag/2015-08-13

@snoyberg Did you use the patched version of NSIS?

I don't know, I presume the non-patched. Where can I download the patched version from?

@snoyberg I can upload builds if you want, or you can follow the newly improved README instructions which describe how to do that.

It's the end of the day for me right now, so I'm about to turn in. If you don't mind uploading these round, I'd appreciate it :)

Sure.

I've tested it, it works correctly for both new 64 bit installers.

@rkarp Excellent. Thank you. I'm working on creating more "official" release builds. Those should be out by the end of the day.


Added yesql

Yesql is pretty useful for using named parameters and for building raw SQL queries by hand before submitting them to node-postgres, for example, instead of using Slonik or Knex.

Github link : https://github.com/pihvi/yesql

Thanks for the suggestion. I'm unfortunately going to pass on this one. I have a lot of PRs to review, so I'm not able to write a custom response.


Add steps and result to foldr expressions

This is good, but I need you to show me how they build up first.
Starting from when the first thing is picked out of the list.
In the way I did in the class, please.

Alright got it.


Angular 9 Support ?

I tried to update my project to Angular 9, but without having examined in too much depth, seemed to be having issues with angular-busy. For the time being canceled the update to Angular 9. Should anguler-busy work under Angular9 and/or are plans for a new version available?

Hi @flipZomb ,
Sorry for the delay caused by me not updating the library to latest angular.
I updated now the library to angular 9 and fixed the issues.
Please let me know if it works for you.
Thank you

Awesome !! Thank you so much for doing this so quickly.


How do I mock this for testing?

How/where do I setup/mock cookies for the cookie service to read?  I don't really want to create an entire mock class of my own if I don't have to.

Hello there!
How and where you mock cookies is up to your and/or your testing framework of choice. I would suggest checking out some of these resources, or creating a Jasmine Spy for the service (if you're using Jasmine, that is). (Here's how to do that.)
Cheers


Add sqlfluff  workflow

See here for an example as well: https://github.com/mergestat/fuse-examples/blob/main/.github/workflows/lint_sql.yml


What is the order of events?

I'm trying to figure out where "do once" initialization code should go for a widget. Intuitively, I thought that ready would fire before onData. However, it seems that we're regularly seeing onData before ready?
Is there a documented order somewhere? Is it: constructor, onData, ready, onData, onData … onData?

In short, there isn't a pre-defined order. I suggest trying to implement your widget in such a way that it doesn't matter what order the events occur. For example, the Graph widget will only process the onData event if the @graph is initialised: https://github.com/Shopify/dashing/blob/439182f3b91c6c3c0cb5b5c8f5bee2562cfff2d4/templates/project/widgets/graph/graph.coffee#L35.
If this is unreasonable or impossible, I suggest using a jQuery.Deferred to synchronise the asynchronous events.
Something like (untested):
...
libraryLoading: $.Deferred()
ready:
  @loadUpMyLibs();
  // call this when all init completed (might need to go in callback if lib init is async.)
  @libraryLoading.resolve();
onData:
  @deferred.done(@doMyStuff);
doMyStuff:
  // some stuff
...

To elaborate a bit on why there is no order...
onData is fired when there is a message received from the SSE EventSource: https://github.com/Shopify/dashing/blob/439182f3b91c6c3c0cb5b5c8f5bee2562cfff2d4/javascripts/dashing.coffee#L107-L115
ready is fired when the Batman.js view is 'ready': https://github.com/Shopify/dashing/blob/439182f3b91c6c3c0cb5b5c8f5bee2562cfff2d4/javascripts/dashing.coffee#L55-L56
A Batman.js view is considered ready when "the view's bindings have been initialized. The view may or may not be in the DOM." (http://batmanjs.org/docs/api/batman.view_lifecycle.html#ready)

Thanks. I did end up going with something similar. (Should your @deferred.done been @libraryLoading.done?)

Yeah, I had initially called it @deferred but decided @libraryLoading was a better name. Glad you were able to resolve your issue and thanks for closing this.


How to fine-tune a base model and what does adapter id mean?

For example, what's aarnphm/opt-6-7b-quotes here?
openllm start opt --model-id facebook/opt-6.7b --adapter-id aarnphm/opt-6-7b-quotes

This is the LoRA Adapters you can find on HuggingFace hub

--adapter-id allows you to serve and merge multiple LoRA weights into the base model. We decided internally that having a simplified fine-tune API is probably not the best UX for now, since you can pretty much find and modify scripts online to do fine-tuning based on your model of choice and your own datasets.
Or at least on my end I dont' see a lot of value add for having a LLM.tune API for now.


Two errors happen when running "make FC=gfortran"

the error script as following:
"""
Makefile:125: recipe for target '../libopenblas_piledriverp-r0.2.14.so' failed
make[1]: *** [../libopenblas_piledriverp-r0.2.14.so] Error 1
make[1]: Leaving directory '/home/lan/Packages/OpenBLAS/exports'
Makefile:89: recipe for target 'shared' failed
make: *** [shared] Error 2
"""
How can i solve such a problem?
Thanks.

Please post more of the error message - what you copied so far is just the summary telling us that "something" failed, nothing about the actual problem that led to it failing. Do you have gfortran installed ? Depending on your system (what is your hardware and operating system, by the way ?), you may have to install a separate package gfortran-devel as well.

@lan2720: Any updates on this, or can this bug report be closed ? (Depending on the circumstances, you may have to install the gfortran package for your operating system, or some related package probably named "binutils","build-essentials" or similar. If you did a build with different settings in this directory earlier, run "make clean" before the "make")

@lan2720 , I am going to close this issue. If you has any further questions, please create an issue. Thank you


Running adb server on the camera

Is there any way to get adbd running on the camera?
Ideally over wifi, which would make application developing and debugging a lot easier.
I poked around in the filesystem via telnet but it seems the adbd binary is missing?

Added adbd binary, started it using your Shell class from my own app, but the camera crashes as soon as Android Studio tries to install an apk (replicated using "adb install").

How did you added adbd binary?
I tried, but filesystem is read-only...or i doing something wrong(

Here's something for you to test. Unzip the file, install the apk, open the Tweak app, Enable wifi and adb with the checkboxes. You should then be able to connect to your camera by running adb connect <your camera's ip>.
I only tested this on my A6000 (Android 2.3.7), I'm not sure this will run on Android 4.1.2 (the newer cameras). Please test it and let me know!
OpenMemories-Tweak-test-adb-1.zip

@ma1co
I downloaded that file, installed apk, but when i enable adb(press checkbox) - it crashes and camera seems to be rebooting((
After that, camera did'nt worked correctly(black screen) until i removed application and formatted SD card(dont know how, but thats helped me)
Tested on Sony NEX-5R v 1.0.3

I installed the apk, and adb works \o/
But it always crashes after ca. 1 minute. This is the adb output:
01-01 00:01:01.502 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:01.502 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:01.504 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-14ms arg1=1 }
01-01 00:01:01.504 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:01.504 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-15ms arg1=1 }
01-01 00:01:01.504 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:01.510 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:04.522 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:04.522 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:04.523 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-13ms arg1=1 }
01-01 00:01:04.523 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:04.523 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-13ms arg1=1 }
01-01 00:01:04.523 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:04.530 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:07.542 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:07.542 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:07.543 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-13ms arg1=1 }
01-01 00:01:07.543 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:07.544 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-14ms arg1=1 }
01-01 00:01:07.544 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:07.550 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:10.562 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:10.562 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:10.563 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-13ms arg1=1 }
01-01 00:01:10.563 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:10.563 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-13ms arg1=1 }
01-01 00:01:10.563 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:10.569 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:13.582 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:13.583 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:13.583 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-14ms arg1=1 }
01-01 00:01:13.584 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:13.585 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-15ms arg1=1 }
01-01 00:01:13.585 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:13.589 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:13.853 588-614/? V/DAConnectionManagerService-JNI: arbiter callback: cmd=4
01-01 00:01:13.853 588-614/? D/DAConnectionManagerService-JNI: pthread cond signal - wake up a thread
01-01 00:01:13.854 588-646/? I/DAConnectionManagerService-JNI: language env isn't set
01-01 00:01:13.854 588-646/? D/DAConnectionManagerService-JNI: function :
01-01 00:01:13.854 588-646/? D/DAConnectionManagerService-JNI: function is NULL
01-01 00:01:13.855 588-646/? D/DAConnectionManagerService: onChange: state = 4
01-01 00:01:13.856 588-646/? I/ActivityManager: START {act=android.intent.action.MAIN flg=0x10200000 cmp=com.sony.scalar.dlsys.scalaralauncher/.ScalarABlackLauncher u=0} from pid 588
01-01 00:01:13.866 197-539/? I/WsClientWrap: [osal_sync_cb][154]
01-01 00:01:13.866 197-539/? I/RIGEL: [WINDOW SYSTEM] call <WindowClient_DI*>(window)->rglDI_flushVDF()
01-01 00:01:13.983 588-598/? I/WindowManager: Aspect: 169
01-01 00:01:13.983 588-598/? I/WindowManager: Aspect: 169
01-01 00:01:13.984 588-598/? I/WindowManager: Aspect: 169
01-01 00:01:13.984 588-598/? I/WindowManager: Aspect: 169
01-01 00:01:13.989 693-693/? D/ScalarALauncher: onNewIntent intent=Intent { act=android.intent.action.MAIN flg=0x10600000 cmp=com.sony.scalar.dlsys.scalaralauncher/.ScalarABlackLauncher }
01-01 00:01:13.989 693-693/? W/ScalarALauncher: setMode mode isn't changed(BLACK)
01-01 00:01:13.990 693-693/? D/ScalarALauncher: onResume start:1487585871577
01-01 00:01:13.990 693-693/? D/ScalarALauncher: onResume Gridview requestFocus
01-01 00:01:13.990 693-693/? D/ScalarALauncher: finishAndroid Comp
01-01 00:01:13.998 588-588/? D/DAConnectionManagerService: called finishComp
01-01 00:01:13.998 588-646/? D/DAConnectionManagerService: New Finish Action has effected!
01-01 00:01:13.999 693-693/? D/ScalarALauncher: onResume end:1487585871586
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: toFinishActivities is not null
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.app.hotspotis added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalaramarketis added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.app.wifisettingsis added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalarausbdlappis added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalaraappmanageris added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalarainstalleris added.
01-01 00:01:14.000 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalarainstalleris added.
01-01 00:01:14.001 588-646/? D/DAConnectionManagerService: com.sony.scalar.dlsys.scalaradisclaimeris added.
01-01 00:01:14.010 588-646/? D/ActivityManager: ************************************  show activity stack  ************************************
01-01 00:01:14.010 588-646/? D/ActivityManager: stack[0] : ActivityRecord{52afbb0 com.github.ma1co.openmemories.tweak/.MainActivity}
01-01 00:01:14.010 588-646/? D/ActivityManager:          : task.Affinity - com.github.ma1co.openmemories.tweak
01-01 00:01:14.010 588-646/? D/ActivityManager:          : state - PAUSED
01-01 00:01:14.011 588-646/? D/ActivityManager: stack[1] : ActivityRecord{5bb5838 com.sony.scalar.dlsys.scalaralauncher/.ScalarALauncher}
01-01 00:01:14.011 588-646/? D/ActivityManager:          : task.Affinity - com.sony.scalar.dlsys.scalaralauncher
01-01 00:01:14.011 588-646/? D/ActivityManager:          : state - RESUMED
01-01 00:01:14.011 588-646/? D/ActivityManager: ***********************************************************************************************
01-01 00:01:14.011 588-646/? V/DAConnectionManagerService-JNI: setState:state=5, flag=0
01-01 00:01:14.011 588-646/? D/DAConnectionManagerService-JNI: [upm_power_save_ok] finished
01-01 00:01:14.011 588-646/? D/DAConnectionManagerService-JNI: [DFS_ok] finished
01-01 00:01:14.011 588-646/? V/DAConnectionManagerService-JNI: ABT_set_state err=0
01-01 00:01:14.012 588-646/? D/DAConnectionManagerService-JNI: start waiting...
01-01 00:01:14.015 588-1350/? I/MountServiceCore-JNI: void android::android_server_MountServiceCore_stop(JNIEnv*, jobject)
01-01 00:01:14.015 588-1350/? I/MountServiceCore-JNI: void android::stop()
01-01 00:01:14.016 677-677/? D/AvindexProviderService: onReceive()# action = com.android.server.DAConnectionManagerService.ExitCompleted
01-01 00:01:14.017 588-1350/? D/MountServiceCore-JNI: stop wait, send cond signal!
01-01 00:01:14.017 588-1246/? D/MountServiceCore-JNI: received cond signal!
01-01 00:01:14.018 588-1246/? D/MountServiceCore-JNI: break loop
01-01 00:01:14.020 677-677/? I/_jniOsalUtil_: SendObjMsg OSAL send. srcId = 0x15e6137, osalErr = 0x0, msgId(android) = 0x10003, msgId(osal) = 0x10003
01-01 00:01:14.020 677-677/? I/_jniOsalUtil_: RecvObjMsg start OSAL Receive waiting...
01-01 00:01:14.024 677-677/? I/_jniOsalUtil_: RecvObjMsg messageId = 0x10004, srcId = 0x15e6137, osalErr = OK
01-01 00:01:14.024 677-677/? I/_InfraScalarMprWrapper_: InfraScalarMprWrapper::stopScalar#return ret = true
01-01 00:01:14.024 677-677/? D/AvindexProviderService: InfraScalarMprEventReceiver.stopScalar() success.
01-01 00:01:14.024 677-677/? D/AvindexProvider: onReceive()# action = com.sony.scalar.database.avindex.action.AVINDEX_DATABASE_UPDATED
01-01 00:01:14.031 693-693/? D/ScalarALauncher: onReceive intent=Intent { act=com.android.server.DAConnectionManagerService.ExitCompleted flg=0x10 }
01-01 00:01:14.031 693-693/? W/ScalarALauncher: setMode mode isn't changed(BLACK)
01-01 00:01:14.105 197-722/? I/GraphicsHAL: [flush][60] dequeue old signals
01-01 00:01:14.133 197-529/? I/GraphicsHAL: [flush][60] dequeue old signals
01-01 00:01:16.602 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:16.603 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:16.604 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-15ms arg1=1 }
01-01 00:01:16.605 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:16.605 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-16ms arg1=1 }
01-01 00:01:16.605 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL
01-01 00:01:16.609 588-636/? D/StateMachine: handleMessage: X
01-01 00:01:19.622 588-636/? D/StateMachine: handleMessage: E msg.what=131155
01-01 00:01:19.622 588-636/? D/StateMachine: processMsg: ConnectedState
01-01 00:01:19.623 588-636/? D/WifiStateMachine: ConnectedState{ what=131155 when=-14ms arg1=1 }
01-01 00:01:19.623 588-636/? D/StateMachine: processMsg: L2ConnectedState
01-01 00:01:19.624 588-636/? D/WifiStateMachine: L2ConnectedState{ what=131155 when=-15ms arg1=1 }
01-01 00:01:19.624 588-636/? D/WifiNative-ath0: doString: SIGNAL_POLL

a6300 Android 4.1.2

@alicepergatta You are right, this doesn't work on gen2 devices. Currently the adbd binary for armv7 only.
@jonasjuffinger Are you sure this isn't the auto-power-off feature of your camera? Try setting it to 30 minutes in the menu.

I'm sorry it works now.
This is absolutely amazing, installing apps with adb and getting debug output makes the developing so much better. Thank you.

@alicepergatta @jonasjuffinger Here's another version. This one should work on older cameras, too. Feel free to test it!
OpenMemories-Tweak-test-adb-2.zip

@ma1co
Now works fine!(at my NEX-5R fw: v1.0.3)
I not tested all functionality, but i successfully connected and executed shell comands)
Later i will try to debug application, and there will be more detailed report.

@ma1co
Yesterday i connected camera to charger and go to bed.
Today turned camera on and it didn'n worked correctly - only showed viewfinder image, no any GUI.
I tried ejecting SD card and battery, but than i understood that camera starting correctly after ~1 minute.
Seems to be adbd and everything needs to be stopped correctly...or i don't know
If debuggable application crashes - camera's GUI also restarts, again after ~1 minute.
Notwithstanding, adb works correctly and now my team can comfortably debug applications)

@alicepergatta Yes, this is a (somewhat) known problem. But it's not adb, it's the wifi.  After the crash, it performs some kind of cold boot, which can take a long time, especially on old cameras.
The same happens if an android app crashes, so I would always register an UncaughtExceptionHandler on the main thread.

I've just released v0.10 which includes the adb switch.

I've been wondering about that odd reboot behavior. Hadn't thought about it being wifi though. Thanks for the tip.


pager plugin does not work in IE11

The pager plugin hides all rows - even in your own demo page (http://tablesorter.com/docs/example-pager.html)

While being less perfomant, the "msie-only" code of the clearTableBody method also works for other browsers, you could probably get rid of the whole deprecated browser detection stuff this way.
Tested in FF 34.0.5, Chrome 39.0.2171.99, IE10 and IE11

Replace the code in the clearTableBody function as indicated below and it seems to work in all browsers:
CURRENT CODE:
if ($.browser.msie) {
function empty() {
while (this.firstChild)
this.removeChild(this.firstChild);
}
empty.apply(table.tBodies[0]);
} else {
table.tBodies[0].innerHTML = "";
}
NEW CODE:
var rowCount = table.rows.length;
for (var x = rowCount - 1; x > 0; x--) {
table.deleteRow(x);
}

Thanks @codeconqueror - that seems to work.

Or just use https://github.com/gabceb/jquery-browser-plugin to replace $.browser.
codeconqueror's solution breaks the pager functionality for me.

Thanks @voidpp - as I stated @codeconqueror's solution worked for me, but nice to know of alternatives!

Tablesorter uses jQuery, so you could simplify that code down to this:
this.clearTableBody = function (table) {
    $( table.tBodies[0] ).empty();
}


Next.js rewrites not working on amplify

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d29xyyagv8f0bn
AWS Region
us-west-2
Amplify Hosting feature
Not Applicable
Frontend framework
Next.js
Next.js version
13.2.1
Next.js router
Pages Router
Describe the bug
The rewrites in next.config.js are not working properly. I get a 404 when accessing pages that are normally accessible locally but not when deployed to amplify.
Expected behavior
I expect "/" to load the static homepage "/terms" to load the terms page and "/privacy" to load the privacy page. However, right now it is 404ing. I have even rolled back my amplify build to a previous bulid that worked before and still having the same issue.
Reproduction steps
Visit www.gobacknforth.com and notice that it 404s. If you check the next.config.js you'll see the rewrite for "/" is set up properly.
Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

this is happening also if you have basePath set


Feature request - Add Gab.ai for proofs

I don't know what else needs to be said.  I'd like to be able to use my https://gab.ai account for a proof.
I really appreciate Keybase and the work being done it!

https://github.com/keybase/keybase-issues/issues/2692

Whoops, the issue you referenced didn't come up in my search originally when I made this one...weird.  Closing in favor of keybase/keybase-issues#2692


CUDA error: 700 (0x2bc) cudaErrorIllegalAddress : an illegal memory access was encountered

Bladebit Chia Plotter
Version      : 3.1.0-dev
Git Commit   : e9836f8bd963321457bc86eb5d61344bfb76dcf0
Compiled With: gcc 11.4.0
[Global Plotting Config]
Will create 1 plots.
Thread count          : 16
Warm start enabled    : false
NUMA disabled         : false
CPU affinity disabled : false
Farmer public key     : xxxxxxxxxxxxxxxxxx367
Pool contract address : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Compression Level     : 7
Benchmark mode        : disabled
Warning: 16G mode is experimental and still under development.
Please use the --check  parameter to validate plots when using this mode.
Direct I/O not supported in 16G mode at the moment. Disabing it.
[Bladebit CUDA Plotter]
Host RAM            : 31 GiB
Plot checks         : enabled ( 2 )
Plot check threshold: 0.600
Selected cuda device 0 : NVIDIA GeForce GTX 1070
CUDA Compute Capability   : 6.1
SM count                  : 15
Max blocks per SM         : 32
Max threads per SM        : 2048
Async Engine Count        : 2
L2 cache size             : 2.00 MB
L2 persist cache max size : 0.00 MB
Stack Size                : 1.00 KB
Memory:
Total                    : 7.92 GB
Free                     : 7.84 GB
Allocating buffers (this may take a few seconds)...
Kernel RAM required       :<PHONE_NUMBER>   bytes ( 4749.08   MiB or 4.64   GiB )
Intermediate RAM required :<PHONE_NUMBER>   bytes ( 4320.07   MiB or 4.22   GiB )
Host RAM required         :<PHONE_NUMBER>   bytes ( 2048.00   MiB or 2.00   GiB )
Total Host RAM required   :<PHONE_NUMBER>   bytes ( 6797.08   MiB or 6.64   GiB )
GPU RAM required          :<PHONE_NUMBER>   bytes ( 6021.54   MiB or 5.88   GiB )
Allocating buffers...
Done.
Generating plot 1 / 1: d7ce4357f4139ba7acf4c1d2ba211981a8b2da90377004661b5a1226201ab726
Plot temporary file: /nvme/chia/output/plot-k32-c07-2023-12-11-03-01-d7ce4357f4139ba7acf4c1d2ba211981a8b2da90377004661b5a1226201ab726.plot.tmp
Generating F1
Finished F1 in 665.61 seconds.
Table 2 completed in 923.05 seconds with<PHONE_NUMBER> entries.
Table 3 completed in 1197.82 seconds with<PHONE_NUMBER> entries.
Table 4 completed in 1524.01 seconds with<PHONE_NUMBER> entries.
Table 5 completed in 1387.38 seconds with<PHONE_NUMBER> entries.
Table 6 completed in 1138.78 seconds with<PHONE_NUMBER> entries.
Table 7 completed in 831.97 seconds with<PHONE_NUMBER> entries.
Finalizing Table 7
Finalized Table 7 in 352.01 seconds.
Completed Phase 1 in 8020.65 seconds
Marked Table 6 in 49.38 seconds.
Marked Table 5 in 38.19 seconds.
Marked Table 4 in 38.14 seconds.
Marked Table 3 in 36.93 seconds.
Completed Phase 2 in 162.66 seconds
Compressing Table 2 and 3...
Step 1 completed step in 631.68 seconds.
Step 2 completed step in 451.55 seconds.
Completed table 2 in 1083.24 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.09% ).
Compressing tables 3 and 4...
Step 1 completed step in 481.10 seconds.
CUDA error: 700 (0x2bc) cudaErrorIllegalAddress : an illegal memory access was encountered
*** Panic!!! *** Fatal Error:
CUDA error cudaErrorIllegalAddress : an illegal memory access was encountered.
./bladebit_cuda(_ZN7SysHost14DumpStackTraceEv+0x53)[0x56302ebc6d93]
./bladebit_cuda(_Z9PanicExitv+0xf)[0x56302ed5827f]
./bladebit_cuda(+0xb9e7f)[0x56302eba9e7f]
./bladebit_cuda(_ZN15GpuUploadBuffer11UploadArrayEPKvjjjjPKjP11CUstream_st+0x549)[0x56302ebaa829]
./bladebit_cuda(_ZN15GpuUploadBuffer11UploadArrayEPKvjjjjPKj+0x13)[0x56302ebaaa33]
./bladebit_cuda(_Z22CudaK32PlotPhase3Step2R18CudaK32PlotContext+0x695)[0x56302eb8bc35]
./bladebit_cuda(_Z17CudaK32PlotPhase3R18CudaK32PlotContext+0x1286)[0x56302eb83756]
./bladebit_cuda(_ZN14CudaK32Plotter3RunERK11PlotRequest+0x122f)[0x56302eb7739f]
./bladebit_cuda(main+0xc1f)[0x56302eb6b2df]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f7dd8970d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f7dd8970e40]
./bladebit_cuda(_start+0x25)[0x56302eb6c9a5]

Under Ubuntu 22.08. 32G memory , NV1070GPU.

CHATGPT result:
It looks like you've encountered a fatal error in your CUDA program. The error message indicates a CUDA error with the code cudaErrorIllegalAddress: an illegal memory access was encountered. This error typically occurs when the program tries to access memory that it's not allowed to access.
Here are a few steps you can take to troubleshoot and fix the issue:
Check the CUDA Error Code:
The specific CUDA error code is 700 (cudaErrorIllegalAddress). This suggests a memory access violation. You should carefully review the parts of your code that deal with memory management, especially memory allocation, copying, and freeing.
Review CUDA Kernel Code:
If your code includes CUDA kernel functions (_Z22CudaK32PlotPhase3Step2R18CudaK32PlotContext, _Z17CudaK32PlotPhase3R18CudaK32PlotContext, etc.), review the corresponding kernel code to ensure there are no out-of-bounds memory accesses or other memory-related issues.
Check CUDA API Calls:
Review the CUDA API calls, especially memory-related functions such as cudaMemcpy, cudaMalloc, and cudaFree. Make sure that memory allocations are correct and that data is being transferred correctly between the host and the device.
Verify GPU Compatibility:
Ensure that your GPU is compatible with the CUDA version you are using. Some GPUs may have specific requirements or limitations with certain CUDA versions.
Memory Profiling:
Consider using CUDA memory profiling tools, such as NVIDIA Nsight or CUDA-MEMCHECK, to identify memory-related issues in your code.
Update CUDA Drivers:
Make sure you have the latest NVIDIA CUDA drivers installed. Outdated drivers can sometimes cause compatibility issues.
Check GPU Resource Limits:
Verify that you are not exceeding the GPU's memory limits. CUDA kernels may fail if they attempt to allocate more memory than is available on the GPU.
Review Recent Changes:
If the error started occurring after recent code changes, review those changes for potential issues.

Any idea how to solve it?

Same issue on Debian 12 with 16GB mode while 128GB mode works fine on the same setup.
GPU: GTX 1080 (as secondary while AMD is primary using MESA driver)
Driver: 545.23.08
CUDA: 12.3

same here
ubuntu 22.04 LTS
Driver:535
GTX 1070
anybody know which driver version this has been tested with ?


Add node packages

Description
This PR adds setup for including the autoprefixer and lazysizes Node packages.

autoprefixer should be added to the webpack config, right?

@bchiang7 Yes, it should haha I just pushed up some fixes that should address that