Evolving all even with the NONE setting

Expected Behavior
Should not evolve.
Actual Behavior
At one point the bot has evolved all the Pokemons.
Steps to Reproduce
I have the log to help you figure out the problem.
Other Information
My Configs:
{
"auth_service": "google",
"username"<EMAIL_ADDRESS>"password": "xxxxxxx",
"location": "40.764889,-73.972744",
"gmapkey": "xxxxxxx",
"max_steps": 5,
"mode": "all",
"walk": 25,
"debug": false,
"test": false,
"initial_transfer": 0,
"location_cache": true,
"distance_unit": "km",
"item_filter": "101,102,103,104,201,202,701",
"evolve_all": "NONE"
}
LOG:
[2016-07-29 14:55:40] [#] Finished walking
[2016-07-29 14:55:40] [#] Arrived at Pokestop
[2016-07-29 14:55:43] [#] Now at Pokestop: Unknown - Spinning...
Traceback (most recent call last):
File ".\pokecli.py", line 220, in
main()
File ".\pokecli.py", line 211, in main
bot.take_step()
File "C:\Users\henri\Desktop\2\pokemongo_bot_init_.py", line 36, in take_step
self.stepper.take_step()
File "C:\Users\henri\Desktop\2\pokemongo_bot\stepper.py", line 62, in take_step
self._work_at_position(position[0], position[1], position[2], True)
File "C:\Users\henri\Desktop\2\pokemongo_bot\stepper.py", line 139, in work_at_position
self.bot.work_on_cell(cell, position, pokemon_only)
File "C:\Users\henri\Desktop\2\pokemongo_bot_init.py", line 96, in work_on_cell
hack_chain = worker.work()
File "C:\Users\henri\Desktop\2\pokemongo_bot\cell_workers\seen_fort_worker.py", line 51, in work
if spin_details['result'] == 1:
KeyError: 'result'
Shutdown Pokemon Go? [Y,N]?N
Iniciando
[2016-07-29 14:55:58] [x] PokemonGO Bot v1.0
[2016-07-29 14:55:58] [x] Configuration initialized
[2016-07-29 14:55:58] [x] Coordinates found in passed in location, not geocoding.
[2016-07-29 14:55:58]
[2016-07-29 14:55:58] [x] Address found: 40.764889,-73.972744
[2016-07-29 14:55:58] [x] Position in-game set as: (40.764889, -73.972744, 0.0)
[2016-07-29 14:55:58]
[2016-07-29 14:56:00] [#] Username: Mashielll
[2016-07-29 14:56:00] [#] Acccount Creation: 2016-07-23 17:53:09.781000
[2016-07-29 14:56:00] [#] Bag Storage: 163/350
[2016-07-29 14:56:01] [#] Pokemon Storage: 151/250
[2016-07-29 14:56:01] [#] Stardust: 1317662
[2016-07-29 14:56:01] [#] Pokecoins: 0
[2016-07-29 14:56:01] [#] PokeBalls: 28
[2016-07-29 14:56:01] [#] GreatBalls: 6
[2016-07-29 14:56:01] [#] UltraBalls: 3
[2016-07-29 14:56:01] [#] -- Level: 32
[2016-07-29 14:56:01] [#] -- Experience: 3392120
[2016-07-29 14:56:01] [#] -- Experience until next level: 357880
[2016-07-29 14:56:01] [#] -- Pokemon Captured: 12759
[2016-07-29 14:56:01] [#] -- Pokestops Visited: 8709
[2016-07-29 14:56:01] [#]
[2016-07-29 14:56:01] [x] Starting PokemonGo Bot....
[2016-07-29 14:56:01] [#] Scanning area for objects (1 / 25)
[2016-07-29 14:56:01] [#] Walking from (40.764889, -73.972744) to (40.764889, -73.972744) for approx. 0.00 seconds
[#] (40.764889, -73.972744, 0)
[#] Attempting to evolve all pokemons ...
[#] Evolved 142 pokemons! Checking if any of them needs to be released ...
[2016-07-29 14:56:03] [#] Ninetales has been exchanged for candy!
[2016-07-29 14:56:04] [#] Dewgong has been exchanged for candy!
[2016-07-29 14:56:05] [#] Poliwrath has been exchanged for candy!
[2016-07-29 14:56:05] [#] Dodrio has been exchanged for candy!
[2016-07-29 14:56:06] [#] Weepinbell has been exchanged for candy!
[2016-07-29 14:56:06] [#] Flareon has been exchanged for candy!
[2016-07-29 14:56:07] [#] Electabuzz has been exchanged for candy!
[2016-07-29 14:56:07] [#] Jynx has been exchanged for candy!
[2016-07-29 14:56:08] [#] Ponyta has been exchanged for candy!
[2016-07-29 14:56:08] [#] Omastar has been exchanged for candy!
[2016-07-29 14:56:09] [#] Tangela has been exchanged for candy!
[2016-07-29 14:56:09] [#] Kabutops has been exchanged for candy!
[2016-07-29 14:56:10] [#] Sandslash has been exchanged for candy!
[2016-07-29 14:56:10] [#] Seadra has been exchanged for candy!
[2016-07-29 14:56:10] [#] Parasect has been exchanged for candy!
[2016-07-29 14:56:11] [#] Slowpoke has been exchanged for candy!
[2016-07-29 14:56:11] [#] Koffing has been exchanged for candy!
[2016-07-29 14:56:12] [#] Psyduck has been exchanged for candy!
[2016-07-29 14:56:12] [#] Gloom has been exchanged for candy!
[2016-07-29 14:56:13] [#] Marowak has been exchanged for candy!
[2016-07-29 14:56:13] [#] Bellsprout has been exchanged for candy!
[2016-07-29 14:56:14] [#] Fearow has been exchanged for candy!
[2016-07-29 14:56:14] [#] Poliwhirl has been exchanged for candy!
[2016-07-29 14:56:15] [#] Pidgeot has been exchanged for candy!
[2016-07-29 14:56:15] [#] Drowzee has been exchanged for candy!
[2016-07-29 14:56:16] [#] Drowzee has been exchanged for candy!
[2016-07-29 14:56:17] [#] Psyduck has been exchanged for candy!
[2016-07-29 14:56:18] [#] Venonat has been exchanged for candy!
[2016-07-29 14:56:18] [#] Venonat has been exchanged for candy!
[2016-07-29 14:56:19] [#] Raticate has been exchanged for candy!
[2016-07-29 14:56:19] [#] Seel has been exchanged for candy!
[2016-07-29 14:56:20] [#] Growlithe has been exchanged for candy!
[2016-07-29 14:56:20] [#] Machop has been exchanged for candy!
[2016-07-29 14:56:21] [#] Haunter has been exchanged for candy!
[2016-07-29 14:56:21] [#] Bulbasaur has been exchanged for candy!
[2016-07-29 14:56:22] [#] Eevee has been exchanged for candy!
[2016-07-29 14:56:22] [#] Goldeen has been exchanged for candy!
[2016-07-29 14:56:23] [#] Omanyte has been exchanged for candy!
[2016-07-29 14:56:23] [#] Paras has been exchanged for candy!
[2016-07-29 14:56:24] [#] Rhyhorn has been exchanged for candy!
[2016-07-29 14:56:24] [#] Arbok has been exchanged for candy!
[2016-07-29 14:56:25] [#] Pidgeotto has been exchanged for candy!
[2016-07-29 14:56:25] [#] Squirtle has been exchanged for candy!
[2016-07-29 14:56:25] [#] Doduo has been exchanged for candy!
[2016-07-29 14:56:26] [#] Pikachu has been exchanged for candy!
[2016-07-29 14:56:27] [#] Tentacool has been exchanged for candy!
[2016-07-29 14:56:27] [#] Geodude has been exchanged for candy!
[2016-07-29 14:56:28] [#] Squirtle has been exchanged for candy!
[2016-07-29 14:56:28] [#] Nidorino has been exchanged for candy!
[2016-07-29 14:56:29] [#] Dratini has been exchanged for candy!
[2016-07-29 14:56:29] [#] Jolteon has been exchanged for candy!
[2016-07-29 14:56:30] [#] Krabby has been exchanged for candy!
[2016-07-29 14:56:30] [#] Dratini has been exchanged for candy!
[2016-07-29 14:56:31] [#] Pikachu has been exchanged for candy!
[2016-07-29 14:56:31] [#] Onix has been exchanged for candy!
[2016-07-29 14:56:31] [#] Poliwag has been exchanged for candy!
[2016-07-29 14:56:32] [#] Magnemite has been exchanged for candy!
[2016-07-29 14:56:33] [#] Machoke has been exchanged for candy!
[2016-07-29 14:56:33] [#] Kabuto has been exchanged for candy!
[2016-07-29 14:56:33] [#] Graveler has been exchanged for candy!
[2016-07-29 14:56:34] [#] Horsea has been exchanged for candy!
[2016-07-29 14:56:34] [#] Nidoran F has been exchanged for candy!
[2016-07-29 14:56:35] [#] Kingler has been exchanged for candy!
[2016-07-29 14:56:35] [#] Nidorina has been exchanged for candy!
[2016-07-29 14:56:36] [#] Gastly has been exchanged for candy!
[2016-07-29 14:56:36] [#] Nidoran M has been exchanged for candy!
[2016-07-29 14:56:37] [#] Spearow has been exchanged for candy!
[2016-07-29 14:56:37] [#] Pidgey has been exchanged for candy!
[2016-07-29 14:56:37] [#] Ekans has been exchanged for candy!
[2016-07-29 14:56:38] [#] Dugtrio has been exchanged for candy!
[2016-07-29 14:56:38] [#] Zubat has been exchanged for candy!
[2016-07-29 14:56:39] [#] Meowth has been exchanged for candy!
[2016-07-29 14:56:39] [#] Wartortle has been exchanged for candy!
[2016-07-29 14:56:40] [#] Voltorb has been exchanged for candy!
[2016-07-29 14:56:40] [#] Shellder has been exchanged for candy!
[2016-07-29 14:56:41] [#] Sandshrew has been exchanged for candy!
[2016-07-29 14:56:41] [#] Rattata has been exchanged for candy!
[2016-07-29 14:56:42] [#] Clefairy has been exchanged for candy!
[2016-07-29 14:56:42] [#] Charmander has been exchanged for candy!
[2016-07-29 14:56:42] [#] Abra has been exchanged for candy!
[2016-07-29 14:56:43] [#] Kakuna has been exchanged for candy!
[2016-07-29 14:56:43] [#] Weedle has been exchanged for candy!
[2016-07-29 14:56:44] [#] Beedrill has been exchanged for candy!
[2016-07-29 14:56:44] [#] Caterpie has been exchanged for candy!
[2016-07-29 14:56:45] [#] Magneton has been exchanged for candy!
[2016-07-29 14:56:45] [#] Metapod has been exchanged for candy!
[2016-07-29 14:56:46] [#] Diglett has been exchanged for candy!
[2016-07-29 14:56:46] [#] Venomoth has been exchanged for candy!
[2016-07-29 14:56:47] [#] Starmie has been exchanged for candy!
[2016-07-29 14:56:47] [#] Magikarp has been exchanged for candy!
[2016-07-29 14:56:47] [#] Seaking has been exchanged for candy!
[2016-07-29 14:56:48] [#] Victreebel has been exchanged for candy!
[2016-07-29 14:57:01] [#] Scanning area for objects (2 / 25)
[2016-07-29 14:57:01] [#] Walking from (40.764889, -73.972744) to (40.767388999999994, -73.972744) for approx. 6.00 seconds
[2016-07-29 14:57:15] [#] Finished walking
[#] (40.767388999999994, -73.972744, 0)
[2016-07-29 14:57:28] [#] Scanning area for objects (3 / 25)
[2016-07-29 14:57:28] [#] Walking from (40.767388999999994, -73.972744) to (40.767388999999994, -73.97024400000001) for approx. 5.00 seconds
[2016-07-29 14:57:39] [#] Finished walking
[#] (40.767388999999994, -73.97024400000001, 0)
[2016-07-29 14:57:49] [#] Scanning area for objects (4 / 25)
[2016-07-29 14:57:49] [#] Walking from (40.767388999999994, -73.97024400000001) to (40.764889, -73.97024400000001) for approx. 6.00 seconds
[2016-07-29 14:57:58] [#] Finished walking
[#] (40.764889, -73.97024400000001, 0)
[2016-07-29 14:58:09] [#] Scanning area for objects (5 / 25)
[2016-07-29 14:58:09] [#] Walking from (40.764889, -73.97024400000001) to (40.762389, -73.97024400000001) for approx. 6.00 seconds
[2016-07-29 14:58:24] [#] Finished walking
[#] (40.762389, -73.97024400000001, 0)
[2016-07-29 14:58:35] [#] Scanning area for objects (6 / 25)
[2016-07-29 14:58:35] [#] Walking from (40.762389, -73.97024400000001) to (40.762389, -73.972744) for approx. 5.00 seconds
[2016-07-29 14:58:47] [#] Finished walking
[#] (40.762389, -73.972744, 0)
[2016-07-29 14:58:58] [#] Scanning area for objects (7 / 25)
[2016-07-29 14:58:58] [#] Walking from (40.762389, -73.972744) to (40.762389, -73.975244) for approx. 5.00 seconds
[2016-07-29 14:59:07] [#] Finished walking
[#] (40.762389, -73.975244, 0)
[2016-07-29 14:59:20] [#] Scanning area for objects (8 / 25)
[2016-07-29 14:59:20] [#] Walking from (40.762389, -73.975244) to (40.764889, -73.975244) for approx. 6.00 seconds
[2016-07-29 14:59:34] [#] Finished walking
[#] (40.764889, -73.975244, 0)
[2016-07-29 14:59:44] [#] Scanning area for objects (9 / 25)
[2016-07-29 14:59:44] [#] Walking from (40.764889, -73.975244) to (40.767388999999994, -73.975244) for approx. 6.00 seconds
[2016-07-29 14:59:56] [#] Finished walking
[#] (40.767388999999994, -73.975244, 0)
[2016-07-29 15:00:08] [#] Scanning area for objects (10 / 25)
[2016-07-29 15:00:08] [#] Walking from (40.767388999999994, -73.975244) to (40.769889, -73.975244) for approx. 6.00 seconds
[2016-07-29 15:00:22] [#] Finished walking
[#] (40.769889, -73.975244, 0)
[2016-07-29 15:00:34] [#] Scanning area for objects (11 / 25)
[2016-07-29 15:00:34] [#] Walking from (40.769889, -73.975244) to (40.769889, -73.972744) for approx. 5.00 seconds
[2016-07-29 15:00:46] [#] Finished walking
[#] (40.769889, -73.972744, 0)
[2016-07-29 15:00:57] [#] Scanning area for objects (12 / 25)
[2016-07-29 15:00:57] [#] Walking from (40.769889, -73.972744) to (40.769889, -73.97024400000001) for approx. 5.00 seconds
[2016-07-29 15:01:05] [#] Finished walking
[#] (40.769889, -73.97024400000001, 0)
[2016-07-29 15:01:17] [#] Scanning area for objects (13 / 25)
[2016-07-29 15:01:17] [#] Walking from (40.769889, -73.97024400000001) to (40.769889, -73.96774400000001) for approx. 5.00 seconds
[2016-07-29 15:01:27] [#] Finished walking
[#] (40.769889, -73.96774400000001, 0)
[2016-07-29 15:01:41] [#] Scanning area for objects (14 / 25)
[2016-07-29 15:01:41] [#] Walking from (40.769889, -73.96774400000001) to (40.767388999999994, -73.96774400000001) for approx. 6.00 seconds
[2016-07-29 15:01:53] [#] Finished walking
[#] (40.767388999999994, -73.96774400000001, 0)
[2016-07-29 15:02:04] [#] Scanning area for objects (15 / 25)
[2016-07-29 15:02:04] [#] Walking from (40.767388999999994, -73.96774400000001) to (40.764889, -73.96774400000001) for approx. 6.00 seconds
[2016-07-29 15:02:17] [#] Finished walking
[#] (40.764889, -73.96774400000001, 0)
[2016-07-29 15:02:30] [#] Scanning area for objects (16 / 25)
[2016-07-29 15:02:30] [#] Walking from (40.764889, -73.96774400000001) to (40.762389, -73.96774400000001) for approx. 6.00 seconds
[2016-07-29 15:02:47] [#] Finished walking
[#] (40.762389, -73.96774400000001, 0)
[2016-07-29 15:03:00] [#] Scanning area for objects (17 / 25)
[2016-07-29 15:03:00] [#] Walking from (40.762389, -73.96774400000001) to (40.759888999999994, -73.96774400000001) for approx. 6.00 seconds
[2016-07-29 15:03:15] [#] Finished walking
[#] (40.759888999999994, -73.96774400000001, 0)
[2016-07-29 15:03:23] [#] Scanning area for objects (18 / 25)
[2016-07-29 15:03:23] [#] Walking from (40.759888999999994, -73.96774400000001) to (40.759888999999994, -73.97024400000001) for approx. 5.00 seconds
[2016-07-29 15:03:34] [#] Finished walking
[#] (40.759888999999994, -73.97024400000001, 0)
[2016-07-29 15:03:48] [#] Scanning area for objects (19 / 25)
[2016-07-29 15:03:48] [#] Walking from (40.759888999999994, -73.97024400000001) to (40.759888999999994, -73.972744) for approx. 5.00 seconds
[2016-07-29 15:03:58] [#] Finished walking
[#] (40.759888999999994, -73.972744, 0)
[2016-07-29 15:04:11] [#] Scanning area for objects (20 / 25)
[2016-07-29 15:04:11] [#] Walking from (40.759888999999994, -73.972744) to (40.759888999999994, -73.975244) for approx. 5.00 seconds
[2016-07-29 15:04:21] [#] Finished walking
[#] (40.759888999999994, -73.975244, 0)
[2016-07-29 15:04:32] [#] Scanning area for objects (21 / 25)
[2016-07-29 15:04:32] [#] Walking from (40.759888999999994, -73.975244) to (40.759888999999994, -73.977744) for approx. 5.00 seconds
[2016-07-29 15:04:43] [#] Finished walking
[#] (40.759888999999994, -73.977744, 0)
[2016-07-29 15:04:57] [#] Scanning area for objects (22 / 25)
[2016-07-29 15:04:57] [#] Walking from (40.759888999999994, -73.977744) to (40.762389, -73.977744) for approx. 6.00 seconds
[2016-07-29 15:05:10] [#] Finished walking
[#] (40.762389, -73.977744, 0)
[2016-07-29 15:05:24] [#] Scanning area for objects (23 / 25)
[2016-07-29 15:05:24] [#] Walking from (40.762389, -73.977744) to (40.764889, -73.977744) for approx. 6.00 seconds
[2016-07-29 15:05:36] [#] Finished walking
[#] (40.764889, -73.977744, 0)
[2016-07-29 15:05:51] [#] Scanning area for objects (24 / 25)
[2016-07-29 15:05:51] [#] Walking from (40.764889, -73.977744) to (40.767388999999994, -73.977744) for approx. 6.00 seconds
[2016-07-29 15:06:04] [#] Finished walking
[#] (40.767388999999994, -73.977744, 0)
[2016-07-29 15:06:16] [#] Scanning area for objects (25 / 25)
[2016-07-29 15:06:16] [#] Walking from (40.767388999999994, -73.977744) to (40.769889, -73.977744) for approx. 6.00 seconds
[2016-07-29 15:06:29] [#] Finished walking
[#] (40.769889, -73.977744, 0)
[2016-07-29 15:06:40] [#] Scanning area for objects (1 / 25)
[2016-07-29 15:06:40] [#] Walking from (40.764889, -73.972744) to (40.772389, -73.977744) for approx. 19.00 seconds
[2016-07-29 15:07:21] [#] Finished walking
[#] (40.772389, -73.977744, 0)
[2016-07-29 15:07:34] [#] Scanning area for objects (2 / 25)
[2016-07-29 15:07:34] [#] Walking from (40.772389, -73.977744) to (40.772389, -73.975244) for approx. 5.00 seconds
[2016-07-29 15:07:45] [#] Finished walking
[#] (40.772389, -73.975244, 0)
[2016-07-29 15:07:56] [#] Scanning area for objects (3 / 25)
[2016-07-29 15:07:56] [#] Walking from (40.772389, -73.975244) to (40.772389, -73.972744) for approx. 5.00 seconds
[2016-07-29 15:08:06] [#] Finished walking
[#] (40.772389, -73.972744, 0)
[2016-07-29 15:08:19] [#] Scanning area for objects (4 / 25)
[2016-07-29 15:08:19] [#] Walking from (40.772389, -73.972744) to (40.772389, -73.97024400000001) for approx. 5.00 seconds
[2016-07-29 15:08:26] [#] Finished walking
[#] (40.772389, -73.97024400000001, 0)
[2016-07-29 15:08:40] [#] Scanning area for objects (5 / 25)
[2016-07-29 15:08:40] [#] Walking from (40.772389, -73.97024400000001) to (40.772389, -73.96774400000001) for approx. 5.00 seconds
[2016-07-29 15:08:48] [#] Finished walking
[#] (40.772389, -73.96774400000001, 0)
[2016-07-29 15:08:59] [#] Scanning area for objects (6 / 25)
[2016-07-29 15:08:59] [#] Walking from (40.772389, -73.96774400000001) to (40.772389, -73.96524400000001) for approx. 5.00 seconds
[2016-07-29 15:09:11] [#] Finished walking
[#] (40.772389, -73.96524400000001, 0)
[2016-07-29 15:09:22] [#] Scanning area for objects (7 / 25)
[2016-07-29 15:09:22] [#] Walking from (40.772389, -73.96524400000001) to (40.769889, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:09:36] [#] Finished walking
[#] (40.769889, -73.96524400000001, 0)
[2016-07-29 15:09:45] [#] Scanning area for objects (8 / 25)
[2016-07-29 15:09:45] [#] Walking from (40.769889, -73.96524400000001) to (40.767388999999994, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:09:57] [#] Finished walking
[#] (40.767388999999994, -73.96524400000001, 0)
[2016-07-29 15:10:07] [#] Scanning area for objects (9 / 25)
[2016-07-29 15:10:07] [#] Walking from (40.767388999999994, -73.96524400000001) to (40.764889, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:10:21] [#] Finished walking
[#] (40.764889, -73.96524400000001, 0)
[2016-07-29 15:10:36] [#] Scanning area for objects (10 / 25)
[2016-07-29 15:10:36] [#] Walking from (40.764889, -73.96524400000001) to (40.762389, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:10:46] [#] Finished walking
[#] (40.762389, -73.96524400000001, 0)
[2016-07-29 15:10:58] [#] Scanning area for objects (11 / 25)
[2016-07-29 15:10:58] [#] Walking from (40.762389, -73.96524400000001) to (40.759888999999994, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:11:10] [#] Finished walking
[#] (40.759888999999994, -73.96524400000001, 0)
[2016-07-29 15:11:24] [#] Scanning area for objects (12 / 25)
[2016-07-29 15:11:24] [#] Walking from (40.759888999999994, -73.96524400000001) to (40.757388999999996, -73.96524400000001) for approx. 6.00 seconds
[2016-07-29 15:11:36] [#] Finished walking
[#] (40.757388999999996, -73.96524400000001, 0)
[2016-07-29 15:11:50] [#] Scanning area for objects (13 / 25)
[2016-07-29 15:11:50] [#] Walking from (40.757388999999996, -73.96524400000001) to (40.757388999999996, -73.96774400000001) for approx. 5.00 seconds
[2016-07-29 15:12:05] [#] Finished walking
[#] (40.757388999999996, -73.96774400000001, 0)
[2016-07-29 15:12:17] [#] Scanning area for objects (14 / 25)
[2016-07-29 15:12:17] [#] Walking from (40.757388999999996, -73.96774400000001) to (40.757388999999996, -73.97024400000001) for approx. 5.00 seconds
[2016-07-29 15:12:24] [#] Finished walking
[#] (40.757388999999996, -73.97024400000001, 0)
[2016-07-29 15:12:34] [#] Scanning area for objects (15 / 25)
[2016-07-29 15:12:34] [#] Walking from (40.757388999999996, -73.97024400000001) to (40.757388999999996, -73.972744) for approx. 5.00 seconds
[2016-07-29 15:12:44] [#] Finished walking
[#] (40.757388999999996, -73.972744, 0)
[2016-07-29 15:12:55] [#] Scanning area for objects (16 / 25)
[2016-07-29 15:12:55] [#] Walking from (40.757388999999996, -73.972744) to (40.757388999999996, -73.975244) for approx. 5.00 seconds
[2016-07-29 15:13:02] [#] Finished walking
[#] (40.757388999999996, -73.975244, 0)
[2016-07-29 15:13:10] [#] Scanning area for objects (17 / 25)
[2016-07-29 15:13:10] [#] Walking from (40.757388999999996, -73.975244) to (40.757388999999996, -73.977744) for approx. 5.00 seconds
[2016-07-29 15:13:22] [#] Finished walking
[#] (40.757388999999996, -73.977744, 0)
[2016-07-29 15:13:30] [#] Scanning area for objects (18 / 25)
[2016-07-29 15:13:30] [#] Walking from (40.757388999999996, -73.977744) to (40.757388999999996, -73.980244) for approx. 5.00 seconds
[2016-07-29 15:13:39] [#] Finished walking
[#] (40.757388999999996, -73.980244, 0)
[2016-07-29 15:13:51] [#] Scanning area for objects (19 / 25)
[2016-07-29 15:13:51] [#] Walking from (40.757388999999996, -73.980244) to (40.759888999999994, -73.980244) for approx. 6.00 seconds
[2016-07-29 15:14:07] [#] Finished walking
[#] (40.759888999999994, -73.980244, 0)
[2016-07-29 15:14:18] [#] Scanning area for objects (20 / 25)
[2016-07-29 15:14:18] [#] Walking from (40.759888999999994, -73.980244) to (40.762389, -73.980244) for approx. 6.00 seconds
[2016-07-29 15:14:30] [#] Finished walking
[#] (40.762389, -73.980244, 0)
[2016-07-29 15:14:40] [#] Scanning area for objects (21 / 25)
[2016-07-29 15:14:40] [#] Walking from (40.762389, -73.980244) to (40.764889, -73.980244) for approx. 6.00 seconds
[2016-07-29 15:14:54] [#] Finished walking
[#] (40.764889, -73.980244, 0)
[2016-07-29 15:15:06] [#] Scanning area for objects (22 / 25)
[2016-07-29 15:15:06] [#] Walking from (40.764889, -73.980244) to (40.767388999999994, -73.980244) for approx. 6.00 seconds
[2016-07-29 15:15:09] [#] Something rustles nearby!
[2016-07-29 15:15:10] [#] A Wild Rattata appeared! [CP 176] [Potential 0.64]
[2016-07-29 15:15:10] [#] IV [Stamina/Attack/Defense] = [14/7/8]
[2016-07-29 15:15:13] [x] Using Pokeball (chance: 43.22%)... (27 left!)
[2016-07-29 15:15:14] [-] Attempted to capture Rattata- failed.. trying again!
[2016-07-29 15:15:16] [x] Using Pokeball (chance: 43.22%)... (26 left!)
[2016-07-29 15:15:16] [x] Captured Rattata! [CP 176] [IV 0.64]
[2016-07-29 15:15:17] [#] Rattata has been exchanged for candy!
[2016-07-29 15:15:22] [#] A Wild Pidgeotto appeared!  [CP 953] [IV 0.64]
[2016-07-29 15:15:30] [#] Pidgeotto has been exchanged for candy!
[2016-07-29 15:15:52] [#] Something rustles nearby!
[2016-07-29 15:15:53] [#] A Wild Spearow appeared! [CP 492] [Potential 0.76]
[2016-07-29 15:15:53] [#] IV [Stamina/Attack/Defense] = [15/11/8]
[2016-07-29 15:15:55] [x] Using Greatball (chance: 39.94%)... (5 left!)
[2016-07-29 15:15:55] [x] Captured Spearow! [CP 492] [IV 0.76]
[2016-07-29 15:15:56] [#] Spearow has been exchanged for candy!
[2016-07-29 15:16:07] [#] Something rustles nearby!
[2016-07-29 15:16:08] [#] A Wild Electabuzz appeared! [CP 438] [Potential 0.53]
[2016-07-29 15:16:08] [#] IV [Stamina/Attack/Defense] = [14/3/7]
[2016-07-29 15:16:10] [x] Using Greatball (chance: 43.90%)... (4 left!)
[2016-07-29 15:16:11] [x] Captured Electabuzz! [CP 438] [IV 0.53]
[2016-07-29 15:16:12] [#] Electabuzz has been exchanged for candy!
[2016-07-29 15:16:17] [#] A Wild Electabuzz appeared!  Electabuzz vanished! :(
[2016-07-29 15:16:37] [#] Finished walking
[#] (40.767388999999994, -73.980244, 0)
[2016-07-29 15:16:37] [#] Found fort 7bcad78e177d4ba0b02a6579fdb37437.16 at distance 0.70km
[2016-07-29 15:16:37] [#] Need to move closer to Pokestop
[2016-07-29 15:16:37] [#] Walking from (40.767388999999994, -73.980244) to (40.76733, -73.980412) for approx. 1.00 second
[2016-07-29 15:16:37] [#] Finished walking
[2016-07-29 15:16:38] [#] Arrived at Pokestop
[2016-07-29 15:16:39] [#] Now at Pokestop: Gainesborough Studios - Spinning...
[2016-07-29 15:16:40] [+] Loot:
[2016-07-29 15:16:40] [+] 50 xp
[2016-07-29 15:16:41] [+] 1x Pokeball (Total: 27)
[2016-07-29 15:16:41] [+] 1x Ultraball (Total: 1)
[2016-07-29 15:16:41] [+] 1x Potion (Total: 1)
[2016-07-29 15:16:41] [+] Recycling 1x Potion...
[2016-07-29 15:16:42] [+] Recycling success
[2016-07-29 15:16:42] [#] PokeStop on cooldown. Time left: 4.91 minutes
[2016-07-29 15:16:44] [#] Found fort 3e10e03d70a44590bdf7193e37e0c6b1.16 at distance 0.76km
[2016-07-29 15:16:44] [#] Need to move closer to Pokestop
[2016-07-29 15:16:44] [#] Walking from (40.76733, -73.980412) to (40.767534, -73.981055) for approx. 2.00 seconds
[2016-07-29 15:16:46] [#] Finished walking
[2016-07-29 15:16:46] [#] Arrived at Pokestop
[2016-07-29 15:16:47] [#] Now at Pokestop: 240 CPS Mosaic  - Spinning...
[2016-07-29 15:16:49] [+] Loot:
[2016-07-29 15:16:49] [+] 50 xp
[2016-07-29 15:16:49] [+] 2x Pokeball (Total: 29)
[2016-07-29 15:16:49] [+] 1x Razz Berry (Total: 41)
[2016-07-29 15:16:49] [+] Recycling 1x Razz Berry...
[2016-07-29 15:16:49] [+] Recycling success
[2016-07-29 15:16:49] [#] PokeStop on cooldown. Time left: 4.92 minutes
[2016-07-29 15:16:51] [#] Found fort 9a0fbeaef1dd451c9221436b66ecb920.12 at distance 0.78km
[2016-07-29 15:16:51] [#] Need to move closer to Pokestop
[2016-07-29 15:16:51] [#] Walking from (40.767534, -73.981055) to (40.768212, -73.980909) for approx. 2.00 seconds

Ehm.. not to worry you, but he didn't evolve all your pokemon, he transferred them all.
You might want to double check your config, it seems like you're still using the old config

This just happened to me as well...

Set "evolve_all": "NONE" to "evolve_all": "false"

I'll do it.

Updated as follows, I hope I do not have that problem anymore. Thank you.
{
"auth_service": "google",
"username"<EMAIL_ADDRESS>"password": "xxxxxxx",
"location": "40.764889,-73.972744",
"gmapkey": "xxxxxxx",
"max_steps": 5,
"mode": "all",
"walk": 25,
"debug": false,
"test": false,
"initial_transfer": 0,
"location_cache": true,
"distance_unit": "km",
"item_filter": "101,102,103,104,201,202,701",
"evolve_all": "NONE"
}

Another detail, this problem occurred after a week of use.

This has just happened to me using the latest revision of the dev branch.
[2016-07-30 04:10:10] [#] Onix has been exchanged for candy! [2016-07-30 04:10:43] [#] Squirtle has been exchanged for candy! [2016-07-30 04:10:44] [#] Electabuzz has been exchanged for candy! [2016-07-30 04:10:45] [#] Charmander has been exchanged for candy!
Plus a tonne more but these hurt the most.

come to slack chat #help and someone can help you
NOT A BUG

This just happened to me.
I It hurts a lot.
Please, if the default value of  "evolve_all" is “NONE” we understand that our pokemon are not going to be evolved. Please change the default value to "false" if it is the solution.
[#] Attempting to evolve all pokemons ...
[#] Evolved 98 pokemons! Checking if any of them needs to be released ...
[2016-07-31 00:00:37] [#] Vaporeon has been exchanged for candy!
[2016-07-31 00:00:37] [#] Golem has been exchanged for candy!
[2016-07-31 00:00:38] [#] Rhydon has been exchanged for candy!
[2016-07-31 00:00:38] [#] Machamp has been exchanged for candy!
[2016-07-31 00:00:39] [#] Rapidash has been exchanged for candy!
[2016-07-31 00:00:39] [#] Primeape has been exchanged for candy!
[2016-07-31 00:00:40] [#] Graveler has been exchanged for candy!
[2016-07-31 00:00:40] [#] Arbok has been exchanged for candy!
[2016-07-31 00:00:41] [#] Pidgeot has been exchanged for candy!
[2016-07-31 00:00:41] [#] Dodrio has been exchanged for candy!
[2016-07-31 00:00:42] [#] Golbat has been exchanged for candy!
[2016-07-31 00:00:49] [#] Venomoth has been exchanged for candy!
[2016-07-31 00:00:49] [#] Grimer has been exchanged for candy!
[2016-07-31 00:01:04] [#] Ponyta has been exchanged for candy!
[2016-07-31 00:01:27] [#] Rhyhorn has been exchanged for candy!
[2016-07-31 00:01:44] [#] Cubone has been exchanged for candy!
[2016-07-31 00:01:53] [#] Rhyhorn has been exchanged for candy!
[2016-07-31 00:02:00] [#] Eevee has been exchanged for candy!
[2016-07-31 00:02:03] [#] Growlithe has been exchanged for candy!
[2016-07-31 00:02:10] [#] Oddish has been exchanged for candy!
[2016-07-31 00:02:12] [#] Raticate has been exchanged for candy!
[2016-07-31 00:02:14] [#] Geodude has been exchanged for candy!
[2016-07-31 00:02:14] [#] Geodude has been exchanged for candy!
[2016-07-31 00:02:15] [#] Mankey has been exchanged for candy!
[2016-07-31 00:02:16] [#] Eevee has been exchanged for candy!
[2016-07-31 00:02:18] [#] Charmander has been exchanged for candy!
[2016-07-31 00:02:18] [#] Venonat has been exchanged for candy!
[2016-07-31 00:02:19] [#] Charmander has been exchanged for candy!
[2016-07-31 00:02:19] [#] Exeggcute has been exchanged for candy!
[2016-07-31 00:02:20] [#] Vulpix has been exchanged for candy!
[2016-07-31 00:02:20] [#] Vulpix has been exchanged for candy!
[2016-07-31 00:02:21] [#] Zubat has been exchanged for candy!
[2016-07-31 00:02:21] [#] Paras has been exchanged for candy!
[2016-07-31 00:02:22] [#] Diglett has been exchanged for candy!
[2016-07-31 00:02:22] [#] Kadabra has been exchanged for candy!
[2016-07-31 00:02:23] [#] Sandshrew has been exchanged for candy!
[2016-07-31 00:02:23] [#] Abra has been exchanged for candy!
[2016-07-31 00:02:23] [#] Pidgey has been exchanged for candy!
[2016-07-31 00:02:24] [#] Diglett has been exchanged for candy!
[2016-07-31 00:02:25] [#] Jolteon has been exchanged for candy!
[2016-07-31 00:02:25] [#] Kadabra has been exchanged for candy!
[2016-07-31 00:02:26] [#] Rattata has been exchanged for candy!
[2016-07-31 00:02:26] [#] Omanyte has been exchanged for candy!
[2016-07-31 00:02:27] [#] Nidoran F has been exchanged for candy!
[2016-07-31 00:02:27] [#] Pidgeotto has been exchanged for candy!
[2016-07-31 00:02:28] [#] Nidoran F has been exchanged for candy!
[2016-07-31 00:02:28] [#] Poliwag has been exchanged for candy!
[2016-07-31 00:02:29] [#] Bulbasaur has been exchanged for candy!

This is absolutely an issue; settings should only be destructive explicitly, not by fallback or default.

I updated the dev version following a few revisions and haven't had the issue since.
There is clearly an issue with the master revision that has been solved in the dev revision, but unsure at what stage it was fixed.
Would recommend switching to dev if you don't want it happening again.


Unable to detect current script loaded via Data URI on iOS7

Looks like the code of the _currentScript getter runs all the way down to the getScriptUrlFromStack, which can't parse Data URI src of the dynamically injected script. Notice that data uri encoded script can be with prefix data:text/javascript;base64, or with data:text/javascript;charset=utf-8, for IE.

FYI @roman01la: I revised this repo to be strictly spec-compliant. All of the other previously included behavior has been moved to JamesMGreene/currentExecutingScript.


Screen background visual effect not working

Describe the bug
Currently setting attributes.screenBackground to any of the visual effects results in a total loss of background, I've fiddled around with every possible attribute variable to make it work but I finally gave up and tried getting help (and checking if this is a bug or not) here.
entryBackground, windowLevel, shadow, none seem to have any effect on the blurred background, been changing them to every possible option and result is always the same.
To Reproduce
Steps to reproduce the behavior:
1- make any EKAlertMessageView ( I've used one of the popup examples)
2- change the attributes.screenBackground to any of the blur visual effects
Expected behavior
background should be see through blurred over
Screenshots
If applicable, add screenshots to help explain your problem.
iPhone (please complete the following information):

Device: IPhone XS
iOS Version: 12.0
Xcode Version: 10.2
SwiftEntryKit Release: 1.0.2

Additional context
Add any other context about the problem here.
Screenshots / Video Links

Here's the background.

same

Did you resolve?

same

same, Is there a any solution?


[Issue] Login token expires while executing in a GitHub Action workflow in the azd container.

Version: Container image using the :daily tag.
Environment: GitHub Actions workflow
While running a GitHub Action workflow, the azd provision step takes about 11 minutes. By the time it is completed, trying to execute azd deploy results in an error message:  ERROR: getting target resource: getting service resource: not logged in, run 'azd auth login' to login.
My assumption is that the OIDC token expires and that this is a similar bug to https://github.com/Azure/login/issues/180 that the Azure/login action faces.
My workaround is to issue another azd login action before running azd deploy but it is confusing and cumbersome.
See non-working pipeline run: https://github.com/sabbour/contoso-names-e2e/actions/runs/4636146397/jobs/8203775220
See working pipeline with the extra logins run: https://github.com/sabbour/contoso-names-e2e/actions/runs/4636235684/jobs/8203944300
Running the same locally using azd provision followed by azd deploy doesn't not reproduce the issue. This is specific to the GitHub Actions and/or running the Azure Developer CLI container.

Related to https://github.com/Azure/azure-dev/issues/1653

Duplicate of: https://github.com/Azure/azure-dev/issues/1740

@sabbour This is a really good find! Appreciate the write-up.
Took a quick look, and I can confirm the current implementation seems to be fetching the token during login, persisting the token:
https://github.com/Azure/azure-dev/blob/9cbad62811cbae78f18698253e126e7ee3a8526d/cli/azd/pkg/auth/manager.go#L443-L478
And reusing the stored token instead of providing a callback that allows for token exchange:
https://github.com/Azure/azure-dev/blob/9cbad62811cbae78f18698253e126e7ee3a8526d/cli/azd/pkg/auth/manager.go#L209-L210

@weikanglim  Not sure if its the same as the OIDC login timeout issue as part of pipelines. Any findings in this?

@rajeshkamal5050 It is the same. The findings are above. Took a second look at the code, it's a simple change. I'm going to assign it to myself.

So does one just call az login in a script somewhere and it will refresh the credentials? Or how does one solve this issue?

Hi @justinmchase , not sure about your use case, but the idea behind this change:

GitHub Actions integrates with Azure to offer federated credentials.
Federated credentials can be retrieved by using environment variables on the runner (ACTIONS_ID_TOKEN_REQUEST_URL and ACTIONS_ID_TOKEN_REQUEST_TOKEN), described in GitHub docs. The access token should be retrieved by querying ACTIONS_ID_TOKEN_REQUEST_URL using ACTIONS_ID_TOKEN_REQUEST_TOKEN. For a reference implementation, see a simplified implementation I made for a CLI project of mine: kusto-synced.

If you're using azd or az to fetch the configured credentials, the CLI should handle this for you.

It is definitely timing out and not handling it.
My use case is I use the azure login action, az cli works fine, then I run a very long running terraform apply and inside of that terraform apply I have some external resources that invoke bash scripts to do things the azurerm provider can do or doesn't do right and I have to invoke the az cli, which throws an expired token error.
If I use that snippet to first refresh the oidc token all is well again but the az cli is definitely not doing it automatically.

@justinmchase I see. It's possible that az handles this differently than azd, as described in this az comment. I'm not familiar with the az implementation, so we'll definitely need to work with the Azure CLI folks at Azure/login. I see that you've commented on the issue here: https://github.com/Azure/login/issues/180#issuecomment-1545459942. Can you add a workflow that reproduces the issue to https://github.com/Azure/login/issues/372 so that the team can better take a look at it? We should continue discussion there since it's az related.

Ok, I guess I thought azd was a debug build of az. I'll follow up over there I can probably reproduce by simply adding a sleep step. I'll try it out thanks.

Same issue here. Unable to use federated token's provided by Azure in azd inside a container. Seems like the "az  login" done via federated token can't be reused by  azd . Please support oidc token reuse from az cli or allow to use azd not only with for provider github but any idp supporting oidc


[stable/kube-ops-view] Not working with Kubernetes 1.16

Describe the bug
When upgrading the chart from 1.1.0 to 1.1.1 on a Kubernetes 1.16.2 cluster, I get an error.
Version of Helm and Kubernetes:
Kubernetes 1.16.2, Helm 2.14.3
Which chart:
kube-ops-view 1.1.0/1.1.1
What happened:
`
Error: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
Error: UPGRADE FAILED: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
`
What you expected to happen:
Upgrade successfully installed
How to reproduce it (as minimally and precisely as possible):
Upgrade (or install should also work) on any Kubernetes 1.16
Anything else we need to know:
This is known behavior; the deprecated resources with version v1beta1 have been removed from 1.16.  Upgrade the apiVersion to v1.  Might be an issue with other resources as well.

Same problem here.. Please update the chart to support Kubernetes 1.16+

Still not fixed, still a problem.

Still not fixed, still a problem


Set initial value of the input field

For use-cases where the postcode lookup might be using existing data (e.g. editing an address rather than adding as new) it would be useful to have the ability to set the initial value of the input field.

Hi,
Sorry, this would a confusing design. I'm the situation provided, the address data should be cleared and a new search initiated.
Also, it would be unlikely the new address would be in the same postcode.
Regards

What a strange response. How do you know what should happen in this situation? The library should provide flexibility for integrators to integrate it into their own workflows. Those workflows are not for you to dictate. I can 100% tell you that being able to lookup from an existing postcode is a completely valid and required real-life workflow.
Furthermore, the proposed change still allows for no initial value to be set (i.e. by default it doesn't change existing behaviour), so I can't really see any rationale for it to be rejected?


CB-7185 - Document MediaPlaybackAllowsAirPlay iOS preference

Pull in only when CB-7090 is complete.

Hi @shazron, the CB-7090 is completed, maybe it is time to merge docs?

yup.

already merged in apache repo, github mirror is taking some time to propagate

Please close this pull request, which is not auto closed.


Overnigth test failure: docker daemon not running

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Nov 28, 2018, 12:17
Job #126344894 failed for 2a8a3b19966a25eff30391e9f50dbe9610d20c33:

In GitLab by [Gitlab user @jjardon] on Nov 28, 2018, 12:17
changed title from Overnigth test failure: docker daemon not {-tunning Job-} to Overnigth test failure: docker daemon not {+running+}

In GitLab by [Gitlab user @valentindavid] on Nov 28, 2018, 21:22
The daemon is running on sled18. I think it is a hiccup where docker was to slow to response.

In GitLab by [Gitlab user @jjardon] on Nov 28, 2018, 21:28
Yeah, I think It's an intermitent issue, let's close and reopen if is permanent

In GitLab by [Gitlab user @jjardon] on Nov 28, 2018, 21:28
closed


Add new brokers

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[JOSS] BIDS option not implemented

openjournals/joss-reviews#6269

MRdataset version: 0.1.dev
Python version: 3.10.12
Operating System: Ubuntu 22.04.3 LTS

Description
I modify the jupyter notebook example and found the BIDS option is flagged as not implemented.
The documentation and the paper gave me the impression that at least the dicom and nifti options are available. This feature has to be added to fit the documentation, and the scope of the paper and the software should be clarified.
What I Did
from pathlib import Path
from MRdataset import import_dataset
import zipfile

MRdataset_root = Path(__name__).resolve().parents[1]
DATA_ARCHIVE = MRdataset_root / 'examples'/ 'example_bids_dataset.zip'
DATA_ROOT = Path('/tmp/')
with zipfile.ZipFile(DATA_ARCHIVE, 'r') as zip_ref:
    zip_ref.extractall(DATA_ROOT)
print((DATA_ROOT/'example_bids_dataset').exists())
dicom_dataset = import_dataset(data_source=DATA_ROOT/'example_bids_dataset',
                               ds_format='bids')

Output:
File [~/projects/reviews/MRdataset/MRdataset/common.py:130](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:130), in find_dataset_using_ds_format(dataset_ds_format)
    [128](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:128)     dataset_class = DicomDataset
    [129](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:129) else:
--> [130](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:130)     raise NotImplementedError(
    [131](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:131)         f'Dataset ds_format {dataset_ds_format} is not implemented. '
    [132](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:132)         f"Valid choices are {', '.join(VALID_DATASET_FORMATS)}")
    [133](https://file+.vscode-resource.vscode-cdn.net/home/haoting/projects/reviews/MRdataset/docs/~/projects/reviews/MRdataset/MRdataset/common.py:133) return dataset_class

NotImplementedError: Dataset ds_format bids is not implemented. Valid choices are dicom, bids

thanks for catching this Hao! it's a matter of integrating it within the newly redesigned MRdataset and protocol libraries.
also related to https://github.com/raamana/protocol/pull/6

Thanks Hao !
BIDSDataset is now included in a new PyPI release. Please try BIDS option again, it should work now.
pip install -U MRdataset --no-cache-dir --ignore-installed

Try the following code block. I have added configuration file, and the path to the example dataset. The same example is in the Jupyter notebook as well.
import zipfile
MRdataset_root = Path(__name__).resolve().parents[1]
DATA_ARCHIVE = MRdataset_root / 'MRdataset/tests/resources/example_bids_data.zip'
DATA_ROOT = Path('/tmp/')
with zipfile.ZipFile(DATA_ARCHIVE, 'r') as zip_ref:
    zip_ref.extractall(DATA_ROOT)
print((DATA_ROOT/'example_bids_dataset').exists())
bids_dataset = import_dataset(data_source=DATA_ROOT/'example_bids_dataset',
                               ds_format='bids')

Hi @sinhaharsh , the above might not work unless we make a new release that includes the BIDS dataset
I think Hao would have a BIDS dataset on her computer already - its better to target your instructions to a local path of a BIDS dataset

Also the ability to run on a test dataset is always a good thing to have!


Explore erasure coded rectangles

Summary
Instead of enforcing equal rows and columns, allow for rectangles which have columns twice the size of rows
Problem Definition
Imagine a set of transactions in a block that taking up 16 shares (including intershare padding). This is great because in a 4x4 square we have no tail padding. However, if the set of transactions takes up 17 shares, we need to double both axes, creating a grid of 8x8 = 64 shares. This means 47 shares are tail padding. If we allow rectangles with sides that are powers of 2. Then we can reduce tail padding. In this example, the rectangle would be 4x8 = 32. Which only means 15 shares of tail-padding.
Proposal
Allow for rectangles with sides powers of 2. We can represent this as the area in which the area can increment in multiples of 2 instead of multiples of 4.
A lot of the current code has the idea of a square baked in so this would be a difficult adjustment to make.
For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

How would the erasure-coded block look like?

Tail padding is a very small issue IMO since it's known simply by looking at the block header.


Install appropriate version of TestNg in user project depending on JDK version

Description
If JDK version is 11 or higher, we can still install release version of TestNg
Otherwise we should install 7.5 version as higher versions of this framework require JDK 11
https://groups.google.com/g/testng-users/c/BAFB1vk-kok
Context
This issue can be implemented after the increasing of intellij-gradle-plugin version from 2020.2

Additional current problem is that even if user already have properly installed Java 1.8 + TestNG 7.5 she still cannot select TestNG as test framework for test generation.


feat: borderRadius customization support.

Thank you for your contribution, i will review it and marge after that . 👍
On Sat, 16 Sep 2023 at 3:20 PM, Riajul Islam @.***>
wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/MohamedAshraf701/daynightbanner/pull/1
Commit Summary

b548327
https://github.com/MohamedAshraf701/daynightbanner/pull/1/commits/b5483274b127b1101fbfb023fd1a04d0d8d7d2d0
feat: borderRadius customization support.

File Changes
(1 file https://github.com/MohamedAshraf701/daynightbanner/pull/1/files)

M lib/src/banner.dart
https://github.com/MohamedAshraf701/daynightbanner/pull/1/files#diff-3ab206257c433ad49af50c6e1621de62c0263bc064918fbab17583e6ea6cf100
(26)

Patch Links:

https://github.com/MohamedAshraf701/daynightbanner/pull/1.patch
https://github.com/MohamedAshraf701/daynightbanner/pull/1.diff

—
Reply to this email directly, view it on GitHub
https://github.com/MohamedAshraf701/daynightbanner/pull/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWCCCSXBQLWUWYQXSEPHLQ3X2VY5XANCNFSM6AAAAAA42YZ6YI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Update checker.py

Missing install after pip.exe in line 46

Either use pip in place of wine, or wait till the requirements.txt is added

Check this out #10
I'll be adding a requirements.txtthis will be irrelevant, if you want go ahead and make the requirements file

Now its okay by Ekultek, :D


Proguard rules

Hi,
Any chance of posting Proguard rules for this lib?
Thanks

Let me know if you run into any issue with the proguarded version, pull requests are welcome.


raise Exception(f"failed to clonefile {src} to {full_dest}") when using a specific combination of apple_framework_packaging and link_dynamic = True

This is a bit 🤯 but hit this internally and managed to get it to repro in rules_ios:

Checkout this branch
Build this bazel build //tests/ios/app:TestAppWithInfoPlist --define=apple.experimental.tree_artifact_outputs=1

You'll hit this err:
ERROR: /Users/thiago/Development/rules_ios/tests/ios/app/BUILD.bazel:273:14: Bundling, processing and signing TestAppWithInfoPlist.__internal__.__test_bundle failed: (Exit 1): bundletool_experimental failed: error executing command (from target //tests/ios/app:TestAppWithInfoPlist.__internal__.__test_bundle)
  (cd /private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main && \
  exec env - \
    APPLE_SDK_PLATFORM=iPhoneSimulator \
    APPLE_SDK_VERSION_OVERRIDE=17.2 \
    XCODE_VERSION_OVERRIDE=<IP_ADDRESS>C65 \
  bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental bazel-out/ios-sim_arm64-min12.0-applebin_ios-ios_sim_arm64-dbg-ST-583c107f4262/bin/tests/ios/app/TestAppWithInfoPlist.__internal__.__test_bundle-intermediates/bundletool_control.json)
# Configuration: 2aae2c8b6c9a86c2bcbecbffdf541d35bd1e3ea9614340c49e0de0b26ab2c255
# Execution platform: @local_config_platform//:host
Traceback (most recent call last):
  File "/private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main/bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.runfiles/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.py", line 310, in <module>
    _main(sys.argv[1])
  File "/private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main/bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.runfiles/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.py", line 302, in _main
    bundler.run()
  File "/private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main/bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.runfiles/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.py", line 138, in run
    self._add_files(f['src'], f['dest'], f.get('executable', False),
  File "/private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main/bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.runfiles/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.py", line 170, in _add_files
    self._copy_file(fsrc, fdest, executable, bundle_root)
  File "/private/var/tmp/_bazel_thiago/122885c1fe4a2c6ed7635584956dfc9d/execroot/_main/bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-5a29d6cb7794/bin/external/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.runfiles/rules_apple~3.1.1/tools/bundletool/bundletool_experimental.py", line 226, in _copy_file
    raise Exception(f"failed to clonefile {src} to {full_dest}")
Exception: failed to clonefile bazel-out/ios-sim_arm64-min12.0-applebin_ios-ios_sim_arm64-dbg-ST-674860435576/bin/tests/ios/app/FW.framework/FW to bazel-out/ios-sim_arm64-min12.0-applebin_ios-ios_sim_arm64-dbg-ST-583c107f4262/bin/tests/ios/app/TestAppWithInfoPlist.__internal__.__test_bundle_archive-root/TestAppWithInfoPlist.xctest/Frameworks/FW.framework/FW
Target //tests/ios/app:TestAppWithInfoPlist failed to build

Notes:

Adding adding errno.EEXIST here in rules_apple bypasses the problem and since this seems to be an issue in rules_ios custom stuff (framework packaging rule and link_dynamic) I don't think we should propose anything upstream
In the repro branch, the AppWithInfoPlist_framework_unlinked mimics something we use internally (but similar to this one too)
In the repro branch actions that "fix" the issue (added comments in the repro branch too about this):

Not adding the *_framework_unlinked target as a dep
Setting link_dynamic = False
Commenting out this block (which is part of the link_dynamic logic)

Still investigating but any insights appreciated.

If I rebase the repro branch the issue is gone 🤔 (🎉 ?). It was a couple of commits behind so maybe the latest transitions related changes have fixed it.

Closing this as it's not happening in main anymore.


Remove float calculations in main.c/gettemp()

Hi, it's been a lot time I have not monitored the project.
Using float is generating more than 1K of code!
This version of gettemp only uses 80 bytes to return Celcius or Farenheit depending on CONF_C_F.
Some approximations are needed, I created an .ods file to check if approximation gives a valid result.

thanks!


feature: allow server switch network without service interruption

What this PR does / why we need it:
feature: allow server switch network between vpc and underlay network without service interruption

Does this PR need to be backport to the previous release branch?:

release/3.7
release/3.6

/cc @zexi

/hold

/hold cancel


⚠ Bofrost.lu has degraded performance

In 741fcc2, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2007 ms

Resolved: Bofrost.lu performance has improved in feb023e after 13 minutes.


libssl3: Ubuntu 22.04 version please

Ubuntu has switched to libssl3. I personally compiled tdlib but encountered runtime error when running the binary:
Error while reading RSA public key.
Could you compile it please?

Turned out that you can install libssl1 from older versions of Ubuntu. I don't know if it's ok, btw it just works.

Ow, that's painful.
How do you use the package? Using .NET or something else, like Node.js?
I am asking because for .NET I'll have to figure out how to pack different Linux artifacts into the same package. I think that should be possible, but I've never done that, yet.

That's kinda upstream and I should ask about it in tdlib/td/issues. Anyway for now we can use old ssl package, and let's wait for tdlib's next release.
And I'm personally using Node.js.
Thanks.

I think I'm ready to start working on libssl3 binaries (ubuntu 22.04-based), provided that tdlib itself is compatible with that version.

I have the same issue.
I made a temporary fix.
I'm made a fork of the code.
Changed the build agents to ubuntu-22.04 and referenced the output files directly.
I now have a working .net 8 application hosted on a linux azure app service.
Hoping for an official release


Regression: additionalProperties=boolean incorrectly reported as an error

Found in release 2.0.12.
The spec (Version 3.0.2) makes clear that it is valid for an object schema to specify "additionalProperties" as a boolean, either true or false. But now this setting causes the OpenAPIDeserializer to incorrectly report an error message. Possibly a defect caused by PR #1082.
See attached example. Parsing this file results in a bogus error message:
attribute paths.'/object'(post).parameters.[param0].schemas.additionalProperties is not of type `object`

object-0.json.txt

Hi @kerrykimbrough, can you please, send us the spec that produces that message so we can reproduce and fix. thanks

@gracekarina Did you try the object-0.json.txt file attached above?

Oops missed it. I will try and let you know. thanks.

I think this problem was introduced in commit fecc74792dbe5356e7db8969a48b24e7b3e6a484 with the fix for #1039 at this line:
 2035     ObjectNode additionalPropertiesNode = getObject("additionalProperties", node, false, location, result);

The getObject method is designed to be a kind of assertion that the given property node is an object; otherwise, it reports an error message. S it's incorrect to use it here when a non-object node is valid.

@gracekarina See PR #1100

merged! thanks


copy pipeline-svc install of yq to open-infra-deployment job

Discovered with the post merge job in https://github.com/openshift-pipelines/pipeline-service/pull/1010 that yq is not available in the base image provided by build-definitions
if this does not work, per discussion with @enarha I'll try awk, then either pin both images, or maybe @enarha tries his python idea
rh-pre-commit.version: 2.3.0
rh-pre-commit.check-secrets: ENABLED

@enarha came up with a sed based solution


Add react-peer-data and react-user-media

https://github.com/vardius/react-user-media
https://github.com/vardius/react-peer-data

Thanks!


make check fails

on Mac OS X Yosemite with graphene 1.2.4:
ERROR: quaternion - missing test plan
ERROR: quaternion - exited with status 134 (terminated by signal 6?)

Can you try running the quaternion test by itself, and see why it's aborting?

I get the following output:
/quaternion/init: OK
/quaternion/operators/invert: OK
/quaternion/operators/dot: **
Graphene:ERROR:quaternion.c:33:quaternion_operators_dot: assertion failed (graphene_quaternion_dot (&q1, &q2) == -3.f): (-3.87258632e+25 == -3)
Abort trap: 6

That's interesting. Which compiler did you use to build Graphene?

Clang
Op 14-aug.-2015 om 11:00 heeft Emmanuele Bassi <notifications<EMAIL_ADDRESS>het volgende geschreven:
That's interesting. Which compiler did you use to build Graphene?
—
Reply to this email directly or view it on GitHubhttps://github.com/ebassi/graphene/issues/41#issuecomment-131031477.

I think commit 7b9381a I just pushed to master fixes the issue.

Yes it did!
Thanks


[Test] Remove unnecessary custom settings

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@nmittler: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
cce7446fefdcf8d5ae269b0dee76d30835c208a1
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio


Path Parameter Error on ref

The build creates undefined object types using refs
To Reproduce
having the parameter id: in the path user/{id}
"/usert/{id}": {
"get": {
parameters": [
{
"in": "path",
"name": "id",
"required": true,
"schema": {
"$ref": "#/components/schemas/ObjectId"
}
}
],
}
}
Expected behavior
Conversion on the ObjectId reference to it's real type String
"ObjectId": {
"type": "string",
"pattern": "^[a-fA-F0-9]{24}$",
"example": "6148653375f4d9018966c771"
},
Library version used:
2.2.0
Additional context
dart error: Undefined class 'ObjectId'

@andrlange I'm not sure but could you please make flutter pub upgrade and than rerun generation?

Hi @andrlange , looks interesting. I will check it asap

Hi again @andrlange ,
The issue happens because your request does not have responses. this field is mandatory. If I put your example to swagger editor - error will occured.

So handle it add responses to your swagger request. For example:
"/usert/{id}": {       "get": {         "parameters": [           {             "in": "path",             "name": "id",             "required": true,             "schema": {               "$ref": "#/components/schemas/ObjectId"             }           }         ],         "responses": {           "200": {             "description": "Success",             "schema": {               "type": "array",               "items": {                 "$ref": "#/definitions/ObjectId"               }             }           }         }       }     }
Please let us know if it will not help.

I've generated code and it looks fine.
///   ///@param id   @Get(path: '/usert/{id}')   Future<chopper.Response<List<ObjectId>>> usertIdGet(       {@Path('id') required ObjectId? id});

Thanks for your super fast response. I have responses on my request but a after bumping json_serializable from 4.1.3 to 5.0.2 it works ...

@andrlange changelog upgraded accordingly.
Our mistake. Thx!


Readme is missing

Consider adding at least basic readme containing information with usage examples and possibilities.
Because for newcomers it is unclear which possibilities this package provide versus just parsing output of wmctrl subprocess.

Bump


IR-Lock

Does anyone know how to get the IR-Lock to work with GQC?
I've done all the set up for it using the PixyMon, but after that I can't find anything with integrating it on the px4 stack with the pixhawk. Was wondering what type of parameters I would have to set or does the IR-Lock start to work automatically.

@kevinlyu1 IRLock has a driver on firmware but the data of it is no being used still.

So basically the IR-Lock won't work on the px4 stack?

The driver is here: https://github.com/PX4/Firmware/blob/4453e4201b7a245cff52beeb38a293161aea4c48/src/drivers/irlock/irlock.cpp. From here to a implementation of usability there are some things that can be done (data logging, precision landing, data wrap to LANDING_TARGET msg). So the driver allows to get the data on the stack, but nothing is done besides the driver right now. You are welcomed to purpose a PR that implements that usage.

What do you mean by a PR?

Pull Request

Okay thanks!

@TSC21 Hey I am working on px4 and pixy camera using the irlock driver included in Firmware/src/drivers/irlock.
I was interested in contributing the usability features (data logging, data wrap to LANDING_TARGET msg) since I'll be needing them soon.
Can you point me to some existing drivers which I can use for reference to implement these features?
PS - For people working on the irlock. The driver is not compiled by default. You can add drivers/irlock to Firmware/cmake/configs/<target_board>.cmake along with other drivers. This would give you irlock command in the nsh terminal of px4.

@ShikherVerma check how other distance sensor drivers are implemented for example. But in this case you would want a landing_target uORB topic to publish to and use the data published to it to implement a precision landing procedure in mc_pos_control for example when LANDING mode is activated (or when a landing setpoint/waypoint is set and the vehicle is on MISSION mode).

@ShikherVerma I am also working on getting the IRLock working in PX4. We have modified the driver to publish its data on a uorb message. Currently I am working on implementing precision landing with it.
What are your goals with the IRLock?

I wanted to compare landing with IRLock w.r.t. landing with other techniques. So I would have to do the same things as you. Publish its data on a uorb message and implement precision landing with it. Can you link to your commits/branch where you have worked on irlock ?

https://github.com/ndepal/Firmware/tree/feature-precland
Consider this very much work in progress. While the estimator is tested a bit on hardware, I have not flown with it on hardware, only SITL.
I intend to open a PR that includes the driver changes, the beacon estimator, and a precision lander next week.
Would very much appreciate testers.


Function for generate an uuid v4

Propose a function implementation for create an UUID V4 on server side.
The name of the function is generateUUIDV4, doesn't take any argument and his return type is an UUID.
Some example case :
SELECT generateUUIDV4 => f4a8d299-3032-40dc-a19c-ceaf6d2fb336
The purpose of this function is to use mostly as a default value.
CREATE TABLE test IF NOT EXIST (
    uuid UUID DEFAULT generateUUIDV4(),
    data String
) Engine = Memory;

INSERT INTO test (data) VALUES('test1');
INSERT INTO test (data) VALUES('test2');
INSERT INTO test (data) VALUES('test3');
INSERT INTO test (data) VALUES('test4');
INSERT INTO test (data) VALUES('test5');
INSERT INTO test (data) VALUES('test6');

SELECT data, uuid FROM test;
test1, 368693a3-deea-42da-9de9-21782cc8d1c6
test2, 9eb2f472-6f63-4d1f-ab0b-0e4bfdf7b515
test3, 2dab3f49-5716-48e5-94b4-8fa5fb6d141c
test4, e1ae40e7-0258-4337-a4e2-eae69a05666b
test5, e8306243-eefd-407c-a92b-10165028dddc
test6, d7b78961-14ce-4cf4-9b72-5fd54fec246d

The implementation of UUID follow the RFC 4122
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Mostly Ok.

I prefer the function to be named with lowercase v: generateUUIDv4.
Because in similar abbreviations, v is also traditionally in lowercase. Examples: IPv4, IPv6.

Method RandImpl::execute now assumes, that sizeof(T) divide sizeof(ReturnType). This looks unnatural. We could do better. For example, RandImpl::execute should take ReturnType * output, size_t output_size parameters... and no template required. And also you could extract this method and implement both RandImpl and Rand64Impl on top of it, to avoid code duplication.

PS. Also you could use name generateRandomUUID instead of generateUUIDv4. This will clearly state the type of UUID algorithm. This is up to your choice, generateUUIDv4 is also Ok :)

Ok, should be could now. :)
I let the name generateUUIDv4 because some library who encapsulate UUID V4 use some components of the UUID V4 algorithm (for determine the version). Name it generateRandomUUID can be a little ambiguous because we can think than every bits of the UUID are random, who it's not totally the case on UUID V4. :)

Ok, thanks!


Dead link  https://visualstudiogallery.microsoft.com/7d745871-cf6a-47cd-a614-8453fa91f608/file/79318/1/Misc Windows 8 storyboard.sbsx

Found in docs/work/backlogs/office/add-share-storyboard-shapes.md

@nschonni - Thank you for reporting this issue. I'm fixing the content and it should be live later today.


Auto-merge Backport PRs in documentation-website repo

Is your feature request related to a problem? Please describe
The Backport tool, while efficient, can occasionally cause friction when a maintainer forgets to merge a PR. Furthermore, the documentation-website repo currently requires that all PRs be "approved", including Backports, which means that maintainers need to take an extra-step to merge a Backport PR even when that PR has passed all checks.
Describe the solution you'd like

Remove the requirement for Backport PRs to require approvals, if possible.
If a Backport PR passes all pipeline and implementations tests, automatically merge that PR upon approval.

Describe alternatives you've considered
We've considered turning on the auto-merge feature for all PRs. However, the quality-control process for documentation PRs prevents us from auto-merging PRs to the main branch, since all PRs must not only pass code-review, but also editorial review. This means that, even though a PR may technically pass GitHub's and organizations requirements for merging, it might not pass the documentation teams quality requirements.
Additional context
For additional information, see https://github.com/opensearch-project/documentation-website/issues/6305

@rishabh6788 will discuss with @Naarcha-AWS to understand the requirements.

Have discussion with @Naarcha-AWS offline and will take a look with auto approval before auto merging.
Thanks.

Added backport remove rule so they can properly remove the branches now.

Will remove these:

  origin/backport/backport-1825-to-1.3
  origin/backport/backport-1834-to-1.3
  origin/backport/backport-2143-to-1.3
  origin/backport/backport-2171-to-1.3
  origin/backport/backport-2342-to-1.3
  origin/backport/backport-2354-to-1.3
  origin/backport/backport-2355-to-1.3
  origin/backport/backport-2360-to-2.4
  origin/backport/backport-2371-to-1.3
  origin/backport/backport-2377-to-1.3
  origin/backport/backport-2385-to-1.3
  origin/backport/backport-2409-to-2.4
  origin/backport/backport-2427-to-1.3
  origin/backport/backport-2449-to-2.3
  origin/backport/backport-2454-to-1.3
  origin/backport/backport-2457-to-1.3
  origin/backport/backport-2458-to-1.3
  origin/backport/backport-2492-to-1.3
  origin/backport/backport-2513-to-1.3
  origin/backport/backport-2518-to-1.3
  origin/backport/backport-2544-to-1.3
  origin/backport/backport-2555-to-1.3
  origin/backport/backport-2557-to-1.3
  origin/backport/backport-2564-to-1.3
  origin/backport/backport-2571-to-1.3
  origin/backport/backport-2599-to-1.3
  origin/backport/backport-2630-to-1.3
  origin/backport/backport-2640-to-1.3
  origin/backport/backport-2641-to-1.3
  origin/backport/backport-2653-to-1.3
  origin/backport/backport-2658-to-1.3
  origin/backport/backport-2668-to-1.3
  origin/backport/backport-2730-to-2.6
  origin/backport/backport-2750-to-1.3
  origin/backport/backport-2762-to-2.4
  origin/backport/backport-2824-to-1.3
  origin/backport/backport-2828-to-1.3
  origin/backport/backport-2829-to-1.3
  origin/backport/backport-2880-to-2.4
  origin/backport/backport-2885-to-2.4
  origin/backport/backport-2885-to-2.5
  origin/backport/backport-2927-to-1.3
  origin/backport/backport-2941-to-1.3
  origin/backport/backport-2946-to-1.3
  origin/backport/backport-2946-to-2.4
  origin/backport/backport-2962-to-1.3
  origin/backport/backport-2999-to-1.3
  origin/backport/backport-3004-to-1.3
  origin/backport/backport-3007-to-1.3
  origin/backport/backport-3025-to-2.4
  origin/backport/backport-3035-to-1.3
  origin/backport/backport-3052-to-1.3
  origin/backport/backport-3054-to-1.3
  origin/backport/backport-3069-to-1.3
  origin/backport/backport-3085-to-1.3
  origin/backport/backport-3086-to-1.3
  origin/backport/backport-3097-to-1.3
  origin/backport/backport-3106-to-1.3
  origin/backport/backport-3119-to-1.3
  origin/backport/backport-3127-to-1.3
  origin/backport/backport-3144-to-1.3
  origin/backport/backport-3146-to-1.3
  origin/backport/backport-3170-to-1.3
  origin/backport/backport-3200-to-1.3
  origin/backport/backport-3230-to-1.3
  origin/backport/backport-3250-to-1.3
  origin/backport/backport-3252-to-1.3
  origin/backport/backport-3253-to-1.3
  origin/backport/backport-3350-to-1.3
  origin/backport/backport-3380-to-1.3
  origin/backport/backport-3426-to-1.3
  origin/backport/backport-3428-to-1.3
  origin/backport/backport-3433-to-1.3
  origin/backport/backport-3467-to-1.3
  origin/backport/backport-3547-to-2.6
  origin/backport/backport-3550-to-2.6
  origin/backport/backport-3584-to-1.3
  origin/backport/backport-3615-to-1.3
  origin/backport/backport-3637-to-1.3
  origin/backport/backport-3645-to-1.3
  origin/backport/backport-3709-to-1.0
  origin/backport/backport-3709-to-1.1
  origin/backport/backport-3709-to-1.2
  origin/backport/backport-3709-to-1.3
  origin/backport/backport-3759-to-1.3
  origin/backport/backport-3775-to-1.3
  origin/backport/backport-3785-to-1.3
  origin/backport/backport-3789-to-1.3
  origin/backport/backport-3812-to-1.3
  origin/backport/backport-3964-to-1.3
  origin/backport/backport-3995-to-1.3
  origin/backport/backport-4029-to-2.7
  origin/backport/backport-4038-to-2.4
  origin/backport/backport-4044-to-1.3
  origin/backport/backport-4101-to-1.3
  origin/backport/backport-4106-to-1.3
  origin/backport/backport-4126-to-1.3
  origin/backport/backport-4149-to-1.3
  origin/backport/backport-4161-to-2.7
  origin/backport/backport-4218-to-1.3
  origin/backport/backport-4218-to-2.7
  origin/backport/backport-4224-to-2.8
  origin/backport/backport-4241-to-1.3
  origin/backport/backport-4268-to-1.3
  origin/backport/backport-4302-to-1.0
  origin/backport/backport-4302-to-1.1
  origin/backport/backport-4302-to-1.2
  origin/backport/backport-4302-to-1.3
  origin/backport/backport-4310-to-2.7
  origin/backport/backport-4313-to-1.3
  origin/backport/backport-4348-to-1.3
  origin/backport/backport-4349-to-2.8
  origin/backport/backport-4352-to-1.3
  origin/backport/backport-4363-to-1.3
  origin/backport/backport-4390-to-1.3
  origin/backport/backport-4392-to-1.3
  origin/backport/backport-4424-to-1.3
  origin/backport/backport-4434-to-1.3
  origin/backport/backport-4436-to-1.3
  origin/backport/backport-4463-to-2.5
  origin/backport/backport-4512-to-1.3
  origin/backport/backport-4530-to-1.3
  origin/backport/backport-4543-to-2.8
  origin/backport/backport-4558-to-1.3
  origin/backport/backport-4560-to-1.3
  origin/backport/backport-4591-to-1.3
  origin/backport/backport-4619-to-1.3
  origin/backport/backport-4655-to-1.3
  origin/backport/backport-4656-to-1.3
  origin/backport/backport-4664-to-1.3
  origin/backport/backport-4665-to-1.3
  origin/backport/backport-4693-to-1.3
  origin/backport/backport-4740-to-1.3
  origin/backport/backport-4768-to-1.3
  origin/backport/backport-4772-to-1.3
  origin/backport/backport-4787-to-1.3
  origin/backport/backport-4789-to-1.3
  origin/backport/backport-4790-to-1.3
  origin/backport/backport-4821-to-1.3
  origin/backport/backport-4822-to-1.3
  origin/backport/backport-4836-to-1.3
  origin/backport/backport-4851-to-1.3
  origin/backport/backport-4856-to-1.3
  origin/backport/backport-4880-to-1.3
  origin/backport/backport-4892-to-1.3
  origin/backport/backport-4921-to-1.3
  origin/backport/backport-4970-to-1.3
  origin/backport/backport-5019-to-2.1
  origin/backport/backport-5019-to-2.2
  origin/backport/backport-5019-to-2.3
  origin/backport/backport-5063-to-1.3
  origin/backport/backport-5084-to-1.3
  origin/backport/backport-5208-to-1.3
  origin/backport/backport-5242-to-1.3
  origin/backport/backport-5272-to-1.3
  origin/backport/backport-5299-to-1.3
  origin/backport/backport-5320-to-1.3
  origin/backport/backport-5340-to-1.3
  origin/backport/backport-5378-to-2.8
  origin/backport/backport-5432-to-1.3
  origin/backport/backport-5458-to-1.3
  origin/backport/backport-5580-to-1.3
  origin/backport/backport-5619-to-1.3
  origin/backport/backport-5619-to-2.9
  origin/backport/backport-5628-to-2.9
  origin/backport/backport-5667-to-2.10
  origin/backport/backport-5667-to-2.11
  origin/backport/backport-5667-to-2.9
  origin/backport/backport-5669-to-1.3
  origin/backport/backport-5669-to-2.0
  origin/backport/backport-5669-to-2.1
  origin/backport/backport-5669-to-2.10
  origin/backport/backport-5669-to-2.11
  origin/backport/backport-5669-to-2.2
  origin/backport/backport-5669-to-2.3
  origin/backport/backport-5669-to-2.4
  origin/backport/backport-5669-to-2.5
  origin/backport/backport-5669-to-2.6
  origin/backport/backport-5669-to-2.7
  origin/backport/backport-5669-to-2.8
  origin/backport/backport-5669-to-2.9
  origin/backport/backport-5724-to-2.11
  origin/backport/backport-5725-to-1.3
  origin/backport/backport-5768-to-1.3
  origin/backport/backport-5824-to-1.3
  origin/backport/backport-5827-to-1.3
  origin/backport/backport-5844-to-1.3
  origin/backport/backport-5924-to-1.3
  origin/backport/backport-5969-to-2.10
  origin/backport/backport-5969-to-2.7
  origin/backport/backport-5969-to-2.8
  origin/backport/backport-5969-to-2.9
  origin/backport/backport-5978-to-1.3
  origin/backport/backport-6048-to-1.3
  origin/backport/backport-6069-to-1.3
  origin/backport/backport-6108-to-1.3
  origin/backport/backport-6137-to-1.3
  origin/backport/backport-6151-to-1.3
  origin/backport/backport-6194-to-1.3
  origin/backport/backport-6208-to-1.3
  origin/backport/backport-6307-to-1.3
  origin/backport/backport-6380-to-2.12
  origin/backport/backport-6427-to-1.3
  origin/backport/backport-6452-to-1.3
  origin/backport/backport-6470-to-1.3
  origin/backport/backport-6582-to-1.3
  origin/backport/backport-6717-to-2.7
  origin/revert-2959-backport/backport-2958-to-2.3
  origin/revert-3841-backport/backport-3807-to-2.0
  origin/revert-3885-backport/backport-3807-to-2.6
  origin/revert-3886-backport/backport-3807-to-2.5
  origin/revert-3887-backport/backport-3807-to-2.4
  origin/revert-3888-backport/backport-3807-to-2.3
  origin/revert-3889-backport/backport-3807-to-2.2
  origin/revert-3890-backport/backport-3807-to-2.1
  origin/revert-5541-backport/backport-5113-to-2.11
  origin/revert-5543-backport/backport-5113-to-2.10
  origin/revert-5544-backport/backport-5543-to-2.9

The github settings of automerge is more on specific PR not on all PRs matching a condition:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge

Still prefer flow:
Add backport label -> Backport PR created -> assume trigger bot token -> Approve by trigger bot -> Wait for status check to complete -> Automerge -> Remove backport branch.

Still prefer flow: Add backport label -> Backport PR created -> assume trigger bot token -> Approve by trigger bot -> Wait for status check to complete -> Automerge -> Remove backport branch.

We'd also like to receive some kind of notification if there is a merge conflict on the backport PR.

Still prefer flow: Add backport label -> Backport PR created -> assume trigger bot token -> Approve by trigger bot -> Wait for status check to complete -> Automerge -> Remove backport branch.

We'd also like to receive some kind of notification if there is a merge conflict on the backport PR.

That notification will appear if the status checks don't complete, I believe.

Will need to tweak the backport workflow source code to add a label, or find the PR number and use gh to add a label through workflow files.
https://github.com/VachaShah/backport

New flow PR:
https://github.com/opensearch-project/documentation-website/pull/6892#issuecomment-2038342821

New backport automerge:

https://github.com/opensearch-project/documentation-website/pull/6893

This is completed now for docs team.
All the other repos changes will be in META:

https://github.com/opensearch-project/opensearch-build/issues/4608

Thanks.


Fix load defaults

@hltbra @spulec This addresses two errors, #5 and #6, to avoid resetting the current_limit as well as an error displaying the data when the current_limit is 0. I am not sure the latter will ever be the case, but I came across it as I was working on the refresh_data call.

LGTM

LGTM


👷 Add automated frontend release process workflow

TL;DR
This PR adds an automated release process for the frontend code.
What changed?
A new Github Action workflow file frontend-release.yaml has been added. This workflow triggers on a push to the main branch with changes in the frontend/ directory. It compares the current version in package.json with the latest release tagged on Github. If the version has changed, it creates a new release.
How to test?
To test, make a change in the frontend directory that updates the version in package.json, then push to main. Check the 'Actions' tab on Github to see the workflow run and the 'Releases' tab to see the new release.
Why make this change?
This change automates the release process, reducing the likelihood of human error and simplifying the release process for new changes.

#120
#119  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mingi3314 and the rest of your teammates on  Graphite

Merge activity

Apr 14, 11:20 AM EDT: @mingi3314 started a stack merge that includes this pull request via Graphite.


Roszypal schlaffman notebook

Here is the Notebook about Rozsypal-Schlaffman's experiment, as well as the Notebook for GenIncProcessModel.

Thanks!  Will look at it tomorrow


Bug: Fixing link pointing to a bad URL

Detected error on kubevirt-Tutorial tests

Fixing link for Lab001 and the URL for RSA file

/kind bug


Update or replace django-dotenv

We use the package django-dotenv in edx/openedxstats. This package was last released in 2017 and it hasn't yet added support for Django3.2. Please follow the guidance in https://openedx.atlassian.net/wiki/spaces/AC/pages/3036972032/Handling+Outdated+Dependencies to resolve the problem this poses for the Open edX Django 3.2 upgrade.

Hi, I want to take this one. We can switch to django-environ-2

@shimulch Thank you so much for reaching out. I will assign this to you. Please let me know once this is done.

@natabene Opened https://github.com/edx/openedxstats/pull/112

edx/openedxstats#112 was Merged. @Jawayria Do we consider it Done now?

Yes its Done.

As per the discussion, it looks like django-environ2 was dropped in favour of django-environ and django-environ now has Django 3.2 support as well. I would like to reopen this issue for now to replace django-environ2 with django-environ. For reference the PR https://github.com/openedx/blockstore/pull/128 can be referenced.

@shimulch  since you worked on this issue before, would you like to pick this up again to replace django-environ-2 with django-environ?


How to run this example?

Hi!
My steps:

I use postgres: npm i sails-postgresql --save
Line 69 in config.js: development: require("sails-postgresql") and comment line 14 in app.js
Change db and port in config.js
npm start. Output:

'undefined' not recognised. Not good, setting to .any()
Server running at: http://sogl.local:1811

What does the first line mean?
5. Output in browser:
{"errors":{"title":"Not Found","status":404}}

What next? I need to create models/blueprints the same as table names in DB?
I think this example need some test DB data :blush:
Env:
node 4.2.1
npm 3.3.12
OS X 10.10.5

Hey @Sogl, if you go to http://sogl.local:1811/docs you'll see the Swagger docs. I've got a seed module nearly ready to be published to help get started :) I'll publish it shortly.

@Sogl
There is now a seed module which will create random data and write to the DB in a "development" environment, see https://github.com/Multicolour/multicolour-example/blob/master/app.js#L14.
:boom:


[stable/mm-te] adding recommended label

What this PR does / why we need it:
adding recommended label
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/lgtm


react-toolbox and Metor

Hi!
i am trying to make a new project with meteor but i cannot make sass work: what should i install? how should i configure it?

See: https://github.com/nathantreid/meteor-react-toolbox-example

Remember that using sass is now optional. Of course you'd need to compile the styles yourself into plain CSS and provide a module with mappings using ThemeProvider but still, you can avoid it.
I have no experience with meteor, hopefully the link would help you. I'm gonna close :)

The link https://github.com/nathantreid/meteor-react-toolbox-example don't work with Meteor <IP_ADDRESS>- How i can install this excellent resource in Meteor?

Not sure, I have no idea how Meteor works.. but if you have the theming concepts clear enough you should be able to configure it with just any project

No. I tried but with no success.
Sadly

What's the issue?

After following the instructions from the example @hmontes posted, you need to modify the instructed package.json additions.
Here is how to make react-toolbox play nice with Meteor.
meteor npm install --save-dev<EMAIL_ADDRESS>meteor add<EMAIL_ADDRESS>Add this to your package.json:
"cssModules": {
	"extensions": ["scss", "css"],
	"enableSassCompilation": ["scss"],
 "globalVariables": [
    "node_modules/react-toolbox/lib/_colors.scss",
	    {
	      "theme-building": true
	    },
	    "client/toolbox-theme.scss"
	  ]
	}

You need to include both scss and css in your extensions option.


Add the SILKY_JSON_ENSURE_ASCII configuration item to support Chinese

Support for users to configure the SILKY_JSON_ENSURE_ASCII parameter to implement json.dumps support Chinese

Could you add a new tests which sets this settings to false?

I'm sorry, but as a python novice, I don't really know how to add this feature. Also, I don't have time to do this right now, but it works fine on my project

Feel free to do it when you have time. Use this decorator to override settings for a test. https://docs.djangoproject.com/en/dev/topics/testing/tools/#overriding-settings


Refactor ClusterManager to call map.setOnCameraIdleListener internally

Is your feature request related to a problem? Please describe.
Mentioned in https://github.com/googlemaps/android-maps-ktx/pull/29#discussion_r402459201.
All of the clustering demos currently look like this:
clusterManager = new ClusterManager<>(this, map);
map.setOnCameraIdleListener(clusterManager);

...which I believe aligns with the majority of use cases of ClusterManager for dynamic clustering based on the map viewport. If a developer doesn't include the 2nd line of code, the clusters won't be re-clustered when the map viewport changes and settles.
Describe the solution you'd like
To make it easier for developers, we could move the registration of GoogleMap.OnCameraIdleListener within ClusterManager to avoid apps having to add this code themselves.
However, I do see use cases for static clustering, where an app wants to show markers and clustering, but not have this change based on the map viewport. If we do change to registering the GoogleMap.OnCameraIdleListener by default, this would be a breaking change for anyone doing static clustering.
So, a new implementation would need to:

Support both dynamic (listening to the camera) and static (not listening to the camera) clustering
Be a major version release due to breaking behavior

Feedback from developers on how they use ClusterManager is welcome! Especially whether you always call map.setOnCameraIdleListener(clusterManager);.
Describe alternatives you've considered
Do nothing - leave code as-is
Additional context
Mentioned in https://github.com/googlemaps/android-maps-ktx/pull/29#discussion_r402459201

Another improvement related to this that can be made is to add an OnCameraIdleListener property within ClusterManager that can be set via setOnCameraIdleListener. ClusterManager can internally set itself as the GoogleMap's OnCameraIdleListener, and if any other listeners are attached within ClusterManager. So, the implementation of onCameraIdle() with ClusterManager would change to:
@Override public void onCameraIdle() {
    if (mRenderer instanceof GoogleMap.OnCameraIdleListener) {
        ((GoogleMap.OnCameraIdleListener) mRenderer).onCameraIdle();
    }
    mAlgorithm.onCameraChange(mMap.getCameraPosition());

    // delegate clustering to the algorithm
    if (mAlgorithm.shouldReclusterOnMapMovement()) {
        cluster();
        // Don't re-compute clusters if the map has just been panned/tilted/rotated.
    } else if (mPreviousCameraPosition == null || mPreviousCameraPosition.zoom != mMap.getCameraPosition().zoom) {
        mPreviousCameraPosition = mMap.getCameraPosition();
        cluster();
    }

    // This will be added
    if (onCameraIdleListener != null) {
        onCameraIdleListener.onCameraIdle();
    }
}

This way, clients can have additional custom behavior when the camera goes idle.

@barbeau any thoughts on the suggestion above?

One improvement that can be made related to this is to add an OnCameraIdleListener property within ClusterManager that can be set via setOnCameraIdleListener.

I agree with this improvement 👍

We should probably bias towards the common use-case which you alluded to—dynamic clustering. If static clustering is desired, we can document that or even provide another example in the demo app for it.

I agree. This would be considered breaking behavior, though, for those that currently have static clustering implemented.

Still valid


Deletes Select queries, updates docker images, docs and tests

Delete Select queries. Since Druid 0.17.0, it has been removed and replaced by the Scan query
Update docker images:

Druid 0.18.0
Zookeeper 3.5.7

Update documentation and unit tests

Thank you for this PR! The docker images all build, the tests all run, and it's a nice cleanup. This is all in order and ready to go.
@krisgeus this is ready to merge.
@anskarl as far as I am concerned, you're more than welcome to add yourself to developers in ThisBuild if you want.

@barend thank you for reviewing the PR. I would be grateful to be included in the list of developers, I will add one more commit for this change.


Unable to Login directly from driveplayer.com on Desktop

Expected Behavior
When clicking the "Add Audio Files from Google Drive" button, expected the Login popup to reroute to the Google account page, listing all available google accounts to choose from.
Actual Behavior
When clicking the "Add Audio Files from Google Drive" button, the resulting popup is unable to bring up available Google accounts to choose from. This only happens on Desktop mode, mobile is working properly.
Steps to Reproduce the Problem

Go directly to driveplayer.com on Desktop mode, not through Google Drive.
Click the "Add Audio Files from Google Drive" button
Login widget will appear and immediately fail.

Specifications

Browser: Google Chrome, Safari
OS: Mac

This damned thing has been dead in the water for every device and machine I own for at least the past year and a half...no one seems to even be managing it anymore...waste of such a once great thing.


Specifying dates with padding zeros to run algo causes error in some systems

In some systems this command fails:
catalyst run -f buy_and_hodl.py --start 2015-03-01 --end 2017-06-28 --capital-base 100000 -o bah.pickle
while this succeeds:
catalyst run -f buy_and_hodl.py --start 2015-3-1 --end 2017-7-25 --capital-base 100000 -o bah.pickle
While we are investigating this issue, if you encounter this error, use the second command.

Cannot replicate this error, may have been misreported due to a misguiding error message that relates to issue #16. Thus, closing it for now.


World gen mappings for 1.18 experimental snapshot 2

I tried mapping some of the things used by the new multi noise biome source.
I know they are unlikely to stay once we get normal snapshots, but they could be useful anyway.

I didnt say that we wont port from them, I said I dont want to promise it. I need to talk to player about figuring out if we can generate intermediaies from 2 match files as in theory its possible.
If that fails we can think again to see if its possible to save the names, but again it might be impossible so dont want to guarantee it.

If that fails we can think again to see if its possible to save the names, but again it might be impossible so dont want to guarantee it.

If 1.18 snapshots don't get matched from this version, I can also just manually port my mappings.
Also, what should we name method_37727? I accidentally named it addFixedValue, because I thought it was the method that took a float and created a FixedFloatFunction. But it actually just directly calls the private add method, probably for future-proofing.
I considered add2, but that isn't a good name. Maybe something like addFunction?

I am pretty sure now this is modeled to be a simple hypercube so it can be easily plugged in to be solved (probably with least squares, didn't check). The sentence is now redundant and should be removed.

I am pretty sure now this is modeled to be a simple hypercube so it can be easily plugged in to be solved (probably with least squares, didn't check). The sentence is now redundant and should be removed.

Actually, maybe the sentence was wrong before 1.18 too. There, offset is used in the same way as now. But it doesn't "favor larger differences", because setting offset to something that's not 0 makes the biome smaller, not larger.

So, is this good then?


I have all the pictures in a folder titled Europe inside /static. I need to get the src's of the images into an array, so I can do this:
`
         var childElements = this.props.photos.map(function(element) {
               return (

            );
        });

`
I'm trying this:
import Images from "/static/Europe/*.jpg"
but it is not working.
How would I import all *.jpgs into an array ?

We have an example in the repo to import static files to get the URL using a Babel plugin but I think it only works while importing each file individually.
With Next.js we don't support importing images the way you want.

You could add a build step outside of Next that turns the directory into a json file and import that in your app 👍


Microsoft.VisualStudio.Workload.NetCoreTools vs Microsoft.VisualStudio.Workload.NetWeb

Hey,
There is no different between Microsoft.VisualStudio.Workload.NetCoreTools and Microsoft.VisualStudio.Workload.NetWeb (based on doc), why there is 2 entries for them?
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b29a1009-5ef4-707b-258e-fe8bbe7275b6
Version Independent ID: 00fac5a7-fc6d-c9cb-2d26-d820c7055890
Content: Visual Studio Enterprise 2017 workload and component IDs - Visual Studio
Content Source: docs/install/workload-component-id-vs-enterprise.md
Product: visual-studio-dev15
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@dehghani-mehdi Thanks for your feedback. The "ID: Microsoft.VisualStudio.Workload.NetCoreTools" for .NET Core cross-platform development workload and the ID: Microsoft.VisualStudio.Workload.NetWeb for [ASP.NET and web development](.NET Core cross-platform development) workload include the same components initially, but diverge after the Microsoft.VisualStudio.Component.VisualStudioData component.
There is purposeful repetition on the page because the data is sorted by workloads, and some workloads share the shame components.

@TerryGLee you're welcome, thanks for the answer.
If I want to develop using .Net core and .Net Framework, I have to select both, even if they share same components?
I created local cache (aka offline installer) and for now I add both, but I want to remove one of them if is possible, that's why I asking this.

@dehghani-mehdi  If you are installing by choosing individual components, you do not have to choose the same components again.
However, it looks like your question has expanded beyond a documentation issue to a support request. If you require further information, we have other venues for you, as listed in the "Get Support" section of any installation-related page in our documentation.
Specifically, please consider using one of the following two venues:

Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.
We also offer a live chat (English only) support option  for installation-related issues.

Thanks,
~ Terry


[All Hosts] (dialog) preview of modal dialog API

Docs Build status updates of commit 8683a49:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/develop/modal-dialog.md
:warning:Warning
View
Details

docs/develop/dialog-api-in-office-add-ins.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/develop/modal-dialog.md

Line 22, Column 27: [Warning: file-not-found - See documentation] Invalid file link: 'dialog-api-in-offfice-add-ins.md'.

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

Docs Build status updates of commit 9ef6e05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/dialog-api-in-office-add-ins.md
:white_check_mark:Succeeded
View

docs/develop/modal-dialog.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Adding to backlog. Closing PR.


(v5.2.0beta1) Missing words in instructions

@chrisoro I assume an API key is needed, but the language is missing:
https://github.com/aeon0/d4lf/blob/638d639c83af10d6cc3f8234bf7e98dab3e366b0/src/gui/qt_gui.py#L219

What do you mean by that?

Sorry, hopefully this makes what I mean clearer. It looks like there are just some words missing for the d4builds instructions:
"For d4builds you need to specify your     in the params.ini file"
                                        ^

I also don't see any documentation in the params.ini section of the readme for d4builds.

Understood. missing word is 'browser'. will fix it


Arccos(e) hangs

The loop at line 430 in InternalAMExtensions.cs

if (x.Equals(EDecimal.One)) return consts.HalfPi;

had to be replaced by
if ((x - EDecimal.One).Abs().LessThan(MathS.Settings.PrecisionErrorZeroRange))
    return consts.HalfPi;


Add generator version

Since serialFizzBuzzMasked assumes input array contains ordered natural numbers it would be fair to ask to add the implementation that simply generates the answer without SIMD magic:
    public int[] serialFizzBuzzGenerate(int[] values) {
        int[] result = new int[values.length];

        for (int i = 0; i < result.length; i++) result[i] = i+1;
        for (int i = 2; i < result.length; i+=3) result[i] = FIZZ;
        for (int i = 4; i < result.length; i+=5) result[i] = BUZZ;
        for (int i = 14; i < result.length; i+=15) result[i] = FIZZ_BUZZ;

        return result;
    }

which produces not-bad results on my machine (jdk8, simd implementations commented out):
Benchmark                                 (arrayLength)   Mode  Cnt        Score        Error  Units
FizzBuzzBenchmark.scalarFizzBuzz                    256  thrpt    5  1148996.962 ± 160573.348  ops/s
FizzBuzzBenchmark.scalarFizzBuzzGenerate            256  thrpt    5  3872721.370 ± 955531.765  ops/s
FizzBuzzBenchmark.scalarFizzBuzzMasked              256  thrpt    5  2499039.637 ± 248389.527  ops/s

Ah, very nice! Could you perhaps create a PR for adding this?


Use nullabillity in Kotlin

The prerequisites of this codelab mention "knowledge of Kotlin classes, including how to access methods and properties from a variable ". The codelab featuring classes and such doesn't come for later on in the course (it's actually the next lesson). Perhaps these two lessons should be swapped places so the prerequisites for Use Nullabillity in Kotlin can be met effectively?

(Prerequisites for Use Nullabillity in Kotlin. Note 3rd item)

(Codelabs in current order)

@BelenSeoane
Thank you for reaching out to us. Your feedback has been taken into consideration and followed by changes in prerequisites section:


Module not found: Can't resolve 'apollo-client'

Describe the bug
Error when starting React app with generated code:
Failed to compile.

<EMAIL_ADDRESS>Module not found: Can't resolve 'apollo-client' in '/Users/rahul/dev/projects/axcio/packages/frontend-react/node_modules/@apollo/react-hooks/lib'

To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

# Put your schema here

My GraphQL operations:

# Put your operations here

My codegen.yml config file:

# Put your YML here

Expected behavior

Environment:

OS:
@graphql-codegen/...:
NodeJS:

Additional context
I can fix this myself by editing the generated code from:
import * as ApolloReactHooks from '@apollo/react-hooks';

to:
import * as ApolloReactHooks from '@apollo/client';

See: https://github.com/apollographql/apollo-client/issues/5808

While there does not seem to be a version that supports the apollo-client 3.0 beta, you can adjust the import statements through config parameters (there's a suprising amount of configuration possible!):
codegen.yml:
generates:
  src/:
    config:
      apolloReactHooksImportFrom: "@apollo/client"
      apolloReactCommonImportFrom: "@apollo/client"

As @Gonozal said, you can easily customize it. Also you should set reactApolloVersion: 3 if you use v3 of Apollo.

As @Gonozal said, you can easily customize it. Also you should set reactApolloVersion: 3 if you use v3 of Apollo. (https://graphql-code-generator.com/docs/plugins/typescript-react-apollo)

See here... https://graphql-code-generator.com/docs/generated-config/typescript-react-apollo#reactapolloversion-2--3-default-value-2