Rarity isnt showing.

When I run the npm run rarity it doesn't show me the correct data, occurrence: '0 in 4000 editions (0.00 %)'. I'm not sure why it says 0 in 4000. Is it because of const DNA_DELIMITER = "-"; ?

@Thebks I don't think the script can count occurances for a layer if you use displayName in src/config.js.

@bolshoytoster I don't follow, what do you mean by displayName?

@Thebks you can set displayName for a layer to make it show differently in metadata, it can mess with the rarity script.
Could you paste the full output of npm run rarity and your layersConfiguration here please.

This is the output for npm run rarity I just put the whole thing here and I have noticed that it shows occurrence for some
`  occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Mage', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Mortarboard',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PartyPopper',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PartyPopper',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Partyapopper',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PinkCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Pirate',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PurpleCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SmallBeenie',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Tourister',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Viking',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Viking',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'YellowCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Ears', weight: '1', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Ears', weight: '2', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Ears', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Alien',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Angry',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Big', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Boxy', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Focused',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'High', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Round',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Square',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Sweet',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: '3D', weight: '11', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: '3D', weight: '12', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: '3D', weight: '13', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Blank',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '8',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '9',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'GoldGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'GreyGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Oval', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Oval', weight: '19', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Oval', weight: '9', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'PinkGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PurpleGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'VR', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'VR', weight: '11', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'BigEarsHead',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BorderBigEarsHead',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BorderSmallEarsHead',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SmallEarsHead',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '1',
occurrence: '2 in 5 editions (40.00 %)'
}
{
trait: 'CigarLeft',
weight: '2',
occurrence: '2 in 5 editions (40.00 %)'
}
{
trait: 'CigarLeft',
weight: '3',
occurrence: '2 in 5 editions (40.00 %)'
}
{
trait: 'CigarLeft',
weight: '4',
occurrence: '2 in 5 editions (40.00 %)'
}
{
trait: 'CigarLeft',
weight: '5',
occurrence: '2 in 5 editions (40.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '1',
occurrence: '3 in 5 editions (60.00 %)'
}
{
trait: 'Serious',
weight: '2',
occurrence: '3 in 5 editions (60.00 %)'
}
{
trait: 'Serious',
weight: '3',
occurrence: '3 in 5 editions (60.00 %)'
}
{
trait: 'Serious',
weight: '4',
occurrence: '3 in 5 editions (60.00 %)'
}
{
trait: 'Serious',
weight: '5',
occurrence: '3 in 5 editions (60.00 %)'
}
{ trait: 'Smile', weight: '1', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '2', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '4', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '5', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'TongueOut',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Nose', weight: '1', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Nose', weight: '2', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Nose', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Nose', weight: '4', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Nose', weight: '5', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'SideBurns',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Blank',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BothEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'LeftEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'LeftEyeSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightEyeSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Spot', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Spot', weight: '12', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Spot', weight: '13', occurrence: '0 in 5 editions (0.00 %)' }
Trait type: Nose
{
trait: 'BurntSienna',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Charcoal',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CoralPink',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'DarkLavender',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'FlamingoPink',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'JungleGreen',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'KingdomGold',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Mahogany',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'MidnightBlue',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'NightHowl',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'OrangeYellow',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'OxfordBlue',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PastelPink',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Pewter',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PinkishBeige',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Rouge',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Umber',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'YellowishGreen',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Beenie',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Blank',
weight: '22',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BlueCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CowBoy',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CowBoy',
weight: '9',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Cowboy',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'GreenCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'HardHat',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'HardHat',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Hat', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Hat', weight: '4', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Hunter',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Hunter',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Hunter',
weight: '9',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Mage', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Mortarboard',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PartyPopper',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PartyPopper',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Partyapopper',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PinkCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Pirate',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PurpleCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SmallBeenie',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Tourister',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Viking',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Viking',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'YellowCap',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Ears', weight: '1', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Ears', weight: '2', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Ears', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Alien',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Angry',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Big', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Boxy', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Focused',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'High', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Round',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Square',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Sweet',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: '3D', weight: '11', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: '3D', weight: '12', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: '3D', weight: '13', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'Blank',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '11',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '12',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '8',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'EyePatch',
weight: '9',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'GoldGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'GreyGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Oval', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Oval', weight: '19', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Oval', weight: '9', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'PinkGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'PurpleGlasses',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'VR', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'VR', weight: '11', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'BigEarsHead',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BorderBigEarsHead',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BorderSmallEarsHead',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SmallEarsHead',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeft',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarLeftColor',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRight',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CigarRightColor',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'CrookedSmile',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Serious',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Smile', weight: '1', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '2', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '3', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '4', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Smile', weight: '5', occurrence: '0 in 5 editions (0.00 %)' }
{
trait: 'TongueOut',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'TongueOut',
weight: '5',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Nose',
weight: '1',
occurrence: '5 in 5 editions (100.00 %)'
}
{
trait: 'Nose',
weight: '2',
occurrence: '5 in 5 editions (100.00 %)'
}
{
trait: 'Nose',
weight: '3',
occurrence: '5 in 5 editions (100.00 %)'
}
{
trait: 'Nose',
weight: '4',
occurrence: '5 in 5 editions (100.00 %)'
}
{
trait: 'Nose',
weight: '5',
occurrence: '5 in 5 editions (100.00 %)'
}
{
trait: 'SideBurns',
weight: '1',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '2',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '3',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'SideBurns',
weight: '4',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'Blank',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'BothEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'LeftEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'LeftEyeSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightEyeScar',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightEyeSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{
trait: 'RightSpot',
weight: '10',
occurrence: '0 in 5 editions (0.00 %)'
}
{ trait: 'Spot', weight: '10', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Spot', weight: '12', occurrence: '0 in 5 editions (0.00 %)' }
{ trait: 'Spot', weight: '13', occurrence: '0 in 5 editions (0.00 %)' }
`

This is my layer configuration
const layerConfigurations = [   {     growEditionSizeTo: 5,     startEditionFrom: 1,     layersOrder: [       { name: "Background" },       { name: "Head" },       { name: "Spots" },       { name: "Side Burns" },       { name: "Ears" },       { name: "Caps" },       { name: "Eyes" },       { name: "Eyewear" },       { name: "Mouth" },       { name: "Nose" }     ],   }, ];

@Thebks if you make growEditionSizeTo bigger you might see higher occurances.

I know that I just made the small amount just so I can paste it here. Ok, lemme make the whole collection, I have 10 designs with all the layerConfigurations I showed in the previous comment and ill be making 1000 copies for each design. I'll get back to you if I face the same problem with the rarity. Thank You

@bolshoytoster Ok, I don't mind if the rarity doesn't show with npm run rarity afterall it's just an experimental feature. I just wanna know one last thing, does the _metadata.json file gets updated every time I make new copies?
Thank You.

@Thebks _metadata.json gets updated at the end of every time you generate.

Alright, That's all I wanted to know. Thank You.


Research: Design Backend Infrastructure

Talk with Sigman to gain access to the mcs Drury server. Though anyone can help with this task, this is a job that will be led by the Server Manager. Once the server is up, we'll need to discuss and design our backend. (Nodejs might be our only option).

I started doing the Medium tutorial i posted in the discord. I'm going to make a new branch and put it there, since there are still some aspects of it not working (at least showing red underlines).


InventoryIterator

Not sure for stdlib, but this is a quite common task for me.

Good in theory, but I'm not a big fan of unit.iterator() for items

Good in theory, but I'm not a big fan of unit.iterator() for items

Good in theory, but I'm not a big fan of unit.iterator() for items

What if unit.inventory? I mean
for i in anyUnit.inventory()
    // ...

Yea i think that's better if it works. You should also add some hotdoc with example code to the .inventory function then.

Status?

Done. Added functions from previous PRs (should I do it? not sure).

Done.

Thanks 🍬


getNameFor

I need something like this its very important.
[...]
public function getNameFor($route_path){
[...]
}
[...]

$klein->respond(array("GET", "POST"), "/Group/Edit/[*:groupname]?", function ($request, $response, $service, $app){
[...]
})->setName("GroupEdit");

$route_name = $klein->getNameFor($request->pathname());

would use !empty($this->matches) instead of count($this->matches) > 0

@jedi58 Two years ago i would rage and dont understand, but not now, im agree :+1:


manage.py stream_stats crashes with a ValueError

