Imports inside .css.ts files produce an error (Next Js)

Describe the bug
At least on Next 13, some imports inside .css.ts files produce the following error:
NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: $RefreshReg$ is not defined
This is triggered when the file containing the thing you import IS or EXPORTS a .tsx file that exports a function which has a name in PascalCase.
Codesandbox instructions: go to the styles/test.css.ts file and comment / uncomment the imports in order.
Some examples available in the codesandbox:
// problem.tsx

export const PascalCaseFunction = () => {
  console.log(":/");
};

// test.css.ts

import { PascalCaseFunction } from "./problem"

PascalCaseFunction() // error

// works.tsx

export const camelCaseFunction = () => {
  console.log("WORKS");
};

// test.css.ts

import { camelCaseFunction } from "./works"

camelCaseFunction () // works

// multiple_exports.tsx

export * from "./problem";
export * from "./works";

// test.css.ts

import { camelCaseFunction } from "./multiple_exports"

camelCaseFunction () // error (because multiple_exports also exports the PascalCaseFunction)

Not lying, I had a pretty hard testing / debugging time on this one, that's not obvious at all :p
Reproduction
https://codesandbox.io/p/sandbox/agitated-ride-g44g7r
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (8) x64 12th Gen Intel(R) Core(TM) i7-12700K
    Memory: 8.07 GB / 15.62 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 16.19.1 - /usr/local/bin/node
    Yarn: 3.3.1 - /usr/local/bin/yarn
    npm: 8.19.3 - /usr/local/bin/npm

Used Package Manager
npm
Logs
(in the terminal of course)

NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: $RefreshReg$ is not defined
Import trace for requested module:
./styles/test.css.ts

### Validations

- [X] Check that there isn't [already an issue](https://github.com/vanilla-extract-css/vanilla-extract/issues) that reports the same bug to avoid creating a duplicate.
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

This seems like an issue with React Fast Refresh, specifically the Webpack plugin which Next.js uses: https://github.com/vercel/next.js/blob/canary/packages/react-refresh-utils/ReactRefreshWebpackPlugin.ts
There's no documentation for that plugin as far as I'm aware, but we can look at another popular Webpack plugin to figure out what's going on: https://github.com/pmmmwh/react-refresh-webpack-plugin/blob/main/docs/TROUBLESHOOTING.md#usage-with-indirection-like-workers-and-js-templates
So it looks like what's happening here is your .css.ts files imports [something that Babel thinks is] a React component and the instrumented code doesn't find the $RefreshReg$ function it expected to be there.
TL;DR: It's better to have your .css.ts files be leaf nodes in your dependency tree i.e. import from not into styles/test.css.ts. If you need to import constants or simple values into your .css.ts files, make sure they're leaf nodes as well.

Thank you for your quick answer!
In my specific case, the file I was trying to import contained a simple object with string values, but was exported from a barrel file alongside other things, some of those were React components.
They (the React components) were not imported into the .css.ts file, but by just being exported from the same file as my import was causing the error. I know, there is a lot of "import / export" in these sentences, it can be confusing (case 3 from my issue, the multiple_exports.ts).
Anyway, I splitted this barrel file in two, components / non-components, and now every thing works fine :)
Maybe this kind of issues should be documented somewhere? The first time you encounter this error, you don't really know where to look at, especially because you don't directly import the things that cause problems (the React components).

Hi @toyi do you have a sample repo to take a look, trying to solve similar issue

Unfortunately I don't have a sample repo available, I just have the codesandbox provided in the issue, but that should do it.
The solution (or should I say "workaround") was to ensure the file you are importing into the .css.ts comes from a file that doesn't export anything that IS or MIGHT BE MISTAKEN FOR a React component.
Take a look at the sandbox, you have multiple examples of working / not working cases.
The main idea is to not import anything that (is a function|is exported alongside other elements that are functions) starting with a capital letter.

@toyi Thanks a lot, I think your investigation saved me from a ton of lost time doing it myself. I have the exact same scenario with Next13.
Monorepo where one package is "ui" library implemented with vanilla extract and all of the components and helper functions are exported via one index file.
Then in my .css.ts file in Next13 app inside the monorepo I was importing a helper function (which is just a normal function sitting in a .ts file in ui lib) like import {helperFunctionName} from 'ui' and I was getting this weird error.
Changing the import to the exact path like import {helperFunctionName} from 'ui/styles/helperFunctionFile' fixed the error -_-

Importing directly from .css.ts helped

@shelooks16 thanks for that, works like a charm

Hello any feedback on this yet or can anyone help with this, I am facing this issue and tried some solutions here, but nothing this is how my files look

Hello any feedback on this yet or can anyone help with this, I am facing this issue and tried some solutions here, but nothing this is how my files look

Is anything other than vars being exports from that theme file?

Hello any feedback on this yet or can anyone help with this

Is anything other than vars being exported from that theme file?

Hey So all it export is something like this

Hello any feedback on this yet or can anyone help with this

Is anything other than vars being exported from that theme file?

Hey So all it export is something like this

Hmm ok. I wonder if the issue is @mantine/core? It's exporting components and utilities. What happens if you remove the rem import from that .css.ts file?

Hello any feedback on this yet or can anyone help with this

Is anything other than vars being exported from that theme file?

Hey So all it export is something like this

Hmm ok. I wonder if the issue is @mantine/core? It's exporting components and utilities. What happens if you remove the rem import from Welcome.css.ts file?

Still the same issue I have a demo repo here link .  the odd part is I am using next13 with the pages dir and this happens however if I use the app dir it works fine

So has there been anything done about this? it seems to still be on triage?

I'm reporting the issue also on a monorepo. __webpack_require__.$Refresh$.register is called on exports of tslib. I've extracted part of what @vanilla-extract/integration is passing to eval:
var _c, _c2, _c3, _c4, _c5, _c6, _c7;
__webpack_require__.$Refresh$.register(_c, "O");
__webpack_require__.$Refresh$.register(_c2, "P");
__webpack_require__.$Refresh$.register(_c3, "E");
__webpack_require__.$Refresh$.register(_c4, "T");
__webpack_require__.$Refresh$.register(_c5, "I");
__webpack_require__.$Refresh$.register(_c6, "D");
__webpack_require__.$Refresh$.register(_c7, "A");

full virtual/_tslib.js part
/***/ "../my-lib/dist/esm/_virtual/_tslib.js":
/*!*********************************************!*\
  !*** ../my-lib/dist/esm/_virtual/_tslib.js ***!
  \*********************************************/
