text:
Collapse Accordion is still using Panels

Per the blog post for v4, Panels were to be removed and swapped for Cards?
http://v4-alpha.getbootstrap.com/components/collapse/
The example is using Panels?

You're right the accordion example still using panels
http://v4-alpha.getbootstrap.com/components/collapse/#accordion-example

This is related to an open TODO item for v4:

Collapse

[ ] Make accordion feature of collapse plugin independent of panels?: twbs/bootstrap#10966

I have tested v4 using Cards and this seems to function as expected, I do believe simply updating the documentation may be sufficient?
Ex:
http://pastebin.com/Qruir6wj
Produces:

Hi @adamreed90!
You appear to have posted a live example (http://pastebin.com/Qruir6wj), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 1, column 1 thru column 65: Start tag seen without seeing a doctype first. Expected <!DOCTYPE html>.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

The JavaScript for the accordion feature currently still assumes the usage of Panels; see https://github.com/twbs/bootstrap/blob/c2cf58b4a0abb66689d5f5174842562c26a6e898/js/src/collapse.js#L59

any plans to change that soon?

Would be nice if accordion wasn't dependent on a component (ie. cards) and was just able to collapse/expand based on data-parent.

I see this in collapse.js where it specifically is looking for the .panel selector.
  const Selector = {
    ACTIVES     : '.panel > .in, .panel > .collapsing',
    DATA_TOGGLE : '[data-toggle="collapse"]'
  }

In my very brief testing I changed that to ACTIVES: '.collapse.in, .collapse.collapsing' which seems to work just fine.

https://gist.github.com/ve3/06e276d566079f102d331f0ed398d5fa

            Collapsible Group Item #1

            Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.

            รายการกลุ่มที่ย่อได้ #2

            อุรังคธาตุแซลมอนเจลซูฮกคาร์โก้เพทนาการ วัคค์ออร์เดอร์สเตเดียมสี่แยกโลชั่น จตุคามมาเฟียธุหร่ำ บ๋อยซาบะซาร์ดีนเมคอัพแบ็กโฮพรีเซ็นเตอร์ธุรกรรม บรรพชนคณาญาติอ่วม บู๊สหรัฐมาร์จินไหร่ ไหร่ซิลเวอร์เฟรชเหมยกรีนโรแมนติกจังโก้ คาแร็คเตอร์เจ็ตคอรัปชั่นวาซาบิ เพียวคอร์ส ลิสต์โอยัวะ กระดี๊กระด๊าปอดแหกจุ๊ยฟยอร์ดควีน จิ๊กซอว์ฟอยล์เปปเปอร์มินต์สึนามิเบิร์น ติวเทคโนแครตกระดี๊กระด๊าโคโยตีสเกตช์เป็นไง ติ่มซำโต๊ะจีนป๋าฮัลโลวีน ศิลปากรทัวร์นาเมนท์ก่อนหน้าอัลมอนด์ศิรินทร์ซังเต คาราโอเกะคัตเอาต์คันธาระแต๋ว แอลมอนด์จ๊าบ แฟนตาซีซาดิสต์โบรชัวร์สเตชันเซอร์ไพรส์โหลยโท่ย เกย์นิวส์กรุ๊ป ฟรุตด็อกเตอร์เคอร์ฟิว ฮาลาลแคร็กเกอร์ อัลบัมโซนี่ปัจเจกชน.

            Collapsible Group Item #3

            Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.

Use this while waiting for the fix. I hope it help.

#18400 was merged to address this.

I did not want to open an issue, but about @timalbert 's quote

Would be nice if accordion wasn't dependent on a component (ie. cards) and was just able to collapse/expand based on data-parent.

Any reason why the accordion is card-dependent ?

IMO it's an historical dependency because on V3 accordion depend on panel which was transformed to card in V4.
But see this : https://github.com/twbs/bootstrap/pull/17021 and you'll find that accordion won't depend on card at the end of the V4

authors: Johann-S KeitIG adamreed90 atu-record chrismbarr cvrebert mdo timalbert twbs-lmvtfy ve3


text:
Look into enabling mangle-props and mangle-regex terser's options

See #21715

@Johann-S: you want to leave this open or should we close it?

Didn't hade time to shim on that issue :worried: but maybe in the futur :smile: so we can let that issue openned

@XhmikosR Should we close this out if we're moving off Uglify?

terser has the same options, at least for the time being, so this still applies.

FYI this does save us currently 608 bytes from the gzip bootstrap.min.js file:

We just need to test the minified build or something, so that we are sure nothing breaks.

We should really try to do this:

Closing as stale. If you have time to revisit ever @XhmikosR we can re-open, but I know you're swamped, so let's not push it :).

I'm going to open this again, because I think the gains are pretty big to ignore.
Our main issue is that we need a way to test the minified files too.
WIP branch: https://github.com/twbs/bootstrap/compare/main-xmr-min-mangle

source: gharchive/issue

authors: Johann-S XhmikosR mdo

repo: twbs/bootstrap

license: MIT

license_type: permissive

license_source: github-api


text:
Split -x in navbar-nav-link-padding-x to -r (right) and -l (left)

At this current state, if a navbar menu is positioned to the right side, the last menu/item will have an extra (unnecessary) padding on the right side, so that it is not on the very right edge of the container.
Similarly, if a navbar is positioned to the left without anything before the navbar, then the first menu/item will have an extra padding on the left side, so that it is not on the left edge of the container.
If the $navbar-nav-link-padding-x is being splitted into $navbar-nav-link-padding-l and $navbar-nav-link-padding-r then it will be easier to manage this.

We don't do that really anywhere so, so unlikely to happen at this time. Generally speaking, padding should be balanced as it affects the hit area for links.

authors: gentledawn mdo


text:
Container negative auto margin

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Additional margin and padding classes that allow to extract column space from container to left or right side.
Demo: https://codepen.io/ArtZ91/pen/wvPgMQX

Add --container-max-width CSS variables.
Add classes like ms-n-auto and me-n-auto for new margin values.
Add classes like ps-auto and pe-auto for new padding values.

Motivation and context
Some designers like to draw blocks that start from the viewport side and ends inside container column.

This is an interesting idea as a helper for containers, I see the appeal for generating viewport-wide content despite being within a container. Happy to experiment with this at some point myself or to see a PR :).

@mdo PR was added and codepen example was updated (added JS code to fix scrollbar issue).

authors: arthurshlain mdo


text:
bootstrap doesn't compile my extended color palette

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
bootstrap doesn't compile my extended color palette
Reduced test cases
I am trying to compile the following scss file for Bootstrap::
@import "node_modules/bootstrap/scss/bootstrap";

$custom-colors: (
        "rcred": #DA291C,
        "rcwine": #A50034,
        "rcblue": #002554,
        "rcgold": #FFB200,
        "rcsilver": #808080,
        "rcskyblue": #00B0F0,
        "aliceblue": #F0F8FF,
        "antiquewhite": #FAEBD7,
        "aqua": #00FFFF,
        "aquamarine": #7FFFD4,
        "azure": #F0FFFF,
        "beige": #F5F5DC,
        "bisque": #FFE4C4,
        "blanchedalmond": #FFEBCD,
        "blueviolet": #8A2BE2,
        "brown": #A52A2A,
        "burlywood": #DEB887,
        "cadetblue": #5F9EA0,
        "chartreuse": #7FFF00,
        "chocolate": #D2691E,
        "coral": #FF7F50,
        "cornflowerblue": #6495ED,
        "cornsilk": #FFF8DC,
        "crimson": #DC143C,
        "darkblue": #00008B,
        "darkcyan": #008B8B,
        "darkgoldenrod": #B8860B,
        "darkgray": #A9A9A9,
        "darkgreen": #006400,
        "darkgrey": #A9A9A9,
        "darkkhaki": #BDB76B,
        "darkmagenta": #8B008B,
        "darkolivegreen": #556B2F,
        "darkorange": #FF8C00,
        "darkorchid": #9932CC,
        "darkred": #8B0000,
        "darksalmon": #E9967A,
        "darkseagreen": #8FBC8F,
        "darkslateblue": #483D8B,
        "darkslategray": #2F4F4F,
        "darkslategrey": #2F4F4F,
        "darkturquoise": #00CED1,
        "darkviolet": #9400D3,
        "deeppink": #FF1493,
        "deepskyblue": #00BFFF,
        "dimgray": #696969,
        "dimgrey": #696969,
        "dodgerblue": #1E90FF,
        "firebrick": #B22222,
        "floralwhite": #FFFAF0,
        "forestgreen": #228B22,
        "fuchsia": #FF00FF,
        "gainsboro": #DCDCDC,
        "ghostwhite": #F8F8FF,
        "gold": #FFD700,
        "goldenrod": #DAA520,
        "greenyellow": #ADFF2F,
        "grey": #808080,
        "honeydew": #F0FFF0,
        "hotpink": #FF69B4,
        "indianred": #CD5C5C,
        "ivory": #FFFFF0,
        "khaki": #F0E68C,
        "lavender": #E6E6FA,
        "lavenderblush": #FFF0F5,
        "lawngreen": #7CFC00,
        "lemonchiffon": #FFFACD,
        "lightblue": #ADD8E6,
        "lightcoral": #F08080,
        "lightcyan": #E0FFFF,
        "lightgoldenrodyellow": #FAFAD2,
        "lightgray": #D3D3D3,
        "lightgreen": #90EE90,
        "lightgrey": #D3D3D3,
        "lightpink": #FFB6C1,
        "lightsalmon": #FFA07A,
        "lightseagreen": #20B2AA,
        "lightskyblue": #87CEFA,
        "lightslategray": #778899,
        "lightslategrey": #778899,
        "lightsteelblue": #B0C4DE,
        "lightyellow": #FFFFE0,
        "lime": #00FF00,
        "limegreen": #32CD32,
        "linen": #FAF0E6,
        "magenta": #FF00FF,
        "maroon": #800000,
        "mediumaquamarine": #66CDAA,
        "mediumblue": #0000CD,
        "mediumorchid": #BA55D3,
        "mediumpurple": #9370DB,
        "mediumseagreen": #3CB371,
        "mediumslateblue": #7B68EE,
        "mediumspringgreen": #00FA9A,
        "mediumturquoise": #48D1CC,
        "mediumvioletred": #C71585,
        "midnightblue": #191970,
        "mintcream": #F5FFFA,
        "mistyrose": #FFE4E1,
        "moccasin": #FFE4B5,
        "navajowhite": #FFDEAD,
        "navy": #000080,
        "oldlace": #FDF5E6,
        "olive": #808000,
        "olivedrab": #6B8E23,
        "orangered": #FF4500,
        "orchid": #DA70D6,
        "palegoldenrod": #EEE8AA,
        "palegreen": #98FB98,
        "paleturquoise": #AFEEEE,
        "palevioletred": #DB7093,
        "papayawhip": #FFEFD5,
        "peachpuff": #FFDAB9,
        "peru": #CD853F,
        "plum": #DDA0DD,
        "powderblue": #B0E0E6,
        "rebeccapurple": #663399,
        "rosybrown": #BC8F8F,
        "royalblue": #4169E1,
        "saddlebrown": #8B4513,
        "salmon": #FA8072,
        "sandybrown": #F4A460,
        "seagreen": #2E8B57,
        "seashell": #FFF5EE,
        "sienna": #A0522D,
        "silver": #C0C0C0,
        "skyblue": #87CEEB,
        "slateblue": #6A5ACD,
        "slategray": #708090,
        "slategrey": #708090,
        "snow": #FFFAFA,
        "springgreen": #00FF7F,
        "steelblue": #4682B4,
        "tan": #D2B48C,
        "thistle": #D8BFD8,
        "tomato": #FF6347,
        "transparent": #00000000,
        "turquoise": #40E0D0,
        "violet": #EE82EE,
        "wheat": #F5DEB3,
        "white": #FFFFFF,
        "whitesmoke": #F5F5F5,
        "yellowgreen": #9ACD32
);