We have started with Zulip earlier this year with a data export from Slack in the migration. I suspect something may have created some inconsistencies in the data/state on the import at that time. I've had problems with creating a data export (this has resolved with the upgrade to the Zulip server v3.0 this week), and upgrades to a release did not work after an upgrade to the Git master branch using the default upgrade mechanism through the .tar.gz ball to the latest version. (Unfortunately I didn't take note or copy/paste the error, as the subsequent Git upgrade to the 3.0 tag has scrolled the message out of the terminal's buffer.)
Anyway, one problem does remain (mentioned in https://github.com/zulip/zulip-mobile/issues/4156 ), and maybe it'll be indicative of the underlying problem that the updater has faced, too
On manage.py stream_stats, the manager tool exits with a ValueError:
$ deployments/current/manage.py stream_stats --verbosity 3 ''
------------
          ( 28 public streams and 16 private streams )
------------
                   stream     subscribers   messages         type
 sales_and_some_marketing Traceback (most recent call last):
  File "deployments/current/manage.py", line 50, in <module>
    execute_from_command_line(sys.argv)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/zulip/deployments/2020-07-22-05-03-57/analytics/management/commands/stream_stats.py", line 52, in handle
    active=True))), end=' ')
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/query.py", line 256, in __len__
    self._fetch_all()
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/query.py", line 1242, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/query.py", line 55, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1127, in execute_sql
    sql, params = self.as_sql()
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 489, in as_sql
    where, w_params = self.compile(self.where) if self.where is not None else ("", [])
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 405, in compile
    sql, params = node.as_sql(self, self.connection)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/sql/where.py", line 81, in as_sql
    sql, params = compiler.compile(child)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 405, in compile
    sql, params = node.as_sql(self, self.connection)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/fields/related_lookups.py", line 130, in as_sql
    return super().as_sql(compiler, connection)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/lookups.py", line 163, in as_sql
    rhs_sql, rhs_params = self.process_rhs(compiler, connection)
  File "/home/zulip/deployments/2020-07-22-05-03-57/zulip-py3-venv/lib/python3.6/site-packages/django/db/models/lookups.py", line 257, in process_rhs
    'The QuerySet value for an exact lookup must be limited to '
ValueError: The QuerySet value for an exact lookup must be limited to one result using slicing.

The Zulip server is running on an Ubuntu bionic (18.04) instance on Digital Ocean (started from a DO Droplet).
Any assistance in tracking down the problem would be appreciated.

I've had problems with creating a data export (this has resolved with the upgrade to the Zulip server v3.0 this week)

This was indeed a minor data inconsistency caused by Slack import of "archived channels" in Slack, now fixed.

upgrades to a release did not work after an upgrade to the Git master

Generally master is ahead of the latest release at any time, so this is expected -- what you were trying to do here is actually a downgrade, which is generally not supported.  https://zulip.readthedocs.io/en/latest/production/upgrade-or-modify.html#upgrading-to-master may be helpful.

deployments/current/manage.py stream_stats

AFAIK this tool actually just hasn't been used in years.  I think long-term we'll want to delete it and replace it with showing this sort of data in "Manage streams" and/or /stats, but I suppose it could be worth fixing for now since people seem to want to use it.
@arpit551 want to take this issue?

Thanks @timabbott for the elaborations on the notes I had put in as context. Really helpful!
As for the stream_stats tool ... I've never needed it, but it was one of the tools that had shown an error when I was trying to debug previous problems. You know ... poking in the dark, trying to gain additional insights, as things seemed to be related to some streams. I've had one stream ID cough up on the previous archival attempt (one coming up from previous Slack times), so I've tried to drill into whatever I could find as being stream related.
Anyway, if it irks you ... fix the bug. But don't feel compelled to do it for me. It may just as well be deprecated until there's a better solution from your point of view available.
Cheers!


Questions about stride K and decoder window size.

I found K, dec_win_size and the dimension of features from backbone have some relations in decoder.
It's difficult to cope with them.
Can you tell me the corresponding dec_win_size when K=10 in your Supplementary and if it still uses features['8x']?
In addition to K=4, 8, 10, 16, can we use othe values which are less than 16?
Thanks a lot!

As we use rectangle window attention, dec_win_size is related to the spatial dimensions of point queries.

The choice of dec_win_size:
Suppose the spatial dimensions of sparse point queries are [sH, sW], then dec_win_size can be set to [sW/2, sH/4]. In this case, it is suggested that sH is divisible by 4 and sW is divisible by 2. In addition, we still use features['8x'] when K=10.

The value of stride K:
Theoretically, stride K can be set to any value. However, different choices of K will result in varied spatial dimensions of point queries, which may increase the difficulty of implementing rectangle window attention.


Don't show Present in affected, Absent in Unaffected if no sibs are loaded

Also, only show these rows in ranked tables for Sibs (doesn't apply to mother/father)


Refine the error feedback

The set of error messages and their context needs a lot of improvement.
Would it make sense to use the thiserror crate?
For example, if an unexpected TTLV tag value is encountered when deserializing the only information returned currently is UnexpectedTtlvTag(ItemTag(4325468), "0x42007F") with no context, i.e. which TTLV structure was the unexpected tag a child of or what the did the whole byte stream look like and where abouts was the read cursor in the stream?
The UnexpectedTtlvTag(ItemTag(4325468), "0x42007F") error message also unhelpfully uses decimal for the one tag and hexadecimal for the other, and doesn't say which was expected and which was not. Though the formatter for the message does include expected and actual so perhaps this is to do with unwrap()ing in a test rather than logging the error? The full error was:
thread 'tests::kmip_10_query_use_case_12_1::query_operation_failed_response_too_large' panicked at 'called
`Result::unwrap()` on an `Err` value: UnexpectedTtlvTag(ItemTag(4325468), "0x42007F")',
src/tests/kmip_10_query_use_case_12_1.rs:42:63

Here are some error scenarios that should probably be explicitly tested to verify and refine the information made available to the caller:
Deserialization scenarios to test and expected error details that we should receive:

[ ] I/O Error: Premature end of input (byte ctx, next expected TTLV element, tag tree path)
[ ] I/O Error: Other (byte ctx, next expected TTLV element, tag tree path)
[ ] Data Error: Unsupported length (exceeds max allowed by configuration) (max length allowed, found length)
[ ] Data Error: Malformed TTLV: Invalid type (byte ctx, tag tree path, found type)
[ ] Data Error: Malformed TTLV: Type not valid at this position (root must be a structure) (byte ctx, tag tree path, expected type, found type)
[ ] Data Error: Malformed TTLV: Invalid length (overflow of parent) (byte ctx, tag tree path, bytes remaining, found length)
[ ] Data Error: Malformed TTLV: Invalid length (byte length not valid for type) (ctx, tag tree path, current type, found length, reason?)
[ ] Data Error: Malformed TTLV: Invalid value (invalid boolean value) (byte ctx, tag tree path, found value)
[ ] Data Error: Malformed TTLV: Invalid value (invalid utf-8 string value) (byte ctx, tag tree path, value as safe text, utf-8 decoder error reason?)
[ ] Configuration Error: Invalid tag name (tag is not hex) (byte ctx, tag tree path, invalid tag)
[ ] Configuration Error: Invalid tag name (invalid variant matcher syntax) (byte ctx, tag tree path, invalid tag)
[ ] Configuration Error: Invalid tag name (cannot use transparent here) (byte ctx, tag tree path, invalid tag)
[ ] Configuration Error: Invalid tag name (cannot use override here) (byte ctx, tag tree path, invalid tag)
[ ] Configuration Error: Unexpected tag name (byte ctx, tag tree path, unexpected tag)
[ ] Configuration Error: Unsupported target type (byte ctx, tag tree path, unsupported type)
[ ] Configuration Error: Missing required tag (byte ctx, tag tree path, required tag)
[ ] Configuration Error: Unknown enumeration value (byte ctx, tag tree path, unknown value)
[ ] Configuration Error: No matching variant found (byte ctx, tag tree path, candidates)
[ ] Configuration Error: More structure members found than expected (byte ctx, tag tree path, ???)
[ ] Internal Error: Unsupported TTLV type (byte ctx, tag tree path, unsupported type)
[ ] Internal Error: Invalid state (wrong next field expected) (byte ctx, tag tree path, expected next TTLV element type, actual next TTLV elemenet type)

Where:

"tag tree path" denotes the ordered sequence of tag names on the current branch of the TTLV tree until the point of decoding.
"byte ctx" is the output "XXXXXXX >> XX << XXXXXXX" style output created using the ContextualErrorSupport trait.

Lots of improvements were made in the v0.2.0 release. I'll close this and come back to this topic again later if needed.


bibupload: modification date fix

Fixes issue with record modification date due to regeneration of
recjson cached introduced in
16fcacc7fbeb4fbece1c44823f5f66437ca11483

Signed-off-by: Lars Holm Nielsen<EMAIL_ADDRESS>

:shipit:


fix: React 19 bool prop to attr value bug

fix https://github.com/muxinc/elements/issues/1015

❤


Added my record to contributor's list

Awesome, thank you very much, and welcome to bitrise contrib! ;)


Adjust Node Label Conditions Based on Full Label Name

The OCS operator searches for the topology.kubernetes.io/zone label key using a string containing logic.
If the customer has a node with a label that includes the string zone.
The OCS operator can read another label containing 'zone' instead of topology.kubernetes.io/zone.

/lgtm
/cc @iamniting

/retest

/test ocs-operator-bundle-e2e-aws


can "aws-amplify" usable with Repack

Ask your Question

