[ Full Stack Cert ] - update all comprehension check questions for attributes lecture

We should update the current set of comprehension check questions for the attributes lecture.
Here are a clearer set of questions and answers that still align with the lecture video

# --questions--

## --text--

Which of the following is an example of a boolean attribute?

## --answers--

`src`

### --feedback--

Watch the last part of the video where common boolean attributes were discussed.

---

`href`

### --feedback--

Watch the last part of the video where common boolean attributes were discussed.

---

`disabled`

---

`alt`

### --feedback--

Watch the last part of the video where common boolean attributes were discussed.

## --video-solution--

3

## --text--

What is the role of an attribute in HTML?

## --answers--

Attributes provide additional information and help define the behavior for HTML elements.

---

Attributes change the background color of an element.

### --feedback--

Review the beginning of the video where the definition for attributes was discussed.

---

Attributes change the font size of an element.

### --feedback--

Review the beginning of the video where the definition for attributes was discussed.

---

Attributes add JavaScript functionality to an element.

### --feedback--

Review the beginning of the video where the definition for attributes was discussed.

## --video-solution--

1

## --text--

Which of the following is the correct syntax for a boolean attribute?

## --answers--

`<input type="checkbox" checked>`

---

`<input type="checkbox" checked="on">`

### --feedback--

Review the last part of the video where the `checked` attribute was discussed.

---

`<input type="checkbox" checked="off">`

### --feedback--

Review the last part of the video where the `checked` attribute was discussed.

---

`<input type="checkbox" checked="isChecked">`

### --feedback--

Review the last part of the video where the `checked` attribute was discussed.

## --video-solution--

1

Here is the file you need to edit
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/25-front-end-development/lecture-html-fundamentals/6708143cab2b583ecd3324f5.md

This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum
Happy coding


fix: change loki release name to match helm chart

this should simplify the resource names from loki-loki-distributed-*
to just loki-distributed-*. some of the svc name references already
expect the latter.

:tada: This PR is included in version 1.0.0-alpha.23 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Metrics for invalid resources

Bring the counts of invalid resources to Metriton. Best reviewed commit-by-commit:

Tweak error message for invalid secret key
This is a really simple text change.

