COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "idna" "decode">

--->  Building cl-idna
xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build
xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source
xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/system
Execute asdf:build-op at idna by SBCL
This is SBCL 2.4.8, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/package.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/package-tmp7LQ0A0VI.fasl
; compilation finished in 0:00:00.011
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/vector.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/vector-tmp74KGUNRZ.fasl
; compilation finished in 0:00:00.566
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/list.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/list-tmpCEL1YIM2.fasl
; compilation finished in 0:00:00.756
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/extended-sequence.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/extended-sequence-tmpHAMQABTV.fasl
; compilation finished in 0:00:01.502
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/api.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/api-tmpUPMG0IBO.fasl
; compilation finished in 0:00:04.651
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/documentation.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/documentation-tmpAKM32D0F.fasl
; compilation finished in 0:00:00.011
; compiling file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/package.lisp" (written 23 DEC 2011 02:25:44 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/package-tmp8UG37QJ5.fasl
; compilation finished in 0:00:00.008
; compiling file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/encode.lisp" (written 23 DEC 2011 02:25:44 AM):

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/encode-tmp65YV5VYW.fasl
; compilation finished in 0:00:00.347
; compiling file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode.lisp" (written 23 DEC 2011 02:25:44 AM):

; file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode.lisp
; in: DEFUN PUNYCODE-DECODE
;     (AREF IDNA::OUTPUT IDNA::I)
;
; note: deleting unreachable code

;     (< (- CHAR-CODE 65) 26)
;
; note: deleting unreachable code

;     (AREF IDNA::OUTPUT IDNA::I)
;
; caught WARNING:
;   Derived type of IDNA::OUTPUT is
;     (VALUES LIST &OPTIONAL),
;   conflicting with its asserted type
;     VECTOR.
;   See also:
;     The SBCL Manual, Node "Handling of Types"

; wrote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.8-macosx-ppc32/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode-tmpGO4MNX7G.fasl
; compilation finished in 0:00:00.244
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=267 "main thread" RUNNING
                                                          {11452741}>:
  COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "idna" "decode">

Backtrace for: #<SB-THREAD:THREAD tid=267 "main thread" RUNNING {11452741}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {12F84019}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {12F84019}>)
2: (INVOKE-DEBUGGER #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {12F84019}>)
3: (ERROR UIOP/LISP-BUILD:COMPILE-FILE-ERROR :CONTEXT-FORMAT "~/asdf-action::format-action/" :CONTEXT-ARGUMENTS ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)))
4: (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)))
5: ((SB-PCL::EMF ASDF/ACTION:PERFORM) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)
6: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION))
7: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">) [fast-method]
8: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1144B2E9}>) [fast-method]
9: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT))
10: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1144B2E9}>) [fast-method]
11: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method]
12: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna">)
13: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
14: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna">) [fast-method]
15: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/OPERATE:BUILD-OP IDNA)
16: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
17: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/OPERATE:BUILD-OP IDNA) [fast-method]
18: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<FUNCTION (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {1144B1BD}> :OVERRIDE T :KEY NIL :OVERRIDE-CACHE T :OVERRIDE-FORCING NIL)
19: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
20: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<FUNCTION (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {1144B13D}> :OVERRIDE NIL :KEY NIL :OVERRIDE-CACHE NIL :OVERRIDE-FORCING NIL)
21: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/OPERATE:BUILD-OP IDNA) [fast-method]
22: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ASDF/OPERATE:OPERATE (QUOTE ASDF/OPERATE:BUILD-OP) (QUOTE IDNA)) #<NULL-LEXENV>)
23: (EVAL (ASDF/OPERATE:OPERATE (QUOTE ASDF/OPERATE:BUILD-OP) (QUOTE IDNA)))
24: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:EVAL . "(require \"asdf\")") (:EVAL . #<(SIMPLE-ARRAY CHARACTER (296)) (setf asdf:*central-registry* (list* (quote *default-pathname-defaults*) #p"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idn... {118D2007}>) (:EVAL . "(asdf:operate (quote asdf:build-op) (quote idna))") (:QUIT)))
25: (SB-IMPL::TOPLEVEL-INIT)
26: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP))
27: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::START-LISP))
28: (SB-IMPL::%START-LISP)

unhandled condition in --disable-debugger mode, quitting
;
; compilation unit aborted
;   caught 1 fatal ERROR condition
;   caught 1 WARNING condition
;   printed 2 notes
Command failed: /opt/local/bin/sbcl --no-sysinit --no-userinit --non-interactive --eval '(require "asdf")' --eval '(setf asdf:*central-registry* (list* (quote *default-pathname-defaults*) #p"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lisp_cl-idna/cl-idna/work/build/system/" #p"/opt/local/share/common-lisp/system/" asdf:*central-registry*))' --eval '(asdf:operate (quote asdf:build-op) (quote idna))' 2>&1
Exit code: 1

That is truly weird. I just tried compiling this with SBCL 2.4.8 (on macos arm64), and that worked without a hitch. Do you have any other systems loaded other than IDNA?

@antifuchs Sorry, I do not know what that means about other systems being loaded. I can deactivate all Lisp ports aside of required dependencies and try again.

I was just trying to install the port: https://ports.macports.org/port/cl-idna
sudo port -v install cl-idna

This is on powerpc though.

Oof, I have no way to reproduce this, as I have no access to powerpc hardware and don't run macports.
Think your best chance is to report the issue to the macports maintainers. As I mentioned, ASDF on a plain sbcl 2.4.8 with quicklisp does manage to build the system, so maybe the macport of any of these libraries does something weird.
I'll close this issue, but feel free to point macports maint's over here & reopen if they find something I couldn't.

@catap Kirill, anything we can do about this error?

@barracuda156 I have no idea, and error quite unclear to say atleast.

@catap Just for an update, still fails with SBCL 2.4.10:
; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/extended-sequence-tmpHAMQABTV.fasl
; compilation finished in 0:00:00.825
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/api.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/api-tmpUPMG0IBO.fasl
; compilation finished in 0:00:04.402
; compiling file "/opt/local/share/common-lisp/source/cl-split-sequence/documentation.lisp" (written 28 MAY 2021 11:05:40 AM):

; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/share/common-lisp/source/cl-split-sequence/documentation-tmpAKM32D0F.fasl
; compilation finished in 0:00:00.010
; compiling file "/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/package.lisp" (written 23 DEC 2011 02:25:44 AM):

; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/package-tmp8UG37QJ5.fasl
; compilation finished in 0:00:00.008
; compiling file "/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/encode.lisp" (written 23 DEC 2011 02:25:44 AM):

; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/encode-tmp65YV5VYW.fasl
; compilation finished in 0:00:00.326
; compiling file "/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode.lisp" (written 23 DEC 2011 02:25:44 AM):

; file: /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode.lisp
; in: DEFUN PUNYCODE-DECODE
;     (AREF IDNA::OUTPUT IDNA::I)
;
; note: deleting unreachable code

;     (< (- CHAR-CODE 65) 26)
;
; note: deleting unreachable code

;     (AREF IDNA::OUTPUT IDNA::I)
;
; caught WARNING:
;   Derived type of IDNA::OUTPUT is
;     (VALUES LIST &OPTIONAL),
;   conflicting with its asserted type
;     VECTOR.
;   See also:
;     The SBCL Manual, Node "Handling of Types"

; wrote /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/.home/.cache/common-lisp/sbcl-2.4.10-macosx-ppc32/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/source/cl-idna/decode-tmpGO4MNX7G.fasl
; compilation finished in 0:00:00.227
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=267 "main thread" RUNNING
                                                          {1154F259}>:
  COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "idna" "decode">

Backtrace for: #<SB-THREAD:THREAD tid=267 "main thread" RUNNING {1154F259}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {13381121}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {13381121}>)
2: (INVOKE-DEBUGGER #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {13381121}>)
3: (ERROR UIOP/LISP-BUILD:COMPILE-FILE-ERROR :CONTEXT-FORMAT "~/asdf-action::format-action/" :CONTEXT-ARGUMENTS ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)))
4: (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)))
5: ((SB-PCL::EMF ASDF/ACTION:PERFORM) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">)
6: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION))
7: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "idna" "decode">) [fast-method]
8: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1154D269}>) [fast-method]
9: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT))
10: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1154D269}>) [fast-method]
11: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method]
12: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna">)
13: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
14: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/OPERATE:BUILD-OP > #<ASDF/SYSTEM:SYSTEM "idna">) [fast-method]
15: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/OPERATE:BUILD-OP IDNA)
16: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
17: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/OPERATE:BUILD-OP IDNA) [fast-method]
18: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<FUNCTION (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {1154D13D}> :OVERRIDE T :KEY NIL :OVERRIDE-CACHE T :OVERRIDE-FORCING NIL)
19: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
20: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #<FUNCTION (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {1154D0BD}> :OVERRIDE NIL :KEY NIL :OVERRIDE-CACHE NIL :OVERRIDE-FORCING NIL)
21: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/OPERATE:BUILD-OP IDNA) [fast-method]
22: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ASDF/OPERATE:OPERATE (QUOTE ASDF/OPERATE:BUILD-OP) (QUOTE IDNA)) #<NULL-LEXENV>)
23: (EVAL (ASDF/OPERATE:OPERATE (QUOTE ASDF/OPERATE:BUILD-OP) (QUOTE IDNA)))
24: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:EVAL . "(require \"asdf\")") (:EVAL . #<(SIMPLE-ARRAY CHARACTER (238)) (setf asdf:*central-registry* (list* (quote *default-pathname-defaults*) #p"/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/system/" #p"/opt/local/share/common-l... {1168B04F}>) (:EVAL . "(asdf:operate (quote asdf:build-op) (quote idna))") (:QUIT)))
25: (SB-IMPL::TOPLEVEL-INIT)
26: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP))
27: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::START-LISP))
28: (SB-IMPL::%START-LISP)

