Relicense under dual MIT/Apache-2.0

This issue was automatically generated. Feel free to close without ceremony if
you do not agree with re-licensing or if it is not possible for other reasons.
Respond to @cmr with any questions or concerns, or pop over to
#rust-offtopic on IRC to discuss.
You're receiving this because someone (perhaps the project maintainer)
published a crates.io package with the license as "MIT" xor "Apache-2.0" and
the repository field pointing here.
TL;DR the Rust ecosystem is largely Apache-2.0. Being available under that
license is good for interoperation. The MIT license as an add-on can be nice
for GPLv2 projects to use your code.
Why?
The MIT license requires reproducing countless copies of the same copyright
header with different names in the copyright field, for every MIT library in
use. The Apache license does not have this drawback. However, this is not the
primary motivation for me creating these issues. The Apache license also has
protections from patent trolls and an explicit contribution licensing clause.
However, the Apache license is incompatible with GPLv2. This is why Rust is
dual-licensed as MIT/Apache (the "primary" license being Apache, MIT only for
GPLv2 compat), and doing so would be wise for this project. This also makes
this crate suitable for inclusion and unrestricted sharing in the Rust
standard distribution and other projects using dual MIT/Apache, such as my
personal ulterior motive, the Robigalia project.
Some ask, "Does this really apply to binary redistributions? Does MIT really
require reproducing the whole thing?" I'm not a lawyer, and I can't give legal
advice, but some Google Android apps include open source attributions using
this interpretation. Others also agree with
it.
But, again, the copyright notice redistribution is not the primary motivation
for the dual-licensing. It's stronger protections to licensees and better
interoperation with the wider Rust ecosystem.
How?
To do this, get explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright, due to not being a "creative
work", e.g. a typo fix) and then add the following to your README:
## License

Licensed under either of

 * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
 * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

and in your license headers, if you have them, use the following boilerplate
(based on that used in Rust):
// Copyright 2016 sysconf.rs Developers
//
// Licensed under the Apache License, Version 2.0, <LICENSE-APACHE or
// http://apache.org/licenses/LICENSE-2.0> or the MIT license <LICENSE-MIT or
// http://opensource.org/licenses/MIT>, at your option. This file may not be
// copied, modified, or distributed except according to those terms.

It's commonly asked whether license headers are required. I'm not comfortable
making an official recommendation either way, but the Apache license
recommends it in their appendix on how to use the license.
Be sure to add the relevant LICENSE-{MIT,APACHE} files. You can copy these
from the Rust repo for a plain-text
version.
And don't forget to update the license metadata in your Cargo.toml to:
license = "MIT OR Apache-2.0"

I'll be going through projects which agree to be relicensed and have approval
by the necessary contributors and doing this changes, so feel free to leave
the heavy lifting to me!
Contributor checkoff
To agree to relicensing, comment with :
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Or, if you're a contributor, you can check the box in this repo next to your
name. My scripts will pick this exact phrase up and check your checkbox, but
I'll come through and manually review this issue later as well.

[ ] @Toby-S
[ ] @gmjosack

:+1:. I don't know if my changes are significant enough to claim authorship of anyway, but:
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Wooops, somehow this fell completely off my radar. Don't know if the scripts will still pick this up but:
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.


⚠ ClamAV has degraded performance

In 7f1c09a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 59 ms

Resolved: ClamAV performance has improved in b0377f5 after 5 minutes.


Add --cmake-args option for ros-ci-for-pr

Add --cmake-args option for ros-ci-for-pr build script.
Will be useful when need to run CI with some specific cmake args or definitions.
For instance to run CI with enabled rosbag2 benchmarks --cmake-args -DBUILD_ROSBAG2_BENCHMARKS=1

I haven't tested it (and apparently I don't have merge permissions), but it looks good to me.

@emersonknapp @clalancette, Could you please merge this PR? It has been reviewed.


[Icon Request] Brand Icons

Brand Icons like,

Github
Facebook
Twitter

Looks kinda like a duplicate request of #184


upgrade nuxt 3.0.0 to 3.2.2 create error on dev server (reading 'port' of undefined)

Environment
Nuxt project info:                                                    07:37:15

Operating System: Linux
Node Version:     v18.12.1
Nuxt Version:     3.2.2
Nitro Version:    2.2.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, buildModules, css, purgecss, vite, nitro, runtimeConfig, experimental, app, sourcemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>

Reproduction
here is nuxt.config.js
import postcssRTLCSS from 'postcss-rtlcss';
import {VitePWA} from 'vite-plugin-pwa';
import app from './config/app';

export default defineNuxtConfig({
  modules: [
    '@vueuse/nuxt',
    '@pinia/nuxt',
  ],
  buildModules: [
    '@nuxtjs/eslint-module',
    'nuxt-purgecss',
  ],
  css: [
    '~/assets/styles/vendors/bootstrap/index.scss',
    '~/assets/styles/globals/index.scss',
  ],
  purgecss: {
    enabled: true,
  },
  vite: {
    server: {
      hmr: {
        protocol: 'ws',
        host: process.env.HOST,
      },
    },
    css: {
      postcss: {
        plugins: [
          postcssRTLCSS(),
        ],
      },
    },
    plugins: [
      VitePWA({
        base: '/',
        workbox: {
          navigateFallback: null,
        },
        manifest: {
          name: app.name,
          short_name: app.shortName,
          description: app.description,
          dir: app.dir,
          lang: app.lang,
          theme_color: app.themeColor,
          background_color: app.backgroundColor,
          icons: app.icons.manifest,
        },
      }),
    ],
  },
  nitro: {
    compressPublicAssets: true,
  },
  runtimeConfig: {
    mainApi: process.env.MAIN_API_SERVER,
    treksPageCache: process.env.TREKS_PAGE_CACHE,
    agenciesPageCache: process.env.AGENCIES_PAGE_CACHE,

    public: {
      mosaferanUrl: process.env.MOSAFERAN_URL,
      mainApi: process.env.MAIN_API_CLIENT,
      leafletTileUrl: process.env.LEAFLET_TILE_URL,
      gaMeasurementId: process.env.GA_MEASUREMENT_ID,
      gaDebugger: process.env.GA_DEBUGGER,
    },
  },
  experimental: {
    writeEarlyHints: false,
  },
  app: {
    buildAssetsDir: process.env.NUXT_APP_ASSETS_PATH,
    cdnURL: process.env.NUXT_APP_CDN_URL,
    pageTransition: false,
    layoutTransition: false,
  },
  sourcemap: {
    client: process.env.SOURCEMAP_CLIENT === 'true',
  },
});

here is .env
HOST=<IP_ADDRESS>
PORT=3000

MOSAFERAN_URL="http://mos.test"
MAIN_API_CLIENT="http://api.mos.test"
MAIN_API_SERVER="http://api.mos.test"

NUXT_APP_ASSETS_PATH=""
NUXT_APP_CDN_URL="http://mos.test"

LEAFLET_TILE_URL=https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png

GA_MEASUREMENT_ID=""
GA_DEBUGGER="false"

TREKS_PAGE_CACHE=10 # time in seconds
AGENCIES_PAGE_CACHE=10 # time in seconds

SOURCEMAP_CLIENT=true

here is package.json
{
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "analyze": "nuxt analyze",
    "postinstall": "nuxt prepare",
    "lint": "eslint --fix --ext .js,.ts,.vue ."
  },
  "devDependencies": {
    "@nuxtjs/eslint-config": "^11.0.0",
    "@nuxtjs/eslint-module": "^3.1.0",
    "@types/bootstrap": "^5.2.5",
    "@vueuse/core": "^9.3.1",
    "@vueuse/nuxt": "^9.3.1",
    "eslint": "^8.25.0",
    "eslint-plugin-nuxt": "^4.0.0",
    "nuxt": "^3.2.2",
    "nuxt-purgecss": "^2.0.0",
    "postcss-rtlcss": "^4.0.1",
    "sass": "^1.55.0",
    "vite-plugin-pwa": "^0.13.1",
    "vue-gtag-next": "^1.14.0"
  },
  "dependencies": {
    "@pinia/nuxt": "^0.4.3",
    "@vue-leaflet/vue-leaflet": "0.5.0",
    "@vueform/multiselect": "^2.5.6",
    "@vueform/slider": "^2.1.5",
    "bootstrap": "^5.2.2",
    "dayjs": "^1.11.5",
    "jalaliday": "^2.3.0",
    "leaflet": "1.9.1",
    "lodash": "^4.17.21",
    "mobile-detect": "^1.4.5",
    "qs": "^6.11.0",
    "resize-sensor": "^0.0.6",
    "sticky-sidebar": "^3.3.1",
    "swiper": "^8.4.4",
    "vue-toastification": "^2.0.0-rc.5"
  }
}

Describe the bug
The bug appeared after upgrading to<EMAIL_ADDRESS>from<EMAIL_ADDRESS>using npx nuxi upgrade.
dev server could not start because of the following error:
Nuxi 3.2.2
Nuxt 3.2.2 with Nitro 2.2.2

 ERROR  Cannot read properties of undefined (reading 'host')

  at Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6768:82)
  at async _main (node_modules/nuxi/dist/cli.mjs:51:20)

so I went to node_modules/nuxi/dist/chunks/dev.mjs:6768:82 and then I saw the following code:
const listener = await listen(serverHandler, {
  showURL: false,
  clipboard: args.clipboard,
  open: args.open || args.o,
  port: args.port || args.p || process.env.NUXT_PORT || config.devServer.port,
  hostname: args.host || args.h || process.env.NUXT_HOST || config.devServer.host,
  https: args.https !== false && (args.https || config.devServer.https) ? {
    cert: args["ssl-cert"] || config.devServer.https && config.devServer.https.cert || void 0,
    key: args["ssl-key"] || config.devServer.https && config.devServer.https.key || void 0
  } : false
});

I wrote console.log(args) and there was just this: { _: [] }
then I added NUXT_PORT=3000 in my .env file and another error appeared:
ERROR  Cannot read properties of undefined (reading 'host')
  at Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6769:82)
  at async _main (node_modules/nuxi/dist/cli.mjs:51:20)