Hacky implementation: bring invalid objects all the way from watt to the IR
The watt snapshot has invalid objects in it, but those invalid objects were
actually being eaten in the fetcher (as of 3.0, this will need to change, but
in 2.X it's fine). This is the small-surface-area hackish way to bring the
invalid objects through from the snapshot to the IR: it's hackish because it
won't currently result in the invalid objects making it through for the CLI
tools or mockery -- but let's face it, those tools largely bit-rotted the
moment we started properly handling annotations in entrypoint, so, whatever.
A later PR needs to fix the hackery and make the CLI stuff work again.

Include counts of invalid objects in the features array we hand to Metriton
This is the center of gravity of this change.

At present, I tested this manually with gmake deploy, setting debug on,
applying a broken secret, and looking at the debug logs to see what got passed
to Metriton, which (correctly) included:
"invalid_counts": {
  "Secret": 1
}

There are no automated tests yet because we don't have any automated tests of
the features dict at the moment, and adding some to the Fake stuff is...
a little weird. Coming soon! 🙂

[x] I don't think that this needs a note in the CHANGELOG.md.
[x] This is unlikely to impact how Ambassador performs at scale.
[x] My change is adequately tested, I think, just... manually.
[x] I didn't need to update DEVELOPING.md.

Grrr. We should modify the build job so that dev charts get overwritten.


Migration to cedar-14 on heroku

I was not able to complete the migration successfully, I had to rollback to a previous deploy. These are the logs:
Counting objects: 1, done.
Writing objects: 100% (1/1), 189 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rack
remote: -----> Using Ruby version: ruby-2.0.0
remote: -----> Installing dependencies using 1.9.7
remote:        Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote:        Rubygems 2.0.14 is not threadsafe, so your gems must be installed one at a time. Upgrade to Rubygems 2.1.0 or higher to enable parallel gem installation.
remote:        Using rake 10.1.1
remote:        Using i18n 0.6.9
remote:        Using minitest 4.7.5
remote:        Using multi_json 1.8.2
remote:        Using atomic 1.1.14
remote:        Using thread_safe 0.1.3
remote:        Using tzinfo 0.3.38
remote:        Using activesupport 4.0.2
remote:        Using builder 3.1.4
remote:        Using activemodel 4.0.2
remote:        Using activerecord-deprecated_finders 1.0.3
remote:        Using arel <IP_ADDRESS>31022201058 from git://github.com/rails/arel.git (at 4-0-stable)
remote:        Using activerecord 4.0.2
remote:        Using backports 3.3.5
remote:        Using bcrypt-ruby 3.1.2
remote:        Using curb 0.8.5
remote:        Using delayed_job 4.0.0
remote:        Using delayed_job_active_record 4.0.0
remote:        Using excon 0.31.0
remote:        Using hpricot 0.8.6
remote:        Using feedbag 0.9.2
remote:        Using mini_portile 0.5.2
remote:        Using nokogiri 1.6.1
remote:        Using loofah <IP_ADDRESS>30718080038 from git://github.com/swanson/loofah.git (at master)
remote:        Using sax-machine 0.2.1
remote:        Using feedjira 1.2.0
remote:        Using formatador 0.2.4
remote:        Using highline 1.6.20
remote:        Using jsmin 1.0.1
remote:        Using kgio 2.8.1
remote:        Using netrc 0.7.7
remote:        Using pg 0.17.1
remote:        Using rack 1.5.2
remote:        Using rack-protection 1.5.1
remote:        Using rack-test 0.6.2
remote:        Using racksh 1.0.0
remote:        Using raindrops 0.12.0
remote:        Using rendezvous 0.0.2
remote:        Using tilt 1.4.1
remote:        Using sinatra 1.4.4
remote:        Using sinatra-activerecord 1.2.3
remote:        Using sinatra-assetpack 0.3.1
remote:        Using sinatra-contrib 1.4.2
remote:        Using sinatra-flash 0.3.0
remote:        Using thread 0.1.3
remote:        Using unicorn 4.7.0
remote:        Using will_paginate 3.0.5
remote:        Using bundler 1.9.7
remote:        Bundle complete! 35 Gemfile dependencies, 48 gems now installed.
remote:        Gems in the groups development and test were not installed.
remote:        Bundled gems are installed into ./vendor/bundle.
remote:        Bundle completed (0.64s)
remote:        Cleaning up the bundler cache.
remote: -----> Writing config/database.yml to read from DATABASE_URL
remote:        Could not detect rake tasks
remote:        ensure you can run `$ bundle exec rake -P` against your app with no environment variables present
remote:        and using the production group of your Gemfile.
remote:        rake aborted!
remote:        Bad file descriptor - /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1/io/open.rb
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1/io/open.rb:2:in `close'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1/io/open.rb:2:in `open'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1/io/open.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:22:in `block in require_relative_dir'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:21:in `each'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:21:in `require_relative_dir'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1/io.rb:3:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:22:in `block in require_relative_dir'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:21:in `each'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:21:in `require_relative_dir'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.1.rb:3:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.2.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.3.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/1.9.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/2.0.0.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/2.0.rb:2:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports/tools.rb:328:in `require_with_backports'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/backports-3.3.5/lib/backports.rb:3:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/contrib/setup.rb:3:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/contrib.rb:1:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/contrib/all.rb:1:in `<top (required)>
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/app.rb:4:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/Rakefile:12:in `<top (required)>'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load_rakefile'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:637:in `raw_load_rakefile'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:94:in `block in load_rakefile'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:93:in `load_rakefile'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:77:in `block in run'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:75:in `run'
remote:        /tmp/build_5153784be9481e7a57fb085d7f2bdf73/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/bin/rake:33:in `<top (required)>'
remote:        vendor/bundle/bin/rake:16:in `load'
remote:        vendor/bundle/bin/rake:16:in `<main>'
remote:
remote: -----> Discovering process types
remote:        Procfile declares types -> console, web
remote:        Default types for Ruby  -> rake
remote:
remote: -----> Compressing... done, 31.2MB
remote: -----> Launching... done, v14
remote: Verifying deploy.... done.

Rakefile missing. Updating the repo and push again resolves the issue.


Contacts widget - Make the + and x icons more noticeably different

Lead: @sachins-geekyants
Is your feature request related to a problem? Please describe.
When selecting contacts in the contacts widget you use a + icon and when deselecting you use the x icon. Currently, both icons are small and grey and don't look very different from each other especially when dealing with a long list.
Describe the solution you'd like
Could we possibly look into maybe adding color to these icons, using bolder icons or using words like select and deselect?

No progress

@tinashe404
I have tried out these differentiations, We shall proceed further with your preference.

@tinashe404
Fixed and raised PR .

requires deployment and testing.


blas: OffDiagonal and Diagonal are transposed

I have no idea what I was thinking when this was written, but OffDiagonal and Diagonal are inverted. This has no impact on the running of code since users normally do not manually choose these, but it is confusing.

No, this was a more recent misreading; the current values are correct.


[Feature] Availability to specify the filename format of the autocreated Files

Availability to choose custom time Format
Since your plugin creates Daily notes automatically, could you make up an Option to choose the filename format

In its actual version the format of the note ist
DayPlanner-20220101
nice to have would be instead in the optopns menu an option to setup a custom format
wrether fully customizable or the ability to choose different options from
i would be very happy if there would be the format
2022-01-01

is the pfefix needed?
since the notes were always created in the folder "DayPlanners" there is no need for the prefix and there would be a compatibility with some other existing plugins like Obsidian Reminders, which creates appointments in that syntax

(@[[2022-01-01]] 12:59)
which obsidian interprets creating a link in the root dir of the vault with this name - instead if a dayplanner could interecept this for future events - this could be a nice feature

My guess
Best would be a feature to choose the Format
like an interpreter which accepts YYYY-MM-DD in the options menu.
Another Idea
or even better if this plugin had a switch to turn on or of like
enable scanning vault to move events into specific daily notes
which would then if turned on recrusively scan the vault and create from those events listed in it and create those dates as files and in them place those events in the required format

from extracted note index.md
with text testappointment (@[[2022-01-01]] 12:59)
create note \DayPlanners\2022-01-01.md
with entry 12:59 testappointment

hope you get it
i have no clue on js, so im not a real help in this but this would be some features i woukd be really glad if you could implement <3
Much love and thanx!!

I agree. I would like to be able to chose the name of files and folders.
In my case I don't plan ahead but would like to log what happened every night.
folder: logbook
filename: log20220101
That would be so cool.   Please :)

I would also love to see that feature.
An easy work around is to manually create the folder and note and run the Day Planner in command mode.

One possible solution is to use your current "Daily Notes" setup, outline/plan those future days in their respective (upcoming) day's note, but only link them to Day Planner (in "Command Mode", using "Link today's Day Planner for today to the current note") when that "future" day arrive… 😅
I'm about to try this for my workflow. Will report back… ;)

The plugin is now integrated with Daily Notes


Problem with running HGTphyloDetect

I have retrieved a protein sequence for the gene with Genbank acc.id AAK99679.1 (its a prokaryotic gene) and run the blastp in the 'main' directory of the tool by using the command **_python blastp.py input.fasta_** and the blastp file was successfully generated in the designated folder.
In the next step, for Horizontally transferred gene dectection, I run the command
python HGT_workflow_close.py input.fasta (for prokaryote to prokaryote).
Unfortunately, the following error message popped up:
This is gene 1------------------
AAK99679.1
Yes, blast file already exists, nice!
**_Attention: please check the gene accession id!_**
I have tried the same multiple times but the same error continued to occur.
Please help!
I need my analysis to be done at the earliest!
Waiting for your positive response!

same here. tried different proteins that were obtained from ncbi/protein and I get the 'not found' error.

The tool is useless. Total garbage.  It is not updated any more nor does
the author give any reply to any such queries sent to him.
Requesting Github to withdraw the tool immediately so that people do not
waste their valuable time during their work anymore.
MAINAK BHATTACHARJEE
DEPTT.OF BIO-TECHNOLOGY, HIT-K
On Mon, Mar 18, 2024 at 11:34 PM Claudio Slamovits @.***>
wrote:

same here. tried different proteins that were obtained from ncbi/protein
and I get the 'not found' error.
—
Reply to this email directly, view it on GitHub
https://github.com/SysBioChalmers/HGTphyloDetect/issues/12#issuecomment-2004596188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BETFR7ZEZPRTLNIV3NDFYJDYY4UBJAVCNFSM6AAAAABDSN5WXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGU4TMMJYHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Disclaimer:
This
e-mail contains confidential information belonging to
Heritage Institute of Technology & is
intended solely for the Addressee.
The unauthorized disclosure,
use dissemination or copying (either whole or
partial of this e-mail,
or any information it contains), is prohibited.
E-mail is susceptible to
alteration and their integrity cannot be
guaranteed. Heritage Institute of Technology shall not
be liable for this
e-mail if modified or falsified.
If you are not the intended recipient of
this e-mail, please delete it
immediately from your system & notify the
sender of the wrong
delivery and the mail deletion.

Sorry for the late reply! I am recently super busy in working on my new projects. For a few proteins that does not have specific subphylum (taxonomy id), HGTphyloDetect can not give the HGT identification result. This is defined by the workflow of HGTphyloDetect. But we will consider your feedback for the improvement of our computational toolbox.
Thanks for your attention! Best, Le


User is taken to embedded artwork page instead of native through articles

Go to Zona Maco, tap "A Young Curator Shares an insder....", tap artwork --> end up on embedded view

@katarinabatina is this in iPad, iPhone, or both?

i think @orta fixed this. closing.


HTML reload on save

How can we auto reload HTML on save as well?

I've activated HTML watching, but I think this isn't working because of https://github.com/webpack/webpack-dev-server/issues/1271


Better error recovery after . followed by return

TypeScript Version:  1.8.10
Hi, I'm trying to make a generic function that include an Array<T> and a callback with a parameter T that returns an OptionElement interface.
Code
interface OptionElement {
    text : string;
    value : string
}

function someFunction<T>(options : Array<T>, mapper : (data : T) => OptionElement){

}

The problem comes with the inference of the compiler when I pass my Array<SomeFakeElement> to someFunction
interface SomeFakeElement{
    someText : string;
    someValue : string;
}

var a : SomeFakeElement[] = [{
    someText : "Text to show",
    someValue : "Text to eval"
}];

someFunction(a, function(someData){

    return {
        text : "Fake 1",
        value : "Fake 2"
    }
})

Expected behavior:
Show the right intellisense on object someData in the callback.
Actual behavior:
The compiler says T is of type SomeFakeElement, but it does not offer completion:

Although, if I specify the type of someData it works!

It's strange, isn't it?
Thank you for reading :smile:
The whole code is:
interface SomeFakeElement{
    someText : string;
    someValue : string;
}

interface OptionElement {
    text : string;
    value : string
}

var a : SomeFakeElement[] = [{
    someText : "Text to show",
    someValue : "Text to eval"
}]

function someFunction<T>(options : Array<T>, mapper : (data : T) => OptionElement){

}

someFunction(a, function(someData){
    return {
        text : "Fake 1",
        value : "Fake 2"
    }
})

I think it's just getting confused after you insert the ., when it tries to parse someData. <whitespace> return... and treats return as a property of someData. If you hover over the return keyword, the error states 'Property return does not exist on type 'SomeFakeElement'.
Try inserting a semicolon before you insert the . and everything works as expected:

Thank you @yortus for your answer, yes I could notice that but; if you explicitly specify the type of someData like this:
someFunction(a, function(someData:SomeFakeElement){
	return {
		text : "Fake 1",
		value : "Fake 2"
	}
})

You will notice Typescript does not get confuse.

Also there is something regarding with intellisense from the example above:
Here works as expected, I need to provide an object of type Person and offers intellisense.

But here says that and empty object is not assignable to object Person but does not offer intellisense.

Yes, I think that the intermediate parse throws the type checker off, and makes the current call an error. Somehow this means that we won't try to infer the type of someData. We can possibly do better here, but it may be difficult.

I see @DanielRosenwasser, I think this is another case of the issue above..

It's worth noting that this is essentially the first issue that I could find about this problem, some newer ones can be found here and here

It does appear that the original issue is fixed though.


Out of order VideoNode

Publishing VideoNode as string instead of Cid would allow easy reordering of nodes in web-app.

[ ] Publish VideoNode instead of Cid.
[ ] Serialise VideoNode for buffering in web-app.
[ ] Reorder nodes if received out of order.

Investigate if sending binary data instead of string is easy.

Still need to resolve through IPLD so you don't save much...

Since media segments are timestamped loading them, out of order is ok.


Update libbpf to 1.4.5

Update the libbpf submodule to version 1.4.5 to get a bunch of bug fixes.

Can this change please be merged and a new release cut?

@alexforster ^^^

Not a single bindgen change?

Pushed to crates.io

Pushed to crates.io

Thank you!


Alarms: Default Fields Not Fulfilled

Fields in the default structure are not being populated.
Some fields are being replicated in the primarySubject.
    {
        "namespace": "dojot.auth",
        "domain": "AuthorizationError",
        "description": null,
        "severity": "Minor",
        "primarySubject": {
            "instance_id": "1",
            "module_name": "Authentication Module"
        },
        "additionalData": {
            "reason": "not authorized",
            "username": "Mario"
        },
        "appearance":<PHONE_NUMBER>130,
        "reportedAppearance":<PHONE_NUMBER>681,
        "lastModified":<PHONE_NUMBER>130,
        "reason": null,
        "reportedReason": null,
        "disappearance": null,
        "reportedDisappearance": null,
        "_id": "5ab54dffe4b01131a7c4b7d4"
    }

This feature is no longer supported by dojot.


Support emitting css file

I'd very much like to see support for emitting a single css file (or perhaps multiple ones depending on the bundle option). Currently trying to migrate a pretty sizable single page application that uses scss modules to esbuild, and for caching reasons we prefer not to have all of our styles inline in index.html.
Is this something you'd be open to supporting? I'm happy to help out with implementation.
Alternatively, do you know of a workaround involving the cssCallback that would work in watch mode etc?

Yeah I've looked at the esbuild plugin API a bit and it doesn't seem like it can support this properly right now. Concatenating the individual files and manually writing to disk works but you lose a lot of nice features like hashes in file names, source maps etc.
If this changes I'll make a PR. Feel free to close this!

Actually, I see now that Evan is already working on a native implementation of CSS modules that emits files. In light of this I'm gonna close this issue. Thanks anyway!


fails to format  commented code: {…}

/// ```
///  { … }
/// ```
fn main() {
  }

rustfmt silently bails out on this code which can be found in the clippy_lints package.
This silent bailout caused my to find #3008 and prevents all further formatting by cargo fmt on the clippy_lints crate.

This has been fixed by #3058. I think this could be closed.


Updated Request investigation content

This PR Updates the request-investigation page with new content

Please add screenshots, etc. @kelvinkipruto


Job Boards you can apply in Blockchain

Description
Job Boards you can apply in Blockchain, Indeed and Glassdoor are going to the same website to Indeed
Screenshots

Additional information
No response

Hey @RModhilalgohind feel free to work on this. You can either remove the glassdoor board or change it's link to point to the correct address. Either works


Async Fault not working

I updated server-test.js to throw Fault exception from an async function but it doesn't seem to be working. Is this a bug or I should be handling this some other way?
	if (args.tickerSymbol === 'trigger error') {
		throw new Error('triggered server error');
	} else if (args.tickerSymbol === 'SOAP Fault') {
		console.log("before timeout");
		setTimeout(function() {
			console.log("throwing Fault exception after timeout");
			throw {
				Fault: {
					Code: {
						Value: "soap:Sender",
						Subcode: { value: "rpc:BadArguments" }
					},
					Reason: { Text: "Processing Error" }
				}
			}
		}, 0);
	} else {
		return { price: 19.56 };
	}

Output:
before timeout
throwing Fault exception after timeout

/tmp/soap/test.js:30
                        throw {
                        ^
[object Object]

One more thing I noticed was when soap fault is thrown the HTTP status code is 200 but as per SOAP spec it should be either 500/400 and there is no way to specify that.
I've been playing with server.js and I think both of these issues can be fixed by extending callback arguments like this:
        setTimeout(function() {
            cb(null, fault, 500);
        }, 0);

I'll try to submit a pull request for this.

Think this is solved by https://github.com/vpulim/node-soap/pull/641


Extraneous sub-resources are spun down

Problem Statement
In the initial POC we didn't have any corrective logic for hijinks. Technically speaking if you create a Pod and manually mark it as owned by a ReplicaSet that already has a full compliment of Pods, the replicaset controller will spin down Pods until it's back at the expected number (most of the time unless there's something wrong with the other Pods it will be the one you added that gets removed). This kind of self-healing is also needed in our controllers for our APIs.
Acceptance Criteria

[ ] if a subresource for a DataPlane (e.g. Deployment, Service) is attached erroneously, the controller will spin down to the right number
[ ] if a subresource for a ControlPlane (e.g. Deployment) is attached erroneously, the controller will spin down to the right number.
[ ] if a subresource for a Gateway (e.g. DataPlane, ControlPlane) is attached erroneously, the controller will spin down to the right number.

Note to self: need to double check whether we ACTUALLY want to destroy the subresources?


导入excel报错：Zip bomb detected! The file would exceed the max. ratio of compressed file size to the size of the expanded data.

Zip bomb detected! The file would exceed the max. ratio of compressed file size to the size of the expanded data.
This may indicate that the file is used to inflate memory usage and thus could pose a security risk.
You can adjust this limit via ZipSecureFile.setMinInflateRatio() if you need to work with files which exceed this limit.
Uncompressed size: 147803, Raw/compressed size: 1462, ratio: 0.009892
Limits: MIN_INFLATE_RATIO: 0.010000, Entry: xl/styles.xml"}
java.io.IOException: Zip bomb detected! The file would exceed the max. ratio of compressed file size to the size of the expanded data.
This may indicate that the file is used to inflate memory usage and thus could pose a security risk.
You can adjust this limit via ZipSecureFile.setMinInflateRatio() if you need to work with files which exceed this limit.
Uncompressed size: 147803, Raw/compressed size: 1462, ratio: 0.009892
Limits: MIN_INFLATE_RATIO: 0.010000, Entry: xl/styles.xml
at org.apache.poi.openxml4j.util.ZipArchiveThresholdInputStream.checkThreshold(ZipArchiveThresholdInputStream.java:130)
at org.apache.poi.openxml4j.util.ZipArchiveThresholdInputStream.read(ZipArchiveThresholdInputStream.java:80)
at org.apache.poi.util.IOUtils.toByteArray(IOUtils.java:151)
at org.apache.poi.util.IOUtils.toByteArray(IOUtils.java:120)
at org.apache.poi.openxml4j.util.ZipArchiveFakeEntry.(ZipArchiveFakeEntry.java:47)
at org.apache.poi.openxml4j.util.ZipInputStreamZipEntrySource.(ZipInputStreamZipEntrySource.java:51)
at org.apache.poi.openxml4j.opc.ZipPackage.(ZipPackage.java:106)
at org.apache.poi.openxml4j.opc.OPCPackage.open(OPCPackage.java:299)
at org.apache.poi.ooxml.util.PackageHelper.open(PackageHelper.java:37)
at org.apache.poi.xssf.usermodel.XSSFWorkbook.(XSSFWorkbook.java:307)

设置了一下ZipSecureFile.setMinInflateRatio(-1.0d);就可以了


Return old state from turnprogress

turnprogress currently returns the new state, but I think it would be convenient to have the old on instead.  I use this in a pattern of "switch off, do something, then restore".
const PROGRESS = Ref(true)
function turnprogress(switch::Bool)
    old_state = PROGRESS[]
    @info "[Turing]: progress logging is $(switch ? "enabled" : "disabled") globally"
    PROGRESS[] = switch
    AdvancedVI.turnprogress(switch)
    return old_state
end

And perhaps also change the name to turnprogress! and Base.@deprecate turnprogress(s) turnprogress!(s)?
Sorry for not making a PR myself, but I am currently in a somewhat fragile, pinned setup...

I think changing the name to turnprogress! makes sense. Since the usual behaviour of in-place functions in Julia is to return either nothing or the updated variable (e.g., when modifying arrays in-place), I'm wondering if returning the old state is too surprising though.

I can see your way of reasoning about the surprisingness, but I was actually surprised that it didn't behave like that.  I thought it is a common pattern for global-state-modifying functions to return the old state, so that you can restore it later.  But maybe that's a Python thing; e.g., numpy.seterr.

I'd also add that  turnprogress is really not an intuitive name, IMO. Something like setprogress! seems more intuitive.

I like setprogress!, turnprogress sounds like a switch although the function is just setting PROGRESS[] to the specified value.

I like setprogress!, turnprogress sounds like a switch although the function is just setting PROGRESS[] to the specified value.

Exactly :+1:

Actually, I think we should maybe just remove turnprogress and the constant PROGRESS completely and just specify progress = true as the default keyword argument to sample in Turing. I am not a big fan of global states, and I am not sure if it provides any advantage over just specifying the keyword argument if desired. In particular, since turnprogress (or whatever alternative) also implicitly changes the progress logging behaviour of AdvancedVI (and possibly other downstream packages in the future) which is not completely transparent.

Is this issue resolved by https://github.com/TuringLang/Turing.jl/pull/1427? Or should we add another switchprogress function that performs the way @phipsgabler initially suggested?

I'm fine with current solution :+1:

I do think that a non-global solution is more elegant; but this specific one is probably really convenient for things like test cases, where you run a large number of separate samples with the same setting, isn't it?


fix error #88 (examples not compile in Linux)

need check in other OS

I'll try on Mac :+1:

Works fine on Mac.
% cargo run -- run examples/hello.sk
    Finished dev [unoptimized + debuginfo] target(s) in 0.17s
     Running `/Users/yhara/tmp/shiika/debug/shiika run examples/hello.sk`
Hello, world!


bowpmap_ros-release: 0.1.2-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository bowpmap_ros-release to 0.1.2-0:

upstream repository: https://github.com/kejriwalnishant1990/bowpmap_ros.git
release repository: https://github.com/kejriwalnishant1990/bowpmap_ros.git
distro file: indigo/distribution.yaml
bloom version: 0.5.22
previous version for package: null

The build of the code failed due to some error in the code. I have corrected the error and pushed it into git. Please rebuild the repo in docker (build farm).

Some comments from #12905 still apply.
Also if one of these PRs is obsolete please close it.

I have closed #12905 and checks on #12909 has been successfully passed.

I will close this due to no response. Please feel free to create a new PR with the comments being addressed.


Don't drop opening brace on long line matches.

Fixes #1225

Thanks again, and also needs a test :-)

and done.

Thank you!


Replace old raw JSQL parser by maven dependency

Ân will remove the old raw JSQL-Parser. Hoang thinks we should import the new version via Maven because (i) the old one is from 2014 and now they have this 2019 version and (ii) we prove that we did not override any of their source code. We will check if there is any side effects.

Resolved! b869dec


Vault deletion?

Hi,
Is there a plan to add a method to the REST API to delete a vault? Currently it's missing from the spec.

Discussed on the May 27, 2021 call.

Seems like there is demand for vault deletion.
Question: How should this interact with replication?
Question: Can you re-create a deleted vault with the same identifier? (In other words: which party is responsible for picking the vault ID, on creation? It should be server.)


Exclude the externals file type from the telescope extension results

Hi!
Thanks so much for your hard work on this plugin - it's great!
Would it be possible to modify the arguments provided to chezmoi list to exclude file types of externals? I have a few external archives (such as zsh-syntax-highlighting) that means the function returns many files I would never edit/manage.
Expand for context

For context I'm using the below key map:
vim.keymap.set('n', '<leader>sc', telescope.extensions.chezmoi.find_files, { desc = '[S]earch [C]hezmoi Managed Files' })

And my results look like so because of my externals:

Looking at the source code it seems the args are currently hardcoded: https://github.com/xvzc/chezmoi.nvim/blob/faf61465718424696269b2647077331b3e4605f1/lua/telescope/_extensions/find_files.lua#L16-L23
For more flexibility, perhaps the function can be modified to allow providing custom options that can override the default args?

Hmm.. i don't think it is a good idea to make the function modifiable, but this is not a expected behavior for sure. maybe we should add --exclude=externals as a option for the list command. Would that be fine?

That sounds good to me! I've validated the functionality in my personal configuration and it works as expected.
I've opened a PR for the change in #18.


Can't test later parts of tutorial in level editor

When you try to open the later parts of the tutorial (e.g tutorial-beginner-4.json) it forces you back to the beginning of the tutorial in a weird state.

This appears to be caused by the interaction of res://src/main/puzzle/puzzle-state.gd with the tutorial json files having a start_level field.
func _prepare_game() -> void:
	game_active = false
	finish_triggered = false
	game_ended = false

	if CurrentLevel.settings.other.start_level:
		# Load a different level to start (used for tutorials)
		var new_settings := LevelSettings.new()
		new_settings.load_from_resource(CurrentLevel.settings.other.start_level)
		CurrentLevel.start_level(new_settings)

	reset()
	emit_signal("game_prepared")
	emit_signal("after_game_prepared")

Not sure why the if start_level hook is there in the first place.
Only the tutorial levels use it, and loading oh-my.json throws an error because "start_level marathon_hard" references a file that was moved.
Maybe delete the if block?

That is indeed the case.
I like that "Retry" and "Start" are the same button :)
Because of that, I almost want to call it intended behavior.
I've found some related behavior.
If I use the Open File on a tutorial level (for example, tutorial/basic-1.json), the id opens as basic_1, but if I use Open Resource, the id opens as tutorial/basic_1.
This is due to how res://src/main/puzzle/level/level-settings.gd generates the level key based on the path in level_key_from_path().
This leads to the tutorial playing correctly (but with a customer that's not Turbo) if I use Open Resource, but not if I use Open File.
The string matching in res://src/main/puzzle/tutorial/tutorial-hud.gd in replace_tutorial_module() causes this.
The interaction between these two things explains the "weird state".
I'm not sure what to do about this...

Right, that's intended behavior. If you're loading a random file on your machine, not a file in the game's resources, so it obviously wouldn't make sense to set the ID to something like Users/Amavect/My Documents/basic_1 or whatever.
It seems strange when you have the Godot project open or when you're navigating through the source code, but that's not what a typical user would be doing.

The level editor has been removed.


It's unclear how to use formatting.

Code formatting is a VSCode feature that we plug into.  From what I can tell, there are two ways to trigger it: the Format Document command and with the "editor.formatOnSave": true setting.
For users of the extension (especially new ones), this is not clear.  I expect something like the following happens regularly:

user wants to use black to format their Python code
they set "python.formatting.provider": "black"
their code does not suddenly get formatted
they save their file but nothing happens
they look for a "Python: ..." command to trigger black
they realize black wasn't installed (and wonder why they weren't prompted)
they finally figure out they need "editor.formatOnSave": true

We can improve this experience with the following:

add a Python: Configure Formatting command that works like Python: Configure Unit Tests
when someone configures formatting but has not set "editor.formatOnSave": true, pop up a message telling them that
add a Python: Format Document command

When a formatter framework is specified for the first time in the settings, prompt users if they want to use format on save

This is now straight forward. User can search for Black or autopep8 extension in the marketplace, install it and it just works out of the box.

As for discoverability of format on save that should be done in VS Code UI


Data downloading freezes for 1min if auto 1min refresh happens at the same time while user is refreshing a page

See video:
https://user-images.githubusercontent.com/1311912/204416868-5102ba16-e2fe-41f5-8f4c-5aadc815629c.mov

Couldn't reproduce this time. Ready to deploy.


Merge with Material?

Stumbled across this project by accident - this is actually pretty interesting. Would love to see RTL support in Material for MkDocs. Would you mind isolating the changes you made into a PR and I would integrate it?

Thank you.
Unfortunately, I don't have enough time to do that.


Ruby client waits for ready when channel is in TRANSIENT_FAILURE state

The Ruby client seems to be waiting for ready when channels are in a failure state, contrary to the advice given in https://github.com/grpc/grpc/blob/ff83681cbb4296dba3dcd92aaba27cba494a934a/doc/wait-for-ready.md.
Should this be an issue in the gRPC issue tracker?
Yes, it's a bug.
What version of gRPC and what language are you using?
gRPC Ruby 1.4.5
What operating system (Linux, Windows, …) and version?
MacOS 10.12.5
What runtime / compiler are you using (e.g. python version or version of gcc)
Ruby 2.3.1p112
What did you do?
Created a stub pointing to an invalid host and attempted several requests. The first request times out, putting the channel in TRANSIENT_FAILURE state.
What did you expect to see?
I expect requests sent while the channel is in TRANSIENT_FAILURE state to fail immediately according to the default wait for ready semantics.
What did you see instead?
All requests fail only after the deadline is reached, even those sent while the channel is in TRANSIENT_FAILURE state. See https://github.com/grantr/grpc-ruby-wait-for-ready for a test case.
Anything else we should know about your project / environment?

Indeed it looks like failed name resolution doesn't appear to follow the value of the wait_for_ready flag. (name resolution appears to continue to retry queries even though wait_for_ready is false).
I'd note that name resolution failures look like a special case here though - if the channel's target has been resolved and the connection sees TRANSIENT_FAILURE, then the wait_for_ready flag does appear to be respected and the RPC does appear to fail immediately.
How severe is this bug for you?
cc @ejona86, who might have a better idea of proper behavior in this failed-name-resolution case.

Good to know @apolcyn, thanks for looking into it!

How severe is this bug for you?

We can work around it with circuit breakers. We'd use those anyway in hot paths, so it's not a huge deal for us, but it could cause problems for anyone not using circuit breakers and expecting that fail-fast applies to DNS resolution failures.

The name resolution is supposed to be attempted, but if it fails then a wait_for_ready=false RPC should fail. Name resolution can continue retrying in the background, though.

This looks like a dup of #13627, which is fixed, so I suspect this is fixed as well.  Please re-open if you're still seeing this problem.


Minor refactorings

Minor refactorings.
Please see logs for each commit.

Thank you @jechol, I appreciate this.


bun example does not render correctly

Following the bun example docs
I get the following output 🤔

src/index.tsx
import { Hono } from 'hono'
import * as React from 'react'
import { renderToString } from 'react-dom/server'

const app = new Hono()

app.get('/', (c) => {
  const hello = (

Hello! React!

  )
  return c.html(renderToString(hello))
})

export default app

tsconfig.json
{
  "compilerOptions": {
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "module": "esnext",
    "target": "esnext",
    "moduleResolution": "node",
    "jsx": "react-jsx",
    "jsxFragmentFactory": "Fragment",
    "jsxImportSource": "hono/jsx",
    "types": [
      "bun-types"
    ],
  }
}

versions
bun 0.1.5
hono 2.0.5

Hi @Inveracity Thank you for using Hono!
Sorry, it's confusing you. There are two patterns for using JSX. The setting is different for it.
JSX middleware (not React)
tsconfig.json:
{
  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxFragmentFactory": "Fragment",
    "jsxImportSource": "hono/jsx"
  }
}

