workflow control

Hi, Paul
So I've figured out how to write a callback that can check the hidden storage for a given disclosure element and see how the callbacks to each disclosure element could be made to change the value of the hidden storage element in the next disclosure element in the workflow sequence. What I haven't been able to figure out is how to disable the expansion of an element that the user isn't ready to access. There seems to be no "disabled" property for these things and doing something like closing the off-limits elements when the user tries to open them seems awkward (and setting the "open" attribute via the callback doesn't seem to have any effect, anyhow, so maybe the callback passes the signal on to whatever toggles the element?).
The solution that I can think of would be to defer constructing the contents of the disclosure elements until they are ready to be used, something like what already happens with the tier mapping. I wanted to check with you though, before undertaking something like that. I seems to me it might be a major restructuring of the app.
David

maybe this will help?  I’ve used it often with buttons:
https://stackoverflow.com/questions/3710114/jquery-enabling-and-disabling-dom-elements-without-removing

On May 5, 2019, at 9:56 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
So I've figured out how to write a callback that can check the hidden storage for a given disclosure element and see how the callbacks to each disclosure element could be made to change the value of the hidden storage element in the next disclosure element in the workflow sequence. What I haven't been able to figure out is how to disable the expansion of an element that the user isn't ready to access. There seems to be no "disabled" property for these things and doing something like closing the off-limits elements when the user tries to open them seems awkward (and setting the "open" attribute via the callback doesn't seem to have any effect, anyhow, so maybe the callback passes the signal on to whatever toggles the element?).
The solution that I can think of would be to defer constructing the contents of the disclosure elements until they are ready to be used, something like what already happens with the tier mapping. I wanted to check with you though, before undertaking something like that. I seems to me it might be a major restructuring of the app.
David
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

sorry - I forgot Dash does not give easy means to run javascript in the client.
How about this?
https://community.plot.ly/t/how-to-disable-html-button/9859
https://community.plot.ly/t/disable-a-component/9437
https://github.com/plotly/dash-html-components/issues/32
Maybe that which works for button also works for the disclosure element?

On May 5, 2019, at 11:07 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
maybe this will help? I’ve used it often with buttons:
https://stackoverflow.com/questions/3710114/jquery-enabling-and-disabling-dom-elements-without-removing

On May 5, 2019, at 9:56 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
So I've figured out how to write a callback that can check the hidden storage for a given disclosure element and see how the callbacks to each disclosure element could be made to change the value of the hidden storage element in the next disclosure element in the workflow sequence. What I haven't been able to figure out is how to disable the expansion of an element that the user isn't ready to access. There seems to be no "disabled" property for these things and doing something like closing the off-limits elements when the user tries to open them seems awkward (and setting the "open" attribute via the callback doesn't seem to have any effect, anyhow, so maybe the callback passes the signal on to whatever toggles the element?).
The solution that I can think of would be to defer constructing the contents of the disclosure elements until they are ready to be used, something like what already happens with the tier mapping. I wanted to check with you though, before undertaking something like that. I seems to me it might be a major restructuring of the app.
David
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Unfortunately, the  property doesn’t apply to . I’ve managed to plug an eternal javascript into a baby Dash app, but I can’t seem to make it add an event listener to a details component, let alone change that component’s properties. As you say, there isn’t a easy way to run the javascript in the Dash app, other than when the window loads.
David

On May 5, 2019, at 12:16 PM, Paul Shannon<EMAIL_ADDRESS>wrote:
sorry - I forgot Dash does not give easy means to run javascript in the client.
How about this?
https://community.plot.ly/t/how-to-disable-html-button/9859
https://community.plot.ly/t/disable-a-component/9437
https://github.com/plotly/dash-html-components/issues/32
Maybe that which works for button also works for the disclosure element?

On May 5, 2019, at 11:07 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
maybe this will help? I’ve used it often with buttons:
https://stackoverflow.com/questions/3710114/jquery-enabling-and-disabling-dom-elements-without-removing

On May 5, 2019, at 9:56 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
So I've figured out how to write a callback that can check the hidden storage for a given disclosure element and see how the callbacks to each disclosure element could be made to change the value of the hidden storage element in the next disclosure element in the workflow sequence. What I haven't been able to figure out is how to disable the expansion of an element that the user isn't ready to access. There seems to be no "disabled" property for these things and doing something like closing the off-limits elements when the user tries to open them seems awkward (and setting the "open" attribute via the callback doesn't seem to have any effect, anyhow, so maybe the callback passes the signal on to whatever toggles the element?).
The solution that I can think of would be to defer constructing the contents of the disclosure elements until they are ready to be used, something like what already happens with the tier mapping. I wanted to check with you though, before undertaking something like that. I seems to me it might be a major restructuring of the app.
David
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/29#issuecomment-489450007, or mute the thread https://github.com/notifications/unsubscribe-auth/AKN4HBTR2KB2BKM237Y3Q6LPT4P6HANCNFSM4HK3V2LA.

I think maybe I’ll just work on enabling buttons in the correct sequence instead of messing around with the disclosures. Even if we figure it out, it’s a lot of head-banging-against-the-wall time for relatively little return.
David

On May 5, 2019, at 2:36 PM, David Beck<EMAIL_ADDRESS>wrote:
Unfortunately, the  property doesn’t apply to . I’ve managed to plug an eternal javascript into a baby Dash app, but I can’t seem to make it add an event listener to a details component, let alone change that component’s properties. As you say, there isn’t a easy way to run the javascript in the Dash app, other than when the window loads.
David

On May 5, 2019, at 12:16 PM, Paul Shannon<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
sorry - I forgot Dash does not give easy means to run javascript in the client.
How about this?
https://community.plot.ly/t/how-to-disable-html-button/9859 https://community.plot.ly/t/how-to-disable-html-button/9859
https://community.plot.ly/t/disable-a-component/9437 https://community.plot.ly/t/disable-a-component/9437
https://github.com/plotly/dash-html-components/issues/32 https://github.com/plotly/dash-html-components/issues/32
Maybe that which works for button also works for the disclosure element?

On May 5, 2019, at 11:07 AM, Paul Shannon<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
maybe this will help? I’ve used it often with buttons:
https://stackoverflow.com/questions/3710114/jquery-enabling-and-disabling-dom-elements-without-removing https://stackoverflow.com/questions/3710114/jquery-enabling-and-disabling-dom-elements-without-removing

On May 5, 2019, at 9:56 AM, David Beck<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi, Paul
So I've figured out how to write a callback that can check the hidden storage for a given disclosure element and see how the callbacks to each disclosure element could be made to change the value of the hidden storage element in the next disclosure element in the workflow sequence. What I haven't been able to figure out is how to disable the expansion of an element that the user isn't ready to access. There seems to be no "disabled" property for these things and doing something like closing the off-limits elements when the user tries to open them seems awkward (and setting the "open" attribute via the callback doesn't seem to have any effect, anyhow, so maybe the callback passes the signal on to whatever toggles the element?).
The solution that I can think of would be to defer constructing the contents of the disclosure elements until they are ready to be used, something like what already happens with the tier mapping. I wanted to check with you though, before undertaking something like that. I seems to me it might be a major restructuring of the app.
David
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/29#issuecomment-489450007, or mute the thread https://github.com/notifications/unsubscribe-auth/AKN4HBTR2KB2BKM237Y3Q6LPT4P6HANCNFSM4HK3V2LA.


InlineCompletionItemProvider gets triggered again when user hovers on first inline suggestion

Type: Bug
For an InlineCompletionProvider registered like so:
context.subscriptions.push(
    vscode.languages.registerInlineCompletionItemProvider(
      "python",
      new CustomInlineCompletionItemProvider()
    )
  );

The registered provider CustomInlineCompletionItemProvider.provideInlineCompletionItems() gets called when the user types with context.triggerKind set to InlineCompletionTriggerKind.Invoke as expected, and the returned suggestion gets displayed inline as gray text.
Now when the user moves their mouse over the gray text (say, to cycle through suggestions, or to click on "Accept"), the registered provider gets called again with context.triggerKind set to InlineCompletionTriggerKind.Automatic.
Expected behaviour:
I see a few ways this could be improved (unless this is intentional):

InlineCompletionProvider should not be triggered again when user hovers their mouse on the provided suggestion. It seems redundant and cyclic.
If it needs to be triggered, exiting early or not returning anything from the provider clears the previous inline suggestion. This should not be the case and the previous suggestion should be persisted until either a new suggestion is returned or explicitely removed by returning a special value like null.

If this behaviour is intentional, is there a recommended way to avoid triggering a new suggestion when the user hovers on the first suggestion?
VS Code version: Code 1.86.1 (Universal) (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:09:01.236Z)
OS version: Darwin arm64 23.3.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 2, 3

Memory (System)
32.00GB (0.03GB free)

Process Argv
--crash-reporter-id 129a6e8a-e1b6-4fc3-8071-8bea980b0dbc

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

tsl-problem-matcher
amo
0.6.2

vscode-eslint
dba
2.4.4

prettier-vscode
esb
10.1.0

extension-test-runner
ms-
0.0.6

gitblame
wad
10.9.0

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww2:30959801
8082a590:30971561
edj9j583:30969295
a89i1917:30961429
dsvsc020cf:30973509

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I am still facing this issue with the latest version (1.87.0) and with all plugins disabled.
https://github.com/microsoft/vscode/assets/47316575/ba971f59-c10e-46be-a82d-0df699ee4397