@each $name, $value in $custom-colors {
  .bg-#{$name} {
    background-color: $value !important;
  }

  .#{$name}:hover {
    color: white !important;
  }

  .text-#{$name} {
    color: $value !important;
  }

  @error "El color: `#{$name}` que has pasado no está disponible.";

}

$theme-colors: map-merge($theme-colors, $custom-colors);

@import "node_modules/bootstrap/scss/bootstrap";

custom error catcher that I have placed:
--------------------
Change Detected...
styles.scss
--------------------
Compilation Error
Error: El color: `rcred` que has pasado no está disponible.
        on line 162 of sass/d:\Desarrollos\Personales\custom BS5\styles.scss
>>   @error "El color: `#{$name}` que has pasado no está disponible.";

   --^

--------------------
Watching...
--------------------

without the custom error:
--------------------
Change Detected...
styles.scss
--------------------
Compilation Error
Error: argument `$color` of `red($color)` must be a color
        on line 185 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `red`
        from line 185 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `luminance`
        from line 174 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `contrast-ratio`
        from line 159 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `color-contrast`
        from line 10 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\mixins\_buttons.scss, in mixin `button-variant`
        from line 61 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_buttons.scss
        from line 24 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\bootstrap.scss
        from line 166 of sass/d:\Desarrollos\Personales\custom BS5\styles.scss
>>     "r": red($color),

   ---------^

--------------------
Watching...
--------------------

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.1.3

i have update the script to test the example of https://getbootstrap.com/docs/5.1/customize/color/#all-colors:
@import "node_modules/bootstrap/scss/bootstrap";

$rc-red: #DA291C;
$rc-wine: #A50034;
$rc-blue: #002554;
$rc-gold: #FFB200;
$rc-silver: #808080;
$rc-skyblue: #00B0F0;
$aliceblue: 	#F0F8FF;
$antiquewhite: 	#FAEBD7;
$aqua: 	#00FFFF;
$aquamarine: 	#7FFFD4;
$azure: 	#F0FFFF;
$beige: 	#F5F5DC;
$bisque: 	#FFE4C4;
$blanchedalmond: 	#FFEBCD;
$blueviolet: 	#8A2BE2;
$brown: 	#A52A2A;
$burlywood: 	#DEB887;
$cadetblue: 	#5F9EA0;
$chartreuse: 	#7FFF00;
$chocolate: 	#D2691E;
$coral: 	#FF7F50;
$cornflowerblue: 	#6495ED;
$cornsilk: 	#FFF8DC;
$crimson: 	#DC143C;
$darkblue: 	#00008B;
$darkcyan: 	#008B8B;
$darkgoldenrod: 	#B8860B;
$darkgray: 	#A9A9A9;
$darkgreen: 	#006400;
$darkgrey: 	#A9A9A9;
$darkkhaki: 	#BDB76B;
$darkmagenta: 	#8B008B;
$darkolivegreen: 	#556B2F;
$darkorange: 	#FF8C00;
$darkorchid: 	#9932CC;
$darkred: 	#8B0000;
$darksalmon: 	#E9967A;
$darkseagreen: 	#8FBC8F;
$darkslateblue: 	#483D8B;
$darkslategray: 	#2F4F4F;
$darkslategrey: 	#2F4F4F;
$darkturquoise: 	#00CED1;
$darkviolet: 	#9400D3;
$deeppink: 	#FF1493;
$deepskyblue: 	#00BFFF;
$dimgray: 	#696969;
$dimgrey: 	#696969;
$dodgerblue: 	#1E90FF;
$firebrick: 	#B22222;
$floralwhite: 	#FFFAF0;
$forestgreen: 	#228B22;
$fuchsia: 	#FF00FF;
$gainsboro: 	#DCDCDC;
$ghostwhite: 	#F8F8FF;
$gold: 	#FFD700;
$goldenrod: 	#DAA520;
$greenyellow: 	#ADFF2F;
$grey: 	#808080;
$honeydew: 	#F0FFF0;
$hotpink: 	#FF69B4;
$indianred: 	#CD5C5C;
$ivory: 	#FFFFF0;
$khaki: 	#F0E68C;
$lavender: 	#E6E6FA;
$lavenderblush: 	#FFF0F5;
$lawngreen: 	#7CFC00;
$lemonchiffon: 	#FFFACD;
$lightblue: 	#ADD8E6;
$lightcoral: 	#F08080;
$lightcyan: 	#E0FFFF;
$lightgoldenrodyellow: 	#FAFAD2;
$lightgray: 	#D3D3D3;
$lightgreen: 	#90EE90;
$lightgrey: 	#D3D3D3;
$lightpink: 	#FFB6C1;
$lightsalmon: 	#FFA07A;
$lightseagreen: 	#20B2AA;
$lightskyblue: 	#87CEFA;
$lightslategray: 	#778899;
$lightslategrey: 	#778899;
$lightsteelblue: 	#B0C4DE;
$lightyellow: 	#FFFFE0;
$lime: 	#00FF00;
$limegreen: 	#32CD32;
$linen: 	#FAF0E6;
$magenta: 	#FF00FF;
$maroon: 	#800000;
$mediumaquamarine: 	#66CDAA;
$mediumblue: 	#0000CD;
$mediumorchid: 	#BA55D3;
$mediumpurple: 	#9370DB;
$mediumseagreen: 	#3CB371;
$mediumslateblue: 	#7B68EE;
$mediumspringgreen: 	#00FA9A;
$mediumturquoise: 	#48D1CC;
$mediumvioletred: 	#C71585;
$midnightblue: 	#191970;
$mintcream: 	#F5FFFA;
$mistyrose: 	#FFE4E1;
$moccasin: 	#FFE4B5;
$navajowhite: 	#FFDEAD;
$navy: 	#000080;
$oldlace: 	#FDF5E6;
$olive: 	#808000;
$olivedrab: 	#6B8E23;
$orangered: 	#FF4500;
$orchid: 	#DA70D6;
$palegoldenrod: 	#EEE8AA;
$palegreen: 	#98FB98;
$paleturquoise: 	#AFEEEE;
$palevioletred: 	#DB7093;
$papayawhip: 	#FFEFD5;
$peachpuff: 	#FFDAB9;
$peru: 	#CD853F;
$plum: 	#DDA0DD;
$powderblue: 	#B0E0E6;
$rebeccapurple: 	#663399;
$rosybrown: 	#BC8F8F;
$royalblue: 	#4169E1;
$saddlebrown: 	#8B4513;
$salmon: 	#FA8072;
$sandybrown: 	#F4A460;
$seagreen: 	#2E8B57;
$seashell: 	#FFF5EE;
$sienna: 	#A0522D;
$silver: 	#C0C0C0;
$skyblue: 	#87CEEB;
$slateblue: 	#6A5ACD;
$slategray: 	#708090;
$slategrey: 	#708090;
$snow: 	#FFFAFA;
$springgreen: 	#00FF7F;
$steelblue: 	#4682B4;
$tan: 	#D2B48C;
$thistle: 	#D8BFD8;
$tomato: 	#FF6347;
$transparent: 	#00000000;
$turquoise: 	#40E0D0;
$violet: 	#EE82EE;
$wheat: 	#F5DEB3;
$white: 	#FFFFFF;
$whitesmoke: 	#F5F5F5;
$yellowgreen: 	#9ACD32;

$custom-colors: (
  "rc-red": $rc-red,
  "rc-wine": $rc-wine,
  "rc-blue": $rc-blue,
  "rc-gold": $rc-gold,
  "rc-silver": $rc-silver,
  "rc-skyblue": $rc-skyblue,
  "aliceblue": $aliceblue,
  "antiquewhite": $antiquewhite,
  "aqua": $aqua,
  "aquamarine": $aquamarine,
  "azure": $azure,
  "beige": $beige,
  "bisque": $bisque,
  "blanchedalmond": $blanchedalmond,
  "blueviolet": $blueviolet,
  "brown": $brown,
  "burlywood": $burlywood,
  "cadetblue": $cadetblue,
  "chartreuse": $chartreuse,
  "chocolate": $chocolate,
  "coral": $coral,
  "cornflowerblue": $cornflowerblue,
  "cornsilk": $cornsilk,
  "crimson": $crimson,
  "darkblue": $darkblue,
  "darkcyan": $darkcyan,
  "darkgoldenrod": $darkgoldenrod,
  "darkgray": $darkgray,
  "darkgreen": $darkgreen,
  "darkgrey": $darkgrey,
  "darkkhaki": $darkkhaki,
  "darkmagenta": $darkmagenta,
  "darkolivegreen": $darkolivegreen,
  "darkorange": $darkorange,
  "darkorchid": $darkorchid,
  "darkred": $darkred,
  "darksalmon": $darksalmon,
  "darkseagreen": $darkseagreen,
  "darkslateblue": $darkslateblue,
  "darkslategray": $darkslategray,
  "darkslategrey": $darkslategrey,
  "darkturquoise": $darkturquoise,
  "darkviolet": $darkviolet,
  "deeppink": $deeppink,
  "deepskyblue": $deepskyblue,
  "dimgray": $dimgray,
  "dimgrey": $dimgrey,
  "dodgerblue": $dodgerblue,
  "firebrick": $firebrick,
  "floralwhite": $floralwhite,
  "forestgreen": $forestgreen,
  "fuchsia": $fuchsia,
  "gainsboro": $gainsboro,
  "ghostwhite": $ghostwhite,
  "gold": $gold,
  "goldenrod": $goldenrod,
  "greenyellow": $greenyellow,
  "grey": $grey,
  "honeydew": $honeydew,
  "hotpink": $hotpink,
  "indianred": $indianred,
  "ivory": $ivory,
  "khaki": $khaki,
  "lavender": $lavender,
  "lavenderblush": $lavenderblush,
  "lawngreen": $lawngreen,
  "lemonchiffon": $lemonchiffon,
  "lightblue": $lightblue,
  "lightcoral": $lightcoral,
  "lightcyan": $lightcyan,
  "lightgoldenrodyellow": $lightgoldenrodyellow,
  "lightgray": $lightgray,
  "lightgreen": $lightgreen,
  "lightgrey": $lightgrey,
  "lightpink": $lightpink,
  "lightsalmon": $lightsalmon,
  "lightseagreen": $lightseagreen,
  "lightskyblue": $lightskyblue,
  "lightslategray": $lightslategray,
  "lightslategrey": $lightslategrey,
  "lightsteelblue": $lightsteelblue,
  "lightyellow": $lightyellow,
  "lime": $lime,
  "limegreen": $limegreen,
  "linen": $linen,
  "magenta": $magenta,
  "maroon": $maroon,
  "mediumaquamarine": $mediumaquamarine,
  "mediumblue": $mediumblue,
  "mediumorchid": $mediumorchid,
  "mediumpurple": $mediumpurple,
  "mediumseagreen": $mediumseagreen,
  "mediumslateblue": $mediumslateblue,
  "mediumspringgreen": $mediumspringgreen,
  "mediumturquoise": $mediumturquoise,
  "mediumvioletred": $mediumvioletred,
  "midnightblue": $midnightblue,
  "mintcream": $mintcream,
  "mistyrose": $mistyrose,
  "moccasin": $moccasin,
  "navajowhite": $navajowhite,
  "navy": $navy,
  "oldlace": $oldlace,
  "olive": $olive,
  "olivedrab": $olivedrab,
  "orangered": $orangered,
  "orchid": $orchid,
  "palegoldenrod": $palegoldenrod,
  "palegreen": $palegreen,
  "paleturquoise": $paleturquoise,
  "palevioletred": $palevioletred,
  "papayawhip": $papayawhip,
  "peachpuff": $peachpuff,
  "peru": $peru,
  "plum": $plum,
  "powderblue": $powderblue,
  "rebeccapurple": $rebeccapurple,
  "rosybrown": $rosybrown,
  "royalblue": $royalblue,
  "saddlebrown": $saddlebrown,
  "salmon": $salmon,
  "sandybrown": $sandybrown,
  "seagreen": $seagreen,
  "seashell": $seashell,
  "sienna": $sienna,
  "silver": $silver,
  "skyblue": $skyblue,
  "slateblue": $slateblue,
  "slategray": $slategray,
  "slategrey": $slategrey,
  "snow": $snow,
  "springgreen": $springgreen,
  "steelblue": $steelblue,
  "tan": $tan,
  "thistle": $thistle,
  "tomato": $tomato,
  "transparent": $transparent,
  "turquoise": $turquoise,
  "violet": $violet,
  "wheat": $wheat,
  "white": $white,
  "whitesmoke": $whitesmoke,
  "yellowgreen": $yellowgreen
);