import { Hono } from 'hono'

const app = new Hono()

app.get('/', (c) => {
  return c.html(
Foo!
)
})

export default app

React
We don't need tsconfig.json. Or you can write:
tsconfig.json:
{
  "compilerOptions": {
    "jsx": "react",
    "jsxFragmentFactory": "Fragment",
    "jsxImportSource": "react"
  }
}

code:
import { Hono } from 'hono'
import { renderToString } from 'react-dom/server'

const app = new Hono()

app.get('/', (c) => {
  return c.html(renderToString(
Foo!
))
})

export default app

Thank you for clearing up for me, much appreciated!

That's good!


OPM won't display the graph

Hello,
OPM is up and running but whenever I click on icon I get this error. My perl version is v5.18.2
[Tue Apr 14 09:20:32 2015] [debug] GET "/graphs/showservice/ithfdb59/CPU%20Load".
[Tue Apr 14 09:20:32 2015] [debug] Routing to controller "OPM::Users" and action "check_auth".
[Tue Apr 14 09:20:32 2015] [debug] Routing to controller "OPM::Graphs" and action "showservice".
[Tue Apr 14 09:20:32 2015] [debug] Action not found in controller.
[Tue Apr 14 09:20:32 2015] [debug] Rendering template "graphs/showservice.html.ep".
[Tue Apr 14 09:20:32 2015] [error] Global symbol "$graphs" requires explicit package name at template graphs/showservice.html.ep line 5.
Global symbol "$server_id" requires explicit package name at template graphs/showservice.html.ep line 5.
Global symbol "$hostname" requires explicit package name at template graphs/showservice.html.ep line 5.
Global symbol "$server_id" requires explicit package name at template graphs/showservice.html.ep line 8.
Global symbol "$services" requires explicit package name at template graphs/showservice.html.ep line 8.
Global symbol "$services" requires explicit package name at template graphs/showservice.html.ep line 15.
10:
11:            <%=l('Change service') .'...' %>
12:
13:
14:
15:         <% foreach my $s ( @$services ) { %>
16:
17:               <%= link_to 'graphs_showservice' => { server => stash('hostname'), service => $s->{'service'} } => begin %><%= $s->{'service'} %><% end %>
18:
19:         <% } %>
20:
[Tue Apr 14 09:20:32 2015] [debug] Template "exception.development.html.ep" not found.
[Tue Apr 14 09:20:32 2015] [debug] Template "exception.html.ep" not found.
[Tue Apr 14 09:20:32 2015] [debug] Rendering cached inline template.
[Tue Apr 14 09:20:32 2015] [debug] Rendering cached inline template.
[Tue Apr 14 09:20:32 2015] [debug] 500 Internal Server Error (0.013365s, 74.822/s).
Thanks,
Nhan