unhandled condition in --disable-debugger mode, quitting
;
; compilation unit aborted
;   caught 1 fatal ERROR condition
;   caught 1 WARNING condition
;   printed 2 notes
Command failed: /opt/local/bin/sbcl --no-sysinit --no-userinit --non-interactive --eval '(require "asdf")' --eval '(setf asdf:*central-registry* (list* (quote *default-pathname-defaults*) #p"/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_lisp_cl-idna/cl-idna/work/build/system/" #p"/opt/local/share/common-lisp/system/" asdf:*central-registry*))' --eval '(asdf:operate (quote asdf:build-op) (quote idna))' 2>&1
Exit code: 1


Remove support for js now that it's all in typescript

@balena-ci rebase

@balena-ci I self-certify!


multiple select boxes in single page

We are using multiple Select Boxes and in all the select boxes when we select like "add " crates new option for the select box and made it to be shown as selected. it works fine in all cases as we reinitialize the stuff as $("#something").material_select();
The problem appears when we create items for the select boxes the the latest select boxes give the right index i.e the selected one. others (the one form where we create the option) show the first index and not the one which is being shown as selected.
Basically When we reinitialize the select box with the id the older used select box shows the selected one but done holds the selected value.

Can you post a codepen?


Assert push arguments appear in call's environment

I root caused a bug (found by fuzzing) for a few days which was due to missing push arguments in the environment of a call. It appears that these are used for proper stack depth tracking, but this is a not so well documented property.
I have started to assert the IR integrity for push arguments in instance calls, but we should do this for the others too (right now IR does not seem clean).

I seem to have the IR clean except
(1) during regexp complation (TBD)
(2) during a [de]serialization trip
we have, before
    PushArgument(v2) specu repr=tagged #uses=0 #env-uses=2
    PushArgument(v0) specu repr=tagged #uses=0 #env-uses=1
    PushArgument(v3) specu repr=tagged #uses=0 #env-uses=1
    v13 <- StaticCall:12<EMAIL_ADDRESS>v0, v3, recognized_kind = DoubleFromInteger, result_type = T{_Double}) T{_Double} env={ v1, v0, v0, a0=PushArgument(v0), a1=PushArgument(v3) } env={ v1, v1, v0, v0, a0=PushArgument(v2) } env specu can-deopt repr=tagged tp=T{_Double} #uses=1 #env-uses=0

but after "RoundTripSerialization"
    PushArgument(v2) specu repr=tagged #uses=0 #env-uses=3
    PushArgument(v0) specu repr=tagged #uses=0 #env-uses=1
    PushArgument(v3) specu repr=tagged #uses=0 #env-uses=0
    v13 <- StaticCall:12<EMAIL_ADDRESS>v0, v3, recognized_kind = DoubleFromInteger, result_type = T{_Double}) T{_Double} env={ v1, v0, v0, a0=PushArgument(v2), a1=PushArgument(v0) } env={ v1, v1, v0, v0, a0=PushArgument(v2) } env specu can-deopt repr=tagged tp=T{_Double} #uses=1 #env-uses=0


feature - support caffe models

maybe possible to cherry pick some of this code
https://github.com/naru-hiyoko/simple-cnn-swift
https://github.com/noradaiko/caffe-ios-sample
http://deeplearningkit.org/wp-content/uploads/2016/01/DeepLearningKitPaper.pdf

should be able to hit up facebook for caffe2 ios code.


Incomplete work

Any work that is still needed to be completed by there it is partially gone fully done after then

Start adding additional users


Automated cherry pick of #8435: feature: support scoped policy that manage ui policies for domains&projects

Cherry pick of #8435 on release/3.5.
#8435: feature: support scoped policy that manage ui policies for domains&projects

/lgtm
/approve


training error