$theme-colors: map-merge($theme-colors, $custom-colors);

@each $color, $value in $custom-colors {
  .bg-#{$color} {
    background-color: $value !important;
  }

  .text-#{$color} {
    color: $value !important;
  }

}

@import "node_modules/bootstrap/scss/bootstrap";

Error output:
Change Detected...
styles.scss
--------------------
Compilation Error
Error: argument `$color` of `red($color)` must be a color
        on line 185 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `red`
        from line 185 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `luminance`
        from line 174 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `contrast-ratio`
        from line 159 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_functions.scss, in function `color-contrast`
        from line 10 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\mixins\_buttons.scss, in mixin `button-variant`
        from line 61 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\_buttons.scss
        from line 24 of sass/d:\Desarrollos\Personales\custom BS5\node_modules\bootstrap\scss\bootstrap.scss
        from line 311 of sass/d:\Desarrollos\Personales\custom BS5\styles.scss
>>     "r": red($color),

   ---------^

--------------------
Watching...
--------------------

to solve it remove duplicate name color like white; and Bootstrap not support SCSS transparent color like: "transparent": #00000000, remove it to.


text:
Update to Jekyll v3.0.0.

Fixes #18073
We need to wait for jekyll-redirect-from to support Jekyll 3 first; https://github.com/jekyll/jekyll-redirect-from/issues/75, we need a new gem published

/CC @cvrebert

