[BUG] Time Jump in %H:%M:%S format

Bug report
Describe the bug
If I output the time in %H:%M:%S format, when 1 occurs in seconds, it jumps constantly, this was not the case on the original firmware Ulanzi TC001.
How can this be solved? Changing the font? Or an additional parameter in the settings?
Additional information

used Hardware:

ESP32
EspHoMaTriXv2 version: 2.0.0
Ulanzi TC001

To Reproduce
Steps to reproduce the behavior:
Output the time in %H:%M:%S format with the font MatrixClock-Chunky6.bdf.
Expected behavior
So that when outputting in %H:%M:%S format, the starting position is the same and does not change during output. The font is monospaced, so stable output is expected.
Configuration
font:
  - file: fonts/MatrixClock-Chunky8.bdf
    id: default_font
    glyphs:  |
      ! "#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz°
  - file: fonts/MatrixClock-Chunky6.bdf
    id: special_font
    glyphs:  |
      ! "#$%&'()*+,-./0123456789:APMTapmt

ehmtxv2:
  id: rgb8x32
  icons2html: true
  matrix_component: ehmtx_display
  time_component: ehmtx_time
  time_format: "%H:%M:%S"
  date_format: "%d/%m"
  default_clock_font: false
  show_seconds: false
  default_font_id: default_font
  default_font_yoffset: 8
  special_font_id: special_font
  special_font_yoffset: 7

Hey there.  I'm the creator of these fonts you're referring to. Actually, the one of Chunky6 is variable width.  If you look closely, you'll notice the colon also only uses 1 column and 1 space column...  I didn't realize that would pretty inconvenient, especially if you decide to display seconds.
Can you close this issue?  It's not an EHMTX issue... it's an issue with my font.  I've already changed the Chunky8 fonts so the numbers all have the same width... I'll change the Chunky6 font, too.  Check my repo and re-download what you need.  I'll have it updated in less than an hour.  https://github.com/trip5/MatrixClockFonts

Sidenote that I'm thinking I should create a slightly taller version of the Chunky fonts similar as I did with the X fonts and stretch everything to the full 6 pixel height.  That might make the numbers look better on our screens.  I don't really use the 6 pixel fonts, actually so it hasn't crossed my mind until now.  What do you think?

Check my repo and re-download what you need. I'll have it updated in less than an hour.

Thank you so much. Everything is great with the new font. I'll close the issue.

Sidenote that I'm thinking I should create a slightly taller version of the Chunky fonts similar as I did with the X fonts and stretch everything to the full 6 pixel height. That might make the numbers look better on our screens. I don't really use the 6 pixel fonts, actually so it hasn't crossed my mind until now. What do you think?

On the contrary, I liked the fonts with a height of 6 the most, they look harmonious on the screen, especially with icons and when displaying the time and date. If only text is displayed, a font height of 8 is good. I'm even thinking of making the font height 6 as the main font.
Can you tell me in what program you edit fonts, I lack the Ukrainian language, I want to add.

Solution - https://github.com/lubeda/EspHoMaTriXv2/issues/81#issuecomment-1720016043

Can you open another issue over there?  And tell me specifically what you're looking for.  By the way, ESPHome and BDF still appear to have issues with Unicode/UTF encoding but if the characters you want function in the 8-series fonts, we can probably work something out!


php artisan opcache:optimize not working

I've just been trying this to manage the opcache. As far as I can tell, opcache is working correctly (it appears in the phpinfo() as enabled, the site is indeed quicker with it enabled, and using the artisan command to get its status also confirms it is running and data is being cached when requested page-by-page)
That is filled from requesting pages normally in the browser. So it does work, but it means the first request is really slow after each change.
So I tried your 'php artisan opcache:optimize' command to pre-generate the cache before the first visit. But it reports 0 files as being optimized. Does that mean 0 are being cached? That doesn't sound right, but I may have misunderstood what it is trying to do or whether caching is separate to optimizing.
For example:
C:\apps\example.com>php artisan opcache:optimize
Optimize started, this can take a while...
0 of 930 files optimized
... and showing the stats command first to show it was working ...
...
Statistics:
+----------------------+---------------------+
| option               | value               |
+----------------------+---------------------+
| num_cached_scripts   | 1102                |
| num_cached_keys      | 2392                |
| max_cached_keys      | 130987              |
| hits                 | 15865               |
| start_time           | 2019-02-25 19:59:28 |
| last_restart_time    | 2019-02-25 20:12:48 |
| oom_restarts         | 0                   |
| hash_restarts        | 0                   |
| manual_restarts      | 2                   |
| misses               | 1102                |
| blacklist_misses     | 0                   |
| blacklist_miss_ratio | 0                   |
| opcache_hit_rate     | 93.505039193729     |
+----------------------+---------------------+

C:\apps\example.com>php artisan opcache:optimize
Optimize started, this can take a while...
0 of 930 files optimized

Hmm.
So I tried extracting the URL it seems to make, and requested that in the browser rather than the terminal. So the one like:
example.com/opcache-api/optimize?key=eybiglongkeyhere
That returns:
{
"result": {
"total_files_count": 930,
"compiled_count": 0
}
}

So the same result, but here is says 'compiled' rather than 'optimized'. Presumably that means the same.
The log does not contain any errors so it's not clear if it is trying to access routes and being blocked or quite what it is trying to do internally. Or perhaps it is working correctly, and 0 is not a problem (the misunderstood situation)?
Thanks!

I have excatly the same problem after upgrading to laravel 5.8.

Should be fixed in 3.0


Website Frontend

how I can contribute to your website frontend in Chic UI

@Nikhil27b Hey there! Currently the documentation of Chic UI hasn't been open-sourced as there is a lot of data to be added.
If you are looking for website frontend designing, you can check out my other project Tech Net
Thank you! 😄


Update search.md

fix Search and collecting link

A link on page search is invalid, I make some changes.

Nice! 👍


Remove windowsUsername and windowsPassword from Windows docs

https://www.pivotaltracker.com/story/show/120012575

Thanks, @benmoss!


JsonSettingStore: declare properties used dynamically

To avoid PHP 8.2 deprecation notes like:
DEPRECATED  Creation of dynamic property anlutro\LaravelSettings\JsonSettingStore::$files is deprecated in vendor/anlutro/l4-settings/src/JsonSettingStore.php on line 22.

DEPRECATED  Creation of dynamic property anlutro\LaravelSettings\JsonSettingStore::$path is deprecated in vendor/anlutro/l4-settings/src/JsonSettingStore.php on line 45.

Why public: is properties not declared, they are public by default. I didn't want to introduce a BC break.

Why it's important: such warnings create a lot of noise in logs

Thanks


Add icons/ directory from Apache HTTP Server.

From the included README:

Public Domain Icons
These icons were originally made for Mosaic for X and have been included in the NCSA httpd and Apache server distributions in the past. They are in the public domain and may be freely included in any application. The originals were done by Kevin Hughes (kevinh@kevcom.com). Andy Polyakov tuned the icon colors and added a few new images.

This should resolve the missing images from directory listings generated by the HTTPD serving guacamole.incubator.apache.org.

Yay icons :shipit:


Test PR #296

Ref: https://github.com/containers/automation_images/pull/296#issuecomment-1688750283

Hey @cevich as long as there's a new image-build PR, can we do something useful with it? Pasta is broken (see https://github.com/containers/podman/pull/19699), is there a dnf way to say "give me the older version"?

Hey @cevich as long as there's a new image-build PR, can we do something useful with it?

We can...though terminating a build in progress definitely leaks VMs.

is there a dnf way to say "give me the older version"?

I'd say we could just reference a specific version in the package list, but it's generic.  So the other Fedora releases would break or break soon.   I s'pose a complex/ugly conditional for all-three Fedora releases could be used.
Hmmm :thinking:
There's a downgrade sub-command, and it appears to still be in dnf5 (used by rawhide).  I'm afraid that may lead to some "interesting" future debugging if the FIXME change is never reverted.
Hmmm :thinking:
Just read your comment, that's odd, it's only affecting F38 and not rawhide?

Ahh, it's F38 and rawhide.  Hmmmm, maybe a !prior-fedora conditional could be used then.

Unless you understand the problem differently, I think maybe it's best to wait for @sbrivio-rh to chime in.  Maybe there's already a fix and this build will pick it up.  But if the problem is ugly/nasty/sticky then skipping the tests in Paul's PR may be a better bet.

Woops, we cross-posted:  I'm fine either way.  There's a chance my PR-table change is broken and I need to tweak this PR anyway.

Ref: workflow log


InterSystems IRIS

related issue #561
repo: https://github.com/daimor/realworld-intersystems-iris

Is there is anything I can do to get it merged?

Thanks, @daimor!
Apologies for the delay in reviewing your PR, the maintenance team had very limited availability and we've recruited new members to help with the project.
I added your backend implementation in #596 and merged it to master. The README should be autogenerated within 24 hours.

Thanks, @daimor!
Apologies for the delay in reviewing your PR, the maintenance team had very limited availability and we've recruited new members to help with the project.
I added your backend implementation in #596 and merged it to master. The README should be autogenerated within 24 hours.


radare2: 5.0.0 -> 5.1.1

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117327 at 3ae466ad run on x86_64-linux 1

3 packages built successfully:

python38Packages.r2pipe
python39Packages.r2pipe
radare2

1 suggestion:

warning: unused-argument
Unused argument: version_commit.
Near pkgs/development/tools/analysis/radare2/default.nix:25:5:
   |
25 |     version_commit, # unused
   |     ^


Add resource version section to api-concepts documentation

Clarify how resource version works, particularly the parameter on get, list and watch.
Clarify HTTP 410 Gone status codes work in conjunction with resource versions.
Add section about reflectors with pseudo-code for how to correctly "list and watch" from a client without "going back in time".