then I added NUXT_HOST=<IP_ADDRESS> in my .env file and again another error appeared:
ERROR  Cannot read properties of undefined (reading 'https')
  at Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6770:70)
  at async _main (node_modules/nuxi/dist/cli.mjs:51:20)

I couldn't do anything about it.
So I wrote console.log(config.devServer) and it was undefined
Then I found out that the problem was config.devServer
I added the devServer: {} to nuxt.config.js and I solved my problem.
but this is not true solution
it's better you handle the problem in your code
Additional context
No response
Logs
No response

I can confirm this.

Thanks for the report. For now, you can likely workaround by passing devServer: {} in your Nuxt options.

I can confirm this, with an error message config.devServer is undefined.

Thanks for the report. For now, you can likely workaround by passing devServer: {} in your Nuxt options, as you have pointed out.
Is there any chance you have an older version of @nuxt/schema in your project? (Check your lockfile.)

@danielroe
I checked my yarn.lock file and here we are:
"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>  version "3.2.2"
  resolved<EMAIL_ADDRESS>  integrity sha512-T3UeLxGSNl7dQgKzmtBbPEkUiiBYgXI+KkemmpkYbQK/l+bWy2f9VQw/Rl0HkQLfRTE2fS8q8jhsOedFiEnHQQ==
  dependencies:
    "@nuxt/schema" "3.2.2"
    ...

"<EMAIL_ADDRESS>  version "3.0.0-rc.12"
  resolved<EMAIL_ADDRESS>  integrity sha512-d/6SeNVL1OPdru5aKjjUIWIwqIjbYN/VYGCrZs5gddkzJ5202DsMxyn2rs/ZyT8+oBbbVTYcCK6M+G0945mQdA==
  dependencies:
    "@nuxt/schema" "3.0.0-rc.12"
    ...

"<EMAIL_ADDRESS>  version "3.0.0-rc.12"
  resolved<EMAIL_ADDRESS>  integrity sha512-LZFy8a+5tZKtqTHvUJrlCjZXmKPSmar4S/p3SpjzgIbc4jDuWzA5r4voUODozd2/bCnYxfYyNtOgtbJSJtDUrw==
  dependencies:
    c12 "^0.2.13"
    ...

"<EMAIL_ADDRESS>  version "3.2.2"
  resolved<EMAIL_ADDRESS>  integrity sha512-o3O2OqLAMKqb/DlGpK8eJq4tH29NA4OMaohknSSXl35+Nw/qHB5eOLDz+cFxNE+MKHoMj1rRVMCfi/Y/PrCN6g==
  dependencies:
    c12 "^1.1.2"
    ...

<EMAIL_ADDRESS>  version "3.2.2"
  resolved "https://registry.yarnpkg.com/nuxt/-/nuxt-3.2.2.tgz#c9017e5b2a0a1d5004a36036a238ebf0e4cdf20f"
  integrity sha512-fxO8zjNwWBd6ORvuOgVFXksd0+eliWSNQwACsCwqNRFXsjFawONfvqtdTd/pBOlRDZMJpPUTvdflsyHPaAsfJg==
  dependencies:
    "@nuxt/kit" "3.2.2"
    "@nuxt/schema" "3.2.2"
    ...

Would you refresh your lockfile with npx nuxi upgrade --force and let me know if it resolves the issue? 🙏

Okay, I think we can confirm that the issue is that your kit (which imports schema) and nuxt versions were mismatching. We can track improving resolving the right kit version in https://github.com/nuxt/nuxt/issues/14146.

I have the same issue running Nuxt 3.4.3, and nothing seems to resolve it. I have tried:

updating @nuxt/kit using nuxi upgrade --force
explicitly installing the kit as recommended here
explicitly adding<EMAIL_ADDRESS>as a dev dependency
adding the suggested workaround, an empty-object devServer option in nuxt.config.ts

I've been removing yarn.lock and node_modules and re-installing everything after each of these steps to no avail.
It seems like I have a dependency which always restores the schema in version 3.0.0, so it is always present alongside the 3.4.3 one no matter what I do:
"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>  version "3.4.3"
  resolved<EMAIL_ADDRESS>  integrity sha512-8bv0/mRDw6THQguSz+cKG5FzDZc2XBkjcc5VZ7yET84r4aWzW9/R274cjlEagFKrw9BDaPEQhnkwpg+kZnpOUA==
  dependencies:
    defu "^6.1.2"
    hookable "^5.5.3"
    pathe "^1.1.0"
    pkg-types "^1.0.2"
    postcss-import-resolver "^2.0.0"
    std-env "^3.3.2"
    ufo "^1.1.1"
    unimport "^3.0.6"
    untyped "^1.3.2"

"@nuxt/schema@npm<EMAIL_ADDRESS>  version "3.0.0-27338323.1e98259"
  resolved<EMAIL_ADDRESS>  integrity sha512-TV8HMFEkD2cMLnsYBE0+wQcOSwElw6SW4rnDOFoDhHI61GeflpGZOfXLQRJS2FLAyMv/QVeBHdd+PWWOxDqGgA==
  dependencies:
    create-require "^1.1.1"
    defu "^5.0.0"
    jiti "^1.12.9"
    pathe "^0.2.0"
    scule "^0.2.1"
    std-env "^3.0.1"
    ufo "^0.7.9"

And the same holds for the kit.
This makes the dev server crash with an error
ERROR  Cannot start nuxt:  Cannot read properties of undefined (reading 'https')                                                                                19:24:31

  at buildClient (/home/.../node_modules/@nuxt/vite-builder/dist/shared/vite-builder.b946f6f0.mjs:285:38)
  at async bundle (/home/.../node_modules/@nuxt/vite-builder/dist/shared/vite-builder.b946f6f0.mjs:851:3)
  at async build (node_modules/nuxt/dist/index.mjs:3175:5)
  at async Promise.all (index 1)
  at async load (node_modules/nuxi/dist/chunks/dev.mjs:210:9)
  at async Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:233:5)
  at async _main (node_modules/nuxi/dist/cli.mjs:48:20)

Any suggestions on how I can force the schema to stick to only the later (3.4.3.) version?

you can add this to your package.json:
{
  "resolutions": {
    "@nuxt/schema": "3.4.3"
  }
}

I'm still getting this issue on a fresh install of Nuxt using this command:
pnpm dlx nuxi@latest init <project-name>

and I've added the resolutions to my package.json but it didn't do anything.


[stable/sealed-secrets] Create service.name value

What this PR does / why we need it:
Addresses https://github.com/helm/charts/issues/15161. This makes the default service name the one that is expected by kubeseal and adds to the NOTES.txt the required CLI option to be passed in the case you decide to change this name.
Tested locally with kubeseal in both the default and custom name cases. Also reinstalled kubeseal using the updated instructions in NOTES.txt to make sure that is copy-pastable.
Which issue this PR fixes

fixes #15161, fixes #11258

Special notes for your reviewer:
Super minor point, should this be a minor version bump rather than a patch version bump? It will change the way people interact with the chart using kubeseal (IMO for the better)
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

Not sure I should count as an approval for my own PR. Sorry to be a bother @stefanprodan any chance you wouldn't mind taking a peek?


Issue with deployment of was EAR with <IP_ADDRESS>

I am having an issue with the <IP_ADDRESS> plugin.   When I deploy an application EAR file to WebSphere and the application EAR file is not already deployed to WebSphere, the plugin deploys fine.   If the application EAR is already installed on WebSphere but NOT started, then the if a redeploy of the application EAR is run, the redeploy works fine.
Here is the problem.  If the application EAR is deployed to WAS and IS started, then the deploy fails during the 'START APPLICATION' step with an error indicating that the application is already started.
I only want to restart the application after the deployment and not the server, so I am setting 'restartAfterDeploy' to false.
We are using the <IP_ADDRESS> version of the plugin and Version 8.5.5. of WAS.
Can you review my use of the plugin and see if you see anything out of the ordinary and/or is there something else I need to do when redeploying using <IP_ADDRESS>.   This is not a problem when using <IP_ADDRESS>.
Thanks
Matt Goodnight
Attached is my configuration of the plugin, the settings.xml file and the error output from running the pom.xml.
my use of plugin.txt
settings for maven.txt
plugin deploy error.txt

The log indicates that the app is already started, and calling starting the app failed.
Looks like there're cases that the app would be started automatically after been installed to WAS. That's strange. Did it start when you see this error?

Yes, the app appears to be starting automatically with <IP_ADDRESS> but not with <IP_ADDRESS>.  but this only appears to be the case with a redeployment of an app that is already deployed.  I have watched the was console and when the app is being installed for the first time, I see that it is not running until the 'START APPLICATION' portion of the plugin starts it.   But in a redeployment, the app is running as soon as it is installed and then getting the 'already started' error when the plugin tries to start.   So, even though I get an error, when I check the WAS console, the app is running.

Maybe we should check the app's status, in the jython script, if the app is running, skip the startApplication method.
But I'm not working with WebSphere any more, I don't have any environment to debug and test the changes, so you might have to help yourself. Make a copy of the jython script and place it in the root of the project (add a  tag for the name of your script) and remove the startApplication part for this very case. Or even better if you can look up docs for wsadmin, see if you can add a status check before starting the application.


Return the search type with search results.

This involves a backwards-incompatible change to the return structure of search results: From a list of results to a list of dicts of result information.
Fixes #212.

This change is

bors r+


[ALLUXIO-2119] Refactor UnderStoreBlockInStream to use composition

https://alluxio.atlassian.net/browse/ALLUXIO-2119
Previously we extended UnderStoreBlockInStream to provide slightly different implementations for a single protected method. Now we pass a factory into UnderStoreBlockInStream which expresses the difference. This decouples UnderStoreBlockInStream from its previous children, making it much easier to test (we no longer need to use Whitebox).

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10984/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10985/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11001/
Test PASSed.


[Feature request] Assets compression / encoding

