text:
fix test/*.yml

fix test*.yml format is little be different. so changed same format.

Fixed upstream due to conflicts.

repo: fnando/browser


text:
音乐列表不全, 尝试了好几次搜索, 暂时没有一首歌超过20条记录的

音乐列表不全, 尝试了好几次搜索, 暂时没有一首歌超过20条记录的

目前每个站点只会选取 Top N ，因为排在后面的歌曲大概率与搜索歌曲是不匹配的了。

source: gharchive/issue

authors: FairyWorld foamzou

repo: foamzou/melody

license_type: permissive

license_source: github-api


text:
Ruby 2.4.0 has deprecated the Fixnum class

This has now been replaced with the Integer class

Changes Unknown when pulling e70bf4a957ec766f0cfe1400f82840c90516e5b1 on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Changes Unknown when pulling e70bf4a957ec766f0cfe1400f82840c90516e5b1 on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Changes Unknown when pulling fe48dbc4170ed472d959b7c8210243a730bad06c on thechrisoshow:fix-2-4-0 into ** on fog:master**.

Closing in favor of #65

Thanks for your interest and contribution here. I did merge this same change from another PR to speed up the process. I don't have time to code myself nowadays so i heavily depend on contributions. Sorry for the trouble.

source: gharchive/pull-request

authors: coveralls plribeiro3000 thechrisoshow

repo: fog/fog-xenserver

license: mit

license_source: bigquery


text:
poetry

adding poetry config
docs: adding poetry setup and missing brew install

Cool! Thank you.

authors: foges iloveitaly

repo: foges/whisper-dictation

license: MIT


text:
MODRS-186: Make system user creation optional

Purpose
To support a proof of concept for improved provisioning and management of system users, implement the ability to disable the creation, management, and use of system users in modules.
Approach

Add SYSTEM_USER_ENABLED configuration property to control system user creation/usage
Remove redundant classes (they must be deleted with migration to the folio-spring-system-user)

Changes Checklist

[ ] API Changes: List any API paths, methods, request or response bodies changed, added, or removed.
[ ] Database Schema Changes: Specify any database schema changes and their impact.
[ ] Interface Version Changes: Indicate any changes to interface versions.
[ ] Interface Dependencies: Note added or removed dependencies.
[ ] Permissions: Document any changes to permissions.
[ ] Logging: Confirm that logging is appropriately handled.
[ ] NEWS: Ensure that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues
List any Jira issues related to this pull request.
Learning and Resources (if applicable)
Discuss any research conducted during the development of this pull request. Include links to relevant blog posts, patterns, libraries, or addons that were used to solve the problem.
Screenshots (if applicable)
If this pull request involves any visual changes or new features, consider including screenshots or GIFs to illustrate the changes.

the feature was merged in scope of https://github.com/folio-org/mod-remote-storage/pull/195

authors: pfilippov-epam yauhen-vavilkin

repo: folio-org/mod-remote-storage


text:
bug: keyboard interrupt when pressing ctrl_c to dismiss "Config change detected" message

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
v0.9.0-dev-1983+g80bede1df
Operating system/version
Linux Mint 20.2
Describe the bug
When cancelling the "Config Change Detected" message with <C-c>, an error is shown:
Error executing vim.schedule lua callback: ....local/share/nvim/lazy/lazy.nvim/lua/lazy/core/cache.lua:375: Keyboard interrupt
stack traceback:
        [C]: in function 'list_rtp'
        ....local/share/nvim/lazy/lazy.nvim/lua/lazy/core/cache.lua:375: in function 'get_rtp'
        ....local/share/nvim/lazy/lazy.nvim/lua/lazy/core/cache.lua:57: in function 'check_path'
        ....local/share/nvim/lazy/lazy.nvim/lua/lazy/core/cache.lua:270: in function 'find_root'
        .../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:208: in function 'lsmod'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:254: in function 'import'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:231: in function 'normalize'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:219: in function 'normalize'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:33: in function 'parse'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/plugin.lua:348: in function 'load'
        ...l/share/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:85: in function <...l/share/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:77>

Steps To Reproduce

Edit any plugin file and save it
Notice a message like

# Config Change Detected. Reloading...

- **changed**: `.config/nvim/lua/plugins/init.lua`

is shown.
3. Press <C-c>
Expected Behavior
Lazy should preferably fail silently (i.e. the message should just close without an error shown to the user)
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Sorry, but that's how Neovim works. You should just press enter instead of interrupting

authors: folke smjonas


text:
feature: APIs to check if a plugin has been loaded

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
I am trying to lazy load the oil.nvim plugin, and this is my current setup:
  {
    "stevearc/oil.nvim",
    opts = {},
    cmd = "Oil",
    keys = {
      {
        "-",
        function()
          return require("oil").open()
        end,
        desc = "Open parent directory",
      },
    },
    init = function()
      if vim.fn.argc() == 1 then
        local stat = vim.loop.fs_stat(vim.fn.argv(0))
        if stat and stat.type == "directory" then
          require("lazy").load({ plugins = { "oil.nvim" } })
        end
      end
      if not require("lazy.core.config").plugins["oil.nvim"]._.loaded then
        vim.api.nvim_create_autocmd("BufNew", {
          callback = function()
            if vim.fn.isdirectory(vim.fn.expand("<afile>")) == 1 then
              require("lazy").load({ plugins = { "oil.nvim" } })
              -- Once oil is loaded, we can delete this autocmd
              return true
            end
          end,
        })
      end
    end,
  },

The part of interest is the init function. I am trying to achieve the following:

If nvim is invoked with a single argument that is a directory, laod oil.nvim.
Otherwise, we create an autocmd that loads oil.nvim the first time we open a directory in nvim.

Because I only want to create this autocmd if oil.nvim is not already loaded, I would like a way to check whether it is currently loaded. The way I am using is the following:
if not require("lazy.core.config").plugins["oil.nvim"]._.loaded then

I believe this makes use of a private field of requrie("lazy.core.config").plugins? I think it would be nice if there is a public API to check whether a plugin is loaded.
Describe the solution you'd like
A public plugin to return whether a plugin is already loaded.
Describe alternatives you've considered
NA
Additional context
No response

That's the correct way to check if a plugin is loaded. _ contains state information.

Thank you so much for the explanation!


text:
docs: Changed dot from LazyVim

#288 I thought it would be better to change the example from dot to LazyVim.

the link texts and the descriptions are wrong in most cases

I'll cleanup the docs in a bit. The idea was indeed to link to LazyVim, once that repo is stable

I agree with you, I'll close this pull request for now.

Updated the docs in the meantime

Thank you!

authors: Liquid-system folke max397574


text:
bug: Neovim breaks when pasting large texts

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.1
Operating system/version
MacOS 14.7
Describe the bug
Neovim breaks when we try to paste up larger texts to a buffer due to scroll functionality.
Steps To Reproduce

Paste a large text  blocks (~1500 lines)
The paste gets jumbled up and few texts are omitted.

Expected Behavior
I disabled the scroll functionality and then it started working fine.
Repro
return {
	"folke/snacks.nvim",
	priority = 1000,
	lazy = false,
	---@type snacks.Config
	opts = {
		-- your configuration comes here
		-- or leave it empty to use the default settings
		-- refer to the configuration section below
		bigfile = { enabled = true },
		dashboard = { enabled = true },
		indent = { enabled = true },
		input = { enabled = false },
		notifier = { enabled = false },
		quickfile = { enabled = true },
		scroll = { enabled = true },
		statuscolumn = { enabled = true },
		words = { enabled = true },
	},
}

Used this to correct the behaviour
return {
	"folke/snacks.nvim",
	priority = 1000,
	lazy = false,
	---@type snacks.Config
	opts = {
		-- your configuration comes here
		-- or leave it empty to use the default settings
		-- refer to the configuration section below
		bigfile = { enabled = true },
		dashboard = { enabled = true },
		indent = { enabled = true },
		input = { enabled = false },
		notifier = { enabled = false },
		quickfile = { enabled = true },
		scroll = { enabled = false },
		statuscolumn = { enabled = true },
		words = { enabled = true },
	},
}

Video for reference -
https://github.com/user-attachments/assets/f9d0498c-7a6d-4b5a-9e2c-203ff73fd5ad

I'm having a similar problem with data cluttering up when pasting large amounts of data content with  scroll = { enabled = true }


text:
Don't crash when post format 1 is improperly used

Fixes #2736

Can you strip the test font from unneeded tables, and replace all glyphs with an empty glyph?
    tag     checksum    length    offset
    ----  ----------  --------  --------
    BASE  0x65235DBD        70     73608
    GDEF  0x0E600F0B       140     73468
    GPOS  0xC58F843E     21494     51972
    GSUB  0x676CF69A      4020     47952
    OS/2  0x5C09739A        96       360
    cmap  0x7D830F03      1820      2660
    glyf  0x1B788E11     40504      5584
    head  0x13A80257        54       236
    hhea  0x08BA0811        36       292
    hmtx  0xF1AD5BC9      2204       456
    loca  0x4BA3735A      1104      4480
    maxp  0x02370109        32       328
    name  0x0AD0EC64      1832     46088
    post  0x00010000        32     47920

Sure

New test font submitted
    tag     checksum    length    offset
    ----  ----------  --------  --------
    cmap  0x16D8EB36      1192      1828
    glyf  0x00000000         1      3804
    head  0x16A8DC50        54       140
    hhea  0x04E408B7        36       196
    hmtx  0xF0754561      1564       264
    loca  0x00000000       784      3020
    maxp  0x01880001        32       232
    post  0x00010000        32      3808

@anthrotype @justvanrossum OK to merge?

authors: justvanrossum miguelsousa

repo: fonttools/fonttools


text:
update graphql to case insensitive

closes #592

Description

Checklist

[ ] Ran Linting
[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Added an entry to the CHANGELOG.md file.
[x] Re-reviewed Files changed in the Github PR explorer.

Loving this program


text:
(In Code Review) Fix compilation error in DeskTest

https://jira.desk.technology/browse/MSDKA-69

:+1:

repo: forcedotcom/DeskMobileSDK-Android


text:
Flagged by Windows Defender when downloading/installing

Summary
I'm unable to download or install the Salesforce CLI on Windows 10 due to it being blocked by Windows Defender.

Steps To Reproduce:

Install on Windows 10 from https://developer.salesforce.com/tools/sfdxcli

Expected result
Successful Installation
Actual result
"Virus Detected. Can't download" message displays in my browser (Edge)
System Information
Version	10.0.19044 Build 19044
OS Name 	Microsoft Windows 10 Enterprise
Additional information

This issue is happening on my work laptop so I'm working with my IT team as well. just want to see if there's anything added recently that may be the cause.

Hey @cmatos23, thank you for reporting this issue. I don't know what would have been added recently to cause this. I assume this is the first time that you have came across this issue? Could you please try installing a previous version of the CLI and see if you get the same error? It would help to narrow down what exe this started tripping Defender. You can get the links to old installer versions on this page. Look for the Windows 64 or Windows x86 Installer links. Those json files have the dowload links to past installers.

Closing this issue due to inactivity, please let us know if you experience this error with previous windows installers so we can take a look at it, thanks!

Hello
This Issue is still coming . Request to please check & please tell the fix for it.

repo: forcedotcom/cli


text:
Release blog post - v0.16.0

This year in cargo-msrv & v0.16 release

[x] Compatibility check cmd overrides with runner=rustup-run
[ ] Revised user output

Iterating, next release may change substantially again, feedback more than welcome, for all btw.

[ ] ...
[ ] Planned for next year.
[ ] Happy new year!

Draft: Compatibility check cmd overrides with runner=rustup-run
December release
Override rustup run commands
By default, the Rustup run command used to test whether a toolchain is compatible, is rustup run <toolchain> cargo check. If you wanted to use another command, you could already use cargo msrv -- <my command>, e.g. cargo msrv -- cargo build. This is necessary for example if you rely on a version of cargo which does not yet have cargo check built in. Then, you could run both: cargo msrv --min 1.16 and cargo msrv --max 1.15 -- cargo build, but this gets old, fast.
From cargo-msrv v0.16 it is also possible to override the compatibility check commands used. To do this, specify the following overrides in your Cargo.toml:

[[package.metadata.msrv.override]]
runner = "rustup-run"
version_req = "<1.17"
compatibility_check = "cargo build"

NB: The combination runner and version_req must be unique. Also note that the version req follows the semver::VersionReq, spec with the following limitation: cargo-msrv only supports stable Rust releases.
By default, from this cargo-msrv release, we will override the compatibility check for Rust toolchains released prior to Rust 1.16 (cargo check became available from Cargo 1.16).
The precedence of overrides is as follows:

Granular override defined in the Cargo.toml >
Global override specified via remainder CLI arguments ( cargo msrv -- <cmd>) >
Default compatibility check override  >
Default compatibility check

Note that running two or more different commands (e.g. cargo build vs cargo check) does mean that you test your project for compatibility in different ways, which may not be consistent with each other.
Since it is unlikely that many people are still using a Rust toolchain before Rust 1.16 (released in 2017, on March 16th), the impact of the default override should be minimal.

repo: foresterre/cargo-msrv


text:
Makes four opinionated changes which improve my user experience:

Makes the distributions bigger, much bigger, so that I can better see them.

I add another height level, 5 (440px) and make 4 (340px) the default.

To do that, and to be able to see the input string at the same time I destroy the cdf.

My brain wasn't really made for interpreting cdfs, and I can switch to the cdf view if I want.
Note that this destroys the pdf + cdf combo as as default everywhere.

Changes the distribution color to a bright, happy and shiny blue, so that I can better see them.
Adds a standard distribution with more personality.

Before:

After:

Hm... I think I liked the CDF. The distribution shape was pretty arbitrary, we've been changing it sporadically for debugging purposes. Happy to change it to this for now.
Happy to go lighter blue, but not quite that bright.

authors: NunoSempere OAGr

repo: foretold-app/widedomain


text:
Sorting animation not working (React 18)

Somehow to sorting animation doesn't work.
Here is an example: https://codesandbox.io/s/nifty-zeh-m9hpkt?file=/src/App.js:0-573

You need actual keys amigo. Indexes are not real keys. https://codesandbox.io/s/angry-resonance-o8nt57?file=/src/App.js

repo: formkit/auto-animate


text:
Refresh container list after making a status change

Fixes #12

Pretty sure this is all that is needed?

@aharpervc Executor.runInTerminal() is an async function, so this change will not take effect.

I see. What's the fix?

There need more code refactoring without using runInTerminal. One option is using child_process.execSync API.  One thing I am curious is that why you would like disable the auto-refresh. Is there any side effect of it? With the auto-refresh, we don't need to refresh container after any operation is done. 😄

I often keep "Docker for Win/Mac" turned off, so this creates problems with the cli tool can't talk to that service. Also I run quite a few instances of VS Code so that's a lot of notices and failing processes spawning all the time. Plus, I don't often change container state except when developing inside of VS Code, so it's not like the auto refresh would tell me about something I didn't just do manually.

Thanks @aharpervc for the detailed info. In that case, it seems that the only side effect of auto-refresh is that it will show error message for each VS Code instance. Therefore, a quick turnaround is to provide an option to allow user to let extension not show the error message. What's your thought about this?

Sure, that would help. You'd also have processes needlessly running and dying in the background unceasingly, but that's probably not that big of a deal.

#16 is opened. Closing this PR. Would you like to send a new PR to implement #16 or let me implement that?

I have no idea how notifications work, so go for it.

authors: aharpervc formulahendry

repo: formulahendry/vscode-docker-explorer


text:
Test/notifier inventory summary email

The encrypted pickle file will only work on the Forseti test env.
Resolves #3431
✔  notifier-inventory-summary-email: Command: `sudo pip3 install -r /home/ubuntu/forseti-security/integration_tests/tests/forseti/requirements.txt`
     ✔  Command: `sudo pip3 install -r /home/ubuntu/forseti-security/integration_tests/tests/forseti/requirements.txt` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/update_server_config.py set_inventory_summary_email_enabled true` exit_status should eq 0
     ✔  Command: `sudo gcloud kms decrypt --ciphertext-file=/home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle.enc --plaintext-file=/home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --key=forseti-test-key --keyring=forseti-test-keyring --location=global` exit_status should eq 0
     ✔  Command: `forseti notifier run` exit_status should eq 0
     ✔  Command: `forseti notifier run` stdout should match /Notification completed!/
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/verify_email.py --pickle_path /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --retries 5 --sender forseti-notify@localhost.domain  --subject "Inventory Summary: 1577488649464095"` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/verify_email.py --pickle_path /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --retries 5 --sender forseti-notify@localhost.domain  --subject "Inventory Summary: 1577488649464095"` stdout should match /Emails found: 1/
     ✔  Command: `sudo rm -rf /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/update_server_config.py set_inventory_summary_email_enabled false` exit_status should eq 0
     ✔  Command: `forseti inventory delete 1577488649464095` exit_status should eq 0
     ✔  Command: `forseti model delete c26909d1938` exit_status should eq 0

@googlebot I consent.

Inventory summary email test is now passing:
 ✔  notifier-inventory-summary-email: Command: `sudo pip3 install -r /home/ubuntu/forseti-security/integration_tests/tests/forseti/requirements.txt`
     ✔  Command: `sudo pip3 install -r /home/ubuntu/forseti-security/integration_tests/tests/forseti/requirements.txt` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/update_server_config.py set_inventory_summary_email_enabled true` exit_status should eq 0
     ✔  Command: `sudo gcloud kms decrypt --ciphertext-file=/home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle.enc --plaintext-file=/home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --key=forseti-test-key --keyring=forseti-test-keyring --location=global` exit_status should eq 0
     ✔  Command: `forseti model use 198d15494e7 && forseti scanner run && forseti notifier run` exit_status should eq 0
     ✔  Command: `forseti model use 198d15494e7 && forseti scanner run && forseti notifier run` stdout should match /Scanner Index ID: ([0-9]*) is created/
     ✔  Command: `forseti notifier run --inventory_index_id 1578499494745638` exit_status should eq 0
     ✔  Command: `forseti notifier run --inventory_index_id 1578499494745638` stdout should match /Inventory summary email successfully sent for inventory id/
     ✔  Command: `forseti notifier run --inventory_index_id 1578499494745638` stdout should match /Notification completed!/
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/verify_email.py --pickle_path /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --retries 5 --sender forseti-notify@localhost.domain  --subject "Inventory Summary: 1578499494745638"` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/verify_email.py --pickle_path /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle --retries 5 --sender forseti-notify@localhost.domain  --subject "Inventory Summary: 1578499494745638"` stdout should match /Emails found: 1/
     ✔  Command: `sudo rm -rf /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/gmail_token.pickle` exit_status should eq 0
     ✔  Command: `sudo python3 /home/ubuntu/forseti-security/integration_tests/tests/forseti/scripts/update_server_config.py set_inventory_summary_email_enabled false` exit_status should eq 0
     ✔  Command: `forseti inventory delete 1578499494745638` exit_status should eq 0
     ✔  Command: `forseti model delete 198d15494e7` exit_status should eq 0

authors: gkowalski-google goofiva

repo: forseti-security/forseti-security


text:
Added capability to start an inventory from a folder or project level

Thanks for opening a Pull Request!
Here's a handy checklist to ensure your PR goes smoothly.

[ ] I signed Google's Contributor License Agreement
[ ] My code conforms to Google's python style.
[ ] My PR at a minimum doesn't decrease unit-test coverage (if applicable).
[ ] My PR has been functionally tested.
[ ] All of the unit-tests still pass.
[ ] Running pylint --rcfile=pylintrc passes.

These guidelines and more can be found in our contributing guidelines.

Adding cla: yes label, as all commit authors are covered by CLA.

authors: blueandgold felixbb


text:
🛑 JLee is down

In d700072, JLee (https://jlee-stg.qpm.co.at/) was down:

HTTP code: 403
Response time: 68 ms

Resolved: JLee is back up in 86fe014.

repo: forsports/upptime


text:
KeyError: 'results'

Hello,
I get this error messege:
if resp['results']['vm']['status'] == "vm_valid" or "vm_eval":
KeyError: 'results'

This is my example code to reproduce the error:
#!/usr/bin/python

from fortiosapi import FortiOSAPI

FGT_HOST='192.168.122.40'
FGT_USER='admin'
FGT_PASSWORD=''

fosapi = FortiOSAPI()
fosapi.https('on')
fosapi.login(FGT_HOST, FGT_USER, FGT_PASSWORD)

print(fosapi.license())

fosapi.logout()

I use the Fortigate-60D with the Firmware v.5.2.11 and fortisapi with 0.9.

Not reproducible with FG-81E and FOS 6.0.2.
Most likely than not there was some change on the API structure since 5.2 that is the root-cause of this error.

I think I saw a similar error on v5.2. Can you confirm the version?
The library supports from 5.6 and later.

The library was started with 5.4 support. Please check the 1.0rc branch as the licensing is much better handled there.

#28 resolve this normally.

authors: barbosm ikreb7 mamunozgonzalez thomnico

repo: fortinet-solutions-cse/fortiosapi


text:
test: add composer

This PR has been initiated to highlight a problem I've encountered while working on the temporary branch available here: https://github.com/NixOS/nixpkgs/pull/232450.
The core issue is my inability to build composer, which has effectively stalled my progress since composer is required in any PHP derivation. I can reproduce the issue with drupol/composer-local-repo-plugin since they are producing the same outputs.
Here's how you can replicate the issue:

Navigate to the tests directory: cd tests
Run the build command: nix build .#composer -L

A thorough review of the logs will clarify the problem.
Composer is attempting to retrieve a package following a four-part version pattern (Root composer.json requires phpstan/phpstan == 1.10.7.0, found phpstan/phpstan[1.10.7] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.). See the versions there 1.10.7.0 !=  1.10.7 !
However, during the construction of the packages.json file, no four-part version pattern is available – only three-part versions are present.
This discrepancy is leading me to suspect a potential bug in composer.
The creation of this PR is largely driven by this suspicion.
After a little investigation, I notice that four-part version pattern is the normalized version, see it here:

Is it possible to access this value with the composer api ? Yes! With $package->getVersion().

That is indeed weird. The lockfile uses the standard three component versions:
https://github.com/composer/composer/blob/2.5.5/composer.lock#L2041
And the packages field docs do not mention anything like that. I guess we will need to look into Composer source code why it is doing that.

Yes, we should check the source code... Maybe @seldaek has clue?
To summarize in a few words, we are trying to find a way to have full reproducibility on packages built with composer. We are currently blocked because of this issue (among all the others we already fixed).

Actually, building grav is also failing :(

Excellent. This is ready to merge :)

So I'm guessing you don't need my input anymore here? Otherwise let me know what exactly because i kinda lack context here

Sorry @Seldaek, it was a misunderstanding on our part. We did not realize that composer update --lock --no-dev after replacing Packagist with a custom repository in composer.json will still try to lookup dev dependencies in the repository, so we did not include them in the repository. Of course, dev dependencies are always listed in the lock file so without them present in the repository Composer would have no way to update the lock file.
We were somewhat confused by Composer claiming attempt to retrieve with a normalized version when the lockfile just uses three-component version string:

Root composer.json requires phpstan/phpstan == 1.10.7.0, found phpstan/phpstan[1.10.7] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

But once we realized what was happening, we decided to always include all dependencies in the repository.

Ok yeah makes sense!

authors: Seldaek drupol jtojnar


text:
Tracks not showing all the tracks.

the app displays something like this.

but on the web-app we have tracks as per below.

@mananwason  have a look. as this is the first page which is getting loaded when the app starts, so I guess we should keep it with all the tracks.

@SilentFlame Just a api issue. Whatever tracks are exposed by the api, all are displayed on the app, not an issue for the app as such, maybe the scraper.

authors: SilentFlame mananwason

repo: fossasia/open-event-android


text:
fix: Modify placeholders in the Nav Header

user placeholder icon is replaced and the position is changed
event image is replaced

fixes #486

@iamareebjamal how is this? I think this is good for now.Custom image can be added later. please review.

@mejariamol We don't need raster icons, please. If they are changed in future, they'll pollute history as they are binary files. Same can be achieved with vector icons.
Also, the account name is very much below from the icon, please fix it

We don't need raster icons

The vector was not scalable. It was blur with the given width height.

he account name is very much below from the icon, please fix it

I checked gmail app and material guideline, they have aligned image at top and name detail at bottom. I can increase the bottom margin for name little. What do you say? Or just below the image?

and the icon used is same which was used earlier just in png format with better quality. The white is the background set.

But we don't want to use raster. They are dpi dependent and size consuming. Vectors look the same on all devices, are small in size and are not binary files. For all non complex resources, it is recommended to use vectors

The vector was not scalable. It was blur with the given width height.

That's another issue. It can be fixed and should be. Raster is not the solution
The image does not appear to be that far away in this and is in middle

@iamareebjamal please review now. :smile: converted that one into xml.

@mejariamol Looks cool. I am searching/creating a default header bg. We'll update both in the same PR. Will send it by night

@mejariamol Header Image

@iamareebjamal good one!

@iamareebjamal please review.

authors: iamareebjamal mejariamol

repo: fossasia/open-event-orga-app


text:
Reduce space between progress bar and status message

During improvement in the presentation of the build logs, the space between the generation progress bar and the status message increased a bit. Also, the layout of the preview and the Download buttons was changed. Please help it to restore to the previous version.
Before

After

I will send a PR for this.

repo: fossasia/open-event-webapp


text:
PS Lab Logo missing

Screenshot for better understand

Can I work on this issue?

Sure! This logo should be displayed there.

I am new to open source projects can you me guide me?

Sure. The documentation is written in Sphinx. The readme explains how to build the documentation website. The layout of the generated website is defined in conf.py. If you look at Sphinx's documentation you should be able to figure out how to add the logo.

Is this ok?

Yes, that looks good! Please open a pull request.

Is this ok?

Is this ok?

Yes! Please open PR with preview link.

Can I work on this issue ?

From the looks of it @nikhanal has already fixed it. However, they haven't opened a pull request yet. @nikhanal, please do so as soon as possible.
@swapnilsparsh, let's wait until after the weekend. If no PR has been opened by then, feel free to start working on this issue.

I am really sorry that I was late.
I have opened the pull request please view it.

Done in #121 - thank you a lot @nikhanal :)

Done in #121 - thank you a lot @nikhanal :)

My pleasure

authors: anilmaurya61 bessman nikhanal orangecms swapnilsparsh

repo: fossasia/pslab-documentation


text:
fix: check if output dir exists

Description of the change

For multi-gpu lora tuning, the output dir may not exist yet for all the processes, thus resulting in error:
INFO:root:Merging lora tuned checkpoint checkpoint-1250 with base model into output path: /data/anhuong/tuning_output/llama-13b-lora-tone-multi-gpu-test-image
ERROR:root:Traceback (most recent call last):
  File "/app/launch_training.py", line 193, in main
    Path(os.path.join(original_output_dir, ".complete")).touch()
  File "/usr/lib64/python3.11/pathlib.py", line 1108, in touch
    fd = os.open(self, flags, mode)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/data/anhuong/tuning_output/llama-13b-lora-tone-multi-gpu-test-image/.complete'

Note that all of this should be alleviated with the upcoming refactor since this copying will only happen once outside of the multi-gpu tuning.
Built 0.1.0-rc.1 into sft-trainer image and ran to find this bug.

LGTM especially since it will be alleviated with the upcoming refactor. Thanks Anh!

authors: anhuong kellyaa

repo: foundation-model-stack/fms-hf-tuning


text:
feat(Abide): add validator-specific error messages

Description
It would be great to display different error messages depending on failed validation.
Now you can add different error messages for each validator using the [data-form-error-on] attribute:
<input required type="email">
Required
Invalid

BREAKING CHANGE: Foundation.Abide#validateText() no longer checks if the input is required. Use the Foundation.Abide#requiredCheck() method for that.

Closes #10799

Types of changes

[x] Documentation
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (anything that would change an existing functionality)
[ ] Maintenance (refactor, code cleaning, development tools...)

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] The pull request title and template are correctly filled.
[x] The pull request targets the right branch (develop or develop-v...).
[x] My commits are correctly titled and contain all relevant information.
[x] I have updated the documentation accordingly to my changes (if relevant).
[x] I have added tests to cover my changes (if relevant).

Hi @soylent,
awesome PR which also includes new tests.
We'll check it and give you feedback.

Thanks, @DanielRuf. Please let me know if I can make this PR better.

Given the data-attribute API is the most common approach, I think the backwards incompatibility in the JS API is probably fine, but we'll need to note it in release notes.
There is a merge conflict right now - I can address that when merging. @DanielRuf do you see any reason not to merge this for 6.6?

We could also need unit tests but so far it looks good.

Please resolve the conflicts / rebase.

Please resolve the conflicts / rebase.

Done!

This pull request has been mentioned on Foundation Open Source Community. There might be relevant details there:
https://foundation.discourse.group/t/foundation-for-sites-6-6-2/1936/1

authors: DanielRuf joeworkman kball soylent

repo: foundation/foundation-sites


text:
Error: No arguments passed to the base constructor.

Hello,
I'm in the process of deploying an NFT contract on the Anvil testnet, as outlined in the Solidity scripting documentation here. However, I've encountered a constructor error. Could you please guide me on how to pass arguments to the base constructor to resolve this issue?
Thank you.

This is an error from solidity, please read the solidity docs. In particular: https://docs.soliditylang.org/en/latest/contracts.html#inheritance

repo: foundry-rs/forge-std


text:
429 from RPC provider: "future transaction tries to replace pending" When using forge script

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (388c3c0 2023-04-11T00:17:58.707017000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
I have a somewhat complex deployment procedure that produces around 20 transactions. I am using forge script to invoke the deployment on the Goerli network.
I have run multiple deployments in the past with no issue. Now, when running the command I get the error:
Error:
(code: -32000, message: future transaction tries to replace pending, data: None)

If you were trying to resume or verify a multi chain deployment, add `--multi` to your command invocation.

2 of the 21 transactions were successfully broadcast, but it appears that maybe forge is not waiting for the results properly before submitting other transactions with the same nonce?
If I run the same command with --resume, then forge correctly picks up from where it left off, but errors again with the same message after submitting a single transaction.
By checking the nonce of the transaction in etherscan and matching it to the relevant transaction in deploy-latest.json, I can see the the hash field is set as null - which I assume means that forge didn't pick up that this transaction was included in a block.
When running with --resume for 3rd time, more transactions are created, but the hashes of completed transactions are never filled in.
As an example, here is the record from the deploy-latest file for nonce 0xe4 which was a contract creation. The equivalent etherscan transaction is here: https://goerli.etherscan.io/tx/0x829df2c378cadcf10b06ddacfd7726813000e516bf82eff4fda2eab6e8f4b17a
{
      "hash": null,
      "transactionType": "CREATE",
      "contractName": "TransparentUpgradeableProxy",
      "contractAddress": "0xFb97e05422b45fe1e21fB4d70FFE1797dC79d095",
      "function": null,
      "arguments": [
        "0x94da33946150493388dBa3fb77Bb292ed9351657",
        "0x2dFD34e23315d9eB9E59E4567120bA34F6a9C63D",
        "0x"
      ],
      "rpc": "https://eth-goerli.g.alchemy.com/v2/dGQ882Y37nKEkoy6dvAnna5S_x0DoB0n",
      "transaction": {
        "type": "0x02",
        "from": "0xc42721384b6e914f33da870b75d793ccebe576cc",
        "gas": "0xb8531",
        "value": "0x0",
        "data": "[encoded data, 7588 characters]",
        "nonce": "0xe4",
        "accessList": []
      },
      "additionalContracts": [],
      "isFixedGasLimit": false
    },

Edit:
After digging into this, it appears to be caused by rate limiting from my RPC provider.

Running the script caused ~80 concurrent RPC requests to Alchemy, which rate limits me every time. I have just found the --slow flag, though when running with that I just get under the rate limit (forge still does a lot of queries before sending a single tx). However, I then got the error: EOA nonce changed unexpectedly while sending transactions. Expected 237 got 238 from provider. - I am not changing the nonce or doing transactions through any other process.
I think that generally the UX can be improved here:

Detecting 429s from rpc providers (if possible) and emitting a better error message.
Adding the ability to put a client side rate limit on requests to the RPC url.

Just ran into the same problem with a forge script against mainnet. --slow fixes this, but is also very slow (for 30+ transactions). Didn't run into rate limit, but ran into https://github.com/ethereum/go-ethereum/issues/26890

I currently have this bug on mainnet, anyone knows how to solve it?

I currently have this bug on mainnet, anyone knows how to solve it?

It is because rpc limits, just use --resume with running your script until all transactions will be completed.

I encountered this issue today and managed to resolve it by adding --slow. Sharing this here in case someone else faces the same problem and comes across this thread.

authors: Willyham bhaveshpraveen danilych delzennejc kahuang

repo: foundry-rs/foundry


text:
Automatically label known contract addresses in traces

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (7922fd5 2024-02-05T00:19:20.258041000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Intel)
Describe the bug
This issue is a follow-up issue of this one, but since that one is old, I'd like to issue a new one.
It seems 0x0000000000000000000000000000000000000001 is a contract automatically created by foundry, but not labeled in traces:
[0] 0x0000000000000000000000000000000000000001::fallback{value: 1000000000000000000}()

It can be reproduced here by running forge test --mp test/BatchInbox.t.sol -vvv

here's the list of precompiles, probably can be labeled with Name value https://book.getfoundry.sh/misc/precompile-registry ?

authors: grandizzy zhiqiangxu


text:
GM Vision and roofs

related to https://github.com/foundryvtt/foundryvtt/issues/11032
With GM Vision active, Overhead tiles that use vision based occlusion don't fade when a token is selected and the GM has to hover over the tile to see the tokens in a room.
I hope that a Core Foundry change will fix this incidentally, but it's best to raise it here too in case we can get an earlier fix for the whole behavior or if GM Vision needs special handling even after core vision gets changed.

based on a quick test in v11 tokens with vision used to actually use vision type occlusion for this roof even with GM vision active, so they were different from visionless tokens in that regard. So I'd say it's an actual regression in the system/not caught up with the core changes.


text:
Fix broken non-land Base Speed tooltip labels in creature documents

This label was missed when the actor base speed labels were refactored.
Noticed while doing some Familiar Sheet work 👀

It doesn't look like it even appears from PC sheets

Yeah it didnt seem to, but it does on Familiar sheets when they have the corresponding Abilities

authors: j-bs stwlam


text:
Make typing \n send multiple messages

Typing
wixS1 wixS2 wixS3 \n wixS4 wixS5 wixS6 \n wixS7 wixS8 wixS9
should send 3 messages, separated by \n.
No delay when you are mod, 1.2s delay when not.

Grumble grumble #366

duplicate of #366

authors: Evanito fourtf nuuls


text:
🛑 Yudu Salons is down

In 9e936df, Yudu Salons (https://www.yudusalons.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Yudu Salons is back up in b0da2be after 23 minutes.

repo: fourthfloor/uptime


text:
adding curl-runnings and cryptocompare libraries, maintainer avi press

Checklist:

[x] Meaningful commit message - please not Update build-constraints.yml

[x] Some time passed since Hackage upload

[x] On your own machine, in a new directory, you have successfully run the following set of commands (replace $package with the name of the package that is submitted, $version is the version of the package you want to get into Stackage):
stack unpack $package
cd $package-$version
stack init --resolver nightly
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

Thanks!

authors: aviaviavi bergmark

repo: fpco/stackage


text:
Window close, Popups, and Autogrid

This branch adds the following:

Layout and LayoutClass shards
Makes certain variables in Shards public for use in Rare

For UI elements such as the CircularImageButton in Rare (For the purpose of side menu in Rare)

Updates SVG crate and SVG.ToImage, also adding an offset parameter

@guusw Need your advice on adding type safety in the LayoutClass Shard's compose function I think. Regarding the type safety of variables in a table parameter passed to the shard that was mentioned a while ago

Looks good, but I think the main thing I'd change would be to change the tables to params where possible
(UI.LayoutClass
   :Layout {:main_direction LayoutDirection.LeftToRight}
   :ScrollArea {:horizontal_scroll_enabled true})

=>

(UI.LayoutClass
   :MainDirection LayoutDirection.LeftToRight
   :HorizontalScrollEnabled true)

I'd like to avoid having similar but slightly different shards like the popup shards. I think we can implement a generic popup by having most of our interactive shards store the last response they generate on the UI context. The popup shard can then be a parent of a button for example and use the response to render the popup.
If you check https://github.com/fragcolor-xyz/shards/blob/65b677e96012050a593c6094b888b1062fbb55ed/shards/egui/src/lib.rs#L128 you can see I change the context into a struct already so you could add an Option<Response> or something to keep the last response, then clear it before the next frame.

Since the last merge, PopupWrapper, window closable & open fields, AutoGrid shard and some other minor changes have been made. drag-and-drop branch has also been rebased. For your reference and review @guusw
Not sure why certain test files like gfx-cube.shs are failing though?

Moved to #815 with some minor changes

authors: Yttruire guusw

repo: fragcolor-xyz/shards


text:
Overswipe "delete" button does not accept color property

In the latest version of F7Vue, the overswipe button does not accept any color property, when property delete is true.

Delete button is always red and its background controlled by --f7-swipeout-delete-button-bg-color CSS prop, you can change this prop to any color you need

Thank you for the response @nolimits4web - I thought deleting the entry after swipeout must not be allways means to delete the entry ... for example overswipe to move to another list ... but ok, is a workaround :-)


text:
🛑 PEDCO is down

In 25785c1, PEDCO (https://pedco.uncoma.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PEDCO is back up in cd88462.


text:
🛑 PEDCO is down

In c6aa7b0, PEDCO (https://pedco.uncoma.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PEDCO is back up in 8b1ba08.


text:
[Feature request] Lint values in a object

Is your feature request related to a problem? Please describe.
Can't lint values in an object passed to a callee.
My list of callees: ["clsx", "cva"].
This doesn't work:
const buttons = cva({
  variants: {
    variant: {
      primary: "bg-white text-black font-bold px-4",
      secondary: "bg-black text-white font-semibold px-5",
    },
  },
});

This does:
const buttons = cva({
  variants: {
    variant: {
      primary: clsx("bg-white text-black font-bold px-4"),
      secondary: clsx("bg-black text-white font-semibold px-5"),
    },
  },
});

Describe the solution you'd like
I would like for the first example to work.

any progress with this?
this would be awesome!

The MR #185 does not fix this specific issue

@francoismassart It looks like bg-white and bg-red are no contradicting classes in the test setup. This is no different then
classNames or classes.
So linting in a object should be closed, a new issue should be opened for linting contradicting classes for background in tailwind.

Found the issue in the example
bg-red is not a valid Tailwind class. This should be a gradient of red, for example red-50. If added red-50 eslint will give you an error.

Fixed in the latest release v3.8.0

authors: ArekBartnik dipsaus9 francoismassart robotkutya


text:
fix: Update vite-dev-server.js Node IP resolution fix

Node more correctly follows OS native dns.lookup() resulting in this breakage

Fixed https://github.com/frappe/frappe-ui/pull/52/commits/232b17f95889abe5df7bf8e37553f1ecf51de041

authors: shariquerik uhrjun

repo: frappe/frappe-ui


text:
Current day is not always rendered

Hi!
I've found a notable bug.
If all the tasks in the Gantt end at least a month before the current day, the program crashes because the rendered date range does not include the current day and the variable today is set to null.

Will be fixed in #394.

authors: chiarapivetta safwansamsudeen

repo: frappe/gantt


text:
Can't remove rests

Error in console

fixxed (31.03.2015 14:48:26)

repo: freakimkaefig/Music-XML-Analyzer


text:
Couldn't get readme example to work - workspaces wouldn't load

Could you add documentation on how to configure/use your own stable diffusion models? I got timeouts when trying to connect to the models that the stable diffusion tool relies on
Thanks for this project btw! Looks really cool and fits well with something I want to prototype

I ran in to an issue when using the stable diffusion tool today, it worked fine until then.
It seems it is trying to connect to https://huggingface.co/api/spaces/gradio-client-demos/stable-diffusion. This causes a gateway time-out error. My question is: shouldn’t it connect to https://huggingface.co/spaces/gradio-client-demos/stable-diffusion instead?

Hi @giannisanni ! I think the issue with the connection is that hugging face spaces went down briefly this morning. Should be back up now!

Hi @brettimus !
gradio-tools 0.0.9 is now released. This includes a new stable diffusion tool that can be easily duplicated when you pass in your own hf_token, i.e. tool = StableDiffusionTool(hf_token="...", duplicate=True). That will create your own private version of the space. You can then upgrade the hardware.
This should make it easier to avoid timeouts.

Thanks! That's awesome. Appreciate the quick patch

authors: brettimus freddyaboulton giannisanni

repo: freddyaboulton/gradio-tools


text:
Reinforcement learning strategy with Koker

The goal is to implement a reinforcement learning strategy using the Koker algorithm as defined in https://teddykoker.com/2019/06/trading-with-reinforcement-learning-in-python-part-ii-application/

I already started this issue. If someone wants to continue this, I created a branch called 2-koker-strategy and you can find some code in the notebook called strategy-koker.ipynb.

repo: fredmontet/tars


text:
🛑 EC is down

In 12756a3, EC (https://ec.tut.ac.za) was down:

HTTP code: 0
Response time: 0 ms

Resolved: EC is back up in 61bfcdf.

repo: fredre/ecMonitor


text:
Merge refs/heads/1.8/internal/779 into alpha

Merge refs/heads/1.8/internal/779 into alpha

This PR has been merged into alpha. Thanks for your contribution!

repo: fredyk/westack-go


text:
/classes should take advantage of fast-refresh.

Describe the bug
We currently are not taking advantage of refreshing our DOM when we create new classrooms and instead rely on reloading our page to see any changes in our UI. Making the data inside of our classes page rely on a state should help us solve that issue and remove the need to reload the page in order to see any new changes made to the UI.
To Reproduce
Steps to reproduce the behavior:

Go to /classes
Create, delete, or edit a classroom
Page must reload to see any changes to the DOM

Expected behavior
The DOM should refresh to show the new state of the ClassInviteTable component.
Additional context
Currently being worked on in #357

@Komal914 See above.

authors: GuillermoFloresV lloydchang

repo: freeCodeCamp/classroom


text:
fix(.github): re-order change directory for linter

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

This now fails for a proper reason - code is not pretty

Probably want to ignore those markdown files?

authors: ShaunSHamilton nhcarrigan

repo: freeCodeCamp/euler-rust


text:
WT!

Challenge Say Hello to HTML Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

Hello World

Hi @luuzuriaga
Thanks for reporting this issue.
Here are some next steps that you should follow before we can help you with your query:

Check these troubleshooting steps first.
Please use the Chat Rooms or try looking through our forum for help with a specific challenge and any coding assistance.

IMPORTANT:
Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only.
Happy Coding!

authors: luuzuriaga raisedadead

repo: freeCodeCamp/freeCodeCamp


text:
npm run develop fails

Describe your problem and - if possible - how to reproduce it
Follow the guide from scratch at this link
reach till the below command
npm run develop
this command fails with below error

Add a Link to the page with the problem
Tell us about your browser and operating system

Browser Name: NA
Browser Version: NA
Operating System: macOS High Sierra 10.13.3

If possible, add a screenshot here

Same problem. Here they say is a node v10 problem (my version is v10.10.0). I solved as write them with npm i natives

We have refactored the repo since this issue. Please make a fresh clone and the instructions in the docs. You should be good to go.

authors: ktajpuri paolaguarasci raisedadead


text:
Use Clockwise Notation - Tests fail if you add any comment code.

On the Basic CSS: Use Clockwise Notation to Specify the Padding of an Element Lesson.
If you fulfil the course as instructed but also add comments in a multi-line format  such as:
/*
aaaa
*/
Placed outside of the relevant style block and also within it will cause one of the tests will fail and state 'You should use the clockwise notation to set the padding of blue-box class.'
Even though the provided  answer is correct, the commenting breaks the test, this is not the case on previous CSS lessons as I usually add comments.

https://learn.freecodecamp.org/responsive-web-design/basic-css/use-clockwise-notation-to-specify-the-padding-of-an-element
Tell us about your browser and operating system:

Browser Name:  Google Chrome
Browser Version: Version 71.0.3578.98 (Official Build) (64-bit)
Operating System: Mac OSX Mojave

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Note, this issue is reproducible. All it takes is having the comment text contain padding-top or any padding-* variant to cause the issue. The issue occurs anywhere within the code (e.g. inside or outside the <style> block.

Pretty much edge case, but created a PR for it (shrug).

Should there not be another test for not including comments?

authors: T4JC paulywill ronaldcs


text:
Add two cybersecurity command line books

Added Red Team Field Manual and Blue Team Field Manual books with links to Amazon and the ISBNs.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@anthonyecampbell Good add, thank you!

authors: anthonyecampbell paulywill


text:
Add Drop Column example

Add Drop Column example with SQL Code instead of image. Also drop column image was removed since it was the same with the change column image.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Thanks @krekalidis for contributing to this repo! 👍
We're glad to accept your changes and look forward to more contributions from you!

authors: krekalidis thecodingaviator


text:
implementation in php added

implementation in php code block added

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: Due to the fact that this article already has examples using the same approach in other languages, we have decided not to add your example.
Thank you and happy coding.

authors: RandellDawson kabircse


text:
Grammar mistake and typo

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


text:
fix(curriculum): Updated solution to meet test requirements for Positive and Negative Lookahead

Solution requirments require a match containing more than 5 characters.
The current solution has a match being made at a minimum of 5 characters, this should be updated to 6.
var pwRegex = /(?=\w{6})(?=\D*\d{2})/;
instead of
var pwRegex = /(?=\w{5})(?=\D*\d{2})/;

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the master branch of freeCodeCamp.
[X] None of my changes are plagiarized from another source without proper attribution.
[X ] My article does not contain shortened URLs or affiliate links.

Closes #XXXXX

So what string passes the current tests that shouldn't?

In the current sample code, there is no string that passes when it should not.  If you included a sample word of ban12 it would pass with the current guidelines, however it should not as the instructions state a match happens at greater than 5.
Using greater than 5, ban12 should not match.  I think ban12 would be a great sample string to have campers test using a match at greater than 5 and updating the regex to:
let pwRegex = /(?=\w{6})(?=\D*\d{2})/
I should have included the above in the initial post. Thank you

Ok, so it'd be best to include a test for that. I suggest you replace the one for 1234, since it's already covered by the previous one.

@emh1010 Are you going to add the new test?

I updated the PR to reflect this is for the challenge file.

@lynxlynxlynx This PR has gone stale.

@lynxlynxlynx We have not heard from the user since you requested changes on December 8th.  This is a stale PR.

Thanks!
@RandellDawson the change is still an improvement.

@RandellDawson @lynxlynxlynx The wrong regex is still passing:

authors: RandellDawson emh1010 lynxlynxlynx thecodingaviator


text:
Create hello.cpp

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.

authors: gikf rupajsen


text:
'yarn develop' gets error with buildChallenges.js

After a fresh clone of this project and a successful yarn install, I get the following error messages when running yarn develop:
success delete html and css files from previous builds — 0.008 s
error We encountered an error while trying to load your site's gatsby-config.js. Please fix the error and try again.

  Error: /home/tc/ws/learn/seed/buildChallenges.js:78
                ...file,
                ^^^
  SyntaxError: Unexpected token ...

Can reproduce, can you please share your system config?

Ubuntu 16.04.4 LTS
npm v5.3.0
yarn v1.6.0
Let me know if there is any other info you need. Thanks!

@raisedadead That got me past that error. Now I'm getting a new one.
...
success onPostBootstrap — 0.000 s

info bootstrap finished - 7.168 s

ERROR  Failed to compile with 3 errors                                                                                17:44:25

These dependencies were not found:

These dependencies were not found:

* /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-object-oriented-programming-use-closure-to-protect-properties-within-an-object-from-being-modified-externally.json in ./.cache/sync-requires.js
* /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-functional-programming-use-the-every-method-to-check-that-every-element-in-an-array-meets-a-criteria.json in ./.cache/sync-requires.js
* /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-functional-programming-use-the-some-method-to-check-that-any-elements-in-an-array-meet-a-criteria.json in ./.cache/sync-requires.js

To install them, you can run: npm install --save /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-object-oriented-programming-use-closure-to-protect-properties-within-an-object-from-being-modified-externally.json /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-functional-programming-use-the-every-method-to-check-that-every-element-in-an-array-meets-a-criteria.json /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-functional-programming-use-the-some-method-to-check-that-any-elements-in-an-array-meet-a-criteria.json

I tried following the instructions, but I get this:
# npm install --save /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-object-oriented-programming-use-closure-to-protect-properties-within-an-object-from-being-modified-externally.json

npm ERR! path /home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-object-oriented-programming-use-closure-to-protect-properties-within-an-object-from-being-modified-externally.json/package.json
npm ERR! code ENAMETOOLONG
npm ERR! errno -36
npm ERR! syscall open
npm ERR! ENAMETOOLONG: name too long, open '/home/tc/ws/learn/.cache/json/javascript-algorithms-and-data-structures-object-oriented-programming-use-closure-to-protect-properties-within-an-object-from-being-modified-externally.json/package.json'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tc/.npm/_logs/2018-05-02T20_45_00_933Z-debug.log

Any ideas? Thanks!

Hmm this looks something similar to #28

Yes, I think that's the same problem I'm having. @tchaffee, is your /home directory encrypted by any chance?
If so, the problem is that the max filename length with encryption using eCryptfs, which I believe Ubuntu uses by default, is 143 characters. A temporary workaround is just to go into /seed/challenges and to find those three challenge titles and shorten them manually. Then you should be able to complete the build.

@scissorsneedfoodtoo Yes, encrypted home dir. Shortening the lesson descriptions worked for me. Thanks!

repo: freeCodeCamp/learn


text:
changed logo link to home page

closes freeCodeCamp/freeCodeCamp#17533 and #177
Whenever someone clicked on the logo they were taken to the curriculum page, so I have linked it to home page(https://www.freecodecamp.org).

LGTM

@Nirajn2311 Thanks for fixing this!


text:
Firmware file upload fails

Tried to upload firmware file via Files and Scripts -> Files menu and got nginx error after press "Upload file" button:
"413 Request Entity Too Large"

2.0.1 fresh install by install.sh

FW file size is about 16M

Ok. Thats solvable. If it's install script based we can hot patch your nginx config while you wait for me to patch the service. If it's docker i can also fix that. See https://www.google.no/amp/s/www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/amp/ for hotfix.

Closing this as there is bigger fishes to fry atm. You can follow guide above to adjust nginx to allow bigger upload payloads

authors: jarlah jogermech

repo: freeacs/freeacs


text:
Create Music Media package

musicmedia_objects, musicmedia_routes, and musicmedia_forms should be in their own package

Should also add route_utilities and remove non-route code from musicmedia_routes into this new file

repo: freeamac/MacMedia


text:
Copy union subtypes when mixing them in.

Subtypes of unions are pointers. Copy the content of them in the mixin() function to prevent global redefinition to list types for named types.

Reviewed the PR and looks good.  Copying the union type in makes a lot of sense.
Only thing I would have changed was unit tests, I generally create a YANG file in parser/testdata and dump the parse tree to a file for comparison.  Turns out there already was a case that tested union + typedefs + leaf-lists and it started "failing" with the PR only because the test assertion was incorrect.
To see test "failure" run
cd parser
go test -run TestParseSamples

and you will see a diff.  To update the assertion, you could edit the json file, but instead just run:
go test -run TestParseSamples -update

and now the test passed and the test assertion file captures the new fixed, results.  Please add that update to this PR.
Thanks a lot!

I really hope we don't have another of these graph like dependencies... I still have some trouble exactly understanding what the combination of YACC parser and compile.go are doing.

authors: HRogge dhubler

repo: freeconf/yang


text:
Collapsed right column gets double padding on mobile

It's where the "could you translate this" message is

Actually, the same thing seems to happen with the left column (table of contents)

This has been fixed

repo: freesewing/website


text:
add contributor.md

we should document some general information for contributors so it becomes a little bit easier for them to start contribution.

closed by 8b2219fa12fc4b62c79c5cda84a220c3105bf083

repo: freewheel/dashflow


text:
Read pipelines

As specified in freme-project/technical-discussion#62

Implemented.

repo: freme-project/pipelines


text:
feat(build): add watch job for css, refactor gulp

affects: @fremtind/jkl-accordion, @fremtind/jkl-bullet-list, @fremtind/jkl-button,
@fremtind/jkl-card, @fremtind/jkl-checkbox, @fremtind/jkl-core, @fremtind/jkl-datepicker,
@fremtind/jkl-divider-line, @fremtind/jkl-dropdown, @fremtind/jkl-footer, @fremtind/jkl-grid,
@fremtind/jkl-header, @fremtind/jkl-loader, @fremtind/jkl-logo, @fremtind/jkl-message-box,
@fremtind/jkl-radio-button, @fremtind/jkl-text-input
📥 Proposed changes
Gulp is a bit smoother now, only one build style job. Should be slightly faster. Added watch job.
☑ Submission checklist

[x] I have read the CONTRIBUTING doc
[x] yarn build works locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

💬 Further comments
I'll look into creating a tool that starts the watch job on yarn dev in -react-package. And add it to yarn dev in style pkgs.

Can run gulp build:watch in the style packages, and it will react to changes in .scss files. But we might want that to be automatic when you start the example server in a react package.

repo: fremtind/jokul


text:
Oppdaterte ikonkomponenter med Material Symbols

Endrer alle ikonene våre til å bruke Material Symbols fra Google.
Alle ikonene våre er tilgjengelige som før, som komponenter med samme navn og samme props. Annet enn å avhenge av ny versjon av webfonts-pakka, som nå også inneholder ikonfonten, skal det være mulig å ta i bruk de nye ikonene uten noen endringer.
Ny funksjonalitet

Fylte ikoner. Material Symbols støtter både fylte og ikke fylte ikoner. Du kan bytte mellom disse med filled-propen. Fyllet animeres inn og ut! ✨
Automatisk bold. Dersom du bruker ikoner i et element med en tekststil fra Jøkul (f.eks. Heading 3) vil ikonet automatisk få riktig fontvekt (bold eller normal). Dette vil også funke automatisk inne i strong-tags, så nå slipper du å finne riktig variant! 😮💨
Mulighet for flere ikoner. Dersom det trengs et ikon som ikke er blant våre vanlige ikoner (og det er fornuftig å bruke et ikon!), kan man bruke den generelle Icon-komponenten, og velge blant alle ikonene i Material Symbols. 🫨

Ting å tenke på

Fontfila til ikonene er ganske svær. Det er nok en god idé å be nettleseren om å preloade den. Du finner instruksjoner for dette i dokumentasjonen! 📘
Ikke gå helt bananas med ikoner bare fordi vi nå har fått tilgang til flere! Reglene for god bruk av ikoner gjelder fortsatt. Sjekk gjerne med andre team hvis du skal bruke et nytt ikon, så sikrer vi at man bruker samme ikon for samme type handling. 🤜🤛

🎯 Sjekkliste

[x] Nye features er dokumentert (sjekk Contributing om du er usikker på hva som trengs av dokumentasjon)
[x] Testet responsivitet og UU (tastaturnavigasjon, skjermleser)
[ ] pnpm build og pnpm ci:test gir ingen feil

Denne fixes #3795 også vil jeg mene

Ser bra ut. Jeg lurer på om check i checkbox er oppdatert også?

@Stormoen Slik ikonene er bygget opp i kode kan de ikke direkte brukes i checkbox. Hvis dere har endret checkbox til å bruke ikoner fra Material kan vi godt fikse det også, men tror det er like greit å ta det som et eget issue i så fall 😊

authors: ivarni piofinn


text:
Fix len() of the OrderedRingBuffer

The len() function was returning negative numbers in certain use cases, causing assertions to be raised. This fix ensures that the function returns a value equal to or greater than zero, as expected.

Updated unit test based on suggestions from Marenz

repo: frequenz-floss/frequenz-sdk-python


text:
Linked list

Fixes #27

@frextrite I removed the redundant commit. Ready for merge.


text:
Implementing laravel query builder

Do you think that using a query builder package is a good idea?
This is a prototype:
https://gist.github.com/mahmutbayri/4278c2b1c00c42f30b4c54af2c3a5d0a
If we support illuminate/database we can use its many benefits migration, seeder so on.
Thanks.

2nd prototype
https://gist.github.com/mahmutbayri/44e35fa110148665d6f11229ee83427d

@mahmutbayri Thanks for opening this issue.
Looks like a cool idea, definitely something others can use too :+1:
I would say if you get a benefit out of it it's always a good idea ^^
I don't know if this will be a part of the project any time soon, but if it fit your needs go for it!

What @SimonFrings says! :+1: Thank you for sharing, I think this looks like a useful integration and I'm sure this will also help others!
I don't think there's much to be done here other than that, so I believe this has been answered and will close this for now. Please come back with more details if you feel there's anything to add and we can always reopen this :+1:

authors: SimonFrings clue mahmutbayri

repo: friends-of-reactphp/mysql


text:
feat: allow redirect_uri to be passed as parameter for getInstance

This PR allows the redirect_uri to be passed as parameter for the getInstance method in order to override the default redirect_uri format.

:rocket: PR was released in @friggframework/api-module-hubspot@0.13.0 :rocket:

authors: d-klotz seanspeaks

repo: friggframework/frigg


text:
New logos

About the PR

Makes the logos brighter and neater
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: eclips_e

add: Added a new logo!

emo doesn't like the stuff so he can fix it


text:
artifact filter UI redesign

Describe your changes
Added grouping to the Artifact Filter UI and included the RV Filter.
Issue or discord link
#1569
Testing/validation
Places that include the changed component include: Artifact tab, Swap Artifact Modal.

Checklist before requesting a review (leave this PR as draft if any part of this list is not done.)

[x] I have commented my code in hard-to understand areas.
[x] I have made corresponding changes to README or wiki.
[x] For front-end changes, I have updated the corresponding English translations.
[x] I have run yarn run mini-ci locally to validate format and lint.
[x] If I have added a new library or app, I have updated the deployment scripts to ignore changes as needed

It would be best if you created another branch on your repo and made a PR from there. These command should be able to do it:
git switch -c <branch_name>
git push -u origin <branch_name>

then come back here and make the PR again with <branch_name>
Otherwise, our CI will not run correctly

repo: frzyc/genshin-optimizer


text:
update FSharp.Compiler.Tools to include props file again

This addresses https://github.com/fsharp/fsharp/issues/821
@enricosada I've confirmed that the FCT compiler is being used in these situations (after FCT added as nuget package reference)

[x] Old-style .NET project built with dotnet build
[x] Old-style .NET project built with msbuild
[x] Paketized old-style .NET project built with dotnet build
[x] Paketized old-style .NET project built with msbuild
[x] New-style single-target project built with dotnet build
[x] New-style single-target project built with msbuild
[x] New-style multi-target project built with dotnet build
[x] New-style multi-target project built with msbuild

It would be good to have this under CI test but it's not easy to verify that the FCT compiler is being picked up.
@enricosada In order to support builds with dotnet build (where msbuild executes using .NET Core) we unfortunately need a copy of the .NET Core-loadable FSharp.Build.dll.  We don't build this in this repository so a binary copy of the one from the .NET SDK 2.1.4 is used.  However this will bit-rot over time.  I don't know what to do about this.

@dsyme as a note about future work there, i was checking this scenario in the work for paket tools (because i want reproducible up to fsc level, and an easy way to change fsc for testing/etc).
Is really needed to include the fsc task assembly and the target file? For new sdk i mean, now is bundled.
While this work ok with old sdk, with new sdk who iterate faster, is a bit harder to maintain parity, because same package can be used with different version (1.0, or 2.0, or 2.1, etc) and multiple msbuild version.
for dotnet build is already included in the sdk, so overriding FscToolPath/FscToolExe is enough to change the fsc binary used, and the cli api maintain the backward compatibility.
The Fsc task is anyway a bit tied to avaiable sdk properties (used to initialize by task).
So is better:

package fsc + sdk integration (target+task dll) in the package and align to supported sdk version ranges
package just fsc and props FscToolPath/FscToolExe and maintain alignment with cli args

@enricosada Yes, you are right I think.  Can you send a PR for this?
Note there is still a risk of an FSharp.Build --> fsc mismatch, e.g. upgrading to a new SDK may result in FSharp.Build from that SDK sending compiler arguments that the compiler in FSharp.Compiler.Tools doesn't understand. But I think that's ok, the user would just need to upgrade FSharp.Compiler.Tools as well.

authors: dsyme enricosada

repo: fsharp/fsharp


text:
🛑 Platform - Matrix Webclient is down

In 58d2f3e, Platform - Matrix Webclient (https://matrix.physik.kit.edu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Platform - Matrix Webclient is back up in ebf476e.


text:
paket outdated --silent is not silent ?

Description And Repro
Create a paket.dependencies + paket.lock containing outdated stuff
for example Newtonsoft.Json 10.x in lock file and no constraints in paket.dependencies
run paket outdated -s
run paket outdated
It actually write the SAME thing except the performance block
>paket outdated -s
Resolving packages for group Build:
 - MSBuild.Microsoft.VisualStudio.Web.targets 14.0.0.3
 - FAKE 4.64.4
 - FAKE.Lib.x64 4.64.4
 - FSharp.Core 4.3.4
 - Http.fs 4.1.2
 - GitVersion.CommandLine 3.5.4
 - OpenCover 4.6.519
 - MSBuild.SonarQube.Runner.Tool 4.1.0
 - NUnit.Runners 3.8.0
 - ReportGenerator 3.1.2
 - SourceLink 1.1.0
 - NUnit.ConsoleRunner 3.8.0
 - NUnit.Extension.VSProjectLoader 3.7.0
 - NUnit.Extension.NUnitV2Driver 3.7.0
 - NUnit.Extension.NUnitProjectLoader 3.6.0
 - NUnit.Extension.NUnitV2ResultWriter 3.6.0
 - NUnit.Extension.TeamCityEventListener 1.0.3
 - Hopac 0.3.23
 - NETStandard.Library 2.0.1
 - Microsoft.NETCore.Platforms 2.0.1
Resolving packages for group Main:
 - Autofac.WebApi2.Owin 4.0.0
 - Microsoft.AspNet.WebApi 5.2.4
 - Microsoft.Owin.Host.SystemWeb 4.0.0
 - Microsoft.CodeDom.Providers.DotNetCompilerPlatform 1.0.8
 - Microsoft.Net.Compilers 2.7.0
 - Microsoft.Owin.StaticFiles 4.0.0

Expected behavior
I have no idea because i don't really know what silent actually means
Should the %ERRORLEVEL% be set to a specific code error when it is silent ?
What is the purpose of silent when this only way to parse result should not be printed ?
Actual behavior
Verbose (~100 lines for me), but remove Performance ~10 lines
Known workarounds
None

/cc @agross

you're too fast man ;) (and that's amazing)

Does it makes sense to run paket outdated in silent mode? I only use it interactively.
One use-case might be to run paket outdated -s || paket update to perform a scripted update only when there is outdated stuff in the lockfile.

@agross
it could make sense with this : https://github.com/fsprojects/Paket/issues/3136
We use it on nightly + a Board that does reporting for all our ~180 repos
So it kinda make sense in this specific use case

Yep, I agree. So -s should make the outdated command silent and exit 1 accordingly.

authors: agross forki tebeco

repo: fsprojects/Paket


text:
remove command: restrict install to the specified group only

didn't manage to fix the recursive resolver, but here's the smallest #fsharpx contribution possible ;)
references #1598

xoxo

authors: forki theimowski


text:
Workaround for Paket.Push 500 error on VSTS + Linux

Solves #2037.
This is a simple fix that shouldn't cause any issues (seeing as we're already using CLRF from windows previously).

thx

authors: forki varon


text:
Improve Facil description

Updated to match new description in repo.

@cmeeren thnx!

authors: Neftedollar cmeeren

repo: fsprojects/awesome-fsharp


text:
Remove 's blog from items in blog section

DRY

Thank you!

authors: VPashkov eugene-g


text:
Pytorch example with alluxiofs

An example that uses Alluxiofs to speed up pytorch distributed NLP training with large CSV files.
Formatted the file using black and reorder_python_imports.

@lucyge2022 @LuQQiu For your review. Thanks!

@lucyge2022 Moved alluxio_fs initialization and file preprocessing to the parent process. Add dependencies in the top comment lines.

@SibylYang  also there's some test case failure, the on in CI/lint seems to be bcos of style, can u use pre-commit tool (apt-get install pre-commit) to screen thru the scripts, it will correct the code style for you.
for the CI/Tests , can u make this change to file tests/conftest.py

@lucyge2022 code updated to address your comments

repo: fsspec/alluxiofs


text:
Is it possible to declare generic parameter type in Hook methods

I am trying to create hook methods for my project, the hook method arguments are not primitive data types, they are typically different type of classes in my project. If I have to declare my Hook methods in Hook classes, I am forced to make all the parameter classes available during the compilation. Will there be any simple way to declaring generic hook methods with generic parameter types where the actual parameter type is not available during Hook classes compilation?

To be more specific, how can I create a hook without providing someclass.test.com class file when I am compiling the Hook classes.
hook method :  someMethod (someclass.test.com param1)

There is a work around for this , I can create dummy classes in Hook class files and proceed. I have tested this with Promagent and its working so you can close the issue.

Great to hear that you found a way to make it work. To clarify (for other people who might find this): In the hook methods you specify the parameter types of the method you want to instrument. If an other parameter type is passed in at runtime (like your method accepts class List and at runtime you get an ArrayList) it will work. The important thing is that the method signature of your hook is the same as the method signature of the class you are instrumenting.

authors: fstab kraghuveer

repo: fstab/promagent


text:
Detekcija i klasifikacija košarkaške lopte i igrača

Tim:

Marković Petar - SW73/2018
Mateja Ćosović - SW9/2018

Asistent:

Vidaković Dragan

Definicija problema:
Detekcija i klasifikacija košarkaške lopte i igrača na košarkaškoj utakmici upotrebom odgovarajućih YOLO algoritama.
Skup podataka:
Za trening podatke ćemo koristiti isečke sa košarkaških utakmica i praviti naš custom dataset, labelovanjem igrača i lopte. Test podaci bi takođe bili isečci košarkaških utakmica.
Metodologija:

YOLOv3
YOLOV3-tiny
YOLOv4
YOLOv4-tiny

Evaluacija:
Kao metriku za merenje performansi iskoristićemo preciznost i tačnost nad testnim podacima.

Da li će modeli navedeni u metodologiji biti ručno implementirani, ili će se koristiti gotovi?
Da li se evaluacija odnosi na kompletan problem, ili samo njegov određeni deo (npr. klasifikaciju)?

Pozdrav,
Za sada je ideja da koristimo gotove modele.
Što se evaluacije tiče, verovatno bismo koristili mAP funkciju za testiranje modela.

Tema odobrena.
Ostavite link ka GitHub repozitorijumu projekta.
Srećan rad.

https://github.com/markuza99/YOLO-Basketball-Object-Detection-And-Tracking


text:
Error fetching eufy_security data

Please check existing (open or closed) issues before creating a new one. (https://github.com/fuatakgun/eufy_security/issues?q=is%3Aissue+)
If this is not an issue, you can use Discussions (https://github.com/fuatakgun/eufy_security/discussions) section.
Describe the bug
I have installed this integration and add-on 2 days ago. On the first day everything was working fine (beside the battery percentage wasn’t correct). I have made automation that turn off the camera’s when at home and when leaving they must be on. And since today 1 camera isnt reacting for turning on/off and getting this error message:
This error originated from a custom integration.
Logger: custom_components.eufy_security
Source: custom_components/eufy_security/eufy_security_api/web_socket_client.py:86
Integration: Eufy Security (documentation, issues)
First occurred: May 31, 2023 at 20:41:33 (218 occurrences)
Last logged: 00:18:33
Unexpected error fetching eufy_security data:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 217, in _async_update_data
return await self.update_method()
File "/config/custom_components/eufy_security/coordinator.py", line 85, in _update_local
await self._api.poll_refresh()
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 160, in poll_refresh
await self._send_message_get_response(OutgoingMessage(OutgoingMessageType.poll_refresh))
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 343, in _send_message_get_response
await self.send_message(message.content)
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 352, in send_message
await self._client.send_message(json.dumps(message))
File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 86, in send_message
raise WebSocketConnectionError()
custom_components.eufy_security.eufy_security_api.exceptions.WebSocketConnectionError
Additional information
Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

Home Assistant Installation Type (OS - Supvervised - Core):
Home Assistant Core Version: core-2023.5.4
Eufy Security Add-on Version: 1.5.2
Eufy Security Integration Version: V6.2.0

Hardware Information;

Camera Model: T8410

Live Streaming Protocol (RTSP/P2P):

Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624)

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

Would you share your device with me in case further debugging required? (Yes/No): No

Additional context
Add any other context about the problem goes here.

please follow the template and generate debug logs and re-open


text:
我不会用github，有没有直接使用的

不会用，有教程？

我下载的没有多开，谁来教一下

怎么多开的，怎么答题的

我是小白，不是这专业的，希望博主教一下，谢谢

我是小白，不是这专业的，希望博主教一下，谢谢

您好，可以直接下载就可以了。

我是小白，不是这专业的，希望博主教一下，谢谢

您好，可以直接下载就可以了。

不能多开啊，也不能多开网页

您扫码登录，后面都是自动了的呀

多开，就是再开一个窗口。

多开，就是再开一个窗口。

开了不行啊

更新了，请按照说明更新

更新了，请按照说明更新

不会

使用最新的app.asar替换resources/app.asar

使用最新的app.asar替换resources/app.asar

换了还是没有多开

打开两个exe啊

repo: fuck-xuexiqiangguo/Fuck-XueXiQiangGuo


text:
Fix path to image

I had to tweak the path to an architecture diagram image in the README. Hopefully it shows up now.

Looks like it will work now. https://github.com/fugro/AutoTimeLiner/tree/RDAMT-256-update-architecture-diagram/DotNet

repo: fugro/AutoTimeLiner


text:
Classes and properties (attributes) are not linked in a loaded model

Emojiopoly's MonopolyClass has no attributes while navigating. Furthermore, an attribute of MonopolyClass (e.g. jackpot) has nil for a parentType.
It appears to be a problem with the import, because if I addAttribute: of jackpot to MonopolyClass, it shows up in the navigation.

Moose (10) only has navigation (and support for calculation of lcom2 for example) if attributes are the parts of a class. The .json needs to use this name (for now) even if we call them properties in TypeScript.

repo: fuhrmanator/FamixTypeScriptImporter


text:
Possible Unhandled Promise Rejection

After debugging my app for a while, I tracked down this warning:
"Possible Unhandled Promise Rejection (id: x):" (x increments)
to this line:
firestack.database.ref('events').orderByChild('ministryID').equalTo(i.toString()).on('value', this.handleEventUpdate.bind(this));
The code functions ok, but the warning makes me nervous.  I know that the warning is not triggered in handleEventUpdate, but something about this line causes the error and I don't know how to catch the error and print it out.  Any ideas?

I have the same problem and my code works only when I mount the component for the first time. If I navigate elsewhere and then come back, I get the "Possible Unhandled Promise Rejection".
Anybody has an idea of what can cause this ?

I'm starting to get it. If I navigate my app via react-native-router-flux (rnrf) componentWillUnmount is never called, so I cant turn off Firebase's listener, so somehow something considers it doesn't have to do the rendering job again.
If I just "close" the component with Actions.pop(), then componentWillUnmount is called, then I can do this.itemsRef.off('value'), then turn it on again on the next call, then it works fine. My problem is that my navigation is not compatible with that process.
A work around can be to call this.itemsRef.once('value') on componentWillMount, then this.itemsRef.on('value') on componentDidMount. It might be the normal way to proceed although I have an ugly feeling about this (because in the end the listener is never removed).

Seems the OP was looking for something like the ES6 construct to trap promise failures? The ".then().catch()" construct reliably solves yellowbox warnings on promise objects (on iOS iPhone simulator anyway).
Firestack source code shows "promisify". Runtime promise objects might mean we need to trap a promise failure. I'm guessing this is when we cannot insure our request returns with a response (?). Something like might work:
firestack.database.ref('events')     .then((eventRef) => {         eventRef.orderByChild('ministryID').equalTo(i.toString()).on('value', this.handleEventUpdate.bind(this))     }     .catch((err) => {     alert('Error: listenForAuth event failed.',  err) });

I'm experiencing this warning as well. Not sure what's causing it. I'll post back if I discover the issue.
Does anyone know if this repo is still being maintained?

@SteffeyDev Looks like mine a is different issue. I usually do console.disableYellowBox = true; until I fond the solution.

@philohelp - were you able to solve this issue ? I am running into exact same issue as you described above. :(

authors: AndrewHenderson SteffeyDev manishtuteja10 nearodney philohelp

repo: fullstackreact/react-native-firestack


text:
Abstract Config Option Values in Code

See example for creating options to be used for plugin configurations:
https://learn.getgrav.org/cookbook/admin-recipes
Rather than testing $placement == 'top'
we should retrive the value for 'top' from the configurations.
Something like $this->version = $this->grav['plugins']->get('admin')->blueprints()->version;
... so dump out the blueprints and figure out how to access the value map abstractly.

Specific example @ginkgomzd referenced:
https://learn.getgrav.org/cookbook/admin-recipes#add-a-custom-select-field
Other reference (may or may not be helpful):
https://learn.getgrav.org/forms/blueprints/fields-available#the-array-field
https://learn.getgrav.org/forms/blueprints/example-plugin-configuration

authors: fulltrucker ginkgomzd

repo: fulltrucker/modified-date


text:
Errors when a generic class exists in Models folder.

Hey team!
I bumped into an issue when using this lib, possibly because I'm doing something unexpected.
In my models folder I have some classes which other models implement, for example /models/Generic/Choice.php isn't actually a model that maps to a database table, it's just a model class that some "real" models implement.
This seems to have caused the generate interfaces process to get very sad. Maybe because you try to generate for all files that exist in /models?
Hopefully this somewhat vague information is useful in tracking down a bug! Please let me know if I can be more specific.
✌

@n1c i think one solution to this is maybe add a feature where you can specify something like $modelTyperIgnore = true and then this package just bypasses it completely - we can get to it when we get time, PR's are more than appreicated!

What happens to that class when you use the internal Laravel model show command for that?
For example:
./artisan model:show Generic/Choice

also would be helpful to know if these are traits or classes this is happening too.

I made a repo here so you can see exactly the (broken) setup I was trying: https://github.com/n1c/modeltyper-test
➜  artisan model:show Generic\Choice

   ERROR  Target class [App\Models\GenericChoice] does not exist.

Interesting to see there it seems to strip out the \. There might be a mismatch of assumptions where Laravel doesn't want models to ever be in a sub-folder while modeltyper doesn't mind?

@n1c thanks for the example repo, yea not sure exactly whats going on with that, but I can take a look at see if I can figure out.

ok @n1c I believe I was able to fix, should be updating the release soon

Awesome, looking forward to it!

@n1c https://github.com/fumeapp/modeltyper/releases/tag/v1.2.1

Looks like packagist doesn't auto-update, is that something ya'll do manually?

yea looks like @acidjazz has to do that

done @n1c

Nice one, thanks team! 🥳

authors: acidjazz n1c tcampbPPU

repo: fumeapp/modeltyper


text:
example/linux-example: add newline in printf format

example/linux-example: add newline in printf format
before
➜  /home/mi/xiaomi/embedded-cli git:(dev) ./build/examples/linux-example/embedded_cli_linux
Cli is running. Press 'Esc' to exit
Type "help" for a list of commands
Use backspace and tab to remove chars and autocomplete
> 123 456 789
Received command: 123
                     Arg 0: 456
                               Arg 1: 789
                                         >
>
> abc edf ghi
Received command: abc
                     Arg 0: edf
                               Arg 1: ghi
                                         >
>
> exit
Cli will shutdown now...
➜  /home/mi/xiaomi/embedded-cli git:(dev)

after
➜  /home/mi/xiaomi/embedded-cli git:(dev) ✗ ./build/examples/linux-example/embedded_cli_linux
Cli is running. Press 'Esc' to exit
Type "help" for a list of commands
Use backspace and tab to remove chars and autocomplete
> 123 456 789
Received command: 123
Arg 0: 456
Arg 1: 789
> abc def ghi
Received command: abc
Arg 0: def
Arg 1: ghi
>
>
> exit
Cli will shutdown now...

Signed-off-by: Junbo Zheng zhengjunbo1@xiaomi.com

Thanks for your contributions!

authors: Junbo-Zheng funbiscuit

repo: funbiscuit/embedded-cli


text:
[WIP] Dicebot 클래스를 추가

Dicebot 클래스를 추가합니다.
이 PR은 #6 이슈와 관련됩니다.

머릿말 WIP(working in progress)는 의미로 사용했습니다. 아직 작업중이니 merge대상은 아닙니다. 구현을 끝내고PR을 올리는 것보다 좀 더 빨리 코드를 동료들에게 공유하기 위함입니다.

코드가 완성되어 WIP머릿말을 제거합니다.
@funprog/core 리뷰 부탁합니다.

dice를 roll 하는 core 기능을 만든다고 생각을 해보면, object name이 DiceBot보다 조금 하위 level의 이름이면  더 좋을 것 같다는 생각이 들지만, 어떤것이 좋을 지는 생각이 잘 안나네요.

@younggi

조금 하위 level의 이름

이라고 표현하신게 더 구체적인 이름을 의미하시는 건가요?

slack의 api request를 처리하는 부분까지를 포함한 부분 DiceBot이라 생각이 들어서 의견 적어봤습니다.
하위 level이란 이름은 모호했네요..

request 처리 부분 => 정렬님 부분
dice bot logic 부분 => 진욱님 부분
==> 전체가 DiceBot 인가 하는 생각도 들어서...

작은 시작이라 큰 문제는 없겠지만, 전체 slack bot에서 layer가 구분되면 함께 작업하는데 좀 더 편할까..하는 생각에 적어봤습니다.
funbot 이니 다른 bot도 만들어 넣을 수 있으면 좋겠다는 생각도 들었네요...

말씀하신 좀 더 구체적인 이름일 수도 있는데, 일단 그냥 진행하셔도 됩니다.~ ^^

@younggi 네 좋은 의견이십니다. 그런데 지금 상태에서는 디자인을 최대한 고려하지 않고 Dice Bot 구현에 대해서만 촛점을 맞추는게 어떨까요? 아마 @kwoolytech 님도 #14 에서 비슷한 고민을 하고 계시지 않나 생각됩니다.

Decent start.

넵~ 고고~ 하시죠^^

@younggi 넵 감사합니다. :) @myeesan 님 리뷰의견이 궁금한데 듣고 진행하는 건 어떨까요?

넵 방금 서버 테스트 완료했습니다. 우선 Request 부분 핸들링은 다음 오프 이후에 결정하는게 좋을 것 같습니다. 현재 Web hook 방식 외에 Command 방식도 있는데 어떤 방식을 사용할지 결정해야 하고요, Request를 직접 처리하려면 웹 프레임워크를 다뤄야 해서요. 우선은 dice bot 구현 부터 완료하고 진행해도 무리 없다고 생각합니다.

다음 시간에 The Rules of the Open Road 내용 같이 한번 봤으면 좋겠네요. 아래는 이 문서의 일부를 발췌한 것입니다.

When you think the code is done, don’t merge it into master; instead, open a pull request from your working branch to master. This pull request will give your fellow contributors a place to review the code, and to discuss your work. Once the review is done and the discussion has ended, one of the reviewing contributors will merge the pull request. You should never merge your own pull request. Having another contributor merge the pull request does one better than just saying “Ship It!”.

몇몇 분들이 이 PR 승인 의견을 주셨습니다. merge해도 되겠다는 판단이드는데요. 그런데 제가 직접 merge를 하는 것은 위 내용과 같이 적절하지 않다고 생각되네요. 다른 분이 merge 해주시면 좋겠네요.

So, your intention on this PR was to create a skeleton of the dice class and the test code. Good job on processing everything so far!  FYI, I am seeing this message, Only those with write access to this repository can merge pull requests.

I have updated the decription so that people may know the scope of this PR. Hope you don't mind. :)

Only those with write access to this repository can merge pull requests.

I am going to address this issue. Thank you for pointing that out.

I have updated the decription so that people may know the scope of this PR. Hope you don't mind.

I must say 👍

authors: jwChung kwoolytech myeesan younggi

repo: funprog/funbot


text:
#94 pubkey info on lightning lite info

Fixes #94 Worked for lnd but was not able to test with cl because I get on error before I can can parse the info further.
Jun 06 21:39:18 python[110174]:   File "./app/repositories/ln_impl/cln_grpc.py", line 477, in get_ln_info_impl
Jun 06 21:39:18 python[110174]:     res = await lncfg.cln_stub.Getinfo(req)
Jun 06 21:39:18 python[110174]:   File "/usr/local/lib/python3.9/dist-packages/grpc/aio/_call.py", line 290, in __await__
Jun 06 21:39:18 python[110174]:     raise _create_rpc_error(self._cython_call._initial_metadata,
Jun 06 21:39:18 python[110174]: grpc.aio._call.AioRpcError: <AioRpcError of RPC that terminated with:
Jun 06 21:39:18 python[110174]:         status = StatusCode.UNAVAILABLE
Jun 06 21:39:18 python[110174]:         details = "failed to connect to all addresses"
Jun 06 21:39:18 python[110174]:         debug_error_string = "{"created":"@1654547958.117541682","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3093,"referenced_errors":[{"created":"@1654547958.117538015","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":163,"grpc_status":14}]}"
Jun 06 21:39:18 python[110174]: >
Jun 06 21:39:18 python[110174]: ERROR:    Application startup failed. Exiting.

@fusion44 can I merge the PR?


text:
Add a README with some basic instructions.

Fixes #202.

This change is

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

bors r+

Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

bors r+

Comments from Reviewable

bors r+

authors: jonathanj mithrandi

repo: fusionapp/fusion-index