https://5da654db8fa033000817e6eb--kubernetes-io-vnext-staging.netlify.com/docs/reference/using-api/api-concepts/

@wojtek-t @smarterclayton @liggitt Looking for reviewers for this.

Accidentally rebased on master. i've fixed it and rebased on dev-1.17, but the language labels have all been added and I'm unable to remove them.

@liggitt Feedback applied. Thanks for there review pass! I've dropped the pseudo-code given how complex it was.

/remove-language de es fr id ja ko zh

@wojtek-t @liggitt  This is ready for another review pass.

@liggitt Is this PR good to go?

@jpbetz Can you look into @wojtek-t comment?

@jpbetz Can you look into @wojtek-t comment?

Feedback applied.

LGTM - but I think @liggitt should be the one approving it.

/lgtm
/approve

Thanks for the review @liggitt. I've opened https://github.com/jpbetz/website/pull/new/resource-version-concepts-fixup with the fixes.


Defines the regexp variable

Bug: The regexp variable is never defined, causing the modal to not be executed! That means that caseinsensitive validation and validation with regex would never work. Just tested that this works with the following:

Whoops! Thanks :smile: :beers:


Add the ability to use wildcards for uploading files.

Allow multiple files to be uploaded, either from a list, or from wildcard expansion.
Many build systems create artifact files that do not have a name known before hand, and may want to publish multiple files.
For example, a zip filename that includes the tag, or the branch that it was created from, or even for what environment it is built for (Windows / MacOS / iOS / Android / etc.)   And adding supporting files, such as an MD5 / SHA1 file, or a signature file.
This would probably require removing the 'asset_name' and 'asset_content_type' attributes to have these generated by this action.
IE:
asset_path: |
path/to/files/*.zip
path/to/files/special_file_name

Dup of #47. Ref #58.

I would also be supportive of this
@opussf if it's of use to you, feel free to use: https://github.com/marketplace/actions/upload-release-assets

Hey @alexellis, looks good. Do you consider to add a way to define the tag for upload manually? Or using ${{ github.event.release }} object for it?

I would accept a PR for that 👍

@opussf You can accomplish this by setting an environment variable and then using it?
      - run: echo "FOO=$(echo hello)" >> $GITHUB_ENV
      - name: Upload windows Release Asset
        uses: actions/upload-release-asset@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          upload_url: ${{ steps.create_release.outputs.upload_url }}
          asset_path: pcb2gcode-windows/pcb2gcode-${{ env.FOO }}.tar

But still, having wildcard support would be nice.  It's not clear to me how you would specify multiple asset_names for multiple asset_paths.

@opussf You can accomplish this by setting an environment variable and then using it?
      - run: echo "FOO=$(echo hello)" >> $GITHUB_ENV
      - name: Upload windows Release Asset
        uses: actions/upload-release-asset@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          upload_url: ${{ steps.create_release.outputs.upload_url }}
          asset_path: pcb2gcode-windows/pcb2gcode-${{ env.FOO }}.tar

But still, having wildcard support would be nice.  It's not clear to me how you would specify multiple asset_names for multiple asset_paths.

As a workaround, I have been using @alexellis's alexellis/upload-assets. For example (source):
  release:
    steps:
      - id: create_release
        uses: actions/create-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ github.ref }}
          release_name: ${{ github.ref }}

      - uses: actions/download-artifact@v2
        with:
          name: gmp

      - uses<EMAIL_ADDRESS>        # ✨✨✨
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          asset_paths: '["./gmp/*"]'

As a workaround, I have been using @alexellis's alexellis/upload-assets. For example (source):
  release:
    steps:
      - id: create_release
        uses: actions/create-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ github.ref }}
          release_name: ${{ github.ref }}

      - uses: actions/download-artifact@v2
        with:
          name: gmp

      - uses<EMAIL_ADDRESS>        # ✨✨✨
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          asset_paths: '["./gmp/*"]'

But if you have wildcards, where does the name come from?  Just from the file name?  What if multiple files with the same name match?

But if you have wildcards, where does the name come from?  Just from the file name?  What if multiple files with the same name match?

I make sure to have different file names 👍

I make sure to have different file names 👍

@eyal0, very honestly, use pyGitHub or any other library for your favourite language and write your own script/action. If you know how to code (I believe you do), doing so will be easier and less frustrating than trying to use this Action. See:

#58
eine/tip
msys2/msys2-autobuild was initially based on eine/tip, but was then customised. It uses the same Python library (pyGitHub), but the internal logic is completely different (adapted to MSYS2's non-trivial ecosystem).

@eyal0, very honestly, use pyGitHub or any other library for your favourite language and write your own script/action. If you know how to code (I believe you do), doing so will be easier and less frustrating than trying to use this Action. See:

#58
eine/tip
msys2/msys2-autobuild was initially based on eine/tip, but was then customised. It uses the same Python library (pyGitHub), but the internal logic is completely different (adapted to MSYS2's non-trivial ecosystem).

@eine I ended up using a different action which already includes an upload feature.  It uses some javascript libraries which are probably the equivalent of pyGitHub.
(I'm using msys2 to auto-release Windows builds with dozens of dlls and with great success.  Thanks for msys2-setup!)

@eine I ended up using a different action which already includes an upload feature.  It uses some javascript libraries which are probably the equivalent of pyGitHub.
(I'm using msys2 to auto-release Windows builds with dozens of dlls and with great success.  Thanks for msys2-setup!)

@eyal0, all the libreries interact with the same API, so all of them are equivalent. I just referenced the Python because that's the one I'm more familiar with. The JS one is probably one of actions/toolkit#334, and that's ok too.
(So glad to hear that!)

@eyal0, all the libreries interact with the same API, so all of them are equivalent. I just referenced the Python because that's the one I'm more familiar with. The JS one is probably one of actions/toolkit#334, and that's ok too.
(So glad to hear that!)

I now used this action


🚑 Emergency bugfix for config migrator

Category
Emergency Bugfix

I will already merge this, as this is an urgent hotfix and shouldn't break anything. Sorry that I'm skipping your review.


[Bug] CI non-rust-lint failing with "sudo: command not found"

🐛 Bug
While trying to land a PR (#9633), I got a report of a failed lint from CI:
https://github.com/diem/diem/runs/4168151259?check_suite_focus=true
The non-rust-lint step is failing with:
CARGO_HOME=/opt/cargo
RUSTUP_HOME=/opt/rustup
/__w/_temp/4eb2382c-901a-4a21-87dc-5ff8d8627203.sh: line 16: sudo: command not found
/__w/_temp/4eb2382c-901a-4a21-87dc-5ff8d8627203.sh: line 17: sudo: command not found
Error: Process completed with exit code 127.
Expected Behavior
My PR doesn't touch anything related to this, so I assume the lint should pass.
System information
N/A

@sausagee explained to me that this was due to a temporary workaround that has since been reverted. I rebased my PR and this problem went away.


Helm Chart: --set extraEnv.LOGDNA_LOG_DIRS=/var/log/containers yields error

Trying to use extraEnv to change LOGDNA_LOG_DIRS.
Use the set above but end up with:
Error: INSTALLATION FAILED: YAML parse error on agent/templates/daemon_set.yaml: error converting YAML to JSON: yaml: line 59: did not find expected '-' indicator

Could not find any example of the proper way to utilize extraEnv

any help or improvements here ?
Thanks

Any improvement/update on this even i facing the same error
Thanks


Error on docker-compose build under Windows

Summary
An error shows up when docker-compose build is launched in the root directory, causing the installation to fail.
Steps To Reproduce

Clone the repository.
In the root folder, type docker-compose build

Expected behavior
A working installation of Parsr.
Actual behavior
https://gist.github.com/aarohijohal/804196e1f308fd6054eac22201e7892f
Environment

OS: Windows
Other details can be extracted if need be

Duckling is no more needed in latest version of parsr.
Also, it's no more needed to build the docker images as they are published on the docker hub (latest version of the docker-compose file reflect that)


Allow use of system setuptools.

I'm assuming this will need some massaging to be completely acceptable but I use this on Fedora.

Hi hobbes1069 ,
That's a good idea to try using an already installed setuptools. But the pull request does not compile, and I have few questions concerninf the proposed changes.

I've got PYGLUE turned off as there are not any consumers of the python module at this time. I guess I could just use python2 then but I don't think that would address the above error.

Ok, I tried building master but got the message I have to build the bindings if the docs are to be built. It may be easiest just to drop the docs for now. As of Fedora 30 (in beta) only providing python2 modules is not allowed due to the impending EOL of Python2.
Feel free to drop this PR for now. Maybe I'll pick it back up once Python3 is supported.

[Potential solution]
The mix between external and compiled Python packages requires two disctint PYTHONPATHs.
A solution could be to configure like that:
set(PYTHONPATH "${EXTDIST_ROOT}/lib${LIB_SUFFIX}/python${PYTHON_VARIANT}/site-packages:${EXTERNAL_SETUPTOOLS_PATH}")


HotTable with webpack

Hi, thank you for creating react compatible handsontable! Looks very promising and I would love to give it try.
One question I had is how to deal with webpack with react-handsontable. I was able to fix original Handsontable webpack issue by implementing solution provided here. However when I try to use HotTable, error says "handsontable is not defined" and I won't be able to display table.
Is there any way to fix this issue by any chance? Seems like react community is already set to use webpack as a default option going forward and not been able to work with it as an out-of-the-box support is little bit painful. I really would love to use handsontable with react webpack :) Your feedback would be really appreciated.

@masato-io,
Currently, I'd suggest using the expose-loader in webpack to expose Handsontable and its dependencies to the global context. I know this solution isn't ideal, but it's a workaround.
Basically, in webpack.config.js, you'd have to set up your loaders like this:
[
// other loaders...
  {
    test: require.resolve('handsontable'),
    loader: 'expose-loader?Handsontable'
  },
  {
    test: require.resolve('numbro'),
    loader: 'expose-loader?numbro'
  },
  {
    test: require.resolve('moment'),
    loader: 'expose-loader?moment'
  }, {
    test: require.resolve('pikaday'),
    loader: 'expose-loader?Pikaday'
  }, {
    test: require.resolve('zeroclipboard'),
    loader: 'expose-loader?ZeroClipboard'
  }
]

And then, in your .jsx file import all of them as follows:
import moment from 'moment';
import numbro from 'numbro';
import pikaday from 'pikaday';
import Zeroclipboard from 'zeroclipboard';
import Handsontable from 'handsontable';
import HotTable from 'react-handsontable';
import 'handsontable/dist/handsontable.full.css';

(to import the .css file the css-loader might come in handy)
When we have something less invasive ready, we'll update react-handsontable to work with it as well.

@jansiegel thank you for your response! Yes, your solution worked well and now I can see HotTable working!! excited to dive into react-handsontable adventure :)

As my question is clearly answered, I'm closing out this ticket. Thanks.

Is this still necessary?

Hi @panesofglass
I'm not an expert but the wrapper hasn't been updated for a year so this tip may still be useful

I just tried it without, and it seems to no longer be required. The reason I asked is the wiki does not indicate the expose-loader is necessary.


docker_image broken on names.w.dots

uh, no idea what's going on here, but i'm getting this error on both cases where we try to pull from a private repo; though the docker_image resource is working for the centos image?!
           ================================================================================
           Error executing action `pull_if_missing` on resource 'docker_image[workspaces-web]'
           ================================================================================

           Docker::Error::ArgumentError
           ----------------------------
           Must have id, got: {"id"=>nil, :headers=>{}}

           Cookbook Trace:
           ---------------
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/base.rb:16:in `initialize'
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `new'
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `create'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:55:in `pull_image'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:105:in `block in <class:DockerImage>'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:111:in `block in <class:DockerImage>'

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/treehouse-docker/recipes/workspaces.rb

            56:   docker_image "workspaces-#{img}" do
            57:     repo fqdi
            58:     tag 'production'
            59:   end
            60: end

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/treehouse-docker/recipes/workspaces.rb:56:in `block in from_file'

           docker_image("workspaces-web") do
             action [:pull_if_missing]
             retries 0
             retry_delay 2
             default_guard_interpreter :default
             declared_type :docker_image
             cookbook_name "treehouse-docker"
             recipe_name "workspaces"
             repo "treehouse/workspaces.env.web"
             tag "production"
           end

we're definitely logged in and can successfully pull from the command-line :/. fwiw, we're using docker 1.7.1

Hi.
Sorry, this changed recently to match the docker remote-api The new syntax is:
docker_image 'fqdi/workspaces-web'
or
docker_image 'a chef resource name' do
repo 'fqdi/workspaces-web'
tag 'latest'
end

hi @someara, yeah, the resource above is the version we'd changed to match the new resource, but we still got this problem.
the resource as described in the recipe looks like:
docker_image 'workspaces-web' do
  repo 'treehouse/workspaces.env.web'
  tag 'production'
end

which seems to match what you described?

maybe this is a bug in the docker-api gem, then?

It's more likely a bug in my usage of it.
I don't think I tested names with dots in it... are those even allowed?
So far its been tested against all this:
https://github.com/bflad/chef-docker/blob/5883cbe3ffd680af637b04b88f2331d1f9b52038/test/cookbooks/docker_test/recipes/image_lwrp.rb

it's definitely allowed; i'm pulling down a copy to test that recipe against and see if i can reproduce, will report back with any findings

mmmmm yep; definitely something about the dot:
       Recipe: docker_test::image_lwrp
        (up to date)

           ================================================================================
           Error executing action `pull_if_missing` on resource 'docker_image[Tom's container]'
           ================================================================================

           Docker::Error::ArgumentError
           ----------------------------
           Must have id, got: {"id"=>nil, :headers=>{}}

           Cookbook Trace:
           ---------------
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/base.rb:16:in `initialize'
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `new'
           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `create'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:59:in `pull_image'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:109:in `block in <class:DockerImage>'
           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:115:in `block in <class:DockerImage>'

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb

             9: docker_image "Tom's container" do
            10:   repo 'tduffield/testcontainerd.b'
            11: end
            12:

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb:9:in `from_file'

           docker_image("Tom's container") do
             action [:pull_if_missing]
             retries 0
             retry_delay 2
             default_guard_interpreter :default
             declared_type :docker_image
             cookbook_name "docker_test"
             recipe_name "image_lwrp"
             repo "tduffield/testcontainerd.b"
             tag "latest"
           end

i guess we can rename our images without too much trouble, but it's definitely weird, because we'd previously been running this with the shell-out version of the cookbook without bumping into this.

Thanks!
For your reference, its consumed here:
https://github.com/bflad/chef-docker/blob/5883cbe3ffd680af637b04b88f2331d1f9b52038/libraries/provider_docker_image.rb#L58
... and ends up in an opts hash here
https://github.com/swipely/docker-api/blob/0735e4eb54176d0e39ef1eec129bbb91d65d579b/lib/docker/image.rb#L105
... which seems to be exactly what the docker cli was doing
https://github.com/docker/docker/blob/34a17a5de1d01a42e3e0173e5565b7de1af95bda/api/client/pull.go#L48-L51

maybe it needs a shellwords escape or a %2E translation somewhere?
On Sat, Aug 8, 2015 at 7:03 PM, Nathan Williams<EMAIL_ADDRESS>wrote:

mmmmm yep; definitely something about the dot:
   Recipe: docker_test::image_lwrp
    (up to date)

       ================================================================================
       Error executing action `pull_if_missing` on resource 'docker_image[Tom's container]'           ================================================================================           Docker::Error::ArgumentError           ----------------------------           Must have id, got: {"id"=>nil, :headers=>{}}           Cookbook Trace:           ---------------           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/base.rb:16:in `initialize'
       /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `new'           /tmp/kitchen/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.0/lib/docker/image.rb:117:in `create'           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:59:in `pull_image'
       /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:109:in `block in <class:DockerImage>'           /tmp/kitchen/cache/cookbooks/docker/libraries/provider_docker_image.rb:115:in `block in <class:DockerImage>'           Resource Declaration:           ---------------------           # In /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb             9: docker_image "Tom's container" do            10:   repo 'tduffield/testcontainerd.b'            11: end            12:            Compiled Resource:           ------------------           # Declared in /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb:9:in `from_file'           docker_image("Tom's container") do             action [:pull_if_missing]             retries 0             retry_delay 2             default_guard_interpreter :default             declared_type :docker_image             cookbook_name "docker_test"             recipe_name "image_lwrp"             repo "tduffield/testcontainerd.b"             tag "latest"           end

i guess we can rename our images without too much trouble, but it's
definitely weird, because we'd previously been running this with the
shell-out version of the cookbook without bumping into this.
—
Reply to this email directly or view it on GitHub
https://github.com/bflad/chef-docker/issues/356#issuecomment-129062039.

yeah, i think something's going wrong in the assignment here, but it's going to take me a while to debug, and at this point i'm pretty convinced that this is actually a bug in docker-api, even if it is needing to do the URI escaping (definitely a hunch worth tracking down). i don't want to waste your time on our edge-case if it's not a problem in your cookbook, so feel free to close this out and i'll pursue it with upstream once i nail it down. thanks for helping track it this far!

by the way, love the cookbook improvements that have been landing lately, keep up the kickass work!

thanks!
-s

I'm running into this problem too. My image name doesn't have a period in it though, but it does have a hyphen, like orgname/base-image. My docker_image block looks like this:
docker_image 'orgname/base-image' do
  repo 'orgname/base-image'
  tag 'latest'
  action :pull
end

@nathwill have you found any solutions for this?

@mrdziuban not yet; for now we've reverted and pinned to docker cookbook version 0.37. it's on the TODO list, but... sooooo busy right now >__<

Thanks, v0.37.0 worked for me as well! I'll stick to that for now.

Hi.
I can't seem to reproduce this username/name-with-dashes thing.
I've added dots and dashes to various image names in the test recipe here
https://github.com/bflad/chef-docker/commit/f43c12fe46ca5ac0db660d0aa53d4cf7fa8ed7b1
I can pull "hello-world', from the public hub, and both push-and-pull "someara/name-w-dashes".
While I was in there, I verified the name.w.dots fails for reference.
-s

Actually, for name.w.dots, I'm getting a silent failure, not a Docker::Error::ArgumentError

renaming this issue for my own sanity

@someara I'm still having trouble pulling an image named username/name-with-dashes on v0.43.0. This is all that my cookbook is doing:
docker_service 'default' do
  action [:create, :start]
end

docker_registry 'https://index.docker.io/v1/' do
  username 'USERNAME'
  password 'PASSWORD'
  email 'EMAIL'
end

docker_image 'IMAGE_NAME' do
  repo 'IMAGE_NAME'
  tag 'latest'
  action :pull
end

I still get the error:
Must have id, got: {"id"=>nil, :headers=>{}}

Update on my situation:
It seems that it's not related to the dashes in the name. I think my issue actually has to do with slashes in the name, i.e. pulling from an organization's repo. I created this public test repo to demonstrate the issue. Try using this to pull the image:
docker_image 'mrdziuban/testrepo' do
  repo 'mrdziuban/testrepo'
  tag 'latest'
  action :pull
end

I've just encountered the same thing, but in my case the workaround was to remove the tag from the resource. No dots here: the image in this case is carevoyance/qubit-bamboo and the tag is simply latest.
Here's the Chef block I'm using, nothing unusual:
docker_image node[:bamboo][:docker_image] do
    action :pull
    tag node[:bamboo][:version]   # Works only when this is commented out.
end

And the compiled version:
 docker_image("carevoyance/qubit-bamboo") do
   action [:pull]
   retries 0
   retry_delay 2
   default_guard_interpreter :default
   declared_type :docker_image
   cookbook_name "cv_mesos"
   recipe_name "qubit-bamboo"
   tag "latest"
   api_retries 3
   repo "carevoyance/qubit-bamboo"
 end

I'm seeing the same behavior with the amazon/amazon-ecs-agent image on Docker Hub.
ubuntu 14.04
chef-client 12.4.1
docker cookbook 1.0.18
  * docker_image[amazon/amazon-ecs-agent] action pull

    ================================================================================
    Error executing action `pull` on resource 'docker_image[amazon/amazon-ecs-agent]'
    ================================================================================

    Docker::Error::ArgumentError
    ----------------------------
    Must have id, got: {"id"=>nil, :headers=>{}}

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.2/lib/docker/base.rb:16:in `initialize'
    /var/chef/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.2/lib/docker/image.rb:117:in `new'
    /var/chef/cache/cookbooks/docker/files/default/vendor/gems/docker-api-1.22.2/lib/docker/image.rb:117:in `create'
    /var/chef/cache/cookbooks/docker/libraries/provider_docker_image.rb:75:in `pull_image'
    /var/chef/cache/cookbooks/docker/libraries/provider_docker_image.rb:137:in `block in <class:DockerImage>'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/r5-ecs-host/recipes/ecs_agent.rb

     25: docker_image 'amazon/amazon-ecs-agent' do
     26:   action :pull
     27:   notifies :redeploy, 'docker_container[ecs-agent]'
     28: end
     29:

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/r5-ecs-host/recipes/ecs_agent.rb:25:in `from_file'

    docker_image("amazon/amazon-ecs-agent") do
      action [:pull]
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      declared_type :docker_image
      cookbook_name "r5-ecs-host"
      recipe_name "ecs_agent"
      tag "latest"
      api_retries 3
      repo "amazon/amazon-ecs-agent"
    end

From my recipe:
# I've tried numerous variations on this using both 'latest' and 'v1.4.0'
# for the tag and including or not including the repo attribute. All behave the same.
docker_image 'amazon/amazon-ecs-agent' do
  action :pull
  notifies :redeploy, 'docker_container[ecs-agent]'
end

docker_container 'ecs-agent' do
  image 'amazon/amazon-ecs-agent'
  env %W(
    ECS_LOGFILE=/log/ecs-agent.log
    ECS_DATADIR=/data
    ECS_CLUSTER=#{node['amazon-ecs-agent']['cluster']}
    ECS_ENGINE_AUTH_TYPE=#{node['amazon-ecs-agent']['engine_auth_type']}
    ECS_ENGINE_AUTH_DATA=#{node['amazon-ecs-agent']['engine_auth_data'].to_json}
  )
  volumes([
    "/var/run/docker.sock:/var/run/docker.sock",
    "#{node['amazon-ecs-agent']['log_dir']}:/log",
    "#{node['amazon-ecs-agent']['data_dir']}:/data"
  ])
  port '51678:51678'
  detach true
end

Hmmm, ok... So, in my case, adding tag and repo attributes works if I'm not otherwise authenticated to a private registry.

@dimfeld Can you test if you're running into #379 ?

#379 only applies if you've authenticated to a private registry, right? In my case I do have a private registry set up, but there's no authentication involved. (That is, I'm not using the docker_registry resource or anything similar.)
I did try removing all recipes that use the private registry from the runlist and it didn't make a difference. Is that sufficient to rule it out?

Well... it's definitely a clue. Are you pulling from public, then private? Or private, then public? Or..

It was private, then public. The problem occurred in odd clusters. It would fail for a while, and then start working again, and then fail again, and now it works, with no changes in any of the docker-related stuff. I was messing around with some DNS configuration but the cookbook should have failed well before it got to the docker stuff if that wasn't configured right.
Unfortunately, I'm not able to get it to reproduce tonight, so I'm not sure if I can do anything else to help for now, but I'll chime back in if I see this again.

This should be fixed in v1.0.21... patched the docker-api gem via #379


Fix memory dom

Codecov Report

Merging #1137 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1137   +/-   ##
========================================
  Coverage    59.99%   59.99%
========================================
  Files          377      377
  Lines        13977    13977
========================================
  Hits          8385     8385
  Misses        5592     5592

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 655f593...e285df0. Read the comment docs.


BUG: Unsupported keyboard key for playing the next song

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The Next Button ">>" for playing the next song does not support next key click on the keyboard.
Adding a Javascript code can make it easy for the users to play the next song
Kindly assign me this issue.
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Varnika2526 Currently for playing React music component is begin used and it have limited functionality. If you can come up with a new alternative option which is better than this component feel free to contribute.

Hi @Varnika2526, could you assign me the task of fixing the unsupported keyboard key bug for playing the next song? Please tag it with GSSOC. Thanks!

@Varnika2526 Can you please assign me this task

Hey, I would like to work on the same. Can you please assign this to me under GSSoC'24.

@Varnika2526 any updates varnika

@Satyam1923 I had modified the Pause/Play feature that works well by pressing "space" key on keyboard
I am attaching a clip for the same kindly review it
https://github.com/Satyam1923/Spring-Music-Player/assets/106170225/7c828c59-953a-4f7d-a94e-7d7dc2383816


Add .asn1 dependencies for files generated from providers/common/der/*.in

This pull request is ready to merge

Merged
e378be2a29f8bc5e679e63d5f5e9766d2f4dfc4b Add .asn1 dependencies for files generated from providers/common/der/*.in


Change Rancher Server path to a custom path

I'd like to serve my Rancher web interface could be served on a custom path, like example.com/rancher, instead of serving it on example.com:8080/.
I've tried setting up a reverse proxy with Apache, using some mod_rewrite rules and some mod_substitute rules (not necessarily together), but failed.

This is not currently possible, but easy to implement because the UI is 100% static files, and is not likely to be added.  Sharing unrelated applications on the same origin is a bad idea for security because you are likely leaking cookies one way or the other.

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it


Preserve formatting for About tab on User Profiles; Item descriptions

On About page for stores your description doesn't preserve formatting (i.e. line breaks)

Finished


Mix_PausedMusic return int vs. SDL_bool.

Would it make sense for Mix_PausedMusic to return a SDL_bool instead of an int?
According to the wiki, the int can only have 1 or 0.

Yes. :)


Changing The texture pattern of the palm in "icubSim"

Hello,
Is it possible to change the texture pattern in the right or left palm of the simulator?
To add an arbitrary image from a file?
Thanks

Does anybody have any good clue on this?

@martz21 might know

Hello Everyone,
I was managed to change the texture pattern titled "bluetexture.bmp" in \iCub\contexts\simConfig\models, and attach an arbitrary image to the palm. That'll do for now
Thanks for the help.


Are the parse trees generated with the Earley algorithm with rule priority consistent?

What is your question?
Are the parse trees generated with the Earley algorithm with rule priority consistent? What is guaranteed?
In an expression like:
x ^ 3 * y + x ^ 2 * y ^ 2 + x ^ 2 * y + x * y ^ 2
With priority ^, *, + in decreasing order,
There are (I believe) multiple parse trees that would be consistent with this expression. How is this ambiguity resolved? Is it deterministic, and can I assume that for very similar expressions, the parse tree will have the analogous structure?
For example, will:
x ^ 4 * y + x ^ 2 * y ^ 2 + x ^ 2 * y + x * y ^ 2 (higher power)
or
x ^ 2 * y ^ 2 + x ^ 2 * y + x * y ^ 2 (first term removed)
Have the same structure, apart from the difference in the expression?

That depends on your grammar. IG, yes it should be consistent, but your grammar might make it not be.

What are features of the grammar that would cause inconsistent parsing?
I'm currently using this grammar:
"""?start: expression
            ?expression: atom
            | addition
            | multiplication
            | power
            | parentheses

            ?atom: WORD | NUMBER

            ?power.3: expression "^" expression -> pow

            ?multiplication.2: expression "*" expression -> mul

            ?addition: expression "+" expression -> add

            ?parentheses: "(" expression ")"

            %import common.NUMBER
            %import common.WORD
            %ignore " "           // Disregard spaces in text
         """,

This should make it consistent. The problem occurs when you have any ambiguity that isn't forced. But I would suggest looking at the calculator example or the python.lark file for a better way to deal with operators.

It's supposed to be consistent, but it's possible that there are still some edge cases in which it's not. Like @MegaIng said, if at all, it comes out in highly ambiguous grammars.

Thank you both for the quick replies.
@MegaIng, regarding your comment on operator handling, do you mean replacing the priorities by making the operator with highest priority be the first option that the algorithm comes across? In the calc example, the "product" operations are closer to the atom level (I'm not sure what the terminology is here). That should allow me to use LALR for better performance, correct?

Yes, it allows you to use LARL. It removes any kind of ambiguity:
start: add
?add: (add "+")? mul
?mul: (mul"*")? atom

When we see a 1 + 2 * 3 it has to be understood as 1 + (2 * 3), since the grammar doesn't allow anything else. (1 + 2) * 3 is not a possible interpretation: mul can not have an add as child, except in parentheses from inside mul.

I think I understand. I tried to generalize from the calculator example. Is this what you meant?
"""?start: sum

                        ?sum: product
                        | sum "+" product -> add

                        ?product: power
                        | product "*" power -> mul

                        ?power: atom
                        | power "^" atom -> pow

                        ?atom: NUMBER
                        | WORD
                        | "(" sum ")"

                        %import common.NUMBER
                        %import common.WORD
                        %ignore " "           // Disregard spaces in text
                     """

Yes

It's much faster and achieves the consistency that I was looking for. Thank you for being so helpful!


Upgrade dependency 'jackson-core' to v2.8.11

Upgrade jackson-core to version 2.8.11

Fixed with the following PR:

https://github.com/wso2-extensions/identity-governance/pull/874


issues with 'Open multiple projects in one window' in WebStorm

In WebStorm 2019.2 (released just a few days ago) they added a really cool and usefull feature (https://www.jetbrains.com/webstorm/whatsnew/) called "Open multiple projects in one window".
This feature allows to have multiple projects opened at the same window, and as such the git context is changed based on what project the file you are currently working on belongs to.
When I start working on an issue, and open a new branch for it using this awesome plugin, it creates the feature branch to ALL open projects - which we can discuss if it good or bad. But what really bothers me is that when you finish with the issue and change the task back to the default task, it only restores the current working branch on the current project context, leaving all other projects stuck on the feature branch... Which of-course leads me to changing them all back to the master branch manually (and for 13 projects it takes a long time)
I'm not sure if this is an issue with WebStorm tasks management, or with the plugin itself. @jk1 do you have any idea what went wrong here?

I think the best solution here is to only checkout the branch in the current git context.
As to task managment - the solution should be based on how webstorm handled the tasks context and sadly I don't know anything about it. We do need to consider working on the same issue on multiple projects simultaneously while allowing to remove a project from the task when you are done with it, without closing the task.

Might be a WebStorm only issue. I opened a bug there - https://youtrack.jetbrains.com/issue/JT-53570

@regevbr right you are, this part is managed by a bundled Task Management plugin


Fonts are huge after 3eaf12

This commit bumped font sizes and, in my opinion, you've gone to the extreme.
On Desktop it feels just a little big, but really not anything that should cause problems. However, on mobile this change seriously impacts readability. The change has seriously diminished the amount of content that fits on screen.

In my opinion, this change is unnecessary on the desktop and hurtful to mobile.
I would like to see the change just reverted, but I realize CSS can handle text sizes. However, I really don't think I should need to maintain a theme to make the mobile client usable.
Thanks

However, on mobile this change seriously impacts readability. The change has seriously diminished the amount of content that fits on screen.

I understand about the reduced amount of content (though 25 lines as shown on your screenshot is still more than what Telegram would show you for example) but readability is better as it is right now, as in it's less hard to read.
I'm going to run some more tests to tweak the current size, but I am certainly against a simple revert.

Resolved by #1561.


youcompleteme faled with autotools project

I build a compilation database with bear for an autotools project and I get the following error:
[Error - 10:01:04] Request textDocument/codeAction failed.
  Message: Request textDocument/codeAction failed with message: Network failed
  Code: -32603

The error occurs by clicking on function or variables.
Where can I get more information about the error?
Are there log files?

My   .ycm_extra_conf.py was not loaded. Now it works!
How can i set automatic loading by each workspace?
I tried "ycmd.confirm_extra_conf": true in the .vscode/settings.json but this is not working.

Of course ycmd.confirm_extra_conf should be false.


Nagios - Change references of ci.adoptopenjdk.net to ci.adoptium.net - check_agent_plugin

Update the nagios server plugin check_agent to use the new URL.
Ref: Issue #2932

[X] commit message has one of the standard prefixes
[X] VPC/QPC not applicable for this PR

@steelhead31 I've already made this change as part of https://github.com/adoptium/infrastructure/pull/2942

@steelhead31 I've already made this change as part of #2942

I'll close this then :)


Cursor sets incorrect for non text nodes

When I change text to the image (or other tag) node I have problem with cursor
I do it in decorator:
return new CompositeDecorator([
    {
        strategy: findSpecialText,
        component: imgSpan
    }
]);

imgSpan:
return (

 );

It works but cursor sets in random place. Sometimes after image, sometimes before text line etc.
It works correct if I use children. But I need only image instead children text. If set display:none for children cursor also sets incorrect
return (

        {props.children}

 );

Check it in the Chrome/FF (Ubuntu/Windows)

The same problem: https://github.com/facebook/draft-js/issues/627

Thanks for reporting this and for linking to related issues! We would love to see a PR addressing this, or some work-arounds for other folks running into it. I don't think we have seen this problem in our internal uses of Draft (in 17+ apps), so I will try to look for what work-around we may have.


Specify main modules for elm make

If my understanding is correct it's currently necessary to specify all main modules that will be using ports to elm-make. For example:
elm-make Components/ComponentA/Main.elm Components/ComponentB/Main.elm
If left unspecified, it will result in an build error that says there cannot be multiple main modules. Something like this:
This module has ports, but ports can only appear in the main module.

89│ port tasks : Signal (Task Never ())
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ports in library code would create hidden dependencies where importing a module
could bring in constraints not captured in the public API. Furthermore, if the
module is imported twice, do we send values out the port twice?

I'm not sure what the appropriate solution is. Considering you specify the path to a single Main module via require.
require('Components/ComponentA/Main.elm')
require('Components/ComponentB/Main.elm')

It would seem that if you did this you'd output the entire Elm core run-time with each component.

This is true. I can think of a couple of ways of fixing it. Give me a day and ping me again if I haven't replied.

I'm interested in what your thoughts are. I think we need to start with extending node-elm-compiler with the ability to build multiple main files.
https://github.com/rtfeldman/node-elm-compiler/issues/26

I've taken a shot at what I think could be a possible solution to handle multiple main files:
https://github.com/joeandaverde/elm-project-loader

This kind of tooling shouldn't be part of a separate loader. I'm also not convinced about introducing the elmproj file. Here are my thoughts, however:

Since we can find all our deps thanks to the node-elm-compiler, it's trivial to get all the Elm modules that aren't main
Each module should be compiled to JS as a separate entity. This is what the elm compiler does internally.
As each Elm module is now a webpackable module, it will be trivial to share library code between each Elm main file
This solves the biggest problem of having multiple mains

I'm interested in an approach to share elm-core between separate require invocations. One of my concerns is that building each file separately will result in that many elm-core modules output in the bundle.
Due to the potential for dead code elimination in the future, my understanding is that modules are unlikely to be separated from elm-core. This seems to require me to build several main files in the same output.
I'm pressed for time to move on from this so I put together what achieves my immediate need.

I'm interested in an approach to share elm-core between separate require invocations. One of my concerns is that building each file separately will result in that many elm-core modules output in the bundle.

Yeah, this is possible. The main difference is doing the concat manually rather than through elm-make. I think it would take me about 3 hours to do. If I get around to it, I'll ping you

@eeue56 Did you get around to doing this? I'm currently researching filesize savings for multiple Elm main modules in our Angular app, but it seems I have to remove duplicate core-and-libraries functions by hand somehow - dead code elimination from Google Closure Compiler doesn't delete it. I wonder if there's a better way... :)

@Janiczek Do you think you could post about this on elm-discuss? There are a variety of "this would make compiled output smaller" ideas floating around, but not a lot of concrete motivating use cases - and it sounds like you have one!

@rtfeldman My problem got solved - Evan told me how to invoke elm-make so that it generates one JS file with both Main modules that share libraries: https://twitter.com/czaplic/status/769199156158083072
Honestly I don't know why I didn't try that before :)

Oh, I just recently tried adding Elm to an existing (and big) application little by little. With one module I had zero problems, but now I have two, and the duplication is running wild... Not only the core modules of Elm are duplicated, but also the modules themselves: I have an Elm module A that is imported in JS and then an Elm module B that imports module A directly from the Elm code and the module B itself is imported in JS...
@Janiczek Were you able to solve the problem only by means of "elm make"? Our application is also Angular mobile that uses webpack and I was hoping I'll be able to use the elm-webpack-loader to gradually introduce Elm module here and there. While the code works, the codebase is getting bloated by duplicated code with the current setup, and I am in despair - instead of writing beautiful Elm code, I have to think of a solution that would play nice with the current setup. Any help would be greatly appreciated.

Try elm-make A.elm B.elm. In the resulting JS file they should share the runtime and there should be no duplication.

@Janiczek This was the first thing I tried, and it works indeed, but this "breaks the flow" of webpack watch configuration. Right now I have a script that runs elm make A.elm B.elm and the application requires the output JS bundle. When the JS bundle is build/re-build, this triggers webpack watch. Overall, the watch takes noticeably more time to rebuild stuff this way. When I just require each file directly and use elm-webpack-loader the watch is almost instantaneous but there is this code duplication in play.

@NeverwinterMoon Also see https://github.com/elm-community/elm-webpack-loader/pull/119 and https://github.com/elm-community/elm-webpack-loader/issues/106#issuecomment-289237917

I was thinking about it yesterday and I think I have a workaround. I am going to introduce Elm into an old AngularJS app to help with some new forms, each form (or group of forms) can have it's own mini-app with some shared utility modules.
Instead of creating many "main" modules, each with Html.beginnerProgram, I can create one Main.elm with a super Model and Msg as a union types of all modules. The super view will delegate to the corresponding view functions of all modules and the initialization will get extra flag to find out which module is actually this instance of.
Does not seem like much of work creating and maintaining it, does it? What's your say?

Give this a try: https://github.com/joeandaverde/elm-webpack-project-loader

@joeandaverde elm-webpack-project-loader works as expected (I was worried I cannot specify elm-make path to ./node-modules/.bin, but since it's launched via npm run it's all OK).
At the beginning, I was thinking it's kind of an add-on to the elm-webpack-loader, but now I can see it's just a standalone loader, does not require/use it.
Maybe you could "join forces"?

I believe both projects will likely be obsolete after the upcoming 0.19 release. I’m glad the project works for you!

Implemented and released as part of 4.4.0. elm-webpack-loader will be maintained after 0.19.
See here for how to use it: https://github.com/elm-community/elm-webpack-loader#files-default---path-to-required-file


If you can use it in combination with the printf function, that's cool

If you can use it in combination with the printf function, that's cool

I printf to byte array and then send this byte array over uart. But I understand what you meant, no plans to look into it


Fix IP forwarding utils Python 3 compatibility.

Current coverage is 98.31% (diff: 100%)

Merging #331 into development will increase coverage by <.01%

@@           development       #331   diff @@
=============================================
  Files               38         38
  Lines             2852       2855     +3
  Methods              0          0
  Messages             0          0
  Branches           136        136
=============================================
+ Hits              2804       2807     +3
  Misses              43         43
  Partials             5          5

Powered by Codecov. Last update 49bd63c...670096e

LGTM


Make sure rapids jar, integration test jar, and pytest bundle are compatible

Is your feature request related to a problem? Please describe.
We need a way to make sure the main rapids jar, integration test jar, and pytest bundle all match when running integration tests.

@pxLi Can you work on this? Maybe discuss with Tom first.
I'm not very clear about  what this issue is. I suppose it requires some changes in the test scripts or Jenkins.
@tgravescs
Does it mean the integration test now may run with the wrong jar files which are built from different Spark versions?

removed 21.12 from Projects, this is a CI-related request that should not block plugin release


Vitest v1.0.0-beta5 browser mode hangs in an infinite reload

Describe the bug
When running the beta-5 release of vitest in browser mode, you can get stuck in an infinite loop if you have an older version of pretty-format installed as sibling of vitest. See animated gif:

Reproduction
mkdir foo && cd foo
npm init --yes
npm i -D vitest@beta @vitest/browser@beta playwright pretty-format@21
touch vitest.config.js
# import { defineConfig } from 'vitest/config';
#
# export default defineConfig({
#   test: {
#     globals: true,
#     browser: {
#       enabled: true,
#       name: 'chromium',
#       provider: 'playwright',
#       headless: false,
#     },
#   },
# });

# Add an example project
npx vitest

Or download this zip:
vitest-infinite-reload.zip
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
    Memory: 10.11 GB / 15.49 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.0/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
    pnpm: 8.9.2 - ~/.nvm/versions/node/v18.18.0/bin/pnpm
  Browsers:
    Chrome: 118.0.5993.117
  npmPackages:
    @vitest/browser: ^1.0.0-beta.5 => 1.0.0-beta.5
    vitest: ^1.0.0-beta.5 => 1.0.0-beta.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I'm getting this issue on all versions from beta.1 to beta.5 and have the latest version of "pretty-format" in my resolutions. Are you sure this is the cause?
↪ yarn why pretty-format                                                                                3875ms ~ 16:23:41 ~ 28 Nov
yarn why v1.22.19
[1/4] 🤔  Why do we have the module "pretty-format"...?
[2/4] 🚚  Initialising dependency graph...
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#@types#jest" depends on it
   - Hoisted from "_project_#@types#jest#pretty-format"
   - Hoisted from "_project_#jest-matcher-utils#pretty-format"
   - Hoisted from "_project_#lerna#@lerna#legacy-package-management#pretty-format"
   - Hoisted from "_project_#@testing-library#react#@testing-library#dom#pretty-format"
   - Hoisted from "_project_#jest-axe#jest-matcher-utils#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#pretty-format"
   - Hoisted from "_project_#jest-matcher-utils#jest-diff#pretty-format"
   - Hoisted from "_project_#@jacuzzi#vacancy#vitest#@vitest#snapshot#pretty-format"
   - Hoisted from "_project_#@jacuzzi#vacancy#vitest#@vitest#utils#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-config#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-message-util#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-snapshot#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-validate#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-config#jest-circus#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-runner#jest-leak-detector#pretty-format"
   - Hoisted from "_project_#jest#@jest#core#jest-config#jest-circus#jest-each#pretty-format"
info Disk size without dependencies: "188KB"
info Disk size with unique dependencies: "296KB"
info Disk size with transitive dependencies: "916KB"
info Number of shared dependencies: 5
✨  Done in 0.38s.

@beamery-tomht what about v1.0.0-beta.6?

Yes, just checked and still happening. I've reverted back to 0.34.6 as the bug with tests hanging sometimes is less of a blocker than the tests not working at all 😿


Lookup modules located next to the file supplied on CLI

Look up modules in the directory containing the main TLA+ file supplied on CLI. This was requested multiple times #426, #1477 and is what TLC does for module lookup.
Drop support for lookup in TLA-Library, unless the main file has no parent directory.
Drop support for TLA_PATH, since it becomes virtually useless.
Mirrors the behavior of TLC since https://github.com/tlaplus/tlaplus/commit/b905a86e31714bf5002290141b51b41ffe280c8e.
I ran manual tests in the shell – lmk if you think this needs integration tests.
Fixes #426. Fixes #1477.

A few preliminary questions/notes based on the PR description:

Isn't the TLA_PATH still very useful if you want to add additional modules as a prelude or alternative "standard library"?

I don't understand the rationale for

Drop support for lookup in TLA-Library, unless the main file has no parent directory.

What is the relevance of the parent directory for the main file? And wouldn't this only be possible if the main file was at the root your file system?

I think we should definitely have integration tests for this kind of feature. Iiuc, since you've currently disabled the TLA_PATH, you're getting unintentional integration test coverage from https://github.com/informalsystems/apalache/blob/eae440964944ba842f1610a78444d2ff30ff47b4/test/tla/cli-integration-tests.md#L1177-L1185

Isn't the TLA_PATH still very useful if you want to add additional modules as a prelude or alternative "standard library"?

I don't know. Supporting it would mean to diverge from how TLC does module lookup, which may have unexpected results. I think we should remain compatible on this point. If someone still has a use case for TLA_PATH, it should be subsequently added to both Apalache and TLC.

I don't understand the rationale for

Drop support for lookup in TLA-Library, unless the main file has no parent directory.

What is the relevance of the parent directory for the main file? And wouldn't this only be possible if the main file was at the root your file system?

To clarify, by parent directory I meant dirname $tlafile. So even for a main file in root, it would search /. I don't know the significance of this, but that's how it's implemented in TLC and SANY.

I think we should definitely have integration tests for this kind of feature.

Fair enough, I'm going to add integration tests. Just be warned that it'll add some non-trivial directory structure in ./test/tla.

Codecov Report

Merging #1491 (3c70ff2) into unstable (bfdcd7d) will decrease coverage by 0.00%.
The diff coverage is 88.88%.

@@             Coverage Diff              @@
##           unstable    #1491      +/-   ##
============================================
- Coverage     74.89%   74.88%   -0.01%
============================================
  Files           358      358
  Lines         11475    11481       +6
  Branches        530      563      +33
============================================
+ Hits           8594     8598       +4
- Misses         2881     2883       +2

Impacted Files
Coverage Δ

...ala/at/forsyte/apalache/tla/imp/SanyImporter.scala
82.92% <85.71%> (-0.86%)
:arrow_down:

...at/forsyte/apalache/tla/imp/SanyNameToStream.scala
100.00% <100.00%> (ø)

.../forsyte/apalache/tla/pp/ConstSimplifierBase.scala
95.29% <0.00%> (-1.18%)
:arrow_down:

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 bfdcd7d...3c70ff2. Read the comment docs.

@andrey-kuprianov, we are removing support for TLA_PATH. I hope the MBT tools are not relying on that.

Good catch there asking MBT, Igor. Let's be sure to wait on their confirmation before merging this in.


"json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)"

I've encountered an error while running the monthly report script - namely, I didn't receive one. 😄 Once I realized, I ran it manually and saw the following:
"Traceback (most recent call last):
File "/home/username/.local/lib/python3.10/site-packages/requests/models.py", line 971, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python3.10/json/init.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.10/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/username/firefly-iii-email-summary-main/monthly-report.py", line 158, in
main()
File "/home/username/firefly-iii-email-summary-main/monthly-report.py", line 42, in main
categories = s.get(url).json()
File "/home/username/.local/lib/python3.10/site-packages/requests/models.py", line 975, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)"
It seems to me, something broke but woudn't know why - I didn't manually change anything on the server regarding the Python environment, and when I look at /home/username/.local/lib/python3.10/site-packages/, all modules were changed in last October, so it is rather strange. On a whim, I updated "requests" package, so now I have the following:
"pip3 list |grep requests
requests               2.28.1"
(before and after upgrading the module, the error message remained the same)
Do you have any ideas on how to restore functionality? I suspect something changed in Firefly 5.7.17.

Solved: I generated a new access token in Firefly III and the reporting works again. I had no idea that access tokens "expire", but will keep them in mind. :)

Solved: I generated a new access token in Firefly III and the reporting works again. I had no idea that access tokens "expire", but will keep them in mind. :)


smard.de integration not working on sunday

Hi,
I'm using your integration with smard.de data source for region AT and relized that the sensor is 'unvailable' on synday afternoon.
After some debugging I found out, that the timestamps always show data from Sunday till Sunday midnight.
an example:
we get all timestamps from this url:
https://www.smard.de/app/chart_data/4170/DE/index_hour.json
the latest timestamp as of now is:<PHONE_NUMBER>000, Oct 1, 2023, 10:00:00 PM UTC ( 00:00 in CEST )
results in this series url:
https://www.smard.de/app/chart_data/4170/DE/4170_DE_hour_1696197600000.json
which gives us data from<PHONE_NUMBER>000 ( Oct 1, 2023, 10:00:00 PM )  till<PHONE_NUMBER>000 ( Oct 8, 2023, 9:00:00 PM).
and that's why the check for marketdata_now fails:
https://github.com/mampfes/ha_epex_spot/blob/7b30c65e0f0fd6c6ceb1409cd2c1af1ff95e62b7/custom_components/epex_spot/SourceShell.py#L98
tl;dr:
on Sunday noon a new series for the net week is released, after which the service becomes unavailable.
I think the right solution would be to not just use the latest timestamp https://github.com/mampfes/ha_epex_spot/blob/7b30c65e0f0fd6c6ceb1409cd2c1af1ff95e62b7/custom_components/epex_spot/EPEXSpot/SMARD/init.py#L101
we could choose the one that includes datetime.now(), or always get the last 2 and filter out "old" data before return.
let me now what you think, and I'll create a pull request

Hi, I create a fix in the main branch. Could you please test it (on Sunday)?
Please note that the main branch contains a major rewrite, therefore some more testing is required before I will release a new version. Please also note that the entity ids changed because they now follow the latest Home Assistant naming conventions.

Hi!
Thanks for the quick fix. I just updated the integration. So far everything looks fine, will update you on Sunday

Sorry, I missed that: Thanks for the detailed analysis!

haven't looked closer yet. But it's still not working on Sunday. Will check again next Sunday

I also configured SMARD with AT for testing. And today (Sunday) I couldn't reproduce the problem. Data was available the whole day. I'm using version 2.0.0.

okay, interesting. must be a me problem then..

Did you install version 2.0.0?

now it's working.
maybe i had some files left from previous troubleshooting/debugging.
Thanks again !


WIP: Support sentencepiece

This PR implements proper handling for sentencepiece-style gluing.
STATUS:
First implementation done, not tested atm.

Looks already pretty good. Would you have some toy example data for easy testing?

I don't have toy data, but I think I can whip up a hand written lexicon_disambig example easily. I intend to create a very small FST at first, and create an image to see that it looks ok. Then I'll try some larger data and see that it compiles without problems.

Ah, a slight annoyance. So with the other lfst scripts, you simply use the pronunciation from the lexiconp_disambig.txt. However, sentencepiece can place the space character anywhere (technically even inside subwords). The g2p mapper cannot handle the space character natively.
My current idea to solve this is to create a separate script that calls the g2p mapper for each subword part, stripped of the space characters, and then inserts special placeholder phones for the space character. A little ugly, but in practice I think that should work. I think I'll include that script here as it's pretty much necessary for using this script, if that's ok?

Sure, feel free to include it.

This is ready to merge, though we should update the documentation. But I think the documentation needs a more general lookover (some legacy code in the examples), so maybe a separate PR.

Looks good indeed! One other gap in the documentation is that you should also fix "align_lexicon.xxx" in the phones directory, otherwise it is not possible to do phone alignment.


Request of New Trial for DisableThirdPartyStoragePartitioning2

Hi Team,
I’m currently working on an extension where we don’t utilize third-party cookies or storage partitioning, as the top-level site always begins with chrome-extension:<id>//<dynamic_URL>. However, we are now removing the prefix chrome-extension://<id> from the dynamic URL. This change results in a third-party context, and I have web-accessible resources on this page inside an iframe, which itself loads another iframe of my hosted CDN (https://abc.com).
Further details can be found here: https://github.com/privacysandbox/privacy-sandbox-dev-support/issues/409
Could you please assist me with a trial token? I wasn’t enrolled in the previous V1 token program.
Thank you!
CC: @miketaylr

@miketaylr, I would appreciate it if there is an alternative way to obtain the trial token, as it is important for us.

@miketaylr, we are working on an extension within our organization. We request your approval to help us unlock it.


Uncaught Parse error in .ftpconfig JSON : SyntaxError: Unexpected token K

[Enter steps to reproduce below:]

I use azure and user name there looks like "projectname\username"
when i try make a connection a get json error Token K
some azure username can look like "projectname$projectname" and then i error with $

Atom Version: 1.0.0
System: Microsoft Windows 8.1
Thrown From: Remote-FTP package, v0.7.1
Stack Trace
Uncaught Parse error in .ftpconfig JSON : SyntaxError: Unexpected token K
At C:\Users\Admin\.atom\packages\Remote-FTP\lib\client.js:78

undefined

Commands
     -0:12.1.0 core:save (atom-text-editor.editor.is-focused)
     -0:08.9.0 remote-ftp:toggle (atom-text-editor.editor.is-focused)
     -0:02.7.0 remote-ftp:connect (atom-text-editor.editor.is-focused)

Config
{
  "core": {}
}

Installed Packages
# User
atom-beautify, v0.28.7
file-icons, v1.5.8
Remote-FTP, v0.7.1

# Dev
No dev packages

Don't you need to escape the \ in your JSON?  Like:
"user": "project_name\\$username",


buildozer command for reproducibility doesn't work with bzlmod

A MODULE.bazel file like
oci.pull(
    name = "distroless_base",
    tag = "latest",
    # digest = "sha256:ccaef5ee2f1850270d453fdf700a5392534f8d1a8ca2acda391fbb6a06b81c86",
    image = "gcr.io/distroless/base",
    platforms = [
        "linux/amd64",
        "linux/arm64",
    ],
)

results in
WARNING: for reproducible builds, a digest is recommended.
Either set 'reproducible = False' to silence this warning,
or run the following command to change oci_pull to use a digest:

buildozer 'set digest "sha256:73deaaf6a207c1a33850257ba74e0f196bc418636cada9943a03d7abea980d6d"' 'remove tag' 'remove platforms' 'add platforms "linux/amd64" "linux/arm64" "linux/arm" "linux/s390x" "linux/ppc64le"' WORKSPACE:rules_oci~1.2.0~oci~distroless_base

which clearly doesn't work, as it references the WORKSPACE file.
@fmeum recently improved buildozer to support use_repo calls - do you have any recommendation if there's an easy way for us to print a command that works for all users?

//MODULE.bazel:distroless_base instead of WORKSPACE:rules_oci~1.2.0~oci~distroless_base should work (the // is optional, but it doesn't require the user to be in the root directory of the project).

Just MODULE.bazel:distroless_base gives you better compatibility. The interesting takeaway is that bazel_dep and tags with a name attribute are recognized as "rules" by buildozer, so all the usual commands just work for them.


sentry

Let's connect it to Sentry

Job gh:yegor256/jpeek#36 assigned to @yegor256, please go ahead (policy).

Bug was reported: +15 points just awarded to @yegor256, total is +4665.

Manual assignment of issues is discouraged, see par.19: -5 points just awarded to @yegor256, total is +4665.

Job gh:yegor256/jpeek#36 is now out of scope.

Order was successfully finished: +30 points just awarded to @yegor256, total is +4865.


Update losses.py

kaggle fix

Thanks for the PR @neoalwayz ! Can you elaborate on why the mean was a problem, please?

hi @jucor ! While running the 'Training a super-resolution model' part of the Kaggle notebook encountered
File "/kaggle/working/worldstrat/src/losses.py", line 27, in tv_loss
return (kornia.losses.total_variation(x) / (height * width)).mean(dim=1)
IndexError: Dimension out of range (expected to be in range of [-1, 0], but got 1) error.


client: integrate skyhookdm-ceph-cls build with arrow build system

Closed by https://github.com/uccross/arrow/commit/7986a0b07dbc2d008e567091d6c6eefc5ef0fbd8


What is the Weaver workflow for unit testing with mock objects?

Hi @trupin I really like this tool, it removes a lot of the boiler plate involved with dependency injection and the compile time checking is a good design choice which many other projects will overlook. My question/feature request is around mock objects.
Can Weaver generate mock objects?
Is there plans to build into Weaver a feature to generate mock objects?
Many times when using dependency injection a mock object is required for the unit test. In your Sample project it looks like the mock is being written by hand, which is boiler plate.
Thanks for making Weaver open source.

Hi @amleszk,
There's no plan to make Weaver support mock objects generation. It is a complex task which IMO would require a separate tool.
Writing templates with Sourcery could be a good start. Maybe even enough.


find_node broken?

Ubuntu 16.04 lts 64 bit
Godot 2.1 stable
Please see the screenshot. Using get_node( "/root/World/ground" ) works, but using e.g. get_tree().get_root().find_node("ground") doesn't. Which surprises me based on the find_node docs.

oh i am reading https://github.com/godotengine/godot/issues/6811 which might be the same thing...


Add Lucide icons / Replace Feather icons

Add Lucide icons. Lucide is a fork of Feather that adds a significant amount of icons matching the same design style.
First commit (3627b66) adds Lucide icon module, second commit (22273a1) removes Feather and adds additional mount for Lucide for backwards compatibility.
Lucide Info:

Git: github.com/lucide-icons/lucide
Web: lucide.dev

Thanks, I would like to add a new vendor instead of replacing the exist one, for compactibility considering, and I don't want to force users to choose the Lucide than Feather.
Closing by cherry-pick the 649b1b3821a01647c9626991db3cca895a2a9da9 commit, thanks for your contributions!


Update cookie-signature package to the security version

A security bug was detected by the Shieldfy in the "cookie-signature" package.
Infected version: 1.0.6
description:-
Affected versions of cookie-signature are vulnerable to timing attacks as a result of using a fail-early comparison instead of a constant-time comparison. Timing attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences. Under favorable network conditions, an attacker can exploit this to guess the secret in no more than charset*length guesses, instead of charset^length guesses required were the timing attack not present.
detected by Shieldfy Team
shieldfy.io

The tool you are using contains a false report. Version 1.0.6 has no vulnerability. That report has been removed from multiple security platforms, but apparently not whatever you are using. See https://github.com/expressjs/express/issues/3583
In the future, report security issue according to our guidelines https://github.com/expressjs/express/blob/master/Security.md


minor_fixes

Related Issue

break statement was missing

Fixes: #[issue number that will be closed through this PR]
Describe the changes you've made
added a break statement
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

Original
Updated

original screenshot
updated screenshot

@ashish-patwal I can merge this but the points for DCP will be given only if u created an issue and then sent the PR. So it's upto u.

Merge it . It's just a line only


operator [R] kiali (1.70.0 1.71.0 1.72.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.

/merge possible


client-body-buffer-size

i want to update client-body-buffer-size
Found for Nginx
nginx.ingress.kubernetes.io/client-body-buffer-size: 1M

@urvineet Do you want to use different body buffer size value for each service?

You can mount custom nginx configuration file via config map volume to kong-ingress-controller container. After that, you have to specify the config file's path with KONG_NGINX_HTTP_INCLUDE env variable. You can find examples from this documentation.

to achieve it,  i need to define custom server block in conf file which i am looking
I just want to update client-body-buffer-size

For the Kong container, set the following env variable:
KONG_CLIENT_BODY_BUFFER_SIZE: 1024k

Refer: https://github.com/Kong/kong/blob/1.2.1/kong.conf.default#L391

Can client-body-buffer-size be configured via an annotation or KongPlugin now? Like nginx: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#client-body-buffer-size

Can client-body-buffer-size be configured via an annotation or KongPlugin now? Like nginx: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#client-body-buffer-size

Same question for me. Is this feature available now?

It can be configured globally per Kong Gateway with the environment variable KONG_CLIENT_BODY_BUFFER_SIZE see how to use it with

with Helm - in value file set gateway.env.client_body_buffer_size:  1024k
for Kong Gateway Operator use DeploymentOptions

Can client-body-buffer-size be configured via an annotation or KongPlugin now? Like nginx: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#client-body-buffer-size

Same question here, as  client_body_buffer_size could differs between ingresses.


Check ἐβαπτίσα (1 Corinthians 1:15)

Parsing(VERB | AORIST | ACTIVE | INDICATIVE | FIRST_PERSON | SINGULAR
ἐβαπτίσα
1 Corinthians 1:15

Should be fixed with the next update.


HBASE-23123 Merge_region fails from shell

The deprecated method Admin#mergeRegions is removed in HBase 3.0 but we need to update new API in admin script.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 33s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:green_heart:
mvninstall
5m 29s
master passed

:green_heart:
javadoc
0m 16s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
4m 52s
the patch passed

:broken_heart:
rubocop
0m  8s
The patch generated 4 new + 307 unchanged - 0 fixed = 311 total (was 307)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
javadoc
0m 14s
the patch passed

_ Other Tests _

:green_heart:
unit
7m 10s
hbase-shell in the patch passed.

:green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

20m  7s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/690

Optional Tests
dupname asflicense javac javadoc unit rubocop

uname
Linux 718bee3c1d11 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-690/out/precommit/personality/provided.sh

git revision
master / f69e7705e0

Default Java
1.8.0_181

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/1/artifact/out/diff-patch-rubocop.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/1/testReport/

Max. process+thread count
2684 (vs. ulimit of 10000)

modules
C: hbase-shell U: hbase-shell

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) rubocop=0.75.0

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

Thank you @saintstack for the approval.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 11s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:green_heart:
mvninstall
6m  4s
master passed

:green_heart:
javadoc
0m 14s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
5m 29s
the patch passed

:broken_heart:
rubocop
0m  7s
The patch generated 1 new + 307 unchanged - 0 fixed = 308 total (was 307)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
javadoc
0m 12s
the patch passed

_ Other Tests _

:green_heart:
unit
8m 25s
hbase-shell in the patch passed.

:green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

23m  4s

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/690

Optional Tests
dupname asflicense javac javadoc unit rubocop

uname
Linux d9bb3a44f762 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-690/out/precommit/personality/provided.sh

git revision
master / f69e7705e0

Default Java
1.8.0_181

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/2/artifact/out/diff-patch-rubocop.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/2/testReport/

Max. process+thread count
2610 (vs. ulimit of 10000)

modules
C: hbase-shell U: hbase-shell

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) rubocop=0.75.0

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

We do not have a UT in hbase-shell for this command?

@Apache9 @virajjasani
It looks to me no test method defined for merge_region. I see only few test from admin_test.rb but not all shell commands included in that test. I think that's our gap. I just ran admin_test.rb test but somehow it is failing. Let me check.
However, I am not sure if maven skip running this test ??  When I run "mvn test" on "hbase-shell" module, it only runs two test classes and reports success but I don't find all of them are running. This is weird.  I will check on this today.
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hbase.client.TestShellNoCluster
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.622 s - in org.apache.hadoop.hbase.client.TestShellNoCluster
[INFO] Running org.apache.hadoop.hbase.client.TestTableShell
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.476 s - in org.apache.hadoop.hbase.client.TestTableShell
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
@virajjasani  "return statement is redundant" is a warning of ruby check style.  This is about I return "nil" without any variable check, something like "if (var > x)  else return nil" etc.
I directly return nil in script because the method mergeRegionsAsync returns void.
Future mergeRegionsAsync(byte[] nameOfRegionA, byte[] nameOfRegionB,
boolean forcible) throws IOException {
If I don't use nil, then I will get CompletableFuture output.
=> #Java::JavaUtilConcurrent::CompletableFuture:0x68631b1d
Example:
hbase(main):001:0> merge_region '39ac83efe7b96b875d0a9e63313a3717','ff68d30015dc2565eaea1a16207e2e91'
Took 0.9494 seconds
=> #Java::JavaUtilConcurrent::CompletableFuture:0x68631b1d

I directly return nil in script because the method mergeRegionsAsync returns void.
Correct, just realized by default async method's return value will be passed on to merge_region.rb.

Regarding the tests, better to include test for merge_region() with this PR. And I agree that "mvn test" doesn't run all tests for hbase-shell and we have to manually take care of them as of now.

Great @virajjasani I will add merge_region testcase. I am very curious that why would we need to run hbase-shell test cases manually,  Sorry.  Is it because the test category is LargeTest?
I see admin_test.rb should run as part of TestAdminShell.

I got @virajjasani.  I see TestAdminShell runs here.

@Apache9 @virajjasani I included test case for merge_region.
By the way, my test case for TestAdminShell was failing on my MAC is due to Openfilelimit. The test mechanism is super intelligent :)  It runs successfully after increasing file descriptor limit.
 Thread LEAK? -, OpenFileDescriptor=744 (was 743) - OpenFileDescriptor LEAK? -, MaxFileDescriptor=10240 (was 10240), SystemLoadAverage=234 (was 274), ProcessCount=390 (was 390), AvailableMemoryMB=620 (was 647)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 34s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

:green_heart:
mvninstall
5m 52s
master passed

:green_heart:
javadoc
0m 16s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
5m  9s
the patch passed

:broken_heart:
rubocop
0m 14s
The patch generated 1 new + 471 unchanged - 0 fixed = 472 total (was 471)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
javadoc
0m 13s
the patch passed

_ Other Tests _

:green_heart:
unit
7m 11s
hbase-shell in the patch passed.

:green_heart:
asflicense
0m 16s
The patch does not generate ASF License warnings.

20m 56s

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/690

Optional Tests
dupname asflicense javac javadoc unit rubocop

uname
Linux 26e8372c1e81 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-690/out/precommit/personality/provided.sh

git revision
master / 2144690fb8

Default Java
1.8.0_181

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/3/artifact/out/diff-patch-rubocop.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/3/testReport/

Max. process+thread count
2744 (vs. ulimit of 10000)

modules
C: hbase-shell U: hbase-shell

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-690/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) rubocop=0.75.0

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


Update _to_add.md

Dave's note: Both 2.8.7 and 2.8.25 talk about OWASP WebGoat Project. Seems like it should be covered in only 1 place. Ann-Marie deleted 2.8.25 here, and also 2.8.25 "Security Champions Books", as that is also duplicated in an earlier file (2.8.7 "Learning resources" #152)

@Ambg05 now that you are starting to get a better feel for the content of the book, if you spot other duplications of content, please delete them :)


update TPB TLD

back to .se

Have you tested that it works? I get a RequestException because they seem to use cloudflare.
Plugin also needs to be updated to use new flexget search api.

Yes it does work for me.
I have seen about the new search API warning. Where are the changes documented?

What is your config? It refuses to work for me because of SSL verification problems.
I am not sure about the specifics of the search API, but changing line 107 to def search(self, task, entry, config=None): and line 123 to for search_string in entry.get('search_strings', [entry['title']]): seems to do the trick.

Nothing particular in my config
    discover:
      what:
        - emit_series:
            from_start: yes
      from:
        - piratebay:
            category: 208
            sort_by: seeds

I don't see how you can get SSL verification problem with an HTTP URI.

Maybe it's something Windows specific. But it definitely checks the SSL certificate. Anyway, if you fix the search api I think we can merge.

Great, thanks.


[bug]jdbc entrance cached  a different jdbc engine

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

use  JDBCEngineExecutor.get(url + ":" + userName + ":" + password) as function return

JDBCEngineExecutor may not require caching, please see
issue: Jdbc executor cache problem]
fix : remove JDBCEngineExecutor  cache


Uploaded M-1 papers

Papers are of years 2015-16.
Uploaded M1 paper for EC branch, though applicable for all branches
There are 4 files comprising, MID term & END term papers.

So guys finally I fixed Travis now Travis build is passing congrats 👍


[camera] cinemachine move Y axis slightly and unexpectly

In the initial room, when move left and right, the cinemachine move Y slightly.
Usually reproduce when cinemachine view meet the boundary.

fixed in master


dev and production SD images for ishiki

build and test new SD card images for desk/ishiki

Addressed in #9.


Error When Trying to Export [win10x64, w2exe 0.3.2b]

I've tried changing output folders, etc. Nothing seems to be working.

Why did you close the issue? Did you solve it? I'd like to know so that others can benefit if they have the same issue :)

Seemed as though the .git folder was messing something up.