Traceback (most recent call last):
File "train.py", line 395, in
main()
File "train.py", line 322, in main
train(cfg, train_loader, model, criterion, optimizer, scaler,
File "/home/zhoup/work/download_source_code/yolop/lib/core/function.py", line 77, in train
total_loss, head_losses = criterion(outputs, target, shapes,model)
File "/home/zhoup/anaconda3/envs/yolop/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in call_impl
return forward_call(input, **kwargs)
File "/home/zhoup/work/download_source_code/yolop/lib/core/loss.py", line 50, in forward
total_loss, head_losses = self._forward_impl(head_fields, head_targets, shapes, model)
File "/home/zhoup/work/download_source_code/yolop/lib/core/loss.py", line 70, in _forward_impl
tcls, tbox, indices, anchors = build_targets(cfg, predictions[0], targets[0], model)  # targets
File "/home/zhoup/work/download_source_code/yolop/lib/core/postprocess.py", line 79, in build_targets
print(""*10, gj.clamp(0, gain[3] - 1))
RuntimeError: result type Float can't be cast to the desired output type long int

The version of pytorch should be 1.7.0


Pool provider is sometimes slow

Description
I wrote in the developer community here: https://developercommunity.visualstudio.com/t/macos-13-Pool-provider-seems-slow/10522135#T-ND10523938 Tong Wu told me to log a bug here.
We are often seeing this message in Azure Pipelines that pool provider is slow and often builds are stuck waiting for macOS-13 agents for upwards of 40 minutes. This is even though in our concurrent builds of 25 there are 20+ agents idling.

You can find some of the affected builds here:
https://trackman.visualstudio.com/Golf/_build/results?buildId=395103&view=results
https://trackman.visualstudio.com/Golf/_build/results?buildId=395072&view=results
It doesn't happen every time, but it happens several times on different pipelines during the day.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Agent name: 'Azure Pipelines 2'
Agent machine name: 'Mac-1700593125567'
Current agent version: '3.227.2'
Operating System
macOS
13.6
22G120
Runner Image
Image: macos-13
Version: 20231025.2
Included Software: https://github.com/actions/runner-images/blob/macos-13/20231025.2/images/macos/macos-13-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/macos-13%2F20231025.2
Runner Image Provisioner
2.0.312.1
Current image version: '20231025.2'
Is it regression?
yes
Expected behavior
Not having to wait upwards of 40 minutes for agent to become available
Actual behavior
Pool provider is slow and there is a long wait for agents
Repro steps
Just queue a macOS-13 vmpool build and observe

Hey @Cheesebaron. Thank you for reaching out, but there is nothing to do on the side of the runner images generation team. Please contact GitHub Support.

Nice to be sent from place to place to get support

@Cheesebaron we are facing the same issue here and changed to macos-13-arm64 which seems to work fine. So, maybe you could try that, if that image works for your needs, until they resolve the issue.

@Cheesebaron we are facing the same issue here and changed to macos-13-arm64 which seems to work fine. So, maybe you could try that, if that image works for your needs, until they resolve the issue.

These don't seem to be available in Azure DevOps pipelines

@Cheesebaron that's weird. I have successfully run Azure Pipelines with that image. I even tried to run it now in case something changed.

Maybe your organization has access to a preview of some sorts?

@Cheesebaron hmm maybe, unfortunately I can't know it for sure.

Please note that the only supported images on Azure DevOps are the following: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software

Anything else is strongly discouraged as it can stop working for you without prior notice.

Please note that the only supported images on Azure DevOps are the following: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software
When it comes to MacOS 13 the only vm image available for Azure DevOps is macOS-13 (in beta).

yeah, it's quite confusing that arm64 is not listed anywhere, but presented in the repository xD
https://github.com/actions/runner-images/blob/main/images/macos/macos-13-arm64-Readme.md
but, seems like this image doesn't have the issue. i've switched our flutter project, it's building faster and without delays. xamarin net7 projects, from time to time, are having some strange freezes during the dotnet build step, we are currently investigating this as for now.

https://github.com/actions/runner-images/issues/8971

Anything else is strongly discouraged and it may stop working for you without prior notice.

macos-13 stops working without prior notice (hence the ticket).
Is there anyone looking into this or can tell us if its an issue thats being worked on, 'macos-13 is beta' is not really an excuse that can last much longer...

Our release pipeline stopped working today due to macOS-13 providers not responding. This is blocking our planned .NET MAUI app release next week.

This is painful:

Same issue.....

I've provided the feedback to the product team when I was at MVP Summit, they are aware of these issues.

We are affected by the same problem. I hope it will be solved soon.

Chiming in to say that this issue also affects us.

I'll also chime in and say that we are required to use macos-13 to build for iOS, due to the warning Apple is giving out in their review process that we need to be building for iOS SDK 17 by April 29 (shown below). This is because MacOS 12 uses XCode 14.2 by default, whereas MacOS 13 uses Xcode 15 which is the version we need. Sometimes I can get this VM pool to pick up right away, but most times it just hangs for a long time.
ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution.


HTML5 Validator fails with Anchors

When I validate my page at https://validator.w3.org/nu/ using Anchors I get this message:
"The name attribute is obsolete. Consider putting an id attribute on the nearest container instead"
Any fix?

Looks like we need to change the format from:

Foo Title

to

Foo Title


Emulator display layout awkward on Firefox 81.0 (64-bit) on Ubuntu 20.04

The issue is best described by this screenshot:

Depending on screen size, the blue bar at the bottom obscures either the H'L' register (in Z80 mode) or the Single Step button. This makes the emulator very hard to use. Is there some way I can adjust the left-hand column to add more space, or perhaps use a different (smaller) font?

I believe it is fixed now, please check and re-open, if needed.

Much better! Thanks for your quick fix.


Update release-notes-rs4.md

Fixed some text issues and naming. Still need to final build number and links updated. Added bullets for new WMR features.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/release-notes-rs4.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


ARM -> thumb calls are not showing up in callee list.

Version and Platform (required):
3.6
Bug Description:
Callee list of ARM functions do not show thumb callees.
Steps To Reproduce:
Open the attached binary: test.zip
Select function _start and execute this in the python console:
>>> current_function.callees
[<func: armv7@0x809c>]

This works because _start and the function at 0x809c (_funcA) are both ARM.
Now navigate to _funcA and execute:
>>> current_function.callees
[]

Empty! This doesn't work and I think it's because this is an ARM function (_funcA) calling a thumb function (_funcB).
Expected Behavior:
The callees of _funcA should not be empty. It should contain _funcB.

Fixed in builds >= 3.6.4585-dev


Quick links and help both are lands to a same page

Describe the bug
A clear and concise description of what the bug is.
In the quick links and help there are some links which are always lands to a same page, I will add pages according to related link
To Reproduce
Steps to reproduce the behavior:

Go to 'Website'
Scroll down 'till the quick link and help means till the end of the page.'
See error

Expected behavior
These links have to land related page or related content.
Screenshots

Desktop (please complete the following information):

Browser [e.g. chrome, safari]

Please assign this issue to me


Adds a notice that the service.wakeonlan module was moved

Motivation for this change
Forgot/didn't know I should've done this
As suggested by https://github.com/NixOS/nixpkgs/pull/140779#issuecomment-939306503
Works for me:
error:
       Failed assertions:
       - The option definition `services.wakeonlan' in `/nix/store/hmgr1sr6qrj98wwgnzl8hcklb9z7d1ak-source/hosts/pain/configuration.nix' no longer has any effect; please remove it.
       This module was removed in favor of enabling it with networking.interfaces.<name>.wakeOnLan

@rnhmjoj please merge this as soon as possible 😄
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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.

What's the alternative to wakeonlan today on nixos?

This here should work: https://search.nixos.org/options?channel=unstable&show=networking.interfaces.<name>.wakeOnLan.enable&from=0&size=50&sort=relevance&type=packages&query=interfaces+wakeonlan


KAFKA-8507 kip 499 Unify connection name flag for command line tool

This is a change updates ConsoleProducer, ConsumerPerformance, VerifiableProducer, and VerifiableConsumer classes to add and prefer the --bootstrap-server flag for defining the connection point of the Kafka cluster.
Committer Checklist (excluded from commit message)

[x ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

One more thing. I grepped docs/ for uses of these old args and found a few hits. Can we update the docs as well?

vagrant/README.md mentions

bin/kafka-console-producer.sh --broker-list broker1:9092,broker2:9092,broker3:9092 --topic sandbox

Multiple system tests leveraging the commands mention broker-list. Should we change those?

There are more tools to update from --broker-list to --bootstrap-server. Did we miss them in the KIP and if so, is it worth adding them in? (kafka-reassign-partitions.sh, GetOffsetShell, ReplicaVerificationTool, TransactionalMessageCopier, VerifiableLog4jAppender)

ok to test

retest this please

https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/4697/

We will follow up in a separate PR with @stanislavkozlovski 's suggestions.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/791 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit ca7328b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-03-15-05-06-10 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


section left hide issue of  tabs.js

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #216
Test URLs:

Before: https://main--icicidirect--aemsites.hlx.live/sidekick/blocks/tabs
After: https://tab-section-fix--icicidirect--aemsites.hlx.live/sidekick/blocks/tabs

@ravverma can you please attach a screenshot of the UI issue

before

after

@ravverma can you please attach a screenshot of the UI issue

attached

@anagarwa
As discussed it is a general practice to use loadBlock method, So we are good here and it is not adding any blocking time.
Please approve


How can I recover a corrupted encrypted db file

Normally we can recover a corrupted database file by using
sqlite3 crrupted.d .recover | sqlite3 fixed.db
But how to recover a database if it is encrypted ？

This issue should be redirected to SQLite3MultipleCiphers. Please leave a comment in this thread with that issue tagged. Closing for now.


Rename FeedItemViewModelTest -> FeedViewModelTest

Kind (Required)

Improvement

Overview (Required)

The title says everything 😄

Links

Thanks! Assigned 👍


Update Documentation

lgtm @Neotastisch , your changes should be aired after 30m, feel free to push the fix if needed and lmk


feature(dingus) nicer tabs, now displays TemplateMark AST

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 91.564% when pulling d6f624d8c63e1117783aaf60a52a9860b46b94b2 on jeromesimeon:js-dingus-better into 7c345b6c7b44d5321190d4fe8cb61c1fc530bf67 on accordproject:master.


Instant crash in iOS simulator iPhone 12 - please help

First of all thanks for this!
So I'm just trying to either:

Use better_player - as I was already doing - then show the airplay cast widget.

OR

Use your native player widget in place of better_player - which has the airplay icon built-in.

e.g.
  Widget _buildvideoPlayer(Video video) {
    if (Platform.isIOS) {
      return FlutterAVPlayerView(
        urlString: widget.video.videoM3u8,
      );
    }

    // Otherwise on Android - load different player.

    return AspectRatio(
      aspectRatio: 16 / 9,
      child: BetterPlayer(
        controller: _betterVideoController!,
      ),
    );
  }
}

Both instantly crash the simulator.
Can you provide at least a minimum code example in-context of how to use your two widgets please?
Thank you.

@daveshirman Thank you for reporting this. I had a very busy week so couldn't check this.
Let me try your code snippet and get back to you.

No problem at all. I am happy to donate to your funding if it helps you
spend some time improving the docs/bugs as this is an excellent feature if
working.
Thank you.
On Mon, 26 Jul 2021, 01:38 Junaid Rehmat, @.***> wrote:

@daveshirman https://github.com/daveshirman Thank you for reporting
this. I had a very busy week so couldn't check this.
Let me try your code snippet and get back to you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MrJai/flutter_to_airplay/issues/16#issuecomment-886391804,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADM6KXS6ZO7KTBSWBDHAIM3TZTYD3ANCNFSM5ATX4UFA
.

@daveshirman I am working on this issue today. But I am unable to reproduce the crash you mentioned. Can you please share some code snippets that will cause the crash?
Also, I noticed that you are asking, for example, I have added the example in the project, and one case is added by default where the video is being loaded from a URL, whereas the other case is commented out where a video can be loaded from assets.
https://github.com/MrJai/flutter_to_airplay/blob/46904f383ff464e04b21f1ddd255129ce3822a95/example/lib/main.dart
Please let me know if you want me to cover more cases in the example project. Please feel free to share if you want some more features in this plugin as well.

Thank you so much for your reply.
I really didn't do anything but set it up as per your original example,
perhaps I missed something, like an important step in the setup on iOS
Xcode project?
I will try to run the plugin again today and reply to you hear.
Thank you and please tell me where I can donate to keep you funded! Put a
button on your GitHub if you haven't already. You deserve it.
On Thu, 5 Aug 2021, 07:55 Junaid Rehmat, @.***> wrote:

@daveshirman https://github.com/daveshirman I am working on this issue
today. But I am unable to reproduce the crash you mentioned. Can you please
share some code snippets that will cause the crash?
Also, I noticed that you are asking, for example, I have added the example
in the project, and one case is added by default where the video is being
loaded from a URL, whereas the other case is commented out where a video
can be loaded from assets.
https://github.com/MrJai/flutter_to_airplay/blob/46904f383ff464e04b21f1ddd255129ce3822a95/example/lib/main.dart
Please let me know if you want me to cover more cases in the example
project. Please feel free to share if you want some more features in this
plugin as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MrJai/flutter_to_airplay/issues/16#issuecomment-893398453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADM6KXVQ2VJP65OHKRTQFM3T3J33TANCNFSM5ATX4UFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Thank you @daveshirman, I have just added some more examples on the basis of the frequently asked uses cases.
For donations, you can buy me as many coffees as you want, because being a developer I convert caffeine to code :P

I am no longer seeing this instant crash,  I can't tell you what is different, but I can successfully launch theAirPlayRoutePickerView now.
Question I guess (having not used this before), is can I use that to mirror the app in general, whilst using my own video player, or do I have to use that widget in conjunction with the FlutterAVPlayerView in order to mirror video content within my app?
Thank you so much, donation coming your way as soon as I've got this release build done!

yes you can use it with any player.

Thanks, so if using just the AirPlayRoutePickerView , does it mirror the whole app?
Also - did you see my error I pasted above? Looks like a simple layout problem is my guess?

Yes, that is intentional behaviour, because I am just providing a control, users can customise its appearance as per their app's UI. I will document it in the next version.

Thank you @daveshirman for coffees.
I think we can close this issue now? You can always open new issue, or reach out to me via twitter at @Rana_Jai.

You're welcome. I think as long as the documentation explains that if you
don't supply a wrapping widget with dimensions, it will crash, then yeah.
Cheers.
On Fri, 6 Aug 2021, 21:05 Junaid Rehmat, @.***> wrote:

Closed #16 https://github.com/MrJai/flutter_to_airplay/issues/16.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MrJai/flutter_to_airplay/issues/16#event-5125242439,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADM6KXUQKBJHBL7AEKJFZGTT3SBGVANCNFSM5ATX4UFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Hi Dave, I just updated the package and its changelog as well. Now the widget comes wrapped around in a 44 x 44 container, but its width and height are customizable, and users can change it as per their need/design requirements. It is also documented both in Changelog and in widget documentation.


Inconsistent Instructions

The user is being instructed to share their seed and then to not share their seed

Thanks for sharing @gamabuntan


[core] actually start the internal life cycles and test it

This fixes a startup regression introduced in 5094210.
The issue was caused by the internal started future never being resolved, which prevents the initial cluster refresh from being called as is done here:
https://github.com/spotify/heroic/blob/master/heroic-core/src/main/java/com/spotify/heroic/cluster/CoreClusterManager.java#L306

Current coverage is 43.06% (diff: 100%)

Merging #101 into master will increase coverage by 0.21%

@@             master       #101   diff @@
==========================================
  Files           596        596
  Lines         15343      15346     +3
  Methods           0          0
  Messages          0          0
  Branches       1578       1578
==========================================
+ Hits           6573       6608    +35
+ Misses         8311       8279    -32
  Partials        459        459

Powered by Codecov. Last update 0ffc22a...daecbc1

Looks good to me. I can confirm that I can now start and query Heroic again without crashes.


Can't see preview of snippet

I remember recently (a few days ago) being able to see a preview of the snippet suggested, but now it's seems to be gone, is this a problem with the extension or with VScode?

@Dannymx I will look into, but 99% new VSCode version.

I found how to view the preview.


takeoff_and_landing example build error

Hi, I saw that there was a previous issue and discussion going over an error building the takeoff_and_landing example. I went through that discussion a few times and I'm still a little confused. (Apologies I'm completely new to PX4 and MAVSDK development). I cloned the most recent version of the repo and got everything setup properly, but I had the same issues when trying to run the takeoff and land example.
I was able to get it to build and work in simulation when I switched to the older v1.4.3 branch. But I was just wondering if there was something I should do so that I can run the examples with the newest code?
It was mentioned that there is a CI system that should keep everything up to date, and I'm wondering if that is something I need to run manually to update the example files? (Apologies - I'm not familiar with how a CI system works). Just wanted to make sure I had everything up to date before I start practicing with my own examples.
To put it more concisely: Is there a way to update the example file so that it will build with the newest main code? Or did I misunderstand the discussion regarding the previous issue?
Thanks!

