[Q] How to tune DVB-C/B aka J.83B 256-QAM transponder over terrestrial?

tsscan --nit-scan --delivery-system DVB-C/B -f 112750000 --debug -m 256-qam -s 5900000

doesn't lock
dvbv5-zap -vvv -c channel.conf test

where channel.conf contains the following, works:
[test]
        DELIVERY_SYSTEM = DVBC/ANNEX_B
        FREQUENCY = 112750000
        MODULATION = QAM/256

I see dvb-c/b has unsupported stuff in a bunch of places, what does that actually "mean"? Is there anything needed to support other than passing this tuning parameter to dvb-api?

Hi @trollcop
I have never used DVB-C, /A or /B, with TSDuck because I never had access to a real cable network. So, I cannot tell by my own experience.
As a troubleshooting method, I suggest:

Try direct reception before full scanning: tsp -d -I dvb ... -O drop
If you receive nothing, make sure to specify all modulation parameters, typically --fec-inner. Each command uses its own defaults and maybe dvbv5-zap and TSDuck don't use the same defaults for the unspecified options.

In the TSDuck user's guide, DVB-C/B is marked as "unsupported", unlike /A and /C. I cannot remember what it means. Probably, at some point, the Linux DVB API did not support it. It has probably changed if you can successfully tune using dvbv5-zap. Fixing this in TSDuck requires a developer with access to a real DVB-C/B network with real streams. I do not have that access.

i can try to add support and test if you point out where i should start. I'll try pre-tuning and running tsp when I'm back at computer.
I've added test support for tuning this in a simple tuning/capture app and it works without any specific fec/etc settings:
https://github.com/trollcop/recskapa/commit/649ecc5c42617b6241d1b5b88ccc8a1daae203bc
I've got a network full of dvbc/b streams and would have no problem giving you access to it as needed.

Here's output of tslsdvb -v when one of the tuners is tuned + locked:
0: /dev/dvb/adapter0 ("Turbosight TBS 6209SE(Octa DVB-T/T2/C/C2/ISDB-T/C/A", DVB-T, DVB-T2, ATSC, ISDB-T, DVB-C, 2, DVB-C/C)
   Device: /dev/dvb/adapter0/frontend0

     Status: has signal, has carrier, has viterbi, has sync, has lock

     Signal: locked: yes, strength: -32.41 dB, SNR: 34.496 dB

     Delivery system ................................ 2
     Frequencies:
       Current ............................ 112,750,000 Hz
       Min ................................. 47,000,000 Hz
       Max ................................ 862,000,000 Hz
       Step .................................... 62,500 Hz
       Tolerance .................................... 0 Hz
     Symbol rates:
       Current .............................. 5,600,000 sym/s
       Min .................................. 1,700,000 sym/s
       Max .................................. 7,200,000 sym/s
       Tolerance .................................... 0 sym/s
     Spectral inversion .......................... auto
     FEC(inner) .................................. auto
     Modulation ............................... 256-QAM

     Capabilities: inversion auto, FEC 1/2, FEC 2/3, FEC 3/4, FEC 4/5, FEC 5/6,
       FEC 7/8, FEC auto, 16-QAM, 32-QAM, 64-QAM, 128-QAM, 256-QAM, QAM auto,
       transmission mode auto, guard interval auto, 2nd generation, recover,
       mute TS

It seems fec-inner should just work with auto - and since I've written drivers for Sony CXD28xx based hardware before, I can tell you that it doesn't even support setting FEC etc. since its all auto. Tuning parameters for DVB-C/J.83 is just frequency and symbol rate.
It is curious that delsys printed in above log is 2, I think that's due to a typo @ tsDeliverySystem.cpp:98 - will change and rebuild and see.
I will poke at the rest of the sores you pointed out and see if I can make something work.

Hey uhhh, just fixing
https://github.com/tsduck/tsduck/blob/2ea222a3cb4ab6c7ce6f9fcd9a299b4f67618cee/src/libtsduck/dtv/broadcast/tsDeliverySystem.cpp#L98
to DVB-C/B makes it tune and work in dvb plugin
./tsp -d -I dvb --delivery-system DVB-C/B --frequency 112750000 -m 256-qam -s 5600000 -O drop
tsp: Debug: debug level set to 1
tsp: Debug: ====> tsp -d
* Debug: debug level set to 1
* Debug: trying to load "/home/timecop/dev/tsduck/bin/release-x86_64-epgstation/tsplugin_dvb.so"
* Debug: registering input plugin "dvb", status: ok
* Debug: dvb: debug level set to 1
* Debug: dvb: ====> tsp -I dvb --delivery-system DVB-C/B --frequency 112750000 -m 256-qam -s 5600000
* Debug: drop: debug level set to 1
* Debug: drop: ====> tsp -O drop
* Debug: tsp: buffer size: 89,240 TS packets, 16,777,120 bytes
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/idVendor = "" (failure)
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/idProduct = "" (failure)
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/manufacturer = "" (failure)
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/product = "" (failure)
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/version = "" (failure)
* Debug: dvb: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb0.frontend0/device/serial = "" (failure)
* * dvb: using /dev/dvb/adapter0 (DVB-T, DVB-T2, ATSC, ISDB-T, DVB-C, DVB-C/B, DVB-C/C)
Debug: loading names file tsduck.dtv.names
* Debug: dvb: adding standards DVB to none
* Debug: dvb: starting discarding frontend events
* Debug: dvb: finished discarding frontend events
* Debug: dvb: tuning on /dev/dvb/adapter0/frontend0
* Debug: dvb: 1 DTVProperties:
* Debug: dvb: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
* Debug: dvb: tuning on /dev/dvb/adapter0/frontend0
* Debug: dvb: 6 DTVProperties:
* Debug: dvb: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 2 (0x00000002)
* Debug: dvb: [1] cmd = 3 (DTV_FREQUENCY), data = 112750000 (0x06B86DB0)
* Debug: dvb: [2] cmd = 4 (DTV_MODULATION), data = 5 (0x00000005)
* Debug: dvb: [3] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
* Debug: dvb: [4] cmd = 8 (DTV_SYMBOL_RATE), data = 5600000 (0x00557300)
* Debug: dvb: [5] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
* dvb: tuned to transponder --delivery-system DVB-C/B --frequency 112,750,000 --symbol-rate 5,600,000 --fec-inner auto --modulation 256-QAM
* Debug: dvb: starting tuner reception
* Debug: dvb: tuner reception started
* Debug: dvb: 6 DTVProperties (statistics result):
* Debug: dvb: [0] cmd = 62 (DTV_STAT_SIGNAL_STRENGTH), count = 2, stat = {scale: 1, value: -32410}, {scale: 2, value: 63500}
* Debug: dvb: [1] cmd = 63 (DTV_STAT_CNR), count = 2, stat = {scale: 1, value: 34781}, {scale: 2, value: 53136}
* Debug: dvb: [2] cmd = 66 (DTV_STAT_POST_ERROR_BIT_COUNT), count = 1, stat = {scale: 3, value: 0}
* Debug: dvb: [3] cmd = 67 (DTV_STAT_POST_TOTAL_BIT_COUNT), count = 1, stat = {scale: 3, value: 0}
* Debug: dvb: [4] cmd = 68 (DTV_STAT_ERROR_BLOCK_COUNT), count = 0, stat =
* Debug: dvb: [5] cmd = 69 (DTV_STAT_TOTAL_BLOCK_COUNT), count = 0, stat =
* dvb: locked: yes, strength: -32.41 dB, SNR: 34.781 dB
* Debug: dvb: initial buffer load: 44,620 packets, 8,388,560 bytes
* dvb: initial input bitrate is 40,544,293 b/s
* Debug: dvb: input thread started
* Debug: control commands: found 0 packet processor plugins
* Debug: drop: output thread started
* Debug: dvb: input: got bitrate 40,544,293 b/s

Damn it! Thanks a lot for finding this. Another wonderful copy/paste story...
I will fix it right away. Because this enum/string table is used everywhere, including in the definition of option --delivery-system, specifying --delivery-system DVB-C/B actually resulted in using DVB-C/A.
See the definition of option:
https://github.com/tsduck/tsduck/blob/2ea222a3cb4ab6c7ce6f9fcd9a299b4f67618cee/src/libtsduck/dtv/broadcast/tsModulationArgs.cpp#L1443

including in the definition of option --delivery-system, specifying --delivery-system DVB-C/B actually resulted in using DVB-C/A.

Yes, I think that's what happened. it was tuning A despite specifying B in cli.
(old version)
tsp -d -I dvb --delivery-system DVB-C/B --frequency 112750000 -m 256-qam -s 5600000 -O drop
...
* Debug: dvb: 7 DTVProperties:
* Debug: dvb: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 1 (0x00000001)

sets it to 1 which is incorrect. with the copypaste fix, it's correct at
* Debug: dvb: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 2 (0x00000002)

okay, so, tuning got fixed... but nit-scan isn't doing too well. It keeps defaulting to DVB-C, probably needs some extra hacks for ISDB... here's some logs
567750000 --debug -m 256-qam -s 5600000 --adapter 1
tsscan: Debug: debug level set to 1
tsscan: Debug: ====> tsscan --nit-scan --delivery-system DVB-C/B -f 567750000 --debug -m 256-qam -s 5600000 --adapter 1
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/idVendor = "" (failure)
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/idProduct = "" (failure)
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/manufacturer = "" (failure)
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/product = "" (failure)
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/version = "" (failure)
tsscan: Debug: /sys/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/dvb/dvb1.frontend0/device/serial = "" (failure)
tsscan: Debug: adding standards DVB to none
tsscan: Debug: starting discarding frontend events
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter1/frontend0
tsscan: Debug: 1 DTVProperties:
tsscan: Debug: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: tuning on /dev/dvb/adapter1/frontend0
tsscan: Debug: 6 DTVProperties:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 2 (0x00000002)
tsscan: Debug: [1] cmd = 3 (DTV_FREQUENCY), data = 567750000 (0x21D72D70)
tsscan: Debug: [2] cmd = 4 (DTV_MODULATION), data = 5 (0x00000005)
tsscan: Debug: [3] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
tsscan: Debug: [4] cmd = 8 (DTV_SYMBOL_RATE), data = 5600000 (0x00557300)
tsscan: Debug: [5] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: got 10000 packets
tsscan: Debug: adding standards MPEG to DVB
tsscan: Debug: got table id 0x00 on PID 0x0000
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got table id 0x40 on PID 0x0010
tsscan: Debug: got table id 0x41 on PID 0x0010
tsscan: Debug: got 10000 packets
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x42 on PID 0x0011
tsscan: Debug: * tuning to --delivery-system DVB-C --frequency 567,750,000 --symbol-rate 5,600,000 --fec-inner 8/9 --modulation 256-QAM
tsscan: Debug: starting discarding frontend events
tsscan: Debug: one frontend event discarded
tsscan: Debug: one frontend event discarded
tsscan: Debug: one frontend event discarded
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter1/frontend0
tsscan: Debug: 1 DTVProperties:
tsscan: Debug: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: tuning on /dev/dvb/adapter1/frontend0
tsscan: Debug: 7 DTVProperties:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 1 (0x00000001)
tsscan: Debug: [1] cmd = 3 (DTV_FREQUENCY), data = 567750000 (0x21D72D70)
tsscan: Debug: [2] cmd = 4 (DTV_MODULATION), data = 5 (0x00000005)
tsscan: Debug: [3] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
tsscan: Debug: [4] cmd = 9 (DTV_INNER_FEC), data = 8 (0x00000008)
tsscan: Debug: [5] cmd = 8 (DTV_SYMBOL_RATE), data = 5600000 (0x00557300)
tsscan: Debug: [6] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: 6 DTVProperties (statistics result):
tsscan: Debug: [0] cmd = 62 (DTV_STAT_SIGNAL_STRENGTH), count = 2, stat = {scale: 1, value: -41000}, {scale: 2, value: 62230}
tsscan: Debug: [1] cmd = 63 (DTV_STAT_CNR), count = 2, stat = {scale: 1, value: 33926}, {scale: 2, value: 51824}
tsscan: Debug: [2] cmd = 66 (DTV_STAT_POST_ERROR_BIT_COUNT), count = 1, stat = {scale: 3, value: 0}
tsscan: Debug: [3] cmd = 67 (DTV_STAT_POST_TOTAL_BIT_COUNT), count = 1, stat = {scale: 3, value: 0}
tsscan: Debug: [4] cmd = 68 (DTV_STAT_ERROR_BLOCK_COUNT), count = 0, stat =
tsscan: Debug: [5] cmd = 69 (DTV_STAT_TOTAL_BLOCK_COUNT), count = 0, stat =
* Frequency: 567,750,000 Hz, locked: no, strength: -41 dB, SNR: 33.926 dB

here's NIT:
* NIT Actual, TID 0x40 (64), PID 0x0010 (16)
  Version: 21, sections: 1, total size: 870 bytes
  - Section 0:
    Network Id: 0x000A (10)
    Network information:
    - Descriptor 0: Network Name (0x40, 64), 8 bytes
      Name: "スカパー!"
    - Descriptor 1: ISDB System Management (0xFE, 254), 2 bytes
      Broadcasting flag: 0 (Broadcasting)
      Broadcasting identifier: 7 (Satellite advanced narrow-band using 27 MHz bandwidth in 12.2 to 12.75 GHz band)
      Additional broadcasting id: 0x01 (1)
    Transport Stream Id: 0x3014 (12308), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8260 (33376), Type: 0x01 (Digital television service)
      Service id: 0x8277 (33399), Type: 0x01 (Digital television service)
      Service id: 0x8281 (33409), Type: 0x01 (Digital television service)
      Service id: 0x8287 (33415), Type: 0x01 (Digital television service)
      Service id: 0x8294 (33428), Type: 0x01 (Digital television service)
      Service id: 0x82A2 (33442), Type: 0x01 (Digital television service)
      Service id: 0x83AF (33711), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 567.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3017 (12311), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8249 (33353), Type: 0x01 (Digital television service)
      Service id: 0x8250 (33360), Type: 0x01 (Digital television service)
      Service id: 0x826E (33390), Type: 0x01 (Digital television service)
      Service id: 0x827E (33406), Type: 0x01 (Digital television service)
      Service id: 0x8285 (33413), Type: 0x01 (Digital television service)
      Service id: 0x82A6 (33446), Type: 0x01 (Digital television service)
      Service id: 0x82BF (33471), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 366.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3018 (12312), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8235 (33333), Type: 0x01 (Digital television service)
      Service id: 0x824A (33354), Type: 0x01 (Digital television service)
      Service id: 0x825C (33372), Type: 0x01 (Digital television service)
      Service id: 0x825F (33375), Type: 0x01 (Digital television service)
      Service id: 0x8274 (33396), Type: 0x01 (Digital television service)
      Service id: 0x8295 (33429), Type: 0x01 (Digital television service)
      Service id: 0x83C5 (33733), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 580.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3019 (12313), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 24 bytes
      Service id: 0x821E (33310), Type: 0x01 (Digital television service)
      Service id: 0x8220 (33312), Type: 0x01 (Digital television service)
      Service id: 0x823A (33338), Type: 0x01 (Digital television service)
      Service id: 0x823C (33340), Type: 0x01 (Digital television service)
      Service id: 0x8248 (33352), Type: 0x01 (Digital television service)
      Service id: 0x8268 (33384), Type: 0x01 (Digital television service)
      Service id: 0x8284 (33412), Type: 0x01 (Digital television service)
      Service id: 0x82BE (33470), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 340.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3020 (12320), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8236 (33334), Type: 0x01 (Digital television service)
      Service id: 0x8237 (33335), Type: 0x01 (Digital television service)
      Service id: 0x825A (33370), Type: 0x01 (Digital television service)
      Service id: 0x8276 (33398), Type: 0x01 (Digital television service)
      Service id: 0x8282 (33410), Type: 0x01 (Digital television service)
      Service id: 0x8291 (33425), Type: 0x01 (Digital television service)
      Service id: 0x8293 (33427), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 587.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3024 (12324), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 18 bytes
      Service id: 0x8259 (33369), Type: 0x01 (Digital television service)
      Service id: 0x825B (33371), Type: 0x01 (Digital television service)
      Service id: 0x8261 (33377), Type: 0x01 (Digital television service)
      Service id: 0x8278 (33400), Type: 0x01 (Digital television service)
      Service id: 0x8279 (33401), Type: 0x01 (Digital television service)
      Service id: 0x827F (33407), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 353.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3025 (12325), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 18 bytes
      Service id: 0x8210 (33296), Type: 0x01 (Digital television service)
      Service id: 0x8211 (33297), Type: 0x01 (Digital television service)
      Service id: 0x8263 (33379), Type: 0x01 (Digital television service)
      Service id: 0x8264 (33380), Type: 0x01 (Digital television service)
      Service id: 0x826D (33389), Type: 0x01 (Digital television service)
      Service id: 0x826F (33391), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 346.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3026 (12326), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x825E (33374), Type: 0x01 (Digital television service)
      Service id: 0x828E (33422), Type: 0x01 (Digital television service)
      Service id: 0x82A4 (33444), Type: 0x01 (Digital television service)
      Service id: 0x83B1 (33713), Type: 0x01 (Digital television service)
      Service id: 0x83B3 (33715), Type: 0x01 (Digital television service)
      Service id: 0x83C6 (33734), Type: 0x01 (Digital television service)
      Service id: 0x83C7 (33735), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 476.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3027 (12327), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 24 bytes
      Service id: 0x824B (33355), Type: 0x01 (Digital television service)
      Service id: 0x824E (33358), Type: 0x01 (Digital television service)
      Service id: 0x829B (33435), Type: 0x01 (Digital television service)
      Service id: 0x829C (33436), Type: 0x01 (Digital television service)
      Service id: 0x829D (33437), Type: 0x01 (Digital television service)
      Service id: 0x82B0 (33456), Type: 0x01 (Digital television service)
      Service id: 0x82B1 (33457), Type: 0x01 (Digital television service)
      Service id: 0x82BD (33469), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 483.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x3028 (12328), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8230 (33328), Type: 0x01 (Digital television service)
      Service id: 0x825D (33373), Type: 0x01 (Digital television service)
      Service id: 0x827B (33403), Type: 0x01 (Digital television service)
      Service id: 0x8280 (33408), Type: 0x01 (Digital television service)
      Service id: 0x83AE (33710), Type: 0x01 (Digital television service)
      Service id: 0x83B0 (33712), Type: 0x01 (Digital television service)
      Service id: 0x83B2 (33714), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 359.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4022 (16418), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 18 bytes
      Service id: 0x8206 (33286), Type: 0x01 (Digital television service)
      Service id: 0x8218 (33304), Type: 0x01 (Digital television service)
      Service id: 0x823B (33339), Type: 0x01 (Digital television service)
      Service id: 0x82A5 (33445), Type: 0x01 (Digital television service)
      Service id: 0x82B2 (33458), Type: 0x01 (Digital television service)
      Service id: 0x83BD (33725), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 327.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4023 (16419), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x821C (33308), Type: 0x01 (Digital television service)
      Service id: 0x8269 (33385), Type: 0x01 (Digital television service)
      Service id: 0x8283 (33411), Type: 0x01 (Digital television service)
      Service id: 0x8289 (33417), Type: 0x01 (Digital television service)
      Service id: 0x828A (33418), Type: 0x01 (Digital television service)
      Service id: 0x828B (33419), Type: 0x01 (Digital television service)
      Service id: 0x82AC (33452), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 132.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4024 (16420), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 42 bytes
      Service id: 0x824F (33359), Type: 0x01 (Digital television service)
      Service id: 0x8257 (33367), Type: 0xA5 (Promotion video service)
      Service id: 0x826C (33388), Type: 0x01 (Digital television service)
      Service id: 0x82A0 (33440), Type: 0x01 (Digital television service)
      Service id: 0x82B3 (33459), Type: 0x01 (Digital television service)
      Service id: 0x82B7 (33463), Type: 0x01 (Digital television service)
      Service id: 0x83BE (33726), Type: 0x01 (Digital television service)
      Service id: 0x83D5 (33749), Type: 0x01 (Digital television service)
      Service id: 0x83D8 (33752), Type: 0x01 (Digital television service)
      Service id: 0x83D9 (33753), Type: 0x01 (Digital television service)
      Service id: 0x83DA (33754), Type: 0x01 (Digital television service)
      Service id: 0x83DB (33755), Type: 0x01 (Digital television service)
      Service id: 0x83DC (33756), Type: 0x01 (Digital television service)
      Service id: 0x83DD (33757), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 125.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4025 (16421), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8266 (33382), Type: 0x01 (Digital television service)
      Service id: 0x826A (33386), Type: 0x01 (Digital television service)
      Service id: 0x8299 (33433), Type: 0x01 (Digital television service)
      Service id: 0x829E (33438), Type: 0x01 (Digital television service)
      Service id: 0x82A3 (33443), Type: 0x01 (Digital television service)
      Service id: 0x82A9 (33449), Type: 0x01 (Digital television service)
      Service id: 0x83BF (33727), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 138.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4026 (16422), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 15 bytes
      Service id: 0x824D (33357), Type: 0x01 (Digital television service)
      Service id: 0x8251 (33361), Type: 0x01 (Digital television service)
      Service id: 0x8258 (33368), Type: 0x01 (Digital television service)
      Service id: 0x8271 (33393), Type: 0x01 (Digital television service)
      Service id: 0x8297 (33431), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 333.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4028 (16424), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x8219 (33305), Type: 0x01 (Digital television service)
      Service id: 0x8244 (33348), Type: 0x01 (Digital television service)
      Service id: 0x8292 (33426), Type: 0x01 (Digital television service)
      Service id: 0x82B6 (33462), Type: 0x01 (Digital television service)
      Service id: 0x83C0 (33728), Type: 0x01 (Digital television service)
      Service id: 0x83C3 (33731), Type: 0x01 (Digital television service)
      Service id: 0x83C4 (33732), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 112.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4029 (16425), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 18 bytes
      Service id: 0x820B (33291), Type: 0x01 (Digital television service)
      Service id: 0x820D (33293), Type: 0x01 (Digital television service)
      Service id: 0x820F (33295), Type: 0x01 (Digital television service)
      Service id: 0x8290 (33424), Type: 0x01 (Digital television service)
      Service id: 0x82AA (33450), Type: 0x01 (Digital television service)
      Service id: 0x82AB (33451), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 314.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4030 (16432), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 18 bytes
      Service id: 0x8217 (33303), Type: 0x01 (Digital television service)
      Service id: 0x8252 (33362), Type: 0x01 (Digital television service)
      Service id: 0x826B (33387), Type: 0x01 (Digital television service)
      Service id: 0x827C (33404), Type: 0x01 (Digital television service)
      Service id: 0x828F (33423), Type: 0x01 (Digital television service)
      Service id: 0x82B5 (33461), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 281.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4031 (16433), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 0x824C (33356), Type: 0x01 (Digital television service)
      Service id: 0x8265 (33381), Type: 0x01 (Digital television service)
      Service id: 0x8267 (33383), Type: 0x01 (Digital television service)
      Service id: 0x8275 (33397), Type: 0x01 (Digital television service)
      Service id: 0x827A (33402), Type: 0x01 (Digital television service)
      Service id: 0x8296 (33430), Type: 0x01 (Digital television service)
      Service id: 0x82A8 (33448), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 119.2500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate
    Transport Stream Id: 0x4032 (16434), Original Network Id: 0x000A (10)
    - Descriptor 0: Service List (0x41, 65), 15 bytes
      Service id: 0x8209 (33289), Type: 0x01 (Digital television service)
      Service id: 0x8222 (33314), Type: 0x01 (Digital television service)
      Service id: 0x8238 (33336), Type: 0x01 (Digital television service)
      Service id: 0x8245 (33349), Type: 0x01 (Digital television service)
      Service id: 0x82B4 (33460), Type: 0x01 (Digital television service)
    - Descriptor 1: Cable Delivery System (0x44, 68), 11 bytes
      Frequency: 320.7500 MHz
      Symbol rate: 5.6000 Msymbol/s
      Modulation: 256-QAM
      Outer FEC: code 3 (reserved), Inner FEC: 8/9 conv. code rate

I guess it tries to tune it as DVB-C/A instead of DVB-C/B, or something idk.

I guess it tries to tune it as DVB-C/A instead of DVB-C/B, or something idk.

Exactly. A NIT-scan is based on the system delivery descriptor for each TS. These descriptors are defined by DVB.
ISDB redefines the satellite delivery descriptor for ISDB-S with same tag as the DVB one but slightly different layout (a standardization nightmare). ISDB also defines a specific descriptor for ISDB-T, with a distinct tag from the DVB terrestrial delivery descriptor (so this one is OK).
But there is nothing for cable. There is no ISDB-C, isn't it? And the DVB-defined cable delivery descriptor does not provide any information to discriminate between DVB-C/A/B/C.
So, currently, when the tuning parameters are extracted from a cable system delivery descriptor, the type is assumed to be DVB-C (meaning /A by default).
https://github.com/tsduck/tsduck/blob/1c16295ef9bcc7969a5bc1c7648fec7615cdc989/src/libtsduck/dtv/broadcast/tsModulationArgs.cpp#L586
We should add something external to the signalization to force the interpretation of a cable delivery descriptor as DVB-C/B (or /C for generalization). There are several possibilities.

This can be an option in tsscan meaning "in a NIT scan, force all delivery systems to this value". This will work but this is limited to tsscan, not used in other contexts.
This can be an ISDB discriminator such as used in the satellite delivery descriptor which uses the same tag but the interpretation of which varies depends on the TS standard, DVB or ISDB.

The problem with the second solution is that the satellite interpretation is well-defined in ARIB STD-B10 and can be safely considered as part of ISDB signalization. AFAIK, the ARIB standards say nothing about cable. There is no strictly defined ISDB signalization on the cable delivery descriptor (unlike satellite). So, assuming DVB-C/B in a cable descriptor as soon as we are in an ISDB context is maybe not legitimate. Are we sure that all Japanese cable networks use DVB-C/B? What about other ISDB countries in South America, the Philippines and Africa?

Maybe there is a more automatic way.
Can we consider that a cable network is always homogeneous? All DVB-C/A or /B or /C, but never a mixture? It sounds rational but is this true? Satellite and terrestrial are different. You can have DVB-T and -T2, or -S and -S2, on the same network. But you usually do not have DVB-S and ISDB-S on the same network.
If we assume that any DVB-C network always uses the same variant A, B or C, considering that the cable delivery descriptor has no data to discriminate between them, tsscan can safely assume that the initial system delivery can be forced on all TS when it is one of DVB-C/x.
If we cannot assume that all DVB-C network are homogeneous, then we need to add some option such as --homogeneous-cable-network to tsscan.
Of course, this only applies to DVB-C/x. In the case of a DVB-C2 TS, there is a specific C2 delivery descriptor.

If we cannot assume that all DVB-C network are homogeneous, then we need to add some option such as --homogeneous-cable-network to tsscan.

there's a nit-other that links to isdb-t channel that's used for discovery of cable network (it has nit-other with the dvb-c/b entries but from what i can see in the current qam nit they're all the same.
i don't have a lot of computer access during the next week so I'm not sure how much time I'll have to dig through the arib specs to look for dvbc specific descriptors.
i like your suggestion to force homogeneous network with a switch, but i wouldn't add it as default under --isdb as this is one specific network (flets tv, catv over fiber) which isn't IP based, and i don't have an easy way to scan others like jcom or similar.

there's a nit-other that links to isdb-t channel

Currently, tsscan uses the NIT Actual only. The idea is to scan a network starting from a TS of that network. Therefore, on the initial TS, the target NIT is the actual one.

dig through the arib specs to look for dvbc specific descriptors.

AFAIK, the only ARIB specs containing signalisation are STD-B10 and STD-B21 (see bibliography) and they do not mention a cable descriptor.
The only spec I do not have access to is ARIB STD-B16 (ISDB Standard Digital Receiver for Satellite) which is not free and not available in English. Given the reference to satellite, I don't think we could find anything about cable.
The only delivery system for which there is no signalisation is DVB-C (/A, /B, /C). So, the only case with a problem is a TS description containing a cable_delivery_system_descriptor. All the rest is addressed using other delivery descriptors.
We face only two cases:

On a cable, inside one "network" (in the DVB sense), all TS use the same Annex A, B or C. In that case, in the presence of a cable_delivery_system_descriptor, we scan that TS using the same variant of DVB-C that was used to scan the initial NIT.
On the same cable, several variants of A, B or C coexist. Since there is no way to signal which variant is used on which TS, I consider this case as unrealistic and unpractical because no official cable set-top box could successfully scan the network.

Therefore, I will implement solution 1. We will see how it behaves. We count on you @trollcop to provide some feedback, when you are available, because you are probably the only TSDuck user who uses it on non-/A DVB-C networks.

On a cable, inside one "network" (in the DVB sense), all TS use the same Annex A, B or C. In that case, in the presence of a cable_delivery_system_descriptor, we scan that TS using the same variant of DVB-C that was used to scan the initial NIT.

That sounds reasonable. As you say in variant 2, it would make no sense to mix and match delivery systems as no box would be able to scan unless hard coded, which i really wouldn't put past a Japanese system, but is probably unlikely for anywhere else. I guess this really only affects cable because even in satellite you'd have a delivery descriptor that would say dvbs or s2 etc, leading to no ambiguity.
and yeah no issues with testing. i still have access to various things remotely even not in front of PC.

I pushed an enhancement of the NIT scan to propagate the original DVB-C/x annex to the scanned transport streams, when they are signalled using a cable_delivery_system_descriptor.
This had other consequences that were not previously considered, in the plugin nitscan and in the format of the channel configuration files.
Let us know if you can now successfully scan a DVB-C/B network.

In the test suite, I added test-161 which uses the TSDuck builtin tuner emulator to scan a DVB-C/B network with two TS. The scan fails before the fix (tsscan tries to use DVB-C on the scanned TS) and passes after the fix. However, a test on a real DVB-C/B network remains necessary.

I've pulled latest revision today and built.
here's output log and generated xml from:
./tsscan --japan --nit-scan --delivery-system DVB-C/B -f 112750000 --debug -m 256-qam -s 5600000 --adapter 0 -l --update-channels skapa2.xml
output.log
skapa2.zip
.zip is xml zipped since I can't attach it.
Other than "locked: no" during scan i think it looks ok? I'm not sure what the locked flag there signifies because its actually locking and receiving ts?

Thanks for the feedback. It looks good.
The service names in output.log look corrupted but it's probably a character representation issue during a transfer because they look correct in the XML file. Normally, the output is forced in UTF-8 representation. Are the service names correctly displayed by tsscan?
Concerning the signal lock status, TSDuck only displays what the driver reports. The status is obtained on the front end device using an ioctl with FE_READ_STATUS command. In the returned value, the lock status is obtained from bit mask FE_HAS_LOCK.
The accuracy of reporting in LinuxTV drivers is decreasing over time. It seems that developers no longer care about doing everything correctly. When the signal is tuned and the TS is read, they stop there and don't care about accurate reporting. When I started with Linux tuners, around 2005, the reporting was accurate: status, BER, SNR, modulation parameters. Getting the latter was especially useful with DVB-T where you can tune on a given frequency without accurate parameters and when the signal is locked the drivers used to report the actual parameters. After a couple of years, I ported TSDuck to Windows and realised that Windows BDA drivers were completely unreliable and reported crap. After nearly two decades of tuning, I would have hoped that the Windows drivers would improve up to the Linux level. However, I realise that this is the opposite: the Linux drivers worsen down to the Windows level...

The service names in output.log look corrupted but it's probably a character representation issue during a transfer because they look correct in the XML file. Normally, the output is forced in UTF-8 representation. Are the service names correctly displayed by tsscan?

I used putty log since > logfile didn't work and only did 'printable' output which skipped non-ascii stuff. yes, it looked fine on console as UTF-8. ARIB encoding was properly picked up.
Regarding lock, it's definitely locked (since my other rec app depends on waiting for lock before going to get TS), so I'm not sure why it would report unlocked. Maybe it needs to poll a little bit for lock status to change? idk. sony frontend hardware has pretty granular lock reporting, for example in ISDB-T they'd have TMCC (1seg/some layers locked) followed by TS lock (actually error-free TS available on all segments), so it's capable of reporting TS lock on DVB-C for sure.
But yeah, overall scan seems to be working correctly. There are indeed 20 transponders and service IDs seem to match. btw, fun (?) fact, service ID determines the visible channel # but with top bit removed. i.e. home drama channel SID 0x8295 = ch 0x295 = ch661 on UI.
Regarding signal reporting accuracy, I think dvbv5 actually improved on things by allowing to store scale/dbm based values so that you can get RF input levels and C/N etc as proper fractions and not just random numbers. I remember last I touched dvb you'd just get a random uint16 as "SNR" and no further explanation of its range or anything.

Closing as resolved, thanks!


Setup DNS for the API Gateway to access the judge from judge.profound.academy

The LambdaJudge should be accessible from judge.profound.academy

Added to the DNS records following this: https://stackoverflow.com/a/57949615/5512770

judge.profound.academy
CNAME
1 hour
https://5qsqutwixi.execute-api.us-east-1.amazonaws.com.

https://judge.profound.academy/
is now available as an endpoint


Fix persistent damage of cloak of gnawing leaves

Bleed is always persistent, so there's nothing to fix here.

I have [bleed] without persistent first inside 2 others new description for items of the last AP

Cloak of Thirsty Fronds
Cloak of Devouring Thorns

I fixed the other outliers, so this one can be closed as everything is no in the same format.


feat: export facemaps

This PR adds the feature of exporting face maps as a mesh attribute by enabling "Face Maps" in the "Geometry" options of the exporter.
Face map names are exported to the current node's extras "facemaps".
"nodes" : [
    {
        "extras" : {
            "facemaps" : [
                "FaceMap"
            ]
        },
        "mesh" : 0,
        "name" : "Cube"
    }
],
"meshes" : [
    {
        "name" : "Cube",
        "primitives" : [
            {
                "attributes" : {
                    "POSITION" : 0,
                    "NORMAL" : 1,
                    "TEXCOORD_0" : 2,
                    "_FACEMAPS" : 3
                },
                "indices" : 4
            }
        ]
    }
],

The topic was discussed here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1232, https://github.com/KhronosGroup/glTF-Blender-IO/pull/1515
Main idea from here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1232#issuecomment-797840257
The original code can be found here: https://github.com/canadaduane/glTF-Blender-IO/tree/export-facemaps-and-vertex-groups
Is it a good idea to merge it into the master branch?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: scurest:x: iuriiiurevichYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for all of your work @scurest and @iuriiiurevich. Is there someone who can authorize it being merged in?

A complete refactoring of custom attribute is in progress here: #1676 , and is planned for 3.4
Facemaps will benefit from these refactoring, so this PR will not be merged as-is.


No difference between match halfs

Especially we can not check the result after basic time of the game and after eventually added time of the game.

No, its not part of this.

But why? Many implementations need more detailed data than just the final result... Match can lasts 90 minutes and can lasts 120 minutes and how can i know the result after first two halfs (after 90 minutes)?


Handling arguments for mitmdump scripts

Hey,
what is the current state of Handling arguments? The Readme states: FIXME. Is it currently possible to pass arguments to a python script for mitmdump?
Cheers

Are you talking about 2.0 or the current master branch? See https://github.com/mitmproxy/mitmproxy/blob/2.0.x/examples/simple/script_arguments.py for 2.0, and https://github.com/mitmproxy/mitmproxy/blob/master/examples/simple/custom_option.py for master. Now I'm only curious where you found that FIXME? 😉

I'm guessing he's referring to this

Ah, yes. I only searched through our README files 😄. Thanks @ujjwal96!

Yes, I am talking at the current master branch. @ujjwal96 found the correct position ;)


Add constructor tests for TopicCreateResult

🆕🐥 First Timers Only
This issue is reserved for people who have never contributed to hedera-enterprise or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution to Hedera.
👾 Description of the issue
In the hedera-base module you can find the ProtocolLayerDataCreationTests test class. The class use junit to automatically test the construction of all records that are used in the protocol layer (see com.openelements.hedera.base.protocol package). As you can see the class tests provides (by using Assertions.assertDoesNotThrow) and negative (by using Assertions.assertThrows) checks for the creatation of records. Today not all records are fully tested and tests for the record TopicCreateResult are missing.
Suggested solution
Create a new test method in the ProtocolLayerDataCreationTests class that is named by the given pattern of all other test methods and implement the needed tests for the record.
📋 Step by step guide to do a contribution
If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow.
A more detailed general documentation of the GitHub PR workflow can be found here.

[ ] Claim this issue: Comment below that you are interested in working on the issue
[ ] Wait for assignment: A community member with the given rights will add you as an assignee of the issue
[ ] Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
[ ] Check out the forked repository
[ ] Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
[ ] Solve the issue in your branch.
[ ] Commit your changes: to your branch
[ ] Start a Pull Request (PR): in the hedera-enterprise repository
[ ] Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the community for support.
[ ] Wait for reviews: Members of the community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
[ ] You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of our community as an open-source contributor ❤

🎉 Contribute to Hacktoberfest
Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽
🤔 Additional informantion
If you have any questions, just ask us directly in this issue by adding a comment. You can join the Hedera community chat at Discord. A general manual about open-source contributions can be found here.

Hi @Ndacyayisenga-droid , I would like to work on this issue. Can you please assign this to me?

Hi @Ndacyayisenga-droid , I am using the string "0.0.12345" to create an instance of TopicId, as shown below.
final TopicId validTopicId = TopicId.fromString("0.0.12345");
Could you please verify this or suggest the string for the TopicId instance?
Thanks

TopicId

@rdodiya that should be okay!


IO-367: Add convenience methods for copyToDirectory (closes #18)

based on patch supplied by James Sawle

Coverage decreased (-0.01%) to 90.029% when pulling 861a4e87e19ec717bef84ec5e37b0b745a611300 on PascalSchumacher:copyToDirectory into 156653ea56fe215b97a263a770ea7094ff6adb84 on apache:master.

Coverage increased (+0.2%) to 90.254% when pulling ab9b96dc58cc0729a925888fb197eae105ef8426 on PascalSchumacher:copyToDirectory into 156653ea56fe215b97a263a770ea7094ff6adb84 on apache:master.

Coverage increased (+0.05%) to 90.086% when pulling ab9b96dc58cc0729a925888fb197eae105ef8426 on PascalSchumacher:copyToDirectory into 156653ea56fe215b97a263a770ea7094ff6adb84 on apache:master.


Clipboard support from integrated terminal

What is your suggestion?
On linux (and WSL2), I like to use clipboard utilities to paste the stdout of a process to the clipboard.
Like the following:
date | xclip -selection clipboard

Currently, it is not possible to do something similar if developing remotely.
It would be great if the vscode would have the functionality code --clipboard to allow this.
So that the following would lead to the text to be in the clipboard:
echo -n my clipboard text |  code --clipboard

Why do you want this feature?
When interacting with tokens etc. it would be a nice feature to hide the tokens from any output and history.
Are there any workarounds to get this functionality today?
Select the output of the application, press CTRL+SHIFT+C.
But that is cumbersome and also in case of passwords, prints the passwords to the terminal which has to be cleared afterwards.

see implementation in PR https://github.com/microsoft/vscode/pull/181725

It's a nice idea. My only concern is that code --clipboard is not very intuitive. code is the command to start code.
I'd suggest a different command name.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I think that's not really a problem as there are already other commands on the code utiliy like listing and adding extensions. But of course we could name it "--copy-stdin-to-clipboard" and keep the short hand "-c".
Nonetheless, if I understand you correctly, you wouldn't go with any parameter to the code command, but instead go with something like code-helpers, code-utils or even code-clip?  I personally do not have a preference here and would go with everything that you think fits best.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@aeschli
It's a shame that 20 votes are needed here for it to be taken into consideration. Unfortunately, it did not reach that, and I also don't see how this could possibly be achieved here without actively making a lot of advertising for it. This can quickly be lost amongst all the issues.
But back to the request: I would still like to have the ability to copy from the terminal via clipboard. The command is not important to me here, but the current implementation in VSCode prevents this from being implemented (even as an extension). See the PR that I had already prepared for this.
Perhaps something else would be more effective and streamlined with the vscode idea, such as an extension to the plugin API that allows commands to be defined that can be accepted by the VSCODE pipe socket (maybe after the user has confirmed it once). The actual command and tooling (copy command in this case) could then be the task of the extension.


ebpf: remove detection of BPF config when running at container #127

remove detection of BPF config when running at container.
In Github Action release.yml , qemu in docker ,do not have BPF config , eCapture cant works with ecapture -h.
other issue : #117
Signed-off-by: CFC4N<EMAIL_ADDRESS>

@vincentmli  Cloud you test this PR ?

I just tested your PR in k8s and k3s cluster,  both not working
# git branch
  master
* remove-detection-bpf
  v0.1.10
  vli-dev
[root@cilium-dev ecapture]# make clean
rm -f user/bytecode/*.d
rm -f user/bytecode/*.o
rm -f assets/ebpf_probe.go
rm -f bin/ecapture
rm -f .check*

[root@cilium-dev ecapture]# make
[root@cilium-dev ecapture]# ls -l bin/ecapture
-rwxr-xr-x 1 root root 7385088 Jul  7 14:53 bin/ecapture

# kubectl exec -it netshoot-ecap -- /bin/bash
bash-5.1# ecapture -h
2022/07/07 14:57:36 Kernel config read failed, error:KernelConfig not found.

Could you upload text content of /proc/1/cgroup when in k8s and. k3s ?

does /.dockerenv exist?

@cfc4n works now
# kubectl exec -it netshoot-ecap -- /bin/bash
bash-5.1# ecapture -h
2022/07/08 15:05:36 Your environment is a container. We will not detect the BTF config.
NAME:
	eCapture - capture text SSL content without CA cert by ebpf hook.


Upgrade identity.inbound.provisioning.scim2 version

Upgrade identity.inbound.provisioning.scim2 version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7208139104

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7208139104
Status: failure


[fix]: add dep bot for GHA and update pipeline

add dep bot for GHA and update pipeline

@yellowhat or @rootfs , could you please help merge this one?


Eagerly initialized Random in various extensions

Fix #2657
Fix #2664

7fd7a23: More fixes.
I'd never tell that we have so many Randoms in our extensions


Add "implement" button on SubclassResponsibility debugger window

When the debugger opens because of a DoesNotUnderstand error, there's a + button to add the method to self class, which opens an editor.
Similarly, there should be a button to implement the method in the subclass when the debugger opens because of a SubclassResponsibility error. Ideally, it should also be possible to choose in which subclass along the chain to implement the method (between self class and the class that had the self subclassResponsibility implementation).
(This feature exists in the Pharo debugger.)


[Style] Improve Our Valuable Contributors title

Description
The current title, "Our Valuable Contributors," is a good starting point, but it could be more engaging and capture the essence of our contributor community.
I would like to improve it, want to make a label ( A colored rectangle with text inside ) and also write something creative replacing "Our Valuable Contributors", example: ⭐ Contributors Spotlight
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Please /assign me the issue
@Rakesh9100

Hi, I would like to solve this issue, please assign me

Hi, I would like to solve this issue, please assign me

I am already working it 😄 have pulled a PR , waiting for it to be reviewed.


add nav-bar in Register/login page and some fixes

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

This is not a fix. This is a request to add login and signup pages to the site.
Summarize what this PR fixes:-
Fixes #
Checklist
(Add an x between the brackets to check the items)

[ ] I have summarize what this PR fixes above
[ ] I have provided the issue ID/URL above
[ ] I have not added Bootstrap or jQuery and used correct styling guide.
[ ] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[ ] I was the first one to claim the issue or I created the issue - I created the issue

Good start, it still needs the more dropdown and dark mode to be applied.


Look for a specific file instead of a heading?

I've got a folder under Journal named Schedule, within which I store schedules for each day. e.g S9923.
I'd like for the day-planner to detect the file, but there's no such option.
I have templater installed, so there's no need to worry about the numbers after S in the file.

Do I understand you correctly that you do not want to put a # Day planner heading into the file or is it about the file detection?

Do I understand you correctly that you do not want to put a # Day planner heading into the file or is it about the file detection?

Yes, I don't need a heading and I also would like for the daily planner to be in separate file.

I see, thanks. Would you mind needing to have a heading though? I like your username btw.

I mean, as long as I get to have the daily planner in a separate file from daily notes, I don't mind having a heading there.

Closing this as a duplicate of #242


Add docker-compose by default

And if possible, would be great to have docker-compose as part of the OS available as well

The user @x-jokay proposed in the issues #6 add by default docker-compose in BurmillaOS
We could create an option in the cloud-config.yml to enable docker-compose

I'd use this also - with the ability to update the version of compose as needed.  This might be more tricky than it seems as there is probably some redundancy with ros service - but migrating that to "plain" compose seems like an extra nice-to-have goal.

It is very easy add docker-compose as system service.
Tricky part is get that how to command available inside of console container. Code contains some extra logic to handle it for user docker and we most likely need something similar.
This code makes user docker commands available to console:
https://github.com/burmilla/os/blob/0308bfe208060a9225e43bfb14a12581b2ee7a55/cmd/control/util.go#L36-L59
but I have not yet found that how container files gets visible to /var/lib/rancher/engine in first place.

So by putting docker-compose in /var/lib/rancher/engine/docker-compose for example and making a symbolic link /usr/bin/docker-compose should the console recognize it?


added the other noOp obj

Ticket: n/a
Context

adding more noOp items in keg-core for the Tap to use

Goal

adding more noOp items in keg-core for the Tap to use so I can use the noPropArr in the tap

Updates

repos/keg-core/core/base/utils/helpers/method/noop.js

added noOpObj, noPropObj, noPropArr

Testing

n/a

michael is doing it


0.1.6 release

This PR finalizes preparation of the mcgoo/cargo-vcpkg tree for the first release from this location.
This updates the tree to build cleanly with the latest rust and cargo-metadata dependencies, and disables a test that was added while @mcgoo was addressing #1 (unfinished).
Motivation for getting this done is so that the vcpkg-rs repo can then be reorganized to address packaging issues mcgoo/vcpkg-rs#33 and mcgoo/vcpkg-rs#35.

I packed all the necessary changes into this single PR, whereas normally one would do the version release dance separately.  @mcgoo already shared publish rights on crates.io, however in this case I do not have write access to this particular repo (I do for mcgoo/vcpkg-rs).


fix: signal done only after table finishes rendering

Not quite ready for review, we're still doing some manual testing


Update appcompat views

This PR fixes https://github.com/elye/loaderviewlibrary/issues/10

Thanks for the input @alorma . Maybe instead of changing the base of LoaderTextView, introduce a new LoaderAppCompatTextView extends AppCompatTextView would ensure existing user is not affected by this change, while user could also use the AppCompat if they prefers. Thanks.

There's no difference on performance or methods.
Even AppCompatTextView extends from TextView so no casting issues


V2.x.x

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (2639972) to head (6a2c8bc).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #75   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          614       616    +2
  Branches       121       121
=========================================
+ Hits           614       616    +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


BigTable as a sink

Investigate using BigTable as a sink using (very) wide columns.

I remember now why this is not possible in BigTable -- you can not conditionally increment a cell.


Make setting the log level from a file neater.

Make setting the log level from the config file a one liner by specialising yaml-cpp.

Given how common this is I think I would make it automatically included in the configuration extension. Now that I think of it we should probably do that with yaml expression too (another PR). Also once this PR is merged you should make a PR where you spread the word of log level to all the modules

So do you mean that we should check for the "log_level" member and if it exists, automatically set the log level with the yaml-cpp extension?


Collect data for 5G cell towers

Currently no data is collected for 5G cell towers, because MLS does not support them. Add support for collecting data for 5G cell towers
Before implementation, investigate:

How does Ichnaea handle fields with values it doesn't support?

If reports with 5G cell tower data are discarded, there needs to be a toggle in the settings whether to send the data

How to map cell tower data (tracking area code etc.) to the data model?

Hi,
Regarding TAC or PCI, it is similar to LTE. Concerning the cellID, the important difference is that you must use a long type variable instead of integer.
OpenCellID has already implemented 5G. The radioType is "NR"

How does Ichnaea handle fields with values it doesn't support?
* If reports with 5G cell tower data are discarded, there needs to be a toggle in the settings whether to send the data

I haven't tested it but as far as I can tell by looking at the code, fields that are not defined in Ichnaea's schemas are discarded not entire reports:
All CellTower classes which are used in the 3 different Submit endpoints inherit (through multiple others) from StringVocabularyNode in https://github.com/mozilla/ichnaea/blob/9e6529e/ichnaea/api/schema.py#L39-L54 which describes that:

It removes the value if it isn't in the vocabulary.

And the vocabulary defined by all submit schemas is:
RADIO_STRINGS = ["gsm", "cdma", "umts", "wcdma", "lte"]

…so, if a report with mutiple cellTowers also includes one with radioType: "NR", it should through out just that cellTower, nothing else.

Looks like Android returns 5G cell tower data (CellInfoNr) only when 5G standalone networks are in use


Exclude Carthage folder the same way Pods is

Hi @tsabend, this is a very nice tool, thanks for sharing it.
I run it on my day job Xcode project, which uses Carthage to resolve dependencies, and got a crash.
I think it was due to the fact that we are using a project called Reachability.swift, which Carthage fetches into a folder with the same name, including the .swift part. fus then tries to read the content of what it thinks it's the filed Reachability.swift, but that's actually a folder.
Errno::EISDIR: Is a directory @ io_fread - /Users/gio/Developer/iflix/ios/Carthage/Checkouts/Reachability.swift
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:35:in `read'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:35:in `block in swift_classes'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:35:in `each'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:35:in `reduce'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:35:in `swift_classes'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:43:in `unused_classes'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/lib/fus/finder.rb:20:in `unused_classnames'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/bin/fus:14:in `find'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/gems/fus-0.0.2/bin/fus:34:in `<top (required)>'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/bin/fus:23:in `load'
  /Users/gio/Developer/iflix/ios/vendor/bundle/ruby/2.3.0/bin/fus:23:in `<top (required)>'

This PR does not fix the issue that results in that crash, but just quickly works around it by excluding the Carthage folder, the same way that the Pods one is already excluded.
I think this is an acceptable workaround for the time being, given that it mimics an already existing behaviour.

Glad you're enjoying it and thanks for opening the PR. Seems like a very reasonable solution.


Better results without accounting for difficult images in Middlebury

Hi,
Thanks for publishing this great work.
I was testing your code on Middlebury and I realized that you obtain slightly better results when you don't multiply by 0.5 on difficult images.
Are you applying this factor because some other previous work did the same or there is any other reason to do it? If there is a previous work that does this scaling, could you tell me which?
By the way, I am referring to this:
difficult_images = ["PianoL", "Playroom", "Playtable", "Shelves", "Vintage"]
...
...
if seq in difficult_images:
    scalar = 0.5

Thanks in advance,
Sergio

Hi,
We used the weights reported in the benchmark (the green bars) of training sparse set:
https://vision.middlebury.edu/stereo/eval3/

Hi,
Oh, thanks, I didn't know about this.
Thanks!

@serizba
Hello,
Have you reproduced this repo with the pretrained model ?


Migrate golang-mock to go-uber-mock package

Fixes https://github.com/antrea-io/antrea/issues/5311
Google no longer maintains the golang/mock package. This PR migrates gomock to go.uber.org/mock package maintained here - https://github.com/uber-go/mock.

The build erro are cause by a dependency that needs to be updated. I have opened https://github.com/vmware/go-ipfix/pull/316

go-ipfix v0.7.0 is available for use. Please consider upgrade antrea's dependency on it according to https://github.com/antrea-io/antrea/pull/4993

@aniketraj1947 I don't see the change to the go.mod (go-ipfix upgrade to v0.7.0)?

@aniketraj1947 could you check the test test failures? they seem pretty straightforward to fix

@aniketraj1947 Did you fix the formatting issues as well (reported by make golangci)?

@aniketraj1947 Did you fix the formatting issues as well (reported by make golangci)?

@antoninbas, all reported failures should be fixed now. Could you please trigger the jobs?

/test-all

Unrelated failure in jenkins-e2e job