akash-mohanto added Readme file

@kranurag7 have i done it in a correct way?

@kranurag7 one more thing i need to ask you is whenever i make progress to this journey...lets say i learned some basic linux command today and now i want to update that in my fork of this repo...should i have to create a new branch or can i just make a new folder..and push the changes in my origin main branch. please guide.

@akash-mohanto Now it's good. Regarding the second question, You can create a new branch if you wish or push the new changes to the same branch as well.


I switch between the choices using up and down arrow, and the line keeps repeating. I assume this is more of an error in TTY::Cursor, rather than TTY::Prompt, but I'm not sure where you want bug reports.
Source code:
require "bundler/setup"
require "tty-prompt"

prompt = TTY::Prompt.new

selected = prompt.select "What is your choice" do |menu|
  menu.choice "First"
  menu.choice "Second"
end

puts "Selected: #{selected}."

Versions of things:
GEM
  remote: https://rubygems.org/
  specs:
    equatable (0.5.0)
    necromancer (0.3.0)
    pastel (0.6.1)
      equatable (~> 0.5.0)
      tty-color (~> 0.3.0)
    tty-color (0.3.0)
    tty-cursor (0.3.0)
    tty-platform (0.1.0)
    tty-prompt (0.6.0)
      necromancer (~> 0.3.0)
      pastel (~> 0.6.0)
      tty-cursor (~> 0.3.0)
      tty-platform (~> 0.1.0)
      wisper (~> 1.6.1)
    wisper (1.6.1)

PLATFORMS
  ruby

DEPENDENCIES
  tty-prompt

BUNDLED WITH
   1.12.5

Thanks for reporting this. It seems that El Capitan has a different interpretation for the ansi escape codes that move arrow up and/or clear the line. I agree, the problem is most likely in tty-cursor dependency. I don't run El Capitan so would really appreciate help here, otherwise I'm not sure how I would fix it as it works for me.
 Maybe the failure shows the different escape codes being used?
Is this behaviour similar when you run multi_select? I would also try the mask and slider as they use similar line clearing ansi. If mask works as expected then it may imply that up/down arrow ansis are broken. Anyhow, you should be able to run quickly all the examples.

One change that has been introduced in new tty-cursor was the code for moving to the previous line. see. Therefore, would it possible for yourself to uninstall tty-prompt v0.6.0 and install v0.5.0 and see if select works there?

Ok, neither multi_select, mask or slider clears data as expected. Here's what mask looks like, with an interesting error:
Are you on track for Launch Zipline by 2019-09-10? stty: 'standard input': unable to perform all requested operations
Are you on track for Launch Zipline by 2019-09-10? astty: 'standard input': unable to perform all requested operations
Are you on track for Launch Zipline by 2019-09-10? •sstty: 'standard input': unable to perform all requested operations
Are you on track for Launch Zipline by 2019-09-10? ••dstty: 'standard input': unable to perform all requested operations
Are you on track for Launch Zipline by 2019-09-10? •••astty: 'standard input': unable to perform all requested operations

Test suite for TTY::Prompt is all green!

Hmmm.... the mask error makes me think that when select is called what may happen is that the error gets printed out to sdterr and then when the line is cleared it only clears the error and leaves the actual line to be cleared untouched? That would explain why the tests are passing as they are using StringIO to mimick stdout and stderr. Do you know where this error is coming from? It seems that unix stty utility tool is misbehaving?

That sounds like a good theory. I'll dig.

Yes, indeed, turns out that %x[stty …] for Echo and Raw sometimes prints an error to standard error (although I'm not sure when, or why). If I redirect stdout/stderr to File::NULL for all four of these commands, it appears to work properly.
system("stty echo", $stdout => File::NULL, $stderr => File::NULL)

Nice work, I suppose we could %x{ stty ... >/dev/null 2>&1 } and thus avoid shelling out with system command? Alternatively, we could try to use io/console and latest echo= implementations? Would you have time to submit PR?

Possibly today! Do you want to keep the separate Echo and Raw-classes? They might be superfluous if io/console is to be used, but since they've been declared public maybe we should keep them.

I'm not really sure since when io/console is part of standard lib? Currently the code runs even on ruby 1.9.3? I'm not precious about these classes and quite frankly would welcome removing them. Do you have time to look into this?
Another step after this fix is to extract the Reader to another dependency as it's usuful in its own way and provides conveniences that I can see easily applicable to other CLIs.
Point taken re runing external commands, no matter how many times I use these I get them mixed up, that's probably why I've created tty-command

I created a quick PR using the workaround code I used locally that uses io/console. If you decide that you'd prefer the system approach instead I'm happy to rewrite the PR; it's all just code. :)

Released v0.7.0. Enjoy!


[bn] Localizes content/bn/docs/tasks/tools/included/optional-kubectl-configs-zsh.md

Signed-off-by: Asif Zubayer Palak<EMAIL_ADDRESS>Localizes content/bn/docs/tasks/tools/included/optional-kubectl-configs-zsh.md  to Bengali
This is an initial PR as may need some improvements!
Tracking issue: #31677

/label tide/merge-method-squash


Allow exit

Adding ability to force exit from inside an EM hook - required to get redcap_custom_verify_username to work without the ability to pass return parameters.  This is also relevant to #89 for @lsgs and @mmcev106 .
Inside my config.json
  "allow-exit": [
    "redcap_cuxstom_verify_username"
  ],

Inside my EM hook:
public function redcap_custom_verify_username($username) {
    ....
    // Previously with this hook, you returned $status and $message, but now you have to render the results yourself.
    if ($status) {
        if (strlen($message) > 0) {
            echo "
" . $message . "
";
        }
    } else {
        echo "
" . $message . "
";
        exit();  // This prevents the rendering of the rest of the user rights page...
    }
}

Per past discussions, I'm not sure we can or should ever support exiting in the middle of a hook, or any other action that allows one module to change the behavior of another module without some kind of consent from the latter module.
In a few hours, I believe I could made the required changes in REDCap and the module framework to allow return codes to work with the redcap_custom_verify_username hook.   I think the delayModuleExecution() method might even be used to allow multiple modules to run redcap_custom_verify_username on the same project.  I believe this solution will be easier to support long term.  If this is holding you back, would you like me to see if I can get the OK to work on this?

Per issue #89 we landed on a different strategy (at least for now).  Closing...


Cluster: automatic nodes discovery not working with remote host

My current setup is the following:
I have a machine on IP <IP_ADDRESS> which hosts a redis cluster with 3 masters (ports 7000, 7001 and 7002) and 3 slaves (ports 7003, 7004, 7005).
The client machine is on IP <IP_ADDRESS> and I pass the configuration:
new Redis.Cluster([{
            port: 7000,
            host: "<IP_ADDRESS>"
        }], {db: 0});

the issue is that my redis node on port 7000 keeps receiving an unlimited amount of "info" requests but never receives the actual requests made within the client code. Looking at the code I think I found the source of the issue:
In the method Cluster.prototype.getInfoFromNode there is a command redis.cluster('slots',... and the results of this command are like this:
[ [ 0, 5460, [ '<IP_ADDRESS>', 7000 ], [ '<IP_ADDRESS>', 7003 ] ],
  [ 10923, 16383, [ '<IP_ADDRESS>', 7002 ], [ '<IP_ADDRESS>', 7005 ] ],
  [ 5461, 10922, [ '<IP_ADDRESS>', 7001 ], [ '<IP_ADDRESS>', 7004 ] ] ]

What happens is that the redis node on <IP_ADDRESS>:7000 replies with the list of nodes that are part of the cluster but it reference them with their localhost address (<IP_ADDRESS> instead of <IP_ADDRESS>). Thus, ioredis tries to connect to theses nodes on <IP_ADDRESS> and keeps getting ECONNREFUSED (because the client machine does not host any redis instance).
Note: I tried to pass all the nodes to the Redis.Cluster constructor and I experienced the same "info" loop issue

Thats likely a problem with setting up your cluster

On 24 Sep 2015, at 14:24, Adrien-P<EMAIL_ADDRESS>wrote:
My current setup is the following:
I have a machine on IP <IP_ADDRESS> which hosts a redis cluster with 3 masters (ports 7000, 7001 and 7002) and 3 slaves (ports 7003, 7004, 7005).
The client machine is on IP <IP_ADDRESS> and I pass the configuration:
new Redis.Cluster([{
port: 7000,
host: "<IP_ADDRESS>"
}], {db: 0});
the issue is that my redis node on port 7000 keeps receiving an unlimited amount of "info" requests but never receives the actual requests within the client code. Looking at the code I think I found the source of the issue:
In the method Cluster.prototype.getInfoFromNode there is a command redis.cluster('slots',... and the results of this command are like this:
[ [ 0, 5460, [ '<IP_ADDRESS>', 7000 ], [ '<IP_ADDRESS>', 7003 ] ],
[ 10923, 16383, [ '<IP_ADDRESS>', 7002 ], [ '<IP_ADDRESS>', 7005 ] ],
[ 5461, 10922, [ '<IP_ADDRESS>', 7001 ], [ '<IP_ADDRESS>', 7004 ] ] ]
What happens is that the redis node on <IP_ADDRESS>:7000 replies with the list of nodes but with the localhost address (not the <IP_ADDRESS>). Thus, ioredis tries to connect to theses nodes on <IP_ADDRESS> and keeps getting ECONNREFUSED (because the client machine does not host any redis instance).
Note: I tried to pass all the nodes to the Redis.Cluster constructor and I experienced the same "info" loop issue
—
Reply to this email directly or view it on GitHub.

If anyone has managed to setup ioredis with a cluster on another machine, I'd be happy to know your configuration

Hi @Adrien-P
Thanks for using ioredis. The redis servers running on the other machines returns <IP_ADDRESS> is because you bound the redis to the wrong network interface (in this case, bind <IP_ADDRESS>).
You can refer to this issue for more details: https://github.com/antirez/redis/pull/1590/files.

Hi @luin
thanks a lot for your answer. bind is definitely the option I was looking for.
For those interested I added this line to my redis.conf files for each node:
bind <IP_ADDRESS> <IP_ADDRESS>
now it works well.
On a side note, we just moved to ioredis from node_redis mostly because of the support of Redis Cluster. The migration has been very easy

:laughing:


OverlappingRange Exception when Converting PDF to Excel

Hello,
I've been using the img2table library to convert PDFs into Excel files, and I've encountered a problem. When running the to_xlsx method, I receive an OverlappingRange exception from the xlsxwriter library. The specific error message is:
xlsxwriter.exceptions.OverlappingRange: Merge range 'L12:Q16' overlaps previous merge range 'L9:N12'.
This error suggests that the library is trying to merge cells in Excel that are already part of another merged region. This happens even after I've cropped the PDF to avoid potential issues with certain regions. The PDF I'm working with is a schematic with various tables.
To try and resolve this issue, I've added a step to my processing where I crop the outer frame of the PDF, as I suspected that the library might be detecting it as a table and this was causing the error. This approach seemed to work sometimes but not always, so it's not a reliable solution.
Here is the code I've been using and a sample pdf i am working on:
H60NDA10BR001  1.pdf
`
import os
import cv2
import tkinter as tk
from tkinter import filedialog
from PIL import Image
import numpy as np
from pdf2image import convert_from_path
import img2table
from img2table.document import Image as Img2TableImage
from img2table.ocr import PaddleOCR
ocr = PaddleOCR(lang="en")
poppler_path = r"C:\Users\alchayah\Desktop\JustInputs\poppler-23.05.0\Library\bin"
comment # Define the fraction of the image you want to crop
comment  # These values should be between 0 and 1
crop_fraction_y = 0.024  # Crop 10% off the top and bottom
crop_fraction_x = 0.017  # Crop 10% off the left and right
def main():
# Open file dialog to select input PDF
input_pdf_path = filedialog.askopenfilename(
title='Select input PDF', filetypes=[
('PDF Files', '*.pdf')
]
)
if not input_pdf_path:
    print("No input PDF selected. Exiting.")
    return

# Open directory dialog to select output directory
output_dir = filedialog.askdirectory(title='Select output directory')

if not output_dir:
    print("No output directory selected. Exiting.")
    return

# Convert the PDF to images
images = convert_from_path(input_pdf_path, poppler_path=poppler_path)

for i, image in enumerate(images):
    # Convert PIL Image to OpenCV image (numpy array)
    open_cv_image = cv2.cvtColor(np.array(image), cv2.COLOR_RGB2BGR)

    # Get the dimensions of the image
    height, width, _ = open_cv_image.shape

    # Calculate the cropping coordinates
    y = int(height * crop_fraction_y)
    h = height - 2*y  # Subtract twice the margin to get the height of the central part
    x = int(width * crop_fraction_x)
    w = width - 2*x  # Subtract twice the margin to get the width of the central part

    cropped = open_cv_image[y:y+h, x:x+w]

    # Convert the cropped image back to a PIL Image
    cropped_pil = Image.fromarray(cv2.cvtColor(cropped, cv2.COLOR_BGR2RGB))

    # Save the cropped image to a file
    cropped_image_path = os.path.join(output_dir, f'cropped{i}.png')
    cropped_pil.save(cropped_image_path)

    # Create an img2table Image object
    img2table_image = Img2TableImage(src=cropped_image_path)

    # Export to Excel
    output_xlsx_path = os.path.join(output_dir, f'output{i}.xlsx')

    img2table_image.to_xlsx(
        output_xlsx_path,
        ocr=ocr,
        implicit_rows=False,
        borderless_tables=False,
        min_confidence=50
    )

    print(f"Output saved to {output_xlsx_path}")

if name == "main":
main()
`
Could you please assist me in understanding why this error is occurring and how it might be resolved? Any assistance you could provide would be greatly appreciated.

Hi,
Thanks for the feedback.
The error was on my side and the handling of merged cells when creating the XLSX file. I have fixed the issue and I will include it in the next release.


chore: Remove QuickJS-emscripten-sync dependency

Refactor data exchange between host and guest system to use standard quickjs-emscripten.
Reasons:

reduce dependencies
package seems not to be highly maintained

quickjs-emscripten-sync provides a lot of useful functionality in marshaling data, it would be a considerable amount of work to replace this functionality, in which my personal thoughts are that this time could be better spent.
Alternatively, the author of quickjs has mentioned "Consider integrating quickjs-emscripten-sync for automatic translation." about integrating this directly into the quickjs-emscripten project. Maybe a discussion could be opened up to make this part of the quickjs-emscripten project with a strategic PR?
Just my thoughts, I hope you don't mind them. The project looks very interesting and I shall try to give it some testing soon.

There are several reasons to remove the quickjs-emscripten-sync.
In addition to the already mentioned things, there are also general, conceptual reasons.
The sync library tries to remove the barrier between host and guest, which results in some kind mix up.
As an example - let's imagine there is a class A in the sandbox like this:
class A {
  methodB() {
     return 'hello'
  }
}

And an instance of this class is given to the host, quickjs-emscripten-sync creates an object on the host, which looks something like this:
{
  methodB() {
     return sandboxContext.callFunction(classInstanceSandboxFunction)
  }
}

There is no clean (de-)serialization. And as soon as the sandbox instance is gone, these things can't be used anymore.
The intention is, to have a clean serialization between host and sandbox - similar to JSON encode/decode, which creates fresh instances.
Btw.: Thanks to the awesome work done in quickjs-emscripten(-sync), it isn't too much work. I've already done it - only some cleanup, tests and so on are missing.


Fix logger in ClassLoaderResourceLoader

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10995 (8b7a6d0) into 3.1 (e7f0ee3) will decrease coverage by 4.64%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##                3.1   #10995      +/-   ##
============================================
- Coverage     69.28%   64.64%   -4.65%
+ Complexity      106       14      -92
============================================
  Files          1463     1418      -45
  Lines         75990    58858   -17132
  Branches      13292     8637    -4655
============================================
- Hits          52651    38046   -14605
+ Misses        18713    16778    -1935
+ Partials       4626     4034     -592

Impacted Files
Coverage Δ

.../dubbo/common/utils/ClassLoaderResourceLoader.java
74.50% <50.00%> (+0.50%)
:arrow_up:

...luster/router/script/ScriptStateRouterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...he/dubbo/test/common/impl/GreetingServiceImpl.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...zookeeper/curator/CuratorZookeeperTransporter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...nfigure/DubboRelaxedBinding2AutoConfiguration.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../apache/dubbo/test/spring/SpringXmlConfigTest.java
0.00% <0.00%> (-96.16%)
:arrow_down:

...egistrycenter/context/ZookeeperWindowsContext.java
0.00% <0.00%> (-81.82%)
:arrow_down:

...istrycenter/processor/FindPidWindowsProcessor.java
5.40% <0.00%> (-81.09%)
:arrow_down:

...pc/cluster/router/file/FileStateRouterFactory.java
0.00% <0.00%> (-80.96%)
:arrow_down:

...ycenter/processor/KillProcessWindowsProcessor.java
10.00% <0.00%> (-80.00%)
:arrow_down:

... and 420 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


cinnamon.nemo: 5.6.5 -> 5.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/nemo/versions.
meta.description for cinnamon.nemo is: File browser for Cinnamon
meta.homepage for cinnamon.nemo is: https://github.com/linuxmint/nemo
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.8.1 with grep in /nix/store/zf09nhs8fzgk2lid41wf939cpjgpz3z1-nemo-5.8.1
found 5.8.1 in filename of file in /nix/store/zf09nhs8fzgk2lid41wf939cpjgpz3z1-nemo-5.8.1

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
cinnamon.cinnamon-common
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.nemo
cinnamon.nemo-fileroller
cinnamon.nemo-python
cinnamon.nemo-with-extensions

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zf09nhs8fzgk2lid41wf939cpjgpz3z1-nemo-5.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cinnamon.nemo https://github.com/r-ryantm/nixpkgs/archive/048cc6e0c4fb6627f1d0ba27dea420fe33f768d2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zf09nhs8fzgk2lid41wf939cpjgpz3z1-nemo-5.8.1
ls -la /nix/store/zf09nhs8fzgk2lid41wf939cpjgpz3z1-nemo-5.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

cinnamon.cinnamon-common
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.nemo
cinnamon.nemo-fileroller
cinnamon.nemo-python
cinnamon.nemo-with-extensions

Maintainer pings
cc @bobby285271 @mkg20001 for testing.

I haven't read what might block this but we need 5.8.2 to fix this issue


Update UI and add level difference

Changes
UI

Add a remain enemy label
Change background image when level cleared

Level Adjustment

Num of enemies will grow randomly
Speed of enemies will increase as the game goes
Chance of enemies shooting will increase as teh game goes
Player will regenerate part of missing health when level cleared
Player has shooting ability power up when reach certain level (3 stage in total)

Fix

The problem of score does not reset

Refactor

Reformat codes

could this be joined into one line to make the code a bit cleaner?

same here, these could all be on one line which would make them easier to read

could this formatting be cleaned up a bit

could this all be moved to one line, and could we write 'enemies' rather than 'enemy'? There's usually more than one ship

The line separations are caused by IDE auto-formating, will change that

Changes
Fix

The problem of score does not reset

Refactor

Reformat codes


checkSSLCert: 2.34.0 -> 2.35.0

Description of changes
https://github.com/matteocorti/check_ssl_cert/releases/tag/v2.35.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 182318 run on x86_64-linux 1

1 package built:

checkSSLCert


Bug in get_balance_allowance function

Overview
get_balance_allowance Function has input variable params that can be null, but function treats this variable as not nullable.
Description
In get_balance_allowance function if params.signature_type == -1: will throw an exception if params is null, therefore it should be if params and params.signature_type == -1: and also test should be covering this space.
Notes

Action items

[ ] Tag issue (bug, enhancement, feature, etc.)
[ ] Initial discussion/assign team member
[ ] Move discussion to PR if necessary and when ready

Are there any updates on this?


No Markup when using MudHidden in UnitTests

Describe the bug
When using MudHidden, the markup in the unit tests is always empty. Even if the property is set to "IsHidden=false", no markup is generated during rendering.
Expected behavior
Markup should be rendered.
TryMudBlazor
Cannot provide any code, because its internal code from my company.
MudHidden an "IsHidden=false":

Did you use MudHidden for show/hide other components?

Yes I did. Now I use instead the display-classes for showing and hiding.


Check for unmaintained packages

Added a check for dependencies which were not modified in the last two years or more.
This PR should cover most cases of deprecated packages, if I should implement additional checks for some edge cases, let me know.
Sorry about the prettier formatting changes, I hope that is fine.
Closes #338.

I filed #351 so that we have a chance to get a green build...

@LinusU any chance that you find some time to get this reviewed and merged?

I too would be interested in this.

Any updates on this?

Will this PR tell us if npm-check is maintained or not......

that would be cool to have.

Sorry for never getting to this! Unfortunately I have a ton of notifications all the time, and I don't have that much time to put on this specific repository...
Personally, I'm not sure that this is a great approach. At least, I think that we should do some research before settling on the two year limit (which actually is just 1 year, as the code is now, if the package was published in late December).
e.g. express had three years between the last two stable releases, yet it is definitely maintained and is one of the most used package in the entire ecosystem. It just doesn't have that many releases because it is incredibly stable.
Since stability is a good thing, I feel like we might punish stable packages unjustly here?

@LinusU yeah, I'm with you.
I've made this simple script to fetch all time.modified field from every dependency and list them sorted, so I can use it to see if I have any dep that's too old for me: https://gist.github.com/micalevisk/5276391d4e7b5c4b0c12fc98d5610245

How about exposing a new option instead of changing something core.
This will not break anything, and is "just" to stable packages.
End users will be the ones to specify the time to distinguish maintained packages, or unmaintained ones.


Pull request workflow

Problem
At the moment we are merging (sometimes huge) PRs into master using squash and merge. This means the PR will show as a single commit in master, named after the PR.
This makes it difficult to follow the history, use git blame etc, when PRs have many commits.
Solution

we could use smaller PRs, but this will not always work
instead I suggest we always merge PRs into master using rebase, not squash.
However, before merging the PR, we use interactive rebase (git rebase -i master) on the feature branch to clean up the PR commit history, squash individual commits etc.
this will result in a more transparent commit history in the master branch.

Also remember [git add -p](https://git-scm.com/docs/git-add#Documentation/git-add.txt--p) is your friend. More usable with editor support.

Workflow:

commit away on feature-branch
in the meantime new commits occur on the master branch.
when you are done with your feature you want to

clean up commit history
sync in new commits from master to ease merge into master or make new tests pass

do this via git rebase -i master while on feature-branch

this will let you pick (p) or squash s your commits, and then put them on top of the commits from master

you are re-writing the commit history
therefore, your remote feature-branch will have diverged
if you are sure that this is only due to your rebase (i.e., before the rebase everything was up-to-date) you can force push to the remote branch: git push origin feature-branch --force-with-lease

more details, e.g., here:
https://www.atlassian.com/git/tutorials/merging-vs-rebasing

I didn't know the difference betwewen --force and --force-with-lease. The latter is gentler in the face of other commits to the branch - see https://stackoverflow.com/a/52823955.

Why sometimes branches should be merged, not rebased. I think it's worth discussing

See #118, information here should be integrated there.

This is now being consistently done by everybody (and referenced for future dev-facing documentation), so closing.


Update GitHub documentation links

On https://developer.github.com/v4 the following message is displayed:

We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Learn more on the GitHub blog. For the most accurate and up-to-date content on this page, visit docs.github.com/v4/

This pull request updates the documentation link to the one mentioned in their message.

@stephan281094 Thanks a lot 👍


pp3: add default bitstream

This PR adds default bitstream for PP3 which was generated in symbiflow-arch-defs with create_default_fasm.py script that was updated to support PP3 in: https://github.com/QuickLogic-Corp/symbiflow-arch-defs/pull/631
Signed-off-by: Paweł Czarnecki<EMAIL_ADDRESS>

Hi @lnsharma is this one ready to be merged?


Current namespace is ambigious

The current namespace that is available to the user provides the following methods/attributes:
'Acidity',
'Niche',
'NutrientLevel',
'Vegetation',
'acidity',
'codetables',
'niche',
'nutrient_level',
'spatial_context',
'vegetation',
'version'

Hence, acidity/Acidity, niche/Niche,... This creates confusion to the user

@stijnvanhoey Any suggestions how to solve this?

An option for the Acidity and NutrientLevel is to not include them in the __init__ , as these are then still loadable, but not visual (at least, that is what I assume).
With respect to the niche, I just would like to have only the class Niche available to the user and not the module niche. I do think it can be achieved by adapting the __init__ file, but we will have to experiment a bit to get the proper behaviour (start with an empty __init__ and see how it behaves).


Rolling index rebuild

It would be useful to rebuild indices in a rolling manner, only dropping the index right before it's rebuilt. This is an issue specifically using realtime indices, where some indices take a long time to rebuild, forcing later indices to wait empty until their turn to rebuild. Though there would be a period of time where the index would return an empty or partial list of results as the index is built, it could continue serving stale results while other indices are being built.

Hi Nicholas - thanks for this suggestion. It's definitely a fair request, but I'm not sure it's possible.
A rebuild is (or at least, should) mostly used when at least one index's structure is changed. Given this is all in a single file, it's not really possible to keep legacy data files around - all of the configuration is updated at once, rather than on a per-index basis. If index A was kept the same, and index B was changed, then it's not going to be possible for Sphinx to run reliably with old B data while processing A's records, because the configuration will have the new B schema.
I'll keep thinking this through in my head, but right now I don't see a clear path forward. Also: how often are you rebuilding? If it's more than just when the structure of indices are changing, I'm curious as to why that's the case.

Hi Pat, thanks for the quick reply. I wasn't using the proper jargon when I posted. I want to initiate a rebuild that updates the config once, then clears one index at a time as it re-indexes it. That way we can continue to serve up results from the untouched indices while we repopulate the current index, avoiding empty result sets for the majority of queries.
The use case is we add a new RT index, deploy, our config is updated on deploy, but that has the effect of breaking document_id calculations and also requires an index before we can write documents to the new index. Since a reindex of all indices will cause duplicates to appear because the document_id is now different for each record due to the addition of the new index (https://github.com/pat/thinking-sphinx/blob/f78e9ab1f5f27845b816fecf83b8e62cc76b9ced/lib/thinking_sphinx/core/index.rb#L37), we are forced to rebuild to clear out the documents in each index. Reducing the amount of time the indices are empty is a priority.
As a sidenote, I have implemented two monkeypatches to improve this situation, perhaps you can weigh in on them.

Implemented index priority to ensure we reindex the most important (visitor-facing) indices first when rebuilding.
Overloaded the transcriber and delete callbacks to use delete old records matching the current index and where the record's id matches the Sphinx document's sphinx_internal_id, eliminating the need to clear out old documents after creating/deleting a sphinx index.

I want to initiate a rebuild that updates the config once, then clears one index at a time as it re-indexes it.

This isn't going to work, I'm afraid, because as you've noted, the offsets change, and so the existing index files will have old offsets, but any updates that may happen will expect new offsets, so you're going to find the wrong records get updated (via callbacks) in Sphinx.
I'm definitely interested in seeing the code for your monkey-patches, and I'm pondering how reindexing could become a multi-process thing, so all indices are processed in parallel (for a specified number of threads), which could hopefully speed things up.
As a manual workaround in the meantime, per-index processing (ts:index) could be a way to update a bunch of indices at the same time:
bundle exec rake ts:rebuild
# And then, once that starts on adding data to indices:
bundle exec rake ts:index INDEX_FILTER=user_core
bundle exec rake ts:index INDEX_FILTER=purchase_core
# etc

Automatic removal of stale Sphinx documents during Realtime Indexing
https://gist.github.com/njakobsen/2135706c35139d484a56d660b089cc5d
The index priority selection is not as interesting, I simply sort the list of indices as desired at the end of ThinkingSphinx::Index#define.

I was going to suggest you submit this as a PR - but frustratingly, Sphinx 2.1.x doesn't support anything but id in the WHERE clause (2.2.x onwards are more flexible).
Given Sphinx 2.2.x has been around for over five years, I'm thinking I should probably drop 2.1 support soon. I'll keep this patch in mind for then.

Sounds good.
FWIW while modifying Transcriber I ended up deleting by ActiveRecord id before replacing because the replace occurs deeper down in the Riddle gem (https://github.com/pat/riddle/blob/develop/lib/riddle/query/insert.rb) and I didn't wan't to change the behaviour too broadly while I was experimenting. Ideally, the replace would simply be based on ActiveRecord id instead, negating the need for a sphinx document id replace, but this would require better knowledge of the gems involved, their desired compatibility with other ORMs, and of Sphinx itself. This is why I didn't make a PR and instead opted for the gist to at least showcase the idea.

I've made a few attempts at parallel processing over the past couple of months, but have found a reasonably simple solution just by refactoring the current code and allowing custom processors. This leaves the door open to others building their own implementations. All wrapped up in f0a7c125407208df51ef689d736ff03111489a92.
And as noted in that commit, I've put together a quick example using the parallel gem:
https://gist.github.com/pat/53dbe982a2b311f5f7294809109419d2
In a test app locally, I'm finding this shaves almost 50% off indexing times, but I'm dealing with very simple indices (and only three of them). Certainly, I'd be keen to know whether such an approach is helpful in your app!

This worked well though I ran into an issue that could potentially be addressed in a similar way. As I reach the end of the list unless the indexing time is well balanced, we end up with several CPUs sitting idle while any long indices are completed. This led me to try parallelizing within the Populator. That worked okay, though I noticed that the memory footprint seemed to grow depending on the number of records in the table being indexed (not scientifically tested), so I'll need to investigate why I wasn't able to keep it constant even though I was using find_in_batches  to load records 100 at a time so we could keep each process fed.
The performance difference for my project on a Macbook pro with 4 cores + hyperthreading was:

No parallelization: Usually around 30 to 40 minutes
Parallelizing per index: 11 minutes
Parallelizing within an index: 8 minutes

Ah, nice to know the per-index option at least made things a decent bit faster on your machine. Fair point about the balancing of indices by size though, that's a bit tricky.
Can you share your changes to the Populator code? I'm curious to see your approach to shift the parallelisation into there.

Be warned it's super janky proof of concept. I just threw this into my config/initializers to test it. The true part was while I was poking around to see if this was the cause of memory seeming to balloon when I indexed a large table. One downside to this is if for some reason memory is affected depending on the table size, all your processes balloon at the same time (unlike your example with per-index parallelization), which is why I started looking into it.
ThinkingSphinx::RealTime::Populator.class_eval do
  def populate(&block)
    instrument 'start_populating'

    scope.find_in_batches(batch_size: 100)

    Parallel.each(scope.find_in_batches(batch_size: 100)) do |instances|
      transcriber.copy *instances
      instrument 'populated', :instances => instances
      true # Don't emit any large object because results are accumulated
    end
    ActiveRecord::Base.connection.reconnect!

    instrument 'finish_populating'
  end
end

I've just added a commit that allows similar customisation in a slightly more native approach, using your code:
class ParallelPopulator < ThinkingSphinx::RealTime::Populator
  def populate
    instrument 'start_populating'

    Parallel.each(scope.find_in_batches(batch_size: batch_size)) do |instances|
      transcriber.copy *instances

      instrument 'populated', :instances => instances

      true # Don't emit any large object because results are accumulated
    end
    ActiveRecord::Base.connection.reconnect!

    instrument 'finish_populating'
  end
end

ThinkingSphinx::RealTime.populator = ParallelPopulator

That said, when I gave it a spin, I didn't find any significant speed improvements over the standard non-parallel approach, let alone the Processor parallelisation. So maybe it's far more dependent on the index definitions and the Rails app?

I think it's going to be very dependent on how the indexes in one's app are balanced. We have some very large and very small indexes, so I ended up with the imbalance. However, combined with the reindexing priority monkey-patch I described in https://github.com/pat/thinking-sphinx/issues/1134#issuecomment-493773048, I ended up prioritizing the large index so it gets a head start while other shorter indices are being processed in parallel. Therefore I probably won't pursue within-index parallelization since the gain is minor compared to the simpler approach, and can be achieved with a manual tweaking of indexing order. I'm also a little worried about the whole ActiveRecord::Base.connection.reconnect! that the Parallel gem suggested, since it didn't really explain why we lose connection, and how exactly this line solved it, see https://github.com/grosser/parallel#activerecord.
FWIW here is a simplification of how I'm implementing index prioritization
module IndexExtensions
  def define(*, &block)
    super
    sort_indices
  end

  private

  def sort_indices
    ThinkingSphinx::Configuration.instance.indices.sort_by! do |index|
      index.options[:reindex_priority]
    end
  end
end

ThinkingSphinx::Index.singleton_class.prepend(IndexExtensions)

ThinkingSphinx::Index.define :page, reindex_priority: 5 do
   # your index here
end

Yeah, avoiding the reconnecting is not a bad idea. For what it's worth, you could remove that monkey patch and instead shift the sorting into the custom processor instead? e.g.
class ParallelProcessor < ThinkingSphinx::RealTime::Processor
  def call(&block)
    Parallel.map(indices) do |index|
      puts "Populating index #{index.name}"
      ThinkingSphinx::RealTime::Populator.populate index
      puts "Populated index #{index.name}"

      block.call
    end
  end

  private

  def indices
    super.sort_by { |index| index.options[:reindex_priority] }
  end
end

ThinkingSphinx::RealTime.processor = ParallelProcessor

I guess I could sort on-the-fly each time since there's no interface for extending ThinkingSphinx::Index. However, indices is a private method, so overriding it in my own subclass would still feel like a monkey patch. Would you be interested in a PR to make custom indexing order a standard feature? Or do you not see it as fundamental to the gem itself? Even something like adding a <=> method to ThinkingSphinx::Index, defaulting to the current behaviour of sorting by name, which could be overridden as desired.

I'm a little wary of adding the new feature, just because this hasn't been requested before in TS' long history.
Fair point about the above solution… here's a simpler approach though that avoids the reliance on a private method and the superclass:
ThinkingSphinx::RealTime.processor = Proc.new do |indices, &block|
  Parallel.map(indices) do |index|
    puts "Populating index #{index.name}"
    ThinkingSphinx::RealTime.populator.populate index
    puts "Populated index #{index.name}"

    block.call
  end
end

Ah, but I forgot to add the sorting in there. Still, easy enough to add :)
The processor needs to be something that responds to call and accepts two arguments: an array of indices, and a block that should be invoked (without any arguments) after each index is processed. The default is a class, but a proc does the job just as neatly.

Yeah, makes sense, thanks for all your help!

No worries, great to get some solutions sorted that help you :)

These changes are now available in the freshly-released v4.4.0 :)

Hi Nicholas - just wanted to let you know that the newly released v5.0.0 release of Thinking Sphinx includes two changes you'd flagged in this discussion: real-time data is deleted before being inserted again (thus old data on different offset values is avoided), and the SphinxQL deletion calls are by ActiveRecord id rather than Sphinx's primary keys (as Sphinx 2.2.11 or newer is now required).
There's also a significant change with needing to specify callbacks - though this is more of a big deal for those not using real-time indices: https://github.com/pat/thinking-sphinx/releases/tag/v5.0.0

I saw that! Thanks for the update @pat. I'll update our code as soon as I'm able and let you know how it goes.


Alert profiles assignments have container providers under cloud/infrastructure providers

The title probably needs to change. In addition, the assign to: has only "selected  infrastructure providers"

@miq-bot add_label providers/containers, bug, ui

@miq-bot assign @moolitayer

Closing this issue as stale; if you're still having this problem with the newest release, please open a new issue in the UI Classic repository. If you like, you can also move this issue as-is to the UI repository by reopening it and commenting with @miq-bot move_issue manageiq/manageiq-ui-classic
Thanks!


Fix Copy, plus reduce the used features

Implement Clone where Copy is needed
Remove all uses of unsafe_destructor, these are no longer needed
Remove the BorrowState, this way we only need std_misc when testing

Looks good! Thanks!


"All" should not be selectable as a custom filter option

Describe the bug
Remove "All" from options when creating new a filter

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

GitHub release
1.0.0

Your semantic-release bot :package::rocket:


split in starter and application

when running a spring-zeebe application, I would like to integrate this via starter into my app instead of running an additional app. (see camunda-bpm-spring-boot-web starter).
This requires:

webjar lib for resources
sb starter lib for backend

application uses both libs

@jangalinski do you want to work on this?

I am quite busy right now, but I'll have a look, should not be too difficult.

Keep in mind that the simple monitor should be a simple monitor - I personally would't add it to any production app anyway ;-)


Fix outputs buttons behavior

If the current output cannot handle the results the package selects an output that can handle them. But the outputs buttons are not updated and the selected button does not match to the selected output.
This updates the outputs buttons if the current output is not equal to the selected output.
Also adds the 'disabled' attribute to the unsupported outputs buttons to prevent their selection.

@LaurensRietveld could you please look at this? Is there anything I need to add or change?

sorry for the delay, thanks for the PR :+1:


Unable to generate  from CLI

Hi Guys!,
Thank you for your efforts to bring this much needed tool!..
I'm trying to use the CLI to generate an OFX from my bank CSV, however so far I've not been successful in generating the LEDGERBAL tag that my Accounting software seems to require...
I've inspected the code and I understand that the tag (LEDGERBAL) is inserted by the account_end method (ofx.py:276), and that this method is called from the footer and the gen_body methods... none of those calls seems to include the parameter "balance" that is required (in account_end) to insert the LEDGERBAL tag... is that the intended behavior?  if that is the case, it is impossible to generate the LEDGERBAL tag from the CLI, am I right?

See #56


add scripts to manage go-tool fork

instead of https://github.com/kamilsk/go-tools/blob/extended/Taskfile

won't do, cause it's better when the script is a part of project


Function "setErrorMap" Not Overriding Default Mapping

Issue Title: setErrorMap Function Not Overriding Default Mapping
Description
Affected Library: ZOD
Current Behavior:
The setErrorMap function in the ZOD library, which is intended to allow users to set their own error mappings for different languages, is not functioning as expected. According to the documentation, this function should override the default error mapping with the custom mapping provided by the user.
Expected Behavior:
When using the setErrorMap function, it is expected that the custom error mapping provided by the user should completely replace the default error mapping. However, in its current state, the library appears to be retaining elements of the default mapping, resulting in unexpected behavior when trying to change the language of error messages.
Steps to Reproduce:

Initialize the ZOD library.
Use the setErrorMap function to set a custom error mapping for a specific language.
Trigger a validation error in that language.

Current Outcome:
Despite setting a custom error mapping using setErrorMap, the error messages still contain elements from the default mapping. This makes it difficult to fully customize the error messages for different languages.
Expected Outcome:
Upon using setErrorMap, the custom error mapping should take precedence over the default mapping, resulting in error messages that are fully customized according to the user's specifications.
Additional Information

Version of ZOD Library: "^3.21.4"
Browser/Environment: node v16.13.0
Code Example:    const { z } = require("zod");
    z.setErrorMap((issue, _ctx) => {
      let message = "Test";
      // all errors should be "Test"
      return { message }
    });

I temporarily solved this in my project by changing the order of the errorsMaps in the "addIssueToContext" function in "./helpers/parseUtil.ts". It can be seen in the function of the same file "makeIssue" because it does not work as expected, a reverse is being used, I don't know if it is intentional or because it is due.

This does look like a bug. Can you share some code that is returning the default error messages?

Delete the node_modules folder and run npm install and it's resolved, I can't replicate it

This is a show stopping bug for anybody that is using zod for form validation and has to support internationalization.

The problem is on this functions, addIssueToContext create a errorMaps array with all alternatives to get the errors from different parts, following a priority described on the comments, but...
export function addIssueToContext(
  ctx: ParseContext,
  issueData: IssueData
): void {
  const issue = makeIssue({
    issueData: issueData,
    data: ctx.data,
    path: ctx.path,
    errorMaps: [
      ctx.common.contextualErrorMap, // contextual error map is first priority
      ctx.schemaErrorMap, // then schema-bound map if available
      getErrorMap(), // then global override map
      defaultErrorMap, // then global default map
    ].filter((x) => !!x) as ZodErrorMap[],
  });
  ctx.common.issues.push(issue);
}

...later on the makeIssue function on this block of code this array that supposed to be ordered from top priority to lowest is inverted, I don't know the logic around that.
let errorMessage = "";
  const maps = errorMaps
    .filter((m) => !!m)
    .slice()
    .reverse() as ZodErrorMap[];
  for (const map of maps) {
    errorMessage = map(fullIssue, { data, defaultError: errorMessage }).message;
  }

Since it is using a for and not break in it after found a message, eventually the result from the getErrorMap() is override by the message already defined on the schema.
Solution: if getErrorMap() finds a custom function don't event do the for loop. For me this is top priority. In this way you can get the error message defined on the schema within the function and look for the translation wherever you want and return the localized message.

I've opened PR #2950 that adds optional support for overriding the default mapping and be able to use the defined schema messages as translation keys on the setErrorMap


OData $skiptoken: add inline docs

This should help explain how odata $skiptokens are defined and used in this codebase.

Looks good to me! We also mention $skiptoken a little in the API docs.

:+1: the docs currently read:

Opaque cursor from @odata.nextLink used for paging.

I found this a bit opaque :grin:


How to use

I would like to see how this works in practice. How would I go about encrypting and then decrypting a file?

I guess I will just program what I want it to do.


Feature:  Expose the build process time into stage wise.

🔖 Feature description
We want to analyse time taken by every build stage during the app build.
🎤 Pitch
Want to see the build stage time for per build , right now multiple stage happen after trigger a build.

CI node provisioning
download build cache(if blob storage configured )
git cloning
pre ci steps
build stage
post build steps
image scan
upload build cache (if blob storage configured )

✌ Solution
NA
🔄 Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#3180

Need : Both stage wise time as well as total build time.
Good to have : Average build time. (based upon past builds average)
cc : @prakarsh-dt @vikramdevtron

This is already completed


Loss is always 0 for multiclass problem

I tried using FocalLoss(gamma=2.0) as a drop-in replacement for nn.CrossEntropyLoss() in a couple different multiclass problems, and in both cases I got losses of 0.  In one case there are 3 classes, in another there were 20.  Is there a recommended way to use it in that context where I wouldn't expect this to happen?
The context in question is either a sentiment analysis tool or a parser, both part of Stanford's Stanza library:
https://github.com/stanfordnlp/stanza/tree/con_focal
(con in this case being short for constituency)
If you're interested in digging into this particular problem, I can provide a few datafiles which are public domain

to use FocalLoss as nn.CrossEntropyLoss() gamma should equal to 0

If you can give more details to dig deeper that would be better!

I may have not expressed the problem well.  If I run CrossEntropyLoss as the loss function, and I print out the first few losses, I get
1.1091877222061157
1.0973833799362183
1.0567669868469238
1.1430968046188354
1.0842665433883667
1.1735007762908936
1.1027023792266846

So what I wanted was to use the focal loss algorithm instead of cross entropy loss.  I would expect that it is sufficient to do this
        loss_function = FocalLoss(gamma=args.loss_focal_gamma)

instead of
        loss_function = nn.CrossEntropyLoss()

However, I then get nan for the first few losses:
nan
nan
nan
nan
nan

This happens regardless of the gamma I use.
Like I mentioned, I can easily send a dataset which will demonstrate the error, if that's helpful.

Thanks for the elaboration,
are you sure that the predictions in one of the following shapes?
(B,)  # for binary classification
(B, C)  # for multi-class classificatio
(B, M, C)  # for sequene prediction
```

And make sure that all the values are between 0-1

It would be better if you could dump the values you are passing the focal loss in pickle file to try it out

@AngledLuffa Could you please check this pull request if it throughs an error after passing your input?
https://github.com/mathiaszinnen/focal_loss_torch/pull/12

Thanks for looking into this.  I suspect that's exactly what is happening
here.  CrossEntropyLoss expects unnormalized input, so I hadn't passed in
softmax output.  I'll have time to check later this afternoon
On Sun, Oct 16, 2022, 10:57 AM Mahmoud Salhab @.***>
wrote:

@AngledLuffa https://github.com/AngledLuffa Could you please check this
pull request if it throughs an error after passing your input?
#12 https://github.com/mathiaszinnen/focal_loss_torch/pull/12
—
Reply to this email directly, view it on GitHub
https://github.com/mathiaszinnen/focal_loss_torch/issues/10#issuecomment-1280020359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2AYWIQUV6ZNXFDYGFBDRTWDQ6WZANCNFSM6AAAAAAREXW5W4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, that was exactly it.  Thanks for the help.


fix: add trailing slash to apps storage url, #356

This PR

adds a trailing slash to storage hub urls in the user's profile for apps with permission publish_data
fixes #356

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: friedger:x: hstoveYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks Friedger! I had to make a new PR to fix the conflicts here: #379


Support Mocha 4

Mocha 4 was released 12 hours ago, and is incompatible with this plugin.
https://www.npmjs.com/package/mocha
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Just published version 4.0.0. Give it a go.

Working, thank you!
One note for people migrating to Mocha 4:
Mocha 4 "will no longer automatically kill itself via process.exit() when it thinks it should be done running." (source)  Here's a "fix":
stream.pipe(mocha({
  exit: true,
}))


Custom job infrastructure

Currently the website has backend support for jobs, datasets, and scripts, however none of this is used or displayed in the UI.
The proposal is to simplify the original plan to use serialised filter queries rather than datasets, and provide only an API. The UI will be built in baw-client.
For this to happen, and few things need to be checked and changed:

[ ] Remove dataset model
[ ] Check that Scripts does what is needed (e.g. command line template, settings template, identifier)
[ ] The job model needs to change to be able to store a filter query.
[ ] There needs to be some way to retrieve the resque jobs that relate to a custom job to determine progress and status. We don't want to store the resque job ids, so this will require some way to filter the resque jobs using the custom job id.
[ ] An API is needed for CR_D actions. Custom jobs can be created; their description, analysis settings, progress, and status can be queried; they can be re-run, and they can be deleted. To modify a custom job, it must be cloned, modified, then run as a new custom job.

Good points, I'll break these down into issues tomorrow.
Need to clarify some detail from @jwim1 's spec first

Closing in favour of milestone.
See #189, #190, #191, #192, #193,


Make sure RFE Message is only set to the response body payload.

Follow up from offline discussion on the right RFE semantics.

/check-enforcer override


iOS Chrome - Refresh page shifts scroll position

Reproduction
Open any Remix page on iOS Chrome (e.g., https://remix.run/docs/en/main/components/scroll-restoration)
Keep refreshing the page. What is this behavior?
https://github.com/user-attachments/assets/c7c2e0b9-d01f-48d2-9d58-f408cf984c63
This doesn't happen on iOS Safari.
System Info
iOS 18.1 Chrome 130.0.6723.37

Used Package Manager
npm
Expected Behavior
The page shouldn't scroll by itself.
Actual Behavior
Page scrolls down every time it refreshes.

This seems to be a Chrome bug as it also happens on a Next.js project. I'd need to do more testing.


Incompatible library version - rlibmemcached.bundle

Hey there!
I'm running 1.8 of your gem and am encountering a curious issue I haven't been able to debug. Here's the output:
/Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require': incompatible library version - /Users/aang/.rvm/gems/ruby-2.3.3/gems/memcached-1.8.0/lib/rlibmemcached.bundle (fatal)
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `block in require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/memcached-1.8.0/lib/memcached.rb:19:in `<top (required)>'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `block in require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/memcached-1.8.0/lib/memcached/rails.rb:1:in `<top (required)>'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:91:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:91:in `block (2 levels) in require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:86:in `each'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:86:in `block in require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:75:in `each'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler/runtime.rb:75:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.6/lib/bundler.rb:106:in `require'
	from /Users/aang/Code/railsproject/config/application.rb:6:in `<top (required)>'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `block in require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application.rb:82:in `preload'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application.rb:143:in `serve'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application.rb:131:in `block in run'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application.rb:125:in `loop'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application.rb:125:in `run'
	from /Users/aang/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/application/boot.rb:19:in `<top (required)>'
	from /Users/aang/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/aang/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from -e:1:in `<main>'

I've nuked my rvm/ruby, reinstalled gems, pristined them, reinstalled memcached, all to no avail. Have you encountered this before? Any idea why rlibmemcached would be the wrong version?


Resolving dependancies broken in multiple places (L5.5)

I found a few breaking bugs in the 1.2.2 release regarding resolving repositories and requests (at least when using Laravel 5.5). @ifox already fixed one I reported before (https://github.com/area17/twill/issues/399), but the same issue happens here as well:

MediaLibraryController 128
FeaturedController line 235
FileLibraryController line 139

Unfortunately this has now broken our Media Library in production as we didn't spot the bug before.

All those have been fixed on 1.2.x-dev and master.


I recorded my sample voice but when I try to authenticate my voice imprint it shows no user found but the user is present in my system. This username does not exist. Please try another user name, or enroll the user

I am having the same issue, did you find a solution?

Hi Michael,
Sharing my project folder with you. I can't remember what changes I did
since it has been a while but it started working for me with all the
changes. Run the python file using any external server if required like
xampp or anything else. let me know if it worked out for you.
drive link:
https://drive.google.com/drive/folders/1BDDdnY7SH0FWHzFu1DpIKZGBleqDkM4l?usp=sharing
Thanks & Regards,
Rahul Pudurkar
On Tue, 15 Mar 2022 at 03:50, MichaelDiFilippo @.***>
wrote:

I am having the same issue, did you find a solution?
—
Reply to this email directly, view it on GitHub
https://github.com/bedangSen/VoiceSens/issues/27#issuecomment-1067358947,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMYM3N3MHUY7B27KNEUENDU763RPANCNFSM4ZQXNTEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Track order for multi disc releases on filesystem provider mixes discs

Unfortunately for multi disc releases the default track order seems to be wrong.

This should be fixed with the 1.0.17 release, thanks for reporting!


color not working using IE

Using InternetExplorer 11 then the background color is not working.  Same table works fine using Chrome.

Thanks. This is a duplicate of the Background color issue, so I will close it. If I can resolve the coloring issue I will.
I am surprised QSD does not display the colors, as I thought it leveraged the Chrome engine and this should work like Chrome. But it seems to have the same problem as IE11.


Make downloads page as simple as possible

There are several things I've noticed with the current downloads page that can act as a deterrent to users getting Haskell up and running as quickly as possible:

The page is incredibly confusing from the get-go. It's not immediately obvious how to get Haskell from any of the ways mentioned.
There's way too much information that we expect a user to ingest before they can even start using Haskell. Most users who visit this page are looking for the easiest way to get up and running with Haskell. Why inundate them with information about sandboxing and global installations when they haven't even had a chance to write a hello world program in Haskell?
A description of each of the three methods of installation at the top of the page are mentioned again in each respective section. So why bother describing it at the top?
The only benefit provided by the "minimal installer" section is a link to the linux page. The other two links for osx and windows take you to the Haskell platform.

Rather than trying to squeeze as much information as possible into a single page, I've opted for a much simpler approach of showing the user where to get Haskell quickly. If the user wants to know more about the particular method they've chosen, then its all on the page that they just clicked into. Here's what it looks like (I took some inspiration from Scala's download page):

I've also moved the unrelated "Additional Libraries" section into its own page called "Packages".

Let me know what you think.

I've recently started looking at Haskell on Windows, and it appears to me that choco-based installs currently seem to provide a better and more uniform experience than the alternatives (and even better than the HP) for when you need to work on Haskell packages which depend on non-trivial things like Gtk+.

On Linux, my favorite (new) way to install the Haskell toolchain is ghcup which AFAIK supports most (all?) Linux distros as well as MacOS. I think it would be unfortunate if this wasn't at least mentioned since its been the smoothest experience I've had (even more so after the bootstrap script is available).
Also, one nice to have would be auto-detecting the operating system and showing the appropriate instructions (check out the rustup page for an example). It turns out this can be done relatively easily with JavaScript.

Also, consider renaming this to the "Install" page?


Too many modules with same name

Fulma should make dev easier ...
sometime it does not.

we need to make a pass on naming things ?

You got a lot of results but some are wrong I think because the suggestion isn't case sensitive. For example, in panel.fs we only have heading in lowercase not in capital case.
I am open to idea, but because the names are coming from Bulma implementation, not much we can do here. In general,

Oki, got no nice idea ... I close this


Run a set of hoprd nodes to be used as entry and exit nodes

The goal of this epic is to create the infrastructure needed to be able to create a set of hoprd nodes that will be used by rpc-h entry and exit nodes.
Tasks

[x] Install hoprd-operator in the stage environment
[ ] Create an ArgoCD application that will be composed of an entry node and a hoprd resource (hoprd-node)
[ ] Create an ArgoCD application that will be composed of an exit node and a hoprd resource (hoprd-node)
[ ] Deploy as many ArgoCD applications of entry and exit as needed on Stage environment
[ ] Check connectivity issues on hoprd nodes and send messages between them and across other nodes external to the cluster to check if they are working correctly
[ ] Install hoprd-operator in prod environment
[ ] Deploy as many ArgoCD applications of entry and exit as needed on Stage environment
[ ] Create additional hoprd-nodes to be used by  the development team in case they need to do debugging of their epics.
[ ] Document how a developer can use those hoprd-nodes
[ ] Create wallet for funding and registering nodes into NR @nionis
[ ] After funding the node, registering the node into NR, and once the node has a high quality connection, register node into RPCh using manager.

Definition of done

[ ] A set of entry and exit nodes are running in the stage environment providing the required stability to rpch
[ ] Developers can use existing hoprd-nodes or create their own for debugging purposes

Reminder that this https://github.com/Rpc-h/applications/issues/6 needs to be updated so new versions of exit-node can run


Invert IPv6 flag for consistency:

This aligns with CNI config

In response to a cherrypick label: new pull request created: #1173


[scala-package][spark] Resources running PS (role = server) should be explicit to Spark

another PR to facilitate the further work on integrating with Spark
The current implementation starts PS (role = server), release the cluster resources as if no one is using that and then start PS (role = worker)
To make the integration more seamless, we should make the resources used by PS (role = server) explicit to Spark
Question to @javelinjs  @terrytangyuan , why we choose to start PS in a child process instead of wrap it with a Spark task?

@CodingCat What do you mean by 'wrap it with a Spark task'?

@javelinjs for example in https://github.com/dmlc/xgboost/blob/master/jvm-packages/xgboost4j-spark/src/main/scala/ml/dmlc/xgboost4j/scala/spark/XGBoost.scala#L140, I called the scala API  directly instead of using java -cp xxxxxxx
in another word, why we choose to start PS  in a main function (https://github.com/apache/incubator-mxnet/pull/7571/files#diff-4c90554b29ca2b5c8dd829764adb7f01R35) instead of a normal function?

@CodingCat I think the main reason is to make ps scheduler & server run in a different process. Sharing native mxnet engine in one process seemed to cause problems.

@CodingCat
build failure:
[ERROR] /workspace/scala-package/spark/src/main/scala/ml/dmlc/mxnet/spark/ParameterServer.scala:156: error: value isAlive is not a member of Process
[INFO]     if (psProcess.get != null && psProcess.get().isAlive) {

@javelinjs , yeah, isAlive is a Java 8 API

I think the main reason is to make ps scheduler & server run in a different process. Sharing native mxnet engine in one process seemed to cause problems.

I do no think so...ps scheduler is in driver side, server is in executor side ...and additionally the current implementation requires users to set --executor-cores 1, so it should not be a problem, right?

@javelinjs  ping

thanks

@CodingCat @javelinjs
I see the same error as mentioned above when I try to build a scala docker image using this 0.12.0(which has this commit. Any suggestions as to what I can do about it?
Error -
/mxnet/scala-package/spark/src/main/scala/ml/dmlc/mxnet/spark/ParameterServer.scala:156: error: value isAlive is not a member of Process
[INFO]     if (psProcess.get != null && psProcess.get().isAlive) {

@mbaijal what's your steps to build docker image?

I found the issue, i was using older java version. Issue is fixed now.
Thanks!
On Oct 31, 2017 8:31 AM, "Nan Zhu"<EMAIL_ADDRESS>wrote:

@mbaijal https://github.com/mbaijal what's your steps to build docker
image?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/pull/7571#issuecomment-340799972,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AderEN36upi3USOgKLfFjaGU8qFgi0xEks5sxz06gaJpZM4O_dGH
.


Derive SBOM package name/version info from OmniBOR metadata

This PR mostly adds the new feature to derive SBOM package name/version info from OmniBOR metadata collected. Three sources of metadata are considered in this pull request:

RPM/DEB package info collected directly from the RPM/Debian package file itself.
extracted package name/version info from the collected file_path attribute during software build. For example, extract "sqlite3/3_3.31.1" /build/_tmp-lnt/work/aarch64-xr-linux/sqlite3/3_3.31.1-r0/sqlite-autoconf-3310100/sqlite3.c file path, or extract "ciscossl/1.1.1s.7.3.243" from ciscossl-1.1.1s.7.3.243/include/openssl/cryptoerr.h path.
source indexing database. This is the pre-built source indexing database, like Yocto/Ubuntu source DB, created via the bomsh_index_yocto.py/bomsh_index_debrepo.py script.

In addition to the above new feature, the followings are included in this PR:

Added new command line option "--derive_sbom" to let user specify the action of deriving SBOM info for the OmniBOR search results.
Added new command line option "--find_parents" to let user specify the action of finding parent GitOIDs for a list of GitOIDs.
Added new command line option "--check_blobs_in_db" to let user specify the action of comparing GitOIDs in two databases.
Added new command line option "--enrich_metadata_with_pkgs" to let user specify the action of enriching metadata database with pkg_info.
Added new command line option "--leaf_nodes_only" to let user specify to consider leaf nodes only for relevant actions.
miscellaneous fixes, including not generating raw records for autoconf configure scripts of conftest, etc.


feat: Open Webui Pipelines service and integration with Open WebUI frontend

Initial support for Open WebUI Pipelines and integration with Open WebUI frontend.
Following wiki:
Added service files:

compose.pipelines.yml — Docker Compose Pipelines service definitions.
compose.x.webui.pipelines.yml — Docker Compose cross-service file for integration with Open WebUI Frontend.

Added configuration files:

open-webui/configs/config.pipelines.json — WebUI Frontend config for connecting to Pipelines API.

Added environment variables override file:

pipelines/override.env

Miscellaneous:

Service environment variables added to profiles/default.env
Service listed in README.md
Refactored Services/Satellites section in README.md for better readability on small screens (please consider my changes, if not let me know, I'll revert it to original formatting)
Service directory added to .gitignore

Please let me know if additions or changes needed.

Added the docs here:
https://github.com/av/harbor/wiki/2.3.25-Satellite:-Open-WebUI-Pipelines
Thanks again!

It's probably my mistake for adding section for pipelines default variables not at the end of the profiles/default.env, but after 4604e6a there is a collision in port mapping between HARBOR_PIPELINES_HOST_PORT and HARBOR_CHATNIO_HOST_PORT.

Thanks for pointing this out! Resolved in latest main by shifting chatnio main port to  34219 (lazy but allows to only update a single wiki entry)


add refreeze action

@github-actions refreeze

Whoops! meant to open this against my fork for messing around. See #1012 and #753 for existing efforts on this


VS Mobile Center Test: grouping Prepare and Run options

Summary
This change modifies the Visual Studio Mobile Center Test tasks. It groups command options into two categories: prepare & run, which correspond to two CLI commands that are executed when submitting tests. It also allows users to skip either of these steps.

Motivation
By creating explicit Prepare and Run groups, we make the VSTS task look more familiar to users who start with the CLI.
By allowing users to skip one of the steps, we let them separate test preparation from test upload. It may be required in a scenario when the QA team wants to manually schedule an extended test run for existing build.
Compatibility with the Xamarin Test Cloud tasks
The new changes make the task look different than the existing Xamarin Test Cloud task. But this is necessary - the Mobile Center is a new product, with a brand-new CLI that is not compatible with the old one.
Implementation details
Changes inside task.json are relatively simple (rearranging / adding groupName).
Changes inside vsmobilecentertest.ts include:

moving code that creates prepareRunner, loginRunners and testRunner to separate functions.
using enablePrepare and enableRun options to decide which steps should be executed
using login command only if run step is enabled (prepare command does not need authenticated users). As a side effect, it requires changes in tests that expect that login is always executed as the first command.

Hi @kmiecikt, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

kmiecikt is FTE.


Needed textures for many mods

RUNES mod :
(All spell textures must be books open, with a distinct glyph/symbol on one or more page)

[x] runes_earthquake_major.png https://github.com/MinetestForFun/server-minetestforfun/commit/ef6f0d31278acaa4fe522a7f2cf8f9b655fcdf52
[x] runes_earthquake_medium.png https://github.com/MinetestForFun/server-minetestforfun/commit/ef6f0d31278acaa4fe522a7f2cf8f9b655fcdf52
[x] runes_earthquake_minor.png https://github.com/MinetestForFun/server-minetestforfun/commit/ef6f0d31278acaa4fe522a7f2cf8f9b655fcdf52
[x] runes_silver_cross_amulet.png (cotton + silver cross) https://github.com/Ombridride/minetest-minetestforfun-server/commit/63b9abe34dbee4332c77ce2f6125459e1696ca8a
[x] runes_minotaur_eye_amulet.png (leather + minotaur eye) https://github.com/Ombridride/minetest-minetestforfun-server/commit/63b9abe34dbee4332c77ce2f6125459e1696ca8a
[x] runes_grim_reaper_amulet.png (chain + skull) https://github.com/Ombridride/minetest-minetestforfun-server/commit/63b9abe34dbee4332c77ce2f6125459e1696ca8a
[x] runes_black_magic_block.png (skull/death/black block) https://github.com/MinetestForFun/server-minetestforfun/commit/a651f88919bafaa6abe746c077ed9b06c49c2d47

MOBS mod :

[x] Dungeon Master Diamond (light red colored diamond https://github.com/Ombridride/minetest-minetestforfun-server/blob/master/mods/mobs/dungeonmaster.lua#L112)
[x] Zombie Tibia (just a big bone https://github.com/Ombridride/minetest-minetestforfun-server/blob/master/mods/mobs/zombie.lua#L42)
[x] Minotaur Fur (https://github.com/Ombridride/minetest-minetestforfun-server/blob/master/mods/mobs/minotaur.lua#L79)
[x] Lot of Minotaur Fur (https://github.com/Ombridride/minetest-minetestforfun-server/blob/master/mods/mobs/minotaur.lua#L85)

Last update : 03/09/2015 at 12:23PM UTC+2 by LeMagnesium

What is that mod ?

The "runes" mod is our selfmade spells implementation for minetest. At the moment, the spells names aren't very great choose. We keep the effect of each spell mysterious (for the moment) :)

How can we make textures if we don't know what are their use ? :)

(If you want participate, join us in our dev irc)

We keep the effect of each spell mysterious (for the moment) :)

The names are pretty abvious though..

Can you leave a link for actual textures? For we can have a look at them :)

I will edit the first post to put the links to the pushed textures.

JukeBox : 5 new textures, 1 redo (the first)
https://github.com/Ombridride/minetest-minetestforfun-server/commit/e4bbe52feb8391f00053bbdcb5b1ab8a9473d6e1

Runes: 1 new texture : 703518

@Ataron, can you created and commited this textures soon ? (The Warrior and Hunter integration aren't very far ;))

Add a few of them : https://github.com/Ombridride/minetest-minetestforfun-server/commit/25a5d20501897e799a0b83c4240b31e6f7fd9957 (with the help of paly2)

Should we close this now?

Closed this issue, we will create another issues when we will need more textures


Cut down the staff UI to just be 1 robot

The current staff UI has 2 alliances and 4 robots. We only need this to be 1 robot now, as well as 1 alliance.
staff UI needs these things:
match num
robot ip
number of active tinder
number of deactivated mirage buttons
start button
time adjust (for just 1 alliance)
match recovery

been done and undone


Bump version to 0.11.1, update log

This change is

Had a typo in the link, now let's get this merged.
bors r=Rhuagh,jojolepro


Clarify Database::basic vs. DatabaseRef::basic

I bumped revm in foundry and fixed all breaking changes, but my tests started failing
after some debugging I noticed something here:
https://github.com/bluealloy/revm/blob/8f01d8609a4d829bd9994941a7fff920e9af4f88/crates/revm/src/db/in_memory_db.rs#L226
this will create a new DbAccount entry and mark it as non-existing
https://github.com/bluealloy/revm/blob/8f01d8609a4d829bd9994941a7fff920e9af4f88/crates/revm/src/db/in_memory_db.rs#L223
and will always return None for the AccountInfo if the state is non-existing
however with following pattern:
let mut info = Database::basic(&mut self, address)?.unwrap_or_default();
info.balance = balance;
self.insert_account(address, info);

another Database::basic(&mut self, address) will still return None because insert_account does not update the state.
this was a bit suprising because
let mut info = DatabaseRef::basic(&self, address)?.unwrap_or_default();
info.balance = balance;
self.insert_account(address, info);

would return the info without additional state check:
https://github.com/bluealloy/revm/blob/8f01d8609a4d829bd9994941a7fff920e9af4f88/crates/revm/src/db/in_memory_db.rs#L285
so now I'm wondering whether I shouldn't use Database::basic(&mut at all

load_account will mark the account as NotExisting only if internal Database returns None, this seems like correct behaviour, DatabaseRef should do the same (will change that behaviour).
In both cases, it should be None, does this fixes the problem @mattsse? I am assuming that the bug is that info in DatabaseRef preserves the NonExisting while with Database with call of unwrap_or_default, AccountState will be set  to None.

I think that should do it.
thanks!


⚠ ClamAV has degraded performance

In e04b233, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in c10d6f5.


Change Bitcoin Cash logo to green instead of orange

Causes less confusion for noob and it looks better. Serves its purpose as cash better, too. Coinbase also has it officially listed in green

+1 in favor of changing the logo to green.
I know that BCH started with the orange logo, but I think that green:

better represents CASH, has positive connotations with cash (greenbacks, positivity, success)
differentiates BCH from BTC more strongly than the circle vs circle inside rectangle currently does
is in line with styling already used by exchanges/community

Green is already widely used as BCH branding, I think it would be great if bitcoincash.org would adopt this design change.

Favor green logo/design too.

Not in favour.
Replacing the colour and design is a major change to the way in which Bitcoin Cash is perceived, and such a change should not be undertaken based solely on subjective remarks. That green looks better than orange and has more positive connotations is pure speculation based on subjective preference. At least until any evidence is provided.
Regarding widespread use of the green color to represent Bitcoin Cash. It'd be nice to see some concrete numbers. To me it seems that orange is still the norm, as seen in coinmarketcap.com, Bithumb (number 1 BCH exchange in terms of volume), Bittrex, and others.
Last, I'd like to point out that the argument that green is better suited to represent a currency might be very Western-centric due to the influence of the US dollar and use in mainstream Western media and film industry. It'd be nice to have some feedback from people with different backgrounds as to the truth of this statement. In particular, I believe bills are red in China. It also questionable whether we want Bitcoin Cash to be more strongly associated with fiat money, and the US dollar in particular.

Having multiple logo is a strong sign of decentralisation in my opinion.

I agree with Mohamed, personnally I prefer green but it's just my opinion. Some businesses have switched to green (Bitcoin.com and Coinbase), which I find it great because it helps users understand that there is a difference.
Local businesses tend to use orange which reminds of the Bitcoin color from what I've seen.
I think it's a strength to have this optionnality.

@MohamedKiouaz I like your idea of adding it to the FAQ at a bare minimum. I personally am a fan of changing the logo, and have made my views clear in other posts. Changing the branding on the existing site is a big move, but at least mentioning that both green and orange logos are being used seems like a quality addition.

Oh boy... I stick to orange 🍊
Bitcoin Cash is Bitcoin and Bitcoin was always orange. It is just a  matter of time until Core is losing its dominance and fading away as a collector's item for Core supporters.
Merry Christmas ;)

merry Christmas !

Stick to orange.  I don't think there is consensus to change it on this website.

that what they need , the orange...
And
As long it start with Bit it will be orange to scam people

Orange performed several orders of magnitude better than green in AB testing twice.  Unless someone wants to build an evidence based case the the contrary, this issue should be closed as resolved.

@schancel > evidence
You keep using that word, I don't think it means what you think it means...


context.slots should hold functions

context.slots should hold functions like Vue 3.0 describes.

This plugin can't implement all details of the RFC because some are simply not feasable in Vue 2. This is one of those.

But scopingSlots already provide this feature and it will replace the slots in 3.0.

In Vue 2, normal slots and scoped slots are still separated, and normal slots do return vnodes, not functions.
That's just how it works in 2.0 and this plugin won't change that.

I think it will make sense to merge scopedSlots and slots in the slots property to make it possible to migrate from this lib to Vue 3

Also note that Vue 2.6 already exposes normal slots as functions under $scopedSlots. So, if this lib were to require Vue 2.6 then context.slots could be able to mirror this.$scopedSlots, no?

@thecrypticace The context.slots will be a mirror of $scopedSlots in the next release.


Deployed Plant contract should work with non-mock Chainlink

Plant is deployed like:
    if (chainId === 31337) {
        await hre.deployments.deploy("PlantMock", {
            from: deployer,
            args: [
                vrfCoordinator.address,
                link.address,
                "0xf86195cf7690c55907b2b611ebb7343a6f649bff128701cc542f0569e2c549da",
                hre.ethers.utils.parseEther("0.0001"),
                land.address,
                fruit.address,
            ],
            log: true,
        });
    }
    await hre.deployments.deploy("Plant", {
        from: deployer,
        args: [
            vrfCoordinator.address,
            link.address,
            "0xf86195cf7690c55907b2b611ebb7343a6f649bff128701cc542f0569e2c549da",
            hre.ethers.utils.parseEther("0.0001"),
            land.address,
            fruit.address,
        ],
        log: true,
    });

Depending on deployed network, link.address and next param probably differ. Currently, it's pointing to the mock Link contract.

Does the keyHash need to change?

All settings are configured now in deploy script for Mumbai.


Get trainable weights from SFT

I ran the provided SFT script, but in the result output dir, there is no such "pytorch_model.bin"? Seems only have the adaptor related weights.

Hi,
I think you need to go into the path_to_saving_checkpoints and run python zero_to_fp32.py . pytorch_model.bin to get the pytorch_model.bin
Regards,
Yukang Chen

I will close this issue as it has been inactive for several days. Please feel free to re-open it if there are any others to discuss.


Loan tab not updating when switching to other address

Issue:
When switching to 2nd address, loans tab show information from 1st address.
How to reproduce:
Wallet with multiple addresses and vaults on each address.
On address 1, open loans tab and manage loans to see information about loans.
Tab portfolio and switch to address 2. open loans tab. Now you still see the loans information from address 1.  If you tab loans again, correct information about loans from address 2 get displayed.
Expectation:
Correct loans information get loaded directly after switching to 2nd address with a vault.
LW 2.4.2
iOS 15.7

/area loans


Add micrometer metrics and optional scrape endpoint

Users can now optionally add configuration like:
adminHttp:
  host: localhost
  port: 9193
  endpoints:
    prometheus: {}

to offer http prometheus metrics on /metrics
A prometheus implementation of MeterRegistry is wired into the global registry so filter classes can use micrometer's static methods to configure metrics for the global registry.
Why:
Users will want to observe what the proxy is doing

@tombentley any further thoughts?

@robobario do you want to write up a suitable commit message and merge this?

@robobario do you want to write up a suitable commit message and merge this?

will do, thanks for review @tombentley and @SamBarker


Unlink service that was deleted

After service gets deleted odo should "unlink" it from all services that link to it.
This requires to have "odo unlink" capability first #929

This should be pretty easy to do once #1107 is in (which I am hoping will happens soon), so I am adding it to this sprint


Update tcpproxy upstream from github.com/google/tcpproxy to inet.af/tcpproxy

Signed-off-by: William Zhang<EMAIL_ADDRESS>

Proposed Changes
tcpproxy repository has been moved out of the github.com/google org to github.com/inetaf.

Types of Changes
Switch to the new repo.
FYI: https://godoc.org/inet.af/tcpproxy/

Verification

Linked Issues

Further Comments

Remove pkg/static/zz_generated_bindata.go from the PR, this shouldn't need to change as part of this, and your local changes conflict with those generated by CI.

Looks good! We'll need an issue to track this against for QA. Other than changing the upstream repo, are there any specific issues that you're aware of this fixing?

Looks good! We'll need an issue to track this against for QA. Other than changing the upstream repo, are there any specific issues that you're aware of this fixing?

We used tcpproxy in a component and referred to the implementation of K3S, but found that the version of library was updated.
So there isn't a  specific issue  to fix, just a regular repository upgrade to keep up with the upstream, thanks.

need resolve the go.md conflict.


Update README.md for Rust 1.5

As of Rust 1.5, cargo install is in the stable build

Cool, thanks @LFalch


Enhance autoformat logic for Groovy files

What's changed?
Bringing back some auto formatting rules to the G type. This focuses on tabs VS spaces, normalizing EOL characters, blank lines, and removing trailing whitespace.
What's your motivation?
Historically, Groovy auto formatting was a bear and would pretty often result in files becoming invalid. As a result, it was disabled fully in the org.openrewrite.java.format.AutoFormatVisitor, so that the Java auto formatting rules would never be applied to any non-J type.
Anything in particular you'd like reviewers to focus on?
While re-introducing auto format support, I found two bugs. One of which is found fixed within this PR, but the other has been noted with a pair of disabled tests.

If a visitor used with withClasses or withImports on an instance of G, this would result in the G.CompilationUnit being recreated due to a bug in the logic. Specifically, getting the classes or imports will always return a new list which means that they will never have instance identity equality. So instead, we should verify that the elements themselves are unchanged, then take the appropriate actions.
GroovyParser appears to be unable to parse the implicit-public constructor. This additionally may extend into constructors with default arguments, so there is a second test case to cover that specific case.

Have you considered any alternatives or workarounds?
N/A
Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've read and applied the recipe conventions and best practices
[x] I've used the IntelliJ IDEA auto-formatter on affected files

I'll figure out what is wrong with auto formatting the rewrite-gradle tests tomorrow and get that fixed.


interface ApplicationParametersInterface

I propose the base class ApplicationParameters (using a special interface) and place a number of standard web applications so that third-party software (modules and extensions) could use it in the future.
interface ApplicationParametersInterface
{
    public function get(string $name): string;

    public function getAdminEmail(): string;

    public function getCharset(): string;

    public function getEmail(): string;

    public function getInfoEmail(): string;

    public function getLanguage(): string;

    public function getName(): string;

    public function getSupportEmail(): string;

    public function has(string $name): bool;
}

This interface with its implementation will allow you to get any string parameters from the configuration without their preliminary description in the application parameters class.
By also extending this class in the application, we will be able to send data of any type and format (arrays and objects).
The standard implementation can work only with parameters of the type string deliberately, for strong typing.

I don't think it is a good idea:

There's no need for interface since it is unlikely to have more than a single implementation.
A third party service won't need all these parameters at once. Usually that's one or two parameters at max. For example, mailer will need support email or admin email only. A service should require what's needed, not where to get it.

It was an alternative to the params array from yii2. Now I don't see anything like it.

It was an alternative to the params array from yii2. Now I don't see anything like it.

You can use array $params (from config params.php) in container configuration (common.php, web.php, ...)

Direct access to $params isn't a good thing overall. Individual services should receive params needed at configuration time. ApplicationParameters is for parameters that don't have any service associates with them. These are usually used in views only.

Direct access to $params isn't a good thing overall. Individual services should receive params needed at configuration time. ApplicationParameters is for parameters that don't have any service associates with them. These are usually used in views only.

I generally thought about using this functionality exclusively in layout and view.

I think we'll stick with current solution for a while. We may reconsider it later.


Update opam - fix dns.7.0.2 revdep cca.0.5

Maybe this will fix the revdep issue here: https://github.com/ocaml/opam-repository/pull/23915#issuecomment-1589175206

thanks for your PR, since the opam-repository PR is already merged, I'll close this one. If you think this is the right way forward, feel free to open a PR directly to ocaml/opam-reository.

@hannesm thank you for taking a look. I will be discussing with the other opam maintainers regarding this (and potentially open a pr directly to the opam repository)


[LOG4J2-1013][Lookups] Allow variables with dashes

JIRA Issue
Move the logic of getting the default value from the StrSubstitutor to the Interpolator

Hey @garydgregory @remkop. Could anyone check the status of this PR? It seems that Travis failed with an error not related to this code.

Can you rebase on master? This will also trigger another build.

Done. Although I think I messed a little bit with the history.

Closing this as a fix has been committed to allow keys with leading dashes to be escaped.


added DELETE route for users; PUT request not working

PUT request is giving me issues. It's reading the ID that I am passing in as a column and saying that the 'column {id} does not exist'.

have you passed debug to your knex object to see what error is coming back?

// Update with your config settings.
require('dotenv').config()
module.exports = {
development: {
client: 'pg',
connection: process.env.DATABASE_URL,
migrations: {
directory: './data/migrations'
},
seeds: {
directory: './data/seeds'
},
debug:true
},
staging: {
client: 'postgresql',
connection: {
database: 'my_db',
user:     'username',
password: 'password'
},
pool: {
min: 2,
max: 10
},
migrations: {
tableName: 'knex_migrations'
}
},
production: {
client: 'postgresql',
connection: {
database: 'my_db',
user:     'username',
password: 'password'
},
pool: {
min: 2,
max: 10
},
migrations: {
tableName: 'knex_migrations'
}
}
};


Bad characters encadage (""")  into module description text

Describe the bug
After update module v4.5.1 -> v4.6.0, some texts are badly encoded (HTML code is not interpreted), see attach.
Server

Web Server: Nginx
PHP Version: 7.1
Prestashop Version: <IP_ADDRESS>
Module Version 4.6.0

Thanks for this report, I had a look at this and this seems to be caused by a escaping done from PS 1.7.
I opened #285 to fix that visual issue.

Closed via #285