Hi everyone,
I have a problem when using the aws-amplify package
It can work with the metro, but I got an error  when running with Webpack 5
How can reproduce:

Clone example repo from https://github.com/callstack/repack-examples/tree/main/module-federation
Add libs : aws-amplify amazon-cognito-identity-js @react-native-community/netinfo @react-native-async-storage/async-storage
import { Auth } from 'aws-amplify';
Call any function with Auth
example:
 Auth.currentSession()          .then((res) => {})          .catch((err) => {});

[app2] ✖ [09:14:22.558Z][LoggerPlugin] Failed to build bundle due to errors [app2] ✖ [09:14:22.558Z][LoggerPlugin] Error in<EMAIL_ADDRESS>Module not found: Error: Recursion in resolving [app2] Stack: [app2]   resolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native/dist/cjs) url [app2]   parsedResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native/dist/cjs) url module [app2]   describedResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native/dist/cjs) url module [app2]   rawResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native/dist/cjs) url module [app2]   internalResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native) url/ module [app2]   parsedResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native) url directory module [app2]   describedResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native) url directory module [app2]   rawResolve: (/Users/xxxx/workspace/xxxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native) url directory module [app2]   internalResolve: (/Users/xxx/workspace/xxx/repack-examples/module-federation/app2/node_modules/@aws-sdk/url-parser-native) url/ directory module
Pls help. Thank guys.

Anyone can help me ~~

I have resolved it. Here is a suggestion for this.
I have added this in webpack.config.js
{
          test: /\.[jt]sx?$/,
          include: [
            /node_modules(.*[/\\])+@aws-amplify/,
            /node_modules(.*[/\\])+@aws-sdk/,
            /node_modules(.*[/\\])+amazon-cognito-identity-js/,
            /node_modules(.*[/\\])+fast-xml-parser/,
            /node_modules(.*[/\\])+quick-lru/,

          ],
          use: {
            loader: 'babel-loader',
            options: {
              presets: [
                [
                  '@babel/preset-typescript'
                ]
              ],
            },
          },
        },


Parses the string value when getting the value for multicastEnabled

Currently after calling SetMulticastEnabled(false) the sting value is changed and because GetMulticastEnabled() does not use the string value multicast is never disabled.

The 2nd commit is a bit tricky. On a system I have multi IP interfaces, a mix of IPv4 and IPv6 addresses. When I start smudge 2 times (on IPv4 and different ports) I receive multiple multicast messages, some send from IPv6 interfaces. I think that this is causing a fatal exception:
nameBytesLen = 6, len(bytes) = 18
 Warn 27/Mar/2018:17:34:33 CEST - 13.X.X.98:9999 does not have a status! Setting to ALIVE
nameBytesLen = 6, len(bytes) = 18
 Warn 27/Mar/2018:17:34:37 CEST - 13.X.X.98:9998 does not have a status! Setting to ALIVE
nameBytesLen = 221, len(bytes) = 28
panic: runtime error: slice bounds out of range

goroutine 62 [running]:
github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge.decodeMulticastAnnounceBytes(0xc42028e000, 0x1c, 0x800, 0x0, 0x0, 0x0, 0x0, 0x0)
	/Users/eelco/go/src/github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge/membership.go:203 +0x1f6
github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge.listenUDPMulticast.func1(0xc4202287e0, 0xc42028e000, 0x1c, 0x800)
	/Users/eelco/go/src/github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge/membership.go:361 +0x5d
created by github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge.listenUDPMulticast
	/Users/eelco/go/src/github.com/eelcocramer/tamtam/vendor/github.com/clockworksoul/smudge/membership.go:360 +0x1a7

That made me think that it is always possible that smudge would receive an invalid multicast packet, every program can send on that address and port so checking if the packet can be parsed would make things more robust. That is what I've tried to do with that commit.

To be clear, the last commit fixes that fatal exception for me. In the debug logging I can see that there are quite some multicast messages being dropped because of the rule that is implemented.

Giving this a bump. I'm wondering what you make of this.


INFRA-57.1: Fix ctest failures on MacOS

Describe the bug
We've been ignoring a set of test failures on the MacOS due to these tests passing on all the other platforms. MacOS has a fairly unique situation where this platform is cross-compiling using apple-clang for C, C++ and GNU for Fortran. These two sets of compilers have their own underlying C++ and C standard libraries which makes it challenging to get all the code to link and load with the proper standard libraries. This might be the reason we see tests fail on MacOS while passing on other platforms.
To Reproduce
Steps to reproduce the behavior:
Build jedi-bundle on MacOs (either native Intel, or native ARM architectures) and run ctests.
Expected behavior
All the ctests pass
System:
What system(s) are you running the code on?
MacOS
Additional context

@srherbener We should consider adjusting the estimates for the issues related to this epic. They are either overlapping or duplicates of each other.

There is definitely overlap - eg, fixing the signal trapping will probably fix some of the test failures. I somewhat arbitrarily reduced the estimates across the issues attached to this epic. There is a total of 5 story points now.

Can this epic be put back into the epic pipeline please @srherbener @climbfuji

Sure! I just moved it back.

Does this epic need to be extended into Q3? @srherbener

@symoore90 thanks for checking, yes this is not completed yet so it needs to be in Q3.

@srherbener It looks like I don't have permissions to edit anything on this epic to you mind extending the date out to Jan 8 please

@symoore90 Can you try again, please?

It's still not letting me edit anything @climbfuji

I've updated the end date for this epic.

I agree. I'll update the end date.

@symoore90 We've updated the end date for INFRA-57.1 to March 31, 2024.

I am closing this. We'll deal with the remaining issues in AOP24 in the CI epic (I moved them to the CI parking lot)


Add additional pipeline step to build arm image

Adds another pipeline step to build a multi-arch amd64 and arm64 image
For https://github.bus.zalan.do/teapot/issues/issues/3171

👍

:+1:

👍


Heldeska

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: 500
Error Message: An error has occurred.
Version: 0.24.9
OS: win32
OS Release: 10.0.19045
Product: Visual Studio Code
Product Version: 1.72.2
Language: en

Call Stack
new RestError extension.bundle.js:2:1709073
extension.bundle.js:2:1696547extension.bundle.js:2:1696547

Please provide repo steps

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Feature add for GenerateWryeBashTags.pas

Updated GenerateWryeBashTags.pas to use the plugin currently highlighted in the leftmost xEdit pane as the default plugin in the prompt box.

@ArcaneTourist I never saw a notification for this PR. Can you resubmit your PR at the new repo?
https://github.com/fireundubh/WryeBashTagGenerator


Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues doesn't use Workload Identity

We host Azure Functions isolated in AKS and have recently migrated from AAD Pod Identity to Workload Identity. However, after this change the function couldn't access Storage Account Queue with the following error:
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[1]
      DefaultAzureCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: 5fd4e2bb-c30f-4a08-b831-b52e53499d1c
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[1]
      EnvironmentCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: 5fd4e2bb-c30f-4a08-b831-b52e53499d1c
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[3]
      EnvironmentCredential.GetToken was unable to retrieve an access token. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: 5fd4e2bb-c30f-4a08-b831-b52e53499d1c Exception: Azure.Identity.CredentialUnavailableException (0x80131500): EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[1]
      ManagedIdentityCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: 5fd4e2bb-c30f-4a08-b831-b52e53499d1c
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[4]
      Probing IMDS endpoint for availability. Endpoint: http://<IP_ADDRESS>/metadata/identity/oauth2/token
