Battle Held Items

Description
These are held-items, and their respective effects, that need to be programmed.
Details
A lot of the items that need their logic implemented can re-use the same logic of other items.
Item List

[x] Absorb Bulb - If the holder is hit by a Water-type damaging move, this item is consumed, and its Special Attack is increased by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Adrenaline Orb - If the holder is affected by Intimidate (or not affected via Hyper Cutter, Mist, etc.), this item is consumed, and its Speed is increased by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Apricot Berry - When the holder's HP falls below 25%, this item is consumed and the holder's Special Defense is raised by 1 stage.
[x] Aguav Berry - When the holder drops below 1/4 Max HP, the item is consumed, and the holder's HP by 1/3 of their Max HP. Confuses the holder if they are of the Naughty, Lax, Rash, or Naive nature.
[x] Air Balloon - Makes the holder not Grounded, thus making the holder immune to Ground-type attacks, and entry hazards. This item is 'popped' (rendered useless for the remained of the battle) if the holder or its Substitute is hit by a damaging move.
[x] Amulet Coin - Doubles all money earned in battle.
[x] Aspear Berry - When the holder becomes frozen, this item is consumed and the holder thaws out.
[x] Assault Vest - Increases the holder's Special Defense by 50%, but prevents the direct usage of Status-type moves, excluding Me First.
[x] Berry Juice - If the holder's HP falls below 50%, this item is consumed, and the holder restores 20 HP.
[x] Berserk Gene - When the holder enters battle, this item is consumed, the holder becomes Confused and has its Attack raised by 2 stages.
[x] Big Root - The holder restores an additional 30% HP when using a Strength Sap or Draining-type move, as well as through Leech Seed, Ingrain, and Aqua Ring. This item also increases damage taken via the Liquid Ooze ability.
[x] Binding Band - While the holder is in battle, all Bind-type damage at the end of a turn to deal 1/6 Max HP instead of 1/8 Max HP.
[x] Black Sludge - If the holder is of the Poison-type, 1/16 Max HP will be restored at the end of the turn, otherwise the holder takes 1/8 Max HP in damage. Pokémon with the Magic Guard ability are immune to this damage.
[x] Bright Powder - Moves that target the holder of this item reduces the accuracy of said moves by 10% of its base accuracy.
[x] Bug Gem - Increases the power of the first Bug-type move used by the holder by 30%, and is then consumed.
[x] Bug Memory - If the holder uses the move Multi-Attack, it will change into the Bug-type.
[x] Burn Drive - If the holder uses the move Techno Blast, it will become a Fire-type move.
[x] Cell Battery - If the holder is hit by an Electric-type move, this item is consumed and the holder's Attack increases by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Cheri Berry - When the holder becomes paralyzed, this item is consumed and the holder is cured of its paralysis.
[x] Chesto Berry - When the holder falls asleep, this item is consumed, and the holder awakens.
[x] Chill Drive - If the holder uses the move Techno Blast, it will become an Ice-type move.
[x] Choice Band - Grants the holder 2x Attack while in battle, but move-locks the Pokemon after their first turn.
[x] Choice Scarf - Grants the holder 2x Speed while in battle, but move-locks the Pokemon after their first turn.
[x] Choice Specs - Grants the holder 2x Special Attack while in battle, but move-locks the Pokemon after their first turn.
[x] Custap Berry - When the user drops below 1/4 Max HP, this item is consumed, and the user will have increased move priority on their next turn.
[x] Damp Rock - If the holder creates Rain (via Drizzle or Rain Dance), the Rain will last for 8 turns instead of 5.
[x] Dark Gem - Increases the power of the first Dark-type move used by the holder by 30%, and is then consumed.
[x] Dark Memory - If the holder uses the move Multi-Attack, it will change into the Dark-type.
[x] Deep Sea Scale - If held by Clamperl, its Special Defense is doubled.
[x] Deep Sea Tooth - If held by Clamperl, its Special Attack is doubled.
[x] Destiny Knot - When the holder of this item becomes Infatuated, the Pokemon that the holder became Infatuated with also becomes Infatuated.
[x] Douse Drive - If the holder uses the move Techno Blast, it will become a Water-type move.
[x] Draco Plate - Boosts the holder's Dragon-type moves by 20%. Judgement becomes a Dragon-type attack. If the holder has the Multitype ability, they will become Dragon-type.
[x] Dragon Gem - Increases the power of the first Dragon-type move used by the holder by 30%, and is then consumed.
[x] Dragon Memory - If the holder uses the move Multi-Attack, it will change into the Dragon-type.
[x] Dread Plate - Boosts the holder's Dark-type moves by 20%. Judgement becomes a Dark-type attack. If the holder has the Multitype ability, they will become Dark-type.
[x] Earth Plate - Boosts the holder's Ground-type moves by 20%. Judgement becomes a Ground-type attack. If the holder has the Multitype ability, they will become Ground-type.
[ ] Eject Button - If the holder is hit by a damaging move and doesn't faint, this item will be consumed and the holder will be switched out with a Pokémon of its Trainer's choice. This item does not proc in wild battles, or if the holder's Trainer has no available Pokémon to switch into.
[ ] Eject Pack - If the holder's stats are lowered (including by use of its own moves, ex. Overheat), this item is consumed and the holder switches out.
[x] Electric Gem - Increases the power of the first Electric-type move used by the holder by 30%, and is then consumed.
[x] Electric Memory - If the holder uses the move Multi-Attack, it will change into the Electric-type.
[ ] Electric Seed - If the holder is holding this item while the field is effected by Electric Terrain, this item will be consumed, and the holder's Defense will increase by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Enigma Berry - When the holder is hit by a Super Effective move, this item is consumed and the holder restores 1/4 of its Max HP.
[x] Eviolite - If the holder is not fully evolved, its Defense and Special Defense are raised by 50%.
[x] Expert Belt - When the holder uses a move that is Super Effective against its target, the power of the move will be increased by 20%.
[x] Exp. Share - The holder of this item will gain 50% of all earned Exp. if they do not partake in battle.
[x] Fairy Gem - Increases the power of the first Fairy-type move used by the holder by 30%, and is then consumed.
[x] Fairy Memory - If the holder uses the move Multi-Attack, it will change into the Fairy-type.
[x] Figy Berry - When the holder drops below 1/4 Max HP, the item is consumed, and the holder's HP by 1/3 of their Max HP. Confuses the holder if they are of the Modest, Timid, Calm, or Bold nature.
[x] Fighting Gem - Increases the power of the first Fighting-type move used by the holder by 30%, and is then consumed.
[x] Fighting Memory - If the holder uses the move Multi-Attack, it will change into the Fighting-type.
[x] Fire Gem - Increases the power of the first Fire-type move used by the holder by 30%, and is then consumed.
[x] Fire Memory - If the holder uses the move Multi-Attack, it will change into the Fire-type.
[x] Fist Plate - Boosts the holder's Fighting-type moves by 20%. Judgement becomes a Fighting-type attack. If the holder has the Multitype ability, they will become Fighting-type.
[x] Flame Orb - Burns the holder at the end of the user's turn.
[x] Flame Plate - Boosts the holder's Fire-type moves by 20%. Judgement becomes a Fire-type attack. If the holder has the Multitype ability, they will become Fire-type.
[x] Float Stone - Halves the weight of the holder.
[x] Flying Gem - Increases the power of the first Flying-type move used by the holder by 30%, and is then consumed.
[x] Flying Memory - If the holder uses the move Multi-Attack, it will change into the Flying-type.
[x] Focus Band - Grants the user a 10% chance to survive from damage that would reduce it's HP to 0.
[x] Focus Sash - If the holder is full HP, the holder will survive a hit that would reduce it's HP to 0.
[x] Full Incense - Forces the holder to move last in it' priority bracket.
[x] Ganlon Berry - When the holder's HP falls below 25%, this item is consumed and the holder's Defense is raised by 1 stage.
[x] Ghost Gem - Increases the power of the first Ghost-type move used by the holder by 30%, and is then consumed.
[x] Ghost Memory - If the holder uses the move Multi-Attack, it will change into the Ghost-type.
[x] Grass Gem - Increases the power of the first Grass-type move used by the holder by 30%, and is then consumed.
[x] Grass Memory - If the holder uses the move Multi-Attack, it will change into the Grass-type.
[ ] Grassy Seed - If the holder is holding this item while the field is effected by Grassy Terrain, this item will be consumed, and the holder's Defense will increase by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Grip Claw - Causes Binding-type moves used by the holder to always last for 7 turns.
[x] Ground Gem - Increases the power of the first Ground-type move used by the holder by 30%, and is then consumed.
[x] Ground Memory - If the holder uses the move Multi-Attack, it will change into the Ground-type.
[x] Heat Rock - If the holder creates Harsh Sunlight (via Sunny Day or Drought), the Harsh Sunlight will last 8 turns instead of 5.
[x] Heavy-Duty Boots - Prevents the holder from taking entry hazard damage.
[x] Iapapa Berry - When the holder drops below 1/4 Max HP, the item is consumed, and the holder's HP by 1/3 of their Max HP. Confuses the holder if they are of the Lonely, Mild, Gentle, or Hasty nature.
[x] Ice Gem - Increases the power of the first Ice-type move used by the holder by 30%, and is then consumed.
[x] Ice Memory - If the holder uses the move Multi-Attack, it will change into the Ice-type.
[x] Icy Rock - If the holder creates Hail (via Hail or Snow Warning), the Hail will last 8 turns instead of 5.
[x] Icicle Plate - Boosts the holder's Ice-type moves by 20%. Judgement becomes a Ice-type attack. If the holder has the Multitype ability, they will become Ice-type.
[x] Insect Plate - Boosts the holder's Bug-type moves by 20%. Judgement becomes a Bug-type attack. If the holder has the Multitype ability, they will become Bug-type.
[x] Iron Ball - Halves the holder's speed, and makes it Grounded.
[x] Iron Plate - Boosts the holder's Iron-type moves by 20%. Judgement becomes a Iron-type attack. If the holder has the Multitype ability, they will become Iron-type.
[x] Jacoba Berry - When the holder is hit by a Physical attack, this item is consumed, and the Attacker loses 1/8 of its Max HP.
[x] Kee Berry - When the holder is hit by a Physical move, this item is consumed and the holder's Defense is raised by 1 stage.
[x] King's Rock - Allows moves that normally wouldn't flinch the enemy, to flinch the enemy at a 10% chance.
[x] Lagging Tail - Forces the holder to move last in its priority bracket,
[x] Lansat Berry - When the holder's HP falls below 25%, this item is consumed and the holder's critical hit ratio is raised by 2 stages.
[x] Lax Incense - Reduces the accuracy of moves that would hit the holder by 10% of the move's original accuracy.
[x] Leek - If held by Farfetch'd or Sirfetch'd, its critical hit ratio is increased by 2 stages.
[x] Leftovers - Restores the holder's HP by 1/16 of it's Max HP (rounded down, but not less than 1) at the end of each turn.
[x] Liechi Berry - When the holder's HP falls below 25%, this item is consumed and the holder's Attack is raised by 1 stage.
[x] Life Orb - Boosts the power of damaging moves that the holder user uses by 30%, but causes the holder to take 1/10 of it's Max HP as damage at the end of each turn.
[x] Light Ball - If held by Pikachu, both its Attack and Special Attack are doubled.
[x] Light Clay - If the holder uses Aurora Veil, Light Screen, or Reflect, the duration of these field effects will last for 8 turns instead of 5.
[x] Luck Incense - Doubles all earned money in battle.
[x] Lucky Egg - If the holder of this item partakes in battle, they will gain 2x Exp.
[x] Lucky Punch - If held by Chansey, its critical hit ratio is increased by 2 stages.
[x] Lum Berry - When the holder is afflicted with a non-volatile status condition or confusion, this item is consumed, and the holder is healed of the status condition.
[x] Luminous Moss - If the holder is hit by a Water-type move, this item is consumed, and the holder's Special Defense is increased by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[ ] Macho Brace - Doubles all earned EVs earned during battle.
[x] Mago Berry - When the holder drops below 1/4 Max HP, the item is consumed, and the holder's HP by 1/3 of their Max HP. Confuses the holder if they are of the Brave, Quiet, Sassy, or Relaxed nature.
[x] Maranga Berry - When the holder is hit by a Special move, this item is consumed and the holder's Special Defense is raised by 1 stage.
[x] Meadow Plate - Boosts the holder's Grass-type moves by 20%. Judgement becomes a Grass-type attack. If the holder has the Multitype ability, they will become Grass-type.
[x] Mental Herb - If the holder is affected by Infatuation, Taunt, Encore, Heal Block, or Disable, the Mental Herb will be consumed, and the holder will be relieved of these status conditions.
[x] Metal Powder - If held by Ditto, its Defense stat is doubled. Does not work when Ditto is transformed.
[x] Metronome - Boosts the power of a move that is used in battle by 20% for each consecutive turn (up to 100% over 6 turns)
[x] Mind Plate - Boosts the holder's Psychic-type moves by 20%. Judgement becomes a Psychic-type attack. If the holder has the Multitype ability, they will become Psychic-type.
[ ] Misty Seed - If the holder is holding this item while the field is effected by Misty Terrain, this item will be consumed, and the holder's Special Defense will increase by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Muscle Band - Boosts the power of the holder's Physical moves by 10%.
[x] Normal Gem - Increases the power of the first Normal-type move used by the holder by 30%, and is then consumed.
[x] Odd Incense - Boosts the power of the holder's Psychic-type moves by 20%.
[x] Oran Berry - When the holder falls below 1/2 Max HP, this item is consumed and the holder restores 10 HP.
[x] Pecha Berry - When the holder becomes poisoned, this item is consumed, and the holder is cured of its poison.
[x] Persim Berry - When the holder becomes confused, this item is consumed, and the holder is cured of its confusion.
[x] Petaya Berry - When the holder's HP falls below 25%, this item is consumed and the holder's Special Attack is raised by 1 stage.
[x] Pixie Plate - Boosts the holder's Fairy-type moves by 20%. Judgement becomes a Fairy-type attack. If the holder has the Multitype ability, they will become Fairy-type.
[x] Poison Gem - Increases the power of the first Poison-type move used by the holder by 30%, and is then consumed.
[x] Poison Memory - If the holder uses the move Multi-Attack, it will change into the Poison-type.
[ ] Power Anklet - The holder gains 8 Speed EVs if they gain Experience in battle, and are not EV capped.
[ ] Power Band - The holder gains 8 Special Defense EVs if they gain Experience in battle, and are not EV capped.
[ ] Power Belt - The holder gains 8 Defense EVs if they gain Experience in battle, and are not EV capped.
[ ] Power Bracer - The holder gains 8 Attack EVs if they gain Experience in battle, and are not EV capped.
[x] Power Herb - If the user uses a Charge-based move (Solar Beam, etc.) this item will be consumed, and the move will not have to charge.
[ ] Power Lens - The holder gains 8 Special Attack EVs if they gain Experience in battle, and are not EV capped.
[ ] Power Weight - The holder gains 8 HP EVs if they gain Experience in battle, and are not EV capped.
[x] Protective Pads - Prevents the holder from being effects by Contact-based move effects (including Perish Body)
[x] Psychic Gem - Increases the power of the first Psychic-type move used by the holder by 30%, and is then consumed.
[x] Psychic Memory - If the holder uses the move Multi-Attack, it will change into the Psychic-type.
[ ] Psychic Seed - If the holder is holding this item while the field is effected by Psychic Terrain, this item will be consumed, the holder's Special Defense will increase by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Quick Claw - Gives the user a 20% chance to move first within its priority bracket.
[x] Quick Powder - If held by Ditto, its Speed is doubled. Does not work when Ditto is transformed.
[x] Rawst Berry - When the holder becomes burned, this item is consumed, and the holder is healed of its burn.
[x] Razor Claw - Raises the critical hit ratio of the holder by 1 stage.
[x] Razor Fang - Allows moves that normally wouldn't flinch the enemy, to flinch the enemy at a 10% chance.
[ ] Red Card - If the holder is hit by a damaging move and doesn't faint, this item will be consumed, and the enemy will be forced to switch into a random Pokémon.
[x] Ring Target - The holder loses its type immunities to moves. Does not apply to Grass-types being immune to Powder/Spore moves, but does make Ground-type Pokémon vulnerable to Thunder Wave.
[x] Rock Gem - Increases the power of the first Rock-type move used by the holder by 30%, and is then consumed.
[x] Rock Incense - Boosts the power of the holder's Rock-type moves by 20%.
[x] Rock Memory - If the holder uses the move Multi-Attack, it will change into the Rock-type.
[x] Rocky Helmet - When the holder takes Contact-based damage, the attacker takes 1/6 of its Max HP in damage. Multi-hit moves proc this effect for each hit. If the holder is hit by Thief, Covet, or Knock Off, or the Attacker has the Magician ability, but faints due to the Rocky Helmet, then the item does not get stolen or knocked off.
[ ] Room Service - If the move Trick Room is used while a Pokémon is holding this item, this item is consumed and the holder's Speed drops by 1 stage. This item will activate and be consumed if the holder of this item swaps into battle while the Trick Room field effect is active.
[x] Rose Incense - Boosts the power of the holder's Grass-type moves by 20%.
[x] Rowap Berry - When the holder is hit by a Special move, this item is consumed, and the Attacker loses 1/8 of its Max HP.
[x] Safety Goggles - Grants the holder immunity to Power/Spore moves, as well as residual damage from Hail and Sandstorm Weather.
[x] Salac Berry - When the holder's HP falls below 25%, this item is consumed and the holder's Speed is raised by 1 stage.
[x] Scope Lens - Raises the holder's critical hit ratio by 1 stage.
[x] Sea Incense - Boosts the holder's Water-type moves by 20%.
[x] Shed Shell - Allows the holder to swap out while trapped, excluding via the use of the move Teleport.
[ ] Shell Bell - The holder of this item restores 1/8 of the damage they dealt this turn, taking multi-hit move damage into consideration. Heal Block does not prevent the holder from restoring its HP.
[x] Shock Drive - If the holder uses the move Techno Drive, it becomes an Electric-type move.
[x] Sitrus Berry - When the holder falls below 1/2 Max HP, this item is consumed and the holder restores 1/4 of their Max HP.
[x] Sky Plate - Boosts the holder's Flying-type moves by 20%. Judgement becomes a Flying-type attack. If the holder has the Multitype ability, they will become Flying-type.
[ ] Smoke Ball - Allows the holder to swap out while in battle, even via the use of the move Teleport.
[x] Smooth Rock - If the holder of this item creates a Sandstorm, the duration of the Sandstorm will be increased to 8 turns instead of 5.
[x] Snowball - If the holder is hit by an Ice-type move damaging move, this item is consumed and the holder's Attack increases by 1 stage. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Splash Plate - Boosts the holder's Water-type moves by 20%. Judgement becomes a Water-type attack. If the holder has the Multitype ability, they will become Water-type.
[x] Spooky Plate - Boosts the holder's Ghost-type moves by 20%. Judgement becomes a Ghost-type attack. If the holder has the Multitype ability, they will become Ghost-type.
[x] Starf Berry - When the holder's HP falls below 25%, this item is consumed and a random stat of the holder is raised by 1 stage.
[x] Steel Gem - Increases the power of the first Steel-type move used by the holder by 30%, and is then consumed.
[x] Steel Memory - If the holder uses the move Steel-Attack, it will change into the Water-type.
[x] Sticky Barb - The holder of this item takes 1/8 of it's Max HP in damage at the end of each turn. If the holder is hit by a Contact move and the Attacker has no held item, this item will transfer over to the Attacker for the remainder of the battle. Pokémon with the Magic Guard ability are immune to this damage.
[x] Stone Plate - Boosts the holder's Rock-type moves by 20%. Judgement becomes a Rock-type attack. If the holder has the Multitype ability, they will become Rock-type.
[x] Terrain Extender - If the holder of this item uses a move or ability that starts a terrain effect, the duration of the terrain will be 8 turns instead of 5.
[x] Thick Club - If held by Cubone or Marowak, its Attack stat is doubled.
[x] Throat Spray - If the holder of this item uses a Sound-based move, this item is consumed and the holder's Special Attack is increased by 1 stage.
[x] Toxic Orb - Poisons the holder at the end of each turn.
[x] Toxic Plate - Boosts the holder's Poison-type moves by 20%. Judgement becomes a Poison-type attack. If the holder has the Multitype ability, they will become Poison-type.
[ ] Utility Umbrella - The holder of this item is unaffected by the effects of Rain and Harsh Sunlight, but not of Hail and Sandstorm. The holder's Abilities and self-targeting moves work as though there was no Rain or Harsh Sunlight present: Growth, etc. won't double its Speed, Water-type and Fire-type moves don't have their power or accuracy altered, Solar Beam will remain a charge-move, the holder may be frozen while Harsh Sunlight is active.
[x] Water Gem - Increases the power of the first Water-type move used by the holder by 30%, and is then consumed.
[x] Water Memory - If the holder uses the move Multi-Attack, it will change into the Water-type.
[x] Wave Incense - Boosts the holder's Water-type moves by 20%.
[x] Weakness Policy - When the holder is hit by a Super Effective move, this item is consumed and its Attack and Special Attack are increased by 2 stages. (Does not activate if the holder has +6 Sp.Defense, or -6 Sp.Defense w/ Contrary)
[x] Wiki Berry - When the holder drops below 1/4 Max HP, the item is consumed, and the holder's HP by 1/3 of their Max HP. Confuses the holder if they are of the Adamant, Jolly, Careful, or Impish nature.
[ ] White Herb - When the holder's stats have a negative stage/modifier, this item is consumed and resets the respecitve stats to default (a stage/modifier of 0).
[x] Wide Lens - Boosts the holder's accuracy by 10%.
[x] Wise Glasses - Boosts the holder's Special-type moves by 10%.
[x] Zap Plate - Boosts the holder's Electric-type moves by 20%. Judgement becomes a Electric-type attack. If the holder has the Multitype ability, they will become Electric-type.
[x] Zoom Lens - If the holder moves last in battle, the accuracy of its moves are increased by 20%.

Unusable Battle Items

Blue Orb - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Red Orb - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Abomasite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Absolite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Aerodactylite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Aggronite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Alakazite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Altarianite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Ampharosite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Audinite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Banettite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Beedrillite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Blastoisinite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Blazikenite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Cameruptite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Charizardite X - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Charizardite Y - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Diancite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Galladite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Garchompite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Gardevoirite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Gengarite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Glalitite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Gyaradosite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Heracronite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Houndoominite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Kangaskhanite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Latiasite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Latiosite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Lopunnite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Lucarionite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Manectite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Mawilite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Medichamite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Metagrossite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Mewtwonite X - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Mewtwonite Y - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Pidgeotite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Pinsirite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Sablenite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Salamencite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Sceptilite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Scizorite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Sharpedonite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Slowbronite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Steelixite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Swampertite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Tyranitarite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.
Venusaurite - Form(e) changing is a permanent feature outside of battle, rendering form(e) changing items useless in battle.

Closing as manual implementation isn't necessary with the move to Smogon's Showdown Sim (#18)


Enhancement in Game

I would like to Enhance the look of overall game Please assign this to me @yashchaudhari008

Please be specific 😅!


React-native proper example

Hi @maxmantz, hope you are well. First of all, yes I've seen https://github.com/maxmantz/redux-oidc/issues/25 but it seem to have become a bit crowded, it's more than 6 months old and the code samples there doesn't seem to be working with the latest versions of react-native. I am kind of hoping to end up with a proper, working example (ideally with silent_renew) that could be added to the documentation. So far I encountered a few problems and I was hoping you/somebody else would be able to shine some light on these:

Correct me if I am wrong, but even when webView seems like an obvious choice, it appears to be blocked by google auth and therefore popup sign in appears to be the only way to make this happen. Right?

With a popup, we handle all authentication in mobile web browser (which is great cause you reuse exiting UI), but what about the callback? Does it need to be a deep link via Linking react-native api. This I am unable to make to work, and it appears to be a rather hacky solution as it asks if you want to open the link in the app which can seem a bit dodgy by users. Am I missing something?

Btw, https://github.com/NerdySaiyan/redux-oidc-example-react-native seemed like a perfect starting point, but:
It doesn't work as of 2018, can't build the project, not sure what changed. It also specifies redirect_uri as localhost:3000 which is very odd cause there's no deep linking setup. I am not sure how it would work to pick up the token from the url. But again, maybe I am missing something. Any input would be highly appreciated. Thanks

Hello,
I know that the react-native examples have stalled lately. The reason is that the oidc-client-js library until now doesn't fully support native applications. It also seems like the implicit flow is not the desired method for authentication in native apps. Please read @leastprivilege 's post in this pull request for more information. The milestone for the PR is version 1.5.0. However, with the information given, it seems like native support is not desirable for this library.

 I have yet to read that specification in full detail but given the overview of what it contains, would it maybe make sense to make it clear in the readme that this lib should not be used in react-native? Current readme states the opposite and while I know it is possible to a certain extent, it's apparently not the best practice. What do you think?

If I understand it correctly, this might provide the correct way of achieving the task at hand, right?

The current readme doesn't state anything opposite to what I just said here. But I will make a note in the readme clarifying this.
To your second point - it seems to be the way to go for react-native. However I haven't tried it yet.

Yep sounds good, thanks again.


Add standalone executables

Example of using CLI11 to build standalone executables for use with the ign tools.
This keeps the ign.cc and ign.hh the same, and just provides a C++ entrypoint.
Signed-off-by: Michael Carroll<EMAIL_ADDRESS>

./bin/transport --help
transport
Usage: ./bin/transport [OPTIONS] SUBCOMMAND

Options:
  -h,--help                   Print this help message and exit
  --help-all                  Show all help
  -v,--version

Subcommands:
  topic                       Introspect ignition topics
  service                     Introspect ignition services

./bin/transport --help
transport
Usage: ./bin/transport [OPTIONS] SUBCOMMAND

Options:
  -h,--help                   Print this help message and exit
  --help-all                  Show all help
  -v,--version

Subcommands:
  topic                       Introspect ignition topics
  service                     Introspect ignition services

./bin/transport topic --help
Introspect ignition topics
Usage: ./bin/transport topic [OPTIONS]

Options:
  -h,--help                   Print this help message and exit
  --help-all                  Show all help
  -t,--topic TEXT             Name of a topic
  -m,--msgtype TEXT           Type of message to publish
  -d,--duration FLOAT Excludes: --num
                              Duration (seconds) to run
  -n,--num INT Excludes: --duration
                              Numer of messages to echo and then exit
[Option Group: command]
  Command to be executed
  [Exactly 1 of the following options is required]
  Options:
    -l,--list
    -i,--info Needs: --topic
    -e,--echo
    -p,--pub TEXT Needs: --topic --msgtype

./bin/transport topic --help
Introspect ignition topics
Usage: ./bin/transport topic [OPTIONS]

Options:
  -h,--help                   Print this help message and exit
  --help-all                  Show all help
  -t,--topic TEXT             Name of a topic
  -m,--msgtype TEXT           Type of message to publish
  -d,--duration FLOAT Excludes: --num
                              Duration (seconds) to run
  -n,--num INT Excludes: --duration
                              Numer of messages to echo and then exit
[Option Group: command]
  Command to be executed
  [Exactly 1 of the following options is required]
  Options:
    -l,--list
    -i,--info Needs: --topic
    -e,--echo
    -p,--pub TEXT Needs: --topic --msgtype

requires https://github.com/ignitionrobotics/ign-utils/pull/2

requires https://github.com/ignitionrobotics/ign-utils/pull/2

the tests were not being compiled, so I re-enabled them in 30a14eff5a3c5684c20286e3ac8d43ae21698504 and fixed the configuration of the cmdtransport.rb file used for testing.
I noticed that calling ign topic with any parameters other than -h or -l get treated like --list
for example:
$ ign topic -l
topic -l
/clock
/gazebo/resource_paths
/gui/camera/pose
/gui/record_video/stats
/stats
/world/default/clock
/world/default/dynamic_pose/info
/world/default/pose/info
/world/default/scene/deletion
/world/default/scene/info
/world/default/state
/world/default/stats

$ ign topic  -e -t /stats
topic -e -t /stats
/clock
/gazebo/resource_paths
/gui/camera/pose
/gui/record_video/stats
/stats
/world/default/clock
/world/default/dynamic_pose/info
/world/default/pose/info
/world/default/scene/deletion
/world/default/scene/info
/world/default/state
/world/default/stats

I like splitting each verb into its own executable; I've updated the ruby script to call each one in ddd1da3
there are now just two test failures, but one of them is a seg-fault in the callback function passed to CLI: https://gist.github.com/scpeters/b18b1cbb38c43e0e02d406254aaeadef

@osrf-jenkins run tests please

opened https://github.com/osrf/homebrew-simulation/pull/1320 to fix brew CI

@osrf-jenkins run tests please

brew build is failing because https://github.com/ignitionrobotics/ign-cmake/pull/143 has not yet been released

@osrf-jenkins run tests please

2 test failures:
 https://build.osrfoundation.org/job/ignition_transport-ci-pr_any-homebrew-amd64/1005/testReport/

adding ign-utils to gazebodistro in https://github.com/ignition-tooling/gazebodistro/pull/27

it took some arcane ruby moves, but I think the tests should now be working

@osrf-jenkins run tests please

@osrf-jenkins run tests please

I forgot CI for this package is using configure.bat, so I added ign-utils to it in 819394b
we will have to add ign-utils as a dependency for anything that uses ign-transport; I'll check gazebodistro once more

we will have to add ign-utils as a dependency for anything that uses ign-transport; I'll check gazebodistro once more

https://github.com/ignition-tooling/gazebodistro/pull/28

I forgot CI for this package is using configure.bat, so I added ign-utils to it in 819394b

actually, I think we need to add a configure.bat to ign-utils for this to work

I forgot CI for this package is using configure.bat, so I added ign-utils to it in 819394b

actually, I think we need to add a configure.bat to ign-utils for this to work

there are two options to fix windows CI; we can choose one or do both:

add a configure.bat script to ign-utils: https://github.com/ignitionrobotics/ign-utils/pull/13
switch to the newer colcon-based windows CI builds: https://github.com/ignition-tooling/release-tools/pull/411, https://github.com/ignition-tooling/gazebodistro/pull/29

cc @j-rivero

there is a flaky failure of UNIT_ign_TEST in the focal workflow
[ RUN      ] ignTest.TopicPublish
  /github/workspace/src/cmd/ign_TEST.cc:337: Failure
  Expected equality of these values:
    g_topicCBStr
      Which is: "bad_value"
    "good_value"
  [  FAILED  ] ignTest.TopicPublish (1625 ms)

@osrf-jenkins run tests please

I forgot CI for this package is using configure.bat, so I added ign-utils to it in 819394b

actually, I think we need to add a configure.bat to ign-utils for this to work

there are two options to fix windows CI; we can choose one or do both:

add a configure.bat script to ign-utils: ignitionrobotics/ign-utils#13
switch to the newer colcon-based windows CI builds: ignition-tooling/release-tools#411, ignition-tooling/gazebodistro#29

cc @j-rivero

I'm rerunning CI because I think we have fixed this

I'm rerunning CI because I think we have fixed this

nope

I'm rerunning CI because I think we have fixed this

nope

It looks like the problem on Windows now is not infra-related anymore, right?
CMake Error in src/cmd/CMakeLists.txt:
  Evaluation file to be written multiple times with different content.  This
  is generally caused by the content evaluating the configuration type,
  language, or location of object files:

   C:/Jenkins/workspace/ign_transport-pr-win/ws/build/ignition-transport10/test/lib/ruby/ignition/cmdtransport10.rb

I'm rerunning CI because I think we have fixed this

nope

It looks like the problem on Windows now is not infra-related anymore, right?
CMake Error in src/cmd/CMakeLists.txt:
  Evaluation file to be written multiple times with different content.  This
  is generally caused by the content evaluating the configuration type,
  language, or location of object files:

   C:/Jenkins/workspace/ign_transport-pr-win/ws/build/ignition-transport10/test/lib/ruby/ignition/cmdtransport10.rb

it could be a problem with this PR, since we've changed that logic here

@mjcarroll it now configures on windows, but there's a linking error related to the ign library:
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(46,1):
 error C2491: 'cmdTopicList': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(58,1):
 error C2491: 'cmdTopicInfo': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(93,1):
 error C2491: 'cmdServiceList': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(105,1):
 error C2491: 'cmdServiceInfo': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(141,1):
 error C2491: 'cmdTopicPub': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(193,1):
 error C2491: 'cmdServiceReq': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.313s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(255,1):
 error C2491: 'cmdTopicEcho': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]
[613.328s] C:\Jenkins\workspace\ign_transport-pr-win\ws\ign-transport\src\cmd\ign.cc(303,1):
 error C2491: 'ignitionVersion': definition of dllimport function not allowed [C:\Jenkins\workspace\ign_transport-pr-win\ws\build\ignition-transport10\src\cmd\ign.vcxproj]

if we want to move forward without digging further, we can re-disable the src/cmd folder on windows

the windows build configures and builds, but the ign tests fail, partially due to https://github.com/ignitionrobotics/ign-tools/issues/43
I think we should disable the ign tests once again until that issue is resolved

@osrf-jenkins run tests please

the windows build configures and builds, but the ign tests fail, partially due to ignitionrobotics/ign-tools#43
I think we should disable the ign tests once again until that issue is resolved

there are other issues as well, so I've added them to #104

I noticed that the help text is less verbose now, for example, before we had:
  -p [ --pub ] arg           Publish a message.
                             arg is the message data. The format expected is
                             the same used by Protobuf DebugString(). E.g.:

                               ign topic -t /foo -m   ignition.msgs.StringMsg
                               -p 'data:"Custom data"'

                             Requires -t and -m.

And now:
    -p,--pub TEXT Needs: --topic --msgtype

Would it be possible to add the verbose descriptions?