If you install MAVSDK from a package, you should use the examples that correspond to its version. Say you install MAVSDK 1.4.7, you should run the examples from tag v1.4.7 (and not from main).
If you compile MAVSDK from source, you should run the corresponding examples. Say you compile MAVSDK from main, you should use the examples on main.
If you try to use the examples in main with an older version (e.g. v0.13), then it may fail because MAVSDK has evolved since then.
Does that make sense?

Thanks so much for the reply! I compiled from source (am using the latest version) and used the examples on main, but those examples seemed to still have the outdated api calls? I may still be missing something...my apologies!

That should not happen, I think, because the CI does that :thinking:. But without more details on exactly what you did and what compilation errors you have, it's difficult to help more

I was following the instructions on this quickstart guide: https://mavsdk.mavlink.io/main/en/cpp/quickstart.html. I just cloned the latest version of the repository and get all the PX4 sim stuff setup separately then I cd into the examples directory and run:
cd takeoff_and_land/
cmake -Bbuild -H.
cmake --build build -j4
The first cmake call runs properly, but the second one results in the following errors:
error: no type named 'NewSystemHandle' in 'mavsdk::Mavsdk'
Mavsdk::NewSystemHandle handle = mavsdk.subscribe_on_new_system(&mavsdk, &prom, &handle {
^
error: no member named 'unsubscribe_on_new_system' in 'mavsdk::Mavsdk'; did you mean 'subscribe_on_new_system'?
mavsdk.unsubscribe_on_new_system(handle);
^~~~~~~~~~~~~~~~~
subscribe_on_new_system
/usr/local/include/mavsdk/mavsdk.h:301:10: note: 'subscribe_on_new_system' declared here
void subscribe_on_new_system(const NewSystemCallback& callback);
^
I was able to get everything running by switching to an old branch and then re running the cmake lines, and then running:
build/takeoff_and_land udp://:14540
But, I figured if I was having to switch to an old branch to get something working, then I was doing something wrong.

But, I figured if I was having to switch to an old branch to get something working, then I was doing something wrong.

You are not. You should use the examples that correspond with the version of MAVSDK you installed, that's expected :+1:

The thing was that I installed the latest version (not the 1.4.3 version that I had to switch to to get it to work), that's why I wasn't sure.


Bug in cart

Describe the bug
Bug in cart:
when you add 1 or more products to cart, and then click on cart -> the hamburger menu not disappear
To Reproduce
Steps to reproduce the behavior:

Go to '/shop'
Click on a product and add to cart
Open cart
See error
4a. The hamburger menu is visible
4b.  When open cart, add class to hamburgermenu and its disappear


doctoc: init at 2.2.0

Description of changes

DocToc generates a table of contents for a Markdown file. Functioning test included.
Not to be confused with the healthcare software.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[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

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

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

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

1 package built:

doctoc


Missing support for time intervals

I'm working on my calendar-cli.
A calendar event typically spans a time interval, and ISO 8601 does specify three standard ways of writing a time interval (according to wikipedia.  I've sort of invented my own way of writing time intervals, but I thought it would be a good idea to support the standard as well.  Actually doing the parsing of ISO time intervals is however out of the scope of calendar-cli, and I was expecting someone else had already written the code for it.  Using a popular search engine, I found the isodate library  - but apparently, it does not support parsing time intervals.
Is it on the roadmap?  Eventually, if I would do the work myself, would someone assist me with design review, code review and merging?  (I can't give any commitments on time frame for this one, right now I have lots of available time by the computer, but it may be years until next time).

Note that rdflib is using parse_datetime which trips up when passed a string such as this:

2023-10-01T22:15:00+00:00/2023-10-01T22:18:00+00:0

Here's a test case using rdflib in one case and then isodate:
FROM python

RUN python -m pip install rdflib

RUN echo '<> <http://purl.org/dc/terms/date> "2023-10-01T22:15:00+00:00/2023-10-01T22:18:00+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> .' > data.ttl

RUN cat data.ttl

RUN echo "Show rdflib using isodate..."

RUN python -c "from rdflib import Graph; g=Graph(); g.parse('data.ttl'); print(g.serialize())"

RUN echo "Now use isodate directly..."

RUN python -c "from isodate import parse_datetime; print(parse_datetime('2023-10-01T22:15:00+00:00/2023-10-01T22:18:00+00:00'))"

$ python build .
STEP 1/8: FROM python
STEP 2/8: RUN python -m pip install rdflib
Collecting rdflib
  Downloading rdflib-7.0.0-py3-none-any.whl (531 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 531.9/531.9 kB 1.3 MB/s eta 0:00:00
Collecting isodate<0.7.0,>=0.6.0
  Downloading isodate-0.6.1-py2.py3-none-any.whl (41 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 41.7/41.7 kB 2.4 MB/s eta 0:00:00
Collecting pyparsing<4,>=2.1.0
  Downloading pyparsing-3.1.1-py3-none-any.whl (103 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 103.1/103.1 kB 2.7 MB/s eta 0:00:00
Collecting six
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: six, pyparsing, isodate, rdflib
Successfully installed isodate-0.6.1 pyparsing-3.1.1 rdflib-7.0.0 six-1.16.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

[notice] A new release of pip available: 22.3.1 -> 23.2.1
[notice] To update, run: pip install --upgrade pip
--> 80d4443ecc73
STEP 3/8: RUN echo '<> <http://purl.org/dc/terms/date> "2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> .' > data.ttl
--> 8b4af12c7fe9
STEP 4/8: RUN cat data.ttl
<> <http://purl.org/dc/terms/date> "2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
--> 801a2c21a7c7
STEP 5/8: RUN echo "Show rdflib using isodate..."
Show rdflib using isodate...
--> e52c88d1667d
STEP 6/8: RUN python -c "from rdflib import Graph; g=Graph(); g.parse('data.ttl'); print(g.serialize())"
Failed to convert Literal lexical form to value. Datatype=http://www.w3.org/2001/XMLSchema#dateTime, Converter=<function parse_datetime at 0x7fd90b497420>
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/isodate/isodatetime.py", line 51, in parse_datetime
    datestring, timestring = datetimestring.split('T')
    ^^^^^^^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 2)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/rdflib/term.py", line 2119, in _castLexicalToPython
    return conv_func(lexical)  # type: ignore[arg-type]
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/isodate/isodatetime.py", line 53, in parse_datetime
    raise ISO8601Error("ISO 8601 time designator 'T' missing. Unable to"
isodate.isoerror.ISO8601Error: ISO 8601 time designator 'T' missing. Unable to parse datetime string '2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00'
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<file:///data.ttl> dcterms:date "2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00"^^xsd:dateTime .

--> 1fbdde804601
STEP 7/8: RUN echo "Now use isodate directly..."
Now use isodate directly...
--> 8f697d0e96de
STEP 8/8: RUN python -c "from isodate import parse_datetime; print(parse_datetime('2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00'))"
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/isodate/isodatetime.py", line 51, in parse_datetime
    datestring, timestring = datetimestring.split('T')
    ^^^^^^^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 2)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/local/lib/python3.11/site-packages/isodate/isodatetime.py", line 53, in parse_datetime
    raise ISO8601Error("ISO 8601 time designator 'T' missing. Unable to"
isodate.isoerror.ISO8601Error: ISO 8601 time designator 'T' missing. Unable to parse datetime string '2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00'
Error: building at STEP "RUN python -c "from isodate import parse_datetime; print(parse_datetime('2023-09-04T02:00:00+00:00/2023-09-04T02:30:00+00:00'))"": while running runtime: exit status 1


Special keywords for npm

Drivers/components are an important part of the Cycle.js ecosystem. Yet finding community libs isn't particularly easy at the moment.
One thing that lots of tools use is to promote usage of a particular npm keyword for their packages. This can help developers find those tools, or power search pages on the project's site itself.
I think a similar system could work well for Cycle.js drivers and components.
Prior art:

Grunt plugins
Gulp plugins
Yeoman generators
Ember Addons

If y'all think this is a good idea, I think the next steps could be:

decide on a keyword (cyclejs-driver/cyclejs-component, for instance)
promote it on the website in the proper section
either link to an npm search, or build your own search on the site

Cycle.js seems cool – I'd like to see the community around it grow, and this could help with that.

Also, without a special keyword, it can be tedious for community members to build discoverability around their modules. It requires adding a whole bunch of permutations, which seems silly and isn't as useful as having one "official" keyword.

More prior art: https://cordova.apache.org/plugins/ (powered by npmsearch)

All drivers aren't listed there, but awesome-cycle is a good start to find cycle related stuff (including drivers).

Because cycle is not good for search engines, let's use cyclejs (like the GitHub org) and Cycle.js in other texts, like in conference talks, etc. Drivers and libraries could be named just cycle-foo, as they already have been.

@staltz sounds good. So – just to clarify – you don't think it's valuable to use npm keywords as a means to power a search page on a site? My recommendation was only referring to npm keywords and the value that they bring, not names of libraries or conference talks, etc.

Unfortunately Cycle packages at @cycle/foo can't even be searched on npmjs.com because NPM still hasn't built search feature for scoped packages.


small rounding error in ETH calculation of the extraBalance

Hi Bokkypoobah
I've confronted my final script https://github.com/lyricalpolymath/Ethereum_DaoExtraBalanceOwners
with yours and found that we have almost everything right but there is a small problem in your ETH balances.
We have the same number of addresses (11.440), the same number of transaction (22.608)
but a tiny difference in ETH value (86360144 WEI or  0.000000000086360144 ETH)

BB (my) tot ETH    - bbtotals:<PHONE_NUMBER>2346864402677
BP (your) tot ETH - bptotals:<PHONE_NUMBER>23468557666626
difference BB-BP  in WEI: 86360144
difference BB-BP  in ETH: 0.000000000086360144 ETH

I've created a comparison file here / and the script that generated it
the problem lies in line 86  of your code
where you do:
var theDAOAmount = amount - extraBalanceAmount
the difference should rather be done with BigNumber
var theDAOAmount = amount.minus(extraBalanceAmount)
because otherwise it truncates the last digits of the number
tiny detail :)

Thanks @lyricalpolymath . I later worked out how to fix my rounding issues using BigNumber and .plus(...) and will use .minus(...) in any of my new calculations. I won't change the figures in the results here just yet as the numbers are close enough (9 decimal places is OK for me). I'll update my front page to state that the results are to 9 decimal places until (if) I revise the figures.

And thanks for confirming the data in http://ethereum.stackexchange.com/a/8342/1268 .

thank you in the first place :) for showing us how to do it. 👍

Hi @lyricalpolymath , I've just uploaded v4 with the rounding errors fixed by using BigNumber maths. See the top of the front page. However my number are slightly different to yours:
BB (my) tot ETH - bbtotals:<PHONE_NUMBER>2346864402677
BP (your) tot ETH - bptotals:<PHONE_NUMBER>23468557666626
difference BB-BP in WEI: 86360144
difference BB-BP in ETH: 0.000000000086360144 ETH
v4<PHONE_NUMBER>23468644033437


disable tweak for app, the app icon moves from inside the file to outside the folder

Device Model
iPhone 12PM A14
iOS Version
16.6.1
Bootstrap Version
1.2.1
Serotonin Version
1.2.1
What happened
When I disable tweak for app, the app icon moves from inside the file to outside the folder
Log output
No response
Acknowledgement of README and FAQ

[X] I have read both the README and the FAQ.

known issue, not a real problem

Not going to be fixed, as this is just a side effect of how injection works.


Temperature UX

Temperatures look fugly on meeting room SVG blocks. Unsure if I can resolve how to display them on the smallest-sized rooms without overcrowding. For now, I'll leave temperatures displayed in the room tooltips.

Alternatively, create a temperature heat map mode that replaced room statuses with temperature-based colors. Only display temperature values on the room modal.


Test driver fixes for error handling

This change follows #1302.
After #1302, I found that any errors in #write of output plugins are not raised in test case code like below:
assert_raise AnyErrors do
  d.run
    d.feed(events)
  end # events flushed and #write called - "AnyErrors" raised
end

Errors are shown on console, but we can't test it.
This change is to check all threads via thread plugin helper, and re-raise errors from these threads at the end of #run method. It shows all errors in all threads related with plugins explicitly as test results - so there's no need to show these errors on console.
Some changes are also included:

add an option to retry for flush errors even in plugin development: to emulate write operations 2 or more times over failures
use Process.clock_gettime instead of Time to work well even when timecop is used
raise TestTimedOut error for hard timeout to show problematic test cases clearly
change to wait post conditions after #run_actual, because output plugin test driver flushes and wait for completion of flushing in #run_actual

@repeatedly could you review this change?
This is required for both of migrations of exec plugins and forward plugin.

@repeatedly ping?

LGTM


Exposed EAN options on ISBN13 constructor

As written in the title, this PR is to expose the no_checksum and guardbar parameters also for the ISBN13 constructor

Thanks!


how to add a button in a dialog

When iam adding a button in dialog using xyzdialog.ts file. Then the button is getting displayed on the top of the grid aswell.
How to restrict the button displaying on the grid?? instead i need to display button on the dialog only

@flextrio-gandhi ,
that's strange. when I am adding buttons in my xyzDialogs, then they appear only on that specific dialog where I do the override of the getButtons method.
can you share your full xyzDialog code where this problem occur?
With kind regards,
John

was using  below functin in dialog.ts, Is that fine or should override any other function??
protected getToolbarButtons(): Serenity.ToolButton[] {
let newBtn: Serenity.ToolButton =
{
//button creation logic goes here
}
buttons.push(newBtn);
return buttons;
}

Which version of serenity do you use?

Hi @flextrio-gandhi ,
in my xyzDialog.ts, I override the same function but do it like this:
       protected getToolbarButtons() {
            var buttons = super.getToolbarButtons();

            // *** Create Dropdown-Button ***
            buttons.push(
                {
                    title: Q.text("Dialogs.Documents.Button.Stampante"),	// *** Get button text from translation
                    cssClass: 'stampe',
                    icon: 'fa-print',
                    onClick: () => {

                        // *** do something on click if you want **

                    },
                }
            );

            return buttons;
        }

The only real difference between your and my code I see in your override declaration. But I have to admit that I am no real developer - just an admin with some DEV ambitions. So I cannot tell if your way of overriding getToolbarButtons is correct or not.
But I know this: I add buttons all the time to many differnet dialogs and they never appear on any grid - only in the dialog where I have added (pushed) them to the existing buttons.
I normally do "var buttons = super.getToolbarButtons();" and then splice (remove) standard buttons if I don't need them in a specific dialog - and after that add my own. But I surely also have had the case where I didn't use the "super..." and just pushed my buttons and this also has worked as expected.
What version of SF is your project based - and core or "real" .net? (I still only use "real" .net as SF on core according to the issues here in the forum seems to have still some issues which the .net version does not have)
Hope this helps.
With kind regards,
John


SAK-46600 Conversations: Fixed aria for comment menu

https://sakaiproject.atlassian.net/browse/SAK-46600

C'mon ... more importants?????
If you want this kind of behaviour, Bootstrap 3.3.7 provides you btn btn-link and it will work all over Sakai
@ottenhoff, @adrianfish this shouldn't be merged with !important, please no. There are ways to do it always better than  important.
Even if you want a new class, you can use unset. Whatever before !important and without reviews.

It was reviewed. Sam didn't like the anchor I started with, understandably, so I swapped it for a button. I didn't want to mess with our button styles so I used important. Just pragmatism. Please open another Jira to add a new transparent button class - I was going to do that, but you may as well. You seem to know more about it than me anyway. I am aware of the problems with important, just so you know.

Well ... Pragmatism is not a good answer for good software but whatever, we will keep fixing bugs here and there, sure.

Just open another jira about a transparent button, put some comments on and assign to Shawn.
Leaving aside your incredibly bad manners @SedueRey, I'll try and explain my ethos on this ticket:

This was effectively a blocker for screen reader users.
Our button css is complex and I didn't want to produce any more bugs by messing with it. I figured the use of a button (semantic), the fixing of a bad a11y bug and the avoidance of disturbing the existing button styles justified the use of an !important in this case. I did intend to open a jira for Shawn or Mike to look at, but I'm not as disciplined as you so I forgot. Please accept my apologies in that regard.

You keep fixing those bugs :)

Well, I'm going to leave it here but typing it in an online translator to be sure I don't think I'm saying what I'm not saying. I encourage you to try to write in a language that is not yours and make yourself understood to be considered rude.
The facts are:

While we were fixing the !important and fixed colors in another of the PRs, which were affecting all of Sakai by not having the namespace, you have added this PR, it has been validated and merged. The rest of us usually have this debate in core calls.

That there is a blocker is not an excuse to put bad code, !important is bad code no matter when you look at it. Screen reader or mobile or whatever another platform.

With all due respect, @adrianfish , you are not a newbie to Sakai. You have been around as long or longer than me, you are a member of the PMC, which I am not and you should know the libraries we have, in what state and that we try to improve the code every time something new is added. I repeat: you do NOT need to add a new class. You should know that.

After this, I stand by it, pragmatism or haste is no excuse for bad code. If you want, we debate it in the core call, I have no problem about it.
This PR should not have been mixed and validated by @ottenhoff . Period.
Thanks. That said, I encourage you to discuss it on the next core call.

I understand that you're writing in a second language and I respect this deeply, but I also recognise sarcasm when I see it.
"we will keep fixing bugs here and there, sure." is just sarcastic and there's no need. It was reviewed, I made amendments and made a value judgment.
If you open a JIRA ticket and detail your concerns and a way to address them, I'll put the fix in.

No, @adrianfish, that's was not sarcastic. When I wrote that I wanted to mean, really,  that we will keep fixing all bugs that we find, we're not going to step back. We are part of this community and want to install 22 this july so, literally, we will keep fixing bugs where we would find them, if you prefer it in that way.
That was not a sarcasm.

In that case I apologise Eduardo. That reads really sarcastically in english but perhaps I should have been more understanding. Maybe you can tell me in spanish next time (seriously). I can read spanish reasonably well. That may have been clearer to me :)
Anyway, can you open a JIRA and assign to me? I'll see what I can do with it. Any any suggestions on that JIRA will be welcome.


No boundaries when opening existing Maxwell model

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
Hello Team,
  When existing Maxwell model with winding and motion, I find they are not in boundaries yet. Please see below.
  We must run pyaedt commands to assign them, and then I could find them in the boundaries list.

  When I open existing model with winding and motion, I could not find any boundaries automatically in 2023R1.

Py1.zip
Steps To Reproduce
Please check the attach files.
1). Just run py to open or load existing Maxwell model.
2). Evaluate M2D.boundaries, and couldn't find any boundary.
Thanks.
Which Operating System are you using?

There was actually an issue in the rename method, it will be fixed in a new PR and be available in the next release.
Giulia

Thanks a lot.


run detekt for all defined profiles and allow different names

I was looking at detekt-gradle-plugin a bit and realized two weird things.

When I named my profile anything other than "main" it seemed not to work correctly.

This seems to have been caused by the var profile in DetektExtension that was initialized to "main" but would never be overwritten with the actual profile name. So detekt would run the _fallback_ profile which only runs the defaults but considers none of the profiles configuration options.

When defining multiple profiles only one would be run by detekt.

While we collect all profiles defined in the detekt { ... } closure of the build.gradle file in a profiles variable we never did anything with them. By adding a getter and looping through all profiles for the DetektCheckTask, DetektCreateBaselineTask and DetektMigrateTask all profiles should now be executed.

Yep that behaviour was as planned :).
If no profile is declared or selected with profile = xxx, the _fallback_ profile is used. The default profile is aimed to be the main profile if declared. If you have many profiles declared, you can pick any by specifying inside the profile = xxx variable or giving the -Ddetekt.profile=xxx- property to gradle.
If you have a profile test declared, which does not override all detekt extensions, the not overridden properties get inherited from the main profile :)
Kinda difficult to know and not documented at all (?!) :D
Running all profiles seems like a good idea, but I do not think all should be run everytime. Maybe an additional flag or task?