root@10:/# mojo version
CORE
Perl        (v5.18.2, linux)
Mojolicious (4.63, Top Hat)
OPTIONAL
EV 4.0+               (4.15)
IO::Socket::IP 0.16+  (0.25)
IO::Socket::SSL 1.75+ (1.965)
root@10:/#

Problem solved by installing newer version of Mojolicious package 5.54
root@ithfdb62:/var/lib/postgresql# mojo version
CORE
Perl        (v5.18.2, linux)
Mojolicious (5.54, Tiger Face)
OPTIONAL
EV 4.0+                 (4.15)
IO::Socket::IP 0.20+    (0.25)
IO::Socket::Socks 0.64+ (not installed)
IO::Socket::SSL 1.84+   (1.965)
Use of uninitialized value $host in concatenation (.) or string at /usr/share/perl5/Mojo/UserAgent.pm line 188.
root@ithfdb62:/var/lib/postgresql#


⚠ GLDDNS Server (ns2.glddns.com) has degraded performance

In 2eb0e0b, GLDDNS Server (ns2.glddns.com) (ns2.glddns.com) experienced degraded performance:

HTTP code: 200
Response time: 495 ms

Resolved: GLDDNS Server (ns2.glddns.com) performance has improved in 6da1085 after 7 minutes.