I'm also not sure what this means when I do ign topic -h:
[Option Group: command]
  Command to be executed

Would it be possible to add the verbose descriptions?

As I mentioned during the meeting, don't take this as a blocker. It can always be improved afterwards. If you peeps think this is good to go, let's get a pre-release out :smile:

Would it be possible to add the verbose descriptions?

As I mentioned during the meeting, don't take this as a blocker. It can always be improved afterwards. If you peeps think this is good to go, let's get a pre-release out

I've approved it, but I've also written a bit of the code here. @mjcarroll how do you feel about the changes I've made?

Can someone else reproduce it?

yes I can reproduce it. I believe the tests all use -n or --durationto limit the output, in which case it works fine. The problem seems to be buffering continuous output to the screen. The executable works fine directly, but theign` tool isn't passing the output along.
thanks for catching this; it's a bug in the interactive mode that our tests don't cover

the following can print everything but it doesn't exit properly:
diff --git a/src/cmd/cmdtransport.rb.in b/src/cmd/cmdtransport.rb.in
index 1ee747b6..f1b4ac8f 100644
--- a/src/cmd/cmdtransport.rb.in
+++ b/src/cmd/cmdtransport.rb.in
@@ -51,8 +51,12 @@ class Cmd
     end

     # Drop command from list of arguments
-    stdout_and_stderr, status = Open3.capture2e(exe_name, *args[1..-1])
-    print stdout_and_stderr
-    exit(status.exitstatus)
+    Open3.popen2e(exe_name, *args[1..-1]) do |_in, out_err, wait_thr|
+      out_err.each do |line|
+        print line
+      end
+      exit_status = wait_thr.value
+    end
+    exit(exit_status)
   end
 end

I need to switch tasks for now in case someone has some good ruby ideas about how to fix this

Removing from beta, this can come in a minor release.

this is ready for further review

give a try to the binaries in the build directory,
ign-transport/build/bin on  add_standalone ❯ ./ign-transport-topic --pub --topic /foo --msgtype String
--pub requires --topic
Run with --help for more information.

There is probably something bad probably in my invocation but from the error message seems difficult to know what.

Does this error happen on your side?
ign topic -l --force-version 10.0.0
Traceback (most recent call last):
	2: from /usr/bin/ign:272:in `<main>'
	1: from /usr/lib/ruby/ignition/cmdtransport10.rb:43:in `execute'
/usr/lib/ruby/ignition/cmdtransport10.rb:43:in ``': No such file or directory - /usr/lib/x86_64-linux-gnu/ignition/transport10/ign-transport-topic (Errno::ENOENT)

Not sure if it's related with having multiple versions of the library installed.

where did you install when you built this branch from source?

giving a try to the binaries in the build directory,
ign-transport/build/bin on  add_standalone ❯ ./ign-transport-topic --pub --topic /foo --msgtype String
--pub requires --topic
Run with --help for more information.

There is probably something bad probably in my invocation but from the error message seems difficult to know what.

yeah, that is a bit confusing; here's what I think is happening:
$ bin/ign-transport-topic  --pub
--pub: 1 required TEXT missing

$ bin/ign-transport-topic  --pub --topic
--pub requires --topic

it seems that the message text to publish needs to immediately follow --pub. I think your command is interpreting --topic as the message content. I wonder how we can improve the messaging here?

Does this error happen on your side?
ign topic -l --force-version 10.0.0
Traceback (most recent call last):
	2: from /usr/bin/ign:272:in `<main>'
	1: from /usr/lib/ruby/ignition/cmdtransport10.rb:43:in `execute'
/usr/lib/ruby/ignition/cmdtransport10.rb:43:in ``': No such file or directory - /usr/lib/x86_64-linux-gnu/ignition/transport10/ign-transport-topic (Errno::ENOENT)

Not sure if it's related with having multiple versions of the library installed.

where did you install when you built this branch from source?

@caguero I'd like to try to reproduce this. Please share more details about how you installed so I can try

Does this error happen on your side?
ign topic -l --force-version 10.0.0
Traceback (most recent call last):
	2: from /usr/bin/ign:272:in `<main>'
	1: from /usr/lib/ruby/ignition/cmdtransport10.rb:43:in `execute'
/usr/lib/ruby/ignition/cmdtransport10.rb:43:in ``': No such file or directory - /usr/lib/x86_64-linux-gnu/ignition/transport10/ign-transport-topic (Errno::ENOENT)

Not sure if it's related with having multiple versions of the library installed.

where did you install when you built this branch from source?

@caguero I'd like to try to reproduce this. Please share more details about how you installed so I can try

I installed it in /usr (default installation).

Does this error happen on your side?
ign topic -l --force-version 10.0.0
Traceback (most recent call last):
	2: from /usr/bin/ign:272:in `<main>'
	1: from /usr/lib/ruby/ignition/cmdtransport10.rb:43:in `execute'
/usr/lib/ruby/ignition/cmdtransport10.rb:43:in ``': No such file or directory - /usr/lib/x86_64-linux-gnu/ignition/transport10/ign-transport-topic (Errno::ENOENT)

Not sure if it's related with having multiple versions of the library installed.

where did you install when you built this branch from source?

@caguero I'd like to try to reproduce this. Please share more details about how you installed so I can try

I installed it in /usr (default installation). Try installing another Ignition Transport library with a different major version in the same location as well.

I'll try it in a docker container, as I don't normally install to /usr on my base system

I installed it in /usr (default installation). Try installing another Ignition Transport library with a different major version in the same location as well.

I'll try it in a docker container, as I don't normally install to /usr on my base system

the executables were being installed to /usr/lib/ignition/transport10, but the ruby script was expecting them in /usr/lib/x86_64-linux-gnu/ignition/transport10, so I changed the lib in the install path to ${IGN_LIB_INSTALL_DIR}, which should fix it

I rebased because the abichecker was failing in a weird way

I really can't figure out why the abichecker is complaining:

 https://build.osrfoundation.org/job/ignition_transport-abichecker-any_to_any-ubuntu_auto-amd64/344/API_5fABI_20report/

it's complaining about a bunch of removed symbols from ReqHandler and SubscriptionHandler

I really can't figure out why the abichecker is complaining:

 https://build.osrfoundation.org/job/ignition_transport-abichecker-any_to_any-ubuntu_auto-amd64/344/API_5fABI_20report/

it's complaining about a bunch of removed symbols from ReqHandler and SubscriptionHandler

I believe the abichecker failure is a false positive and have noted it in https://github.com/ignition-tooling/release-tools/issues/336#issuecomment-831469694
I think this is ready for review again, as I have addressed the problem noted by @caguero

@caguero any other thoughts on this one?


PulseAudio: Unable to connect: Connection refused

Normally I control my audio via amixer and have it assigned to keyboard shortcuts. It works fine in i3, but I seem to not have control over pulseaudio in sway.
shortcuts from my config:
# add shortcuts for controlling audio volume
bindsym F10 exec amixer -D pulse sset Master 10%+ unmute && killall -SIGUSR1 i3status
bindsym F9 exec amixer -D pulse sset Master 10%- unmute && killall -SIGUSR1 i3status
bindsym F8 exec amixer -D pulse sset Master toggle && killall -SIGUSR1 i3status

When trying to use amixer from a command line I get a ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused error. Trying to control audio via pavucontrol results in it stuck in the "Establishing connection to PulseAudio. Please wait..." stage. My assumption is that wayland and pulseaudio aren't playing nice at the moment. Using alsamixer doesn't help much either since I can't play with my default soundcard profile to adjust the volume. The only thing it shows is S/PDIF output for some reason, and it looks like it 'copied' the S/PDIF controls from another output sources.
Using sway -v I get sway version 0.11-6-g36f896a (2017-01-04, branch "makepkg"). I'm using Arch.

I'm not sure what your issue is but it has nothing to do with sway.

I looked more into it and pulseaudio in general isn't working for some reason, even with i3. I'm not quite sure what happened. I was going to close this myself once I figured out what it was. It's very recent whatever caused it and I didn't notice it until I just recently played with sway again.


Fix PEP8 Issues

https://github.com/commitmas/pybluedot/pull/10 introduces a Tox-based framework for doing CI, but does not address the PEP8 issues shown when running tox -epep8. Someone should fix these :smile:

I will look at this one.

@gamefiend Awesome! This is a top priority so we can get the build fixed (that way others know if they've re-broken the build). I merged #10 so you should be able to pull the latest master, then run tox -epep8 to see where all the style issues are.

Sweet! I'll work on this tonight.
On Tue, 6 Dec 2016 at 16:31 Matt Oswalt<EMAIL_ADDRESS>wrote:

@gamefiend https://github.com/gamefiend Awesome! This is a top priority
so we can get the build fixed (that way others know if they've re-broken
the build). I merged #10 https://github.com/commitmas/pybluedot/pull/10
so you should be able to pull the latest master, then run tox -epep8 to
see where all the style issues are.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commitmas/pybluedot/issues/11#issuecomment-265278758,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZC6IllOis6wfWCJpuMb2lip8bNlzJjks5rFdQzgaJpZM4LE0t8
.


Kick off ES2 support branch

WIP - this will contain the updates to support ES2.0

@bonzofenix - Just a heads up that we're currently working on this - once we've figured out which version of KOPF and HQ work reliably I'll drop you a message asking you to merge.

Hi there!
We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.
The current status is as follows:

[ ] #132590957 Kick off ES2 support branch

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.


Question: compiling ffmpeg with openh264 binaries using the royalty free approach

I'm trying to use this library royalty free but I'm having trouble setting up without certain files from the source (i.e: codec/api/wels/codec_api.h) which, by my understanding, nullifies Cisco covering the license fees.
Does anyone know whether there is any way to compile ffmpeg without using the source files or are we all stuck in a catch 22?

There are three ways to do it:

Build ffmpeg against your own-built openh264 and then don't ship your link libraries
Modify ffmpeg to dlopen it, thus not requiring openh264 artifacts at build-time (this is what Fedora and openSUSE do)
Use a skeleton at build time instead (this is what Flathub does with noopenh264)

skretch
Am Do., 2. März 2023 um 10:53 Uhr schrieb Ilia @.***>:

I'm trying to use this library royalty free but I'm having trouble setting up without certain files from the source (i.e: codec/api/wels/codec_api.h) which, by my understanding, nullifies Cisco covering the license fees.
Does anyone know whether there is any way to compile ffmpeg without using the source files or are we all stuck in a catch 22?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

--
By Cqa-s Co-orp

Just an update, new home of noopenh264 is https://gitlab.com/freedesktop-sdk/noopenh264


Add resiliency to curl commands

It's always good to add retries and a timeout in CI to make the command more resilient.

Hi @ChrisBr, thanks for raising this! I'm the tech writer looking after these docs. I've been considering whether this fits in the docs and think the answer is no. It is a good practice, but it is more of a good practice for using curl rather than using Buildkite. These code snippets aim to show how to use the Buildkite-specific parameters to make a call. Additional practices for using curl are out of scope.
Thanks again for raising this, though. It helped me clarify the scope for this in the docs. Let me know if you think I'm missing something. 😊

Fine by me!


[WIP}[Refactor]--Remove unused field/methods relating to mesh handling.

Motivation and Context
In preparation for rewriting the asset load pipeline, I'm coming across some unused code in ResourceManager and the various mesh constructs.  This PR is for removing these methods, so that the pending asset load functionality PRs will retain their focus :) .

How Has This Been Tested

All local c++ and python tests pass
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@jturner65, feel free to use the codecov report to help find likely dead code.


Add option for PyPSA-USA policy constraints to be run above custom USA or Regional model

Feature Request
A user contacted me regarding using the policy constraints implemented in pypsa-usa but overlayed above their own proprietary data.

[ ] Create an option for custom network input into prepare_network, such that all downstream rules are continued.

Suggested Solution
No response
Additional Info
No response

Closed with #356


Mark HasDataLoaderMeta type as unique

Currently trying to use `` as interface type gives following error computed property name in an interface must refer to an expression whose type is a literal type or a 'unique symbol' type.
Use case trying to declare global meta params
declare module 'vue-router' {
	interface RouteMeta {
		[HasDataLoaderMeta]: (() => Promise<unknown>)[]
	}
}

https://github.com/posva/unplugin-vue-router/blob/f268adbf3a84e3e86aad78f2a039017af17d5276/src/data-fetching/dataFetchingGuard.ts#L6
Can be fixed with
export const HasDataLoaderMeta: unique symbol = Symbol()

What are you trying to do? This shouldn't be necessary

I am using typesafe-i18n. I kinda repurposed defineLoader to load namespaced translations async during page load in order to reduce waterfalls.
My code looks basically like this:

declare module 'vue-router' {
	// TODO. Until is fixed https://github.com/posva/unplugin-vue-router/issues/133
	// eslint-disable-next-line @typescript-eslint/no-shadow
	const HasDataLoaderMeta: unique symbol

	interface RouteMeta {
		[HasDataLoaderMeta]?: (() => Promise<unknown>)[]
		i18nNamespace?: string
	}
}

const useI18nLoader = defineLoader(async (route) => {
	const namespace = route.meta.i18nNamespace as Namespaces

	if (namespaces.includes(namespace)) {
		const { commitLoadedLocales, locale } = useGlobalStore()

		await loadNamespaceAsync(locale, namespace)
		commitLoadedLocales()
	}
})

const i18nLoaderModulePromise = Promise.resolve({
	useI18nLoader,
})

const i18nLoaderModuleFn = () => i18nLoaderModulePromise

export const router = createRouter({
	extendRoutes(routes) {
		// Only iterating over top routes is enough,
		// because nested routes inherit meta from parent.
		for (const route of routes) {
			route.meta ??= {}
			route.meta[HasDataLoaderMeta] ??= []

			route.meta[HasDataLoaderMeta].push(i18nLoaderModuleFn)
		}

		return routes
	},
	history: createWebHistory(),
})

I see. I don't recommend hijacking the RouteMeta with your own type and import as this is considered internal API and if it changes in the future it would break your code. Instead, create another symbol and add another navigation guard.
But even though, HasDataLoaderMeta is already a unique symbol as it's created with = Symbol(). Otherwise it would error in this project too

Typescript doesn't consider it unique, thats why you need to mark it as such. At least not as key for interfaces.
I want to leverage loader so data/locales fetching happens in parallel, so I need a way to add them to loader.  Loading becomes blocking. I looked into RFC and how to manually add loaders. If that is not recomended perpahs another api is needed?

Typescript doesn't consider it unique, thats why you need to mark it as such. At least not as key for interfaces.

It seems to be doing so within the project as = Symbol() already forges a unique symbol type, so I'm surprised that changes fixes your issue as it doesn't change the type and that makes sense as the project itself would otherwise also error.
Regarding your use case: I don’t think parallelism brings much but you could still await within a loader, for example:
const useI18nLoader = defineLoader(async (route) => {
	const namespace = route.meta.i18nNamespace as Namespaces
	if (namespaces.includes(namespace)) {
		const { commitLoadedLocales, locale } = useGlobalStore()
        await i18nLoaderModuleFn()
		await loadNamespaceAsync(locale, namespace)
		commitLoadedLocales()
	}
})

This would avoid hijacking a private API while keeping the parallelism, so It's future proof 💯

You are absolutely right about symbol, sorry. It is another issue entirely.typed-router.d.ts inside module declarations exports things from unplugin-vue-router/runtime, but in my project those types are not being resolved. If I manually add import 'unplugin-vue-router/runtime at the top of typed-router.d.ts thise exports start to work. I am not sure how that supposed to behave.
Regarding with i18n loader how do I make loader run on every route? I already await things that i need inside the loader, and  i18nLoaderModuleFn is just fake module mock that I later inject to HasDataLoaderMeta array , calling it inside the loader itself doesn't make much sense for me or am I misunderstanding something?

Regarding your loader for each route, the way you are doing it is actually fine. I was confused because you overrode the RouteMeta interface but I also realize the type is probably not augmented correctly.

I created reproduction of the issue. Stackblitz doesn't seem to support type info in vue files, but nonentless, if you go to the main.ts file and hover on meta field you will see nothing. However if you add import 'unplugin-vue-router/runtime' at the top of typed-router.d.ts it will begin to work.

Not sure if this is the correct issue but is it necessary to have to import the macro from 'vue-router/auto'? Shouldn't it just be available similar to defineProps  in terms of typescript?

Yes, it’s necessary. It’s different from defineProps because it’s a Vue compiler macro

Heads up: the internal HasDataLoaderMeta will be removed in the next releases as it won't be necessary anymore


sentry error reporting

https://docs.sentry.io/platforms/javascript/guides/vue/?_ga=2.240938307.1548587100.1602747830-1799454226.1602747830&_gac=1.261767679.1602747830.CjwKCAjw5p_8BRBUEiwAPpJO67Bw6xj32mASTKHt2ASDs7AmIz8M3b-mo9P63dTfKthboQH5X5wVOhoCh1IQAvD_BwE

I've added Sentry to staging now, @ashachaf can we get the GitHub integration going?

github integration in place.


Adding Log level print macros to SJSU-Dev2

Codecov Report

Merging #221 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #221      +/-   ##
==========================================
+ Coverage   86.44%   86.48%   +0.04%
==========================================
  Files          44       44
  Lines        1888     1887       -1
==========================================
  Hits         1632     1632
+ Misses        256      255       -1

Impacted Files
Coverage Δ

firmware/library/L4_Application/task_scheduler.cpp
65.9% <0%> (+1.46%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f21a75c...ef7a8e9. Read the comment docs.


totally disable sending DM on leave message

Like #919, but with a clean history.
This pull requests adds several needed fixes to the DM templates in YAGPDB's custom command scripting.
We simply check if the template is being executed by the leave message, if that is true, it will fail to send the message.
This is to remedy the "abuse" of execCC to still be able to send a leave DM, and should be quite future-proof.
Moreover, we add the info text we can see in sendDM to the other DM template sendTemplateDM - Luckily @Pedro-Pessoa helped me with that, so a big kudos to him.
Of course, this might be a small-ish breaking change (again), but I think it is more important to block leave DMs entirely.
Everything works, as far as I can tell, fine on a selfhosted instance.
Cheers!

Has conflicts now, I'll resolve them in a moment

Not sure why it redouts now, investigating.

i'll be really happy to see this being implemented... 😈


Add "Border" around Image

Hey, is it somehow possible to add a "border" around an image?
This is currently my attempt:
$image = Image::make(public_path($img));
$canvas_image = $image;
$image->resize(1024, 1024, function ($constraint) {
    $constraint->aspectRatio();
    $constraint->upsize();
});
$image->save();

$canvas_image->resize(996, 996, function ($constraint) {
    $constraint->aspectRatio();
    $constraint->upsize();
});

$white_canvas_image = Image::canvas($image->width(), $image->height(), '#ffffff');
$white_canvas_image->insert($canvas_image, 'top-left', 28, 28);
$white_canvas_image->save('white_canvas_' . $img);

With insert() i unfortunately only have the possibility to place the image on the x and y axis.
Maybe someone has an idea.

$canvas->rectangle(5, 5, 395, 590, function ($draw) {
            $draw->background('rgba(255, 255, 255, 0.5)');
            $draw->border(1, '#000');
        });

this code use for draw rectangle border. border (size,color);

You can perhaps more easily create a border simply using the resizeCanvas method... something like:
$image->resizeCanvas($border_width*2, $border_width*2, 'center', true, $border_colour);
Where:

$image is the Intervention image;
$border_width is the width of the border you want to add in px
'center' adds the border uniformly around the image
true allows use of relative dimensions
$border_colour is the colour of the border you want to add.
HTH!


Fix documentation and license file omissions

This PR fixes some omissions seen in the PR of the transport module, and ensures sequential attribution of the software.

@brynpickering updated the license information with your feedback. I've also merged heat with better co-author attribution (you should be able to see this in the main repo).

@brynpickering is this OK to merge?


kube-vip configMap failed to be applied (task: kubernetes/loadbalancer/kube_vip)

When creating the cluster on bare metal with Ansible, it fails while trying to apply the kube-vip ConfigMap.
The template here does not specify the properties range-development: as this behavior was changed in this commit
# Reference Link: https://kube-vip.io/docs/usage/cloud-provider/#the-kube-vip-cloud-provider-configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: kubevip
  namespace: kube-system
data:
{% for address in kubernetes_loadbalancer_addresses %}
  {{ address }}
{% endfor %}

This is the error:

TASK [kubernetes/loadbalancer/kube_vip : Apply kube-vip Cloud Provider configMap] ***********************************************************************************
Wednesday 04 October 2023  09:49:27 +0000 (0:00:00.553)       0:01:58.174 *****
fatal: [control]: FAILED! => {"changed": true, "cmd": "kubectl apply -f /tmp/kube-vip-cm.yaml\n", "delta": "0:00:00.282581", "end": "2023-10-04 09:49:27.960276", "msg": "non-zero return code", "rc": 1, "start": "2023-10-04 09:49:27.677695", "stderr": "Error from server (BadRequest): error when creating "/tmp/kube-vip-cm.yaml": ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal string into Go struct field ConfigMap.data of type map[string]string", "stderr_lines": ["Error from server (BadRequest): error when creating "/tmp/kube-vip-cm.yaml": ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal string into Go struct field ConfigMap.data of type map[string]string"], "stdout": "", "stdout_lines": []}

If /tmp/kube-vip-cm.yaml is updated with range-development: the ConfigMap is created correctly

Hey @leonidasas,
Are you still running into this issue? I was not able to recreate this problem using viya4-iac-k8s:3.6.0. I believe the issue may be how you defined the kubernetes_loadbalancer_addresses in your ansible-vars.yaml, could you share your what you set for that?
For context this is what I tested with and did not run into the error you saw.
ansible-vars.yaml snippet
kubernetes_loadbalancer : "kube_vip" # Load Balancer accepted values [kube_vip,metallb]
kubernetes_loadbalancer_addresses :
  - "range-global: <IP_ADDRESS>-<IP_ADDRESS>"
  - "range-development: <IP_ADDRESS>-<IP_ADDRESS>"

checking config map
$ kubectl get cm kubevip -n kube-system -o yaml
apiVersion: v1
data:
  range-development: <IP_ADDRESS>-<IP_ADDRESS>
  range-global: <IP_ADDRESS>-<IP_ADDRESS>
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"range-development":"<IP_ADDRESS>-<IP_ADDRESS>","range-global":"<IP_ADDRESS>-<IP_ADDRESS>"},"kind":"ConfigMap","metadata":{"annotations":{},"name":"kubevip","namespace":"kube-system"}}
  creationTimestamp: "2023-12-06T20:49:51Z"
  name: kubevip
  namespace: kube-system
  resourceVersion: "1626"
  uid: 6c928d28-4791-4236-a0f6-b0cb3ffee0dc

Marking as stale/inactive. If there are further questions please open a new GitHub issue.


out-of-place native FFT: move buffer alloc inside timing

This matches our Python behavior for these benchmarks.

Overall the change is good.  Thanks!
However, removal of #incude print_buf.inc means that even for small inputs the computed Fourier harmonics are not going to be printed out.
If this is unintended, we should put the include in the loop, like:
     if (s == 0 && it == -1) {
           # include print_buf.inc
     }


Fix error deserializing unsigned integers

Fixes an issue where deserializing a PyInt would always deserialize to a signed integer.
This could cause problems if the integer was larger than could be represented by an i64.
With this change, any positive value will be preferentially deserialized as a u64, only falling back to an i64 if extraction as a u64 fails.
Also introduces a panic if the value is not representable with either of these, which while perhaps not ideal is better than a silent failure IMO

IMO it will be awesome to cover this case with tests

Thanks for the PR! Agreed a test would be great, and I am not comfortable with the panic. We should error on overflow (and a test for that would be fantastic).

Upon adding tests I discovered that this works just fine as is, so I'm editing the PR to just add unit tests.
Sorry for the alarm! Someone had made this edit on an internal fork so I assumed it was necessary.

Thanks @Walter-Reactor - I think actually you might have been onto something, I did some experimentation and have now pushed #69 which I think fixes some edge cases with large numbers. I'll close this one, but thank you for reporting / pushing this first pass!


Add rule for plugins without required

Is it working without some source files of notcms/core? Some stubs

Can I add some stub files from Notcms? License etc..?

@lulco Can I add some stub files from Notcms? License etc..?

It would be better to create rule more generic - in class, in method, caller class and called method name should be in parameters and the rule would be registered in final config

Also, please add new rule to readme

Thanks I'll finish some cleanup later


LINQ with Contains and Enum does not consider converterType

Describe the bug
azure-cosmos-dotnet-v3 supports LINQ query generation. When working with enum serialized as string in simple where clause, the expression is properly translated in SQL using the string value of the enum.
But when using Contains operator to generate "IN" clause. This does not work with array of enum, as the SQL translated from it always contains ordinal values of enum, regardless of the model definition.
To Reproduce
public class Foo
{
        [JsonProperty("status")]
        [JsonConverter(typeof(StringEnumConverter))]
        public FooStatus Status { get; set; }
}

public enum FooStatus
{
        StatusA,
        StatusB
}

var query = container.GetItemLinqQueryable<Foo>();
query = query.Where(foo => new[]{FooStatus.StatusA}.Contains(foo.Status));
Console.WriteLine(query.ToQueryDefinition().QueryText);

Expected behavior
SELECT VALUE root FROM root WHERE (root["status"] IN ("StatusA"))

Actual behavior
SELECT VALUE root FROM root WHERE (root["status"] IN (1))

Environment summary
SDK Version: 3.6.0
OS Version (e.g. Windows, Linux, MacOSX):
Operating System: Ubuntu 19.10
Kernel: Linux 5.3.0-40-generic
Architecture: x86-64

Additional context
Simple where clause works just as expected
var query = container.GetItemLinqQueryable<Foo>();
query = query.Where(foo => foo.Status == FooStatus.StatusA);
Console.WriteLine(query.ToQueryDefinition().QueryText);

SELECT VALUE root FROM root WHERE (root["status"] = "StatusA")

We met similar problem with query like  query = query.Where(foo => foo.ADictionary[FooStatus.StatusA] == "a value");
Where foo.ADictionary is Dictionary<FooStatus, string>

I found a workaround but I don't like it it's by using JsonConvert.DefaultSettings, please allow to use CosmosJsonDotNetSerializer  so we can share the JsonSerializerSettings

This is still an issue. Any update?

any update on this bug?

@sboshra @j82w I'd be happy to look into this issue and contribute a PR if this is within reach for a new contributor?

Looking over the code it looks like this needs to be enhanced to support the serializer settings
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/11b774459a894657dcca8cbf89b945b42e008a86/Microsoft.Azure.Cosmos/src/Linq/ExpressionToSQL.cs#L529

Hi, are there any updates about this?

Hi all, we've merged what we hope will be a solution to this issue by allowing the custom serializer to be used for LINQ translations. This also unblocks having System.Text.Json attributes applied in LINQ queries.
We plan to release this as part of the next preview package, but I also wanted to take this time to confirm these changes meet your needs before finalizing them as part of our public API.  If you try the changes out, please follow up in the thread if this update addresses your concerns. If it doesn't, please let us know why.
To use your own custom serializer for LINQ translations you must implement CosmosLinqSerializer and set it as a custom serializer on the CosmosClient. There is a sample of this for serialization with System.Text.Json in CosmosLinqSerializer.cs.

@Maya-Painter thank you for merging the fix. We have tested our code with the nighly build and it fixes our problem with quering againts array of enums marked with JSonConverter(XYZ).
Do you know when we can expect next preview package available on the nuget feed?

@lukasz-pyrzyk We do not have a release scheduled yet but are hoping to get it out by the end of the month.

Leaving a link to source mentioned in comment above
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos.Samples/Usage/SystemTextJson/CosmosSystemTextJsonSerializer.cs


Cargo audit fails because of time: Potential segfault

See https://rustsec.org/advisories/RUSTSEC-2020-0071

Users of time 0.1 do not have a patch and must upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

$ cargo audit
Crate:     time
Version:   0.1.44
Title:     Potential segfault in the time crate
Date:      2020-11-18
ID:        RUSTSEC-2020-0071
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0071
Solution:  Upgrade to >=0.2.23
Dependency tree:
time 0.1.44
└── chrono 0.4.22
    ├── spin-cli 0.7.1
    ├── oauth2 4.2.3
    │   └── bindle 0.8.0
    │       ├── spin-publish 0.7.1
    │       │   └── spin-cli 0.7.1
    │       ├── spin-loader 0.7.1
    │       │   ├── spin-trigger 0.7.1
    │       │   │   ├── spin-testing 0.7.1
    │       │   │   │   ├── spin-redis-engine 0.7.1
    │       │   │   │   │   └── spin-cli 0.7.1
    │       │   │   │   └── spin-http 0.7.1
    │       │   │   │       ├── spin-testing 0.7.1
    │       │   │   │       └── spin-cli 0.7.1
    │       │   │   ├── spin-redis-engine 0.7.1
    │       │   │   ├── spin-http 0.7.1
    │       │   │   └── spin-cli 0.7.1
    │       │   ├── spin-publish 0.7.1
    │       │   ├── spin-cli 0.7.1
    │       │   └── spin-build 0.7.1
    │       │       └── spin-cli 0.7.1
    │       └── spin-cli 0.7.1
    ├── liquid-lib 0.23.1
    │   ├── spin-templates 0.7.1
    │   │   └── spin-cli 0.7.1
    │   └── liquid 0.23.1
    │       └── spin-templates 0.7.1
    └── liquid-core 0.23.2
        ├── spin-templates 0.7.1
        ├── liquid-lib 0.23.1
        └── liquid 0.23.1

Is the work item here to upgrade the time crate and ensure functionality is unaffected?  If so, Do we feel the test automation we have in place is sufficient to cover our needs here?

@vdice it looks like we only consume time via chrono, and chrono has supposedly broken its dependency on time:
https://github.com/chronotope/chrono/commit/4c351b1e720a30a6e32068fe386293b36d0e86fd
So we might be able to just rev chrono and have the problem go away in favour of some exciting new problem.

...well, coercing chrono to 0.4.23 didn't seem to remove the dependency.  Very weird, what I see in the Cargo cache and what I see in the release history don't really match up...?!


Fix UI audit

Run make ui-audit-fix to fix audit errors.

From https://github.com/weaveworks/weave-gitops/actions/runs/6534950064/job/17743288099 seems to be mainly babel stuff

build is still working
Ran tilt up, still works


Replaced bootstrap-tour with introJs tour library in FotoToon Activity

I have migrated FotoToon activity tutorial from bootstrap-tour to IntroJs
Issue: https://github.com/llaske/sugarizer/issues/1090

Good. Thanks for your help on this task.


Add docs for project upgrades

Add in documentation for project upgrades procedure. For example: juno:v1.0.0 -> juno:v2.0.0

Agree this could be clearer, thanks for raising. The easiest solution is to use a snapshot (e.g. from Polkachu), or the Generic build outlined in the docs to step through the versions.
Will add a wiki when I can

There is a wiki here @JianHongHong, does this cover what you were looking for? https://github.com/akash-network/cosmos-omnibus/wiki/Chain-Upgrades

Yes this is what I was looking for. Thanks!


Add paragraph on Python for HPC content

This was published at https://bssw.io/items/python-for-hpc
This PR addresses some changes to the published item

The contents were merged in the article available at: https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/edit/master/CuratedContent/PythonForHPC.md


Docs menu

Would be great the „further documentation“ chapter would already be listed in the main navigation

I have changed the docs accordingly. Now all the subsections are directly available in the menu.


python312Packages.ufmt: 2.1.0 -> 2.7.0

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

8 packages built:

python311Packages.ruff-api
python311Packages.ruff-api.dist
ufmt (python311Packages.ufmt)
ufmt.dist (python311Packages.ufmt.dist)
python312Packages.ruff-api
python312Packages.ruff-api.dist
python312Packages.ufmt
python312Packages.ufmt.dist


Missing properties for non-required top-level keys

Steps to reproduce

Add an invalid field to testdata/validation/valid-component-definition.yaml
Execute go-oscal validate -f testdata/validation/valid-component-definition.yaml -r output.yaml
Review the errors

Expected result
Single error for the invalid field
Actual Result
valid: false
timeStamp: 2024-06-18T15:59:49.449638313Z
errors:
    - keywordLocation: /oneOf/0/required
      absoluteKeywordLocation: http://csrc.nist.gov/ns/oscal/1.0/1.0.4/oscal-complete-schema.json#/oneOf/0/required
      instanceLocation: ""
      error: 'missing properties: ''catalog'', missing properties: ''profile'''
    - keywordLocation: /oneOf/2/properties/component-definition/$ref/properties/components/items/$ref/additionalProperties
      absoluteKeywordLocation: http://csrc.nist.gov/ns/oscal/1.0/1.0.4/oscal-complete-schema.json#/definitions/oscal-complete-oscal-component-definition:defined-component/additionalProperties
      instanceLocation: /component-definition/components/0
      error: additionalProperties 'test' not allowed
    - keywordLocation: /oneOf/3/required
      absoluteKeywordLocation: http://csrc.nist.gov/ns/oscal/1.0/1.0.4/oscal-complete-schema.json#/oneOf/3/required
      instanceLocation: ""
      error: 'missing properties: ''system-security-plan'', missing properties: ''assessment-plan'', missing properties: ''assessment-results'', missing properties: ''plan-of-action-and-milestones'''
metadata:
    documentPath: testdata/validation/valid-component-definition.yaml
    documentType: component-definition
    documentVersion: 1.0.4
    schemaVersion: 1.0.4

Note the two entries for missing-properties being the non-existent models.
Severity/Priority
medium
Additional Context
May be a byproduct of our use of the complete schema - when no invalid fields are present, the linting passes without any errors.

This looks like you have two seperate errors, one top level, violating "oneof" behavior and one with the additionalProperties, am I missing something?

I would have to dig deeper, but my understanding of what is happening right now is that because a component in components is malformed this means -> component-definition is malformed and since there are no other top level fields possible due to "oneOf" jsonschema is telling you to fix your component definition or try a new field, but it would be nice to reduce noise if there is a consistent pattern that wont cause lack of info in other edge cases, right now it still gives what is needed to fix the oscal, though it could be more clear, also errors are completely different in v6 so we may need to make a decision on how much to sink into v5 before just upgrading and seeing what the new jsonschema version offers in way of error clarity as it has had a major overhaul.

from #274:

{
  "valid": false,
  "timeStamp": "2024-07-17T22:16:32.221863-07:00",
  "errors": [
    {
      "keywordLocation": "/oneOf/2/properties/component-definition/$ref/properties/components/items/$ref/additionalProperties",
      "absoluteKeywordLocation": "https://github.com/defenseunicorns/go-oscal/tree/main/src/internal/schemas/oscal_complete_schema-1-0-4.json#/definitions/oscal-complete-oscal-component-definition:defined-component/additionalProperties",
      "instanceLocation": "/component-definition/components/2",
      "error": "\"additional properties 'test' not allowed\""
    }
  ],
  "metadata": {
    "documentPath": "testdata/validation/valid-component-definition.yaml",
    "documentType": "component-definition",
    "documentVersion": "1.0.4",
    "schemaVersion": "1.0.4"
  }
}


[Logistic Regression] Fix bug when regParam is set to 0

This PR fixes the bug that LogisticRegression(regParam=0).fit(df) throws a division by zero error.
The error is due to init:self.set_params(**self._input_kwargs), where self._input_kwargs is {"regParam", 0}, and in this case, _param_value_mapping will set cuml param C to 0.
The fix revised _param_value_mapping to set cuml param C to 1.0 / sys.float_info.min when regParam is 0, and throws a warning for the implicit mapping of regParam from 0 to sys.float_info.min.

build

build

build

build

build

build


Vendoring libkv @v0.2.1

Update libkv to v0.2.1.
Includes:

(bug fix) zk: fix wrong error code check on List

Signed-off-by: Alexandre Beslic<EMAIL_ADDRESS>

@abronan @icecrime should this be in 1.12 ? 👼

LGTM, sounds like it should be on the milestone, so I'll add it, but please let us know if it shouldn't be :smile:

LGTM

LGTM


Upgrade OTel

FYI this is blocking me from marking #2787 as ready to review. I need to rebase it on these changes first.


Neuvector docs redirecting to suse website

The https://open-docs.neuvector.com/ seems to be inaccessible. It is getting redirected to https://www.suse.com/neuvector/. I could not find any docs over there as well!

The issue with the documentation has been sorted out.

Thanks @dimitarzahariev is there any specific reason for the redirection?


Where's the toolkit.jar?

I can't find the toolkit.jar. Please help!

I CAN'T GET THE toolkit.jar? WHY!

I could not find a pre-built binary. You can build it by first installing the JDK and Maven, then cloning the repo and building it.

i made a re release with the .jar I got before https://github.com/users-things/toolkit-re-release/releases/tag/archives

The latest commit on main has been added to releases.
https://github.com/ennuo/toolkit/releases/tag/Release


Adding ROS World links to ROSCon Content page

fixes #921
Signed-off-by: maryaB-osr<EMAIL_ADDRESS>

@Mergifyio backport rolling

Oh, I love what you've done with the tabbed content here.  Big :+1: from me.


Fix volumes and rename service name

Pod gets stuck in ContainerCreating state. After referencing Racher's docs, only PersistentVolumeClaim is required.
changes:

fix service name and port
referenced longhorns example and noticed that only PersistentVolumeClaim section is needed (https://github.com/longhorn/longhorn/blob/master/examples/deployment.yaml)

Will be deployed to Civo.com in a few minutes (just kicked off the test run and deploy). Thanks.


🐛 After sleep, session manager start and can't log in

branch
stable
Architecture
x86_64
Description
After sleep on Manjaro sway, session manager, not swaylock, prompt password and can't login with errors like below.
amdgpu:  amdgpu_device_initialize failed.
libEGL warning: egl: failed to create dri2 screen
00:00:00.026 [wlr][EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed"
amdgpu_device_initialize: AMDGPU_INFO_ACCEL_WORKING = 0
amdgpu: amdgpu_device_initialize failed.
libEGL warning: egl: failed to create dri2 screen
00:00:00.029 [wlr][EGL] command: eglInitialize, error : EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed"
00:00:00.029 [wlr][EGL] command: eglInitialize, error : EGL_NOT_INITIALIZED (0x3001), message: "eglInitialize...
00:00:00.029 [wlr][render/egl.c:264] Failed to initialize EGL
00:00:00.029 [wlr][render/egl.c:554] Failed to initialize EGL context
00:00:00.029 [wlr][render/gles2/renderer.c:679] Cloud not initialize EGL
00:00:00.029 [wlr][render/wlr_renderer.c:333] Could not initialize renderer
00:00:00.029 [sway/server.c:79] Failed to create renderer
The above error is momentary and immediately returns to session manager.
After clean installing Manjaro sway, still the problem has persisted.
I use MINISFORUM EliteMini HX90 https://store.minisforum.com/products/hx90 .
Reproduction steps
Wait for sleep.

Screenshots
No response
Logs
No response

Hm, that is fishy. I have a not too different main PC, the think-centre m75q G2,  it wakes up from sleep with open sway lock, as it should.

Yes, that is difficult to solve.
But before some update, there was no problem with Manjaro sway.
And I'm sorry not to be able to say which update cause the problem because I've reinstalled from the latest Manjaro sway installer.
The errors are GPU related but I don't think that GPU have problem because it works before sleep.
Sometimes even the session manager doesn't appear when I type keys but only black screen.
I'm still new to Manjaro sway, so I don't know where to start to diagnose. Which log files should I check?

I misunderstood the difference between sleep and suspend.
Disabling suspend with systemctl mask suspend.target made swaylock work.
It doesn't solve the fundamental problem, but it save the rebooting.


updated style.css

Added some changes related to font

Hey @LunaNika I don't see any changes, please make some fonts more easy to read and visible
Thank you

Hey @LunaNika I don't see any changes, please make some fonts more easy to read and visible Thank you

Can you please check PR.

I can't merge this PR cause I don't any changes in the site.


Updated the code by adding valid fonts-family and font-weight to styl…

…e.css..
First contribution: "https://github.com/vinitshahdeo/Water-Monitoring-System/edit/master/assets/css/style.scss" [Pull request](link to GitHub pull request on Cosmos)
Description
Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Fixes # (issue)
Updated the fonts to a newer level by adding less known types..
Type of change
Please delete options that are not relevant

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] Any dependent changes have been merged and published in downstream modules

Reviewer: Vinit Shahdeo

Sir kindly review it and tell me if any changes needed..


Search function is case-sensitive

I was browsing through the icons but realized that they won't show up when I was searching for them. It turned out that auto correction wrote a lot of words with capital first letter and the search function is case-sensitive which makes it almost useless on mobile.
Hope you can fix that 😀
Beside that, thanks for the great collection of icons 🙏

Thank you for your feedback, we have fixed the issue with capitalization of letters in the search function.


Add missing re import for slack publisher

slacknotifier uses re.sub but it is not imported in the module.

We've gotta get flake8 going in Travis CI :)

I've pushed v1.4.1 to PyPI with this change. Thank you!


#359 add net core 3.1 & net 6

Have added in net core 3.1 & net 6 as they allow for further optimisations of dependendencies
closes #359

Thank you!


automatic restart for linuxserver/wireguard container after wireguard-ui config save

I've created a companion docker service to automatically restart a container running wireguard based on systemd.
docker run -d --name wg-monitor \
    --security-opt seccomp=unconfined \
    --tmpfs /tmp \
    --tmpfs /run \
    --tmpfs /run/lock \
    -v /path/to/wireguard/config/folder:/etc/wireguard:ro
    -v /sys/fs/cgroup:/sys/fs/cgroup:ro \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -e CONTAINER=wireguard \ # change this to whatever the container you wish to restart is named
    kking124/wireguard-monitor

NOTE: the config folder for linuxserver/wireguard MUST be mounted :ro or the wireguard container will be stuck constantly restarting
You can find it on the Docker Hub at:
https://hub.docker.com/r/kking124/wireguard-monitor

i dont't know if it's a mistake of my part, but when I use your docker-compose, the endpoint address is missing in the wg0.conf file.

Tl;dr - that's expected. You need to generate one from the wireguard-ui web interface by clicking "Apply Config" in the top right.
Is it causing an error, or is the file just missing?
Long explanation:
Because linuxserver/wireguard and kking124/wireguard-monitor both mount the config folder with :ro they can't write to it.  Normally, linuxserver/wireguard would write a wg0.conf at container start, but I'm guessing their init procedure performs a touch on that file, triggering a "change", which triggers the container restart.
I'll look into changing the monitoring script so that it only triggers on a SHA1 change so that linuxserver/wireguard can write it's initial configuration file. It just didn't seem necessary since wireguard-ui overwrites it without reading it anyway.

You can see how I've tackled this problem within my terraform project https://github.com/paklids/flexiwire . Not perfect but the majority is found in the shell script https://github.com/paklids/flexiwire/blob/main/templates/wg_conf_restart.sh (run on a cron).


Fix for excess IP release race condition | handshake between agent and operator

Forward port of https://github.com/DataDog/cilium/pull/24
Currently there's a 15 sec delay in updating ciliumnode (CN) CRD after IP allocation to a pod, meanwhile the operator can determine that a node has excess IPs and release the IP causing pod connectivity issues.
This PR introduces a handshake between the operator and agent before releasing an excess IP to avoid the race condition. A new operator flag excess-ip-release-delay is added to control how long operator should wait before considering an IP for release (defaults to 180 secs). This is done to better handle IP reuse during rollouts. Operator and agent use a new map in cilium node status .status.ipam.release-ips to exchange information during the handshake.
Fixes: #13412

The following alternative options were considered :

We could force a CN write to go through before allocation but it can result in too many writes from the agent.

The operator picks the ENI with the most free IPs to release excess IPs from, this is done so that the ENI could potentially be released in the future. We could move the excess detection logic to the agent, but this involves calling into cloud provider specific implementation, which AFAIU the agent IPAM implementation does not.

Fix for excess IP release race condition. New operator flag excess-ip-release-delay is introduced to control waiting period before marking an IP for release.

Note : https://github.com/DataDog/cilium/pull/24 already received some valuable feedback from @aanm @gandro and @christarazi

/test

There's one more corner case that needs addressing.
After the handshake is complete and the operator is done releasing an IP, CiliumNode status (release-ips) and spec (pool) are updated in two consecutive requests. There's a tiny window between the two updates where the entry is removed from .status.ipam.release-ips but the IP is till present in spec.ipam.pool. It might be possible that the IP can be allocated between these requests.
Can i flip the order of update only when there are changes to IP release status ? Comments in syncToAPIServer() say that the status should always be updated first though. I don't fully understand why.
https://github.com/cilium/cilium/blob/eeb7f1b464b283dc0c2b2bcada2a149b40372437/pkg/ipam/node.go#L700-L701

There's one more corner case that needs addressing.
After the handshake is complete and the operator is done releasing an IP, CiliumNode status (release-ips) and spec (pool) are updated in two consecutive requests. There's a tiny window between the two updates where the entry is removed from .status.ipam.release-ips but the IP is till present in spec.ipam.pool. It might be possible that the IP can be allocated between these requests.

Oh wow, good catch! In dynamic cluster pool, we avoid this by having the agent remove the entry from status once it is no longer present in pool, which might also be an option here.

@gandro / @aanm Can i flip the order of update only when there are changes to IP release status ? Comments in syncToAPIServer() say that the status should always be updated first though. I don't fully understand why.

While I'm also not sure, I believe the order might have to do with the fact that we need to know the ENI metadata for each IP present in spec. If the agent sees an IP in the pool before it knows about its ENI, on other words to avoid this error being hit:
https://github.com/cilium/cilium/blob/124fa2be77c85d6bce65c15bbd91f69507876f70/pkg/ipam/crd.go#L528

The two CI failures (besides checkpatch) look unrelated:

Smoke Test with IPv6 has a failing host-to-b-multi-node-clusterip pod, which looks like a variant of https://github.com/cilium/cilium/issues/12279 https://github.com/cilium/cilium/runs/4305950192?check_suite_focus=true
test-1.22-4.9 hit https://github.com/cilium/cilium/issues/17919 and #17881

@christarazi Thanks for the review. Addressed most the the feedback except the conversations still unresolved. There's also one more refactor suggestion in the original PR https://github.com/DataDog/cilium/pull/24#discussion_r740761791 we can add to the list for the future PR.

/test

@hemanthmalla the unit tests failures are legitimate

/test

/ci-gke

Thanks @hemanthmalla! Merging.


Increment version for template releases

Increment version for template releases

Can one of the admins verify this patch?


Issue interface in version:<IP_ADDRESS>1

Today, without doing any update, I see this:

Why? Best regards.

Same issue here. Apparently, parse_ini_file was disabled in PHP's main config.

RainLoop does not use parse_ini_file function if it is disabled.

@umbertoB67
Any errors in php logs?

No errors in php logs, but now it works correctly!

Just FYI, today I got these variables instead of the actual labels in the login form. Ctrl + F5 fixed it (latest Chrome, Windows).