Huh, didn't know that was behaving as planned. Thanks for explaining the rationale behind how it should be used. But it feels a bit confusing to me.
I personally would not like editing my build.gradle files to change the profile = xxx values for every run of detekt. And somehow passing arguments to the gradle command is a nice option but also doesn't feel like something I'd like to do on every run.
If I set up a main and a test profile I'd personally expect them both to run. And if my main profile is called "default" it should still run that profile and not the _fallback_ profile (which would be incredibly hard to even realize in many cases).
I'd think that whenever I can enter a String in a gradle configuration I should be able to use whatever string I like. Forcing it to be "main" feels a bit weird.
Same goes for multiple profiles. If I explicitly define multiple profiles, why not run all of them? Maybe we could even define tasks for each profile.
Let's take detektCheck as an example if I define the above mentioned main and test profiles:

detektCheck would run both (all profiles that are defined)
detektCheckMain would run the main profile
detektCheckTest would run the test profile

We can move the discussion to a new Issue as well and close this PR for now.

Yes, please open an new issue and close this one. It would be good to discuss the usage of profiles. I introduced them when we had no option to exclude rules for test sources. My usecase for them was also to have separate config files for different project modules, eg. some rules are ok for gui code but not for library code.

I opened #540 to continue the discussion.


Some types incorrectly stored by builddb

