Data migration

Prep

[x] convert script to use async/await
[x] v0.1 Listing addresses

[x] Rinkeby: 0x94dE52186b535cB06cA31dEb1fBd4541A824aC6d
[x] Ropsten: 0xE66c9c6168d14bE4C3c145f91890740CbDf9EC8B

[x] Download listings:

[x] Rinkeby
[x] Ropsten

[ ] Run new migration script against local chain and post output

Dry Run (on 0.5.8)

[x] Confirm test accounts have eth for gas

[x] Rinkeby: 0x94654f3904277585ea3fd882cf61433e2d28f52b

https://plus.google.com/103455851849409861163/posts/UDN3SSm6iCy

[x] Ropsten: 0xbd8414aa07e52edd5c0369b779ad80406e191165

https://ropsten.etherscan.io/address/0xbd8414aa07e52edd5c0369b779ad80406e191165

[x] Have ListingsRegistry addresses

[x] Rinkeby: 0xbc16a0193de4cbbb39c188850df711340d151b3f
[x] Ropsten: 0xac824c89eab1b2e1b92f0e1675b49d5ddaee06fe

[ ] Run migration and post output

[ ] Rinkeby
[ ] Ropsten

Migration (on 0.5.10)

[ ] Confirm migration accounts have eth for gas

[ ] Rinkeby
[ ] Ropsten

[x] Have ListingsRegistry addresses

[x] Rinkeby: 0x23e9b208198e7c7d7f828dfe9f136938d61a731f
[x] Ropsten: 0x2eeb6eafecef49a82d25a03d136c61109b61793a

[ ] Run migration and post output

[ ] Rinkeby
[ ] Ropsten

Follow-up

[ ] visual inspection through dapp

[ ] Rinkeby
[ ] Ropsten

[ ] Post notice of migration complete on Discord

