rails generate camaleon_cms:install fails

Forgot to add backtrace in previous message, sorry about that.
/home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/connection_adapters/connection_specification.rb:177:in `rescue in spec': Specified 'mysql2' for database adapter, but the gem is not loaded. Add `gem 'mysql2'` to your Gemfile (and ensure its version is at the minimum required by ActiveRecord). (Gem::LoadError)
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/connection_adapters/connection_specification.rb:174:in `spec'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/connection_handling.rb:50:in `establish_connection'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/railtie.rb:120:in `block (2 levels) in <class:Railtie>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/lazy_load_hooks.rb:38:in `instance_eval'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/lazy_load_hooks.rb:38:in `execute_hook'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/lazy_load_hooks.rb:45:in `block in run_load_hooks'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/lazy_load_hooks.rb:44:in `each'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/lazy_load_hooks.rb:44:in `run_load_hooks'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/base.rb:315:in `<module:ActiveRecord>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activerecord-4.2.4/lib/active_record/base.rb:26:in `<top (required)>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/camaleon_cms-0.2.1/config/initializers/active_record_extension.rb:32:in `<top (required)>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `load'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `block in load'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:in `load_dependency'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:268:in `load'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/engine.rb:652:in `block in load_config_initializer'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/activesupport-4.2.4/lib/active_support/notifications.rb:166:in `instrument'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/engine.rb:651:in `load_config_initializer'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/engine.rb:615:in `each'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/engine.rb:615:in `block in <class:Engine>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:30:in `instance_exec'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:30:in `run'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:55:in `block in run_initializers'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:226:in `block in tsort_each'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:348:in `block (2 levels) in each_strongly_connected_component'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:418:in `block (2 levels) in each_strongly_connected_component_from'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:427:in `each_strongly_connected_component_from'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:417:in `block in each_strongly_connected_component_from'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:44:in `each'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:44:in `tsort_each_child'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:411:in `call'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:411:in `each_strongly_connected_component_from'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:347:in `block in each_strongly_connected_component'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:345:in `each'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:345:in `call'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:345:in `each_strongly_connected_component'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:224:in `tsort_each'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/tsort.rb:205:in `tsort_each'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/initializable.rb:54:in `run_initializers'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/railties-4.2.4/lib/rails/application.rb:352:in `initialize!'
        from /home/ozgun/Workspace/cms_cameleon_project/config/environment.rb:5:in `<top (required)>'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:92:in `require'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:92:in `preload'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:143:in `serve'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:131:in `block in run'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:125:in `loop'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application.rb:125:in `run'
        from /home/ozgun/.rvm/gems/ruby-2.1.1@camaleon_cms/gems/spring-1.3.6/lib/spring/application/boot.rb:18:in `<top (required)>'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /home/ozgun/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from -e:1:in `<main>'

Gemfile is:
source 'https://rubygems.org'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '4.2.4'
# Use mysql as the database for Active Record
gem 'mysql2'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.1.0'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'therubyracer', platforms: :ruby

# Use jquery as the JavaScript library
gem 'jquery-rails'
# Turbolinks makes following links in your web application faster. Read more: https://github.com/rails/turbolinks
gem 'turbolinks'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.0'
# bundle exec rake doc:rails generates the API under doc/api.
gem 'sdoc', '~> 0.4.0', group: :doc

# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'

# Use Unicorn as the app server
# gem 'unicorn'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug'
end

group :development do
  # Access an IRB console on exception pages or by using <%= console %> in views
  gem 'web-console', '~> 2.0'

  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
end

gem 'camaleon_cms'

I found a fix:
change in your Gemfile
gem 'mysql2'
gem 'mysql2', '~> 0.3.13'

Thanks, that fixed it.


Incoherent pubkey type

I've found this while debugging swarm identify protocol. It seems that the pubkey is stored as a string if derived from priv key and it is a buffer if the pubkey is passed directly.
buffer -> https://github.com/diasdavid/js-peer-id/blob/master/src/index.js#L133-L135
string -> https://github.com/diasdavid/js-peer-id/blob/master/src/index.js#L163
I'm ok both, although I expected it to be a buffer (like it was before). @nginnever what is your input on this.

Aha so when we derive the ID from passing in a public key, I wasn't actually sure what the source of that public key was or how it would be formatted. In our tests we supply it with a string formatted public key (I might have changed this from a buffer?). So when creating an ID from a public key it will simply store the public key in whatever format you supply it.
So if our system will always supply deriving an ID from a public key as a buffer, then I should add a line to creating from a private key that will transform the string to a base64 buffer as well for consistency I suppose.
Keep in mind that if we do supply deriving an ID from a public with a buffer then we technically buffer a buffer on this line. It does come out with the same result but this line would probably not be needed.
Let me know what you think about the consistency and double buffering and if you want I will add a line to the private key function to make sure it stores a buffer of the public key for consistency.

Aha so when we derive the ID from passing in a public key, I wasn't actually sure what the source of that public key was or how it would be formatted. In our tests we supply it with a string formatted public key (I might have changed this from a buffer?). So when creating an ID from a public key it will simply store the public key in whatever format you supply it.

So if our system will always supply deriving an ID from a public key as a buffer, then I should add a line to creating from

Let's make it always a buffer by default then :)

Keep in mind that if we do supply deriving an ID from a public with a buffer then we technically buffer a buffer on this line. It does come out with the same result but this line would probably not be needed.

Same applies for the privateKey. It should be specified what is the input encoding format and what is the format that both keys are available. Also, to make this more obvious since it might lead to errors, let's get commented on top of the function signatures which types are they expecting in their args.

thank you for fixing this :)


update: ref -> reference

update: ref -> reference
Was it forgotten?
According to #1819

Good, changes are done

Thanks for your contribution @t-h2o :)


foreign_key_constraint changeset error

On the previous driver mysql, a changeset error is being returned when a foreign key constriant is detected...I'm however receiving a raised error here with %MyXQL.Error{mysql: %{code: 1032}}.
Is this properly handled? Or is foreign_key_constraint not working on changesets?

We have integration tests for this feature and the tests work as expected,
so there needs to be a bit more going on here. Can you please do a complete
report on the Ecto SQL project, including the versions and a way to
reproduce the error? Thank you!
José Valim
www.plataformatec.com.br
Founder and Director of R&D

Closing this for now. Let's continue on https://github.com/elixir-ecto/ecto_sql/ with a new report whenever you want. :)

The error is ER_KEY_NOT_FOUND:
$ perror 1032
MySQL error code MY-001032 (ER_KEY_NOT_FOUND): Can't find record in '%-.192s'