The type of appUnsafe from System._Unsafe misses uniqueness attributes. May be due to an outdated clean compiler.

Let's defer this until the clean-compiler moves to git.

We moved to the latest clean-compiler, but it did not resolve this issue.


Support RTL

Hi This framework support RTL language for example persian arabic etc?

Since the move to flexbox, RTL support is pretty decent out of the box. However there are still some components that will need special treatment (normally involves adjusting margin/padding left/right), namely:

[ ] Blockquote
[ ] Breadcrumb
[ ] Button group
[ ] Close button
[ ] Custom checkboxes and radio buttons
[ ] Dropdown toggle
[ ] Modal/picker footer
[ ] Stepper
[ ] Table (first and last cell)

you can use my bootstrap-v4-rtl and its done every thing


SPOI-11043 Create JMSOutputOperator example application

@sanjaypujare, please review and merge as appropriate.

@oliverwnk this PR is dependent on the apex-malhar PR you have opened for the original fix in the JMS output operator. I am reviewing this and adding comments but merging cannot be done until the above mentioned PR is merged (I understand @PramodSSImmaneni  is reviewing it?)


Live Preview from command line

tldr; I would like to preview an html file from the command line but when I run command gp preview $(gp url 3000)/index.html, I get an error.
Details:
If I run command gp preview $(gp url 3000)/index.html after first starting the gitpod workspace, when the browser tab opens with https://3000-plum-galliform-dpkqmaaq.ws-us18.gitpod.io/cluster-linking-exercise.html in the address bar and the window contains the message Port 3000 Not Found Please make sure this port is exposed and your application is up and running.
If I then open the file in the editor and preview it using the Live Preview: Show Preview button, the file is displayed in the new preview window after a short delay until port 3000 is activated.
If I then return to the window that had the error, the file preview is now visible.
If I close the editor and preview windows and then run command gp preview $(gp url 3000)/index.html again, the file preview is shown. If I close the preview tab and wait, after a bit of delay port 3000 returns to an inactive state. At that point, running the command gives the same error that was previously mentioned.
Enhancement request:
Could this extension be updated so that it can be activated from the command line in the same manner as it is when the Live Preview: Show Preview button is pushed?

In terms of the GitPod integration, unfortunately, that's out of scope since this might be an issue with how GitPod works with VS Code or the extension. If you see the same issues on somewhere like codespaces (which is supported), please let me know.
The enhancement request is a duplicate of #368


Directories list in Subdomain Details page

Mockups

Specifications

The directories list will contain the following columns:

Directories: Directory path
Method: Ex: GET
Status code: Ex: 301
Size: Value in KB

The directories tab title will include the total amout of directories included in the list.
Every column of the list will contain arrows to sort the data ascending or descending
The list will have a paginator, if needed

@gorums Please, provide the list of possible values for Status code and Method columns.

How is going to be populated this list?

@YanetABUC  we got that data from the Agents.

There is a style issue to be fixed in #189


Relation name and join key fixes for :many_to_one

@solnic Thanks for all your hard work. I'm really enjoying using ROM. I've been using it to make a legacy database a little more consistent and I think I may have found a couple of bugs.
I would love it if you could confirm this is a bug or maybe I'm just not using ROM incorrectly?

Can't change many_to_one relation name.
many_to_one uses the wrong tables primary key name.

PS: I'll cleanup the test.

Hey James, this is a good change thank you for spotting this and fixing :) I'll wait for you to clean up the tests like you said and will merge it in and release new version.
BTW I stopped using those macros as I discovered I'm perfectly happy with the lower level join / outter_join interface. Renaming and qualifying columns is as easy as select(:id, :name).qualified.prefix(:bazinga) so I really no longer feel the need for those macros. Not saying they should be removed but I figured I should mention that :)

@solnic thanks for getting back to me so quick. I'll try the lower level method tomorrow.
I've cleaned up the test using the existing database shared example. Looks much better.

Thanks, I just released 0.5.3 with your fix included :tada:


Unable to upload blog icon that is 60x60 px, 4kb and in png format

Issue Summary
I attempted to upload a "publication icon" via the admin screen. It's 60x60 px and 4kb, in png format, so it should be okay. But I keep getting:

Blog icon must be a square .ico or .png file between 60px – 1,000px, under 100kb.

Looking at the console output, it attempted a POST to https://grantwinney.com/ghost/api/v0.1/uploads/icon/ but got a 422 in response.
Here's the output of the "...production.error.log" file:
{
	"name": "Log",
	"hostname": "ghost-blog",
	"pid": 1601,
	"level": 50,
	"req": {
		"meta": {
			"requestId": "09b25980-761a-11e7-bc6b-abd7697343ef",
			"userId": "1"
		},
		"url": "/uploads/icon/",
		"method": "POST",
		"originalUrl": "/ghost/api/v0.1/uploads/icon/",
		"params": {},
		"headers": {
			"x-forwarded-for": "<IP_ADDRESS>",
			"x-forwarded-proto": "https",
			"x-real-ip": "<IP_ADDRESS>",
			"host": "grantwinney.com",
			"connection": "close",
			"content-length": "2010",
			"origin": "https://grantwinney.com",
			"x-requested-with": "XMLHttpRequest",
			"content-type": "multipart/form-data; boundary=----WebKitFormBoundarywUybUygeIOrKGeXD",
			"accept": "text/plain, */*; q=0.01",
			"user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36",
			"x-ghost-version": "1.2",
			"dnt": "1",
			"referer": "https://grantwinney.com/ghost/",
			"accept-encoding": "gzip, deflate, br",
			"accept-language": "en-US,en;q=0.8"
		},
		"body": {},
		"query": {}
	},
	"res": {
		"_headers": {
			"x-powered-by": "Express",
			"cache-control": "no-cache, private, no-store, must-revalidate, max-stale=0, post-check=0, pre-check=0",
			"access-control-allow-origin": "https://grantwinney.com",
			"vary": "Origin, Accept-Encoding",
			"content-type": "application/json; charset=utf-8",
			"content-length": "140",
			"etag": "W/\"8c-OHQ99jnxlHCzO0uLwFlA5EWw1Ps\""
		},
		"statusCode": 422,
		"responseTime": "40ms"
	},
	"err": {
		"id": "09b825e0-761a-11e7-bc6b-abd7697343ef",
		"domain": "https://grantwinney.com",
		"code": null,
		"name": "ValidationError",
		"statusCode": 422,
		"level": "normal",
		"message": "Blog icon must be a square .ico or .png file between 60px – 1,000px, under 100kb.",
		"stack": "ValidationError: Blog icon must be a square .ico or .png file between 60px – 1,000px, under 100kb.\n    at new ValidationError (/var/www/ghost/versions/1.2.0/node_modules/ghost-ignition/lib/errors/index.js:115:23)\n    at /var/www/ghost/versions/1.2.0/core/server/middleware/validation/blog-icon.js:62:29\n    at tryCatcher (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/promise.js:512:31)\n    at Promise._settlePromise (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/promise.js:569:18)\n    at Promise._settlePromise0 (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/promise.js:614:10)\n    at Promise._settlePromises (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/promise.js:693:18)\n    at Async._drainQueue (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/async.js:133:16)\n    at Async._drainQueues (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/async.js:143:10)\n    at Immediate.Async.drainQueues (/var/www/ghost/versions/1.2.0/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:672:20)\n    at tryOnImmediate (timers.js:645:5)\n    at processImmediate [as _immediateCallback] (timers.js:617:5)"
	},
	"msg": "Blog icon must be a square .ico or .png file between 60px – 1,000px, under 100kb.",
	"time": "2017-07-31T17:59:46.243Z",
	"v": 0
}

I think I see the reason for the error - there's a possible issue with the validation in the "core/server/middleware/validation/blog-icon.js" file, where it checks that the minimum width is <= 60 even though it seems like the intention was to allow 60px.
I opened a pull request, in case I'm right about the fix.
Steps to Reproduce

Create a 60x60 px image, save in png format.
Attempt to upload image.

Technical details:

OS: Ubuntu 16.04.2 LTS
Node Version: v6.11.1
Ghost-CLI version: 1.0.0
Ghost Version (at /var/www/ghost): 1.2.0
Database: mysql Ver 14.14 Distrib 5.7.19, for Linux (x86_64) using EditLine wrapper
Browser: Chrome Version 59.0.3071.115 (Official Build) (64-bit)

Good catch @grantwinney!! I can confirm this behaviour.


connecting spyder to remote server via ssh

I'm having ubuntu 16.04 on my desktop and server.
Now I am trying to connect the spyder to my remote server.
details about the spyder on my desktop:
I have spyder 4.1.1 now and Python 3.6.6 64-bit | Qt 5.9.6 | PyQt5 5.9.2 | Linux 4.15.0-106-generic
I read the explanation on spyder website.
I think my lack of knowledge is the problem. I appreciate if someone can help me with the steps.
Here is what I did so far:
In my server machine in the terminal I did:
python -m spyder_kernels.console
and it shows:

based on the tutorial now I should do this:
Copy the connection file (jupyter/runtime/dir/path/kernel-pid.json) to the machine you’re running Spyder on (if remote) or note its location (if local).
I am not sure where should I find this file and where should I copy this?
I want to run spyder on my desktop while running the code in the server, so I am confused a little where should I run python -m spyder_kernels.console and where I should find it, and where I should copy/paste it?
In the tutorial, it says: You can get jupyter/runtime/dir/path by executing jupyter --runtime-dir in the same Python environment as the kernel. but I am not using jupyter so I am not sure how it is even related?
I appreciate any help in this regard.
I have not moved to the next steps since I got stuck at the beginning.

Hi @seyeeet.
On my Mac the path is /Users/<username>/Library/Jupyter/runtime
To get information on where they might be stored on the remote machine you can try running this command
(see: https://jupyter.readthedocs.io/en/latest/projects/jupyter-directories.html#:~:text=On Linux and other free,row of the table above).)
jupyter --paths

On my machine it returns something like:
config:
    /Users/<username>/.jupyter
    /Users/<username>/miniconda3/envs/spy36/etc/jupyter
    /usr/local/etc/jupyter
    /etc/jupyter
data:
    /Users/<username>/Library/Jupyter
    /Users/<username>/miniconda3/envs/spy36/share/jupyter
    /usr/local/share/jupyter
    /usr/share/jupyter
runtime:
    /Users/<username>/Library/Jupyter/runtime

Hope this loves the question.
Cheers

@goanpeca so spyder saves at the same path as jupyter?

@seyeeet, yes it does.

A Spyder Kernel is just a normal IPython/Jupyter Kernel with some added functionality to be able to communicate extra functionality with Spyder.

@goanpeca Thanks, I was able to connect to the server with your clarification!
But there is one more problem. in the spyder console it keeps repeating this even when I am not doing anything:

@seyeeet see this issue. https://github.com/spyder-ide/spyder/issues/10240

@goanpeca Thanks man! It seems like it is working well now, every 10 min it repeated again so there might be something deep there that you guys want to look into, but in general, it looks like it is working well.
This just added one more reason for me to LOVE spyder!
For newbies like me that might have a little problem doing it, here is what I did:

read this spyder tutorial on how to install the requirements and stuff.
I want to run spyder on my desktop and connect it to my server, and I am using ssh usually to do it. both my systems are ubuntu 16.04.
kill the other kernels on your server, not sure if it is a right way, but i did it with kill -l
on the server run jupyter --paths to know where the kernel will be saved, you need to copy the runtime path
on the server do: python -m spyder_kernels.console or if you already have the kernel created, do this: python -m spyder_kernels.console -f kernel-xxx.json apparently the second one works better.
go to the runtime path and copy the json file and paste it on your desktop
I also kill the kernels on my desktop (not sure if it is necessary)
open the spyder on your desktop and follow the steps as mentioned  here


Querying Salesforce DB from the Django Shell

Hi, I am new to this awesome project.
Trying to integrate to the Salesforce db/connected app. I want to do a simple ORM query of the Salesforce database.

I believe my auth worked because I get all the models when I run python3 manage.py inspectdb --database=salesforce.
I can open the Django shell and run from salesforce import SalesforceModel etc.

What do I need to import import? How do I do simple Users.objects.all() or Contact.objects.all() ?
Thanks for any example code

It’s exactly what you describe, there’s nothing different than using any other kind of Django model.

It’s exactly what you describe, there’s nothing different than using any other kind of Django model.

When I try to import the models, I get errors. I can't import the models listed in inspectdb. How can I import the models to ultimately read data from the Salesforce DB?
from salesforce.models import User
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name 'User' from 'salesforce.models'

You’ll need to create a models file and import from that. This is all pretty much basic Django stuff, so you may want to review the Django tutorial as well.

You’ll need to create a models file and import from that. This is all pretty much basic Django stuff, so you may want to review the Django tutorial as well.

Thanks for your time Phil.
I know I can run a command like this  python3 manage.py inspectdb --database=salesforce > models.py
But I already am integrating Salesforce into a deployed app with a PostgresDB.
So do I add the new models to my existing models.py file? Or create a new one and point to it somehow? Or how do I otherwise manage having both a Salesforce DB and a traditional DB?

That seems to vary quite widely. Some people create a whole app for their Salesforce models (this is where i’d suggest you start), others split them up by use case, it really depends. It’s pretty much a Django project planning question, IMO.

It is very similar to multiple databases in Django with normal database backends. A database router can select a database that will be used for reading and writing data. All people that I know use a recommended database router DATABASE_ROUTERS = ["salesforce.router.ModelRouter"] and usually only one salesforce database and its name is "salesforce".
The differences are:

All model that are descendants of salesforce.models.Model use the salesforce database by default.
All model that are descendants of only django.db.models.Model, but not salesforce.models.Model can use only non-salesforce databases, by default the "default" database.

You can not create foreign for cross references between different databases, but the keys can be saved eventually saved as normal fields.
That is reason why I would recommend to separate the models to two applications. One of them will have only models.py file and the models will be imported into views and forms of the main application.


Check for rails when determining whether ActionView instrumentation is compatible

Fixes https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/475
When using the OpenTelemetry::Instrumentation::ActionView instrumentation outside of a Rails app the instrumentation will fail with an error:
ERROR -- : OpenTelemetry error: Instrumentation: OpenTelemetry::Instrumentation::ActionView unhandled exception during install:
[{stack trace ...}] - uninitialized constant Rails

The instrumentation does not check for ::Rails when testing for compatibility
        present do
          defined?(::ActionView)
        end

but does require ::Rails::Railtie when installing the instrumentation
      # This Railtie sets up subscriptions to relevant ActionView notifications
      class Railtie < ::Rails::Railtie

I'm not sure how to instrument ActionView outside of RailTie, but at the least the instrumentation should fail it's compatibility check if ::Rails is not defined.

I'm working to fix the CLA issue ☝
This change does not include tests because it was not clear how I should approach testing this. If the maintainers have a suggested approach I would be happy to implement it.

@jmorrell check for use of hide_const for examples of how we test it.
https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-ruby-contrib hide_const&type=code


feat: create static selection component

@iambumblehead  also remember to enable auto deleting of branches after merge

The auto-delete setting is enabled now

approved :)