Preload multiples languages on init

Hi,
I have in my application multiple languages. The user can load one of them at runtime.
But i cannot find a way to configure ngx-translate to preload them, or is it done at runtime ?
If my default browser language is "fr", ngx-trsnalte only loads fr.json, but i also have the other ones.
Thanks

Ok, i found a solution, by preloading them with a mix of http calls and translate.setTranslation API


How to implement: "c == null"

 var interpreter = new Interpreter();
 var info = interpreter.DetectIdentifiers("c != null");
 var lambda = interpreter.Parse("c == null",new Parameter("c",typeof(string)));
 var result1 = lambda.Invoke(new Parameter("c", null,typeof(string)));
//throw exception....

Excuse me:
Is it safe to call the invoke function multiple times for the same lambda instance, and will the performance be improved?

I want to achieve such a function...
<iftrue test="c==1">
</iftrue>

Yes, calling multiple times the Invoke function is fine, and it is suggested whenever possible. Your code seems to be correct. Write me if you see problems.

Yes, calling multiple times the Invoke function is fine, and it is suggested whenever possible. Your code seems to be correct. Write me if you see problems.
//When c = null,Exceptions will occur System.ArgumentNullException:“Value cannot be null.

            Expression<Func<int, bool>> expression = s => s < 1;
            var p = Expression.Parameter(typeof(int?), "s");
            var binary = Expression.MakeBinary(ExpressionType.Equal, p, Expression.Constant(null));
            var exp = Expression.Lambda(binary, p);
            var da = exp.Compile();
            var res = da.DynamicInvoke(new object[] { null});

Obviously, it can be realized

The problem is on how you construct the Parameter object. The constructor is defined as:
public Parameter(string name, Type type, object value = null)
So you should write: new Parameter("c", typeof(string), null)


Can you expose the CupertinoPageRoute so that we can use it?

I am using auto route and have a custom route builder that I want to use your CupertinoPageRoute on so that I can handle will pop scope correctly with it.

Never mind, I realize now this is not needed

I lied actually. This is. still needed in my instance.

Did you mean your own PageTransition, or a page route? Because the CupertinoPageRoute on its own will not help you. You'll need something like the ConditionalWillPopScope widget (which my package provides). This widget alone should let you do anything you want. I just created the CupertinoWillPopScopePageTransionsBuilder as an extra, to provide some UI indication that the navigation gesture was cancelled. It is not needed for scope popping to work.
You can check the sample app to see how this transition is used:
    pageTransitionsTheme: PageTransitionsTheme(
      builders: {
        TargetPlatform.android: ZoomPageTransitionsBuilder(),
        TargetPlatform.iOS: CupertinoWillPopScopePageTransionsBuilder(),
      },
    ),

I mean the Page Route. I am using auto_route with a custom route builder, and on ios I am injecting the CupertinoPageRoute. I then use the ConditionalWillPopScope on my page, and when it is true, I do not get the animation when swiping back as I believe I should. I think this is because I am manually injecting the CupertinoPageRoute which is then ignoring the injected 'TransitionsBuilders' unless I am understanding things incorrectly.

Right, so if you use the CupertinoWillPopScopePageTransionsBuilder transition, it'll automatically load the the modified version of CupertinoPageRoute that has the animation.
You should be able to wrap MaterialApp.router() with a Theme that would set the pageTransitionsTheme, and everything should work for you. (Or if you already have a theme above it in the context tree, just add the pageTransitionsTheme to it.)

Resolving and closing as I assume everything is good now.


Single precision support for MPI messages