but we only handle ER_ROW_IS_REFERENCED_2 and ER_NO_REFERENCED_ROW_2 (https://github.com/elixir-ecto/ecto_sql/blob/v3.2.2/lib/ecto/adapters/myxql/connection.ex#L53).
We were not handling that error code on the previous adapter either (https://github.com/elixir-ecto/ecto_sql/blob/v3.1.6/lib/ecto/adapters/mysql/connection.ex#L66) so not sure how this worked for you before.
The fix is easy, we only need to add ER_KEY_NOT_FOUND to the list but we need a way to reproduce, if you can please open up an issue on ecto_sql as José mentioned.

I will open there. just gathering up information. aparently it seems even ecto_sql 3 also has the issue.


Switch golangci-lint to GitHub Actions

The official golangci-lint GitHub Action speeds up the linter through caching and adds helpful annotations of errors (example: https://github.com/LeviHarrison/prometheus/commit/1bb34da5a76977710f30b85398ac21708ed7b6f2).
The workflow file is force synced to Go repositories because Makefile.common now won't run golangci-lint in CircleCI. Because there isn't any centralized CircleCI config where a variable to skip linting could be specified, this is the cleanest way I could do it. I guess if we wanted to make it optional we could check if the workflow file is present when running the make target, similarly to how we check if yamllint is installed (just with the logic reversed).
Ref #8453, #8984
cc @roidelapluie

Note: the latest run wasn't as fast as I've claimed it should be because the cache is invalidated every 7 days.

Took a little bit of futzing with the Make, but I think this is the cleanest solution.

Thanks!


infra: add a pre-commit hook to maintain a top-level list of deployments

@jlstevens what do you think about that? It's a simple pre-commit hook that will keep updated a top-level YAML file with a list of all the deployments declared across the project files, to be consumed by some monitoring process.
I would not merge that until we think monitoring through anyway but I wanted to have a quick feedback on this from you :) Marking as draft.

Superseded by https://github.com/holoviz-topics/examples/pull/345


It doesn't disconnect new users

Hello enrico69,
i tried to use this incredible extension on the new 2.2.1 CE version but it doesn't disconnect the new users.
Can you check?
Thanks

Hi.
OK I am going to check.
Just a couple of simple questions: How did you installed it and did you follow instructions on the Readme?

I installed it on 2.2.0 by composer and then i had to do a setup:upgrade of course. Btw i can assure that before update to 2.2.1 it worked.

Ah! Do you have the last version of the module (1.3)?

Yes, can't you reproduce on your desk?

Some news?
I would to know if it's a version problem or only mine..
Thanks for patience

I installed it directly on a 2.2.1 CE and no problems.
I am going to try your procedure: install it on a 2.2.0 CE and upgrade to 2.2.1.

Ok thanks for your help.
I attached a screen where you can see that account is not active actually but however i can login anyway.
Maybe is a good idea unistall and reinstall module? How can i do it?

Question: is the module still active?

Yes, after bin/magento module:status

And when you are going in the store settings, the admin activation is still set to "yes"?

Could you try (if not already done) to set it to "No", reindex and clean cache. Then set it to "Yes", reindex and clean cache again?

I just tried, no way...
Do you think i should try to unistall and reinstall?

The concern is that there is currently no automatic uninstall script (it should come soon). If you do it, you will have some "dead" attributes in you database + the new ones.

I am currently cloning a 2.2.0.

Are there only 2 attributes? One for activation and one for email? I can delete them manually

Yes only those two.
And in the core_config table there should also be an attribute for the configuration (you should look here first).

Those elements need to be checked first:

Nothing... i tried and re-tried...
No errors anywhere, i can't understand :|

OK. So we are going to debug manually.
Using a debugger, put some breakpoints (or, if you don't have a debugger, put an old exit("I am here") ) in the following line :
https://github.com/enrico69/magento2-customer-activation/blob/master/Plugin/Create.php#L76
and
https://github.com/enrico69/magento2-customer-activation/blob/master/Plugin/Create.php#L79
And tell me what happens when you create a new user account.

Ok now i think what could be!
Reading your code i remembered that i have this plugin installed too
https://github.com/php-cuong/magento2-redirect-customer
In particulary the code here
https://github.com/php-cuong/magento2-redirect-customer/blob/master/Observer/CustomerLogin.php#L70
Maybe it has higher "priority" so when i log in with a new account it redirect me at custom page avoiding your redirect here!
https://github.com/enrico69/magento2-customer-activation/blob/master/Plugin/Create.php#L85
How can i set "priority"? Some nice advice?

This module is a horror show :dagger:  haha!
Let me explain:

first of all it uses an observer. In Magento 2, you have to use plugins as often as possible (in this case, you can) ;

then, even if you use an observer, you should NEVER put code that could short-circuit the others.  In this case, it prevents the execution of the code after, including some Magento logic. I understand why he did it, but it is clearly inapropriate.

exit() is not a function, it is a language construct. The parenthesis are useless if no parameter is given

using double equal to compare code is a security flaw

and, the most annonying: as far I know in Magento 2 you cannot prioritize observers, while you can do it with plugins. On top of that, as the observer of this developer is triggered before my afterExecute plugin, my code is never reached.

Sorry but I have currently no solution for this one...

Actually I have a solution : you can create a plugin in your project. This plugin would be similar to mine afterExecute one. It would look if the path is a redirect respond to the customer account (the default Magento behavior). If it is the case, you can redirect where you want. If not, do nothing.
I am going to ask the developer of the other module :p

Ok you are so clear and very kind. Thanks for explanations!
The last question is:
instead of create a new plugin can i simply add here
https://github.com/enrico69/magento2-customer-activation/blob/master/Plugin/Create.php#L88
an else with a banal redirect? If yes what are the right row of code?
These ones should be ok?
$resultRedirect = $this->resultRedirectFactory->create();
$resultRedirect->setPath('mypath');
$result = $resultRedirect;

It would work but would be a bad practice:

never edit third-party code : only override it
it would be reset by any update of my module (if you do it)

I am going to create my own module to do what your want. It is very simple and easy. I will let you know soon!


Make Python CI more stable

coverage: 47.934% (-0.02%) from 47.956% when pulling 4643e3df43e732a587b667003a333868a6bc6d23 on fix_python_ci_v2 into e5d4745cdc532bfa50d77eb675a2402de85ecbe6 on master.


WebpackOptionsValidationError, Unable to build

The command nuxt build fails throwing an error WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. on Heroku.
Stack trace:
nuxt:build Building... +0ms
[AXIOS] Base URL: https://now-staging.hl.com/ , Browser: https://now-staging.hl.com/
  nuxt:build App root: /Users/aslam/Work/hl-student-web +0ms
  nuxt:build Generating /Users/aslam/Work/hl-student-web/.nuxt files... +0ms
  nuxt:build Generating files... +5ms
  nuxt:build Generating routes... +17ms
  nuxt:build Building files... +26ms
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module.rules[2].use should be one of these:
   non-empty string | function | object { loader?, options?, query? } | function | [non-empty string | function | object { loader?, options?, query? }]
   Details:
    * configuration.module.rules[2].use should be a string.
    * configuration.module.rules[2].use should be an instance of function.
    * configuration.module.rules[2].use should be an object.
    * configuration.module.rules[2].use should be one of these:

Complete stacktrace: https://gist.github.com/aslam/b1e4bfb4a8c07ce158dd44ccaafdaea1
My package.json looks like this: https://gist.github.com/aslam/d14bf1efdfcec8a1dcbcce32ab3fd5d9
and nuxt.config.js: https://gist.github.com/aslam/35302868dbc9ab75ad6deae7e89f53cf
The build works locally. I have specified the node and npm versions to use in package.json so that the Heroku box also use the same versions as I am.
"node": "6.11.0",
"npm": "3.10.10",
"yarn": "0.27.5"

Excuse me, can you provide your nuxt.config.js?

@shirohana sure:
module.exports = {
  /*
  ** Router config
  */
  router: {
    middleware: ['namespace', 'check-auth']
  },
  /*
  ** Headers of the page
  */
  head: {
    title: 'HL Student - Web',
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: 'Nuxt.js project' }
    ],
    link: [
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' },
      { rel: 'stylesheet', href: 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700|Material+Icons' }
    ]
  },
  /*
  ** Customize the progress-bar color
  */
  loading: { color: '#3B8070' },
  /*
  ** Build configuration
  */
  build: {
    vendor: ['vuetify', 'vuelidate']
  },
  modules: [
    '@nuxtjs/pwa',
    '@nuxtjs/component-cache',
    ['@nuxtjs/axios', {
      baseURL: 'https://now-staging.hl.com/',
      credentials: false,
      requestInterceptor: function _reqInterceptor (config, { store }) {
        if (store.getters.accessToken) {
          config.headers.common['Authorization'] = 'Bearer ' + store.getters.accessToken
        }

        return config
      }
    }]
  ],
  plugins: [
    '~plugins/vuex-router-sync.js',
    '~plugins/vuetify.js',
    '~plugins/vuelidate.js',
    '~plugins/firebaseConfig.js'
  ],
  css: [
    { src: '~assets/style/app.styl', lang: 'styl' },
    { src: '~assets/style/typography.scss', lang: 'scss' }
  ]
}

Currently, I am able to do a local build via nuxt build successfully. However, this is still failing on Heroku.

In the webpack project they pointed me to configuration.module.rules[2].use[2].options is not an object.

Should be fixed with the last release, feel free to comment or reopen this issue if the bug persists.


Catch UNAVAILABLE exception when ComputationServer not ready

Mill always has logs at the beginning of running. It is because the ComputationServer pods usually take longer to get ready. This PR is to catch these errors and log at INFO level.

This change is

I tried to make the container init wait until the downstream servers are in READY status. (So far it wait until dependencies are RUNNING, which might not be READY). But it is hard to implement without third party library. And I think it is not a bad thing to start the init even when dependencies not ready.


Anonymous validators

Hi there,
is there chance that anonymous validators will be introduced?
I have dynamically generated form and each component has its own validations (basically it's array of paris - regexp pattern and error message).
It would be nice to be able to specify anonymous / custom validators during component rendering.
Now, in order to achive this scenario, I'm doing this:

    const patternValidator = function (values, value, pattern) {
        const regexp = new RegExp(pattern);
        return regexp.test(value);
    };
    times(20, i => {
        Formsy.addValidationRule(`pattern_${i}`, patternValidator);
    });

And form my perspective it's super ugly :)
Maybe I missed something and there is a better solution?

Maybe just use matchRegexp validation?

@Semigradsky each pattern has its own message.


Player 2 becoming player 1 in coop

Kind of problem with the global table of players
i think we ether need to make it so players are always in the same position in that table or expose some more stuff from state?

I know it's confusing, it's a table of human controller Player-entities that exist, dead or alive. I don't really want to touch the table too much though, a lot of old stuff might break.
In MP there are also PlayerGhosts and these may or may not coexist with their Player corpses. Some scripts may want to use the corpses and others may want ghosts instead. This probably needs some new interface, get_player(SLOT), get_ghost(SLOT), get_the_thing_currently_controlled_by(SLOT) or something.

i wanted to do it but can't find ghost entity anywhere in state, like which ghost correlates with which player slot. I guess i can get all ghost entities and check in there inventory which slot they belong

I finally added these functions in #193


cannot rename multiple keyword messages

Coder's rename method refactoring doesn't allow one to rename multiple keywords at the same time.

With the changes, you should be able to tab/shift tab between the keywords to rename the complete selector instead of just the initially selected keyword.


Typo

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Ah I see. Can the Edit this page link at the bottom be changed to point to the correct file?

Yup, right now it's not clear at all. Do you care to create an issue on this repo so that we can improve that?

So, there are a few things going on here. For 1.13.0, we could not parse all the info we needed from the upstream files, so we actually did have the static content in our own repo (and still do). So your PR was actually correct. However, there #1829 will remove that duplicated content. The good news, is the issue raised in your PR actually is fixed upstream so when #1829 goes in, the content will be fixed.
@joaofnfernandes I'm sorry you were not fully aware of the situation.


feat: added onDrop prop for UploadDropzone component

Added a prop onDrop for the <UploadDropzone /> component. Whenever the user selects or drops the file it will call the passed onDrop callback function.
Closes #805

I have updated docs and added changeset.

can you please merge this PR?

I am currently fixing our CI.
Seems like something broke in Node 20.13 which the runners seems to use since last night.
Will merge once everything's green 👍🏼

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo.
I am able to bundle it successfully and published it.
But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself. Hope that helps!

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Thanks for the quick reply, I didn't know about that PNPM could insert the dependency version.
I have just tried to bundle it in the dist folder. I was able to publish it and then installed it in another React app successfully. But I am not able to use it and getting below error.
Unhandled Runtime Error
Error: Cannot find module 'fs'

Call Stack
webpackEmptyContext
file:///home/growupanand/Development/repos/ConvoForm/apps/web/.next/static/chunks/app/(protectedPage)/forms/%5BformId%5D/page.js (18:10)
__require
<EMAIL_ADDRESS>(46:9)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_XMLHttpRequest
<EMAIL_ADDRESS>(15:21)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_xmlhttprequest
<EMAIL_ADDRESS>(109:5)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_polling
<EMAIL_ADDRESS>(58:26)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_transports
<EMAIL_ADDRESS>(42:13)

Would you kindly assist me with this as well? I would really appreciate it. And I have created an issue here for the discussion.

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Hey @juliusmarminge ,
In my project, I am trying to publish a internal package of turborepo. I am able to bundle it successfully and published it. But when I am trying to use it in another react app, I am facing below error. Can you please help me with that whenever you got some time?
╰─$ npm install @convoform/react                                                                                130 ↵
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Message here since I was not able to contact you on LinkedIn or Twitter 😅
https://github.com/growupanand/ConvoForm/commits/231-publish-react-hook-as-npm-package/

You cannot use workspace:* in published packages since the consumer won't have that workspace reference.
If you publish with pnpm it should replace the workspace:* with the proper version for you, but if you use npm you'll need to do it yourself.
If you don't wish to also publish the dependency, you'll have to bundle it into the @convoform/react dist
Hope that helps!

Thanks for the quick reply, I didn't know about that PNPM could insert the dependency version.
I have just tried to bundle it in the dist folder. I was able to publish it and then installed it in another React app successfully. But I am not able to use it and getting below error.
Unhandled Runtime Error
Error: Cannot find module 'fs'

Call Stack
webpackEmptyContext
file:///home/growupanand/Development/repos/ConvoForm/apps/web/.next/static/chunks/app/(protectedPage)/forms/%5BformId%5D/page.js (18:10)
__require
<EMAIL_ADDRESS>(46:9)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_XMLHttpRequest
<EMAIL_ADDRESS>(15:21)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_xmlhttprequest
<EMAIL_ADDRESS>(109:5)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_polling
<EMAIL_ADDRESS>(58:26)
__require2
(app-pages-browser)/../../packages/react/dist/index.js
require_transports
<EMAIL_ADDRESS>(42:13)

Would you kindly assist me with this as well? I would really appreciate it. And I have created an issue here for the discussion.

It is fixed.


[Python] Use BufferedLogger instead of logger to log in boot.go

Using logger directly may result in Null pointer exception like:
panic: runtime error: invalid memory address or nil pointer dereference

This PR uses BufferedLogger instance to log reliably.
Tried on Dataflow Runner:

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Thank you.
There are no python changes here. Are these precommits flaky? If yes, could we file a bug and de-flake those?

Yeah, YAML one looks flaky with an error starting the expansion service-

Python Unit Tests is flaky as well. It failed abruptly without any signs. Giving it another run

cc: @jrmccluskey

Could you please file issues for the flaky tests?

Done - https://github.com/apache/beam/issues/31269


Generate and review validation reports: marc.ucb_tind

Step 2: Generate reports [status: in progress --> ready for review]

[x] Generate validation reports (run validate_by_mapper DAG):
[x] Add a comment (in this issue) to the output URLs
[x] Download the validation reports locally; prepend the collection registry number to the filename
[x] Upload validation reports to the Rikolti Data Validation folder

Step 3: Review reports  [status: ready for review --> review in progress]

[x] Review sample collections validation reports; leave notes in the spreadsheet
[x] Quickly (and not very deeply) scan through other validation reports (to identify if any new metadata fields surface)
[x] Synthesize notes at the mapper level
[ ] Share an update (and surface any anomalies) during a weekly check-in (Mondays at 3:00pm)

Step 4: Have data validation issues? Address & resolve validation issues (synthesized mapper-level):

[x] Create a new issue (“Validation results: Rikolti mapper name“) and report/request CIC fixes & investigations. Assign to CIC.
[ ] Add a comment to link to the new “validation results” issue.
[ ] Add a “blocked/paused” label to this issue. Include a status note in this issue title (e,g., HOLD for CIC fixes; HOLD for code review; etc.)
[ ] Move this issue back to the “To Do” pile.

[Re-generate & re-review (repeat steps 2-3 above, as needed.]
Step 5: Have acceptable validation reports?

[ ] Move the valid (accepted) reports to the “VALID” folder in google drive.
[ ] Update the mapper progress spreadsheet; indicate that the mapper is accepted

validation results: https://github.com/orgs/ucldc/projects/2/views/2?pane=issue&itemId=86550467

Validated on 2024-11-13!


browsersync can be returned as promise

see title

@IamManchanda TY. Should i wait for @kball or merge?

I will wait for kev!

Hmm... after merging this finding browsersync is not working. Have verified it is related to the change to the server() function. Going to revert for now.

@kball Hey, sorry. I can see how this was premature / incomplete alteration.


🐞 - PrimitiveTextfield postfix/prefix input-props don't work with text-align: right

Which @taiga-ui/* package(s) are the source of the bug?
core
Please provide a link to a minimal reproduction of the bug
See description
Description
<tui-primitive-textfield
    postfix="things"
    prefix="$"
    [style.textAlign]="'right'"
    [value]="30"
>
    text-align: right;
</tui-primitive-textfield>

Angular version
any
Taiga UI version
2.39.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Link: https://github.com/Tinkoff/taiga-ui/issues/1193

@splincode thanks, i did not know that the same issue already exists.
I will close my issue.


Simplify _jacoco_offline_instrument.

resolve_command shouldn't be required here.

Thanks for the PR.
I have to admit, I don't understand when this should or should not be required. Can you add any links to documentation as to why you think it shouldn't be required?
Tests passing are a strong hint, but I'd like to find some documentation that could also guide us.

I think resolve_command is only useful if you pass the first string argument. Then, it can parse out of the $(location //some/tool) directives for you and return the requisite tools.

Travis is printing:
running test test_coverage_on
Test "test_coverage_on" successful (20 sec)

Thanks!


Remove try_from_dtos

Description of change
Remove try_from_dtos() since it's not needed anymore
Links to any relevant issues
Closes https://github.com/iotaledger/iota-sdk/issues/1713

Aren't these used in the bindings core?

Now not anymore :trollface:


Rework

This is a major refactoring of the TimeSlider with the aim to:

disentangle source
remove unused stuff
improve readability, examples, documentation

Major points
Concise naming of concepts
These naming conventions are employed in the code and documentation

TimeSlider - the timeslider object itself
Dataset - a set of records from the same source with parameters applied (like color)
Source - a dynamic source of records (either via AJAX or something else)
Record - a single record displayed on the timeslider either as a point or a range
Element - a DOM element

Static building of d3.timeslider.js
When a bundle is created, this is now done using Browserify that also bundles all dependencies (like d3)
Modularization
It is now possible to require d3.timeslider and its plugins.
Several changes in the API:
Sources must now conform to the new Source interface:
They must either be a function that supports the following parameters:

start, end, params, callback (two parameters records, paths)
or they must have a fetch method using the same parameters
or be null (in that case, statically supplied records will be used)

The coverageselected event is now called recordClicked
And the event detail object now has the following values:

start
end
dataset - the dataset ID
params - an optional hash. see below

Records are now different
Records are now either:

a single Date
an Array of one or two Dates and  optionally an additional parameters Object.

The parameters can be used for filtering and if it has an id or name, it is shown as a tooltip when hovering the record.
Example with all possible options:
var timeSlider = new TimeSlider(document.getElementById('d3_timeslider'), {
    // ... other options
    datasets: [{
        id: 'test',
        color: 'magenta',
        records: [
            // single Date object
            new Date("2012-01-03T12:00:00Z"),
            // single Date object within Array
            [ new Date("2012-01-02T12:00:00Z") ],
            // single Date object with parameters
            [ new Date("2012-01-03T12:00:00Z"), {someParam: 1234, id: "this will be shown as tooltip"}],
            // two Date objects
            [ new Date("2012-01-06T12:00:00Z"), new Date("2012-01-06T16:00:00Z")],
            // two Date objects with parameters
            [ new Date("2012-01-01T12:00:00Z"), new Date("2012-01-01T16:00:00Z"), {testParam: false, name: "this will also be shown as tooltip"} ],
        ]
    }],
    // ...
});

Record filtering
Occurrences of geographic bounding boxes have been removed. Instead a global function can be installed via timeslider.setRecordFilter(filterFunc). The filter function is called for each record upon drawing and shall return a boolean value, indicating whether it is shown fully (true) or hollow (false). This can be used to make bounding box checks using the bounding box from the records parameters.
Example:
var timeSlider = new TimeSlider(document.getElementById('timeSlider'), {
    // ... other options
    datasets: [{
        id: 'test',
        color: 'red',
        records: null,
        source: { fetch: function(start, end, params, callback) {
            callback([
                [ new Date("2012-01-01T12:00:00Z"), new Date("2012-01-01T16:00:00Z"), {visible: false} ],
                [ new Date("2012-01-02T12:00:00Z"), {visible: true}],
                [ new Date("2012-01-03T12:00:00Z"), {visible: false}],
                new Date("2012-01-03T12:00:00Z"),
                [ new Date("2012-01-05T00:00:00Z"), new Date("2012-01-06T00:00:00Z"), {visible: false}],
                [ new Date("2012-01-06T12:00:00Z"), new Date("2012-01-06T16:00:00Z")],
            ]);
        }}
    }],

    recordFilter: function(record, dataset) {
        var params = record[2];
        if (params && params.hasOwnProperty("visible")) {
            return params.visible;
        }
        return true;
    }
});

Seems like some nice changes of necessary things that needed to be done, i did not know that this was critical right now. For now i would mark this as [WIP] as not all functionality has been ported and merging could break multiple dependencies. Merging this would mean a release number bump i guess.
I still have not enough experience with browserify but i strongly disencourage from building d3 into the timeslider library unless browserify can disentangle and understand build dependencies and separate them into their core components requiring this in another project which uses d3 would mean integrating d3 twice. I have seen in other projects building the dependencies into one separate file, i guess this would also be a possibility.

Yes, you are right it is still WiP. Until all previous functionalities are ported this will nit be merged. I give a preview of the changes as basis for further diacussion.
Regarding the second part of your remarks: the lib will be able to be used in two ways:

as a standalone bundle built with browserify (this includes d3) and is meant as starting point to add a timeslider to your page without hassling with dependencies.
as a library that can be required by client code. In this case, the dependencies will be installed when using npm install and bundled however the client lib wants it. I'm using webpack in another project and dependency resolution worka fine. (In special cases, like when two libs require different versions of a single dependency, you have to make shims manually)
Is this more clear now?

Now WMS and WPS (EOxServer: "getTimeData" process) sources are implemented and working again.
I consider this PR complete, but please check if thats the case for everyone.

I introduced in a not to clean way the visualization of line plots in the time slider and it was probably overlooked, i guess this should be also considered for porting and should probably be separated more cleanly, maybe as  specific process or similar, would need to look closer into the new refactoring to see what would be the best way.
In any case i considered that we specifiy specific releases in projects that depend on the timeslider so i guess we can play around with a major release now even if not all functionality is there.
It would probably make sense to change how we do the releases as i think that we use a somewhat outdated approach in the timeslider library.

@santilland The line datasets should now work again. Please check your integrations so that we can close this PR.


tmp: old (healthy) rebase for #671

/test integration-servicemesh

/retest integration-servicemesh


Duplicate upstream config in KongIngress CRD

Below are duplicated items in yaml:
https://github.com/Kong/kubernetes-ingress-controller/blob/922ae26bd00bbde2977d565f3ee5cb482019301a/deploy/manifests/custom-types.yaml#L145
https://github.com/Kong/kubernetes-ingress-controller/blob/922ae26bd00bbde2977d565f3ee5cb482019301a/deploy/manifests/custom-types.yaml#L191
I'm tracking KIC CRDs in my repo and my yamllint checker picked it up.

Indeed, thanks for the issue.
It seems like this has been fixed in the master branch since then:
https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/manifests/base/custom-types.yaml
Does that solve your problem?

Hi @hbagdi,
Yeah I see its fixed in master.
In my case, when I using KIC 0.5.0 I've taken CRDs from your tagged version 0.5.0 and locally removed redundant duplicate upstream.


Model will not be uploaded unstar.

Please remove this repo as you have no intention to deliver on your promise. Thanks.
-The owner said they aren't releasing the model, no need to check up on the repo.

There seem to be some connections to other similar projects on github, like HeSer (head swapper)
Same thing there, no code or models...

It was evident from the beginning that this would happen, I have removed the star and obviously I am disappointed, anyway this technology is advancing faster and faster and after seeing what is possible to do with Stable Diffusion probably better things will come out soon.

Ok.
Mobile faceswap is working quite good.
I made minor changes to it:
Rescale, crop output, keep audio...
Maybe they are not allowed to publish because model is trained using commercial data?
But nevertheless it's 'not amusing'...

Yes, but there are also things about the paper that don't fit me too well in terms of "reliability" so they probably don't have such an effective model and if they do, it is not in our interests if it is not going to be published.


Downsampling downsamples downsampled points

All historical data gets downsampled down to just 1 point.

Closed by #268


Properly handle Slack commands

This PR moves processing logic for Slack commands into services/slack-_command_handler.go
Callers will invoke services.BuildSlackCommand() to get a SlackCommand object.
When .Execute() is called on this object, the appropriate action will be taken.

Closed pending @cored refactor


wip amara env vars

This was a WIP I was working on friday but couldn't finish.
We need the amara credentials setup to run in staging, this is not finished up but its half way done so someone can pick this up

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   56.06%   56.06%
=======================================
  Files           7        7
  Lines         346      346
=======================================
  Hits          194      194
  Misses        143      143
  Partials        9        9

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 8c2b64a...aa2312c. Read the comment docs.


Migrations should force run on master

What steps will reproduce the problem?
Configuration with replications:
'db' => [
	'class' => yii\db\Connection::className(),
	'dsn' => 'mysql:host=<IP_ADDRESS>;port=3306;dbname=kit',
	'username' => 'vagrant',
	'password' => 'vagrant',
	'slaveConfig' => [
		'username' => 'vagrant',
		'password' => 'vagrant',
	],
	'slaves' => [
		['dsn' => 'mysql:host=<IP_ADDRESS>;port=3306;dbname=kit']
	]
]

create a migration, for example:
$this->createTable($this->tb_name, [
    'id' => $this->primaryKey(),
    'status' => $this->smallInteger(1)->notNull()->defaultValue(0),
    'identity' => $this->smallInteger(1)->notNull(),
    'is_online' => $this->smallInteger(1)->notNull()->defaultValue(0),
    'register_at' => $9this->integer()->notNull(),
    'phone' => $this->string(11)->notNull()->unique(),
]);

$this->createIndex('idx_phone', $this->tb_name, 'phone');

What is the expected result?
The migration will run successfully.
What do you get instead?
There is an error occured.
Additional info
After create table, It will fetch the schema information, and it will connect to slave to fetch that.
but the replication it not performed.
We can disable slave to resolve this problem?
Just set Connection::$enableSlaves = false when execute the migrations. Or some else suggestion?
Thanks.

Q
A

Yii version
2.0.9?

PHP version
7.0.1

Operating system
centos

Disabling slaves by default makes sense.


Persistent settings across documents?

Is there a way to save a user token across documents, so the user can stay signed in when using the add-in of an Office app (PowerPoint in my case) across more than one file?

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

ID: b683480b-a4fe-97ba-64f9-45ecfe829bf4
Version Independent ID: a0993174-18dd-9594-9c3c-102d078e2217
Content: Persisting add-in state and settings - Office Add-ins
Content Source: docs/develop/persisting-add-in-state-and-settings.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@Rick-Kirkham do you happen to know on this one? Thanks!

For the most part, an add-in lives in a universe where there's only one Office document: the one that's open. So, I'm not sure what you mean by using an add-in "across more than one file". If a user opens your add-in in a document, then closes the document and opens another one, (s)he has to relaunch the add-in.
There is a preview Single Sign-on system (that shouldn't yet be used in a production add-in). Basically, your add-in could get a token of the current user logged into Office by calling the getAccessToken method. You could design the add-in to call this when the add-in launches. Each time the add-in is launched in a different document, the token would be fetched again. But it would not be stored anywhere in between.
This is more a programming question, than a problem with the article, so I'm going to close this, but you can still add comments and we'll see them.

Thank you @Rick-Kirkham. I brought this issue up, because my draft PowerPoint add-in was rejected because of this SSO issue. My add-in gives access to a slide template database, but the PowerPoint Javascript API has only 1 function at the moment: create a new presentation. So whenever a user picks a slide for download, I need to serve it as a new presentation in a new Window or browser tab. I will link to this discussion, and hopefully Microsoft will approve my add-in because on my end, I cannot do much about this behaviour.
Lifting the SSO option out of preview would be great, and even better: exposing an API method that allows you to add a single slide to an existing presentation.


[Communication] - All - Added powershell docs to readme

/azp run java - communication - tests

/azp run java - communication - tests


Order of filters seems to matter to raw

I'm trying to use the raw filter to allow HTML through (when I have autoescape on).
This works correctly: {{ topic.content|trim|raw}}
Doesn't work: {{ topic.content|raw|trim }} - This outputs the escaped HTML.
Interestingly none of these work either, so it doesn't seem that it's about the order necessarily.
{{ topic.content|raw|trim|nl2br }}
{{ topic.content|nl2br|trim|raw }}

Thanks for all your hard work on this library. I'm a huge fan of twig and it's nice to use this in the JS ecosystem.

Okay, seems this is related to the fact nl2br also performs escape. Protip, if you need to combine these things, do nl2br outside of your template and then just do {{ variable|raw }} to save yourself a headache.


[Snyk] Upgrade @mapbox/rehype-prism from 0.8.0 to 0.9.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @mapbox/rehype-prism from 0.8.0 to 0.9.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 6 months ago, on 2023-11-01.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Uncaught Exception SNYK-JS-YAML-5458867
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Open Redirect SNYK-JS-GOT-2932019
482/1000  Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit

Open Redirect SNYK-JS-GOT-2932019
482/1000  Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit

Regular Expression Denial of Service (ReDoS) SNYK-JS-HTTPCACHESEMANTICS-3248783
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

Prototype Pollution SNYK-JS-MINIMIST-2429795
482/1000  Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: @mapbox/rehype-prism

0.9.0 - 2023-11-010.9.0

0.8.0 - 2021-09-210.8.0

    from @mapbox/rehype-prism GitHub release notes

Commit messages

Package name: @mapbox/rehype-prism

6c19410 0.9.0
f2a335f prepare v0.9.0
4806b23 update dependencies
a0a7d5d Merge pull request #36 from mapbox/dependabot/npm_and_yarn/minimist-1.2.6
f197083 Bump minimist from 1.2.5 to 1.2.6

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

👷 Deploy Preview for boisterous-rugelach-efa48d processing.

Name
Link

🔨 Latest commit
1dc61d1a47be2a8239ee7abe8c2409076f823d4d

🔍 Latest deploy log
https://app.netlify.com/sites/boisterous-rugelach-efa48d/deploys/6623fa644c00d20008097cf6


Enhancements

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

Fixed: ArrayAccessTrait don't support set values as $object[]=42.
Minor refactoring ArrayableTrait::extractRootFields (faster by 5-6%).
Remove reset($args); in ArrayHelper::merge.
Remove array_unique in ArraySorter::getKeys (useless, we always get first element).
Add more tests.

reset($args); removed in ArrayHelper::merge because is useless. After run next methods $args is reseted. Example:
function x(...$x) {
    var_dump(current($x)); // 1
}
$a = [1,2];
end($a);
x(...$a);

👍


QUnit support

How can I use this construction in combination with a /app/tests folder and QUnit, just like ember does this with minispade?

Figures it was not that hard, though maybe nice to include in this great package!
See the sample here:
https://gist.github.com/1894905

I'll add tests today -- completely forgot about tests!

@devinus have you had time to add tests? because i took the sample of @ralfschimmel and implemented it in my fork. shall i open a pull request?

@pangratz I did start it, but I got distracted! I'll get back on that today and let you know as soon as it's pushed. It's almost exactly what @ralfschimmel did anyway, so if you've already copied his method you're pretty much good to go.

@devinus Great! Thanks. A pull request is not needed then I guess. Looking forward for your implementation.


Change module name to  github.com/kubernetes-sigs/go-open-service-broker-client/v2

The current mod file is：
module sigs.k8s.io/go-open-service-broker-client/v2

go 1.14

require k8s.io/klog/v2 v2.0.0

Thanks for reaching out, @mackwong . Are you experiencing a particular issue?
sigs.k8s.io is redirected appropriately, and seems to be working perfectly with the golang toolchain.


feat(presentation): add resolver APIs

This PR introduces two new APIs for resolving locations and documents. Both are optionally provided via the top level resolve plugin option.
resolve.locations
An improved Locations API which (soft) deprecates the locate option.
It accepts a DocumentLocationResolver as locate does, but also accepts a simplified object format which abstracts away observable logic, meaning users no longer need to wrangle with RxJS.
resolve.mainDocuments
Accepts an array of DocumentResolver objects, which contain a path pattern (using path-to-regexp) to match against the current previewUrl, and a method for resolving a document: a document type, groq filter, or resolver function.
Todo before merging

[x] Documentation

Docs are nearly there, so we can probably review this, hopefully it can land in the next release.


FIX: Minimal fix to AROMA metadata key

Testing nipreps/niworkflows#563 before merging.

Works, closing this PR without merge.


Checking chunk parameter length before unmarshalling

As discorvered by @melekes in #17 many parameters do not validate the length of the body matches the expected length as given by the header. This can lead to panics in the handling code.
This could be fixed by making a check in the build_param function.
A quick look suggests that this also is an issue for chunk unmarshalling. This is probably a pervasive issue in the codebase.

[x] Parameters have this issue. Fixable by checking size in src/param/mod.rs::build_param Edit: This is already checked in ParamHeader::unmarshal
[x] Chunks have this issue. Fixable by checking size in Packet::unmarshal Edit: This is already checked in ChunkHeader::unmarshal

After more investigation the original culprits seem to be None-issues because they were already checked, in an unexpected place.

Great! Thanks for looking into this 👍


bug: --about Could not append type because the JSON schema for the dictionary

Related to https://github.com/meltano/hub/issues/1671. This command prints the about json but it logs several warnings that it cant figure out the type. This is for one of the built in configs as part of faker_config.
tap-dataverse --about --format=json
Could not append type because the JSON schema for the dictionary {'oneOf': [{'type': ['number']}, {'type': ['string']}, {'type': ['boolean']}]} appears to be invalid.`

Closing as duplicate of https://github.com/meltano/sdk/issues/2226 😅
I guess I'll to give this 20 min to try fixing.

@edgarrmondragon oops I didnt find that one for some reason 😞

Addressed in https://github.com/meltano/sdk/releases/tag/v0.35.1


docs: add forking instructions + workflow + fix contributing notes

See individual commits.

Working from a fork will make it harder for contributors to rebase their PRs, no? Would that make sense instead to work on cilium/cilium but to add the fork as a distinct remote for pushing the changes?

Can you clarify which rebase scenario you think is harder? 🤔
As for using cilium/cilium and having the fork as a separate remote: I think this is a bad idea.
Not in the sense that you should not do it (if you do and it suits you, please continue :D), but in the sense that this is not standard practice. The usual way for people to work with forks/upstream on GitHub is to fork, then clone the fork, then setup the upstream as a remote (see doc).
I personally think the documentation is written specifically for not-so-Git-savvy peeps since Git aficionados will do whatever works best for them anyway no matter the documentation... hence my thinking that we should try to keep it standard ^^

Sneaky push to fix commit logs... (no #topys in there, I swear, don't need to look 😇)


Create recurrent build to always have latest patches/versions

Would be nice to have some scheduled action to routinely rebuild the images, staying always up-to-date with latest minors.

@rexdivakar well, this is embarrassing. Sorry I totally missed notification about this comment of yours, almost a year ago.
I have just accomplished the intention of this task - we added a schedule: 0 1 * * *  trigger on the Github Action that builds/pushes the images; this way we will always have an up-to-date version on Hub Docker.
Improvements still would be:

Only build if versions actually changed (Node/npm)

Cool no worries, appreciate the reply 😇


make deploy does not work on OSX

I've successfully compiled the unix binaries from the master branch on OSX, however, I was not able to compile the OSX application via make deploy. I previously had no problems doing this either with core or XT
make deploy
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C src qt/bitcoin-qt
  OBJCXXLD qt/bitcoin-qt
Undefined symbols for architecture x86_64:
  "_main", referenced from:
      start in crt1.10.6.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [qt/bitcoin-qt] Error 1
make: *** [src/qt/bitcoin-qt] Error 2

I'm on this now.

I don't have this problem.
OSX version 10.11.2 / Qt5
Are you using Qt4?

OSX Cert was just granted today. We will be using it to build QT-OSX

Working well for me https://s3.amazonaws.com/rromanchuk-public/Bitcoin+Classic.dmg

We stopped supporting the 0.11.2 branch, as such I'll close this report.


mypy complaining about is_categorical_dtype

Describe the bug
I've updated pandas-stubs from version 2.1.1 to 2.1.4 and now mypy is saying that pd.api.types.is_categorical_dtype doesn't exist. I found out that it was being imported in version 2.1.1, but not anymore in version 2.1.4.
To Reproduce

Run any code containing is_categorical_dtype
mypy will return the following error:

Please complete the following information:

OS: Linux
OS Version 20.04.6 LTS
python version 3.10.13
version of type checker: mypy 1.6.0
version of installed pandas-stubs: 2.1.1

Using is_categorical_dtype should trigger warnings since pandas 2.1. https://pandas.pydata.org/docs/dev/whatsnew/v2.1.0.html isinstance(obj.dtype, pd.CategoricalDtype) is the recommended way of testing if the type is categorical.

Oh, I see. Thank you very much!


Use berkshelf for chefspec

This will correctly set the cookbook_path so that it
does not rely on things on the dev machine.

+1 merge it

:+1:

foodcritic is still causing failures


Make dashboard load all latest data with one API call

/sensors-dense

Seems to work!
Station (42 requests on 1min auto refresh):

Devstation (2 requests on 1min auto refresh):


Project and Swagger-UI setup.

Project and Swagger-UI setup.

According to Dialyzer:

dialyzer: Analysis failed with error:
No .beam files to analyze (no --src specified?)

@cabol please make sure that both make dialyze and make test work. At least add xref_SUITE in your test folder


Getting "branch_name is missing" error when creating commit

Obviously the branch is provided:
commit = gitlab.create_commit(project.id, 'master', 'initial commit', [{action: 'create', file_path: '/index.html', content: "01"}])

/Users/inem/.rvm/gems/ruby-2.4.0/gems/gitlab-4.2.0/lib/gitlab/request.rb:80:in `validate': Server responded with code 400, message: branch_name is missing. Request URI: https://gitlab.com/api/v3/projects/4413953/repository/commits (Gitlab::Error::BadRequest)
        from /Users/inem/.rvm/gems/ruby-2.4.0/gems/gitlab-4.2.0/lib/gitlab/request.rb:49:in `post'
        from /Users/inem/.rvm/gems/ruby-2.4.0/gems/gitlab-4.2.0/lib/gitlab/client/commits.rb:143:in `create_commit'
        from 01.rb:78:in `<main>'

I added puts options.inspect inside Gitlab::Request#post, and it seem to work as expected:
{:body=>{:branch=>"master", :commit_message=>"initial commit", :actions=>[{:action=>"create", :file_path=>"/index.html", :content=>"01"}]}

Does this mean that GitLab's API have changed, and the gem doesn't follow it yet?

I've just tried it with the sample code from specs and got the same error: Server responded with code 400, message: branch_name is missing. Request URI: https://gitlab.com/api/v3/projects/4418686/repository/commits (Gitlab::Error::BadRequest)

Oh, figured it out finally! I forgot to specify v4 in endpoint. Closing this


Customize detail pages

Please describe the problem that your request should resolve.
Different entity data deserve different presentation
Describe the solution you'd like
Differentiate styles of detail pages to highlight each entity's properties.
A single style of table for every entity detail does not highlight different data importance and does not look visually repeating
In the same fashion, we may see among various explorers
Is it already possible to achieve the same outcome in any other way? If so, how?
Data are served just fine, we can do it better
Additional context

especially here

and wallet portfolio
and account detail
and tx detail
and contract detail


Catching up - home page and links

Awesome, this should make it easier for us for the time being, thank you,
God there must be a part of me that was just happy with typing in the urls all this time to not be bothered by it.... what does that say to you???


Vim command a incorrect behaviour

Lapce Version
0.2.0
System information
Ubuntu 22.04.1
Describe the bug
When a (the Append command) is pressed from Normal mode while the cursor is on an empty line, the cursor will move down to the next line.
Additional information
Not sure what could be causing this; in the source it seems like the cursor is only moved right, not up or down.

I opened a pull request ( #1219 ) with a fix for this


NMEA Messages on Android

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Adds ability to listen to NMEA messages on Android.
:memo: Links to relevant issues/docs
Closes #561, closes #605, closes #819
This builds upon #605 and #819 using the updated project structure. I understand that @mvanbeusekom is working on a different approach, but this may function as a workaround for now. Until this is merged, you will need to include this in your project's pubspec.yaml:
dependency_overrides:
  geolocator:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator
      ref: nmea
  geolocator_platform_interface:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator_platform_interface
      ref: nmea
  geolocator_android:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator_android
      ref: nmea

:thinking: Checklist before submitting

[x] I made sure all projects build.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I followed the style guide lines (code style guide).
[x] I updated the relevant documentation.
[x] I rebased onto current main.

I have tested this feature and it's working very well.
I think in pubspec.yaml should be:
dependency_overrides:
  geolocator:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator
      ref: nmea
  geolocator_platform_interface:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator_platform_interface
      ref: nmea
  geolocator_android:
    git:
      url: git://github.com/rickcasson/flutter-geolocator.git
      path: geolocator_android
      ref: nmea

Hi @mvanbeusekom, I'm not sure what your plans are with NMEA message streaming in this plugin, but I cleaned up this PR and brought it back up to date with the main branch in hopes in might get merged or helps your other development plans. Please let me know if there is anything else I can do to help!

Hey @mvanbeusekom, I brought this PR back in line with main and targeted the latest release of the baseflow_plugin_template to get around the deprecation errors, but wondering if you would like me to separate this into multiple PRs or if the internal dependency overrides can just be removed before this possibly gets merged?


[release-1.8] Add a bit more logging when a pod crashes in ci

This is an automated cherry-pick of #28177

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio_release-1.8
e369168836e0064942230758ca68029560bdeea0
link
/test integ-multicluster-k8s-tests_istio_release-1.8

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

/retest


CTRL + Shift + F Find should highlight all of the items as long as the search bar is open

When we press CTRL + Shift + F to find something on the console, the results aren't all highlighted, only one result at a time is highlighted, the rest should be cycled through manually.
I need this to change to be just like search in browsers. When you press CTRL + F in Edge and type something, all of the results are highlighted without the need to cycle through them.

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #7561 for more discussion.
/dup #7561

@zadjii-msft Thank you and sorry that I didn't find the duplicate issue.


Improve net.uri queries in pyvast-threatbus

:notebook_with_decorative_cover: Description
Substring queries in VAST are slow compared to point queries. Instead of using in to query for the concept net.uri, we use strict equality in case the indicator begins with a protocol identifier, and otherwise search for the indicator and the indicator prefixed with common prefixes like http:// or tcp:// instead.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/threatbus, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Run locally.

Closing; we can always re-open after we've had the meeting about cross-stack URI handling improvements.


Fix doFinally rx extension

Expected behavior
Underlying peripheral queue should execute all operations in sequential manner.
The issue
Peripheral queue is not executing operations sequentially when there are more than 2 operations enqueued.
Receiving side would get interleaving chunks for different incoming packets.
Reason
public func queue<O: GattOperation>(operation: O) -> Single<O.Element> returns sequence with injected side-effects utilizing internal state to manage/run operation queue in case there are more operations to be executed. doFinally rx extension was added to enqueue next operation when the current one finishes, however it's not implemented correctly.
Typical rx sequence lifecycle:
==...==completed==disposed=|
==...==error==disposed=|
Please note: subscription is disposed immediately after completed/error event occurs.
doFinally is called twice per single operation (e.g. completed, disposed) and due to side-effects utilizing internal state it skips freshly enqueued operation (which will still complete!) and moves to the next one.
Example:

Schedule 3 write operations
Write1 completes
doFinally is executed for Write1 because of the completed event so Write #2 is enqueued
doFinally is executed again for Write1 because subscription will be disposed so Write #3 will be enqueued
We are now sending packets both for Write2 and Write3 simultaneously

Added test to cover this behavior. Revert my change to doFinally to see test failing with previous logic: receiving side would get "Packet 1 containing dummy dataPackeP3t 2 containing slightly more dummy data than first packet" instead of "Packet 1 containing dummy dataPacket 2 containing slightly more dummy data than first packetP3"
Fix
Added variable to guard against multiple invocations.

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


400 API_ID_INVALID error

I've got here (https://my.telegram.org/apps) API_ID, API_HASH,  IP and port of DC I should use.
I set everything corectly, but anyway get 400 API_ID_INVALID error using TLRequestAuthSendCode.

Works with another AipId (obtained a long time ago). So it's Telegram's issue

for me, I removed ' ' of appID and it worked.😍💃


Quickpick separators come and go when scrolling

Testing #153344
Doesn't feel so much like a rendering glitch, but more like everytime the list is rendered, the separators are toggled on/off.

@joaomoreno hmm I can't seem to repro this on macOS... are you scrolling with arrow keys or mouse wheel?

Keys. Now that I see it again, maybe it is a rendering glitch...

rendering glitch makes the most sense... not sure if maybe @deepak1556 you have thoughts on this? How do we typically handle rendering glitches?

You still seeing this @joaomoreno?

Nope!


i2c enhance 1

感谢提交 Pull Requests！
Thanks for submitting a pull request.

Security Check : cf494a509228c14d9a329902af1b6d78d1ffcfdb

autotest fail,number:1797


SlotableV2 using shared state by leveraging procs (issue caused by #664)

Summary
After updating to version 2.28.0 our view components gem started to fail rendering. This was caused by #664
undefined method 'cell' for nil:NilClass
In this PR is simplified extraction of the code which shows the need for state that is passed on to the children that ran without issues before #664.
Other Information
We pass on the state of the parent component so our developers only need to set a boolean in a single place rather than to provide it on each row they add.
How can we still pass on certain state and still have the changes in #664?
@BlakeWilliams

@xtr3me Thanks for the report and the PR!
Would it be possible to update the components in the test to be a minimal reproduction of the issue?

Yes, what would you like to have removed? I could remove the rows and leave the header + cell. Is that enough?

What we could do is pass down the parent to it's children, for example:
class ViewComponent::Base
  attr_accessor :parent_component

  #...logic to set the parent_component after initializing the child component...
end

class TableComponent < ViewComponent::Base
  attr_accessor :selectable

  renders_one :header, HeaderComponent

  def initialize(selectable: selectable)
    @selectable = selectable
  end
end

class HeaderComponent < ViewComponent::Base
  delegate :selectable, to: :parent_component, allow_nil: true
end

@BlakeWilliams how would you feel about this potential solution? What are the drawbacks about this approach?

@xtr3me I'd like to avoid having to inject another parameter if possible.
Thank you for simplifying the test case! I took a peek this morning and I got the tests passing with this change:
diff --git a/test/app/components/nested_shared_state/table_component.rb b/test/app/components/nested_shared_state/table_component.rb
index c13e096..94b124d 100644
--- a/test/app/components/nested_shared_state/table_component.rb
+++ b/test/app/components/nested_shared_state/table_component.rb
@@ -9,9 +9,8 @@ module NestedSharedState
       header_system_arguments[:selectable] = @selectable

       header_component = NestedSharedState::HeaderComponent.new(**header_system_arguments)
-      render(header_component) do
-        block.call(header_component)
-      end
+
+      header_component
     end

     # @param selectable [Boolean] When enabled it allows the user to select rows using checkboxes

The two cases look similar but the difference is that render will return the string representation of the component instead of the component instance itself. That being said, both examples should work.
I got both working by making sure we pass arguments through to the block in the capture call:
diff --git a/lib/view_component/slotable_v2.rb b/lib/view_component/slotable_v2.rb
index e69772a..08f382c 100644
--- a/lib/view_component/slotable_v2.rb
+++ b/lib/view_component/slotable_v2.rb
@@ -227,7 +227,9 @@ module ViewComponent
         # current component. This is necessary to allow the lambda to access helper
         # methods like `content_tag` as well as parent component state.
         renderable_value = if block_given?
-          slot_definition[:renderable_function].bind(self).call(*args, **kwargs) { view_context.capture(&block) }
+          slot_definition[:renderable_function].bind(self).call(*args, **kwargs) do |*args|
+            view_context.capture { block.call(*args) }
+          end
         else
           slot_definition[:renderable_function].bind(self).call(*args, **kwargs)
         end

I think it would be worth testing that it works well with keyword args since it may need to be updated for that, but otherwise should make both cases work. If you have any interest incorporating that diff into your PR and testing out the keyword arg case that would be awesome, otherwise I can dedicate more time to this later.

@BlakeWilliams i'm super happy that you were able to take a peek and got it to work. I will update my PR tomorrow with your changes and add some tests to make sure arguments and keyword arguments work as expected.
I will also add an entry to the CHANGELOG.md so it will be easy to merge in.

@BlakeWilliams I have integrated your patch and added an additional fixes when supplying keyword arguments.
To be able to check these cases I added additional asserts in the tests.
Also the CHANGELOG.md is updated and I have added additional documentation about sharing data from the parent component whilst still being able to chain upon the returned component.
Let me know if there is anything else you would like to see changed.
Have a great weekend!

Hi @BlakeWilliams while i was implementing a component based on the result of this PR I came across the following weirdness:
The following bits are not captured in the cell content method:
<% row.cell(classes: "col-xs-1") do %>
   <%= 'Hi Blake' %>
<% end %>

#

But wrapping it in a capture block within the view of my program it is captured into the content:
<% row.cell(classes: "col-xs-1") do %>
  <% capture do %>
    <%= 'Hi Blake' %>
  <% end %>
<% end %>

#
Hi Blake

Without the ERB tag <%= %> it works fine:
<% row.cell(classes: "col-xs-1") do %>
  Hi Blake
<% end %>
#
Hi Blake

Would you be so kind to assist me with this and/or point me in the right direction so I can also squash bug as well?

@xtr3me thanks for implementing that patch and getting things working!
Since that issue seems to be related, can you create a failing test for it?

@BlakeWilliams I'm working on that, but it seems that Rails does some kind of hack to be able to use <%= on a block which isn't supported by ERB out of the box.
Currently I have:
template = ERB.new <<-EOF
  <%= controller.view_context.render(NestedSharedState::TableComponent.new(selectable: false)) do |table_card| %>
    <% table_card.header do |header| %>
      <% header.cell { 'Cell1' } %>
      <% header.cell(class_names: '-has-sort') do %>
        <%= 'Cell2' %>
      <% end %>
    <% end %>
  <% end %>
EOF
@rendered_component = template.result(binding)

assert_selector("div.table div.table__header div.table__cell", text: "Cell1")
assert_selector("div.table div.table__header div.table__cell.-has-sort", text: "Cell2")

# Check shared data through Proc
refute_selector("div.table div.table__header span", text: "Selectable")

But that crashes with:
SyntaxError: (erb):1: syntax error, unexpected ')'
...able: false)) do |table_card| ).to_s); _erbout.<< "\n

As it seems Rails does a workaround where it rewrites the ERB input to something that is valid for ERB to process.
Is there a way to render this for the test without the ERB workaround that i'm trying?

@xtr3me I think you could create a component with that erb as a template instead of trying to implement the ERB.new call in the test. That may help you work around it?

@BlakeWilliams that does work, but it doesn't trigger my issue. Since we also have a wrapper to lookup the component and render it I will investigate if that combination is the culprit:
def render_our_component(name, *args, **kwargs, &block)
  render(ComponentResolver.resolve(:internal, name).new(*args, **kwargs), &block)
end

@xtr3me Any updates on the other issue you are seeing?

@BlakeWilliams I didn't manage to create a minimal test case within the gem and didn't find enough time to make a sample app that I could share with you. Is it okay to come back on this early next week?
(we did experience the issue in different code bases where we use our gem that is based on ViewComponents.)

@xtr3me Totally, no rush!
Do you feel like this change is good to merge, or do you feel like you need to validate the other issue isn't related first?

@BlakeWilliams It would be super nice to merge this already, I will make sure a new issue is opened with reference to a repo that displays the additional issue.


Site not working

Describe the bug
When you open the site https://www.covid19india.org/, it does not open
To Reproduce
Steps to reproduce the behavior:

Go to https://www.covid19india.org/

Expected behavior
It should work, but the site is not loading.
Screenshots

Its all blank

Desktop (please complete the following information):

Macbook Air
Mojave
Chrome
80.0.3987.149

Smartphone (please complete the following information):
NA
Additional context
NA

It is working, It looks like it was on maintenance mode without any message


nvlddmkm.sys error caused blue screen everytime i update my gpu in device manager or try download from hp or nvidia

#nvlddmkm.sys error caused blue screen everytime i update my gpu in device manager or try download from hp or nvidia

Hi @jereytucker, I'm closing this issue as it is not documentation-related (this is a doc repo for Windows driver developers). I did a quick internet search and found a relevant article that might help you. Otherwise, I encourage you to reach out to NVIDIA's customer support. Hope you are able to resolve your issue quickly.


Create an entity-row as well

This card is very handy, indeed! However, it would be even greater if it was possible to integrate it in an Entities card, thus having these functions on an entity-row instead of a fully fledged card :)

@igorsantos07, I agree with you that integrating it with the entities card could have been better, but I don't think it's possible. AFAIK, it's only possible to extend Home Assistant frontend with new cards. But, I would be happy to learn that it's possible if you can point me to an example or documentation.

Done.
V1.2.0 supports embedding the component inside the Entities card.
Thanks!


create node references for custom fields

Adding the functionality to create node references for custom fields that contain a valid postID. It supports referencing either attachments or custom post types. References can be set on any post type, except on attachments (I didn't find a case where this would make sense, but this can be easily expanded).
Requires the customPostTypeReferences array to be defined in gridsome.config.js under the plugin settings
plugins: [{
    use: '@gridsome/source-wordpress',
    options: {
      baseUrl: 'https://example.com', // required
      apiBase: '?rest_route=/',
      typeName: 'WordPress',
      perPage: 100,
      concurrent: 10,
      routes: {
        post: '/:year/:month/:day/:slug',
        post_tag: '/tag/:slug'
      },
      customPostTypeReferences: [
        {
           type: 'attachment',
           sourceField: 'banner_image_id',
           targetField: 'bannerImage'
        },
        {
           type: 'car',
           sourceField: 'car_brand_id',
           targetField: 'carBrand'
        },
        ...
      ]
    }
}]

Example of a Query making use of a custom node reference:
query {
  allWordPressPost {
    edges {
      node {
        title
        bannerImage {
          id
    	  sourceUrl
          mediaDetails {
             width
          }
        }
      }
    }
  }
}

Thanks! The PR looks good. We have a refs option for the filesystem source plugin which is doing something similar to this. But our plan is to replace that option with something that can be used across all source plugins. But we are not sure how that configuration should look like yet.
My concern is if we should let each of our source plugins do this in their own way or if we can wait until we find a solution that works for all of them. Any feedback or ideas would be appreciated :)
It is also possible to do it with the new Schema API in Gridsome v0.7:
api.loadSource(({ addSchemaTypes }) => {
  addSchemaTypes(`
    type WordPressPost implements Node @infer {
      bannerImage: WordPressAttachment @proxy(from:"bannerImageId")
      carBrandId: WordPressCar
    }
  `)
})

@infer means that Gridsome will add fields that are not defined for the type
@proxy is a helper to use a value from another field on the node

I didn't know about the Schema API, I was still at 0.6.7 when writing this change. This looks nice!
One problem that I keep running into is that wordpress custom fields are strings and the id has to be cast to integer to create the reference. I see this happening with the @proxy as well, I didn't dive into the addSchemaTypes syntax yet to see if there's a way this could be overcome.
I understand your concern. Looking at the bigger picture it makes sense to standardise the way plugins extend this type of functionality. I'm more biased towards the approach that has all project specifics in the config file, so this direction that I took with my PR feels more at home for me.


Remove REST#query_users, REST#accept_invite

The query endpoint no longer exists.

The scope of this library is not aimed at user bots, so I'm not sure why the accept invite endpoint was included.

Bots can use the accept invite endpoint during the authorisation process with a bearer token, and while it's true that we don't support user bots, we do support user operations using OAuth2.

So some usage may be like the following?
client = Discord::Client.new token: "Bearer XYZ"
client.accept_invite("ABCdef")

You're right, that's acceptable then. I think I would at least like to expand the documentation a little to mention this.


Authentication token is missing or invalid

I used the following docker-compose to deploy the marketplace on the DMZ host.
# Copyright (c) Microsoft Corporation.
# Licensed under the MIT License
version: "3"
services:

  marketplace-db:
    container_name: marketplace-db
    image: openpai/marketplace-db:${TAG}
    restart: always
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: marketplace
      POSTGRES_DB: marketplace
    volumes:
      - ./postgres-data:/var/lib/postgresql/data

  marketplace-restserver:
    container_name: marketplace-restserver
    image: openpai/pai-marketplace-restserver:${TAG}
    restart: always
    depends_on:
      - marketplace-db
    environment:
      DB_USERNAME: user
      DATABASE: marketplace
      DB_PASSWORD: marketplace
      DB_HOST: marketplace-db
      DB_PORT: 5432
      PORT: 9293

  marketplace-webportal:
    container_name: marketplace-webportal
    image: openpai/pai-marketplace-webportal:${TAG}
    restart: always
    environment:
      MARKETPLACE_API_URL: https://my-domain/pai-marketplace/api

  marketplace-nginx:
    restart: always
    container_name: marketplace-nginx
    image: nginx
    volumes:
      - ./nginx/conf/conf.d:/etc/nginx/conf.d
      - ./nginx/conf/nginx.conf:/etc/nginx/nginx.conf
      - ./nginx/log:/var/log/nginx

TAG=v1.8.0, and the configuration of Nginx is shown below.
server {
    ...

    location /pai-marketplace/ {
        proxy_pass http://marketplace-webportal:9292/;
    }

    location /pai-marketplace/api/ {
        proxy_pass http://marketplace-restserver:9293/;
    }

    ...

}

Then I can access plugin.js and rest server API through the following link:
https://my-domain/pai-marketplace/plugin.js
https://my-domain/pai-marketplace/api/

Then I configured openpai as follows according to the document:
culster.common.marketplace=true

webportal:
  server-port: 9286
  marketplace: false
  save-template: true
  plugins:
  - id: marketplace
    title: Marketplace
    uri: https://my-domain/pai-marketplace/plugin.js

However, the browser prompts me with Internal Server Error.
From the browser's console, we can see that the following two links will encounter 500 Internal Server Error Error.
https://my-domain/pai-marketplace/api/categories
https://my-domain/pai-marketplace/api/items?type=all

When I visit the link directly, it prompts me Authentication token is missing or invalid.
Why does this issue occur? How to solve it?

There is indeed Authentication in the request header.


Terninal text blank because OOMkill kills GPU process

Apologies if this has already been reported, I have had a look through for similar things but couldn't find anything.
Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.63.2
OS Version: NixOS 21.11

Problem: When OOMkiller kills processes, sometimes the terminal text is blanked entirely. I can still type but can't see what I'm typing. Sometimes I can see how much text is already there but not what text it is.
I used to see some kind of message saying something like "It's slow to draw on the GPU, would you like to switch?" at which point I can do, but no longer see this kind of thing.
Thanks
Expected: text to not be blanked - so maybe code should either not have the gpu process as a separate task or detect the gpu process being killed and relaunch it?
Steps to Reproduce:

Have the terminal started
Search for "code --type=gpu-process" in the list of processes
Kill the process

Workaround:
Go to settings, look for Terminal › Integrated: Gpu Acceleration and change the value - canvas doesn't help but just changing to on and back to auto or off and back to auto fixes the terminal's text.

Can you check if issue repros with latest stable 1.73, the integrated terminal has gotten improvements since the report which might have addressed this issue.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

It hasn't happened in a little while but I think it could be related to missing letters in terminal or reproducible by OOM, so I'll make sure it's not gone.