ServiceNow only showing "Everyone" in permissions step

As documented here, the ServiceNow connector should offer two different options in the Manage search permissions step :

Everyone
Only people with access to this data source

However the only option I see is Everyone. The documentation also states the following :
The ServiceNow connector is in preview if you choose Only people with access to this data source.

Does that mean I have to enable preview functionalities somewhere in order to be able to see this option?!?
Thanks!

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

ID: a5175b51-8cee-6432-325e-216310e9ecb0
Version Independent ID: a75c2239-2a07-e901-ac78-4dcde7bd197b
Content: ServiceNow Graph connector for Microsoft Search
Content Source: MicrosoftSearch/servicenow-connector.md
Service: mssearch
GitHub Login: @mecampos
Microsoft Alias: mecampos

Hello @spplante , the "Only people with access to this data source" option is in preview for a limited group of clients at this point, and it will be open for a wider audience via targeted release in the next weeks.
You can adopt it in your tenant if you opt-in for targeted release updates.

@mecampos  Yes I opened a ticket with Microsoft and they just confirmed me this. It would be useful to mention this in the documentation because currently it does say this option is in preview but nothing says it's still in development and not available even for targeted release tenants, it kinda is misleading as we speak :(
Thanks!

Thank you very much for the feedback and suggestion @spplante.


fix nest ng-sortable bug

See also: http://jsbin.com/xecamoqaqo/1/
If you drag a sub item, the item will append to $scope.items, not sort in item.elems

same problem here, fix by this pull request, pleas merge it ASAP!

:+1:

Hi, I have the same problem. However this PR doesn't seem to have solved it, the DOM works fine, but the scopes aren't managed to sync with it.

Try dev-branch.


Change stripe size limit units from MB to GB

100,000 MB references can be changed to 100 GB to arguably increase readability without doing a quick conversion.

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

ID: 6e9b99dc-4e63-75a7-a6ed-ea635159c01e
Version Independent ID: 6e9b99dc-4e63-75a7-a6ed-ea635159c01e
Content: Back up to URL best practices & troubleshooting for S3-compatible object storage - SQL Server
Content Source: docs/relational-databases/backup-restore/sql-server-backup-to-url-s3-compatible-object-storage-best-practices-and-troubleshooting.md
Service: sql
Sub-service: backup-restore
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

@nanoDBA -- thank you for your suggestion.  I'll update the article.


Support for Firefox

Hello,
at the moment, this component doesn't work in Firefox. Picker opens on mousedown, but closes immediately on mouseup.
Browser: Firefox 56
OS: Linux

Thank you, will test and fix it in the nearest release

My colleague also has this problem with Firefox on Linux. With Firefox on MacOS, I don't have this problem.

The firefox issues are still present on linux with newest beta.

Oh, will test it, thanks

@mfolnovic is the issue still present for you?
Seems like for me it's gone with latest beta (both material ui and material ui pickers)

firefox 58
material-ui-pickers 1.0.0-beta.7

For some reason, text color for year and numbers on dial are white.
Other than that, it works, awesome! :)

@mfolnovic Could you check latest beta here?
Looks like it works properly if FF now.

I'm closing this for now, feel free to reopen if it's still an issue


openai embedding custom url

The bge-m3 model is a local embedding model that surpasses openai's large embedding model. I would like to load this into a server compatible with openai API and use it in conjunction with chromadb. Therefore, it would be nice if users could use custom URLs when using the openai embedding feature in your project.
Thank you for your efforts,

https://github.com/michaelfeil/infinity
Please refer to the project

@codeMonkey-shin, PR is up. I'll create a new release later today

@codeMonkey-shin, this is now done an new version 0.1.4 is published:
https://central.sonatype.com/artifact/io.github.amikos-tech/chromadb-java-client/overview

thank you!


Anything i type in my terminal do not show

ADD ISSUE DESCRIPTION HERE
I am able to type in my code space but when am to run the code at the terminal anything I type at the terminal do not show
Version: 1.70.2
Commit: e4503b30fc78200f846c62cf8091b76ff5547662
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

does changing terminal.integrated.gpuAcceleration help?

Yes, it is working now. Thank you


Unbind gender field properly and improve javadoc

Changes Unknown when pulling 53a8a83cde8e9344187aa9b95251a25fd8ba53e9 on OscarWang114:fix-addli into ** on CS2103AUG2017-T13-B1:master**.


Error during switching to the colorscheme

When switching to the scheme by typing:
:colorscheme nightfall

I get this message:
Error detected while processing /home/kaczor/.local/share/nvim/lazy/nightfall.nvim/colors/nightfall.lua:
E5113: Error while calling lua chunk: ...al/share/nvim/lazy/nightfall.nvim/lua/nightfall/init.lua:106: attempt to concatenate field 'compile_path' (a nil value)
stack traceback:
        ...al/share/nvim/lazy/nightfall.nvim/lua/nightfall/init.lua:106: in function 'load'
        ...ocal/share/nvim/lazy/nightfall.nvim/colors/nightfall.lua:1: in main chunk

OS:
Ubuntu 24.4 (WSL),
Neovim version:
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1703358377

It appears that you might not have called the setup function, which is necessary for nightfall.nvim to work correctly.
Here's a snippet that demonstrates the correct installation of nightfall.nvim with lazy.nvim:
{
  "2giosangmitom/nightfall.nvim",
  lazy = false,
  priority = 1000,
  opts = { -- lazy.nvim will call setup() automatically
    -- Your custom options go here
  },
}

If you’ve followed this setup and the issue persists, please share more details about your configuration, so I can assist you further.


Netatmo-Energy adapter 2.6.0 added to stable

Netatmo-Energy adapter 2.6.0 added to stable repository

RE-CHECK!

2.6.0 released 01.05.2023
User 12 (9,4%)
no issues
OK


Broken Dockerfile example

Sample code
# Dockerfile
# Uses multi-stage builds requiring Docker 17.05 or higher
# See https://docs.docker.com/develop/develop-images/multistage-build/

# Creating a python base with shared environment variables
FROM python:3.10-slim as python-base
ENV PYTHONUNBUFFERED=1 \
    PYTHONDONTWRITEBYTECODE=1 \
    PIP_NO_CACHE_DIR=off \
    PIP_DISABLE_PIP_VERSION_CHECK=on \
    PIP_DEFAULT_TIMEOUT=100 \
    POETRY_HOME="/opt/poetry" \
    POETRY_VIRTUALENVS_IN_PROJECT=true \
    POETRY_NO_INTERACTION=1 \
    PYSETUP_PATH="/opt/pysetup" \
    VENV_PATH="/opt/pysetup/.venv"

ENV PATH="$POETRY_HOME/bin:$VENV_PATH/bin:$PATH"

# builder-base is used to build dependencies
FROM python-base as builder-base
RUN apt-get update \
    && apt-get install --no-install-recommends -y \
        curl \
        build-essential

# Install Poetry - respects $POETRY_VERSION & $POETRY_HOME
ENV POETRY_VERSION=1.2
RUN curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python

# We copy our Python requirements here to cache them
# and install only runtime deps using poetry
WORKDIR $PYSETUP_PATH
COPY ./poetry.lock ./pyproject.toml ./
RUN poetry install --no-dev  # respects

# 'development' stage installs all dev deps and can be used to develop code.
# For example using docker-compose to mount local volume under /app
FROM python-base as development
COPY --from=builder-base $POETRY_HOME $POETRY_HOME
COPY --from=builder-base $PYSETUP_PATH $PYSETUP_PATH

# venv already has runtime deps installed we get a quicker install
WORKDIR $PYSETUP_PATH
RUN poetry install

WORKDIR /app
COPY . .

FROM python-base as production
COPY --from=builder-base $VENV_PATH $VENV_PATH
COPY ./app /app
WORKDIR /app

Result
 > [builder-base 5/5] RUN poetry install --no-dev  # respects:
#10 0.383 /bin/sh: 1: poetry: not found

Sorry, my mistake. Fixed by removing ENV POETRY_VERSION=1.2.


some problems about branch:refactor/mv3 until 2022/11/22

Describe the bug
some problems about branch:refactor/mv3 until 2022/11/22
I downloaded the latest source code:
❯ npx degit antfu/vitesse-webext#refactor/mv3 antfu@vitesse-webext_mv3_202211

problem 1
there is a ERR_PNPM_FETCH_404 error when using pnpm to install.
❯ pnpm i
Lockfile is up-to-date, resolution step is skipped
Packages: +893
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 WARN  GET https://registry.npmjs.org/<EMAIL_ADDRESS>error (ERR_PNPM_FETCH_404). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/<EMAIL_ADDRESS>error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/<EMAIL_ADDRESS>Not Found - 404

No authorization header was set for the request.
Progress: resolved 893, reused 891, downloaded 0, added 0

but it's normal if turn to yarn.
problem 2
scripts/client.tsline:12
const socketHost = `localhost:3303`

the socket port is hardcoded, so If the port is set by env variables,  the follwoing error would occur:
client.ts:26

       WebSocket connection to 'ws://localhost:3303/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

problem3
HMR is not stable, sometimes the changed reflected immediately, but sometimes, the changes can't be rendered in time. especially when continuously change the code. I haven't found what's the problem is. @tmkx
Reproduction
reproduction
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel Core Processor (Haswell, no TSX, IBRS)
    Memory: 25.33 GB / 31.35 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
  Browsers:
    Chrome: 103.0.5060.53
    Firefox: 105.0

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Problem1. remove pnpm-lock.yaml and try install again
Problem2. could be solved
Problem3. HMR is unstable in MV3 as expected because the implementation is a little tricky, and that's why it's still not merged into main branch. needs more investigation.

@tmkx
problem4  error Uncaught SyntaxError: Cannot use import statement outside a module would occur when importing other modules.
for example, add such codes in background.ts
import axios from 'axios'

const axiosTest = () => {
  const baseURL = 'http://localhost:8080'
  const axiosInstance = axios.create({})
  return axiosInstance
}
console.log(axiosTest)

show:

Problem 4

The background script is bundled by tsup, it will external dependencies and peerDependencies, see the tsup doc.
To solve ①, you can install axios to devDependencies, or add noExternal: ['axios'] in tsup.config.ts.
There is another error: Adapter 'http' is not available in the build, try axios.create({ adapter: 'xhr' })
Still get Adapter xhr is not supported by the environment, because that XMLHttpRequest is not supported in background pages in MV3

@tmkx  so it means that axios can't be used in MV3?  and what about problem 5?

background script is not bundled by vite, there is no import.meta.hot and HMR.

It seems that axios is based on XHR, you can find a fetch-based alternative, or use fetch directly.

so how to use a background script to always inject the latest version of content-scripts in MV3, as as browsers would cache them for each reload

Maybe you can create a WebSocket connection to Vite server, cleanup & remount content-scripts to the page when receiving updates? It's not implemented yet.

@tmkx,  for problem 4, I have searched a similar issue which also got errors when bundling axios with tsup.  https://github.com/axios/axios/discussions/4842.  It explains it maybe caused by nodejs builtin modules when using for the browser. so I followed his instruction, firstly, add esbuild-plugins-node-modules-polyfill
 yarn add esbuild-plugins-node-modules-polyfill --dev

then , modify tsup.config.ts by adding:
import { nodeModulesPolyfillPlugin } from 'esbuild-plugins-node-modules-polyfill'
export default defineConfig(() => ({
...
  esbuildPlugins: [nodeModulesPolyfillPlugin()],
...
}))

this time, axios was bundled without any errors.
then, I tried to use axios to request something. Indeedly, the error "AxiosError: Adapter http is not supported by the environment you refered to occured.
{
    "message": "Adapter http is not supported by the environment",
    "name": "AxiosError",
    "stack": "AxiosError: Adapter http is not supported by the environment\n    at Object.getAdapter (chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:69518:15)\n    at Axios.dispatchRequest (chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:69554:36)\n    at Axios.request (chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:69803:33)\n    at Axios.get (chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:69822:17)\n    at Function.wrap [as get] (chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:54941:15)\n    at chrome-extension://hbidegeigejmmpppbdmbbmobgcingopm/dist/background/index.mjs:70515:15",
    "code": "ERR_NOT_SUPPORT",
    "status": null
}

so I found an  fetch adapter for axios to install:
yarn add @vespaiach/axios-fetch-adapter --dev

and use it in background.ts
import axios from 'axios'
import fetchAdapter from '@vespaiach/axios-fetch-adapter'
const axiosTest = () => {
  const axiosInstance = axios.create({ adapter: fetchAdapter })
  return axiosInstance
}
console.log(axiosTest)

but this time, new errors occured when bundling:
✘ [ERROR] Could not resolve "axios/lib/core/settle"

    node_modules/@vespaiach/axios-fetch-adapter/index.js:2:19:
      2 │ import settle from 'axios/lib/core/settle';
        ╵                    ~~~~~~~~~~~~~~~~~~~~~~~

  The path "./lib/core/settle" is not exported by package "axios":

    node_modules/axios/package.json:6:13:
      6 │   "exports": {
        ╵              ^

  You can mark the path "axios/lib/core/settle" as external to exclude it from the bundle, which
  will remove this error.

✘ [ERROR] Could not resolve "axios/lib/helpers/buildURL"

    node_modules/@vespaiach/axios-fetch-adapter/index.js:3:21:
      3 │ import buildURL from 'axios/lib/helpers/buildURL';
        ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./lib/helpers/buildURL" is not exported by package "axios":

    node_modules/axios/package.json:6:13:
      6 │   "exports": {
        ╵              ^

  You can mark the path "axios/lib/helpers/buildURL" as external to exclude it from the bundle,
  which will remove this error.

✘ [ERROR] Could not resolve "axios/lib/core/buildFullPath"

    node_modules/@vespaiach/axios-fetch-adapter/index.js:4:26:
      4 │ import buildFullPath from 'axios/lib/core/buildFullPath';
        ╵                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./lib/core/buildFullPath" is not exported by package "axios":

    node_modules/axios/package.json:6:13:
      6 │   "exports": {
        ╵              ^

  You can mark the path "axios/lib/core/buildFullPath" as external to exclude it from the bundle,
  which will remove this error.

✘ [ERROR] Could not resolve "axios/lib/utils"

    node_modules/@vespaiach/axios-fetch-adapter/index.js:5:62:
      5 │ import { isUndefined, isStandardBrowserEnv, isFormData } from 'axios/lib/utils';
        ╵                                                               ~~~~~~~~~~~~~~~~~

  The path "./lib/utils" is not exported by package "axios":

    node_modules/axios/package.json:6:13:
      6 │   "exports": {
        ╵              ^

  You can mark the path "axios/lib/utils" as external to exclude it from the bundle, which will
  remove this error.

Oh,my god! Why can't tsup  handle so common packages? It seems tsup can't resolve the path axios/lib/*.  I don't know what's wrong with it and how to fix it now, can you help me?

There is a solution:

It's no need to install esbuild-plugins-node-modules-polyfill, just set tsup.platform to browser(default node, I forgot to mention it yesterday)
@vespaiach/axios-fetch-adapter requires ^0.27.2(as devDeps), but it declared a ">=0.26.0" peer range, I guess that you've installed a 1.x version, it's not compatible.

pnpm add<EMAIL_ADDRESS>@vespaiach/axios-fetch-adapter -D

 // tsup.config.ts
 export default defineConfig(() => ({
+  platform: 'browser',
 }))

import axios from 'axios'
import fetchAdapter from '@vespaiach/axios-fetch-adapter'

const instance = axios.create({ adapter: fetchAdapter })
instance.get('https://httpbin.org/get').then(res => console.log(res.data))

@tmkx thanks for your suggestion, it's fixed. It's hardly to related to the compatible problem by the poor prompt! But it's tedious and labourious to be bundled by vite and tsup separately, as some scripts can't be reused for them together (such as import.meta.env). Is there a better alternative that only uses one bundle tool?  just like the mv2 template which only use vite.

background can run as HTML script in MV2, but it should be a service worker in MV3, it's different. take a look at the first refactor commit

@tmkx  Problem 6
when I imported an sass file, the error [sass] This file is already being loaded. occurred, but the same codes in MV2 template run well.
add in popup/main.ts
import 'quasar/src/css/index.sass'

errors when bundle:
/home/john/project/testscratch/typescript-demos/bex-demo-mv3/node_modules/.pnpm/sass@1.32.12/node_modules/sass/sass.dart.js:13172
      var error = new self.Error(message);
                  ^

Error: [sass] This file is already being loaded.
  ╷
1 │ @import '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass'
  │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  src/quasar-variables.sass 1:9  root stylesheet
    at Object._newRenderError (/home/john/project/testscratch/typescript-demos/bex-demo-mv3/node_modules/.pnpm/sass@1.32.12/node_modules/sass/sass.dart.js:13172:19)
    at Object._wrapException (/home/john/project/testscratch/typescript-demos/bex-demo-mv3/node_modules/.pnpm/sass@1.32.12/node_modules/sass/sass.dart.js:12998:16)
...
    at Object._rootRunBinary (/home/john/project/testscratch/typescript-demos/bex-demo-mv3/node_modules/.pnpm/sass@1.32.12/node_modules/sass/sass.dart.js:4749:18) {
  formatted: 'Error: This file is already being loaded.\n' +
    '  ╷\n' +
    "1 │ @import '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass'\n" +
    '  │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n' +
    '  ╵\n' +
    '  src/quasar-variables.sass 1:9  root stylesheet',
  line: 1,
  column: 9,
  file: '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass',
  status: 1,
  id: '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass',
  frame: 'Error: This file is already being loaded.\n' +
    '  ╷\n' +
    "1 │ @import '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass'\n" +
    '  │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n' +
    '  ╵\n' +
    '  src/quasar-variables.sass 1:9  root stylesheet',
  plugin: 'vite:css',
  pluginCode: "@import '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass'\n" +
    "@import 'quasar/src/css/variables.sass'\n" +
    '\n' +
    '\n' +
    '$primary   : #1976D2\n' +
    '$secondary : #26A69C\n' +
    '$accent    : #9C27B0\n' +
    '\n' +
    '$dark      : #1D1D1D\n' +
    '\n' +
    '$positive  : #21BA45\n' +
    '$negative  : #C10015\n' +
    '$info      : #31CCEC\n' +
    '$warning   : #F2C037',
  loc: {
    file: '/home/john/project/testscratch/typescript-demos/bex-demo-mv3/src/quasar-variables.sass',
    line: 1,
    column: 9
  }
}

Node.js v18.12.0
 ELIFECYCLE  Command failed with exit code 1.
ERROR: "dev:web" exited with 1.
 ELIFECYCLE  Command failed with exit code 1.

what's wrong with it?

Have you tried this https://quasar.dev/start/vite-plugin?

@tmkx  yes, I followed their instructions and modified following files.
pnpm add quasar @quasar/extras @quasar/vite-plugin<EMAIL_ADDRESS>-D

vite.config.ts
import { quasar, transformAssetUrls } from '@quasar/vite-plugin'
...
export const sharedConfig: UserConfig = {
  root: r('src'),
  resolve: {
    alias: {
      '~/': `${r('src')}/`,
    },
  },
  plugins: [
    Vue({
      template: { transformAssetUrls },
    }),
    quasar({
      sassVariables: r('src/quasar-variables.sass'),
    }),]
...
}
...

src/popup/main.ts
```ts
import { createApp } from 'vue'
// quasar
import { Quasar } from 'quasar'
import iconSet from 'quasar/icon-set/svg-material-icons'
// Import icon libraries
import<EMAIL_ADDRESS>import 'quasar/src/css/index.sass'
import App from './Popup.vue'
import '../styles'

const app = createApp(App)
app.use(Quasar, {

  iconSet,
}).mount('#app')

then pnpm run dev, the aforementioned errors appear.
I'm confused that for the same codes,  why mv2 boilerplate is ok, but mv3 not to bundle sass?

@tmkx , I searched two similar issues which haven't presented an answer yet.
[vue.js - Vue CLI 5 with Vuetify SCSS variables and CSS imports - Stack Overflow](https://stackoverflow.com/questions/71709928/vue-cli-5-with-vuetify-scss-variables-and-css-imports)
[javascript - SassError: This file is already being loaded. @import '~src/css/quasar.variables.scss', 'quasar/src/css/variables.sass'; src\css\quasar.variables.scss - Stack Overflow](https://stackoverflow.com/questions/68496522/sasserror-this-file-is-already-being-loaded-import-src-css-quasar-variables)

it seems that HMR does not work with quasar sass variables. I'm not familiar with quasar, you can use import 'quasar/dist/quasar.css' for dev while import 'quasar/src/css/index.sass' for build? I haven't had much time lately.

It's a good provisional way to resolve this problem ! Thanks,now I can go along it again!

@tmkx Problem 7
new apis which are only supported in mv3 can't be typed well in this boilerplate, is there a better practice to improve it?

you can declare missing definitions like this:
// shim.d.ts
declare module 'webextension-polyfill' {
  declare namespace Browser {
    const mv3: {
      hello: () => void;
    };
  }

  export = Browser;
}

That should be the last choice because I have to manually  write all new-added mv3 type definitions one by one. It's very tedious. Since mv3 has been published from 2020, it's weird that there hasn't yet been an public mv3 types package in community for the past two years.

There is an official type definitions package, but it's for Chrome only, have a try!
pnpm add @types/chrome -D

 // tsconfig.json
 "types": [
   "vite/client",
+  "chrome"
 ],

Problem1. remove pnpm-lock.yaml and try install again
Problem2. can be solved
Problem3. HMR is unstable in MV3 as expected because the implementation is a little tricky, and that's why it's still not merged into main branch. needs more investigation.

Hi @tmkx, any advance on Prob. 3?
I recently update my project to the mv3 template, most functions works fine for me, but the dev model for vite. It won't hot reload modification of .ts file, like the vuex storage index.ts I used in my project.
After changging the index.ts, the shell print
9:38:47 AM [vite] page reload store/index.ts
ESM Build start
ESM extension/dist/mv3client.mjs        38.74 KB
ESM extension/dist/background/index.mjs 100.08 KB
ESM ⚡ Build success in 12ms

However, the file in the extention dir extention/store/index.ts.js won't chage accodingly, unless I re-run the npm run dev cmd.
I investigate the MV3Hmr vite plugin, but I don't understand how it works.

HMR is supported in the main branch, closing this issue.
if there still have any problems, please reopen it :)

Problem5
background script is not bundled by Vite, there is no import.meta.hot and HMR.

I still have this issue in the main branch, import.meta.hot is undefined


Fix bad assert in initialize_cluster if PG already exists

Quick fix for bad assert in https://github.com/vllm-project/vllm/pull/397 - my bad for missing that one!

cc @zhuohan123


TBSTFNP-27: The tasks escape params when invoking the msbuild scanner

More details at: https://jira.sonarsource.com/projects/TBSTFNP/issues/TBSTFNP-27
Note: I haven't updated the actual msbuild scanner executable to 1.1 because we need to release it / sign it first. The fix won't be complete without it, but it won't break anything.

LGTM


Updating test_tool_failure cassette

Seen in this CI run:
    | vcr.errors.CannotOverwriteExistingCassetteException: Can't overwrite existing cassette ('tests/cassettes/TestTaskDataset.test_tool_failure.yaml') in your current record mode ('none').

This PR regenerates the cassette so this test passes

Would running these on new_episodes prevent these from breaking in the future?
https://vcrpy.readthedocs.io/en/latest/usage.html#new-episodes

Would running these on new_episodes prevent these from breaking in the future? vcrpy.readthedocs.io/en/latest/usage.html#new-episodes

That would be fine, we'd just have to add a bot to commit the new cassettes. Otherwise we'd be regen'ing every time and not realize we have a stale cassette


The special query will make influxd.exe crash

With default config run.
The 90 query join will make influxd.exe crash, here is stack trace.
stacktrace.txt

@Cricle Are you still experiencing this issue? If so, can you can provide a full stack trace including the panic as well as what the query is?

Closing because of no response


⚠ Tada Website has degraded performance

In b68357c, Tada Website ($WEBSITE_URL) experienced degraded performance:

HTTP code: 500
Response time: 18025 ms

Resolved: Tada Website performance has improved in f4979d0.


not support python 3.9

please update this package for python 3.8 and 3.9

Hey @esmaily, thanks for your request. Would you mind elaborating, what the issue is you are having? Just double checked and 3.8 and 3.9 should be supported:

Required version: >3.6.1, <4.0
Looks like the tests running fine with 3.8 and 3.9: PR to run tests for 3.9 as well

Hey @esmaily, thanks for your request. Would you mind elaborating, what the issue is you are having? Just double checked and 3.8 and 3.9 should be supported:

Required version: >3.6.1, <4.0
Looks like the tests running fine with 3.8 and 3.9: PR to run tests for 3.9 as well

Looks like there is nothing left to do. Closing :)


Show specific version query url on app submit

Basically, this will display to the version specific query url to the user on app submit:

Appix output

Verbose mode

In not verbose mode I'd prefer printing only one url (the one with Acc), so that the developers don't have to think. Otherwise they will be confused about which one to use when they create the acc environment.
What do you think?

I agree @markvincze, showing only 'acceptance' makes more sense here.  In verbose mode we show all URLs already (in the LINKS session).


SignalXY respect marker settings

Purpose:
#1763
This also fixes a similar issue where LineWidth of zero was ignored, as well as LineStyle.None.

FWIW we can probably apply the same optimization of only drawing visible points to the line as well. Doubt that line drawing is anywhere near as expensive as markers, because the lines are (hopefully) all drawn at once within GDI.


Implement "upgrade interactive" command

Yarn (the Javascript package management tool) has an "upgrade interactive" command. It presets all updates available for all packages in package.lock, and for each package lets you choose whether you want to go to the very latest version (even if it's a new major version), to just the latest minor/patch version, or no change at all.
I think it would be great to see such a feature for poetry too. It would help to resolve certain version conflicts that just using up --latest can't deal with.
For example, at the time of writing, flake8-eradicate v1.4.0 has a dependency restriction of ">=3.5,<6" on flake8. Using up --latest fails when both of these packages are installed, because it's unresolvable. The latest version of flake8 is 6.x, and that's not compatible with the latest version of flake8-eradicate, so the dependency resolver doesn't know what to do and gives up.
If I could choose which updates I want for each package, I could deal with this problem directly. At the moment, the only solution I have is to manually update some dependencies and not use up --latest.

Hey @djmattyg007, thanks for reporting an issue.
I think an "upgrade interactive" command could be a great addition. However, I don't feel I have the time right now to implement this feature because I'm currently involved in other projects but feel free to contribute if you would like :)
Regarding your unresolvable issue, you can come around it by either pinning the package(s) that causes this issue or alternatively put them in a separate group and then exclude the group with up --latest --without my-group.


Status command

Fixes #32  .
Changes proposed in this PR:

[x] implemented core function for status

modified OceanNodeKeys to include ethAddress

generated address from private key in getPeerIdFromPrivateKey

[x] expose HTTP interface

[x] expose P2P interface

This is the response from Postman calling /directCommand with status:

Extended version:
{
    "id": "16Uiu2HAmJKKnHoDrc5xcxPfVJUWLrv8iNnhqZ3YdnUfRRsAiJvAJ",
    "publicKey": {
        "0": 8,
        "1": 2,
        "2": 18,
        "3": 33,
        "4": 3,
        "5": 84,
        "6": 28,
        "7": 121,
        "8": 227,
        "9": 133,
        "10": 2,
        "11": 175,
        "12": 121,
        "13": 26,
        "14": 211,
        "15": 103,
        "16": 80,
        "17": 5,
        "18": 222,
        "19": 172,
        "20": 81,
        "21": 16,
        "22": 222,
        "23": 176,
        "24": 207,
        "25": 4,
        "26": 178,
        "27": 204,
        "28": 198,
        "29": 186,
        "30": 188,
        "31": 60,
        "32": 16,
        "33": 205,
        "34": 204,
        "35": 13,
        "36": 231
    },
    "address": "0x02354A1F160A3fd7ac8b02ee91F04104440B28E7",
    "version": "1.0.0",
    "http": true,
    "p2p": true,
    "provider": [
        {
            "chainId": "1",
            "network": "mainnet"
        },
        {
            "chainId": "137",
            "network": "polygon"
        },
        {
            "chainId": "80001",
            "network": "mumbai"
        }
    ],
    "indexer": [
        {
            "chainId": "1",
            "network": "mainnet",
            "block": "0"
        },
        {
            "chainId": "137",
            "network": "polygon",
            "block": "0"
        },
        {
            "chainId": "80001",
            "network": "mumbai",
            "block": "0"
        }
    ]
}

For testing, I suppose this issue needs to be solved first in order to create an Ocean node class and call this commands when the node is up.
cc @alexcos20

hi @mariacarmina
overall, lgtm , just wondering if we should do the public key more "user friendly" to read.. instead of returning the byte array we could do something like
Buffer.from(config.keys.publicKey).toString('hex') for instance
Like we have on the node getPeerDetails()
Just cosmetic anyway, but imo, it might look better & is more aligned with the other fields.
thanks

Sure thing, I'll do that to look easier to read. Thanks!

Updated response


specimen: days_to_collection field

This should be mapped to the time_of_collection field of the GA4GH Biosample message.
Check what data is coming for this. Probably use the same days to ISO 8601 function as for disease and individual.

@pnrobinson @ielis I have a question about the Phenopacket age element.  The documentation says it should be age: iso8601duration: "P25Y3M2D", but in op_individual the parameter is described as ":param iso8601duration: age represented as an ISO 8601 Period".  Is the element 'Age' or 'iso8601duration'?
https://phenopacket-schema.readthedocs.io/en/latest/age.html

Hi @msierk
OpIndividual is a convenience wrapper for constructing instances of Individual component of the Phenopacket Schema. The purpose of the wrapper is to simplify creation of the Protobuf object. The Python bindings generated by the Protobuf "compiler" are sometimes hard to work with, and OpIndividual simplify this.
However, with the benefit of hindsight, I think OpIndividual does not help too much. So, I think I'll remove it from the code base.
To create a well-formatted Age, either to use in time_at_last_encounter in Individual, in time_of_collection of Biosample, or elsewhere, we must first have a well formatted ISO8601 duration string (such as P25Y3M2D in your example), and then set it to time_element.age.iso8601duration field.
You may need to fight the Protobuf bindings to get it done though.. :confused:
In the long term, I would like to create a Python library to simplify this. We have such a library in Java (Phenopacket tools, in particular the builder package), but Python needs one too.
Finally, I agree that we should compute the age at collection per your suggestion, and it is not yet clear to me how to make the subject's age available in the function. We'll have to work something out. Let's keep this issue open until we can resolve it.


Make interpreters code async by default

This MR would like to make all interpreters run async code by default. The current logic is that if the async attribute is present and its value is explicitly false  then it goes back to sync mode, otherwise all code runs just with top-level await available by default.
This MR also already showed that while it's trivial at code level to change these expectations, 5 tests had really hard coded different expectations and I am expecting tests in PyScript to have issue too once this is brought in.
The TL;DR of this MR is that it might take a lot of effort to make this fundamental change around our code but it should be duable, given enough time to test all the things are still working and we don't break all our test coverage we had in place before.
/cc @ntoll

actually ... I've discovered a bug with async scripts and the document.currentScript accessor ... so here the thing, we cannot grant that at any point in time the currently executing asynchronous script points at the right currentScript within the Python code because async means other scripts might also run in the meantime.
However, I think this is one of those non resolvable cases as these are fighting against the current Web standard implementation of document.currentScript and we should never interfere (more than we do already) with that part of the specs.
I think it's safe to move forward with this MR as all tests are green and I am quite satisfied of the result.


Condenser temperature is a signed value

The condenser temperature under register 0x6a is a signed value, as it will dip down below 0C whenever the outside temperature is low. Treating this as an unsigned value means that -1C shows up as 65535C, which is how I noticed the error.
I've tested this on my Midea Heat Pump over the last couple of weeks and it works without issue.

Thank you for spotting this!


"Biled" is listed in the drop-down menu

Description:
The commune is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions:
The website (https://peviitor-ro.github.io/ui.orase/) is up and running. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Biled".

Expected results
The location is listed in the drop-down menu as "Comuna Biled, TIMIȘ ".


Update jq dependency to latest stable version

Hello @apanicker-nflx, I completely agree about the comment that you left here: #1867
However, there is a newer stable version, so please take in consideration this PR. Thanks

Pull Request Test Coverage Report for Build 4560

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
16 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.08%) to 69.568%

Files with Coverage Reduction
New Missed Lines
%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraEventHandlerDAO.java
8
68.42%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraMetadataDAO.java
8
56.48%

Totals

Change from base Build 4556:
-0.08%

Covered Lines:
12838

Relevant Lines:
18454

💛  - Coveralls


Minimize Button

Add a minimize button beside the X button

WIll be included in v0.6b.

v0.6b now includes a minimize button.
The way window buttons are currently handeled is by using an icon button, which sometimes has problems with certain icons.
The default minimize icon doesn't work correctly so ive replaced it with the next best thing. It looks kind of weird but it works.
Once theres a fix in the ui library im using, ill make the change to a normal looking minimize button.
minimize button commit


feat: add livesense-inc/go-simple-http-redirector

livesense-inc/go-simple-http-redirector: Redirect HTTP requests to specific URI
$ aqua g -i livesense-inc/go-simple-http-redirector

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
root@11bad657ee7b:/workspace# redirector --help
{"time":"2024-03-14T08:50:52.474083762Z","level":"INFO","msg":"maxprocs: Leaving GOMAXPROCS=24: CPU quota undefined"}
Usage of redirector:
  -csv string
        Redirect list CSV file path
  -loglevel string
        Log level (debug, info, warn, error) (default "info")
  -port int
        Listening TCP port number (default 8080)
  -version
        Show version

Reference

https://github.com/livesense-inc/go-simple-http-redirector/blob/main/README.md

73fa16f26e4b10bd63ad56a1ae2099e25e81e402 aqua g gets command names from the last element of the package name or files on the top level, so if command names are different from the last element of the package name we have to set files on the top level.
Before
> livesense-inc/go-simple-http-redirector

After
> livesense-inc/go-simple-http-redirector [redirector]

I'd like to improve the behavior somehow, but for now we have to set files on the top level.

v4.153.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.153.0


error-prone :: remove unnecessary 'final'

Addresses:
[WARNING]
[UnnecessaryFinal] Since Java 8, it's been unnecessary to make local variables and parameters final for use in lambdas or anonymous classes. Marking them as final is weakly discouraged, as it adds a fair amount of noise for minimal benefit.
(see https://errorprone.info/bugpattern/UnnecessaryFinal)

Yeah I might have been a little too zealous with this change. Might be worth setting this rule to ignore.
I also did not realize that this is technically an 'experimental' rule. Might be worth setting all experimental rules to ignore?


some small typos

sorry Hong, please do let me know if you find these typo fixes too annoying to be bothered with.

sorry Hong, please do let me know if you find these typo fixes too annoying to be bothered with. Of course you can always grant me push permission :)

No problem at all.  Thanks for polishing it.  I will grant you the permission to push.


Use Microsoft SDK Hive directly

Summary

Part of https://github.com/paketo-buildpacks/dotnet-core/issues/722
Use the Microsoft official SDK download, which includes the runtime and libraries, instead of the Paketo-hosted, stripped down version
** Note ** the URI and SHA are hardcoded. A separate PR to update the dep-server metadata will go in after this PR is merged for future versions.
Other changes:

URI and SHA in buildpack.toml are the same as the source URI and SHA
Remove SDK compatibility tables
Limit number of patches per version line to 1, since SDK Hive is compatible with any runtime/asp.net in the same major/minor version line.
No longer require dotnet-runtime, as it's included in the SDK
Look at BP_DOTNET_FRAMEWORK_VERSION as a version source instead of RUNTIME_VERSION
Consider *.*proj files as a version source
Remove DOTNET_ROOT symlinking in favour of copying the .NET CLI into the /workspace/.dotnet_root and making it available on the path at launch-time. This is necessary for the FDD case, which will need access to the CLI at launch.

Use Cases

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[X] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@paketo-buildpacks/dotnet-core-maintainers I'll go in and update the dep-server metadata for the versions in this iteration of the buildpack once this is approved. However, I'm wondering if it's at all problematic to swap over versions to the Microsoft versions if we've already shipped buildpacks with that version?

I think that's probably fine. Maybe we call this a minor version bump instead of a patch?

@sophiewigmore did you happen to test run these changes against https://github.com/paketo-buildpacks/dotnet-core/issues/703 or https://github.com/paketo-buildpacks/dotnet-core/issues/670?

@fg-j Yes, I saw a successful build of https://github.com/blogifierdotnet/Blogifier with:
 pack build blogifier -e BP_DOTNET_PROJECT_PATH="src/Blogifier" --env BP_DOTNET_PUBLISH_FLAGS="--self-contained=true" -b <path to local .NET Core language family buildpackage> -v --clear-cache

And I also saw a successful build of https://github.com/ManuDinicola/NetPublishedFailed with:
pack build testpublish --env BP_DOTNET_PROJECT_PATH=./src/WebApi --env BP_DOTNET_PUBLISH_FLAGS="--verbosity=detailed" -b <path to local .NET Core language family buildpackage>

I'd love for someone else to try it out as well if they have the time. It requires the sw-patch-1 version of SDK, Runtime, ASP.NET, and Publish buildpacks in the language family though, so if it's too much of a pain to test out that's fine too.

@sophiewigmore Since you've taken it for a spin, I'll probably wait to do that as an acceptance step at the language family level before we cut a release.

It seems like now that there's a new available version of the SDK (6.0.302), we've got a merge conflict. How did you generate the hand-rolled metadata for the SDK dependencies you added? We'll need to do that again or let the dep server roll out the change.


optional annotation parameter types

[@thradec] We should allow an annotation parameter to be an optional type.
It's related a little with #3953.
Without this feature, we will have to use similar pattern for unspecified values like in java.
public @interface Foo {
    Class<?> bar = DefaultBar.class;
    static class DefaultBar {}
}

Which is little ugly.
[Migrated from ceylon/ceylon-spec#850]

If we’re not going to implement this soon, can we at least have a note in the spec about this? I almost reported this issue again after running into it.


chore(main): release 0.4.8

:robot: I have created a release beep boop
0.4.8 (2023-03-14)
Dependency Updates

deps: bump github.com/onsi/gomega from 1.27.2 to 1.27.4 (#277) (517804f)
deps: bump github.com/statnett/controller-runtime-viper from 0.1.5 to 0.1.6 (#264) (0d20cc1)
deps: bump github.com/vektra/mockery/v2 from 2.21.4 to 2.22.1 (#265) (e3b9c80)
deps: update ghcr.io/aquasecurity/trivy docker tag to v0.38.3 (#279) (7f2e089)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/statnett/image-scanner-operator/releases/tag/v0.4.8 :sunflower:


Marker.Animated is lagging too much on IOS

I have a car marker animating on map.
it have bearing and position animation.
everything work fine in Android but as IOS it's too lagging when starting the animation.
There are the codes for animating the marker

if (Platform.OS === 'android') {
        marker?.current?.animateMarkerToCoordinate?.(
          {
            latitude: 38.3368456,
            longitude: -122.0299002,
            latitudeDelta: 0.0043,
            longitudeDelta: 0.0041,
            ...(props.origin || []),
          },
          10000,
        )
      } else {
        markerOrigin?.current?.region
          ?.timing({
            latitude: 38.3368456,
            longitude: -122.0299002,
            latitudeDelta: 0.0043,
            longitudeDelta: 0.0041,
            ...(props.origin || []),
            duration: 10000,
          })
          .start()
      }

// Bearing Animation

    const rotation = new Animated.Value(0)
    const bearingDegree =
      rotation.interpolate({
        inputRange: [0, 360],
        outputRange: ['0deg', '360deg'],
      }),

Animated.timing(rotation, {
          toValue: props.bearing,
          useNativeDriver: true,
          duration: 10000,
        }).start()

This is the car marker
<Marker.Animated
        coordinate={markerOrigin.current.region}
        ref={marker}
        tracksViewChanges={track}
        flat
        anchor={anchor}
      >
        <AnimatedImage
          source={require('../../assets/images/motor-map.png')}
          style={allStyles}
          resizeMode="contain"
          onLoad={onLoad}
        />
      </Marker.Animated>

I am using
<EMAIL_ADDRESS><EMAIL_ADDRESS>

the only real issue is that animateMarkerToCoordinate is not supporting in ios

@pvinis sorry if I bother you :) .
would you mind to help the community to solve this issue in IOS.
the issue is in here Marker.js in line 311.
it suppose to return a function but it return undefined.
here are the code portion
_runCommand(name, args) {
    switch (Platform.OS) {
      case 'android':
        NativeModules.UIManager.dispatchViewManagerCommand(
          this._getHandle(),
          this.getUIManagerCommand(name),
          args
        );
        break;

      case 'ios':
        this.getMapManagerCommand(name)(this._getHandle(), ...args);
        break;

      default:
        break;
    }
  }

No idea why I was pinged here, but if you know what the problem is, maybe do a PR?

@pvinis I don't know that much about ObjectiveC. but hope you help to solve it. this issue exist since 2018 and it seems that there is no one to solve it

@gabrielmoncea is there any progress on this issue.

Hey @EhsanSarshar I haven't seen any PR that might solve this issue. And I only label issues for now.
And please don't spam other community members. People do open source for different reasons and no one is obligated to solve any issues.

@gabrielmoncea thanks for the response. I am very sorry if I bothered anyone. I must use mapbox-gl or webview until this issue will fix.

yep, still a thing

this issue is still active don't stale it

still a thing

@stale hold on

Still a problem


Right-to-left layout

When trying to add multilingual support, I've encountered two issues with right-to-left languages (such as Hebrew):

Round "Back" button is not shown in the upper right corner of the wizard control. Instead, some other random stuff shows up. Button, however, works, so it's a visual problem.
Wizard pages do not mirror their constituents, whilst wizard itself, header and footer do.

Can the problem be alleviated by me, or do I have to wait for a fix?
Thank you. Awesome wizard.
Originally posted: 2013-04-13T12:24:51

If you have the time to take the current code base and make the fixes, you will likely resolve it sooner than I am able. Please send me the patches you make so I can update the root.
Originally posted: 2013-04-15T08:00:55

What properties have you changed on the parent form? Localizable = true, RightToLeft = true, RightToLeftLayout = true? I started to look at what happens to the control and form when I change settings like those and would like to know all of what you have changed that have led to the bugs.
Originally posted: 2013-04-15T08:56:01

Will you pull up a Windows Vista/7 OS based wizard (like Devices & Printers | Add a printer) in Hebrew (or another right-to-left language) and send me a screenshot? I have no idea how the final UI is to display.
Originally posted: 2013-04-15T09:30:53

Thank you for quick reaction!
Actually you need "Localizable" only when there is more than one language supported.
For testing purposes it's sufficient to set RightToLeft = true and RightToLeftLayout = true in the default language. Then, everything on the form, including child windows, should be reversed (mirrored). Windows already does almost everything for you - the horizontal coordination starts from the right and proceeds to the left. So, if you play by the book, everything should be reversed already, like in the attached hebrew "Add printer" screenshot. The problem is with the bitmaps. Generally, their picture may not necessarily be reversed, except special cases, such as "Back" button. Note, that windows knows to reverse the bitmap itself. Another caveat is, when you map windows objects on the screen, always map rectangles, not separate points. This way, layout will be preserved always. So use RectangleToClient/RectangleToScreen instead of PointToClient/PointToScreen in .NET.
Originally posted: 2013-04-15T14:33:28

I don't see the attached screenshot though, so please, tell me how can I communicate it to you. It's PNG image.
Originally posted: 2013-04-15T15:35:31

I didn't think I'd have time to look at this, but it turns out I have. So far I have corrected the title alignment and the mirroring of the WizardPage content. The Back Button weird display is a mystery. Give me another day and I'll attach an updated assembly for you to test. Thanks for finding this problem. It is a significant gap in capability.
Originally posted: 2013-04-15T21:30:20

I have tried about 20 ways to get the Back Button to display correctly with no success. Sorry for the delay. Still working the problem.
Originally posted: 2013-04-30T17:02:06

Send me the code you use to paint the LTR button and maybe I'll come up with the right code for RTL one.
Originally posted: 2013-04-30T18:49:54

The painting code is in ThemeImageButton.cs which then uses routines in VisualStylesRendererExtender.cs. The problem I'm having is that the image seems to not be painting in the space defined by the control.
Originally posted: 2013-05-01T08:38:28

Ok, I've found the bug in your code. Don't use "this.Bounds", because it's in wrong coordinates. Always use the bounds, provided by "OnPaint" directly. The corrected code follows:
protected override void PaintButton(Graphics graphics, Rectangle bounds)
{
if (Application.RenderWithVisualStyles || DesktopWindowManager.IsCompositionEnabled())
{
try
{
VisualStyleRenderer rnd = new VisualStyleRenderer(StyleClass, StylePart, (int)ButtonState);
if (this.IsDesignMode() || !DesktopWindowManager.IsCompositionEnabled())
{
rnd.DrawParentBackground(graphics, bounds, this);
rnd.DrawBackground(graphics, bounds);
}
else
{
rnd.DrawGlassBackground(graphics, bounds, bounds);
}
return;
}
...
Originally posted: 2013-05-01T15:02:00

P.S. Don't forget to invert the image!
Originally posted: 2013-05-01T15:17:07

That did it! Thank you! I need to fix the code that displays the help text at the bottom of the wizard and then I'll update the download. Should be done by tonight.
Originally posted: 2013-05-02T08:35:40

When scaling to DPI, are you speaking to the icon between the title text and the back button or the back button?
Originally posted: 2013-05-02T15:17:41

It's the icon between the title text and the back button as can be deduced from the proposed code.
Originally posted: 2013-05-02T15:58:01

Actually, that code provides backup images for the back button in case the Visual Styles fail. That's what led to my confusion. Thank you for the clarification. The code that adjusts that small icon is in the ThemedLabel.cs file. I will take your suggestion and adjust the appropriate code.
Originally posted: 2013-05-03T09:54:30

My bad, looking at the wrong code section. In the code you posted, what is the purpose of adding a "new Size(1, 1)" to the SmallIconSize?
Originally posted: 2013-05-03T10:08:23

If your/my icon lacks some basic size, such as 20x20, then this code ensures, that the larger one, 24x24 is downsized, not the smaller - upsized.
Originally posted: 2013-05-03T11:19:10

Resolved with changeset 72703: * Completed work on support for RTL languages

Fixed DPI scaling of title image

Originally posted: 2013-05-03T14:06:58

demidov, please let me know if release 1.2.5 appropriately fixes the RTL and DPI problems.
Originally posted: 2013-05-04T15:29:45

Yes, it does. Thank you.
Originally posted: 2013-05-04T21:44:45

Originally posted: 2013-05-03T14:06:58


[FCE-937] Fix expo doctor issues

Description
Fixed warnings which appeared when running expo doctor
Motivation and Context
Expo doesn't recommend using different package versions than those used by Expo, it may cause issues along the way.
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

WDYT about somewhere info about how to use expo doctor? Maybe in CONTRIBUTING.md?

@mironiasty I've added the info about expo doctor to CONTRIBUTING.md
Also I think we should consider changing dependabot.yml to only update Expo and it's dependencies because otherwise the expo doctor will throw warnings again.

@mironiasty @MiloszFilimowski I've added expo dependencies to ignore in dependabot config so you can check them and say if you have any objections

@mironiasty I've added only major and minor as ignored types


Inconsistent strikethrough in pylint tracking issue (#970)

In the pylint/ruff gap tracking issue #970 some rules are striked as to indicate that it is considered obsolete/unneeded.
As I am using this issue in scripts to determine the gap every now and then, I noticed one of them is not striked like the rest.
confusing-consecutive-elif / R5601 has just the name striked, while the rest is striked through to the end of the rule code.
If possible can it be fixed?
Thanks in advance

Done. I hope I did it correctly.


validation error cause not in BIDS specification

Validating ds005 leads to two error in the models folder which I could not find in de BIDS 1.7. specification. Is the yaml schema out of sync with the written documentation or is this another problem?
dataset_path = './tests/data/ds005'
layout = BIDSLayout(dataset_path)
report = validate_dataset(layout.dataset)
for message in report.messages:
print(message)
returns
    #{'severity': 'error', 'message': "Invalid entity 'ds' in artifact 'models/ds-005_type-mfx_model.json'"}
    #{'severity': 'error', 'message': "Invalid entity 'type' in artifact 'models/ds-005_type-mfx_model.json'"}
    #{'severity': 'error', 'message': "Invalid entity 'ds' in artifact 'models/ds-005_type-test_model.json'"}
    #{'severity': 'error', 'message': "Invalid entity 'type' in artifact 'models/ds-005_type-test_model.json'"}
    #{'severity': 'error', 'message': "Invalid entity 'ds' in artifact 'models/extras/ds-005_type-test_model.json'"}
    #{'severity': 'error', 'message': "Invalid entity 'type' in artifact 'models/extras/ds-005_type-test_model.json'"}

Neither 'ds' nor 'type' is in the written documentation. May be from the recently defined models specification.

The entities 'ds' and 'type' are not specified. Maybe, instead of an error, there should be just warning for unspecified entities?

Well, I'd suggest we take the schema serious. if they are specified as required there, they should raise and error.  Do we need to report to the maintainers?

The official BIDS Validator reports an error:
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.

From this I conclude that ALL files in a dataset are validated. So far I thought its only those explicitly listed in the specification.
A message similar to what you wrote would be helpful. Should we add a third field with the name 'specification' or 'reference'  that provides the respective information?


file access and user id philosophy in containers.

I'm new to docker and cloud in general, so just doing the default thing (everything is root) for now, similar to how the demo doesn't bother with SSL) and not worrying about it. I had some discussions with @tomkralidis about the topic, and I don't really have any conclusion so I thought I would document the concerns/issue. Each container often needs access to local files, and they will use a user id to establish their permission to write files, and allow other processes using the same files to read them, or prevent same.
It's unclear if this is important or not. Some say this is not an issue because in true cloud environments, the username does not matter and there is no possibility of corrupting the calling host.
Normal development environments avoid the use of the root account, and it is longstanding best practice to develop code without requiring root access at all, or at least minimizing it. Default docker uses root for everything, and root of the container is pretty close to root on the host. As a long-time unix/linux admin, this is surprising, violating the https://en.wikipedia.org/wiki/Principle_of_least_astonishment.
Files Are Shared
Whatever is done, one must also contend with the current design of wis2node, where the data consumer and the wis2node containers read and write files in common directory trees, and likely a third container, responsible for cleaning out old files will also access the same file areas.  So the user-id approach among at least these three containers need to be consistent, in that they must allow appropriate reading and writing of files created by other containers.  To eliminate sharing of files is simple, put all the wis2node/data-consumer and cleaning functionality into a single container.  That's straightforward to do... but unsure if it is desirable.
AllRoot: Default Docker Behaviour
So if you have a linux server/workstation as the host on which you run the docker containers, and you run a container that does nothing for set it's effective uid, it will run as root be able to read/write "anything". The definition of the container is all that constrains where it can write to... so... no problem :-)
benefits:

dead simple, one can always write to the files on needs.

disadvantages:

basically this has all the downsides of running an application as root, considered poor security practice

violation of https://en.wikipedia.org/wiki/Principle_of_least_privilege in that uid's are shared among container and host... so root in the container is root in the host... albeit with some limitations.
avoid use of root when you just need a privileged port, etc...  principle of https://en.wikipedia.org/wiki/Privilege_separation

if developing as non-root account on host, one must use sudo to clean up/manage: slight inconvenience.
incorrect 'volumes' configuration can make sensitive areas of host vulnerable to corruption, either by inadvertant or malevolent actors .  Security concern for availability (inadvertance) and Integrity (malevolence.) ability to take down host, violation of container isolation.

HostUser:  Import user from Host
This is what I expected to happen with container... I expected that the container would run root in the container, but mapper to my userid in the host, so it would have the same file permissions as my user.  One has to configure docker to behave this way.
references:

https://jtreminio.com/blog/running-docker-containers-as-current-host-user/#ok-so-what-actually-works

This results in adding something like:

ARG USER_ID=`id -u -n`
ARG GROUP_ID=`id -g -n`

RUN  groupadd -g ${GROUP_ID} wis2node &&\
    useradd -l -u ${USER_ID} -g wis2node &&\

USER wis2node

This doesn't actually work for me so far... the container always exits immediately.
benefits:

writing on host os works as expected (principle of least surprise.)
container code runs as 'wis2node' fixed username, can be used in containers (e.g. ~wis2node)
container code does not run as root (many security benefits.)
id is consistent among different containers (each one must define the user.)
does not rely on host user scheme (say in LDAP) so does not require container to understand entire authentication architecture of host, it just uses host user and group-id as given, and provides a fixed name for use in the application.
all code

disadvantages:

every container needs the above code to provide consistent user definition.
if the code really does use root, this would be a problem.

FixedUser: Define a user for use in the host
One coulde define a specific uid/gid combination to be used by all containers... difference to the above approach would be to fix USER_ID and GROUP_ID to 1000, for example, so all files would be written as uid & gid 1000, rather than importing from the host.
Benefits:

perhaps can define directory permissions to be more constrained, so container cannot write in any host user file directories.

Disadvantages:

still need sudo (root access) to manage files, as current development user may not have rights to clean up.

There may be other options... these are the ones I noticed.
General disadvantages (all approaches so far):

username is set at image build time.  Some people might want to distribute images, and have the user chosen at container run time.

wrinkles:  alpine linux has only a rudimentary 'adduser'   whereas full fledged linux distributions have useradd... the options are all different.

@webb-ben mentioned 'rootless mode' so looked that up... https://docs.docker.com/engine/security/rootless/

@petersilva I didn't see this! But yes I am having trouble figuring out the test workflow in Github Actions because the actions vm user is not root. However, like you said, the default docker deployment run containers as root which causes permission errors. I am still orienting myself with docker but happy to try to think through this however possible... especially once I figure out my own issue :)

@webb-ben fwiw... I ended up switching my images to use root for now.  Maybe later, we can figure out non-root... this issue just documents the exploration.


REFACTOR-#6944: Apply 'isort' formatting for scripts from tutorials

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #6944
[ ] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@dchigarev it's better to rename it to "FIX-" so we don't forget to add the PR to the patch release.


R Interactive occasionally shows System.NullReferenceException

When I'm working with Python project, R Interactive occasionally shows System.NullReferenceException.
The error message on the interactive was:

このフレームのコンテンツを作成しようとして例外が発生しました。この情報は "C:\Users\mic\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml" にも記録されます。

(Japanese text means "Making frame contents of this frame caused exception. This information also recorded in ActivityLog.xml")

例外の詳細:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context)
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage()
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()

(Japanese text means "Details of the exception")

I'm sorry but I did not check whether this exception also occur when working with R project.
R Tools for Visual Studio   0.5.21008.0800
Provides project system, R Interactive window, plotting, and more for the R programming language.

VS occasionally shows a message like "Couldn't load 'RPackage' package".

May be the same as related to #2612

Should not be happening anymore


dfrph: Initial implementation

The driver implements support for the DFRobot pH sensors.  It was
tested with both the standard and Pro versions, calibrated with
standard buffer solutions at pH 4.01 and pH 7.0.
Signed-off-by: Jon Trulson<EMAIL_ADDRESS>

implemented and pushed upstream (intel-iot-devkit)


[unsafe] return underlying c rocksdb instance

return the underlying c instances for a few gorocks structs.
We want to extend the gorocks beyond the c bindings.
For instance, for the application we are developing we we want to use some of these methods in DB object (the c++ struct in rocksdb/db.h)
NewIterators (for multi CF iterators)
PurgeOldBackups
If we get the underlying c object then we can c++ code to access those methods from our go code, while still using the awesome api provided by  gorocksdb.
an example ->
https://github.com/pavanka/opaque-rocksdb/blob/purge/test.go
see commands for how we compile this.
however, for NewIterators seems like we need a private fork. any suggestions.
https://github.com/pavanka/opaque-rocksdb/blob/iterators/test.go#L41
this is invalid reason: cannot use iter (type *C.struct_rocksdb_iterator_t) as type *gorocksdb.C.struct_rocksdb_iterator_t in argument to gorocksdb.NewNativeIterator

if I fork & modify gorocks: this is how it would look.
https://github.com/pavanka/gorocksdb/commit/8bcd9875b44f17218d9fe871ab0ff3097601c39a
Please let me know which approach you prefer so we can close or go forward with this pr.

like updated in comment, not needed for us. we'll need to fork nevertheless.

Hey, sorry did not see your earlier comment.
sure, the idea you suggested would work. are you okay with that change?
https://github.com/pavanka/gorocksdb/tree/fork -> here's the fork
perhaps I can go back to the original pr then?

sure, that sounds good! I re-submit the pr with more changes I need. thanks!

so my understanding is that NewNativeIterators would not work outside this package anyway, because of the compilation issue, so this diff should not really break anyone that it was not already breaking!
in that case, at some point on a need basis, I will expose all c structs we need, and convert all NewNative.. types to take an unsafe.Pointer instead.
I will use the modified code to re-compile my original code & see, if it works. Thanks!

re-wrote the extension library with these changes:
https://github.com/pavanka/opaque-rocksdb/tree/support_pr
it compiles!! will let you know if functionality actually works on a real db, when I get to testing it.
Thanks!

sure, that sounds much better. let me change that.

the extension implementation I wrote using these changes work as expected:
https://github.com/pavanka/gorocksext/tree/support_pr
wrote some quick, crude manual tests for those extensions: https://github.com/pavanka/gorocksext_test
this might be a good way to extend gorocksdb package by adding more methods as needed.


\pC is not accepted

Long form \p{Other} is accepted.
C is not what I think of for General_Category=Other, but it's the official short value. Since regex claims to support the short values for the General_Category sets, \pC should probably also be supported.

Interesting! There's probably a silly bug somewhere, since that alias is in the Unicode alias table.
Other aliases, like \pZ, work: https://play.rust-lang.org/?gist=ab7ba8ea46f953129e8c926f7449f846&version=stable

....wow. That was, indeed, a silly bug.

UAX44-LM3. Ignore case, whitespace, underscore ('_'), hyphens, and any initial prefix string "is".

"linebreak" is equivalent to "Line_Break" or "Line-break"
"lb=BA" is equivalent to "lb=ba" or "LB=BA"
"Script=Greek" is equivalent to "Script=isGreek" or "Script=Is_Greek"

[...]
Existing and future property aliases and property value aliases are guaranteed to be unique within their relevant namespaces, even if an initial prefix string "is" is ignored. The existing cases of note for aliases that do start with "is" are: dt=Iso (Decomposition_Type=Isolated) and lb=IS. The Decomposition_Type value alias does not cause any problem, because there is no contrasting value alias dt=o (Decomposition_Type=olated). For lb=IS, note that the "IS" is the entire property value alias, and is not a prefix. There is no null value for the Line_Break property for it to contrast with, but implementations of loose matching should be careful of this edge case, so that "lb=IS" is not misinterpreted as matching a null value.

Should we write the Unicode Consortium and propose a revision to this text to mention ISO_COMMENT (isc)? Or is this technically a non-issue for a rigorous application of UTS18 Unicode Regular Expressions because ISO_COMMENT is a non-binary property?

UTS18-1.2 Properties
[...]
Some properties are binary: they are either true or false for a given code point. In that case, only the property name is required. Others have multiple values, so for uniqueness both the property name and the property value need to be included.
For example, Alphabetic is a binary property, but it is also a value of the enumerated Line_Break property. So \p{Alphabetic} would refer to the binary property, whereas \p{Line Break:Alphabetic} or \p{Line_Break=Alphabetic} would refer to the enumerated Line_Break property.
There are two exceptions to the general rule that expressions involving properties with multiple value should include both the property name and property value. The Script and General_Category properties commonly have their property name omitted. Thus \p{Unassigned} is equivalent to \p{General_Category = Unassigned}, and \p{Greek} is equivalent to \p{Script:Greek}.

According to my reading of the spec, the regex \p{isc} should resolve to p{General_Category=Other}
First, resolve isc. By looking at PropertyAliases.txt, we see that isc is equivalent to the property ISO_COMMENT. s bpt=Close, gc=Other, JSN=C, and jt=Join_Causing. ISO_COMMENT is not a binary property; ISO_COMMENT is a Miscellaneous Property. Therefore, \p{isc} does not mean \p{ISO_COMMENT=true}. Thus, we check to see if \p{Script=isc} or \p{General_Category=isc} is accepted. By looking at PropertyValueAliases.txt, and ignoring the prefix is as per UAX44-LM3, we see that c is an alias for the value gc=Other. Thus, \p{isc} resolves to the canonical(ish) form of \p{General_Category=Other}.
That the alias c for ISO_COMMENT stopped the check advancing to General_Category=c is its own bug. If \p{isc} doesn't resolve to \p{General_Category=Other}, I'm submitting another bug on principle. Note that \p{gc=isc} currently does resolve to \p{General_Category=Other}, and \p{isp} resolves to \p{General_Category=Punctuation}. Note also that \p{ISO_COMMENT} is correctly rejected.
[TANGENT]
.... And while testing these I noticed that you handle \p{XID_START}, \p{XID_CONTINUE}, and \p{WHITE_SPACE}. Given that I'm currently assembling sets manually for those, I should probably stop doing that and just use the property reference. Sure, it's nice to control what version of Unicode my grammar rules are against, but I'm not adjusting UAX31 and am already using GENERAL_CATEGORY properties from regex, so I'm already just using "a Unicode standard" rather than a specific one.
Actually, what's your expected policy for tracking new Unicode standards as they release? Things like XID_START are bound by stability guarantees, but WHITE_SPACE isn't, and I think that leads to some "fun" C# programs that work differently depending on your compiler & system Unicode settings.
[/TANGENT]

I'm not sure what the right way to interpret the Unicode standard is for this particular case is. I certainly do not have the bandwidth to follow up with Unicode proper. :-)

Actually, what's your expected policy for tracking new Unicode standards as they release?

My plan is to just update all of the tables. I don't think we've generally considered updates to Unicode to be a breaking change in the Rust ecosystem.


Adding verkle genesis command

This PR has been used in https://github.com/protolambda/eth2-testnet-genesis/pull/27
Said genesis tool has been included in: https://github.com/ethpandaops/ethereum-genesis-generator/tree/verkle-genesis
The resultant file was used to create the Kaustinen testnet here: https://github.com/ethpandaops/verkle-testnets/blob/master/ansible/inventories/kaustinen-testnet/group_vars/all/all.yaml#L37
Now that verkle looks a bit more mature, could we merge this PR and all the upstream ones so that we can avoid it bitrotting?


Training

Hello I cant find anything that mentions how to train it.
Should I use rnnoise to train a new model i I want one?

You can use rnnoise to train (nnnoiseless is compatible with the same model files). You can also check out the train branch, which has some training instructions (in the train/README.md file). It's a work in progress, but the goal is to eventually make training more convenient than it is in rnnoise (i.e. with less of the preprocessing).

Perfect! I'm trying it out.

I finally merged the train branch, along with some improved documentation, and I'm going to release 0.4 with these changes.


Add the “AnyConcept” concept to the stdlib

See https://github.com/LIonWeb-org/organization/issues/71

Done per commit 72a773e63ae4944583d47f1bd25050f69559f05c.


:recycle: Refactors test_urlrequest.py

uses @pytest.mark.skipif() rather than return
couple of DRY fixes using helper functions

A small test refactoring before addressing #6946, also refs https://discord.com/channels/423249981340778496/490493814281338890/722883388889104446

Addressed all the comments, including:

What's up with the :recycle: in the title?

It's commit emoji, https://gitmoji.carloscuesta.me/ I assume you didn't like it, so I removed it :smile:

Oh, it didn't render as a ♻ in the title so I was confused by what it was supposed to be.

Yes, BTW, I just see the merge message picked the GitHub title rather than the actual commit title. So now we have a merge commit with the icon :man_facepalming:


pre-build

Motivation
While devcontainers features aim to enable modern software development, the feature code itself is stuck in a lot of code duplication.
For example we can find # Determine the appropriate non-root user 17 times within the features repo. It's the same for me for detecting python version etc etc.
One of the main principles in software development is DRY: Don't Repeat Yourself. That is currently not possible for features!
Proposal
Variant: generic pre-build
Add support for pre-build.sh (in src/_pre_build.sh, src/_pre_build/pre_build.sh, src/_special_cli_stuff/pre_build.sh) which would be executed upon build and feature test calls with an appropriate set of parameters. This way the script can do arbitrary things like copy common code. But it could do even more like downloading common code from yet another source. It could merge code into single files. etc.
Variant: common code
Add support for src/_common which could contain code that is used throughout my features. Build and feature test calls will package that code as well as the install.sh script of the feature. Within install.sh one can simply source/call anything from _common as it's part of the package.
P.S. I wasn't sure whether to put this to cli or spec, please move if incorrect.

Or: The devcontainer-feature.json could list relative paths of files and folders that should be copied to the tar file during packaging.
It could be nice if the file structure in the tar file was the same as in the source repository, but currently the devcontainer-feature.json has to be top-level in the tar. Maybe something to think about.


Question: torrent-stream performance compared to libtorrent

how is torrent-stream performance compared to libtorrent, i mean writing bindings to libtorrent would make it faster than torrent-stream?

IMHO, any comparison would be unfair. Torrent-stream solves a very specific problem that libtorrent doesn't address: streaming files while they are being downloaded.
Having said that, I find that t-s is not very memory-efficient, but incredibly fast and resilient.

As a person who has worked with both to create a product, I can say this: torrent-stream beats libtorrent in terms of speed of download almost every time. By almost I mean that torrent downloading has a late number of variables and a lot of conditions play a role.
That being said, libtorrent usually over time develops a higher speed of download - it has a better peer selection system over time.
Also, libtorrent would have a lower CPU and memory usage. There are several reasons for this. First, we have the barebones c++ vs JavaScript/V8 reason. Second, and more importantly - the architecture/design - libtorrent is designed for downloading in the background vs torrent stream being designed to accelerate fast and keep downloading in order which is more demanding, requires more data kept in memory and more calculations.
Ultimately, different libraries, both very well designed and implemented but for a specific purpose.

@asapach can't we achieve the same thing by writing a storage that caches the results in the memory like t-s does?

@0x4139, your premise is incorrect: t-s doesn't cache the whole torrent in memory - just the pieces that are being currently downloaded (like most bittorrent implementations do). What distinguishes t-s is that it is able to prioritize the the pieces that are being requested by the consumers and stream them sequentially (instead of downloading them in random order) while blocking the stream until the pieces are ready.

@asapach i didn't say that it caches the whole torrent in memory,  you can do that with libtorrent as well. http://www.rasterbar.com/products/libtorrent/manual.html#piece-picker. Don't get me wrong not promoting libtorrent, just want to understand better what is the difference exactly .

OK, imagine that you have a torrent with 100 files and you want to download the 42nd file as fast as possible. I'm not sure what kind of API libtorrent exposes, but judging by the clients (e.g. Deluge), you'd first have to deselect all the other files, or set the highest priority to the required file and wait for it to download (regardless of strategy you pick). With t-s you can just start streaming it and t-s will provide you with the first bytes as soon as the first piece becomes available, before the file download completes.

Sorry to piggy-back on this question but this does feel to be on-topic.
Does 'storage' stream the piece from the file instead of memory as soon as it is complete? Assuming a piece was downloaded before the stream needed to read it or it was already downloaded from overlapping streams?
I'm trying to get a gauge of what ever part of this project does and it seems like storage handles reading/writing to File IO, does it handle downloading pieces also?

Storage is responsible for storing the downloaded pieces (hence the name). It can be backed by the file system, or by memory, or by carrier pigeons if you implement the contract and pass it as the storage option. Pieces that are in-flight (not downloaded yet), are not being stored.


All subdomains support in dns resolver

I'd like to resolve all subdomain for host .lan by the embdded dns.
Setting hostname, domainname and alias on connect to network doesn't allow me to resolve
I tried to set these params with mask *.lan. But dns resolve olny host *.lan
Is there some problem? Is this opportunity missed?

+1

@artemkaint It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926

Feature is still relevant


Pipeline with multiple inputs (different storage adapters)

It would be good to add a test to ensure that a single pipeline with multiple inputs (all with different storage adapters) will pass. I suspect this will fail currently - especially if one requires authentication info.

The config needs to be updated to prompt for authentication info for each of the inputs and the generated files need to be updated to include this config info on the actual job. That is, it needs to be possible to use different credentials for inputs which may use the same backend.


rmapi: <IP_ADDRESS> -> 0.0.28

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ddvk/rmapi/releases.
meta.description for rmapi is: Go app that allows access to the ReMarkable Cloud API programmatically
meta.homepage for rmapi is: https://github.com/ddvk/rmapi
meta.changelog for rmapi is: https://github.com/ddvk/rmapi/blob/v0.0.28/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.0.28 in filename of file in /nix/store/wjlz2mk7yq69yk4jdh2wk8w9d5dck1x4-rmapi-0.0.28

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

rmapi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wjlz2mk7yq69yk4jdh2wk8w9d5dck1x4-rmapi-0.0.28 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rmapi https://github.com/r-ryantm/nixpkgs/archive/e56d88b500f507223e893d9de390981d013be801.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e56d88b500f507223e893d9de390981d013be801#rmapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wjlz2mk7yq69yk4jdh2wk8w9d5dck1x4-rmapi-0.0.28
ls -la /nix/store/wjlz2mk7yq69yk4jdh2wk8w9d5dck1x4-rmapi-0.0.28/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

rmapi

Maintainer pings
cc @NickHu for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360214

aarch64-darwin

:white_check_mark: 1 package built:

rmapi


Add LeakPeek

Add this row below to the category Leaks
- [LeakPeek](https://leakpeek.com/) - Search for your publicly leaked passwords using an email or username, secure your personal data

Hello,
I am interested in working on this issue. Can you please assign it to me?

Please go ahead @RajatX24 : )

Hey @edoardottt ,
I have made a pull request regarding this issue.
You can check it out here:https://github.com/edoardottt/awesome-hacker-search-engines/pull/245
Please review it and let me know.
Thanks

Thanks @RajatX24 for your contribution!
Appreciated


Rename the default config file name to .launchable-config.yml

As @Konboi and I discussed, the config file should be .launchable/config.yml. However, I found Launchable CLI uses .launchable as a test session store. They are conflicting. So, I named the config file as .launchable-config.yml.

How about .launchable.d/config.yaml?
Although seen less often these days, it is an occasional pattern to add a .d suffix to a directory, as in emacs.d or init.d.
Currently, the contents of the .launchable file used by launchable/cli may also be placed under that directory.
In this case, I think there could be a plan to migrate to using a .lanchable directory in the future.

I vote .launchable.d/config.yaml because I personally don't like adding too many dotconfigs at the repository root.

.launchable.d/config.yaml is a good idea! If there are no objections, I'll go with this one.


Basic liver mechanism

About the PR
Adds a mechanism to livers. Currently, they don't do much since neither organ damage nor drunkenness are a thing, so they just metabolize all reagents like in SS13. To futureproof this and give YAML monkeys something to do, toxin and boozePower have been added and need to be set on reagents where relevant. I'm definitely not doing that in this PR unless a maintainer fusses at me to.
TODO:

[x] Make livers actually work by bugging Smug to look at this.

Changelog

:cl: ike709

add: Added a basic implementation of livers. They handle reagent metabolization now.

@DrSmugleaf I tried testing this by setting my hunger to starving and eating a bunch of food, under the assumption that metabolizing the nutrient reagent in the food would fix my hunger. But nothing happened. Any ideas?

Apparently the issue is BloodstreamComponent is null...

I fixed that. Stomach doesn't seem to be adding reagents to the bloodstream.

Stupid thing works now.


Register CovarianceFunctions.jl

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/50479
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" b2c3a296b265622334ba286a2ca9b774b4b3c1c7
git push origin v0.1.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/50479
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" fffd8df66e0e438a8a58ba378795c5e66dfe6ea3
git push origin v0.1.0

@JuliaRegistrator register
Release notes:

added Barnes Hut algorithm for fast multiplication with kernel matrices
added fast sparsification algorithm based on ball trees

Registration pull request created: JuliaRegistries/General/53254
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" b6e8ef467eb811bf35a7e2c3930486c15beaa8c5
git push origin v0.2.0

@JuliaRegistrator register
Release notes:

added Barnes Hut algorithm for fast multiplication with kernel matrices
added fast sparsification algorithm based on ball trees

Registration pull request updated: JuliaRegistries/General/53254
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 485942254f2b4af70f01d36db4c2adff444f15d7
git push origin v0.2.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/57762
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 5b0ff67493a0d8faabae30fda37348611c792d34
git push origin v0.2.1

@JuliaRegistrator register

Making cholesky more robust to small asymmetries in Gramian

Registration pull request created: JuliaRegistries/General/58296
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" 680f2b754474f5461e6643a1d5447ce693b30571
git push origin v0.2.2

@JuliaRegistrator register
Release Notes:

Improving efficiency of BlockGramian constructor

@JuliaRegistrator register
Release Notes:

Moving specializations for BlockFactorizations into gramian

Registration pull request created: JuliaRegistries/General/58455
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" a5218b907e7df2fe125f5ca5f6990b93be9687fd
git push origin v0.2.4

@JuliaRegistrator register
Release Notes:

Improvements to multiplication with Gramian
Made Matérn kernels to be differentiable at zero, enabling computation of gradient kernels
Single-argument isotropic kernel methods now dependent on r^2 instead of r to simplify gradient kernel calculation
Improved Barnes-Hut factorization
Added Taylor factorization as alternative to Barnes-Hut for negative weights
Made kernels functors to enable simple differentiation with Zygote and Flux

@JuliaRegistrator register
Release Notes:

added FFTW to dependencies to make ToeplitzMatrices work out of the box

Registration pull request created: JuliaRegistries/General/60019
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" 3f09e3a13347c7b97bd5957c6995568ce4e48e3b
git push origin v0.3.1

@JuliaRegistrator register
Release Notes:

gramian now automatically recognizes non-symmetric Toeplitz structure
gramian falls back to the lazy implementation if input kernel k has GenericInput type.

Registration pull request created: JuliaRegistries/General/60123
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" f8a8cf6479bee6a819a16d75eac2f280f758d929
git push origin v0.3.2

@JuliaRegistrator register
Release Notes:

Increased performance of GradientKernel on Sum and Product kernels
Increased performance of ValueGradientKernel

Registration pull request created: JuliaRegistries/General/60487
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" c4dd8bad7348ddc052890fc2d8c980f1e6e09885
git push origin v0.3.3

@JuliaRegistrator register
Release Notes:

Fix of NaN issue when target of mul! with BlockGramian is initialized with a NaN

Registration pull request created: JuliaRegistries/General/60676
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.4 -m "<description of version>" 8bcc1d2f4045787cd6fd607cf94719c1136bb6fe
git push origin v0.3.4

@JuliaRegistrator register
Release Notes:

Simplifying fix for constructor of GradientKernelElement

Registration pull request created: JuliaRegistries/General/61431
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.6 -m "<description of version>" 2ad5529a90af2899e8565491c7556143d4e4c470
git push origin v0.3.6

Also, note the warning: Version 0.3.6 skips over 0.3.5
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61702
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.5 -m "<description of version>" c551902160963980d35e0d17f693f481d0e33d70
git push origin v0.3.5


feat: Project selector in EA mode

Description
Adding Option to choose project during app creation in EA mode
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Created a project in EA mode and checked if project is assigned or not.
[x] Give User permission for assigned project and unassigned project and checked under various roles.
[x] Tested Code for FULL mode.

Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR require documentation updates?
[ ] I've updated documentation as required by this PR.
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

Duplicate PR. Changes if this PR has been covered in #663.


refactor(log): environment based logging and feat(test): jest added for unit and integration testing

refactor(log)
Logging feature added based on the environment. It will not generate any log in production time. console.log has been replaced by useLog utility fn.
feat(test):
Jest lib added for testing. React Testing Library could be the best option for react component testing.
*Note: No need to keep package-lock.json

#166 I've added the basic test setup in this PR


Subcategory needs better explaining

The subcategory syntax as described is accepted by the auditpol command yet when following its syntax, it always completes the setting for the whole category.
So either document how we get the GUID for a subcategory or tell us how to get the syntax working.
For instance
auditpol /set /category:"Object Access" /subcategory:"SAM" /success:disable
applies the change to the whole category NOT just to the subcategory. Maybe the documentation is not correct or the auditpol application does not work?

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

ID: e25b2b95-37c3-bc34-7c3d-d8f5351f63f9
Version Independent ID: 4e2abc4c-64e0-ba5b-2176-14a908678cb2
Content: auditpol get
Content Source: WindowsServerDocs/administration/windows-commands/auditpol-get.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close