Moving into the original thread (#148)


OSError: cannot identify image file <_io.BufferedReader name='./data/LSUN_fix/LSUN_fix/._correct_resize_1.png'>

Hi, nice work!
When I ran experiments on cifar10, I got the error, it seemed like that the files of LSUN_fix. I was a freshman on the task, Would you please give me some advice?
Best wished to you!

Hi,
It was too strange，I ran the experiments normally now, I had not met the error anymore, maybe I had some incorrect manner.
I was very sorry to bother you! Thank you very much!


Error in Internet Explorer 11

const VueModelAutoset = {
  install(Vue)  {

expecting  ":" after "install" method

It is ES2015+ js standard notation. You should use babel compiler to convert this to es5. ES2015+ support is not wide spread in browsers yet.


minimal working example: rollup + babel + async/await

I saw some issues (#209, #306) and questions on stackoverflow about how to configure rollup and babel so I can use async and await. There are many (often outdated) answers and it is a tedious, difficult (but hopefully not impossible) task to create a working rollup.config.js. I was not able to do that.
My repository

https://github.com/htho/mweRollupBabelAsyncAwait

should become a minimal working example.
Right now it is a vanilla rollup.config.js based on the official rollup.js guide. https://rollupjs.org/guide/en/#babel
I understand that rollup is currently es6 only, and therefore does not support async/await natively. But I thought that this would be babel's job anyway. For the Developer Experience, setting up rollup+babel with async/await support, should be a no-brainer.
Please help me. Or integrate it into this repository. A set of minimally working examples would make developers lifes so much easier.

It all depends on what are your requirements and target format, you can make your example work by using such a setting:
{
  "presets": [
    ["@babel/env", { "modules": false, "useBuiltIns": "usage" }]
  ]
}

I am required to set the corejs version.
$ ./node_modules/.bin/rollup -c

src/BuildTest.js → dist/BuildTest.js...

WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in
future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option.

You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following
commands:

  npm install --save core-js@2    npm install --save core-js@3
  yarn add core-js@2              yarn add core-js@3

(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
regenerator-runtime/runtime (imported by src\BuildTest.js)
created dist/BuildTest.js in 2.3s

OK, which core-js should I use, and where do I "explicitely" set the corejs version via the corejs option?
I can not find the answer: https://duckduckgo.com/?q=babel+rollup+declare+the+core-js+version&t=ffab&ia=web

Use latest one:
{
  "presets": [
    ["@babel/env", { "modules": false, "useBuiltIns": "usage", "corejs": 3 }]
  ]
}

Still not sufficient:
./node_modules/.bin/rollup -c

src/BuildTest.js → dist/BuildTest.js...
(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
regenerator-runtime/runtime (imported by src\BuildTest.js)
created dist/BuildTest.js in 2s

U have to install regenerator-runtime module and u should be ready to go

Thank you so far.
I have updated my repository in order to reflect the changes we discussed.
The regenerator is available now.
But IE still needs a Polyfill for Promise. I'd expect babel to include it aswell, but it isnt. Is it a problem with babel? To my understanding, the babel documentation suggests that the Promise polyfill is included aswell: https://old.babeljs.io/docs/usage/polyfill/

In your example rhe reference to a Promise is only in so called babel helpers (asyncGeneratorStep & asyncToGenerator here). Those are insertes "as is" - without compilation, so preset-env doesn't visit it to see a Promise which would cause it to insert a ponyfill import. To work around this you can insert Promise.resolve() into your code, or you can just polyfill Promise globally.

Hi. Once someone explained the internals to me, this seems totally logical. But in my opinion consumers of a tool should not need learn these internals. They should not be required to solve this problem on their own. The solution should not be a dummy call to Promise.resolve(). But that is another topic.
 On the other hand, I am really frustrated a task that is so basic, is so complicated. The documentation of all the releated tools and all the error messages are so useless. I really am someone who says and does RTFM ans STFI all the time, but I cant help myself here.
Manually including the polyfill circumvents the useful useBuiltIns. So I make the dummy call.
Guess what! It still does not work. The polyfill that is included uses calls to require() and of course they can not be resolved at runtime. Thats what rollup or babel should do.
I updated the repository again.
Please I really start doubting myself.

I agree with all of your points, this is a surprisingly hard thing to do for something supposedly that simple. Even I had to look through docs and babel source code to try find a good combo of options for various outputs which I have wanted to achieve here.
Problem is that requirements are different for people though, one is fine with polluting global namespace with polyfills, one is not and want to use ponyfill imports, other one doesn't want to polyfill at all or just want to handle on their own. That's why there is no one golden example for doing this. I've brought this up to a Babel team though and hopefully we should be able to figure out a better way of doing this like this.
I'll look at your repo at later time, unfortunately I don't have much time right now.

Have a look at egoist/bili  it removes a lot of the complexity.  And uses rollup under the hood.
I've pulled my hair about this today, and I could have recent Babel 7, along with tests to work. Lots of things changed since Babel 6.
I pushed something that works with testing with recent config. Tests works woth modern async/await, uses modules and does transpilation in different targets (e.g. Node, Browser) and mimicks one module member of a monorepo.  Try it out, maybe it'll help. https://github.com/renoirb/experiments-201907-bili-babel-preset-env-multiple-target-builds

Hi @renoirb,
bili sounds nice. But I am always sceptical when I need to put more and more parts of my build-process into someone elses hands. New systems introduce new problems. This speaks from my heart: https://bravenewgeek.com/tag/taco-bell-programming/
As long as I can, I want to use the cat, sed and grep of the bundle/transpile world.
Anyway, it is good to know that there is bili out there. Should I or the awsome devs at rollup and/or babel not find a solution in the next time, I need to reeavaluate it.
Thank you very much!

 /dist/BuildTest.js

  ...
  var $ = require('../internals/export');
  var IS_PURE = require('../internals/is-pure');
  var global = require('../internals/global');
  var path = require('../internals/path');
  var redefineAll = require('../internals/redefine-all');
  ...

Hi,
I didn't find an "internals" directory, so where did it require internals?

Hi @FuJuntao as far as I understood the problem. This code is copied&pasted somwhere from within babels directory structure. Somewhere in there, there might be an internals directory. But the problem is, that the code is not transpiled/included before it is moved here.

as a workaround, set useBuiltIns value to "usage" inside @babel/preset-env options. These required variables from internals came from core-js internal.

I'm having the same kind of issues. I've tried just about every combination I can think of between rollup and babel, but still can't get it working properly.
rollup.config.js:
import pkg from './package.json';
import babel from 'rollup-plugin-babel';

export default [
  {
    input: 'src/index.js',
    output: [
      { file: pkg.browser, format: 'umd', name: 'MyLib' },
      { file: pkg.main, format: 'cjs' },
      { file: pkg.module, format: 'es' },
    ],
    plugins: [
      babel({
        babelrc: false,
        exclude: 'node_modules/**',
        presets: [
          [
            '@babel/preset-env',
            {
              corejs: 3,
              modules: false,
              useBuiltIns: 'usage',
              forceAllTransforms: true,
              targets: {
                node: 'current',
                ie: '11',
              },
            },
          ],
        ],
      }),
    ],
  },
];

The first few lines of my output file, however, contain references directly to core-js and regenerator-runtime. I have both of those installed as devDependencies.
require('core-js/modules/es.array.from');
require('core-js/modules/es.array.iterator');
require('core-js/modules/es.map');
require('core-js/modules/es.object.to-string');
require('core-js/modules/es.string.iterator');
require('core-js/modules/web.dom-collections.for-each');
require('core-js/modules/web.dom-collections.iterator');
require('regenerator-runtime/runtime');

Update: Finally got it working with the following rollup.config.js (no babel config as it is inlined in the rollup config):
import pkg from './package.json';
import babel from 'rollup-plugin-babel';
import resolve from 'rollup-plugin-node-resolve';
import commonjs from 'rollup-plugin-commonjs';

export default [
  {
    input: 'src/index.js',
    output: [
      { file: pkg.browser, format: 'umd', name: 'ZDocs' },
      { file: pkg.main, format: 'cjs' },
      { file: pkg.module, format: 'es' },
    ],
    plugins: [
      babel({
        babelrc: false,
        exclude: 'node_modules/**',
        presets: [
          [
            '@babel/preset-env',
            {
              corejs: 3,
              modules: false,
              useBuiltIns: 'usage',
              targets: {
                ie: '11',
              },
            },
          ],
        ],
      }),
      resolve(),
      commonjs(),
    ],
  },
];

The fix was adding rollup-plugin-node-resolve and rollup-plugin-commonjs. I didn't need any additional babel plugins like transform-runtime or transform-async-to-generator.
CC @FuJuntao - I had the same internals references as you after I added rollup-plugin-node-resolve. That was fixed and properly inlined once I added rollup-plugin-commonjs. Hope that fixes your problem as well.

Thank you @green-arrow now it works!
https://github.com/htho/mweRollupBabelAsyncAwait
@Andarist It still is necessary to include the dummy call to `Promise.resolve()``. Will there be a solution for this inconvenience?

I am currently looking into that example: https://github.com/htho/mweRollupBabelAsyncAwait.
It kinda works but the Promise.resolve() hacks seems weird and confusing (Is it just Promise or are other things broken too?). Has there been any progress in finding the cause of that problem?
My current work around is basically @babel/plugin-transform-runtime. And honestly, I don't really understand the difference between babel's plugin-transform-runtime and preset-env's useBuiltIns set to usage. The former one seems to produce slightly smaller output than the latter one.

I have a running example of async/await written in TypeScript, and multiple build outputs. It's also using @babel/plugin-transform-runtime

Thanks for putting this together guys! Awesome stuff. This was a confusing process indeed.


Update nozzle.go to remove old envelope types

Signed-off-by: Lukasz Rabczak<EMAIL_ADDRESS>Updates the the nozzle package to no longer refer to HttpStart/HttpStop envelopes which were removed from sonde-go in https://github.com/cloudfoundry/dropsonde-protocol/commit/3dd1473786cf6acdcc55e2206a58f08ad02f29ca

Thanks!


Bump upper bound of hpc to 0.8

I recently released a new major version of hpc: <IP_ADDRESS>. The only significant difference is that hpc has dropped all promises about safe/trustworthy Haskell. This is due to the fact that we depend on the directory package which recently dropped its SafeHaskell promises.
If you don't use SafeHaskell then you shouldn't notice a difference, except that we are now compatible with newer versions of the directory package.

Oh! Sorry I didn't see this @BinderDavid! I did do this in #32, so this is not needed anymore


Fix warnings with ruby 2.7

Please let me know if I need to change anything.

@jfabre Thanks for this! What do you think about adding some 2.7 test coverage by updating the rvm list of the .travis.yml?

Merged and bumped to 3.1.0.

Hey I'm sorry, I must have forgotten about your reply.
Thanks for merging it anyway.

Hey, no worries, @jfabre, I appreciate the pull request.  I added the 2.7.1 coverage. We're good to go.


Reforganized, refactored, and linted code

Implemented a few guards instead of if blocks
Used SwiftLint to have code meet the swift standards
Switched several functions to computed variables instead

These look like good changes to me, although obviously breaking

Thanks for submitting this @Ponyboy47. These changes are pretty massive, and breaking so I don't think we want to merge this. If you'd like to break out some of these pieces (some of which aren't necessary anymore such as the Package.swift changes) and submit them separately feel free!


Update pod specs

This PR updates pod specs for proper support of Cocoapods integration. Version is bumped to 1.1.1

Thanks for this!


Failed to upload a part to S3: The provided token has expired

Error dump:

Mapbox Studio @ http://localhost:3000/
Error: Failed to upload a part to S3: {"message":"write EPIPE","code":"NetworkingError","errno":"EPIPE","syscall":"write","region":"us-east-1","hostname":"tilestream-tilesets-production.s3.amazonaws.com","retryable":true,"time":"2014-12-01T14:22:48.833Z","statusCode":400}
 Additionally failed to abort the multipart upload on S3: ExpiredToken: The provided token has expired.
    at Writable. (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/index.js:124:17)
    at Writable.emit (events.js:117:20)
    at Response. (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/s3-upload-stream/lib/s3-upload-stream.js:249:21)
    at Request. (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/request.js:263:18)
    at Request.callListeners (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/sequential_executor.js:117:20)
    at Request.emit (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/sequential_executor.js:85:10)
    at Request.emitEvent (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/request.js:537:10)
    at Request.failRequest (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/request.js:498:10)
    at Request. (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/request.js:484:32)
    at Request. (/Users/kristianfallro/Projects/mapbox-studio/node_modules/mapbox-upload/node_modules/aws-sdk/lib/request.js:541:20)

npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "start"
npm ERR! node v0.10.30
npm ERR! npm  v2.1.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `./index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is most likely a problem with the mapbox-studio package,
npm ERR! not with npm itself.

Data source: Roughly 2 GB of PostGIS data
Will try to run a mbtiles export as well.

We fix a regression on the Mapbox API side that we issuing credentials with shorter expirations. This should be fixed now.


New Proposal for How to Move Extras out of Ansible Core Umbrella

Extras, I think, should be in a bit of a different place regarding how it is contributed to and who manages it.  This is a first draft proposal for how to accomplish that. @gregdek @jimi-c @robynbergeron @ansible/ansible-commit

I don't see us changing the rules for core but community will clearly want to loosen up the ones for extras


kubefirst should leverage a pull through cache on images hosted in dockerhub

dockerhub images can be problematic due to their rate limits. ecr has the ability to establish a pull through cache for the dockerhub upstream so we don't depend on docker for anything beyond first-time image pulls. this would also improve our reliability for kubefirst local attempts in a kubecon type environments where folks have to share public ip space.

If not, 'k8s-image-swapper':
https://estahn.github.io/k8s-image-swapper/
is an easy to use, on-the-fly transparent cache.


Backport: "stabilize the C2P resolver URI scheme" to v1.49.x

Backports https://github.com/grpc/grpc/pull/30653

failures unrelated


Badges with stats

First, thanks for making this, it is really useful 🙂
Second, the reason of this issue: I think it would be really nice to be able to have badges for separate stats (gofmt, golint, ...) as well as for the global score as it appears on the High Scores page. The target goal being to be able to just have a glande at the badges without having to click on the current goreport badge to see details.
What do you think about it?

I quite like the idea, to be honest. But it would require some code changes and perhaps a more cluttered UI (which is best avoided), and a CI tool like Jenkins or Travis-CI is perhaps a better place for this. If we get a lot of upvotes on this issue I might rethink my stance, but for now I think it's not worth the extra complication.

It could perhaps be done by passing additional query parameters to the badge URL, that's how Sonarqube does it for different metrics, for example image:https://sonarcloud.io/api/badges/measure?key=org.codehaus.griffon:griffon&metric=sqale_debt_ratio["Technical Debt", link="https://sonarcloud.io/dashboard?id=org.codehaus.griffon%3Agriffon"] results in


Retirement warn in days only

Since we only support days for retirement_warn, the PR that added the hour granularity needed to have those fields removed and remaining fields needed to be changed to make sure that we're staying true to storing an int in that field as a count of days like the UI sets.

So all these fields should set an int that reflects days before retirement.
Fix for https://github.com/ManageIQ/manageiq/issues/18618.
https://bugzilla.redhat.com/show_bug.cgi?id=1695219 is the bz.

@miq-bot assign @tinaafitz
@miq-bot add_label bug
No idea what you all want to do for backporting, any ideas, Tina?

@miq-bot add_reviewer @jrafanie

hey @eclarizio could you please 👀

anyone want to merge this?

@gmcculloug hi, could you please look at this again?


1.1.0 alpha cgroups

Introducing unprivileged containers:

Containers with the privileged=False are forced to join the corex cgroup. This group atm only limits accessing some system devices.
Also those containers capabilities are lowered a lot. so processes running inside this container loses root privileges (this will prevent it from remounting the cgroup fs and change their cgroups permissions for example)
It was tricky limiting the capabilities since cap limiting works per thread and GO itself is a multithreaded runtime. So we had to make sure the current thread is limited before doing an exec

Codecov Report

Merging #214 into 1.1.0-alpha will decrease coverage by 0.36%.
The diff coverage is 0%.

@@               Coverage Diff               @@
##           1.1.0-alpha     #214      +/-   ##
===============================================
- Coverage        16.74%   16.38%   -0.37%
===============================================
  Files               15       15
  Lines             1033     1056      +23
===============================================
  Hits               173      173
- Misses             849      872      +23
  Partials            11       11

Impacted Files
Coverage Δ

base/pm/pm.go
0% <0%> (ø)
:arrow_up:

base/pm/runner.go
0% <0%> (ø)
:arrow_up:

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 fb7a1f6...ea072fc. Read the comment docs.


other browsers than Chrome?

Hi
I am looking for an easy way to commit my code to github. I found your Chrome extension. I work on different projects under different Google accounts so I am using Vivaldi and Brave at the same time. It seems tome that the extension is working only with Chrome. Is that right?
Are you planning to support other browsers like Brave or Vivaldi or any other?
Thank you
Radek

The old version can support other browsers, but the new version(5.x) only works with chrome since it use the chrome login feature.


Updated java version check to fix dependency error

Issue #, if available:
Current java type checking caused issues differentiating between Java 1.x and Java Version x
Description of changes:
Updated the bash script for installation to include regex that can handle both ways of reporting Java Version
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Meant to make this in my personal repository, sorry.


Upgrade to Jackson 2.10

I'm looking into adding support for configuring the header mapper for an outbound channel adapter in XML; it seems to be missing.
I've cloned the repository, but I can't get the unit tests running ("gradlew test"). They all fail with "java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/json/JsonMapper"
I guess I'm doing something wrong?

I have just pushed an upgrade to Jackson 2.10 and all tests passes for me.
Thank you for your willing to contribute; looking forward for your PR(s) !


Can't modify frozen jenkins_jnlp_slave

Cookbook version
v5.0.1
Chef-client version
13.0.118
Platform Details
Chef Client is running in a Vagrant VM driven by Test Kitchen. VM is a Centos 7.2 machine provided by Bento (bento/centos-7.2). My development machine is a Macbook Pro running macOS 10.12.3 with the following ChefDK:
$ chef --version
Chef Development Kit Version: 1.3.43
chef-client version: 12.19.36
delivery version: master (dd319aa632c2f550c92a2172b9d1226478fea997)
berks version: 5.6.4
kitchen version: 1.16.0

Scenario:
I'm trying to create a new Jenkins slave by leveraging the jenkins_jnlp_slave resource. Whenever my cookbook converges, it appears to create the slave and set it up correctly. I can verify this by going into the Jenkins master I'm testing against and finding my test VM connected and ready. I'm even able to schedule Jenkins jobs to run on it. Despite the slave being functional, the Chef Client run fails. I've included the error message in the Actual Results section.
Steps to Reproduce:
Initially, I thought the issue was due to my usage of the jenkins_jnlp_slave resource, so I created a test cookbook which you can find here. Using that cookbook, one can reproduce the issue simply by running: $ kitchen converge.
However, I discovered this morning the issue may be reproduced without my test cookbook. Simply clone this repo and run the following test suite:
$ kitchen converge jenkins-slave-create-centos-73
Expected Result:
In the case of my test cookbook, I was expecting Chef Client to complete its run successfully. In the case of the jenkins_slave_create test cases, I was expecting the cookbook to converge correctly and for Test Kitchen to run the verifier.
Actual Result:
This is the error message I got from trying to run the jenkins_slave_create test suite:
================================================================================
Error executing action `create` on resource 'jenkins_jnlp_slave[builder]'
================================================================================

RuntimeError
------------
can't modify frozen #<Class:#<Chef::Resource::JenkinsJnlpSlave:0x00000004bb4d48>>

Resource Declaration:
---------------------
# In /tmp/kitchen/cache/cookbooks/jenkins_slave/recipes/create_jnlp.rb

   10: jenkins_jnlp_slave 'builder' do
   11:   description  'A generic slave builder'
   12:   remote_fs    '/tmp/jenkins/slaves/builder'
   13:   service_name 'jenkins-slave-builder'
   14:   labels       %w(builder linux)
   15:   user         'jenkins-builder'
   16:   group        'jenkins-builder'
   17: end
   18:

Compiled Resource:
------------------
# Declared in /tmp/kitchen/cache/cookbooks/jenkins_slave/recipes/create_jnlp.rb:10:in `from_file'

jenkins_jnlp_slave("builder") do
   action [:create]
   default_guard_interpreter :default
   declared_type :jenkins_jnlp_slave
   cookbook_name "jenkins_slave"
   recipe_name "create_jnlp"
   description "A generic slave builder"
   remote_fs "/tmp/jenkins/slaves/builder"
   service_name "jenkins-slave-builder"
   labels ["builder", "linux"]
   user "jenkins-builder"
   group "jenkins-builder"
   slave_name "builder"
end

System Info:
------------
chef_version=13.0.118
platform=centos
platform_version=7.3.1611
ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
program_name=chef-client worker: ppid=3797;start=17:23:59;
executable=/opt/chef/bin/chef-client

Recipe: jenkins::_master_war
* runit_service[jenkins] action restart (up to date)

Running handlers:
[2017-05-12T17:28:59+00:00] ERROR: Running exception handlers
[2017-05-12T17:28:59+00:00] ERROR: Running exception handlers
Running handlers complete
[2017-05-12T17:28:59+00:00] ERROR: Exception handlers complete
[2017-05-12T17:28:59+00:00] ERROR: Exception handlers complete
Chef Client failed. 74 resources updated in 05 minutes 00 seconds
[2017-05-12T17:28:59+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
[2017-05-12T17:28:59+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
[2017-05-12T17:28:59+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2017-05-12T17:28:59+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2017-05-12T17:28:59+00:00] ERROR: can't modify frozen #<Class:#<Chef::Resource::JenkinsJnlpSlave:0x00000004bb4d48>>
[2017-05-12T17:28:59+00:00] ERROR: can't modify frozen #<Class:#<Chef::Resource::JenkinsJnlpSlave:0x00000004bb4d48>>
[2017-05-12T17:28:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[2017-05-12T17:28:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Misc.:
I observed in https://github.com/chef-cookbooks/jenkins/issues/537 that the CI testing for this repo omits the aforementioned test suites.
I'm happy to provide additional information / testing if needed.

At someone's suggestion, I did some more cogitation / testing and I came to the following conclusion:
Pinning Chef Client to 12.19.36, this resource ran with no trouble. With that in mind and given that Chef 13 was released very recently and introduces a number of breaking changes, this resource (and possibly others) are broken in Chef 13. I happened to encounter this because my Chef-generated .kitchen.yml does not pin the Chef Client version. That said, if something breaks, test-kitchen is the best place for that to happen :smile:.
I also realize I neglected to include my chef-stacktrace.out file when I created this issue. It can be found here.

+1

I am also encountering this problem since upgrading to Chef 13, but going to back to Chef 12.x isn't an option for us at this point. Has anyone been able to make any progress in isolating the cause of this?

This has been fixed on master and I'll be cutting a release once I fix a few other problems


[ffmpeg] Build error on x64-linux

vcpkg install ffmpeg[all]

error: mfx-dispatch is only supported on '!linux & !uwp & !osx'

When compiling ffmpeg on the Linux platform, will qsv be supported?
Are there any plans to support qsv?

Because the dependency mfx-dispatch only supports Windows, it will be difficult to implement unless upstream starts supporting other platforms: https://github.com/lu-zero/mfx_dispatch?tab=readme-ov-file#windows

@lu-zero Hello, are there any plans to support Linux?

In theory you may rely on https://github.com/intel/libvpl nowadays.

@MonicaLiu0311 Hi, do you have any ideas? Is it possible to support the use of libvpl?

@MonicaLiu0311 Hi, do you have any ideas? Is it possible to support the use of libvpl?

@MonicaLiu0311 Please let me know if there is any progress, thanks!

https://github.com/microsoft/vcpkg/issues/29489
Can we remove mfx-dispatch dependency?

#29489 Can we remove mfx-dispatch dependency?

https://github.com/FFmpeg/FFmpeg/blob/n7.0.2/configure#L3274
https://github.com/FFmpeg/FFmpeg/blob/n7.0.2/configure#L6895-L6899
libmfx is a dependency of feature qsv. Feature is optional and you can choose not to install qsv.

@MonicaLiu0311
If qsv is not selected, how to use the hardware acceleration of Intel GPU?
The issus is that we want to be able to use qsv hardware acceleration on Linux.
Why is jellyfin-ffmpeg able to use qsv on Linux?

Because the dependency mfx-dispatch only supports Windows, it will be difficult to implement unless upstream starts supporting other platforms: https://github.com/lu-zero/mfx_dispatch?tab=readme-ov-file#windows

This answer got 2 :+1:? But it doesn't make sense.
Upstream has Linux support: https://github.com/lu-zero/mfx_dispatch?tab=readme-ov-file#linux
But vcpkg port mfx-dispatch is limited to "!linux & !uwp & !osx"


test: Update kubeconfig path for recent change in E2E test run locations

What type of PR is this?
/kind test

What this PR does / why we need it:
Updates kubeconfig path used by the e2e test Github Actions for recent changes in the cluster locations.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+21.5%) to 64.36%

Totals

Change from base Build<PHONE_NUMBER>:
21.5%

Covered Lines:
3794

Relevant Lines:
5895

💛  - Coveralls


OCSP is not supported

The Online Certificate Status Protocol is not supported. Why is that?

Major browsers also do not check that.
https://www.ssl.com/blogs/how-do-browsers-handle-revoked-ssl-tls-certificates/

I'm sorry but what's the alternative?
On Sun, Jan 8, 2023, 09:22 Yihong Wu @.***> wrote:

Major browsers also do not check that.
https://www.ssl.com/blogs/how-do-browsers-handle-revoked-ssl-tls-certificates/
—
Reply to this email directly, view it on GitHub
https://github.com/SoftEtherVPN/SoftEtherVPN/issues/1667#issuecomment-1374848197,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZ52AVVNLYABDIGIZL6FZTWRLEQZANCNFSM6AAAAAAQ2IWYQE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@domosekai https://www.ssl.com/blogs/how-do-browsers-handle-revoked-ssl-tls-certificates/#:~:text=Unlike Chrome%2C Firefox’s default settings also query OCSP responders to confirm the validity of SSL/TLS certificates. (You can change this setting in Firefox’s security preferences.)
Firefox does support OCSP. Chrome has its own proprietary CRL.
You can do OCSP or CRL or both. But doing none is unacceptable from the security standpoint.

pull request #1775   solves this. The right approach is to delegate AAA (Authentication, Authorization, Audit) to a radius server. FreeRADIUS can obviously do OCSP.
@domosekai Thank you and this ticket should be closed.


Save previous property value

I have an entity:
use Doctrine\Common\Collections\ArrayCollection;

private $aliases;

public function __construct()
{
    $this->aliases = new ArrayCollection();
}

public function getAliases() : ArrayCollection
{
    return $this->aliases;
}

I hydrate the entity as follows:
$brand = $hydrator->hydrate(\App\Entity\Brand::class, $request->getParsedBody());

And... the following error (incorrect behaviour):
var_dump($brand->getAliases()); // returns array...

I fixed this problem, now it works as follows::
var_dump($brand->getAliases()); // returns ArrayCollection...

Is the project still supported?

@fenric sorry I'm away on holiday until next week, I can have a look and merge it then.

please study my code...
https://github.com/autorusltd/doctrine-bridge/blob/01696f8379888d6b475a75f3b4347cf9fc18d16c/src/ArrayHydrator.php
you can reject this PR... and consider switching to setters and adders...

Hi @fenric, making this change will likely be a breaking change for existing users. You're proposing that to-many relationship properties should be merged with any existing values, whereas the existing functionality replaces them entirely.
I'm happy to keep this PR open for a while to see if anyone else who uses this package has an opinion. Alternatively I would accept a PR that leaves the replacing-to-many-values functionality as it is but adds a flag to enable merging-to-many-values.


Code completion on overides not offering suggestions

See e.g: https://dartpad.dartlang.org/f4e41229e2c16df41a5b8edc74c03437
Code completion on the 'd' should offer to override 'doSomething' but doesn't.
This would be very helpful when attempting to find the method to override in visitor patterns.

I have an implementation of this that is 90% complete, but there was some issue in the communication between server and client that prevented it from working.

Possibly this is done? @pq https://github.com/flutter/flutter-intellij/issues/1110

Yep.  This is done on the server side. Thanks!


⚠ AGEG website (prod) has degraded performance

In c71d498, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 1630 ms

Resolved: AGEG website (prod) performance has improved in a58a425.


Message.hs:Use explicit function instead of typeclass foo

Hello,
When trying to build this with newer upstream libraries (cabal with --allow-newer flag), I get the following error:
src/Cardano/Shell/NodeIPC/Message.hs:35:65: error:
    • No instance for (ConvertText BSLC.ByteString GHC.Base.String)
        arising from a use of ‘toS’
    • In the second argument of ‘(<>)’, namely ‘toS blob’
      In the expression: "Failed to decode given blob: " <> toS blob
      In an equation for ‘P.show’:
          P.show (DecodeFail blob)
            = "Failed to decode given blob: " <> toS blob
   |
35 |     show (DecodeFail blob) = "Failed to decode given blob: " <> toS blob
   |                                                                 ^^^^^^^^

A fix for a similar error was suggested in Cardano-Prelude by @erikd (see link).
However, the exact same fix doesn't apply.

@Heinrich-CH The only reason you are seeing this error is because you are using the --allow-newer cabal flag.

Fixed (and compiled the rest of the code) by downgrading protolude  from 0.3.0 to 0.2.4.
Leaving this bug open in case there are plans to upgrade the protolude dependency or add an explicit constraint.

Stop using the --allow-newer flag and this problem disappears.
Using --allow-newer is a user error.


Add SimpleTest Snippet

Matthew Tift put this SimpleTest config together after a day of struggles. Let's get this added to the handbook. Woot woot!

test this please

test this please

test this please


Unable to run tests using Nunit category expressions

See Nunit Category Expression section for more info: https://nunit.org/docs/2.5/consoleCommandLine.html
This may be more of a feature request, but I'm not really sure how to re-use test cases for multiplatform/multidevice type testing without using categories in this way. Currently we are unable to send tests to AppCenter (via VSTS AppCenter Test step) using Nunit category expressions, such as --include-category A+B . This covers the use case of if you have test cases that are of specific feature sets, and are to be run on specific devices.
As an example - if I have all tests that are set to be run on phone type devices marked with a category of "Phone", and a subset of those tests are marked with feature set category of "Docs", there is no way to run these tests via AppCenter without running all tests marked with either category. Currently sending category expressions via --include-category parameters is not supported via AppCenter, only multiple --include-category parameters. In practice, this would look like sending --include-category Phone --include category Docs , which would run both all of the Phone category tests, and all of the Docs category tests.
Some Nunit category expressions:
A+B+C
Selects only tests having all three of the categories assigned (scenario described above)
A+B-C
Selects tests with both A and B but not C.
A+(B|C)
Selects tests having both category A and either of B or C
etc.

As we do not have plans to add support for this feature in the next year, I'm closing the issue.


Fix or add an option to ff-dialog for dialogs containing a dropdown

Story
No response
Description
Currently, by default a ff-dropdown fill causes an ff-dialog to scroll, rather than pop-out.

FlowForge has been fixing this by manually overriding the overflow setting for dialogues containing just a dropdown, but a more universal fix; or a flag property to enable "no-scroll" should be added to ff-dialog.
Example:

https://github.com/flowforge/flowforge/pull/1294
https://github.com/flowforge/flowforge/pull/1257

Also seen in the create stacks dialog, which usually scrolls.


Use nomkl to speed up tests

Pull Request Test Coverage Report for Build 280

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 70.541%

Files with Coverage Reduction
New Missed Lines
%

pyiron_vasp/_version.py
1
43.32%

pyiron_vasp/vasp.py
3
39.46%

Totals

Change from base Build 276:
0.0%

Covered Lines:
2179

Relevant Lines:
3089

💛  - Coveralls


Failed to migrate dataset from prod to int instance

Yuyi,
I was investigating why one of our WMCore testing templates was failing to go through, and I just noticed that the dataset from the production DBS instance has not been migrated to the int instance yet. Here is how I just checked:
>>> from dbs.apis.dbsClient import DbsApi
>>> dbsApi = DbsApi(url = 'https://cmsweb-testbed.cern.ch/dbs/int/global/DBSMigrate/')
>>> dbsUrl = 'https://cmsweb.cern.ch/dbs/prod/global/DBSReader'
>>> dataset = '/RelValZEE_14/CMSSW_11_1_0_pre4-110X_mcRun3_2021_realistic_v8-v1/GEN-SIM'
>>>
>>> migrateArgs = {'migration_url': dbsUrl, 'migration_input': dataset}
>>> dbsApi.submitMigration(migrateArgs)
{'migration_details': {'migration_status': 9, 'create_by': 'amaltaro', 'migration_url': 'https://cmsweb.cern.ch/dbs/prod/global/DBSReader', 'last_modified_by': 'amaltaro', 'creation_date':<PHONE_NUMBER>, 'retry_count': 3, 'migration_input': '/RelValZEE_14/CMSSW_11_1_0_pre4-110X_mcRun3_2021_realistic_v8-v1/GEN-SIM', 'migration_request_id': 210003, 'last_modification_date':<PHONE_NUMBER>}, 'migration_report': 'REQUEST ALREADY QUEUED. Migration terminally failed. '}
>>>

Could you please investigate what the issue is?
Can you please check whether any migration has actually worked since HG2002? I'm concerned with the removal of c-ares in this PR: https://github.com/cms-sw/cmsdist/pull/5438
FYI: @todor-ivanov

Thanks for tagging me here @amaltaro

Let me check.
Crab had problem with migration from prod to phys03 because a new data tier introduced in prod, but not  in phys03 yet.

The migration is done. Please check, Alan.
Let me know if any problems. Otherwise, Please close this tickent.

Thanks, Yuyi. Dataset is now available in testbed:
https://cmsweb-testbed.cern.ch/dbs/int/global/DBSReader/filesummaries?dataset=/RelValZEE_14/CMSSW_11_1_0_pre4-110X_mcRun3_2021_realistic_v8-v1/GEN-SIM
Closing the ticket!


support for definition in queryMsg / execMsg in schemas

When generating schemas from sylvia framework written contracts, the queryMsg (and execMsg) is a ref to a definition, this causes error in ts-codegen.
/Users/.../node_modules/wasm-ast-types/main/client/client.js:175
  var methods = (0, _utils.getMessageProperties)(queryMsg).map(function (jsonschema) {
                                                           ^

Example of the schema
"query": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "QueryMsg",
    "anyOf": [
      {
        "$ref": "#/definitions/InstallableQueryMsg"
      },
      {
        "$ref": "#/definitions/QueryMsg"
      }
    ],
    "definitions": {
      "InstallableQueryMsg": {
        "type": "string",
        "enum": []
      },
      "QueryMsg": {
        "oneOf": [
          { ...}

full version: https://gist.github.com/whalelephant/957540ad83f8a35c05cd08fa7a009385#file-schema-json-L281

@pyramation I believe that this is an issue with parsing the entry-point messages here:
https://github.com/CosmWasm/ts-codegen/blob/10c8be3191cc16e89df92030662227e267c2df34/packages/ts-codegen/src/utils/schemas.ts#L73-L102
We should be collapsing the schema first to find them.

should be fixed!
Successfully published:
 -<EMAIL_ADDRESS>


Add Hg Summary data elements to Export Endpoint

Add Hg Summary data elements to Export Endpoint for both Official and Workspace views

Test Case: TC1160

HG Sum Official

HG Sum Workspace

Test Passed


Remove TODO from TTT Readme

Please update readme to remove todo in this section:
https://github.com/microsoft/aitour-ai-apps-with-scalable-database/tree/main/train-the-trainer#todo

This has been updated.

Thank You!


Generated attribute takes first type on types list.

Consider the following jsonSchema:
  {
        "type" : "object",
        "properties" : {
            "foo" : {
                "type" : ["boolean", "string","number","integer"]
            }
        }
    }

In this case generated attribute foo will have as type Boolean:
package com.example;

import javax.annotation.Generated;

@Generated("jsonschema2pojo")
public class Example {

public Boolean foo;

}

I noticed that, if type is not specified in jsonSchema, foo takes the type Object:
  {
        "type" : "object",
        "properties" : {
            "foo" : {
            }
        }
    }

Result:
package com.example;

import javax.annotation.Generated;

@Generated("jsonschema2pojo")
public class Example {

public Object foo;

}

There's a way of having the last result (without changing the jsonSchema) when a list of types is passed ?

Maybe related to #676 ?

Yes, it's directly related and the answer will be the same

Often people use union types like: ["boolean", null], where the result is an optional value. In this case, it's obviously desirable to just take the first item. It would probably be better if use we use the following logic for union types:

Remove null values.
If one value remains, use this as the type; If multiple values remain, use Object as the type.

Logic of taking first type should be changed, as a user can pass ["null", "boolean"] and should have the same result


Bundle also the production dependencies

This bundles more of the dependencies and reduces the PR overload

This repo is currently not able to merge PRs anyway. Hence keeping it as is until that is fixed :/

This repo is currently not able to merge PRs anyway. Hence keeping it as is until that is fixed :/

it is, you just merged #650 today

This repo is currently not able to merge PRs anyway. Hence keeping it as is until that is fixed :/

it is, you just merged #650 today

hm ok that had a CI fail originally. Or I confused repos. Oops


Add RocketChat

Adds Rocket Chat
Project URL
https://github.com/RocketChat/Rocket.Chat.Electron
Category
Chat
Description
Free open source chat system for teams. An alternative to Slack that can also be self hosted.
Why it should be included to Awesome macOS open source applications  (optional)
Good open source projects including meteor server, electron apps and reactive-native apps.
Checklist

[x] Edit applications.json instead of README.md.
[x] Only one project/change is in this pull request
[x] Screenshots(s) added if any
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@aihowes Thank you! 👍


目前只支持英伟达的显卡吗

Search before asking

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

Description
No response
Documentation Links
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

兼容cuda的理论都可以吧～


[3.x] Mono: Replace distutils function with shutil equivalent

Fixes #91154.
Tested locally, seems to still copy stuff fine.

Cherry-picked for 3.5.4.

Does the master branch not need a similar fix?

No, it's not using Mono and doesn't have this code anymore.


now that we have a base image, let's use it!

Here is the image, FYI: https://github.com/signalfx/splunk-otel-java/pkgs/container/splunk-otel-java%2Fprofiling-petclinic-base


support for swagger configuration options, especially security scheme and security/authorization

This feature request especially applies to the docker image that is tightly integrated with swaggerapi/swagger-ui
Since PostgREST auto-generates the OpenAPI specs, it needs a way to add options such as security scheme or security/authorization (which makes permissions visible with a lock icon - see https://swagger.io/docs/specification/authentication/).
This could be accomplished in the COMMENT which is already a supported feature. This way it would be stored in the database and survive dump/import.

This is the same feature request as https://github.com/PostgREST/postgrest/issues/1082#issuecomment-1178662247 right?
Let's follow up there. Laurence is checking the implementation now.


Bug 2058747: Update base-plugins.txt

Manual backport of #1416

/bugzilla refresh

installed plugins list from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_jenkins/1424/pull-ci-openshift-jenkins-openshift-3.11-images/1514279998775627776 for ART request @coreydaley
2022-04-13T16:38:57.856716213Z Installed plugins:
2022-04-13T16:38:57.864711933Z ace-editor:1.1
2022-04-13T16:38:57.871436356Z ant:1.11
2022-04-13T16:38:57.878129576Z apache-httpcomponents-client-4-api:4.5.13-1.0
2022-04-13T16:38:57.884968095Z authentication-tokens:1.4
2022-04-13T16:38:57.891355345Z blueocean-autofavorite:1.2.3
2022-04-13T16:38:57.898149233Z blueocean-bitbucket-pipeline:1.24.4
2022-04-13T16:38:57.904587760Z blueocean-commons:1.24.4
2022-04-13T16:38:57.910929880Z blueocean-config:1.24.4
2022-04-13T16:38:57.917333111Z blueocean-core-js:1.24.4
2022-04-13T16:38:57.924044555Z blueocean-dashboard:1.24.4
2022-04-13T16:38:57.930840831Z blueocean-display-url:2.2.0
2022-04-13T16:38:57.937329939Z blueocean-events:1.24.4
2022-04-13T16:38:57.943723220Z blueocean-github-pipeline:1.24.4
2022-04-13T16:38:57.950543743Z blueocean-git-pipeline:1.24.4
2022-04-13T16:38:57.957236192Z blueocean-i18n:1.24.4
2022-04-13T16:38:57.963885548Z blueocean:1.24.4
2022-04-13T16:38:57.970444204Z blueocean-jwt:1.24.4
2022-04-13T16:38:57.977514143Z blueocean-personalization:1.24.4
2022-04-13T16:38:57.984305408Z blueocean-pipeline-api-impl:1.24.4
2022-04-13T16:38:57.990847735Z blueocean-pipeline-editor:1.24.4
2022-04-13T16:38:57.997239638Z blueocean-pipeline-scm-api:1.24.4
2022-04-13T16:38:58.003614012Z blueocean-rest-impl:1.24.4
2022-04-13T16:38:58.010041962Z blueocean-rest:1.24.4
2022-04-13T16:38:58.016569837Z blueocean-web:1.24.4
2022-04-13T16:38:58.023035952Z bouncycastle-api:2.18
2022-04-13T16:38:58.029359435Z branch-api:2.7.0
2022-04-13T16:38:58.035864282Z caffeine-api:2.9.1-23.v51c4e2c879c8
2022-04-13T16:38:58.042837562Z cloudbees-bitbucket-branch-source:2.4.4
2022-04-13T16:38:58.049449799Z cloudbees-folder:6.16
2022-04-13T16:38:58.055983334Z conditional-buildstep:1.3.1
2022-04-13T16:38:58.062759814Z config-file-provider:3.7.1
2022-04-13T16:38:58.069466668Z configuration-as-code-groovy:1.1
2022-04-13T16:38:58.076337583Z configuration-as-code:1.51
2022-04-13T16:38:58.083313424Z credentials-binding:1.23
2022-04-13T16:38:58.089775862Z credentials:2.6.1
2022-04-13T16:38:58.096287029Z display-url-api:2.3.4
2022-04-13T16:38:58.102584353Z docker-commons:1.18
2022-04-13T16:38:58.109131614Z docker-workflow:1.23
2022-04-13T16:38:58.115804746Z durable-task:1.35
2022-04-13T16:38:58.122399071Z echarts-api:4.7.0-4
2022-04-13T16:38:58.129207120Z favorite:2.3.1
2022-04-13T16:38:58.135757247Z git-client:3.7.1
2022-04-13T16:38:58.142328602Z github-api:1.114.2
2022-04-13T16:38:58.148651293Z github-branch-source:2.6.0
2022-04-13T16:38:58.155222846Z github:1.33.1
2022-04-13T16:38:58.161815787Z git:4.7.2
2022-04-13T16:38:58.168271519Z git-server:1.10
2022-04-13T16:38:58.174976651Z google-oauth-plugin:1.0.0
2022-04-13T16:38:58.182031407Z groovy:2.2
2022-04-13T16:38:58.188986804Z handlebars:1.1
2022-04-13T16:38:58.195682857Z handy-uri-templates-2-api:2.1.6-1.0
2022-04-13T16:38:58.202325430Z htmlpublisher:1.21
2022-04-13T16:38:58.208836414Z jackson2-api:2.12.2
2022-04-13T16:38:58.215395143Z jenkins-design-language:1.24.4
2022-04-13T16:38:58.221942861Z jira:3.0.17
2022-04-13T16:38:58.228392611Z job-dsl:1.77
2022-04-13T16:38:58.234726627Z jquery3-api:3.5.1-1
2022-04-13T16:38:58.241595168Z jquery-detached:1.2.1
2022-04-13T16:38:58.247863994Z jsch:<IP_ADDRESS>
2022-04-13T16:38:58.254292032Z junit:1.30
2022-04-13T16:38:58.260862006Z kubernetes-client-api:4.13.3-1
2022-04-13T16:38:58.267857644Z kubernetes-credentials:0.8.0
2022-04-13T16:38:58.274629223Z kubernetes:1.29.7
2022-04-13T16:38:58.281468742Z lockable-resources:2.10
2022-04-13T16:38:58.288281558Z mailer:1.34
2022-04-13T16:38:58.294668512Z mapdb-api:<IP_ADDRESS>
2022-04-13T16:38:58.301431677Z matrix-auth:2.6.6
2022-04-13T16:38:58.307794644Z matrix-project:1.18
2022-04-13T16:38:58.314280967Z mercurial:2.12
2022-04-13T16:38:58.320754053Z metrics:<IP_ADDRESS>
2022-04-13T16:38:58.327081469Z momentjs:1.1
2022-04-13T16:38:58.333573545Z oauth-credentials:0.3
2022-04-13T16:38:58.340196736Z okhttp-api:<IP_ADDRESS>
2022-04-13T16:38:58.346550829Z openshift-client:1.0.35
2022-04-13T16:38:58.353064802Z openshift-login:1.0.26
2022-04-13T16:38:58.359412888Z openshift-pipeline:1.0.57
2022-04-13T16:38:58.366140966Z openshift-sync:1.0.46
2022-04-13T16:38:58.372842648Z pam-auth:1.6
2022-04-13T16:38:58.379790069Z parameterized-trigger:2.39
2022-04-13T16:38:58.386574580Z pipeline-build-step:2.16
2022-04-13T16:38:58.393136996Z pipeline-github-lib:1.0
2022-04-13T16:38:58.399437732Z pipeline-graph-analysis:1.10
2022-04-13T16:38:58.406028609Z pipeline-input-step:2.11
2022-04-13T16:38:58.412598302Z pipeline-milestone-step:1.3.1
2022-04-13T16:38:58.419394170Z pipeline-model-api:1.7.2
2022-04-13T16:38:58.425862146Z pipeline-model-declarative-agent:1.1.1
2022-04-13T16:38:58.432291445Z pipeline-model-definition:1.6.0
2022-04-13T16:38:58.438896138Z pipeline-model-extensions:1.7.2
2022-04-13T16:38:58.445384712Z pipeline-rest-api:2.15
2022-04-13T16:38:58.451971567Z pipeline-stage-step:2.3
2022-04-13T16:38:58.458297257Z pipeline-stage-tags-metadata:1.6.0
2022-04-13T16:38:58.464853106Z pipeline-stage-view:2.10
2022-04-13T16:38:58.471422097Z pipeline-utility-steps:2.12.0
2022-04-13T16:38:58.478587023Z plain-credentials:1.7
2022-04-13T16:38:58.485121150Z plugin-util-api:1.2.2
2022-04-13T16:38:58.491851368Z prometheus:2.0.10
2022-04-13T16:38:58.498108503Z pubsub-light:1.13
2022-04-13T16:38:58.504529289Z run-condition:0.10
2022-04-13T16:38:58.510904243Z scm-api:2.6.5
2022-04-13T16:38:58.517435134Z script-security:1.78
2022-04-13T16:38:58.524224059Z snakeyaml-api:1.29.1
2022-04-13T16:38:58.530638744Z sse-gateway:1.24
2022-04-13T16:38:58.537179959Z ssh-credentials:1.19
2022-04-13T16:38:58.543567498Z sshd:3.0.4
2022-04-13T16:38:58.549935816Z structs:308.v852b473a2b8c
2022-04-13T16:38:58.556123068Z subversion:2.15.1
2022-04-13T16:38:58.562488069Z token-macro:267.vcdaea6462991
2022-04-13T16:38:58.569293286Z trilead-api:1.0.13
2022-04-13T16:38:58.575857381Z variant:1.4
2022-04-13T16:38:58.582623913Z workflow-aggregator:2.6
2022-04-13T16:38:58.589286407Z workflow-api:2.47
2022-04-13T16:38:58.596264380Z workflow-basic-steps:2.18
2022-04-13T16:38:58.602861839Z workflow-cps-global-lib:564.ve62a_4eb_b_e039
2022-04-13T16:38:58.609494293Z workflow-cps:2660.vb_c0412dc4e6d
2022-04-13T16:38:58.615820961Z workflow-durable-task-step:2.35
2022-04-13T16:38:58.622158188Z workflow-job:2.41
2022-04-13T16:38:58.628726628Z workflow-multibranch:711.vdfef37cda_816
2022-04-13T16:38:58.635210062Z workflow-remote-loader:1.5
2022-04-13T16:38:58.641982150Z workflow-scm-step:2.13
2022-04-13T16:38:58.648526638Z workflow-step-api:622.vb_8e7c15b_c95a_
2022-04-13T16:38:58.654847503Z workflow-support:3.6

/approve

/lgtm

took a peek at the e2e failure at https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_jenkins/1424/pull-ci-openshift-jenkins-openshift-3.11-e2e-gcp-jenkins/1514279998683353088 @coreydaley
from what I see, jenkins came up without any issues with the plugins, but its attempts to access the openshift api server in the test env failed with socket timeouts
so IMO these are "environmental" issues
let's try a few retests to see if we can get "lucky" with the 3.11 gcp environment, but if need be, we'll see about overriding e2e-gcp-jenkins and merging this
and finally, with 3.11 about to be totally out of service, I at least don't think we go through the pain of working with test platform to "bolster" the env
And then we just wait for @jitendar-singh to verify the 3.11 level with the ART changes you'll request and circle back if need be, though again, the plugin startup from the log dumps looked good, and we have the positive 4.x results as well.
@adambkaplan @jitendar-singh FYI
/retest

Cool we got non constrained run @coreydaley !
Now you can just mimic the ART request like I did in the 4.6 PR so they update the plugin RPM for the official builds

ART request: https://issues.redhat.com/browse/ART-3975


KAFKA-3904: File descriptor leaking (Too many open files) for long ru…

…nning stream process
I noticed when my application was running for more than one day, I will get 'Too many open files' error.
I used 'lsof' to list all the file descriptors used by the process, it's over 32K, but most of them belongs to the .lock file, e.g. a single lock file shows 2700 times.
I looked at the code, I think the problem is in:
FileChannel channel = new RandomAccessFile(lockFile, "rw").getChannel();
Each time new RandomAccessFile is called, a new fd will be created.
Fix this by caching the FileChannels we created so far.

LGTM, alternatively you can use FileChannel.open as @ijuma suggests.

I have updated my PR to address all the comments, please take a look.

@HenryCaiHaiying I have a question about a potential race condition as I left on the previous discussion between you and @ijuma .

@guozhangwang replied to your comment

Actually, when I looked at the original problem again (file descriptors leaking), I realized my code didn't have the fix from the following checkin.  I don't think we need to introduce that map of channels, the following fix would be fine for now.
commit 996e29cfe8a9e5a45d4b778a84fb20479eeba469
Author: Greg Fodor<EMAIL_ADDRESS>Date:   Mon Apr 25 13:45:51 2016 -0700
KAFKA-3619: File handles are leaked on .lock files of ProcessorStateManager

@HenryCaiHaiying do you mean the whole PR is not necessary, or there are some code changes that are worth merging? If not please feel free to close this PR and the corresponding JIRA as "duplicate".

I think the fix in KAFKA-3619 should fix this problem too, I am closing this PR

@HenryCaiHaiying, the fix in KAFKA-3619 is not quite right, see KAFKA-3812. I think what was attempted in this PR may be needed for KAFKA-3812.


Directory that clearly exists not listing?

I recently quickly started a server with serve. When I open it up I get a nice directory listing as is to be expected:

But when I try to open the Testing/ folder, I get the following error:

It clearly exists, you can see it in the root directory listing. Below is the actual directory listing on my drive so it obviously exists there:

And all the other folders and files open/download perfectly fine. Any idea why this one is causing serve so much trouble?

@kognise Can you please check the permissions on your Testing directory.

@r0mflip Here's the GUI view. Do you want something more console-y or this ok?


fix(feed-item,feed-item-row): fix avatar alignment

DLT-1223 fix feed item avatar alignment

:hammer_and_wrench: Type Of Change

[x] Fix
[ ] Feature
[ ] Refactoring
[ ] Documentation

:pencil: Checklist

[x] I have reviewed my changes
[ ] I have added tests
[ ] I have added all relevant documentation
[x] I have validated components with a screen reader
[x] I have validated components keyboard navigation
[x] I have considered the performance impact of my change
[x] I have checked that my change did not significantly increase bundle size
[ ] I am exporting any new components or constants in the index.js in the component directory
[ ] I am exporting any new components or constants in the index.js in the root

:crystal_ball: Next Steps

:camera: Screenshots / GIFs
Before:

After:

Vue2 #1170


Update the Top bar to be aligned with the Side bar

I changed the left padding to 28px when navigation is not used and 12px padding for variant with navigation. Today we have a 48 px padding for the ghost button here. In his way the icon will line up with the icons in the side bar, and the title as well when no icon is used in the top bar.

I changed the left padding to 28px when navigation is not used and 12px padding for variant with navigation. Today we have a 48 px padding for the ghost button. In his way the icon will line up with the icons in the side bar, and the title as well, when no icon is used for the title section.


[fix][ml]fix OpAddEntry release error when exception in ManagedLedgerInterceptor

Motivation
There is a redundant releases in org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl#beforeAddEntry at line:853.
It will cause the error log as follows when there is an exception in ManagedLedgerInterceptor#beforeAddEntry.
 2022-09-01T16:07:04,851 - ERROR - [test-OrderedScheduler-1-0:SafeRunnable@38] - Unexpected throwable caught
io.netty.util.IllegalReferenceCountException: refCnt: 0, decrement: 1
	at io.netty.util.internal.ReferenceCountUpdater.toLiveRealRefCnt(ReferenceCountUpdater.java:83) ~[netty-common-4.1.77.Final.jar:4.1.77.Final]
	at io.netty.util.internal.ReferenceCountUpdater.release(ReferenceCountUpdater.java:147) ~[netty-common-4.1.77.Final.jar:4.1.77.Final]
	at io.netty.buffer.AbstractReferenceCountedByteBuf.release(AbstractReferenceCountedByteBuf.java:101) ~[netty-buffer-4.1.77.Final.jar:4.1.77.Final]
	at io.netty.util.ReferenceCountUtil.release(ReferenceCountUtil.java:90) ~[netty-common-4.1.77.Final.jar:4.1.77.Final]
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.beforeAddEntry(ManagedLedgerImpl.java:854) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.internalAsyncAddEntry(ManagedLedgerImpl.java:774) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.lambda$asyncAddEntry$4(ManagedLedgerImpl.java:769) ~[classes/:?]
	at org.apache.bookkeeper.mledger.util.SafeRun$1.safeRun(SafeRun.java:32) ~[classes/:?]
	at org.apache.bookkeeper.common.util.SafeRunnable.run(SafeRunnable.java:36) ~[bookkeeper-common-4.15.0.jar:4.15.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.77.Final.jar:4.1.77.Final]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]

Modifications

Remove duplicate release in ManagedLedgerInterceptor

Verifying this change

[x]  Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[x] doc-not-needed

@Jason918 @HQebupt @codelipenghui @Technoboy- @AnonHxy  PTAL

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@codelipenghui @Technoboy- PTAL, thanks in advance.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

It looks like we got many conflicts when cherry-picking it to branch-2.9.
Would you mind pushing a PR to branch-2.9? (To avoid cherry-picking involving bugs)

It looks like we got many conflicts when cherry-picking it to branch-2.9. Would you mind pushing a PR to branch-2.9? (To avoid cherry-picking involving bugs)

Sorry, I miss the message. PTAL https://github.com/apache/pulsar/pull/17928 @mattisonchao


Org syntax not supported

I am trying this plugin, but seems the org syntax highlighter is not supported
markdown:
highlight with ==highlight==

In org syntax highlight is defined as:
highlight with ^^highlight^^

Would be great to add support for org syntax. Thanks!

Could you try the latest version?

Sorry, still not work.


Take a long time until "Processing audio with duration ..." log

If call two model.transcribe simultaneously, it takes 5 mins to see 'Processing audio with duration ...' log.
If call one, it takes 2~3s.
[2023-05-23 09:00:56,877] INFO in app: 3bFMKBD42YI.webm, device: cuda
[2023-05-23 09:00:59,289] INFO in app: 4UQh0M7jjOo.webm, device: cuda
[2023-05-23 09:06:06,576] INFO in transcribe: Processing audio with duration 11:13.506
[2023-05-23 09:06:08,217] INFO in transcribe: Processing audio with duration 15:06.344

[2023-05-23 04:36:54,805] INFO in app: 9JpiQ-tnSQU.webm, device: cuda
[2023-05-23 04:36:56,817] INFO in transcribe: Processing audio with duration 01:50.283

What transcription options are you using?

WhisperModel('medium', device="cuda", compute_type="float16", local_files_only=True)

model.transcribe(media_file, word_timestamps=True, beam_size=5)

Between the call to model.transcribe and the log "Processing ...", only the function decode_audio is executed. So I tried decoding the files in separate threads but the decoding time is expected:
import threading
import time

from faster_whisper import decode_audio

s = time.time()
decode_audio("3bFMKBD42YI.webm")
e = time.time()
print(e-s, "time for 3bFMKBD42YI")

s = time.time()
decode_audio("4UQh0M7jjOo.webm")
e = time.time()
print(e-s, "time for 4UQh0M7jjOo")

t1 = threading.Thread(target=decode_audio, args=["3bFMKBD42YI.webm"])
t2 = threading.Thread(target=decode_audio, args=["4UQh0M7jjOo.webm"])

s = time.time()
t1.start()
t2.start()

t1.join()
t2.join()
e = time.time()
print(e-s, "time for both")

2.271620988845825 time for 3bFMKBD42YI
3.12764573097229 time for 4UQh0M7jjOo
3.257882833480835 time for both

So you are not just calling model.transcribe but you are also creating a new model here. Try creating a single model instance, and then reuse it for every requests.

If share single model instance, it takes more time for 2 requests than non-sharing

[2023-05-24 04:19:48,070] INFO in app: of3_iV5q9Lo.webm, device: cuda
[2023-05-24 04:23:48,523] INFO in transcribe: Processing audio with duration 16:09.828
[2023-05-24 04:26:16,040] INFO in transcribe: Detected language 'ko' with probability 1.00

It seems to take a long time to init WhisperModel.

Hmm, I did a pip install upgrade for latest master commit, and now occassionally getting the same issue, stuck around 4 minutes on processing segment at 00:00.000. Happened on both GPU. Will try to move back to old versions to find out the commit that caused this.

num_workers seems not to be the cause.

I make AMI and use it for aws auto scaling.
In original instance, it does work well, but not new instance.

It seems to take a time to create WhisperModel instance.
[2023-06-01 17:18:00,382] INFO in app: of3_iV5q9Lo.webm, device: cuda
[2023-06-01 17:18:00,383] DEBUG in connectionpool: Starting new HTTPS connection (1): huggingface.co:443
[2023-06-01 17:18:00,623] DEBUG in connectionpool: https://huggingface.co:443 "GET /api/models/guillaumekln/faster-whisper-medium/revision/main HTTP/1.1" 200 1804
[2023-06-01 17:18:00,638] DEBUG in connectionpool: https://huggingface.co:443 "GET /api/models/guillaumekln/faster-whisper-medium/revision/main HTTP/1.1" 200 1804
[2023-06-01 17:24:06,260] WARNING in task: Task queue depth is 1
[2023-06-01 17:24:06,261] INFO in app: whisper model created!
[2023-06-01 17:24:06,261] INFO in app: whisper model created!

After clear huggingface cache, it takes a time after 'Processing audio' log.
[2023-06-01 17:49:36,349] INFO in app: whisper model created!
[2023-06-01 17:49:41,269] INFO in transcribe: Processing audio with duration 16:09.828
[2023-06-01 17:49:41,270] INFO in transcribe: Processing audio with duration 16:09.828
[2023-06-01 17:49:57,985] WARNING in task: Task queue depth is 3
[2023-06-01 17:49:58,134] WARNING in task: Task queue depth is 4
[2023-06-01 17:50:27,988] WARNING in task: Task queue depth is 5
[2023-06-01 17:50:28,154] WARNING in task: Task queue depth is 6
[2023-06-01 17:50:57,992] WARNING in task: Task queue depth is 7
[2023-06-01 17:50:58,161] WARNING in task: Task queue depth is 8
[2023-06-01 17:51:27,995] WARNING in task: Task queue depth is 9
[2023-06-01 17:51:28,183] WARNING in task: Task queue depth is 10
[2023-06-01 17:51:57,998] WARNING in task: Task queue depth is 11
[2023-06-01 17:51:58,194] WARNING in task: Task queue depth is 12
[2023-06-01 17:52:28,002] WARNING in task: Task queue depth is 13
[2023-06-01 17:52:28,220] WARNING in task: Task queue depth is 14
[2023-06-01 17:52:58,006] WARNING in task: Task queue depth is 15
[2023-06-01 17:52:58,245] WARNING in task: Task queue depth is 16
[2023-06-01 17:53:09,643] INFO in transcribe: Detected language 'ko' with probability 1.00
[2023-06-01 17:53:09,644] INFO in transcribe: Detected language 'ko' with probability 1.00
```[2023-06-01 17:49:36,349] INFO in app: whisper model created!
[2023-06-01 17:49:41,269] INFO in transcribe: Processing audio with duration 16:09.828
[2023-06-01 17:49:41,270] INFO in transcribe: Processing audio with duration 16:09.828
[2023-06-01 17:49:57,985] WARNING in task: Task queue depth is 3
[2023-06-01 17:49:58,134] WARNING in task: Task queue depth is 4
[2023-06-01 17:50:27,988] WARNING in task: Task queue depth is 5
[2023-06-01 17:50:28,154] WARNING in task: Task queue depth is 6
[2023-06-01 17:50:57,992] WARNING in task: Task queue depth is 7
[2023-06-01 17:50:58,161] WARNING in task: Task queue depth is 8
[2023-06-01 17:51:27,995] WARNING in task: Task queue depth is 9
[2023-06-01 17:51:28,183] WARNING in task: Task queue depth is 10
[2023-06-01 17:51:57,998] WARNING in task: Task queue depth is 11
[2023-06-01 17:51:58,194] WARNING in task: Task queue depth is 12
[2023-06-01 17:52:28,002] WARNING in task: Task queue depth is 13
[2023-06-01 17:52:28,220] WARNING in task: Task queue depth is 14
[2023-06-01 17:52:58,006] WARNING in task: Task queue depth is 15
[2023-06-01 17:52:58,245] WARNING in task: Task queue depth is 16
[2023-06-01 17:53:09,643] INFO in transcribe: Detected language 'ko' with probability 1.00
[2023-06-01 17:53:09,644] INFO in transcribe: Detected language 'ko' with probability 1.00

In original instance, it does work well, but not new instance.

What's the difference between the 2 instances?

They are same.

I have met the same problem, when i use multiprocess, and every process will init a model


2019.4.17f1 - Does not bake the navmesh when the object is completely flat.

Hello,
NavMesh component does not bake the navmesh when the object is completely flat. It does create the navmesh data but its Source Bounds is all 0.

Hi,
It seems to work just fine in my test. What do you do differently?

A NavMesh is not generated when the scale is negative, but the bounds are not zero. I haven't checked, but a negative scale might be clamped to zero at the moment when the geometry is rasterized by the NavMesh builder process.

Hmm, I tried with generic Unity plane on my project and it works. but not with this mesh.
Here is the mesh that does not generate the proper navmesh-
city_ground_b.zip

I'm sorry, I can't look at this mesh now.
Can it be that the mesh is somehow inverted? (i.e. its faces are visible only from inside the mesh) What happens if you flip the mesh up side down?

If I see the mesh from below, it wont show/render. I can try that side see
if navmesh gets created though
On Thu, Mar 4, 2021 at 4:49 AM Adrian Țurcanu<EMAIL_ADDRESS>wrote:

I'm sorry, I can't look at this mesh now.
Can it be that the mesh is somehow inverted? (i.e. its faces are visible
only from inside the mesh) What happens if you flip the mesh up side down?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Unity-Technologies/NavMeshComponents/issues/206#issuecomment-790593683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5BMUVK3SX26ZA7LYOBLJDTB56UBANCNFSM4YSUWMFQ
.

--
Jae Hyun Yoo
Twitter @fkkcloud

@turadr As you can see, it shows this white wire box as a viewport gizmo of NavMeshSurface.
NavMesh data is generated but does not display on the viewport. Gizmos is definitely on.


Deploy CS to Production & Start Monitoring Front Pages

Done! As of 12:40am ET on June 18, the system has been successfully monitoring several pages for 8 hours, and the scheduler is continuing to run several jobs every minute. I'll check in the morning to see if there are any job failures. Commit: 5c30f290444c654239484b8bba20551c0c573313


Fix issue #1175 and cater additional scenarios

The Issue(s)
As shared in issue#1175. The current code fails to restore nested properties and doesnot cater for scenairos like
unflattenObject({ 'a.b': 1, 'a.c': 2, d: 3 })
unflattenObject({ 'a.b': 'foo', d: 3 })

where either the same key is being refered more than once or the values are non numbers. More detials can be seen in this runkit shared in the issue as well.
An additional scenario which the code failed to handle was when the flat path reffered to particular indices in the arrays values against a key. For example.
unflattenObject({ 'a.b.0': 5, d: 3 })

should return something like {a:{b:[5]}, d: 3}. However, the code fails to compile.
Solution
I fixed the snippet to handle these scenarios along with some improvements. The updated code which passes all these tests can be seen in this runkit.
Modifications / Improvements
The previous code uses JSON.parse() to parse the manually built string into JSON and then merges it with the accumulator using Object.assign(). This happened for ever iteration of Array.prototype.reduce(). My code takes a slightly different approach of making the reference to the values as the next accumulator. This ways, I can directly mutate and nested objects without having to merge on each iteration. This arguably improves the performance fo the code.

@Chalarangelo updated code and tests are here.

Thanks @Chalarangelo !


converters: allow wrapping and passing self and fields

This allows to wrap converters into classes and pass them the instance that is being initialized and the field for which the value is converted.
Things open:

[ ] narrative docs in init.md
[ ] I'm not sure how to approach the typing side, since every attempt failed. I suspect due to a lack of Mypy plugin support. Can we somehow cheat our way here?

fixes #404, fixes #709 (and probably more)
It will enable #240 if anyone still cares about it.

Here are the changes for the next step.
We need to make Converter generic over the input and output types:
In = typing.TypeVar("In")
Out = typing.TypeVar("Out")

class Converter(typing.Generic[In, Out]):
    """
    Stores a converter callable.

    Allows for the wrapped converter to take additional arguments. The
    arguments are passed in the order they are documented.

    :param Callable converter: A callable that converts a value.
    :param bool takes_self: Pass the partially initialized instance that is
        being initialized as a positional argument. (default: `False`)
    :param bool takes_field: Pass the field definition (an `Attribute`) into
        the converter as a positional argument. (default: `False`)

    .. versionadded:: 24.1.0
    """

    __slots__ = (
        "converter",
        "takes_self",
        "takes_field",
        "_first_param_type",
        "_global_name",
    )

    @typing.overload
    def __init__(
        self,
        converter: typing.Callable[[In, AttrsInstance, typing.Any], Out],
        *,
        takes_self: typing.Literal[True] = ...,
        takes_field: typing.Literal[True] = ...,
    ) -> None: ...

    @typing.overload
    def __init__(
        self,
        converter: typing.Callable[[In, typing.Any], Out],
        *,
        takes_field: typing.Literal[True] = ...,
    ) -> None: ...

    @typing.overload
    def __init__(
        self,
        converter: typing.Callable[[In, AttrsInstance], Out],
        *,
        takes_self: typing.Literal[True] = ...,
    ) -> None: ...

    @typing.overload
    def __init__(self, converter: typing.Callable[[In], Out]) -> None: ...

    def __init__(self, converter, *, takes_self=False, takes_field=False):
        self.converter = converter
        self.takes_self = takes_self
        self.takes_field = takes_field

        self._first_param_type = _AnnotationExtractor(
            converter
        ).get_first_param_type()

Then, we change the type stubs for field to take:
converter: _ConverterType | Converter[Any, _T] | None = ...,

I don't think this matters much since Mypy patches it.
Optional additional step: we finally make attrs.Attribute generic at runtime. That will let us have better typing here (and is more correct in general).
Then, we implement support for this in the Mypy plugin. This should be pretty straightforward since Converter is nicely generic.

@Tinche thanks for fixing Mypy tests – is there anything else to do around them or is this the best we can do for now?


Add v15.6.0 nodejs version to node-versions

Tool name
nodejs
Tool license
MIT
Add or update?

[ ] Add
[X] Update

Desired version
15.6.0
Approximate size
No response
Brief description of tool
I would like to request that v15.6.0 is added to node-versions (it says to open an issue here).
We often get this error when setup-node runs and subsequently fails:
Attempting to download 15.6.0...
Not found in manifest. Falling back to download directly from Node
Acquiring 15.6.0 - x64 from https://nodejs.org/dist/v15.6.0/node-v15.6.0-linux-x64.tar.gz
aborted
Waiting 12 seconds before trying again
aborted
Waiting 12 seconds before trying again

URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
It should be added to https://github.com/actions/node-versions

Tool installation time in runtime
No response
Are you willing to submit a PR?
Yes

@hobbsh Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

Hi @hobbsh The required version 15.6.0 nodejs has EOL on  01 Jun 2021, at present the current default version of ubuntu 22 is 18 and default version of ubuntu 24 is 20. Hence the downgrade of version is not possible which will effect other customers.

@RaviAkshintala Thanks for your quick reply! What you explained is understandable, except why are major versions 6, 8, 10, 12, 13and14` all supported in node-versions?


Give the AMD module an id

What issue will this PR address?

@haoliu-amp, Unsure, but hoping it will solve the mismatched anonymous define errors that were reported with require-js. It's still unclear to me how to reproduce the issue.
This makes the module definition less anonymous. I looked into how libraries like jQuery work as AMD modules and this was the only notable difference.


MatButtonToggle not initialized properly in tests

What is the expected behavior?
MatButtonToggleGroup in a component should be fully initialized when launching Jasmine tests
What is the current behavior?
My component with a MatButtonToggleGroup is not initialized properly in Jasmine tests. Thus, I can not write a test to check that value is initialized properly
What are the steps to reproduce?
Clone this project, and run ng test.
The failing test is this one :  https://github.com/loriepisicchio/MatButtonToggleInitBug/blob/master/src/app/app.component.spec.ts#L43
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
    "@angular/animations": "^7.2.6",
    "@angular/cdk": "^7.3.3",
    "@angular/common": "~7.2.0",
    "@angular/compiler": "~7.2.0",
    "@angular/core": "~7.2.0",
    "@angular/forms": "~7.2.0",
    "@angular/material": "^7.3.3",
    "@angular/platform-browser": "~7.2.0",
    "@angular/platform-browser-dynamic": "~7.2.0",
    "typescript": "~3.2.2"

Is there anything else we should know?
I have tried to wait for async changes with fixture.whenStable, tried to run again the change detection, nut nothing fixes the issue.
When running app with ng serve, the MatButtonToggleGroup is initialized properly

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.

@josephperrott this was meant to be an actual bug report. The MatButtonToggleGroup should be properly initialized by material lib in order to do proper assertions in tests. Please have a look at the github project to reproduce.

Hey @loriepisicchio , did you find any solution for this? I'm having "Cannot read property 'isSelected' of undefined" error on the test (during cleanup) due to this and it seems that I cannot find any suitable solution. Thanks!

Nope, no real solution so far. I've changed my test to check the value of the property bound to the MatSelect instead of testing the control itself but it's not ideal...


Apply transparency to colored mesh

I am working to develop an AR app on HoloLens 2 using MRTK3 and Unity. The goal is to apply color to each vertex of a mesh and also apply transparency. I use Graphics Tools/Standard. However, I could apply color to the mesh's vertices, not transparency.
Is there any capability in MRTK to achieve this goal?

Hi @mnamvarcfd, thank you for reaching out. Is the issue the alpha value in your mesh's vertex colors isn't being applied? If so, do you have a mesh with vertex colors with alpha values I could test?
I tried with another Mesh in Graphics Tools that has vertex colors - but I think the alpha values are all 1.0:

The material setup to be transparent and display vertex colors:

Hi @Cameron-Micka
Yes, the problem is the transparency. However, I applied 0.1 for the alpha value.
For debuging purposes, I used a triangle and applied blue, red, and green colors to each vertex. For the material I am using the same material as you used (i.e. Graphics Tools/Standard), rendering mode: Transparent, and also, check the Vertex colors. The code I am using for debugging is as follows:
using UnityEngine;

public class MeshVisualizerDebug : MonoBehaviour
{
    [SerializeField] private Material debugMaterial;

    private Mesh mesh;
    private GameObject meshObj;

    private void Start()
    {
        // Initialize GameObject
        meshObj = new GameObject("DebugMeshObj");

        // Assign material
        Material material = debugMaterial;

        // Set up MeshFilter and MeshRenderer
        var meshFilter = meshObj.AddComponent<MeshFilter>();
        mesh = new Mesh();
        meshFilter.mesh = mesh;

        var renderer = meshObj.AddComponent<MeshRenderer>();
        renderer.material = material;

        // Directly define the mesh data
        Vector3[] vertices = new Vector3[]
        {
            new Vector3(0.0f, 0.0f, 0.0f),
            new Vector3(1.0f, 0.0f, 0.0f),
            new Vector3(0.0f, 1.0f, 0.0f)
        };

        int[] triangles = new int[]
        {
            0, 1, 2
        };

        Color[] colors = new Color[]
        {
            new Color(0.0f, 0.0f, 1.0f, 0.1f), // Blue with 0.1 alpha
            new Color(1.0f, 0.0f, 0.0f, 0.1f), // Red with 0.1 alpha
            new Color(0.0f, 1.0f, 0.0f, 0.1f)  // Green with 0.1 alpha
        };

        // Apply the mesh data
        ApplyMesh(vertices, triangles, colors);
    }

    private void ApplyMesh(Vector3[] vertices, int[] triangles, Color[] colors)
    {
        // Apply data to the mesh
        mesh.Clear();
        mesh.vertices = vertices;
        mesh.triangles = triangles;
        mesh.colors = colors;

        // Recalculate properties
        mesh.RecalculateBounds();
        mesh.RecalculateNormals();
    }
}

Thank you so much for the sample code @mnamvarcfd! I'll work on fixing this.

Hey @mnamvarcfd, I just tried your script and it looks like the alpha value of the vertex is coming though correctly:

Are you seeing a different behavior?

Hi @Cameron-Micka
Thanks for your response.
In the unity scene it is ok, but not on the HoloLens 2 device.
I read more about the shader parameters and I played with them. With the setting I did in the following picture it is working fine and I can see the transparency, but it is too sensitive to the amount of light in the physical space.

Ah gotcha, if it's too sensitive to the amount of light in the physical space - what happens if you bring the albedo color down a bit. For example, make it neutral grey (0.5, 0.5, 0.5, 1.0) rather than white?

If I use grey for albedo the color is changed compared to the white. However, the white value for albedo results in a more realistic color map.
BTW if you confirm the above setup is correct I go on that.

albedo: Grey

albedo: white

Your images look correct to me. But if you are unhappy with the result, I'd recommend experimenting with these material values:

Here are docs on those values: https://docs.unity3d.com/Manual/SL-Blend.html
You may be able to land on the blending result you desire!


Print quantity limitation and usage monitoring

Is your feature request related to a problem? Please describe.
There is currently no built-in functionality to limit the quantity of prints in the system, nor is there an option to display the number of already printed pictures in the gallery area. This lack of functionality can lead to challenges in managing print quantities and monitoring usage, particularly on high-volume printers.
Describe the solution you'd like
I propose the implementation of a feature that allows administrators to set limits on the number of prints available and provides an option to display the number of already printed pictures in the gallery area aimed at end users.
Describe alternatives you've considered
Bash script as proposed in https://github.com/photobooth-app/photobooth-app/discussions/294 but relying solely on external scripts is not a sustainable long-term approach
Additional context
In a high-volume printing environment, the lack of built-in functionality to limit print quantities and monitor usage can significantly impact efficiency and resource management. It is essential to address this gap to better serve users in managing their printing needs effectively.

While I would consider a print stats counter in the admin dashboard as kind of useful, I myself will not implement a limitation or display in the frontend. High volume printing could indicate a commercial/professional use for which you would need to implement the display to the user and limitation yourself.   I do not think the user would benefit from the display in the gallery anyways because he cannot use the information: If he runs in the limitation the user will just be frustrated. Just let them print...

I see your points.
Why would early users get away with many prints and later with no prints?
Could the option to use blocking time be a good alternative? If prints are limited to for example 1 per minute, the waste would be highly reduced.

Hello,
you can add this code into shareservice.py L48
max_prints = getattr(appconfig.share, 'maxprint', 0)         if max_prints > 0 and self._information_service._gather_printing_stats() >= max_prints:             self._sse_service.dispatch_event(                 SseEventFrontendNotification(                     color="info",                     message="Maximum number of impressions reached! Please try again later.",                     caption="Share Service Error",                 )             )             raise RuntimeError("Maximum number of impressions reached!")
and adding "maxprint": 300, into config.json in "share" section.
If someone can add a field into the admin form to edit maxprint.

Hello,
i push a feature : https://github.com/photobooth-app/photobooth-app/pull/332

It took some effort to get the code right, but it is implemented now.
Thx @loiczam !


Update some public API documentation.

Fully completes public API documentation, adding a lint to ensure this coverage is not lost in the future.

Codecov Report

Merging #107 (f4efda4) into dev (077c721) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head f4efda4 differs from pull request most recent head 724181e. Consider uploading reports for the commit 724181e to get more accurate results

@@           Coverage Diff           @@
##              dev     #107   +/-   ##
=======================================
  Coverage   94.87%   94.87%
=======================================
  Files          68       68
  Lines        9526     9526
=======================================
  Hits         9038     9038
  Misses        488      488

Impacted Files
Coverage Δ

src/lib.rs
100.00% <ø> (ø)

src/query/mod.rs
50.00% <ø> (ø)

src/registry/contains.rs
91.83% <ø> (ø)

src/system/mod.rs
0.00% <ø> (ø)

src/system/par.rs
0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add GET/POST Request support for temp change

Is it possible to change the temperature from GET/POST Request?

That's currently how Fermentrack updates the temperature mode - temperature changes are submitted via POST from forms within Fermentrack.
Do you mean that you want to change it from another app, outside Fermentrack (like an API)?
There isn't an API for doing this at the moment due to security constraints.

Ok...i'm waiting the API for add the integrati in my WebApp (BeerOK). I think i Will publish It on January 21
Thanks
Percoco Diego

From: John<EMAIL_ADDRESS>Sent: Sunday, September 27, 2020 3:39:31 PM
To: thorrak/fermentrack<EMAIL_ADDRESS>Cc: dxcoco2<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [thorrak/fermentrack] Add GET/POST Request support for temp change (#497)
That's currently how Fermentrack updates the temperature mode - temperature changes are submitted via POST from forms within Fermentrack.
Do you mean that you want to change it from another app, outside Fermentrack (like an API)?
There isn't an API for doing this at the moment due to security constraints.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/thorrak/fermentrack/issues/497#issuecomment-699636961, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE4NHVSWXWCBKURZEYWB5TTSH46BHANCNFSM4R3MKXVA.


Fix PR issues

Fix issues in following pull requests,

#548
#617
#631

Can you please resolve conflicts and send this PR again?

Closed to fix merge conflict


Add "css" to use within a property

RNCSS
`${props` =>
    props.user &&
    `
      width: 120px;
      color: #fff;
      margin-left: 10px;
      font: normal 15px/17px 'Robotoo';
    `}

import styled, {css} from 'styled-components/native'
${props` =>
    props.user &&
   css  `
      width: 120px;
      color: #fff;
      margin-left: 10px;
      font: normal 15px/17px 'Robotoo';
    `}

with css import, in vscode of o auto complete

I didn't understand, sorry. What is the feature?

https://styled-components.com/docs/api#css

Sorry but I don't see the point:
const complexMixin = props => `
  color: ${props.whiteColor ? 'white' : 'black'};
`

const StyledComp = styled.div`
  ${props => (props.complex ? complexMixin(props) : 'color: blue;')};
`

highlighting RNCSS syntax without adding {css}

highlighting styled-components syntax without adding {css}

vscode extension doesn't work without adding additional {css}

Does this work with your extension:
String`
  width: 120px;
`


Add how it works to README

Add information about how pytest-motor works to the README.

[ ] Explain that it downloads a a binary the first time it runs
[ ] Explain that it might take long the first run
[ ] Explain default binary download destination
[ ] Explain the fixture scope

Solved by #67


Using jQuery

I would like to use jQuery from node_modules. How do I include it in the project?
Thank you for your assistance.

If you're using ES6:
import $ from `jquery`

or ES5
var $ = require('jquery')

If you're wanting to put $ on window to make it globally accesible, see comments in https://github.com/vigetlabs/gulp-starter/issues/252


Fix subheading size.

Changes / Comments
Remove a redundant CSS class from a subheading element.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


support php version 8.0 or high such as major and minor updates

Oh thanks, I missed it!

Released as Laravel Eloquent Flag v5.3.1

Thanks 🌹


Rollover file logger

Add implementation of file logger that can into files rollover, time or size based

wip #92


Update iframe when url attribute changes

Thanks for the PR @fabianVeliz. It has been merged and will be released in the newer version.


[ANCHOR-175] Fix missing more_info URL JWT secret validation.

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Fix missing more_info URL JWT secret validation.
Why
Here is the original bug report:
If the developer does not configure secret.sep24.more_info_url.jwt_secret / SECRET_SEP24_MORE_INFO_URL_JWT_SECRET, requests to SEP-24’s GET /transaction(s) endpoints return 500 because the anchor platform cannot create the url tokens without the secret.
This makes the more info URL jwt secret a required environment variable. However, I suggest we make both the interactive url and more info url use the same jwt secret.
Known limitations
N/A

Reference Server Preview is available here:https://anchor-ref-pr764.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr764.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr764.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr764.previews.kube001.services.stellar-ops.com/


Snakemake Simplify Nodes

Snakemake Finish throws an error that it's missing Simplify Nodes input, but when I generate the snakemake graphic diagram, it doesn't include Simplify Nodes. Does this need to be included in the Snakemake Finish inputs anymore?

I reviewed Snakemake-maintenance.md and saw that nodes is a debugging tool. I made edits to the shell syntax in Snakemake-finish a while back, and did not also change the condition in build-kg2-snakemake.sh
    sed -i "/\        shell(config\['S3_CP_CMD'\] + ' {input.simplified_output_nodes_file_full}.gz s3:\/\/' + config\['S3_BUCKET'\])/d" ${CODE_DIR}/Snakefile-finish
So sed did not delete this line in Snakemake, causing the issue. It's fixed now, but this seems like a problem that can easily come up in the future.


Bug in proxy-cache plugin not returning age header

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
Kong Enterprise <IP_ADDRESS>
Current Behavior
I have the proxy-cache plugin running (with the response_headers parameters on default) and I do only get back x-cache-status and x-cache-key but not the age header.
By default it should return age and I don't specifically set those values and I also tried to force the age to true but that didn't make any difference.
I checked in both 3.5 (using Kong Gateway in docker) and <IP_ADDRESS> (using the Kong Gateway Operator in Kubernetes) and it was the same behaviour.
Expected Behavior
I expect a header to be present called age with a number indicating the seconds the request is "old".
Steps To Reproduce

add proxy-cache plugin to a route
run curl command with -v and inspect headers

Anything else?
This is my Kubernetes resource:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: my-cache-1min
  namespace: my-api-v4
config:
  cache_ttl: 60
  content_type:
    - text/plain
    - application/json
    - application/json; charset=utf-8
  request_method:
    - GET
    - HEAD
  response_code:
    - 200
  ignore_uri_case: true
  strategy: memory
plugin: proxy-cache

Hey @tobiasehlert!
Looking at the documentation for proxy-cache plugin you are missing some configuration parameters on the plugin. It seems that if you want the response to have the Age header you need to enable the following configuration:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: my-cache-1min
  namespace: my-api-v4
config:
  cache_ttl: 60
  content_type:
    - text/plain
    - application/json
    - application/json; charset=utf-8
  request_method:
    - GET
    - HEAD
  response_code:
    - 200
  ignore_uri_case: true
  strategy: memory
  reponse_headers:
    age: true
plugin: proxy-cache

Link to the plugin documentation: https://docs.konghq.com/hub/kong-inc/proxy-cache/
Hope this helps,
Joel

hi @joelact and thanks for your reply, but the issue doesn't lie in that.
When looking in the configuration of the plugin it says that the response_headers section is required, but it has the three components set to true already. So you actually don't need to specify all parameters since it should default to those default parameters when not being specified, except for one.. the config.strategy!
You could actually create the KongPlugin resource by only doing this:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: my-cache-1min
  namespace: my-api-v4
config:
  strategy: memory
plugin: proxy-cache

So yeah.. "required field" flag in the docs doesn't really apply to the KongPlugin part, since the admission webhook (kongplugins.validation.ingress-controller.konghq.com) doesn't actually validate those. Another parameter would be the config.cache_control that is required but has a default and in their own docs (basic example) don't include that either.
But this is not the issue in this case.. it's that the config.response_headers.age parameter is not respected.
Regards,
Tobias

@tobiasehlert just tested locally. You are right the Age header is not being returned.
I think the schema definition may be the problem. The header does not match the configuration header value.
I will try to submit a PR today with a possible fix so the Kong team can review it ASAP.