Platforms
dart
Description
Hello,
We currently compress the fetched images / videos ourselves outside photomanager. Was wondering if that feature could be added to the plugin such that it would silently (in background) compress the media with a specified compression ratio (+ optional width height) and desire result format (jpg / mp4).
Is that something you might be adding in the next future?
Why
High performant media compression / format encoding and resize is bit tricky and usually end up involving different plugins on the native side. We are adopting this solution at the moment, but it would be great if that burden might  be shifted onto PhotoManager. To us, it would also make sense, being that the plugin is envisioned as a Manager and not just a picker.

There are currently no such plans. Video transcoding and image conversion formats are very professional fields, and it is currently difficult to integrate them into this plug-in.


How to use images on Footer?

Hi!
I want use Image instead Button in Footer like here https://github.com/GeekyAnts/NativeBase/issues/360#issue-195653323
Can't find any information about how it should work

The link is broken. Can you please check?

@sankhadeeproy007 fixed!

Fixed link, not issue

Please use the issue template and fill out the details. Without the version numbers, it's hard for us to figure out.

@sankhadeeproy007
"native-base": "0.5.22",
"react": "15.4.2",
"react-native": "0.40.0",

With nativebase 0.5.x, it's not possible to add images to footer. We recommend upgrading to 2.0.x for the same.

ok, is it documented for 2.0.x?

Here's the link . just replace the Text/Icon with your image.

@sankhadeeproy007 thank you


⚠ Minecraft has degraded performance

In e6a5c09, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 980 ms

Resolved: Minecraft performance has improved in 5ef2a82.


Couple block_height and block_time together in DB and Bitcoin interfaces

In #29 we introduced the block time in addition to the block height in the confirmed_coins and confirm_coins result, as well as in the structures managing transaction (GetTxRes and DbCoin for instance).
Both fields are optional, but they should always either both be there or both not be. It would be cleaner to have a BlockInfo that itself is optional with time and height non-optional fields. So that we can avoid passing around confusing tuples, and avoid unwrapping on one field after we checked the other was present.

Part (but only part) of this was done in #63.

For instance an occurence is here https://github.com/revault/liana/blob/c98c520f06380e8d130d150ba2ce4573ed950919/src/database/mod.rs#L272-L276

Hi @darosior, I'd be happy to work on this issue.

Hello @jp1ac4, sounds good!


Remove preload token from HSTS header

Please see the documentation on how to include your domain in the preload lists:
https://hstspreload.appspot.com

Merged, thanks @jlduran. I adapted that bit of the nginx conf from another use and didn't catch removing that part as well.

:+1: no problem. And thank you for switching to nginx!


[BUG] Upload video

Upload video function not working, throws no errors but video doesn't upload...
Log from logger...
2020-03-02 17:22:51,696 - INFO - Started uploading 'video.mp4'
Analizing `video.mp4`
FOUND w:720, h:900, rotation=0, ratio=0.8
Vertical video
2020-03-02 17:23:11,453 - INFO - Video 'video.mp4' uploaded

To Reproduce

Use any .mp4 video
Create simple program that logins to instabot and uploads video
use upload_video() function

Upload photo works fine...

Still have this issue here.
Any solution?


Add ontoProc

Closes #185
This PR adds ontoProc, after much 🎢 , to the image. renv decided to also add a couple of bioc repos to the lockfile which didn't seem like too much of a problem, but I can remove them if we want!

🤖


Minor improvements to AuthenticationRestControllerIT for integration test stability

After merging #3301 , I was able to debug a seemingly random failure we were seeing in AuthenticationRestControllerIT.  It appears to be caused by the fact that several test methods use the same eperson account for testing, and not all methods which login also have a logout at the end.  This seems to have resulted in odd failures if methods ran in a specific order, as the EPerson might have been logged in earlier than expected (if the prior method didn't perform a logout).
In any case, this PR is a simple change to ensure every test method which logs in also logs out at the end.  This ensures that regardless of the order, they should all start with an unauthenticated user.
Making this change required very minor refactoring of the how we were creating a short-lived token, so that we could ensure we could logout after those tests were complete.
This PR should be easy to review as it only modifies ITs.  I'll also force it to rebuild several times in GitHub CI, just to see if I can reproduce the random failures we were previously seeing.

I've rerun the GitHub CI five times now for this PR, and have yet to re-encounter the random-ish IT failures again.  So, it seems like this may have fixed the random failures that occasionally pop up in AuthenticationRestControllerIT
@benbosman : Would you or someone on your team be willing to give this a quick review?  It should be very straightforward as it's all IT changes...nothing new to test, just a code review is necessary.  Thanks!

Hi @tdonohue from our point of view code is fine. The only observation is that if, from a point of view, code performing logout might be extracted in a method, from another point of view, having it explicit in each test improves test readability, thus I think it is ok as is.

Thanks @corrad82-4s !  In that case, merging this with one approval as it only involves ITs.


Is there a way to get full width on all elements?

Is there a way to specify a full width for the picker and slider elements, even if I set it with css the clicks don't register at the correct coordinates

Thanks for using the library!
Do you have a REPL to show what you exactly did? I haven't considered a full width case until now so it's most probably not handled correctly.

@Ennoriel here is a repl https://svelte.dev/repl/e296a6b48bfa430689293f59c8ce37cc?version=4.1.1 as you can see I am trying to get everything to be full width, but the cursor positions are not calculated correctly, is there a different way of doing this or is it something that is not implemented?

The issue is only on the main color picker not on the other sliders

Thanks for the REPL. It's clearer!
Try to apply the css variable --picker-width to you wrapper and let me know if that solves your issue:
.wrapper{
  max-width:500px;
  background:gray;
  --picker-width: 100%;
}


Implement lifecycle hook – Subscribe to insert/update with relationships

Hello,
For my use-case, I want to be able to subscribe to any changes that happens to a model (created/deleted/updated instances). It works fine with store.subscribe vuex API, but vuex-orm does not fire relationship mutations when inserted from their parent relationships for instance (which is not an issue by the way).
class User extends Model {
  static fields () {
    return {
      id: this.attr(null),
      bookCurrentlyReading: this.belongsTo(Book, 'currentBookId')
    }
  }
}

class Book extends Model {
  static fields () {
    return {
      id: this.attr(null),
    }
  }
}

You see, if I insert this data
dispatch('entities/user/insert', {
  id: 1,
  bookCurrentlyReading: {
    id: 12,
    title: 'a Book'
  }
})

I want to be able to subscribe to inserting/updating actions that happen to book model only.
No mutation is fired for book model (eg: 'entities/insert'  with entity === 'book' )
So now, I'm forced to subscribe to user model to retrieve data when a book change.
store.subscribe(({ type, payload }, state) => {
  if (type === 'entities/insert' || type === 'entities/update') {
    const { entity } = payload
    if (entity === 'book') {
       //dont gets it
    } else if (entity === 'user') {
       //gets it
    }
  }
})

Would it be valuable to have an API for this. Is there any workaround you can suggest ?
Thanks

Thanks for the feedback. Yeah this can be tough to catch via store.subscribe method. Maybe it depends on what you want to do when subscribing to the book model change, but I think it would be good for Vuex ORM to implement such lifecycle hook that users can subscribe to.
To do so, I'm thinking to add method that you can define on modules for example something like onInsert method.
Could you elaborate bit more on what you are trying to do after entity === 'book'? Maybe it depends on that use case on how or where to emit the lifecycle hook.

Yes, I feel like adding lifecycle hooks to models definition could be a great feature. My need is mostly about tracking changes on models to fire some persisting cache/save some data in local database

OK, thanks for the confirmation. I've been thinking about lifecycle hooks but not sure where to define it just yet if it should be in model or module (or maybe both). I'll think about it and try to come up with nice API 😃

I was thinking about the implementation of the lifecycle hook event, and here I would like to share my thoughts. It might be harder than I thought.
Let's say we add beforeCreate and afterCreate hook. To define those hook, I think it's nice to be able to define both in modules (in action), and models.
// Define hooks in the module action.
const actions = {
  // the `user` is the user object that has been created.
  afterCreate (context, user) {
    // ...
  }
}

// Define hooks in the model.
class User extends Model {
  // the `user` is the user object that has been created.
  beforeCreate (user) {
    // ...
  }
}

Now, it is easy to imagine that a user would like to dispatch another action in this beforeCreate method. For example, maybe user would like to increment a count field of a user when a new post is being created for that user.
With the current implementation of Vuex ORM, all of the operations happen inside mutation handler. This is because we're just calling Query.create method to dispatch all complicated logic inside Query class. Which means, by the time we know what records are being created, it's inside mutations handler.
The problem is we shouldn't be calling dispatch inside mutations handler since it could be async. So, maybe we should change how data is being saved to the state via Query class but haven't come up with any idea yet.
Maybe we should separate data normalization (preparation) phase and committing the normalized data phase. And call hooks inside the action. Or maybe it's hacky but pass action context to the Query class and let Query class commit each entity mutation...?
// Something like below? Omitting many intermediate processes but I think it
// shows the idea.

create (context, { data }) {
  Query.create(rootState, state.$name, data, context)
}

class Query {
  static create (state, entity, data, context) {
    const normalizedData = this.normalize(data)

    Object.keys(normalizedData).forEach((entity) => {
      const record = normalizedData[entity]

      this.dispatchHook('beforeCreate', record)

      context.commit(`${state.$name}/${entity}/create`, { data: normalizedData[entity] })

      this.dispatchHook('afterCreate', record)
    })
  }
}

I haven't come to any conclusion but just wanted to open my mind. I'll come back again if I come up with anything solid.

I've started this at #133. It works pretty well right now ❤

Lifecycle Hook is now supported by Vuex ORM 0.24.0! 🎉
https://github.com/vuex-orm/vuex-orm/releases/tag/v0.24.0
I would like to make it able to define lifecycle hook at models too, but I'll create new issue for this.

Sorry to bring this one back to life, but per the code above...
// Something like below? Omitting many intermediate processes but I think it
// shows the idea.

create (context, { data }) {
  Query.create(rootState, state.$name, data, context)
}

class Query {
  static create (state, entity, data, context) {
    const normalizedData = this.normalize(data)

    Object.keys(normalizedData).forEach((entity) => {
      const record = normalizedData[entity]

      this.dispatchHook('beforeCreate', record)

      context.commit(`${state.$name}/${entity}/create`, { data: normalizedData[entity] })

      this.dispatchHook('afterCreate', record)
    })
  }
}

