srg-mmwave-australia

Type of issue
Other (describe below)
Feedback
.TH LIMINE 1 "version @PACKAGE_VERSION@" "@REGEN_DATE@"
.SH NAME
limine - Multiplexer to several Limine-related utilities.
.SH SYNOPSIS
.B limine
.RI " <args...>"
.SH DESCRIPTION
\fBlimine\fR provides a series of Limine-related utilities condensed in a single executable.
.SH BUGS
Please report bugs via
.IR @PACKAGE_BUGREPORT@ .
.SH HOMEPAGE
.I @PACKAGE_URL@
body {
font-family: 'Roboto',Arial,sans-serif;
font-weight: 400;
text-align: left;
font-size: 1rem;
line-height: 1.5;
color: #212529;
}
:root {
--wp--preset--aspect-ratio--square: 1;
--wp--preset--aspect-ratio--4-3: 4/3;
--wp--preset--aspect-ratio--3-4: 3/4;
--wp--preset--aspect-ratio--3-2: 3/2;
--wp--preset--aspect-ratio--2-3: 2/3;
--wp--preset--aspect-ratio--16-9: 16/9;
--wp--preset--aspect-ratio--9-16: 9/16;
--wp--preset--color--black: #000000;
--wp--preset--color--cyan-bluish-gray: #abb8c3;
--wp--preset--color--white: #ffffff;
--wp--preset--color--pale-pink: #f78da7;
--wp--preset--color--vivid-red: #cf2e2e;
--wp--preset--color--luminous-vivid-orange: #ff6900;
--wp--preset--color--luminous-vivid-amber: #fcb900;
--wp--preset--color--light-green-cyan: #7bdcb5;
--wp--preset--color--vivid-green-cyan: #00d084;
--wp--preset--color--pale-cyan-blue: #8ed1fc;
--wp--preset--color--vivid-cyan-blue: #0693e3;
--wp--preset--color--vivid-purple: #9b51e0;
--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);
--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);
--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);
--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);
--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);
--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);
--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);
--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);
--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);
--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);
--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);
--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);
--wp--preset--font-size--small: 13px;
--wp--preset--font-size--medium: 20px;
--wp--preset--font-size--large: 36px;
--wp--preset--font-size--x-large: 42px;
--wp--preset--spacing--20: 0.44rem;
--wp--preset--spacing--30: 0.67rem;
--wp--preset--spacing--40: 1rem;
--wp--preset--spacing--50: 1.5rem;
--wp--preset--spacing--60: 2.25rem;
--wp--preset--spacing--70: 3.38rem;
--wp--preset--spacing--80: 5.06rem;
--wp--preset--shadow--natural: 6px 6px 9px rgba(0, 0, 0, 0.2);
--wp--preset--shadow--deep: 12px 12px 50px rgba(0, 0, 0, 0.4);
--wp--preset--shadow--sharp: 6px 6px 0px rgba(0, 0, 0, 0.2);
--wp--preset--shadow--outlined: 6px 6px 0px -3px rgba(255, 255, 255, 1), 6px 6px rgba(0, 0, 0, 1);
--wp--preset--shadow--crisp: 6px 6px 0px rgba(0, 0, 0, 1);
}
:root {
--wp--preset--font-size--normal: 16px;
--wp--preset--font-size--huge: 42px;
}
{jRuby2,JSON}
{
"sets": [
{
"contact"<EMAIL_ADDRESS>"primary": "https://sackrace.ai",
"serviceSites": [
"https://socket-to-me.vip"
],
"rationaleBySite": {
"https://socket-to-me.vip": "A headless server to augment application that has a primary serverless architecture."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://poalim.xyz",
"associatedSites": [
"https://poalim.site"
],
"rationaleBySite": {
"https://poalim.site": "one of 3rd party cookie solutions option"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://nacion.com",
"associatedSites": [
"https://lateja.cr",
"https://elfinancierocr.com"
],
"rationaleBySite": {
"https://lateja.cr": "Newspaper owned by Grupo Nación",
"https://elfinancierocr.com": "Newspaper owned by Grupo Nación"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://wp.pl",
"associatedSites": [
"https://o2.pl",
"https://pudelek.pl",
"https://money.pl",
"https://abczdrowie.pl",
"https://wpext.pl"
],
"rationaleBySite": {
"https://o2.pl": "News portal and email service",
"https://pudelek.pl": "Special Interest Website - celebrity news and gossip",
"https://money.pl": "Special Interest Website - news and information on the stock market, currencies, business and economics",
"https://abczdrowie.pl": "Special Interest Website - healthy living and medical health",
"https://wpext.pl": "Content delivery domain for sensitive content websites"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://cafemedia.com",
"associatedSites": [
"https://cardsayings.net",
"https://nourishingpursuits.com"
],
"rationaleBySite": {
"https://cardsayings.net": "Co-branded content site",
"https://nourishingpursuits.com": "Co-branded content site"
}
},
{
"primary": "https://bild.de",
"contact"<EMAIL_ADDRESS>"associatedSites": [
"https://welt.de",
"https://autobild.de",
"https://computerbild.de",
"https://wieistmeineip.de"
],
"serviceSites": [
"https://www.asadcdn.com"
],
"rationaleBySite": {
"https://welt.de": "News Website welt.de",
"https://autobild.de": "Special Interest Website Autobild",
"https://computerbild.de": "Special Interest Website Computerbild",
"https://wieistmeineip.de": "Internet speed Measurement Website of Computerbild",
"https://www.asadcdn.com": "CDN for Ad Files - Frequency Capping"
}
},
{
"primary": "https://gliadomain.com",
"contact"<EMAIL_ADDRESS>"associatedSites": [
"https://salemoveadvisor.com",
"https://salemovefinancial.com",
"https://salemovetravel.com"
],
"rationaleBySite": {
"https://salemoveadvisor.com": "The domains are very clear that they are all a part of the SaleMove family of sites. These sites are used as demo sites to show how multiple sites can be linked together for the purpose of live chat linking across multiple domains. A user would expect the sites to be linked as they are all a part of the same demo family of sites to show how it works",
"https://salemovefinancial.com": "The domains are very clear that they are all a part of the SaleMove family of sites. These sites are used as demo sites to show how multiple sites can be linked together for the purpose of live chat linking across multiple domains. A user would expect the sites to be linked as they are all a part of the same demo family of sites to show how it works",
"https://salemovetravel.com": "The domains are very clear that they are all a part of the SaleMove family of sites. These sites are used as demo sites to show how multiple sites can be linked together for the purpose of live chat linking across multiple domains. A user would expect the sites to be linked as they are all a part of the same demo family of sites to show how it works"
}
},
{
"primary": "https://hapara.com",
"contact"<EMAIL_ADDRESS>"associatedSites": [
"https://teacherdashboard.com",
"https://mystudentdashboard.com"
],
"rationaleBySite": {
"https://teacherdashboard.com": "Portal for Hapara teachers",
"https://mystudentdashboard.com": "Portal for Hapara students"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://songstats.com",
"associatedSites": [
"https://songshare.com"
],
"rationaleBySite": {
"https://songshare.com": "Specialized Platform for Music Smart Links"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://hindustantimes.com",
"associatedSites": [
"https://livemint.com",
"https://livehindustan.com",
"https://healthshots.com",
"https://ottplay.com",
"https://desimartini.com"
],
"rationaleBySite": {
"https://livemint.com": "https://livemint.com",
"https://livehindustan.com":  "https://livehindustan.com",
"https://healthshots.com" : "https://healthshots.com",
"https://ottplay.com" : "https://ottplay.com",
"https://desimartini.com" : "https://desimartini.com"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://landyrev.com",
"associatedSites": [
"https://landyrev.ru"
],
"rationaleBySite": {
"https://landyrev.ru": "Same publisher's website in a different region"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://jagran.com",
"associatedSites": [
"https://gujaratijagran.com",
"https://punjabijagran.com"
],
"rationaleBySite": {
"https://gujaratijagran.com": "News Website for Gujarati audience",
"https://punjabijagran.com": "News Website for Punjabi audience"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://mercadolibre.com",
"associatedSites": [
"https://mercadolivre.com",
"https://mercadopago.com",
"https://mercadoshops.com",
"https://portalinmobiliario.com",
"https://tucarro.com"
],
"rationaleBySite": {
"https://mercadolivre.com": "Mercado Libre in Brazil",
"https://mercadopago.com": "Mercado Libre's payments ecosystem",
"https://mercadoshops.com": "Mercado Libre's online ecommerce store builder",
"https://portalinmobiliario.com": "Mercado Libre's brand for real estate ecommerce in Chile",
"https://tucarro.com": "Mercado Libre's brand for motors ecommerce in Colombia and Venezuela"
},
"ccTLDs": {
"https://mercadolibre.com": [
"https://mercadolibre.com.ar",
"https://mercadolibre.com.mx",
"https://mercadolibre.com.bo",
"https://mercadolibre.cl",
"https://mercadolibre.com.co",
"https://mercadolibre.co.cr",
"https://mercadolibre.com.do",
"https://mercadolibre.com.ec",
"https://mercadolibre.com.gt",
"https://mercadolibre.com.hn",
"https://mercadolibre.com.ni",
"https://mercadolibre.com.pa",
"https://mercadolibre.com.py",
"https://mercadolibre.com.pe",
"https://mercadolibre.com.sv",
"https://mercadolibre.com.uy",
"https://mercadolibre.com.ve"
],
"https://mercadolivre.com": [
"https://mercadolivre.com.br"
],
"https://mercadopago.com": [
"https://mercadopago.com.ar",
"https://mercadopago.com.br",
"https://mercadopago.com.mx",
"https://mercadopago.com.uy",
"https://mercadopago.com.co",
"https://mercadopago.cl",
"https://mercadopago.com.pe",
"https://mercadopago.com.ec",
"https://mercadopago.com.ve"
],
"https://mercadoshops.com": [
"https://mercadoshops.com.ar",
"https://mercadoshops.com.br",
"https://mercadoshops.com.mx",
"https://mercadoshops.cl",
"https://mercadoshops.com.co"
],
"https://tucarro.com": [
"https://tucarro.com.co",
"https://tucarro.com.ve"
]
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://joyreactor.cc",
"associatedSites": [
"https://reactor.cc",
"https://cookreactor.com"
],
"rationaleBySite": {
"https://reactor.cc": "Domain for fandomes, old version of site and mirror",
"https://cookreactor.com": "Cooking fandome"
},
"ccTLDs": {
"https://joyreactor.cc": [
"https://joyreactor.com"
]
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://unotv.com",
"associatedSites": [
"https://clarosports.com"
],
"serviceSites": [
"https://cmxd.com.mx"
],
"rationaleBySite": {
"https://clarosports.com": "Member of AMX Contenido websites, as unotv",
"https://cmxd.com.mx": "Used for personalization purposes across AMX Contenido websites."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://idbs-cloud.com",
"associatedSites": [
"https://idbs-dev.com",
"https://idbs-staging.com",
"https://idbs-eworkbook.com",
"https://eworkbookcloud.com",
"https://eworkbookrequest.com"
],
"rationaleBySite": {
"https://idbs-dev.com": "Dev version of main application IDBS-cloud",
"https://idbs-staging.com": "Staging version of main application IDBS-cloud",
"https://idbs-eworkbook.com": "E-workbook services part of IDBS-cloud product",
"https://eworkbookcloud.com": "E-workbook services part of IDBS-cloud product",
"https://eworkbookrequest.com": "E-workbook request part of IDBS-cloud product"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://mightytext.net",
"serviceSites": [
"https://textyserver.appspot.com",
"https://mighty-app.appspot.com"
],
"rationaleBySite": {
"https://textyserver.appspot.com": "API service for mightytext.net",
"https://mighty-app.appspot.com": "alternative domain for API service for mightytext.net"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://vwo.com",
"associatedSites": [
"https://wingify.com"
],
"rationaleBySite": {
"https://wingify.com": "Alias"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://wildix.com",
"associatedSites": [
"https://wildixin.com"
],
"rationaleBySite": {
"https://wildixin.com": "Wildix PBX's domain"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://timesinternet.in",
"associatedSites": [
"https://indiatimes.com",
"https://timesofindia.com",
"https://economictimes.com",
"https://samayam.com",
"https://cricbuzz.com"
],
"serviceSites": [
"https://growthrx.in",
"https://clmbtech.com",
"https://tvid.in"
],
"rationaleBySite": {
"https://indiatimes.com": "Indiatimes.com is primary domain for Times Internet which publish stories on Indian Lifestyle, Culture, Relationships, Food, Travel, Entertainment, News and New Technology News. The connection to Times Internet Limited is reflected in the About Us Section and the footer of the website.",
"https://timesofindia.com": "Times of India (TOI) is Indias largest and most influential news publisher in English. Its digital platform timesofindia.com is powered by Times Internet Limited, aptly represented in the About Us section and footer of the website.",
"https://economictimes.com": "Economic Times is India's top business news platform, providing comprehensive coverage of the economy, stock markets, and personal finance to inspire and empower business leaders and entrepreneurs. This digital platform is powered by Times Internet Limited as is clear from the About Us section of the website.",
"https://samayam.com": "Samayam is a Regional News publisher powered by Times Internet Limited. Its relationship to Times Internet is reflected in the footer of the website.",
"https://cricbuzz.com": "Cricbuzz is an Indian cricket news & live score platform owned by Times Internet Limited which is aptly reflected in the footer on the website.",
"https://growthrx.in": "GrowthRx is a customer engagement platform powered by Times Internet",
"https://clmbtech.com": "This is a times-internet data and customer management platform for managing publisher data.",
"https://tvid.in": "TVID is an in-house video management platform powered by Times Internet"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://hc1.com",
"associatedSites": ["https://hc1.global"],
"serviceSites": ["https://hc1cas.com", "https://hc1cas.global"],
"rationaleBySite": {
"https://hc1.global": "hc1 Insights Lab platform for UK.",
"https://hc1cas.com": "hc1 Insights Lab platform authentication service for US.",
"https://hc1cas.global": "hc1 Insight Lab platform authentication service for UK."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://kompas.com",
"associatedSites": [
"https://tribunnews.com",
"https://grid.id",
"https://bolasport.com",
"https://kompasiana.com",
"https://kompas.tv"
],
"rationaleBySite": {
"https://tribunnews.com": "Indonesian local news by KG Media",
"https://grid.id": "Indonesian entertainment & lifestyle news by KG Media ",
"https://bolasport.com": "Indonesian sport news by KG Media ",
"https://kompasiana.com": "Indonesian largest blog community by KG Media ",
"https://kompas.tv": "Indonesian national news by KG Media "
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://journaldesfemmes.com",
"associatedSites": [
"https://commentcamarche.net",
"https://linternaute.com",
"https://journaldunet.com",
"https://phonandroid.com",
"https://commentcamarche.com"
],
"rationaleBySite": {
"https://commentcamarche.net": "Centralized account for redactors, forums & real-time messages",
"https://linternaute.com": "Centralized account for redactors, forums & real-time messages",
"https://journaldunet.com": "Centralized account for redactors, forums & real-time messages",
"https://phonandroid.com": "Centralized account for redactors, forums & real-time messages",
"https://commentcamarche.com": "Centralized account for redactors, forums & real-time messages"
},
"ccTLDs": {
"https://journaldesfemmes.com": [
"https://journaldesfemmes.fr"
],
"https://linternaute.com": [
"https://linternaute.fr"
],
"https://journaldunet.com": [
"https://journaldunet.fr"
]
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://johndeere.com",
  "associatedSites": ["https://deere.com"],

  "rationaleBySite": {
     "https://deere.com": "Both johndeere.com and deere.com share branding, logos, and terms and conditions. They are used interchangeably. The names themselves are associated to Deere & Company in the marketplace."
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://lanacion.com.ar",
  "associatedSites": [
    "https://bonvivir.com"
  ],
  "rationaleBySite": {
    "https://bonvivir.com": "Wine club for sell wine by La Nación"
  }
},
{
	"contact"<EMAIL_ADDRESS>
	"primary": "https://nien.com",
	"associatedSites": [
		"https://chennien.com",
		"https://nien.org",
		"https://nien.co"
	],
	"rationaleBySite": {
		"https://chennien.com": "Alias domain for Nien Studio",
		"https://nien.org": "Campaign pages for Nien Studio",
		"https://nien.co": "URL shortener for Nien Studio"
	}
},
{
	"contact"<EMAIL_ADDRESS>
	"primary": "https://hearty.me",
	"associatedSites": [
		"https://hearty.app",
		"https://hearty.gift",
		"https://hj.rs",
		"https://heartymail.com",
		"https://alice.tw",
		"https://jiayi.life",
		"https://miss.com.tw"
	],
	"rationaleBySite": {
		"https://hearty.app": "API endpoints for Hearty Journal",
		"https://hearty.gift": "Campaign pages for Hearty Journal",
		"https://hj.rs": "URL shortener for Hearty Journal",
		"https://heartymail.com": "Email service for Hearty Journal",
		"https://alice.tw": "Alice's blog",
		"https://jiayi.life": "Jiayi's blog",
		"https://miss.com.tw": "Company website"
	}
},
{
  "primary": "https://talkdeskqaid.com",
  "contact"<EMAIL_ADDRESS>  "associatedSites": ["https://trytalkdesk.com"],
  "rationaleBySite": {
    "https://trytalkdesk.com": "Specialized platform for CCaS"
  }
},
{
  "primary": "https://talkdeskstgid.com",
  "contact"<EMAIL_ADDRESS>  "associatedSites": ["https://gettalkdesk.com"],
  "rationaleBySite": {
    "https://gettalkdesk.com": "Specialized platform for CCaS"
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://onet.pl",
  "associatedSites": [
    "https://fakt.pl",
    "https://businessinsider.com.pl",
    "https://medonet.pl",
    "https://plejada.pl"
  ],
  "serviceSites": [
    "https://ocdn.eu"
  ],
  "rationaleBySite": {
    "https://fakt.pl": "Special interest news website that is part of the Ringier Axel Springer Polska media group. It provides up-to-date news and covers a wide range of topics including politics, sports, entertainment, and lifestyle. Fakt.pl aims to deliver reliable and engaging content to its readers, keeping them informed about the latest events and trends.",
    "https://businessinsider.com.pl": "Special interest news website within the Ringier Axel Springer Polska media group. It focuses on business, finance, technology, and related topics. The website provides in-depth analysis, market insights, and news articles tailored for professionals, entrepreneurs, and those interested in the business world.",
    "https://medonet.pl": "Special interest news website within the Ringier Axel Springer Polska media group dedicated to health and medical topics. It offers a wide range of articles, news, and features related to various aspects of health, wellness, medical research, treatments, and lifestyle. Medonet.pl aims to provide reliable and accurate information to its readers, promoting healthy living and informed decision-making.",
    "https://ocdn.eu": "Service dedicated to processing events that occur on websites, assists in managing and optimizing multimedia content, including images, videos, or other resources, for websites that rely on event-related functionality.",
    "https://plejada.pl": "Special interest news website within the Ringier Axel Springer Polska media group dedicated to exclusive information, interviews, videos, and galleries from the world of show business."
  }
},
{
   "contact"<EMAIL_ADDRESS>   "primary": "https://elpais.com.uy",
   "associatedSites": [
      "https://clubelpais.com.uy",
      "https://paula.com.uy",
      "https://gallito.com.uy"
   ],
   "rationaleBySite": {
      "https://clubelpais.com.uy": "Domain from El Pais Uruguay",
      "https://paula.com.uy": "Domain from El Pais Uruguay",
      "https://gallito.com.uy": "Domain from El Pais Uruguay"
   },
   "ccTLDs": {
      "https://elpais.com.uy": [
         "https://elpais.uy"
      ]
   }
},
{
  "primary": "https://libero.it",
  "contact"<EMAIL_ADDRESS>  "associatedSites": [
    "https://supereva.it"
  ],
  "serviceSites": [
    "https://iolam.it"
  ],
  "rationaleBySite": {
    "https://libero.it": "Web portal",
    "https://supereva.it": "Gossip web site",
    "https://iolam.it": "Used for personalization purposes"
  }
},
{
  "primary":"https://rws1nvtvt.com",
  "contact"<EMAIL_ADDRESS>  "associatedSites": ["https://rws2nvtvt.com", "https://rws3nvtvt.com"],
  "rationaleBySite": {
      "https://rws2nvtvt.com": "Test 1",
      "https://rws3nvtvt.com": "Test 2"
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://stripe.com",
  "serviceSites": [
      "https://stripecdn.com",
      "https://stripe.network"
  ],
  "rationaleBySite": {
      "https://stripecdn.com": "Serves static assets accelerating page loads and sandboxes select Javascript",
      "https://stripe.network": "Receives telemetry preventing fraud across Stripe services"
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://repid.org",
  "associatedSites": [
    "https://reshim.org",
    "https://human-talk.org"
  ],
  "rationaleBySite": {
    "https://reshim.org": "Silent login",
    "https://human-talk.org": "Silent login"
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://ya.ru",
  "associatedSites": ["https://yandex.ru", "https://yandex.net", "https://turbopages.org", "https://auto.ru", "https://kinopoisk.ru", "https://clck.ru", "https://edadeal.ru", "https://webvisor.com", "https://yastatic.net"],
  "rationaleBySite": {
    "https://yandex.ru": "Yandex owned website",
    "https://yandex.net": "Yandex owned website",
    "https://yastatic.net": "Yandex owned website",
    "https://auto.ru": "Yandex owned website",
    "https://kinopoisk.ru": "Yandex owned website",
    "https://clck.ru": "Yandex owned website",
    "https://webvisor.com": "Yandex owned website",
    "https://turbopages.org": "Yandex owned website",
    "https://edadeal.ru": "Yandex owned website"
  },
  "ccTLDs": {
    "https://ya.ru": ["https://ya.cc"],
    "https://yandex.ru": ["https://yandex.az", "https://yandex.by", "https://yandex.kz", "https://yandex.md", "https://yandex.tj", "https://yandex.tm", "https://yandex.uz", "https://yandex.st", "https://yandex.com", "https://yandex.com.am", "https://yandex.com.ru"]
  }
},
{
  "primary": "https://victorymedium.com",
  "contact"<EMAIL_ADDRESS>  "associatedSites": [
    "https://standardsandpraiserepurpose.com"
  ],
  "serviceSites": [
    "https://technology-revealed.com"
  ],
  "rationaleBySite": {
    "https://standardsandpraiserepurpose.com": "Publisher #1 for RWS Test",
    "https://technology-revealed.com": "Frequency Capping Domain #1 for RWS Test"
  }
},
{
	"contact"<EMAIL_ADDRESS>
	"primary": "https://startupislandtaiwan.com",
	"associatedSites": [
		"https://startupislandtaiwan.net",
		"https://startupislandtaiwan.org"
	],
	"rationaleBySite": {
		"https://startupislandtaiwan.net": "Domain alias",
		"https://startupislandtaiwan.org": "Domain alias"
	}
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://carcostadvisor.com",
  "associatedSites": [],
  "serviceSites": [],
  "rationaleBySite": {},
  "ccTLDs": {
    "https://carcostadvisor.com": [
      "https://carcostadvisor.be",
      "https://carcostadvisor.fr"
    ]
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://caracoltv.com",
  "associatedSites": [
    "https://noticiascaracol.com",
    "https://bluradio.com",
    "https://shock.co",
    "https://bumbox.com",
    "https://hjck.com"
  ],
  "rationaleBySite": {
    "https://noticiascaracol.com": "Informative news show that covers the most important events in Colombia and around the world, owned by Valorem business group.",
    "https://bluradio.com": "Blu Radio is a Colombian radio network, owned by Valorem business group.",
    "https://shock.co": "It is a media outlet that publishes specialized content daily about music, movies, and television series. Owned by Valorem business group.",
    "https://bumbox.com": "Podcast platform from the media group of Caracol Televisión, El Espectador, and Blu Radio. Owned by Valorem business group.",
    "https://hjck.com": "It's a private Colombian radio station with a cultural programming. It belongs to the Valorem business group."
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://max.auto",
  "associatedSites": [
    "https://firstlook.biz"
  ],
  "rationaleBySite": {
    "https://firstlook.biz": "Presents core reports and SSO auth flow"
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://gridgames.app",
  "associatedSites": [
     "https://wordle.at"
  ],
  "rationaleBySite": {
     "https://wordle.at": "We are migrating our domain and will soon redirect all traffic from here to the primary, both of which we own. The two sites are almost identical. For convenience we want to transfer session cookies so users stay logged in."
  }
},
{
  "primary": "https://blackrock.com",
  "contact"<EMAIL_ADDRESS>  "associatedSites": [
    "https://blackrockadvisorelite.it",
    "https://cachematrix.com",
    "https://efront.com",
    "https://etfacademy.it",
    "https://ishares.com"
  ],
  "rationaleBySite": {
    "https://blackrockadvisorelite.it": "A site for Italian investment professionals. The branding is clearly visible on the site.",
    "https://cachematrix.com": "Cachematrix is a cash management firm acquired by BlackRock. The relationship is described on the About Us page.",
    "https://efront.com": "eFront is BlackRock's alternative solutions platform. The BlackRock branding is clearly visible on the site.",
    "https://etfacademy.it": "An Italian language education site about ETFs. The iShares by BlackRock branding is clearly visible on the site.",
    "https://ishares.com": "iShares is BlackRock's ETF brand. The branding is clearly visible on the site."
  }
},
{
  "contact"<EMAIL_ADDRESS>  "primary": "https://tvn.pl",
  "associatedSites": [
        "https://player.pl",
        "https://tvn24.pl",
        "https://zdrowietvn.pl"
  ],
  "rationaleBySite": {
      "https://player.pl":  "Streaming service that is owned by TVN S.A.. Information about the connection with TVN is included in the footer of this website",
      "https://zdrowietvn.pl": "Educational service that is owned by TVN S.A.. Information about the connection with TVN is included in the footer of this website",
      "https://tvn24.pl": "News service that is owned by TVN S.A.. Information about the connection with TVN is included in the footer of this website"
  }
},
{
  "primary": "https://zalo.me",
  "contact"<EMAIL_ADDRESS>  "associatedSites": [
    "https://zingmp3.vn",
    "https://baomoi.com",
    "https://smoney.vn"
  ],
  "rationaleBySite": {
    "https://zingmp3.vn": "Music Website owned by Zalo Group, VNG",
    "https://baomoi.com": "News Website owned by Zalo Group, VNG",
    "https://smoney.vn": "News Website owned by Zalo Group, VNG"
  }
},
{
  "primary": "https://finn.no",
  "contact"<EMAIL_ADDRESS>  "associatedSites": [
    "https://prisjakt.no",
    "https://mittanbud.no"
  ],
  "serviceSites": [
    "https://pdmp-apis.no"
  ],
  "rationaleBySite": {
    "https://prisjakt.no": "Site owned by Schibsted with shared SSO across Schibsted Norway's sites and common branding that clearly shows the relation between the sites.",
    "https://mittanbud.no": "Site owned by Schibsted with shared SSO across Schibsted Norway's sites and common branding that clearly shows the relation between the sites.",
    "https://pdmp-apis.no": "Site owned by Schibsted that provides APIs for users across Schibsted's sites."
  }
},

{
"contact"<EMAIL_ADDRESS>"primary": "https://laprensagrafica.com",
"associatedSites": [
"https://elgrafico.com",
"https://eleconomista.net",
"https://ella.sv",
"https://grupolpg.sv"
],
"rationaleBySite": {
"https://elgrafico.com": "News portal owned by La Prensa Grafica Group",
"https://eleconomista.net": "News portal owned by La Prensa Grafica Group",
"https://ella.sv": "News portal owned by La Prensa Grafica Group",
"https://grupolpg.sv": "Domain owned by La Prensa Grafica Group"
}
},
{
"primary": "https://kaksya.in",
"contact"<EMAIL_ADDRESS>"associatedSites": ["https://nidhiacademyonline.com"],
"serviceSites": [],
"rationaleBySite": {
"https://nidhiacademyonline.com": "This website is a subpart of kaksya.in and is used to host Nidhi Academy educational content videos/notes and more."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://vrt.be",
"associatedSites": [
"https://dewarmsteweek.be",
"https://sporza.be",
"https://een.be",
"https://radio2.be",
"https://radio1.be"
],
"rationaleBySite": {
"https://dewarmsteweek.be": "domain for a yearly campaign",
"https://sporza.be": "sub brand for sports news",
"https://een.be": "sub brand site",
"https://radio2.be": "sub brand site",
"https://radio1.be": "sub brand site"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://nvidia.com",
"associatedSites": [
"https://geforcenow.com"
],
"rationaleBySite": {
"https://geforcenow.com": "A site that represents the WEB client for NVIDIA GEFORCE NOW service. Players are able to instantly stream their PC game library. NVIDIA branding is clearly visible on this site."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://sapo.pt",
"associatedSites": [
"https://meo.pt"
],
"rationaleBySite": {
"https://meo.pt": "MEO is a prominent telecommunications and entertainment provider in Portugal, offering a wide range of services including television, internet, phone, and mobile."
},
"ccTLDs": {
"https://sapo.pt": [
"https://sapo.io"
]
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://tolteck.com",
"associatedSites": [
"https://tolteck.app"
],
"rationaleBySite": {
"https://tolteck.app": "Tolteck application"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://p24.hu",
"associatedSites": [
"https://24.hu",
"https://startlap.hu",
"https://nlc.hu",
"https://hazipatika.com",
"https://nosalty.hu"
],
"rationaleBySite": {
"https://24.hu": "Hungarian news portal",
"https://startlap.hu": "Hungarian news aggregator site and link collection",
"https://nlc.hu": "Hungarian women's online magazine",
"https://hazipatika.com": "Hungarian health portal",
"https://nosalty.hu": "Hungarian recipe portal"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://cognitiveai.ru",
"associatedSites": ["https://cognitive-ai.ru"],
"rationaleBySite": {
"https://cognitive-ai.ru": "This domain is our backend service that needs to share cookies with the main user-facing domain for authentication and session management."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://citybibleforum.org",
"associatedSites": ["https://thirdspace.org.au"],
"rationaleBySite": {
"https://thirdspace.org.au": "Similar content served in slightly different formats to different audiences"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://p106.net",
"associatedSites": [
"https://smpn106jkt.sch.id"
],
"rationaleBySite": {
"https://p106.net": "Indonesia Junior High School",
"https://smpn106jkt.sch.id": "Indonesia Junior High School"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://indiatoday.in",
"associatedSites": [
"https://aajtak.in",
"https://businesstoday.in",
"https://intoday.in",
"https://gnttv.com",
"https://indiatodayne.in"
],
"rationaleBySite": {
"https://intoday.in": "The one-stop destination for all of India Today Group's digital properties.",
"https://aajtak.in": "aajtak.in is the fastest, most reliable, and most popular website of news in Hindi. It provides readers with the news of India and worldwide along with every significant information related to everyday life with complete authenticity",
"https://businesstoday.in": "Top destination for business news, markets,  economy and more",
"https://indiatoday.in": "IndiaToday.in brings you news, analysis, explainers and opinion on a variety of subjects including politics, crime, civic issues, business, sports, technology, science, heatlh, lifestyle, and much more",
"https://gnttv.com": " Good News Today is a website that focuses on the bright side of life and showcases stories of triumphs and positivity.",
"https://indiatodayne.in": "India Today NE is dedicated to covering news and views of India’s north-eastern region which includes eight states—Assam, Arunachal Pradesh, Nagaland, Manipur, Mizoram, Tripura, Meghalaya and Sikkim"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://naukri.com",
"associatedSites": [
"https://ambitionbox.com",
"https://infoedgeindia.com"
],
"rationaleBySite": {
"https://ambitionbox.com": "Ambition box associated url",
"https://infoedgeindia.com": "InfoEdge India website"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://text.com",
"associatedSites": [
"https://livechat.com",
"https://helpdesk.com",
"https://chatbot.com",
"https://livechatinc.com",
"https://knowledgebase.com",
"https://openwidget.com"
],
"rationaleBySite": {
"https://livechat.com": "LiveChat - leading live chat software for business",
"https://helpdesk.com": "HelpDesk - leading help desk software for business",
"https://openwidget.com": "OpenWidget - free widgets for websites",
"https://chatbot.com": "ChatBot - leading automation software and chatbot platform",
"https://knowledgebase.com": "Knowledge base software for customer support and self-service",
"https://livechatinc.com": "Services supporting LiveChat"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://thejournal.ie",
"associatedSites": [
"https://the42.ie"
],
"rationaleBySite": {
"https://the42.ie": "Sports publication of TheJournal"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://html-load.com",
"associatedSites": [
"https://css-load.com",
"https://img-load.com",
"https://content-loader.com",
"https://07c225f3.online",
"https://html-load.cc"
],
"rationaleBySite": {
"https://css-load.com": "This domain is designated for the Pro version.",
"https://img-load.com": "This domain is designated for the Enterprise version.",
"https://content-loader.com": "This domain is designated for the Legacy version.",
"https://07c225f3.online": "This domain is designated for the Legacy version.",
"https://html-load.cc": "This domain is designated for the Essential version."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://interia.pl",
"associatedSites": [
"https://pomponik.pl",
"https://deccoria.pl",
"https://top.pl",
"https://smaker.pl",
"https://terazgotuje.pl"
],
"rationaleBySite": {
"https://pomponik.pl": "Special Interest Website - celebrity news and gossip",
"https://deccoria.pl": "Special Interest Website - advice and inspirations foron interior design and garden care",
"https://top.pl": "Special Interest Website - wide range of articles, news and tips ",
"https://smaker.pl": "Special Interest Website - recipes, cooking, diet and everything for home cooks",
"https://terazgotuje.pl": "Special Interest Website - cooking news, tips and recipes"
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://graziadaily.co.uk",
"associatedSites": [
"https://heatworld.com",
"https://closeronline.co.uk",
"https://yours.co.uk",
"https://motherandbaby.com",
"https://takeabreak.co.uk"
],
"rationaleBySite": {
"https://heatworld.com": "Our websites are uniformly owned and operated by Bauer Media, a fact clearly indicated by the consistent footer across all domains.",
"https://closeronline.co.uk": "Our websites are uniformly owned and operated by Bauer Media, a fact clearly indicated by the consistent footer across all domains.",
"https://yours.co.uk": "Our websites are uniformly owned and operated by Bauer Media, a fact clearly indicated by the consistent footer across all domains.",
"https://motherandbaby.com": "Our websites are uniformly owned and operated by Bauer Media, a fact clearly indicated by the consistent footer across all domains.",
"https://takeabreak.co.uk": "Our websites are uniformly owned and operated by Bauer Media, a fact clearly indicated by the consistent footer across all domains."
}
},
{
"contact"<EMAIL_ADDRESS>"primary": "https://drimer.io",
"associatedSites": [
"https://drimer.travel"
],
"rationaleBySite": {
"https://drimer.travel": "The travel portal for Drimer"
}
}
]
}
Page URL
https://learn.microsoft.com/en-us/windows/powertoys/administrator
Content source URL
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/powertoys/administrator.md
Author
@alvinashcraft
Document Id
5e66eda4-be07-4afd-7187-3e4d896f7861

It looks like there's no actionable feedback here, so I'll go ahead and close the issue. Please open a new issue if you have feedback about the documentation that you'd like us to address.


Inconsistent button labels in contact details removal alert box

Expected behavior
The buttons in the alert box should be labeled consistently and clearly indicate the action to be taken (e.g., "Cancel" and "Remove," "No" and "Yes").
Steps to reproduce the issue
Login the app with valid user credentials.
Open the user detail page of a user for which contact details are saved.
Attempt to remove the email, phone number, or external ID.
Observe the alert box that opens up asking for confirmation of the action.
Environment details
App version: v1.10.0
App environment: UAT
Additional information
https://jam.dev/c/90f4313d-af68-42cd-a197-e29ddfb9e1da

Verified and working fine in release v1.11.0. Hence, closing this issue.


Make Translation Tables Actual Classes

Currently, the translation tables e.g pokemon_names  monkey-patch the created tables to poked.db.multilang. This can cause a lot of problems. i.e. if someone were to pickle an instance, this will happen
_pickle.PicklingError: Can't pickle <class 'pokedex.db.multilang.type_names'>: attribute lookup type_names on pokedex.db.multilang failed

It would be more efficient if the tables for translations were built-in to the module that creates the schema.
An example would be:
pokemon_species = create_translation_table(
    'pokemon_species_names',
    PokemonSpecies, 'names',
    relation_lazy='joined',
    name = Column(
        Text,
        nullable=True,
        index=True,
        doc=u"The name",
        info=dict(format='plaintext', official=True, ripped=True)),
    genus = Column(
        Text,
        nullable=True,
        doc=u'The short flavor text, such as "Seed" or "Lizard"; usually affixed with the word "Pokémon"',
        info=dict(official=True, format='plaintext')),
)

What. Why are you trying to pickle a database object?

I'm making a text based rpg and I want to serialize an Pokemon that the player can use


Need newer version of contentful-management with bugfixes

I'm using contentful-importer for a project and also need contentful-management 0.7.0 installed because of some of the bugfixes available in that version.

Thank you.


tmp

Note

Why not current approach: https://github.com/OCA/odoo-module-migrator/pull/114

Not actually work, e.g multi-line string
Make quite lots of noise (also not explicit)

Why this?

Simple
Easy to maintain

This change

Since https://github.com/OCA/pylint-odoo/pull/423/commits/2db6690791efa93ce06f81be40c3339462015b50, some checkers for translation were added, by emitting translation-* instead of logging-

translation-format-interpolation
translation-format-truncated
translation-fstring-interpolation
translation-not-lazy
translation-too-few-args
translation-too-many-args
translation-unsupported-format
Result

can you simulate that change on a few big repos? web, server-tools, server-ux for example

to ponder if these should go into mandatory checks or optional

on the final OCA PR, only keep the description starting from This change
in issue https://github.com/OCA/oca-addons-repo-template/issues/270, add a comment with a link to the OCA PR, something like "started here:`

can you locally simulate that change on a few big repos? web, server-tools, server-ux for example
* to ponder if these should go into mandatory checks or optional

on the final OCA PR, only keep the description starting from This change

in issue https://github.com/OCA/oca-addons-repo-template/issues/270, add a comment with a link to the OCA PR, something like "started here:`

Hi anh, it hurts the server-tools really bad :))
But it's important to quality of the repos as you said
How about we go with 'mandatory' for now and wait for community's feedback?


Better visibility into task arguments

We have a particularly compute heavy task that tends to occupy most of our cluster. It takes just a couple strings as arguments and crunches for some number of hours. It'd be nice if the web UI could show us those arguments so we can quickly see what the cluster is doing and also quickly learn something about tasks that fail. I understand that this doesn't make sense for a lot of use cases (e.g. when passing around huge dataframes) but the ability to inspect simple scalar arguments seems like it would always be a win.
I'm pretty sure I checked the UI thoroughly for something like this but never found it -- please correct me if I'm wrong.

You're correct that this isn't available today.  For security reasons the
scheduler actually doesn't unpack the Python tasks, so they're little black
boxes that are hard to visualize.
However, you might want to try a project like Prefect, which builds on top
of Dask to provide more information like this, and tends to include other
features that are commonly requested from people in your situation.
On Fri, Jul 10, 2020 at 7:23 PM John Emhoff<EMAIL_ADDRESS>wrote:

We have a particularly compute heavy task that tends to occupy most of our
cluster. It takes just a couple strings as arguments and crunches for some
number of hours. It'd be nice if the web UI could show us those arguments
so we can quickly see what the cluster is doing and also quickly learn
something about tasks that fail. I understand that this doesn't make sense
for a lot of use cases (e.g. when passing around huge dataframes) but the
ability to inspect simple scalar arguments seems like it would always be a
win.
I'm pretty sure I checked the UI thoroughly for something like this but
never found it -- please correct me if I'm wrong.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/6396, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTEJQ33KYCQWOWXL47TR27EKNANCNFSM4OXCTKAQ
.

https://www.prefect.io/
On Fri, Jul 10, 2020 at 8:01 PM Matthew Rocklin<EMAIL_ADDRESS>wrote:

You're correct that this isn't available today.  For security reasons the
scheduler actually doesn't unpack the Python tasks, so they're little black
boxes that are hard to visualize.
However, you might want to try a project like Prefect, which builds on top
of Dask to provide more information like this, and tends to include other
features that are commonly requested from people in your situation.
On Fri, Jul 10, 2020 at 7:23 PM John Emhoff<EMAIL_ADDRESS>wrote:

We have a particularly compute heavy task that tends to occupy most of
our cluster. It takes just a couple strings as arguments and crunches for
some number of hours. It'd be nice if the web UI could show us those
arguments so we can quickly see what the cluster is doing and also quickly
learn something about tasks that fail. I understand that this doesn't make
sense for a lot of use cases (e.g. when passing around huge dataframes) but
the ability to inspect simple scalar arguments seems like it would always
be a win.
I'm pretty sure I checked the UI thoroughly for something like this but
never found it -- please correct me if I'm wrong.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/6396, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTEJQ33KYCQWOWXL47TR27EKNANCNFSM4OXCTKAQ
.

Ah, we had stumbled upon prefect and it looked pretty promising but we didn't want to completely rearchitect our outer loop (adding dask in the middle was a big change already). It sounds like we should consider a more thorough retooling now that we're comfy with dask.


Fix minor typo and update name of script

The guide says the script in lf-west-template is called lf_build.py, but is is named lfc.py.
See here: https://github.com/lf-lang/lf-west-template/tree/main/scripts

Ok, I did it using VSCode find and replace so I'm confident I got them all :)


delete survey UI

currently there is no way to delete a survey using the GUI.
Be sure to include a confirmation dialog.

does it remove all associated submission data as well?

Especially if you want to have this delete submissions, we should have it backup the server automatically right before this delete is done #42

@danbjoseph could be an option in the confirm dialoge

Rather than actually removing data, let's make a deleted-submissions directory and move things in there. That way you can Undo.


security

Build 'demo' is failing!
Last 50 lines of build output:
[...truncated 57 lines...]
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] dir
Running in /var/jenkins_home/workspace/demo/app-devops-bootcamp/api-store
[Pipeline] {
[Pipeline] sh
+ npm audit
# npm audit report

webpack  5.0.0 - 5.75.0
Severity: high
Cross-realm object access in Webpack 5 - https://github.com/advisories/GHSA-hc6q-2mpp-qw7j
fix available via `npm audit fix`
node_modules/webpack
  @nestjs/cli  7.5.1-next.1 || 7.5.2-next.2 - 9.2.0
  Depends on vulnerable versions of webpack
  node_modules/@nestjs/cli

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
Stage "Build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
Stage "Deploy" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] sh
+ docker logout
Removing login credentials for https://index.docker.io/v1/
[Pipeline] deleteDir
[Pipeline] step

Changes since last successful build:
No changes
No changes
No changes
No changes
View full output

Build 'demo' is failing!
Last 50 lines of build output:
[...truncated 57 lines...]
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] dir
Running in /var/jenkins_home/workspace/demo/app-devops-bootcamp/api-store
[Pipeline] {
[Pipeline] sh
+ npm audit
# npm audit report

webpack  5.0.0 - 5.75.0
Severity: high
Cross-realm object access in Webpack 5 - https://github.com/advisories/GHSA-hc6q-2mpp-qw7j
fix available via `npm audit fix`
node_modules/webpack
  @nestjs/cli  7.5.1-next.1 || 7.5.2-next.2 - 9.2.0
  Depends on vulnerable versions of webpack
  node_modules/@nestjs/cli

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
Stage "Build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
Stage "Deploy" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] sh
+ docker logout
Removing login credentials for https://index.docker.io/v1/
[Pipeline] deleteDir
[Pipeline] step

Changes since last successful build:
No changes
No changes
No changes
No changes
No changes
No changes
View full output

Build 'demo' is failing!
Last 50 lines of build output:
[...truncated 57 lines...]
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] dir
Running in /var/jenkins_home/workspace/demo/app-devops-bootcamp/api-store
[Pipeline] {
[Pipeline] sh
+ npm audit
# npm audit report

webpack  5.0.0 - 5.75.0
Severity: high
Cross-realm object access in Webpack 5 - https://github.com/advisories/GHSA-hc6q-2mpp-qw7j
fix available via `npm audit fix`
node_modules/webpack
  @nestjs/cli  7.5.1-next.1 || 7.5.2-next.2 - 9.2.0
  Depends on vulnerable versions of webpack
  node_modules/@nestjs/cli

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
Stage "Build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
Stage "Deploy" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] sh
+ docker logout
Removing login credentials for https://index.docker.io/v1/
[Pipeline] deleteDir
[Pipeline] step

Changes since last successful build:
No changes
No changes
No changes
No changes
No changes
No changes
No changes
No changes
View full output


Thank you!

This is simple enough and yet so powerful. Thank you!!!

Thanks for the appreciation Carlos!


HIdden Markov Models

I didn't see any HMM implementations yet, any objection if I implement one and add it? It would probably be similar in api to https://github.com/hmmlearn/hmmlearn.

That would be a welcome addition, go for it.

I guess I could have a go at this.
Do you prefer MLE, MAP or Bayesian (mean-field) HMMs? hmmlearn implements MAP, but since we're talking about a from scratch implementation here, a proper Bayesian model might be more appropriate.

I'd welcome any implementation that you find useful and want to share.

Is anyone doing this? I would be interested in using it; Bayesian version the better option for me.

I am currently not working on this.

I should also mention that while I'd love for this to a feature of Oml, perhaps leveraging some of the capabilities of Libra might make an implementation easier if you're looking for a pure OCaml solution.


MalformedPolicyDocument: Policy statement must contain resources.

Description
I am running the tests/complete example that is provided in https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/tree/main/tests/complete . There are a few deprecated values like:
with module.eks.aws_eks_addon.this["coredns"],
│   on .terraform\modules\eks\main.tf line 392, in resource "aws_eks_addon" "this":
│  392:   resolve_conflicts        = try(each.value.resolve_conflicts, "OVERWRITE")
│
│ The "resolve_conflicts" attribute can't be set to "PRESERVE" on initial resource creation. Use "resolve_conflicts_on_create" and/or "resolve_conflicts_on_update" instead

The actual error that I get and I am scratching my head is :
│ Error: creating IAM Policy (aws-node-termination-handler-20230529162529323600000001): MalformedPolicyDocument: Policy statement must contain resources.
│       status code: 400, request id: 64dc2efe-47c7-4f2f-b51c-2b01a70392c1
│
│   with module.eks_blueprints_addons.module.aws_node_termination_handler.aws_iam_policy.this[0],
│   on .terraform\modules\eks_blueprints_addons.aws_node_termination_handler\main.tf line 237, in resource "aws_iam_policy" "this":
│  237: resource "aws_iam_policy" "this" {
│

Module version [0.1.0 (latest)]:

Terraform version:
">= 1.0"

Provider version(s):
aws  ">=2.17"
kubernetes ">=2.17"
helm ">= 2.8"

Steps to reproduce the behavior:
terraform init
terraform plan
terraform apply
Expected behaviour
Deploy architecture without errors
Actual behaviour
Get an error mentioned above

please provide a reproduction that demonstrates the error

please provide a reproduction that demonstrates the error

Thank

Sorry, I misclicked and closed the issue by mistake.
In regards to the reproduction - I've literally cloned the repo and then followed the steps you've mentioned in the README.md file here https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/tree/main/tests/complete .

are you saying the complete test case does not work as its written? I just validated this case at the end of last week and I did not encounter any of the errors you have reported here

are you saying the complete test case does not work as its written? I just validated this case at the end of last week and I did not encounter any of the errors you have reported here

Yes, I can confirm this does happen on the complete test case.
Just happened today again.
After cloning the repo, changing directory to tests/complete , terraform init, terraform plan, terraform apply I create most of the resources but still some of the addons don't work. They take about 20 minutes to create.
The ones that I can see are:
module.eks.aws_eks_addon.this["aws-guardduty-agent"]: Still creating... [18m1s elapsed]
module.eks.aws_eks_addon.this["aws-ebs-csi-driver"]: Still creating... [15m21s elapsed]
module.eks.aws_eks_addon.this["vpc-cni"]: Still creating... [15m11s elapsed]
At the end of the 20-ish minutes I get:
╷ │ Warning: Running terraform apply again will remove the kubernetes add-on and attempt to create it again effectively purging previous add-on configuration │ │   with module.eks.aws_eks_addon.this["aws-ebs-csi-driver"], │   on .terraform\modules\eks\main.tf line 382, in resource "aws_eks_addon" "this": │  382: resource "aws_eks_addon" "this" { │ │ (and 2 more similar warnings elsewhere) ╵ ╷ │ Warning: Argument is deprecated │ │   with module.eks.aws_eks_addon.this["aws-ebs-csi-driver"], │   on .terraform\modules\eks\main.tf line 392, in resource "aws_eks_addon" "this": │  392:   resolve_conflicts        = try(each.value.resolve_conflicts, "OVERWRITE") │ │ The "resolve_conflicts" attribute can't be set to "PRESERVE" on initial resource creation. Use "resolve_conflicts_on_create" and/or "resolve_conflicts_on_update" instead │ │ (and 5 more similar warnings elsewhere) ╵ ╷ │ Warning: Helm release "argo-cd" was created but has a failed status. Use the helmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.argocd.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.argocd\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-cloudwatch-metrics" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_cloudwatch_metrics.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_cloudwatch_metrics\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-efs-csi-driver" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_efs_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_efs_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-for-fluent-bit" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_for_fluentbit.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_for_fluentbit\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-fsx-csi-driver" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_fsx_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_fsx_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-load-balancer-controller" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_load_balancer_controller.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_load_balancer_controller\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "aws-privateca-issuer" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.aws_privateca_issuer.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_privateca_issuer\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "cert-manager" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.cert_manager.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.cert_manager\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "cluster-autoscaler" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.cluster_autoscaler.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.cluster_autoscaler\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "external-dns" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.external_dns.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.external_dns\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "external-secrets" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.external_secrets.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.external_secrets\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "gatekeeper" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.gatekeeper.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.gatekeeper\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "ingress-nginx" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.ingress_nginx.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.ingress_nginx\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "kube-prometheus-stack" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.kube_prometheus_stack.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.kube_prometheus_stack\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "metrics-server" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.metrics_server.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.metrics_server\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "secrets-store-csi-driver" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.secrets_store_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.secrets_store_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "velero" was created but has a failed status. Use thehelmcommand to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.velero.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.velero\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Warning: Helm release "vpa" was created but has a failed status. Use thehelm command to investigate the error, correct it, then run Terraform again. │ │   with module.eks_blueprints_addons.module.vpa.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.vpa\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: waiting for EKS Add-On (complete:aws-ebs-csi-driver) create: timeout while waiting for state to become 'ACTIVE' (last state: 'CREATING', timeout: 20m0s) │ │   with module.eks.aws_eks_addon.this["aws-ebs-csi-driver"], │   on .terraform\modules\eks\main.tf line 382, in resource "aws_eks_addon" "this": │  382: resource "aws_eks_addon" "this" { │ ╵ ╷ │ Error: waiting for EKS Add-On (complete:aws-guardduty-agent) create: timeout while waiting for state to become 'ACTIVE' (last state: 'CREATING', timeout: 20m0s) │ │   with module.eks.aws_eks_addon.this["aws-guardduty-agent"], │   on .terraform\modules\eks\main.tf line 382, in resource "aws_eks_addon" "this": │  382: resource "aws_eks_addon" "this" { │ ╵ ╷ │ Error: waiting for EKS Add-On (complete:vpc-cni) create: timeout while waiting for state to become 'ACTIVE' (last state: 'CREATING', timeout: 20m0s) │ │   with module.eks.aws_eks_addon.this["vpc-cni"], │   on .terraform\modules\eks\main.tf line 382, in resource "aws_eks_addon" "this": │  382: resource "aws_eks_addon" "this" { │ ╵ ╷ │ Error: client rate limiter Wait returned an error: context deadline exceeded │ │   with module.eks_blueprints_addons.module.argocd.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.argocd\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_cloudwatch_metrics.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_cloudwatch_metrics\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_efs_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_efs_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_for_fluentbit.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_for_fluentbit\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_fsx_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_fsx_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_load_balancer_controller.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_load_balancer_controller\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.aws_privateca_issuer.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.aws_privateca_issuer\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.cert_manager.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.cert_manager\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.cluster_autoscaler.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.cluster_autoscaler\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.external_dns.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.external_dns\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.external_secrets.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.external_secrets\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.gatekeeper.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.gatekeeper\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.ingress_nginx.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.ingress_nginx\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.kube_prometheus_stack.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.kube_prometheus_stack\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.metrics_server.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.metrics_server\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.secrets_store_csi_driver.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.secrets_store_csi_driver\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.velero.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.velero\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" { │ ╵ ╷ │ Error: failed pre-install: timed out waiting for the condition │ │   with module.eks_blueprints_addons.module.vpa.helm_release.this[0], │   on .terraform\modules\eks_blueprints_addons.vpa\main.tf line 9, in resource "helm_release" "this": │    9: resource "helm_release" "this" {

To be clear:

This is a warning based on the v5.0 of the AWS provider that Hashicorp released last week
│ The "resolve_conflicts" attribute can't be set to "PRESERVE" on initial resource creation. Use "resolve_conflicts_on_create" and/or "resolve_conflicts_on_update" instead

I am not seeing the error you provided in your original message in this output
``
│ Error: creating IAM Policy (aws-node-termination-handler-20230529162529323600000001): MalformedPolicyDocument: Policy statement must contain resources.
│       status code: 400, request id: 64dc2efe-47c7-4f2f-b51c-2b01a70392c1
│
│   with module.eks_blueprints_addons.module.aws_node_termination_handler.aws_iam_policy.this[0],
│   on .terraform\modules\eks_blueprints_addons.aws_node_termination_handler\main.tf line 237, in resource "aws_iam_policy" "this":
│  237: resource "aws_iam_policy" "this" {
│

I suspect what you are encountering is an issue with Gatekeeper but that is separate from the issue you posted

we have made some recent changes (you can see these in the v0.2.0 release notes) and I can confirm that the complete test case is working as intended. I'll close this for now but please feel free to provide additional details and a reproduction if you'd like us to look into your issue further

I am getting this error with
enable_aws_node_termination_handler = true
with latest eks_blueprints_addons version 1.12.0
╷
│ Error: creating IAM Policy (aws-node-termination-handler-20231203064834013500000007): MalformedPolicyDocument: Policy statement must contain resources.
│ 	status code: 400, request id: d1f13162-0b81-4c6e-a914-1dff5c978073
│
│   with module.eks_blueprints_addons.module.aws_node_termination_handler.aws_iam_policy.this[0],
│   on .terraform/modules/eks_blueprints_addons.aws_node_termination_handler/main.tf line 242, in resource "aws_iam_policy" "this":
│  242: resource "aws_iam_policy" "this" {


add canonical_book_list.json

The ordering came from sorting by uuid with vscode, I wasn't sure the order mattered since we shouldn't have any page overlap between canonical books?


Fixing native "redirect" calls incorrectly caching

Fixes a typo in the redirect API call that is caching tokens in browser storage in native calls
Adding an include needed for native code in 1P library

PS: Tested manually with WAM sample, @lalimasharda is working on a PR to merge the sample incrementally

Codecov Report

Merging #5338 (16f7aea) into dev (d8174f3) will not change coverage.
The diff coverage is 100.00%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.50% <ø> (ø)

msal-browser
86.47% <100.00%> (ø)

Carriedforward from d8174f3

msal-common
85.45% <ø> (ø)

Carriedforward from d8174f3

msal-core
82.84% <ø> (ø)

Carriedforward from d8174f3

msal-node
82.90% <ø> (ø)

Carriedforward from d8174f3

msal-node-extensions
76.03% <ø> (ø)

Carriedforward from d8174f3

msal-react
94.50% <ø> (ø)

node-token-validation
88.88% <ø> (ø)

Carriedforward from d8174f3

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

lib/msal-browser/src/index.ts
100.00% <ø> (ø)

...l-browser/src/interaction_client/RedirectClient.ts
98.67% <100.00%> (ø)

Abandoning this as a part of new PR #5706


Hanging on rule create_warps

This is happening only with very high resolution data (46x46x60um). I tried increasing the resources from 16gb to 96gb memory but still same problem (and in the system monitor it doesn't appear to use this all anyway). I can also see this is using a single core, but I've left it running for a whole week and never got an output.
I know the interpolation step can be somewhat memory-intensive, so perhaps this is the issue?

Looking more into this, it seems each call to scipy's interpolation.griddata generates a subprocess that doesn't clear after we evaluate it. In this case each takes ~40gb and a very long time to complete, likely exceeding the resources allocated by snakebids. I opened a branch to try and run and then clear these serially to save memory https://github.com/khanlab/hippunfold/tree/create_warps_resource_manage.
If this makes sense and work then I'll make a PR and we can do some further refining

Yes sounds like it needs more memory than available..
But is it getting past the first griddata call? If so, then maybe clearing things up might help, but I suspect it's the first griddata call that is causing it to hang..
I doubt there would be much you can do except use a large memory system (can check the griddata code to see what it needs to allocate), try to work with downsampled data for this step, or perform this interpolation on chunks of the image at a time..

Now that we identified the real problem (see https://github.com/khanlab/hippunfold/pull/94), closing this issue


Adding Tags

I added a tags attribute to Case and functionality in the form to choose tags and show statistics of them in the Metrics view

@melomys to be honest I don't remember exactly how it works, maybe those were just never used, I will test a bit after work today


CEP for specifying the location of site-packages in repodata

Description
This CEP proposed to introduce an optional python_site_packages_path field in repodata that python packages can use to explicitly specify the location of the site-packages directory. This allows for noarch: python packages to be linked into the correct location when this path does not match the on used by standard builds of CPython. This includes alternative implementation of the Python programming langauge (PyPy, GraalPy) and free-threading builds of CPython.
The motivation and request for this CEP came from conda/conda#14053, which discusses noarch: python support in conda in environments with the experimental free-threading configuration of CPython 3.13.

https://github.com/conda/ceps/pull/86/files is working in the same space, to allow ABI3 packages

I have put together a draft PR for conda-build that implements support for specifying this field in the build section of a recipe, see conda/conda-build#5502.
With this I created sample packages that specify this metadata field for testing with downstream tools. They are available on anaconda.org in the jjhelmus/label/sp_path channel.
There are three noarch packages with the following paths specified

python 3.99.99 : lib/python3.99t/site-packages - A "free-threading" like path
python 3.99.90 : sample_path/from_the_file/index_json - Something that stands out
python 3.99.50 : ../../../../../invalid_path : Should be rejected by tooling as being invalid

conda/conda#14256 contains an rough draft of the change needed for conda to make use of this field.

Should we fix the name for python in the shebang of entry-points in this CEP or a separate one? Currently there's a python3.13t->python3.13 symlink

Should we fix the name for python in the shebang of entry-points in this CEP or a separate one? Currently there's a python3.13t->python3.13 symlink

I'd suggest keeping it here TBH, since a whole CEP for a simple change like this may be overkill.

A bit of context about the python executable name.
On Unix, CPython (upstream and conda) has python3.13 for freethreading and default builds. For freethreading python3.13 is a symlink to python 3.13t. On Unix, PyPy does the same
On Windows, CPython upstream has python.exe for default build and python3.13t.exe for freethreading builds as there's only one installer. On conda-forge, python3.13.exe and python.exe is a copy of python3.13t.exe for freethreading builds.
On PyPy, they have python3.10.exe copy for python.exe
For noarch: packages, the entry-points right now uses python3.13 for unix and python.exe for windows. Do we want to keep using these or have a way for specifying the executable name? Note that it's straightforward to change the name in Unix as it's about changing the shebang, but it's hard on windows due to the need to create an executable.
I'm okay with keeping the current status quo and requiring python<major>.<minor> on Unix and python.exe on Windows for all python flavours.

At least on macOS, Python virtual environment created using venv from the standard library provide executables named python, python3 and python3.x with the second two being symlinks to the first. A t executable is not provided for freethreading environments which is surprising to me.
By default the path of the executable used to run pip is used when creating console entry-points in these environments. The pip, pip3 and pip3.x command all use the path to python for the executable so this path will be used unless pip is started using python3{.X} -m pip.
Based on this I would be in favor of conda using python for the shebang in entry-points.

I tend to be in favor of putting the site-packages path in a separate file in python's info/, for example in link.json or paths.json where it would be possible to increment the version, and make it non-installable by incompatible condas.

The benefit of including the site-packages path in repodata is the ability to correct it with hotfixing after the package is built. This can be used to add this field to existing packages, like the PyPy and GraalPy packages in conda-forge, or correct mistakes in future packages. If functionality is not needed then the field could be moved to link.json or paths.json.
Another benefit of including this is repodata is discoverability. Repodata can be examined without downloading and extracting the package itself.
Incrementing the version would prevent the installation with incompatible version of condas but the user experience is not great. Specifically the environment would solve and the user would not be aware of a problem until the packages are downloaded, extracted and staged for linking.

Another advantage of storing this information in the repodata is that that information is always readily available during installation, even for already installed records (even if the cache is cleared).

So what should the behavior be if more than one package in installed with this field set?

Good question! I assumed it would be ignored except for the package that provides python. In rattler we currently assume that is the package called “python”. I wonder how conda does this.

So what should the behavior be if more than one package in installed with this field set?
I assume failure of some kind?

This field is only allowed on the conda package named python, if packages with other names include this field it is ignored as mentioned in the CEP. There can only be one python package installed in an environment so there will never be a case where there is more that one package installed with this field.
Another way of thinking about this change is that instead of using the package with name python to determine the major and minor version that are used in the site-packages path, the python package can also use this field to declare the path.  The sample conda PR shows how this could be implemented.

In coordination with @jjhelmus, I post this request for a vote:
@conda/steering-council
This vote falls under the "Enhancement Proposal Approval" policy of the conda governance policy,
please vote and/or comment on this proposal at your earliest convenience.
It needs 60% of the Steering Council to vote yes to pass.
To vote, please use the following form to vote. If you have questions concerning the proposal, you may also leave a comment or code review.
This vote will end in one week on 2024-10-15, End of Day, Anywhere on Earth (AoE).
@xhochy (Uwe Korn)

[ ]  yes
[ ]  no
[ ]  abstain

@cj-wright (Christopher J. 'CJ' Wright)

[ ]  yes
[ ]  no
[ ]  abstain

@mariusvniekerk (Marius van Niekerk)

[ ]  yes
[ ]  no
[ ]  abstain

@chenghlee (Cheng H. Lee)

[ ]  yes
[ ]  no
[ ]  abstain

@ocefpaf (Filipe Fernandes)

[ ]  yes
[ ]  no
[ ]  abstain

@marcelotrevisani (Marcelo Duarte Trevisani)

[ ]  yes
[ ]  no
[ ]  abstain

@msarahan (Michael Sarahan)

[ ]  yes
[ ]  no
[ ]  abstain

@mbargull (Marcel Bargull)

[ ]  yes
[ ]  no
[ ]  abstain

@jakirkham (John Kirkham)

[ ]  yes
[ ]  no
[ ]  abstain

@jezdez (Jannis Leidel)

[ ]  yes
[ ]  no
[ ]  abstain

@wolfv (Wolf Vollprecht)

[ ]  yes
[ ]  no
[ ]  abstain

@jaimergp (Jaime Rodríguez-Guerra)

[ ]  yes
[ ]  no
[ ]  abstain

@kkraus14 (Keith Kraus)

[ ]  yes
[ ]  no
[ ]  abstain

@baszalmstra (Bas Zalmstra)

[ ]  yes
[ ]  no
[ ]  abstain

@beckermr (Matthew R. Becker)

[ ]  yes
[ ]  no
[ ]  abstain

@hind-m (Hind Montassif)

[ ]  yes
[ ]  no
[ ]  abstain

@trallard (Tania Allard)

[ ]  yes
[ ]  no
[ ]  abstain

When conda doesn't understand this field, does that Python package work?

Yes, the current GraalPy, PyPy and free-threading CPython python packages in conda-forge include work arounds like symlinks or sitecustomize.py files that work conda linking noarch: python packages into the incorrect path. The CEP mentions these work around the recommends that they be maintained for some time:

Because existing releases of conda, mamba and pixi do not support this field, python packages should continue to provide work around to allow files to be installed into an incorrect site-packages directory until such time as this proposal has been implemented and available for a sufficient amount of time.

I just had one shower-thought: what if we would store a map for this, and could that help with noarch: ruby / noarch: php etc. packages?
It's been a long standing issue that we cannot support other languages with noarch packages as easily as Python for which each package manager needs to add some specific code.
If we had a noarch_map: { ... } field of some sort that would map directories, such as:
noarch_map: {
   "site-packages": "lib/python3.10/site-packages"
}

And for Ruby it could read something like:
noarch_map: {
   "gems": "lib/ruby5.3/gemfiles/gems"
}

This would still leave open the question on pre-compiling py / rb / ... files but it would solve one of the noarch-ruby problems and would not introduce more python special handling.
The noarch_map could be consulted for any noarch package (generic or not) that contains a folder of the sort.
I think this might be worth it to revisit if we can afford it.
I was trying to find some old references / issues, could only find one so far.

https://github.com/conda/conda/issues/702#issuecomment-53069244

I don't think we should introduce any other noarch types. noarch: generic is enough for most use-cases and we should just use a version independent path for other languages. For python, it's historic debt.

But is that possible?
Certainly, one interpretation of noarch-Python is that it's historic debt. But eliminating it would require patching the default path search behavior of python; and there is version-dependent byte compilation as well.
In contrast, for R we are fortunate that the search path is platform and version-independent, but the byte compilation issue remains, which means that currently we have to rebuild many noarch packages with each major R release.
I think it would be good to  enumerate the additional languages being considered and the potential obstacles to the use of noarch-generic. If there are none, great, but at least for me I'm speaking from ignorance of these alternatives.

@isuruf we wouldn't have to introduce any new noarch types. Just move the files in the right places and the noarch-map would take care of it :)
I am just advocating to produce less technical debt for python specifics.

Certainly, one interpretation of noarch-Python is that it's historic debt. But eliminating it would require patching the default path search behavior of python; and there is version-dependent byte compilation as well.

Right, it would require a .pth file to change the search behaviour. noarch: python should be used only for byte compilation, the moving of files shouldn't be necessary IMO, but unrelated to this CEP.
@wolfv, yes, but it's adding another layer of unnecessary behaviour when all we need to do is to make sure the packages end up in a version-independent path in the first place. You are producing more general technical debt in order to produce less technical debt for python specifics.

@jezdez What is the status of this CEP? Did it pass or are there still discussions to be had?

@jezdez What is the status of this CEP? Did it pass or are there still discussions to be had?

I'll update the PR in the coming week, currently out of office.

If we had a noarch_map: { ... } field of some sort that would map directories, such as:

Why make this a nested field when any individual package should only ever define one entry. A python package can declare the location of the site-packages directory, it would not declare a R or Ruby location.  In addition "Flat is better than nested".

One could imagine multiple entries, such as:
noarch_map: {
  "r_bin": "lib/r/5.0/bin",
  "r_lib": "lib/r/lib",
}

and noarch packages that would have r_bin and r_lib at the root would get mapped.
But yeah, idk, maybe not useful enough :)

Awesome, that's great! :)

The vote is closed, and we have the following result:
Total voters: 17 (valid: 13 = 76.47%)
Yes votes (13 / 100.00%):

@xhochy (Uwe Korn)
@mariusvniekerk (Marius van Niekerk)
@chenghlee (Cheng H. Lee)
@ocefpaf (Filipe Fernandes)
@marcelotrevisani (Marcelo Duarte Trevisani)
@msarahan (Michael Sarahan)
@jezdez (Jannis Leidel)
@wolfv (Wolf Vollprecht)
@jaimergp (Jaime Rodríguez-Guerra)
@baszalmstra (Bas Zalmstra)
@beckermr (Matthew R. Becker)
@hind-m (Hind Montassif)
@trallard (Tania Allard)

No votes (0 / 0.00%)):
Abstain votes (0 / 0.00%):
Not voted (4):

@cj-wright (Christopher J. 'CJ' Wright)
@mbargull (Marcel Bargull)
@jakirkham (John Kirkham)
@kkraus14 (Keith Kraus)

Invalid votes (0):
Thus we reached quorum and enough YES votes to mark this as accepted. 🎉

This has been implemented in rattler (and thus in the next pixi release) and rattler-build !


Dashboard Token Listing: RORx

Discord Handle of Submitter: jon.bray.eth
Token Symbol: RORx
Network: Base
Token Address: 0x307d8225C6428A1E505f824b1c97CF9127351f0c
Network Explorer Link: https://basescan.org/address/0x307d8225C6428A1E505f824b1c97CF9127351f0c
Is a Super Token? true
Address of Underlying Token:  0x9e13480a81Af1Dea2f255761810Ef8d6CbF21735
SVG Logo Link: https://aquamarine-evil-bedbug-307.mypinata.cloud/ipfs/QmYWu8exywwMwEmPcFt3ztmURRFc9Z8KTnAY4f6784oRUR
Coingecko or Hardcoded Price?: Coingecko
Coingecko ID: rorschach
Harcoded Price (if Coingecko ID is unavailable):
Token HEX Color: #040404
Info on Listing: creating a staking pool with real-time payments, and would like to stream future allocations to prevent large token unlocks
Please close only after token has been added to resolver!

It should be handled already.


Question about seq2act

@zhouxin913
hi，I can’t find the gbash.sh file in the seq2act project. Is this file not submitted?

In fact, I still have a lot of questions about the seq2act project. Can we add WeChat? I would like to consult you in detail. Thank you very much.
My WeChat ID is<PHONE_NUMBER>2

Hi! sorry for the late response, could you send us (Yang Li and me) an email listing your questions, so that we could track the discussion better. Looking forward to it!
Our emails are listing at the paper https://arxiv.org/abs/2005.03776

Hi! sorry for the late response, could you send us (Yang Li and me) an email listing your questions, so that we could track the discussion better. Looking forward to it!
Our emails are listing at the paper https://arxiv.org/abs/2005.03776

Thank you for your reply. I have sent an email to Professor Li, but I have not received a reply yet. I would like to ask if you can provide the crawled_instructions.json file. Although the instructions in README.md have listed all the steps about how to generate the AndroidHowTo Dataset, but the CommonCrawl Dataset is very large and difficult for me the deal with. So if it is convenient for you guys to supply the final crawled_instructions.json file? That will help a lot of people who have situations like me.

Hello, where can we find gbash.sh file?

I guess gbash.sh is internal to Google and we can’t get it, but it should be possible to remove this line of code and then change the code to runnable
------------------ 原始邮件 ------------------
发件人:                                                                                "google-research/google-research"                                                                                @.>;
发送时间: 2021年12月11日(星期六) 中午1:04
@.>;
抄送: "北京航空航天大学<EMAIL_ADDRESS>主题: Re: [google-research/google-research] Question about seq2act (#658)
Hello, where can we find gbash.sh file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I guess gbash.sh is internal to Google and we can’t get it, but it should be possible to remove this line of code and then change the code to runnable
…
------------------ 原始邮件 ------------------ 发件人: "google-research/google-research" @.>; 发送时间: 2021年12月11日(星期六) 中午1:04 @.>; 抄送: "北京航空航天大学<EMAIL_ADDRESS>主题: Re: [google-research/google-research] Question about seq2act (#658) Hello, where can we find gbash.sh file? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

Thank you so much I will try it


Fixed firefox tooltips

Updated markup from button to div, apparently Firefox doesnt like buttons children to have events.

Does this impact accessibility in any way?

Any other negative side-effects?

It leaves accessibility in roughly the same space.  A button is recognized better by screen readers but we still have tabbing here because I added tabindex="0".  I could additionally add aria-role="button" to help with this difference.  If we are talking about accessibility there are a lot of other items preventing us from being totally accessible like the lazy loader tabbing that has no concept of siblings remaining.


use eslint for typescript

Something I found pretty useful in making jupyterlab extensions (rather than widgets) is the automatic linting of typescript code using eslint. Adding eslint as a dev dependency would allow for running: npm run lint to automatically style the typescript code (e.g. https://github.com/jupyterlab/jupyterlab-git/blob/8d56986409461cd9968d7208da4946fca8c70392/package.json#L23-L25). You can also add it to the the checks that happen on opening PRs https://github.com/jupyterlab/jupyterlab-git/blob/8d56986409461cd9968d7208da4946fca8c70392/.travis.yml#L15
Given that this is more of a python first project this may not be necessary, but thought I'd raise the idea.
FWIW this is included by default in the extension-ts-cookiecutter, but not in the widget-ts-cookiecutter

No, I think it's equally a .ts project, it's just that I'm way better in python, so I tend to write more python.
That's a good idea :)

I too am better at python than typescript. Which I think is why I found the compilation of typescript and linting so helpful!


Use ODP CSW service as primary metadata source

Expected behavior
Our remote ODP data stor implementation should be changed so that its primary metadata source is the ODP's CSW service, which will provide to Cate the following additional dataset meta-information:

Temporal and spatial coverage of each dataset
Dimension names and shape (= dimension sizes) of each dataset / variable
A dataset's human-readable citation information, Terms of Use information, as well as a title.
Overall dataset sizes in bytes

This can be done by using the CSW interface in conjunction with the ESGF search API as is implemented by the CCI Open Data Portal Search user interface.  The steps are:

CSW query using search facets (same facet names as used by ESGF
For each ISO record result extract the identifier(s) for the equivalent ESGF datasets
Query ESGF search API using the ESGF dataset identifiers extracted in 2.

Actual behavior
We don't use the CSW so far and are thus lacking the important meta-information listed above.
Steps to reproduce the problem
Type cate ds info DS or watch the GUI's details panel on a selected remote dataset.

Temporal coverage is derived or OPeNDAP or from filenames which takes too long to compute.
Can't make reasonable assumptions of the dataset sizes to be downloaded and how long it will take
We have no human-readable dataset names or descriptions

Specifications
Cate 0.8.0rc2

[X] Temporal and spatial coverage of each dataset
[ ] Dimension names and shape (= dimension sizes) of each dataset / variable
[X] A dataset's human-readable citation information, Terms of Use information, as well as a title.
[X] Overall dataset sizes in bytes

At the moment there is no information about dimsension names or shape in catalogue


Replace current integration & functional tests with unit tests

Areas affected

[ ] Debugger tests
[ ] Linter tests
[ ] Unit tests
[ ] Formatter tests

I'm sure you've already anticipated this, but hopefully this doesn't result in tightly coupling the tests to the implementation...
Functional tests take more time, but give more safety at the cost of being slower.
I tend to use unit tests mostly for algorithms and other pure functions.  Largely agree with https://web.archive.org/web/20170809062922/https://www.kenneth-truyers.net/2015/06/27/the-test-pyramid/

@jcrben actually point of this exercise is to decouple things because we had a ton of failures hit us when VS Code released with a bug that cascaded through a huge chunk of our tests.

Closing as we have a general agreement on how and what kind of tests we need.
Can re-open or create a new issue if we need to revisit this.


Not able to dump iOS apps

I use the command ktool dump --headers --out RandomHeaders some_random_binary but I just get a whooole lot of errors saying ERROR - ktool.objc:L#678:Class:from_image() - Loading a class failed.
Trying to dump SoundCloud headers. Yes the app is decrypted (anyipa). All that's generated is a SoundCloud.h file with 3 blank lines and then a SoundCloud-Struct.h file, which is empty.

I was able to get ktool to dump an older arm64 binary but on newer binaries I just get 2 empty files MyApp-Structs.h and MyApp.h in the output directory. I also tried to run ktool open it shows the same 2 files.
I was able to see the methods and classes via hopper disassembler just fine though.

If you're able to share binaries it would be highly helpful here

@0cyn hello!  i use  ktool dump tiktok`s framework ,although I got a lot of header files, most of them were incomplete.


Calling on-finish at the 'second-last' step?

Hello,
Is there anyway to call the 'on-finish' function just before the final step so that I can show the 'results' of their input on the 'last step' ?
I am trying to find a config before implementing something on my own.
Please help..

You can utilize the canEnter function or canExit function of the previous step, or you can watch the currentStep property and trigger changes based on that.  Hope this helps.


Refresh page after a bounty claim is submitted

Currently it's hard for users to know that their bounty claim was properly submitted, need to refresh the page so they see it live after successful submission.

what folder/file can i find this issue?


Build system: Build cxl in one step.

to avoid missing compiler flags, build everything at once.
Signed-off-by: Gabriel Krisman Bertazi<EMAIL_ADDRESS>

This fix is supposed to solve the following issue:
https://github.com/ibm-genwqe/genwqe-user/issues/106

Forgot to press merge. Sorry.


Unable to successfully perform "deck sync" with converted OAS definition file

I'm using deck version v1.25.0 to convert a OpenAPI Spec definition file (learnservice_oas.yaml) to Kong file:
deck file openapi2kong \
  --spec learnservice_oas.yaml \
  --output-file learnservice_oas-converted.yaml

I performed deck sync  and received the following errors:
Error: 3 errors occurred:
	while processing event: {Create} plugin request-validator for route 8672b2ee-d302-54fb-9364-025435e1d0aa failed: HTTP status 400 (message: "schema violation (config.parameter_schema: {\n  {\n    schema = \"the JSONschema is missing a top-level 'type' property\"\n  },\n  {\n    schema = \"the JSONschema is missing a top-level 'type' property\"\n  }\n})")
	while processing event: {Create} plugin request-validator for route d60e3425-0968-5c42-9f5c-a46f637f1516 failed: HTTP status 400 (message: "schema violation (config.parameter_schema: {\n  {\n    schema = \"the JSONschema is missing a top-level 'type' property\"\n  }\n})")
	while processing event: {Create} plugin request-validator for route 5a006f23-2702-5318-a120-06d9a8d3cab6 failed: HTTP status 400 (message: "schema violation (config.parameter_schema: {\n  {\n    schema = \"the JSONschema is missing a top-level 'type' property\"\n  }\n})")

There are 3 APIs that trigger the issue, but the root cause is the same. Taking example of "/activities/videos" API:
    get:
      tags:
      - activities
      summary: Returns the user's video activity
      operationId: getVideoActivities
      parameters:
      - name: userId
        in: query
        required: true
        schema:
          "$ref": "#/components/schemas/parameterValue"

deck file openapi2kong converts the schema #/components/schemas/parameterValue to the following:
plugins:
    - config:
        parameter_schema:
        - explode: false
          in: query
          name: userId
          required: true
          schema: '{"$ref":"#/definitions/parameterValue","definitions":{"parameterValue":{"anyOf":[{"$ref":"#/definitions/symbol"},{"$ref":"#/definitions/sanitized_number"}]},"sanitized_number":{"maximum":1000000000,"minimum":-1000000000,"type":"integer"},"symbol":{"maxLength":4096,"type":"string"}}}'
          style: form
        version: draft4
      id: 2d99210c-a989-5fb8-b1cf-9efb3a7e39fd
      name: request-validator
      tags: []
which triggers the error schema violation (config.parameter_schema: {\n {\n schema = \"the JSONschema is missing a top-level 'type' property\"\n

I changed the schema to '{"type": "object","definitions":{"parameterValue":{"anyOf":[{"$ref":"#/definitions/symbol"},{"$ref":"#/definitions/sanitized_number"}]},"sanitized_number":{"maximum":1000000000,"minimum":-1000000000,"type":"integer"},"symbol":{"maxLength":4096,"type":"string"}}}' and there is no more schema violation, which confirms that there needs to be type property.
There is no rational reason on why userId should accept 3 different types: symbol, sanitized_number and an array of symbol
Understand that the example is a trivial one, so propose to change to the following:
    get:
      tags:
      - activities
      summary: Returns the user's video activity
      operationId: getVideoActivities
      parameters:
      - name: userId
        in: query
        required: true
        schema:
          "$ref": "#/components/schemas/symbol"

This is reported in the wrong repo. The problem here is that the top-level type field is missing from the JSONschemas. These are required to properly know how to deserialize the data that comes in from a query or header parameter (since they technically always are strings)
Unfortunately the example OAS config contains the JSONschemas without it. I'll update the examples.