Command line parsing overhaul.

 I scaled back those plans though, implementing an adapter from the proposed-new-world-order to the existing COMMAND_STRUCTURE infrastructure.
The current way vcpkg does command line parsing has been outgrown as we've added commands that don't speak installations. Examples:

We print help text for unrelated commands, e.g. triplet in search or new or add
We don't have help topics in vcpkg help for some commands. (not fixed here)
Paths aren't consistently handled. (sometimes --a=b, sometimes --a b)
We don't consistently handle switches. (Sometimes --no-foo is accepted, sometimes it is not)
We don't print good diagnostics

And there are some maintainability concerns:

Switch names and processing are duplicated so it's easy to declare switches without wiring them up appropriately
Shared switches (like --triplet) can't have their handling shared unless we special case them in the frontend (possible to fix with this infrastructure but not actually fixed here)
CommandStructure has a lot of things that lots of commands don't use.
We don't have good testing (or even ways to test) the parsing machinery since the definition of switches is combined with the parsing etc.
The existing "ICommand"-ish infrastructure results in needing to edit 3-4 places when adding commands for "extensibility" we do not use (and often have to work around). So we currently pay the tax of needing to declare MOUNTAINS of stuff in headers to make this declarative and available to other commands, but get no benefit from doing so.

Explicit non-goals:

Making commands entirely declarative. There is always going to be imperative code that needs to respond to commands, so I don't see substantial value in making it completely declarative. Note that this is a major design philosophy change vs. the previous design.
Allowing order-dependency between --switches and other entities. (that is, "a --arg value" and "--arg value a" should be equivalent)

Other notes:

In some cases we allowed multiple identical switches, and in other cases we did not. This implementation chose to not. (For example, --debug --debug was supported, but --keep-going --keep-going was not)

In a future PR I want to use the new CmdParser type to overhaul how commands are selected and give a more consistent handling of help commandname and autocomplete commandname
Resolves https://github.com/microsoft/vcpkg/issues/29015
Example diagnostic improvements:
Before: https://github.com/microsoft/vcpkg/issues/29015
After:

Before (why are you printing usage at me?):

After (Oh!):

Before (You're just going to ignore --xtree?):

After:

Before and after (can have spaces now):

Before (what arguments are you complaining about again?):

After (Oh!):

Drafting this because I need a solution for what happens with switches that are already named "no" or "no-". I think I'm going to fix it so that x-/z- and no- can occur in either order and flip the sense accordingly but not sure yet....

On my machine the z-applocal tests fail, but they also fail with the currently shipping product :shrug:

Filed https://github.com/microsoft/vcpkg-tool/pull/869 about that test failure

Why you should rewrite cmd parser, when many library for command line parsing exists such as https://github.com/CLIUtils/CLI11 and https://github.com/jarro2783/cxxopts .
I think in many situations using mature library is better than reinvented wheels , and we can achieve all benefits from library (for example CLI11 try to implement autocomplete or ...)

ITNOA

I don't know what this means.

@BillyONeal Why you should rewrite cmd parser, when many library for command line parsing exists such as https://github.com/CLIUtils/CLI11

This looks pretty close to workable but:

it is incompatible with our licensing
it is incompatible with localization

I'll keep it in mind if I get to do something completely new next time.

and https://github.com/jarro2783/cxxopts .

This doesn't look capable of mimicking our existing interface.

I think in many situations using mature library is better than reinvented wheels , and we can achieve all benefits from library (for example CLI11 try to implement autocomplete or ...)

I agree, that's part of why vcpkg exists in the first place. But an off the shelf solution drop-in compatible with our existing interface seems unlikely to be out there.

@BillyONeal You better know than me, but I think license of CLI11 is very flexible, and you can use it in all product, so I do not understand why you says it is incompatible.
for localization problem, I think we can use vcpkg message for declare all sentences and keywords, instead of raw string in CLI11, to support localization.

I do not understand why you says it is incompatible

They are 3 clause BSD, we are MIT. Therefore they would impose more restrictions on our customers than we currently require. (Notably, license notices added on all derivative works)

@BillyONeal I am not lawyer, but for you know, @phlptp says in https://github.com/CLIUtils/CLI11/issues/847
Every lawyer I have talked to on the subject has been of the opinion that the standard BSD 3-clause license and MIT licenses are equivalent and can be used freely in any project commercial or open source and used as components in projects licensed in other forms. The only functional difference is that the standard BSD 3 clause includes a non endorsement clause which is entirely appropriate for any software written by a government or government funded entity. All open source software we work on is BSD-3-clause if we want to it to be permissive.
@henryiii can speak to the original decision on licensing CLI11, but I don't see any reason to change the current license.
BSD-3-clause is a pretty standard license there is nothing unusual about it and you are perfectly free to include any project using BSD-3-clause license in an MIT licensed project with no legal issues. I have certainly seen it done many times.

BSD-3-clause is a pretty standard license there is nothing unusual about it and you are perfectly free to include any project using BSD-3-clause license in an MIT licensed project with no legal issues. I have certainly seen it done many times.

Our lawyers do not agree: BSD requires attribution in binary forms, MIT doesn't.
Either way, I don't think we're going there now. But we will look at something like that should we ever add another exe.

The bug I drive by fixed in https://github.com/microsoft/vcpkg-tool/pull/901 where x-set-installed had code to handle --only-downloads but didn't declare such is an example of the type of bug I want to shut down with what I meant by the "declaration isn't bound to the actual data".

Hm it seems that this broke command line parsing in https://github.com/microsoft/vcpkg-tool/pull/802. Before this PR
➜  vcpkg git:(master) ✗ vcpkg test-features --ci-feature-baseline=../Lichtsteuerung/vcpkg/scripts/ci.feature.baseline.txt libsbml
compute 15 install plans

1/15 libsbml[core]:arm64-osx
Detecting compiler hash for triplet arm64-osx...
^C

After this PR
➜  vcpkg git:(master) ✗ vcpkg test-features --ci-feature-baseline=../Lichtsteuerung/vcpkg/scripts/ci.feature.baseline.txt libsbml
error: while loading ci.feature.baseline.txt:
error: ci.feature.baseline.txt does not exist

Ok nvm my transformation from args.command_arguments to args.forwardable_arguments was wrong, I have to use options.command_arguments


An small problem, really need your help!

Hi Prof. Lee! @WeiHongLee
I really appreciate the wonderful work and really want to have a try. When I train each single model(for example, 'dtd'), there is error in meta_dataset.data.reader.py. There are errors in Line 245 and 246: self.base_path = self.dataset_spec.path self.class_set = self.dataset_spec.get_classes(self.split). Since the 'dtd' is str, I wonder the method for solving this problem. Thanks a lot!

Hi, you can check your python version. This code requires python3.6 or a greater version. Hope this can help!


DEBUG logging does not emit XML payloads from VTN

Where DEBUG level appears to configure VEN to print 2 instances of an XML payload, the VTN prints python dict representations of payloads. It would be very helpful to see the XML on both sides of the exchange to aid testing.

You're right; the logging of XML messages was inconsistent across the application. I've made some changes so that each side will debug-log every message that gets parsed and every message that gets created. Hopefully this is more useful.


Use default metadata port 8775.

This switches the default metadata port from 9697 (which is for neutron's metadata proxy) to 8775 (which is for nova-api, the service that actually provides metadata in Calico).

Some docs pages have been updated: the Calico Configuration page had the default value of metadata port changed to 8775, the Red Hat Packaged Install page had the change of the Metadata IP setting removed, as did the Ubuntu Packaged Install page.


bug: formatting no longer works after client reload

this is probably due to the fact that this plugin does NOT read formatted messages on-demand, rather it intercepts incoming/outgoing messages
the plugin works before reloading the discord client, after that it refuses to acknowledge any formatted messages

fr

Must first get motivation to fix this goofy ahh project


Add CRUD/FLS checks to RD2_PauseForm_CTRL

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

W-13641522


feat: Propagate VS Code identity to background processes

This change specifies user id / session id overrides in the environment of background processes to ensure a single thread of user activity.
As it turns out, we don't need to override VS Code's implementation of Session ID. It doesn't appear to ever renew within the lifetime of the window.
Depends on https://github.com/getappmap/appmap-js/pull/1191

I'm going to move this back to a draft for now. Another requirement has become clear and it may affect this PR.


Order of steps changed (step 6 moved to step 3)

launch.json needs to be created before "Download Symbols" are used, because the connection information are needed to download all dependencies from tha target server. (Otherwise VS Code is requesting to create a new launch.json file).

Thanks for your contribution!


Option to save comicinfo/metadata and poster on the manga root folder.

Describe your suggested feature
Save the metadata and the poster in the manga's root folder, so that it is easier to import it to other services.
Source
├── Manga Name
│   ├── Chapter 1.cbz
│   ├── Chapter 2.cbz
│   ├── Chapter 3.cbz
│   ├── Poster.jpg
│   └── ComicInfo.xml
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.16.5.
[X] I will fill out all of the requested information in this form.

Totally agree! This allows for better portability of downloaded comics.
Especially going through the migration from Tachiyomi to Mihon. I have a large number of manga downloaded in Tachiyomi that are not recognized in Mihon. Although it can be read, the icon shows that it has not been downloaded, and there is no response when clicking the download icon.
A similar scenario also occurred when I changed to a new phone and I had to re-download all comics to ensure that the download icon was displayed correctly.

Totally agree! This allows for better portability of downloaded comics.
Especially going through the migration from Tachiyomi to Mihon. I have a large number of manga downloaded in Tachiyomi that are not recognized in Mihon. Although it can be read, the icon shows that it has not been downloaded, and there is no response when clicking the download icon.
A similar scenario also occurred when I changed to a new phone and I had to re-download all comics to ensure that the download icon was displayed correctly.

That wouldn't have been necessary, you could have just invalidated the download index from the advanced settings.

很需要这个，我有大量来自Manga Manager标注的漫画，mihon暂时还无法识别元数据分组，软件目前的本地功能还是有些羸弱

I agree, this would be a great feature to easily convert non-local series to local series.


feat(collections/queue): feat vector-based queue page

Hi, @weihanglo I has updated. Plz review again, TKS.


Placeholder: Add a property to hide the button on view mode

Category
[x] Enhancement
[ ] Bug
[ ] Question
Version
Please specify what version of the library you are using: [latest]
Expected / Desired Behavior / Question
Add a property to specify if the placeholder button is hidden on page view mode.

Newly introduced property hideButton is available in the latest beta.
Sample usage:
<Placeholder iconName='Edit'
                     iconText='Configure your web part'
                     description='Please configure the web part.'
                     buttonLabel='Configure'
                     hideButton={this.props.displayMode === DisplayMode.Read}
                     onConfigure={this._onConfigure} />

This has been released with the latest 1.11.0 version.


fix(TDI-44413): fix big date values (#1681)

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-44413
Backport of https://github.com/Talend/components/pull/1681
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Components - Snowflake Definition .................. SUCCESS [05:05 min]
[INFO] Components - Snowflake Runtime ..................... SUCCESS [ 48.280 s]
[INFO] Components - Snowflake Integration Tests ........... SUCCESS [04:25 min]
[INFO] Components - Snowflake Aggregator .................. SUCCESS [  0.305 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:15 min
[INFO] Finished at: 2020-07-02T19:30:19+00:00
[INFO] Final Memory: 106M/1590M
[INFO] ------------------------------------------------------------------------

https://ci-common.datapwn.com/job/components_pull-request_master/411/consoleFull


Not detecting PC

No matter the settings the patrols never spot the PC right in front of them at all

Hello! It seems you haven't read the Before Posting an issue as indicated at the top of the Repository Readme The Issue has been closed.
If you are reporting a bug, feel free to follow the steps here (https://theripper93.com/info/issues) and reopen the issue with all the relevant information.


Wrong value with "precision: 4"

I'm setting the precision to 4, but this is formatting wrong.
if I enter the value 4 and 8 it is formatting like this: 4,8
but the correct one is: 0,0048

It was fixed in latest version.


Fix different ordering of gestures in calliope

fixes #583

Codecov Report

Merging #771 into develop will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #771   +/-   ##
==========================================
  Coverage      41.31%   41.31%
  Complexity      3697     3697
==========================================
  Files            634      634
  Lines          28214    28214
  Branches        2468     2468
==========================================
  Hits           11656    11656
  Misses         15748    15748
  Partials         810      810

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 0871881...d23cdc2. Read the comment docs.

Thanks a lot! Similar to the other blockly related one, can you create it over in the blockly repo with just the source files changed?


Updating link to Fuchsia blog post

Visiting the old link results in an Obsolete message.

Thanks for the patch!


coral-hive: added window function support

New test cases in ParseTreeBuilderTest.java ensures that translations from Hive ASTNode Tree to Calcite SqlNode Tree are correctly done.
The test cases in HiveToRelConverterTest.java ensure that Calcite SqlNode Tree to Calcite RelNode Tree are successfully done.  The Calcite RelNode Tree validation requires some additional work to ensure the correctness (which is called out as TODO in the test cases).

Thanks for the detailed code review @wmoustafa and @ljfgem ! Will address the review comments and let you know when I am done.

@wmoustafa @ljfgem  All comments have been addressed.  Can you take a look again?

Thank you @uzshao for this PR. Great to see window function support.


Add OptionalField for fields which can be None

Fields are optional by default except declared required explicitly. Using OptionalField is intuitive but may cause confusion.
class MyModel(Model):
    foo: Optional[int]
    bar: int

    class Meta:
        required = ['bar']

If introducing Optional, the feature of required should be removed at the same time.

The issue I had that I was trying to solve was in assigning None to optional fields. I figured that None was just not supported yet, thus the addition. Maybe I was just doing something wrong.
I'll experiment and attempt to reproduce my issue in the published version (currently my project is pointing at my fork) and get back to you here.

In the very early version, None was supported (later removed). If a field was not assigned, it would default to None.
When using this lib in my projects, I found it was kind of cumbersome to deal with None.  If 'empty' semantics was needed, I choose to assign a 'falsy' value like [], {}, 0.
But maybe in some cases None is necessary. Please go ahead with your experiments.

I played with the code a bit and I understand better how it works today. Longer explanation is below but TL;DR I would like to ability to mark a field as Optional so that a static type checker (mypy) will prevent me (and my fellow coders) from using it in an unsafe way.
The way it is currently, all fields are "optional" unless explicitly set as required (you said this above, I'm just restating). In the library's semantics, as is, this means you aren't required to set a value on the field, not that the value can be set to None. Instead, if you do not set the field and attempt to access it you will get a runtime exception. If you attempt to set the field to None, you get a different runtime exception.
In the builtin Python typing module, the Optional type indicates not that a value can be "unset" but that the value can be set to None. This is extremely useful for code which is statically checked with mypy as mypy will indicate when you have a potentially unsafe reference (e.g. trying to treat a value as str when it could be None).
My goal with this feature was exactly that, to be able to indicate to mypy that a field could be unset so it will warn when we use it in unsafe ways to help prevent errors. Ideally "unset" would be None instead of raising an exception since there are static checks for None and easier semantics for dealing with it (e.g. my_model.my_optional_str or "default_string_here" instead of try and except).
If you wish to retain the existing behavior (allowing fields to be unset when not included in Meta.required and raising exceptions when accessed) then perhaps OptionalField is a confusing name for it. Perhaps NullableField or NoneableField? I was just trying to align with the built in nomenclature.

In the library's semantics, as is, this means you aren't required to set a value on the field, not that the value can be set to None.
You are right. Without an Optional field, this library could not work well with some static checker.
Could I invite you an a collaborator?

I think OptionalField is a better name, so Meta.required seems need to be removed.

@cymoo I made a branch called "optional_field" in this repo now so you can more easily work on it directly. I removed references to "required" in metadata and updated some tests to use Optional fields. I fixed some issues that I found with the Optional fields in failing tests, but there are still a few more errors.
My understanding of the inner workings of the project is still pretty early. Will you take a look at that branch and help fix the tests that are still failing?


Limited Unbonding Chunks.

In light of not to be forgotten between BETA tasks + almost insubstantial.

A test would be good.


pandoc-plot v1.1.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

/azp run

Thank you!


Generate binaries for all platforms

Hi, this would be cool to generate binaries for all GO plateforms. This is a matter of minutes using GOX:
go get github.com/mitchellh/gox
gox -build-toolchain
gox

That's it!

Hi,
I have a fork. If you are interested:
https://github.com/gustavopaes/lanyon
tks


Add OpenTelemetry Proguard rules for compile-only annotations

What does this PR do?
There is the following Proguard error when trying to minify OpenTelemetry module:
ERROR: R8: Missing class com.google.auto.value.AutoValue (referenced from: io.opentelemetry.api.common.AttributeKeyImpl and 2 other contexts)
Missing class com.google.errorprone.annotations.MustBeClosed (referenced from: io.opentelemetry.context.Scope io.opentelemetry.context.Context.makeCurrent() and 3 other contexts)

In fact both these annotations are not needed in runtime, so it is safely to ignore them.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.56%. Comparing base (5197289) to head (88ff084).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2080      +/-   ##
===========================================
+ Coverage    68.46%   68.56%   +0.10%
===========================================
  Files          719      719
  Lines        26552    26567      +15
  Branches      4464     4472       +8
===========================================
+ Hits         18177    18214      +37
+ Misses        7179     7138      -41
- Partials      1196     1215      +19

see 30 files with indirect coverage changes


add command history

up and down arrows allow user to view previous commands

See comment on #24 for the approach being taken.

This feature has been implemented in 0.9.0


Not working with recent nightly 6.99

Using it with recent nightly release, it stop working.
I think because kicad programmer changed the option "SetExcludeEdgeLayer()

Hi,I didn't get the meaning.
We are in China time and just tried,it is workig well.
Could you tell me the details?

I am using the nightly version of Kicad:
Version: (6.99.0-2815-gbbc0c61ccb), release build in Windows 64
In stable version of kicad 6.0 Your plugin is working; in nightly version it doesn't work. The procession bar stop and the files are not generated.
In the python console the message is:'PCB_PLOT_PARAMS' object has no attribute 'SetExcludeEdgeLayer'

Thanks,I will contact with KiCAD team about this.

The line
        popt.SetExcludeEdgeLayer(True)

Should be
        if hasattr(popt, "SetExcludeEdgeLayer"):
            popt.SetExcludeEdgeLayer(True)

Thansk for the help,last time we didn't find the way out

it doesn't work wth the 7.0rc1 still. Please make sure it does, because many of us are using it and trying to push designs using this plugin.

Yes I agree. It is very unhandy to have this not working. Please fix it soon.

KEEP IN MIND THAT I'M NOT A PROGRAMMER....
so the modification are proposed without any warranty and i'm not responsible if you receive an incorrect board made with these modifications.
Hello, i have managed to make it working again by changing and adding some lines in the thread.py file, according to the changes made to another similiar plugin (AISLER):
modify from:
boardWidth = pcbnew.Iu2Millimeter(board.GetBoardEdgesBoundingBox().GetWidth())
boardHeight = pcbnew.Iu2Millimeter(board.GetBoardEdgesBoundingBox().GetHeight())
to:
boardWidth = pcbnew.ToMM(board.GetBoardEdgesBoundingBox().GetWidth())
boardHeight = pcbnew.ToMM(board.GetBoardEdgesBoundingBox().GetHeight())
----add:
angle = f.GetOrientation()
try: # kicad >= 6.99
angle = angle.AsDegrees()
except AttributeError: # kicad <7
angle /= 10.0
---before components.append({ statement.
modify from:
'rotation': f.GetOrientation() / 10.0,
to:
'rotation': angle,

Now we have solved the problem and updated the plugin that suitable for version7

still not available in Kicad itself tho.

Version 0.1.3 works for me in KiCad 7. Downloaded the plugin and installed manually. I assume version 0.1.3 will be added to the official KiCad plugin repository eventually.

We will add to the official KiCad plugin repository in gitlab soon


Do Solana validators prioritize transactions with security assertions?

We have an app that interacts with our Solana program at:
https://explorer.solana.com/address/iLEPWontSkuaCDeg8psrxB3mVHAA39fWWRtinSJcrtJ
I'm signing solana transactions in typescript,
by two means:

transactions signed by native solana browser extensions (SolFlare, Phantom) when sent using @solana/wallet-adapter-react useWallet sendTransaction

transactions signed via Magic.link's magic-sdk and then sent using a connection to RPC node created with @solana/web3.js

Option 1 is super fast, validated/confirmed in 3 to 4s
Option 2 (Magic) takes forever (up to 1 min), and most often fails
while inspecting the differences, I found out that on option 1) the transaction object has a 'compiledInstructions' array with five (05) instructions
but on option 2), even after signing, 'compiledInstructions' has only one (02) instructions
I found out that the instructions that are added by the wallet extensions are:
setComputeUnitLimit instruction
The other two that talk to the Lighthouse (Assertion Solana Program), as below:
#4 - Unknown: Unknown
Raw Interact With Unknown
L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95
Input Accounts
#1 - Account: AZAh9d3pdD9JaMFy734T1p9Yi1bUjHeYHUv2m8oqgncm Writable Signer Fee Payer
Instruction Data
3zkF6GTy
#5 - Unknown: Unknown
Raw Interact With Unknown
L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95
Input Accounts
#1 - Account: EPbrYBp5oCEb7eb6FtULdizy5CuESJLsgdfhbiJonTfS Writable
Instruction Data
8A8uiXy3AqR3n36X8SDrAtaSmDj5DpjX3bSqGkDY2g5iayUejwhgx4BUHD6F3KU7V89M
The above transaction sent with wallet extension is:
https://solscan.io/tx/UYceY467QU39u9pb9eLkbwJ9kT9hUj2NAe1eMwHN3SpAwY6Vvm8ou28aT6q41JR4i2RmQZjVVcYAFvMxUoNkZC5
An example of the txn signed and then sent with Magic is:
https://solscan.io/tx/2dx9gHfb5CygoLUGpWm1Pwmcv2uPp7fojrtyxHJddi8SWbqHqM9XA4AhCbgDmPAtujy8iVfzb7sWdv566MQVMD7x
(already added the computeLimit instruction to this one, but didn't solve the issue)
I'm trying to add the Lighthouse assertion instructions to the txn to be sent with Magic too.
But after days debugging this, I'm not sure it's the right path.
I failed trying to run the latest lighthouse-sdk with our app, which uses @solana/web3.js 1.95 still.
I tried to install @solana/web3.js v2 and use it with lighthouse-sdk, but no good.
Then I copied over the code from the SDK into my local files, tried to import stuff directly from solana/web3 v2, no good.
I spent some 2 hours reading the source code, console.logging, trying to get a handle on the encoders logic.
I'm making process, but excruciatingly slowly. We lost a bunch of users cause Magic txns are not going through.
I'm asking for help anywhere I can.
Any pointers?

Just saw the instructions on how to use lighthouse-sdk-legacy.
Trying it out now.

Can´t use it out-of-the-box either, it seems, I get a:
Uncaught Error: Module not found: Package path ./dist/lib/client is not exported from package .../zbet-web/node_modules/rpc-websockets (see exports field in .../zbet-web/node_modules/rpc-websockets/package.json)

We apologize for the inconvenience you’re experiencing. For personalized assistance, please contact our support team directly.
Ticket ID:SOL678
Solana support
To start a chat with a live support agent, click the live chat icon at the bottom corner of the page.

Tried to install this repo and run the tests locally. But I'm getting a lot of crate compatibility errors.
Seems like rust compiler can't find compatible candidates on crates.io:
    Updating crates.io index
error: failed to select a version for the requirement `spl-pod = "^0.1.1"`
candidate versions found which didn't match: 0.5.0, 0.4.0, 0.3.1, ...
location searched: crates.io index
required by package `spl-token-2022 v2.0.1`
    ... which satisfies dependency `spl-token-2022 = "=2.0.1"` of package `lighthouse-program v2.0.0 (/media/st/Rígido/perion/lighthouse/programs/lighthouse)`

For anyone facing a similar compiler issue, I had to manually patch 7 crate versions to get the compilation to start:
[patch.crates-io]
solana-program = { git = "https://github.com/solana-labs/solana", tag = "v1.18.8" }
solana-program-test = { git = "https://github.com/anza-xyz/agave", tag = "v1.18.8" }
spl-pod = { git = "https://github.com/solana-labs/solana-program-library", rev = "950efde" }
spl-transfer-hook-interface = { git = "https://github.com/solana-labs/solana-program-library", rev = "950efde" }
spl-type-length-value = { git = "https://github.com/solana-labs/solana-program-library", rev = "950efde" }
solana_rbpf = { git = "https://github.com/solana-labs/rbpf", tag = "v0.8.0" }

I was able to install lighthouse-sdk-legacy by manually editing the node_modules installed.
Specifically the solana web3 imports that were failing to identify .cjs files as default exports from a folder.
Adding the .cjs extension to the imports in the solana packages (in node_modules) solved the issue.


[Feedback]Command  Not Found

Page: /cli/start/install
Feedback:
bash: amplify: command not found - Unable to install Amplify - amplify configure gives me a command not found message.

yes, I am. Thanks


Update Node Requirements

When installing via npm it get the following warning:
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">= 0.10.0 <= 0.11.0"} (current: {"node":"2.0.0","npm":"2.9.0"})
With newer versions of Node available, it would probably be a good idea to test this lib with newer versions, and update the package.json to reflect the changes.

Also getting this error in the tsd project

This one fails our CI builds...

@Bartvds

As a temp solution puting --force flag while install the packages like: npm i --force - but of course it's not a solution at all!


Seed bootstrapping fails

What happened:
#1863 introduced a bug which causes the Seed bootstrapping to fail for a new Seed.
Bootstrapping fails on apllying the newly introduced VPA kube-state-metrics-vpa (see here):
time="2020-02-14T11:10:05+01:00" level=error msg="no matches for kind \"VerticalPodAutoscaler\" in version \"autoscaling.k8s.io/v1beta2\"" seed=local-seed

It looks like the issue here is the order in which we apply the rendered resources (VPA created before VPA CRD is created).
What you expected to happen:
Seed bootstrapping to succeed.
How to reproduce it (as minimally and precisely as possible):

Spin up a cluster somewhere.
Register it as a seed.

Anything else we need to know?:
Environment:

Gardener version:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

Duplicate of https://github.com/gardener/gardener/issues/1871?

Wasn't this error message present only until the vpa components are started?

Duplicate of #1871?

No, this is the actual Seed Bootstrapping that fails, not the installation of the ControllerInstallation's MR.

Wasn't this error message present only until the vpa components are started?

The vpa components won't come up, because they are part of the same chart and the chart applier fails and returns before it can apply the vpa components...

The vpa components won't come up, because they are part of the same chart and the chart applier fails and returns before it can apply the vpa components...

In the next reconciliation the VPA CRD is installed and then also the VPA CRs should be able to get created.
The root cause is the same like in #1871, so I suggest closing one issue.

After a deeper look it turns out that the root cause here is indeed completely different: Our Kubernetes applier returns an error if it cannot create/update a resource, causing the subsequent resources to not be considered at all. Hence, it will never succeed because the VPA CRD is coming after the VPA CR for the kube-state-metrics.
Eventually, we should switch to using the gardener-resource-manager for the seed bootstrapping (which will also allow an easy implementation for cleaning up the created resources when the seed shall be deleted/disconnected). Though, we should still fix the applier the continue with the other resources and return a combined error at the end.

/assign
I will take care of the fix for the chart applier to return a combined error.


Screen and Display bases

Quick test making bases for Screen and Display so it's possible to do typing. The Screen and Display types are dynamically overridden by the platform specific types so it's impossible to do anything related to typing with those.
Accidentally whitespace trimmer on. Can revert that if needed.

There is another way to hack around his


Add color to CLI output

Added a Color enum with ANSI color codes, and a color function that takes an std::string and a Color and returns the string colored that color.
Usage:
std::cout
    << color("this will be green\n", Green)
    << color("this will be red\n", Red)
    << color("there are other colors but im not gonna type them all\n", Bold);

Why not a stream-friendly implementation, like this? Also, not really sure about doing more stuff in legacy.


Closes issue #4192 (second attempt)

Because we must use different names for the text for "Following" from the channel page and another text for the sidebar panel and another for searh list options. Currently is the same text everywhere and can't be translated separate.
And most interestingly:

the message that a new user is receiving after first channel subscription is "Awesome! You just subscribed to your first channel." with the label "Subscriptions 101" as you can see in the file ui\modal\modalFirstSubscription\viewjs.
everywhere in the app (in over 20 files) is used the word subscriptions and subscribed as in:
(import { selectSubscriptions } from 'redux/selectors/subscriptions';)
(subscriptions: selectSubscriptions(state),)
(subscriptions: subscriptionsReducer,)
many commented lines in the code like:
//   Populate a channels unread subscriptions or update the type
// Remove multiple files (or all) from a channels unread subscriptions
// If no channel is passed in, remove all unread subscriptions from all channels
// if the user isn't sharing data, keep the subscriptions entirely in the app
// They are sharing data, we can store their subscriptions in our internal database
Lbryio.call('subscription', 'new', {
channel_name: subscription.channelName, etc.
even the files from redux (actions, reducers, selectors) folder are named subscriptions.js
ui\store.js uses: const subscriptionsFilter = createFilter('subscriptions', ['subscriptions']); and const whiteListedReducers = [...   'subscriptions',];
and most interesting:
const sharedStateFilters = {
tags: { source: 'tags', property: 'followedTags' },
subscriptions: {
source: 'subscriptions',
property: 'subscriptions',
transform: function(value) {
return value.map(({ uri }) => uri);
},
where we can see the use of the "subscriptions" and "followed tags" string also.

So with so many examples in the code, why not use the same term in the program interface too? But the main reason is that we need to separate the instances where the "following" word is used.
An alternative for using "Subscriptions" is that we can use "Followed channels", but I think is too long. So do you have any real reason for not using Subscriptions? After all, we must use other word in side panel instead of the "Following" which is inappropriate at least in other languages.
PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number:
#4192
What is the current behavior?
What is the new behavior?
Other information

@TigerxWood Just because we use certain words in our code, doesn't mean we need to use the same words in the UI.
I'm going to close this. We do not plan to switch back to "subscribers" for the time being.

Again, did you read carefully what I said? That code examples was just as a side note to add an additional motive for using the word subscription. Personally I am not as attached about Subscription word, I choose it because was suggested in the opened issue by somebody.
The main problem instead is, that we need to use 3 different words in those 3 different places: content page, side panel and filter in the search box.  Closing it I don't think is a solution without any proposed alternative. After all, it's an opened issue by someone else and a problem  for translation for many other languages, including my language. I saw this problem when I was translating it, but instead of opening an issue I tried to make a compromise, not very good it seems. When a friend asked me what means that word in the side panel I explained him why is this, because is the same word used in the content page to show you that you are following a channel and I was waiting to see if other languages have the same problem. And it seems they have even opened an issue about that before me.
So, my alternate solution to subscriptions, as I said above, are "Following channels" (in side panel), "Following" (on page content, as it is now) and "Followed" (in the search filter, where it's about filtering the followed content). If you have another suggestions I am glad to hear them, but we need to use 3 different words in those places.
And by the way, the same problem is with the word "Repost" from page content and filter from the search option, where should be another word, for example Reposted (which is more apropriate even in English, because it's about filtering only reposted content).
And if you want to understand why I am so invested in updating the strings (there are still more that are missing) and having a good translatable interface is because on one hand, a interface partially translated make an impresion in other languages of an application half baked, hard to understand, and on the other hand, and the main reason, is that many people from other languages, including myself, want to translate the main site, especially the FAQ section. Where, as we can see, are used many examples with screen captures in them. So, we can't make screen capture with half translated strings or innaproriate translations. It's not enough just to translate the application, just like any classic application. To understand fully what this application is about you need more informations that you can find it only on the main site, which should also be translated to make the app really international. That milestone I want to be reached as soons as possible.
When I started to translate the site, soon I realised that I can't go further without a basic good translatable interface and I had to intervene in the source code to repair these problems. So, now instead of going forward with my translation, I am moving in circles, by fishing missing strings and trying to explain why they should be that or that. I am the main proofreader and translator in my language for the Proton applications. And I can assure you that this application is top notch in terms of professional translation in my language. Almost everyday, they update the strings for translations, even if is just because of a missing dot after a sentence. And I love their dedication for this. And I want that for LBRY also. To have a perfect translated interface that make a professional impresion in as many languages as possible. That's why is called Library after all, right? To be available to everyone.
I am sorry for the long message I know you are busy with the code, I just wanted you to understand my point of view that as exciting may be some new features to the app, they are not so appealing if the users can't understand them in their native language. And because in English some words can be used in different places with different meanings, in other languages the nuances make a big difference.
I hope that you will reconsider this closed issue #4192 and help me further to achieve my goal to make all strings translatable as soon as possible.
Have a great day

If I understood both of their requests correctly, I believe it is something I've encountered before in my other projects.
I think what they are saying is that while an English word can be re-used safely in different contexts, other languages might not.  The problem then lies in how we are using the English database (if memory serves) --> we assume the key and value is identical.
One possible fix to
(1) use the English database the same way as other languages, and
(2) treat key as a string ID.  In the string ID, we can add some "context" help in the key to make it unique. (In my other project, we use an enum as the ID).
The end result would be something like this:
English (all resolves to the same value):
"Following !!Used in sidebar!!": "Following",
"Following !!Used in bottom bar!!": "Following",
"Following !!Used in other bar!!": "Following",

French
"Following !!Used in sidebar!!": "Abcdefg",
"Following !!Used in bottom bar!!": "Xcdhfue",
"Following !!Used in other bar!!": "Whatever",

Client side:
 label={__('Following !!Used in sidebar!!'}

Changes needed:

Make English use the value, just like in other languages.
The Transifex process probably needs to change a bit to accommodate this.

It's not a trivial change, but not too complex either.

Well I don't think the English is so poor in words and even in this case I think using the same English word in different contexts is inapropriate. And instead of complicating the source code we just need to use the right words as it need. Because as a programmer, maybe for you is very clear what it means, but is not necessarly the same for a user, especially for a new one. Even Youtube use the Subscriptions word for subscribed channels and Subscribe for the button to subscribe to a channel. So, I don't know why do we need to reinvent the wheel when there are already consecrated words and additionally want to attract more youtubers into the LBRY?

Ohh, I forgot. Many youtubers import the same videos from the Youtube or upload the same video to LBRY and Youtube and somewhere in the video they say "Hit that Subscribe button below to subscribe to my channel" So my question is: what subscribe button? I don't see any. So in this situation he looks like he don't know what he is talking, because there is no subscribe button, right? In this case we need to mirror exactly, where is the case, the words used in the Youtube interface.


Allow options to specify ACL of reduced image

In the current implementation, it's not possible to specify the ACL of the image about to be reduced.  Instead, the ACL from the original image is read, which is not always desired and could have unexpected results.  This commit uses the ACL from the config and will use the generally specified ACL if none is available in the reduce object.

@akfreas Thanks!


editors/vscode: Add working file parent directory to include path

Adds the path of the working file to the include path when invoking
the compiler. Without this the compiler fails to resolve imports as
the file it is invoked on is in a temporary directory, without any
of the other source files present.

thanks!


dependsOn not working for app Insights resource

Bicep version
Bicep CLI version 0.14.46
Describe the bug
I have following bicep code:
module appinsights 'bicep/modules/appinsights:latest' = {
  name: 'WebAppInsights'
  params: {
    insightsName: 'WebAppInsights'
    tags: tags
  }
}

module webappz 'bicep/modules/app:latest' = {
  name: 'webapp'
  dependsOn: [
    appinsights
  ]
  params: {
  siteConfig: {
      linuxFxVersion: 'NODE|14-lts'
      appSettings: [
        {
          name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'
          value: reference(resourceId(resourceGroup().name,'Microsoft.insights/components/', 'WebAppInsights'), '2020-02-02').ConnectionString
        }

To Reproduce
first run  - fails
"code\": \"ResourceNotFound\",\r\n    \"message\": \"The Resource 'Microsoft.insights/components/WebAppInsights' under resource group 'xxxx' was not found
Run second time - works, because WebAppInsights was already created in the first run.
Additional context
How do I create both application and its application insights, using modules, with bicep?
Do I really have to have 2 separate bicep files, because of creation order/dependsOn not working?

We plan to fix this execution graph issue to not evaluate module params so agressively. In the meantime, the best workaround for this would be to construct an existing reference inside of bicep/modules/app:latest so that you don't do the manual reference() in the param.
So bicep/modules/app:latest would look something like:
param webAppInsightsName string

resource webAppInsights 'Microsoft.Insights/components@2020-02-02' existing = {
  name: webAppInsightsName
}

var connectionString = webAppInsights.properties.ConnectionString // use this value wherever you need it

Hi Alex, Thanks for the reply,
I have managed to make it work with outputs (I save webAppInsights.properties.ConnectionString as output)

Going to close this regardless since we have a workaround. The execution graph issue is tracked internally here: https://msazure.visualstudio.com/One/_workitems/edit/7512374


Modify Page of Post Job Opportunity

###Following changes to be made
1.) Box around the form that will look attractive
2.) Shift search bar corner / add login option

@abdus can i work on this?

@saumyasrivastava08 @abdus  Can I work on this issue please, I am GSSoC2021 participant.

Can i work on this issue?

cc: @vaishali614

@saumyasrivastava08 @rutuja2229 We appreciate your interest, but we assign tasks on First come first serve bases. So @saumyasrivastava08 you can take up the task. And @rutuja2229 how about, going through some other task?

@saumyasrivastava08 There's a small addition on top right there will be a search bar and a login/sign up button beside it.  In case you can't figure it out, ping me I will share pen paper design

@saumyasrivastava08 There's a small addition on top right there will be a search bar and a login/sign up button beside it. In case you can't figure it out, ping me I will share pen paper design

yeah sure make it attach it here and i will start working on this and label this as gssoc.
Thanks

@saumyasrivastava08

@saumyasrivastava08

okay done
add gssoc label

and where is our channel on discord there are channels for every community but where is ours @Manvityagi

please assign me

and where is our channel on discord there are channels for every community but where is ours @Manvityagi

#opportunity-calendar-frontend
#opportunity-calendar-backend


Stemcell for s390x architecture on Xenial

Hi there,
Xenial now supports s390x architecture.  I wonder if we can have s390x based Stemcell in preparation for attempting Cloud Foundry deployments.
Thanks.

Hi @rishigits ,
If you want a 390x-based Xenial stemcell soon, you may want to try to build your own. A good place to start would be here.

Thanks @cunnie - I am already looking at that and running into some issues specifically related to image_create/image_install_grub stages.  Apparently grub does not work on s390x architecture and code will require some adjustments.  Incidentally, would you or anybody know in what capacity BOSH uses grub.
Many thanks.

@rishigits just to properly boot the system. nothing special i believe.

Closing due to inactivity. Feel free to reopen or join discussions on slack.cloudfoundry.org#bosh with specific questions if you start investigating this route. Currently we're only producing Ubuntu Trusty stemcells, so this is probably first blocked on a Xenial stemcell, mentioned in #1249.


StellarGraph info method does not give information on numerical features.

Describe the bug
When I provide networkx graph and features along with it:
Gs = sg.StellarGraph(G, node_features=node_features)
if the graph G already has some attributes assigned, will they be used in training or not?
If the node_features are provided and the graph has attributes, StellarGraph shows only the graph attributes in the info method and for some reason, node features provided directly in the node_features argument are not shown in the summary:
> Gs.info()

 StellarGraph: Undirected multigraph
 Nodes: 2010, Edges: 2013

 Node types:
  default: [2010]
        Attributes: {'degree', 'star', 'betweenness'}

To Reproduce
Steps to reproduce the behavior:

Create a NetworkX graph with node attributes.
Create a StellarGraph object Gs with numerical features provided in the node_features argument.
Information in Gs.info() only shows the original node attributes, and no information on the numerical features is given.

Expected behavior
Information on the features actually used for the ML algorithms is shown.

Any updates on this?

Hi @gijswobben, in #979 we added an extra line to give more info, e.g. on the Cora dataset, info now looks like:
StellarGraph: Undirected multigraph
 Nodes: 2708, Edges: 5429

 Node types:
  paper: [2708]
    Features: float32 vector, length 1433
    Edge types: paper-cites->paper

 Edge types:
    paper-cites->paper: [5429]

And on the MovieLens which has two node types with different feature sizes:
StellarGraph: Undirected multigraph
 Nodes: 2625, Edges: 100000

 Node types:
  movie: [1682]
    Features: float32 vector, length 19
    Edge types: movie-rating->user
  user: [943]
    Features: float32 vector, length 24
    Edge types: user-rating->movie

 Edge types:
    user-rating->movie: [100000]

(Note the Features: ... line.)


Fully automate dev setup with Gitpod

This commit implements a fully-automated development setup using Gitpod.io, an
online IDE for GitLab, GitHub, and Bitbucket that enables Dev-Environments-As-Code.
This makes it easy for anyone to get a ready-to-code workspace for any branch,
issue or pull request almost instantly with a single click.

Thanks much for the pull request.
I realize this model makes it very easy for people to submit pull requests. However, "pull request almost instantly with a single click" is exactly the sort of model we would like to avoid.


[Bug]: Unable to delete DOI from a source

Steps to reproduce the bug
1.Make a new source
2. Add a DOI (not necessarily a valid one) in the appropriate field
3. Save the source
4. Open the source again
5. Delete the DOI
6. Click "Save"
7. Watch the DOI reappear

Editing the DOI works as expected.

Screenshot
DOI entered:

DOI deleted:

DOI returns:

Expected behavior
When I delete the DOI from the field, I expect the field to be blank after I save it.
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
0.35.1
Browser Used
Firefox

Adding DOI to a field automatically creates an identifier. Please delete using radial.

Thanks for showing me that process @proceps.
Unfortunately, attempting to delete the DOI using the radial isn't working either---clicking the red trash icon brings up a dialogue box saying "You're trying to delete this record. Are you sure want to proceed?", and after clicking "OK" the identifier remains visible.

@jlpereira I confirm, I cannot delete doi as identifier from the Source. not from the task, not from radial.

It's a backend issue, it seems global identifiers doesn't belong to a project. That could be the problem why we can't access to them, if you try to access directly it gives you a 404 response, same if you try to delete them.
I'm going to assign this one to Matt


Setup instructions unclear

Thanks for putting the time to release this jest module. The first step in the instructions is
At the top of your test file:

import {matcher, serializer} from '../src'
expect.addSnapshotSerializer(serializer)
expect.extend(matcher)

I feel like I'm missing something. Where do matcher and serializer come from? I'm using create-react-app in my project, if that's worth mentioning. As it is, jest complains that it "Cannot find module ../../src".

Sorry, my bad, the docs have been updated. Good luck!

@kentcdodds Thanks for the fast reply, I think it works. Just need to figure out the second error.


Fix CSI CI (Update CSI Sidecar versions)

What this PR does / why we need it:
Cinder CSI is breaking with sidecar containers update to CSIv1.0.0
Using older version until cinder driver updated to 1.0.0
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:
NONE

/assign @dims

/override cloud-provider-openstack-acceptance-test-flexvolume-cinder

/lgtm
/approve


Docs: add more nodes for --cloud-nodes

What type of PR is this?

/kind documentation

What this PR does / why we need it:
two points here:

update description about convert.

this update is for better understating.
the command below is to convert with one node as a cloud node. same as the logic thought.

add a note, how to use "," to add more nodes for --cloud-nodes params

this is useful when we deploy our openYurt cluster.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

other Note

/assign @yixingjia
please have a look.

@adamzhoul Very appreciate you for improving the document of OpenYurt. and welcome you to apply for OpenYurt community member. you can get apply example here: https://github.com/openyurtio/community/issues/23

@adamzhoul Very appreciate you for improving the document of OpenYurt. and welcome you to apply for OpenYurt community member. you can get apply example here: openyurtio/community#23

@rambohe-ch  thanks for your inviting. will do it soon.

/lgtm
/approve


Update index.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @scjane 👍


Added documentation snippet to show how entities can be tagged and added to Quick Launch

Added documentation snipped to show how entities can be tagged and added to the quick launch.
The documentation snippet can be found in the Catalog Items YAML Syntax

Very nice idea @tbouron. Done. :)


Validate channel inputs

When linking a channel, we should validate the channel identifier inputs. For instance, whatsapp channels expect numbers, so we should normalize and validate it. This way, we can prevent users from linking two channels with the same number but different spacing.

@SmittieC is there any more to do on this or can we close it?

If we want to validate facebook / slack inputs as well, then yes. Maybe not needed?

If we want to validate facebook / slack inputs as well, then yes. Maybe not needed?

We are already validating slack but fine to keep open for facebook.

I don't find a reliable way to verify a facebook page ID. There's this handwavy method, but I'm not sure how much I trust that in the longer term. I think until we have more people using this and starting to get issues, we can revisit. Closing this out for now


Make installation more faster

The installation script should not clone the whole commit history. By adding --depth=1 it will clone only the latest commit history and make installation process more faster.

:+1: For more fasterer :checkered_flag:! Good spot!


SNBT Parser cannot parse negative numbers in IntArrays

Title...
Attempting to parse an integer array fails with a SyntaxError if the array contains a negative number.
This effectively means that any SNBT containing a UUID fails as those are length 4 Integer Arrays and UUID format guarantees a negative number here.
A simple check to confirm:
StringNbt.Parse("{uuid:[I; 0, 0, 0, -1]}");

throws
System.Data.SyntaxErrorException: 'Syntax error at index 19: Invalid character '-' in integer array.'

Well, that is an embarrassing oversight on my part, no clue how I let that happen....
I don't have the code on my current machine to test with, but the fix would likely also require and additional check to ensure the - is the first character, and not just anywhere within the string (e.g. -123 is valid, but 1-2-3- is not). Either way, it will be a trivial fix to implement, thank you for taking the time to report.


Compile error

Hi, everything works fine in Arduino, but when I try to include the header via declaring
#include "hw_rng.h"
in some test code...
I get the following error:
In file included from ../arm/random.cpp:10:0:
/Users/player1/Synced/Documents/Arduino/Libraries/hw_rng/src/hw_rng.h: In static member function 'static void SimpleHacks::HW_RNG::fill(T&)':
/Users/player1/Synced/Documents/Arduino/Libraries/hw_rng/src/hw_rng.h:141:61: error: expected ',' before ')' token
             static_assert(sizeof(size_t) >= sizeof(uint16_t)); // 1999 ISO C standard (C99): size_t is an unsigned integer type of at least 16 bits
                                                             ^
/Users/player1/Synced/Documents/Arduino/Libraries/hw_rng/src/hw_rng.h:141:61: error: expected string-literal before ')' token
In file included from ../arm/random.cpp:10:0:
/Users/player1/Synced/Documents/Arduino/Libraries/hw_rng/src/hw_rng.h:142:41: error: expected ',' before ')' token
             static_assert(sizeof(T) >= 0);
                                         ^
/Users/player1/Synced/Documents/Arduino/Libraries/hw_rng/src/hw_rng.h:142:41: error: expected string-literal before ')' token
make: *** [arm/random.cpp.o] Error 1

14:38:10 Build Failed. 5 errors, 3 warnings. (took 354ms)

I'm using a version  of Eclipse called Sloeber which is optimized for C/C++ Arduino compatible development.

Aha.
After snooping around, it seems the version of arm-none-eabi-gcc in Arduino was 7-2017q4 whereas the one pulled for the Sloeber (old Adafruit 0.9.3 nRF52840) was 5_2-2015q4
Relinked and it works.

Nice!  Glad you were able to find the root cause, and to fix it.


No title slot on several ships (Spanish version)

I've just noticed that several ships with existing Titles doesn't actually have the slot to equip them. I believe the reason is the new translated names on most of them, but there is also the Y-wing which was already translated. The ships are:
-Y-wing (both Rebel and Scum)
-Aggressor
-StarViper
-M3-A Interceptor
-VT-49 Decimator

Still need the actual translations, but at least the stubs are there.


Sponsored issue: Stats Card Alignment

Stats Cards should be centered aligned and the width shouldn't be more than 265px to follow the same boxy styled.
Attaching both before and after styling applied ss
Priority Support

@musharaf-faheem is using  Mintycode to fund this issue.
If you want to accept  bounty for solving this issue join Mintycode.

Hey Musharaf!
Could you please attach the screenshot so I could understand the issue better?

Hi There,
I have attached the images in the ticket as well, sending you here as well
in case they aren't visible to you.
Thanks.
On Tue, 7 Nov 2023 at 12:21, Gaurav Shukla @.***> wrote:

Hey Musharaf!
Could you please attach the screenshot so I could understand the issue
better?
—
Reply to this email directly, view it on GitHub
https://github.com/EddieHubCommunity/BioDrop/issues/9741#issuecomment-1797942914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDV44CMAZNPYWNF5RJSQNLDYDHOPZAVCNFSM6AAAAAA7AWEOYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJXHE2DEOJRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Mushi
Full Stack Software Engineer
https://www.linkedin.com/in/mushi-faheem/

Thank you for raising the issue, the issue is unclear because it is not using our issue template, thus labels are not automatically added correctly and therefore does not trigger the appropriate GitHub Actions. This causes confusion within the community (as already seen above) and extra work for the maintainers.
When clicking on the provided link to the Minty platform for more information as suggested, it requires registration on that platform.
As the issue is unclear and this process is not part of our current workflow, I will close this issue.


Hide preroll libraries from Home page

Just wondering if there's a way to hide the pre-roll libraries so that they're still accessible by the plugin but don't show up on the Home page next to Movies, Shows, Music, etc.
Thanks.

Unfortunately no, at least none that I am aware of at the moment. This is next on my roadmap though. When making the switch to libraries, to provide the meta data based selection, I briefly looked for a way to hide certain libraries from everyone but the Admin while still allowing the plugin to show content from it to all users (I had done this with Channels before but this always felt too hacky and the wrong way to organize this type of content).
I will need to do a deep dive into the Jellyfin source code to get a sense if this is even possible with a plugin and it could be time consuming. I didn't want this to hold up the release of the updated plugin because alot of work was done to provide the new selection options. I thought it best to get the new version out there. I'll mark this as an enhancement and keep the thread open. Not sure when I'll get to it but it will be the next thing I do. Hope you enjoy the plugin and thanks for starting the discussion!

Also, what I have done in the mean time is name my pre-roll libraries "z Trailer Pre-Rolls" and "z Feature Pre-Rolls" so they appear at the end of the library list by default. It's far from a perfect  workaround.

Great. I look forward to checking it out.

I'm glad you're looking into this! In the meantime the "far from a perfect workaround" of naming the libraries starting with z actually does help so thank you for that suggestion


CORTX-31043: Exit on helm failure

Description
This change causes the deploy script to exit immediately if any helm install command fails.
Type of change

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates

Applicable issues

This change fixes an issue: CORTX-31043
This change is related to an issue: #

How was this tested?
This was tested by:

Running ./deploy-cortx-cloud.sh specifying namespace with invalid characters ("Bad-namespace!")
Verified that deploy works through normal path

Checklist

[x] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
[x] All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change addresses a CORTX Jira issue:

[x] The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

Just for future reference, "This change fixes an issue: CORTX-31043" is referring to https://jts.seagate.com/browse/CORTX-31043


routinator: 0.8.0 -> 0.8.1

Motivation for this change
Upgrade to 0.8.1.
Things done

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

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

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

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

1 package built:

routinator


Docker template

Add a Dockerfile template for deploying
Consume nats credentials env variable
Run nats docker locally if not already running

@sharipalik I updated the terraform file structure in this PR and this other one https://github.com/SpiffInc/events/pull/5
Let me know if that looks better


the training process may get into stuck

after I enter python tools/train.py configs/libra_rcnn/libra_faster_rcnn_x101_64x4d_fpn_1x_copy.py
it shows
INFO - workflow: [('train', 1)], max: 20 epochs
and get stuck

Please use the Error Template.
This bug could caused by many reasons, we cannot do much help here without information required in the Error Template.


Is Task support via DAV possible yet?

Title says it all. I very much look forward to using this plugin as I find the tasks integration lacking in too many places, especially when it comes to other programs that already store my calendar and task events as DAV.
So: Is this already possible?
If yes: HOW?
:)))
If not: is it planned?
If yes: How high is it on the priority list?
THANKS for this VERYPROMISING implementation.

duplicate of #45 and #25.
CalDAV sync is a tough nut to crack, task support is one of the next things up after #103.

I am sorry about this. I did search for task related issues but it is a little difficult to navigate the many requests. Glad to see its next up on the list.
and ... THANK YOU!


centos6.5 can't install python2.7-devel

I was facing the issue when excuting make apps:

"Error: must have python development packages for 2.7. Could not find Python.h. Please install python2.7-devel".  Stop.

the default version of python-devel is 2.6.6 in centos6.5, how can i upgrade it to 2.7

Only Centos 6.8 and more are tested/supported starting from Hue 4.3
http://cloudera.github.io/hue/latest/administrator/installation/dependencies/#centos-6-8-6-9-os
If you need Hue 4.2 or less


Squiz.PHP.EmbeddedPhp false positive when using PHP short open tag

Describe the bug
When the short_open_tag ini directive is enabled, the sniff Squiz.PHP.EmbeddedPhp raises a false positive error for code that uses a single-line statement with the short open tag.
Code sample
<? echo 'This is a short open tag'; ?>

To reproduce
Steps to reproduce the behavior:

Enable the short_open_tag ini directive in the PHP configuration file.
Create a file called test.php with the code sample above.
Run phpcs --standard=Squiz --sniffs=Squiz.PHP.EmbeddedPhp test.php
See the error message displayed

FILE: test.php
----------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------
 9 | ERROR | [x] Expected 1 space after opening PHP tag; 2 found
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

Expected behavior
PHPCS should report no errors.
Versions (please complete the following information)

Operating System
Ubuntu 24.04

PHP version
8.3

PHP_CodeSniffer version
master

Standard
Squiz

Install type
git clone

Additional context
The sniff assumes that there is always a space after the PHP open tag that is part of the content of the T_OPEN_TAG token. That is true for the PHP long open tag, but not for the PHP short open tag. When processing a short open tag, the sniff "sees" an extra space that doesn't exist, causing it to report the error, saying that it expected one space but found two.
Here is the code which was added in 3172a21:
https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/ac5fd07fa2db2335fd739e19c34e39ad923bc758/src/Standards/Squiz/Sniffs/PHP/EmbeddedPhpSniff.php#L381-L386
I believe the sniff should be fixed by changing the if condition highlighted above to differentiate between the short open tag and the long open tag when the directive short_open_tag is enabled. This could be done by checking the value of $tokens[$stackPtr]['cotent']. I wonder if there is a better way to do it.
Please confirm

[x] I have searched the issue list and am not opening a duplicate issue.
[x] I have read the Contribution Guidelines and this is not a support question.
[x] I confirm that this bug is a bug in PHP_CodeSniffer and not in one of the external standards.
[x] I have verified the issue still exists in the master branch of PHP_CodeSniffer.

@rodirgoprimo Nice find. Low priority to fix as it is uncommon for short open tags (not echo) to be enabled, let alone used.

I believe the sniff should be fixed by changing the if condition highlighted above to differentiate between the short open tag and the long open tag when the directive short_open_tag is enabled. This could be done by checking the value of $tokens[$stackPtr]['cotent']. I wonder if there is a better way to do it.

I don't think the directive short_open_tag needs to be checked, as if it is off, <? would not be tokenized as T_OPEN_TAG and wouldn't trigger the sniff.
Checking with the current condition + a content check for stripos($content, '<?php') === 0 should be sufficient I think ?
Note the use of stripos() - it should also be ensured that there are tests with <?PHP to safeguard that this new condition is properly covered.

Thanks for checking, @jrfnl. I agree that this is a low-priority issue, as you said. It seems somewhat straightforward to fix it, so I might give it a try if I have some time in the next few days.

Noting here that I found a scenario where this bug, combined with another sniff, can cause a parse error. Running the following PHPCBF command against the same code sample used in the description of the issue will result in invalid PHP file.
phpcbf test.php --standard=Generic,Squiz --sniffs=Squiz.PHP.EmbeddedPhp,Generic.PHP.DisallowShortOpenTag

Here is the resulting PHP file:
<?php phpecho 'This is a short open tag'; ?>

Here is the part of the phpcbf -vvv output that shows what is causing the problem:
---START FILE CONTENT---
1|<? echo 'This is a short open tag'; ?>
2|
--- END FILE CONTENT ---
	Generic.PHP.DisallowShortOpenTag:67 replaced token 0 (T_OPEN_TAG on line 1) "<?" => "<?php"
	Squiz.PHP.EmbeddedPhp:398 replaced token 1 (T_WHITESPACE on line 1) "·echo" => "echo"
        => Fixing file: 2/2 violations remaining [made 1 pass]...
	* fixed 2 violations, starting loop 2 *
---START FILE CONTENT---
1|<?phpecho 'This is a short open tag'; ?>
2|
--- END FILE CONTENT ---
	Generic.PHP.DisallowShortOpenTag:67 replaced token 0 (T_OPEN_TAG on line 1) "<?" => "<?php·"
        => Fixing file: 1/2 violations remaining [made 2 passes]...
	* fixed 1 violations, starting loop 3 *
---START FILE CONTENT---
1|<?php phpecho 'This is a short open tag'; ?>
2|
--- END FILE CONTENT ---
        => Fixing file: 0/2 violations remaining [made 3 passes]...
DONE in 1ms
	=> File was overwritten

On a first pass, Generic.PHP.DisallowShortOpenTag replaces <? with <?php. Then Squiz.PHP.EmbeddedPhp removes the whitespace before the echo keyword. Resulting in <?phpecho. On a second pass, <? is tokenized as T_OPEN_TAG and phpecho as T_STRING. So, Generic.PHP.DisallowShortOpenTag replaces <? with <?php again, resulting in <?php phpecho`.

@rodrigoprimo Good catch, still low prio.
Having said that, might be good to check if the Generic.PHP.DisallowShortOpenTag sniff fixer checks whether there is a whitespace char after the short open tag before replacing it and yes/adjusts the replacement value if not.
That would be a separate issue though.

Having said that, might be good to check if the Generic.PHP.DisallowShortOpenTag sniff fixer checks whether there is a whitespace char after the short open tag before replacing it and adjusts the replacement value if not.
That would be a separate issue though.

@jrfnl, good point, I checked, and the sniff does check that:
https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/84acf4e56f110db8e75cb9a575c5727df637643c/src/Standards/Generic/Sniffs/PHP/DisallowShortOpenTagSniff.php#L61-L65
https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/8b7beb182c5db1026261c94eb8afa818a8fb6dbc/src/Standards/Generic/Tests/PHP/DisallowShortOpenTagUnitTest.2.inc#L7
https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/8b7beb182c5db1026261c94eb8afa818a8fb6dbc/src/Standards/Generic/Tests/PHP/DisallowShortOpenTagUnitTest.2.inc.fixed#L7
The problem only happens when the two sniffs are executed together. So it seems to be a case of conflict between the fixers. I'm assuming it is not worth investigating this further as the issue in Squiz.PHP.EmbeddedPhp will be fixed and, as you said, this is low priority as the PHP short open tag is not commonly used. But please let me know if you want me to look more into this.


with-apollo example webpack break?

And I think it make HMR breaking there. Is this only me?

Hmm I don't have that issue when running the example (using 2.0.0-beta.32). Can you look at what throws the error?

@sedubois I'm trying 2.0.0-beta.32 with nearly same error result

About the prefetch errors, go to chrome://serviceworker-internals and unregister the next-prefetcher.js. That mechanism has been removed recently.

@sedubois Weird enough clear cache, app cache, local storage did the trick (I'm using chrome extension to clear them all so I'm not so sure which one causing this)
Thanks!


Add temporary volume for import function to store pg_dump

Hi,
I was recently testing import function to prepare some upgrade procedures for our databases, and I have one thought. Currently we need to provide additional space in data volume to temporarily store pg_dump. The problem is, not every storage type accepts storage size decrease (also I'm not sure CNPG supports storage downsizing at all ?). So after the operation, we're left with possibly considerable amout of unsused and somehow unreclaimable storage. It would be good to have additional temporary storage volume for such purposes. It could be defined for instance in the import section and mounted only for the time of the import operation is in progress.
Proposed spec:
import:
storage:
storageClass: XXXXXX
size: XXGi

Duplicate of: #1669

As @sxd suggested in #1669, the best course of action for such scenarios is to launch another pod with your storage requirements and use that to perform your import. If you need, you can even launch said pod on the same node as the primary database instance (to avoid additional network latency), although it's not 100% guaranteed the primary won't change.
My preferred choice for an image is: alpine:3.17 with: apk add postgresql15-client.

@itay-grudev I feal You do not understand the case. We are talking about CPNG function that enables doing automatic import od data from another database. This function is available from the code/cluster manifest level. During its action it requires enough data storage to fit both imported data and temporary pg_dump that is being transfered from the source DB. So after the operation compeltes, we have cluster that has much more data storage that is actually required. This storage is unreclaimable. So much wiser it would be to have a temp storage volume just to store pg_dump there only for that operation to complete. Actually Gabrielle agreed to such an approach on slack channel , so I've made this issue to get this option developed.

@MichaluxPL Can you link to the CNPG function you're referring to in their documentation?

Got it. You're correct.

I'm unsure if my use case is relevant to this issue, let's find out!
I want to leverage Secret Store CSI / Vault CSI Provider to create the secrets related to the DB.
e.g. Using Secret Provider Classes
The ability to mount additional volumes would enable to dynamically create secrets base on the pod creation.
Let me know if I need to open another issue.
Thanks!

That's a totally different case. This one is only for the import functionality.


"curse no" command does not hide the cursor in all contexts

The command "curse no" meant to hide the cursor does not work in certain applications. Two cases I'm aware of are notepad++ and Adobe Acrobat Reader. It is possible that the failure case is applications which define custom cursor appearance.

@tararoys could not reproduce this behaviour in NotePad++ in Windows 10.  Just to confirm, you have the user.mouse_cursor_commands_enable tag enabled?

I shouldn't have included the notepad++ example without verifying it myself, I happened to see this comment while digging a bit. I do have that tag enabled.


Add Jest's flow-typed definition to the jest package

Summary
Full summary of the issue is inside #2350 - this would resolve it.
Test plan
I think the best way to test this is to create a fresh project, then to manually place this file inside the node_modules/jest folder then see what details flow gives you in Jest files.

Merging this but we really need to work on the danger integration. Right now it is really noisy.

Also a test plan would be nice.

actually, travis is unhappy with this :P

Haha, yeah, and I need to actually verify it does what I expect, might be able to get around to all of this.

I've tested this out, I took a quick project from my vscode plugin:

These are flow errors about expect, describe, it et al not being available. I copied the following file into my node modules:

and added it to my libs in the .flowconfig
[ignore]

[include]

[libs]
node_modules/jest/build/jest.flow.js

[options]

Then my errors went away:

@ryyppy  does this ^ feel reasonable to you? To do it this way, I think we'd need to ask users to include
[libs]
node_modules/jest/build/jest.flow.js

In their .flowconfig, which looks like how you did it in styled-components

Nooooo! please, @orta / @cpojer could we wait with that? I think this happens to be bad practise with how to deal with libdefs :-/ ...

We will go away from styled-component's approach, since we got so many complaints and issues with colliding .flowconfig... we already are in the process of porting styled-components to flow-typed... it's easier to run flow-typed install instead of messing around with your flow configuration ... but yeah, I would actually love to be able to do this in a library as well... it's just not practical yet

Glad I asked 💃
Alright, I definitely know to trust your opinion on this - so then I'm gonna close this PR. Let me know if your opinion changes on the subject 👍

sorry :-D ... It will spare us a lot of problems in the future... although we could think about a strategy how to sync library / flow-typed definitions...

I don't know the extent to which you're going to keep with the github repo as source of truth there, but we created a user authentication server atop of a repo for CocoaPods ( https://github.com/cocoapods/trunk.cocoapods.org ) that allows people to push their own versions: https://github.com/CocoaPods/Specs/commit/f3d0186aa1939e3172666563f40811f2a3f98de4


Crash when backspacing through template

First off, just want to say thank you for creating such an amazing mod. The options and templating language features are truly 💯!
I have noticed when tweaking in options that whenever I backspace through something like [col=FFFFFF]%v[/col] to [%v[/col], the game client will crash. Upon restarting, I lose a lot of my configuration.
I wonder if this is a bug in the template evaluation logic?

Yeah, that sounds like a bug. I will have a look into it.

Will be fixed with commit https://github.com/Artenuvielle/GW2-SCT/commit/37a3d663e5f5df20e32bddae5462e5de9b750b35


Union proxy config

[2/N] in #134

Union cross-silo rpc related config into one Config. This can do good for multi-job config management.
Make it a parameter infed.init API to reduce tha amount of RPC related config parameters.

The UT failure is not related to this PR, has filed an issue #153

BTW, could you please update the PR title and the description? They're not match to your PR context.


Cannot hear the call response through speaker on outbound calls

This is my code for making the outbound call and setting the speaker. The outbound call goes through successfully. But I am not able to hear any audio for the outbound call through the speaker.

agent.connect(endpoint, {
            success: function () {
                console.log("outbound call connected");
            },
            failure: function (err) {
                console.log("outbound call connection failed");
                console.log(err);
            }
        });

    //Device id is being selected from a menu which is pre-populated with the device id values.
    function changeOutputDevice() {
        var deviceId = document.getElementById("outputDevicesMenu").value;
        try {
            window.myCPP.agent.setSpeakerDevice(`${deviceId}`);
        } catch (err) {
            console.log(err);
            try {
                connect.setSpeakerDevice(`${deviceId}`);
            } catch (error) {
                console.log(error);
            }
        }
}

Hi pvranjana@ everything looks correct here. Can we have some more details as to how this is failing? Are you sure you have interacted with the window before expecting to hear audio? Are there any console errors occurring?


Update to use library for finding remote servers

Sorry for the late response.  Is there a particular reason for moving this code into a library?

I have a use-case where I need to forward auditd events though rsyslog and not have them go to a file since auditd is already sending these logs to a file. currently i'm replicating the search code in my cookbook. Here's what my config looks like in rsyslog.d
$ActionQueueType LinkedList # use asynchronous processing
$ActionQueueFileName srvrfwd # set file name, also enables disk mode
$ActionResumeRetryCount -1 # infinite retries on insert failure
$ActionQueueSaveOnShutdown on # save in-memory data if rsyslog shuts down
$SystemLogRateLimitInterval 0

if $programname == 'audispd' then @rsyslog_server
& ~

With the removal of chef-solo support this is all going to get reworked in the near future.

thanks for the update. Should I assume I need to continue to implement my own search function for my use-case or will that be resolved with the rework?


fix(notify): Always update websocket config

这个 PR 实现什么功能/修复什么问题:
每次启动notify服务都应该更新websocket相关的配置。
是否需要 backport 到之前的 release 分支:

release/2.12
release/2.13
release/2.14
release/3.0

Codecov Report

Merging #4483 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4483      +/-   ##
=========================================
+ Coverage    6.82%   6.83%   +0.01%
=========================================
  Files         521     521
  Lines       88444   88444
=========================================
+ Hits         6039    6048       +9
+ Misses      81901   81890      -11
- Partials      504     506       +2

Flag
Coverage Δ

#aFlag
6.83% <ø> (+0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

pkg/cloudcommon/cronman/cronman.go
54.85% <0%> (+5.33%)
:arrow_up:

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 ba68820...0cb2abe. Read the comment docs.

/cc @zexi


'flet' has no attribute 'MainAxisAlignment'

Description

AttributeError: module 'flet' has no attribute 'MainAxisAlignment'
Do you have updated documentation and where can it be accessed ?
I tried copying and pasting from the website itself and I got the above mentioned error

import flet as ft

def main(page: ft.Page):
    page.title = "Flet counter example"
    page.vertical_alignment = ft.MainAxisAlignment.CENTER

    txt_number = ft.TextField(value="0", text_align="right", width=100)

    def minus_click(e):
        txt_number.value = str(int(txt_number.value) - 1)
        page.update()

    def plus_click(e):
        txt_number.value = str(int(txt_number.value) + 1)
        page.update()

    page.add(
        ft.Row(
            [
                ft.IconButton(ft.icons.REMOVE, on_click=minus_click),
                txt_number,
                ft.IconButton(ft.icons.ADD, on_click=plus_click),
            ],
            alignment=ft.MainAxisAlignment.CENTER,
        )
    )

ft.app(target=main)

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):
Flet version (pip show flet):
Version: 0.1.65
(paste your output here)

Operating system:

Additional environment details:

Okay thanks, I will do so.


[iOS] Implement missing showSoftInputOnFocus prop on TextInput on the new arch

Summary
showSoftInputOnFocus prop was not implemented on the new architecture TextInput component on iOS. I added the implementation based on how it's implemented on the old architecture: https://github.com/facebook/react-native/blob/b314e6f147fdfcd71e7ba3b17338bb44356df98e/Libraries/Text/TextInput/RCTBaseTextInputView.m#L313-L325
Changelog
[IOS] [FIXED] - Added missing showSoftInputOnFocus on TextInput on the new architecture
Test Plan
Added the prop on the TextInput component and checked whether the keyboard opens.

Not stale

Looks like it was implemented in https://github.com/facebook/react-native/pull/45298


WHAM-BAM finished normally

the runing break suddenly and says "WHAM-BAM finished normally"
there is no result . I mapped my read to reference with bowtie2 ,Does that matter?

Yes you need to use bwa-mem.
On Fri, Jan 3, 2020 at 5:56 AM liufy11<EMAIL_ADDRESS>wrote:

the runing break suddenly and says "WHAM-BAM finished normally"
there is no result . I mapped my read to reference with bowtie2 ,Does that
matter?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zeeev/wham/issues/53?email_source=notifications&email_token=AAE7CIOP3MGB4T5QZA3MTZLQ34YXVA5CNFSM4KCNFMI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ID3Y6MA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE7CILXKBQKVFNGYXLSCJ3Q34YXVANCNFSM4KCNFMIQ
.

Thanks for your  quick reply !


Improve tests

Unit tests

[x] Test the Account API.
[x] Test the Actor API to the extent possible without integration.
[ ] Test the Replica API to the extent possible without integration.
[ ] Find potential pain points with regards to testability/modularity.

Integration tests

[x] Build up a network of the components to test the integrated flow.
[x] Adapt for property based testing with quickcheck.
[ ] Include byzantine parameters validation in quickcheck.
[x] Expand on test cases.
[ ] Evaluate using proptest instead of quickcheck.
[ ] Improve test performance.

Closing this as it's over a year old and this repo is being archived - can be recreated in safe_network if still relevant


Fix links in README

Simply fixes a couple broken links in the Readme.

Hi @ticofab,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
http://www.lightbend.com/contribute/cla

Apologies for the delay here, @ticofab—there's been some package renames since this was opened. Care to update and refresh the PR?

Thanks @ticofab!

Oh wait there wasn't any change yet - I was just syncing my own branch with the original :)

@ticofab Oh, then rebase and let me know when things are ready to merge :)

hey @viktorklang I re-fixed most offending links 😄 there is one tho that I wasn't sure how to fix, which is
[`entity.js`](node-support/src/entity.js)

, so maybe you or @jroper can fix that one before merging? :)

Thanks @ticofab, the documentation will get better with each such PR :)


Test the abstract MGM

References #49

[x] create a test file for testing the MGM abstract implemented functions
[x] write unit tests for the implemented functions using pytest

researched the matLAb mgm class and how it works so I can get an idea of how to test a python port
created a dumym mgm class and set up to import for the tester file
working on creating the tester file to test the abstract classes implemented functions
thinking on creating a dummy implementation that just inherits the abstract functions so an object can be created to test those methods with.
[t:60]

got all tests to run with the correct failing exception
all functions have tests
added numpy to the lint testers dependencies
need to figure out if its ok to have the lin tester fail since these tests should fail or if theres a way to ignore these tests
[t:75]


[dune-issue] dune fails build under trunk/5.3 on macOS

dune.3.12.2 no longer builds under trunk/5.3 on macOS which effectively disables this CI workflow:
Install dune
  /Users/runner/hostedtoolcache/opam/2.1.5/x86_64/opam install dune
  Constructing initial basis...
  Number of 0-1 knapsack inequalities = 28
  Constructing conflict graph...
  Conflict graph has 28 + 6 = 34 vertices
  The following actions will be performed:
    ∗ install dune 3.12.2

  <><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
  ⬇ retrieved dune.3.12.2  (https://github.com/ocaml/dune/releases/download/3.12.2/dune-3.12.2.tbz)
  [ERROR] The compilation of dune.3.12.2 failed at "ocaml boot/bootstrap.ml -j 4".

  #=== ERROR while compiling dune.3.12.2 ========================================#
  # context     2.1.5 | macos/x86_64 | ocaml-variants.5.3.0+trunk | git+https://github.com/ocaml/opam-repository.git
  # path        ~/work/multicoretests/multicoretests/_opam/.opam-switch/build/dune.3.12.2
  # command     ~/.opam/opam-init/hooks/sandbox.sh build ocaml boot/bootstrap.ml -j 4
  # exit-code   2
  # env-file    ~/.opam/log/dune-26017-16d463.env
  # output-file ~/.opam/log/dune-26017-16d463.out
  ### output ###
  # ocamlc -output-complete-exe -w -24 -g -o .duneboot.exe -I boot -I +unix unix.cma boot/libs.ml boot/duneboot.ml
  # ./.duneboot.exe -j 4
  # cd _boot && /Users/runner/work/multicoretests/multicoretests/_opam/bin/ocamlopt.opt -c -g -I +unix -I +threads dune_digest_stubs.c
  # In file included from src/dune_digest/dune_digest_stubs.c:10:
  # In file included from /Users/runner/work/multicoretests/multicoretests/_opam/lib/ocaml/caml/md5.h:24:
  # In file included from /Users/runner/work/multicoretests/multicoretests/_opam/lib/ocaml/caml/io.h:26:
  # /Users/runner/work/multicoretests/multicoretests/_opam/lib/ocaml/caml/platform.h:79:17: error: implicit declaration of function 'atomic_load_acquire' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
  #     uintnat v = atomic_load_acquire(p);
  #                 ^
  # 1 error generated.
  #

The reason is that https://github.com/ocaml/ocaml/pull/12839 removed a macro definition for atomic_load_acquire in CAML_INTERNALS combined with dune not following the OCaml manual's instructions for using the this internal API.
The error has been reported and fixed upstream in dune in https://github.com/ocaml/dune/pull/9733.

The fix for this should be available from the next 3.14.0 release.
I can see a 3.14.0~alpha1 being rolled out https://github.com/ocaml/opam-repository/pull/25220

Closing, as the latest macOS trunk run in https://github.com/ocaml-multicore/multicoretests/pull/437 installed the latest dune.3.14 which includes the fix, and hence no longer triggers the issue.


Add FXC (Direct3D shader compiler)

FXC is Microsofts "old" shader compiler, would be neat to get HLSL bytecode output and inspect it the same way as assembly.
https://msdn.microsoft.com/en-us/library/windows/desktop/bb232919(v=vs.85).aspx

Looks tricky: seems to be a MS-only compiler.

This might help with this particular issue - https://github.com/jbarczak/Pyramid
Haven't checked in depth how this would work on non-Windows systems but it's just calling some native DLL functions to get the bytecode/assembly and is self-contained with no DX SDK or anything required ( might run with no problems on Wine).

https://github.com/jbarczak/Pyramid


CASSANDRA-19577 Make queries visible to the "system_views.queries" virtual table at the coordinator level

patch by Caleb Rackliffe; reviewed by Chris Lohfink for CASSANDRA-19577

Committed as https://github.com/apache/cassandra/commit/428fa1f4453735ef43d508621e5e7d9e0a054415


docker networking

A network for api + database is enough.
the front app and api will communicate through registered DNS


Some improvements to the build process + a fix

This is also a test for the automatic triggering of Sensiolabs Insight code analysis at https://insight.sensiolabs.com/projects/92bca775-5e4e-4288-9fd5-9cbb660280ac
This PR should generate the 6th analysis.

The sensiolabs thingy didn't work... I'll try to understand why.
I started it manually

Merging to test sensiolab webhook


how i set range of date in filtering with using two date picker? (such as below img link)

depends on where you get your data. I am sure there is a way to filter between dates in javascript though, you would just have to filter your data before returning it to the grid.

Checkout the answer to the following issue https://github.com/tabalinas/jsgrid/issues/60

Thanks,resolved :)


vmrunner.py lacks an on_finished event

It would be helpful with an event that gets called when vmrunner.py has finished to make necessary clean ups etc. This is also useful in cases where the exit status doesn't matter.

Added on_exit in 4943f7e


Remove incorrect hard-coded "fish" shell identification.

Fixes #3496
The lines I removed cause the shell to be identified as fish if the __fish_bin_dir environment variable is set, even when $SHELL is explicitly set to something else.
This causes a fish user to get the fish env when running a non-fish sub-shell.  Until fixed all bash scripts that use docker-machine env will fail for fish users.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:cibotech/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:cibotech/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

:+1:

Cool, thanks @sakoht -- you'll need to update the test as well please:
ok  	github.com/docker/machine/libmachine/provision/serviceaction	1.020s
--- FAIL: TestDetectFish (0.00s)
	Error Trace:	shell_test.go:29
	Error:		Not equal: "fish" (expected)
			        != "bash" (actual)

This PR is flawed.
The real problem is that $SHELL  contains the login shell, not the current shell, which is what docker-machine env requires.
The real solution would have to look through the stack of parent processes until it hits one that is a shell.  The only reasonable way to know a shell is to check /etc/shells, though this is technically just the shells that can be used for login.
It would still probably be better to remove these lines, because it will force things to think they are fish that are not.  But this is undoubtedly helping someone who put it there.  I'm going to revisit this for a more thorough replacement....

Unless you want to leave it to the user to always use --shell if not running in your login shell.

Thanks @sakoht , I'm going to close this for now, if you have a change of heart or file a new PR to help with this feel free to ping me

This PR is still an improvement over what existed.

I'm OK with whatever -- not being a fish user, it's hard for me to say what's the best course, but if you think it'd be good to merge I'm in favor @vikstrous .  It certainly is a little odd to try and auto-detect this somewhat arbitrary environment variable.

Going to merge this and see how it turns out for us...

LGTM

Thanks

👍


Third-party cookie warning

Currently, the Chrome browser (Version 129.0.6668.101) displays a warning about third-party cookies:
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.

It's unclear whether the Google Pay button will stop working once Chrome starts blocking third-party cookies. In any case, it seems advisable to take action, either to prevent future issues or to change the current behavior so that this warning disappears.
This question is related to:

[x] React component (@google-pay/button-react)
[ ] Custom element (@google-pay/button-element)
[ ] Angular component (@google-pay/button-angular)

Hi. The Google Pay button will continue to work even once Chrome starts to fully block 3rd party cookies.

Good to know. But it would be great to get rid of warnings, as they spaming to often.


Add Graph DFS

The Graph DFS is missing please add it.

Hey @abhishektripathi66 Can you assign this to me?

Is the issue still open?

I have created a PR to add the Depth First Search! :) Hope it helps.


Error when to goal is available in widget

When no goal is set, a error is shown in the widget instead of telling the user to go to the sprint/iteration to set one:

Fixed with #19