The registered provider CustomInlineCompletionItemProvider.provideInlineCompletionItems() gets called when the user types with context.triggerKind set to InlineCompletionTriggerKind.Invoke as expected, and the returned suggestion gets displayed inline as gray text.

Now when the user moves their mouse over the gray text (say, to cycle through suggestions, or to click on "Accept"), the registered provider gets called again with context.triggerKind set to InlineCompletionTriggerKind.Automatic.

Are you sure? It should be the other way around.
And yes, this is by design. Implementations should return a list of all suggestions on hover, so the user can cycle through them.
When the user types, only one suggestion is sufficient.

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

Are you sure? It should be the other way around.

My bad! As seen in the screen-recording, it gets called with TriggerKind=1 (automatic) when the user types, and then with TriggerKind=0 (invoke) when the user hovers on the suggestion.
Thank you for explaining the current behaviour!
However, my issue right now is that if the suggestions generated on hover are not the same as the suggestion generated when typing, it results in a poor user experience (they go to accept one suggestion, but it changes on hover). I believe this will be a more and more common usecase with AI-powered code completion, which can be quite fuzzy.
I understand why this is the default behaviour, but I believe there should be a way to disable it as well. Otherwise, is it the expectation from the extension to ensure the suggestions are deterministic?

You can just cache the result for a given position and text model version!

Thank you for the confirmation!


Add signal handling for graceful shutdown of the gRPC Collector, GethCollector and Executor (Being worked on in https://github.com/astriaorg/astria/pull/854)

Closing this issue since I accidently raised it from the task list. I do not to intend make individual issues as of now.


SDK errors

Current problems I see:

Lack way to handle errors per SDK (API exposing hasError etc.) so we need to define errors in multiple places/defefine them or have helper methods for creating proper message per type.

Errors type should be probably moved to the core and not defined for kafka specifically

SDK on its own defines all errors on root package. Maybe we should have kafkaerrors.ERROR_40 instead?

Current problems I see:
SDK on its own defines all errors on root package. Maybe we should have kafkaerrors.ERROR_40 instead?

I just have a question - can you explain further what the problem you see is?

There are 80 fields in the root of the SDK (from which 95% are errors constants)

Thanks that is clear!

It feels like this was overkill to handle only 3 errors from srs (as all kafka errors were handled already).
We should try to refactor error handling in the CLI but I see this as step process where we improve new and existing commands rather than doing this as whole.


More fine-grained support for picking the composer version

Describe the feature
Pin to a specific major.minor.patch version of composer, or major.minor. Composer 2.2.0 has some regressions, so I'd like to stick with the latest 2.1.x series version.
Version

[ ] I have checked releases, and the feature is missing in the latest patch version of v2.

Underlying issue

Describe alternatives

Additional context

Are you willing to submit a PR?

@GrahamCampbell
This is already supported.
https://github.com/shivammathur/setup-php#wrench-tools-support
You can specify the composer's exact semver version tools: composer:2.1.14 or major.minor version tools: composer:2.1.
If you use major.minor notation for the version, please specify COMPOSER_TOKEN environment variable using the GITHUB_TOKEN secret to avoid rate GitHub API rate limiting.
Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/1612081597/workflow

So it is! Thanks. ❤


NIFI-6187

Added checkbox task for building on JDK 8 and JDK 11.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Given the nature of the change I went ahead and merged to master before realizing you asked for a review from Jeff. Hope you don't mind ;)


CNV-41203: Change virtctl download links popover to a single link to CLI tools

📝 Description
This PR changes the virtctl download links popover to a link to the command-line-details page so that the user can download oc as well.
Jira: https://issues.redhat.com/browse/CNV-41203
🎥 Screenshots
Before

After

Linked page

/cherry-pick release-4.16


Adding a booking history page

By accessing this feature, the user can view his ticket booking history and compare and go through all the relevant information he needs from past bookings and apply them to the present bookings; or he can go through his previous bookings using this section.

@Bhumika79 Why a user need to have previous billing details?

The ticket will be printed, it can be too referred


Enhancement to Dimension and TensorShape API documentation

This PR is intended to help beginners understand the functionality of both Dimension and TensorShape API better by providing additional notes about each function and making it self-explanatory.

I signed it!

I signed it!

@SSaishruthi we did not see CLA , can you please make sure you use same username and email while signing CLA

CLA issue has been resolved.

Hi @rthadur,
Is this PR in review?
TIA

Hi @rthadur,
Is this PR in review?
TIA

yes, can you please resolve conflicts.

@rthadur
Resolved

Working on the changes.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

It has been 43 days that this pull-request has stalled. Please create a new pull-request with the requested changes.


Improve LaTeX support

Adds support for all (standard and amsmath) math environments.

latex-inline and latex-display are combined to latex since math environments can be started at any time.
The reason for latex now being included earlier is that it needs to precede escape since we match \[.

awesome! would you mind updating the readme to mention the features that have been added?

Sure! This should do it.

@jonschlinkert Why not merging?


Hidden Repeater with relationship don't work correctly

Package
filament/filament
Package Version
v3
Laravel Version
10
Livewire Version
3
PHP Version
8.2
Problem description
I have a form that has a Fieldset that has a repeater.
The repeater is a relationship.
In some cases, I don't want this fieldset to be shown, so I hide it.
Now, if the fieldset is hidden, when I try to save the form, it throws an error because it tries to save the repeater as it was not a relationship.
If I hide the repeater instead of the fieldset, the error remains.
Expected behavior
Saving a form should ALWAYS consider that any repeater that is set as relationship is not going to be saved as a field of the table but in another table, does not matter if it is hidden or not.
Steps to reproduce
a) Create a form with some Fieldsets and a Repeater with a relationship inside it.
b) Hide the repeater.
c) Try to edit something in the form and save it.
The form should save, but instead, it gives an error because it is trying to save the repeater as if it was a field in the table instead of being another table.
Reproduction repository (issue will be closed if this is not valid)
I don't have any repository.
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

WORKAROUND: I understand that you cannot work on the problem if I don't make the effort to prepare a testing environment, but I am not that fluent in laravel so I can prepare a testing environment that does not take me too much time, so we are in a deadlock.
Anyway, I found two workarounds to mitigate this problem, that happens to be a blocking one:
First solution... If the decision to hide has something to do with user roles or similar...
If you can decide if something is hidden or not when creating the form, you can simply don't add the thing to the schema...
Example with problem:
public static function form(Form $form): Form
{
$userIsSomething=auth()->user()->hasRole("something");
return $form->schema([
Fieldset::make('firstFieldset'),
Fieldset::make('secondFieldset')->schema([
Repeater::make('noFieldButRelationshipTable')
->relationship()
])
->hidden($userIsSomething),
Fieldset::make('fthirdFieldset'),
        ]);
}

The code above should work, and it does when the secondFieldSet is not hidden, but when it is hidden, then updating the record throws an error saying that UPDATE cannot find noFieldButRelationshipTable field in the table.
Now, the solution that I found is with a ternary operator + array_filter:
public static function form(Form $form): Form
{
$userIsSomething=auth()->user()->hasRole("something");
return $form->schema(array_filter([
Fieldset::make('firstFieldset'),
$userIsSomething?false:Fieldset::make('secondFieldset')->schema([
Repeater::make('noFieldButRelationshipTable')
->relationship()
])
Fieldset::make('fthirdFieldset'),
        ]));
}

In this case, so, I don't filter the fieldset, I directly don't show it.
Now, that does not work if the hidding decision has to do with the record status, as the record has not been set yet when we run the static function.
In this case, given that I cannot use hidden, I use extraParameters to hide the Fieldset. NOT GREAT, as someone could easily modify the DOM to show the hidden fieldset, but it works by now.
Example with problem:
public static function form(Form $form): Form
{
return $form->schema([
Fieldset::make('firstFieldset'),
Fieldset::make('secondFieldset')->schema([
Repeater::make('noFieldButRelationshipTable')
->relationship()
])
->hidden(fn ($record)=> $record->recordIsSomething==true),
Fieldset::make('fthirdFieldset'),
        ]);
}

Workaround:
public static function form(Form $form): Form
{
return $form->schema([
Fieldset::make('firstFieldset'),
Fieldset::make('secondFieldset')->schema([
Repeater::make('noFieldButRelationshipTable')
->relationship()
])
->extraAttributes(fn ($record)=> ($record->recordIsSomething==true)?['hideTheFieldSet']:[]),
Fieldset::make('fthirdFieldset'),
        ]);
}

And then, in custom.css
.hideTheFieldSet {
display:none;
}
Not pretty, but it is enough while the error in the vendor library is not solved (in some cases...)


java.math.BigDecimal is not supported

I deployed on the cloud dynamodb using the CloudFormation, and try to play with the basic property using gremlin> :> g.E().hasLabel("likes").property("weight", 0.4).
But got this error:
Property value [0.4] is of type class java.math.BigDecimal is not supported

Seems it is a Titan problem: https://groups.google.com/forum/#!topic/aureliusgraphs/BWSWd-pV9m4
By adding :> double a=0.4; g.E().hasLabel("likes").property("weight", a) solves the problem

@bobzsj87 you might want to try using the JanusGraph compatible version available here.


Glossary links to 'Concepts Overview' are dead

From the Glossary, clicking on 'Baggage' https://opentelemetry.io/docs/concepts/overview/#baggage returned my a 404. Upon inspection, it appears many links in the Glossary are pointing to https://opentelemetry.io/docs/concepts/overview/ and 404'ing.

Could you assign me this issue? I want to work on it

@austinlparker this issue can be closed. The linked PR resolves it


java version

any plan to add a java version of this library

Hey! Appreciate you asking. Nothing in the immediate future, but we're happy to explore if there's sufficient user interest.
If you think it'd be valuable to have a Java version of this library, could you file a feature request here and include any details about your specific use case? Others will be able to vote on the request and we'll be able to track interest and reach out as needed. Thank you!


Support for Backup for GCS Bucket Subdirectories

While creating backup in GKE cluster, we can currently handle a backup in GCS like
CREATE BACKUP STORE store_name
USING 'GoogleCloudBlobStore' WITH settings = {'bucket': 'google_bucket_name'};

The customer needs the ability to use Subdirectories for google_bucket_name like
backup/dev
backup/qa

Not the right place to report this issue. Will report the issue at DSE Server Side Backup and Restore

Not the right place to report this issue. Will report the issue at DSE Server Side Backup and Restore


Clipping Plane Issue

Overview
Since I've updated to Unity 2017.2.0f3 now my clipping plane has become extremely large.
Expected Behavior
I have set the  clipping plane near setting to 0.01 on the MixedRealityCamera and I want the hologram to clip just inches in front my my face.
Actual Behavior
I have set the  clipping plane near setting to 0.01 on the MixedRealityCamera however the hologram clips out 2-3 feet in front of me.
Steps to reproduce
Described above.
Unity Editor Version
Unity 2017.2.0f3
Mixed Reality Toolkit Release Version
HoloToolkit-Unity-v1.2017.2.0

Part of the problem is that you're using the wrong editor version for both Hololens and IMHD development

I do not really know what you mean.
If you mean the wrong versions of Unity and MRTK then what do you suggest I be using?

I swear you guys don't really read the release notes.

That helped!
What I did in the first place was based off of your suggestion...
What you'll need to install
Unity Editor 2017.2.0p1 MRTP4 or later - I will try again. This did not allow me to compile in VS so I had to change to Unity 2017.2.0f3
Running the Windows Fall Creator's Update Build 1709 or later - Done
Visual Studio 2017 build 15.3 or later - Currently build 15.4.4
Window 10 SDK 10.0.16299.0 or later - Done

Stephen,
Since I know that you are the most knowledgeable individual on the planet with regards to this. I took another stab at it and this is what happened.
After installing I still ended up with issues so I decided to uninstall Unity, VS, and run a cleaner to make sure that my registry was clean of any reference of each software. I then reinstalled the following based off of your release notes:
Unity Editor 2017.2.0p1 MRTP4 or later - 2017.2.0p1-MRTP4
Running the Windows Fall Creator's Update Build 1709 or later - Done
Visual Studio 2017 build 15.3 or later - Currently build 15.4.4
Window 10 SDK 10.0.16299.0 or later - Done
Download of the most up-to-date version of MRTK - https://github.com/Microsoft/MixedRealityToolkit-Unity
Issues: Although I am able to compile and run the hologram on my HoloLens the same issue is happening. Clipping is happening 2-3 feet from head.
Over 70 other warnings regarding cursor and animation.
One major issue I also had is that I lost the ability to connect to Universal Windows Platform after reinstalling Unity 2017.2.0p1-MRTP4. The reason this happen is that I used the "Unity Editor 64 bit" standalone installer instead of the UnityDownloadAssistant.exe. The DowloadAssistant.exe gives the option of installing the component while the standalone did not.
Please tell me what I am doing wrong? I would like to reduce this clipping plane to almost nil.
Thank you in advance!

Are you changing the clipping plane on the MixedRealityCamera object settings in the scene, or on the MixedRealityCameraManager script in the Inspector? The script will overwrite any settings set on the Game object itself.

That updated info really helped get us closer to understanding your problem.
Sorry if I came across as rude, but not acknowledging the correct editor build has been a real problem lately.  Knowing you've tried other builds does help us zero in on your issue though.

Do you have a sample project you're willing to share with us on github regarding this issue?
It'd be much easier to just see how you've got things setup to better understand what's happening.

Try resetting the camera prefab as well, making sure there are no changes to it saved in your scene.

Thank you for the replies!
Keveleigh - I am not making the changes on the manager script. Just on the MixedRealityCamera Clipping Plane Settings. I am setting it to 0.01.
Stephen - Your suggestion was correct as per usual! :) The issue that we have is when you add the Mixed Reality Camera Prefab through Mix Reality Toolkit>Apply Mixed Reality Scene Settings>Add the Mixed Reality Camera Prefab it does not add the HoloLensCamera component of the Prefab. When I manually reset/added the camera prefab the additional camera component showed up with a clipping plane of 0.85. Once I changed that to 0.01 I was good to go.
I hope I described the issue well here? Thanks again for your help!
Now off to my other main issue... Anchoring!

Wait, I'm not sure that's the right thing to do. You now have both the MixedRealityCameraParent prefab and the HoloLensCamera prefab in your scene? You likely only want one.
If you just use the HoloLensCamera, then yeah, you can change the clipping plane directly on the GameObject.
If you just use the MixedRealityCameraParent, then you'll want to change the clipping plane in the Inspector on the MixedRealityCameraManager component, NOT the script itself and NOT the camera's clipping plane. That'll solve your original issue using the prefab you had before.

@keveleigh it goes back to the MRCP editor not serializing properly. See #1258

@stephenhodgson Wasn't that fixed?
Also, I disagree because @tspaddock stated:

I am not making the changes on the manager script. Just on the MixedRealityCamera Clipping Plane Settings

Which sounds like it has nothing to do with an issue in the script, just setting the clipping plane in the wrong place. Any change on the camera will be overwritten by the script on launch.

It was fixed, but not in the the release he said he was using (v1.2017.2.0)

Ahh yes, that's true.

@StephenHodgson
I'm using unity editor 2017.4.1f1 and MixedRealityToolkit-Unity version 2<IP_ADDRESS>, the MixedRealityCamera still has the same issue. But HoloLensCamera works very well.
In my scenario, I hope user can see the very near hologram, which even near 20cm in front of theirs face.
thanks,

@zhangalex You need to set the clipping plane on the MixedRealityCameraManager script in the Inspector. The script will overwrite any settings set on the GameObject itself.
This script will be visible in the Inspector when you select the MixedRealityCamera GameObject. The Transparent settings there are the ones being set on HoloLens.

@keveleigh
Thanks.

Be careful setting the clipping plane that close… Rendering holograms there will make most people somewhat uncomfortable because of accommodation/vergence conflict.
From: Alex Zhang<EMAIL_ADDRESS>Sent: Wednesday, June 27, 2018 3:38 AM
To: Microsoft/MixedRealityToolkit-Unity<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Clipping Plane Issue (#1406)
@StephenHodgsonhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FStephenHodgson&data=02|01|cwhite%40exchange.microsoft.com|523ef45654464769d2a508d5dc1a1653|72f988bf86f141af91ab2d7cd011db47|1|0|636656926961990807&sdata=%2BwhFX3N2JoP1F1XrcqQfQLh7URG6biCfe83t9j2DgHY%3D&reserved=0
I'm using unity editor 2017.4.1f1 and MixedRealityToolkit-Unity version 2<IP_ADDRESS>, the MixedRealityCamera still has the same issue. But HoloLensCamera works very well.
In my scenario, I hope user can see the very near hologram, which even near 20cm in front of theirs face.
thanks,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FMixedRealityToolkit-Unity%2Fissues%2F1406%23issuecomment-400626974&data=02|01|cwhite%40exchange.microsoft.com|523ef45654464769d2a508d5dc1a1653|72f988bf86f141af91ab2d7cd011db47|1|0|636656926961990807&sdata=%2BtlIyOAyFHVN%2Fd3iLt%2FucVl4DVc8cZgC2JIiD6ber84%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIo6gG4u4JyRZhgyoRvTY2pYs3y6RatPks5uA2CWgaJpZM4QkrKq&data=02|01|cwhite%40exchange.microsoft.com|523ef45654464769d2a508d5dc1a1653|72f988bf86f141af91ab2d7cd011db47|1|0|636656926962000816&sdata=cK1vCs%2BuwNjhSPkiSmAbX1GWCrVdqnuMcGl5z3GCKkY%3D&reserved=0.


API: Create a new API that returns the ETH price at the end of epoch

FE needs the ETH price at the end of each epoch. But we can't get this value from Vyper contract.
I know we store the ETH price at the end of each epoch in the Backend DB so please create a new api that returns the ETH price at the end of epoch. I will send you an epoch id as a param.

We were not storing the closing price.. but I updated the priceprdiction so it will from now on also we now have an api https://github.com/VolumeFi/price-prediction-api that being said our dns host is not accepting new domains right now so I won't be able to set up an endpoint until tomorrow. that being said it'll be https://pp.palomachain.com/epoch_info and https://pp.palomachain.com/bid_info when that's finished.. if you use the blank endpoints it'll bring all the records back if you use ?epoch_id you will be able to Bring a specific epochs back

This is blocked by squarespace. Somehow we're unable to edit or save new dns records here https://account.squarespace.com/domains/managed/palomachain.com/dns/dns-settings

@rootedbox created a ticket for this

@rootedbox this seems to be still down. Let's put this on palomabot.ai which is on namecheap and move on

https://pp.palomabot.ai/epoch_info
https://pp.palomabot.ai/bid_info
?epoch_id  for a specific epoch
@jamie088


Scrolling issue in Ionic 2 Starter Tutorial template

Short description of the problem:
The ion-content in the side menu in the ionic2-starter-tutorial does not properly scroll on Safari or Android 4.4.4. It does work properly on Chrome.
If you add a overflow-y: auto to the ion-content, then in Safari dev tools disable then enable it, scrolling works properly. But, this only works if you manually add the style via dev tools after load. Adding the style in code does nothing.
What behavior are you expecting?
Normal Scrolling
Steps to reproduce:

clone https://github.com/JacksonKearl/ionic-2-testing, which is the same as https://github.com/driftyco/ionic2-starter-tutorial but with more items in the side menu.
ionic serve
open side menu, items will not be scrollable until adding the aforementioned overflow-y: auto

Which Ionic Version?  2.x
Plunker that shows an example of your issue
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.3.0
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.11
Ionic CLI Version: 2.0.0-beta.36
Ionic App Lib Version: 2.0.0-beta.19
ios-deploy version: 1.8.4
ios-sim version: 5.0.1
OS: Mac OS X El Capitan
Node Version: v6.3.1
Xcode version: Xcode 7.3.1 Build version 7D1014

Hello, thanks for using Ionic! I cannot reproduce this with our latest release. Because of this I am going to close this issue for now, thanks!


README not being shown for packages (pnpm 6 only)

Your Environment

verdaccio version: 5.1.6
node version [12.x.x, 14.x.x]: 14.15.5
package manager: pnpm@6
os: Linux

Describe the bug
Verdaccio is not showing the README for packages that I publish to the registry. I can download the tarball directly and verify that the README does exist, but the Verdaccio UI always displays this now:
ERROR: No README data found!

To Reproduce
Publish a package and then open the UI.
Expected behavior
The UI should be showing the README.
Configuration File (cat ~/.config/verdaccio/config.yaml)
# https://github.com/verdaccio/verdaccio/issues/301
server:
  keepAliveTimeout: 0
# path to a directory with all packages
storage: (redacted)
web:
  title: (redacted)
security:
  api:
    legacy: false
    jwt:
      sign:
        expiresIn: 30d
  web:
    legacy: false
    sign:
      expiresIn: 7d
auth:
  htpasswd:
    file: (redacted)
    max_users: -1
  ldap:
    type: ldap
    cache:
      # max credentials to cache (default to 100 if cache is enabled)
      size: 100
      # cache expiration in seconds (default to 300 if cache is enabled)
      expire: 300
    client_options:
      url: (redacted)
      searchBase: (redacted)
      searchFilter: (redacted)
      reconnect: true
# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/
    max_fails: 100
    maxage: 2h
  fontAwesome:
    url: https://npm.fontawesome.com/
    max_fails: 100
    maxage: 2h
    auth:
      type: bearer
      token_env: FONT_AWESOME_NPM_TOKEN
packages:
  '@arista/*':
    access: $all
    publish: $authenticated
    proxy: npmjs
  '@fortawesome/*':
    access: $all
    proxy: fontAwesome
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    proxy: npmjs
  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all
    # allow all known users to publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated
    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs
# Use `npm audit`
middlewares:
  audit:
    enabled: true
logs: {type: stdout, format: pretty, level: http}
listen: (redacted)

Environment information
Environment Info:
  System:
    OS: Linux 4.19 Alpine Linux
    CPU: (40) x64 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
  Binaries:
    npm: 6.14.14 - /usr/local/bin/npm
{"level":30,"time":1634060285178,"pid":107,"hostname":"npm-0","msg":"exit caught"}

Debugging output
Can furnish upon request.
Contribute to Verdaccio

[ ] I'm willing to fix this bug 🥇

Yes, we have a README.md in all our projects. If I download the tarball from the Verdaccio UI, I can see the README inside.

@kaiyoma I've written this for you hopefully helps
https://github.com/verdaccio/verdaccio/wiki/Debugging-Veadaccio#debugging-in-production

https://www.npmjs.com/package/verdaccio-local-storage-advance  try this

Closing this, try the next pnpm release and feel reopen if issue persist

@juanpicado I just tried publishing packages with version 6.24.1 of pnpm and the same problem persists. Verdaccio is reporting ERROR: No README data found!

I haven't tried myself yet, but as far I've seen the changes looks good enough, kudos to @FolknR  which is the one that fix it 👏🏼 .


Use dom.setAttribute for non-dynamic (static) attributes.

This is a failing test for https://github.com/emberjs/ember.js/issues/13992.
Discussed with @wycats and will be implementing a separate
addDynamicAttribute (which will be what addAttribute will become)
and an addStaticAttribute to ElementStack.

@wycats - You mentioned to ping you when I had this up for review.


Add metadata links for rubygems

Add metadata for the source and changelog. These create direct links on rubygems, as well as help with automated management of gem upgrades.

Merged as e85731f4f441da95bef93c0b732d1921482a8a13


Fix code scanning alert - Token-Permissions

Tracking issue for:

[ ] https://github.com/NAL-work/jenkins/security/code-scanning/18

Fixed.


Support GCP Error Reporting

This optionally enables GCP Error Reporting from Cloud Run by properly formatting any error log messages. Error Reporting is extremly helpful when trying to understand failure rates overtime and alert on new types of errors after releases.

Working example in GCP: https://console.cloud.google.com/errors;service=pr-690-appmain;version=pr-690-appmain-00002-vac?project=staging-cloud-web-app


DatabaseError: Can't Load Database

const { JsonDB } = require( 'node-json-db' );
const { Config } = require( 'node-json-db/dist/lib/JsonDBConfig' );
var db = new JsonDB(new Config("myDataBase", true, false, '/'));
var data1 = db.getData('/');
console.log(data1);  // result: {}
db.push('/db', {}); // myDataBase.json: {db :{}}
var data2 = db.getData('/db');
console.log(data2); // result: DatabaseError: Can't Load Database...

Just to mention, I got the same error out of no where! after deleting the db.json file, it recreated it, and the error went away!
I have no Idea why it happened!

Just to mention, I got the same error out of no where! after deleting the db.json file, it recreated it, and the error went away!
I have no Idea why it happened!

Thought I'd chime in while I was searching: the issue I had was due to deleting all the values out of the document.
node-json-db expects at least an empty object { } if the file still exists. If is doesn't exist it creates a new file but with an object.

The original code sample doesn't produce any errors with Node.js 18.12.1 and node-json-db 2.1.3.
The output is as follow:
...>node Cannot_Load_Database.js
Promise { <pending> }
Promise { <pending> }

The created myDataBase.json contains the expected data:
{"db":{}}

Probably the issue had been fixed.

I'm encountering the same issue and I'm using:
# node --version
v18.20.1
"node-json-db": "^2.3.0",
Perhaps the problem has returned for a round 2?
I let it rebuild the json file, but it always comes out as totally blank, and when I try to put a {} it leaves the file blank, on the next .push() attempt!


"Run" vs "Run in terminal" time gap

Hello Stan
Thank you for showing me your extension at RubyKaigi.
There's a significant time gap between the "Run" and "Run in terminal".

It looks like the entire app restart for each individual test. Is there a way to optimize the "Run" task?

Normally the 2 should use the same command to run tests, which theoretically should have similar duration. Can you provide more information? Like the actual commands being invoked?
One possibility is that the one runs in terminal utilizes spring, while the one runs in test explorer doesn’t.

It runs each tests individually.
I'm on Rails <IP_ADDRESS>, rspec-rails (6.1.2), rspec-core (3.13.0), VScode 1.90.0, MacOS 14.5 on ARM (M1)
Run in terminal:
bundle exec rspec /Users/thomas/project/spec/lib/csv_imports_lib/things_spec.rb:3

Run:
Run options: include {:locations=>{"./spec/lib/csv_imports_lib/things_spec.rb"=>[324]}}
.

Finished in 0.19813 seconds (files took 10.59 seconds to load)
1 example, 0 failures

Coverage report generated for RSpec to /Users/thomas/project/coverage. 175 / 564 LOC (31.03%) covered.
Run options: include {:locations=>{"./spec/lib/csv_imports_lib/things_spec.rb"=>[307]}}
.

Finished in 0.02762 seconds (files took 3.81 seconds to load)
1 example, 0 failures

Coverage report generated for RSpec to /Users/thomas/project/coverage. 144 / 562 LOC (25.62%) covered.
Run options: include {:locations=>{"./spec/lib/csv_imports_lib/things_spec.rb"=>[292]}}
.

Finished in 0.11977 seconds (files took 3.81 seconds to load)
1 example, 0 failures

Coverage report generated for RSpec to /Users/thomas/project/coverage. 254 / 1408 LOC (18.04%) covered.
Run options: include {:locations=>{"./spec/lib/csv_imports_lib/things_spec.rb"=>[272]}}
.

Finished in 0.20968 seconds (files took 3.8 seconds to load)
1 example, 0 failures

Coverage report generated for RSpec to /Users/thomas/project/coverage. 267 / 1408 LOC (18.96%) covered.
Run options: include {:locations=>{"./spec/lib/csv_imports_lib/things_spec.rb"=>[250]}}
.

[...]

I'm seeing this too.
ruby 3.3.3 (2024-06-12 revision f1c7b6f435) [x86_64-linux]
Rails <IP_ADDRESS>
Via terminal:
Run options: include {:locations=>{"./spec/controllers/application_controller_spec.rb"=>[5]}}
.....................

Finished in 0.56302 seconds (files took 5.79 seconds to load)
21 examples, 0 failures

Via test explorer:

Fix for this would be great, makes the "Run" command pretty useless for larger spec files.

@st0012 I confirmed that this problem that occurs with latest ruby-lsp (0.20.1) and ruby-lsp-rspec (0.1.16) using Ruby 3.3.5 and Rails <IP_ADDRESS>. How and where does the rspec is called?

The main plugin has an open issue for this: https://github.com/Shopify/ruby-lsp/issues/2402
The test execution loop in the extension is here.  It will execute anything marked with the 'example' tag.  But it will also enqueue any children of that node to be potentially run.  So even if we changed the codelens response from the rspec extension to tag the context/describe codelens commands with 'example', the current extension code would still end up running the children as well.
and then there is the issue of how to pluck the success/error responses from the stdout of the test and properly populate the test explorer ui.
it looks like someone tried to do it for minitest but gave up, and the maintainers from shopify claim its on their roadmap to address eventually.


Fingerprint of apk signing certificate

For users not compiling the apk themselfes and instead rely on provided builds (on Github) it would be good to provide a fingerprint as SHA256 from the signing certificate for the user to verify the apk.

@rdy2go isnt it what you want https://github.com/Akylas/OSS-DocumentScanner?tab=readme-ov-file#appverifier-hashes ?

True. My Bad. I checked a few weeks ago and assumed that it was still not provided. But with a commit 2 weeks ago it got introduced. Thanks.


Docker build failed - gcc no such file or directory

Hello !
Everytime I want to build the container according to the README the build fail when it tries to download python regex library.
unable to execute 'gcc': No such file or directory
    error: command 'gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zugkz3ko/regex_5c32842a6c6b4975b244ab4d40699a9a/setup.py'"'"'; __file__='"'"'/tmp/pip-install-zugkz3ko/regex_5c32842a6c6b4975b244ab4d40699a9a/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-03aj5qvg/install-record.txt --single-version-externally-managed --compile --install-headers /usr/include/python3.8/regex Check the logs for full command output.

I fixed it locally and I will submit a PR as soon as possible.

Hello @ThePicpixel!
Thank you very much for your help! I will close the issue as you've fixed it in your PR.
Have a nice day! (:


Feat/hcf and lcm

Ref : #126

[x] Route math/hcflcm Added
[x] Test for math/hcflcm added

@abhinab-choudhury kindly resolve the merge conflicts

kindly resolve the conflicts

Please merge my PR a have resolved the conflit

@abhinab-choudhury ,Thank you for your valuable contribution .Do check out other repositories from IEEE-VIT


Is it possible to add two ng-admin apps for two different types of users?

Hello,
I want to create two types of users, with separate admins pages.Is it possible that each ng-admin app inherits from custom ui.router state? Each  ui.router state would have a custom namespace and resolver for user's  authentication.

Related to #1026. You need to build dynamically the menu list according your user role.

Duplicate of #875


MSHU11: Updated VERDICT Installation Guidelines in ReadMe(s)

Added a few points of clarification after following the ReadMe installation guidelines available in release 1.6.4

Docker Desktop on Windows: the FILE_SHARING setting is not available for non-Windows container configurations. More information on this can be found in the docker windows documentation:

Note: The File sharing tab is only available in Hyper-V mode because the files are automatically shared in WSL 2 mode and Windows container mode.

MacOS verdict settings can be found from the OSATE application toolbar > OSATE > Verdict > Verdict Settings... etc.), different from windows

Specified that the Verdict menu is available in the application toolbar (for all OS's)

Investigating the distinction between Docker's "Hyper-V" and "Windows-Container" modes

Squashed & Marked Ready for Review


Add additional extra var to update plyabook run

Add additional extra var to update-edpm.yml playbook run
named update_playbook_run to make it possible to skip some
ansible tasks on deployment and run them on update only.
Signed-off-by: Mikołaj Ciecierski<EMAIL_ADDRESS>As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/lgtm
(restoring @marios's one)
/approve


Hope tab title support drag operation

Description of the new feature/enhancement

hope can drag tab title to another solid window
Proposed technical implementation details (optional)

Thanks for the request! This is /dup #1256


Preventing blocking touches on overlapping items

Added pointerEvents="box-none" to item wrapper to prevent blocking touches when items are overlapping and have touchable children.

Hi @henninghall,
Could you please tell me more about the issue you're trying to prevent with this commit? Can you share a screenshot of the overlapping items on which you had trouble tapping?

Of course, here is some screenshots:

The purple squares are item borders. The red zones are shows where touches are blocked on underlying items. Because of the rendering order, the items to the right are rendered on top of their left neighbor and are therefore blocking touches on items on the left.
In this example, the buy-button is actually touchable since it is on the left side. If placed on the right side instead, it would be hidden beneath the right item and therefore be untouchable.
This PR fixes this problem.

@henninghall Interesting, thanks for the detailed explanation. Still, I'm curious: how did you make the carousel behave this way (overlapping items)? Negative margins? Are there any drawbacks besides the one fixed by this PR?

By the way, you can start using your fix right away:
"react-native-snap-carousel": "https://github.com/archriss/react-native-snap-carousel#a3212af"

I'll publish a new release when I'm done working on other fixes ;-)

Exactly, I'm passing negative margins to the sliderStyle prop. I have been using it for months and, except for this fix, it works like a charm. Thanks for your work!


Need ability to switch between front and back cameras

Coming in a few days.

We've added the VideoKitCameraManager.facing property to switch cameras, in addition to specifying the VideoKitCameraManager.device. See the changelog.


Cannot download icon from self-signed secure http websites

Please first read the documentation. Problems affecting the client, e.g. Plex or Emby should be reported there in the forum.
Describe the bug
PNG icon is hosted on website with either self-signed or invalid ssl cert.
Threadfin seems unable to retreive image. Shows as broken link.
Server (please complete the following information):

OS: Docker running on Alpine LXC
Arch: AMD64
Threadfin Version and Build: Latest docker image

To Reproduce
Steps to reproduce the behavior:

Add xmltv epg from following link: https://xmltvfr.fr/xmltv/xmltv.xml.gz
Find m3u playlist that includes channel supported in xmltv: https://iptv-org.github.io/iptv/countries/fr.m3u
Map channel that includes an image hosted on unsecure web server (arte is one of them but not available in the m3u playlist linked above. I guess you could just map Arte XMLTV entry to whatever channel.
Image should not download properly

Expected behavior
Icon should download from unsecure https website.
Screenshots

Additional context
Example image that causes issue: http://s3.i3ns.net/portal/picon/2021-06/37306f7774bbe96a948dc9d923c1db22.png

That isnt something I can fix. It wont work unless the SSL cert is valid


Auto select the app engine api when objectify is selected

fixes #1018
unit tests pending.
This will current auto select the App Engine API when objectify is chosen. It does not however prevent the user from then unselecting the App Engine API afterwards. I'm debating between adding logic to prevent this, and adding a text label somewhere to indicate that App Engine API is required when Objectify is selected.

I'm leaning towards not disabling the App Engine API checkbox (so that it can't be unchecked) after selecting the Objectify library. Thoughts on this?
Other than this point, its ready for review.

Current coverage is 25.40% (diff: 76.92%)

Merging #1030 into master will increase coverage by 0.37%

@@             master      #1030   diff @@
==========================================
  Files           222        222
  Lines          8245       8258    +13
  Methods           0          0
  Messages          0          0
  Branches       1643       1649     +6
==========================================
+ Hits           2064       2098    +34
+ Misses         5789       5764    -25
- Partials        392        396     +4

Powered by Codecov. Last update 01cfdd0...8ea2a25

Did you mean "so that it can be unchecked"?

If Objectify depends on the App Engine API, than I think it would make sense to both disable the App Engine API button if Objectify is enabled AND adding the text explaining why that is happening.
I can't think of a reason why a user would want Objectify enabled and the App Engine API disabled, and get the subsequent compilation errors.

@patflynn I updated the library panel per our discussion.


Added More Documentation and Comments

I am a literate programmer, so I write comments wherever I code (except HTML), so I changed most of the JavaScript to have more comments. I also made lots of questions in my comments which can be found by looking at the Files changed in the tabs above, pressing Ctrl+F  or Cmd+f, and typing in "Noble Mushtak:". I also added README.mds to help with documentation. I didn't change Extension, though, because it looked like something separate and it was too big for me to go through it all.
I put the JavaScript in tests/sync_test.html in a separate tests/sync_test.js file because the JavaScript is so big, it should be a separate file. Also, we need to be using asynchronous HTTP requests, so I switched fetchEntries() and sync() in Backend/sync.js to asynchronous requests and made appropriate changes in tests/sync_test.js. Synchronous HTTP requests in JavaScript is never acceptable now that we're in the 2010s.
Also, in the root README.md, I added myself as a team member. Hopefully, I will count if you accept this pull request...

I too am a literate programmer; but I wrote this stuff in a fairly short amount of time.
The reason I didn't put the Javascript for tests in separate files, is because those files aren't going to be around for much longer; I wrote those simply to test a few things.
In the production "builds", all HTTP Requests will be asynchronous.
If you want, I'll add you to our Slack group, where we could further discuss you becoming a team member.
We're not accepting many people to help us, as we don't want to have to try and keep a large team organized.

OK, that's cool. I think we should always use AJAX even in testing, though, because the synchronous requests were too laggy for my computer. I don't know how to use Slack, but I'd be OK with joining one. Do I need to sign up for a Slack account or can I just give you my e-mail?

...I'll just need an email address; you'll receive instructions on how to join when I invite you.

OK, I gave you my e-mail on KA. Please tell me when you copied it so I can delete the Tip/Thank.

Invited you. Thanks!

Got the e-mail. Thanks!


Question: How does the bot update the dependencies of a specific branch

Hello, I have two branches, a main one and a test one, I need the bot to only update and open PR in a specific branch

Configure "baseBranches"


Resolve no results instead of rejecting the promise

When using Sentry this localstorage adapter reports an error every time a query result is empty. How about resolving no results instead of rejecting the promise?
In my usecase an empty response is desired if the query in question returns an empty result, it's not an error.
Here is the rejection:
https://github.com/locks/ember-localstorage-adapter/blob/master/addon/adapters/ls-adapter.js#L115
How about resolving it like it's done here:
https://github.com/locks/ember-localstorage-adapter/blob/master/addon/adapters/ls-adapter.js#L90

My referenced PR updates this. Please consider it :)

Yeah this is kind of unexpected behavior. If you don't want to resolve results then perhaps consider updating the read me with example code on how to handle the rejected promise.
Newbies might be tripped up by this. 😄


Address sanitizer & memory sanitizer issues

Expected Behavior
asan and msan should not detect issues.
Current Behavior
We ran address sanitizer and memory sanitizer on mmseqs2 and they flagged a few issues.
asan

ODR violation over binary_name.
Possible signed overflow in random number generation using unsigned integer types.
'initialisation order fiasco'

msan

String not terminated.

Fixes
We fixed these issues, respectively, by:

Changing this line to:

__attribute__ ((weak)) const char* binary_name = "mmseqs";

Applying this patch to lib/alp/njn_random.cpp:

--- a/lib/alp/njn_random.cpp
+++ b/lib/alp/njn_random.cpp
@@ -50,19 +50,19 @@ namespace {

 	const size_t r_off = 12;

-	long	state [33] = {
-	static_cast <long> (0xd53f1852),  static_cast <long> (0xdfc78b83),  static_cast <long> (0x4f256096),  static_cast <long> (0xe643df7),
-	static_cast <long> (0x82c359bf),  static_cast <long> (0xc7794dfa),  static_cast <long> (0xd5e9ffaa),  static_cast <long> (0x2c8cb64a),
-	static_cast <long> (0x2f07b334),  static_cast <long> (0xad5a7eb5),  static_cast <long> (0x96dc0cde),  static_cast <long> (0x6fc24589),
-	static_cast <long> (0xa5853646),  static_cast <long> (0xe71576e2),  static_cast <long> (0xdae30df),   static_cast <long> (0xb09ce711),
-	static_cast <long> (0x5e56ef87),  static_cast <long> (0x4b4b0082),  static_cast <long> (0x6f4f340e),  static_cast <long> (0xc5bb17e8),
-	static_cast <long> (0xd788d765),  static_cast <long> (0x67498087),  static_cast <long> (0x9d7aba26),  static_cast <long> (0x261351d4),
-	static_cast <long> (0x411ee7ea),  static_cast <long> (0x393a263),   static_cast <long> (0x2c5a5835),  static_cast <long> (0xc115fcd8),
-	static_cast <long> (0x25e9132c),  static_cast <long> (0xd0c6e906),  static_cast <long> (0xc2bc5b2d),  static_cast <long> (0x6c065c98),
-	static_cast <long> (0x6e37bd55)};
+	unsigned long	state [33] = {
+	0xd53f1852ul,  0xdfc78b83ul,  0x4f256096ul,  0xe643df7ul,
+	0x82c359bful,  0xc7794dfaul,  0xd5e9ffaaul,  0x2c8cb64aul,
+	0x2f07b334ul,  0xad5a7eb5ul,  0x96dc0cdeul,  0x6fc24589ul,
+	0xa5853646ul,  0xe71576e2ul,  0xdae30dful,   0xb09ce711ul,
+	0x5e56ef87ul,  0x4b4b0082ul,  0x6f4f340eul,  0xc5bb17e8ul,
+	0xd788d765ul,  0x67498087ul,  0x9d7aba26ul,  0x261351d4ul,
+	0x411ee7eaul,  0x393a263ul,   0x2c5a5835ul,  0xc115fcd8ul,
+	0x25e9132cul,  0xd0c6e906ul,  0xc2bc5b2dul,  0x6c065c98ul,
+	0x6e37bd55ul};

-   long	*rJ = &state [r_off];
-	long	*rK = &state [sizeof state / sizeof *state - 1];
+  unsigned long	*rJ = &state [r_off];
+	unsigned long	*rK = &state [sizeof state / sizeof *state - 1];

 }
 void Random::seed (long x)
@@ -73,7 +73,7 @@ void Random::seed (long x)

    // linear congruential initializer
 	for (i = 1; i < sizeof state / sizeof *state; ++i) {
-		state [i] =<PHONE_NUMBER> * state [i - 1] + 12345;
+		state [i] =<PHONE_NUMBER>ul * state [i - 1] + 12345ul;
 	}

 	rJ = &state [r_off];
@@ -85,7 +85,7 @@ void Random::seed (long x)
 long Random::number () // uniform random x : 0 <= x <= exp2 (31) - 1

 {
-	long r;
+	unsigned long r;

 	r = *rK;
 	r += *rJ--;
@@ -97,6 +97,6 @@ long Random::number () // uniform random
 			rJ = &state [sizeof state / sizeof *state - 1];
    }

-   return (r >> 1) &0x7fffffff; // discard the least-random bit
+   return (r >> 1) &0x7ffffffful; // discard the least-random bit
 }

Instead of running plain xxd, we generate header files for resource files with the following pattern:

"""
#ifndef MMSEQS2_XXD_{1}_H_
#define MMSEQS2_XXD_{1}_H_
#include "mmseqs2/{0}_data.h"

// Use casters to make values act as properties. This is to prevent static variables causing
// "initialization order fiasco".
struct {0}_CharCaster {{
  operator const unsigned char*() const {{
    return reinterpret_cast<const unsigned char*>({0}_data_create()->data);
  }}
  operator const char*() const {{
    return reinterpret_cast<const char*>({0}_data_create()->data);
  }}
  operator const void*() const {{
    return reinterpret_cast<const void*>({0}_data_create()->data);
  }}
}};

struct {0}_LenCaster {{
  operator unsigned int() const {{
    return static_cast<unsigned int>({0}_data_create()->size);
  }}
}};

inline constexpr {0}_CharCaster {0};
inline constexpr {0}_LenCaster {0}_len;

where {0} is the filename of the respective file.

Changing \n to \0 in this line.

We hope this is helpful.
Best wishes

Thank you for the patches! How did you find these errors?
We are running MMseqs2 in our regression with asan and neither of these shows up.

Hi Martin,
That's a great point, thanks. I've got a few pieces of information:

We run asan with non-default flags --check_initialization_order=true and --strict_init_order=true.

We realised that point 3 from my list ('initialisation order fiasco') is specific to how we build stuff, so that shouldn't be an issue for you or other users.

We're not quite sure why we got the ODR violation flagged, while you didn't.

Best wishes

I can't reproduce asan errors (on a simple search at least, the run_search.sh script in our regression). With neither gcc-12 nor clang-15.
I enabled the following asan options:
ASAN_OPTIONS=abort_on_error=1:strict_string_checks=1:detect_stack_use_after_return=1:check_initialization_order=1:strict_init_order=1

Hi, thanks for looking into that! We're not sure about what other differences are causing our differing results...
Points 1 & 3 might be specific to the way we build the binary; we think that the overflow in njn_random could be more general & worth looking at.


[Rippled Server Doesn't Sync] (Version: [1.9.1])

Issue Description
I started a server for a testnet, but it is not synchronized.
However, when we started the server about a week ago, also for the testnet, it synchronized without any problems.
Both are running with the same settings.
When we tried to start the system for the mainnet, the synchronization was performed without any problems.
We have investigated, but cannot find the cause.
If you have a solution, please let me know.
Also, please let us know if there is anything else you need other than the information below
Steps to Reproduce
Run rippled 1.9.1 for testnet
Expected Result
Server synchronization has begun.
Actual Result
Error Message:
"result": {
        "error": "noNetwork",
        "error_code": 17,
        "error_message": "Not synced to the network.",
        "request": {
            "command": "ledger_current"
        }

Environment
server_info:
"result" : {
      "info" : {
         "build_version" : "1.9.1",
         "closed_ledger" : {
            "age" : 97168,
            "base_fee_xrp" : 1e-05,
            "hash" : "2F32C774620C13257CE80B37CD4B6D4820A24D5262EEEC747D49163282408D40",
            "reserve_base_xrp" : 200,
            "reserve_inc_xrp" : 50,
            "seq" : 2
         },
         "complete_ledgers" : "empty",
         "hostid" : "ip-10-55-214-85.ap-northeast-1.compute.internal",
         "io_latency_ms" : 1,
         "jq_trans_overflow" : "0",
         "last_close" : {
            "converge_time_s" : 0,
            "proposers" : 0
         },
         "load" : {
            "job_types" : [
               {
                  "in_progress" : 1,
                  "job_type" : "clientRPC"
               }
            ],
            "threads" : 4
         },
         "load_factor" : 1,
         "node_size" : "small",
         "peer_disconnects" : "0",
         "peer_disconnects_resources" : "0",
         "peers" : 0,
         "pubkey_node" : "n9MWmEerWrJYinCLV6QDUJ9komfScs7FhC4k7q4WUrXrstQW4mVT",
         "pubkey_validator" : "none",
         "published_ledger" : "none",
         "server_state" : "disconnected",
         "server_state_duration_us" : "97163731697",
         "state_accounting" : {
            "connected" : {
               "duration_us" : "1103435",
               "transitions" : "1"
            },
            "disconnected" : {
               "duration_us" : "97163958428",
               "transitions" : "2"
            },
            "full" : {
               "duration_us" : "0",
               "transitions" : "0"
            },
            "syncing" : {
               "duration_us" : "0",
               "transitions" : "0"
            },
            "tracking" : {
               "duration_us" : "0",
               "transitions" : "0"
            }
         },
         "time" : "2022-Jun-01 09:52:38.179769 UTC",
         "uptime" : 97165,
         "validation_quorum" :<PHONE_NUMBER>,
         "validator_list" : {
            "count" : 1,
            "expiration" : "2022-Nov-15 00:00:00.000000000 UTC",
            "status" : "active"
         }
      },
      "status" : "success"
   }
}

Supporting Files

The one thing that jumps out at me is that your node has "peers" : 0 and was only ever in the connected state for just over 1 second. That usually indicates a networking or connectivity issue. Start with https://xrpl.org/server-doesnt-sync.html for more info and tips. Also double-check https://xrpl.org/connect-your-rippled-to-the-xrp-test-net.html to ensure you didn't miss any setup steps.

@ximinez
I would like to confirm, is the server "r.altnet.rippletest.net" currently unavailable? When the above error occurred, the item "ips" in rippled.cfg specified the above server.

Per the docs I linked to, the [ips] section should contain s.altnet.rippletest.net 51235


Upgrade to Babel 6

I just upgraded my project to babel 6 and am receiving the following error.
error given was: Error: Cannot find module 'glob'
at Function.Module._resolveFilename (module.js:337:15)
at Function._module3.default._resolveFilename (/Users/sridattap/Applications/frontend/node_modules/webpack-isomorphic-tools/node_modules/require-hacker/babel-transpiled-modules/require hacker.js:403:34)
Any plans to upgrade this project and require-hacker to babel 6??

You can make up a sample project illustrating the error and I can have a look at it.
I haven't even looked at Babel 6 yet.

@Sridatta7 I upgraded to Babel 6 and all works fine. One of the most major breaking changes was destructiring export default of an object in the import statement no longer works. That is most likely your problem but I can't know for sure

@Sridatta7 why do you care, isomorphic tools is precompiled (doesn't seem like this would be related to glob)? I just went through this at work and it was painful, would be happy to help out. I'm on Babel 6 and isomorphic tools works great, use https://www.npmjs.com/package/babel-plugin-add-module-exports

FYI
I'm posting this in every issue and PR to notify whoever may be interested:
today I've released an alternative helper library called universal-webpack.
It takes a different approach than webpack-ismorphic-tools and instead of hacking Node.js require() calls it just compiles all code with target: 'node' webpack configuration option.
As a result, all Webpack plugins and features are supported.
If you think you might need that here's an example project:
https://github.com/halt-hammerzeit/webpack-react-redux-isomorphic-render-example


Problem with licensing

Your library says that it includes code written by Douglas Crockford. That seems very likely to be the json.org json library.
That library had a license that is not Apache License compatible. Inclusion of that code would make your library incompatible with the Apache License.
I have a few questions and a suggestion:

is that the code you are referring to in your POM?

if so, can you clarify your license so that people don't misunderstand and think that your code is open source.

is it possible to switch your dependency to a library that has a valid open source license? I would offer https://github.com/tdunning/open-json as an example of such.

Json-lib is licensed under Apache 2.0


fixes #423

Pull Request (PR) description
To work around the PSScriptAnalyzer introduced in 1.18 and described in #423 , this PR changes the order of the classes defined in schema.mof, for resources that had subclasses.  The OMI_BaseResource class gets listed first now, which also happens to workaround the PSSA test that was erroneously failing.
This Pull Request (PR) fixes the following issues
#423
Task list

[ ] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #424 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #424   +/-   ##
=======================================
  Coverage   90.77%   90.77%
=======================================
  Files          17       17
  Lines        2438     2438
=======================================
  Hits         2213     2213
  Misses        225      225

Continue to review full report at Codecov.

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


Annotated 3DPW dataset

Hi,
What a wonderful work, I want to know will the annotated 3DPW dataset be released? Thx
Best

Hi,
Please follow our readme for the annotated 3DPW dataset

Cool!, Thanks for your work and code.


Favicon

The favicon does not display.
Image file is present and in the right directory
Settings in _config.yml in main directory
We discussed one possibility might be that the image format is .jpg, not ico

changing the image format to .ico worked


Implement queuing for message edits

Issue
PomoBot supports numerous auto-updating messages, including the pinned status message in timer channels, and temporarily live responses to groups and status.
Due to the current bursty nature of these requests (sent in batches every n seconds), when managing many guilds PomoBot frequently hits the global ratelimit of the Discord API.
Proposed solution
Implement queuing logic for message edits and frequent requests, and add intelligent spacing between such calls that adapts to the current load.

Adding bug tag and bumping priority since these requests caused the API to temporarily hard-ratelimit the public instance. The relevant features are currently disabled pending implementation of this issue.


Alert & Reports running into lock issues often after upgraded to 3.0.0

After we migrate to 3.0.0, we have seen it happening quite often when modifying alerts that it fails on the front end. In the logs, it says (MySQLdb._exceptions.OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction'). When the request was still executing, I checked the mysql db but it returns nothing when running Show open tables where in_use>0; . We didn't observe such behavior before upgrading to 3.0.0.
How to reproduce the bug
I don't find a definitive way to reproduce the issue. It just happens sometimes.

Go to Alerts & Reports page
Click on any existing alert
Try to modify any field, like owner or query.
Click save and see error

Expected results
Alerts & Reports saved successfully
Actual results
Cannot save edited alters & reports even after retrying
Screenshots
If applicable, add screenshots to help explain your problem.

Environment
(please complete the following information):

browser type and version: Chrome latest
superset version: superset version 3.0.0
python version: python --version 3.9
node.js version: node -v v20.8.0
any feature flags active: ALTERS_REPORTS is set to True

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@zhaorui2022 are you still facing this? It seems like it's a MYSQL issue. Did SHOW PROCESSLIST work (noting that you need sufficient privileges)? You might need to adjust the DB's lock timeout. I also wonder if you've been scaling your alerts/reports, so it makes a lot (potentially thousands — who knows) of queries simultaneously. Beyond that, I'm not quite sure how to diagnose/replicate this.

Not sure if anyone's facing this and we don't support Superset prior to 4.x any more, so I'll close this out. Holler if it needs more attention.


[fix] sns_user_account auth error #1285

Coverage decreased (-0.006%) to 84.463% when pulling 1288f487bae23f876a6dd8929347809524e62eb9 on itowtips:fix into 30a3eeb710ca75ff7a2ffebca617b15a932f7bd4 on shirasagi:master.

Coverage decreased (-0.04%) to 84.427% when pulling 1288f487bae23f876a6dd8929347809524e62eb9 on itowtips:fix into 30a3eeb710ca75ff7a2ffebca617b15a932f7bd4 on shirasagi:master.


BYOL: Move unnecessary dependencies to "if name == 'main'" section

Move imports, to the "if name == 'main' section.
What does this PR do?
Avoids importing unnecessary stuff, among them a cv2 import via the SimCLR transform modules, when importing BYOL

Hello @sorenrasmussenai! Thanks for opening this PR.

In the file pl_bolts/models/self_supervised/byol/byol_module.py:

Line 186:121: E501 line too long (122 > 120 characters)
Line 188:1: W293 blank line contains whitespace

Do see the Hitchhiker's guide to code style


Updates for Auth and Design

Updates For:

Closer match for the new UI design
Replace old authentication
Fix auth token issues
Remove old libraries like PCLCrypto
UI performance changes
Unit test cleanup

@michaelstonis Thanks for the PR. We'll need some time to review this one since it's so big, but we'll get back to you.

@danmoseley I can, but a lot of it is interdependent on the .NET 8 upgrade. Let me take a pass at splitting it out into multiple.


ListUserTags output is incorrect

ListUserTags should have a result member under Tags, currently there is item instead.
https://docs.aws.amazon.com/IAM/latest/APIReference/API_ListUserTags.html
Discovered while using localstack with Go SDK.   Expected the SDK to successfully list user tags, but since output doesn't match the spec, it doesn't find the tags in the response.
Installed moto via docker localstack.

Thanks for raising this @farrellit - the Python SDK is a bit more forgiving with the exact XML format, that's why we don't tend to notice mistakes like this.


MAL Access Control Interface not found

Hi,
The current version of the MAL implementation does not seem to provide any extension point for an application to provide an access control implementation as specified by the MAL recommended standard (CCSDS 521.0-B-2).
Will this feature be added?

Hi,
 Such an API or SPI was not part of the initial objectives of the

MAL/C prototype. However, the project is open and now it really make
sense to add these access control functions. If you want to study this
task we can possibly help you according to your needs
Regards, Andre.
Le 24/06/2016 à 15:14, ebjorntvedt a écrit :

Hi,
The current version of the MAL implementation does not seem to provide
any extension point for an application to provide an access control
implementation as specified by the MAL recommended standard (CCSDS
521.0-B-2).
Will this feature be added?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ccsdsmo/malc/issues/1, or mute the thread
https://github.com/notifications/unsubscribe/ARUdEScq0oFkrJs7UgVnFidFs5ja4KPiks5qO9gmgaJpZM4I9wOd.

--
Need help for architecturing your distributed application?
Need professional support or additional development about Joram?
<EMAIL_ADDRESS>Freyssinet Andre<EMAIL_ADDRESS>ScalAgent Distributed Technologies              http://www.scalagent.com


feat: specify prom server start addr

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
start prometheus API server with specified addr, so the /query and /query_range can be accessible outside of container by running the standalone mode: cargo run -- standalone start --prom-addr=<IP_ADDRESS>:4004

promql-server will change to prometheus (discuss). So for this PR we'd better name the config prometheus-server

promql-server will change to prometheus (discuss).

Shall we create an issue for this? I'm not sure whether we already have an issue tracking this.

promql-server will change to prometheus (discuss).

Shall we create an issue for this? I'm not sure whether we already have an issue tracking this.

Sure: https://github.com/GreptimeTeam/greptimedb/issues/1127


Client Allocation Request for: 广州星淼文化传播有限公司

Client Allocation Questions
Core Information

Name: 广州星淼文化传播有限公司
Website / Social Media:  https://aiqicha.baidu.com/company_detail_28119221923694?rq=ef&pd=ee&from=ps
Region: Greater China
DataCap Requested: 10TiB
Addresses to be Notarized: f3tdrpylphoxvu6sgngnmlmai7my6tapqa3dfw2yipwv5jkns64bm3fvr26rjoust5j5r4hc4gk27dycjf4rya
Notary Requested: IPFSUnion

@denglpo Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

I added the explanation on the previous application（https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/894）


Add smart retries to table.mutate

[x] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)

A couple of things to note about this PR:

There's a bug where faketimers don't play nicely streams. I filed a bug on process-nextick-args which causes an issue of readable-streams, so that's the deal with the patch files. Node v4 has a nested node_modules structure while >= v6 is flat.
patch-package doesn't handle possible missing packages so that's why the git commands are run manually

Codecov Report

Merging #17 into master will decrease coverage by 0.24%.
The diff coverage is 94.44%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage     100%   99.75%   -0.25%
==========================================
  Files           8        8
  Lines         792      814      +22
==========================================
+ Hits          792      812      +20
- Misses          0        2       +2

Impacted Files
Coverage Δ

src/table.js
98.89% <94.44%> (-1.11%)
:arrow_down:

Continue to review full report at Codecov.

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

I can get coverage for unit tests back to 100% with the following patch, although I'm not sure it's the right thing to do
diff --git a/test/table.js b/test/table.js
index f348120..9173788 100644
--- a/test/table.js
+++ b/test/table.js
@@ -999,8 +999,10 @@ describe('Bigtable/Table', function() {
     describe('error', function() {
       describe('API errors', function() {
         var error = new Error('err');
+        var setTimeoutStub;

         beforeEach(function() {
+          setTimeoutStub = sinon.stub(global, 'setTimeout').callsFake(setImmediate);
           table.requestStream = function() {
             var stream = new Stream({
               objectMode: true,
@@ -1015,6 +1017,10 @@ describe('Bigtable/Table', function() {
           };
         });

+        afterEach(function() {
+          setTimeoutStub.restore();
+        });
+
         it('should return the error to the callback', function(done) {
           table.maxRetries = 0;
           table.mutate(entries, function(err) {
@@ -1022,6 +1028,17 @@ describe('Bigtable/Table', function() {
             done();
           });
         });
+
+        it('attempts to retry the mutation', function(done) {
+          table.maxRetries = 1;
+          table.mutate(entries, function(err) {
+            assert.strictEqual(err, error);
+            assert.strictEqual(setTimeoutStub.callCount, 1);
+            assert(setTimeoutStub.getCall(0).args[1] > 2000);
+            assert(setTimeoutStub.getCall(0).args[1] < 3000);
+            done();
+          });
+        });
       });

       describe('mutation errors', function() {

This PR introduces an "integration" test command, but we already have system tests that are supposed to be the same thing: "Does our code work when integrated with the system?" (Using the name "system tests" was a decision that involved more languages than just us). I also see a reference to "acceptance" testing. I think we should keep everything under one roof, "system tests", since that's our pattern across all of the API libraries. It should only be one command for a contributor/maintainer to determine if their changes introduce any issues with the upstream API, and that's historically been "npm run system-test".
Regarding the patching, I would prefer to wait for https://github.com/calvinmetcalf/process-nextick-args/pull/10 to be merged and released.

Regarding patching, after calvinmetcalf/process-nextick-args#10 is merged (it already was), nodejs/readable-stream#317 needs to be merged, publish a release (note this module is basically part of node core), and then wait for through2 to publish a release with that updated readable-stream dependency. I figured this was a good enough workaround in the meantime

I see, thanks for the rundown. Yeah, I suppose the patching will have to do for now.

Thanks for splitting that out. I believe there might be some work for the code coverage still.

I can add the following test to the unit tests to get it back to 100%. Is that something you'd be ok with?
    describe('retries', function() {
      var fakeStatuses = [
        [
          {
            status: {
              code: 0,
            },
          },
          {
            status: {
              code: 4,
            },
          },
        ],
        [
          {
            status: {
              code: 0,
            },
          },

        ]
      ];

      beforeEach(function() {
        FakeGrpcService.decorateStatus_ = function(status) {
          return {};
        };
        table.requestStream = function() {
          var stream = new Stream({
            objectMode: true,
          });

          setImmediate(function() {
            stream.emit('request');
            stream.end({entries: fakeStatuses.shift()});
          });

          return stream;
        };
      });

      it('should succeed after a retry', function(done) {
        table.maxRetries = 1;
        table.mutate(entries, done);
      });
    });
  });

That test looks good to me. I also think we should have another unit test to confirm only the correct subset of entries from the original request is sent when a retry is made, effectively testing the new pendinEntryIndices, entryToIndex holders.

Done, coverage appears to be back to 100%

I made some small changes, just to conventionalize the code (stream error handling first, all caps file-wide const name, etc). Tests still pass, but please make sure these changes look harmless to you as well.

Look good to me!


Missing docs on how to consume from SPM (on Windows)

Description
I'm not finding any docs on how to reference this project from SPM. I tried a straightforward
    dependencies: [
        .package(url: "https://github.com/apple/swift-testing.git", from: "6.0.3")
    ],

As well as exact: "6.0.3". In both cases, the build then fails with "Testing" contains unsafe build flags. I was able to get it to work with an explicit commit hash but that's not great:
    dependencies: [
        .package(url: "https://github.com/apple/swift-testing.git", revision: "18c42c19cac3fafd61cab1156d4088664b7424ae"), // 6.0.3
    ],

Am I doing it wrong? Docs would help.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
6.0.3
Swift & OS version (output of swift --version && uname -a)
compnerd.org Swift version 6.1-dev (LLVM 80d178d8cbb1cee, Swift fb259eaa4980e29)
Target: x86_64-unknown-windows-msvc

Swift Testing is part of the Swift 6 toolchain. There are no instructions on adding a package dependency because you don't need one. You can simply import Testing in your test target.


WIP: Increase test coverage

Description
This is to increase the test coverage for the cookbook.
Issues Resolved

Increase SV timeout to 30 seconds in kitchen file (https://github.com/chef-cookbooks/jenkins/pull/692/commits/1f3f817ec17f869a717f3cc0ada88f7d4e6a97bf)
Fix bug where cannot find version of plugin from plugin universe (https://github.com/chef-cookbooks/jenkins/pull/692/commits/f3c45dea00d443ffa261d0dc97c1f4e7244e38c1)
Fix delete action on jnlp slave (https://github.com/chef-cookbooks/jenkins/pull/692/commits/a00572c305c985578bfbe07875e0dd055cbc9400)
Convert custom Jenkins ServerSpec resources to InSpec resources
Convert ServerSpec tests to InSpec tests
Reduce number of suites and moved as many tests into the smoke suites

To Do:

[ ]  Cleanup ServerSpec tests and resources

Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

This is a WIP. Need Travis to run tests.

Hey @tas50
This PR is almost finished; I just need to

delete all the ServerSpec tests and helpers
update kitchen.yml to remove all the redundant suites

Can you review before I do the final cleanup, or did you want me to delete all the ServerSpec files first?
I'm not fussed either way, but it could be easier to compare the ServerSpec tests vs the InSpec tests file to file, rather than git diff, as there's going to be a lots of files deleted.
For example, comparing test/integration/jenkins_job_*/* with test/integration/jenkins_smoke/controls/jenkins_job.rb

This is massive and seems all legit. Thank you so much for taking the time to put it all together. Nothing stands out to me so feel free to keep on the good work and I can merge this whenever you want. I added you as a collaborator on the cookbook since at this point you know ore about the setup of things than I do.

No worries. :)
I'll keep cleaning it up & will let you know when its ready

@josh-barker any reason not to merge what you have here and then do any further cleanup in another PR. It would be great to get this on master.

Hey @tas50, sounds good. Let's get this into master. :-)


Anti Diagonal Traversal of Matrix

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Both codes in C++ and Python are written by me
Due to some wrong commits by me, code got deleted from previous PR #458
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #348

Please review sir @HarshCasper @iamrajiv @ankitaggarwal23 @atarax665 @gat786 @nidh-ish