←[40m←[32minfo←[39m←[22m←[49m: Azure.Identity[5]
      IMDS endpoint is available. Endpoint: http://<IP_ADDRESS>/metadata/identity/oauth2/token
←[40m←[32minfo←[39m←[22m←[49m: Azure.Core[1]
      Request [5fd4e2bb-c30f-4a08-b831-b52e53499d1c] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=REDACTED&resource=REDACTED&client_id=REDACTED
      Metadata:REDACTED
      x-ms-client-request-id:5fd4e2bb-c30f-4a08-b831-b52e53499d1c
      x-ms-return-client-request-id:true
      User-Agent:azsdk-net-Identity/1.4.0,(.NET 6.0.25; Linux 5.15.0-1042-azure #49-Ubuntu SMP Tue Jul 11 17:28:46 UTC 2023)
      client assembly: Azure.Identity
←[40m←[37mdbug←[39m←[22m←[49m: Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcFunctionInvocationDispatcher[0]
      Adding jobhost language worker channel for runtime: dotnet-isolated. workerId:1547cb39-27de-4f71-b670-e7867e9f747b
←[40m←[32minfo←[39m←[22m←[49m: Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcFunctionInvocationDispatcher[0]
      Worker process started and initialized.
←[40m←[1m←[33mwarn←[39m←[22m←[49m: Azure.Core[8]
      Error response [5fd4e2bb-c30f-4a08-b831-b52e53499d1c] 404 Not Found (80.6s)
      X-Content-Type-Options:REDACTED
      Date:Wed, 29 Nov 2023 07:01:20 GMT
      Content-Type:text/plain; charset=utf-8
      Content-Length:275

←[40m←[1m←[33mwarn←[39m←[22m←[49m: Azure.Core[7]
      Response [5fd4e2bb-c30f-4a08-b831-b52e53499d1c] took 80.6s

As you can see it uses User-Agent:azsdk-net-Identity/1.4.0,(.NET 6.0.25; Linux 5.15.0-1042-azure #49-Ubuntu SMP Tue Jul 11 17:28:46 UTC 2023) and after some digging I have probably found why. The reason for this is that the Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues references Microsoft.Azure.WebJobs.Extensions.Storage.Queues 5.0.0, which in turn references Microsoft.Extensions.Azure 1.1.1, which in turn references Azure.Identity 1.4.0 which doesn't support Workload Identity.

It looks like upgrading Microsoft.Azure.WebJobs.Extensions.Storage.Queues to 5.1.3 helped despite the fact that it references Azure.Identity 1.7.0 while the documentation states that it has to be Azure.Identity 1.9.0

One more finding: the token acquiring from the Azure Function succeeded because according to the logs, the DefaultAzureCrential pipeline successfully stopped at ClientAssertionCredential which was used by TokenExchangeManagedIdentitySource.

The identity package has been upgraded now. In host as well as the storage extension.


Update strings.xml

Added more strings into the Simplified Chinese version of the file for internationalisation.

@pipix51 Why have you deleted strings? Have you checked if these strings are still there in the other string resources?

@pipix51 Why have you deleted strings? Have you checked if these strings are still there in the other string resources?

@mananwason  Yes, I have check if the strings are still in the other string resources. I just repositioned those strings so that it is similar to the original strings.xml layout.

@mananwason  Yes, I have check if the strings are still in the other string resources. I just repositioned those strings so that it is similar to the original strings.xml layout.

Okay Thanks. I'm merging this!


chore(package): Add repository field to package.json

This adds the repository field to the package.json to avoid
npm displaying the npm WARN<EMAIL_ADDRESS>No repository field. warning.
Change-Type: patch

@jhermsmeier please rebase

@zvin sure thing, done!


docs(dialog): emphasize clicking on backdrop in disableClose docs

Mentions the backdrop explicitly in the disableClose docs in order to avoid confusion.
Fixes #11750.

Is there a way to handle this a little bit better than updating the documentation? It still seems like a design flaw. It should operate just like MatSelect or MatMenu. There is no backdrop with those components but when a user clicks outside of it, it automatically closes. The MatDialog should have the same behavior if disableClose is used. Having a backdrop and disabling the ability to close the dialog serve two different use cases and shouldn't be dependent on each other. I understand there is a workaround by adding a custom backdropClass, but it's a workaround. disableClose and hasBackdrop are two different things and shouldn't be dependent on each other.

It's a supported case to turn off the backdrop and let users interact with the page behind the dialog; it doesn't really have anything to do with disableClose at all.

@jelbourn That is also a valid case which is why disableClose should work regardless of the value of hasBackdrop


Add the ability to store CrewAI's memory (short and long) in a database other than Chroma and SQLLite

I'm trying to ship a CrewAI application into production. The current implementation of short and long-term memory use SqlLite and ChromaDB and don't allow the ability to swap out these stores with anything else.
More specifically, I'd like to use CosmosDB as the store for these, but I don't have a mechanism to write my own implementation. Currently there's not an interface, but the actual methods that store and retrieve data don't seem specific to Chroma/SQLLite at first glance.
I'd really like memory classes like LongTermMemory to be able to accept an overriding implementation instead of CrewAI creating it directly, like this:
storage = LTMSQLiteStorage()
I would want the ability to pass my own implementation into the LongTermMemory constructor, and then, if I don't override it with something, it would default to LTMSQLiteStorage to have a great experience out of the box as it currently does today.
TL;DR:
As someone shipping a CrewAI app to production, I want the ability to write my own implementation for short-term and long-term storage, so that I can store this information externally to support more scaling options as well as to have the option to not have to introduce a new database technology within my organization.

This is the discord post related: https://discord.com/channels/1192246288507474000/1250488576404226078

You could use mem0 by @mem0ai as it supports both Qdrant and Chroma (vector stores) and SQLite (traditional datastore) out of the box


cleistogeny, fibularia (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Update datamarts-get-started.md

Added "Adding or removing objects to the default dataset" and "Using model view layouts" sections

@davidiseminger
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Why is this not accepted? Are there any blockers still? @davidiseminger

Looks good!
#sign-off


Update GHA workflow to add Scout comparison into PRs

can we merge this one before #114 to see the output in #114 ?


Where is 'habitat_sim._ext'?

❓ Questions and Help
File "/home/zhp/habitat-sim/habitat_sim/nav/init.py", line 1, in from habitat_sim._ext.habitat_sim_bindings import (
ModuleNotFoundError: No module named 'habitat_sim._ext'
help!!!

This happens if you try to run habitat from the root folder of the habitat-sim git repo and habitat-sim has not built with the --inplace argument. Either build it using build.sh, delete the habitat-sim folder, or call it from a different location.

Coule you add above statements to the readMe?

This issue is fixed in more recent versions


[YM-29951] Release 3.0.1

## Purpose
Contains a couple of bug fixes on the Android side of the SDK:

Upgrade RN to 0.63.5 to fix Android sample app crash. More info here

B&T'ed


Fixed font color for textarea

Fixes #25
Overview
The textarea font-color has been changed to $carbon--black-100 for visibility. Tested on Edge, Chrome, and Firefox.

@camilasb For your review (please ignore the ERROR):


disable "conversation view off"

Hi,
is it possible disable conversation view ?
I think this :

Hey @joazif — thanks for reporting this. N1 is built around a threaded conversation model and we don't have any plans to support non-threaded display. If you're interested in working on this, you could probably achieve this with a package but we won't be building it into core.

Actually, I prefer non-threaded display mode. Because it is really not easy to find and follow emails :-1:

Same here

Same. Nylas seems super nice, but not being able to disable conversation view is a dealbreaker for me. To each their own!

Ah, bummer. Same here. :(

cannot disabled? T_T awesome product anyway

Why do so many startups do this - develop on assumptions instead of user feedback?  Over and over again, I watch startups accelerate their burn rate, with failure to achieve market success due to lack of true market fit.  Nylas has the potential to be the best mail client on the market.  The one major issue is unthreading conversations.  If Nylas ONLY wants to be a personal email client, then threaded conversations is not a problem.  However, many, like myself, are desperately looking for a good, clean mail client that can be used for work AND personal emails.  For work, being able to place client and employee emails into their corresponding folder, as well as snoozing are insanely valuable to my productivity.  But if conversations between 10 different employees or a mixed bag of clients and employees are grouped together, it makes it impossible for me to organize and categorize the emails, meaning my productivity with my inbox hits a wall.  I LOVE CloudMagic, but it too has fallen short with the dreaded conversation threading.  However, at least they are wise and listening to their audience and implementing the change.  I am interested to see who gain more traction in the market place in the next 180 days, as CloudMagic is implementing the option to unthread conversations within 30 days. All the best of luck to you Nylas, without listening to your audience, you are going to need it.

I hope this thread is old and the Nylas team has changed their mind on threaded views. I prefer threaded views. However, the current implementation is pushing me away from Nylas. Currently, when conversation view, I end up with every email that was part of that thread repeated inside every email in the thread. Gmail has solved this beautifully. That is by truncating anything prior to the last message. You'll see a little button with ellipses. As it is right now in Nylas I am constant scrolling a long list of replies just to get past one email in the conversation. Worse, the replies are indented, and at some point become one character wide. It is kinda ridiculous. I too feel that Nylas has the potential to be the best email client out there. I even paid for it. Sadly, I am likely to stop because of this poor conversation view.

Just another quick thought on conversation view. If the last email in the conversation had an indication that it is the last. Maybe in the header to left of the reply button - text that read "last in thread". That way I would not have to scroll down past all of the nested replies in that individual email to check if it is the last. This is not a replacement for truncating all of the nested replies but it would potentially be a "quick" fix for the time being.

No, they did not change their mind, but check out CloudMagic.  They listened to their audience and have adjusted the conversation view, unlike Nylas, Canary, Polymail and others that THINK they know what the audience wants, despite multiple pleas to change it.
Kind Regards,
Paul Jerome
-----Original Message-----
From: dkraljic<EMAIL_ADDRESS>To: nylas/N1<EMAIL_ADDRESS>Cc: paulzny<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Wed, Aug 10, 2016 8:22 am
Subject: Re: [nylas/N1] disable "conversation view off" (#325)
I hope this thread is old and the Nylas team has changed their mind on threaded views. I prefer threaded views. However, the current implementation is pushing me away from Nylas. Currently, when conversation view, I end up with every email that was part of that thread repeated inside every email in the thread. Gmail has solved this beautifully. That is by truncating anything prior to the last message. You'll see a little button with ellipses. As it is right now in Nylas I am constant scrolling a long list of replies just to get past one email in the conversation. Worse, the replies are indented, and at some point become one character wide. It is kinda ridiculous. I too feel that Nylas has the potential to be the best email client out there. I even paid for it. Sadly, I am likely to stop because of this poor conversation view.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

  It's literally impossible to see who a message is from since so many names are crammed into a little subject line. Not to mention organizing and finding mail is a huge chore. I am going to be requesting a refund.

Hi Vinny,
Try Newton (formerly Cloud Magic) or AirMail 3.  Honestly I like the N1 interface better than those two, but both companies actually listen to their audience and made conversation view and option.  Even Google/Gmail made conversation threading an option.  I don't understand why email client providers don't follow.
Kind Regards,
Paul Jerome
-----Original Message-----
From: Vinny Troia<EMAIL_ADDRESS>To: nylas/N1<EMAIL_ADDRESS>Cc: paulzny<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Tue, Dec 13, 2016 8:34 pm
Subject: Re: [nylas/N1] disable "conversation view off" (#325)
Conversation view sucks.  It's literally impossible to see who a message is from since so many names are crammed into a little subject line. Not to mention organizing and finding mail is a huge chore. I am going to be requesting a refund.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

This was a dealbreaker for me as well. Nylas looked nice, but conversation view sucks, and sucks hard. Not being able to turn it off made me uninstall Nylas so glad I didn't pay for this app.

My problem is more that conversation view doesn't work. It seems like it is based purely on the subject of emails. So I have conversations spanning three years because they have the same subject. Not to mention receiving emails without subjects that all get lumped into one big conversation. We should be able to turn of conversation view, or the very least tweak the time period of emails that get grouped into a conversation.
Unfortunately, I already paid for the app, but I will definitely not review my subscription.


Testing/bernede1/pre alloc fix

Following on #638. Added only the last commit.

Ah ah! Looks like it's working great indeed, and now sharing allocation on ruby!


Replace async-foreach?

This project is using async-foreach, which is an unlicensed and unmaintained package. Is it possible to replace it? I see @EightArmCode is trying to fix the situation here https://github.com/cowboy/javascript-sync-async-foreach/pull/10 but that's unlikely to get merged and released as @cowboy did not touch the project for 5 years.
Technically it is illegal to dynamically link code without explicit license, which renders node-sass unusable in any environment where people care about licensing.

Looks like it's used in the CLI bin file only https://github.com/sass/node-sass/blob/d3aebe72d2735b79e68019b3801000fe8178f18b/bin/node-sass
Happy to review something that replaces the functionality. Not sure if this was used for old Node compatibility, if so we might be able to take an ES6+ patch in the v5 branch

To me the easiest and I believe drop-in replacement would be var forEach = require('async/each') https://caolan.github.io/async/docs.html#each

Please use a different library. There are much better choices than that code I wrote seven years ago.
Also, the node-sass project maintainers should consider dropping support for very old versions of node. Doing so will decrease the costs of maintaining the project. I recommend looking at other projects that are likely to be used with node-sass. For example, webpack, babel and eslint all appear to require node 6+.

We will be dropping support for node < 6 in v5
On Mon., 12 Nov. 2018, 1:47 am Ben Alman<EMAIL_ADDRESS>wrote:

Please use a different library. There are much better choices than that
code I wrote seven years ago.
Also, the node-sass project maintainers should consider dropping support
for very old versions of node. Doing so will decrease the costs of
maintaining the project. I recommend looking at other projects that are
likely to be used with node-sass. For example, webpack, babel and eslint
all appear to require node 6+.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2487#issuecomment-437675953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWNoZhA-7cOE2tmn-32nZzdCXFGzKks5uuDh0gaJpZM4WVbUy
.

Addressed this in #2312

Fixed in #2312


SQL: column references cannot be replaced by constants

Affected Version
0.16.0 and 0.17.0
Description
The following query throws an exception. However if the LOOKUP is performed on a column reference, then it works even though the column would also just evaluate to a string value for each row.
SELECT
   LOOKUP('some', 'adtype_by_adtypeid') AS tst

What exception do you get? A query like that should work fine, as long as the lookup exists and is loaded on the Broker that handles the query.

I'm getting the following;
SQL Error [00000]: Error -1 (00000) : Error while executing SQL "SELECT¶   LOOKUP('some', 'adtype_by_adtypeid') AS tst": Remote driver error: RuntimeException: java.lang.AssertionError: Type mismatch:¶rowtype of new rel:¶RecordType(VARCHAR tst) NOT NULL¶rowtype of set:¶RecordType(VARCHAR NOT NULL tst) NOT NULL -> AssertionError: Type mismatch:¶rowtype of new rel:¶RecordType(VARCHAR tst) NOT NULL¶rowtype of set:¶RecordType(VARCHAR NOT NULL tst) NOT NULL

This is with SQL compatible null handling turned OFF.
I can check tomorrow what I get back if I have it switched on.
I'm beginning to understand that the behaviour under compatible null handling is more important to get right as it is the desired true north state to thave compat mode switched on, but as we experience a performance issue with compat mode, we need to stick with the default mode for now. I'll update the ticket tomorrow when I have access to the cluster again with what I get under compat mode.


Var post empty set

Motivation
Closes #1967 #2311 #2311
Changes
Hare always finished with a result
If preround fails empty set is used for hare continue
If hare fails empty set is considered as hare result

Moved to https://github.com/spacemeshos/go-spacemesh/pull/2438


Access keys assigned to an IAM user is limited to 2

Policy Template Name
AWS Rotation Policy
Issue Type
Access keys assigned to an IAM user is limited to 2
Policy Template version (Bug Only)
1.4
Error Messages (Bug Only)
errorMessage": "Cannot exceed quota for AccessKeysPerUser: 2"

It's worth noting that the policy works as-is.
When the error occurs, the policy takes action to delete a key and then create the new key.
However, it is understood that the error that is generated in AWS by the failed request is confusing.
So the plan is to update the policy to avoid this error.

Solved by PR: https://github.com/rightscale/policy_templates/pull/122


feat(react:Tab): Add option to not automatically scroll Tab(s) into view

Description
Add option for consumer to specify that a Tab should not be scrolled into view upon focus. The current implementation is particularly annoying for tabs that are not in view initally on a page - e.g. the middle of the page (or wherever the tabs are located) is scrolled into view upon landing on the page.
Also, remove "javascript:void(0)" as React adds a warning to browser console: "A future version of React will block javascript: URLs as a security precaution. Use event handlers instead if you can."
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

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.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

Doesn't look like this is working on Safari for me, but seems to work on Chrome and Firefox. Good catch with regards to the javascript:void(0) stuff, but instead of removing the href altogether, could you use one of these methods suggested by React team? Concerned that removing the href altogether would mess with the accessibility tabbing

Weird, appears safari probably doesn't support the option. Maybe I'll prevent the call to .focus() altogether if the new prop present
And yes, will add the href back in!

LGTM! @jcatalan-cisco I think this is good to merge in unless if we want another set of eyes on it 👍🏽

@eazy-g please just merge the latest base branch changes here and then I'll merge 👍

Thanks @jcatalan-cisco just hung up on a percy diff now

@eazy-g I did the override on the percy test, but there is another that seems stuck. Maybe you can force push and retrigger?

Hmm, this test_web_components step still sticking @jcatalan-cisco


Fix docker compose alias in .sh files

Fixed in https://github.com/aurora-is-near/standalone-rpc/pull/10


Arcyd: remove plugin vestiges

We stopped supporting plugins some time ago but some of the supporting
code was left in, so the documentation was potentially confusing.
Remove the last vestiges of plugin support, it will still be possible to
revive it from the history of this repo.
Test Plan:
$ ./precommit.sh

LGTM.

Thanks!


feat: add support for logging

Coverage remained the same at 100.0% when pulling 40068b1fbcac8c84610117627386356e90228c81 on feature/logging into 1059d3b1e9f38a6d7b66f481177bfc20882536a4 on master.

Coverage remained the same at 100.0% when pulling a3082bfa6612416d29293ebf7402e10c03305bc3 on feature/logging into 1059d3b1e9f38a6d7b66f481177bfc20882536a4 on master.


ImageMagick - Right way to go ?

Hi,
I have a generall question regarding ImageImagick. Why did you decide to implement it? As far as I remember script worked without it.
I usually see external tools and bridges as a major design flow because of lack of flexibility and dependency on external provider. Perhaps there is a good reason for imagemagick?
Best regards

Imagemagick was in the script since the beginning, it is the tool that the script used to make gifs, it is only not needed when making static images legofied. You can see it in the (first commit)[https://github.com/JuanPotato/Legofy/blob/f5eb2000ccd6043ae56c007ee5a6a9f6d7586f5e/legoify.py#L114]

Ok , I'll check if there is anything suitable

I have seen that you can save a gif in PIL to be animated, but last time I tried it greatly messed up.
try this and tell me what happens
i = Image.open("test.gif")
i.save("test_pillow.gif", save_all=True)

I've made some test and the whole animated gif thing is not achieveable by PIL alone. I've made some reasearch and put together working solution here: https://github.com/JuanPotato/Legofy/pull/71

Hi when I ran legofy image.jpg it returns
Could not find the MAGICK_HOME environment variable.
I already install imagemagick 64-bit in my window
what's the next step to resolve the issue?
thank you,

@hungmeenhong Just wait a bit, I'm merging things now.

@hungmeenhong running legofy image.jpg (static images) should work with the latest commits. If it is not working please try to see where imagemagick is installed and add the environment variable by using setx MAGICK_HOME C:/path/to/imagemagick

@JuanPotato  now it says
Brick asset "C:\Users\jhung\AppData\Local\Continuum\Anaconda\lib\site-packages\legofy-0.0.1-py2.7.egg\legofy\assets\bricks\1x1.png"
was not found.

@hungmeenhong you are running python setup.py install and then legofy image.jpg right? Also does that directory exist when you use file explorer? or to what level does it exist?

Right, so I copy paste the setup.py and legofy folder under Anaconda file, wrote
python setup.py install
legofy image.jpg
this is the returning error message:
Brick asset "C:\Users\jhung\AppData\Local\Continuum\Anaconda\lib\site-packages\legofy-0.0.1-py2.7.egg\legofy\assets\bricks\1x1.png" was not found.
When I check "lib" folder I couldn't find it. There's one "Lib" folder, but I don't think they are the same. @JuanPotato

@hungmeenhong the "Lib" folder should still work, it works on my laptop. Are you sure you are copying everything into the folder?

@JuanPotato  I think I got it right now, so  assets folder wasn't in legofy. So I copy the assets from your  original legofy folder into it, and it worked! thanks!

Looks like PIL supports saving gifs : http://pillow.readthedocs.org/en/3.0.x/handbook/image-file-formats.html#saving-sequences

@niroyb see the fourth comment in this issue.

@JuanPotato I've made some tests what save_all behaves weird and sometimes inconsistent. E.g. It sometimes misses 1 frame and I'm not sure why.
I've also found some threads like this one : https://github.com/python-pillow/Pillow/issues/1355
I'll give it another try today and give you heads up.

Ok, so I took a deeper look at Pillows GifImageFile class and it won't be that easy to adopt native Pillow classes . First of all , single frames are accessible via ImageSequence class which is basically a wrapper for more direct seek() function (GifImagePlugin.py). GifImageFile object (in this case PIL.Image) is always represented by a single frame. seek() function only replaces the frame representation. More than that - it does it each time by reading the file on the bit level.
GifImageFile also doesn't have any easily accessible function that would reassemble set of singles images into Gif animation. There is whole SAVE_ALL architecture based on drivers for particular Image formats but it requires more time to work with and probably a customized GifImageFile mutation. And well, thats what https://github.com/CasualBeer/images2gif library basically is.
I going to read more about PIL but afaik there is no "Image-Sequence" object that is saveable.


Google Analytics Firebase Does Not Support UWP Apps

Following your Getting Started github document at https://github.com/dotnet/windows-sdk-for-google-analytics/wiki/Getting-Started, we are required to select MobileApp rather than WebApp Property when registering a UWP app.  However, Google Analytics is forcing to create MobileApp from Firebase but Firebase does not support UWP (as per attached screenshot).
Therefore, we are unable to create any new Windows app properties.

You can create a web app in Google Analytics then Create a new View and make the new view mobile without needing to use Firebase.

I have an UWP app, planning to integrate firebase analytics. Is this feasible? How do I go about doing it since it allows only three options iOS, Android and web app. Please advice.


Show information when platform does not support automatic updates

Description of the Change
Currently, when on a platform that does not support automatic updates (ie. Linux) the updates section of the About screen is hidden completely. This change leaves the updates section visible, but hides the "Check Now" button and the checkbox at the bottom. Instead, the text informs the user that their system is not supported and provides a link to the Atom Readme, where they can download the latest version.
Before:

After:

Alternate Designs
There are currently at least two ways for Linux users to update Atom besides manually downloading a fresh .deb or .rpm file each time a new version is released:

Updating through native Linux tools via the unofficial Atom PPA
By installing the third-party Atom Updater package

Incorporating either of these methods into the About page (or using code similar to Atom Updater) would do much more for the user than a link. However, if major code changes are undesirable for now, my proposed change is still better than nothing.
Benefits
It is made more clear that automatic updates are not supported on Linux; hopefully this will mean fewer redundant issues on this topic.
Possible Drawbacks
This does not address the lack of automatic updates (as I understand, these are blocked on Electron's autoUpdater). The code will likely have to change again in the future, either when the Electron groundwork is done or some other workaround is implemented.
Applicable Issues
#38

How does this work for portable mode installers that also don't automatically update?

This particular PR relies on UpdateManager.State - we should check that portable mode correctly reports Unsupported but that doesn't have to be part of this PR.

If you're saying that Atom never supports auto-updates in portable mode, I think a note about that should be added to the Flight Manual page (for Windows and Mac users, at least).
Is there any difference between the normal Linux install and portable mode? As I understand, all I would need to do to test this is move the .atom directory into the same folder as my Atom installation, right?

Yes, Atom does not support auto-updating in portable mode.   Basically the auto-updater downloads a new setup program and that would want to install in a regular non-portable mode, modify system paths, icons etc.
So it is disabled. Yes, a note in the flight manual would be a good idea.
Normal Linux installs use .rpm or .deb packages - we don't provide a specific portable installation there.

Is there anything I can do to help get this PR merged?
I don't think the Travis failure was caused by my changes - the failing tests weren't touched by my code. So I think it might be a result of the Atom/Electron version bump between Build 212 and 214.

That build failure was a problem that has since been resolved.
I think the only real issue is that it links to the flight manual but we don't have a section in there on manually updating.  @lee-dohm can we put something in there?

@damieng We could totally put something in there. I'm not sure what we would put in there other than "do whatever you did to install in the first place again". If you're in a situation where you have to manually update, I fear there may be too many scenarios to list. I'm totally open to suggestions or a PR though :+1:


Update package name and android_compose_layout_material_bottom_sheet2 snippet.

<  close deposit

_ No description provided. _

]deploy close


There are any plans for a searchable multiple choice and a searchable single choice dialogs?

That would be great!

Sorry, no

oh!


fix TLS key logging file entry corruption on non-Windows

On Windows I see properly formatted key logging files that include CRLF, e.g.
CLIENT_RANDOM 1acfa70620279d4e2b2895fc510897db6b164be7c97b5e8ee2d3180a551d52ec 4214c5de0498316cedea48c767b97dcbc3cf8121c21b1c441026297796a8b96f502d06de280442b8232221f6be1fbf3a

However, on macOS and Linux see first 10 characters missing. Also there is no CR at the end of the line, e.g.
  DOM 0d462bc4dd7884a8ef0d6f493de9a3d9622e88cd22e117f41eff6a833317cb99 aeac8859bdffc000d385b23a9dbec5a6397a7e27097399c23e838617d3a22da00bcf3722d543c93015bd117b11c8a413

This fix changes "\r\n" to "\n" which Wireshark appears to accept on both Windows and macOS.

I notice this PR is going stale. We are locally patching our gRPC library so we can use TLS keys on non-Windows, and would really like to see this merged.

ping @Vignesh2208


Frontend: CSS units

Description 📜

Adding the explanation for various css measurement units like cm, px, em, vh etc in form of documentation

Domain of Contribution 📊

[x] Frontend Dev (HTML, CSS, JS)

/assign

Is this issue still on? I'd love to contribute

@joshi-kaushal Yes, I'm working on this issue


fixing source map issues by including src directory

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fixing source map issues by including src directory

Fixing #257


CB-11850 Error message in case of delete node from orchestrator is mi…

…sleading
See detailed description in the commit message.

@horadla23 Is there a reason this remained in draft?

@horadla23 Is there a reason this remained in draft?

yes, there is a blocking jira, I think we need a doc for customer about how to reenable minions and we need that in error message based on guideline of error messages. If this is enough, then we can merge this, but based on this error message, customer won't know, how to readd salt keys and restart minions

discussed with @sodre90, we will go with this error message for now
cc @pdarvasi @foldik


Fix some typos in docs/.

Fix some typos in docs/.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Invalid config for [sensor.resolvbus]: [ttyPort]

In HASS I'm seeing the following error when trying to validate the config.
Invalid config for [sensor.resolvbus]: [ttyPort] is an invalid option for [sensor.resolvbus]. Check: sensor.resolvbus->ttyPort.
I checked under HASS.io System and can see /dev/ttyUSB0 listed.
Any ideas?

This looks like an issue with your configuration file.
Can you add a note here with the corresponding section of your configuration file?
Could you please also confirm the version of Home Assistant you are using?

Hi
Sensors
sensor:
Weather prediction

platform: yr

platform: time_date
display_options:

'time'

platform: mqtt
name: Hot_Water
state_topic: "hot_water/tele/SENSOR"
value_template: "{{ value_json['DS18B20']['Temperature'] }}"
unit_of_measurement: "°C"

platform: resolvbus
name: MyResol
ttyPort: /dev/ttyUSB0
filterSource: 0x7321
filterDestination: 0x0010
filterCommand: 0x0100
attributes:

name: temperature_sensor_1
offset: 0
size: 2
factor: 0.1
type: temperature
name: system_time
offset: 18
size: 2
type: time
name: pump_speed_relay_1
offset: 10
size: 1

Using HASS 0.91

Can you try with the latest from the dev branch, and confirm it's ok?

No still the same issue with dev branch.

Does your file "custom_components/resolvbus/sensor.py" contain the updated PLATFORMSCHEMA from 4eeed61 ?
The dev branch definitely works for me on HASS 0.97.2

It didn't but it does now. Config validated and saved.
Now to figure out how to get a list of sensors/pumps etc. from the Resol device to buld the HASS config.
I used the examples you provided but I just get Temperature 1 None C and Pump 1 None%.


Make better use EAV structure

RDF gives us the ability to leave many values NULL for each object in the database. Currently we don't make good use of this facility, inputting a sort of NULL (called graph variables in the source code). Correcting this should be done in concert with improving the query functionality.
Acheiving this would drastically reduce the update time from the reduction in triples inserted.

This ticket was opened for alpha0.5 and that branch has since been modified to no-longer insert "graph variables".


Apparently the global section is evaluated 5 times (why 5 times?). This is not very clean. Also what I actually do in my project involves some non-trivial computation in global section so evaluation it multiple times slows things down quite a bit, too.

Also I see it's evaluated at the beginning of the 2nd step. eg, my script looks like:
[global]
...
print('{} genes to analyze for {}'.format(len(genes), tissue))

[default_1]
...
[default_2]

When I run with -J 40 I get:
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
1 genes to analyze for Thyroid
INFO: Executing default_1: utils
INFO: input:    []
INFO: output:   ['/home/gaow/Documents/GTExV8/.utils.R']
1 genes to analyze for Thyroid
INFO: Executing default_2:
INFO: input:    []
INFO: db16a2022c77a52e9471ff5004136ce3 started

You see one line gets printed in between the 2 steps.

The global section is designed to contain "definitions" that will be used by each step, and is executed at the beginning of each step in the current implementation. Although it is possible to define a sos_dict that contains the global definitions (after executing global section once) and be used by each step, the dictionary might not be pickleable and thus cannot be passed to each worker.
So basically the global section should only contain definitions, not any computation.

I see. But what if I do need to compute some global level quantities, would it work if I just write them outside global section ( I seem to remember that it will not work for SoS Notebook without global) ?

Or I should use a separate step for it, and expose it to other steps via shared?

Yes. That would be the recommended method.


Sometimes the PR reviewer checklist action fails to run

Problem
Coming from this Slack conversation, sometimes the PR reviewer checklist action fails to run on PRs. Here is an example.
Why is this important
If the checklist check fails to run then a PR can be merged without the checklist having been completed which might result in bugs slipping through the review process.
Solution
Investigate why the action fails to run and fix it. cc @AndrewGable
Edit: It looks like what happened in the example PR is someone approved my PR and the checklist was not fully filled out so the PR could not be merged. Next I merged main into the PR which does not cause the stale review to be dismissed and so it shows as passing. The solution could be to change the trigger to also run on synchronize so that it checks every time a commit is pushed, as Andrew pointed out here.

This issue has not been updated in over 15 days.  eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@neil-marcellini, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.


fix: VC Verification API Doc

https://input-output.atlassian.net/browse/ATL-7158

2 checks's job are in queue for more than 15 hours. cc @yshyn-iohk @milosbackonja @CryptoKnightIOG


symfony 3 support

Updated symfony libraries, so symfony 3.0 is supported

Well, kherge/amend requires symfony/console: ~2.1 so it will not update.
And also PHP version 5.5 is needed for symfony 3

I sent a PR https://github.com/box-project/amend/pull/11 But the repository is not updated for a long time.


[zype] Extract subtitles from the m3u8 manifest

Should fix #929

I had also made this patch, but just didn't get around to pushing it yet 😄


Fixes zero width or height image reading

Updated for a bug associated with mapnik-vector-tile. Initial commit points to a branch on mapnik-vector-tile, eventually will point to released version.
/cc @springmeyer for review.

Codecov Report

Merging #764 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #764   +/-   ##
=======================================
  Coverage   96.23%   96.23%
=======================================
  Files          42       42
  Lines        8810     8810
=======================================
  Hits         8478     8478
  Misses        332      332

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 c335992...c232757. Read the comment docs.

@flippmoke - I presume the next step here is to revisit this after the changes to mapnik core? https://github.com/mapnik/mapnik/pull/3672

@springmeyer yes, the changes here will be tweaked slightly once we have an official mapnik core release.

Waiting on binaries to be built for Mapnik core on windows and then hopefully we are good to merge this and start release process.


Make sure backoff is working fine

Will re-open if we got some problem with it.
Ref: https://github.com/litl/backoff/blob/master/tests/test_backoff.py


Add section on the user guide explaining how to construct, e.g., an Isometry3 from an Isometry2.

Cf. the feedback on reddit.

This issue has been moved to the nalgebra.org repository: https://github.com/sebcrozet/nalgebra.org/issues/8


Add tests

We'd like to have tests on this repository 🧪
As much as possible we'd like to use:

tape or node-tap (node-tap is my new goto)
have two scripts

one for running all tests once
one for running tests in watch mode

execute the first script in the CI on node 18.x and the LTS.
coverage is a plus

I'm on it

Hey @PierreDemailly 👋
Thanks for this amazing work. 👏
How goes this issue? Do you need any support?

Hi @tony-go
network.js  is the last file to test.
I remember tried to test it but it thrown due to missing browser API and/or others things, I will look again and give more details

@PierreDemailly awesome ^^
Do you think that you could add a list of stuff you did and what is missing?
Thanks again for this amazing job 👏

Hi @tony-go 👋
So I've tried again to test NodeSecureNetwork but i'm stuck.
There was a problem with ESM:

I've tried multiple things to make it works, the only thing that seem to works is:

I wonder if it is an "anti-pattern" without deep-import / tree-shaking, not sure..
Then Network is made for browser and use multiple API we don't have in Node (that make crash the process):
I've 'mock' it (adding JSDOM needed APIs to global), it seem to be a bad practice -> WDYT ?
import crypto from "node:crypto";
import { JSDOM } from "jsdom";

const { window } = (new JSDOM(`

`));
const { document } = window;

global.window = window;
global.navigator = window.navigator;
global.document = document;
global.crypto = crypto;
global.Element = window.Element;
global.HTMLCanvasElement = window.HTMLCanvasElement;

I've also needed to add canvas to the dev deps: https://github.com/jsdom/jsdom/issues/3042#issuecomment-734031683
I've made my first test: OK.
tap.test("it should throw when providing unknown theme", (t) => {
    try {
        new NodeSecureNetwork(nsDataSet, { theme: "AZJ001" });
    }
    catch (e) {
        t.same(e, new Error("Unknown theme AZJ001. Theme value can be LIGHT or DARK"));
    }
    finally {
        t.end();
    }
});

So I've tried somethings like this:
t.equal(network.highlightEnabled, false, "highlight is disabled by default");
network.neighbourHighlight({ nodes: [0] });
t.equal(network.highlightEnabled, true, "highlight has been enabled");

(https://github.com/NodeSecure/vis-network/blob/main/src/network.js#L173)
But if I call any method from the NodeSecureNetwork, always this error:

And now, I'm stuck.
I'm not sure how to handle Missing Browser API & events (Network.on(), Network.stabilize(),  Network.start/stopSimulation()...).
Maybe I should completely mock Network ?
I also would see e2e tests, WDYT ?

I saw that you already add a few test here: https://github.com/NodeSecure/vis-network/compare/main...PierreDemailly:vis-network:feat/add-tests-v1
Maybe you should raise a PR, and then we could merge it.
Also if some classes or functions are too broad maybe should we think about the e2e tests as you mentioned.


Edit OAuth Client without changing secret

Resolves #973

Seems fine. I find having to copy the secret from the flashed message a little annoying (rather than a separate form), but I don't think it'll be used often.


scope issues in comprehensions

Example JSON
{
   "foods": [
      { "name": "carrot" },
      { "name": "banana" }
   ],
   "people": [
      { "name": "alice", "likes": "apples" },
      { "name": "bob", "likes": "banana" },
      { "name": "carrol", "likes": "carrot" },
      { "name": "dave", "likes": "donuts" }
   ]
}

What happens as of 99f6771
$ jello "foods = set(f.name for f in _.foods)
         [p.name for p in _.people if p.likes not in foods]"
jello:  Query Exception:  NameError
        name 'foods' is not defined
        query:  foods = set(f.name for f in _.foods)\n[p.name for p in _.people if p.likes not in foods]
        data:  {'foods': [{'name': 'carrot'}, {'name': 'banana'}], 'people': [{'name': 'alice', 'likes': 'apples'}, {'name': 'bob', 'likes': 'banana'}, {'name': 'carrol', 'likes': 'carrot'}, {'name':
            'dave', 'likes': 'donuts'}]}

$ jello "[p.name for p in _.people if p.likes not in (f.name for f in _.foods)]"
jello:  Query Exception:  NameError
        name '_' is not defined
        query:  [p.name for p in _.people if p.likes not in (f.name for f in _.foods)]
        data:  {'foods': [{'name': 'carrot'}, {'name': 'banana'}], 'people': [{'name': 'alice', 'likes': 'apples'}, {'name': 'bob', 'likes': 'banana'}, {'name': 'carrol', 'likes': 'carrot'}, {'name':
            'dave', 'likes': 'donuts'}]}

What I expected to happen
$ jello "foods = set(f.name for f in _.foods)
         [p.name for p in _.people if p.likes not in foods]"
[
  "alice",
  "dave"
]

$ jello "[p.name for p in _.people if p.likes not in (f.name for f in _.foods)]"
[
  "alice",
  "dave"
]

Suggested change
diff --git a/jello/lib.py b/jello/lib.py
index 60b442c..ed2f4cc 100644
--- a/jello/lib.py
+++ b/jello/lib.py
@@ -459,10 +459,12 @@ def pyquery(_θ_data, _θ_query):
     del _θ_query
     _θ_last = ast.Expression(_θ_block.body.pop().value)    # assumes last node is an expression

-    exec(compile(_θ_block, '<string>', mode='exec'))
+    _θ_scope = {'_': _}
+
+    exec(compile(_θ_block, '<string>', mode='exec'), _θ_scope)
     del _θ_block

-    _θ_output = eval(compile(_θ_last, '<string>', mode='eval'))
+    _θ_output = eval(compile(_θ_last, '<string>', mode='eval'), _θ_scope)
     del _θ_last

     # convert output back to normal dict

Hi there, thanks for reporting this!
Your solution seems to work and tests are passing, so it doesn't look like it breaks anything. Nice!
For my benefit, could you help explain what this fix does? I had not messed around with the exec and eval scopes as I'm not very familiar with their functionality and I don't want to break anything. Is this basically adding the _ object to the scope, or is it deleting everything from the scope except for _? How did this end up fixing the issue?
I feel like I have run into other oddities in the past and this might be the fix for those as well.

How did this end up fixing the issue?

I don't really know why the list comprehension behaves that way. But passing in the scope explicitly is almost always what you want.
I suspect the reason for the creative variable naming and del from scope was to avoid user input from accidentally affecting local variables.  But they still have access to globals.
$ echo 1 | jello "list(globals().keys())"
[
  "__name__",
  "__doc__",
  "__package__",
  "__loader__",
  "__spec__",
  "__file__",
  "__cached__",
  "__builtins__",
  "os",
  "sys",
  "ast",
  "json",
  "shutil",
  "TextWrapper",
  "DotMap",
  "highlight",
  "Style",
  "Name",
  "Number",
  "String",
  "Keyword",
  "JsonLexer",
  "JavascriptLexer",
  "Terminal256Formatter",
  "HtmlFormatter",
  "PYGMENTS_INSTALLED",
  "opts",
  "JelloTheme",
  "Schema",
  "Json",
  "load_json",
  "warning_message",
  "pyquery"
]

Maybe this is unlikely to cause breakage, but if you pass in the global scope explicitly it'll be used for both locals and globals when the user input that is evaluated, instead of using the current scope.  Then it might behave more in the way you want it and you shouldn't have to worry about inadvertent side-effects.
So that's what I would suggest. But sorry I can't explain in great detail why this fixes anything other than what is in the docs. (They do mention something about not having access to nested scopes but I don't really know if that's what's going on with the list comprehension.) With stuff like this, I look how it's done in the standard library, like in pdb or runpy. If I'm trying to write something that does a similar as those modules I'll look at how they work, like how they use eval and exec in this case, and look at what they do because I more or less don't really know what I'm doing and mainly try to copy smart people and hope things work.

oh one real quick bonus meme because you mentioned this

I feel like I have run into other oddities in the past and this might be the fix for those as well.

so I noticed you remove the last statement from the block and eval it separately in order to get the result of the expression. alternatively, if the last statement in the block is an expression you could leave it in and change it to an assignment statement so it stores to some variable '__final' or something and that will be written to the scope dictionary passed in to exec when the block is exectued
But I don't actually know if this is better or not. I couldn't find a situation where this actually improved anything so it maybe doesn't. Just an idea if the current approach doesn't work for some reason in the future or whatever.

Nice - thanks! Yes, that was a struggle to find out how to do get that to work similar to a REPL. I'll definitely consider the option you describe.
Yes, I was using the strange variable names and del to keep from polluting the scope too much, but also wanted some convenience modules pre-imported like os.environ. I'll dig into this a bit more. Thanks again!

fixed in v1.5.3 available on Pypi. Binaries coming soon.


ActionBar | Ensure component follows best practises regarding dom

Compare dom for the component named Accordion in Radix ui and the ActionBar and try making our ActionBar-dom look more like Radix.

Was fixed in #752


Why force ReactScreen to Show at 50% of viewport ?

https://github.com/gao-sun/react-screen/blob/d5e2db4d1b4cc65b3800dc564651bfce2625d4b0/src/jsx/react-screen.jsx#L89
Hi,
ReactScreen shows up at 50% into the viewport, presumably because of mentionned line.
Would you consider making it configurable ?
Adding style margin-top:90vhon Screen wrapper and margin-bottom:-90vh on previous block
could allow Screen to showup at 10% of the viewport, preventing massive 50% empty space.
Cheers

Hi Gruck! As this project was built 3 years ago, I could hardly remember the purpose of setting the screenStartTop to 50% vh. Would you mind to make a pull request to make this configurable, if it will resolve your question? Thanks!


Elaborate on secure backup strategy?

Is it worth elaborating slightly on secure backup strategies and recommend some ways of performing zero-knowledge off-site backups where only you have access to the encryption key used?
https://www.arqbackup.com/
https://spideroak.com/

I haven't used either of those products; my encryption strategy is just to use gpg. I'll happily outline the steps I use, and/or feel free to PR your methodology. Thanks!

These backup solutions, is any of them open source? If not, I'm not sure how they can be trusted. They can talk all they want about how the data is encrypted client-side and without their knowledge, but unless the source is available noone can ever verify that easily.
Check out https://restic.github.io/ for a good looking alternative.
Regards, Leo
19 okt 2015 kl. 15:40 skrev Dominic Evans<EMAIL_ADDRESS>
Is it worth elaborating slightly on secure backup strategies and recommend some ways of performing zero-knowledge off-site backups where only you have access to the encryption key used?
https://www.arqbackup.com/
https://spideroak.com/
—
Reply to this email directly or view it on GitHub.


Extract code snippets from how-to-create-a-presentation-document-by-providing-a-file-name.md

Extract the code snippets from docs/presentation/how-to-create-a-presentation-document-by-providing-a-file-name.md and use docfx snippets to retrieve them from the samples folder and audit the text.

closing as duplicate


symbolic link identification

as it is now you can't differentiate a file/directory from a symbolic link to a
file/directory, thats because the use of stat(2) which will follow the symbolic link,
maybe add an extra flag to the mode, something like MODE_LINK and use lstat(2)
to set that, which later can be used to draw an arrow or something similar at the
bottom right corner of the icon if it is a symlink, you know better the source so I'm
sure that you can think of a better way to do it :D

A "dl" on the FILE_ICONS environment variable now matches a link to a directory.
I've also added a new .xpm icon for link to directory:

A "dl" on the FILE_ICONS environment variable now matches a link to a directory.
I've also added a new .xpm icon for link to directory (it need to be configured manually, tho):

Nice work!!!!!!!!! Thanks!


Use array of chars instead of StringBuilder for Company#domainName

Codecov Report

Merging #978 (ec31786) into main (d7ade4f) will decrease coverage by 0.17%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff              @@
##               main     #978      +/-   ##
============================================
- Coverage     92.39%   92.23%   -0.17%
+ Complexity     2761     2757       -4
============================================
  Files           289      289
  Lines          5522     5522
  Branches        601      601
============================================
- Hits           5102     5093       -9
- Misses          268      274       +6
- Partials        152      155       +3

Files
Coverage Δ

...ain/java/net/datafaker/providers/base/Company.java
97.61% <100.00%> (ø)

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Doc fixes

Update to github markdown and clean up a bunch of the grammar. Also fix #267 path to the data dir.

I committed most of this to the wiki directly.


Update gradle versions. Update Google Play Services library version.

Update gradle versions.
Update Google Play Services library version.

I SIGNED IT!

This pull request is already outdated. Before merging it we should update it to:
play-services-maps:8.3.0
and the build tools to:
buildToolsVersion "23.0.2"

Ummm... then what happens in another 2