/***/ (function(__unused_webpack_module, __webpack_exports__, __webpack_require__) {

__webpack_require__.r(__webpack_exports__);
/* harmony export */ __webpack_require__.d(__webpack_exports__, {
/* harmony export */   __addDisposableResource: function() { return /* binding */ D; },
/* harmony export */   __assign: function() { return /* binding */ r; },
/* harmony export */   __asyncDelegator: function() { return /* binding */ O; },
/* harmony export */   __asyncGenerator: function() { return /* binding */ g; },
/* harmony export */   __asyncValues: function() { return /* binding */ j; },
/* harmony export */   __await: function() { return /* binding */ m; },
/* harmony export */   __awaiter: function() { return /* binding */ s; },
/* harmony export */   __classPrivateFieldGet: function() { return /* binding */ T; },
/* harmony export */   __classPrivateFieldIn: function() { return /* binding */ I; },
/* harmony export */   __classPrivateFieldSet: function() { return /* binding */ k; },
/* harmony export */   __createBinding: function() { return /* binding */ y; },
/* harmony export */   __decorate: function() { return /* binding */ o; },
/* harmony export */   __disposeResources: function() { return /* binding */ A; },
/* harmony export */   __esDecorate: function() { return /* binding */ i; },
/* harmony export */   __exportStar: function() { return /* binding */ d; },
/* harmony export */   __extends: function() { return /* binding */ t; },
/* harmony export */   __generator: function() { return /* binding */ p; },
/* harmony export */   __importDefault: function() { return /* binding */ x; },
/* harmony export */   __importStar: function() { return /* binding */ E; },
/* harmony export */   __makeTemplateObject: function() { return /* binding */ P; },
/* harmony export */   __metadata: function() { return /* binding */ l; },
/* harmony export */   __param: function() { return /* binding */ a; },
/* harmony export */   __propKey: function() { return /* binding */ u; },
/* harmony export */   __read: function() { return /* binding */ b; },
/* harmony export */   __rest: function() { return /* binding */ n; },
/* harmony export */   __runInitializers: function() { return /* binding */ c; },
/* harmony export */   __setFunctionName: function() { return /* binding */ f; },
/* harmony export */   __spread: function() { return /* binding */ v; },
/* harmony export */   __spreadArray: function() { return /* binding */ _; },
/* harmony export */   __spreadArrays: function() { return /* binding */ w; },
/* harmony export */   __values: function() { return /* binding */ h; },
/* harmony export */   "default": function() { return /* binding */ C; }
/* harmony export */ });
var e = function (t, r) {
  return e = Object.setPrototypeOf || {
    __proto__: []
  } instanceof Array && function (e, t) {
    e.__proto__ = t;
  } || function (e, t) {
    for (var r in t) Object.prototype.hasOwnProperty.call(t, r) && (e[r] = t[r]);
  }, e(t, r);
};
function t(t, r) {
  if ("function" != typeof r && null !== r) throw new TypeError("Class extends value " + String(r) + " is not a constructor or null");
  function n() {
    this.constructor = t;
  }
  e(t, r), t.prototype = null === r ? Object.create(r) : (n.prototype = r.prototype, new n());
}
var r = function () {
  return r = Object.assign || function (e) {
    for (var t, r = 1, n = arguments.length; r < n; r++) for (var o in t = arguments[r]) Object.prototype.hasOwnProperty.call(t, o) && (e[o] = t[o]);
    return e;
  }, r.apply(this, arguments);
};
function n(e, t) {
  var r = {};
  for (var n in e) Object.prototype.hasOwnProperty.call(e, n) && t.indexOf(n) < 0 && (r[n] = e[n]);
  if (null != e && "function" == typeof Object.getOwnPropertySymbols) {
    var o = 0;
    for (n = Object.getOwnPropertySymbols(e); o < n.length; o++) t.indexOf(n[o]) < 0 && Object.prototype.propertyIsEnumerable.call(e, n[o]) && (r[n[o]] = e[n[o]]);
  }
  return r;
}
function o(e, t, r, n) {
  var o,
    a = arguments.length,
    i = a < 3 ? t : null === n ? n = Object.getOwnPropertyDescriptor(t, r) : n;
  if ("object" == typeof Reflect && "function" == typeof Reflect.decorate) i = Reflect.decorate(e, t, r, n);else for (var c = e.length - 1; c >= 0; c--) (o = e[c]) && (i = (a < 3 ? o(i) : a > 3 ? o(t, r, i) : o(t, r)) || i);
  return a > 3 && i && Object.defineProperty(t, r, i), i;
}
function a(e, t) {
  return function (r, n) {
    t(r, n, e);
  };
}
function i(e, t, r, n, o, a) {
  function i(e) {
    if (void 0 !== e && "function" != typeof e) throw new TypeError("Function expected");
    return e;
  }
  for (var c, u = n.kind, f = "getter" === u ? "get" : "setter" === u ? "set" : "value", l = !t && e ? n.static ? e : e.prototype : null, s = t || (l ? Object.getOwnPropertyDescriptor(l, n.name) : {}), p = !1, y = r.length - 1; y >= 0; y--) {
    var d = {};
    for (var h in n) d[h] = "access" === h ? {} : n[h];
    for (var h in n.access) d.access[h] = n.access[h];
    d.addInitializer = function (e) {
      if (p) throw new TypeError("Cannot add initializers after decoration has completed");
      a.push(i(e || null));
    };
    var b = (0, r[y])("accessor" === u ? {
      get: s.get,
      set: s.set
    } : s[f], d);
    if ("accessor" === u) {
      if (void 0 === b) continue;
      if (null === b || "object" != typeof b) throw new TypeError("Object expected");
      (c = i(b.get)) && (s.get = c), (c = i(b.set)) && (s.set = c), (c = i(b.init)) && o.unshift(c);
    } else (c = i(b)) && ("field" === u ? o.unshift(c) : s[f] = c);
  }
  l && Object.defineProperty(l, n.name, s), p = !0;
}
function c(e, t, r) {
  for (var n = arguments.length > 2, o = 0; o < t.length; o++) r = n ? t[o].call(e, r) : t[o].call(e);
  return n ? r : void 0;
}
function u(e) {
  return "symbol" == typeof e ? e : "".concat(e);
}
function f(e, t, r) {
  return "symbol" == typeof t && (t = t.description ? "[".concat(t.description, "]") : ""), Object.defineProperty(e, "name", {
    configurable: !0,
    value: r ? "".concat(r, " ", t) : t
  });
}
function l(e, t) {
  if ("object" == typeof Reflect && "function" == typeof Reflect.metadata) return Reflect.metadata(e, t);
}
function s(e, t, r, n) {
  return new (r || (r = Promise))(function (o, a) {
    function i(e) {
      try {
        u(n.next(e));
      } catch (e) {
        a(e);
      }
    }
    function c(e) {
      try {
        u(n.throw(e));
      } catch (e) {
        a(e);
      }
    }
    function u(e) {
      var t;
      e.done ? o(e.value) : (t = e.value, t instanceof r ? t : new r(function (e) {
        e(t);
      })).then(i, c);
    }
    u((n = n.apply(e, t || [])).next());
  });
}
function p(e, t) {
  var r,
    n,
    o,
    a,
    i = {
      label: 0,
      sent: function () {
        if (1 & o[0]) throw o[1];
        return o[1];
      },
      trys: [],
      ops: []
    };
  return a = {
    next: c(0),
    throw: c(1),
    return: c(2)
  }, "function" == typeof Symbol && (a[Symbol.iterator] = function () {
    return this;
  }), a;
  function c(c) {
    return function (u) {
      return function (c) {
        if (r) throw new TypeError("Generator is already executing.");
        for (; a && (a = 0, c[0] && (i = 0)), i;) try {
          if (r = 1, n && (o = 2 & c[0] ? n.return : c[0] ? n.throw || ((o = n.return) && o.call(n), 0) : n.next) && !(o = o.call(n, c[1])).done) return o;
          switch (n = 0, o && (c = [2 & c[0], o.value]), c[0]) {
            case 0:
            case 1:
              o = c;
              break;
            case 4:
              return i.label++, {
                value: c[1],
                done: !1
              };
            case 5:
              i.label++, n = c[1], c = [0];
              continue;
            case 7:
              c = i.ops.pop(), i.trys.pop();
              continue;
            default:
              if (!(o = i.trys, (o = o.length > 0 && o[o.length - 1]) || 6 !== c[0] && 2 !== c[0])) {
                i = 0;
                continue;
              }
              if (3 === c[0] && (!o || c[1] > o[0] && c[1] < o[3])) {
                i.label = c[1];
                break;
              }
              if (6 === c[0] && i.label < o[1]) {
                i.label = o[1], o = c;
                break;
              }
              if (o && i.label < o[2]) {
                i.label = o[2], i.ops.push(c);
                break;
              }
              o[2] && i.ops.pop(), i.trys.pop();
              continue;
          }
          c = t.call(e, i);
        } catch (e) {
          c = [6, e], n = 0;
        } finally {
          r = o = 0;
        }
        if (5 & c[0]) throw c[1];
        return {
          value: c[0] ? c[1] : void 0,
          done: !0
        };
      }([c, u]);
    };
  }
}
var y = Object.create ? function (e, t, r, n) {
  void 0 === n && (n = r);
  var o = Object.getOwnPropertyDescriptor(t, r);
  o && !("get" in o ? !t.__esModule : o.writable || o.configurable) || (o = {
    enumerable: !0,
    get: function () {
      return t[r];
    }
  }), Object.defineProperty(e, n, o);
} : function (e, t, r, n) {
  void 0 === n && (n = r), e[n] = t[r];
};
function d(e, t) {
  for (var r in e) "default" === r || Object.prototype.hasOwnProperty.call(t, r) || y(t, e, r);
}
function h(e) {
  var t = "function" == typeof Symbol && Symbol.iterator,
    r = t && e[t],
    n = 0;
  if (r) return r.call(e);
  if (e && "number" == typeof e.length) return {
    next: function () {
      return e && n >= e.length && (e = void 0), {
        value: e && e[n++],
        done: !e
      };
    }
  };
  throw new TypeError(t ? "Object is not iterable." : "Symbol.iterator is not defined.");
}
function b(e, t) {
  var r = "function" == typeof Symbol && e[Symbol.iterator];
  if (!r) return e;
  var n,
    o,
    a = r.call(e),
    i = [];
  try {
    for (; (void 0 === t || t-- > 0) && !(n = a.next()).done;) i.push(n.value);
  } catch (e) {
    o = {
      error: e
    };
  } finally {
    try {
      n && !n.done && (r = a.return) && r.call(a);
    } finally {
      if (o) throw o.error;
    }
  }
  return i;
}
function v() {
  for (var e = [], t = 0; t < arguments.length; t++) e = e.concat(b(arguments[t]));
  return e;
}
function w() {
  for (var e = 0, t = 0, r = arguments.length; t < r; t++) e += arguments[t].length;
  var n = Array(e),
    o = 0;
  for (t = 0; t < r; t++) for (var a = arguments[t], i = 0, c = a.length; i < c; i++, o++) n[o] = a[i];
  return n;
}
function _(e, t, r) {
  if (r || 2 === arguments.length) for (var n, o = 0, a = t.length; o < a; o++) !n && o in t || (n || (n = Array.prototype.slice.call(t, 0, o)), n[o] = t[o]);
  return e.concat(n || Array.prototype.slice.call(t));
}
function m(e) {
  return this instanceof m ? (this.v = e, this) : new m(e);
}
function g(e, t, r) {
  if (!Symbol.asyncIterator) throw new TypeError("Symbol.asyncIterator is not defined.");
  var n,
    o = r.apply(e, t || []),
    a = [];
  return n = {}, i("next"), i("throw"), i("return"), n[Symbol.asyncIterator] = function () {
    return this;
  }, n;
  function i(e) {
    o[e] && (n[e] = function (t) {
      return new Promise(function (r, n) {
        a.push([e, t, r, n]) > 1 || c(e, t);
      });
    });
  }
  function c(e, t) {
    try {
      (r = o[e](t)).value instanceof m ? Promise.resolve(r.value.v).then(u, f) : l(a[0][2], r);
    } catch (e) {
      l(a[0][3], e);
    }
    var r;
  }
  function u(e) {
    c("next", e);
  }
  function f(e) {
    c("throw", e);
  }
  function l(e, t) {
    e(t), a.shift(), a.length && c(a[0][0], a[0][1]);
  }
}
function O(e) {
  var t, r;
  return t = {}, n("next"), n("throw", function (e) {
    throw e;
  }), n("return"), t[Symbol.iterator] = function () {
    return this;
  }, t;
  function n(n, o) {
    t[n] = e[n] ? function (t) {
      return (r = !r) ? {
        value: m(e[n](t)),
        done: !1
      } : o ? o(t) : t;
    } : o;
  }
}
_c = O;
function j(e) {
  if (!Symbol.asyncIterator) throw new TypeError("Symbol.asyncIterator is not defined.");
  var t,
    r = e[Symbol.asyncIterator];
  return r ? r.call(e) : (e = h(e), t = {}, n("next"), n("throw"), n("return"), t[Symbol.asyncIterator] = function () {
    return this;
  }, t);
  function n(r) {
    t[r] = e[r] && function (t) {
      return new Promise(function (n, o) {
        (function (e, t, r, n) {
          Promise.resolve(n).then(function (t) {
            e({
              value: t,
              done: r
            });
          }, t);
        })(n, o, (t = e[r](t)).done, t.value);
      });
    };
  }
}
function P(e, t) {
  return Object.defineProperty ? Object.defineProperty(e, "raw", {
    value: t
  }) : e.raw = t, e;
}
_c2 = P;
var S = Object.create ? function (e, t) {
  Object.defineProperty(e, "default", {
    enumerable: !0,
    value: t
  });
} : function (e, t) {
  e.default = t;
};
function E(e) {
  if (e && e.__esModule) return e;
  var t = {};
  if (null != e) for (var r in e) "default" !== r && Object.prototype.hasOwnProperty.call(e, r) && y(t, e, r);
  return S(t, e), t;
}
_c3 = E;
function x(e) {
  return e && e.__esModule ? e : {
    default: e
  };
}
function T(e, t, r, n) {
  if ("a" === r && !n) throw new TypeError("Private accessor was defined without a getter");
  if ("function" == typeof t ? e !== t || !n : !t.has(e)) throw new TypeError("Cannot read private member from an object whose class did not declare it");
  return "m" === r ? n : "a" === r ? n.call(e) : n ? n.value : t.get(e);
}
_c4 = T;
function k(e, t, r, n, o) {
  if ("m" === n) throw new TypeError("Private method is not writable");
  if ("a" === n && !o) throw new TypeError("Private accessor was defined without a setter");
  if ("function" == typeof t ? e !== t || !o : !t.has(e)) throw new TypeError("Cannot write private member to an object whose class did not declare it");
  return "a" === n ? o.call(e, r) : o ? o.value = r : t.set(e, r), r;
}
function I(e, t) {
  if (null === t || "object" != typeof t && "function" != typeof t) throw new TypeError("Cannot use 'in' operator on non-object");
  return "function" == typeof e ? t === e : e.has(t);
}
_c5 = I;
function D(e, t, r) {
  if (null != t) {
    if ("object" != typeof t && "function" != typeof t) throw new TypeError("Object expected.");
    var n;
    if (r) {
      if (!Symbol.asyncDispose) throw new TypeError("Symbol.asyncDispose is not defined.");
      n = t[Symbol.asyncDispose];
    }
    if (void 0 === n) {
      if (!Symbol.dispose) throw new TypeError("Symbol.dispose is not defined.");
      n = t[Symbol.dispose];
    }
    if ("function" != typeof n) throw new TypeError("Object not disposable.");
    e.stack.push({
      value: t,
      dispose: n,
      async: r
    });
  } else r && e.stack.push({
    async: !0
  });
  return t;
}
_c6 = D;
var R = "function" == typeof SuppressedError ? SuppressedError : function (e, t, r) {
  var n = new Error(r);
  return n.name = "SuppressedError", n.error = e, n.suppressed = t, n;
};
function A(e) {
  function t(t) {
    e.error = e.hasError ? new R(t, e.error, "An error was suppressed during disposal.") : t, e.hasError = !0;
  }
  return function r() {
    for (; e.stack.length;) {
      var n = e.stack.pop();
      try {
        var o = n.dispose && n.dispose.call(n.value);
        if (n.async) return Promise.resolve(o).then(r, function (e) {
          return t(e), r();
        });
      } catch (e) {
        t(e);
      }
    }
    if (e.hasError) throw e.error;
  }();
}
_c7 = A;
var C = {
  __extends: t,
  __assign: r,
  __rest: n,
  __decorate: o,
  __param: a,
  __metadata: l,
  __awaiter: s,
  __generator: p,
  __createBinding: y,
  __exportStar: d,
  __values: h,
  __read: b,
  __spread: v,
  __spreadArrays: w,
  __spreadArray: _,
  __await: m,
  __asyncGenerator: g,
  __asyncDelegator: O,
  __asyncValues: j,
  __makeTemplateObject: P,
  __importStar: E,
  __importDefault: x,
  __classPrivateFieldGet: T,
  __classPrivateFieldSet: k,
  __classPrivateFieldIn: I,
  __addDisposableResource: D,
  __disposeResources: A
};

var _c, _c2, _c3, _c4, _c5, _c6, _c7;
__webpack_require__.$Refresh$.register(_c, "O");
__webpack_require__.$Refresh$.register(_c2, "P");
__webpack_require__.$Refresh$.register(_c3, "E");
__webpack_require__.$Refresh$.register(_c4, "T");
__webpack_require__.$Refresh$.register(_c5, "I");
__webpack_require__.$Refresh$.register(_c6, "D");
__webpack_require__.$Refresh$.register(_c7, "A");

/***/ }),

I'm blocked with the issue, as I can play with leaf nodes / filenames / exports / to bypass that. Any idea?

I've come up with patching @vanilla-extract/integration to mitigate the $Refresh$ issue by removing the problematic lines from source
diff --git a/dist/vanilla-extract-integration.cjs.dev.js b/dist/vanilla-extract-integration.cjs.dev.js
index f9ece42d38952835bb6c9e3414f64807d9a3d79c..07e3d34ddb0457c057d154c7b31047f40fd119b7 100644
--- a/dist/vanilla-extract-integration.cjs.dev.js
+++ b/dist/vanilla-extract-integration.cjs.dev.js
@@ -128,7 +128,7 @@ async function processVanillaFile({
   const adapterBoundSource = `
     require('@vanilla-extract/css/adapter').setAdapter(__adapter__);
     ${source}
-  `;
+  `.replaceAll(/.*__webpack_require__\.\$Refresh\$.*/g, '');
   const evalResult = evalCode__default["default"](adapterBoundSource, filePath, {
     console,
     process,

This could potentially be an issue with how mantine exports a combination of components and non-components from @mantine/core. This can cause issues with react refesh, as evidenced in https://github.com/vanilla-extract-css/vanilla-extract/issues/1072. It is strange that this only occurs with the pages dir and not app dir.

any solution yet?

Depends what your issue is. Have you tried separating your React component exports from your style/theme exports?

I've just spent hours upgrading a repo from v6 to v7 replacing createStyles with vanilla extract and now come across this issue. Next.js 13 pages dir app. Followed the Mantine upgrade docs + vanilla extract docs. No idea how to resolve it.

./src/components/layouts/Footer.css.ts
NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: document is not defined

Upgrading to Next.js 14 also didn't help with this issue.
In the end I've switched use CSS modules as recommended for now. However, would be great to understand if this issue could be resolved as I prefer CSS-in-JS styles with TypeScript and this migration to CSS has involved a LOT of work 😅

Upgrading to Next.js 14.2 triggered this problem for me (see issue#1393). My guess would be that these issues are related and would be curious if this fix works.
The outcome should be the same as the solution @guillaumewuip proposed but without patching.

👋 I ran into a kinda related similar issue to this thread when using Mantine + Vanilla Extract + NextJS.
I was getting the following error

The guide on https://mantine.dev/styles/vanilla-extract/#theming says to create a theme.css.ts file with the following contents:
// theme.css.ts
import { createTheme } from '@mantine/core';
import { themeToVars } from '@mantine/vanilla-extract';

// Do not forget to pass theme to MantineProvider
export const theme = createTheme({
  fontFamily: 'serif',
  primaryColor: 'cyan',
});

// CSS variables object, can be access in *.css.ts files
export const vars = themeToVars(theme);

This for some reasons bricks the compiling. I fixed this by creating a separate vars.css.ts file with the following contents and removing themeToVars part from theme.css.ts
import { themeToVars } from "@mantine/vanilla-extract";
import { theme } from "./theme.css";

export const vars = themeToVars(theme);

Hopefully this helps some peopel

Thank you @tadhglewis for the pointer. My issue was that I'm using Mantine's Textarea.extend in the same file where themeToVars is called. Textarea uses react-textarea-autosize which requires document. The conflict is happening somewhere in the client vs server nextjs mess and it's difficult to debug. The theme is consumed on the server (in layout), but "vars" are consumed intermixed. Moving the extend() functionality out of the file and not including the components: {} object in the call fixed the issue.
Related issues:
https://github.com/mantinedev/mantine/issues/6719
https://github.com/Andarist/react-textarea-autosize/issues/335

Not a single solution worked for me even for the simplest theme with nothing else in the file. Spent hours trying everything but was never able to use the vars in a .css.ts file using themeToVars with mantine 7.12.1 and nextjs 14.0.4. In the end I ended up copy and pasting the theme values into a new object  so I could use them and that worked but :(

Is this your error?
NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: $RefreshReg$ is not defined
If so you can try:
next.config.js
const { createVanillaExtractPlugin } = require("@vanilla-extract/next-plugin");

const withVanillaExtract = createVanillaExtractPlugin();

/** @type {import('next').NextConfig} */
let nextConfig = {
    webpack(config, { nextRuntime, webpack }) {
        if (!nextRuntime) {
            config.plugins.push(
                new webpack.BannerPlugin({
                    banner: `$RefreshReg$ = () => {};\n$RefreshSig$ = () => () => {};\n`,
                    raw: true,
                    entryOnly: true,
                    include: /\.css.ts$/,
                }),
            );
        }
        return config;
    },
};

nextConfig = withVanillaExtract(nextConfig);

module.exports = nextConfig;

For those getting NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: document is not defined when using the pages directory of a Next.JS app with mantine & vanilla-extract: I have found that merely adding the Next.JS "app directory" to my project fixes the issue. This seems to work even if you're using output: "standalone" in your next.config.js.
mkdir -p ./src/app
touch ./src/app/.gitkeep

At this point I don't know if the issue lies within Mantine, Vanilla Extract, or even Next.JS itself, but hopefully this can help unstick some people...


CF Release

Updates
Added

capital-framework: [patch] Add dry run option to make testing releases easier

Review

@cfpb/front-end-team-admin

I am a bot
After this PR is merged, I will instruct Travis to automagically perform the following steps:

Increment Capital Framework's version per our guidelines.
Add a timestamped entry to the changelog with the new version and its changes.
Tag the release and push it to GitHub.
Publish both capital-framework and any individually updated components to npm.
Update both canary, our development branch, and master, our release branch.

If I do something wrong, blame a human.

🚂 Cmon Travis 🚂


ADFS On-premises sample

Hi
Is this sample code compatible with ADFS On-premises scenario?
If not, would you be able to share the on-premises example?
Thanks,
Vincent

Hi,
we are having the same problem. We found the on behalf of, and the normal login scenario. But mating the two has proven to be "difficult". (I tried for one week now).
.

Would the following sample be a good start ? https://github.com/Azure-Samples/active-directory-dotnet-webapp-wsfederation


Scalar series labels in compare adding random html after action

The series labels start out ok, but the moment I do anything (zoom, hover, etc.) the random html appears.

Trains 0.14.1
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0

Clarification, it only appears when I zoom using Ctrl+ScrollWheel

Hi @WillNichols726
The bug is verified, I can reproduce it on Firefox and on Chrome, regardless of the host OS.
A quick fix:  once you are done with zooming the page, if you refresh the page, the legend will go back to normal.
BTW,
I was only able to reproduce this behavior by changing the zoom of the entire page (with either ctrl+wheel or ctrl+plus/minus)
What did you mean by "the moment I do anything (zoom, hover, etc.)"?
Hover seems to work for me, and also enabling/disabling a specific series on the graph...

@bmartinn As per my second comment, I only see the bug when doing whole page zooms.
And as always, thanks again for such an awesome ML platform!

Hi @WillNichols726,
I forgot to update here, the bug was fixed in trains-server v0.15 :)


Differenciate between Monokai themes

Originally the monokai theme was based on the sublime variant.
This PR makes it mostly accurate to the original textmate theme, taking some liberties where textmate did not allow themes.
This PR also forks the original sublime based theme and improves it by copying the direct colors values instead of relying on color selections.

To document, I used https://github.com/textmate/monokai.tmbundle as the textmate reference since the blog by monokai which hosted it got deleted and now redirects to monokai pro

Would you mind updating the README too?


Added force flag to runtest

This PR addresses issue #81 by removing the alias file when if it exists before executing the build plan.

Thanks. One issue is that the @runtest alias is recursive and this patch will only deletes the toplevel runtest alias files. So for instance if you just run jbuilder runtest and have no tests defined at toplevel it will do nothing.
One solution would be to scan the alias store recursively and delete all runtest alias files, but that's becoming complicated. It the end I think it'd be simpler to implement this feature directly in build_system.ml. If you look for if rule_changed, that's where jbuilder decides whether to re-run an action or not. We can simply add: if rule_changed || (t.force_runtest && is_runtest targets).
is_runtest would be a predicate checking that all the targets are runtest alias files. You can look at Utils.describe_target for an example of how to detect and interpret alias files.

Just a note: The implementation diml is describing is something similar to what initially Richard was going for. I wrongly convinced him that the implementation had to be outside the build rules themselves to be "clean"

Yh, deleting the file was my initial idea as well but it turns out that it doesn't work well in practice

Alright, I made the changes you suggested, however, I felt that I had to add too many optional parameters to get the flag accessible from where I wanted.  Is there perhaps a better way of getting the force_runtest parameter where it needs to be more cleanly?

@rdavison You might remember clflags.ml :smile:
Although let's defer to @diml if we need another global variable here.

I suppose that would work if we wanted to support a global --force flag

Well, I'd like to get rid of Clflags at some point, so it's better not to add new things in it

@rdavison do you plan on updating this? I can take it over if you don't want to work on this anymore.

@rgrinberg : You're more than welcome to

This is implemented in master.


Devbook User Profile

As a user, I want to have a profile with personal information, so that people can learn about me.

Short + basic example of what a gherkin-formatted user story would look like for (one of the stories contained within this one)
Given I am a DevBook user
When I log in
Then I see my Profile page


facing issue while reading one log event present in logfile

fluentd or td-agent version: fluentd 1.3.3

Environment information:

Operating system: windows 21012 R2

My configuration

<source>
    @type
    path "C:\\Bharath020419100816.txt"
    pos_file etc/td-agent/pos/xxxxxxxxxx.pos
    tag xxxxxxxx
    path_key tailed_path
    format none
    read_from_head true
</source>

<filter xxxxxx-**>
    @type record_modifier
    <record>
        entity "xxxxxxxxxx"
        shipped_time "${Time.at(time).to_s}"
        log_time "${record['tailed_path'].split(\"/\")[-1].split(\".\")[0][-12..-1]}"
        component ${tag}
        hostname "#{Socket.gethostname}"
    </record>
</filter>
<match **>
   @type stdout
</match>

Our problem explanation :

One of application is one event logs to one file with timestamp extension to file example : xxxxxxxxxxxxxxxxxx020419100816.txt
Each event is writing one log event in single logfile with timestamp at prefix of file as above examples.
when i am providing enter at end of log event in file then only its start consuming. but i should not be change any content in log file because its written by application itself.
example of log event :--
Log file : xxxxxxxxxxxxxxxxxx020419100816.txt
Below is just example one Log event in file :--
2019-04-14 17:00:45.234 DEBUG com.cs.xxxxxxxxxxxxxxxxxxx(IntfUtilLog.java:40)
Let me know if you need any other information.
Please help me to identify this issue.

If i am following same steps in RHEL server using td-agent , Fluentd able to read that event !! is there some issue with windows td-agent ? not sure how to debug more on this ..

Please try path "C:/Bharath020419100816.txt".
See also https://stackoverflow.com/questions/7173000/slash-and-backslash-in-ruby

its didn't worked. when i am hitting EOF with new line , its started capturing logs. but if no newline character at end of log its not capturing anything from log file.


Drag bounds not working dinamycally

Describe the bug
Using react three fiber I'm trying to make the camera move vertically as I drag the canvas, to simulate scrolling on canvas environment. I have a inferior and a superior limit in wich the camera has to stay inside, and I would like to use the rubberband property, and so I'm using bounds that should update if the camera position is at the superior limit, not letting the camera to go up further, or the inferior limit, not letting the camera go down further, but that doesn't seem to work at all, the camera act as if there's no bounds at all. What is going on? Is this intended/ not implemented yet or what am I missing?
Sandbox or Video
Here's a simple app, with a custom camera with its position-y controlled by the spring and the drag gesture, and a dodecahedron and ambient light just to visualize the 'scrolling'.

https://codesandbox.io/s/use-gesture-test-i3n9o?file=/src/App.js

Information:

dependencies:
"@react-spring/three": "9.2.3",
"@react-three/drei": "7.0.6",
"@react-three/fiber": "7.0.2",
"@use-gesture/react": "10.0.0-beta.17",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-scripts": "4.0.0",
"three": "0.130.1"
Device: PC
OS: Windows 10
Browser Chrome

Checklist:

[X] I've read the documentation.
[X] If this is an issue with drag, I've tried setting touch-action: none to the draggable element.

@danielx-art haven't tried your sandbox, but bounds are only calculated when the gesture starts.

So it is impossible to use the rubberband effect on scrolling to final of a page, for example?

Not sure I understand sorry. How is this impossible?

Oh I see, so if I understand you correctly and the bounds are calculated when the gesture starts, then I still can update those bounds on each drag gesture by using the initial coordinates of the gesture and their distance to the bounds. Going to test that this minute and I'll report back!

I was missing the fact that I can write bounds in terms of the canvas coordinates using transform exactly as they express in the documentation, but with flipped y to ensure the drag orientation. For some reason I believe that transform only worked if the bounds, even in canvas coordinates, would stay inside the viewport, I don't know why I tought that. I updated the sandbox to a version that works, if someone is interested:
https://codesandbox.io/s/use-gesture-test-i3n9o?file=/src/App.js
Thank you very much @dbismut, I'm closing this topic.


[FR] Implement hashing

Hashing ComponentArrays (v0.9.3) doesn't seem to be implemented and the generic fallback (tested on 1.6) doesn't work. An unfortunately side-effect of this is that ComponentArrays don't work with certain remote constructs (here because auto global-shipping relies on the hash):
julia> using ComponentArrays, Distributed

julia> addprocs(1);

julia> x = ComponentArray(a=[1,2], b=[3]);

julia> @fetch x
ERROR: MethodError: no method matching LinearIndices(::Tuple{Symbol, Symbol})
Closest candidates are:
  LinearIndices(::Tuple{}) at indices.jl:454
  LinearIndices(::R) where {N, R<:Tuple{Vararg{AbstractUnitRange{Int64}, N}}} at indices.jl:451
  LinearIndices(::Tuple{Vararg{AbstractUnitRange{var"#s79"} where var"#s79"<:Integer, N}}) where N at indices.jl:455
  ...
Stacktrace:
  [1] hash(A::ComponentVector{Int64}, h::UInt64)
...

Hm. I'd love to have this working, but to be honest, I have no idea what I'm supposed to do to implement this. Looking at how it's implemented for AbstractArrays doesn't help much either. Can I just do something like this?
Base.hash(x::ComponentArray, h::UInt) = hash(getdata(x), h)

The docstring for hash mentions that == should be implemented as well, but it seems like the fallback ==(A::AbstractArray, B::AbstractArray) should be sufficient.

I guess its a little unclear because the docstring says
Compute an integer hash code such that isequal(x,y) implies hash(x)==hash(y).

and we currently have ComponentArray(a=1, b=2) == [1,2] so it seems like your hash function is the right one, but at the same time, that would imply (to use remote shipping as an example, but anything bashed on hash would behave similarly)
julia> x = [1,2];

julia> @fetch x
[1,2]

julia> x = ComponentArray(a=1, b=2);

julia> @fetch x
[1,2] # x not updated on remote since it thinks it hasnt changed locally

Perhaps its actually ComponentArray(a=1, b=2) == [1,2] that should be false? What do other array wrapper packages do?

All the other array wrappers that I've tried (including Adjoint from LinearAlgebra and SubArray from Base) work the same way
julia> [1 2 3] == [1, 2, 3]'
true

julia> [1, 2] == view([1, 2, 3], 1:2)
true

julia> using StaticArrays

julia> SVector(1, 2, 3) == [1, 2, 3]
true

julia> using LabelledArrays

julia> LVector(a=1, b=2, c=3) == [1, 2, 3]
true

It seems like hashing on the underlying array is the right thing to do, then, to be consistent with everyone else.
julia> hash([1 2 3]) == hash([1, 2, 3]')
true

julia> hash(SVector(1,2,3)) == hash([1,2,3])
true

And StaticArrays works because when it falls back to the default AbstractArray method, keys gives the LinearIndices of the array so it will work the same as a plain array.

Ah just saw you merged. Unfortunately I have to say, I think this is the wrong behaviour and I do think ComponentArrays should implement its own == (and hash) which accounts for the axes. To me the axes are a fundamental part of what they are, so the current behaviour is wierd
julia> ComponentArray(a=1, b=1) == ComponentArray(x=1, z=1)
true

This is similarly wrong to me:
julia> component_array1 == component_array2
true

julia> @unpack a = component_array1
1

julia> @unpack a = component_array2
# error

If equality included the axes, then so would hash (solving the distributed issue above), and it just seems more natural. If someone wants to check equality vs an array, the can do all(component_array .== array).

I still haven't tagged it yet so I could change it again for this release. I agree that it would make more sense for equality to require the same axes as well as underlying data.
With that said, I am hesitant to implement behavior that is fundamentally different than all the other array types. I don't really know whose code is depending on equivalence of two different types of arrays in this way.
Also, the same argument as yours above could be made for, say 1 and 1+0im:
julia> x1 = 1; x2 = 1+0im;

julia> x1 == x2
true

julia> hash(x1) == hash(x2)
true

julia> @unpack re = x2
1 + 0im

julia> @unpack re = x1
ERROR: type Int64 has no field re
Stacktrace:
 [1] getproperty(x::Int64, f::Symbol)
   @ Base .\Base.jl:33
 [2] unpack(x::Int64, #unused#::Val{:re})
   @ UnPack ~\.julia\packages\UnPack\EkESO\src\UnPack.jl:34
 [3] top-level scope
   @ ~\.julia\packages\UnPack\EkESO\src\UnPack.jl:101

If I were able to just change ==(a::ComponentArray, b::ComponentArray) so they had to have matching axes and let ==(a::ComponentArray, b::AbstractArray) fall back to the default method, I would, but I don't see any way to make this work with hashing.

I’ll reopen the issue too.

I guess the counterpoint to my last example would be:
julia> nt1 = (a=1, b=1); nt2 = (x=1, z=1);

julia> nt1 == nt2
false

Hmm yea that last example I think puts it in perspective. I guess there's basically just two incompatible interfaces in terms of what ==/hash should give, AbstractArrays and NamedTuples, and the question is which one is a ComponentArray? Even though intuitively I think of it as "both," and its NamedTuple-ness as kind of a superset of its Array-ness, I suppose its formally an <:AbstractArray, so maybe you did make the right choice. I'm fine if you wanted to mark it as closed again. Might be interesting to ask on Slack/Discourse to get other inputs, I bet this has come up before but I don't know where.

I think maybe a good way to frame this is that ComponentArrays are typically used as NamedTuples by end users and AbstractArrayss by the solvers they are passing them to. Users always know that they are working with ComponentArrays, so they at least have the ability to change their code accordingly. The authors of solver libraries (DifferentialEquations, Optim, Turing, and wherever else ComponentArrays are used) don't--and shouldn't need to--know that their code is working with ComponentArrays.
So I think I'd rather err on the side of AbstractArray-ness. If a solver uses A==B somewhere expecting the arrays A and B to follow the standard convention for equality of  AbstractArrays, the user who is trying to pass a ComponentArray through that solver is going to have a problem that they can't fix without some serious monkey-patching. On the other hand, if a user needs ComponentArrays to follow a more strict NamedTuple-ish form of equality, they can always do themselves with something like
is_strictly_equal(a::A, b::B) where {A,B} = a==b && A===B

Actually, maybe it would be a good idea to just define that in ComponentArrays and export it. And maybe give a warning when equality is asked between two equal but not strictly equal ComponentArrays.

Alright, let's do it the ComponentArray(a=1, b=1) != ComponentArray(x=1, z=1) way.

Thanks for looking into this, I agree in the end this was the right solution!


calico/node v1.0.0-rc3: Unexpected command output Device "eth0" does not exist.

I have working k8s cluster with calico v0.23.0:
OS: ubuntu 14.04
kubernetes: 1.4.7
docker-engine: 1.12.1-0~trusty
etcd: 3.0.15
calico-containers: v0.23.0
calico-cni: 1.4.3
Everything works ok.
Then I'm trying to run new hosted version of calico:
http://docs.projectcalico.org/v2.0/getting-started/kubernetes/installation/hosted/hosted
using yaml file:
http://docs.projectcalico.org/v2.0/getting-started/kubernetes/installation/hosted/calico.yaml
I've edited yaml file changing fields: etcd_endpoints, cidr and version of the image quay.io/calico/node to v1.0.0-rc3:
https://gist.github.com/r0bj/e3773396b287e5378f893907a415cf02
After successful calico/node DeamonSet start, creating pods isn't possible due to error message from kubelet:
E1212 12:21:33.303277    1134 docker_manager.go:357] NetworkPlugin cni failed on the status hook for pod 'nginx-1691775941-t7f51' - Unexpected command output Device "eth0" does not exist.
 with error: exit status 1

Logs with more context:
https://gist.github.com/r0bj/5f4a32f68d628ebb8c4678d02682ff02
Logs with debug:
https://gist.github.com/r0bj/2f4546ef763e9def9b0951e9b2e8a789
cali interface isn't created on node.
  The kubelet has an async status check that, when it occurs before the CNI plugin is finished, emits that message.
Since the "Device "eth0" does not exist." is likely a red-herring, there is probably something else preventing the pods from starting.
This is the last log I see from Calico
INFO[0000] Populated endpoint                            Workload=default.nginx-1691775941-qifgx endpoint=&{{workloadEndpoint v1} {{} eth0 default.nginx-1691775941-qifgx k8s dev-k8s-worker-p3 map[]} {[<IP_ADDRESS>/32] [] <nil> <nil> [k8s_ns.default]  <nil>}}

but I'd expect some more logs to come after that.  Can you make sure that you're not missing some of the logs further down?
You can also check kubectl describe pod X on a pod that isn't coming up - it may provide more information.

Thanks for help.
kube-proxy wasn't running on the node. So without communication with API there was not possible to create pod. I guess this is difference in comparison to previous version of calico.
I'm closing this issue then.


update

Adding a profile set #9
Add the ability to automatically download translation packages #25

Just copy the code if you can't.


DQ API add optional proxy server function

Add optionality to modify the BASE URL's and to use a proxy server for connecting to JPMorgan DataQuery.

Approved without merge.


[5.4] Use UUID for generating file names

In reference to https://github.com/laravel/internals/issues/161

Looks like you're missing a namespace import?

Fixed, sorry. Was submitting to 5.3 first and changed branch looks like I dropped this import.

Isn't getHex() get the same strip dashes?
https://github.com/ramsey/uuid/blob/master/src/Uuid.php#L357

And I have one question about UUIDv4 uniqueness. I had an experience couple of years ago with this package in high load advertisement tracking system. All clicks were marked with UUIDv4, after half a year I found that there were ~3% of ID duplications. After that I'm always trying to use UUIDv5 when I want to make really unique value, but it require to generate namespace UUID first.

or just use str_random(32)

I thought about this, but maybe it's not a good idea because of inconsistencies on case-sensitive vs. case-insensitive filesystems.

I thought about this, but maybe it's not a good idea because of inconsistencies on case-sensitive vs. case-insensitive filesystems.

Just lowercase the output of the function?

The result would be unevenly distributed (bias towards letters), still it would have more entropy than my solution, so it might be better, technically.
Just as a reminder, these kinds of discussions are endless ;)

Just use str_random, and we're done. No need to f**k about with uuids.

Graham does make a good point :smile:

I had an example in mind for the lowercase need.
If you do path splitting as lucasmichot said above:
0123456789abcdef.jpg => 01/23/45/67/89/ab/cd/ef.jpg
If you reuse some data from windows to linux server, you're very likely to encounter issue.
I think we should really apply a strtolower.

Just write your own file storing procedure if you need something different, it's not hard. This methods exists really only for convenience.

Refs the subsequent https://github.com/laravel/framework/commit/5811bc377ef43f5d228b493579cec428e074efe4.
:smile:

Documentation needs to be updated: https://laravel.com/docs/master/filesystem#file-uploads.


Build fails when depending on pyodbc

Hello,
I am working on a repo that depends on pyodbc. The build fails since it cannot find sql.h. I was wondering if there's a way to fix this! Build info below
Details

Read the Docs project URL:https://readthedocs.org/projects/epivizfileparser
Build URL (if applicable):https://readthedocs.org/projects/epivizfileparser/builds/9049219/

Building wheels for collected packages: aioodbc, ujson, idna-ssl, pyodbc, tornado, pyyaml, psutil, toolz, httptools, msgpack-python, heapdict, pycparser
  Building wheel for aioodbc (setup.py): started
  Building wheel for aioodbc (setup.py): finished with status 'done'
  Stored in directory: /home/docs/checkouts/readthedocs.org/user_builds/epivizfileparser/.cache/pip/wheels/a7/5d/05/3348def6ff1a40e6a8305ac05f143f52da8b81ed8ebc44c447
  Building wheel for ujson (setup.py): started
  Building wheel for ujson (setup.py): finished with status 'done'
  Stored in directory: /home/docs/checkouts/readthedocs.org/user_builds/epivizfileparser/.cache/pip/wheels/28/77/e4/0311145b9c2e2f01470e744855131f9e34d6919687550f87d1
  Building wheel for idna-ssl (setup.py): started
  Building wheel for idna-ssl (setup.py): finished with status 'done'
  Stored in directory: /home/docs/checkouts/readthedocs.org/user_builds/epivizfileparser/.cache/pip/wheels/d3/00/b3/32d613e19e08a739751dd6bf998cfed277728f8b2127ad4eb7
  Building wheel for pyodbc (setup.py): started
  ERROR: Complete output from command /home/docs/checkouts/readthedocs.org/user_builds/epivizfileparser/envs/latest/bin/python -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-iabmvvue/pyodbc/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-omvz2tfx --python-tag cp35:
  ERROR: running bdist_wheel
  running build
  running build_ext
  building 'pyodbc' extension
  creating build
  creating build/temp.linux-x86_64-3.5
  creating build/temp.linux-x86_64-3.5/src
  gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/home/docs/.pyenv/versions/3.5.5/include/python3.5m -c src/buffer.cpp -o build/temp.linux-x86_64-3.5/src/buffer.o -Wno-write-strings
  cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
  In file included from src/buffer.cpp:12:0:
  src/pyodbc.h:56:10: fatal error: sql.h: No such file or directory
   #include <sql.h>
            ^~~~~~~
  compilation terminated.
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for pyodbc
  Building wheel for pyodbc (setup.py): finished with status 'error'

Thanks!
Jay

Do you strictly need pyodbc for building the documentation and is there no pre-built version of it? We would need to have some C libraries installed on the build docker images to be able to build it from source.

I was able to remove the pyodbc, pymysql & aiomysql dependencies and get the docs to build.

Thanks! I'm closing it as resolved.


have Java.version return null if java --version fails or cannot be run

Summary
Fixes https://github.com/flutter/flutter/issues/139180, where flutter create could crash if the java binary the tool found cannot be run.
Context
At startup, the tool searches for a Java installation[^1]. Unless the located installation is from an Android Studio installation, the tool does not verify that the binary is runnable. For more, see https://github.com/flutter/flutter/issues/139613, which tracks this inconsistency in behavior.
This means that in the scenario where

the user does not have Android Studio installed or the java binary found within cannot be run and
the user has a) flutter config --jdk-dir set, b) JAVA_HOME set in their environment, or c) java on their system path and
the java binary we think we found during cannot be run (or java --version fails), then

the user running flutter create with Android enabled will hit a tool crash.
Change
Java.version should return null if version checking fails for any reason. This is documented behavior. Therefore, we'll update the implementation to first verify that the binary is runnable. If it isn't, it will return null.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on [Discord].

[^1]: We find java by calling the static Java.find, see: https://github.com/flutter/flutter/blob/48187028c11ca8ca10e0179705d25553e1fe2c14/packages/flutter_tools/lib/src/context_runner.dart#L271
[^2]: This PR doesn't change this, as this would be too dangerous to cherry-pick into stable.

So after this change what will happen during the flutter create workflow?

So after this change what will happen during the flutter create workflow?
Oops, I forgot to discuss this. See https://github.com/flutter/flutter/issues/139180#issuecomment-1843747490 for context. Basically, this change would make the tool not check compatibility during flutter create if Java is unavailable. However, I think you're onto something here. Maybe we should print a warning when flutter create includes Android but Java cannot be run. We could also throwToolExit if we want to be more opinionated about it.

One question I have is: is flutter create the only time we check for Java compatibility? If it is, we indeed want to make this a ToolExit. However, if it's not, to keep this change as easy to cherry-pick as possible, a warning about Java being unavailable could suffice. I will follow up in the android channel in discord.

And would it not be better to check this in Java.find() and throwToolExit there if we resolved to a path that COULDN'T be run?

Maybe we should, but such a drastic change could be dangerous to cherry-pick. I've filed https://github.com/flutter/flutter/issues/139613 to track this.

So after this change what will happen during the flutter create workflow?
Oops, I forgot to discuss this. See #139180 (comment) for context. Basically, this change would make the tool not check compatibility during flutter create if Java is unavailable. However, I think you're onto something here. Maybe we should print a warning when flutter create includes Android but Java cannot be run. We could also throwToolExit if we want to be more opinionated about it.

One question I have is: is flutter create the only time we check for Java compatibility? If it is, we may want to make this a ToolExit. However, if it's not, to keep this change as easy to cherry-pick as possible, a warning about Java being unavailable could suffice. I will follow up in the android channel in discord.

And would it not be better to check this in Java.find() and throwToolExit there if we resolved to a path that COULDN'T be run?

Maybe we should, but such a drastic change could be dangerous to cherry-pick. I've filed #139613 to track this.

Ahh yes, this is a good point. I will approve this as is so we can cherry-pick it to the release and avoid crashes. Any other types of changes we probably wouldn't want to cherry-pick, and thus should happen in a later change.


[Migration Policies]: Move helper functions out of API package & stop using "LabelSelector"

What this PR does / why we need it:
After this PR:

Helper methods for migration policies will be moved away from API package
Instead of using LabelSelector (whish is essentially a struct with map[string]string field for matching labels and []LabelSelectorRequirement for requirements), now the selectors are defined to be map[string]string, without the requirements part, as it is now being ignored.

This PR addresses these comments, see them for more info.
Release note:

NONE

/cc @rmohr

/retest

/test pull-kubevirt-e2e-kind-1.22-sriov

Thanks @iholder-redhat This PR merely improves the code quality and doesn't change the logic. /approve
/cc @xpivarc please take a look as well.

@xpivarc ping

Thanks @iholder-redhat This PR merely improves the code quality and doesn't change the logic. /approve
/cc @xpivarc please take a look as well.

@vladikr  This does change the API, right?

Thanks @iholder-redhat This PR merely improves the code quality and doesn't change the logic. /approve
/cc @xpivarc please take a look as well.

@vladikr This does change the API, right?

Let me explain.
Previously we used metav1.LabelSelector as the type for label selectors. The struct has two fields and is defined in the following way (I've removed json metadata & comments for clarity):
type LabelSelector struct {
	MatchLabels map[string]string
	MatchExpressions []LabelSelectorRequirement
}

Currently, the "MatchExpressions" field is ignored. So it is part of the API, but a part that is redundant and should be deleted. IOW this change does not add any capabilities or anything like that, just protects the user from using something that would later be completely ignored.
Also, I'd like to stress out that this package is v1alpha1, which means that by definition its API is not stable yet.

Thanks @iholder-redhat This PR merely improves the code quality and doesn't change the logic. /approve
/cc @xpivarc please take a look as well.

@vladikr This does change the API, right?

Let me explain. Previously we used metav1.LabelSelector as the type for label selectors. The struct has two fields and is defined in the following way (I've removed json metadata & comments for clarity):
type LabelSelector struct {
	MatchLabels map[string]string
	MatchExpressions []LabelSelectorRequirement
}

Currently, the "MatchExpressions" field is ignored. So it is part of the API, but a part that is redundant and should be deleted. IOW this change does not add any capabilities or anything like that, just protects the user from using something that would later be completely ignored.
Also, I'd like to stress out that this package is v1alpha1, which means that by definition its API is not stable yet.

I understand I just want confirmation from Vladik as it wasn't clear from the comment.
Otherwise
/lgtm
/hold

Thank @xpivarc!
/unhold


chore: update renovate config

I just applied change of https://github.com/unjs/defu/pull/56 to the template.
Should I apply this change to other unjs repositories too, where @nuxtjs is still used?

Should I apply this change to other unjs repositories too, where @nuxtjs is still used?

Sure thanks <3


[Enhancement] Inventory Changer Case Opening

Features to add and open cases and keys for inventory changer

You can now open cases (86e1c5ccf6606e26d88fc7d5c4ce4faeb144603b).


Performance idea: squeezing down file size

For the bike network tool, ultimately I'd like to work on and present some vision at a large scale -- like all of North or South Seattle (50-60MB right now, or 20 gzipped) or the whole area (270MB, or 100 compressed). The Map files are gigantic, but I have some ideas for paring this down and creating something smaller, containing less detail than what's needed for traffic simulation...

overall this method fetches and re-fetches lanes, intersections, turns, etc many times and winds up being nontrivial.

Not sure if you already decided against using CHs here, but maybe here it would help to be able to just update the weights of an input_graph instead of 'building' the entire graph again. Not sure though, because this would just mean we replace a list of (from, to, weight)s with a list of just weights.

Not sure if you already decided against using CHs here, but maybe here it would help to be able to just update the weights of an input_graph instead of 'building' the entire graph again

Luckily, #748 pretty much resolved this problem -- there was lots of redundant work happening when calculating the vehicle input graphs. Now this process is fast enough. I'm not sure updating the graph vs building from scratch would make much of a difference; the expensive thing is calculating each edge's weight.
Also, this issue is about a newer side-project to create a bike network planning tool (previewable at abstreet.s3-website.us-east-2.amazonaws.com/0.2.58/abstreet.html?--ungap&system/us/seattle/maps/udistrict.bin). There's no traffic simulation, so the usage patterns for pathfinding are very different. I'm still exploring the idea, but possibly the user will have a few sliders where they can tune parameters that make bike routes avoid hills or avoid stressful roads. Only one or two routes would be calculated using these new weights. So probably, just Dijkstra's makes much more sense here. But that's not known for sure -- I might discretize the routing preferences into just a few options, after doing some of the parameter tuning myself and finding values that produce subjectively good routes in some example areas I know well.


Add parameter for -no-lock option

http://www.aptly.info/doc/api/
The -no-lock option allows the CLI and HTTP API to be used concurrently.
It's set to false to maintain the current behaviour.
Requested in #53.

Looks fine. Bonus points for tests. Merge away.


TBOX 151: Test namespace imports

↪ Pull Request

Adds testing for proper namespacing of modules.
Fixes some modules that were not previously importable from the namespace

✔ PR Todo

[ ] Add documentation
[ ] Add examples
[ ] Ensure you are following the practices in the contributor guide and coding_standards

Use consistent and descriptive name conventions
Uses google-style docstrings
Uses versioned API/client methods only
Avoid global variables
Avoid giant try/catch
Don't use mutable default variables
Use a main() function in your scripts

[ ] Added/updated testing for this change (ensure you are testing any changes/new code!)
[ ] Update title to link to TBOX issue (i.e. start pull request title with TBOX-xx)
[ ] Approval from first code-reviewer
[ ] Approval from second code-reviewer (only required if a second reviewer has left comments)
[ ] Pass all checks

I don't think this testing fully resolves the issue.  After checking it out and manually removing from . import upstream from tamr_toolbox/utils/__init__.py, I am able to observe that
import tamr_toolbox as tbox
tbox.utils.upstream

causes the error
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'tamr_toolbox.utils' has no attribute 'upstream'

However, invoke test does not detect any problems.
I think it would be helpful to have a commit that intentionally causes this test to fail as a demonstration, followed by a commit correcting the error.


Support sm4 encryption algorithm

What problem does this PR solve?
Issue Number: close #5714
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

Supports Chinese national standard encryption algorithm SM4 for encryption at rest.

/rebuild

/rebuild

/run-all-tests

/rebuild

/run-all-tests

/run-unit-test

/run-build-release

/run-build-release

/run-build-release

/run-build-release

/run-build-release

/run-build-release

/run-build-arm64

/run-all-tests

/run-all-tests

@JaySon-Huang @flowbehappy @CalvinNeo PTAL

/rebuild

/run-all-tests

/run-all-tests

/merge


chore: updating version.go adding more detail to Agent function

we can't add client type because we are calling Agent() somewhere we don't have access to client type.

Fixes #823

please apply your changes on PR https://github.com/pactus-project/pactus/pull/825


Pool of host-emitters, plus DynamicConfig fix

... fixing 'shutdown before launch' NPE in DynamicConfiguration.
Looks like the multiple host emitters did solve our problem here.

And Ville, to your question:

Does the configurable actor wrap the sink or another actor? In the latter case should the RR be pushed down into that level?

The configurable actor does indeed wrap the Emitter.java actor, and indeed, the RR is pushed down to that level; that is, a pool of Emitters is being created. There are no more actors beneath the Emitters.

Regarding my question your original proposal seemed to leave open the possibility of creating multiple configurable proxy actor instances. So I was asking if the RR should be of emitters inside the proxy which is what you have done here. No concerns about this (other than the comments above).

Comments addressed, thanks Ville, and sorry for the delay.

Matt looks good to me. I am concerned that this does not fix the NPE so much as avoids it. As I have not seen this issue before, if you are able to reproduce it could you file another issue with a description of how this happens that would be appreciated. I'll merge this once I am at a computer.
Ville
Sent from my iPad

On Jul 27, 2016, at 2:21 PM, Matthew Hayter<EMAIL_ADDRESS>wrote:
Comments addressed, thanks Ville, and sorry for the delay.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

VIlle - great, thanks; lodged issue #26 regarding the 'root cause' of the NPE.


Fixes AClient to work under Windows

Fixes issues: #66 , #68

Please check that this still works under Linux.

I confirmed that this works under Linux (VMWare instance).

Thanks for the patch! We need to test this under Linux before merging

Ooops missed that second comment, I think we are good to merge

Verified still works under Linux: "python3 examples/blinky.py"

Thanks for your patch!

I will close #66 and #68 once I can test on Thursday.


Pipeline repository name

Description: Add a new pipeline.repository.name read-only pipeline variable containing the name of the repository in which the pipeline is defined.
Related issue

Is this already added to the documentation?


Fix HASS Code

While upgrading to app-template v2, I was having issues getting the code server part back up and running. This issue is to remember to fix it.

Issue with ReadWriteMany PVC being created.
failed to provision volume with StorageClass "ceph-block": rpc error: code = InvalidArgument desc = multi node access modes are only supported on rbd `block` type volumes

Waiting for a volume to be created either by the external provisioner 'rook-ceph.rbd.csi.ceph.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.

This is fixed now.


More updates to Dutch translation

Updated capitalization according to readme
Changed formal to informal language, according to readme
Grammar fixes

Thank you for the update!


Fix resource picker regression

ref-counted types weren't being referenced properly before calling set_script()
fixes https://github.com/godotengine/godot/issues/69356

As discussed in #70311, this kind of issue warrants discussing the underlying problem of RefCounted vs Object */Variant, but for the short term this PR is a good fix.

Thanks!


Error: "Invariant Violation: scrollToIndex out of range: requested index 228 is out of 0 to 148"

Hi, I use react-native-element-dropdown. Data for displaying in dropdown counts about 300 items. From time to time I receive error : "Invariant Violation: scrollToIndex out of range: requested index 228 is out of 0 to 148" when I use search.
Here is code
`

  {renderLabel()}
  <Dropdown
    dropdownPosition={'bottom'}
    // flatListProps={}
    selectedTextProps={{
      numberOfLines: 1,
    }}
    style={[styles.dropdown]}
    containerStyle={styles.listOfitems}
    placeholderStyle={styles.placeholderStyle}
    selectedTextStyle={styles.selectedTextStyle}
    // iconStyle={styles.iconStyle}
    data={L}
    autoScroll
    labelField="label"
    valueField="value"
    placeholder={!isFocus ? t('Choose a branch') : '...'}
    value={choosenBranch}
    onFocus={() => setIsFocus(true)}
    onBlur={() => setIsFocus(false)}
    onChange={async item => {
      setChoosenBranch(item.value);
      setIsFocus(false);
    }}
    renderItem={item => renderItem(item)}
    search
    // searchField="value"
    searchPlaceholder={t('Search...')}
    inputSearchStyle={styles.inputSearchStyle}
    maxHeight={350}
  />
</View>`

"react-native": "0.70.5",
"react-native-element-dropdown": "^2.3.0",

Is there any way to fix this?

@jonqwerty Have you been able to solve this? Facing same issue

https://github.com/HERYORDEJY-DEV
I didn't solve this problem, but I avoided it. As I understand it, this error occurs when autoscrolling to the selected item and when the length of the list is more than 50 items (determined experimentally).
How to avoid it:  autoScroll={false}. But then autoscroll will not be working :)

hi @jonqwerty @HERYORDEJY-DEV ,
This error happen in version 2.8.1?

@hoaphantn7604
No, this error happen in version 2.3.0
"react-native-element-dropdown": "^2.3.0"

@hoaphantn7604 No, this error happen in version 2.3.0 "react-native-element-dropdown": "^2.3.0"
Did you try again on version 2.8.1?

@hoaphantn7604
I try version 2.8.1 and receive the same error:

I have the same issue, on the 2.9.0 version.
The other workaround would be to provide getItemLayout in flatListProps:
flatListProps={{
  getItemLayout: (data, index) => ({
    length: itemHeight,
    offset: itemHeight * index,
    index,
  }),
}}

@wilkuintheair can you help me fix this error. i can't find flatListProps

Same error happening with<EMAIL_ADDRESS>getting this error please help.

@HERYORDEJY-DEV
I didn't solve this problem, but I avoided it. As I understand it, this error occurs when autoscrolling to the selected item and when the length of the list is more than 50 items (determined experimentally).
How to avoid it: autoScroll={false}. But then autoscroll will not be working :)

Did you find any other way to fix this code even i am getting the same error

I placed the problem code in try catch.it stops the crash ===>
try{
refList?.current?.scrollToIndex({
index: index,
animated: false,
});
}
catch(e){
console.log("error===>",e)
}
in scrollIndex function

The solution that worked for me is
add this prop in your dropdown, where itemHeight = 50.
This hack is surely gonna work.
flatListProps={{
getItemLayout: (data, index) => ({
length: itemHeight / data?.length,
offset: itemHeight * (index),
index,
}),
}}
Also apply add height to your dropdown style. I have added
style = {{ height: 55 }}

The solution that worked for me is
add this prop in your dropdown, where itemHeight = 50.
This hack is surely gonna work.
flatListProps={{
getItemLayout: (data, index) => ({
length: itemHeight / data?.length,
offset: itemHeight * (index),
index,
}),
}}
Also apply add height to your dropdown style. I have added
style = {{ height: 55 }}

add autoScroll={false}

The solution that worked for me is
add this prop in your dropdown, where itemHeight = 50.
This hack is surely gonna work.
flatListProps={{ getItemLayout: (data, index) => ({ length: itemHeight / data?.length, offset: itemHeight * (index), index, }), }}
Also apply add height to your dropdown style. I have added style = {{ height: 55 }}

how to add this code in dropdown


Upload new inversion data to work with

@dccowan you mention that you have new data you want to work with on the inversion notebook. Feel free to replace the files in data. You'll also have to update the hash value for each one of them. But that's easy, you can run those cells with known_hash=None and the retrieve function will print it out for you: https://www.fatiando.org/pooch/latest/retrieve.html .
If you happen to change their names, then remember to update them also in the notebook while downloading it.

I'm closing this since @dccowan already fixed it.


testEnvLocalK8S script has configurable etcd datadir

@rosenhouse: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
1072887a84c48d76d2a7012c3a581dffe9801d64
link
/test istio-pilot-e2e

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

/test istio-pilot-e2e

@rosenhouse: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
d021f132df97809c2260e5671fd4ae7d7708e5e9
link
/test istio-pilot-e2e

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

/test istio-pilot-e2e

/assign @costinm
cc @rshriram

@rosenhouse: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
d021f132df97809c2260e5671fd4ae7d7708e5e9
link
/test istio-pilot-e2e

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


Dot error and docs

Two fixes

We raise a more informative errors to guide users to install pydot if they try to visualize a graph
We replace mentions of blockshape/blockdims with chunks in docs

Fixes #255
cc @koldunovn

LGTM


$accesstoken variable in Run-TestsInBcContainer

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
I am currently migrating our BC Containers from -auth UserPassword to -auth AAD.
I am not sure on how to generate an access token for a specific user for a local BC instance running in Docker container.
I have already tried passing WebAccessKey as access token, it didn't work.
Scripts used to create container and cause the issue
Run-TestsInBcContainer `
    -containerName $ContainerName `
    -tenant $TenantId `
    -companyName $runTestsInCompany `
    -credential $credential `
    -accessToken $tenantpassword ` # this is the webaccesskey
    -XUnitResultFileName $xunitResultsFile `
    -extensionId $app.AppId `
    -disabledTests $disabledTests

Full output of scripts
Currently not applicable.

Screenshots
If applicable, add screenshots to help explain your problem.
Currently not applicable.
Additional context

does it happen all the time?
Yes, on containers built using -auth AAD
did it use to work?
Yes, on containers built using -auth UserPassword

Freddy. are there any known solutions to make Run-TestsInBcContainer work on local AAD containers?

For AAD auth, you should use New-BcAuthContext and then use that.
This should work towards local AAD containers as well (with the right parameters), but I haven't tried.
If it doesn't work, I will fix the errors.

@freddydk In the case of $credential, we are creating below token headers:
$TokenRequestParams = @{
    Method = 'POST'
    Uri    = "$($authority.TrimEnd('/'))/oauth2/token"
    Body   = @{
        "grant_type" = "password"
        "client_id"  = $ClientId
        "username"   = $credential.UserName
        "password"   = [System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($credential.Password))
        "resource"   = $Resource
    }
}

Do we need clientID to be passed for local container with AAD auth?
I am under the impression that New-BcAuthContext is not designed to generate access tokens for local AAD containers.
If you can give me any pointers on this issue, I'll be happy to do the testing and submit a pull request.

@freddydk Hi Freddy, any update on when we can have the ability to run Tests on containers with AAD auth?

Hope to be able to look at this next week.

@freddydk We are still looking forward to this.
I have been digging the Run-TestsInContainer.Ps1 and PsTestTool.ps1 to find any workarounds.
So far I was able to accomplish this:

I created a user inside tenant.
Generated WebServicesKey for it.
Declared serviceurl and credentials variable.
$serviceurl = "https://vjaad:443/BC/cs?tenant=tnt1"; $tenantcredential =<EMAIL_ADDRESS>$(ConvertTo-SecureString -String "WebServicesKeyPlaceholder" -AsPlainText -Force))
Imported needed assemblies using Add-Type.
Microsoft.Dynamics.Framework.UI.Client.dll Newtonsoft.Json.dll
Opened ClientContext successfully.
$clientcontext = [ClientContext]::new($serviceurl, $tenantcredential)
Fails while opening form.
$clientcontext.OpenForm("130455")
ERROR DIALOG: You do not have access to . Verify that you have been set up as a valid user in .

WebServiceKey is for web service access.
Run-TestsInBcContainer uses client services and emulates a user session - web service key cannot be used for that.
I am working on this right now and it should be done some time this week.
It did require quite some work (rewrite of bcauthcontext to use oauth2 v2.0) - but in the latest containerhelper pre-release version, it actually should work. I can run this on my machine (with the latest containerhelper prerelease):
$containerName = "bcserver"
$licenseFile = $LicenseFileSecret.SecretValue | Get-PlainText
$credential = New-Object pscredential -ArgumentList 'admin', $PasswordSecret.SecretValue
$artifactUrl = Get-BCArtifactUrl -country us -type OnPrem
$aadCredential = New-Object pscredential -ArgumentList ($AadUserNameSecret.SecretValue | Get-PlainText), $AadPasswordSecret.SecretValue

$useSSL = $true
$params = @{ "useSSL" = $useSSL }
if ($useSSL) {
    $protocol = "https://"
    $params += @{
        "isolation" = "hyperv"
        "installCertificateOnHost" = $true
    }
}
else {
    $protocol = "http://"
}

$aadTenant = $aadCredential.UserName.Split('@')[1]
$appIdUri = "$protocol$containerName.$aadTenant/BC"

$AdProperties = Create-AadAppsForBC `
    -AadAdminCredential $aadCredential `
    -appIdUri $appIdUri `
    -publicWebBaseUrl "$protocol$containerName/BC" `
    -PreAuthorizePowerShell

New-BcContainer @params `
    -containerName $containerName `
    -accept_eula `
    -artifact $artifactUrl `
    -auth AAD `
    -Credential $credential `
    -licenseFile $licenseFile `
    -includeTestToolkit -includeTestFrameworkOnly `
    -updatehosts `
    -AuthenticationEMail $AadCredential.UserName `
    -AadAppId $AdProperties.SsoAdAppId `
    -AadAppIdUri $appIdUri

$authcontext = New-BcAuthContext -credential $aadCredential -scopes "$appIdUri/" -tenantID $aadTenant
Run-TestsInBcContainer -containerName $containerName -bcAuthContext $authContext

@freddydk Referring to this code I integrated the needful changes on my functions.
I confirm that I was now able to run Tests on AAD containers.
Thanks much Freddy, as always.


Difference between SN-Noop and nothing

if SN-Noop does nothing, then why include it? There must be a difference between having this technical profile somehwere and not having at all, but what?

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

ID: 8a542986-5eda-2cdd-180a-ecdd748b6ef6
Version Independent ID: d535e4db-5f33-ab9b-9196-6a1e0c7a551b
Content: Single sign-on session management using custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/custom-policy-reference-sso.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@Ponant Thanks for the question! We will review and get back to you!

@Ponant This is answered by Jas here.
SM-Noop explicitly states to not include the technical profile as part of the session. If session management technical profile reference is absent from a technical profile, the result should be the same, but better to be explicit.

@Ponant I have updated the document to include this information. It will be published after review by the author.


You have requested downloading the video partially, but ffmpeg is not installed

I'm facing this error when using example app:
You have requested downloading the video partially, but ffmpeg is not installed. Aborting
This is because of this line in python ffmpeg handler:
raise FileNotFoundError(errno.ENOENT, os.strerror(errno.ENOENT), args[0])

When I remove the line, it run through communicate function but after all it throws AttributionError:
Popen.__init__: <yt_dlp.utils.Popen object at 0x126d28160> (['ffmpeg', '-bsfs'],)
Popen.communicate: <yt_dlp.utils.Popen object at 0x126d28160> () {'timeout': None}
Popen.kill: <yt_dlp.utils.Popen object at 0x126d28160>
Popen.wait: <yt_dlp.utils.Popen object at 0x126d28160> {'timeout': None}
ERROR: 'Popen' object has no attribute '_Pop__args'

Please explain the python handler code, I have very little knowledge about python @kewlbear, thanks!

@kientux Thanks for reporting!  Fixed it.  Please update YoutubeDL-iOS package.


Mirror device version and usb version in descriptors

Devices presented over usbip should have their descriptors are mirrored in their entirety. This include USB version and bcdDeviceVersion.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 34 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 41.66%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/lib.rs
0
2
0.0%

src/device.rs
17
32
53.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
542

Relevant Lines:
1301

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

17 of 34 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 42.373%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/lib.rs
0
2
0.0%

src/device.rs
17
32
53.13%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
525

Relevant Lines:
1239

💛  - Coveralls


fixed 2096

Fixes #2096
First time playing with Scala 3 derivation. Apologize in advance for potential silly mistake.

You need to employ the same strategy in the Encoder otherwise the discriminator will not have the correct value.

You need to employ the same strategy in the Encoder otherwise the discriminator will not have the correct value.

I think the new implementation addressed this concern.

@kailuowang, thanks for the work on this!  The tests appear to be hanging for Scala 3 in CI, mind taking a look?  I tried locally and got the same result.

@kailuowang, thanks for the work on this! The tests appear to be hanging for Scala 3 in CI, mind taking a look? I tried locally and got the same result.

@zarthross thanks! I think it's fixed (weird it didn't hang for me before)

@zarthross, I just added a test for recursive ADT. Looks to me that it's ready for merge?

Thanks @kailuowang

Thanks @kailuowang

Thank you! Is there, by any chance, a release scheduled in the near future?


"codePageRanges" custom parameter results in temp file being unreadable

If a file has the codePageRanges custom parameter set, the following error occurs:
Loading Glyphs file failed: invalid literal for int() with base 10: 'bit 29'

This is a problem with glyphsLib, not the plugin.


[Bug] [Worker] 数据补数时日期计算错误

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

${system.biz.date}
日常调度实例定时的定时时间前一天，格式为 yyyyMMdd，补数据时，该日期 +1

以上内容拷贝自官方文档
没太搞明白为啥补数要+1的操作
在补数据时对日期+1的操作，会导致传入脚本的日期+1，从而无法获取正常结果，特别调度任务是在周调度、月调度等不适连续天调度执行的情况下，在此情况我只能通过修改调度时间或者用其他方式实现补数
What you expected to happen
在补数时，该变量应该遵循定义的值，不应该+1
How to reproduce
在补数时，该变量应该遵循定义的值，不应该+1
Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@lenboo Could you please take a look is this issue related to PR https://github.com/apache/dolphinscheduler/pull/6389

@XiaoYoungk
For the convenience of communication, please use English title and content.

To facilitate communication, please use English titles and content.
When you modify it, you can reopen it.


Fails with Invalid OAuth token

Version<EMAIL_ADDRESS>Code:
Spotilocal = require('spotilocal').Spotilocal

const spotilocal = new Spotilocal()
const trackUri = 'spotify:track:5S81KTmjVTeXxVhtBVUm9k'
spotilocal.init().then(spotilocal => {
    return spotilocal.play(trackUri)
}).then(status => {
    console.dir(status)
}).catch(console.error)

Error:
{ error: { type: '4102', message: 'Invalid OAuth token' },
  version: 9,
  client_version: '<IP_ADDRESS>9.g4ab01679',
  running: true }

Unfortunately, this project will no longer work. Added DEPRECATED warning to description.

@ShyykoSerhiy Maybe it's better to add your project to the archive?


Panic for resources.GetMatch(“https://picsum.photos/400/300.webp”) on Windows

See https://discourse.gohugo.io/t/bug-panic-for-resources-getmatch-https-picsum-photos-400-300-webp-on-windows/43048.
Note: This issue is about fixing Hugo so the panics don't happen at all, and so that behavior is consistent across Mac, Linux, and Windows. The fact that there's a workaround is irrelevant. GetMatch shouldn't panic when given a URL.
This issue is also about having Hugo print the actual panic stack trace so it's easier to debug situations like this. There's nothing actionable about the nil reference message without any context.
What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.110.0+extended darwin/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes

These are the patterns that are not Windows-friendly:
FAIL (error 1)
{{ resources.GetMatch ":/a" }}
{{ resources.GetMatch "a:/a" }}

FAIL (error 2)
{{ resources.Get ":" }}
{{ resources.Get ":/" }}
{{ resources.Get "a:" }}

FAIL (error 3)
{{ resources.Get "/" }}

error 1 : error calling GetMatch: runtime error: invalid memory address or nil pointer dereference
error 2: executing "main" at <resources.Get>: error calling Get: CreateFile C:\Users\joe\Code\hugo-testing\assets:: The filename, directory name, or volume label syntax is incorrect.
error 3: executing "main" at <resources.Get>: error calling Get: dirs not supported resource types

These all work fine on Windows

PAGE RESOURCE

{{ .Resources.GetMatch ":" }}
{{ .Resources.GetMatch ":/" }}
{{ .Resources.GetMatch ":/a" }}
{{ .Resources.GetMatch "/" }}
{{ .Resources.GetMatch "/a" }}
{{ .Resources.GetMatch "a:" }}
{{ .Resources.GetMatch "a:/" }}
{{ .Resources.GetMatch "a:/a" }}
{{ .Resources.GetMatch "a:a" }}
{{ .Resources.GetMatch "a" }}

{{ .Resources.Get ":" }}
{{ .Resources.Get ":/" }}
{{ .Resources.Get ":/a" }}
{{ .Resources.Get "/" }}
{{ .Resources.Get "/a" }}
{{ .Resources.Get "a:" }}
{{ .Resources.Get "a:/" }}
{{ .Resources.Get "a:/a" }}
{{ .Resources.Get "a:a" }}
{{ .Resources.Get "a" }}

GLOBAL RESOURCE

{{ resources.GetMatch ":" }}
{{ resources.GetMatch ":/" }}
{{ resources.GetMatch "/a" }}
{{ resources.GetMatch "a:" }}
{{ resources.GetMatch "a:/" }}
{{ resources.GetMatch "a:a" }}
{{ resources.GetMatch "a" }}

{{ resources.Get "/a" }}
{{ resources.Get "a:/" }}
{{ resources.GetMatch "a:a" }}
{{ resources.GetMatch "a" }}

it's confidential because its family matters. i don't know what really the hugo is, but i will give some history. but first can i ask if i can point brand?


Fix/create groups UI

Merging after creating group configuration

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


updateLink versioned extension regression on dev/build

Affected Version
3.x-dev
Description
When running a dev/build via the browser on an empty database (or specifically without any ErrorPage records when using the CMS module) the user is logged out and sent back to /Security/login?BackURL=%2Fpage-not-found%2F%3Fstage%3DStage
Expected behaviour: for dev/build to complete successfully.
I've narrowed this down to the following:

DevelopmentAdmin::init() calls Versioned::reading_stage('Stage'); (https://github.com/silverstripe/silverstripe-framework/blob/47a9cdfd49146e769760e8d8db3f01925597de41/dev/DevelopmentAdmin.php#L76-L79)
VersionedStateExtension::updateLink() appends stage=Stage to links when the object was queried from the draft stage (https://github.com/silverstripe/silverstripe-framework/blob/47a9cdfd49146e769760e8d8db3f01925597de41/model/VersionedStateExtension.php#L23-L48), this means switching stages after the object has been fetched (and possibly published) won't fix the problem and ?stage=Stage will still be appended to the URL.
ErrorPage::requireDefaultRecords() uses Director::test() to "statically publish" the error pages it generates (https://github.com/silverstripe/silverstripe-cms/blob/12826b2ace76808d29b5017e1f445514b7fcf62a/code/model/ErrorPage.php#L116)
VersionedRequestFilter::preRequest() takes outputting responses into it's own hands instead of returning a boolean response
VersionedRequestFilter::preRequest() saves the dummy session from Director::test() which causes the current session to be invalidated and the user logged out

Steps to Reproduce

Create a vanilla 3.x-dev site or delete the error pages from the CMS
Go to dev/build in the browser

Potential fix
I've fixed this locally by wrapping the ErrorPage::requireDefaultRecords() logic in Versioned::reading_stage(Versioned::LIVE); which fixes the specific error, but I feel this only resolves part of the issue.
Another fix could be to strip the ?stage query param from $page->Link() in ErrorPage::requireDefaultRecords()

I've opened this against framework instead of CMS because most of the root issues are in framework and the PR to framework caused this regression
PRs:

[ ] https://github.com/silverstripe/silverstripe-framework/pull/8122
[ ] https://github.com/silverstripe/silverstripe-cms/pull/2181

I've fixed this with the suggested adjustment, but also reset the "default" stage to draft in dev/build in order to prevent other links being generated with querystring args. This is the same approach we used in LeftAndMain to prevent stage args in the CMS.


[Update] Simplify login check and always set active account cookie

#4442  👈
main

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

Join @jnsdls and the rest of your teammates on  Graphite


can't successfully install odin-lang/Odin (IO error)

Error: unhandled exception: cannot open: /home/sharpcdf/.jitter/nerve/odin-lang::odin::dev-2022-08/core/odin/printer/ [IOError]

was an error with the dependency, not jitter itself

was an error with a dependency, not jitter itself


doc: release-notes-3.7: Add Ezurio release notes

Laird Connectivity boards were rebranded to Ezurio.

Thanks for the reminder @kartben. Already got a mention there: https://github.com/zephyrproject-rtos/zephyr/blob/main/doc/releases/migration-guide-3.7.rst#boards


[TASK]: ARKWORKS: Simplify traits for CRH and Merkle tree

Overview
Due to the overwhelming complexity of traits defined in arkworks-gadgets, I'm proposing to massively simplify traits for the Merkle tree and hash function, in the following way:
CRH:
struct Poseidon<F: PrimeField> {
   params: PoseidonParameters<F>,
}

impl Poseidon<F: PrimeField> {
    fn new(params: PoseidonParameters<F>) -> Self;
}

trait FieldHasher<F: PrimeField> {
	fn hash(&self, inputs: &Vec<F>) -> F;
        fn hash_two(&self, left: &F, right: &F) -> F;
}

Path:
// Path
#[derive(Clone)]
pub struct Path<F: PrimeField, H: FieldHasher> {
	pub(crate) path: Vec<F>,
}

impl<F: PrimeField, H: FieldHasher> Path<F, H> {
	pub fn check_membership(
		&self,
		root_hash: &F,
		leaf: &F,
		params: &H::Parameters,
	) -> Result<bool, Error>;

	pub fn calculate_root(&self, leaf: &F) -> Result<F, Error>;
}

Merkle tree:
/// Merkle sparse tree
pub struct SparseMerkleTree<F: PrimeField, H: FieldHasher> {
	/// data of the tree
	pub tree: BTreeMap<u64, F>,
	empty_hashes: Vec<F>,
	height: u8,
  _hasher: PhantomData<H>
}

impl<F: PrimeField, H: FieldHasher> SparseMerkleTree<F, H> {

	pub fn insert_batch(
		&mut self,
		leaves: &BTreeMap<u32, F>,
		params: &H::Parameters,
	) -> Result<(), Error>;

	pub fn new(
		leaves: &BTreeMap<u32, F>,
		params: &H::Parameters,
	) -> Result<Self, Error>;

	pub fn new_sequential(
		leaves: &[F],
		params: &H::Parameters,
	) -> Result<Self, Error>;

	pub fn root(&self) -> F;

	pub fn generate_membership_proof(&self, index: u64) -> Path<F>;
}

Checklist

[ ]  Implement simplified Path struct

[ ]  Update Sparse Merkle tree to use new Path

[ ]  Implement simplified sparse Merkle tree

[ ]  Fix all the occurrence of SMT and Path

[ ]  Implement FieldHasher and FieldHasherGadget for Poseidon — do not delete CRH impl

[ ]  Replace all occurrences of CRH with FieldHasher

[ ]  Leaf gadgets
[ ]  SMT + Path
[ ]  Circuits

[ ]  ADDITIONAL TASK: Remove old Poseidon implementation, just leave Circom version from circom folder

Issues
Linked tasks

@GhostOfGauss Spec is updated. Please just do the Poseidon part first and open a PR, so I an review it properly