the hook only passes in the record -- which is normalized. sometimes it is also very handy to have the payload/data as well.. Can we pass this into the hooks as well?

@rkingon Thank you for the feedback! Oh yeah that's so true. Could you create a issue for that? So that it gets a bit more attention 🤝


Have terminal listen to fine grained events

Fixes #36502

@sandy081 let me know if this looks right 😃

LGTM


Restrain dragging bounds to screen rect, add status bar bg and fix readme

some minor changes I did for myself and thought someone might profit from it. Thanks for publishing Shari!

Thanks!

Oh, miss. Please don' t delete README.md


[Bug]:azure_openai Does not support gpt-35-turbo-0125

Bug Description
within these versions:
llama-index==0.10.18
llama-index-llms-openai==0.1.9
llama-index-llms-azure-openai==0.1.5
llama-index-embeddings-openai==0.1.6
llama-index-embeddings-azure-openai==0.1.6

and also previous ones seems that gpt-35-turbo-0125 model coming from Azure OpenAI is not supported.
This seems to be due to AZURE_TURBO_MODELS inside llama_index.llms.openai.utils that does not contain any reference to gpt-35-turbo-0125
AZURE_TURBO_MODELS: Dict[str, int] = {
    "gpt-35-turbo-16k": 16384,
    "gpt-35-turbo": 4096,
    # 1106 model (JSON mode)
    "gpt-35-turbo-1106": 16384,
    # 0613 models (function calling):
    "gpt-35-turbo-0613": 4096,
    "gpt-35-turbo-16k-0613": 16384,
}

Version
0.10.18
Steps to Reproduce
Try to initiate and use the AzureOpenAI (from llama_index.llms.azure_openai import AzureOpenAI) using the gpt-35-turbo-0125 model, this error is throwned:
Unknown model 'gpt-35-turbo-0125'. Please provide a valid OpenAI model name in: gpt-4, gpt-4-32k, gpt-4-1106-preview, gpt-4-0125-preview, gpt-4-turbo-preview, gpt-4-vision-preview, gpt-4-0613, gpt-4-32k-0613, gpt-4-0314, gpt-4-32k-0314, gpt-3.5-turbo, gpt-3.5-turbo-16k, gpt-3.5-turbo-0125, gpt-3.5-turbo-1106, gpt-3.5-turbo-0613, gpt-3.5-turbo-16k-0613, gpt-3.5-turbo-0301, text-davinci-003, text-davinci-002, gpt-3.5-turbo-instruct, text-ada-001, text-babbage-001, text-curie-001, ada, babbage, curie, davinci, gpt-35-turbo-16k, gpt-35-turbo, gpt-35-turbo-1106, gpt-35-turbo-0613, gpt-35-turbo-16k-0613
Relevant Logs/Tracbacks
The error log is coming from the ValueError inside the function openai_modelname_to_contextsize inside llama_index.llms.openai.utils

Unknown model 'gpt-35-turbo-0125'. Please provide a valid OpenAI model name in: gpt-4, gpt-4-32k, gpt-4-1106-preview, gpt-4-0125-preview, gpt-4-turbo-preview, gpt-4-vision-preview, gpt-4-0613, gpt-4-32k-0613, gpt-4-0314, gpt-4-32k-0314, gpt-3.5-turbo, gpt-3.5-turbo-16k, gpt-3.5-turbo-0125, gpt-3.5-turbo-1106, gpt-3.5-turbo-0613, gpt-3.5-turbo-16k-0613, gpt-3.5-turbo-0301, text-davinci-003, text-davinci-002, gpt-3.5-turbo-instruct, text-ada-001, text-babbage-001, text-curie-001, ada, babbage, curie, davinci, gpt-35-turbo-16k, gpt-35-turbo, gpt-35-turbo-1106, gpt-35-turbo-0613, gpt-35-turbo-16k-0613

@logan-markewich as I reported it's confirmed from the response too the AZURE_TURBO_MODELS dictionary in llama_index.llms.openai.utils is missing the gpt-35-turbo-0125 model. Is this an integration in plan to be added or not? The model has been available in some Azure regions since February.

@matteosdocsity it just needs to be added to that dict, not a crazy change. I'll get to it at some point. You were the first to notice it wasn't there

@logan-markewich I'just created the pull request

merged + published


[BUG] unable to join discord

unable to join discord server

i've tried with 2 accounts but both having same issue
new account as well as old account but did not worked
maybe u can add me ?
user id:<PHONE_NUMBER>17869864
username: asonacademy

i've tried with 2 accounts but both having same issue new account as well as old account but did not worked
maybe u can add me ? user id:<PHONE_NUMBER>17869864 username: asonacademy

Sent you a friend Request.


parentage problem for "conversion of ds siRNA to ss siRNA"

This term has parentage to some "response to " terms that it shouldn't have.
I think this is due to  the parentage of "dsRNA fragmentation" and hence "cellular response to ds RNA"
"conversion of ds siRNA to ss siRNA"
can be used to  describe RNAi type processes which are regulating  gene expression, rather than the processing of exogenous dsRNA (which seems to be what this term might be appropriate for?)
The term  "conversion of ds siRNA to ss siRNA"   ends up with "response to organic cyclic compound" and "response to nitrogen" but it isn't any of these things?

see

I find the term name and definition a bit vague as well. It's not clear what the "conversion" involves.
Current: "The process in which double-stranded small interfering RNA (ds siRNA) molecules are converted to single-stranded small interfering RNA (ss siRNA). "
As the process actually involves cleavage, shouldn't the definition be based around the parent definition (dsRNA fragmentation)?
Proposed: "The process in which double-stranded small interfering RNA (ds siRNA) molecules are cleaved by an RNaseIII-family enzyme to produce single-stranded small interfering RNA (ss siRNA)."
And the term name could be "Cleavage of ds siRNA to ss siRNA"? If appropriate, we would also need to update the other terms that include conversion of ds siRNA to ss siRNA.

I think there are a lot of unnecessary terms!
A lot of terms look like activities?
"conversion of ds siRNA to ss siRNA" involved_in .....
I don't think "cleavage" should be described as "fragmentation"? fragmentation implies "uncontrolled breakage". It should be "processing" (which is also present). The "fragmentation" parentage seems superfluous?

Has always been a bit of a mess under gene silencing.....

Yes, that's true. Fragmentation is the wrong word, all of the child terms involve cleavage, and dsRNA cleavage is a function. All of the child terms of dsRNA fragmentation should be described as "production of small RNA"
Would this work?
"dsRNA fragmentation" change to "production of small RNA"
--> production of ss siRNA (formerly "conversion of ds siRNA to ss siRNA")
--> production of small RNA involved in gene silencing by RNA
--> production of scnRNA
This is obviously not complete, just deals with the existing direct terms under the fragmentation term, but these are hardly used in comparison with the deeper terms under gene silencing.

We haven't even reached gene silencing yet!

I can't even annotate our gene silencing by RNA silencing papers I'm so confused by this part of the ontology (pombe use the RNAi machinery but are not RNAi in the GO sense, although I now see these terms are under RNAi, which cause TPVs).
This might be a miniproject.....

re

As the process actually involves cleavage ...

and

And the term name could be "Cleavage of ds siRNA to ss siRNA"?

If the RNA is changing from double- to single-stranded, then the conversion process must include unwinding, at least in addition to any nuclease activity, perhaps instead of. I don't know this area well, but from a quick look at the paper cited for the def (PMID:17310250) and a couple of reviews, it's clear that a large dsRNA molecule is cleaved into smaller, but still double-stranded, RNAs, before the small ds RNAs are unwound. I can't easily tell whether the RNAs undergo any further endo- or exonucleolytic cleavage upon being unwound.
I'm therefore worried that renaming GO:0033168 to "cleavage ..." would obscure the more important part of the ds-to-ss conversion process. "dnRNA fragmentation" seems like a better candidate to change to a "cleavage" term.
For the same reason, the link GO:0036404 ! conversion of ds siRNA to ss siRNA part_of GO:0031050 dsRNA fragmentation looks a little odd, and I won't argue to keep it.

Would this work?
"dsRNA fragmentation" change to "production of small RNA"
--> production of ss siRNA (formerly "conversion of ds siRNA to ss siRNA")
--> production of small RNA involved in gene silencing by RNA
--> production of scnRNA

I don't know enough to have biology-based reasons to oppose renaming various terms to "production", but GO has historically used "production" a bit differently, as exemplified by the "cytokine production" (GO:0001816) branch. My limited understanding is that it follows a usage common among immunologists.
The suggestions also seem somehow less specific than the various current names - "conversion of ds siRNA to ss siRNA" isn't pretty but it does say what happens as a result of the process, albeit not how. (I'm aware that I'm ignoring the question of which of the terms in this branch really represent multi-activity processes, but I really really don't know enough to comment on that!)

Regarding production, there are already terms such as "production of small RNA involved in gene silencing by RNA" and "production of miRNAs involved in gene silencing by miRNA", which are under the dsRNA fragmentation term, so I suggested a name to be consistent with this.
You can ignore my first comments on cleavage as my second comment suggests the alternative "production" name instead of cleavage.

Yeah probably need to identify the steps involved in the "conversion". I had a quick look earlier and I couldn't work it out immediately based on out annotations.
Can have a closer look after the meeting.

I'm wondering if the original dsRNA terms were created to deal with response to dsRNA viruses and not really related to RNAi at all.

Yes I was thinking that.
Although the RNAi machinery does deal with these in some species. but not all siRNA formation is involved in this process, its only one pathway. It's a big mix up....

So I think the key to the issue in this ticket is the links to to dsRNA fragmentation. I suspect this term was meant to be a response to dsRNA but not to represent anything to to with siRNA. However, it looks like the two might in fact be related. PMID:17698400

So there are other terms related to silencing viral genes under GO:0009616 virus induced gene silencing (which is under multi-organism process).
If we are keeping the dsRNA fragmentation term, we could put a comment on that it should only be used for describing processing of endogenous dsRNA, even though the same machinery is used for processing foreign dsRNA.

