Unexpected dependency in build script

This line: https://github.com/coreos/etcd/blob/v2.0.11/build#L14 introduced by https://github.com/coreos/etcd/commit/d30e764b2d20a783a0f569d2677a125da1832936 introduces an unexpected build-time dependency on git. This breaks any build where you ship the code to a remote machine to compile where you don't have, and don't want to have, git.
Is there any way we can get versioning information for that script without adding the extra dependency?
How about writing "N/A" or some other default in case git cannot be found?

@luan Yes. We are aware of this and considering to fix this before next release. Do you want to send a pull request? git not found or similar string would be good enough.

Happy to, just didn't know what the right solution would be, now that we know, we'll get on submitting the PR.

Done, it'd be nice if this gets backported to 2.0 as well.

LGTM
/cc @yichengq

fix https://github.com/coreos/etcd/issues/2867

lgtm

@luan could you update commit title to build: default git sha to GitNotFound in case git fails?

@yichengq how's that?

@luan Thanks. Merging.


feat(edge-local-hooks): CEXT-2904 - Updated hooks plugin version.

Description
Bumped hooks plugin version.
Related Issue
CEXT-2904
Motivation and Context
Allows for ES6+ imports to support additional runtime environments, such as edge compute.
How Has This Been Tested?

Link and run local development

aio plugins:link @adobe/aio-cli-plugin-api-mesh
aio api-mesh run mesh.json

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Would it make sense to consider publishing a beta version with this change?

Would it make sense to consider publishing a beta version with this change?

Updated to alpha release tag based on alpha/beta package versions of mesh-builder and plugin-hooks.

Updated to alpha release tag based on alpha/beta package versions of mesh-builder and plugin-hooks.

Do you intend to publish the alpha version of the CLI?  If so, merging this PR to the develop branch won't publish anything as you can only publish a beta version from develop.

Updated to alpha release tag based on alpha/beta package versions of mesh-builder and plugin-hooks.

Do you intend to publish the alpha version of the CLI? If so, merging this PR to the develop branch won't publish anything as you can only publish a beta version from develop.

Updated to beta version.


Upgrade package_info_plus : ^4.0.2

../../../../.pub-cache/hosted/pub.dev/package_info_plus-3.0.2/lib/src/file_version_info.dart:13:17: Error: Field 'wLanguage' cannot be nullable or have type 'Null', it must be int, double, Pointer, or a subtype of Struct or Union.
external int? wLanguage;

I close this as it is already upgraded on the dev branch.


Please add support to Django 1.8

When using Linguo with Django 1.8, I receive the following error:
AttributeError: 'NoneType' object has no attribute 'split'

Its possible that this PR: https://github.com/zmathew/django-linguo/pull/18 fixes the error you are seeing.


feat(aws): Add support AWS WAFv2

Issue #506

@alikhajeh1 ready to check

Hey @alikhajeh1! Will happy to review this

@ekifel ready to review

@alikhajeh1 LGTM!


Windows

Windows

yes

So what’s the issue? I don’t understand

No issue posted still. Closing.


Implement ability to migrate Identity Management configuration from OCP 3.x cluster to OCP 4.0 cluster.

As we build the functionality to assist with migrating Identify Management configuration, let's ensure we capture:

Able to work with user input via survey
Able to work with data from a configuration file

For Identify Management configuration in 3.x see:
https://docs.openshift.com/container-platform/3.11/install_config/configuring_authentication.html
Please test at least 3 different authentication provider configurations:

[ ] Httpasswd
[ ] Github Auth
[ ] Google

related PR - https://github.com/fusor/cpma/pull/29

 [ControlPlane] Implement ability to migrate Identity Management configuration from OCP 3.x cluster to OCP 4.0 cluster.


Set searchable mail in article_emails like article_reviews_emails.

 Reimplement the search toolbar in the mailing queue of a given preprint


Fix for flaky error code 72 on Risco Cloud

This code change aims to mitigate a flaky error code 72 experienced in Risco Cloud, as mentioned in #16.

I think I somehow missed this, but it looks ok. Is this still relevant?


[x86] [ARM] WOCCatalog Foundation Tests - In URL Session, clicking Resume crashes the app

Latest master build - with 1701 payload

@aballway This is a result of #1607.
[self _registerDownloadTask:newTask withCompletionHandler:completionHandler];
is called in multiple places in NSURLSession, but if resumeData is nil, we insert a nil object into the array and blow up.

Not clear if reference platform allows this.

Checked reference platform, this is indeed expected to crash.  We were previously passing nil value for resumeData and expecting the session to return a nil.


external_node-1  | error: unexpected argument '--enable-snapshots-recovery' found

🐛 Bug Report
📝 Description
Using the ansible-en role release v3.8.1, after complete configuration with ansible role
playbook has enable_snapshots_recovery: true and enable_consensus: false
Proceed to run docker compose up -d in /opt/en
Getting error
external_node-1  | Usage: zksync_external_node <--enable-consensus|--components |--config-path <CONFIG_PATH>|--secrets-path <SECRETS_PATH>|--external-node-config-path <EXTERNAL_NODE_CONFIG_PATH>|--consensus-path <CONSENSUS_PATH>>
external_node-1  |
external_node-1  | For more information, try '--help'.
external_node-1  | error: unexpected argument '--enable-snapshots-recovery' found
external_node-1  |
external_node-1  |   tip: a similar argument exists: '--enable-consensus'
external_node-1  |
external_node-1  | Usage: zksync_external_node <--enable-consensus|--components |--config-path <CONFIG_PATH>|--secrets-path <SECRETS_PATH>|--external-node-config-path <EXTERNAL_NODE_CONFIG_PATH>|--consensus-path <CONSENSUS_PATH>>
🔄 Reproduction Steps
docker compose up -d
in /opt/en
🤔 Expected Behavior
--enable-snapshots-recovery should not be an unexpected argument.
😯 Current Behavior
As in description
🖥 Environment
Any relevant environment details like:

Ansible version ansible [core 2.17.3]
Operating system Ubuntu Jammy 22.04
External Node version 24.23.0 or 24.6.0

📋 Additional Context
Add any other context about the problem here. If applicable, add screenshots to help explain.
📎 Log Output
docker compose logs related error pasted in description.
Paste any relevant log output here.

@lion100x thanks for reporting, this is now fixed in https://github.com/matter-labs/ansible-en-role/releases/tag/v3.9.0


apps Error : RetryAfter()

I'm trying to use django-telegram bot but during the running phase I have this error frequently:
ERROR 2018-05-29 16:28:47,375 apps Error : RetryAfter()
after this message the system doesn't work, this is the message during the chat:
WARNING 2018-05-29 16:28:55,619 views Request for not found token : XXXXXXXXXXXXXX
[29/May/2018 16:28:55]"POST /prefix/XXXXXXXXXXXXXXXX/ HTTP/1.1" 200 2

The result is that I don't receive any message in telegram.
I think the problem is in the rapidly sequence of instruction in apps.py file during the setWebhook phase .
A possible solution that I finded is this:
setted = bot.setWebhook(hookurl, certificate=certificate, timeout=timeout, max_connections=max_connections, allowed_updates=allowed_updates)
time.sleep(5)
webhook_info = bot.getWebhookInfo()

I added to time.sleep function and now the system seems to work.

@newton21890 Best approach to solve it PR #10


2700's section revamp #235

Is IndexedDB automatically deleted or not? Can we expect a small summary for beginners without having to read through it completely, please?


feat: use folder without creating a file

Feature Request
At the moment, when creating a subfolder you need to create a cairo file that'll containing all the stuff existing in that folder:

lib.cairo
tests (folder)
tests.cairo

So if I have a tests folder I'll need to have a tests.cairo file that'll contain one line per fail existing in tests.
It would be easier if it was possible to make those directly in lib.cairo:
mod tests;
use tests:test_file1;
use tests:test_file2;

Mind that this is diverging from Rust's design. Perhaps this could be replaced with a compiler plugin like https://github.com/dtolnay/automod

Not sure I understand how it differs:
https://doc.rust-lang.org/cargo/guide/project-layout.html
Keen to understand what I'm missing 😄

Your suggestion is missing module declarations for test_file1 etc. and I understand that you ask for having an ability to omit them. That's not how things work in both Cairo and Rust, these mod test_file1; items are the only ways to tell the compiler about the existence of these modules (in normal module tree). The automod procmacro allows you to autogenerate these.
In Rust there is an UX trick that makes the tests folder work differently, but mind that this is just an UX trick, and implementation-wise this works completely different. Each file in tests folder is actually a separate compilation unit and is processed on Cargo-level. The outcome of this is that you get separate test binaries for each top-level file in tests dir in Rust. This is not something portable to Cairo and still it's a topic for the test runner to handle.

I think what @gaetbout has it mind (and please correct me if I misunderstood) is not just the tests dir specifically but that any "module directory" has to have a .cairo file of the same name associated with it.
Here's a different example:
src
├── core
│   ├── bar.cairo
│   ├── baz.cairo
│   ├── foo.cairo
├── core.cairo
├── external
│   └── pragma.cairo
├── external.cairo
├── interfaces
│   ├── IBar.cairo
│   ├── IBaz.cairo
│   ├── IFoo.cairo
│   └── external.cairo
├── interfaces.cairo
└── lib.cairo

Where e.g. core.cairo is only:
mod bar;
mod baz;
mod foo;

and lib.cairo is:
mod core;
mod external;
mod interfaces;

The question is why do we need core.cairo, external.cairo and interfaces.cairo at all if they only declare the mods in the respective directories. Can't the compiler figure out by itself from lib.cairo?

I think it's obvious that the compiler could figure this right now, but how should it behave when #3457 is merged? Should all modules be pub or not?

They should be whatever they're declared as.
If I understand the linked PR correctly, there will be the possibility to have pub mod Foo and also an internal mod Bar.

I was asking about these compiler inferred declarations for files within a directory :-) In your example, that would mean, what should the compiler infer as contents of core.cairo and lib.cairo files

@milancermak
This can be solved following this pattern:
mod interfaces {
mod IBar;
mod IBaz;
mod IFoo;
}

Since Twitter is not the best place to discuss things, moving the discussion here.
The question is, can we use mod declaration without intermediate files, as described above?
@mkaput considers this to be an unintended compiler bug, @gaetbout an undocumented feature. I think it's pretty neat as well. In either case, it's used in Satoru
What do you think @OriStarkware @spapinistarkware @yuvalsw? Does this work as intended? Can we keep using it?

Seems we already can do it, I've seen it used in multiple other projects.
It seems like a feature in the Rust grammar so I see no reason to remove it.


Use runtimeVersion as the key in Job.

Instead of rewriting the entire thing for ScoreCard I figured it would be the best to just adapt Job a bit.
The GC will be done in a subsequent PR.
Before the next deploy the indexes should be updated, but not cleared (so that the old releases will continue to work too).

This means the old versions will keep running dartdoc and analysis?

Correct. It also means that on a release rollback it should just work without any issues (minus the dartdoc generated content, but I'm on that too).


Backspace element removal

Which issue does this PR address?

Make the most standard shortcut (i.e. Backspace on MacOS and DELETE on other systems) the menu shortcut
Make the other shortcut available via the browser view (listen to it and react accordingly)

Closes #1989
Acceptance Criteria

[ ] Corresponds to the concept
[ ] Corresponds to the design

Definition of Done

[ ] corresponds to the design principles
[ ] corresponds to the code standards
[ ] passes Continuous Integration checks
[ ] available as feature branch on GitHub

[ ] contains the cleaned up commit history
[ ] commit messages satisfy our commit message guidelines
[ ] a single commit closes the issue via Closes #issuenr

Note for the reviewer
I decided against using the globals.isMac property inside the edit menu to avoid chaining this through the whole application. The helper function should be satisfying. We could also consider using this for the KeyboardBindings as well, but since we already make the isMac property available there as well, it should be good.

Updates @nikku @barmac: I went for updating the menu entries in the KeyboardBindings module depending on the platform and registering the secondary shortcut afterward. I decided to do a proper find-and-replace inside the entries instead of directly manipulating, to avoid ending up in monkey-patching stuff.

Does not work on Linux :thinking:.

Works for me on Windows...

Must have been a caching issue. Now it works for me, too. :crossed_fingers:

👍 We should consider your added https://github.com/camunda/camunda-modeler/pull/1994#discussion_r517165140 anyhow, let's align this one in another PR. --> Will add


[✨] Please make the CLS borders opt-in

Is your feature request related to a problem?
Not related to an issue.
Describe the solution you'd like
I would much prefer the display of borders around objects to be opt-in, rather than a default.
flag in the Vite config?
Describe alternatives you've considered
there are no alternatives.
Additional context
When working on a design, having random red borders pop up doesn't help much and is distracting.
I get why it is there and I am sure it is a great way to diagnose slow speeds or layout jiggling, but it should be up to me wether I am in debug mode or wether I just want to focus on design.
At least in my case, they are not consistent either, sometimes a block is affected, sometimes not. This is visually very annoying.

This is the first and ONLY match on Google when searching for "quick cls". These even appear when just playing with the sample code and it's really not obvious what's going on...

Is this still problematic?

 Still, I like to have some level of control over this, as I prefer to decide myself when in the process I will take care of an optimisation issues.
Like with the useVisibleTask$ discouragement: Yes, I know it can be bad and it is a last resort but there is also the fact that I might not have the time to tackle each case right now and for that, I can disable the eslint warning on case by case basis. It is up to me, it is my responsibility in the end.
Real world example: I wrote a 24k loc qwik frontend for ecommerce and it gets complicated.. I resorted to useVisibleTask in 2-3 places because it was the only way to get a feature working for now. I am perfectly aware that it is discouraged, but I also have a deadline and need to move on and decide to come back later and a solution might very well cause a medium sized refactoring that simply isn't possible right now.
There are also some complicated grid views and a few generated responsive pages for which I currently do not have a solution on how to handle some limited cls issues. Same thing: I just dont have the time right now and there are other priorities.
The thing is, in the end, the functionality and the resulting app still works perfectly fine but Qwik makes the assumption that everybody is chasing metrics at all times.
The only thing I am asking is to have an option to decide myself. On the other hand, as humans do, I also became quite efficient at simply accepting the fact that there are some exclamation marks and I have more important things to solve for the time being, so I just move on. :-)

I suppose we can have an option to disable it in the qwik vite plugin. PRs welcome

Maybe a simple customisation of this CSS class could solve the problem.

Closed by #6450

@gioboa are you sure it's handling the CLS issue and not just the images?

I linked the wrong PR. Here you are https://github.com/QwikDev/qwik/pull/6427

thanks!


Add repl to swift-help topics

Most just run swift repl here, but also reference the possibility of passing Swift Frontend arguments.
rdar://109411493

@swift-ci Please test


can you support a option tansform

transform:true use css3 transform
transform:false don`t use css3 transform
if there are so many elements  in the draggabilly·s,  it will shake
i think  it  happen at the “proto.dragEnd” function

Thanks for your input. See #92 Closing here.

#92    is different  with this
this issue means ,when i dragend the draggabilly`s element ,it will shake


Optional arguments

Are optional arguments currently possible with click?
For example...
$ greet
hello all
$ greet john
hello john
$ greet john sally
hello john and sally

I think the documentation could make this flag more obvious, by putting a section on the Arguments page.

I landed here looking for a way of specifying multiple optional arguments. Based on the examples above, I did:
@click.command()
@click.argument('size', required=False)
@click.argument('flavour', required=False)
def order_pizza(size, flavour):
    print "Ordering {} ({})".format(size, flavour)

This gives you two positional arguments, both of which are optional.


Input - really slow mouse movements not detected downwards or rightwards

 Issue by ldmldmldm
Thursday Aug 11, 2016 at 01:44 GMT
Originally opened as https://github.com/Cloudef/wlc/issues/181

Hi.
Moving really slowly (like 0.3cm/sec) results in the cursor not moving at all.

Only occurs when moving downwards or rightwards.
Does not occur when moving upwards or leftwards.
Occurs for the apple touchpad and some mouse.
Does not occur under libinput on X11 or weston.

Note: on the touchpad I start from the middle to avoid any of the palm detection (which triggers if you start from top left or top right)
I confirmed I am using libinput on X using
arch:~$ grep -e "Using input driver " ~/.local/share/xorg/Xorg.0.log
[ 25022.988] (II) Using input driver 'libinput' for 'USB Optical Mouse'
[ 25023.031] (II) Using input driver 'libinput' for 'bcm5974'

My sway settings:
input "1133:49242:Logitech_USB_Optical" {
    accel_profile flat
}

input "7247:3:SIGMACHIP_Usb_Mou"{
    accel_profile flat
}

input "5426:67:Razer_Razer_DeathAdder_Chr" {
    accel_profile flat
}

input "1452:594:Apple_Inc._Apple_Internal_Keyboard_\/_Trac" {
    accel_profile flat
    tap enabled
    scroll_method two_finger
    dwt enabled
    natural_scroll enabled
}

input "1452:594:bcm" {
    accel_profile flat
    tap enabled
    scroll_method two_finger
    dwt enabled
    natural_scroll enabled
}

My X11 settings:
Section "InputClass"
    Identifier "libinput touchpad catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "libinput"

    Option "Tapping" "true"
    Option "NaturalScrolling" "true"
    Option "DisableWhileTyping" "true"
    Option "ScrollMethod" "twofinger"

    Option "AccelProfile" "flat"
EndSection

Version info:
arch:~$ pacman -Qi wlc-git
Version         : 0.0.5-1
arch:~$pacman -Qi sway-git
Version         : r1863.49afdb4-1
arch:~$ sway -v
sway version 0.9-38-g49afdb4 (2016-08-10, branch "master")

Thanks.

 Comment by ldmldmldm
Thursday Aug 11, 2016 at 01:49 GMT

@psgarsenal no https://github.com/Cloudef/wlc/issues/166#issuecomment-237883598 does not solve the issue. I believe the profile is already flat, and there is something else screwing with the cursor when going rightwards and downwards.

 Comment by Cloudef
Thursday Aug 11, 2016 at 11:08 GMT

Do you have this issue with weston?

 Comment by ldmldmldm
Friday Aug 12, 2016 at 03:01 GMT

No. Weston works perfectly (with both mouse and touchpad) in all directions.

 Comment by cafehaine
Monday Aug 29, 2016 at 06:48 GMT

Ok so I did some testing, and it turns out that "accel_profile flat" in sway does not solve my issue, and that it does not appear in weston, so this issue and mine (#166) are the same
Basically, to sum up both issues, there is a problem that causes slow movements to not be detected in certain directions, depending on the mouse. I don't know about the apple's trackpad, but it seems that our problem is still linked with hi-dpi mice

 Comment by ldmldmldm
Wednesday Aug 31, 2016 at 00:09 GMT

@psgarsenal your linked issue seems to have different symptoms, are you now exhibiting my symptoms also?

 Comment by ldmldmldm
Wednesday Aug 31, 2016 at 07:01 GMT

Logitech B100 at 800dpi and Razer Deathadder Chroma at 1200dpi, Sigmachip at 800dpi

all show the issue with no configuration applied
but do not show the issue with accel_profile flat

The Logitech I have at work shows the issue, but i'll check this again when I next go in.
Apple touchpad

does show the issue with accel_profile flat
I confirmed the settings are being applied as natural_scroll does apply
it's so bad that sway is basically unusable
works perfectly in weston and x11

 Comment by cafehaine
Wednesday Aug 31, 2016 at 06:23 GMT

Symptoms were the same explained differently, i cannot move my mouse slowly, in the down-right direction, I just thought moving it in circle would show it better on video.
It must be something with the hardware acting in a different way than "traditional mice", since, as you can see in my issue, a 5 buck mouse don't have this problem.

 Comment by MateusZitelli
Thursday Jan 05, 2017 at 11:14 GMT

Any updates on this? The issue persists with the actual master using Apple Touchpad.


Unexpected results with complex foreign keys

As per my comment in #101, we're getting some odd results in some of our entities:
@Entity("booking",{schema:"dbo"})
export class Booking {

    @ManyToOne(type=>Cancellationpolicy, Cancellationpolicy=>Cancellationpolicy.bookings2,{  nullable:false, })
    @JoinColumn({ name:'LanguageID'})
    language:Cancellationpolicy | null;

Our schema has the following:
ALTER TABLE [dbo].[booking]  WITH CHECK ADD  CONSTRAINT [FK__booking__cancellationPolicy] FOREIGN KEY([CancellationPolicyID], [LanguageID], [CountryID])
REFERENCES [dbo].[cancellationpolicy] ([CancellationPolicyID], [LanguageID], [CountryID])

Looks like the multi-column foreign key relationship may be giving the generator trouble.
Is it even possible to model that in TypeORM?
I've put together a repo with our full schema, along with my method for generating models, here.
Thanks a bunch.

I have the same issue.  I had multiple foreign keys on a single table and the generator failed to create them properly.  If I remove one of the keys it works fine, but with both it creates entities that cause exceptions when attempting to read the db.  In order to generate my model I need to run a script that copies the db structure to another database and drops the foreign keys.  Then generate with no relationships.

I'd love to see this feature in the next version. I need to create several partitioned postgres tables and need compound foreign keys. It would be great to have this natively in typeORM, rather than what I'm gonna have to do in the interim - insert/update manually.

Implemented in<EMAIL_ADDRESS>


Height of donut containers

Add some indicator that there are more donuts than one on the (entire) page; didn't realize I should scroll to see more.

Done :v:


Semantic segmentation source

Hello,
When do you plan to release source code corresponding to section 4.4 Semantic Segmentation in the paper?
Thanks!

Hello,
In case of detection and segmentation, the distillation part is almost identical to ImageNet code. But, the base training code is quiet complicated and there are a lot of things to clean up.
Perhaps the release date will be after the ICCV 2019 conference or after the CVPR 2020 submission deadline.

Segmentation codes were released today.
So, this issue will be closed.


Add name to nova/logout route

Nova was failing to load because it could not find the route named nova.logout. Routes can't have multiple names so this gives the name to the redirect. I'm open to better solutions; I couldn't find a more elegant fix.
Closes #451

Assigning to Ross per Slack:

I'm about to run away from my computer for a bit but I may play with that later
View in Slack

Per slack this is the least bad way to do this.


fix(Button): allow to overwrite the focus config

Hey Nik,
Changes look good. But:

I see a test cases breaking, I tired to look into it but it needs more debugging.
As we discussed I think we need to work to make focus styles more easily configurable and simplified for user. Default I think should be blue outline one....but  then user should be able to easily switch to animated focus, or use some altogether different focus style of his own. We can think more to improve it.

@jpuri I will continue on the bootstrap theme today. I think this will have a big impact on the API design.


Add Webhook For Stream Events on Publish Start and On Publish Stop

Webhook for stream publish event if stream started publishing or stopped.

This won't be merged for reasons that were already explained to you.


Expose trace IDs as environment variables

Requirements for Contributing to this repository

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?
This PR exposes the traces ids, such as trace_id and span_id, of the traces spans as environment variables.
The environment variables are:

X_DATADOG_TRACE_ID for the traceID.
X_DATADOG_PARENT_ID for the spanID.

Those environment variables are available for Jenkins Build span, and for all Jenkins Pipeline workflow steps, setting the correct spanID in the correct step environment.
This feature is required to be able to correlate spans sent from the datadog-ci tool.

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.

I'd say it's not possible to add this API to datadog.opentracing.OTSpan because the lack of this API is intended, as we don't want the user can modify the IDs of the Spans. This should be an internal detail.


Improvements to StaffSearch duplicates

Change vw_StaffSearch to reduce the duplicates
Change TableList key to avoid warning on any possible duplicates

We ended up addressing this (and more) in #88, including being able to remove the extra GROUP BY for search results we added in earlier. Take a look at the how the search query ended up and reach out if you have any questions, I'd be happy to talk through it or hear any other ideas!


🎭 [vue-tsc] Resolve alias when generating the types

Hi 👋🏻
I prefer using absolute paths using aliases in projects. I'm building a UI framework and found that vue-tsc doesn't convert the aliases to proper path. IDK if this is from vue-tsc or working can not be enhanched but generated types have alias and doesn't resolve the type properly:

In above image, I changed @ to package name anu-vue and still due to how package's folder structure this path fails to load and result in broken types.
Can I do something on my side or this is enhanchement for vue-tsc? I guess vite-plugin-dts support pathsToAliases and I guess that of this kind of issue.

The capabilities of vue-tsc are consistent with tsc. Because tsc does not support rewrite import path mapping, so vue-tsc does not support it, also. If you want to enhance this feature to vue-tsc, you should raise an issue for tsc.
I had a similar problem within my company. The suggestion I gave them was not to use path mapping in the library package.
We do have projects that rely heavily on path mappings. The solution for this kind of project is: use vue-tsc to generate .d.ts for the project, and then use rollup-plugin-dts to bundle all .d.ts into one file. rollup-plugin-dts will regard your tsconfigs's paths mapping (see demo).

Hi @xiaoxiangmoe Thanks for the recommendation, Does it work with other libs like type-fest because I'm getting with it:
[commonjs--resolver] Failed to resolve entry for package "type-fest". The package may have incorrect main/module/exports specified in its package.json.

Do you have any idea? Moreover, Do this plugin do the same?

I don't know 😭

No worries, I'll use relative imports. Thanks!


Published cmake-lint 1.4 on pypi

Hi
Great project. Any plans for that happen? Would be nice.
Thanks in Advance

Although the current is older
$ cmakelint --version
cmakelint <IP_ADDRESS>

release v1.4 does provides rather trivial than significant changes:
https://github.com/richq/cmake-lint/compare/v1.4...master
Is that the reason why there is no PyPi for v1.4?

I published 1.4. I see no reason why not. master branch could also be published with some more patches, but I need git permissions first.


nsfs: noobaa UI is not showing data written on buckets

when we write anything under nsfs in any bucket , UI is showing 0 bytes data under  'Data Written on Buckets'  It always shows:
Data Written on Buckets   0 bytes

Moved issue to noobaa-core

Currently we are not collecting R/W amount per NS buckets, its an open task.
You can see the collected data per NS bucket when you go into such a bucket
example

Hi @nimrod-becker , This UI has been very useful for debugging and getting a good view of the system. The Grafana gives a bigger picture but not details like No. of namespace buckets, No. of objects in bucket etc.
Is there a way to get it integrated with ODF UI  or else, if there is a way to see that in current view itself. Thanks.

@akmithal @nimrod-becker
We actually do report on num_namespace_buckets metric,
Should we keep this defect for collecting and reporting R/W amount per NS buckets / No. of objects in bucket
or do we have another Github issue that tracks it?

We are actually in the process of deprecating and removing the noobaa UI

Understood. We can close this defect then. @nimrod-becker , please do so( I don't have permission to close it)

#6948

Closing :)


bazel_skylib version problem

Hello, I've met a problem while intergrating the new mypy-intergration. The problem might be that I have relied on many rules package like
rules_bison rules_cc rules_flex rules_foreign_cc rules_foreign_cc_bazel_version rules_java rules_m4 rules_proto
rules_python and etc

The error was
'struct' value has no field or method 'to_list'
Available attributes: difference, disjoint, intersection, is_equal, is_subset, union

I think it's the problem with bazel_skylib version conflits. While in mypy, we use version 1.0.2. It might have been used a lower version in the other packages. But in mypy, we have
def repositories():
    excludes = native.existing_rules().keys()

    rules_python_version = "0.1.0"

    if "bazel_skylib" not in excludes:
        http_archive(
            name = "bazel_skylib",
            urls = [
                "https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/1.0.2/bazel-skylib-1.0.2.tar.gz",
                "https://github.com/bazelbuild/bazel-skylib/releases/download/1.0.2/bazel-skylib-1.0.2.tar.gz",
            ],
            sha256 = "97e70364e9249702246c0e9444bccdc4b847bed1eb03c5a3ece4f83dfe6abc44",
        )

If bazel_skylib is already installed with a old version by the other packages, the new version 1.0.2 will not be installed. This will cause the problem I met. So, how could I do with this problem. Thanks you so much !

I found a solution:
        http_archive(
            name = "bazel_skylib",
            urls = [
                "https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/1.0.2/bazel-skylib-1.0.2.tar.gz",
                "https://github.com/bazelbuild/bazel-skylib/releases/download/1.0.2/bazel-skylib-1.0.2.tar.gz",
            ],
            sha256 = "97e70364e9249702246c0e9444bccdc4b847bed1eb03c5a3ece4f83dfe6abc44",

Put this at the beginning of the project workspace can solve this problem, although it seems not a very good idea. But at least it works....

👋  @WeiYunKolmostar I don't think is a problem with the integration; this is a problem with Bazel's repository rules generally. The integration relies on a minimum version of Skylib and if some other dependency pulls in an earlier version there's no good way in Bazel for the integration to communicate that it doesn't support that version.


feat: merge wait-for into the main library

About
This pull request merges the wait-for ext into the main library
The ext will be depreciated once the pr is merged
Checklist

[x] The pre-commit code linter has been run over all edited files to ensure the code is linted.
[x] I've ensured the change(s) work on 3.8.6 and higher.

I've made this pull request: (check all that apply)

[ ] For the documentation
[x] To add a new feature
[ ] As a general enhancement
[ ] As a refactor of the library/the library's code
[ ] To fix an existing bug
[ ] To resolve #ISSUENUMBER

This is:

[ ] A breaking change

@EdVraz Due to the inconsistency of the length of the return values, along with the difficulty of conveying that to the user, I've changed wait_for_modal to return a tuple of the context with a list of the field values


add frontier-pos-template

Project Abstract
This is a development template based on Polkadot's NPOS consensus, compatible with EVM.
It aims to enable new developers or teams in the Polkadot ecosystem to quickly create EVM-compatible chains based on NPOS consensus.
reopen https://github.com/w3f/Grants-Program/pull/2342
Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
[x] I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

I have read and hereby sign the Contributor License Agreement.

I have read and hereby sign the Contributor License Agreement.

Thanks for the application @weimeme and I'm happy to see that you have identified a common pain point for developers. My question is, how do you plan to fund & maintain this project after this grant? What are your plans for gaining traction with devs and marketing this product in a way that it can gain some real adoption?

Thanks @weimeme we also now pay all of our grants partly in vested DOT. This DOT is vested linearly on-chain for two years. If you are okay with this can you please include a DOT % line, indicating the amount of vested DOT you you are willing to receive? See https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md?plain=1#L127

Thanks @keeganquigley, I have updated it.

Hey @weimeme , thanks for the update. I'll share the application with the committee.

Hey @weimeme , thanks for the update. I'll share the application with the committee.

Thank you very much @PieWol . Our two cooperating teams are also about to launch their mainnet and testnet. Hope it helps more teams.

recheck

recheck

Thanks for the application, @weimeme. Happy to support it. While we wait for further reviews, could you fill out the KYB form (assuming you are applying as a company, otherwise please use this form)?

Thanks for the application, @weimeme. Happy to support it. While we wait for further reviews, could you fill out the KYB form (assuming you are applying as a company, otherwise please use this form)?

Thanks @semuelle  , I have done the identity verification.

Hey @weimeme ,
I'm hopeful that you will keep maintaining the template with good documentation so that this will be a benefit to lots of teams trying to build on Substrate. I hope whatever projects are to launch with this template will still try to participate in the Polkadot ecosystem and not exist in complete isolation. I approve it as well. Once KYB has passed we can officially accept and merge your application. Thanks.

Hey @weimeme , I'm hopeful that you will keep maintaining the template with good documentation so that this will be a benefit to lots of teams trying to build on Substrate. I hope whatever projects are to launch with this template will still try to participate in the Polkadot ecosystem and not exist in complete isolation. I approve it as well. Once KYB has passed we can officially accept and merge your application. Thanks.

Yes, this solo chain is just an option for early teams to create projects. Many teams hope to build their own business on this  and build a parachain after reaching a certain number of users and funds. This coexistence mode is very useful.


Flash jitter config

Jittering for Flash dldTime does not work with the normal settings correctly. The reason I believe could be that due to the 4-quadrant DLD, consequative entries in each quadrant are separated by 4 integers, and thus would need jitter amplitude=2.

@steinnymir The code you put into the 8s_... delay stuff solves this issue I think, however only if we apply the delay on the level of bins, rather than ns, and leave the conversion to ns to the energy calibration function. I would propose to put the 8s... coversion actually into the flash loader, and always execute it if configured in the loader (is there a flag in the files we can use to detect if we have such a detector?) because the dldTime without the conversion does not make any sense anyways.

For the time being we are collecting methods in the SedProcessor. When things are working we can see if they live better in the loader as you suggested.
I will move everything to the right place before the PR

oh and this will require a "jitter amp" parameter to be passed in the config, so that the tof_channel of hextof can be jittered correctly, properly solving this issue

oh and this will require a "jitter amp" parameter to be passed in the config, so that the tof_channel of hextof can be jittered correctly, properly solving this issue

Well, my point is that if you jitter after sorting out the channels, and correcting on the level of bins, and before converting into ns, you can still jitter half a bin...

Then it's consistent with the other loaders

no, the half bin still doesn't work. The dldTime channel is in units of steps, but the real digial signal there is 8 times bigger, as the first 3 bits are overwritten to encode the sector ID. Therefore, with the channel correcly in steps, the jitter needs amplitude of 4 steps not .5

alternatively, these conversions can be done including one which changes the step size to be 8 times larger, and changing the step_to_nanosecond parameter value

No, I thought I needed to, but I don't in the later version, for similarity to how this was done previously. I might revert this though

in #169 the dldTimeSteps column is now in units of 1 step. Jittering works as in all other channels, with no requirement for an amplitude parameter passed.


Convert finishModules hook to be an AsyncSeries

Change finishModules hook to be AsyncSeries.
Resolves #2924

Thanks!


centered update

the centered_update option inhered from LDASsa  no longer works.
the option should be managed  by assim alarm  in ldas_assim GC.

@gmao-rreichle  the PR #392  address this issue


Sufficiently Large models in Scene Composer will get rendered outside the visible range of the Viewer, resulting in a confusing customer experience

Describe the bug
When you load a large size model in the Scene Viewer, the default camera logic can zoom so far out that the model itself is rendered outside the visible range of the viewer, resulting in it seeming not to have been rendered at all.
To Reproduce
Steps to reproduce the behavior:

Create a scene in TwinMaker with a very large (geometrically, not necessarily complexity) model
Open the Scene Viewer in Grafana or AppKit

Expected behavior
A clear and concise description of what you expected to happen.

Model should download and be rendered visually with the default camera position

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

This issue is fixed by updating the Unit of Measure = millimeters on the Scene Composer for my particular case.

We've figured out that the issue was the "Unit" of the model file (or TwinMaker's default choice of "defaulting to meters" for 3D rendering). After setting it to "millimeters", it started rendering as expected. I was able to replicate the same "full gray" rendering by setting it to "meters". So if you're facing the similar; try other options of the "Unit of Measure" .
In meantime, TwinMaker Scene Composer (or viewer / AppKit) should be somehow guiding to avoid this confusion.


Extend Storage Abstraction and Rework Configuration Loading

 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.2 out of 3 committers have signed the CLA.:white_check_mark: dzahariev:white_check_mark: dpanayotov:x: Kiril KabakchievKiril Kabakchiev seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Pull Request Test Coverage Report for Build 89

84 of 646 (13.0%) changed or added relevant lines in 11 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-18.4%) to 15.274%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

rest/interfaces.go
0
4
0.0%

storage/postgres/storage.go
3
19
15.79%

storage/postgres/broker.go
0
21
0.0%

main.go
0
37
0.0%

server/config.go
0
39
0.0%

server/server.go
0
55
0.0%

env/env.go
0
62
0.0%

storage/storagefakes/fake_storage.go
48
133
36.09%

storage/storagefakes/fake_broker.go
0
243
0.0%

Files with Coverage Reduction
New Missed Lines
%

server/server.go
1
0.0%

server/config.go
1
0.0%

Totals

Change from base Build 28:
-18.4%

Covered Lines:
106

Relevant Lines:
694

💛  - Coveralls


Ability to recover NFT Plot rewards in the machinaris container itself or automatically.

Describe the request
Ability to recover NFT Plot rewards in the machinaris container itself or automatically.
On "All the Blocks" there is the recovery tool for recovering Plot rewards on NFT plots. I would love to have the abillity to do this in the machinaris container itself. The Flora devs are providing this tool here (which All the Blocks is also using):
https://github.com/Flora-Network/flora-dev-cli
To use the tool one must provide the Launcher ID and the pool contract address in a preloaded config.
I hoped that it would be possible to integrate or run along with the Machinaris main container since it needs python and git as Prerequisites. Just to automate things. it even provides the ability to loop at custom timings.
I thought it could be implemented with a button or just the ability to enable it in the machinaris config.
configs in the tool look like this and can be used for every fork that uses NFT chia plots (k32+)
# Set env var to blockchain path.
export FD_CLI_BC_DB_PATH=$HOME/.flora/mainnet/db/blockchain_v1_mainnet.sqlite

# Set env var to wallet path.
# This must be the wallet that is associated with mnemonic from which NFT plot was created. (Usually your hot wallet)
# Replace <fingerprint> with your wallet fingerprint found at below path or by using "chia wallet show"
export FD_CLI_WT_DB_PATH=$HOME/.flora/mainnet/wallet/db/blockchain_wallet_v1_mainnet_<fingerprint>.sqlite

# Set env var to launcher id of NFT plot. Replace the below ID with output of "Launcher ID:"
# Launcher ID: can be obtained using "chia plotnft show"
# Execute above command in Chia, as those values are the original NFT contract details, which do not exist in the forks
export LAUNCHER_HASH=aaa0cbae497933a6c029a3819759fe148829dfde0316cb0512ccad23edce6aaa

# Set env var to pool_contract_address.
# Pool contract address: can be obtained using "chia plotnft show"
# Execute above command in Chia, as those values are the original NFT contract details, which do not exist in the forks
export POOL_CONTRACT_ADDRESS=xch13rht0xz4tpdqfq08e3dk20kewg9cjj3pw0wwjf7vay8whlxn7ppqapeqhz

fd-cli nft-recover \
  -l "$LAUNCHER_HASH" \
  -p "$POOL_CONTRACT_ADDRESS" \
  -nh <IP_ADDRESS> \
  -np 18755 \
  -ct $HOME/.flora/mainnet/config/ssl/full_node/private_full_node.crt \
  -ck $HOME/.flora/mainnet/config/ssl/full_node/private_full_node.key

# All coins that were mined +7 days ago WITH NFT PLOT should be spendable soon via wallet.

The examples of Recovering coins on Flora blockchain:
One time recovery of coins in Flora blockchain:
./flora_recovery.ps1 -POOL_CONTRACT_ADDRESS [your_pool_contract_address] -LAUNCHER_HASH [your_launcher_id]
One time recovery of coins in Flora blockchain when multiple wallet are available:
./flora_recovery.ps1 -POOL_CONTRACT_ADDRESS [your_pool_contract_address] -LAUNCHER_HASH [your_launcher_id] -fingerprint [wallet_fingerprint]
One time recovery of coins in Flora and Silicoin blockchains:
./flora_recovery.ps1 -POOL_CONTRACT_ADDRESS [your_pool_contract_address] -LAUNCHER_HASH [your_launcher_id] -blockchains flora, silicoin
Recovery of coins in Flora and Silicoin blockchains in a loop, executing the recovery every 24 hours:
./flora_recovery.ps1 -POOL_CONTRACT_ADDRESS [your_pool_contract_address] -LAUNCHER_HASH [your_launcher_id] -blockchains flora, silicoin -sleep 24

Should be available in v0.6.2 now.  Log output to /root/.chia/machinaris/logs/fd-cli.log daily, in each container executing it (not Chia and not Chives).

I get this error in my log on HDD coin.
An error occurred while sending the recovery transaction.
Traceback (most recent call last):
  File "/usr/local/bin/fd-cli", line 33, in <module>
    sys.exit(load_entry_point('fd-cli', 'console_scripts', 'fd-cli')())
  File "/fd-cli/fd_cli/fd_cli.py", line 220, in main
    fd_cli()
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/fd-cli/fd_cli/fd_cli.py", line 193, in fd_cli_nft_recover
    fd_cli_cmd_nft_recover(
  File "/fd-cli/fd_cli/fd_cli_cmd_nft_recover.py", line 211, in fd_cli_cmd_nft_recover
    fd_cli_print_raw(exception, pre=pre)
  File "/fd-cli/fd_cli/fd_cli_print.py", line 15, in fd_cli_print_raw
    print(f'{" " * pre * 4}{value:{fill}s}')
TypeError: unsupported format string passed to HTTPError.__format__

Re-opening as another Unraid user reported a similar error from the script.  Seems to be tied to the inputs to the script, however I haven't been able to replicate this myself.

is it possible to try and stike the pool address part in the next update? i have a feeling that is the issue.

or is there a way to edit this myself?

Finally got a chance to try the command without the -p pool_contract_address:

Here's a redacted version of what I tried:
export FD_CLI_BC_DB_PATH=/root/.hddcoin/mainnet/db/blockchain_v1_mainnet.sqlite
export FD_CLI_WT_DB_PATH=/root/.hddcoin/mainnet/wallet/db/blockchain_wallet_v1_mainnet_123456789.sqlite
/usr/local/bin/fd-cli nft-recover -l REDACTED -nh <IP_ADDRESS> -np 28559 -ct /root/.hddcoin/mainnet/config/ssl/full_node/private_full_node.crt -ck /root/.hddcoin/mainnet/config/ssl/full_node/private_full_node.key

Spoke to Guy on Discord. Currently the farmer node rpc port is being passed and I believe it needs to be the full node port.  He said he would push the full node ports in the next updates to the containers.

it seems to be the RPC port that you need to have it wired into - for flora that is 18755

Hi all, this hasn't fallen off my radar.  Still working to fix a dumb-typo I allowed to slide thru in v0.6.3.  Corrected in latest :develop stream (pre v0.6.4).  Right now I am monitoring all my fork full-nodes, watching the fd-cli.log, hourly as I've sped it up from daily for testing purposes.

This fix has now been released as v0.6.4.  Let me know if the problem recurs in this latest release and I'll re-open the issue.  Thanks again for the report.


fix opacity for some backgrounds

hey some fix for https://github.com/JrSchmidtt/lunar-vscode-theme/issues/1

@JrSchmidtt, hey can u please check ?

🚀🚀🚀


logging

Thanks for your great work. Would you support Logger Objects in the future?

Right now there's the logx.msg() functionality, which is logging to logfile. Maybe you were looking for more functionality than that?

Say, I set the logging as follows:
import logging

logging.basicConfig(level=logging.INFO,
        format='%(asctime)s %(levelname)s %(threadName)-10s %(message)')
logging.info('This will get logged')

Could I configure runx so that it formats the log information in a same fashion?
Thanks!

I see, right, I chose to keep the logging very basic, without using the logging package, to keep the implementation minimal. It would probably not be terribly difficult to change to use the logging package, so i'll make a note of this, but not sure when i can get to it.

I see, right, I chose to keep the logging very basic, without using the logging package, to keep the implementation minimal. It would probably not be terribly difficult to change to use the logging package, so i'll make a note of this, but not sure when i can get to it.

Thanks!


Remove obsolete methods from DriverJDBCVersion

If I understand correctly the current codebase supports jdbc 4.1 and jdbc 4.2 specs. This means that there is no need to check if the driver supports jdbc 4.1 and lower since 4.1 is the earliest jdbc version implemented by the driver. Therefore I believe that the methods in DriverJDBCVersion:
checkSupportsJDBC4
and
checkSupportsJDBC41
are obsolete and can safely be removed. There are just under 200 references in the code for the two methods and removing them would make the code much cleaner. The methods are no-ops and are probably removed by the compiler anyway.

As #187 has been merged I believe this can be closed.


[WIP/SPIKE] Tour wiring

closes #5169, refs #5168

heavily WIP, working on getting the html/css working first
likely going to use ember-wormhole for the rendering

TODO:

[x] finish converting old Sass code to CSS
[x] get the demo working correctly (harcoded html/css)
[x] build out tour component
[ ] build out wiring system
[ ] As always, tests
[ ] :tada:

likely going to use ember-wormhole for the rendering

Now that the modals refactor PR is merged we already have liquid-tether included which takes the concepts of ember-wormhole and ties them into liquidfire so that we have a central place to manage the animations.

Ah okay. ember-wormhole was the first thing that came to mind, but I'll have a look-see at what liquid-tether can do and use that instead :smile:

So for the moment this is working as a component with hardcoded content. I will work on finishing up the dynamic tour wiring over the next couple of days but would appreciate some input on the CSS side of things just to make sure I copied everything over correctly.
cc @JohnONolan @kevinansfield

It looks totally fine as far as I can see :+1:

Closing in favor of TryGhost/Ghost-Admin#20


Weird formatting in code summaries

Description
Code summaries that UTBot generates contain some weird whitespaces and tabs (\r\n...).
To Reproduce
Generate tests for any method.
Expected behavior
Pretty-formatted code summaries.
Actual behavior
Lots of \r\n inside the summaries.
Environment
Java 11

Currently, we surround our summaries with the <pre> tag and it leads to some shifts in the rendered docs.
This tag is supposed to surround multiline code snippets, but we surround the whole summary with it including text.
I suggest to get rid of <pre> in our summaries to make to make them nice.


Looking for a replacement method to encode/decode the ( phrase || privateKey ) <> keystore

Thinking about the keystore file format compatible to ethereum's system, however is not so efficiency. But it still worth finding a replacement to the format.
In dart, to implement the keystore encode/decode, one has to combine the scrypt and pbkdf2 to it. The easiest way to complete the job is to borrow the code from web3dart or laksadart I previously built for Zilliqa. However the encoding speed is too slow because of scrypt algorithm is slow.
Another option is to use FFI from other native library like ethsign , it is fast and run smoothly when I tried to bind it to the dynamic library. However, in rust  we generally use serde_json to encode the Crypto object,  the serde_json will be binded too, which will largely increase the bundle's size.
I don't have enough time to do enough search to finish the task. So if you have idea or solution, please comment or reply.

A replacement standard or format for keystore.
A fast and efficient way to encode/decode using FFI or pure dart code.
Any other good ideas

Close due to b446ebb49eb84bf7e32d821d67d18d64b11fc21c


Need a learn more button on Manage Keys screen

Asn to give text.

Learn More:
All your keys would be visible in this section. You can ensure their accessibility via Health Checks, fund Canary Wallets, view fingerprints and even change signer type, all from this central location for keys.

Here is the Learn more Modal for keys. (Its placed next to Manage Keys Flow section in file)
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=2120-4527&t=novBcNs2Vw4LhIp5-1

For New Manage Key Icons please refer to - #5100

Can't see in latest app

The code has been merged, most probably it did not go in the build.
It will be reflected in new build, marking it fixed.

Completed


Connection Getting Closed

After successfully establishing a connection using the EventFlux package, the connection gets unexpectedly disconnecting when new SSE event arrives.
Environment:

SSE package version: 1.6.7+1
Operating System: Android
Flutter version: 3.19.4

Additional Details:

Relevant code snippets or configurations
void _connect() {
_eventFlux.connect(
EventFluxConnectionType.get,
AppConst.API_BASE_URL + ApiEndPoints.SSE,
autoReconnect: true,
onConnectionClose: () {
logger.e("[SSE] Connection closed");
},
onError: (final EventFluxException p0) {
logger.e("[SSE] error\n\np0");
},
onSuccessCallback: (final EventFluxResponse? response) {
if (response != null && response.stream != null) {
st = response.stream!.listen((final EventFluxData event) {
logger.i("EVENT: ${event.event}\n\nData: ${event.data}");
});
}
logger.i(
"[SSE]\n\nStatus: ${response?.status}\n\nErrorMsg: ${response?.errorMessage}\n\n",
);
},
);
}

Haha. No worries. If you face any issues with my package in the future, please do open an issue.

Sorry! My bad. Its a server issue for us.

Hi @Vinayak006, I'm running into a similar issue. What was the server issue you ran into?


obout some json files

Hi, thanks for the excellent work. I would like to know how to generate these json file refcoco+_train.json, refcoco+_val.json, refcoco+_train.json, refcoco+_test.json in data.tar.gz. How to get those json files for refcoco and Refcocog datasets?

Hi, they are generated from the original refcoco+ annotation, by converting the bounding boxes into patch masks.

Thank you for your reply, dose original refcoco+ annotation mean instances. json and refs(unc).p? Are these json files or any conversion scripts available?

Here is the code snippet for the conversion. I used the official refer API to load the original annotation.
import torch
import os
import json
from refer import REFER
import numpy as np

data_root = './data'  # contains refclef, refcoco, refcoco+, refcocog and images
dataset = 'refcoco+'
splitBy = 'unc'
refer = REFER(data_root, dataset, splitBy)

split = 'test'
ref_ids = refer.getRefIds(split=split)

annotations = []

dim_w, dim_h = 384, 384
patch_size = 32
n_patch_w, n_patch_h = dim_w//patch_size, dim_h//patch_size

refer.getRefIds()
for ref_id in ref_ids:

    ref = refer.Refs[ref_id]
    image = refer.Imgs[ref['image_id']]

    width, height = image['width'], image['height']
    w_step = width/n_patch_w
    h_step = height/n_patch_h
    patch_area = height*width/(n_patch_w*n_patch_h)

    mask = refer.getMask(ref)['mask']

    patch = []
    for i in range(n_patch_h):
        for j in range(n_patch_w):
            y0 = max(0,round(i*h_step))
            y1 = min(height, round((i+1)*h_step))
            x0 = max(0,round(j*w_step))
            x1 = min(width, round((j+1)*w_step))
            submask = mask[int(y0):int(y1),int(x0):int(x1)]
            patch.append(submask.sum()/patch_area)

    text = [sentence['sent'] for sentence in ref['sentences']]
    imgPath = os.path.join('/export/share/datasets/vision/coco/images/train2014', image['file_name'])
    annotation = {'image': imgPath, 'text':text, 'patch':patch, 'type':'ref', 'ref_id':ref['ref_id']}
    annotations.append(annotation)

for ann in annotations:
    ann['patch'] = [torch.Tensor(ann['patch']) for n in range(len(ann['text']))]

torch.save(annotations,'refcoco+_%s.pth'%split)

OK, thanks a lot!


FIX: map view generation

@xybrnet please can you verify this using Emily's test URL:
http://localhost:8000/data/map/?table=YOUTH_LABOUR_FORCE_OFFICIAL_AGE_GROUP_GENDER&geo_ids=ward-79800037,municipality-JHB,province-GT,country-ZA,ward|municipality-JHB&primary_geo_id=ward-79800037#column|unemployed%2Csumlev|ward
My databases aren't up to date.

@longhotsummer
Yep - seems to have fixed it.


Slowmo Powerup

Add in that new powerup allready! It's basically done in dev!

Added with screen shake in v1.2


Convergence issues encountered when using CMatch.

Currently, I can basically reproduce the results on the original data. Because I want to use the mmd and adv methods inside, I switched to a cross-accent dataset and set the vocabulary to 1000. However, it has never converged. Even if I adjust the learning rate very small, the loss is still high. After changing the vocabulary size to 30, the loss can converge but the word error rate is very high. So I replaced the encoder with wav2vec2 encoder pre-trained on 960 hours of librispeech. I connected it with a linear layer at the back to keep the same dimension as before, and everything else remained unchanged. But it still cannot converge. Even if I keep reducing the learning rate, the loss will not decrease. I would like to ask where should I start troubleshooting?

Can you adjust the tradeoff parameter of CMatch to better balance the MMD term?


generate:sw wizard Should ignore hidden directories when presenting folder to use as root

Library Affected:
workbox-cli
My test directory had two folders, app/ and .git/. It doesn't seem like any hidden folder would ever be the root of a site's content. If I'm right, then workbox-cli shouldn't offer hidden folders as an option.

Marking as P1. We'll need to verify this is indeed still the current behavior, but I agree that user expectation would probably not be to include hidden directories as a default.


How can I convert my simple json to netcdf format?

Thanks for sharing this repo,
I need to convert my json files to netcdf format.

I gave my json file as input to the code but the input file is about 26MB but the nc file is 330B !  So I think my json format is not compatible with the code, is it possible to change the code so that it would be compatible with this form of json?

Hi @spacelover1,
Have you given the json2netcdf-compact.py script a go? See the very final section of the README. Make sure dimensions are specified with the dimensions key and the variable names that use those dimensions are append with [dim]. Using the -v flag when running the script might help as it'll show you what variables are being parsed. Let me know how you get on.
FYI I'm going to get rid of the original json2netcdf.py script as the syntax is too verbose.
Cheers,
Sam

Hi Sam,
I don't know how to pass my input file to json2netcdf-compact.py.
 json2netcdf-compact.py: error: the following arguments are required: input, output.

This should do the trick:
json2netcdf-compact.py input_file.json output_file.nc

where input_file.json is your JSON file and output_file.nc is the new NetCDF file to create.
I'll get around to documenting it properly some day...

Ok so I could run json2netcdf-compact.py using your sample JSON file.
I'm not sure how to specify x_dim or y_dim for my case.
This is how my data looks like:

I'm not sure how you want your data to look in the NetCDF file as it's not really compatible with NetCDF in that format. If you want each of those objects in the list to be groups then they need names. This would work:
{
    "group1": {"userId": 111111, "productId": 1000000, "eventName": 4, "timestamp": 100000000},
    "group2": {"userId": 111111, "productId": 1000000, "eventName": 2, "timestamp": 100000000},
    "group3": {"userId": 111111, "productId": 1000000, "eventName": 4, "timestamp": 100000000},
    "group4": {"userId": 111111, "productId": 1000000, "eventName": 4, "timestamp": 100000000},
    "group5": {"userId": 111111, "productId": 1000000, "eventName": 4, "timestamp": 100000000}
}

This gives the following NetCDF file:
netcdf test {

group: group1 {
  variables:
        int64 userId ;
        int64 productId ;
        int64 eventName ;
        int64 timestamp ;
  data:

   userId = 111111 ;

   productId = 1000000 ;

   eventName = 4 ;

   timestamp = 100000000 ;
  } // group group1

group: group2 {
  variables:
        int64 userId ;
        int64 productId ;
        int64 eventName ;
        int64 timestamp ;
  data:

   userId = 111111 ;

   productId = 1000000 ;

   eventName = 2 ;

   timestamp = 100000000 ;
  } // group group2

group: group3 {
  variables:
        int64 userId ;
        int64 productId ;
        int64 eventName ;
        int64 timestamp ;
  data:

   userId = 111111 ;

   productId = 1000000 ;

   eventName = 4 ;

   timestamp = 100000000 ;
  } // group group3

group: group4 {
  variables:
        int64 userId ;
        int64 productId ;
        int64 eventName ;
        int64 timestamp ;
  data:

   userId = 111111 ;

   productId = 1000000 ;

   eventName = 4 ;

   timestamp = 100000000 ;
  } // group group4

group: group5 {
  variables:
        int64 userId ;
        int64 productId ;
        int64 eventName ;
        int64 timestamp ;
  data:

   userId = 111111 ;

   productId = 1000000 ;

   eventName = 4 ;

   timestamp = 100000000 ;
  } // group group5
}

If you want that list to be a variable with an array of compound data types then I'm afraid this library won't work as it doesn't deal with compound data types.

Thank you Sam for the complete explanation, actually I want to feed my data to DSSTNE engine and it needs data to be in NetCDF format, and my data is kinda similar to movielens dataset, as you can see here  they have changed CSV to NetCDF before using data.
So my question is that can I use this script of yours in this case?

I'm not familiar with DSSTNE so not sure I can answer, but having a quick look at the docs you linked to, I think it'd be easier for you to convert your JSON to CSV and then use the method they use for the movielens dataset, you're data looks closer to the movielens CSV format than it is to the NetCDF format (accordingly to this page, anyway).
This JSON to CSV converter looks like it'll work directly on the JSON you posted above, if you don't want to write a script: https://json-csv.com/.

Closing this as it's not an issue with the software itself.


log-backup: Using PD as metastore

What is changed and how it works?

Issue Number: Close https://github.com/tikv/tikv/issues/13867
What's Changed:
This PR implemented a PD based metastore, and make it the default for log backup.
I added a new trait MetaStorageClient to the package pd_client, which is the API set for interacting with a MetaStorage service.
This trait has been implemented for client::RpcClient, because MetaStorage is another service rather than the PD service, I reused the channel we have dialed to PD.
There are some MetaStorageClient wrappers for general purpose, AutoHeader for adding request headers, Checked for checking the response.

This also makes `etcd-client` and `tonic` optional requirements, you can enable them by `metastore-etcd`.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

Release note
None

Hi @nolouch please note that the current implementation is based on the GlobalConfig API and may be hugely changed in the future, perhaps you don't need to review this PR for now.

/test

@nolouch The PR is ready for review now.
also cc @BusyJay and @tabokie , please help to check the pd_client part (only implemented for v1 now, do I need to implement MetaStorageClient for v2 now?), thanks.

Maybe we can remove the GlobalConfig interface in another pr?

/merge


Improve dark colour themes like Monokai for colouration of tabs

When using the Monokai theme or many of the other dark themes, e.g. "Dark(Visual Studio)",  it is extremely confusing that all of the tabs are highlighted except for the active one.  This is especially problematic when only two files are opened.  In such circumstances, I find myself constantly clicking on the darker tab in order to switch the other file, but of course this does nothing because the dark tab is the current one.
What makes this all the more confusing is that the unselected tab colour is almost identical to the selected text highlight background colour.
Sane:
Sublime Text with Monokai and Flatland Dark theme, index.html is the selected file and is highlighted brighter.  Furthermore, the selected tab has a curved base which subtly overlaps the non-active tab and ties in with the horizontal bar of the same colour, further visually reinforcing which tab is currently active.

Not Sane:
VS Code with Monokai theme, with index.html on the left as the active tab.  It is "highlighted" by being darker than the other tabs.  The tabs are completely square and so other than the colour there is no visual cue as to which tab is active.  Note similarity between highlighted text and the colour of the inactive tab.

PR welcome if small.

the following in my user settings improves the situation
"workbench.colorTheme": "Monokai",
"workbench.colorCustomizations": {
    "[Monokai]": {
		"tab.inactiveBackground": "#2c2e27",
		"tab.inactiveForeground": "#ccccc7", // needs to be bright so it's readable when another editor group is focused
		"tab.activeBackground": "#494842",
                "tab.activeForeground": "#d3d1cc",
    }
},

The file defining the colours is here.  It does not define "inactive" tab colours, only active colours.  So it's possible at the time when the theme was authored the default inactive colour was darker and that some point later the default was changed, creating the problem.
I'm not sure if I want to try to make a PR myself,  because I'm not really set up for building and testing VSCode from sources and also as I mentioned the problem is present in more than one theme (a broader fix may be needed than just to Monokai).   I could fork VSCode and edit the one Monkai config file using the web interface and just submit PR without testing and hope for the best, but I imagine that sort of behaviour is frowned upon.

It's "highlighted" as being the same color as the editor, it looks better when there are multiple editors:

Inverting it as you suggest looks wrong imo:

@roblourens @misolori

This was very confusing choice of colors for me also. I really like this monokai-theme, so I solved it like this:   (commented colors are the originals)
"tab.inactiveBackground": "#272822", // "#414339"
"tab.activeBackground": "#414339",    // "#272822"
"tab.activeBorder": "#f5db19",

This has worked for me, and I didn't have to change the color scheme.

It's currently not possible to have a bottom-border on the inactive tabs, but no bottom border on the active tab.
Other possibilities include a top-border colour for the active tab, that way it can connect to the page on the bottom, and have a bright colour indicator, e.g. Notepad++ (to some extent)

I agree with @Tyriar, the inactive tabs looked grayed out and sort of "behind" the active tab/editor.

@Fraasi, yes the yellow underline definitely helps to underscore the active tab, I like that.
@Tyriar I disagree that having the tab the same colour as the editor is a good visual indicator that it is the current tab, especially when the inactive tabs are brighter and there is a solid separating line between the editor and the tabs.  Though I could start to agree with you if your first screenshot was changed to something like this (photoshopped hack)

@uglycoyote the shadow means that there's content to scroll above the top so it seems a little think it still makes sense to keep the shadow. You can see it without the shadow if you scroll to the top:

NB: you can remove the shadow that appears when scrolled by adding this to your settings:
workbench.colorCustomizations": {
    "scrollbar.shadow": "#0000"
}

We could try reducing the opacity of the inactive tabs (text + icons) so it's more obvious which tab is active:

@misolori, There's a comment on this line in the current Monokai theme json:
	"tab.inactiveForeground": "#ccccc7", // needs to be bright so it's readable when another editor group is focused
I'm imagining that it was originally darker, and someone added the comment when making it brighter to try to solve the readability problem.  I tend to agree with this person, that highlighting the inactive tabs to a brighter grey while simultaneously dimming the text makes for poor contrast, not to mention that it is a mixed message.
In the Explorer window and other left-docked windows,  a lighter shade of grey is used consistently to highlight the current item.  Having some consistency about what colour represents "selected"  seems more important than having colour-coordinating the selected tab with the editor background.
Looking at some other software, it seems other programs solve these issues by having some kind of a "header bar", and having the colour of the header bar and the selected tab be the same.
Chrome (incognito)

Sublime Monokai & Flatland Dark

Thus they have the "selected tab colour matches something below it" property that you desire without forcing the selected tab to be darker than the unselected ones, even though the editor (or main content window in the case of Chrome) is dark.

For the Monokai theme, the inactive tabs do appear too bright. I'd suggest reducing the background color from #414339  to #34352f.
Before

After

This pattern where the inactive tabs are grayed out works well with the rest of our dark themes:
One Dark Pro

Flatland Monokai

Absent (Rainglow)

@misolori I agree that does look better, I think we should probably concern other places like the status bar to use that color as well. Then #414339 can still be used primarily for selection?

I like that darker color for inactive tabs, but I would keep the same color other places like the status bar. I like the status bar brighter to contrast with the editor background. It's used for list.inactiveSelectionBackground, but that should also stay brighter so it stands out in the list.

Also, the breadcrumbs bar under the tabs kind of helps with the general tab discussion above...

We can try this out in Insiders, let me know if you have any feedback...

I think it'll be much better if the background color of the inactive tabs is the same as the tab gutter:

	"workbench.colorCustomizations": {
		"tab.inactiveBackground": "#1E1F1C",
		"tab.inactiveForeground": "#AAAAAA",
		"tab.activeForeground": "#FFFFFF",
	}


background image and background color is merged making it impossible to apply both

Describe the bug
When using custom gradients you may want to apply both a gradient as background-image and a background-color.
Currently tailwind-merge will remove "duplicate" properties based on their prefix even though they apply different styles.
To Reproduce
Having following custom gradient:
backgroundImage: {
  "my-gradient": "linear-gradient(0deg, var(--alpha-50, rgba(9, 9, 11, 0.50)) 0%, var(--alpha-50, rgba(9, 9, 11, 0.50)) 100%)"
}

Will generate a classname bg-my-gradient to apply the gradient.
// Im using cn helper from shadcn:
import { clsx, type ClassValue } from "clsx"
import { twMerge } from "tailwind-merge"

export function cn(...inputs: ClassValue[]) {
  return twMerge(clsx(inputs))
}

cn("bg-red bg-my-gradient"); // Returns bg-my-gradient, but should be bg-red bg-my-gradient

Environment

"tailwind-merge": "^2.5.4",
"clsx": "^2.1.1",

Additional context
As a workaround you can use media-query modifiers:
cn("sm:bg-red bg-my-gradient"); // Returns sm:bg-red bg-my-gradient

Hey @crtl! 👋 Thanks for your patience!
tailwind-merge doesn't have access to the tailwind.config.js file and you need to configure it separately so it knows about the bg-my-gradient class.
Here is an example on how to configure tailwind-merge: https://github.com/dcastil/tailwind-merge/blob/v2.5.4/docs/recipes.md#adding-custom-scale-from-tailwind-config-to-tailwind-merge-config.
And here is the documentation on how the tailwind-merge configuration works: https://github.com/dcastil/tailwind-merge/blob/v2.5.4/docs/configuration.md#usage-with-custom-tailwind-config.

(For myself)
Related: https://github.com/dcastil/tailwind-merge/discussions/489, https://github.com/dcastil/tailwind-merge/issues/469, https://github.com/dcastil/tailwind-merge/issues/447, https://github.com/dcastil/tailwind-merge/issues/368, https://github.com/dcastil/tailwind-merge/discussions/322, https://github.com/dcastil/tailwind-merge/issues/321, https://github.com/dcastil/tailwind-merge/discussions/315, https://github.com/dcastil/tailwind-merge/issues/302, https://github.com/dcastil/tailwind-merge/issues/276, https://github.com/dcastil/tailwind-merge/discussions/275, https://github.com/dcastil/tailwind-merge/issues/274, https://github.com/dcastil/tailwind-merge/issues/250, https://github.com/dcastil/tailwind-merge/issues/207

To make a note:
This issue basically because tailwind-merge can't visit tailwind config directly, so even if we have declare the new variable in the tailwind config, tailwind-merge can't understand what all these custom variables are. And by some reasons in the tailwind-merge these custom variables and original tailwind variables will always try to overwrite each other.
And the solution is above, to use the extendTailwindMerge to create the new extended merge functions.
For the shadcn/ui scenario, you can try this:
import { clsx, type ClassValue } from "clsx";
import { extendTailwindMerge } from "tailwind-merge";

const customTwMerge = extendTailwindMerge({
  extend: {
    classGroups: {
      // Add custom merging rules here
      "font-size": [
        "text-h1",
        "text-h2",
        "text-h3",
        // ... and so on
      ],
      "bg-color": [
        "bg-background",
        "bg-foreground",
        "bg-card",
      ],
      "text-color": [
        "text-background",
        "text-foreground",
        "text-card-foreground",
      ],
      "border-color": [
        "border-background",
        "border-foreground",
        "border-card",
      ],
      z: ["z-app-bar", "z-popup", "z-menu", "z-tooltip", "z-modal"],
    },
  },
});

export function cn(...inputs: ClassValue[]) {
  return customTwMerge(clsx(inputs));
}

It is a solution for me, and I am not sure if this will affect shadcn/ui because Copilot also send some shadcn/ui variable into it.

And by some reasons in the tailwind-merge these custom variables and original tailwind variables will always try to overwrite each other.

tailwind-merge by default treats classes that could be a color class as a color class, e.g. bg-whatever. I did this because colors are changed very often in the config and this allows you to set up custom colors without the need to configure that in tailwind-merge.
The downside of course is that all unknown classes starting with bg- will be interpreted as a color class and therefore removed if another background-color class comes after it.

And by some reasons in the tailwind-merge these custom variables and original tailwind variables will always try to overwrite each other.

tailwind-merge by default treats classes that could be a color class as a color class, e.g. bg-whatever. I did this because colors are changed very often in the config and this allows you to set up custom colors without the need to configure that in tailwind-merge.
The downside of course is that all unknown classes starting with bg- will be interpreted as a color class and therefore removed if another background-color class comes after it.

I understand and that is just a note. I think maybe it will be a better practice to build the custom tailwind variables first, and then use it to generate the tailwind config and extended tailwind-merge function. Sadly that's not the shadcn/ui's style ❤

This happened to me as well, but with the text-... class. I have custom classes for text-button-filled-label and text-button-md. One changes the button text color, and the other changes the font size, respectively. It merges the two and keeps only the last one. I can't use both together with tailwind-merge :(

@GuiSelair you can, you just need to configure tailwind-merge accordingly:
import { extendTailwindMerge } from 'tailwind-merge'

export const twMerge = extendTailwindMerge({
    extend: {
        classGroups: {
            'font-size': ['text-button-md']
        }
    }
})

You don't need to configure text-button-filled-label because tailwind-merge defaults to all unknown classes beginning with text- to be interpreted as a text color class.

It's works! Thanks you! 🥇


system/gcov: enhance gcov

Summary

supports generating device-side code coverage
adjust gcov configuration name
deal compile warming

Impact
Testing

[Experimental Bot, please feedback here]
This PR summary is missing crucial information to determine if it meets NuttX requirements.
Missing Information:

Specifics on the change:

What "device-side code coverage" means and how it's implemented.
How the "gcov configuration name" is adjusted and why.
What "compile warnings" are addressed and how.

  We need to understand:

What features are added/changed and how users are affected.
Build process changes, hardware/architecture implications.
Documentation needs, security considerations, compatibility impacts.

Testing Context:

What build hosts and target environments were used for verification?
The provided testing log sections are empty.  Actual logs are needed.

To meet NuttX requirements, the PR needs to:

Expand the Summary: Provide clear, concise explanations of each change.
Complete the Impact section: Address ALL bullet points with specifics.
Include Testing Details:  Specify environments and provide REAL testing logs demonstrating the changes' effects.

Still CI errors :\

Still CI errors :\

since it depends on https://github.com/apache/nuttx/pull/13965, let's merge both together.


Add run_key

Summary
Adds compatibility for https://github.com/PrefectHQ/orion/pull/2205
Relevant Issue(s)

Checklist

[ ] Summarized PR's changes in CHANGELOG.md

#18 finished


Data access restrictions modal has broken link to Data Access and Use Policy

Clicking the link to the Data Access and Use Policy in the data access restrictions modal routes to a Page Not Found page.
I encountered this error doing the follow:

Navigated to MAL-ED study and clicked the "Download" tab
Clicked the "Participant Repeated Measures" dataset in the "My Subset" section
Clicked the link to the Data Access and Use Policy in the modal that popped up

The link works now.


cobigen-cli shell wrappers fail to handle args with quote

Expected behavior
As a user, I want to use cobigen-cli in a way so that even arguments containing quotes are handled correctly.
Actual behavior
cobigen / cg separate arguments even with quoted spaces and such fail to identify files with space in path or filename.
Steps to reproduce (bug) / Use Case of feature request (enhancement)
$ ./cg g "openapi file.xml"
[ERROR] Your <inputFile> 'openapi' has not been found

Comments/Hints:
Use "$@" instead of $*. This forwards the correct quoting of arguments to other called programs. Hint: Use https://www.shellcheck.net/ to detect such issues.
Also you might replace the current check, if any argument is added, with a more often used code - even when the current check does not run into errors when quoted args are used.
Use either
if [ $# -eq 0 ] . . .
if [ -z "$1" ] . . .

Compare with #1044

Thanks for the feedback and the hints to solve it! We will solve it ASAP.

You have missed, that it is already the bash wrapper scripts that fails to handle the quoted file correctly.  I have not yet checked the java code changes - this may workaround the error from the wrapper. But this won't generate stable results, I'd say.
Please fix it by changing
java -javaagent:$SOFTWARE_PATH/cobigen-cli/class-loader-agent.jar -jar $SOFTWARE_PATH/cobigen-cli/cobigen.jar $*

into
java -javaagent:$SOFTWARE_PATH/cobigen-cli/class-loader-agent.jar -jar $SOFTWARE_PATH/cobigen-cli/cobigen.jar "$@"

See https://github.com/koalaman/shellcheck/wiki/SC2048 for an example. Or check the bash man page.

Fixed by #1051. Thx


Update LFI-gracefulsecurity-linux.txt

added a path which is used in retriving the password hash of the user

Thanks for the suggestion - is there a source to this?

Thanks for the suggestion - is there a source to this?

yes Hackthebox Topology machine

This is already present in Discovery/Web-Content/apache.txt.
If the attacker already has knowledge that there is a web server in the target machine, it might make more sense to make a manual wordlist appending the /var/www/dev/ prefix to every line in Discovery/Web-Content/common.txt, or any of the other web-content discovery wordlists.

@abhishekmorla Thanks for the suggestion - however I do feel this is the wrong file to add it.
As @ItsIgnacioPortal already said, its been added.
@ItsIgnacioPortal I do agree that would be a smart idea - fancy doing it? :D

@ItsIgnacioPortal I do agree that would be a smart idea - fancy doing it? :D

For the purpose of maintaining the wordlists, it's better to avoid making wordlists with duplicate content.

What is this ? D
Le dim. 31 mars 2024 à 21:50, Ignacio J. Perez Portal <
@.***> a écrit :

@ItsIgnacioPortal https://github.com/ItsIgnacioPortal I do agree that
would be a smart idea - fancy doing it? :D
For the purpose of maintaining the wordlists, it's better to avoid making
wordlists with duplicate content.
—
Reply to this email directly, view it on GitHub
https://github.com/danielmiessler/SecLists/pull/885#issuecomment-2028887925,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5MEH2IFQX7UXB2LES6JEPLY3BSJFAVCNFSM6AAAAAAZS6WUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYHA4DOOJSGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

in fact, the question I wanted to ask you is about a mining predictor
casino software could we have a solution on this software you can tell me
your price how much I paid you for Can you help me get this software?
Le dim. 31 mars 2024 à 22:17, Laci Sig @.***> a écrit :

What is this ? D
Le dim. 31 mars 2024 à 21:50, Ignacio J. Perez Portal <
@.***> a écrit :

@ItsIgnacioPortal https://github.com/ItsIgnacioPortal I do agree that
would be a smart idea - fancy doing it? :D
For the purpose of maintaining the wordlists, it's better to avoid making
wordlists with duplicate content.
—
Reply to this email directly, view it on GitHub
https://github.com/danielmiessler/SecLists/pull/885#issuecomment-2028887925,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5MEH2IFQX7UXB2LES6JEPLY3BSJFAVCNFSM6AAAAAAZS6WUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYHA4DOOJSGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>