There is the compile time seleciton mechanism for the precision in the code base, however the MPI modules are currently hardcoded for MPI_DOUBLE_PRECISION. We need to figure out a way to fix this so that we can run single precision simulations.
A very incomplete attemt is here (albeit the wrong place, it should be in base backend)
https://github.com/xcompact3d/x3d2/blob/85246f3b27fecee0095559029dbc4faadb7b5731/src/cuda/backend.f90#L26
Then based on the dp parameter MPI_FP_PREC can be set and used everywhere afterwards. This probably will require converting mpi_sendrecv modules into classes, so that they can be instantiated at the backends with the MPI_FP_PREC
Thanks @JamieJQuinn for pointing out this in #67.

This is not the correct way to do it - dp = kind(0.0d0) (or something similar) will be compiler-specific, and not necessarily aligned with the MPI library. Something equivalent to
#ifdef DOUBLE_PREC
integer, parameter :: MPI_FP_PREC = MPI_DOUBLE_PRECISION
#else
integer, parameter :: MPI_FP_PREC = MPI_REAL
#endif

is what should be used (could also do with functions, but then can't make it constant)

it might also be worth looking into MPI_F08 - this is a better module than the default MPI one, however it isn't very well supported and tends to break tools so I haven't really used it... But it is a bit better on the type safety side of things.

Parameter is actually very simple way of implementing this, and probably most robust. I think we can go ahead with it.


 I'll come up with a patch to fix it.

OK, should be fixed by #32
Really sorry I didn't test this earlier. I only realized my mistake once I started replacing my old code :(

@rs, @yanfali, I assume this can be closed?


Create ADR for; Don't rely on third party depencies for the filteredlist.

Acceptance criteria:
Use the ADR format;
Discuss with the community

Don't rely on third party dependencies for the filtered-list
Date: 2023-05-04
Status
Open
Context
While starting to move components we started with the filterd-list, which is now published on npm.
Functional wise the filterd-list works fine, but replacing the integrated filtered-list with the newly published stand alone filtere-list comes with unforseen complications.
In Open-SCD we use the integrated filtered-list as an extension of @material/mwc-list, because of this the filtered list gets cast to mwc-list.
In the newly stand-alone components we made a decision to no longer extend the components from material webcomponents but use the material webcomponent in the render function.
This is why casting to a mwc-list will no longer work.
Because the material web component will be implemented in the render function it also gets loaded differently, which can result in an empty list if it's called in the same
manner as we do now in Open-SCD.
Decision
While implementing components in the future, be sure not to rely on third party dependencies. In case of the filtered-list this would be mwc-list.
This means:

no longer cast to the third party dependency
be sure to load the new stand-alone components asynchronously and use the requestUpdate/updateComplete.

Consequences
These decisions will result in that implementation can not be simply used in the same manner as we do in Open-SCD right now.
Be sure to make changes as stated in the decision.

" in the same manner as we do in Open-SCD right now" can you be more specific? If we read this 5 years later, we don't know what this is.
Are their more consequences? E.g. takes more time? More flexible..

In order to move forward, you can send a pull-request and ask for reviews ;) This is how we can get the community on board.


ux: Leap sorts by pinned, unreads, and pals

Context
After using preview Leap, noticed I was using it to primarily jump between my unreads and pins. So, this PR bakes in some of this behavior.
Changes

[x] score Group results by membership in pinnedGroups, then by isGroupUnread, then A-->Z
[x] score Channel results by membership in pinned, then if it's a member of a group in pinnedGroups, then by if the channel is within the currently viewed group, then by isChannelUnread, then by A-->Z
[x] score Ships results by prioritizing mutuals in %pals graph, the mention heuristics (e.g., downrank comets), then by unread status
[x] fuzzy string compare when filtering

Leaving a note for testing: make sure this works without %pals

Not covered in this PR, but some issues I've noticed with leap:

if your ship does not have a contact store entry for a ship, you can't navigate to a DM with that ship (even if you've started one with them). This effects all new ships (which are currently effected by #1305).
I can't search for and navigate to a group DM.

#1936 and #1937

Should we merge?

Does it work without pals installed?


Debug NIST issues on the latest Release

Currently getting a NPE when tryng to load profiles with the latest NIST release (1.5.5)
NIST team created a 1.5.6, but still having issues.

Have a call with Hossam (NIST Team) Today - 1/5/23 to see if we can find environmental issues since they claim it's working on their environment.

NIST has released version 1.5.6-SNAPSHOT. We narrow down the issue to the NIST libraries not being able to load certain schema files - ConformanceContext.xsd and its dependencies, Extension.xsd and Commons.xsd.
As a stop gap, I've downloaded those schemas from source code from NIST and added them directly under resources folder on our project. That seems to mitigate the problem while NIST folks further investigate why that's an issue on certain environments.
No windows environment runs properly withouth the local XSD. Some macs run ok, some don.t - we tried two different JDKs - openJDK and aws correto JDK (all v.11)
We also ran sucessfully on linux under windows subssytem on a cdc machine.

Waiting for NIST to release 1.5.6 (not as SNAPSHOT) to finish updating the library.


'No Frame Received' error in realsense-viewer after a source code update

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.10.0-42-generic

SDK Version
rs2

Working commit: 4ed892bf4037102844e2dc361af493ca8ec92080
Commit not working: 0cc659d985af42f311b2c1c6aa9664d17133621d

Hi @marvin-hao
Could you please provide more information? We have noticed some performance degradation between the two commits you mentioned, and since then submitted a fix to the development branch.
Could you let us know if it helped?

Can you please help me locate the commit in the dev branch that fixes the issue?

This is the Pull-Request I was referring to: #907


stage1/usr_from_coreos: use CoreOS 1029.0.0 with systemd v229

Yay

:+1: @iaguis do you want "Yay" to appear in the changelog? ;-)

@iaguis do you want "Yay" to appear in the changelog? ;-)

No, but I can't think of anything else right now :/

You can reference the following:
Fixes https://github.com/coreos/rkt/issues/1759
https://github.com/coreos/coreos-overlay/pull/1833

LGTM.
I'm testing this with tests/aws.sh to check for regressions. I'll paste the results here..

Fedora 22
--- FAIL: TestAPIServiceListInspectImages (2.02s)
--- FAIL: TestImageSize (0.94s)

Already reported: https://github.com/coreos/rkt/pull/2501
--- FAIL: TestNonRootFetchRmGCImage (6.72s)

???
--- FAIL: TestServiceFile (10.26s)

https://github.com/coreos/rkt/issues/2323
--- FAIL: TestSocketProxyd (127.52s)

https://github.com/coreos/rkt/pull/2512
--- FAIL: TestUserns (18.87s)

Test needs to be fixed with CAP_SYS_PTRACE.
https://github.com/coreos/rkt/pull/2518
Fedora 23
--- FAIL: TestAPIServiceListInspectImages (1.80s)
--- FAIL: TestImageSize (0.94s)

Already reported: https://github.com/coreos/rkt/pull/2501
=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (6.73s)
        rkt_non_root_test.go:113: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-897918756 --local-config=/tmp/localdir-101433395 --system-config=/tmp/systemdir-810844150 image gc
        rkt_non_root_test.go:118: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-897918756 --local-config=/tmp/localdir-101433395 --system-config=/tmp/systemdir-810844150 image rm sha512-3df086faf54c592a8bd7c35a3f72b6ef
        rkt_tests.go:138: rkt terminated with unexpected status 1, expected 0
                Output:

???
--- FAIL: TestServiceFile (10.25s)

https://github.com/coreos/rkt/issues/2323
--- FAIL: TestUserns (18.31s)
[ 1912.727071] inspect[5]: Cannot stat file "/proc/1/root/": stat /proc/1/root/: permission denied

Test needs to be fixed with CAP_SYS_PTRACE.
https://github.com/coreos/rkt/pull/2518
Fedora 24
For some reason (unrelated to this PR), the test script didn't start the test on Fedora-24...
Fedora Rawhide
execv() failed: No such file or directory

Known SELinux issue: https://github.com/coreos/rkt/issues/2322
Restarting manually without SELinux.
Then, on the host flavor, all tests fail:
sysusers.service: Main process exited, code=exited, status=203/EXEC

Because we don't copy systemd-sysusers.
And on the coreos flavor:
=== RUN   TestTrust
panic: test timed out after 30m0s

--- FAIL: TestNetHostConnectivity (6.82s)
Ubuntu 1604
--- FAIL: TestAPIServiceListInspectImages (1.50s)
--- FAIL: TestImageSize (0.88s)