Hello,
What's the action here ?
Thanks, Pascale

Looks like 'dsRNA fragmentation' shouldn't have parent 'part of' some 'cellular response to dsRNA'
Can I just remove that ?
Pascale

Yes that would help.
At the same time maybe you could change the name of
'cellular response to dsRNA' to 'cellular response to exogenous dsRNA'
this would alleviate the reported issue.
One day, the entire branch of chromatin remodelling and RNAi needs a thorough and comprehensive review. Not yet though. .....

Changed a number of labels to improve consistency:
id: GO:0031051 scnRNA production
NEW name: scnRNA processing
id: GO:0031050  dsRNA fragmentation
NEW name: dsRNA processing (+ removed parent  'cellular response to dsRNA')
GO:0031051 scnRNA production
NEW name: scnRNA processing
GO:0031050 dsRNA fragmentation
NEW name: dsRNA processing
Pascale


Manage prefix for owned entities

Resolves #78
Follows up on https://github.com/opendatahub-io/model-registry/pull/68#discussion_r1366550044
Also aligns to name mapping as showcased in #77
Description
Address acceptance criterias in #78
How Has This Been Tested?
go test ./internal/...
go test ./test/...

Merge criteria:

[x] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

two approvals, no vetos, proceeding to merge.


Preporocessor on - lag sound (iPhone 3g)

When preprocesor function is on, voices is lagged:
Film test:
http://www.screentoaster.com/watch/stVEpcS0BIR1FaQV1VU1JbU1Vd
When preprocessor is off all still good (when one user transmite)
15 sec+ i try reproduce crash (4+ users transmite) but at these time all work good...

Closing this. The latest builds have a configurable preprocessor option.


Create LICENSE

Using MIT as in other CHAOSS operational repositories (such as the working groups and website).

Thanks! The Project Charter requires us to use MIT or GPL but we use GPL only for software and MIT for everything else.


version numbers in readme are out of date?

this came up at https://users.scala-lang.org/t/tracing-libraries-for-scala-2-13/6499

They were indeed, I just pushed a fix, thanks 😃 !


Investigate git ci build issue.

Investigating GIT ci build issue

@obabec running the build with env var CI=true I saw the same issue as GitHub CI.  This change resolves the issue locally by flipping the env var for the react build only.  Hoping this does the trick on CI too.


"Zoom in to start collecting data" toast is shown when map is already zoomed in

Describe the bug
A small issue, but the "Zoom in to start collecting data" toast seems to show up even when the map is already zoomed in. Maybe we need to add a small delay before checking the map zoom?
To Reproduce
Steps to reproduce the behavior:

Zoom in enough to be able to start collecting points.
Switch to a different menu item (e.g. sync menu).
Switch back to map view, see that the "Zoom in" message is triggered.

Expected behavior
"Zoom in" message should not be shown when able to collect points.
Actual behavior
"Zoom in" message is shown.
Screenshots

Sorry, I also opened this as a duplicate of #2286. Closing this one!


Adding a type to an optional parameter marked by a question token puts the question token in the wrong spot

Hey @dsherret. Looks like I found another interesting one. Trying to add a type to an optional parameter marked by a question token seems to put the '?' token in the wrong place in the output code. Check out this reproduction:
import Project, { MethodDeclaration, SyntaxKind } from 'ts-simple-ast';

const project = new Project();
const sourceFile = project.createSourceFile( 'my-file.ts', `
	class MyClass {
		someMethod( param1? ) {}
	}
` );

const method = sourceFile
	.getDescendantsOfKind( SyntaxKind.MethodDeclaration )[ 0 ] as MethodDeclaration;

const param1 = method.getParameters()[ 0 ];
param1.setType( 'any' );

console.log( 'Transformed:' );
console.log( sourceFile.getFullText() );

Basically the original source code:
class MyClass {
    someMethod( param1? ) {}
}

Gets changed into:
class MyClass {
    someMethod( param1: any? ) {}
}

Where the correct output should be:
class MyClass {
    someMethod( param1?: any ) {}
}

Best,
Greg

As always, thanks for the excellent report @gregjacobs! Luckily for you I happened to be programming tonight so this is fixed now in 12.7.1.

@dsherret You're the man! Thanks so much for the fix, and so quickly! Much appreciated!
Best,
Greg


Locking the click version fixes the 1.0.1 release of meta-pelion-edge

Recent update to click python module broke the mbed-fcc. Locked the click
version to 7.0. This fixes the bug - https://jira.arm.com/browse/PELEDGE19-2493

@ygoyal18 Checking, was the problem with click an issue with v7.1 or 7.1.1?
Reference: https://pypi.org/project/click/#history

@cmonr One of those I guess, by default it was pulling the latest and when I moved to 7.0 it build fine.


Improve error message and bridge UI when sequence in shipyard has no tasks

Is your feature request related to a problem? Please describe.
We ran into a problem and spent several hours of troubleshooting on why an evaluation sequence didnt execute any tasks. Turned out that the shipyard file didnt have any tasks specified for that evaluation sequence.
kind: shipyard
spec:
  stages:
  - name: testing
    sequences:
    - name: evaluation

The reason we ended up in the situation of not having any tasks was because of the wrong assumption that Keptn will default to a sequence with the evaluation task in case the task list is empty. This assumption was wrong as Keptn only defaults to an evaluation sequence if the evaluation sequence itself is not defined at all.
The shipyard controller immediately sends an evaluation.finished with a result of pass. But - because there are no tasks executed in the sequence the keptn bridge shows the sequence as still executing. This is why we ended up troubleshooting a long time as we thought the sequence is still doing something but nothing ever happened

Describe the solution you'd like
I suggest two things
a) the SEQUENCENAME.triggered event sent by the shipyard-controller should not use pass as a result but fail with the error message that the sequence has no task
b) the bridge needs to not show this sequence is still processing

In the docs, the explanation of the behavior is mentioned here - at "Why I do not need to specify a task sequence for quality gates in this stage?": https://keptn.sh/docs/0.12.x/quality_gates/get_started/#definition-of-project-stage-and-service
We should highlight it more prominently to avoid this issue again.

This is not a bug in the Bridge, since the GET /sequence endpoint return state started for this sequence, which should be finished in this case.

Hi,
may I please ask you for the exact steps to reproduce the problem?
I was unable to reproduce it, my steps were:

Creating a project keptn create project test --shipyard=./short-shipyard.yaml with shipyard
`apiVersion: "spec.keptn.sh/0.2.3"
kind: "Shipyard"
spec:
stages:

name: testing
sequences:

name: evaluation`

creating service keptn create service helloservice --project=test
triggering evaluation keptn trigger evaluation --project=test --stage=testing --service=helloservice --start=2022-03-26T10:05:53.931Z --end=2022-03-26T10:10:53.931Z

Result:
/home/odubaj/Pictures/Screenshot from 2022-02-28 16-18-48.png
Thank you in advance!

From my investigation this problem was fixed with this commit
https://github.com/keptn/keptn/commit/bdcd95e5c5857a7c5ef0abff49524cafdf2a8b86
and is fixed in version 0.13.0, see release notes
https://github.com/keptn/keptn/releases/tag/0.13.0
it's not fixed in 0.12.2
https://github.com/keptn/keptn/releases/tag/0.12.2

Closing this issue, as we do not plan to backport the fix to version 0.12.2


[Bugfix][CI/Build] Test prompt adapters in openai entrypoint tests

Adds OpenAI compatible server entrypoint tests for prompt adapters. Prompt adapters are a new feature added by https://github.com/vllm-project/vllm/pull/4645/.
Also fixed some tests that didn't have model_name parameterized.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

/ready

@DarkLight1337 all tests passed except docs build, which I think will be fixed by https://github.com/vllm-project/vllm/pull/6454. Can I ask this be merged now with the one failing docs build test?


Add Sloth with common plugins deploy example

Codecov Report

Merging #120 (f89a98c) into main (97e4fb0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #120   +/-   ##
=======================================
  Coverage   79.04%   79.04%
=======================================
  Files          16       16
  Lines         921      921
=======================================
  Hits          728      728
  Misses        139      139
  Partials       54       54

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 97e4fb0...f89a98c. Read the comment docs.


New UDS Component: Table/Grid

We need a component to help us with this issue in electrofishing query. We used dgrid and dynamic fetching. I'm not sure if that was needed or if we want to build that into the new component.

The client from electrofishing requested the header sorting functionality. It would be great to include this with the first release of this component.

I don't see a PR for this component...

I don't see a PR for this component...

Yep, you're right. The linked commit from above is now in a draft pr.


Implement auto-discovery function

Examples here: https://github.com/ioBroker/ioBroker.discovery/tree/master/lib/adapters

Done in https://github.com/ioBroker/ioBroker.discovery/pull/26


FF extension doesn't work: An unexpected property was found in the WebExtension manifest.

I followed the compilation steps and when loading the zip-file FF says, the extension seems to be damaged.
Reading manifest: Warning processing version_name: An unexpected property was found in the WebExtension manifest.

after removing the line
"version_name": "1.1.1-firefox",
in shells/firefox/manifest.json it still doesn't work. The error is gone though.


Exception: Model type not yet supported by TreeExplainer: <class 'sklearn.pipeline.Pipeline'>

I'm getting the following error when i executed the TreeExplainer, could you help on this.
clf = Pipeline(steps=[('preprocessor', transformations),
('classifier', RandomForestRegressor(max_depth=6, random_state=0))])
model = clf.fit(X_train, Y_train)
explainer = shap.TreeExplainer(model)
shap_values = explainer.shap_values(X_train)
Exception: Model type not yet supported by TreeExplainer: <class 'sklearn.pipeline.Pipeline'>

Your model is actually a pipeline (usually a sequence of preprocessing operations in sklearn followed by the actual classifier).
It seems you'll have to do the preprocessing by hand and only give the classifier itself to the explainer.

@erickrf is right. If you need to explain a whole pipeline I recommend using a model agnostic approach, which under the new API can be explainer = shap.Explainer(f, X); explainer(X)

Thanks @erickrf & @slundberg , I'm getting the following error
Exception                                 Traceback (most recent call last)
 in
----> 1 explainer = shap.Explainer(model, X_train)
2 shap_values = explainer(X_train)
~\Anaconda3\lib\site-packages\shap\explainers_explainer.py in init(self, model, masker, link, algorithm, output_names)
123                 # if we get here then we don't know how to handle what was given to us
124                 else:
--> 125                     raise Exception("The passed model is not callable and is not any known model type: " + str(model))
126
127             # build the right subclass
Exception: The passed model is not callable and is not any known model type: Pipeline(memory=None,
steps=[('preprocessor',
ColumnTransformer(n_jobs=None, remainder='drop',
sparse_threshold=0.3,
transformer_weights=None,
transformers=[('num',
Pipeline(memory=None,
steps=[('imputer',
SimpleImputer(add_indicator=False,
copy=True,
fill_value=None,
missing_values=nan,
strategy='median',
verbose=0)),
('scaler',
StandardScaler(copy=True,
with_mean...
RandomForestRegressor(bootstrap=True, ccp_alpha=0.0,
criterion='mse', max_depth=6,
max_features='auto', max_leaf_nodes=None,
max_samples=None,
min_impurity_decrease=0.0,
min_impurity_split=None,
min_samples_leaf=1, min_samples_split=2,
min_weight_fraction_leaf=0.0,
n_estimators=100, n_jobs=None,
oob_score=False, random_state=0,
verbose=0, warm_start=False))],
verbose=False)

I think with model agnostic explainer you need to pass a function responsible for giving predictions not the model itself. Try:
explainer = shap.Explainer(model.predict, X_train)
At least it worked for me with KernelExplainer in ver 0.35

Thanks @Lamiane  I'm getting error in shap_values = explainer(X_train)

I don't know what your data is and how your code exactly works but I assume X_train contains sth that is not a number. A string maybe?
It seems that the problem is raised by the isfinite function from numpy. You can try to run it on each row of X_train to see which row causes the error.

I tried the workaround using
explainer = shap.Explainer(model.predict, X_train)
but I am receiving warnings that say:
Compilation is falling back to object mode WITH looplifting enabled because Function "_build_fixed_multi_output" failed type inference due to: non-precise type pyobject
and
Compilation is falling back to object mode WITHOUT looplifting enabled because Function "_build_fixed_multi_output" failed type inference due to: Cannot determine Numba type of <class 'numba.core.dispatcher.LiftedLoop'>
I'm not sure what these mean.

@erickrf is right. If you need to explain a whole pipeline I recommend using a model agnostic approach, which under the new API can be explainer = shap.Explainer(f, X); explainer(X)

@slundberg Could you please provide a brief code example of how shap can be made to work with a sklearn Pipeline object ? I reviewed the shap documentation, but may have missed it.

I solved this problem  like this
`explainer = shap.TreeExplainer(pipe.named_steps["model"])
shap_values = explainer.shap_values(pipe[:-1].transform(X_tr))
visualize the first prediction's explanation (use matplotlib=True to avoid Javascript)
shap.force_plot(explainer.expected_value, shap_values[0,:], X.iloc[0,:])`

@cmougan isn;t that solution ignoring the transformation steps though?

i solved this problem like this
explainer = shap.Explainer(vr.predict, test)
shap_values = explainer(test)


Revert "Draft: Sync spack package"

Reverts lanl/ports-of-call#27

Oops sorry didn't notice it was a draft. This PR unmergers if needed. Let me know how you want to proceed @rbberger

@Yurlungur no this is fine, just wanted to wait until the spiner CI clears. We can close this one.

Got it. Thanks, @rbberger


No solution yet


NuGetPack overwrites developmentDependency and requireLicenseAcceptance from nuspec.

What You Are Seeing?
Builtin NuGetPack always replaces developmentDependency and requireLicenseAcceptance values when transforming a nuspec file.
Only developmentDependency and requireLicenseAcceptance operate in this manner.
What is Expected?
NuGetPack would not replace any setting within the nuspec, unless that setting has been specifically configured within the NuGetPackSettings instance.
What version of Cake are you using?
0.25.0+Branch.main.Sha.05b4d3f596defbdf5baecdb3712c9bc17f849b55
Are you running on a 32 or 64 bit system?
64
What environment are you running on?  Windows? Linux? Mac?
Windows
Are you running on a CI Server?  If so, which one?
No
How Did You Get This To Happen? (Steps to Reproduce)
Occurs for any call to NuGetPack when provided with a nuspec file with the developmentDependency setting configured as true.

Any progress on this? I am getting this and luckily we have a step to verify that this was set.


Multiple CI improvements

pin CI package versions
tell renovate about pinned versions
quote shell variables
build released package from sdist

Codecov Report

Merging #600 (30b9508) into main (57b0289) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #600   +/-   ##
=======================================
  Coverage   97.50%   97.50%
=======================================
  Files           6        6
  Lines         400      400
  Branches       80       80
=======================================
  Hits          390      390
  Misses          8        8
  Partials        2        2


Define a Simple Data Model and OData Service with CDS

Tutorial URL: https://developers.sap.com/tutorials/odata-05-data-model-service.html
Please specify the step you are referring to
Hello, I got the error below when trying to build the db module:
"15:26:16 (HDB) Build command failed : failed to prepare payload on pre build stage: service hdispacedeploy3c6d1298-c699-440a-8a90-316535ba9b7b is not valid: failed install hdispacedeploy3c6d1298-c699-440a-8a90-316535ba9b7b application: Failed to execute install command: Failed to execute install command: failed to set delete service : Row not found
15:26:16 (HDB) Build of /Products/db failed due to The "task for hdb build" process finished with code 1."
Some other people seem to be having the same issue, as mentioned on this post:
https://answers.sap.com/questions/12862407/hana-cloud-foundry-trial-hdispacedeploy-creation-f.html#

Hi  @andrecontax. Did you solve it ? I'm getting the same error.
Please, if you did, tell me how solved.
Thanks

Hi  @andrecontax. Did you solve it ? I'm getting the same error.
Please, if you did, tell me how solved.
Thanks


BC 6.2.6

Can you add again BuildCraft handlers  in the newer versions of NEI -Intergration for those who didn't update to BC 6.3 ?

I assume this is related to Logistics Pipes (correct me if I'm wrong). That mod has updated by now though. Anything else keeping you from updating BC?

LP has been updated to buildcraft 6.3

no no .is ok now.thanks anyways


update install docs to match #1565 (don't prompt to install on use)

https://github.com/project-serum/anchor/pull/1565

blocked until https://github.com/project-serum/anchor/pull/1565 is included in a published anchor release

Thanks!


Handle r11s-driver requests and errors in custom RestWrapper

This is a redo of #5200 with request error handling happening as close to the HTTP request as possible

/AzurePipelines run Build - client packages


In the new update there is no modded lobbies because they moved everything around they moved gamemodes to exit of stump

they prob did that to stop modding? or something like that

they are prob working on the fix but for now do not  install utilla fix just wait for the devs to do their thing and it will be fixed soon

i found a fix in wrysers modding cave thing and it works

banned for 8 weeks cuz of an old version of utilla


Bug was: the docker registry client didn't include the hostname

Result was that we tried to pull OT images from dockerhub.
This fixes that.

This is still failing, opentable/two no longer deployed after resolve ... I'll take a look this morning and see if I can figure out what's wrong.

On the trail of the integration fail - got it working here, and the result will be a lot more solid. In the meantime it's not going to work so...


QuantizedConv2D (inference) on iOS

Hello,
I had some question and it would be nice to get quick help/reply.
I know, that accelerate framework (cblass_sgemm) is used for Conv operation (gemm_functors.h) incase of iOS platform. However, that is for float datatype.

What happens incase of quantized op of inception5h graph. For example, which library is used for QuantizedConv2D operation incase of iOS mobile platform?
Is Accelerate framework is used also for QuantizedConv2D operation? If so, then is the comptuation actually happens for float datatype and not 8bit mult and 32bit accumulation?

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


ReferenceError: Lockr is not defined

Basic usage is causing a reference error. Thoughts?
  Lockr.prefix = 'lockr';
  Lockr.set('website', 'website.com');
  Lockr.set('categories', 8);
  Lockr.set('users', [{ name: 'John Doe', age: 18 }, { name: 'Jane Doe', age: 19 }]);

Hello Spencer,
Can you please send me an error stacktrace showcasing the problem?
Thank you!
On Jun 10, 2017 1:10 AM, "Spencer Thayer"<EMAIL_ADDRESS>wrote:

Basic usage is causing a reference error. Thoughs?
Lockr.prefix = 'lockr';
Lockr.set('website', 'website.com');
Lockr.set('categories', 8);
Lockr.set('users', [{ name: 'John Doe', age: 18 }, { name: 'Jane Doe', age: 19 }]);
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tsironis/lockr/issues/51, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvwcNA3K6emCCiRoGpJg8QdfsGcUvJfks5sCcK9gaJpZM4N14h9
.

I am getting same error. I am trying to use this in my reactjs project. I tried importing Lockr, but it seems its not exported module.

I'm sorry I never sent the error. I decided not to use Lockr in my app. Thanks!


Added documentation for Compass

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

[ ] Bug fix
[ ] Feature implementation
[x] Doc updates

Related Issue

#60

What changes have you introduced?
Hi, I have added documentation for Compass in the form of an experiment.

Does this PR introduce a breaking change?

Preview / Steps to verify your work:
Preview link

Sir, I'm unable to create a preview link.

@cweitat Please review

you can create github pages from this repo and share your github pages link

you can create github pages from this repo and share your github pages link

I tried building GitHub pages with the master branch but it isn’t working.

@cweitat Could you please assist me with the former.

@cweitat Please review...Changes are ✅.

Changes have been made.
Please review @cweitat @hpdang

@NishithP2004 @mariobehling The second experiment about whether the compass uses magnets or not was added by me to the PSLab docs repository as the name suggests hence shouldnt I be the one to be able to merge it? The doc is names Aryanguls_experiment.md.


change expected response from ACCEPTED to OK

RTR is checking for a 202 Accepted but WorkerResource.doShutdown() sends back a 200 OK:
https://github.com/druid-io/druid/blob/master/indexing-service/src/main/java/io/druid/indexing/worker/http/WorkerResource.java#L169

Is there any unit test for this behavior?

@drcrallen no unit test, the logic is the same regardless of the response code except for a log message

👍  LGTM


Official, gradual path to RN packages not publishing untranspiled code

The current practice in the RN community for package authors is to publish untranspiled code, to npmignore babelrc, and for the RNP to transpile node_modules.
While this may work great for the RN community, this defies many best practices in the wider node/npm/JS community:

package.json's "main" only points to ES5 commonJS
npm explore foo && npm install && npm test should work (note this isn't universal, but it's frustrating to be asked to npmignore .babelrc and break this use case due to the RNP)

In addition, this practice kind of permanently cements RN packages with the transpiler settings that the RNP uses - which, since it includes not-yet-stage-4 features, are quite likely to change in a breaking way in the future.
Here's my proposal to enable the benefits of the current approach (cleaner stack traces, optimization opportunities within the RNP, etc) in a way that will allow RN packages to rejoin the wider JS ecosystem:

Designate a new top-level package.json key - let's go with "sources" for the time being. This contains an object. All subkeys of "sources" are optional.
Within "sources":
"raw" points to the entry point for utterly untranspiled code. .babelrc (or other babel config locations), if provided, configure how this code should be transformed.
"react-native-v1" (swap out v1 for any versioning scheme; this frees up the RNP to change their preferred transpiler settings freely.
"node4", "node5", "node6", "node7", etc: code transpiled down to features matching the indicated major node version, following https://www.npmjs.com/package/babel-preset-node7, https://www.npmjs.com/package/babel-preset-node6, etc.
"es2015", "es2016", etc: code transpiled down to features that are included in the given year of publication of the ecmascript standard.
The RNP ships with support for this, with priority: ["react-native-", "node-" (>= the major node version, obv), "main" (with transpiling)]. This change is loudly communicated with blogs, tweets, and documentation.
At some future point (this can be as soon, or as indefinite, as is deemed necessary), the RNP will cease transpiling "main" - since the other "sources" don't require looking for babel configs, this will be when RN packages can (and should) publish their .babelrcs again.

This approach allows for supporting other languages, future transpiler settings, etc, in a nonbreaking way, without infecting the npm ecosystem with untranspiled "main" entry points (inhibiting people's ability to share RN packages across normal react). A package will always be able to choose to omit "main" entirely, which will clearly and explicitly convey to users that their package must not be used without the RNP.
Further reading (credit @ide): https://gist.github.com/ide/e7b9181984933ebb0755c7367a32e7e8

I'm fully in support with stopping to transpile node modules. I have to consider a bit more deeply what the actual solution will look like and how many sources on average will be published. We shouldn't encourage people to publish their package with ten sets of differently compiled code.
For RNP, I would recommend the following:

At some point in the future, start warning for every node_module that it has to compile. Communicate with the community what we are planning to do and encourage package developers to compile their code. Provide an easy workflow to make this happen.
At some point later, we should stop compiling node_modules by default. If something breaks, we'll encourage users to manually whitelist the package that fails.

There is no reason not to enable the escape hatch; especially since there is no point in breaking existing users completely in a way they can't move forward.

@cpojer I think it would be worse if the packager didn't transpile node_modules at all. We get a lot of benefits because the packager is able to transpile node_modules that are mentioned in the gist. I would be on board with your RNP proposal if this bullet point came before the other two:

If a package specifies sources.react-native-vX, transpile the source code from that entry point. Skip the other steps since this package author has explicitly said they want RNP to transpile the code, we don't need to print a warning.

We shouldn't encourage people to publish their package with ten sets of differently compiled code.

Ten might be excessive, for the sake of this conversation wrt React Native why don't we focus on just two? Package authors will choose which sources they want to publish. If someone is authoring react-native-widget they will likely just want to publish main and sources.react-native-v1. A package like lodash might publish just main and es2016. I think the package tarballs will compress quite well too.

I'm not sure i see the harm in publishing packages with multiple sets of differently compiled code, a great many packages already publish two. That said, we don't need to encourage that - it'd be more that we were encouraging them to select one thing, and publish 1) ES5, 2) their choice, and 3) very optionally the "raw". The goal is to enable/encourage publishing ES5, and explicitly informing the RNP of which transpiler settings it should be using.

Somewhat related -- I just made this: https://github.com/skevy/babel-preset-react-native-syntax
This preset would help React Native package authors transpile their code down to what is described here as "sources.react-native-v1".

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.

@hramos it should absolutely still be open for all the same reasons; RN packages are polluting the ecosystem, and this issue proposes a path to stop that. Please reopen.

Has there been any movement here? I don't disagree on the usefulness of the work, rather it seems like the issue is not actively being worked on.

Unfortunately it doesn't seem that way; but issues should be closed when they're resolved or wontfixed, not just because nothing has happened yet.

Unfortunately we have over 1,000 issues open. Closing inactive issues will allow us to focus on what is actively being worked on. Closing the issue won't delete the conversation, and we can easily re-open when things get moving.

@cpojer any thoughts on starting this process? The sooner it's begun the more time we have to gradually migrate module authors over.

@ljharb hey jordan! The packager is actually getting moved out of this repo pretty soon, into it's own thing (which should be easier to iterate on, discuss, take PRs, etc). I'll try to remember to open this issue there (unless you beat me to it). This should be happening in a couple weeks. :)

Thanks, that sounds great!

In the process of closing stale issues, I missed that @ljharb was the original author of this issue. I think it's fair to re-open an issue where the OP is actively interested.
I'll re-open this for now, so we don't lose track of it when the packager is moved out.

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos any chance this could still be left open? I'm still actively interested.

Of course. Re-opening.

stalebot: this issue has the For Discussion label.

No supper for stalebot tonight.

This is definitely still forever going to be a problem until the RN team fixes it.

@cpojer what should we do here? This issue seems like a better fit for the discussions-and-proposals repo, which didn't exist at the time the issue was created.

(Stale bot is not supposed to nag on Discussion issues, but I recently renamed the "Type: Discussion" label but neglected to update Stale bot's config. Sorry about that)

Don't currently have any plans to change what we are doing in RN.

@cpojer can you elaborate on whether you've changed your mind since your comment here?

I haven't changed my mind, but I doubt anybody is going to change things and I won't have time to spend on this either.

I'm gonna close this now as we aren't likely to make any progress on this in the next six months, and this issue has been open for a very long time without any progress. If anybody wants to volunteer to change the status quo, please create an issue with a thorough plan in our discussions-and-proposals so that we can agree and that you can start executing on this.


Unable to download your finetuned Bert model

Please provide the aws link for downloading your finetuned model. Thanks.

https://huggingface.co/monologg/bert-base-cased-goemotions-ekman
https://huggingface.co/monologg/bert-base-cased-goemotions-group

I tried to download all the files and use it for prediction as shown in your github readme. It is showing me
UnicodeDecodeError : 'utf-8' codec can't decode byte : invalid continuation byte. Please let me know how to fix this.

I tried to download all the files and use it for prediction as shown in your github readme. It is showing me
UnicodeDecodeError : 'utf-8' codec can't decode byte : invalid continuation byte. Please let me know how to fix this.

First of all, you don't have to download the files manually. If you run the code below, all the files will be downloaded automatically from huggingface s3
from transformers import BertTokenizer
from model import BertForMultiLabelClassification
from multilabel_pipeline import MultiLabelPipeline
from pprint import pprint

tokenizer = BertTokenizer.from_pretrained("monologg/bert-base-cased-goemotions-original")
model = BertForMultiLabelClassification.from_pretrained("monologg/bert-base-cased-goemotions-original")

goemotions = MultiLabelPipeline(
    model=model,
    tokenizer=tokenizer,
    threshold=0.3
)

texts = [
    "Hey that's a thought! Maybe we need [NAME] to be the celebrity vaccine endorsement!",
    "it’s happened before?! love my hometown of beautiful new ken 😂😂",
    "I love you, brother.",
    "Troll, bro.  The motherfucker does nothing but stink up libertarian subs talking shit",
]

pprint(goemotions(texts))

Plz run this code and write all the logs you got:)

I ran this snippet of code and got the mentioned error. I have to download
it manually as my http access is blocked. So it can't be downloaded while
running the code. Please give me some idea if possible why the earlier
mentioned error is happening.
Thanks and Regards.
Saumajit Saha
On Thu, 30 Jul, 2020, 1:28 PM Jangwon Park<EMAIL_ADDRESS>wrote:

I tried to download all the files and use it for prediction as shown in
your github readme. It is showing me
UnicodeDecodeError : 'utf-8' codec can't decode byte : invalid
continuation byte. Please let me know how to fix this.
First of all, you don't have to download the files manually. If you run
the code below, all the files will be downloaded automatically from
huggingface s3
from transformers import BertTokenizer
from model import BertForMultiLabelClassification
from multilabel_pipeline import MultiLabelPipeline
from pprint import pprint
tokenizer = BertTokenizer.from_pretrained("monologg/bert-base-cased-goemotions-original")
model = BertForMultiLabelClassification.from_pretrained("monologg/bert-base-cased-goemotions-original")
goemotions = MultiLabelPipeline(
model=model,

tokenizer=tokenizer,

threshold=0.3

)
texts = [
"Hey that's a thought! Maybe we need [NAME] to be the celebrity vaccine endorsement!",

"it’s happened before?! love my hometown of beautiful new ken 😂😂",

"I love you, brother.",

"Troll, bro.
Reply to this email directly, view it on GitHub
https://github.com/monologg/GoEmotions-pytorch/issues/1#issuecomment-666205202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI6PWP6XUNCFT67Y46TLAJLR6ERYRANCNFSM4PKZLQFQ
.

I can't infer the reason only based on the one line of the log that you gave. (UnicodeDecodeError : 'utf-8' codec can't decode byte : invalid continuation byte)
You should give all the log from console.
What I can only guess is that you might not save the file (vocab.txt etc) in utf-8 format.
Can you check the encoding of the files?


Feature/all kinds suggestions

This PR attempts to make relationships between optional files more clear.

Slots can now receive an OptionalityGroup, which in the general case does nothing except be a renderable. However, the merge_groups utility can use these groups to add some structure to a list of slots.
Currently only one layer of optionality groups is supported. However, multiple layers can be implemented with recursion if necessary.
Also I've added help texts to the side of the attachment slots.

Super nice, imma take this and merge it


Added a new book as well as missing author names and file types for various books under "Operating System Development" section. Updated links for some books.

Added famous free book "Operating System: From 0 to 1" by Tu, Do Hoang.
Added missing author names and file types for various books under "Operating Systems" section.
Updated links for some books to reflect the current version of the book.
What does this PR do?
Added book "Operating System: From 0 to 1" by Tu, Do Hoang.
Added missing author names and file types.
For resources
Description
"Operating System: From 0 to 1" by Tu, Do Hoang is a famous free book for OS Development.
Author names and file types were missing for various books in the "Operating Systems" section. I added the same.
Why is this valuable (or not)?
"Operating System: From 0 to 1" by Tu, Do Hoang appears on the first page on google search of "best free books to learn operating system development".
The authors get their due credit, folks know the book file types! :)
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

I had mistakenly created a new branch under my fork and made the last PR through it. I have closed my previous PR and created a new one with my "main" branch containing all the changes that I have made. :)

Thanks, and welcome to free-programming-books!

Thanks, and welcome to free-programming-books!

Thank you, sir! I will keep contributing by adding new resources and maintaining the current ones. I will perhaps do more of the maintenance work. 😊


HAS_STRUCTURE biome tag fields should be renamed to HAS

Example of what I am seeing in 1.20 Yarn BiomeTags class:

Personally, I feel this is a cause where it should break out of the <inner_tag>_<outer_folder> format in favor of cleaner readability.
In this case, I propose HAS_<inner_tag>. Or HAS_STRUCTURE_<inner_tag> which still reads better that current situation

Another possible format is HAS_<inner_tag>_STRUCTURE just for completeness.
So
HAS_STRONGHOLD
HAS_STRONGHOLD_ STRUCTURE
HAS_STRUCTURE_STRONGHOLD
Just should ideally start with HAS_

FYI, these names are automatically generated in this format by name-proposal. The mappings for that class look pretty empty:
https://github.com/FabricMC/yarn/blob/b0581c68220cc4fe9247584984b7395b37e6cf4b/mappings/net/minecraft/registry/tag/BiomeTags.mapping#L1-L3


Expose connection property on _JSONSpeechAPI.

Operation.poll uses the connection to make the request.  This was missed in the tests since they set connection to _Connection().

Thanks @tseaver! I have system tests that these are blocking! More to come!


Streaming generation support

Is there a way to support streaming intermediate results during decoding, like GPT-3?
Thank you,
Michael

Please refer this example https://github.com/NVIDIA/FasterTransformer/blob/main/examples/cpp/multi_gpu_gpt/multi_gpu_gpt_async_example.cc

Thank you @byshiue. Would it be possible to do this for T5 specifically? And ideally with Triton support?

This feature would be very helpful for us. We could be interested in making it ourselves and contributing it as a PR. Could you outline the rough steps necessary? Can we mostly copy the GPT code?

You can refer how GPT module register the call back by registerCallback, and how we pass the call back in triton and triton backend.


Allow passing '-' to 'reprounzip graph' to write to stdout

[Current coverage][cc-pull] is 62.66%

Merging [#190][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master       #190   diff @@
==========================================
  Files            32         32
  Lines          6092       6034    -58
  Methods          70         69     -1
  Messages          0          0
  Branches        932        926     -6
==========================================
- Hits           3814       3781    -33
+ Misses         1943       1919    -24
+ Partials        335        334     -1

Powered by Codecov. Last updated by [690dbc8...b7eee78][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ViDA-NYU/reprozip/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ViDA-NYU/reprozip/compare/690dbc814859a9bd541a0f0f29508acf1948825b...b7eee78143a18fdcda72838dca8aa3ff5e351ad4
[cc-pull]: https://codecov.io/gh/ViDA-NYU/reprozip/pull/190?src=pr


Compilers: elaborate on NQP more?

the NQP section doesn't even mention that rakudo's written in it; that could be quite enlightening

fixed via ed8ca15


Better chat behavior

for the chat, it would be better if it had better scrolling and a better way of finding messages without losing your place when new messages pop up. an arrow to go to the top of the chat would be cool too (idea of button from cherrybun)
would like to know if this is possible or not because how cytube handles chat @airforce270

out of scope cos cytube


Sample code generated does not work

Here's the process for testing:

open p5.serialcontrol
scan for ports
open a port
Copy serial code as generated
paste into a new sketch at  https://editor.p5js.org
add CDN link after line 6 of index.html:

Solution: the CDN link mentioned on the main readme page needs a closing  tag.

Added closing tag in the readme file!


Properly set ActiveContent after drop

For some reason, the ActiveContent of a Pane is not changed after a DockTo is performed. This is not in line with how Visual Studio docking behaves; if you dock something it will always become the active content.

I think this is resolved by PR #529 ?

Closed via #529


Invalid duration of youtube video reported by --dump-json

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2019.09.01
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-j', u'-v', u'tUmWbZ2HCp4']
[debug] Encodings: locale UTF-8, fs UTF-8, out None, pref UTF-8
[debug] youtube-dl version 2019.09.01
[debug] Python version 2.7.15rc1 (CPython) - Linux-4.19.66-1-MANJARO-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: ffmpeg 3.4.6, ffprobe 3.4.6
[debug] Proxy map: {}
[debug] Default format spec: bestvideo+bestaudio/best

{
    "_filename": "live Ashra Mjalis (Z Qazi wasim abas Multan)  04 Muhrram Thallah Syedan G14 Islamabad 2019-tUmWbZ2HCp4.mp4",
    "abr": 128,
    "acodec": "mp4a.40.2",
    "age_limit": 0,
    "album": null,
    "alt_title": null,
    "annotations": null,
    "artist": null,
    "automatic_captions": {},
    "average_rating": 4.8415842,
    "categories": [
        "People & Blogs"
    ],
    "channel_id": "UCgBWyQBWQ0Lduws9sIvr6Ig",
    "channel_url": "http://www.youtube.com/channel/UCgBWyQBWQ0Lduws9sIvr6Ig",
    "chapters": null,
    "creator": null,
    "description": "official video of http://wwvw.talagangazadari.com like http://www.facebook.com/TalagangAzadari Whatsapp +923045121476 +923349457214",
    "dislike_count": 4,
    "display_id": "tUmWbZ2HCp4",
    "duration": 1,

Description

WRITE DESCRIPTION HERE
The --dump-json reports duration=1 while the video is over 1 hour long.
Use this command:
youtube-dl -j 'https://www.youtube.com/watch?v=tUmWbZ2HCp4' > tUmWbZ2HCp4.json
Look into the json file and you'll see that duration is reported as 1.
If this is for some reason a 'nofix', then at least tell me how to determine when the duration field is invalid. Maybe youtube-dl should sum the formats/duration fields to calculate the final duration?

I tried that but the actual method worked a little differently for me
The --dump-json reports duration=12 while the video is not even an hour long.
Use this command:
youtube-dl -j 'https://www.youtube.com/watch?v=3IJYHdq36io&t=3s' > 3IJYHdq36io&t=3s.json
Look into the json file and you'll see that duration is reported.
If this is for some reason a 'nofix', then at least tell me how to determine when the duration field is invalid. Did youtube-dl should sum the formats fields to calculate the total duration?

both videos report the correct duration.
youtube-dl -j tUmWbZ2HCp4 | jq .duration
4131
youtube-dl -j 3IJYHdq36io | jq .duration
145


wb55: fix SYSCFG base address (and Makefile)

This is a batch of two fixes:

Uses the correct base address from the RM for SYSCFG. This fix was checked to work in the hardware
Fixes Makefile to produce correct directory

Thanks!
It looks like the SYSCFG problems run deeper: the reason the SVD has the wrong address is because SYSCFG is split between 4001_0000-4001_002F and 4001_0100-4001_01FF with VREFBUF stuck in the middle. As well as updating the baseAddress as you've done, we should update the addressBlock size to 0x200. Unfortunately it seems all the registers in the 4001_0100 region are wrong in the SVD too (IMR1, IMR2, C2IMR1, C2IMR2, SIPCR) as their offsets ignore the jump over VREFBUF so need updating to 0x100, 0x104, etc.

Thanks!
It looks like the SYSCFG problems run deeper: the reason the SVD has the wrong address is because SYSCFG is split between 4001_0000-4001_002F and 4001_0100-4001_01FF with VREFBUF stuck in the middle. As well as updating the baseAddress as you've done, we should update the addressBlock size to 0x200. Unfortunately it seems all the registers in the 4001_0100 region are wrong in the SVD too (IMR1, IMR2, C2IMR1, C2IMR2, SIPCR) as their offsets ignore the jump over VREFBUF so need updating to 0x100, 0x104, etc.

@adamgreig so the next steps should be joining those two together with the VREFBUF area marked as reserved/skipped to get a contiguous memory map for SYSCFG?

@adamgreig so the next steps should be joining those two together with the VREFBUF area marked as reserved/skipped to get a contiguous memory map for SYSCFG?

@adamgreig so the next steps should be joining those two together with the VREFBUF area marked as reserved/skipped to get a contiguous memory map for SYSCFG?

Yes, I think that's the best way to go.

@adamgreig so the next steps should be joining those two together with the VREFBUF area marked as reserved/skipped to get a contiguous memory map for SYSCFG?

Yes, I think that's the best way to go.

The same problem exists in the WL family. I'll try to get to it this week and perhaps you can use the same patches here.

#493 cherry-picked the Makefile fix, and #624 fixes SYSCFG, so it looks like this PR can be closed now. Thanks for getting it started!


Documentation and Async fix

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: