Two output files share the same path but have different contents: media/img.svg [plugin angular-compiler]

Command
serve
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
It is not possible to import in SCSS two or more files with the same name but located in different folders when using new esbuild builder@angular-devkit/build-angular:application during serve.
.main {
  background: url('../assets/subdir1/img.svg');
}
.content {
  background: url('../assets/subdir2/img.svg');
}

And problem appears only during serve, production build works as expected: its generate 2 different images in media folder with different hashes.
The only possible workaround I found is adding "outputHashing": "media" to development configuration.
Minimal Reproduction
https://github.com/ln-e/ng17-image-import-bug

Clone repo
npm run start

Exception or Error
✘ [ERROR] Two output files share the same path but have different contents: media/img.svg [plugin angular-compiler]

Application bundle generation failed. [1.409 seconds]

Your Environment
Angular CLI: 17.0.0
Node: 18.16.1
Package Manager: npm 9.5.1
OS: darwin arm64

Angular: 17.0.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0
@angular-devkit/build-angular   17.0.0
@angular-devkit/core            17.0.0
@angular-devkit/schematics      17.0.0
@angular/cli                    17.0.0
@schematics/angular             17.0.0
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else relevant?
No response

Using "outputHashing": "media" is the correct solution for applications in this scenario. The output filenames will otherwise have identical names as shown.
To help mitigate this problem, we can consider making this the default behavior in the next major version.
We can also adjust the error message to indicate that using the outputHashing option will solve the problem.
Also of note, by referencing files inside a directory that is configured to be copied as an asset via the assets option, the images are present in the output twice. Once via the assets option copying and again via the url() from the CSS bundling.  If the images are intended to be processed and hashed during a production build, then the images should either be moved to a location not configured in the assets option or the assets option should be adjusted to not include their location. Conversely, if the assets should only be copied (and retain their respective directory structure), the CSS references should be adjusted to be relative to a runtime accessible location (i.e., ../assets/subdir1/img.svg --> assets/subdir1/img.svg) and the externalDependencies option should include assets/* to indicate the location should not be processed during the build.

@clydin how and where to set the externalDependencies option? And is it possible to configure the name of the new media directory where the css media are copied? Because it could conflict with an existing route or other existing resources, and that can be a problem.

If you use the externalDependencies option, the files will not be placed in the media directory and instead the location will be based on the assets build option configuration.


It was not possible to use mobile apps in a AngularJS application with authentication aad using adal js library.

The settings were performed as guided by the tutorials.
Will Mobile Apps does not support a web application SPA with AngularJS?

After some research on the issue, I found the solution in the example https://github.com/Azure-Samples/app-service-api-dotnet-todo-list, and was associated with the adal client settings.


Bug/fixing unbound variable 63

Using -z in an if statement causes an unbound variable error if set -eu is declared but the variable has not been declared.  Changing thing to -n which checks if the variable is declared and/or undefined. undefined is an empty string like bob=""
undeclared is if it has never been declared at all
Resolves https://github.com/gruntwork-io/bash-commons/issues/63

@gcagle3 not sure how we missed this.

Tested this with a simple script:
#!/bin/bash

set -eu

if [[ -z $bob ]]; then
  echo "It is there with -z"
else
  echo "Fail on -z"
fi

if [[ -n $bob ]]; then
  echo "It is there with -n"
else
  echo "Fail on -n"
fi

echo "Bob is ${bob}"

Which fails with these results:
./testingif.sh: line 5: bob: unbound variable

If you add in a line into the script above the if statements:
bob=""

Then you get this result (with no error message, and the script completes):
It is there with -z
Fail on -n
Bob is

@gcagle3 not sure how we missed this.

Excellent catch, thank you for creating this PR! I think missing this is a side effect of the limitations of the test cases. I'm going to create a task to research improving that situation to help avoid future issues being missed.

This has been merged and included in release v0.2.1. We have also updated the release notes for v0.2.0 to include a warning about the bug.


Construct $termLink with relLangURL  to generate correct category and tag links

Example:
Site: example.com/sub-site/
When visiting: example.com/sub-site/categories/

The category links are: example.com/categories/cat1/

It should now show as: example.com/sub-site/categories/cat1/

And with an added benefit to use a different Lang for categories and tags.

LGTM! Already merged.


Reach - Compelling Tribute - Ralof and All Stormcloaks Turned Hostile

User had to restart to resolve

I cannot remember which .esp commit it was but I am pretty sure that this was caused by some faction changes that were rolled back


big endian

closes #15
closes #35

@tomusdrw please review :)

Looks sane, but do we have any benchmarks to prove the performance?

Thanks for the review! Unfortunately we don't have. For now I focused only on making it work and not decreasing performance on little-endian platforms


Add Belgium flag

@TheWebartist Hey!
Thank you for contributing. Please update this PR as per Contributions guidelines.


Error while using Custom client

TypeError: itr.getReader is not a function
node_modules/ollama/dist/utils.js:120:28)
My code :
const ollama = new Ollama({ host: 'https://...' })
const ollamaResponse = await ollama.chat(apiMessage);
Called from NodeJs, but it looks like the code is using browser libraries.
Do I miss something ? Any idea to solve that issue ?

Try this code:
import ollama from 'ollama';
const message = {
  role: 'user',
  content: `Tell me a joke`,
};

const response = await ollama.chat({
  model: 'mistral:latest',
  messages: [message],
  stream: true,
});
for await (const part of response) {
  process.stdout.write(part.message.content);
}

I use this in nodeJS, it works. Your package.json  file must contain this also "type": "module"

I've installed Ollama on my little server and I'm running Mistral. Everything works fine, I can chat via cmdline interface, and also API requests works ok, except streaming response.
I try to get streaming response working by using your library, but I got stuck using it.
I have this simple script to talk to my local Ollama instance:
import {Ollama} from 'ollama'

async function run() {
    const ollama = new Ollama({host: 'http://xxxx.duckdns.org:11434'})

    const response = await ollama.generate({
        model: 'mistral',
        prompt: "Write a C code that parses a string into words that are divided by spaces.",
        stream: true
    });

    console.log(response);

    for await(const part of response) {
        process.stdout.write(part.message.content);
    }
}

run();

I get the following error:
{
  next: [Function (anonymous)],
  throw: [Function (anonymous)],
  return: [Function (anonymous)],
  [Symbol(Symbol.asyncIterator)]: [Function (anonymous)]
}
file:///Users/nordin/development/nodejs/ollama-req/main.js:15
        process.stdout.write(part.message.content);
                                          ^

TypeError: Cannot read properties of undefined (reading 'content')
    at run (file:///Users/nordin/development/nodejs/ollama-req/main.js:15:43)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I hope you can pinpoint the problem, as it's relatively simple piece of script.

I have the same problem when I used ollama in the browser. I think you need to call next() func in returned object.
Try this:
const responseNext = response.next()
for await(const part of responseNext) {
    process.stdout.write(part.message.content);
}

You helped to take a look to the iterator I wasn't familiar with.
The following snippet should give you a working result:
    for await (const part of response) {
        console.log(part);
    }

From here you're good to go 😉

太优秀了


@ngtools/webpack npm latest tag is release candidate

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [x] devkit
- [ ] schematics

Versions
macOS 10.13.4
npm 6.0.0
node 10.0.0
Repro steps
have<EMAIL_ADDRESS>installed and run npm outdated, the output shows something like
@ngtools/webpack                       1.10.2        1.10.2  6.0.0-rc.10

Desired functionality
It should probably not be the latest but next version on npm

Just fixed. Thanks for reporting this.


add calendar type to date-picker and calendar

Description
many people today use calendar type other than Gregorian like Shamsi (solar) or Chinese calendar, it is good to have this option for date-picker component  and maybe for calendar component have a major calendar type and show one or two alternative calendar type date in each cell with lighten color.
Suggested solution
we can use date lib like date-fn, momentJs, dayjs and so on that have already plugins for other calendar types
Alternative
some alternative component that i found for jalali type:
Vue persian datetime picker
Vue 3 Persian Datepicker
Vue Persian Datepicker
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

It seems to be a RTL problem about DatePicker/TimerPicker/Calendar?

no it's about calendar systems, look here
so we can get calendar system name and start of week from props and the rest is a utile method that give us first weekday of month in  given calendar system and total days of that month (28,29,30 or 31) then we make a view-layer over calendar cells for represents calendar in specifies calendar system (chinese, indian, islamic, japanese, persian, ...) and actual gregorian date remains untouched for date calculations

I try to understand and reexplain: we need a calendar-system(instance) to provide context or calculation (like Dayjs) and it can work with DatePicker and Calendar components? (now they only can work with Date class)

dayjs has solution with this plugin @calidy/dayjs-calendarsystems
i make simple component with it and its very simple:
<script lang="ts" setup>
import dayjs from 'dayjs'
import calendarSystems from '@calidy/dayjs-calendarsystems'
import PersianCalendarSystem from '@calidy/dayjs-calendarsystems/calendarSystems/PersianCalendarSystem'
import HijriCalendarSystem from '@calidy/dayjs-calendarsystems/calendarSystems/HijriCalendarSystem'
/* import 'dayjs/locale/fa' many locale translation already exists and we can import */

dayjs.extend(calendarSystems)
dayjs.registerCalendarSystem('persian', new PersianCalendarSystem())
dayjs.registerCalendarSystem('islamic', new HijriCalendarSystem())
const props = defineProps<{
  calendar?: 'gregory' | 'islamic' | 'persian' // hebrew, ethiopic and amazigh systems already implemented and other system can implemet easly
  startOfWeek?: 0 | 1 | 2 | 3 | 4 | 5 | 6
}>()
const today = computed(() => dayjs(new Date()).toCalendarSystem(props.calendar ?? 'gregory'))
const wd = ['Su', 'Mo', 'Th', 'We', 'Tr', 'Fr', 'Sa'] // weekdays
const wdi = computed( // weekdays index
  () => Array
    .from({length: 7}, (_, i) => i + props.startOfWeek)
    .map(c => c > 6 ? c - 7 : c)
)
const si = computed(() => wdi.value.indexOf(today.value.startOf('month').day())) // index of start-of-month in weekdays as start point

// and finally we can make our cells matrix of calendar
const cells = computed(() =>
  Array.from({length: 6},
    (_, i) =>
      Array.from({length: 7},
        (__, j) => {
          const diff = i * 7 - si.value + j
          return diff < 0 ? today.value.startOf('month').subtract(Math.abs(diff), 'days') : today.value.startOf('month').add(diff, 'days')
        }
      )
  )
)
</script>

with wd i have week day names and with cells i can create calendar (i use pug for my template and unocss for styling):
<template lang="pug">
.bg-white.p3.gap-y-px.font-sans
  .flex.justify-between.items-center.py-3.font-black
    .text-xl {{ today.format('MMMM') }}
    .text-3xl {{ today.format('YYYY') }}
  .gap-x-px.items-center
    .s-8.bg-zinc-2.flex.justify-center.items-center.rounded(v-for="key in wdi" :key="key") {{ wd[key] }}
  .gap-x-px.items-center(v-for="(row, k) in cells" :key="k")
    template(v-for="(day, key) in row" :key="key")
      .s-8.flex.justify-center.items-center.rounded.bg-zinc-1.text-zinc-3(v-if="day.get('M') !== today.get('M')" ) {{ day.get('D') }}
      .s-8.flex.justify-center.items-center.rounded(v-else, :class="day.date() === today.date() ?'bg-sky-5 text-white':'bg-zinc-1'") {{ day.get('D') }}
</template>

Could this feature be achieved by providing a slot for custom rendering of each calendar cell (with date value parameter)?

maybe, but we must do same thing every where that we use date-picker or calendar, how about config-provider ?
can you add method property as cellCustomRender in config provider?

Could you try 2.3.15? Refer to https://www.vexipui.com/en-US/component/config-provider.html, now you can use slots prop to specify rendering method for each slot with same name (currently only Calendar and DatePicker are effective).


Support "omit empty"

Golang firestore library supports the ability to tag fields as omitempty meaning they will not get stored in the DB when not set. This could be done via e.g. combining Optional with a Config option like
class Model(AsyncModel):
  field: Optional[str]
  another: Optional[List[int]]
  # ...

  class Config:
    omitempty = "*"
    # or
    omitempty = ["field", "another"]

Alternatively e.g. by extending Field() or similar from pydantic

Pydantic dict() and json(), or the corresponding model_dump() in v2, support the param:
exclude_unset: Whether to exclude fields that are unset or None from the output.
So maybe Firedantic save() could have it similarily easily.
But I agree that model conf for it would be nice.


Layout simplification, updated FAQ

Removes the hero section of the site and simplifies the FAQ layout, to deliberately look drier and less marketing-y.
Also updates FAQ content to use stuff in the google doc we were working on yesterday.
Desktop (1920 x 1080) and mobile (412 x 915) screenshots:

@ozxybox this good with you? I know you've read the text but may as well get confirmation. Anyone can go ahead and merge after Ozxy's approval.


Question about the Click Event

I'm trying to link each section of the funnel to a unique URL using the click event but I can't seem to get it working correctly as it's only going to the first URL.  Below is the fiddle showing what I am trying to accomplish.
https://jsfiddle.net/uk4yf1wn/216/

Your onClick function merely checks the contents of your initial data array by index. Those checks always return a member of that array, which are always objects. if (someValidObject) will always be coerced into true, which is why only the first link is opening. You can use the index key of the parameter supplied to the onClick function to determine which node was clicked.
I updated your Fiddle below:
https://jsfiddle.net/9dkLt4wc/1/
It might be cleaner to add a url key to your data array should that instead of having a bunch of if statement you can just use window.open(data[d.index], '_blank');.

Thank you for the quick response. This was very helpful answer and I'll take your advice and add the url to the data array.

Closing the issue. Please let me know if you have any more problems.


Typings

Steps

Install semantic-ui-react to my existing react project, got version 0.67.0
import form in semantic-ui-react
Additional info. I'm using the same React boilerplate with my other project, and was using 0.63.6 and the typings are all there

Expected Result
Typings should be there, including onSubmit, placeholder etc
Actual Result
So far, I cannot see onSubmit, placeholder
Version
0.67.0
Testcase
My Package.json in this current project
"ava": {
    "require": [
      "babel-register"
    ],
    "babel": "inherit"
  },
  "scripts": {
    "start": "npm run watch",
    "watch": "gulp watch",
    "build": "gulp build",
    "deploy": "gulp deploy",
    "test": "ava --tap | tap-nyan"
  },
  "author": "Maurizio Mangione",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/Granze/react-starterify/issues"
  },
  "homepage": "https://github.com/Granze/react-starterify",
  "dependencies": {
    "history": "^3.0.0",
    "react": "^15.0.1",
    "react-bootstrap": "^0.30.6",
    "react-dom": "^15.0.1",
    "react-loading": "0.0.9",
    "react-router": "^2.3.0",
    "react-timeago": "^3.1.3",
    "rxjs": "^5.0.3",
    "whatwg-fetch": "^2.0.1"
  },
  "devDependencies": {
    "autoprefixer": "^6.3.6",
    "ava": "^0.15.2",
    "babel": "^6.5.2",
    "babel-core": "^6.7.7",
    "babel-eslint": "^6.0.4",
    "babel-preset-es2015": "^6.6.0",
    "babel-preset-react": "^6.5.0",
    "babel-register": "^6.7.2",
    "babelify": "^7.3.0",
    "browser-sync": "^2.12.5",
    "browserify": "^13.0.0",
    "cssnano": "^3.5.2",
    "eslint": "^2.8.0",
    "eslint-config-airbnb": "^9.0.1",
    "eslint-plugin-import": "^1.6.0",
    "eslint-plugin-jsx-a11y": "^1.0.3",
    "eslint-plugin-react": "^5.0.1",
    "gulp": "^3.9.1",
    "gulp-eslint": "^2.0.0",
    "gulp-gh-pages": "^0.5.4",
    "gulp-html-replace": "^1.5.5",
    "gulp-imagemin": "^3.0.1",
    "gulp-notify": "^2.2.0",
    "gulp-plumber": "^1.1.0",
    "gulp-postcss": "^6.1.0",
    "gulp-rename": "^1.2.2",
    "gulp-sass": "^3.1.0",
    "gulp-sourcemaps": "^2.0.0-alpha",
    "gulp-strip-debug": "^1.1.0",
    "gulp-uglify": "^1.5.3",
    "imagemin-pngquant": "^5.0.0",
    "lodash": "^4.11.1",
    "postcss-nested": "^1.0.0",
    "postcss-simple-extend": "^1.0.0",
    "postcss-simple-vars": "^2.0.0",
    "react": "^15.4.2",
    "react-addons-test-utils": "^15.0.1",
    "react-dom": "^15.4.2",
    "react-router": "^2.8.1",
    "rimraf": "^2.5.2",
    "run-sequence": "^1.1.5",
    "tap-nyan
```": "0.0.2",
    "vinyl-buffer": "^1.0.0",
    "vinyl-source-stream": "^1.1.0",
    "watchify": "^3.7.0"
  }

Snippet of code in .js file
import { Form, Button, Input, Dropdown } from 'semantic-ui-react';
...
<Form loading={this.state.loading} onSubmit={/* <--does not show up*/}>
        <Form.Group>
          <Form.Input label="Title" type="text" />
          <Form.Input label="Description" type="text" />
          <Input label="" placeholder="" />
          <Form.Group>
          </Form.Group>
          <Input
            label={<Dropdown defaultValue=".com" options={salaryOptions} />}
            labelPosition="left"
            placeholder={/* <--does not show up*/}
          />
        </Form.Group>
        <Button typ />
      </Form>

In 0.67.0 we removed selializer functionality from Form component (#1367). So, onSubmit prop was removed too. We define only components' props in typings, see #1072.
However, you can still use onSubmit on Form and placeholder on Input (#1072).


llama stack fails to build on WSL.

Running inside WSL
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Cloned the repo made it to trying to build a model. First issue
llama stack build --name test
usage: llama [-h] {download,model,stack} ...
llama: error: unrecognized arguments: --name test

llama stack build doesn't work
After that we just manually go through the configuration, that fails with a missing file error:
(llama-stack) __username__@LAPTOP-I128A4F6:/mnt/c/Users/__username__/Documents/llama-stack$ llama stack build
Enter value for name (required): test
Enter value for distribution (default: local) (required):
Enter value for api_providers (optional):
Enter value for image_type (default: conda) (required):
Traceback (most recent call last):
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/common/exec.py", line 43, in run_with_pty
    process = subprocess.Popen(
              ^^^^^^^^^^^^^^^^^
  File "/home/__username__/anaconda3/envs/llama-stack/lib/python3.12/subprocess.py", line 1026, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/__username__/anaconda3/envs/llama-stack/lib/python3.12/subprocess.py", line 1955, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/core/build_conda_env.sh'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/__username__/anaconda3/envs/llama-stack/bin/llama", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/cli/llama.py", line 54, in main
    parser.run(args)
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/cli/llama.py", line 48, in run
    args.func(args)
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/cli/stack/build.py", line 161, in _run_stack_build_command
    self._run_stack_build_command_from_build_config(build_config)
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/cli/stack/build.py", line 122, in _run_stack_build_command_from_build_config
    build_package(
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/core/package.py", line 137, in build_package
    return_code = run_with_pty(args)
                  ^^^^^^^^^^^^^^^^^^
  File "/mnt/c/Users/__username__/Documents/llama-stack/llama_toolchain/common/exec.py", line 92, in run_with_pty
    if process.poll() is None:
       ^^^^^^^
UnboundLocalError: cannot access local variable 'process' where it is not associated with a value

the referenced file that fails to open is there:
#!/bin/bash

# Copyright (c) Meta Platforms, Inc. and affiliates.
# All rights reserved.
#
# This source code is licensed under the terms described in the LICENSE file in
# the root directory of this source tree.

LLAMA_MODELS_DIR=${LLAMA_MODELS_DIR:-}
LLAMA_TOOLCHAIN_DIR=${LLAMA_TOOLCHAIN_DIR:-}
TEST_PYPI_VERSION=${TEST_PYPI_VERSION:-}

if [ -n "$LLAMA_TOOLCHAIN_DIR" ]; then
  echo "Using llama-toolchain-dir=$LLAMA_TOOLCHAIN_DIR"
fi
if [ -n "$LLAMA_MODELS_DIR" ]; then
  echo "Using llama-models-dir=$LLAMA_MODELS_DIR"
fi

set -euo pipefail

if [ "$#" -ne 4 ]; then
  echo "Usage: $0 <distribution_type> <build_name> <pip_dependencies>" >&2
  echo "Example: $0 <distribution_type> mybuild 'numpy pandas scipy'" >&2
  exit 1
fi

distribution_type="$1"
build_name="$2"
env_name="llamastack-$build_name"
config_file="$3"
pip_dependencies="$4"

# Define color codes
RED='\033[0;31m'
GREEN='\033[0;32m'
NC='\033[0m' # No Color

# this is set if we actually create a new conda in which case we need to clean up
ENVNAME=""

SCRIPT_DIR=$(dirname "$(readlink -f "$0")")
source "$SCRIPT_DIR/common.sh"

ensure_conda_env_python310() {
  local env_name="$1"
  local pip_dependencies="$2"
  local python_version="3.10"

  # Check if conda command is available
  if ! command -v conda &>/dev/null; then
    printf "${RED}Error: conda command not found. Is Conda installed and in your PATH?${NC}" >&2
    exit 1
  fi

  # Check if the environment exists
  if conda env list | grep -q "^${env_name} "; then
    printf "Conda environment '${env_name}' exists. Checking Python version...\n"

    # Check Python version in the environment
    current_version=$(conda run -n "${env_name}" python --version 2>&1 | cut -d' ' -f2 | cut -d'.' -f1,2)

    if [ "$current_version" = "$python_version" ]; then
      printf "Environment '${env_name}' already has Python ${python_version}. No action needed.\n"
    else
      printf "Updating environment '${env_name}' to Python ${python_version}...\n"
      conda install -n "${env_name}" python="${python_version}" -y
    fi
  else
    printf "Conda environment '${env_name}' does not exist. Creating with Python ${python_version}...\n"
    conda create -n "${env_name}" python="${python_version}" -y

    ENVNAME="${env_name}"
    # setup_cleanup_handlers
  fi

  eval "$(conda shell.bash hook)"
  conda deactivate && conda activate "${env_name}"

  if [ -n "$TEST_PYPI_VERSION" ]; then
    # these packages are damaged in test-pypi, so install them first
    pip install fastapi libcst
    pip install --extra-index-url https://test.pypi.org/simple/ llama-models==$TEST_PYPI_VERSION llama-toolchain==$TEST_PYPI_VERSION $pip_dependencies
  else
    # Re-installing llama-toolchain in the new conda environment
    if [ -n "$LLAMA_TOOLCHAIN_DIR" ]; then
      if [ ! -d "$LLAMA_TOOLCHAIN_DIR" ]; then
        printf "${RED}Warning: LLAMA_TOOLCHAIN_DIR is set but directory does not exist: $LLAMA_TOOLCHAIN_DIR${NC}\n" >&2
        exit 1
      fi

      printf "Installing from LLAMA_TOOLCHAIN_DIR: $LLAMA_TOOLCHAIN_DIR\n"
      pip install --no-cache-dir -e "$LLAMA_TOOLCHAIN_DIR"
    else
      pip install --no-cache-dir llama-toolchain
    fi

    if [ -n "$LLAMA_MODELS_DIR" ]; then
      if [ ! -d "$LLAMA_MODELS_DIR" ]; then
        printf "${RED}Warning: LLAMA_MODELS_DIR is set but directory does not exist: $LLAMA_MODELS_DIR${NC}\n" >&2
        exit 1
      fi

      printf "Installing from LLAMA_MODELS_DIR: $LLAMA_MODELS_DIR\n"
      pip uninstall -y llama-models
      pip install --no-cache-dir -e "$LLAMA_MODELS_DIR"
    fi

    # Install pip dependencies
    if [ -n "$pip_dependencies" ]; then
      printf "Installing pip dependencies: $pip_dependencies\n"
      pip install $pip_dependencies
    fi
  fi
}

ensure_conda_env_python310 "$env_name" "$pip_dependencies"

printf "${GREEN}Successfully setup conda environment. Configuring build...${NC}\n"

$CONDA_PREFIX/bin/python3 -m llama_toolchain.cli.llama stack configure $config_file

Those errors were a bit misleading as I kept chasing them down. The main issue is that this doesn't build on windows and in WSL somehow all the files were corrupted. I had to dos2unix the entire cloned git repo and then those errors went away.

Re the first issue, we have simplified the CLI to only requiring llama stack build. Wondering if you have link the documentation where you have seen the llama stack build --name test command. Wanted to make it consistent with the actual implementation.
llama stack build -h
usage: llama stack build [-h] [--config CONFIG]

Build a Llama stack container

options:
  -h, --help       show this help message and exit
  --config CONFIG  Path to a config file to use for the build

Re the second issue, the error message suggests it may be cause by https://github.com/meta-llama/llama-stack/blob/736092f6bc9887552d11b7c6f266c6ac4087a0a8/llama_toolchain/common/exec.py#L43 running WSL, where process = subprocess.Popen may fail.

The instructions that still shows using command line arguments here:
https://github.com/meta-llama/llama-stack/blob/main/docs/cli_reference.md#step-32-build-a-distribution
specifically here:
Step 3.2: Build a distribution
Let's imagine you are working with a 8B-Instruct model. The following command will build a package (in the form of a Conda environment) and configure it. As part of the configuration, you will be asked for some inputs (model_id, max_seq_len, etc.) Since we are working with a 8B model, we will name our build 8b-instruct to help us remember the config.

llama stack build local --name 8b-instruct

The WSL issue is was fixed with dos2unix somehow on git pull on windows then using going into WSL the files somehow got corrupted.
If you can update the above commands we can call this issue close.

The instructions that still shows using command line arguments here: https://github.com/meta-llama/llama-stack/blob/main/docs/cli_reference.md#step-32-build-a-distribution

Thanks! Could you run git pull, and check again? It have been updated!


Shape editing bug

I think we have an editing issue similar to the previous multilink editing bug. We can create the initial shape, but editing does not yield any change.
Returning to the edit form might yield something like this, even though very different numbers were initially put as the Center X and Y

Unlike before, you can press Edit Component, but nothing happens on the editor.
We got this error in the console:
Warning: A component is changing a controlled input of type number to be uncontrolled. Input elements should not switch from controlled to uncontrolled (or vice versa). Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://fb.me/react-controlled-components
    in input (created by FormControl)
    in FormControl (created by CreateBooleanControllerForm)
    in div (created by CreateBooleanControllerForm)
    in CreateBooleanControllerForm (created by PaperControllerForm)
    in div (created by PaperControllerForm)
    in PaperControllerForm (created by CreateModelControllerForm)
    in div (created by Transition)
    in Transition (created by ForwardRef)
    in ForwardRef (created by Fade)
    in Fade (created by TabPane)
    in TabPane (created by Tabs)
    in div (created by TabContent)
    in TabContent (created by Tabs)
    in Tabs (created by Tabs)
    in Tabs (created by CreateModelControllerForm)
    in CreateModelControllerForm (created by CreateComponentForm)
    in div (created by Transition)
    in Transition (created by ForwardRef)
    in ForwardRef (created by Fade)
    in Fade (created by TabPane)
    in TabPane (created by Tabs)
    in div (created by TabContent)
    in TabContent (created by Tabs)
    in Tabs (created by Tabs)
    in Tabs (created by CreateComponentForm)
    in div (created by CreateComponentForm)
    in CreateComponentForm (created by ForwardRef)
    in div (created by ForwardRef)
    in ForwardRef (created by CreatorMain)
    in div (created by CreatorMain)
    in div (created by CreatorMain)
    in div (created by CreatorMain)
    in CreatorMain react-dom.development.js:88:30
    React 11
    unstable_runWithPriority webpack://paperprograms/./node_modules/scheduler/cjs/scheduler.development.js?:653
    React 5
    unstable_runWithPriority webpack://paperprograms/./node_modules/scheduler/cjs/scheduler.development.js?:653
    React 4
    unstable_runWithPriority webpack://paperprograms/./node_modules/scheduler/cjs/scheduler.development.js?:653
    React 5

@brettfiedler showed me this today, and I suspect a fix for this will be the same as #115

Nope, it was just that editing shape options wasn't supported at all. Fixed in the above commit.

Merged into main.


Update dbeaver-enterprise to 4.0.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

This appcast has been updated 3 times in the last 20 days without an application update. It's time to consider removing the appcast.

@colindunn I agree, appcast removed.

@miccal There are several casks like this with either development or alternate versions released out of sync on the same appcast, brave is one that has had the appcast updated several times without a version bump. Should we consider removing those appcasts as well?

@colindunn I will let @vitorgalvao make that call.

brave uses a github appcast, as does atom and many others. It did indeed get version bumps, it’s just that those bumps were not made to the stable version. As such, the appcast is still valuable.
We can safely say appcast is useful. What we need now is a type of appcast do that will let us be granular about what to ignore/keep from the appcast.
Maybe we even change the whole system and all appcasts become blocks that output a string that we can transform anyway we want. That way we’ll even be able to parse webpages that frequently change and just get the piece we want. Then we compare the result from the appcast to something else (like the previous value, or version), and use that to determine if an update occurred.
I’ve add a system like this in mind for a long time, but not to be included in casks. It’s basically be an external system that would then leverage cask-repair to automate the updates. The advantage would be we could output a common format that other apps/users would be able to take advantage of as well.

Sorry @vitorgalvao I missed this comment somehow.
Love the idea of an appcast do or similar but agree that it doesn't really seem to belong in the casks themselves. The idea of an external shared system of some kind would be great here too and probably more appropriate.
When I have a bit more spare time I'd be happy to open an issue on this one for discussion. I had already promised I would share some of my update finding methods so will wrap it in there as well.

When I have a bit more spare time I'd be happy to open an issue on this one for discussion. I had already promised I would share some of my update finding methods so will wrap it in there as well.

I’d appreciate that. I’d like to read your insights before working on it.


Integrations: Adobe DC View

My notes / TODO on the integration with Adobe's DC viewer

[ ] Delete annotations in the PDF when our thread is removed
[ ] Migrate thread data structure to W3C's annotation spec
[ ] Focus annotation in the PDF when the thread is focused
[ ] Reapply annotations in the PDF when our thread is reapplied (undo) and during initial mount
[ ] Remove unsupported features from the PDF reader (drawing tools, strikethrough, exports, etc)

Also of note - may not necessarily go with Adobe's. Mozilla's PDF reader is also pretty nice (and seemingly more lightweight) but I haven't looked into how easy it'll be to wire annotations into it. https://github.com/mozilla/pdf.js#online-demo


Issue Title: ImportError in CellPhoneDB - Cannot Import main

I'm encountering an ImportError when trying to run CellPhoneDB commands in my conda environment. The error message indicates that cellphonedb cannot import the main module from the package.
I have tried
conda create -n cpdb_env python=3.8
conda activate cpdb_env
pip install cellphonedb
cpdb_env) ashamoon@c37:/projects/mpn/Arzoo/Fleischhauer_lab/Integrated_ScRNA_analysis/Sample1234/CellPhoneDB$ cellphonedb method analysis test_meta.txt test_counts.txt
Traceback (most recent call last):
File "/homes/ashamoon/mambaforge/envs/renv/bin/cellphonedb", line 2, in
from cellphonedb import main
ImportError: cannot import name 'main' from 'cellphonedb' (/homes/ashamoon/mambaforge/envs/renv/envs/cpdb_env/lib/python3.8/site-packages/cellphonedb/init.py
(cpdb_env) ashamoon@c37:/projects/mpn/Arzoo/Fleischhauer_lab/Integrated_ScRNA_analysis/Sample1234/CellPhoneDB$ cellphonedb --help
Traceback (most recent call last):
File "/homes/ashamoon/mambaforge/envs/renv/bin/cellphonedb", line 2, in
from cellphonedb import main
ImportError: cannot import name 'main' from 'cellphonedb' (/homes/ashamoon/mambaforge/envs/renv/envs/cpdb_env/lib/python3.8/site-packages/cellphonedb/init.py)

Hi @ArzooShamoon,
Thanks for using CellPhoneDB! Seems like you're using CLI commands, but they are discontinued after v5 (not sure how they are both recognised and cannot be found) so you should use CellPhoneDB from Python instead of running CellPhoneDB commands from terminal.
Hope this helps!
Best,
Batu


Allow modification of velocityThreshold.

This PR makes settings.velocityThreshold mutable.
This setting was mutable in box2d, see the CHANGELOG.md entry "Made velocityThreshold mutable (as per jbox2d and other box2d implementations)."
It became constant in this changeset: https://github.com/flame-engine/forge2d/commit/a89ee1fd8cd1a066e6f191dd7c28340b1087bbc1
Without allowing it to be mutated, some simulations develop the behaviour described here: https://gamedev.stackexchange.com/questions/98851/body-lost-a-velocity-component-when-hitting-a-wall

Looks good, please add [Next] section in top of the changemog and add a line describing your change.

Nvm, I fixed that part. Thanks for your contribution!


Exception in callback of async function: TypeError: ready is not a function

Hi, i'm trying to CRONize phone calls
const sendCall = function (phone,ready) {
    phone = "+38050XXXXXXXX";
    bound(() => {
        ready();
        Meteor.call("sendCall",phone);
    });
};
cron.setInterval(sendCall, 60 * 1000, 'sendCall');

I'm having an issue:
Exception in callback of async function: TypeError: ready is not a function
question
What is for ready() and how it works?

Hello @valorloff ,
Here is example on passing arguments from the docs:
const cron = new CRONjob({db: db});
let variable = 'string';

const task = function (arg2, ready) {
  //...some code here
  ready();
};

const taskWithArgs = function (ready) {
  task(variable, ready);
};

cron.setInterval(taskWithArgs, 60 * 60 * 1000, 'taskWithArgs');

in your case:
const sendCall = function (phone, ready) {
    // Better to place `ready()` as a call back of Meteor.call method
    Meteor.call("sendCall", phone, ready);
};

const sendCallWrapper = function (ready) {
    phone = "+38050XXXXXXXX";
    bound(() => {
        ready();
        sendCall(phone, ready)
    });
};

cron.setInterval(sendCall, 60 * 1000, 'sendCall');

correction:
cron.setInterval(sendCallWrapper, 60 * 1000, 'sendCall');
It works!
Thanks for super fast response and great clarification

@valorloff I'm glad you've solved it 👍
Feel free to reopen it in case if the issue is still persists on your end.


replace print with logger

I would like to add one more thing.
By default, rich logs to standard output, but I think it is better to change it as follows.
https://github.com/Textualize/rich/issues/2022
Current
handler = RichHandler()

Proposal
from rich.console import Console
from rich.logging import RichHandler
handler = RichHandler(console=Console(stderr=True))


Broken position on InputEventMouse* event passed from moving child Control with MOUSE_FILTER_PASS

Godot version:
3.1 beta 5
OS/device including version:
X11 64 bits
Issue description:
Calculation of global_position and position in the InputEventMouse subclasses is broken when the event is passed from an offset child Control.
Note: assert(abs((event.global_position - get_global_mouse_position()).length()) < 10) also fails.
The problem is that event.position has the position relative to the child control that passed the event, and not to the control thats calling _gui_event. And it looks like global_position is being calculated from that, because the above assert is also failing.
In fact, you dont even have to click on the intersection of the two controls to trigger the error.
Steps to reproduce:
Open MRP, move the mouse and click on the bigger transparent white square.
MRP.zip

Note: assert(abs((event.global_position - get_global_mouse_position()).length()) < 10) also fails.
The problem is that event.position has the position relative to the child control that passed the event, and not to the control thats calling _gui_event. And it looks like global_position is being calculated from that, because the above assert is also failing.

I confirm: The assertion fails when hovering the gray square.
Godot 3.1 beta 7
Windows 10 x64

3.1.1 stable
Control node blocks InputEventMouseMotion to go to _unhandled_input
+
It seems that Control node blocks handled input on HTML5 builds as the _gui_input goes before _input.

This appears to be fixed in the master branch.
Probably fixed by #31915.


Error 500 instead of 404 if a controller is named testController

Hello,
I just found an interesting bug. When I make an empty controller calling any method returns error 404. But if I rename it to testController then I get an error 500, if the name is not an integer (/test/foo for example) :
Error (E_UNKNOWN) :: Encountered an unexpected error
: ER_BAD_FIELD_ERROR: Unknown column 'NaN' in 'where clause'

Best

really this is a bug or not?


pull request for e2e test at 12/12/2016 23:15:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Shadow blade not granting adv vs target in darkness and its attack roll not using highest attribute modifier

QuickSave_2.sav.zip
in this save, when attacking an enemy in the dark, the character has no adv. And I noticed when calculating ab and dmg, CHA is used instead of DEX, which is higher.

Fair enough, but the first issue is still there, perhaps.

yeah, will check the first one.

I cannot test any save on a location. Tests must be made on campaigns otherwise I won't be able to open the save.

fixed. I'll tweak that NONE on ADV to say Shadow Blade.


Spyder has encountered an Internal Problem

I try to reset the spyder, but it didnt work. Could anyone help me out with this.

Looks like the version of spyder-kernels doesn't match the version of spyder, try updating both.

How do I do it?
Any particular method?

Depends how you installed them, if you used conda for example:
conda update spyder-kernels
conda update spyder

okay, thanks. I'll try.

I'm still facing the same problem. I tried to reinstall it again.

@basangoudapatil, this error is fixed in our latest version (5.3.1).
Since it's still not available in Anaconda, you have two options:

Use our Windows installer, which you can find here.

Create a new environment with conda-forge packages. For that, please close Spyder, open the Anaconda Prompt and run the following commands there:
 conda create -n spyder-cf -c conda-forge spyder
 conda activate spyder-cf
 spyder


GPTMD needs max mods per peptide field

This seems like a straightforward thing but I'll just add a comment that "Max mods per peptide" is how many mods to search with. It doesn't define how many mods are annotated in the database. This distinction is obvious in the search and calibration tasks because PTMs aren't being annotated. But in the GPTMD window it's likely not clear. I'm not sure if a tooltip is enough to inform the user of this very important difference. Something to think about


Added sound commands and fixed two bugs here

This will fix the never ending settimezone command in #36 . Also making sure that requirements.txt contains all the necessary packages fixing #35 .
Added the soundlist command to get the current list of sounds
Added the soundrm <sound> command to remove given sound
Changed the us <sound> to soundupload
Moved sounds element to separare file
Changed sound messages resolve #37

Fixed #41 using python alpine image, also added a README.md file with how to install


bump versions of go used in tests

testing was done on versions 1.12 -> 1.16... all of which are old and started to cause issues in CI.  It looks like 1.18 and 1.19 are the versions currently being actively supported, and I've added 1.17 in case not everyone has updated at this point.  It's not feasible to test against every version of go but hopefully one unsupported prior version won't be a big deal 🤷

The licensed-ci GitHub Action has created a pull request containing license metadata updates based on the changes in this branch.
Please review the pull request for any additional changes required and merge when ready.

the drift between go with modules and go without modules was getting difficult to manage so I ended up removing testing support for go without modules.  To do that I moved the existing go without modules fixtures to a separate test/fixtures/dep folder, with a new script/source-setup/dep script and corresponding changes needed in various fixtures and test scripting


[libxml2] Update to v2.13.5

[X] Changes comply with the maintainer guide.
[X] SHA512s are updated for each updated download.
[X] The "supports" clause reflects platforms that may be fixed by this new version.
[X] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Update PR 39478 already exists.

Update PR 39478 already exists.

👋 @jimwang118  I’ve been trying to replace our custom registry at https://github.com/WebKitForWindows/WebKitRequirements with the canonical registry. Then I plan on integrating vcpkg into the build of WebKit.
I saw your PR but it seemed like you were having trouble with it. I have experience with building libxml2 and libxslt so that’s why I landed an update of the later in https://github.com/microsoft/vcpkg/commit/21692b2960b36564d42df3c3351ae7ddf211fb7b .
Comparing our two PRs I can see that it’s carrying over some stuff that’s obsolete. Like the pkgconfig specific changes. You can see they added stuff at https://github.com/GNOME/libxml2/blob/fe1ee0f25f43e33a9981fd6fe7b0483a8c8b5e8d/CMakeLists.txt#L385 which does the _LIBS changes. There’s also some commits added since the last release that obsolete some changes in that diff see https://github.com/GNOME/libxml2/commits/2.13/ .
There are also a number of build options that aren’t exposed in the feature listing that I was planning on adding to the vcpkg.json.
Apologies for not doing a thorough review of your PR making the above points. It’s after work hours for me and it’s hard to do a review through a phone.

/azp run

I reran the build to workaround a company-wide authentication issue that broke the first run but the failures now look legitimate:
/Users/vcpkg/Data/b/librsvg/src/librsvg-2-a2e28f96fe.clean/rsvg-css.c:866:20: error: incompatible function pointer types assigning to 'xmlStructuredErrorFunc' (aka 'void (*)(void *, const struct _xmlError *)') from 'void (void *, xmlErrorPtr)' (aka 'void (void *, struct _xmlError *)') [-Wincompatible-function-pointer-types]
    handler.serror = rsvg_xml_noerror;
                   ^ ~~~~~~~~~~~~~~~~
1 warning and 1 error generated.

It seems likely that rsvg_xml_noerror needs to be patched to have a different signature due to changes in libxml2?

I reran the build to workaround a company-wide authentication issue that broke the first run but the failures now look legitimate:
/Users/vcpkg/Data/b/librsvg/src/librsvg-2-a2e28f96fe.clean/rsvg-css.c:866:20: error: incompatible function pointer types assigning to 'xmlStructuredErrorFunc' (aka 'void (*)(void *, const struct _xmlError *)') from 'void (void *, xmlErrorPtr)' (aka 'void (void *, struct _xmlError *)') [-Wincompatible-function-pointer-types]
    handler.serror = rsvg_xml_noerror;
                   ^ ~~~~~~~~~~~~~~~~
1 warning and 1 error generated.

It seems likely that rsvg_xml_noerror needs to be patched to have a different signature due to changes in libxml2?

Yea I think the changes to that port from https://github.com/microsoft/vcpkg/pull/39478 need to be integrated. Will give that a go and add @jimwang118 as a co-author.

Alrighty added and credited @jimwang118 for his work. 🤞 were 🟢 and this can land

All features passed with following triplets:
x86-windows
x64-windows
x64-windows-static

Usage test passed on x64-windows.

@donny-dont , I think this might have led to build failure on iOS, with the following error:
[3/46] /Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -DLIBXML_STATIC -DSYSCONFDIR="/Users/runner/builddir/_deps/vcpkg-src/packages/libxml2_arm64-ios/etc" -I/Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/arm64-ios-rel -I/Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/src/v2.13.5-a978bfa150.clean/include -isystem /Users/runner/builddir/vcpkg_installed/arm64-ios/include -fPIC -fvisibility=hidden -g -pedantic -Wall -Wextra -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wno-long-long -Wno-format-extra-args -O3 -DNDEBUG -arch arm64 -isysroot /Applications/Xcode_15.4.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.5.sdk -miphoneos-version-min=14.0 -fPIC -MD -MT CMakeFiles/LibXml2.dir/dict.c.o -MF CMakeFiles/LibXml2.dir/dict.c.o.d -o CMakeFiles/LibXml2.dir/dict.c.o -c /Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/src/v2.13.5-a978bfa150.clean/dict.c
FAILED: CMakeFiles/LibXml2.dir/dict.c.o
/Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -DLIBXML_STATIC -DSYSCONFDIR="/Users/runner/builddir/_deps/vcpkg-src/packages/libxml2_arm64-ios/etc" -I/Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/arm64-ios-rel -I/Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/src/v2.13.5-a978bfa150.clean/include -isystem /Users/runner/builddir/vcpkg_installed/arm64-ios/include -fPIC -fvisibility=hidden -g -pedantic -Wall -Wextra -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wno-long-long -Wno-format-extra-args -O3 -DNDEBUG -arch arm64 -isysroot /Applications/Xcode_15.4.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.5.sdk -miphoneos-version-min=14.0 -fPIC -MD -MT CMakeFiles/LibXml2.dir/dict.c.o -MF CMakeFiles/LibXml2.dir/dict.c.o.d -o CMakeFiles/LibXml2.dir/dict.c.o -c /Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/src/v2.13.5-a978bfa150.clean/dict.c
/Users/runner/builddir/_deps/vcpkg-src/buildtrees/libxml2/src/v2.13.5-a978bfa150.clean/dict.c:970:17: error: call to undeclared function 'getentropy'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
if (getentropy(globalRngState, sizeof(globalRngState)) == 0)
^
1 error generated.

IMO this is an upstream issue then. IIUC iOS doesn't have getentropy. The offending call is guarded with HAVE_DECL_GETENTROPY. So something goes wrong at configuration/detection of HAVE_DECL_GETENTROPY.

@dg0yt , most likely yes, see this commit (https://gitlab.gnome.org/GNOME/libxml2/-/commit/e1657f3f272e87577aaf0c77aa040609394a0312).
The commit itself doesn't apply against 2.13.5; I've manually backported the commit into a patch locally and if that is successful I'll upstream.


Implement incremental backup as default and add a "-full" parameter

Restic supports incremental backup by providing a snapshot ID.
Incremental backup should be the default behavior. An additional parameter "-full" should force restic to read all files again.

Isn't this the same as #121 ?

True, thanks for reminding me!


Go to symbol in editor not respecting outline preferences

I find it strange that when opening the "Go to symbol in editor" prompt, outline preferences do not apply. They show the same thing. I like to have an epurated window with the strict minimum visible at once. I generally prefer to use keyboard shortcuts to show extra things when necessary.
In that spirit, I do not let the outline panel always visible. I prefer to use "Go to symbol in editor". Unfortunately, my outline view is customized to show the most important things only and thus I have much more items when using "Go to symbol in editor" which makes it quite useless (too verbose).
Maybe an option to link them together would be nice.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

We can filter outline and breadcrumbs, but not the go to symbol list... Why? It is the most useful search area with keyboard shortcuts.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

So sad. If someone from the team sees this: don't you think that's just a bug that should be resolved? The label "feature-request" doesn't feel accurate.

It is very strange, that we can filter 'outline' and 'breadcrumbs', but not the 'go to symbol' list.


Add Test Reporting to Travis CI

Test Reporting for Travis using Testspace.com
Hi ponyc team. We added test reporting to your repo. We have a blog article on why we are staging repos.
Note that there a lots of different ways to organize your test results. We choose creating folders based on the os type: linux and osx.  Note, if interested we could purse bringing in Windows running on AppVeyor.  Thus, would have all of your testing consolidated.
Few of the benefits using Testspace:

view all your test results from a single dashboard
triage and manage your test failures faster
add more metrics
leverage built-in analytics
get a test badge

Checkout your test results: https://open.testspace.com/projects/TryTestspace:ponyc from our fork.

Give Testspace a try?

Create Open (free) account: https://testspace.com/pricing
Add a New Project from the list of Github repo's
Add a Travis Environment Variable: Name: TS_ORG  Value: organization name - based on subdomain selected in step 1
Invite others: https://help.testspace.com/how-to:invite-other-users

Hi @jemc, @SeanTAllen,  @Praetonus I was hoping if you had a moment to take a look/review this pull request. It basically captures your test results and presents them in an organized format based on your source repo (and your os). There is no impact on the workflow. There are a number of benefits and we are working on more analytics to be rolled out in 2018.
We somewhat new to open source, but not the enterprise world. So we decided to fork repos and add the test reporting. This is our approach to getting users.
Mark


added installation instructions on installing without sqlite support

I've added a fix on the section title helper, since the menu displayed the escaped markup.


BUG plugin leaves junk in package.json after uninstall

Describe the bug
After uninstalling using cordova plugin rm cordova-plugin-ios-xhr the following is left in package.json
    "devDependencies": {
        "@globules-io/cordova-plugin-ios-xhr": "^1.0.5",

Expected behavior
Not leaving anything in package.json after uninstall.
Desktop (please complete the following information):
My environment:
node 10.22
npm 6.14.6
cordova 10.0.0
cordova-ios 6.1.0
ios-deploy 1.11.0

Additional context
Somewhat connected with #4.

Fix. Please do a PR next time.

Ok, thanks!


Improve error messages and classref for occluders and portals

Misused functions would previously produce no error messages which was confusing for users.
Fixes #71908
Notes

The same lack of error message was present in portals so I fixed that too.
Let me know any improvements on wording.

I get why the notice is needed for a method called set_point, but is there any confusion for other methods in this PR? We have many methods in the API that set some data for the provided index, and there is never an expectation that a method that is supposed to set a position or a radius of something would automagically create a new instance of that something, if the index is out of bounds.

I'm happy to remove the note on the set_position() and set_radius() if this is preferred, no strong feelings here, I don't think it matters a great deal one way or the other though here.

I just think it stands out when the rest of the docs never mention such a concern in similar situations. If confusion is unlikely, I'd drop it for the sake of the overall consistency.

Thanks!


fix(docs): correct typo in eslint-config-custom/package.json

Thank you for your attention to detail!


LSP does not find the "Content-Length" for psalm-language-server

The pattern Content%-Length:%s*(%d+) works well for most LS's however, the psalm-language-server returns response in the following format
{"jsonrpc":"2.0","method":"window\/logMessage","params":{"type":3,"message":"Initializing: Loading Reference Cache..."}}
Content-Type: application/vscode-jsonrpc; charset=utf8
Content-Length: 115

The current pattern does not match the Content-Length and therefore fails to init the LS.
As a quick workaround I'm modified line 1202 to
if output:find('^Content%-Length: %d+\r\n') or output:find('Content%-Length:%s*(%d+)') then

Can you share the config used to activate psalm?

Sure, see below
lsp.add_server {
  name = "psalmls",
  language = "php",
  file_patterns = {
    "%.php$",
  },
  command = {
    core.root_project():absolute_path("vendor/bin/psalm-language-server"),
    '--config', core.root_project():absolute_path("psalm.xml"),
    },
  incremental_changes = true,
  verbose = false
}

Finally tested this and as you shared above just removing the ^ fixed the issue but it seems that psalm has some issues with my installed PHP version (8.2.12) and I keep getting the following when typing on the document:
[psalm-language-server] RuntimeException: PHP Error: Undefined property: stdClass::$range in vendor/vimeo/psalm/src/Psalm/Internal/LanguageServer/Server/TextDocument.php:122 for command with CLI args "vendor/bin/psalm-language-server --config psalm.xml" in vendor/vimeo/psalm/src/Psalm/Internal/ErrorHandler.php:77

Now that PHP removed or deprecated dynamic properties it has become a nightmare for code that depended on that :S
Anyway fixed it with:
-        if (count($contentChanges) === 1 && isset($contentChanges[0]) && $contentChanges[0]->range === null) {
+        if (count($contentChanges) === 1 && isset($contentChanges[0]) && (!property_exists($contentChanges[0], "range") || $contentChanges[0]->range === null)) {

But I'm not getting any autocompletion or diagnostics as far as I see, maybe I need to configure something on the psalm.xml file


Config options: Namespace, PrettyPrint, and Export I18n JS

This commit adds the following features:

Add :namespace option to config (per segment) which sets the Javascript namespace in the translations output file in order to avoid namespace conflicts
Add :pretty_print option to config (per segment) which writes the output file with linebreaks and indentation
Add :export_i18n_js to config (global) which functions the same as I18n::JS.export_i18n_js_dir_path

In addition, I have refactored the following:

Extract "Segment" class which handles writing of translation JSON files, and allows options to be set per-segment. Includes specs.
Move some specs to new sprockets_spec.rb and utils_spec.rb files to reduce bloat
Minor change of I18n::JS.export_i18n_js_dir_path so that any non-String is interpreted as "do not export". This should not break existing implementations, and also the README has previously said the only way you can set path is via a String variable.

@PikachuEXE please consider merging this soon.

:+1:

First, I think this pull request too too big to be reviewed properly.
Second, I am very busy for my job until mid-March :s
Third, I actually plan to move the config out of yml. (#298)

Having pretty print would be really helpful!

@PikachuEXE

Most of the PR code is just tests for the new functionality. All I've done is re-factored the currently bulky export process to be slightly more object oriented, i.e. introducing a Segment object which encapsulates the JSON generation and can take options.

Can anyone else help review?

Can you give an example of what you mean by moving config out of yml? My design in this PR is that each export file should take its own generation options--this is very useful for my app. Example:

translations:
- file: "public/javascripts/file_1.js"
  pretty_print: true
  only:
    - '*.date.abbr_day_names'
    - '*.date.month_names'
    - '*.date.abbr_month_names'

- file: "some/other/dir/file_2.js"
  namespace: "CustomI18n"
  only:
    - 'en.my.key'

You can ignore point 3 for now.
Point 1 is related to point 2.
The diff is quite big so I can't review it with the time I have.

@PikachuEXE would it help for me to break into 3 PRs:

Segment change (refactor)
namespace + pretty_print options
export_i18n_js option

@johnnyshields yessss
I feel painful when I have to deal with many "big" internal PR in my company :sos:

OK done. Raised #299, #300, #301, and #302.
Please merge 299-301 in order.
302 can be merged by itself

Will check soon! Thanks!


Fix: crash caused by video path containing non-ASCII characters

In windows/my_grabber_player.cpp line 390.
If the video path contains non-ASCII characters (e.g. C:/Users/Public/Videos/中文.mp4), it will pass url-encoded path to the MFSourceResolver API (e.g. file:///C:/Users/Public/Videos/%E4%B8%AD%E6%96%87.mp4).
If pass a path to the MFSourceResolver API with file:// scheme , it will url-decode the path. It treats the "%" character as a url encoded string. But the IMFSourceResolver API does not support url decoding of non-ASCII characters for the file:// scheme, so the video cannot be loaded and causes a crash.

Another example is when the path is file:///C:/Users/Public/Videos/example%20.mp4, the example .mp4 video will be loaded.

If pass a path to the MFSourceResolver API WITHOUT file:// scheme, it will NOT url-decode the path. It treats the "%" character as normal string.

e.g. the path is C:/Users/Public/Videos/example%20.mp4, the example%20.mp4 video will be loaded.

Which version of video_player_win are you using?
I test on video_player_win: 2.2.2,
and it works for me with the following code:
var controller = WinVideoPlayerController.file(File("E:\\test 中文.mp4"));
var controller = WinVideoPlayerController.file(File("file:///E:/test_中文.mp4"));
var controller = WinVideoPlayerController.file(File("file:///E:/test 中文.mp4"));   // with a white-space in it

I' m test on video_player: ^2.7.1 and video_player_win: 2.3.0.
If using WinVideoPlayerController standalone, everything works fine.
Because the file path will not be url encoded.
If using "VideoPlayerController", the file path passed in is url encoded.
It will call lib/video_player_win_plugin.dart Future<int?> create(DataSource dataSource) from video_player_platform_interface.
You can verify this issue with the following code:
var controller = VideoPlayerController.file(File("E:\\test 中文.mp4"));

That's right.
The new version of video_player will encode path string, and make native player wrong.
Thanks for the code change.


[WIP] Img exif

PR Checklist

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[ ] I have checked that this PR does not introduce a breaking change

PR Type
What kind of change does this PR introduce?

[ x] Bugfix

Fixes
Issue Number: #3435
What is the current behavior?
EXIF data is ignored, this leads to photos been shown with the wrong orientation. This can be a problem as people take photos with their smart phones upside down and sideways.
What is the new behavior?
The orientation of the photo is honoured using EXIF data.
Other information
At the time of writing this PR this patch only works for the preview, I still need to implement this for the thumbnails.
I thought I would submit this now because I was wondering if it was okay to use the blueimp-load-image library.
https://github.com/blueimp/JavaScript-Load-Image
In the future, it might be a good idea if the client could remove such meta data on upload. Especially since it can contain Geo data.

Thanks for the PR @tuxfoo ! We'll get a review on this soon. Once it's completed, can we show you some appreciation ?

@tuxfoo would still love to see this, but will probably close PR next week if no progress
malicious EXIF data can be considered out of scope here


Request for MLC Version Update and NVILA Support in nano_llm Model

Hi,
Thank you for your amazing work on this project! I have two requests:
Could you please update the MLC version to the latest release? This would help us keep our setup up to date.
I’m also using the nano_llm model and was wondering if there are any plans to add support for NVILA. This would be very useful for applications that require both visual and linguistic integration.
If these updates are not currently planned, any guidance on how we might implement them ourselves would be greatly appreciated.
Thank you again for your time and support!

Hi !, yes, I am about halfway through updating MLC to the latest haha.   I hope for it to be ready by Jan 1.  I had meant to release the container along with Orin Nano Super, but hit a couple build issues and had to circle back.
I am also updating jetson-ai-lab.com with a Javascript 'model configurator' that will give you the right 'docker run' or docker-compose to spin up local OpenAI-protocol server (these are now provided by MLC, TRT-LLM, vLLM, llama.cpp, ollama)
That approach is more scalable going forward than me being able to keep NanoLLM updated (also at that time there hadn't been the OpenAI servers , and they haven't supported img2txt Completion for VLMs)
For NVILA, that is supposed to be available through vLLM, and was hoping to also rebuild that container.  Will work through these!   Ultimately this will keep them updated easier 👍

From: JIA-HONG-CHU @.>
Sent: Thursday, December 26, 2024 2:27:02 AM
To: dusty-nv/NanoLLM @.>
Cc: Subscribed @.***>
Subject: [dusty-nv/NanoLLM] Request for MLC Version Update and NVILA Support in nano_llm Model (Issue #61)
Hi,
Thank you for your amazing work on this project! I have two requests:
Could you please update the MLC version to the latest release? This would help us keep our setup up to date.
I’m also using the nano_llm model and was wondering if there are any plans to add support for NVILA. This would be very useful for applications that require both visual and linguistic integration.
If these updates are not currently planned, any guidance on how we might implement them ourselves would be greatly appreciated.
Thank you again for your time and support!
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/NanoLLM/issues/61, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADVEGK5B63CKEQXYP5CZX4T2HOVUNAVCNFSM6AAAAABUG23VBWVHI2DSMVQWIX3LMV43ASLTON2WKOZSG42TSMZZHE2DSNQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Windows 10 Edge cursor bug

Throwing this foxhole ticket here:
Description:
Upon dragging the carousel over the image or copy, notice that the hand cursor will not change into a drag cursor. Only happens when dragging the current item.
Expected behavior:
Is this a limitation? If not, cursor icons should be consistent with drag gestures.
Browser:
Windows 10 - Chrome, Edge

Can you gimme the link to the Asana task?  Hoping there is a vid there cause I don't really get it yet.

See https://app.asana.com/0/0/1201922496048500/f

@jonjahr, closing this since https://app.asana.com/0/0/1201922496048500/f was resolved ... issue was maybe fixed by some other fix

Here’s the ticket: https://app.asana.com/0/1201922496048500/1201922496048500

From: Robert Reinhard @.>
Sent: Thursday, March 10, 2022 5:12:42 PM
To: BKWLD/vue-ssr-carousel @.>
Cc: Jonathan Jahr @.>; Author @.>
Subject: Re: [BKWLD/vue-ssr-carousel] Windows 10 Edge cursor bug (Issue #60)
Can you gimme the link to the Asana task? Hoping there is a vid there cause I don't really get it yet.
—
Reply to this email directly, view it on GitHubhttps://github.com/BKWLD/vue-ssr-carousel/issues/60#issuecomment-1064673050, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABT4275F3V33FMX34YYPFQLU7KMYVANCNFSM5QOHCNWA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>


Weird behaviour if first glob in array is using '**'.

if I do a thing like
const copy = require('copy');

const files = ['dist/**/*','README.md','LICENSE.md'];
copy(files, '/tmp/folder', (err, files) => {
 // handle result here
})

Result :

README.md and LICENSE.md are located in /tmp
The content of the dist folder is in '/tmp/folder'

Should be :

README.md and LICENSE.md are located in /tmp/folder
The content of the dist folder is in /tmp/folder/dist

Note that the order of the globs is important as if i declare it like :
const files = ['README.md','LICENSE.md','dist/**/*'];

It behaves as intended.

strange, I'll look into it. I'm guessing it has to do with how the glob parent is created. thanks for the issue

Honestly, I just switched to using vinyl-fs.
const vfs = require('vinyl-fs');

function copyFiles(glob, dest) {
  return new Promise((resolve, reject) => {
    // the base is important, if not set it will put all
    // files directly in the 'dest' folder
    const stream = vfs.src(glob, { base: '.' })
      .pipe(debug({
        minimal: false
      }))
      .pipe(vfs.dest(dest));
    stream.on('finish', () => {
      resolve();
    });
    stream.on('error', (error) => {
      reject(err);
    });
  });
}

Honestly, I just switched to using vinyl-fs.

That's great. we use vinyl-fs quite a lot, and we contribute a lot to that ecosystem (gulp and vinyl). It's a bit overkill for simple copying, but I don't blame you after having issues with this lib.

FYI for anyone that comes across this issue... You can set the srcBase option to specify the base property used when creating file objects. This is similar to setting the base option on vfs.src in the example above.
updated example from original comment
const copy = require('copy');

const files = ['dist/**/*','README.md','LICENSE.md'];
copy(files, '/tmp/folder', {srcBase: '.'}, (err, files) => {
 // handle result here
})

I'm going to keep this open for now since this is something we need to update in the documentation.


Clicking on attachments does nothing...

Submit feature requests to http://www.mattermost.org/feature-requests/. File non-security related bugs here in the following format:
Summary
I'm noticing when I'm using Mattermost on iPhone, if Danielle sends a Word file or a PDF file, I can't launch or open the Word doc or PDF file. This is pretty limiting.
Environment Information

Device Name: Iphone 5SE
OS Version: 11
Mattermost App Version: Most recent
Mattermost Server Version: unknown

Steps to reproduce
Try to open an attachment from a mattermost chat
Expected behavior
The attachment should open in the default handler for that file type.
Observed behavior
Nothing happens, no errors or anything.
Possible fixes
If you can, link to the line of code that might be responsible for the problem.

Hi @Patriccarver - we're working on adding previews for other file types, and will also be looking into adding sharing files to other apps, and downloading files to iOS devices (download is already supported on Android).
Pull request is here with the start of the work: https://github.com/mattermost/mattermost-mobile/pull/1170


Does not autohide in youtube videos

Looks like this isn't maintained anymore but this seems important since it's a problem with youtube.
With youtube's change to their player, where you can now "scroll down for details", the scrollbar will now show on the video.

I can confirm this. I get the same in Chrome 73.0.3683.86

No longer an issue after changes from youtube.


[WIP] Static matrix design doc December update

Note: This is a WIP design doc -- we'll merge it into the main design doc (https://github.com/stan-dev/design-docs/pull/21) later
@SteveBronder @rok-cesnovar @t4c1 I tried to do a rewrite of the design doc focused on setting up the language discussion again.
I think brevity is our friend here, so I didn't avoided examples and implementation details as much as possible. We can always link to the implementation stuff we have now.
Rendered version

I realized we called the test function for varmat expect_ad_matvar. Seems like it should be expect_ad_varmat lol.

@syclik @t4c1 thanks for comments, I made the edits (or comments)

Also, maybe we should not list option 2 here as 1, 3 and 4 are end-game options:

new type
smart use of varmat (avoid when heavy single-cell indexing is used)
varmat only

2 is just a midpoint because we can't realistically expect to implement everything for 2.26. If everything in Math has varmat 2 becomes either 3 or 4.

I'll add that 2 is kindof a stepping stone, but if it is something we're considering for release we should have it in the design doc.

Edits in. Hopefully stuff looks okay? At this point the thing that bothers me are the old varmat benchmarks. We should have something newer.
@rok-cesnovar mentioned maybe we should remove the version of the compiler with explicit types from this. That was the original design, but I agree now it looks unnecessary and difficult. If it's not an option we're considering, let's remove it. If nobody objects I'll remove it tomorrow sometime.
Does tomorrow afternoon work to reopen the design doc pull with this? I think we should close the old one and open a new one just to get a refresh on the conversation. That last one was loooooong (https://github.com/stan-dev/design-docs/pull/21). Can ofc. link back to it.

A few interesting comments from the last design:
On assigning to varmat: https://github.com/stan-dev/design-docs/pull/21#discussion_r421833109
Something about a LHS -- seemed interesting but not sure what it was: https://github.com/stan-dev/design-docs/pull/21#issuecomment-623697543
How to construct varmats directly: https://github.com/stan-dev/design-docs/pull/21#issuecomment-625537542
Betancourt weighing in on elementwise modification: https://github.com/stan-dev/design-docs/pull/21#issuecomment-626918408

From reading the previous design doc comments, what is missing here is a discussion of what member functions are required in the different var_value<T> types. The previous doc says linking to C++ implementation is not the right way to do this.

Also, if I remove explicit types as an option here, this leaves two options at the compiler level:
1. Use `matvar` types if there is at least one function in the Stan program that does not support `varmat`

2. Use `varmat` types by default, but if variable assignment is detected, or a `varmat` is used
in an unsupported function convert to and from `matvar` automatically.

Is the first thing here something we're thinking about seriously? I don't like the first that much. The 2nd seems better and more like what is being discussed: https://github.com/stan-dev/design-docs/pull/29#discussion_r542767273
And there are the scalar access benchmarks. I'll try to do some of those today so we have them. Maybe with that we actually do have a pretty complete idea of what the language implementation will look like and can finish that part of the doc.

Code below, double checks are appreciated.

Here's the code: https://gist.github.com/bbbales2/347ea12273ed90b1df35d55cf247989e
A slowdown of 1 (the y-axis) would mean that the two things run at the same speed.

So reading this it looks like for something like
vector[N] A = //fill in;
vector[N] B;
for (i in 1:N) {
  B[i] = some_func(A[i]);
}

would be about 4x as slow?

I thought it would have been about the average of the two, but it's much much expensive!
Code here

Just saving this text here:
For implementation of `vari_value<T>` where `T` is an Eigen dense type (the basic `varmat`),
look [here](https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/vari.hpp#L604)

For implementation of `vari_value<T>` where `T` is an Eigen expression, look
[here](https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/vari.hpp#L546). The
Eigen expressions implemented are ones that can be implemented as views into another matrix.
So blocks of matrices, matrix transpose, column-wise access, etc. are supported.

For implementation of `vari_value<T>` where `T = double` (the reimplementation of var),
look [here](https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/vari.hpp#L81)

For implementation of `vari_value<T>` where `T` is an OpenCL type, look
[here](https://github.com/stan-dev/math/blob/develop/stan/math/opencl/rev/vari.hpp#L23)

For implmementation of `vari_value<T>` where `T` is an Eigen sparse type, look
[here](https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/vari.hpp#L746)

Can we do a Hangouts tomorrow to write a 0.1 compiler spec? Just to get a reasonable baseline written out? Like 9 or 10AM
or 11AM EST?
I tried to write it myself and wasn't really getting very far.
I think I could share screen and ask questions and get something written down pretty quick, but I'm kinda clueless on compiler stuff by myself.

Yeah sure let's do like 11

Lest @rok-cesnovar and @t4c1 want to join and meet at an earlier time

@SteveBronder Rok said he had car repair to do, so we'll flex the time a bit to what works for him. Will message on slack when it's go-time.

@rok-cesnovar @SteveBronder @t4c1 alright, design doc up with a full compiler implementation we discussed this AM and the dependencies on the C++ implementation removed. Have another skim through (and then we can make this an official design-doc pull and get comments, etc. etc.).

I like it! Do we have a few other folks look over this then it goes to an accept / reject vote?

Next step is making it the varmat design doc and getting comments from everyone. Rok was happy with this version, so since you're happy with it too I'll go ahead and make it the varmat doc and go about summoning comments.


Temporarily disable OIT by default for iOS and iPad

Due to increased reports of https://github.com/CesiumGS/cesium/issues/9827, this disables orderIndependentTranslucency by default on iOS and iPad as a temporary workaround.

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @ebogo1.

Have we checked that this branch fixes issues on the newer devices?

Do you mean other than the issues which were brought up in https://github.com/CesiumGS/cesium/issues/9827?

I meant more to check that navigator.platform was identifying iOS devices as the iPad iPhone iPod strings. I couldn't find an official list of its possible values. Happy to merge if we're confident that those are correct, I just wanted to double check.

I was able to verify this is working on my iPhone, logging the value of Scene.orderIndependentTranslucency:

I tried my iPad, which is a iPad Pro. Unfortunately I believe this type of iPad always presents the desktop version of a website, so the value of navigator.platform is MacIntel, same as my desktop. However, I believe it should work for smaller and older models of iPad.

Cool, thanks @ggetz!


Add transforms fuzzer.

It simulates internal modular decoder workflow:

create "output" image
meta-apply transforms
simulate decode (fill "transformed" channels with data)
undo transforms

Drive-by: fix indentation in tools/CMakeLists.txt

Another possible thing to do is to make a random image, apply random lossless fwd transforms to a copy of it, and check it applying inv transforms to the result of that gives back the original image data.

Sure, why not!

Did you try running the fuzzer for a while? how did you test this?

I've compiled with ossfuzz-asan and runned overnight.
Current stats: cov: 875 ft: 4559 corp: 824/30Kb lim: 4096

If, e.g. I rebase it onto
commit f49870935c95ac20de5f6ec939e5e4080cc189c8
Author: Sami Boukortt<EMAIL_ADDRESS>Date:   Tue Jul 27 16:12:29 2021 +0200

    Fix benchmark_xl with grayscale images

(before recent fixes) it quickly discovers (with current corpus):
==1917423==ERROR: AddressSanitizer: container-overflow on address 0x620000237a08 at pc 0x558d99a5eacd bp 0x7ffdb225ef30 sp 0x7ffdb225ef28
READ of size 8 at 0x620000237a08 thread T0
    #0 0x558d99a5eacc in jxl::InvSqueeze(jxl::Image&, std::__1::vector<jxl::SqueezeParams, std::__1::allocator<jxl::SqueezeParams> >, jxl::ThreadPool*) /src/libjxl/lib/jxl/modular/transform/squeeze.cc:300:51
    #1 0x558d999ef24e in jxl::Transform::Inverse(jxl::Image&, jxl::weighted::Header const&, jxl::ThreadPool*) /src/libjxl/lib/jxl/modular/transform/transform.cc:30:14
    #2 0x558d999e98a6 in jxl::Image::undo_transforms(jxl::weighted::Header const&, int, jxl::ThreadPool*) /src/libjxl/lib/jxl/modular/modular_image.cc:20:23
    #3 0x558d999b16fc in jxl::TestOneInput(unsigned char const*, unsigned long) /src/libjxl/tools/transforms_fuzzer.cc:116:9
    #4 0x558d999b5134 in LLVMFuzzerTestOneInput /src/libjxl/tools/transforms_fuzzer.cc:146:10
    #5 0x558d998b1a93 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:599:15
    #6 0x558d998b0f9a in fuzzer::Fuzzer::RunOne(unsigned char const*, unsigned long, bool, fuzzer::InputInfo*, bool, bool*) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:505:3
    #7 0x558d998b3374 in fuzzer::Fuzzer::ReadAndExecuteSeedCorpora(std::__Fuzzer::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:814:7
    #8 0x558d998b3589 in fuzzer::Fuzzer::Loop(std::__Fuzzer::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:845:3
    #9 0x558d998a2db4 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:906:6
    #10 0x558d998cc982 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
    #11 0x7f42d3d15d09 in __libc_start_main csu/../csu/libc-start.c:308:16
    #12 0x558d99878288 in _start (/usr/local/google/home/eustas/clients/libjxl/build-asan/tools/transforms_fuzzer+0x78288)

0x620000237a08 is located 2440 bytes inside of 3584-byte region [0x620000237080,0x620000237e80)
allocated by thread T0 here:
    #0 0x558d999abd3d in operator new(unsigned long) /src/llvm-project/compiler-rt/lib/asan/asan_new_delete.cpp:99:3
    #1 0x558d999f26ee in __libcpp_operator_new<unsigned long> /usr/local/bin/../include/c++/v1/new:235:10
    #2 0x558d999f26ee in __libcpp_allocate /usr/local/bin/../include/c++/v1/new:261:10
    #3 0x558d999f26ee in allocate /usr/local/bin/../include/c++/v1/memory:840:38
    #4 0x558d999f26ee in allocate /usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:260:20
    #5 0x558d999f26ee in __split_buffer /usr/local/bin/../include/c++/v1/__split_buffer:314:29
    #6 0x558d999f26ee in std::__1::vector<jxl::Channel, std::__1::allocator<jxl::Channel> >::insert(std::__1::__wrap_iter<jxl::Channel const*>, jxl::Channel&&) /usr/local/bin/../include/c++/v1/vector:1827:53
    #7 0x558d99a5e0f5 in jxl::MetaSqueeze(jxl::Image&, std::__1::vector<jxl::SqueezeParams, std::__1::allocator<jxl::SqueezeParams> >*) /src/libjxl/lib/jxl/modular/transform/squeeze.cc:272:21
    #8 0x558d999f15ab in jxl::Transform::MetaApply(jxl::Image&) /src/libjxl/lib/jxl/modular/transform/transform.cc:64:14
    #9 0x558d999b0e42 in jxl::TestOneInput(unsigned char const*, unsigned long) /src/libjxl/tools/transforms_fuzzer.cc:105:20
    #10 0x558d999b5134 in LLVMFuzzerTestOneInput /src/libjxl/tools/transforms_fuzzer.cc:146:10
    #11 0x558d998b1a93 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:599:15
    #12 0x558d998b0f9a in fuzzer::Fuzzer::RunOne(unsigned char const*, unsigned long, bool, fuzzer::InputInfo*, bool, bool*) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:505:3
    #13 0x558d998b3374 in fuzzer::Fuzzer::ReadAndExecuteSeedCorpora(std::__Fuzzer::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:814:7
    #14 0x558d998b3589 in fuzzer::Fuzzer::Loop(std::__Fuzzer::vector<fuzzer::SizedFile, fuzzer::fuzzer_allocator<fuzzer::SizedFile> >&) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:845:3
    #15 0x558d998a2db4 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:906:6
    #16 0x558d998cc982 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
    #17 0x7f42d3d15d09 in __libc_start_main csu/../csu/libc-start.c:308:16

HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_container_overflow=0.
If you suspect a false positive see also: https://github.com/google/sanitizers/wiki/AddressSanitizerContainerOverflow.
 Test unit written to ./crash-84e30b22f013130c73fb7abb28cd5f6d15acf65c
Base64: CjaJERERM3t79ns3AO4QfNEAyC4AgAt0ewEuwBERERELCwsLCwsLCwsLCwEj11Oat0U=

Friendly ping.


Few manga are repeated

When more was clicked Roppongi Black cross, Aishichattano, and Narutaru were repeated.

Please add in more details as to how to reproduce it and where it is happening so it is easier to debug

It is happening on the first page last three manga.

Yes correct, please try to get in a fix :smile:

I can give it a try. It'll take time though

Sure thanks, take your time.


Jolokia xml schemas defined in examples are missing from website

fo rinstance https://www.jolokia.org/jolokia-spring/schema/config/jolokia-config.xsd is defined but ther eis a 404

duplicates of https://github.com/jolokia/jolokia/issues/493


_ prefix for unused locals

The following code should be allowed by _ prefix for declaration of nominal types.
TypeScript Version:  master
Code
class C {
  private _: void;
}

Expected behavior:
$ node built/local/tsc.js --noEmit --lib es6 --noUnusedLocals index.ts

Actual behavior:
$ node built/local/tsc.js --noEmit --lib es6 --noUnusedLocals index.ts
index.ts(2,11): error TS6133: '_' is declared but never used.

Some people are going to prefix all privates with _ as a naming convention and will find the lack of checking odd. Why are you in this state?

The fix here is to use the local somewhere, or declare it as public or protected.
The only exclusion we have added is for function parameters, since a function might not be using all the functions it declares.

@RyanCavanaugh I'm using nominal types to distinguish commands.
type WorkerCommand<T, D>
  = WorkerCommand.Deps<T>
  | WorkerCommand.Call<D>
  | WorkerCommand.Exit;

namespace WorkerCommand {
  abstract class AbstractCommand {
    private WORKER_COMMAND: void;
  }
  export class Deps<T> extends AbstractCommand {
    private COMMAND: this;
    constructor(public namespace: T) {
      super();
    }
  }
  export class Call<D> extends AbstractCommand {
    private COMMAND: this;
    constructor(public data: D) {
      super();
    }
  }
  export class Exit extends AbstractCommand {
    private COMMAND: this;
    constructor(public reason: any) {
      super();
    }
  }
}

@mhegazy I see, thanks.


Add uthmani font

Why? Uthmani font is not used with 16 line page format, so it doesn't make any sense to me

Why? Uthmani font is not used with 16 line page format, so it doesn't make any sense to me

For me it is much more easier in uthmani script

does this look good?

There are minor issues with pause-mark placement. Its hard to find a good non-indopak font that can work with the Quran text I am using.

does this look good?

There are minor issues with pause-mark placement. Its hard to find a good non-indopak font that can work with the Quran text I am using.

Bro look at this picture and what do you think which picture is easy to read

The colors can be adjusted, but the pure black background is intentional because it saves battery life if your phone has an AMOLED screen.
After checking a bit, it seems that the uthmani script doesn't have a lot of pause marks that we have in indopak script. So indopak text will appear incorrect with an uthmani font. There are a lot of other things missing in my screenshot above like no hamza-tul-wasl
The problem here is that it took a lot of effort to create the 16 line text format that this app has, see the data. Adding uthmani text in there is going to take a huge amount of effort which I am not sure is worth it at all.
If it was as easy as just changing the font, I'd have done it.
So to be able to support this, we need the correct uthamani text data with pagination first.

The colors can be adjusted, but the pure black background is intentional because it saves battery life if your phone has an AMOLED screen.
After checking a bit, it seems that the uthmani script doesn't have a lot of pause marks that we have in indopak script. So indopak text will appear incorrect with an uthmani font. There are a lot of other things missing in my screenshot above like no hamza-tul-wasl
The problem here is that it took a lot of effort to create the 16 line text format that this app has, see the data. Adding uthmani text in there is going to take a huge amount of effort which I am not sure is worth it at all.
If it was as easy as just changing the font, I'd have done it.
So to be able to support this, we need the correct uthamani text data with pagination first.

Bro could you recommend some Quran reading apps which use does not internet. Most of the Quran apps in F-droid and play store use internet access . Bro I am not trying to be rude or something

Hmm, I checked a few apps but seems like almost every app requires internet.. at least for translation. This one (on fdroid) https://github.com/mirfatif/NoorUlHuda can be used for reading without internet it seems.
After checking out the available data, I think I will try to add support for uthmani quran text. Can you help with testing?

Salam Waqar Brother my name is Talha Ramzan and I'm from Pakistan and I also want this revision helper edition Holy Quran in Uthmani font with 16 line overlay
If it's not much difficult for you then we would appreciate your work if you make one for some users like us. Or else you can tell us the way to make it because I would be going with software development next year InshAllah.
I guess then I myself will be able to get it ready.
May Allah almighty grant me determination .
We all love your work.
May Allah grant you better return if your hard work on the day of judgement.
Wassalam.
Request you to pray for us and our Palestinian brothers and sisters.

@McRamzan see my comments above. Its not easy and 16 line + Uthmani is something I have never seen in real life, if you have a sample, please share. Note that this 16 line format is not something I made up myself, its based on the actual 16 line version of Quran that is used in Pakistan.
I have plans to create a 15 line version at some point though.


migrate miq_groups to assign sequence and guid

per request from @matthewd add sequence and guuid to miq groups the right way
This is already part of #5186
/cc @matthewd let me know if you like this
/cc @gmcculloug fyi

ping @matthewd I made these changes on capablanca PR, would like to move these over to master so we don't loose them


Update scale to zero documentation

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

$subject to explain scale to zero feature and add screenshots
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

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


build: Generate lists of source files at bootstrap time in src_vars.mk.

This moves the definition of SYSAPI_SRC, COMMON_SRC, LOCALTPM_SRC,
SAMPLE_SRC and TPMSOCKETS_SRC variables to src_vars.mk. This file is
generated at bootstrap time and the list of source files in each
variable generated dynamically. We leave the list of source files for
the applications (resourcemgr and tpmclient) in the Makefile.am due
to the Windows specific files in the tpmclient directory that the
bootstrap script would pickup. We can work around these with #ifdefs
in the future if necessary.
This resolves #26.
Signed-off-by: Philip Tricca<EMAIL_ADDRESS>

Need to rebase to latest code.

Should be good to go.


Add safeguarding_concerns and relationship_corrections to references

Context

We want to allow referees to say whether the applicant is a suitable candidate to work with children so that a provider can properly assess their application. We also want them to confirm and correct their relationship with the candidate.
Changes proposed in this pull request

This PR adds a migration with two columns to the referees table

safeguarding_concerns to record (if any) concerns as a string
relationship_correction to record (if any) incorrect details are in the relationship field

Guidance to review

Does this make sense? Shall we just amend the existing relationship field instead of using a separate relationship_correction field is cleaner? I'm open for suggestions
Link to Trello card

https://trello.com/c/QlKuThen/1130-build-referee-view-of-candidate-working-with-children
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

I think this makes sense, having two separate fields as part of a Reference as it seems from the provider view (https://bat-design-history.netlify.com/apply-for-teacher-training/give-a-reference-second-iteration#provider-view-with-amended-relationship)
Thanks, Ting, this is super helpful. What do you think @tvararu, are you happy with these changes?


Creating Migrations after vendor:publish

Describe the bug
When I ran "php artisan vendor:publish --all" package creating migrations. But I already have the tables
Versions (please complete the following information)

PHP: 8.0.5
Database: PostgreSQL 13
Laravel: 8.40.0
Package: 4.0.0

@freekmurze I believe that's an issue in the spatie package tools. 🤔
As that package publishes the migration it should check if the class already exists.

I've been taking a look to the spatie/laravel-package-tools and I've seen where the bug is coming from. The hasMigration() method is expecting a snake case migration name, like create_activity_log_table but activitylog is using CreateActivityLogTable (see it here).
There are two options:

Just change the name of the stubs to be snake case and update the hasMigration() call.
Modify the migrationFileExists() method in spatie/laravel-package-tools (here to allow non-snake case migration names.

I'm going to submit a PR with option one.


Write provider settings file from API

Right now we have settings.json kept as provider settings. To avoid this going stale, we need to build up and write this file via the provider config API.

Fixed via #28