Already reported: https://github.com/coreos/rkt/pull/2501
=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (7.07s)
        rkt_non_root_test.go:113: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-568934105 --local-config=/tmp/localdir-795000932 --system-config=/tmp/systemdir-250041971 image gc
        rkt_non_root_test.go:118: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-568934105 --local-config=/tmp/localdir-795000932 --system-config=/tmp/systemdir-250041971 image rm sha512-025cc26604d106568b6209127efefaa3
        rkt_tests.go:138: rkt terminated with unexpected status 1, expected 0
                Output:

???
--- FAIL: TestServiceFile (10.27s)

https://github.com/coreos/rkt/issues/2323
--- FAIL: TestUserns (18.95s)
[ 1752.024649] inspect[5]: Cannot stat file "/proc/1/root/": stat /proc/1/root/: permission denied

Test needs to be fixed with CAP_SYS_PTRACE.
https://github.com/coreos/rkt/pull/2518
Ubuntu 1510
Debian
I had to workaround the failed installation of wget and restart the test manually from SSH:
--- FAIL: TestAPIServiceCgroup (8.85s)
        rkt_api_service_test.go:49: Running rkt api service
        rkt_tests.go:113: Running command: /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-778361519 --local-config=/tmp/localdir-401176130 --system-config=/tmp/systemdir-750413497 --insecure-options=image run --interactive /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/test-tmp/rkt-inspect-interactive.aci
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:489: Pods are not in RUNNING state
        rkt_api_service_test.go:484: Pods are running
        rkt_api_service_test.go:174: Expected the cgroup suffix to have "/machine-rkt\\x2d6dbeecdd\\x2dc9e6\\x2d42ec\\x2da660\\x2dc902ca5c6fa4.scope", but saw "/system.slice/ssh.service"
        rkt_api_service_test.go:174: Expected the cgroup suffix to have "/machine-rkt\\x2d6dbeecdd\\x2dc9e6\\x2d42ec\\x2da660\\x2dc902ca5c6fa4.scope", but saw "/system.slice/ssh.service"
        rkt_api_service_test.go:174: Expected the cgroup suffix to have "/machine-rkt\\x2d6dbeecdd\\x2dc9e6\\x2d42ec\\x2da660\\x2dc902ca5c6fa4.scope", but saw "/system.slice/ssh.service"

???
$ cat /proc/self/cgroup
8:perf_event:/
7:blkio:/
6:net_cls,net_prio:/
5:freezer:/
4:devices:/system.slice/ssh.service
3:cpu,cpuacct:/
2:cpuset:/
1:name=systemd:/system.slice/ssh.service

CentOS
--- FAIL: TestAPIServiceListInspectImages (1.08s)
--- FAIL: TestImageSize (0.87s)

Already reported: https://github.com/coreos/rkt/pull/2501
=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (7.19s)
        rkt_non_root_test.go:113: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-784530456 --local-config=/tmp/localdir-484231319 --system-config=/tmp/systemdir-947059466 image gc
        rkt_non_root_test.go:118: Running /var/tmp/rkt/builds/build-rkt-coreos/build-rkt-1.4.0+git/tmp/functional/rkt --dir=/tmp/datadir-784530456 --local-config=/tmp/localdir-484231319 --system-config=/tmp/systemdir-947059466 image rm sha512-5549c54f89d23daa837b08fb75fd4e70
        rkt_tests.go:138: rkt terminated with unexpected status 1, expected 0
                Output:

???

so I've been experimenting with this,  init.scope seems to only end up in the systemd hierarchy, not anything else that cadvisor looks at.  Any chance it can be includes in the same set of groups as the standard app cgroups are (i.e. what would be system.slice/pause.service cgroup)

so I've been experimenting with this, init.scope seems to only end up in the systemd hierarchy, not anything else that cadvisor looks at.

init.scope is created by systemd inside the pod, so it should only be created after the pod has been started. But this cgroup is not the root cgroup of the pod and it only contains one process: systemd inside the pod. The other processes of the pod will be in "neighbor" cgroups.
So, cadvisor could use init.scope as a signal that the pod has been created and that the API service will know about the pod. But it should not use it for the other hierarchies nor as the root cgroup of the pod.

LGTM


Write a Perl program to convert weeks to seconds

Description
Write a Perl program to convert weeks to seconds
1 week = 7 days = 168 hours = 10080 minutes = 604800 seconds
Input  : 5
Output : 3024000

How to contribute

Save the solution in program/convert_weeks_to_seconds.pl file
Add convert_weeks_to_seconds.pl file in convert-weeks-to-seconds folder

!assign


[date-picker] Is it possible to get hook for current selected date when using the keyboard navigation

Date-picker has good aria support, it allow navigation through keyboard. But date is changed only when user hits enter / space.
Are there any possible hooks which give the current selected date when navigating via keyboard.

I think you mean current focussed date, based on the fact that you're talking about keyboard navigation?

I have noticed that there is already something like that activeDate available. But its not exposed to public API.
May be if we can expose activeDate. Then code should be able to watch it safely without any performance issues.

I have created an addon which can work independently from Datepicker API.
Here is the GIST if anyone need this feature without waiting for "Purgatory" updates.
It works by watching the activeDate.

This sounds like a reasonable feature, although this should be opt-in if it were implemented.

Closing in favor of #4772.


link is broken at README

https://github.com/kcl-lang/kcl-openapi?tab=readme-ov-file#translate-swagger-openapi-spec-to-kcl
https://github.com/kcl-lang/kcl-openapi?tab=readme-ov-file#kcl-openapi-spec ---> KCL OpenAPI Spec
@Peefy
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your KCL components version? (Required)

I want to fix it but I can't find the correct link

Seems like it's https://www.kcl-lang.io/docs/tools/cli/openapi/openapi-to-kcl

or https://www.kcl-lang.io/docs/tools/cli/openapi/spec


⚠ Samsung has degraded performance

In 27f2b67, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2248 ms

Resolved: Samsung performance has improved in 17c216c.


chore(package): update linting dependencies

Summary
Now that eslint-config-fbjs supports range on eslint-plugin-relay we can upgrade all of our stuff.
Only lint dep not upgraded is babel-eslint (to 8), waiting for https://github.com/facebook/fbjs/pull/275

Test plan
Green CI

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4964   +/-   ##
=======================================
  Coverage   60.36%   60.36%
=======================================
  Files         198      198
  Lines        6608     6608
  Branches        4        4
=======================================
  Hits         3989     3989
  Misses       2619     2619

Impacted Files
Coverage Δ

packages/jest-util/src/install_common_globals.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Oh man, I appreciate so much how you are keeping the Jest repo clean. This is so important to onboard new people in the future :)


Fix focasble border in Data Toolbar

Saw this occuring in https://github.com/patternfly/patternfly-next/pull/2229

relates to : #2184

thanks Matt ^ ill close this


Implement "gopass-jsonapi version"

Add CLI command to output release version.

Actually works with current main branch:
./gopass-jsonapi --version
gopass-jsonapi version 1.11.1

I think I tried it with an outdated binary from the gopass repo - all good here.


Road to v0.3

Features:

[x] Looping mechanisms.
[ ] Module mechanism.
[ ] Small std lib & testing mechanism.
[ ] Syntax guide
[ ] Test Coverage
[ ] LSP
[ ] Github Actions for Releases

Bug fixes:

object field mutation fix
indexing operation assignment mutation on stack fix
config files & test fix

The list of features was too ambitious for a single PR. Finalising current updates and merging as is.


Random id for buttons

Buttons will have a random id if it is not specified

I'm not sure if it's useful. If you include buttons in your message, you probably expect the user to click on them, which means you'll need to recognize the button that was pressed. One of the most convenient ways to do that is by looking at the button ID, which is much more convenient if you make the ID yourself.


License is not specified

Hi,
Thanks for developing this, the idea is great.
However, please specify a license, so users can expect what to get when they use the library.

According to package.json file it is ISC licence.

Yes, I was happy to go with the ISC license in the package.json but it's not clear outside of this. Will clarify.

I see, thanks for Info, but I guess it wouldn't harm to add LICENSE.txt to the project.

Thanks.


[DevCenter] Update release date

Update release date for DevCenter 1.0.0
Original dev center sdk 1.0.0 PR: https://github.com/Azure/azure-sdk-for-js/pull/29512
APIView: @azure-rest/developer-devcenter - apiview.dev

API change check
API changes are not detected in this pull request.


count() Parameter must be an array or an object

Hi,
I'm getting the following error when clicking on every menu option (logged in as domain\administrator):
Warning: count(): Parameter must be an array or an object that implements Countable in C:\xampp\htdocs\includes\organizations.php on line 24
Also: When logged in al the counters stay at 0 (organisations, backup jobs, etc).
In the REST log I can see I'm logged in and no further errors there.
Logging in with a tenants credentials doesn't work at all at the moment.
I'm running PHP 7.3.5.
Do you have any idea?

From the looks of it, there is no organization added in the VBO console. Once you add an organization the warning will be gone as the total count will be 1 instead of 0 (which creates the message).
I will update it in the code however you can disable the warnings by opening the organizations.php file and by adding the following on line 2 (right after the <?php part):
error_reporting(0); // Disable all errors.

Thanks, I will try that.
The strange thing is, I've got about 5-10 organizations added in the console at the moment (and running backups) And I must add that the portal worked the first time around. Then after I hadn't used it for a month or 2 I got connection errors when logging in, this is when I installed the latest version of PHP/Apache and your code, and then this happened.
So I'm not trying to suppress the message, but it seems that the webserver won't talk to VBO in a correct way or something.
I already dug up some fix for Guzzle from Github regarding this issue, but that doesn't seem to fix it :(
https://github.com/guzzle/guzzle/pull/2038/files/f8265f45535e35e4fa5d4f7f3d3d916a82f802b7

If you took the newer code, it could be due to the fact the config.php had a change (supports both v2 and v3). Can you double check the config.php file and make sure it points to the correct VBO server and API version?

It connects to the FQDN of the portal, which on the Apache server resolves to <IP_ADDRESS>, thats correct as the VBO instance is also running on this server. The port is correct and the API is set to V3 (my VBO version is <IP_ADDRESS>2

If possible, we can do a remote session and dig into it - just drop me an e-mail via<EMAIL_ADDRESS>so we can arrange something. It all looks correct but the count() error means it fails at getting the organizations so the API call is returning incorrect info.

Will do!


Fix forced alignment on patch version

Context
See https://github.com/nebula-plugins/gradle-nebula-integration/issues/51

@ljacomet don't trust the :x: above, performance tests passed with the latest commit. Let me know what you think.

@melix Can you add the release note reference to the contributed test?

@ljacomet he already is ;)


Remove version: Amazon.Chime version 4.34.9941.1

Reason

Installer unavailable. See https://github.com/microsoft/winget-pkgs/issues/171560#issue-2505208830

Resolves #171560

Microsoft Reviewers: Open in CodeFlow

URL: https://clients.chime.aws/win/releases/Chime.4.34.9941.exe
Status Code: 200
(Automated message - build 894)


use batch for hook build to match main

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherypick release-0.19

/cherrypick release-0.19

/approve
/lgtm


Composite primary key causes a UnknownPropertyException

When applying the SortableGridView to a model with a composite primary key, the id is not recognized.
I would like to suggest using the data-key that is stored in each row instead of the items[]_#. This stores a json array with the keys and columnames when a composite PK is used.

https://github.com/himiklab/yii2-sortable-grid-view-widget/pull/9

https://github.com/himiklab/yii2-sortable-grid-view-widget/pull/9


Broken repository indexes for Ubuntu 14.04 "trusty"

Describe what happened:
apt-get update is broken:
W: Failed to fetch https://apt.datadoghq.com/dists/stable/main/binary-amd64/Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old ones used instead.

with the following repository configuration:
$ cat datadog.list
deb https://apt.datadoghq.com stable main

Repository for agent 6.x doesn't work as well:
$ cat datadog.list
deb https://apt.datadoghq.com/ stable 6
$ sudo apt-get update >/dev/null
W: Failed to fetch https://apt.datadoghq.com/dists/stable/6/binary-amd64/Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old ones used instead.

Describe what you expected:
According to this page, agent should be available for 14.04:
https://docs.datadoghq.com/agent/basic_agent_usage/?tab=agentv6#supported-os-versions
Steps to reproduce the issue:
Simply run apt-get update with pre-configured datadog repository on 14.04.
Additional environment details (Operating System, Cloud provider, etc):
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.6 LTS
Release:	14.04
Codename:	trusty

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.6 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.6 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

Hi @defanator, thanks for reporting this issue. We have checked the integrity of the repository on our end, is the issue still happening consistently on your end?

However, I tried to spin up a fresh trusty VM and configure both older (5.x) and new (6.x) datadog repositories, and everything went fine.
I'm investigating what's happening on other hosts - will post an update here.

Ok, perhaps this is the reason:
# find /var/lib/apt/lists/ -name "*datadog*" -exec ls -l {} \;
-rw-r--r-- 1 root root 204435 Nov  6 16:26 /var/lib/apt/lists/partial/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages.decomp.FAILED
-rw-r--r-- 1 root root 26620 Nov  6 16:26 /var/lib/apt/lists/partial/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages
-rw-r--r-- 1 root root 5393 Aug 26 16:26 /var/lib/apt/lists/apt.datadoghq.com_dists_stable_InRelease
-rw-r--r-- 1 root root 203425 Aug 26 16:26 /var/lib/apt/lists/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages
# diff -u /var/lib/apt/lists/partial/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages.decomp.FAILED /var/lib/apt/lists/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages
--- /var/lib/apt/lists/partial/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages.decomp.FAILED	2019-11-06 16:26:23.000000000 +0000
+++ /var/lib/apt/lists/apt.datadoghq.com_dists_stable_main_binary-amd64_Packages	2019-08-26 16:26:09.000000000 +0000
@@ -5314,29 +5314,3 @@
  forwards metrics from your applications as well as system services.
  .
  See http://www.datadoghq.com/ for more information
-
-Package: datadog-agent
-Version: 1:5.32.5-1
-License: Simplified BSD License
-Vendor: Datadog<EMAIL_ADDRESS>-Architecture: amd64
-Maintainer: Datadog Packages<EMAIL_ADDRESS>-Installed-Size: 334879
-Conflicts: datadog-agent-base (<< 5.0.0)
-Replaces: datadog-agent-base (<< 5.0.0), datadog-agent-lib (<< 5.0.0)
-Section: utils
-Priority: extra
-Homepage: http://www.datadoghq.com
-Filename: pool/d/da/datadog-agent_5.32.5-1_amd64.deb
-Size: 104802018
-SHA1: 2910d51f4f540b4fe1d7b1e6a06fcf18a227af00
-SHA256: cef68c0386d465075e7f4a46f2ed80fc9209db95b9489d51dbb227ce027a60dd
-MD5sum: 9af1ea4964187e0da36522102540a85e
-Description: Datadog Monitoring Agent
- The Datadog Monitoring Agent is a lightweight process that monitors system
- processes and services, and sends information back to your Datadog account.
- .
- This package installs and runs the advanced Agent daemon, which queues and
- forwards metrics from your applications as well as system services.
- .
 Done

Not sure whether it was a temporary issue with the repo back in Nov 6, or some bug in apt.
Let me know if you would like to get those lists, otherwise please feel free to close the issue.
Sorry for the noise. :)

Thanks for all the additional details here @defanator!
Interestingly there was an InRelease file in your local apt cache (/var/lib/apt/lists/apt.datadoghq.com_dists_stable_InRelease), dated Aug 26. This matches a change we did on the APT repo on that day to start providing an InRelease file on the repo, which was subsequently reverted after we found out that older versions of Debian (7 and below) and Ubuntu (12.04 and below) disable support of the InRelease file.
For some reason even after the InRelease file was removed from the repo, it appears that apt continued to read the InRelease file it had in its cache and trusted its contents, even though it was outdated.
In any case, what you did to resolve the issue, i.e. clearing the local cache of datadog-related repository metadata file (find /var/lib/apt/lists/ -name "*datadog*" -delete) and then re-running apt-get update, is indeed a good solution 👍
I'll go ahead and close this issue then, but feel free to comment here if anything new comes up, thanks!

I had the same issue while trying to upgrade my Linode server from Ubuntu 14.04 to 16. Luckily, find /var/lib/apt/lists/ -name "datadog" -delete) and then re-running apt-get update fixed the issue! Thanks.

This fix above didn't fix my problem, however, my goal was to just get this thing to work. So I updated my vagrant box to "ubuntu/focal64" which is ubuntu 20.04, so now it works


[4.3.2] confirmDate plugin is not working

confirmDate plugin is no longer working.
No errors on console.

Reproduction Link
https://flatpickr.js.org/plugins/#confirmdate
Your Environment

flatpickr version used: 4.3.2
Browser name and version: Chrome 65
OS and version: Ubuntu 16.04 x64

@ankurk91 works now


use style-resolve instead of ./lib/css-resolve

fixes: https://github.com/sheetify/sheetify/issues/57

also made a PR to style-resolve to update the deps and upgrade the version to 1.0.0: https://github.com/hughsk/style-resolve/pull/1
/cc @hughsk, but no rush. :smiley:

ACK :tada:

Released as v4.0.6 :tada: