loragw_pkt_logger: ERROR: failed to start the concentrator

I have an error similar to that; https://github.com/will127534/LoRa-concentrator/issues/33
I have Version 3 of LoRa Concentrator, this is so good Gateway for using LoRaWAN with TheThingsNetwork for PoC.
I examined this on RPi3(Latest Raspbian Desktop), however it doesn't run successfully.
We can found this wiki; https://github.com/will127534/LoRa-concentrator/wiki/Startup-Guide
I got below error at first step(2.5A supplied);
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ sudo ./util_pkt_logger
loragw_pkt_logger: INFO: found global configuration file global_conf.json, trying to parse it
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
loragw_pkt_logger: INFO: lorawan_public 1, clksrc 1
loragw_pkt_logger: INFO: radio 0 enabled (type SX1257), center frequency 915000000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
loragw_pkt_logger: INFO: radio 1 enabled (type SX1257), center frequency 916500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
loragw_pkt_logger: INFO: LoRa multi-SF channel 0 enabled, radio 1 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 1 enabled, radio 1 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 2 enabled, radio 1 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 3 enabled, radio 0 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 4 enabled, radio 0 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 5 enabled, radio 0 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 6 enabled, radio 0 selected, IF 200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 7 enabled, radio 0 selected, IF 400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa standard channel enabled, radio 1 selected, IF -200000 Hz, 250000 Hz bandwidth, SF 7
loragw_pkt_logger: INFO: FSK channel enabled, radio 1 selected, IF 300000 Hz, 125000 Hz bandwidth, 50000 bps datarate
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000000
loragw_pkt_logger: INFO: found local configuration file local_conf.json, trying to parse it
loragw_pkt_logger: INFO: local_conf.json does not contain a JSON object named SX1301_conf
loragw_pkt_logger: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000101
loragw_pkt_logger: ERROR: failed to start the concentrator
Who do know or can solve this?

Ok, then try open the debug output to see where is the problem
to open the debug config, modify the following file: lora_gateway/libloragw/library.cfg
change DEBUG_HAL= 0 to DEBUG_HAL= 1
then recompile both packet_forwarder and lora_gateway and try running the gateway again.

Thanks for replying.
I got below;
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ ./util_pkt_logger
loragw_pkt_logger: INFO: found global configuration file global_conf.json, trying to parse it
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
loragw_pkt_logger: INFO: lorawan_public 1, clksrc 1
lgw_board_setconf:427: Note: board configuration; lorawan_public:1, clksrc:1
loragw_pkt_logger: INFO: radio 0 enabled (type SX1257), center frequency 915000000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
lgw_rxrf_setconf:488: Note: rf_chain 0 configuration; en:1 freq:915000000 rssi_offset:-166.000000 radio_type:2 tx_enable:0 tx_notch_freq:0
loragw_pkt_logger: INFO: radio 1 enabled (type SX1257), center frequency 916500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
lgw_rxrf_setconf:488: Note: rf_chain 1 configuration; en:1 freq:916500000 rssi_offset:-166.000000 radio_type:2 tx_enable:0 tx_notch_freq:0
loragw_pkt_logger: INFO: LoRa multi-SF channel 0 enabled, radio 1 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 0 configuration; en:1 freq:-400000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 1 enabled, radio 1 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 1 configuration; en:1 freq:-200000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 2 enabled, radio 1 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 2 configuration; en:1 freq:0 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 3 enabled, radio 0 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 3 configuration; en:1 freq:-400000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 4 enabled, radio 0 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 4 configuration; en:1 freq:-200000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 5 enabled, radio 0 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 5 configuration; en:1 freq:0 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 6 enabled, radio 0 selected, IF 200000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 6 configuration; en:1 freq:200000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa multi-SF channel 7 enabled, radio 0 selected, IF 400000 Hz, 125 kHz bandwidth, SF 7 to 12
lgw_rxif_setconf:607: Note: LoRa 'multi' if_chain 7 configuration; en:1 freq:400000 SF_mask:0x7e
loragw_pkt_logger: INFO: LoRa standard channel enabled, radio 1 selected, IF -200000 Hz, 250000 Hz bandwidth, SF 7
lgw_rxif_setconf:581: Note: LoRa 'std' if_chain 8 configuration; en:1 freq:-200000 bw:2 dr:2
loragw_pkt_logger: INFO: FSK channel enabled, radio 1 selected, IF 300000 Hz, 125000 Hz bandwidth, 50000 bps datarate
lgw_rxif_setconf:637: Note: FSK if_chain 9 configuration; en:1 freq:300000 bw:3 dr:50000 (50000 real dr) sync:0xC194C1
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000000
loragw_pkt_logger: INFO: found local configuration file local_conf.json, trying to parse it
loragw_pkt_logger: INFO: local_conf.json does not contain a JSON object named SX1301_conf
loragw_pkt_logger: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000101
ERROR: FAIL TO CONNECT BOARD
loragw_pkt_logger: ERROR: failed to start the concentrator
Pin assign is failure?

please also open DEBUG_REG
I forgot DEBUG_REG is the actual underlying interaction between SPI and SX1301.

I also got that(DEBUG_REG = 1);
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ ./util_pkt_logger
...
loragw_pkt_logger: INFO: local_conf.json does not contain a JSON object named SX1301_conf
loragw_pkt_logger: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000101
ERROR CONNECTING CONCENTRATOR
ERROR: FAIL TO CONNECT BOARD
loragw_pkt_logger: ERROR: failed to start the concentrator

Did you run ./reset_lgw.sh start before starting the gw?

It seems like connection issue though...

Yes, I run "./reset_lgw.sh start" properly.
Of course, enabled SPI.
pi@ttn-gateway:~/lora_gateway $ ./reset_lgw.sh  start
Accessing concentrator reset pin through GPIO25...
pi@ttn-gateway:~/lora_gateway $ cd util_pkt_logger/
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ ls
Makefile  global_conf.json  inc  local_conf.json  obj  readme.md  src  util_pkt_logger
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ ./util_pkt_logger

Here is GPIO mapping;
pi@ttn-gateway:~ $ gpio readall
+-----+-----+---------+------+---+---Pi 3B--+---+------+---------+-----+-----+
| BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
|     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
|   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5v      |     |     |
|   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |
|   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT5 | TxD     | 15  | 14  |
|     |     |      0v |      |   |  9 || 10 | 1 | ALT5 | RxD     | 16  | 15  |
|  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |
|  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |
|  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
|     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |
|  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |
|   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
|  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |
|     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
|   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
|   5 |  21 | GPIO.21 |   IN | 0 | 29 || 30 |   |      | 0v      |     |     |
|   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
|  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
|  19 |  24 | GPIO.24 |   IN | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
|  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | IN   | GPIO.28 | 28  | 20  |
|     |     |      0v |      |   | 39 || 40 | 0 | IN   | GPIO.29 | 29  | 21  |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
+-----+-----+---------+------+---+---Pi 3B--+---+------+---------+-----+-----+