OK, we get one error
Liquid error: undefined method `getConverterImpl’ for #<jekyll::site:0x00000003a51fd8></jekyll::site:0x00000003a51fd8>

Trying to figure it out.

I think it's due to our callout.rb plugin.

All right, I think everything should work now.

Tested it out locally; LGTM.
:ship:

Should we backport this to 3.x too so that we don't have to switch Jekyll stuff around?

I can't find a reason not to backport it.

source: gharchive/pull-request

authors: XhmikosR cvrebert


text:
Blockquote border width

zhegeshi wo men

Hi @wuxingfang!
Thanks for wanting to contribute to Bootstrap by sending this pull request!
Unfortunately, your pull request seems to have some problems:

The CNAME file should never be modified.
Changes must be made to the original Sass or Less source code file(s), not just the compiled CSS file(s).
Changes must be made to the original JS source code file(s), not just the generated concatenated JS file(s).

You'll need to fix these mistakes and revise your pull request before we can proceed further.
Once you've fixed these problems, you can either ask the maintainers to re-open this pull request, or you can create a new pull request.
Thanks!
(Please note that this is a fully automated comment.)

authors: twbs-rorschach wuxingfang


text:
Changing Copyright info for new year.

This won't be implemented until midnight, but will be easier to push if it's ready to go!

Good

Thanks, but there are more places the year needs to change.

authors: AustinTice XhmikosR gjp3384


text:
Rewrote displays type variables to use them as a map

Rewrited displays type variables to use them as a map so it would be easier to extend and modify.
Fixes #26515.

please fix the test failures.

Could you check now? I tried to just push the fixes to my own branch but the pull request would never get updated (I don't know if its a github bug or what)... so I pushed to my own fork master... according to github message "Add more commits by pushing to the master branch on afanjul/bootstrap."
It's a bit complicated to just update a pull request... :(

GitHub could have a slowness issue right now, but usually you just push to your branch.

Hi @afanjul,
I'm a bit afraid it's not clear what 300 means here for people who don't have a clue the font weight is set:
https://github.com/twbs/bootstrap/blob/3182990fee5aa32b3e4146685e257821c37d9666/scss/_variables.scss#L306-L309
I did a similar PR once, but closed it since I was a bit worried we're mixing up too many different "styles" of configuration: https://github.com/twbs/bootstrap/pull/26533.

Hi @afanjul,
I'm a bit afraid it's not clear what 300 means here for people who don't have a clue the font weight is set:
bootstrap/scss/_variables.scss
Lines 306 to 309 in 3182990
1:(6rem, 300),
2:(5.5rem, 300),
3:(4.5rem, 300),
4:(3.5rem, 300)
I did a similar PR once, but closed it since I was a bit worried we're mixing up too many different "styles" of configuration: #26533.

Another alternative (a worse one from my point of view) is simply split it in two maps:
In _variables.scss
$display-sizes: (
  1:6rem,
  2:5.5rem,
  3:4.5rem,
  4:3.5rem
);
$display-weights: (
  1:300,
  2:300,
  3:300,
  4:300
);

The only "issue" is that you have to use the $index in for loop (and maintain a coherence in the maps):
@for $i from 1 through length($display-sizes) {
  $size: nth($display-size, $i);
  $weight: nth($display-weight, $i);
  .display-#{$index} {
    @include font-size($size);
    font-weight: $weight;
    line-height: $display-line-height;
  }
}

But the worst method, for me, is the actual one, with separate values/variables for size and weights. It's ugly and not extendible.

Anyway, if you are using Sass as a "web developer", I'm assuming that you can read and interpret docs, comments, functions, etc.  Either way, you will be using compiling bootstrap.css

For example, what if I want to add another "display-5" in the actual bootstrap version?
I can add a new $spacers or $sizes element, but you don't let me do the same with "$displays"? A bit odd..

I did a similar PR once, but closed it since I was a bit worried we're mixing up too many different "styles" of configuration: #26533.

Reading that thread again @MartijnCuppens, it looks like I punted on it for redoing bigger things in v5. I can't recall exactly what though, but perhaps it was related to your RFS work?

Now I think that the source code is complete and prettier... Using a map for $display-types, with key value explicit names. So now is pretty easy to modify or extend by the people... Just be aware of the new variable called $display-types for docs, and so...

This needs a rebase + squash

Replaced by #30568.

authors: MartijnCuppens XhmikosR afanjul mdo


text:
How to filter only tweets from original user with  stream.filter(follow=['12345'])

it looks like stream.filter(follow=['12345']) includes tweets at someone and RT, what's the way to get tweets solely from that user?

I too am experiencing this. Did anyone find a solution?

I had to write a few lines of code to filter it out my self. I did not find a solution for this in tweepy.

What did you do to filter it out yourself?

Looking at Twitter's API it seems like it is not possible to filter tweets from original user out.
My work around method:

I created a function that checks whether the status object is from original creator or not.
I will only print/save tweet if it is from the original creator.

def from_creator(status):
    if hasattr(status, 'retweeted_status'):
        return False
    elif status.in_reply_to_status_id != None:
        return False
    elif status.in_reply_to_screen_name != None:
        return False
    elif status.in_reply_to_user_id != None:
        return False
    else:
        return True

class MyStreamListener(tweepy.StreamListener):

    def on_status(self, status):
        if from_creator(status):
            try:
                # Prints out the tweet
                print(status.text)
                # Saves tweet into a file
                with open("Test.txt", 'a') as file:
                    file.write(status.text)
                return True
            except BaseException as e:
                print("Error on_data %s" % str(e))
            return True
        return True

    def on_error(self, status_code):
        if status_code == 420:
            print("Error 420")
            #returning False in on_error disconnects the stream
            return False

If the API key I'm using for OAuth is linked to my personal Twitter account, I seem to only get tweets from users my account is following. How do I stream all tweets filtered globally, and not just the from the users my account follows?

In short, this isn't possible natively to Twitter's API.
The only parameter the statuses/filter endpoint has for following a specific user is follow, which:

For each user specified, the stream will contain:

Tweets created by the user.
Tweets which are retweeted by the user.
Replies to any Tweet created by the user.
Retweets of any Tweet created by the user.
Manual replies, created without pressing a reply button (e.g. @twitterapi I agree).

See https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/basic-stream-parameters.
You'll have to filter out other Tweets yourself.
@mathemaphysics That is not related to this issue, but I'm unable to reproduce this using Stream.filter.
The statuses/filter endpoint is not limited to a specific user context like the now deprecated and retired User Streams used to be.

repo: tweepy/tweepy

license: mit

license_source: bigquery


text:
POST to hasMany relationship incorrectly includes empty 'attributes' objects

Per API spec here: http://jsonapi.org/format/#crud-updating-to-many-relationships
hasMany relationships can be bound via a POST action to the relationship URL:
implementation example (this is a sync action which adds all available 'devices' to a 'project')
            addDevicesToProject() {
                this.startEvent();

                return new Promise((resolve, reject) => {
                    //const create = [];

                    const create = this.availableDevices.map((device) => {
                        return {type: 'devices', id: device.id}
                    });
                    JsonApi.one('project', this.project.id).all('device').post(create)
                        .then((responses) => {
                            this.successEvent(responses);
                            console.log('addDevices', responses);
                            resolve(responses);
                        })
                        .catch((error) => {
                            this.errorEvent(error);
                            reject(error);
                        });
                });
            }

In the above, the "create" const is prepared with an array of relationship objects.
The prepared payload is:
{"data":[{"type":"devices","attributes":{},"id":"27"},{"type":"devices","attributes":{},"id":"28"}],"meta":{}}

The 'attributes' fields are unnecessary and cause problems.
I am testing with a version 2.0.3.

I came here to close this but I see a fix references this...
My feedback is in error largely because relationship binds are not meant to be sent via POST to this URL. It is missing the "relationships" part of the URL.
For now I came up with a hacky middleware to get around this limitation in Devour.

@SirLamer I created a PR - I've tested this fix in my project.
Just have to get the build passing.
https://github.com/twg/devour/pull/98

To get around the "relationships" part missing, I've called .all('relationships) ¯_(ツ)_/¯

Yes your solution for attributes nonetheless seems appropriate in general, even though my initial issue comment is invalid.

authors: SirLamer masimons

repo: twg/devour

license: ISC


text:
The border of vertical button is not finely cropped

There is a little gray shades around vertical aligned buttons. It seems the vertical button is not finely cropped

This is fixed.


text:
Notebook mode (Javascript/Node) not working on MacOS

Plugin: v1.8.1
Obsidian: v1.3.7
MacOS: Ventura 13.5
Node: v20.4.0 /opt/homebrew/bin/node
No errors in console.
https://github.com/twibiral/obsidian-execute-code/assets/865311/616b2fc8-b693-4c4f-8023-dbb039bcd63a

same here 👍

authors: jancbeck mi-skam

repo: twibiral/obsidian-execute-code


text:
List - incorrect behavior when the control style is enabled "multicol"

I am using "mIRC v7.67" + "DCX dll v3.1-git428" in system "Windows 8.1 x64".
When set the control style multicol, when a line is selected, then in that part of the line with text that goes beyond the set boundaries of the column width, several text layers are superimposed on each other - it looks like a constant increase in bold font. Logically, this part of the line with the text should be hidden (not erased or cut off) beyond the set width of the column border and can be completely read by moving the cursor to the right and left.
If I am doing something wrong, please explain how to properly configure and use it. Thanks.

Here is a test piece of script to reproduce this the problem. To run the script click on "F5" or enter the command "/list_test":
alias F5 { list_test }
alias list_test {
  if ($dialog(list_test)) .dialog -x list_test
  else { .dialog -m list_test list_test }
}
dialog list_test {
  title "List test"
  icon $mircexe,0
  option pixels
  size -1 -1 300 255
}
on *:DIALOG:list_test:init:*:{
  .dcx Mark $dname list_test_work
  .xdialog -b $dname +ty
  .xdialog -g $dname +b $rgb(20,20,27)
  list_making $dname 1
}
alias -l list_making {
  .xdialog -c $1 $2 list 30 30 240 200 notheme multicol
  .xdid -x $1 $2 +b
  .xdid -m $1 $2 +w 100
  .xdid -C $1 $2 +b $rgb(40,40,47)
  .xdid -C $1 $2 +t $rgb(235,227,203)
  .xdid -f $1 $2 + ansi 10 Comic Sans MS
  var %i 1 | while (%i <= 10) {
    .xdid -a $1 $2 %i %i - Line of text to test
    inc %i
  }
}
alias list_test_work {}

fixed.

authors: EpicNet OokEek

repo: twig/dcxdll


text:
Docs styling improvements

Summary

Uses Paste tokens for colors
Uses Paste fonts
Added tabs to features overview and categorized the features accordingly
Updated to new Flex logo assets
Fixed a couple typos

Checklist

[x] Tested changes end to end
[x] Added PR Label "ready-for-review"
[x] Requested one or more reviewers for the PR

Updated Paste appearance of docs with new logos:

New feature overview tabs:


text:
Incorrect guidelines for launching sample project

CONTRIBUTING.md indicates the sample project may be created via sbt run. However, launching run in the sbt console fails with java.lang.RuntimeException: No main class detected.
(PR Incoming)

Resolved in #119 , thanks again!

authors: blast-hardcheese charles-rumley

repo: twilio/guardrail


text:
2.0 wip - Removed dotted outline on navbar dropdown menu

Screenshot of the issue: http://img337.imageshack.us/img337/9261/bootstrap.png

We can't in good conscience remove the browser's :focus effect in these instances. Perhaps we can replace it (there was another issue about this recently), but that will have to wait I think. We'll attempt to tackle things like this in our accessibility issue when we get to that (#931).

Yes, you are quite right. We shouldn't remove the :focus effect.
Perhaps, the dropdown JavaScript plugin should unfocus the toggle element after being clicked?

authors: SimonBartlett markdotto

repo: twitter/bootstrap


text:
Hover state added for active

.nav-list .active > a:hover {
background-color: #000;
}

Just resolved this (will push shortly) by making the hover state the same as the active. Thanks!

Cool. I threw the #000 in there only for attention. Thanks!
/
Van
646-831-9219
(Sent from an Apple device that is mostly awesome, but sometimes inserts its own words into email..leading to awkward misunderstandings)
On Feb 1, 2012, at 8:54 PM, Mark Ottoreply@reply.github.com wrote:

Just resolved this (will push shortly) by making the hover state the same as the active. Thanks!

Reply to this email directly or view it on GitHub:
https://github.com/twitter/bootstrap/issues/1528#issuecomment-3771256

authors: markdotto vanshea


text:
Community notes data is again out of date – most recent contribution was 7 days ago

A similar issue occurred not very long ago – I flagged it in #254.
It looks like it is happening again – the note on https://x.com/i/communitynotes/download-data currently says:

Data includes contributions up until 2:03 AM · Aug 18, 2024

I.e. 7 days ago.
It’s still useful to have these bulk data downloads even with this delay, but it would be useful to know if this length of delay should be expected going forward.

Retrospectively closing this, as it was resolved.
There does seem to be a general problem, though, that community notes data always lags by more than the documented one day, and sometimes by significantly more.

it's been down again for the last 5 or so days.
stuck on 1437535 notes

Thanks, @plopnl – I’ve reopened this issue accordingly.

In fact, I’ll close this (because it was resolved at the time) and will open a new issue.

authors: andylolz plopnl

repo: twitter/communitynotes


text:
modify kafka-spout README.md

There is a little clerical error in kafka-spout README.md file.

Ship it!

authors: kramasamy mycFelix

repo: twitter/heron


text:
Change imageIdentifier later?

Is it possible to change imageIdentifier later somehow?
Use case: the user uploads an image to the server. Before sending the image to the server, the app stores it into the cache. After the image is uploaded, it retrieves an url of the image and updates imageIdentifier.
Or may be there's a better way to handle such use case?

This is a good use case and something we should consider better support for in TIP itself.  At the moment, we will store an image to a pipeline and upon completion (and knowing the canonical URL) will save the same image to the new identifier while deleting the old identifier.
I think the addition of a method on the pipeline to simply change the identifier is what you are looking for and would serve your needs (and ours too!).
- (void)changeIdentifierForImageWithIdentifier:(NSString *)currentIdentifier toIdentifier:(NSString *)newIdentifier;

We will consider this for a future drop of TIP.  In the meantime, you should be able to unblock yourself by either using the same pattern we have or by forking TIP to add this method yourself.

This has been merged with v2.4.4 - closing

authors: NSProgrammer agordeev

repo: twitter/ios-twitter-image-pipeline


text:
Fix missing comma (ru)

In the basic page (ru) a comma is missing.
Proof link :smile: (http://orthographia.ru/punctum_uk.php?rid=187)

Got an OK from @egonina.

authors: benpence nerro


text:
Only mark cookies secure for https requests

When using secure_cookies: true over plain http, the cookies are marked as secure and are not served on subsequent requests.
Maybe @stve can add this as part of https://github.com/twitter/secureheaders/pull/238 ?
See https://stackoverflow.com/questions/36447768/unable-to-login-to-my-rails-app-after-implenting-secure-headers-gem-in-my-local#new-answer

That is a really good catch. Feel free to assign this one to me, i'm getting close to finishing my list and can tackle it

authors: oreoshake stve

repo: twitter/secureheaders


text:
BloodHound ignoring TTL on prefetch

We are experiencing an issue with bloodhound's cache, which is not refreshed after the suggested TTL. even at the low settings below:
var users = new Bloodhound({
        datumTokenizer: function(d) {
            return d.tokens;
        },
        queryTokenizer: Bloodhound.tokenizers.whitespace,
        prefetch: 'URL',
        ttl:1
    });

I assume this should refresh the cache after every millisecond. However, it keeps the cache even after several refreshes. There is also no trace of a request to the URL either.

Very nasty solution localStorage.clear(); before typeahead().
Any ideas how to just disable cashe? TTL completely not working.

@justinhomes and others, I know this is a little stale, but numbers like 1393469786476 are timestamps for the time at which the data will be cleared (not the amount of time they'll be saved). So, it's probably working as expected.

I had the same issue, but like @romeoonisim said, first clear the local storage cache because your data is already cached from your previous code. E.g. at first I was testing without TTL. So naturally the cache was set to 1 day. Then I added the TTL of 5 seconds and expected the cache to expire after 5 seconds. Well it won't because the cache is already set to 1 day. You first need to remove the old cached data, and again run your code.
Maybe it is possible to NOT clear the cache and reinitialize bloodhound with bloodhound.initialize(true). Maybe this would work too, haven't tested it, but the first approach is tested and it works.
Regards.

This is what I had to do:

Manually delete the local storage for that page to ensure it's not looking at old data. If Chrome, go to Chrome Developer Tools -> Application -> Clear storage -> click "Clear selected" (I swear I have to click it a few times to make it work). This deletes all site data, so only delete Local storage if you want to keep cookies etc.
Uncheck Chrome Developer Tools -> Network -> "Disable cache".

Docs say "Initialization entails adding the data provided by local and prefetch to the internal search index" so I believe it will check local storage before any of your settings. And if your last settings put data in there with a timestamp, then it will get it.

@andrewevans this solution is fine if you're the only user of the application.

authors: RomkaLTU andrewevans micahlisonbee rash805115 sinaa the911s


text:
Kip-848: Next Generation Consumer Group

I wanted to know what is the plan on implementing KIP-848. I see a dedicated branch just for this, but it's been inactive for a year. @twmb I would be happy to help move it forward.

I have to evaluate what this entails. The branch is stale because I used to implement protocol support before it was rolled out in Kafka, but stopped once Kafka started changing APIs repeatedly before the API was finally released.
I'm not sure 848 is high priority though because it's released as preview only. I'm not sure how hard it'll be to implement, but likely pretty hard...

Yeah I'm probably going to need help with this, this is a big one.

I definitely missed your reply above^.
I'm starting to think about this (a little bit). One thing I may lean to do first is to improve the guts of the consumer so that moving a partition between brokers does not require a full consumer stop/restart -- and then after, implement KIP-848.
Or it may make sense to just start with 848 logic, I'm really not sure -- I haven't dug into it much.

authors: aratz-lasa twmb

repo: twmb/franz-go


text:
bad interpreter

I only get an exception like "bad interpreter"

bash: /usr/bin/snoo: node: Defekter Interpreter: Datei oder Verzeichnis nicht gefunden

What to do?

@Hans-Maulwurf install node >= 7.4.0. :-)

node -v
v7.5.0

that's my output :/

@Hans-Maulwurf just updated something. Could you please git pull / npm i the latest version and try again?

now i get

/usr/bin/env: „node --harmony“: Datei oder Verzeichnis nicht gefunden

Could you run the following command in your terminal?
$ /usr/bin/env node --version
v7.5.0

v7.5.0
using arch linux

I got it working now. It seems it's the way you call node, I changed the first line of cli.js to

#!/usr/bin/node --harmony

and now it's working :)

From what I know #!/usr/bin/env node is the suggested way, as the node binary doesn't necessarily need to be under /usr/bin/. So for users that installed node into e.g. /opt, your solution would not work as well.
I'm really wondering how come that when you run /usr/bin/env node manually it works, but when your shell interprets the shebang statement it apparently can't find it anymore. That's really weird.

authors: Hans-Maulwurf mrusme

repo: twostairs/snoo


text:
Help, why 'no output directory' ?

Why the results are no output directory?
I went to the folder google-hosts-master/scripts/, and then:
$./filter.sh mail.google.com
no output directory.
$./select.sh
no output directory.

You must run ./auto.sh first, this script will create output directory.
$ ./auto.sh
BTW, Don't forget to check Requirements:
https://github.com/txthinking/google-hosts/blob/master/scripts/README.md
On Mon, Apr 20, 2015 at 4:31 PM xujchen notifications@github.com wrote:

Why the results are no output directory?
$./filter.sh mail.google.com
no output directory.
$./select.sh
no output directory.
—
Reply to this email directly or view it on GitHub
https://github.com/txthinking/google-hosts/issues/83.

authors: txthinking xujchen

repo: txthinking/google-hosts


text:
rfc: use exception's Control.Monad.Catch.MonadThrow instead of ExceptT

Most or at least many haskell packages went the way of using MonadThrow instead of typed Exceptions for IO code.
See Michael Snoyberg's essay for a rationale.

Yes! This is definitely on my list of todos.

Before I start doing that, what's your stance on pull #21 (mtl-style API)? I would like to base the work on that pull request.

I'd hold off on doing this until I can get my branch I'm actively developing on pushed up. Then you can work off of that branch since there are so many changes there. I'll try my best to get it pushed up soon!

No hurry! Can you update either bug when it lands?

Yes, no problem.

I haven't had a chance to work on this lately, so I pushed what I have to a branch https://github.com/tylerholien/milena/tree/new-style-groups.
It's in pretty embarrassing shape, but you can work off of that!

authors: ibotty tylerholien

repo: tylerholien/milena


text:
Failed to load: https://cdnjs.cloudflare.com/ajax/libs/tinymce/4.3.7/plugins/bootstrapaccordion/plugin.min.js

Failed to load: https://cdnjs.cloudflare.com/ajax/libs/tinymce/4.3.7/plugins/bootstrapaccordion/plugin.min.js
Did you stop support for plugin ?

I have not looked at this plugin in a while. I wonder why that url is broken now?

Can you please give a glance to your plugin ?

@bantawa04 I'm sorry; I don't have time to maintain this right now. It doesn't seem to be in much use and I don't think it was a good solution in the first place. Feel free to work on it if it can be of use to you though.

Latest version of TinyMCE looks for plugin.min.js
This project uses plugin.js

authors: bantawa04 craigpotter tyleryasaka

repo: tyleryasaka/tinymce-bootstrap-accordion


text:
[enhancement] Add missing bower.json.

Hey, maintainer(s) of typekit/webfontloader!
We at VersionEye are working hard to keep up the quality of the bower's registry.
We just finished our initial analysis of the quality of the Bower.io registry:
7530 - registered packages, 224 of them doesnt exists anymore;
We analysed 7306  existing packages and  1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).
Sadly, your library typekit/webfontloader is one of them.
Can you spare 15 minutes to help us to make Bower better?
Just add a new file bower.json and  change attributes.
{
  "name": "typekit/webfontloader",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.
NB! Please validate your bower.json with jsonlint before commiting your updates.
Thank you!
Timo,
twitter: @versioneye
email: timo@versioneye.com
VersionEye - no more legacy software!

Would be nice to reconsider bower publish

The Web Font Loader is available on NPM, so you don't need bower.

I thought npm was dedicated to node modules only?
Wouldn't this decision make things difficult for users maintaining their web packages through bower?
A case example:
User having

/package.json defining test/build and deployment dependencies in order to generate output directory.
/bower.json defining web app dependencies which will be installed into src/vendor directory

Structure:
.
├── bower.json
├── package.json
├── node_modules
└── src
    └── vendor

Wouldn't this mean that if I also need node-only packages available at node_modules and not under src/vendor I then wouldn't be able to install webfontloader throught npm in this case since it would be installed under node_modules and not src/vendor as with other browser related packages?

+1 for having bower install option.  It's dead simple to add the config and gives developers the ability to leverage whatever package installer they already have setup with their dev ecosystem.  What's the reason to not use bower?

@bramstein I would also appreciate this on bower, I use bower for frontend resources, and, npm for gulp things.
I did once try just using NPM instead of bower, but, I found it very unhelpful. When using NPM only, you can't do any sort of logic in the package.json because it's json.
I do hope you change your mind,
Many thanks

authors: bramstein lexbi timgluz troygrosfield zanona

repo: typekit/webfontloader


text:
NullPointer when trying to use stm-containers library

I am not sure if this ticket belongs here or on eta-hackage,  I decided to put it here.
This package is not on eta-hackage but it compiled just fine.
Attempt to create a map and add data to it causes
Exception in thread "main" eta.runtime.exception.EtaException: JException java.lang.NullPointerException
	at stm_containers.stmcontainers.hamt.Nodes$$wa2.enter(Unknown Source)
	at main.Main$createMap2.enter(Unknown Source)
	at eta.runtime.apply.Function.applyV(Function.java:16)
	at eta.runtime.stm.STM.atomically(STM.java:67)
	at main.Main$main1.enter(Unknown Source)
	at main.Main$DZCmain.enter(Unknown Source)
	at eta.runtime.apply.Function.applyV(Function.java:16)
	at eta.runtime.stg.Closures$EvalLazyIO.enter(Closures.java:96)
	at eta.runtime.stg.Capability.schedule(Capability.java:150)
	at eta.runtime.stg.Capability.scheduleClosure(Capability.java:97)
	at eta.runtime.Runtime.evalLazyIO(Runtime.java:189)
	at eta.runtime.Runtime.main(Runtime.java:182)
	at eta.main.main(Unknown Source)

I have created a trivial example that runs fine with stack and NullPointer-s  with etlas run.
https://github.com/rpeszek/eta-stm-containers

@rpeszek To get the fix, clone master of the repository, run:
> stack install eta-build
> eta-build rts-clean

This will install the runtime fix without you having to reinstall eta.
Love the bug reports, keep them coming! :)

authors: rahulmutt rpeszek

repo: typelead/eta


text:
More speakers, less papers

Another follow-up to #79

:+1:

authors: adelbertc fthomas


text:
Make it impossible to loose data with visual editor

Currently the visual editor has a big problem that drive me nuts:
Here what very often happens in my case:

I edit a paragraph, a table or something else
I want to copy a phrase from another paragraph or table and click there to select the text
The first visual editor will be cancelled and all edits are lost and now the visual editor of the clicked element is openend

There could be different solutions to avoid this:

Leave multiple visual editors open for unsaved/uncanceled content blocks
When the content in a visual editor is edited, lock the editor so that I have to click on save/cancel first before editing another section.
Just treat leaving the editor block as save
Ask the user what to do, when he leaves a editor without saving/canceling

I will investigate it. Vue has the option to keep the data for forms, but it will interfer with the Typemill logic. I suppose the best way is to store changes automatically if block closes and editor did not click the "cancel" button.

Solution 2 is implemented in next release 1.4.0: When the content block is edited in the visual mode, then the editor is locked so that you have to click on save/cancel first before editing another section.
Automatic saving is another option, but I am not sure if all users want that behavior in all situations (you can't cancel and go back to the previous version then).
The downside of the current solution (lock editor) is, that you cannot open another block to copy the markdown. Anyway, in the visual editor the complex markdown (images, tables and similar) is not directly visible, so the use of copy and paste is very limited.

published with version 1.4.0

authors: Tekl trendschau

repo: typemill/typemill


text:
Moving files results in lower case nav titles

Hi,
when doing something like this on command line:
# mv 02-groupware/03-exchange/ .

the nav titles of the 03-exchange folder and articles below change to lower case:

Therefore you have to edit the nav titles on the meta tab to get it back to normal.
EDIT: the same happens if I manually create pages with a text editor.

Yes, I can't guarantee that everything works as expected if you use the file system directly (or an external text-editor) instead of using the author interface. It is probably because the events are missing that update the cache files with additional information like navigation title or hide/not hide. If those information are missing, then it falls back to the titles that are generated from the file-names. You can try to delete the cache files (delete manually or use the button in the admin interface). Does that help?

Sorry, forgot to mention: I've already tried to delete the content of the cache dir. Doesn't make a difference.

Sorry for delay: I just tried it with a live website and ftp, the workflow is the following:

Rename a folder with console or ftp
delete the cache in the settings
go to the frontend website and do a hard refresh (or wait 10 minutes).
Then the navigation in frontend and backend is recreated automatically and the navigation names from meta-settings are there again.

The workflow is not very intuitive, I know, but the use case is not very common, so I do not really want to spend time to improve it. One improvement could be to change the button function from "clear cache" to "recreate cache" but for me it is low prio right now.
Does that help?

Indeed it works that way.

I changed the clear cache functionality to a recreate cache functionality, so the important parts of the cache will work without visiting a frontend page as of version 1.4.9.

authors: thenktor trendschau


text:
Fix https://github.com/typesupply/lasermeasure/issues/39

Minor fix on handle measurements

Thanks!

authors: ryanbugden typesupply

repo: typesupply/lasermeasure


text:
[Question] Implementation following system

These are my data.
{
  "users": [
    { "id": 1, "username": "Alex" },
    { "id": 2, "username": "John" },
    { "id": 3, "username": "Maria" },
    { "id": 4, "username": "Jane" },
    { "id": 5, "username": "Mike" },
    ect...
  ],

  "followers": [
    { "id": 1, "userId": 1, "followerId": 4},
    { "id": 2, "userId": 2, "followerId": 5},
    { "id": 3, "userId": 3, "followerId": 1},
    { "id": 4, "userId": 4, "followerId": 2},
    { "id": 5, "userId": 5, "followerId": 3},
    ect...
  ]
}

How to get the following users and followers?

Read the documentation, it clearly describes how you could go about doing this with _expand and _extend
https://github.com/typicode/json-server#relationships

@northkode I read the docs and I test it. I can get the followers but my problem is how to get following users?

I really dont know what you mean?  If you read the docs you would see that if you have a route called /followers then you need to do what the docs say and do
/followers?_expand=user and it uses the userId to map the users to the follower.

authors: northkode propanto

repo: typicode/json-server


text:
Typings Collaboration

This issue should be used as a reference for package authors.
Summary
We want to improve the TypeScript ecosystem. DefinitelyTyped was great because a lot of people come together to create type definitions, but it quickly becomes unwieldy. Since TypeScript supports typings resolution over package.json and typings supports distributed type definitions, we can better service the community in new ways now. One of these ways is to partner with package authors and help them maintain their own definitions - this helps TypeScript users as there'll be official typings for them, it helps the package author as TypeScript consumers will more likely use their package (and provides users with some awesome type safety and autocompletion) and it provides a better mechanism for distribution.
How?
There's two way we can collaborate with package authors. The preferred is that we can help get type definition inside packages. This means consumers don't even need to install Typings, and things start working immediately after they install a package. The second method is to collaborate with the author in @types, which means consumers will continue to install Typings for now. The least preferred method is what we currently do now, where we contribute independently, unofficially and do not collaborate. The model used is dependent on the package author.
Inside The Package
When a user-facing API change is occurring in your package (E.g. major or minor), ping @typings collaborators and we'll help you update or review the type definitions. If you want a peer review of the type definition, you can also ping us.
Inside Typed Typings
When a user-facing API change is occurring in your package (E.g. major or minor), create an issue on the mirrored package definition in @types and we'll collaborate on updating the type definition. It helps us to have release notes so we can quickly make the relevant changes.
Independently
This is the existing model. The package author has no idea about Typings or TypeScript and a nice contributor has been maintaining the type definition in sync with API changes. Of course, this one is much harder and slower for us to react to changes.
We can also maintain a list of @typings contributors and package names so you'll always know who you can ping for help on updating your package.
Update: Cross-organisation team mentions do not work, I've updated this issue to reflect changes in how it would work without mentions.
P.S. If you would like to help us by contributing, just mention it and we can add you to the team.

Nice but my gut says something is missing.
One idea:
The package author do not really need to ping typings author for changes occurs. The answer is green keeper.
In generated repo, I install the source package as dev dependency. So..... :smirk:

I think would be good if central repository would be still present for foreseeable future, since some authors not very good at maintaining .d.ts files. See https://github.com/mzabriskie/axios as example.
So relying fully on NPM would be idealistically good, but as developer I want to have ability to replace such poisonous definitions. Community maintained central location seems to be good place for me, to help overcome such cases.

@kant2002 I think you're missing the point. It does not matter where the .d.ts files live if they are maintained, so we're proposing to partner with authors to help them with the maintenance. Also, you can always use typings install to install from wherever you want - nothing is changing there.

As working on generator-typings, the typings repo can now link directly to the specific version of the source package. One possible collaboration between the package author and typings author is to produce a set of tests that verify the API.
If the author can have a way to separate API test from functional and unit tests (e.g. name the tests as *.api.js or put them under a specific folder), typings author can import those files over for each release and update the typings accordingly.
That would be a huge time saver for the typings author, and also help guarantee the quality of the typings.
When salsa based validation is available, it would be even better.

@blakeembrey I have contacted some package developers in Meteor/React world, and their are willing to include the typescript definition in their packages.
My questions here are:

So, do they include the ambient definition?

declare module "@kadira/storybook" {
 ...
}

If not, what is the prefered way of defining this in the javascirpt package?

How does Typescript recognise these definitions? The only way I can image this to work, is to include that definition in tsconfig.json in [files] section.

Thanks

@tomitrescak Sorry for the delayed response. It got a little with everything lost this week.

If it's imported, then no. TypeScript definitions for packages need to be in external module format.
Use typings in package.json, check out https://www.typescriptlang.org/docs/handbook/typings-for-npm-packages.html

Thanks for your response. Already added TS in several packages.

I'm unclear on how nested typings are managed within a npm module.
I'm using flickr/yakbak that doesn't have typings. I've written my own typings and now I'd like to publish my changes. The library depends on Node.js and some of my typings depends on Node.js too.
If I manage to convince flickr to integrate my changes in their repo, how do I manage the nested Node.js dependency for typings? with a typings.json? Is there any example you could link me too?

You should use a typings.json with the npm: module resolution.
main-project/typings.json
{
  "dependencies": {
    "flickr": "npm:flickr"
  }
}

This will tell typings to look into node_modules/flickr, search for a typings.json (or index.d.ts) inside.

@danielepolencic You can look at any of the dependencies of Typings. For example, it depends on typings-core which depends on popsicle which depends on a bunch of files in typings.json. The ideal pattern, however, is to get the modules to contain native .d.ts files - but when needed, you can work around it using Typings resolution.

I've publish a plugin to NPM (aurelia-http-utils) with its package.json/typings and typings.json. Can I install it with typings install aurelia-http-utils? Or do I need to PR this registry every time I publish a new version to NPM?

@heruan Nope, you never need to add it to the registry. If it's usable with typings.json, TypeScript can pick it up automatically (the package.json/typings field). If it's not, you can install it using Typings by doing typings install npm:<pkg>.

@blakeembrey What you say is only true if the user is using NPM as the package manager. If the user is using e.g. JSPM and has installed the package from NPM, TypeScript won't pick it up automatically. What is the solution to that problem? Can we somehow use typings to download the typings from those NPM modules?

Yes.

@niieani working on typings install jspm:<pkg> right now. Welcome to join the discussion:
https://github.com/typings/core/issues/116
In the meantime, the old trick is to double install. Install it from jspm and also to npm

@unional JSPM typings support will be great, I just wonder: if having the typings entry in packages.json would make the use of typings.json not necessary with NPM, shouldn't it be the same for JSPM? It would be quite confusing otherwise.

Sorry, don't understand what you mean by typings in package.json would make use of typings.json...

Trying to figure out whether I can include global tyings insdie the npm package that publishes the global scripts (option 5 from the example page).
Can someone point me in the right direction?
I also posted my question over at typings/discussions but not sure whether that was the right place or here.

@blakeembrey How can i integrate typings for Nightwatchjs in typed typings for external consumption ?https://github.com/rkavalap/NightWatchTest/blob/master/typings/nightwatch/nightwatch.d.ts

@rkavalap You can create a new repo for them, which can be moved to @typed-typings once it's ready. There's some documentation for creating the repo in the README, and once that done I'd be happy to add you to @typed-typings so you can move it.

@blakeembrey Here is the link just for the type definitions. https://github.com/rkavalap/npm-nightwatch. Let me know if there is something i need to change or missed.

issue added:
https://github.com/rkavalap/npm-nightwatch/issues/1

@rkavalap If you want to add me to the repo, I can transfer it to @types for you. Or I can also add you to the organisation.

@blakeembrey, @unional  I just invited you guys to my repo as a collaborators.

@rkavalap Just wanted to check, but you do understand that you can contribute the type definitions without them being in @types? The useful of being a collaborator is limited, since I can't actually move the repo without admin access. Instead, I'll add you to @types and you can choose to move it. I just wanted to make sure someone would be there to maintain it (E.g. you).

@blakeembrey I re-read your initial post on this issue and the README of this project. I initially misunderstood them. Yes, I understand that I could still have contributed to the type definitions without them being @types. In that scenario, I would be the only contributor, unless there were additional collaborators to my repo. My repo would be consumed by github url present in typings.json for typings to install. Or I publish this as an npm package to npm registry
Several things have happened from your initial post on the issue to my current writing, and it was confusing. A lot of the project README's and issues revolving under @typings and @types have a reference to typed-typings. I believe typed-typings was renamed to @types
So i am trying to understand what's the added advantage, other than the eyes of all the @types members for any issues created on these repositories ? or new type definitions requests
On a consumer aspect, anyone who is not familiar with typings, requires to understand all different ways of acquiring type definitions. It's not very clear on the README on how a consumer can consume as well as how a contributor needs to communicate for his type definitions to be consumed by typings.

@rkavalap Please check the README of the project. It's pretty well documented, but if there's something missing please open a PR. See https://github.com/typings/typings#usage which links to the registry which has contributing docs (https://github.com/typings/registry#contributing).
There's no major advantage to moving it to @types other than the rest of the community can help maintain it in a case where someone goes offline. It's useful for more common type definitions, less so with yours, which is why I didn't push to add it to @types - I assumed you'd read the issue you were commenting in and were asking to be added to it.
The @typed-typings rename only occurred a week ago (https://github.com/typings/registry/commit/93ead745b013e997af21d28fee22e8af6c3e6773), I'll update the issue description to mirror this.

@rkavalap Also note this issue is intended for package authors, as mentioned at the very beginning:

This issue should be used as a reference for package authors.

Because of this, the options are provided in the context of how Typings can collaborate with a package author - not how contributors can contribute their type definitions, which is documented in the Typings registry and the registry is mentioned in a few places documenting how the project works.

authors: blakeembrey christianacca danielepolencic demurgos heruan kant2002 niieani rkavalap tomitrescak unional

repo: typings/typings


text:
touying:0.5.0 and touying-aqua:0.5.0

I am submitting

[ ] a new package
[x] an update for a package

Description:
This is a significant disruptive version update. Touying has removed many mistakes that resulted from incorrect decisions. We have redesigned numerous features. The goal of this version is to make Touying more user-friendly, more flexible, and more powerful.
Major changes include:

Avoiding closures and OOP syntax, which makes Touying's configuration simpler and allows for the use of document comments to provide more auto-completion information for the slide function.

The existing #let slide(self: none, ..args) = { .. } is now #let slide(..args) = touying-slide-wrapper(self => { .. }), where self is automatically injected.
We can use config-xxx syntax to configure Touying, for example, #show: university-theme.with(aspect-ratio: "16-9", config-colors(primary: blue)).

The touying-slide function no longer includes parameters like section, subsection, and title. These will be automatically inserted into the slide as invisible level 1, 2, or 3 headings via self.headings (controlled by the slide-level configuration).

We can leverage the powerful headings provided by Typst to support numbering, outlines, and bookmarks.
Headings within the #slide[= XXX] function will be adjusted to level slide-level + 1 using the offset parameter.
We can use labels on headings to control many aspects, such as supporting  the <touying:hidden> and other special labels, implementing short headings, or recalling a slide with #touying-recall().

Touying now supports the normal use of set and show rules at any position, without requiring them to be in specific locations.

A simple usage example is shown below, and more examples can be found in the examples directory:
#import "@preview/touying:0.5.0": *
#import themes.university: *

#show: university-theme.with(
  aspect-ratio: "16-9",
  config-info(
    title: [Title],
    subtitle: [Subtitle],
    author: [Authors],
    date: datetime.today(),
    institution: [Institution],
    logo: emoji.school,
  ),
)

#set heading(numbering: "1.1")

#title-slide()

= The Section

== Slide Title

#lorem(40)

Theme Migration Guide:
For detailed changes to specific themes, you can refer to the themes directory. Generally, if you want to migrate an existing theme, you should:

Rename the register function to xxx-theme and remove the self parameter.
Add a show: touying-slides.with(..) configuration.

Change self.methods.colors to config-colors(primary: rgb("#xxxxxx")).
Change self.page-args to config-page().
Change self.methods.slide = slide to config-methods(slide: slide).
Change self.methods.new-section-slide = new-section-slide to config-methods(new-section-slide: new-section-slide).
Change private theme variables like self.xxx-footer to config-store(footer: [..]), which you can access through self.store.footer.
Move the configuration of headers and footers into the slide function rather than in the xxx-theme function.
You can directly use set or show rules in xxx-theme or configure them through config-methods(init: (self: none, body) => { .. }) to fully utilize the self parameter.

For states.current-section-with-numbering, you can use utils.display-current-heading(level: 1) instead.

If you only need the previous heading regardless of whether it is a section or a subsection, use utils.display-current-heading().

The alert function can be replaced with config-methods(alert: utils.alert-with-primary-color).
The touying-outline() function is no longer needed; you can use components.adaptive-columns(outline()) instead. Consider using components.progressive-outline() or components.custom-progressive-outline().
Replace states.slide-counter.display() + " / " + states.last-slide-number with context utils.slide-counter.display() + " / " + utils.last-slide-number. That is, we no longer use states but utils.
Remove the slides function; we no longer need this function. Instead of implicitly injecting title-slide(), explicitly use #title-slide(). If necessary, consider adding it in the xxx-theme function.
Change #let slide(self: none, ..args) = { .. } to #let slide(..args) = touying-slide-wrapper(self => { .. }), where self is automatically injected.

Change specific parameter configurations to self = utils.merge-dicts(self, config-page(fill: self.colors.neutral-lightest)).
Remove self = utils.empty-page(self) and use config-common(freeze-slide-counter: true) and config-page(margin: 0em) instead.
Change (self.methods.touying-slide)() to touying-slide().

You can insert visible headings into slides by configuring config-common(subslide-preamble: self => text(1.2em, weight: "bold", utils.display-current-heading(depth: self.slide-level))).
Finally, don't forget to add document comments to your functions so your users can get better auto-completion hints, especially when using the Tinymist plugin.

Other Changes:

theme(stargazer): new stargazer theme modified from Coekjan/touying-buaa.
feat: implemented fake frozen states support, allowing you to use numbering and #pause normally. This behavior can be controlled with enable-frozen-states-and-counters, frozen-states, and frozen-counters in config-common().
feat: implemented label-only-on-last-subslide functionality to prevent non-unique label warnings when working with @equation and @figure in conjunction with #pause animations.
feat: added the touying-recall(<label>) function to replay a specific slide.
feat: implemented nontight-list-enum-and-terms, which defaults to true and forces list, enum, and terms to have their tight parameter set to false. You can control spacing size with #set list(spacing: 1em).
feat: replaced list with terms implementation to achieve align-list-marker-with-baseline, which is off by default.
feat: implemented scale-list-items, scaling list items by a factor, e.g., scale-list-items: 0.8 scales list items by 0.8.
feat: supported direct use of #pause and #meanwhile in math expressions, such as $x + pause y$.
feat: provided #pause and #meanwhile support for most layout functions, such as grid and table.
feat: added #show: appendix support, essentially equivalent to #show: touying-set-config.with((appendix: true)).
feat: Introduced special labels <touying:hidden>, <touying:unnumbered>, <touying:unoutlined>, <touying:unbookmarked> to simplify control over heading behavior.
feat: added basic utils.short-heading support to display short headings using labels, such as displaying <sec:my-section> as "My Section".
feat: added #components.adaptive-columns() to achieve adaptive columns that span a page, typically used with the outline() function.
feat: added #show: magic.bibliography-as-footnote.with(bibliography("ref.bib")) to display the bibliography in footnotes.
feat: added components like custom-progressive-outline, mini-slides.
feat: removed touying-outline(), which can be directly replaced with outline().
fix: replaced potentially incompatible code, such as type(s) == "string" and locate(loc => { .. }).
fix: Fixed some bugs.

Nice!

repo: typst/packages


text:
Add auto option for page headers/footers

See #3938.
none now suppresses the header or footer altogether.

I simplified it a bit by getting rid of all the Cows that weren't necessary anymore. It was easier to just do than to review since I wasn't sure whether it would work out. Thanks for the PR!

repo: typst/typst


text:
Provisioning over Access point

Hello,
does this library support an WiFi access point mode in which we can connect to the chip to provision it over a website?
(configure the local WiFi the chip should connect to, to connect to the internet)
We are currently using the WGM160 from silabs which provide such a functionality, but want to change chips.
On the ublox website I couldn't find much information how one provides a build-in webpage within the host MCU.
Maybe you have some more insight?
Best regards

Hi Alexander,
We have planned for this but it will not make it for the coming 1.2 release.
I could however provide you with a prototype version as soon as I have something, if you want to help out testing it.
BR
/Peter

Hi plerup,
thank you for the information! After a bit of digging deeper, I realized I might be in the wrong library.
Is this the library for the openCPU or u-connect version?
We would like to use the u-connect version of the NINA chip (w15) and connect an external host MCU.
When running the NINA chip in access point mode, connect an external device and provide a website from the NINA/MCU setup to the user.
If this is the correct version for this use case, will there be a webpage template/example on how to connect the requests by the website to the host MCU?
Best regards

Well, ubxlib handles (to some extent) both opencpu and u-connect. The planned first implementation of WiFi access point in ubxlib is by using u-connect from a host cpu as you describe.
We currently have no web-server example but that is a good idea to include as part of this functionality.
BR
/Peter

Alright, that is good news!
I would be interested in any pre-release when you are ready or if you need a tester's feedback as we are currently in the preparation for a new project that will start in the next months in which we would use the chip in the setup described above.
Best regards
Alex

@plerup Due to some planning changes, we are currently fast tracking our project. And would begin development next week.
I would like to take you up on your offer for a preview version, if that is available?
Best regards

@AlexanderZender
Hi, I'm working on it, but nothing usable just yet. The main challenge is to implement a tcp server in ubxlib. That has never been done before. I assume that you need that in order to access the AP once it's started, i.e. i small webserver for provisioning of WiFi credentials.
Maybe some very alfa version could be available next week. I will keep you posted.
BR
/Peter

@plerup
Hey,
yes, that is correct that is an important feature, but we also need to get familiar with the library first.
That sounds fantastic! Whenever you think you are ready we would be happy to give it a spine. And provide you with feedback.
As a side question, is this library only compatible with RTOS systems or could we also use it with bare metal chips?
Thank you

No, an RTOS is required, either FreeRTOS or Zephyr

Thank you for the info,
At the moment we are going bare metal so, do you have someone in the team that could be asked about AT commands?
I encountering an ERROR but I cant figure out whats the problem.

Hi @AlexanderZender: some questions for clarification:

You say "bare metal": ubxlib does need an RTOS, for tasks/queues/mutexes; I guess you mean that you have an RTOS environment of your own which you are now porting ubxlib to, following the DIY instructions.  Is that correct?
Can you explain the sequence you are following that results in the error; e.g. an idea of the sequence of uPort/uDevice/uNetwork etc. API calls you are making, the kind of thing you see in our examples, and maybe a .txt file log of the AT exchanges?

Hey @RobMeades,
by bare metal I mean we are implementing the AT commands by hand, as there is no underlying OS.
But one AT command does not work as expected and we cant find the issue.
If you want I can explain it here

It is possible that I'm misunderstanding here, please bare with me:

@plerup is creating code inside ubxlib which will allow a user of ubxlib to tell a u-blox WiFi module to be a WiFi access point that can serve a simple web page to an attached WiFi client,
this code will be "ubxlib code", and so will rely on RTOS features (tasks, queues and mutexes) like the rest of ubxlib,
is it your plan to somehow make use of what Peter delivers, but without an RTOS?
if not, can you indicate how Peter's delivery will be of use to you?

Apologies if this is all a bit deliberate/stupid, I just have a feeling there's a misunderstanding and would like to get to the bottom of it so that I can help.

Thank you, sure. I will send you an email describing the problem tomorrow if that is alright.
Also can you share your email?

rob.meades@u-blox.com

This feature is now published, see https://github.com/u-blox/ubxlib/releases/tag/v1.3.0 and the example here: https://github.com/u-blox/ubxlib_examples_xplr_iot/tree/master/examples/captive_portal (though you will need to update the ubxlib submodule of that repo to point to the latest ubxlib to bring in the functionality).
Closing this issue: please re-open, or start a new one, if you have further issues.

authors: AlexanderZender RobMeades plerup

repo: u-blox/ubxlib


text:
Move Add User Functionality Over to a Non-Setup Handler

This allows admins to come back and add more users after setup. Previously we blocked them based on whether or not they already had any users. That is now removed. To make this more obvious, after the setup flow the admin is redirected over to the add users handler. That handler can now be accessed from the landing page so if the admin wants to add more users later, the admin can just click the button on the landing page.
Additionally, this joins the group add functionality in with the previous domain add functionality so that admins can find users based on group key or just showing all of the ones in their domain. From that point, the admin still has the option of selecting which ones to actually add (by checking the box next to the user).
So now an entire group, a subset of a group, an entire domain, a subset of a domain, or any combination thereof can be added at any time. Finally, adding the same user from the domain or a group will not generate multiple instances of the same user. It simply generates a new public/private key pair for the existing user. We can change this later if we don't want this operation to impact existing users (in case an admin accidentally adds a person who is already authorized), but I don't think it will actually be much of a problem.

:+1: Looks good to me!

authors: blueandgold xwsxethan

repo: uProxy/ufo-management-server


text:
socksEcho tests failing on Mac

I'm seeing 2 failed tests in socksEcho:

These tests (e.g. https://github.com/uProxy/uproxy/blob/master/src/lib/integration-tests/socks-echo/base-spec.core-env.ts#L276) are also a little weird because they are written in a way where the test can pass regardless of whether testModule.connect fulfills or rejects.  Maybe we want to remove the code with "This code should not run" comments?

I'll take a look at this before next week's release cycle starts up.

So, on my system, If I disable these two tests then all is well:

connect to many different servers in parallel
attempt to connect to a nonexistent DNS name with reproxy

Neither seems extremely important so I'll send a PR and perhaps @bemasc can have a go at investigating.

authors: dborkan trevj

repo: uProxy/uproxy


text:
Having AbstractNetwork.error in the getter side console

Google Chrome	41.0.2272.53 (Official Build) beta
Revision	4c4528cbe3422e85c1837d4be92e71e8cb205748-refs/branch-heads/2272@{#257}
OS	Linux
Blink	537.36 (@189927)
JavaScript	V8 4.1.0.15
Flash	16.0.0.305
it was easy to reproduce happens couple of times .
after proxying a while , I see the followings in red in in the getter's console. also the newtwork was broken .
!!! [Google] Firewall: invalid client state: {"userId":"0luso2mf1bcpf0ej8po9jbnq5j@public.talk.google.com","clientId":"0luso2mf1bcpf0ej8po9jbnq5j@public.talk.google.com/uproxy792A6BCC","lastUpdated":1424462552634,"lastSeen":1424462552634}scripts/social.js:126 AbstractNetwork.error

 !!! [Google] Firewall: invalid incoming message: {"from":{"userId":"0luso2mf1bcpf0ej8po9jbnq5j@public.talk.google.com","clientId":"0luso2mf1bcpf0ej8po9jbnq5j@public.talk.google.com/uproxy792A6BCC","lastUpdated":1424462552634,"lastSeen":1424462552634},"message":"{\"type\":3000,\"data\":{\"handshake\":{\"instanceId\":\"3cb0bfd7be8c49d226d4c451d82a4dff23347270\",\"keyHash\":\"\",\"description\":\"\"},\"consent\":null}}"}scripts/social.js:126 AbstractNetwork.error

also adding a screenshot

another one

Hmm, I think @mollyling was looking at this at one point.

Dup of https://github.com/uProxy/uproxy/issues/892

authors: iislucas klazizpro trevj


text:
use workers

fix #1387.

:+1:

authors: iislucas willscott


text:
Update version number to 0.5.3.

ran grunt test

:+1:

authors: dborkan lucyhe


text:
Memory issue

Hi, I'm getting massive memory usage when connecting more clients than the maximum number of open files (ulimit -n) (1024 by default).
These are the steps to reproduce:
Compile the uWS.cpp and throughput.cpp in the benchmark folder
Run the uWS server, then connect more than (ulimit -n) clients with the throughput tool.
Watch as the 'Connections:' counter gets stuck (memory still normal)
Now connect another client, I did this with chrome:
u = new WebSocket("ws://localhost:3000");
Memory usage should start to increase very quickly.
I'm using the v0.7.8/v0.7.9 release and GCC 5.4.0

What OS is this on?

Obviously this is Linux, I need to sleep.

Well this is kind of obvious. Just look in Server.cpp, Server::acceptHandler. I return when accept fail after allocating a new uv_poll_t. So this will just loop forever. That return should be something else.

This diff fixes the memory leak, I will apply it after finishing up merging the client support. You could apply this yourself in the mean time.
diff --git a/src/Server.cpp b/src/Server.cpp
index c848450..114d284 100644
--- a/src/Server.cpp
+++ b/src/Server.cpp
@@ -37,9 +37,8 @@ void Server::acceptHandler(uv_poll_t *p, int status, int events)
     socklen_t listenAddrLength = sizeof(sockaddr_in);
     uv_os_sock_t serverFd;
     uv_fileno((uv_handle_t *) p, (uv_os_fd_t *) &serverFd);
-    uv_poll_t *clientPoll = new uv_poll_t;
     uv_os_sock_t clientFd = accept(serverFd, (sockaddr *) &server->listenAddr, &listenAddrLength);
-    if (uv_poll_init_socket(server->loop, clientPoll, clientFd)) {
+    if (clientFd == INVALID_SOCKET) {
         return;
     }

@@ -54,6 +53,8 @@ void Server::acceptHandler(uv_poll_t *p, int status, int events)
         SSL_set_accept_state((SSL *) ssl);
     }

+    uv_poll_t *clientPoll = new uv_poll_t;
+    uv_poll_init_socket(server->loop, clientPoll, clientFd);
     new HTTPSocket(clientPoll, server, ssl);
 }

Awesome, it works. Thanks.

authors: alexhultman nagalun

repo: uWebSockets/uWebSockets


text:
🛑 guaca-soc is down

In 409d687, guaca-soc (https://aules.ccss.uab.cat/guacamole/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: guaca-soc is back up in a3d8e53.

repo: uab-dtic/guacamole-uab-monitoring


text:
Configure database logging

PostgreSQL audit logs should be enabled.

Sung documented here: https://confluence.it.ubc.ca/pages/viewpage.action?pageId=358484623
IEC documentation for pgAudit on RDS:
https://confluence.it.ubc.ca/display/IEC/2021-10-27+IEC-13153+Enable+pgaudit+on+PostgreSQL+PRD+Databases
https://confluence.it.ubc.ca/display/IEC/8.5.3.44+Installation+step+and+use+of+pgaudit+extension+to+audit+Amazon+RDS+DB+instance


text:
Commenting out comparing revisions

This is causing more issues than help. Commenting out for the time being.

@Pawka this is again something very specific to SQ. So merging as this is causing a major problem.

repo: uber/arcanist


text:
Upgrade Golang base image to 1.18 to remediate CVEs

What changed?
Fix #5034 by bumping golang base images to golang:1.18.8-alpine3.15.

Why?
To remediate go-related CVEs of Cadence Server.

How did you test it?
# checkout to master
git checkout master
git pull

# build server image
docker build . -f Dockerfile -t ubercadence/server:master --build-arg TARGET=server

# scan with any vulnerability scanner
/usr/local/bin/twistcli images scan --details ubercadence/server:master

Scan results after (remaining unfixed CVEs):

Fixes:

CVE-2022-41715 (high)
CVE-2022-2880 (high)
CVE-2022-2879 (high)
CVE-2022-27664 (high)
CVE-2022-41716 (medium)

Not fix:

CVE-2022-42915 (critical)
CVE-2022-42916 (high)
CVE-2022-35252 (low)
CVE-2022-32221 (low)

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018507a8-4fd3-40a3-a70e-cc7a16e254bd

0 of 0   changed or added relevant lines in 0 files are covered.
99 unchanged lines in 16 files lost coverage.
Overall coverage increased (+0.01%) to 57.288%

Files with Coverage Reduction
New Missed Lines
%

common/task/weightedRoundRobinTaskScheduler.go
1
89.64%

common/util.go
2
52.84%

service/history/execution/mutable_state_util.go
2
36.04%

service/matching/matchingEngine.go
2
71.83%

common/cache/lru.go
3
90.73%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
60.0%

service/history/queue/timer_gate.go
3
95.83%

service/history/task/fetcher.go
3
91.75%

common/persistence/serialization/parser.go
4
63.91%

common/persistence/serialization/thrift_decoder.go
4
57.14%

Totals

Change from base Build 0185076a-a7d3-446a-abf6-9f10967bec17:
0.01%

Covered Lines:
85206

Relevant Lines:
148734

💛  - Coveralls

repo: uber/cadence


text:
minor mutable-state log fix

What changed?
Some reasonable feedback on a diff I didn't address before autolanding, so landing here. Just making the logs both slightly more defensive and returning early where possible.

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018e2f31-f624-46df-bca7-f24f826c6a82
Details

9 of 15 (60.0%)  changed or added relevant lines in 1 file are covered.
49 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.02%) to 64.1%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/history/execution/mutable_state_builder.go
9
15
60.0%

Files with Coverage Reduction
New Missed Lines
%

service/history/task/transfer_standby_task_executor.go
2
87.01%

common/persistence/sql/sqlplugin/postgres/task.go
2
73.4%

common/persistence/sql/sqlplugin/postgres/db.go
2
80.0%

service/matching/taskListManager.go
2
79.7%

service/history/queue/timer_queue_processor_base.go
3
77.82%

common/persistence/statsComputer.go
3
94.64%

service/frontend/wrappers/metered/metered.go
4
65.5%

service/history/execution/mutable_state_task_refresher.go
7
66.46%

service/history/execution/mutable_state_builder.go
12
70.3%

common/persistence/sql/workflow_state_maps.go
12
81.25%

Totals

Change from base Build 018e2ebe-807b-4e78-97fa-f22e8f0a52db:
0.02%

Covered Lines:
93452

Relevant Lines:
145791

💛  - Coveralls

authors: coveralls davidporter-id-au


text:
Apply replication history events to passive cluster

Created history replicator which is invoked by the replicator for
processing of history replication tasks.  It processes the history
events from the replication task and make mutable state updates for each
event.  Once all events are processed it commits the entire update using
the workflowContext API used by rest of the stack.
Also mutableStateBuilder changes to apply mutable state changes using
the actual event.  This required some refactoring of mutableStateBuilder
to reuse as much code as possible between replicator and rest of the
stack.
History service has new API ReplicateEvents which is called by the
replicator to apply history events.
Current this change only works for the happy case and is not guarded by
version updates on the domain.
Replicator does not support out of order processing of history
replication tasks.

Coverage decreased (-0.7%) to 62.417% when pulling 58055897347c3de698e144cd7283703403faf42f on samarabbas:xdc-replication-protocol into 3e3e2fcef759ee67edcd870c69d55bddcadbcc28 on uber:master.

authors: coveralls samarabbas


text:
Performance on large amounts of data

Hello!
I'm attempting to train a relatively simple transformer model on a large amount of data (35m rows, 20 features). The data have been materialized as parquet, where each column is an array of size ~30. These are just small enough that with some manipulation I can fit them into a pandas data frame and keep that in memory, but I'd like to be able to train on larger datasets -- and more workers -- in the future.
At least with my naive use of petastorm, it appears that throughput is quite low. Simply iterating over a petastorm.pytorch.DataLoader can take hours, timings which make my use case somewhat intractable. Changing the worker type or number of workers did not seem to make things better or worse.
I'm materializing the dataset this way:
import numpy as np

from petastorm.etl.dataset_metadata import materialize_dataset
from petastorm.codecs import NdarrayCodec
from petastorm.unischema import Unischema, UnischemaField

train_path = f"{base_path}/train"

fields = [
    UnischemaField(
        column,
        np.float32,
        (encoder_length if column.endswith("encoder") else decoder_length,),
        NdarrayCodec(),
        False,
    )
    for column in data_result.data_train.columns
]

schema = Unischema("schema", fields)

with materialize_dataset(spark, train_path, schema):
    data_result.data_train.write.mode("overwrite").parquet(train_path)

And reading it this way:
from petastorm.pytorch import DataLoader

train_reader = make_batch_reader(
    train_path,
    num_epochs=None,
    # reader_pool_type="process",
    # workers_count=15,
    # cur_shard=hvd.rank(),
    # shard_count=hvd.size(),
)

with DataLoader(train_reader, batch_size=batch_size) as train_dataloader:
    train_dataloader_iter = iter(train_dataloader)

    for _ in range(steps_per_epoch):
        batch = next(train_dataloader_iter)

Any hints as to what I can do to improve throughput? Some option or technique I might be missing? Using BatchedDataLoader instead of DataLoader did help substantially, but I'm running into possibly memory-related errors when using that with Horovod (any insight into that would also be appreciated -- unfortunately Databricks doesn't give me much information other than telling me the process has died).

Is it possible to use a plain parquet store (do not serialize it with materialize_dataset and unischema)? It works well with large numpy arrays, but with relatively small data, the overhead of numpy serialization overhead would be too noticable.
Using make_batch_reader is the right way to go, as it will read entire row-groups in one go and deliver data to you doing minimal processing.
I'd try benchmarking for batch in train_reader, since that's what BatchDataLoader is using underneath. If iterating over train_reader is slow, there is no chance BatchDataLoader will do better.
If you can provide a runnable snippet with some mocked data that I could run "out-of-the-box", I should be able to help you get the optimal throughput.

repo: uber/petastorm


text:
Support simple iarange in ADVI; fix a shape bug

This fixes some site shapes and adds support for (non-subsampled) iarange in ADVI. This also adds a dependency on contextlib for ExitStack (backported from Python3's contextlib).
Even after this PR our ADVI implementation handles only a small class of models:

no handling of subsampling
no handling of irange
no handling of discrete latent variables

Tested

added some cheap tests in tests/infer/test_advi.py
ran a time series model with various shapes (works after this PR, failed before)

Ready to merge as soon as tests pass.

repo: uber/pyro


text:
Hint position when charts used in grid systems

I've had issues with integration of Hint component for the Sunburst element, especially when I try to implement charts/graphs within Grid. The Hint are displayed, and the behavior is really weird.
Hints on the left, are most of time well displayed,
Hints on the right are display way out the range on right.
Are there any solutions to have the Hint component targeted to a specific area so it doesn't overflow the view?

Hey @dbrrt, I think i know what you are saying, but would you mind posting some pics if possible?

Assuming that I'm using a grid system, native or not. This is the behavior of my Hint components nested in Sunburst component (the black rectangles are enabled dinctinctly, when I'm hovering the corresponding the area of the sunburst).

I followed step by step the Sunburst example from this repo : https://github.com/uber/react-vis/blob/master/showcase/sunbursts/sunburst-with-tooltips.js

I have exact same issue

I stumbled into the same issue, even without grid layout.

@torioLuz What do you mean by I didn't import the css file correctly?
How did you import the style from react-vis?

@dbrrt I didn't imply you didn't. I was referring to my own case and what caused the issue.
If you think this also applies to you, then to your question:

The easiest way is just to include a link tag in your html file.

Or, in my particular case, since I'm using LESS, I just used an import statement.
@import "../../node_modules/react-vis/dist/style.css"; (depends on your directory)

@torioLuz Thanks for your response, I'm importing the styles directly in my app. I'll give a try to this way to import react-vis assets.

The key to this issue is that the parent element of the <Hint> component must be position: relative so they can absolutely position correctly.
I'm manually doing the styles via CSS-in-JS so I too had the problem.

@SimeonC thanks, I'll test it

I found this behavior with the example as well and then randomly I thought to try just changing this:
    x: radius * Math.cos(truedAngle),
    y: radius * Math.sin(truedAngle)

to this (switching the x and y calcs):
    y: radius * Math.cos(truedAngle),
    x: radius * Math.sin(truedAngle)

authors: SimeonC dbrrt mcnuttandrew robwise smilexu torioLuz

repo: uber/react-vis