pull request for e2e test at 11/12/2016 20:45:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Consider chart mirrors capabilities

On behalf of @zcrisler
What would you like Loftsman to do?
react to the idea of chart mirrors in chart source locations
Why is this needed?
If we have airgapped installs, we may need to explore this

@zcrisler picking up this conversation here, referencing what you put in the PR that triggered this ticket:

I like this change a lot. It will make it very easy to locate charts in upstream repositories; however, I think it needs a "mirrors" feature similar to containerd's registry mirrors. This would enable manifests to reference a chart in it's upstream location as maintained by https://github.com/helm/chart-releaser-action (e.g., https://cray-hpe.github.io/nexus3) but provide installers the ability to resolve such requests to a local directory (i.e., to support airgap packaging). I think passing in a --mirrors configuration file to loftsman would be sufficient, although we could support a specifying individual mirrors on the command line too.

I want to talk through some examples here and see what in this is already addressed/possible, and we'll get to the meat of what improvements around this might be warranted. So, let's say you have a manifest like this:
apiVersion: manifests/v1beta1
metadata:
  name: master-online
spec:
  sources:
    charts:
    - type: repo
      name: nexus3
      location: https://cray-hpe.github.io/nexus3
    - type: repo
      name: victoria-metrics
      location: https://victoriametrics.github.io/helm-charts/
  charts:
  - name: nexus3
    source: nexus3
    namespace: default
    version: 1.1.0
  - name: victoria-metrics-cluster
    source: victoria-metrics
    namespace: default
    version: 0.8.24

And maybe that's my default, online manifest. Maybe I have tooling to generate an offline one alongside this one:
apiVersion: manifests/v1beta1
metadata:
  name: master-offline
spec:
  sources:
    charts:
    - type: directory
      name: nexus3
      location: /var/charts
    - type: directory
      name: victoria-metrics
      location: /var/charts
  charts:
  - name: nexus3
    source: nexus3
    namespace: default
    version: 1.1.0
  - name: victoria-metrics-cluster
    source: victoria-metrics
    namespace: default
    version: 0.8.24

The spec.sources.charts or configuration for sources is the only diff, just updated to point to a directory where packaged charts were pre-pulled or whatever.
One thing to mention here: I continue to believe that auto-generating, or assembling manifests with automated tooling is a good idea. Of course manifestgen has been used on that side to that end, but I even think that it's powerful to explore ideas like maintaining different manifests, or just sections of a manifest that can be merged together to create a master one. It's worth mentioning b/c the above means you can easily maintain multiple release manifests alongside each other as built artifacts. Think of automated pipelines being able to auto-maintain or increment chart versions for a manifest artifact when an updated chart passed integration tests, that sort of thing. Or even just a team managing the section of a manifest that they care about.
To the mirrors implementation, I'm not entirely sure the approach we'd want to take if it's needed, but taking our master-online manifest example above along with some of your initial ideas, maybe I'd run a ship something like:
loftsman ship --manifest-path ./manifest.yaml --mirrors ./mirrors.yaml

where mirrors.yaml might look something like:
mirrors:
- source: https://cray-hpe.github.io/nexus3
  mirror: file:///var/charts
- source: https://victoriametrics.github.io/helm-charts/
  mirror: file:///var/charts

A few points/concerns I have with this if I'm thinking about this right:

I'm not sure this is any easier than simply defining something similar in the actual manifest applied, the first example presented
I do have concerns about approaches Loftsman takes under the hood moving forward where we end up in situations where the applied manifest isn't representative of what and how things were installed. Ryan and I discussed this a bit on the last PR as I was exploring some routes to modifying the manifest on-the-fly. We need to remain as aimed as possible on the actual manifests provided to ship being representative of what happens.
I wonder if simply maintaining an http/https proxy in the environment executing the loftsman cli is also another recommended path to explore here for the need?

Let me know your thoughts and other design/implementation paths we might explore here.

@rockholla Thanks for giving this a good bit of thought. Looking at this again, I'm not sure my --mirrors suggestion really addresses the airgap use-case I had in mind.
I suppose I just like the option of not having to rewrite a manifest to update sources. What if loftsman ship had a--cache DIR option? For example, consider your first manifest example above. When using loftsman ship --cache ./charts --manifest-path ./manifest.yaml it would look in ./charts/cray-hpe.github.io/nexus3 for charts with source: nexus3 before searching https://cray-hpe.github.io/nexus3. (Perhaps there's also a --cache-only option to disable trying to search remote locations?) In addition, it might be useful to also provide a loftsman cache [-d DIR] MANIFEST... command that populates the cache directory given by -d or the current directory by default? This would enable us to easily cache charts for a given manifest to enable airgap packaging. I could also see it being useful for any bandwidth limited environment as well.
That said, I also like supporting local paths in the location for .spec.sources.charts items. Have you considered how manifests would support charts stored in OCI registries? I think the --cache option would be compatible with that; however, maybe using an HTTP proxy as you mentioned would be best? Although it'd be proxy specific, we'd probably need some tooling to help initialize the proxy's cache given manifests -- again to support airgap use-cases. So maybe loftsman cache still has a purpose? Of course, if you really prefer rewriting the sources in the manifest, I suppose we could call it loftsman freeze instead and have it output an updated manifest based on where it cached charts.

Hmm, yeah, the cache idea might be a general-enough use-case. I have historically thought in the context of Loftsman, that it is just a process downloading some charts by some other process, putting them in a local location and then having the manifest refer to them as opposed to having Loftsman care about it, but there's some merit in the idea of encapsulating some air-gapped capabilities into Loftsman to this end.
The question here is in part: what job of it of Loftsman to help assemble, template, or render a manifest? I'm not entirely sure yet. As we move into it as an operator some things might happen naturally here. I'd say until then we're definitely dealing with a tool that just expects a manifest as-is.
I'll file this under v2 considering, as that's when we should make the leap to operator.

worth noting too, I think airgapped use cases can still operation like online ones. E.g. a proxy or just straight up routing to a particular url can happen to a place within the network if your network running loftsman operations routes it as such. I've also thought about airgapped needs being solved most-appropriately in this way, Loftsman aside: my airgapped network routes requests to https://charts.my.org to some internal url  as opposed to the actual public one.
I believe in airgapped scenarios being solved in such ways generally, e.g. reacting to HTTP_PROXY, HTTPS_PROXY as opposed to a given tool have some special cases for dealing with such things.


Update K8S YAMLs for Gunicorn

Addresses #81
The image tag and the entrypoint command have been updated in the
WES deployment YAML.

Tested posting pipeline and works fine.


Jupyter Notebooks only allow searching the whole notebook instead of individual cell

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

VS Code Version: 1.64.0
OS Version: Mint 20.3

Steps to Reproduce:

Create a Notebook with multiple cells and content in those cells
Press ctrl-f and search for something that can be found in more than 1 cell
The search feature will only allow you to search the whole notebook and not the individual focused cell.

The desired behavior is that if I am searching in a given cell, I am only search that one cell and not the whole notebook.
There was an issue submitted about this (that I cannot find right now) that said that this is fixed but that is not the case unfortunately... (Unless I am doing something wrong)
e: #141493 is a related issue... Still can't find the original issue that was closed because it was fixed in insiders.
According to this stackoverflow post it used to be possible to search and replace in cells and not the whole notebook...

My reading of that SO thread is, find used only to look in the current cell and you couldn't get it to operate across the whole notebook. Now the opposite is true, and the other issue you linked to is about offering both. I think this one here should be closed as a duplicate.
/duplicate