Have u checked the NSS pin, is it connected to the right pin!
On Wed, 15 May, 2019, 23:17 tokina (himitu<EMAIL_ADDRESS>wrote:

Here is GPIO mapping;
pi@ttn-gateway:~ $ gpio readall
+-----+-----+---------+------+---+---Pi
3B--+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| | | 3.3v | | | 1 || 2 | | | 5v | | |
| 2 | 8 | SDA.1 | ALT0 | 1 | 3 || 4 | | | 5v | | |
| 3 | 9 | SCL.1 | ALT0 | 1 | 5 || 6 | | | 0v | | |
| 4 | 7 | GPIO. 7 | IN | 1 | 7 || 8 | 1 | ALT5 | TxD | 15 | 14 |
| | | 0v | | | 9 || 10 | 1 | ALT5 | RxD | 16 | 15 |
| 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | 0 | IN | GPIO. 1 | 1 | 18 |
| 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | |
| 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | 0 | IN | GPIO. 4 | 4 | 23 |
| | | 3.3v | | | 17 || 18 | 0 | IN | GPIO. 5 | 5 | 24 |
| 10 | 12 | MOSI | IN | 0 | 19 || 20 | | | 0v | | |
| 9 | 13 | MISO | IN | 0 | 21 || 22 | 0 | IN | GPIO. 6 | 6 | 25 |
| 11 | 14 | SCLK | IN | 0 | 23 || 24 | 1 | IN | CE0 | 10 | 8 |
| | | 0v | | | 25 || 26 | 1 | IN | CE1 | 11 | 7 |
| 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 |
| 5 | 21 | GPIO.21 | IN | 0 | 29 || 30 | | | 0v | | |
| 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 |
| 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | |
| 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 |
| 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 |
| | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+---Pi
3B--+---+------+---------+-----+-----+
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/will127534/LoRa-concentrator/issues/34?email_source=notifications&email_token=AA7OX7Y6NTBU6C36HMT3CNLPVREEJA5CNFSM4HNFLEMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVPNSUY#issuecomment-492755283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7OX737FWST646QF7QGSFDPVREEJANCNFSM4HNFLEMA
.

Is your local_conf.json file correct, because I don't see Ur device
connection to any lora backed server and still working with
global_conf.jskn file.
On Wed, 15 May, 2019, 22:48 tokina (himitu<EMAIL_ADDRESS>wrote:

I have an error similar to that; #33
https://github.com/will127534/LoRa-concentrator/issues/33
I have Version 3 of LoRa Concentrator, this is so good Gateway for using
LoRaWAN with TheThingsNetwork for PoC.
I examined this on RPi3(Latest Raspbian Desktop), however it doesn't run
successfully.
We can found this wiki;
https://github.com/will127534/LoRa-concentrator/wiki/Startup-Guide
I got below error at first step(2.5A supplied);
pi@ttn-gateway:~/lora_gateway/util_pkt_logger $ sudo ./util_pkt_logger
loragw_pkt_logger: INFO: found global configuration file global_conf.json,
trying to parse it
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named
SX1301_conf, parsing SX1301 parameters
loragw_pkt_logger: INFO: lorawan_public 1, clksrc 1
loragw_pkt_logger: INFO: radio 0 enabled (type SX1257), center frequency
915000000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
loragw_pkt_logger: INFO: radio 1 enabled (type SX1257), center frequency
916500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
loragw_pkt_logger: INFO: LoRa multi-SF channel 0 enabled, radio 1
selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 1 enabled, radio 1
selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 2 enabled, radio 1
selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 3 enabled, radio 0
selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 4 enabled, radio 0
selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 5 enabled, radio 0
selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 6 enabled, radio 0
selected, IF 200000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa multi-SF channel 7 enabled, radio 0
selected, IF 400000 Hz, 125 kHz bandwidth, SF 7 to 12
loragw_pkt_logger: INFO: LoRa standard channel enabled, radio 1 selected,
IF -200000 Hz, 250000 Hz bandwidth, SF 7
loragw_pkt_logger: INFO: FSK channel enabled, radio 1 selected, IF 300000
Hz, 125000 Hz bandwidth, 50000 bps datarate
loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named
gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to
AA555A0000000000
loragw_pkt_logger: INFO: found local configuration file local_conf.json,
trying to parse it
loragw_pkt_logger: INFO: local_conf.json does not contain a JSON object
named SX1301_conf
loragw_pkt_logger: INFO: local_conf.json does contain a JSON object named
gateway_conf, parsing gateway parameters
loragw_pkt_logger: INFO: gateway MAC address is configured to
AA555A0000000101
loragw_pkt_logger: ERROR: failed to start the concentrator
Who do know or can solve this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/will127534/LoRa-concentrator/issues/34?email_source=notifications&email_token=AA7OX747VPHLBB7NOKMM333PVRAVBA5CNFSM4HNFLEMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GT7LJUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7OX73UETTH65AQ5SPSHVLPVRAVBANCNFSM4HNFLEMA
.

Can you double check the soldering between the board and the pins?

Sorry, I cannot check because I don't have a tester..

It run succesfully with remounting the HAT, thanks.


Unkown File Types

How do I go about adding a file type? I'm dealing with exchanging of Quickbooks Backups (*.QBB && *.QBX)

We can, but how do you validate them? Is there a parser to figure out sane/dangerous files?

As far as my concern goes, the Quickbooks backup is safe because it's opened by the quickbooks program and read to a new file, it's not really opened directly. Obviously there's probably a way to use it to hide malware but for the most part in my experience when a virus gets ahold of it they either break the file by making it malicious (can't be restored from backup, but if you double click it, it runs a program) or it leaves them alone because it's an unkown file type.
I'm trying to prevent clients bringing us unclean USBs that may have autorun malware, or images/executables that aren't intended for us but just on their USB (multipurpose USBs). I'm not suggesting this for every environment but I would like to just add the .QBB/.QBX file extension to automatically copy over.
I'm going to talk to quickbooks about their linux applications and see if there's something that doesn't require licensing that can verify the backups.

So your use case is to only allow .QBB/.QBX file extensions, and discard everything else?

I suppose, we don't necessarily want to discard everything else though. Just to at least not mark .QBB/.QBX files to be marked DANGEROUS_MyKittyStore.QBX_DANGEROUS as that scares the bookkeepers.

Makes sense. Do you have a sample file I could try to make sure it works properly?

Sure thing. I downloaded a Quickbooks template online and made a backup of it:
https://macemore.net/u/Sample.QBB
Never too careful...
https://www.virustotal.com/#/url/e62d098b0465021f447924e94279277d14bdfd34cc568c6820eff32f4f39aac7/detection


Patch image-builder to fix Goss validations for all EKS-A infra provider image builds

Along with the Goss post-build validations included in upstream image-builder, we also have our own validations which verify some EKS-A specific build changes and configurations.  The inline variables for these Goss validations are passed in only for OVA builds (since they were the only images we were building when the patch was added) but they are being set to empty for other providers which caused incorrect var resolutions and false positive errors such as
File: /var/cache/etcdadm/etcd//etcd--linux-amd64.tar.gz: exists:Expected <bool>: false to equal <bool>: true

This happened because the etcd tarball template is /var/cache/etcdadm/etcd/{{ etcd_version }}/etcd-{{ etcd_version }}-linux-amd64.tar.gz but etcd_version is not passed to the Goss vars list.
This PR fixes this by adding the vars in the AMI, Raw, Cloudstack and Nutanix Packer configs.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Release V1.15.0

Release tracker for V1.15.0
To get a look at where this release is in our internal pipeline look at our Github
project here
Changelog

(#1068)(#1090)(#1079)(#1096)(#1114)(#530)(#1121)(#1122)(#1103) Documentation and example updates
(#1084) Add ssm:GetParametersByPath to SSMParameterReadPolicy
(#1015) Allow setting auth to NONE with AWS_IAM default authorizer
(#1088) Allow references in NotificationARNs property
(#1066) Add cognito event sources
(#1093) Remove extra stage only when OpenApiVersion is set
(#1065) Add SQS option to SNS event
(#1101)(#1113) Add code commit policy templates
(#1105) Use scoped logger instead of root
(#1104) Openapi version type errors
(#1035) Randomize logical IDs of API stage and Lambda permission
(#1120) Add support for aws lambda streaming batch feature
(#1119) Combine test and prod permissions for api events
(#1077) Support for resource policy Iam, Vpc and Ip whitelist/blacklist
(#953) Add request parameters support

Found issue with Resource policy changes in internal QA. This fix is here #1145

Internal QA found Request parameters example does not work as expected. More in this https://github.com/awslabs/serverless-application-model/issues/931#issuecomment-534463087. This example needs to be updated.


Issue 692

Fixes #692

[ ] npm run test succeeds.
[x] npm run lint succeeds.
[x] Appropriate changes to README are included in PR.

@grant
Given the scope of the changes, I have no idea why test fails with node 12.9.0

Can you fix the test?:
Change the assertion to be anything nully.

Could it be because of missing some process.exit(0) perhaps? Odd that tests do run fine with node 8 and 10 but faill with 12

@grant Testing and Chai are not my high point, but I feel fishy this exit code null
would adding something like expect(result.stderr).to.equal('') make sense in your opinion?

If we merge clasp's master to your master before making the PR, the # of commits should be less and the number of Travis runs should be less too.

Is this something I can/should do? Before starting any PR, I:

checkout to my local master
pull from upstream/master and sync
create a new local branch

@grant I found the cause of why the push with no .claspignore test was failing and re-implemented it.

The additional stderr tests are to ensure nothing gets logged on stderr when we expect no error. Added value, if this assertion fails, we get a glimpse at what has been logged on stderr.

We're testing if stderr is '' and not testing if it is different.
Why could we just have all tests expect stderr is clean after the test?

Not sure what you would like the tests to be like. I checked every existing tests and added stderr assertion where it was obvious no error is expected. untouched tests are those which actively check stderr for an error.

Is there some bug that prompted this PR?

#692

Changes as requested. Tests are rather due to fail until quota reset though


Entities from old devices still showing in Home Assistant

Home Assistant release (hass --version): 0.50.2
Python release (python3 --version):
Component/platform: HASS
Description of problem:
Devices which were formally tracked via iOS app and are no longer connected to Home Assistant are still showing up as entities; specifically sensor._battery_level and sensor._battery_state.
Expected:
When a device is no longer using the iOS app and not in known_devices.yaml it should not show up as a sensor in HASS.

I believe the sensor data comes from the .ios.conf file Might be worth renaming the file and letting it be re created.

Ah! Hidden file. That was it. Thank you!


Feature support connection info in route matching

Description: Add the ability to route match based on client credentials.
This is an output of the changes requested for PR #8248 (https://github.com/envoyproxy/envoy/pull/8248#discussion_r327884919)
To more cleanly support #8248 , it would be better to be able to route based on downstream connection details, instead of hoisting more information into headers.
As an API example, route matching based on presented and/or expired client certificate is supported.
The end goal for #8248 is to route based on 'validated'.
By default the routing rules are unchanged.
Risk Level: Medium
Testing: Currently Manual tests
Docs Changes: API proto changes
Release Notes: N/A

Some API comments to start things. Also, have you considered having a filter put this information in dynamic metadata and doing a more generic match on that in the route table? I'm not generally a fan of putting too much business logic for specific cases here unless it's widely interesting.

@htuch My thought on this is consolidating with what RBAC has, we already have huge overlap with there and the properties from the TLS connection will be also interested there. This falls into the goal of consolidating all HttpMatcher in v4.

@lizan yeah, RBAC unification makes sense. Is there an issue and/or roadmap somewhere to provide a north star? Is there anything actionable in this review on that front?

@lizan yeah, RBAC unification makes sense. Is there an issue and/or roadmap somewhere to provide a north star? Is there anything actionable in this review on that front?

Part of #5569, this is the one of big item we've been discussing for v4 and UDPA.


ha-google-home depends on glocaltokens==0.7.1 which depends on ghome-foyer-api==1.0.0 which depends on protobuf>=4.21.12,<5.0.0, but home assistant is starting to ship with a newer protobuf.

The issue is that ha-google-home depends on glocaltokens==0.7.1 which depends on ghome-foyer-api==1.0.0 which, in the end, depends on protobuf>=4.21.12,<5.0.0.
However, HomeAssistant 2024.11 comes with protobuf==5.28.3, it was bumped to 5.x in https://github.com/home-assistant/core/pull/124936 so a new version of ghome-foyer-api supporting protobuf>=5 and a new version of glocaltokens is needed.
For what is worth I've ran the following inside my homeassistant container and so far it is working:
uv pip install glocaltokens==0.7.1  # This will downgrade protobuff to version 4.25.4
uv pip install protobuf==5.28.3  # Bump again to homeassistant provided version

And after a restart, it seems to be working even with protobuf>=5, so maybe is just minor work effort:

Originally posted by @skgsergio in https://github.com/leikoilja/ha-google-home/issues/918#issuecomment-2453581838
Any chance we can get a version of ghome-foyer-api that works with protobuf>=5?

Thanks for the report! I'll try to update the dependencies soon.

Duplicate of #122


Encrypted backup flow with password

Allow a user to store a backup server-side, encrypted with a password. Need to address the issue that a backup size exposes information about a user's collection, namely the number of Jubmojis they have

We can pad the data with fake jubmojis to not reveal any additional data to server. Nice thing about only being able to collect 1 of each


tsParticles Error in log "adding particle"

Contact Details
@Idas86
What do you need?
Using tsParticles.js I run into this error in the logs with Chrome: "error adding particle: Error: Particle is overlapping and can't be placed".
The canvas is generated correctly, as well as the animation of the particles. If it weren't for the logs, everything would seem fine.
This is my code added in Drupal site:
tsParticles.load("tsparticles", {
  fps_limit:

  fullScreen: {
    enable: true,
    zIndex: -1
  },
  background: {
    color: "tansparent"
  },
  interactivity: {
    detect_on: "canvas",
    events: {
      onclick: { enable: false, mode: ["remove", "push"] },
      onhover: {
        enable: false,
        parallax: { enable: true, force: 100, smooth: 120 }
      },
      resize: true
    },
    modes: {
      bubble: { distance: 400, duration: 2, opacity: 0.5, size: 40, speed: 3 },
      grab: { distance: 400, line_linked: { opacity: 0.3 } },
      push: { particles_nb: 4 },
      remove: { particles_nb: 4 },
      repulse: { distance: 200, duration: 0.4 }
    }
  },
  particles: {
    color: { value: "#ffffff" },
    line_linked: {
      color: "#ffffff",
      distance: 230,
      enable: true,
      opacity: 0.1,
      width: 1,
      triangles: {
        enable: true,
        color: "#ffffff",
        opacity: 0.01
      }
    },
    move: {
      attract: { enable: false, rotateX: 600, rotateY: 1200 },
      bounce: false,
      direction: "none",
      enable: true,
      out_mode: "out",
      random: false,
      speed: 0.5,
      straight: false
    },
    collisions: {
      bounce: {
        horizontal: {
          random: {
            enable: false,
            minimumValue: 0.1
          },
          value: 1
        },
        vertical: {
          random: {
            enable: false,
            minimumValue: 0.1
          },
          value: 1
        }
      },
      enable: true,
      mode: "bounce",
      overlap: {
        enable: false,
        retries: 0
      }
    },
    number: {
      value: 300,
      density: {
        enable: true,
        value_area: 1300
      },
      limit: 150
    },
    opacity: {
      anim: { enable: false, opacity_min: 0.1, speed: 1, sync: false },
      random: false,
      value: 0
    },
    shape: {
      type: "cyrcle",
      stroke: { color: "#FFFFFF", width: 0 },
      polygon: { nb_sides: 1 },
    },
    size: {
      anim: { enable: false, size_min: 0.1, speed: 40, sync: false },
      random: false,
      value: 50
    }
  },
  retina_detect: true,
});

Version
1.42.3
Which library are you using?
Vanilla (tsparticles)
Code of Conduct

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

Contact Details
@Idas86
What do you need?
Using tsParticles.js I run into this error in the logs with Chrome: "error adding particle: Error: Particle is overlapping and can't be placed". The canvas is generated correctly, as well as the animation of the particles. If it weren't for the logs, everything would seem fine.
This is my code added in Drupal site:
tsParticles.load("tsparticles", {
  fps_limit:

  fullScreen: {
    enable: true,
    zIndex: -1
  },
  background: {
    color: "tansparent"
  },
  interactivity: {
    detect_on: "canvas",
    events: {
      onclick: { enable: false, mode: ["remove", "push"] },
      onhover: {
        enable: false,
        parallax: { enable: true, force: 100, smooth: 120 }
      },
      resize: true
    },
    modes: {
      bubble: { distance: 400, duration: 2, opacity: 0.5, size: 40, speed: 3 },
      grab: { distance: 400, line_linked: { opacity: 0.3 } },
      push: { particles_nb: 4 },
      remove: { particles_nb: 4 },
      repulse: { distance: 200, duration: 0.4 }
    }
  },
  particles: {
    color: { value: "#ffffff" },
    line_linked: {
      color: "#ffffff",
      distance: 230,
      enable: true,
      opacity: 0.1,
      width: 1,
      triangles: {
        enable: true,
        color: "#ffffff",
        opacity: 0.01
      }
    },
    move: {
      attract: { enable: false, rotateX: 600, rotateY: 1200 },
      bounce: false,
      direction: "none",
      enable: true,
      out_mode: "out",
      random: false,
      speed: 0.5,
      straight: false
    },
    collisions: {
      bounce: {
        horizontal: {
          random: {
            enable: false,
            minimumValue: 0.1
          },
          value: 1
        },
        vertical: {
          random: {
            enable: false,
            minimumValue: 0.1
          },
          value: 1
        }
      },
      enable: true,
      mode: "bounce",
      overlap: {
        enable: false,
        retries: 0
      }
    },
    number: {
      value: 300,
      density: {
        enable: true,
        value_area: 1300
      },
      limit: 150
    },
    opacity: {
      anim: { enable: false, opacity_min: 0.1, speed: 1, sync: false },
      random: false,
      value: 0
    },
    shape: {
      type: "cyrcle",
      stroke: { color: "#FFFFFF", width: 0 },
      polygon: { nb_sides: 1 },
    },
    size: {
      anim: { enable: false, size_min: 0.1, speed: 40, sync: false },
      random: false,
      value: 50
    }
  },
  retina_detect: true,
});

Version
1.42.3
Which library are you using?
Vanilla (tsparticles)
Code of Conduct

[x]  I agree to follow this project's Code of Conduct

Your configuration has collisions enabled, and you can choose if particles can overlap when placing. If there's no space found the particle won't be added and an error in the console is written.
The retries value tries n times to place the particle before throwing the error, but in your config n = 0 so, if the random position is not available the error is thrown immediately.


Added steps to change DNS Servers to use Default (Azure-Provided) DNS…

Added steps to change DNS Servers to use Default (Azure-Provided) DNS server and removed IP address in the nslookup command

#sign-off

@mamccrea: I'm sorry - only the author of this article, @jasonwhowell, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@JasonWHowell - Please sign-off

#sign-off


Color styling problem

Hi,
this is going to be a little controversial: I spend a lot of time while working with Cursive in a very non-effective way trying to get desired coloring of views. Since the styling (like applying effects, using different colors from Palette) is usually determined by the code of View::draw(...) method, I am forced to either create wrappers that modify a theme to each view in separate or fork the entire view and manually modify the drawing method. That obviously increases cost of development and maintenance, especially with complex third party views.
In views I write, I decided to move away from predefined palette, and created something like a "style tree", where I just override colors with html color codes defined in JSON. If other (default, third party etc) views used similar technique, I would be able to achieve required styling very fast, in a way a little similar to CSS.
Would that be something you could consider for Cursive? If you are open to discussion I can make a design draft. I am thinking about something like this: https://github.com/njskalski/sly-editor/blob/master/src/default_settings.rs (theme part) but more streamlined. Like "cascading, json defined themes", that could be deserialized into objects via serde_json, so one can either configure in-code or via json.
I we'd agree on some format, I could help you to update the views, and fork and update some third party views, even help with maintaining.

Hi!
I'm thinking about the best solution for color management.
I think a lot can be solved by using a larger palette - possibly arbitrarily large.
Let's consider an example use-case: I want to use a third-party view likew TreeView while customizing the color it uses for arrows; and I want this color to be different in a special popup I'm sometimes creating.
The TreeView will specify that it uses a specific color from the Palette for arrows - it could be Secondary, or something custom like TreeViewArrows. I'll just need to update this value in my palette to change this color.
Now, to have a different color when the TreeView is in a popup, the popup will need to specify a different TreeViewArrows color. To do this, it might copy over the MyPopupContent.TreeViewArrows value - it might actually copy over any value in MyPopupContent.*, so we can also re-define the background, or other colors.
So a first simple solution would be to allow any string as extra key in the palette.
An example toml configuration would look like:
[colors]
    primary = "black"
    TreeViewArrows = "red"
    "MyPopupContent.TreeViewArrows" = "green"
    "MyPopupContent.background" = "white"

Now, a single large, flat palette of colors like this might work, but is less than ideal to use. There is no clear hierarchy between keys, apart from a common prefix. We could try to use an actual tree:
[colors]
    primary = "black"
    TreeViewArrows = "red"

    [MyPopupContent]
        TreeViewArrows = "green"
        background = "white"

However, it does make the structure a bit more complex: instead of something like a Map<String, Color>, we now have a more free-form structure. It probably doesn't matter so much; we're already parsing the toml  table manually anyway.
The custom part of the Palette itself may end up looking like a tree:
enum PaletteValue {
    Leaf(Color),
    Node(HashMap<String, PaletteValue>),
}

Thank you for long answer, you convinced me in all points. How do we proceed?

The first step is to increase the size of the Palette with a tree of custom keys. This means the Palette may not stay Copy, but I don't think it's a big loss.
The Palette would get a custom entry, with a simple PaletteValue structure described in a post above. We should probably add some Index<&str> implementation to make it easy to go down the tree.
Then, we should add a wrapper view that transforms the theme of the drawer when given to the child. The idea is to make it very easy to merge a sub-tree from the theme into the root node.

Ok, how about this? #256 If it's bad, tell me what to change, if it's ok, what next? Loading? Tests?

I also need something like this.
I have various projects like this one which were implemented using Python and urwid and, while urwid has its advantages, it's a poster child for what happens when duck typing goes wrong. (It's expression of a type error is some horrendously cryptic message, a dozen layers deep in the stack trace, about not being able to unpack a tuple because it has the wrong number of elements)
As you can see from the screenshot on that page, I have a decent sense of design. The problem is that Cursive doesn't appear to support producing that layout without custom code hackery while, if I had more versatile theming, I could just say "Yes, I know this is a one-line TextView, but use the theming for headers and footers" and so on.
(And I'm stubborn enough about producing exactly the user experience I want that, if I have to choose between compromising on appearance and suffering urwid's lack of a type system, I'll continue to suffer with urwid.)


Captured image have wrong orientation on Samsung S5

It seems that param orientation doesn't work at all on the Samsung S5 device. Whatever orientation value is passed to native, it doesn't work. The image is always in same, wrong orientation.
Steps to reproduce

Capture image with Samsung S5

Expected behaviour
Go to the recent/gallery and you will see that image have wrong orientation ( to the left)
Actual behaviour
An image should be saved as it's captured, in portrait mode.
Environment

React Native version: 0.30
React Native platform + platform version: Android 5.0

react-native-camera
Version: 0.3.8

experiencing the same thing on ios sim/iphone.

Thank you for reporting.
I'll close this issue since it's a duplicate of #309.

@markos85  are you able to test my PR?  It may help with this https://github.com/lwansbrough/react-native-camera/pull/682.


Typings / Typescript

HI,
having trouble getting the typings to work.
What version of Typescript is needed for the typings to work? 2.3?
I get
TS2368 TypeScript Type parameter name cannot be 'any'
and
TS2314 TypeScript Generic type requires 10 type argument(s).
and
TS2314 TypeScript Generic type requires 2 type argument(s).
in Visual Studio with typescript tools version 1.8 and 2.3.
Any idea?

Should be closed now?


validates connection present for edge

Sometimes connection is undefined at show/hide Edge functions which creates a crash for 'fg' in next code:
AbstractEdge.prototype = {
    hide: function() {
      this.connection.fg.hide();
      this.connection.bg && this.bg.connection.hide();
    }
};

So I believe it is good idea to check for:
this.connection

Hey, I've rearranged the code quite a lot recently. I'll provide some way to incorporate your proposal (it's quite up on my list)


define a CRD for riff system

Since riff system is made up of a number of components like istio, knative, buildpacks etc and components around eventing planned, we should define a CRD which will help tying these components together. This CRD will be leveraged to install/uninstall/upgrade the riff system.
apiGroup: "projectriff.io/v1alpha1"
kind: Manifest
metadata:
  name: riff, riff-namespace, in-memory-channel, kafka-channel, container-source
spec:
    dependencies:
    - istio
    images:
    - projectriff/correlator:s1p2018
    - ....
    resources:
    - path: https://example.com/foo.yaml
      content: | # inlined path
      hash: deadbeef1234
      checks:
      - apiGroup: v1
        kind: Pod
        namespace: knative-serving
        name:# using a label selector instead
        labelSelector: app=controller
        jsonPath: '...'
        pattern: ;Ready=True;
    - # second resource set

Once we have an object like this, we could guide the install by iterating over all resources and checking  the status of the resource before deploying the next resource. In the case of a repeat install due to a previous install failure, we can quickly do statusCheck of the resource and continue from the failure point.
Thanks @scothis for your valuable inputs in defining the structure of the CRD/object!

What are the semantics, if any, of the metdata names?

done in https://github.com/projectriff/cnab-k8s-installer-base


Suggestion about Material Theme Darker

Hello, let me say that your theme is awesome, is one of the best themes I have ever tried.
In the darker version I found the comments color too dark, and compared to the background color I found very hard to read comments in my code.
May I suggest you a change of color?
best regards
Stefano

You can edit your local Material-Theme-Darker.tmTheme by browsing extensions. Make note that every changes will be lost when you update the extension. At the moment no color scheme changes are planned. Thank you and enjoy :)


Add a spy on m to localize class names?

It may be nice to have
var mx = mithrilJ2c.spy(m, j2c)
mx('.foo.', 'hello') //
hello

What do you think?

+1

where do you put the definitions than?


fix: remove preemptionPolicy when priority class name is used

Fixes #1233
Starting at kubernetes 1.19, a PriorityClass can now define a
PreemptionPolicy. By default a pod will have a PreemptionPolicy set to
PreemptLowerPriority.
If the PriorityClass defines a different PreemptionPolicy, there will be
a conflict, so the patcher has to remove the PreemptionPolicy on the
pod. By default a PriorityClass will have a PreemptionPolicy set to
PreemptLowerPriority too, so it's safe to always remove it from the pod
when the priorityClassName is specified for the sparkapplication.

Thanks for the PR.


USHIFT-624: Adjust MicroShift minimal system requirements to better reflect the current resource usage

Closes USHIFT-624

/lgtm


Property sheets with specified file extension

Property sheets don't work when specifying a particular file extension.
For example, the sample FileTimesPropertySheet works perfectly with all files, but not for .pdf (or anything more specific than AssociationType.AllFiles).
[ComVisible(true)]
//[COMServerAssociation(AssociationType.AllFiles)]
[COMServerAssociation(AssociationType.FileExtension, ".pdf")]
public class FileTimesPropertySheet : SharpPropertySheet

Using Windows 10, 64bit. Compiled as Any CPU. Installing/Registering with (x64) in ServerManager.
This does not seem to be related to #129. All the SharpShell dlls used are compiled from the current github.
The logs for AssociationType.AllFiles:
Message: SharpShell Diagnostics Initialised. Process ServerManager.
Message: FileTimesPropertySheet: Constructing property sheet.
Message: SharpShell Diagnostics Initialised. Process dllhost.
Message: FileTimesPropertySheet: Constructing property sheet.
Message: FileTimesPropertySheet: Initializing shell extension...
Message: FileTimesPropertySheet: Shell extension initialised.
Parent folder: <none>
Items:
C:\Users\Oliver\Documents\results.pdf
Message: FileTimesPropertySheet: Adding Pages...
Message: Bridge Initialised
Message: Creating property page handle via bridge.
Message: FileTimesPropertySheet: Created Page Proxy, handle is 22b5fc2ddb0
Message: FileTimesPropertySheet: Adding Pages (Done)

The logs when specifying a file extension. These two lines of course appear when opening ServerManager, before even installing/registering the server.
Message: SharpShell Diagnostics Initialised. Process ServerManager.
Message: FileTimesPropertySheet: Constructing property sheet.

Obviously the workaround is to registed for AllFiles and check for the file extension in CanShowSheet().

I have the same issue. Interesting that prior to Windows 10 Fall Creators Update my property sheet worked good with AssociationType.FileExtension, but not worked with AssociationType.ClassOfExtension. Now, after my system has been updated, AssociationType.AllFiles is the only working option.

Maybe this could be related to #126 and #145
@olivercoad can you check that you have a valid registry entry for .pdf with a default value for pdffile (or smth like that?) Or can you check if it happens with .ico, too?

It doesn't seem related to those issues; this issue is about FileExtension, not ClassOfExtension.
From memory .pdf was just an example, it would happen with other file types. It should work with any file type even without a related classname.
Other features like preview handlers worked fine.
Of course this is from just over a year ago, so it might happen to have been fixed with a windows update or work that has been done in the repo since.

@olivercoad Oh funny, I read "October 27" and not the year ;) Didn't notice it beeing the same day last year.
Will try it myself then with FileExtension and ClassOfExtension

Let me know how it goes @Countryen - if we cannot reproduce at this stage it is likely already fixed with recent updates and we'll close the issue. Thanks for the extra info @olivercoad!

Hey there, did some testing, interesting results...
Can't seem to get it to work with any of tested "well known" extensions
[COMServerAssociation(AssociationType.FileExtension, ".pdf")]
[COMServerAssociation(AssociationType.FileExtension, ".txt")]

But following works.
[COMServerAssociation(AssociationType.FileExtension, ".c0pppp")]
Note: I never used/had extension "c0pppp" before, just typed it in to try.

<EMAIL_ADDRESS>Debug Any CPU, VS2017
Windows 10 64 Bit (up to date)

Also, specifying more than 1 is possible (but only "new" extensions are working for me)

Did some more testing with different extensions
pdf, application, xml, pcb, jar, dll, etc.
Only extensions that I create new work for me.
Maybe you try it with a "new one" as well, @olivercoad ?
Checked the registry for any differences but can't find none.
Also checked some, but not all of the Access Rules for the keys - no difference so far.

Fixed by #240


Suggest minor changes to README.md

Made a few minor suggestions and added content about Hygieia's features from https://developer.capitalone.com/opensource-projects/hygieia/.

I had updated that sentence since it seemed a little redundant with the content above and below. What do you think about the following modification instead?
from this:
Capital One DevOps Engineers developed Hygieia after researching existing tools and finding:
to this:
Capital One Engineers from our DevOps team developed Hygieia with the need for a user-friendly, out-of-the-box DevOps visualization tool in mind after researching existing tools and finding:

@593062 Sure..not a problem. Glad to help and thanks for the contribution.

@tabladrum LGTM


Will Visual Studio Code ever support the Acrylic material in the custom title bar?

The Acrylic material is a brush that is part of the Fluent Design language, which I think could make the UI more intuitive and natural. I wonder whether it would ever be supported here.

Oh hell yes and please add to this a full fluent design theme with pure black background

#52707.

this will be closed for the same reasoning as the PR linked above


Next version of GFM

[x] Drop support for compilers < 2.067

[x] Use std.experimental.logger instead of the logger package

[x] Split gfm:math

Put rarely used stuff of gfm:math into gfm:math-extras.This lowers amount of stuff to compile in most cases.
- gfm.math.half
- gfm.math.rational
- gfm.math.wideint
- gfm.math.fixedpoint

[x] Do you prefer column-major or row-major (current)? I've always thought row-major was best but maybe not. => LATER

Now available with "~>4.0" in your favourite package retailer.


BookShelf - Sawyer

[x] I have read the steps to getting a blot

[x] I am submitting art that...

[x] is algorithmically generated (will change each time the program is run)
[x] is drawable on a blot (fits in the work area & doesn't overlap too much)
[x] is original (not copied from somewhere else)
[x] doesn't call Math.random() (See the documentation on randomness)

[ ] Optional, if you used a tutorial or based your art on something else, please include the link here:

[ ] Optional, if you remixed this from something else, mention it here:

This artwork Generates a bookshelf that's full of books. I have a good amount of experience coding but it is all in other languages like C# (making games in Unity) and Java (Writing code for First Robotics). I've never done any generative art before so it was fascinating learning how to make it use randomness for it to be different every time

Just an update, I will be closing this PR. Please create a new PR once you have updated your art! We are doing this due to new management of the PR system.


Html being sanitized from markdown

Hello I ran into and issue using the lastest packages from elderjs.
This is current  package vesions

It seems as though any html from markdown is being removed

Use case is I want to use a html table inside a markdown file

I digged abit deeper and found that if I set  sanitize to false in the markdown plugin it no longer parses out the html
https://github.com/remarkjs/remark-html#optionssanitize
This is the change I made to prevent the html being parsed out from a markdown file.
But Im not too sure if this is a good way to solve this issue.
(Index.js markdown plugin)

@conoroshea1996 Thanks for this. I had been troubleshooting #214 and hadn't realized remarkHtml had changed it's api. Fixed in latest plugins.


"Test framework pytest is not installed. Install?" even though it is installed.

I have a workspace with the following:

valid tests
pytest installed in the configured interpreter
pytest configured in the workspace settings

With the most recent insiders build of the extension I clicked on the "Discover Tests" button in the test explorer.  A window popped up saying Test framework pytest is not installed. Install?  I verified that pytest was indeed really installed for the current interpreter.  Then I looked at the "Python Test Log" Output panel.  It showed that pytest discovery had failed (due to a import errors in my test files).
So when pytest discovery fails, the extension is erroneously acting as though pytest hasn't been installed yet.
Given that pytest discovered most of the tests, I would have expected those tests to show up in the test explorer.  I would also have expected a warning to pop up saying that there was a failure during test discovery (with a button to open the "Python Test Log" panel).

I've marked this as a regression, as I'm sure this wasn't a problem before.

Here's the output fromthe  "Python Test Log" Output panel:
python /home/esnow/.vscode/extensions/ms-python.python-2019.6.18460-dev/pythonFiles/testing_tools/run_adapter.py discover pytest -- -s --cache-clear .

Hint: make sure your test modules/packages have valid Python names.
Traceback:
ModuleNotFoundError: No module named 'tests.test_spam'
_______________ ERROR collecting syntax-error/tests/test_spam.py _______________
ImportError while importing test module '/home/esnow/projects/work/test_projects/testing/syntax-error/tests/test_spam.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
ModuleNotFoundError: No module named 'tests.test_spam'
=============================== warnings summary ===============================
.venv/lib/python3.7/site-packages/_pytest/mark/structures.py:337
  /home/esnow/projects/work/test_projects/testing/.venv/lib/python3.7/site-packages/_pytest/mark/structures.py:337: PytestUnknownMarkWarning: Unknown pytest.mark.spam - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
    PytestUnknownMarkWarning,

-- Docs: https://docs.pytest.org/en/latest/warnings.html
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!
===================== 1 warnings, 2 error in 0.10 seconds ======================

Traceback (most recent call last):
  File "/home/esnow/.vscode/extensions/ms-python.python-2019.6.18460-dev/pythonFiles/testing_tools/run_adapter.py", line 16, in <module>
    main(tool, cmd, subargs, toolargs)
  File "/home/esnow/.vscode/extensions/ms-python.python-2019.6.18460-dev/pythonFiles/testing_tools/adapter/__main__.py", line 90, in main
    parents, result = run(toolargs, **subargs)
  File "/home/esnow/.vscode/extensions/ms-python.python-2019.6.18460-dev/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 35, in discover
    raise Exception('pytest discovery failed (exit code {})'.format(ec))
Exception: pytest discovery failed (exit code 2)

Per @DonJayamanne, this is because the extension looks for "ModuleNotFoundError" (or "ImportError"?) in the output to decide if pytest is installed or not.  Apparently that is to naive.

I'm having the same problem.
Mac OS 10.14.5
VS Code Version 1.35.0 (1.35.0)
My project uses pipenv environment. When VS Code prompts "Test framework pytest is not installed, install?" I answer "Yes". The integrated terminal shows this output:

$ pipenv install pytest --dev
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Installing pytest…
Adding pytest to Pipfile's [dev-packages]…
✔ Installation Succeeded
Installing dependencies from Pipfile.lock (e043b0)…
🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 22/22 — 00:00:02
However, after this I don't see any tests in the panel. I right click the python file in my 'tests' subfolder and choose "Debug all tests". A dialog pops up and informs me that "There was an error in running the tests" and this output shows up in the Output window:
Test Discovery failed:
Error: spawn /Users/xxxxx/.local/share/virtualenvs/artifact-AWruN-gO/bin/python ENOENT
Test Discovery failed:
Error: spawn /Users/xxxxx/.local/share/virtualenvs/artifact-AWruN-gO/bin/python ENOENT
...[repeated about 8 times]
If I go to "Python: Discover Unit tests" it tells me again that "Test framework pytest is not installed, install?".
I'd be happy to provide more information if needed. Please escalate the priority of this bug, it prevents us from running Python tests. Thanks!

@ftrofin Please could you create a separate issue for the one you're facing.
Slightly similar, but the cause is different.

I don't understand why you think it's not the same issue. It's the same behaviour: repeatedly asking to install pytest although it is already installed. I merely tried to give you more context to help you debug it.

I don't understand why you think it's not the same issue.

In @ericsnowcurrently 	case the cause is an error ModuleNotFoundError: No module named 'tests.test_spam' is dispalyed and that's causing the message to be displayed. This is a known issue and exists today.
In your case, the extension is unable to spawn the python process. Error: spawn /Users/xxxxx/.local/share/virtualenvs/artifact-AWruN-gO/bin/python ENOENT
Hope you understand why they are different reasons. Again, behavior may be the same, but the cause is completely different and its easier to manage the issues separately else it gets too confusing when we end up discussing different things..

I confirm ericsnowcurrently's diagnosis. I wasted full working day installing-reinstalling-purging-installing again pytest, python, conda, vscode... I just had bad luck in that my test was failing because of the missing module...
Please note, that my "bad luck" is actually a very probable scenario caused by another usability problem: when you write a unit test in pytest, just importing the module you want to test with import tobetested at the beginning of the test file does not work, and triggers the ModuleNotFoundError: No module named 'tobetested'error... then you are bombarded with the apparent problem with the pytest installation...

Prescribed Solution

Check whether the module is not installed before displaying the message (rather than parsing stdout)

Today we parse stdout and look for module not found and display the message

I've verified that the extension no longer says pytest isn't installed (even though it is).  The text in "Python Test Log" output panel did not change (as expected).


Problem on buttons.pug

Hi,
There is a problem on buttons.pug in components, when you specify the caption for submit-primary,
like this
+submit-primary("CREATE")
you have the value equal to #{caption} and the class equal to btn-#{type}.
I tried to replace the code (line 135) :
input.btn(class="btn-#{type}",type="submit",value="#{caption}")
by
input.btn(class="btn-" + type,type="submit",value=caption)
and now it works fine.
it the same thing on line 115 in the same file
cheers
Fabrice

Thanks for raising this and sorry for the late response - I've been on holiday. would you be able to make a PR for this with your fix in it? No worries if you can't - just let me know either way.

Actually - it was pretty quick so I fixed it in cd42b5a3d0ab0a17aa0eec98df96ea0df03d96a8


Update README.md

Hello!
Could you please add Umappp to your user list?

Yeah, thanks @kojix2!

Thanks!


Added documentation about installing Camel K on Kind

Documentation about installing Camel K on Kind

Release Note
NONE

This solves #1468


Binaries as FastCGI parameters

Let's say I want to pass {"NAME", <<"VALUE">>} to the FastCGI server:
out(Arg) ->
	yaws_cgi:call_fcgi_responder(
		Arg,
		[
			{app_server_host, my_app:conf(fcgi_host)},
			{app_server_port, my_app:conf(fcgi_port)},
			{extra_env, [
				{"NAME", <<"VALUE">>}
			]}
		]
	).

My little patch handles it.
Interestingly, this also fixed unicode issue with non-ASCII urls. For example, when I tried to reach <IP_ADDRESS>:1806/ёжик server stopped responding. Now it works like a charm.

Do all tests still pass, and are any new tests needed for this? Does any documentation need to change?

Yes. Everything looks good.
As you can see, the changes are tiny and they don't affect existing API or documentation.

The change is bigger than you think. Your example shows use of extra_env, which is mentioned in the yaws_api.5 man page (and in fact is documented incorrectly there), and another part of the code in yaws_cgi.erl uses extra_env as well.
Also, the way you indented the revised if expressions doesn't match the rest of Yaws code. We use the emacs erlang-mode indentation style.
I've pulled your branch to my clone, have fixed the man page and the indentation, and will check to see if we already have tests that cover these changes.

Your change works for FCGI because it all eventually gets sent over TCP, and gen_tcp doesn't care if you send lists or binaries. But looking more carefully at the code in yaws_cgi.erl, we see that in the cgi_worker/7 function an extra_env is used to build an env for the erlang:open_port/2 function. The documentation for that function specifies that that env is [{Name :: string(), Val :: string() | false}]; Val here is clearly not allowed to be a binary. Changing the Yaws documentation to allow a binary in extra_env values means this code has to be modified as well to change any such binaries to lists before passing them to open_port/2. I'll make this change in my clone.

I pushed a modified commit to master. Thanks for contributing this.

Thank you, @vinoski.


Document that default git symbol requires Powerline patched font

Currently as far as I can see there is no mention that the default git symbol requires a Powerline patched font to render. This should definitely be documented somewhere. I only figured it out because I saw you were using Fira Code in another issue after a lot of searching 😆

See the relevant discussion at https://github.com/denysdovhan/spaceship-zsh-theme/pull/78#discussion_r115125008.

Yeah, seems like we should add note about it and link to this discussion to docs.


blocking receive

currently receive tries to fetch every x seconds which is not ideal

a possible solution is to use keyspace events: https://medium.com/nerd-for-tech/redis-getting-notified-when-a-key-is-expired-or-changed-ca3e1f1c7f0a


TMX with utf-16le encoding considered invalid

Hi,
I have never been able to use tmx files for creating engines or importing new data. After a lot of trial and error, today I managed to import data after converting the TMX file to utf-8.
These were standard tmx exports from memoQ, encoded in utf-16LE (which is legal according to the TMX specs, AFAIK).
The error message in node.log gave me a clue on where to look (copied below).
Is this by design, or is there some other issue which may also be causing it?
Perhaps a note in the relevant part of the wiki would be useful, if this is indeed the case.
Gary
Error message (from node.log):
Invalid TMX ES.tmx
at eu.modernmt.model.corpus.impl.tmx.TMXLineReader.read(TMXLineReader.java:56)
at eu.modernmt.cluster.kafka.KafkaDataManager.upload(KafkaDataManager.java:203)
... 28 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2]
Message: The markup in the document preceding the root element must be well-formed.

Just an idea : it sounds like a problem while reading the BOM bytes.

Hello @gdaine,
Thank you for trying ModernMT :)
As you pointed out, by design ModernMT requires data to be UTF-8 encoded.
I'm sorry this information was not included in the documentation.
I have promptly added it in the engine creation page and I have also added a new related question in the FAQ page.
Thank you for your support!
Best,
Andrea

Thanks for the clarification (and the documentation update).
And congratulations on an amazing program!

I'm glad you appreciate MMT :)
Since this issue was cleared I'm going to close it now.
For any problem or further doubt, however, don't hesitate to reopen it.
Have a nice day!
Andrea


KAFKA-12969: Add broker level config synonyms for topic level tiered storage configs

Topic -> Broker Synonym

local.retention.bytes -> log.local.retention.bytes
local.retention.ms -> log.local.retention.ms

We cannot add synonym for remote.storage.enable topic level config as it depends on KIP-950
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

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

@satishd @divijvaidya @showuon
PTAL when you get chance!

@kamalcph , there's compilation error, could you take a look?
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-14114/8/pipeline

Thanks! Let's wait for the CI build.

A few unrelated tests failed in Jenkins jobs, merging it to trunk.


B4

Baker ID: 776
Account Address: 3qpEJfXSH18NCV9zoXxC3x2c9x91uc9dVnTFsd8J5Ud3eirJ3M
Observations: My baker id has changed after when I stopped and restarted. Previous Transaction ID has gone. Baking confirming randomly, sometimes takes hours, sometimes takes minutes.

confirmed:B4
address:3qpEJfXSH18NCV9zoXxC3x2c9x91uc9dVnTFsd8J5Ud3eirJ3M
baker:232

confirmed:B4
address:3qpEJfXSH18NCV9zoXxC3x2c9x91uc9dVnTFsd8J5Ud3eirJ3M
baker:232

Form Submitted
Friday, April 22, 2022, 02:57
Time zone in Istanbul (GMT+3)


Adding an abstraction layer for VS2015 and VS2017 tools and .json and .csproj projects.

This PR adds two abstraction layers to the extension which allows us to isolate the deployment code from the differences in the underlying project systems employed by VS 2015 and VS 2017.
Host abstraction layer.
The first layer is the host abstraction layer. This layer provides functionality that varies depending on the version of VS that is hosting the extension. Currently the only service offered by this layer is the IToolsPathProvider interface. This interface provides the paths to the tools used by the deployment classes to build and deploy the apps to Windows VMs, App Engine and GKE.
This layer is composed of two namespaces, HostAbstraction.VS14 and HostAbstraction.VS15. Each namespace contains implementations for the host abstraction interfaces, now only IToolsPathProvider. There's a common class called HostAbstractionLayer which takes care of detecting the version of VS that is hosting the extension and returning the right implementation of the common interfaces.
Project abstraction layer
The project abstraction layer allows the deployment modules to accept project instances without having to care for the specifics for the project, whether it is a project.json or a .csproj project, for example.
There two namespaces, Projects.Net4 and Projects.NetCore which contain the project implementation for each supported runtime. Under those there are the various types of projects supported. CsprojProject and JsonProject, which represent the support for the .csproj and project.json projects.
There's a common class, ProjectParser which takes care of opening the project file and determining what kind of project it is. It will then create the right instance of project to manage that project.
With this layer the deployment code does not have to care about the particulars of each project.
Review details
The review contains 30 files, but most of the changes are actually just renaming of classes and moving files around. The main meat of the review is in the common classes, HostAbstractionLayer and ProjectParser.

PTAL

Will look at the class name changes, I will not however use a Java-ism in the code :).

PTAL

Thank you, once the appveyor build finishes I'll merge the PR.


[Mobile UI bug] Org Account drop-down causes page to stretch up to the limits of the screen

The Issue
If user edits organisation's type or industry:
Depending on the length of the option chosen, drop-down width is adjusted, causing the entire screen to be stretched beyond the space it should be within, and therefore length of divider lines and button's padding are stretched out and left-aligned elements are placed in the limit of the screen.
Steps to reproduce
On mobile, go to organisation's account information.
Choose a long length option on the drop-down menus.
Short option

Long option

It'd be great if we can fix this behaviour, and also we could have the drop-downs be a bit longer (within the limits of alignments) so longer options can be read a bit better.
Note this isn't a problem when creating the account, only when editing the settings.

Verified in STG on mobile, its working fine in both create and edit ORG page, refer below screenshot:


AppVeyor doesn't know how to build Vulkan

Therefore all PRs against dev are currently failing, eg https://ci.appveyor.com/project/bjornbytes/lovr/builds/43991150 for #556

Previously I've tried installing the Vulkan SDK in the appveyor script, but it timed out.  Since LÖVR only uses the headers, maybe KhronosGroup/Vulkan-Headers could be cloned instead (and CMake could be tricked into using that, or there could be an option to specify the Vulkan include path instead of using FindVulkan).  For glslangValidator, the standalone binary could be built from deps/glslang.  This would mean building glslang twice -- once for lovr and once for the standalone exe, unless CMake enables ENABLE_GLSLANG_BINARIES.

appveyor can build the dev branch now.

Cool


Add Chainsaw cut duration...

Hello @Timmeey86, it's possible add the option as a title mentioned inside this mod? I know the Lumberjack's mod have this, but i would use your mod... In this case, this mod has more realistic 👍🏻

Hi, I won't integrate features of other existing mods into my mod (unless I don't know about the other mod, of course).
Lumberjack has many settings so you could set it up to just have a different cut duration, but disable super strength etc.
Both mods are compatible with one another

Hi, ah ok it's compatible both in same time?
Il Mar 8 Ott 2024, 14:59 Timmeey86 @.***> ha scritto:

Hi, I won't integrate features of other existing mods into my mod (unless
I don't know about the other mod, of course).
Lumberjack has many settings so you could set it up to just have a
different cut duration, but disable super strength etc.
Both mods are compatible with one another
—
Reply to this email directly, view it on GitHub
https://github.com/Timmeey86/FS22_ForestryHelper/issues/24#issuecomment-2399780494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A27M5Q2CWYSSQO5G4OF2QWLZ2PJMJAVCNFSM6AAAAABPQW4DRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZG44DANBZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, they do different things so they can be used together


.neighborhood method in C++ BQMs should be const

Right now it's possible to modify only the upper or lower triangle bias in the adjacency via the .neighborhood method. That method should be const.
Blocking this:
https://github.com/dwavesystems/dimod/blob/2b5a6eafda89571f376227e759348f7e2733cd9a/dimod/bqm/shapeablebqm.pyx.src#L522
https://github.com/dwavesystems/dimod/blob/2b5a6eafda89571f376227e759348f7e2733cd9a/dimod/bqm/adjarraybqm.pyx#L308

Closed by #818


bug: doubling input

Something wrong with keyboard input as all entered digits are doubling.
How to reproduce:

Lunch the phone
Enter the phone number using the dialpad or keyboard
Clear the input
Enter the digit using the keyboard

Here i entered 1234, the result is below:

solved


Packaging request: fcitx5-skk

Project description
fcitx5-skk is an input method engine for Fcitx5, which uses libskk as its backend.
It seems some of the fcitx5 engines (including fcitx5-skk) are missing. Probably the other engines also need to be added.
Metadata

homepage URL:　https://github.com/fcitx/fcitx5-skk
source URL:　https://github.com/fcitx/fcitx5-skk
license: gpl3+
platforms: linux

PR is wellcome.
What is ENABLE_QT for? Is it involved in fcitx5-qt?


feat: add scanner for Spring HTTP endpoints

Description
Adds a scanner to find all Spring HTTP endpoints annotated with GetMapping, PostMapping, PatchMapping, PutMapping, DeleteMapping and RequestMapping.
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ActiveRecord::Result break AwesomePrint formatter.

Hello!
When an ActiveRecord::Result is returned, AwesomePrint break. For example:
ap ActiveRecord::Base.connection.exec_query('SELECT id, title, body FROM posts')

will result in:
NoMethodError: undefined method `keys' for #<Array:0x007ffb0b7dee30>
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/formatter.rb:103:in `awesome_hash'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/formatter.rb:67:in `awesome_self'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/formatter.rb:28:in `format'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/inspector.rb:137:in `unnested'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/inspector.rb:104:in `awesome'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/core_ext/kernel.rb:10:in `ai'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/core_ext/kernel.rb:20:in `ap'
	from /Users/louim/.gem/ruby/2.2.3/gems/awesome_print-1.6.1/lib/awesome_print/inspector.rb:31:in `output_value'
	from /Users/louim/.gem/ruby/2.2.3/gems/railties-4.2.4/lib/rails/commands/console.rb:110:in `start'
	from /Users/louim/.gem/ruby/2.2.3/gems/railties-4.2.4/lib/rails/commands/console.rb:9:in `start'
	from /Users/louim/.gem/ruby/2.2.3/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:68:in `console'
	from /Users/louim/.gem/ruby/2.2.3/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
	from /Users/louim/.gem/ruby/2.2.3/gems/railties-4.2.4/lib/rails/commands.rb:17:in `<top (required)>'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `require'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `block in require'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:in `load_dependency'
... 2 levels...
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `load'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `block in load'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:in `load_dependency'
	from /Users/louim/.gem/ruby/2.2.3/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `load'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/commands/rails.rb:6:in `call'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/command_wrapper.rb:38:in `call'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:183:in `block in serve'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:156:in `fork'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:156:in `serve'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:131:in `block in run'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:125:in `loop'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application.rb:125:in `run'
	from /Users/louim/.gem/ruby/2.2.3/gems/spring-1.4.4/lib/spring/application/boot.rb:18:in `<top (required)>'
	from /Users/louim/.rubies/ruby-2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Users/louim/.rubies/ruby-2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'

I just came across this as well. Workaround is to not let the console inspect it:
> result = ActiveRecord::Base.connection.select_all("select * from users limit 1;"); nil
nil
> puts result.inspect # manually inspect it

Traced this to ActiveRecord::Result#to_hash, which returns an array of hashes.
Suggestions:

Check object.respond_to?(:to_ary) first, and handle Array.try_convert(object) as an array.

AwesomePrint::Formatter#awesome_self can call Hash.try_convert(object) (which calls #to_hash rather than calling object.to_hash directly. This way, a more meaningful TypeError is returned:

Hash.try_convert(ActiveRecord::Base.connection.select_all("select * from users limit 1;"))
TypeError: can't convert ActiveRecord::Result to Hash (ActiveRecord::Result#to_hash gives Array)

Aside from that, I've submitted a post to the Rails core mailing list about the issue (post to be approved) with the following:

==ActiveRecord::Result#to_hash doesn't return a hash==

ActiveRecord::Result#to_hash

It's unexpected for #to_hash to not return a hash, e.g. AwesomePrint checks and uses #to_hash to inspect hash-convertible objects, as noted in an AwesomePrint issue.
Ruby core even expects Hash from #to_hash:
Hash.try_convert(ActiveRecord::Base.connection.select_all("select * from users limit 1;"))
TypeError: can't convert ActiveRecord::Result to Hash (ActiveRecord::Result#to_hash gives Array)
#to_ary already exists, meaning users of ActiveRecord::Result#to_hash should really be using ActiveRecord::Result#to_a

@Kache Thanks for following up, hadn't had the time to dig in myself. :+1:

It is actually already fixed in master by 4ee2ade5f72677e2afd92033e6f0d4c244a8e43d

Nice!

@gerrywastaken I think this is resolved. Wdyt?

Just tested it on the AP v1.7.0 release using Rails 5 RC1 and it is working for me.
@waldyr feel free to close.
@louim or anybody else, if this is still not working then please tag myself and @waldyr in any comments you post here.

I'm going to mark this as resolved. If anybody else find it not working a version upgrade will fix it.


vm boot-diagnostics get-boot-log should not write to stdout directly

Current implementation of get_boot_log(resource_group_name, vm_name) writes directly into stdout, while other methods use file parameter of main() which can be redirected into any other stream:
command_modules/azure-cli-vm/azure/cli/command_modules/vm/custom.py:498
     #our streamwriter not seekable, so no parallel.
     storage_client.get_blob_to_stream(container, blob, StreamWriter(sys.stdout), max_connections=1)

@yugangw-msft @williexu any thoughts on this issue? not sure if the CLI even supports specifying what file stream to write directly to. I imagine a user can simply redirect the output to a file using output redirection.
Should I close this?

Agreed to close. We can re-open it when we have more votes
For now, redirecting from stdout would be the reasonable approach to consume the log in the command shell


Make ObjC work correctly when receiving a compressed message

See node's fix #6719.

@jcanizales - Where is the corresponding functionality implemented in ObjC? I don't see how this fix maps in ObjC.


Requests made when a JWT token expires always fail (Supabase v2)

Bug report
Describe the bug
Making a request right when a JWT token expires results in a 400: JWT expired error on React Native iOS. This only happens exactly as the token is expiring, and subsequent requests seem to work.
I think this might also be causing the random logging out issues as well.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Set the JWT expiry timeout to 5 seconds
Make a request as the JWT token expires (every 5 seconds)
See JWT expired error message

NOTE: making a second request after getting the JWT expired error later results in that second request working.
Expected behavior
I would expect the token to be refreshed before making the request and the request to work fine.
Screenshots

System information

OS: macOS
Browser: React native iOS
Version of supabase-js: ^2.0.0
Version of Node.js: v16.13.1

Additional context

Good question: curious about this too

Hey we're tracking this issue internally. We did some changes to the way expiration is handled in v2 (i.e. removed a safety margin that was previously there). But I think it's time to bring it back now, as it clearly is not behaving as well as we hoped. I'll submit a PR right now.

@hf okay thanks! When you submit the PR, could you please link it here? Would love to test it and give feedback (and maybe switch to the PR branch if it fixes it).
For context, this is causing data loss for our users where they make an action on the app and don't see it reflected once they refresh/reopen/etc

This is the PR (that was contributed by another member of the community a few days ago). https://github.com/supabase/gotrue-js/pull/482

If you could leave your review on it that would be great since it's going to take at least one day before we can deploy a fix to this.

Hey @alexreyes, just sanity checking -- you're setting the JWT expiry to 5 seconds only to test this behavior right? We don't recommend setting an expiry time of less than 2-3 minutes on it, except for testing purposes like this.

Yup, it’s just for testing. Normally I set the expiry to 1 hour
On Fri, Oct 14, 2022 at 12:22 PM Stojan Dimitrovski <
@.***> wrote:

Hey @alexreyes https://github.com/alexreyes, just sanity checking --
you're setting the JWT expiry to 5 seconds only to test this behavior
right? We don't recommend setting an expiry time of less than 2-3 minutes
on it, except for testing purposes like this.
—
Reply to this email directly, view it on GitHub
https://github.com/supabase/gotrue-js/issues/487#issuecomment-1279374263,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVRBXOYXTIYYFF5TLSFYRTWDGXGZANCNFSM6AAAAAARERAIDM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@hf I tried it, and I still had the same problem of the request failing because of JWT expiry when using the changes linked in the PR. Do you have any other ideas what might be causing this?

I ended up figuring out why this bug was happening! Turns out, it had nothing to do with Supabase and instead was due to the way react renders things.
The situation:
I am updating the JWT token in a useEffect() in the context file for my project. There are times when the JWT token updates in the context, and this updated token isn't being passed down and reflected in the child component where the API request is made.
The solution:
I use await supabase.auth.getSession(); to retrieve the JWT token before making API calls instead of getting the session from the context

@hf Actually, https://github.com/supabase/gotrue-js/pull/482 did partly fix the issue. I just tried the same thing without the contents of that PR, and I got the JWT expired error.
So the PR changes are needed to fix this issue

That's reassuring because we were discussing about finding some time to squeeze a refactor of the auto refresh code. 😅


Improve pageant process handling

Don't wait indefinitely for pageant (given that it's a service-like process that adds a tray icon and waits for input), and don't error when there are already 2 pageant processes.
Hanging bug
This is the old behaviour I observed (that I believe f28bb54 removes):
Start state:

I am on Windows 10 with pageant 0.63 running. GitUtils runs as part of my powershell profile.
I start powershell.exe and run $env:GIT_SSH = "plink"
I kill any pageant.exe that is running

Repro:

I run  Start-Process powershell.exe which creates a new powershell window,  starts pageant, then hangs forever (waiting for it to return).
I close the hanging powershell window, pageant stays running
I run  Start-Process powershell.exe in my original powershell window which starts fine since pageant is already running

Multiple-pageant bug
When using GitExtensions on my machine I end up with two pageant processes (one is created by ShimGen), 99021d4 fixes the powershell error thrown in Start-SshAgent due to having an array returned. Stop-SshAgent also uses this, so should work with multiple pageant processes, but you need to call Stop-SshAgent once for each running SshAgent process which could be better, but is an improvement over doing nothing and erroring.

Do we actually end up waiting for pageant? It always returns immediately for me, even if it's asking for a key to be unlocked. Some quick testing timing the options for launching pageant looks like there's not much difference.

Is the waiting indefinitely an artifact of the instance already running?

I don't think makes a difference, since an existing process would have caused Start-SshAgent to exit by then. Attempting to launch pageant while it's already running manually (without specifying a key to add) causes it to immediately return as normal, but with a "Pageant is already running" alert.

This is the behaviour I observe on Windows 10 with pageant 0.63 starting with no pageant.exe process is running:

I start powershell.exe and run $env:GIT_SSH = "plink"
I run  Start-Process powershell.exe which creates a new powershell window,  starts pageant, then hangs forever waiting for it to return.
I close the hanging powershell window, pageant stays running
I run  Start-Process powershell.exe in my original powershell window
powershell.exe starts fine since pageant is already running

I'm not a Pageant user, so I'll defer to whatever you come up with. I don't see a down-side to switching from & to Start-Process.

The only downside I can think of is that it wouldn't work in Powershell 2.0 and below. The readme says 2.0 is deprecated, does that mean this is fine? Powershell 3.0 did come out 3 years ago...

No downsides and fixes issues, let's get this merged.

:100:


[WIP] Migrate internal tests to new API

It refactors the current tests for the new Ember Engines Testing API #653
The purpose of #653 was to create an API for ember engines that gives our audience the same approach to test engines as it has for normal ember apps and add-ons without preloadAssests and engineResolveFor. I discovered an issue when we tried to import some files not found by this.engine.lookup() for example import Initializer from 'ember-blog/initializers/ember-blog-initializer'; at this line
I've tried the usage of importSync from embroider into the test suite to load these files on-demand but it didn't work for initializers, given the engine is booted during the setupEngine() calling. That being said we still need some work to make the new API consistent with the Ember guides where we can import any files from the app/addon into the test files.

cc @SergeAstapov @void-mAlex @chriskrycho

preloadAssets and setupEngine are actually both very bad as they rely on asset manifest which is not compatible with the future of ember and es modules in general
instead of this we really need to deprecate both approaches immediately

I kindly disagree because It's not true, setupEngine is way better than preloadAssets and closer to the ember-engines in real life, loading engines on demand. You're worrying about the implementation instead of thinking about our users and how painful it's been for many years. I'd love to discuss it with you, @SergeAstapov, and anyone else interested, I'm pretty sure you're missing some gaps about what Ember Engines in the Ember ecosystem @void-mAlex.
I think everyone here knows the ember-asset-loader will be deprecated in favor of embroider (I might be one of the person that most want to see it), but erasing the whole RFC as you're doing is not the best thing to do here, please remember we have an RFC and we still rely on it until a new ember engines/micro frontend comes up. 🙏

I'm blocking this pr as it would fail CI and it's the current changes are the wrong thing to do even if you want to move to the new testing api
steps would be

make the engines have a proper structure as one would expect to see an engine following the guides to set one up
move the preload assets to setupEngine with the macros in place similar to what the current test-helper does to preload assets so we can have clean CI
implement and switch to a setupEngine provided by embroider to make testing engines possible under those scenarios as well (keep macro config for backwards compatibility tests)

that is the direction this pr needs to take, but most likely need to land step one in separate smaller prs that are more manageable

@void-mAlex thanks for the response. Bringing clarity to this conversation the setupEngine is an official helper merged and approved by the core team into this addon, so the tests were passing and we were using this official test helper to modernize the code. That being said I don't see any reason to block this PR, what you are saying is 100% out of the scope of this PR proposal.

@villander resolve the conflict and you will see what I'm talking about with failing tests
second it's very related to this pr as those tests are in the wrong place. even if you stretch the intent of the tests engines have never been meant to work in a v1 addon which is where they are working from now. all that we are testing now is that that engines 'work' in a place where they are not supposed to ever be used. Add on top of that, that the things being tested are not even able to be considered ember projects let alone engines there is no reason to move forward with something that doesn't address the underlying problem and just makes more code that needs to be cleaned up.

@void-mAlex we still need to make the tests modernized and don't load everything once, we need the ability of test engines as they perform in real life. You're not proposing any changes here to keep the Testing user story getting better.

@villander @void-mAlex I think there is miscommunication in this tread.
Me and @void-mAlex had a discussion about this and using setupEngine() test helper for is not a problem per se.
The problem is that setupEngine() under the hood uses asset loader which is not supported under Embroider.
Once we figure out how we could load and instantiate engine using Embroider router or Embroider provided tools under the hood - we should be good.
With above, public API of setupEngine() should not change even under Embroider:
import MyComponent from 'my-engine/components/my-component';
import { render } from '@ember/test-helpers';

module('Rendering | MyComponent', function (hooks) {
  setupRenderingTest(hooks);
  setupEngine(hooks, 'my-engine');

  test('it renders', function () {
    await render(<template><MyComponent /></template>, { owner: this.engine });
    assert.dom('[data-test-my-component]').exists();
  });
});

the tricky part - how to create an instance of engine under Embroider. That's something @void-mAlex had some ideas for.
I agree with @void-mAlex in that this PR "as is" can't go in as it would break CI and we need to do some maintenance in this repo to properly setup engines as addons and test components provided by those engines in the engine's dumm app (rather than doing it in ember-engines package which is wrong)

@SergeAstapov can we have another discussion about the setupEngine with the three of us, I have a different option about this direction, given we're still relying on ember-asset-loader and the CI is green now with the engines being built upon this addon I don't see any problem in fixing this PR to make it green so we can handle with ember-asset-loader later and hit two birds with one stone, also I can lead this initiative in replacing the ember-asset-loader by Embroider router/loading given the embroider router is not enough because we have routeless engines.

the tricky part - how to create an instance of engine under Embroider.

I also have some ideas, how we can discuss it as a team?

I agree with @void-mAlex in that this PR "as is" can't go in as it would break CI

can we merge it if I get the CI green @SergeAstapov?

can we merge it if I get the CI green?

@villander tbh I don't think is possible under Embroider. I would be glad to be wrong, so you could make it green - I would be happy to review proposed changes!

@SergeAstapov we don't need to make it work under embroider right away - we just need to do the same as we did for #855 so we can make the tests real satisfying the original RFC which means the @classiconly so we can handle embroider later.
if (macroCondition(!dependencySatisfies('@embroider/core', '*')) {
  // handle with ember asset loader stuff
}


prevent marginfigure / sidenotes from running off page

marginfix was removed, which fixed https://github.com/fmarotta/kaobook/issues/77 and https://github.com/fmarotta/kaobook/issues/169
The consequence, however, is that without marginfix, the MWE produces the following output:

adding it back in gives

I don't know what a good solution is.
\documentclass[
	letterpaper, 	% Page size
	fontsize=11pt, % Base font size
	twoside=false, % Use different layouts for even and odd pages (in particular, if twoside=true, the margin column will be always on the outside)
	%open=any, % If twoside=true, uncomment this to force new chapters to start on any page, not only on right (odd) pages
	secnumdepth=1, % How deep to number headings. Defaults to 1 (sections)
]{kaobook}

\pagestyle{centeredpagenum.scrheadings}
% \usepackage{marginfix} this makes or breaks this document

\usepackage[utf8]{inputenc}

% necessary for `kaorefs`'s `\addto` definitions
\usepackage[english]{babel} % Load characters and hyphenation

% Load mathematical packages for theorems and related environments
% needs to be included, otherwise
% `! LaTeX Error: Command \openbox already defined.`
\usepackage{kaotheorems}

% Load the package for hyperreferences
% n.b.: defines command `\refeq`, and so needs to be after `mathtools` and renaming
\usepackage{kaorefs}

\begin{document}

\chapter{Introduction}
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text, and a reference to \cref{fig:a}
\begin{marginfigure}
    \centering
    \includegraphics[width=1\textwidth]{example-image}
    \includegraphics[width=1\textwidth]{example-image}
    \includegraphics[width=1\textwidth]{example-image}
    \includegraphics[width=1\textwidth]{example-image}
	\caption[One sentence caption for list.]{
        The image already ran off the page. But if it didn't then:
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
        A really long caption that is going to run off the bottom of the page
    }
    \label{fig:a}
\end{marginfigure}

\appendix
\end{document}

Is there a reason to not include the graphics a little higher? The following code works fine for me, it produces the same result as in your second image.
\documentclass[
	letterpaper, 	% Page size
	fontsize=11pt, % Base font size
	twoside=false, % Use different layouts for even and odd pages (in particular, if twoside=true, the margin column will be always on the outside)
	%open=any, % If twoside=true, uncomment this to force new chapters to start on any page, not only on right (odd) pages
	secnumdepth=1, % How deep to number headings. Defaults to 1 (sections)
]{kaobook}

\pagestyle{centeredpagenum.scrheadings}
% \usepackage{marginfix} this makes or breaks this document

\usepackage[utf8]{inputenc}

% necessary for `kaorefs`'s `\addto` definitions
\usepackage[english]{babel} % Load characters and hyphenation

% Load mathematical packages for theorems and related environments
% needs to be included, otherwise
% `! LaTeX Error: Command \openbox already defined.`
\usepackage{kaotheorems}

% Load the package for hyperreferences
% n.b.: defines command `\refeq`, and so needs to be after `mathtools` and renaming
\usepackage{kaorefs}

\begin{document}

\chapter{Introduction}
\begin{marginfigure}
	\centering
	\includegraphics[width=1\textwidth]{example-image}
	\includegraphics[width=1\textwidth]{example-image}
	\includegraphics[width=1\textwidth]{example-image}
	\includegraphics[width=1\textwidth]{example-image}
\caption[One sentence caption for list.]{
			The image already ran off the page. But if it didn't then:
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
			A really long caption that is going to run off the bottom of the page
	}
	\label{fig:a}
\end{marginfigure}
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text\\
A lot of text, and a reference to \cref{fig:a}

\appendix
\end{document}

The reason is to produce a MWE illustrating the issue. I don't believe that the solution to move the figure up works in general. I suspect there is an MWE with multiple margin figures, where, depending on the pagination, some of them are off the page.

I can confirm that, I definitely encounter figures that run off the page instead of being moved around. I can indeed counter this by moving the figure higher, exchanging them, or radically set their placement by hand by removing their floating status. But this means that changing the text at some place can completely wreck havoc in my document further down and I have to redo the placement work again, which is really painful.

I have similar issues with long list of citations (i.e. using \sidecite{A, B, ...}).
Reactivating marginfix solves the problem.
So at least on my document the advantages of marginfix definitely outweigh its advantages.


Mazumder - Propose a new FAQ page with more questions in the next week or two

Current FAQ page only has 5 questions: https://data.argosdb.org/static/faq
Jingyue (primary) and Emily (and later other team members) propose a new FAQ page with more questions in the next week of two.

Status update per Raja's feedback: Remove questions regarding license, copyright, and data distribution. Incorporate these information in the banner. Jonathon, Pat, and Raja are double checking MIT license. Jingyue continues working with Stephanie to finalize the responses.
This needs to be done before the data push next Friday (8/4)

Modify FAQs with @steph-sing  on Friday: https://docs.google.com/document/d/1vQo8GeIBC7XuV-P4mtGYLsOI9pDptPmoSEjx5SZnJdU/edit?usp=sharing
Once done, this will be included in the data release next week.

FAQs will be updated as part of v1.54


Change include so that harfbuzz can find graphite

Hi there, thanks for your work on this!
In order to have freetype-harfbuzz build i found that i needed to change the include directory to capture includes like like graphite2/Font.h. I'm not confident this is the best way to fix this, or that this needs fixing in general, but in my case this was the smallest change that led to a successful build.

Of course!
Good catch, I hadn't realized that there was an issue with graphite's header files not being found.


Add image to iFrame

can't upload a SVG because it's more than 10MB
https://github.com/TurboWarp/extensions/issues/90

A new image was posted in #90 that we'll use instead

oh ok


Add authentication

Should solve this issue.
Merge pending confirmation of OSX compatibility.

Apparently tr would fail with tr: Illegal byte sequence if the locale were set to UTF-8. I've just hardcoded the entire script to be C. Poor fix in regards to i18n but I don't have the bandwidth or linguistic skills to test that stuff :upside_down_face:
Works otherwise :+1:


Document metrics and update overview section

Thank you for the initiative @yolossn 😄
I've made some grammar suggestions to help with the overall flow, and this is a fantastic resource for people who are starting out. Apologies if I over-commented as this is my first PR review for this project, and hope this was helpful!

@andrewpollack  sorry I am not able to see any suggestions. Am I missing something here?

@andrewpollack sorry I am not able to see any suggestions. Am I missing something here?

My bad, I think I forgot to publish! Try checking now

Relates to #1856