Cosmos Hub Chain Name Service discussion

Still early, but we can use this issue as a place to aggregate architectural notes and user requirements.

At present we know relayers are using this repo. I believe Keplr is also planning to integrate. Are there other known users we should be speaking to?

Hi - would this be possible to track features? (Chain supports permissioned or permissionless cosmwasm for example).
We started using this for helping some tools, and it would be awesome if there was a way to load all chain configs or filter to chains meeting certain feature or other criteria.

Could also turn on the "discussions" feature in git repo ;)

Seems a little off topic. Maybe make a new issue for this? Agree this info could be useful.

@hxrts love the idea of a Chain Name Service. I recently built restake.app and cosmos.directory, the latter is built around the Chain Registry and provides live APIs making it easy to use this data in web applications. REStake then uses cosmos.directory for all interchain config. I also built most of Cosmos Omnibus which again relies heavily on Chain Registry.
I'm very interested in the outcome of the chain name service and would love to help out where I can if needed.

thanks for your interest @tombeynon! what we need most right now is a better understanding of how an on-chain chain name + metadata directory might be used. if you have specific ideas please share!

Hi, simple UI dev here - i have gone through the various api's and i have a quick question, which one is best suited to return me chain info and a URL to an icon for the chain ?
To provide some context i a have POC i am currently working on and i want to provide a menu not to dis similar to the mint scan menu, so i need chain info and the logo.. see an example below

@hxrts love the idea of a Chain Name Service. I recently built restake.app and cosmos.directory, the latter is built around the Chain Registry and provides live APIs making it easy to use this data in web applications. REStake then uses cosmos.directory for all interchain config. I also built most of Cosmos Omnibus which again relies heavily on Chain Registry.
I'm very interested in the outcome of the chain name service and would love to help out where I can if needed.

@hxrts Apologies for being a little off topic so which api would you sugegst to use? , also question to @tombeynon - i have had a look at the cosmos.directory - where can i get info on the api's you mentioned, also the restake app is a very cool app ...

@Goochie you can see a high level overview of the APIs available on the cosmos.directory Github: https://github.com/eco-stake/cosmos-directory. They've evolved a bit from there but it's easy enough to check what's being returned.
@hxrts personally chain registry really provides everything I need; so an on-chain version of that would be amazing. Biggest concerns would be how to keep it updated in a reliable and fast manner, e.g. gov proposals are great but don't move super quickly, and there are times where updates to Chain Registry are needed quite quickly (chain ID changes etc). I imagine allowing gov to vote on wallet addresses that are allowed to update each chain is enough, then those wallet addresses can make updates as often as required. Similar to Regen's carbon credit authorities.
Otherwise, all cosmos.directory does is provide the chain registry data directly, and decorate it with extra attributes to make integrating UIs easier. I maintain the Validator Registry which is very similar to Chain Reg but for validator attributes, so whatever happens with Chain Name service, would be interesting to see how it could apply to Val Reg too. Again cosmos.directory exposes this data in API form, and decorates with on-chain data, keybase images etc etc.
I'm not sure we'll avoid some middleware like cosmos.directory entirely, but making the Chain updates more permissionless/crypto native is definitely something I'm on board with.
Apologies for the slow reply, will try to keep on top of this conversation.

En büyük endişeler, bunun güvenilir ve hızlı bir şekilde nasıl güncel tutulacağıdır; örneğin, gov teklifleri harikadır ancak çok hızlı ilerlemezler ve Zincir Kayıt'ta güncellemelerin oldukça hızlı bir şekilde gerekli olduğu zamanlar vardır. Hükümetin her zinciri güncellemesine izin verilen cüzdan adreslerine oy vermesine izin verilmesinin yeterli olduğunu, ardından bu cüzdan adreslerinin gerektiği sıklıkta güncelleme yapabileceğini düşünüyorum.


chronological context (storing and recalling of events)

when asking to describe how events developed that are related to a specific theme, they are returned out of order, which also changes (confuses) the context of how they are being represented.
related to that, newer (more recent) relationships should override older ones:
marriage spouse1 -> divorce -> marriage spouse2 -> what's spouse's name?
same also for if there's no chronological data related to context, such as training data for model ("knowledge") should always be considered as "last resort" if there is no data with chronological association.
i've for example ingested a short novel that is divided up into numbered chapters (consecutively number w/ single word as chapter title); i've ingested each chapter separately and in order, and i've added the chapter number and title (word) at the start each time; yet when queried for the main events and how they influenced the story progression, the order of the events were all over the place, creating illogical outcomes (progression / story flow).

This is indeed one of the issues we plan to address in the future. Currently, the indexing phase does not incorporate chronological data, and we're working on figuring out how to effectively integrate chronological order into the system.

This is indeed one of the issues we plan to address in the future. Currently, the indexing phase does not incorporate chronological data, and we're working on figuring out how to effectively integrate chronological order into the system.

it seems they've done it: https://help.getzep.com/graphiti/graphiti/overview


nuimo_app create a zombie process when a nuimo is removed

The unexpected behaviour takes place when the nuimo is removed from the app through the event change listener. A tested workaround is to restart nuimo_app in case a new nuimo is added/removed and keep the change listener only when the components configuration is changed.

solved in PR #252


feat(measurement): Add calibration type labels (ERMF, PROJ, USER)

Context
The user needs to know how the calibration of size on an image is derived.  There are several options, including USER manual calibration, ERMF, projection and others.  Add the labels here.
Changes & Results
Stores the calibration object and uses it to provide the label display.
Testing
Test various measurements on various projection modalities (CR, DX) to ensure that the appropriate label is displayed
Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

[] I have run the yarn build:update-api to update the API documentation, and have
committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] "OS:
[] "Node version:
[] "Browser:

seems like you need to do the api build again

looks good, can you respond to my remaining comment only?

I pushed an update to deal with that.

can you run yarn run build:update-api? and include them? https://www.cornerstonejs.org/docs/contribute/update-api


Not able to use Sunlit blade cantrip with reach weapon such as Polearms at 1 space away

The title is self-explanatory; Thanks for all the hard work folks; Really appreciate the mod. Attached a save for reference.
AutoSave_9.zip

@ThyWoof you used the cantrip on an adjacent enemy. When you try to use it one space away the cantrip says the target is out of reach (even though the long mace has the range to attack. This was possible on previous version of the mod)

I know. Wrong screenshot


Provide searching for base versionless and fully-qualified packages u…

…sing ?q=.

@carlosthe19916 still [draft] but here's a shot at supporting ?q= on /api/v1/package and /api/v1/package/base depending on how wide a given search wants to be.
I suspect I don't have sorting right yet.

One thing that I will probably request on another gh_issue is to support appropriate filtering on GET /api/v1/package?q=.... I appreciate we have multiple endpoints at the moment, but the client will use the filtering query parameters for searching "by type", "by namespace", "etc". But first things first, let's have this done and then we can discuss what to do next

I'd hope filters would work already. It's using our standard Query magic from Jim.

Cool. Looking forward to see this PR merged!

Right on, added a test and indeed filtering by fields works as expected.
    let uri = "/api/v1/package?q=type=maven";

This PR has been approved. Whenever you are ready push the merge button :)


Push Notification Icon in Background Mode

Hi.
When using your Plugin in my Xamarin Android App, when the application is running in foreground, the icon set with FirebasePushNotificationManager.IconResource works fine and it's displaying the correct notification icon that I set.
But when the app is not running or is in background mode, the icon that it's being displayed is the gray square, (which in this case is the application icon not the notification icon)
Am I missing something, or is this a BUG in your Plugin?
protected override void OnCreate(Bundle bundle)
{
TabLayoutResource = Resource.Layout.Tabbar;
ToolbarResource = Resource.Layout.Toolbar;
base.OnCreate(bundle);
Rg.Plugins.Popup.Popup.Init(this, bundle);
global::Xamarin.Forms.Forms.Init(this, bundle);
Xamarin.FormsGoogleMaps.Init(this, bundle);
CrossCurrentActivity.Current.Init(this, bundle);
Xamarians.GPS.Droid.GPSServiceAndroid.Initialize(this);
Plugin.InputKit.Platforms.Droid.Config.Init(this, bundle);
        LoadApplication(new App());

        FirebasePushNotificationManager.Color = Android.Graphics.Color.Rgb(239, 51, 64);
        FirebasePushNotificationManager.IconResource = Resource.Drawable.icon;
        FirebasePushNotificationManager.ProcessIntent(this, Intent);

}

Hi,
I solved with this answer in stackoverflow.
Regards!

I have the same problem, when application is on foreground the FirebasePushNotificationManager.IconResource is used, when it is on background it uses the application icon. I set it in MainApplication class

@Nadezhda-Popova just cut your code and put it in Main Application class. If you don't have an Main Application class, you can see it here how create.
Regards!

@mimunoz the definition is in MainApplication class
`public override void OnCreate()
{
base.OnCreate();
RegisterActivityLifecycleCallbacks(this);
//A great place to initialize Xamarin.Insights and Dependency Services!
CrossCurrentActivity.Current.Init(this);
        if (Build.VERSION.SdkInt >= Android.OS.BuildVersionCodes.O)
        {
            //Change for your default notification channel id here
            FirebasePushNotificationManager.DefaultNotificationChannelId = "FirebasePushNotificationChannel";

            //Change for your default notification channel name here
            FirebasePushNotificationManager.DefaultNotificationChannelName = "General";
        }

        //If debug you should reset the token each time.

#if DEBUG
FirebasePushNotificationManager.Initialize(this, true);
#else
FirebasePushNotificationManager.Initialize(this,false);
#endif
FirebasePushNotificationManager.IconResource = Droid.Resource.Mipmap.ic_stat_ic_notification;
        //Handle notification when app is closed here
        CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
        {

            System.Diagnostics.Debug.WriteLine("NOTIFICATION RECEIVED", p.Data);
        };
    }`

Any update on this? @mimunoz what I do wrong or is it an issue with the plugin? Thank you!


Log if aiohttp hits error during IndieAuth

So a user came to me the other day with a very interesting bug around IndieAuth. They were trying to auth with the iOS app but kept getting invalid client_id. I helped them through adding some debug logging around IndieAuth. We finally determined that the client_id lookup was entirely failing most likely due to an IPv6 issue. The error was getting eaten by this except-pass though.
This PR adds a log error if we hit an error during redirect_uri lookup.
Thanks to Yeitso for identifying this issue and working with me to determine where exactly it happened.

Yeitso here, the issue was related to my installation.
I was using macOS with python3.6 without a virtualenv and had forgotten to run the file:
/Applications/Python\ 3.6/Install\ Certificates.command

Python3.6 does not have any root certificates by default on macOS so running that command after installation is essential.
So learn from my mistake and either install via Homebrew or if you install python3.6 manually. Run that command :)


replicate problem with unit test

Related to #677

@ProTip, this should fix your problem.  Once the new package is available, could you verify in your generation scenario, please?


Design and implement panel informing user of actual state of application

Expected Behavior
There should be a specific place in user interface that tells user what is the actual state of the application.
Actual Behavior
For most of the time user is not aware of what state application is in.

What does it mean? :) Could you explain what state means exactly?

I think that it will be something along the lines of status bar but without any sophisticated options. Just information about the current state of the app, like tagging with tool X, Selection sent successfully etc.


Switch panel to the right side

Hi! Please, tell me  how to switch panel to the right side? I want to have project folders from the left, FTP panel from the right and editor between them.

Me too!

Please check new Remote-FTP version.


use .forEach rather than .map in forEach helper

+1 for this proposal, this looks amazing; just happened to catch this while reading through it.

Thank you!

Yea this looks great. Really digging the direction JS is going! Thanks for the proposal @mindeavor


SELF-482: Upgrade Storybook

JIRA

SELF-482

Description

Upgrades storybook to version 8

Reviewer Checklist
This section is to be filled out by reviewers
Testing

[ ] This code was tested by somebody other than the developer. Do not merge until this has been done.

Closing in favor of https://github.com/lob/ui-components/pull/544


feat(build): allow disabling jpms for all projects.

Summary
Filing for @darvld before rebase.

[x] fix: wasm killswitch
[x] fix: jpms killswitch

Summary by CodeRabbit

Refactor

Improved task configuration methods in build processes to enhance performance and reliability.

New Features

Added new checks and configurations for Java and Kotlin projects to better manage module and compilation settings based on project requirements.

Documentation

Updated file paths and constants documentation to reflect new configurations and checks.

merging as part of #788


Added first shot of an Iterator benchmark

This PR adds the JMH benchmark library and a first shot of an Iterator benchmark.
I tested three variants of an ArrayIterator. However, I think the benchmarks might be not optimal at the moment, e.g. Iterable creation might need to be isolated etc. Discuss!
First results:
Benchmark                                                               Mode  Cnt  Score   Error  Units
IteratorBenchmark.fullyIteratingArrayIteratorNaiveFor1000Elements       avgt   25  0.680 ± 0.001  ns/op
IteratorBenchmark.fullyIteratingArrayIteratorNaiveForOneElement         avgt   25  2.689 ± 0.005  ns/op
IteratorBenchmark.fullyIteratingArrayIteratorTryCatchFor1000Elements    avgt   25  0.455 ± 0.001  ns/op
IteratorBenchmark.fullyIteratingArrayIteratorTryCatchForOneElement      avgt   25  2.688 ± 0.011  ns/op
IteratorBenchmark.fullyIteratingArrayIteratorWithLengthFor1000Elements  avgt   25  0.678 ± 0.001  ns/op
IteratorBenchmark.fullyIteratingArrayIteratorWithLengthForOneElement    avgt   25  2.685 ± 0.005  ns/op

Codecov Report

Merging #2372 into v1.0.0 will decrease coverage by 3.58%.
The diff coverage is 14.28%.

@@             Coverage Diff              @@
##             v1.0.0    #2372      +/-   ##
============================================
- Coverage     98.42%   94.83%   -3.59%
  Complexity      164      164
============================================
  Files            10       10
  Lines           317      329      +12
  Branches         58       59       +1
============================================
  Hits            312      312
- Misses            3       16      +13
+ Partials          2        1       -1

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/io/vavr/collection/Iterator.java
60.97% <14.28%> (-25.24%)
5 <0> (ø)

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 9a88bb1...698e876. Read the comment docs.

Looks like the optimized version is the fastest. Having an AbstractIterator (like Scala does, in order to reduce class file size of implementing classes) is contra-productive.
Benchmark                                                                                Mode  Cnt   Score   Error  Units
ArrayIteratorBenchmark.fullyIteratingArrayIteratorNaiveFor1000Elements                                     avgt   25  20.630 ± 0.063  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorNaiveForOneElement                                       avgt   25   3.429 ± 0.009  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchFor1000Elements                                  avgt   25  20.829 ± 2.839  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchForOneElement                                    avgt   25   3.431 ± 0.011  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchOptimizeExtendsAbstractIteratordFor1000Elements  avgt   25  21.244 ± 3.434  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchOptimizedExtendsAbstractIteratorForOneElement    avgt   25   3.436 ± 0.016  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchOptimizedFor1000Elements                         avgt   25  18.974 ± 0.033  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorTryCatchOptimizedForOneElement                           avgt   25   3.434 ± 0.007  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorWithLengthFor1000Elements                                avgt   25  20.662 ± 0.046  ns/op
ArrayIteratorBenchmark.fullyIteratingArrayIteratorWithLengthForOneElement                                  avgt   25   3.434 ± 0.011  ns/op


Refactoring classes

script.js splited in 4 files
classes made with SOLID principles aproach
started styling

Hi, @Wikitelmex @peterdgreat,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


release-please bootstrap with --dry-run executes live operations

Problem:
When running with --dry-run, the release-please bootstrap command creates a real commit with new files and opens a real PR using the GitHub API, in violation of the defined behavior from the CLI documentation for global flags.
Expected behavior:
Using the --dry-run flag should cause release-please to solely indicate what would be done, not actually do it.
Sample:
$release-please --token=REDACTED_TOKEN --dry-run --repo-url=USERNAME/REDACTED_REPO bootstrap
✔ Starting GitHub PR workflow...
✔ Successfully found branch HEAD sha "REDACTED_SHA".
✔ Successfully created branch at https://api.github.com/repos/USERNAME/REDACTED_REPO/git/refs/heads/release-please/bootstrap/default
✔ Got the latest commit tree
✔ Successfully created a tree with the desired changes with SHA REDACTED_SHA
✔ Successfully created commit. See commit at https://api.github.com/repos/USERNAME/REDACTED_REPO/git/commits/REDACTED_SHA
✔ Updating reference heads/release-please/bootstrap/default to REDACTED_SHA
✔ Successfully updated reference release-please/bootstrap/default to REDACTED_SHA
✔ Successfully opened pull request available at url: https://api.github.com/repos/USERNAME/REDACTED_REPO/pulls/1.
✔ Successfully opened pull request: 1.
{
  headBranchName: 'REDACTED_REPO/bootstrap/default',
  baseBranchName: 'main',
  number: 1,
  title: 'chore: bootstrap releases for path: .',
  body: 'Configuring release-please for path: .',
  files: [],
  labels: []
}

Environment details

OS: MacOS 12.5.1
Node.js version: 16.17.0
npm version: 8.15.0
release-please version: 14.2.4

Steps to reproduce

Run the release-please tool in a new repository containing valid content with the --token and --dry-run and --repo-url set to valid values, and specify the bootstrap command. See the above section "Example" for sample input/output of running this command.
Instead of specifying what files, commit(s), and/or PR would be created, release-please interacts with the GitHub API to actually create a PR after creating files and a commit.

This is an oversight in the implementation of the bootstrap command.


First draft of the winforms core porting guide

New porting winforms from .NET Framework to .NET Core article
Fixes #9615

Do you want to add a link to this article to ~/docs/core/porting/index.md?


Leaking validator's private key

recently I came accross with this:
https://www.scs.stanford.edu/~dm/blog/simplified-scp.html
if I understand correctly, if ValidatorA signs 2 different blocks at the same height, then it's private key is leaked. From our code, it seems when we are about to emit a SCP_ST_CONFIRM message we sign the block that is about to be created.
However from the link above it doesn't seem that reaching the SCP_ST_CONFIRM state means the block that we just signed will definitely be to block that will eventually be externalized. I think the doc and the SCP code is a little bit out of sync, but the SCP_ST_CONFIRM seems to correspond in the doc with this:
'COMMIT ⟨n, x⟩: This states that value x is chosen in ballot n.'
you can also look at the SCP balloting code and see:

doesn't seem the federeated voting on the 'COMMIT (n,x)' (which has several steps) has finished while we are already sending and receiving SCP_ST_CONFIRM messages(and signing different blocks left and right at the same height and LEAKING private keys)
please comment

doesn't seems voting is finished...

I see two possible options which might solve this:-

Include the ballot number in the signature noise so that a node can only sign a single block each ballot round of SCP_ST_CONFIRM.
Only create block signaturtes in the SCP_ST_EXTERNALIZE phase.

I think we should keep it simple and would prefer option 2. However even option 2 can be insecure and reveal the private key in the following scenario:
ValidatorA's quorum has enough validator's under the control of an attacker. This attacker could trigger a valueExternalized event in ValidatorA's quorum and as a response ValidatorA would sign that block. Of course this block will not never have enough signatures, so will never be added to ValidatorA's ledger. Later ValidatorA will catch up and receive the real block agreed upon by the majority of the network. This block is different from what ValidatorA has already signed, and based on the current implementation I think ValidatorA will sign this new block too, again revealing its private keyl

ValidatorA's quorum has enough validator's under the control of an attacker. This attacker could trigger a valueExternalized event in ValidatorA's quorum and as a response ValidatorA would sign that block.

That scenario shouldn't be possible possible though (well, highly unlikely).

I think it is a possible scenario and even mentioned in the SCP whitepaper under the name of befouled node

any chance of leaking the private key regardless of how likely should be tackled I think, or we should somehow be able to calculate the probablility of such event and decide if that is acceptable

I think, regardless of this issue, we should make sure, in the node, that we do not sign the same block twice.
Currently we don't because nodes are well behaved and simply won't do it, but as a mean to prevent any bug from having disastrous consequences on end user, there should be a failsafe mechanism.

I mentioned a corner case saying just blindly signing an externalized message is still dangerous if during the catchup (or at any point of time) the node signs a different block(which I assume it does currently). A well-behaving node can run buggy agora implementation, it is not about the node's intention.

ValidatorA's quorum has enough validator's under the control of an attacker. This attacker could trigger a valueExternalized event in ValidatorA's quorum and as a response ValidatorA would sign that block.

That scenario shouldn't be possible possible though (well, highly unlikely).

So if the calculation below is correct then after 10 days there is a 30% chance of a node to end up in a quorum where he can potentially be befouled and potentially leak it's private key unless we solve the corner case I mentioned. I think this is far from being very unlikely.
Here are the assumptions that are used that are based on our current implementation (with some simplification).
There are 1000 validators, 50 of them are under the control of an attacker. Each validator stakes the same amount of money, and so being equally likely to be chosen as a quorum member. Each quorum consists of exactly 7 nodes, and the 5 nodes out of the 6 nodes is enough for the remaining 1 node to be convinced. I assume that there are at least 1 validator in every 10 minutes that chose to enroll and at least 1 whose enrollment expires. This will (according to our current implementation) trigger a quorum reshuffling in every 10 minutes. I assumed that the number of total validators always stays 1000 and the number of attackers stays 50.
Pat least 1 validator is befouled after X quorum suffling = (1 - (Pno validators are befouled after 1 quorum suffling)X)
Pno validators are befouled after 1 quorum suffling = (Pone randomly chosen validator is not befouled after 1 quorum shuffling)950
Pone randomly chosen validator is not befouled after 1 quorum shuffling = (1 - (Pone randomly chosen validator is befouled after 1 quorum shuffling))
Pone randomly chosen validator is befouled after 1 quorum shuffling = (50 / 1000) * (49 / 1000) * (48 / 1000) * (47 / 1000) * (46 / 1000) + (50 / 1000) * (49 / 1000) * (48 / 1000) * (47 / 1000) * (46 / 1000) *  (45 / 1000)
Pat least 1 validator is befouled after 10 days =
( 1 - ((1 - (50 / 1000) * (49 / 1000) * (48 / 1000) * (47 / 1000) * (46 / 1000) + (50 / 1000) * (49 / 1000) * (48 / 1000) * (47 / 1000) * (46 / 1000) * (45 / 1000))^950)^(10 * 24 * 6)) = 0.30473860327
Let me know if my calculation is incorrect and in fact it is me who got befouled.

 // `valueExternalized` is called at most once per slot when the slot externalize its value.
    virtual void
    valueExternalized(uint64 slotIndex, Value const& value)

https://github.com/stellar/stellar-core/blob/master/src/scp/SCPDriver.h#:~:text=// `valueExternalized` is called,Value const%26 value)

I think if we sign after the externalize phase and the above event is called from the SCPDriver we are ok.

I think so too, but we still have to make sure we never again sign a block at the same block height(for example during catchup). As the block we signed during the externalize phase might not be the right block(if the node is befouled)

I think so too, but we still have to make sure we never again sign a block at the same block height(for example during catchup). As the block we signed during the externalize phase might not be the right block(if the node is befouled)

Yes I was also thinking about that. I think we might need to save to a file our signature for block height and read from this file on catchup so that we can not be tricked into signing a different block hash for the same height.

There is still an edge case where we do a clean restart and then we have to trust catchup information from other nodes. Maybe we should not sign blocks in that scenario to be on the safe side.

The problem is that the validator should remember that he signed a block and never forget it. But what if

I just copy my entire handrive with all the validator's data into a new computer (so it will not look like a fresh restart)
start validating on my old computer and got befouled and signed a block, later I switch off this computer
start my new computer that starts to catchup (doesn't look like a fresh restart), and sign a different block a the same height as I cannot remember what I signed.

The problem is that the validator should remember that he signed a block and never forget it. But what if

I just copy my entire handrive with all the validator's data into a new computer (so it will not look like a fresh restart)
start validating on my old computer and got befouled and signed a block, later I switch off this computer
start my new computer that starts to catchup (doesn't look like a fresh restart), and sign a different block a the same height as I cannot remember what I signed.

Then the only safe thing is to not sign blocks during catchup in any scenario.

Yes, that is what I was thinking too.


Possible support for swedish Branch ID

Hello! Are there any plans for adding support for Swedish branch id when using the IbanBuilder?
Here's some related documentation on the clearing number, that might help (unfortunately in Swedish):
bankernaskontonummeruppbyggnad_anvandarmanual_sv.pdf
Best regards,
William

Data related to this https://github.com/Bankinfrastruktur/BankData
(The pdf you provided is actually dual language)
Another resource for IBAN is at (this one Swedish only) https://www.bankinfrastruktur.se/framtidens-betalningsinfrastruktur/iban-och-svenskt-nationellt-kontonummer
Keeping track of all possible national BBAN validation is probably out of scope of a IBAN validation library.
Also, you might not want to limit any input to "known banks" since there is infrequent changes to that list.

Haha thanks @NiKiZe, beat me again. It is a similar discussion idd as #139
What we can do is consider these use cases and come up with an abstraction, but the actual implementations would have to live elsewhere.
eg. the BbanBuilder could accept an ICheckDigitCalculator and for example a custom factory method to 'extract' anything not part of the registry (in this case the clearing number).
I could help facilitate this, but the community would have to supply concrete implementations per country and/or bank.

@WilliamWirsen any chance you can expand on what you had in mind here?
Several of the clearing numbers is not relevant in IBAN at all. examples being clearing 3300 and 6000-6999, you also need "ibanid" which is not always same as clearing.
So what I think you are looking for is a Swedish BBAN generator. But I would like to get that confirmed with an example


Message list: hide footer view if empty

Hide the footer view in message list if empty
Before

After

I mean great if the footer is gone when the message list is empty but why was it needed at all in the first place?
(I would remove it completely)

Thanks a lot for your contribution :heart:
Sorry for the delay in getting this merged.
@szaimen: The footer view is used as a button to fetch more messages from the server ("Load up to X more").

@szaimen: The footer view is used as a button to fetch more messages from the server ("Load up to X more").

Ah okay, thanks for the clarification!
Could the footer also get hidden if all mails in a specific folder are loaded?
(I can of course open a new issue for that, if you want)

@szaimen: This change will hide the footer whenever it would have been displayed as an empty view. So your case is covered by this as well.

@szaimen: This change will hide the footer whenever it would have been displayed as an empty view. So your case is covered by this as well.

Ah okay great! Thanks for for this!


Fix wrong macro being tagged with macro_export

I forgot to tag ìmport_exception with #[macro_export], so now it can't be used by dependent crates.

thanks!


Merge async/await API addition to Combine community support

Merge and style #9820
This is an addition to the community supported Combine library

LGTM

LGTM on the typo, but the OAuthProvider addition doesn't seem to belong into the Combine module.

Thanks, I'll reevaluate


Any reason model methods/properties can't be indexed?

Thanks for this package, it's very helpful.
I have some models that have very few actual fields (that store raw data) and a bunch of properties that parse the raw field into more useful output.
I'd like to be able to add the value of these properties to the search index, but from reading the code, that doesn't seem possible? Is there any reason for this?
I'm willing to contribute a pull request if you think it could be done.

you can actually just set
my_object.search_index = "abc def ghji"
then
my_object.save()
it seems to work for me

+1
It wiil be cool. Like a:
class Page(models.Model):
    name = models.CharField(max_length=200)
    description = models.TextField()
    tree = models.ForeignKey(OtherTree)

    search_index = VectorField()

    @property
    def denorm_tree(self):
         chldstr=""
         for children in tree.get_children():
            chldstr+=children.name
         return chldstr

    objects = SearchManager(
        fields = ('name', 'description'),
        customs_strings = ('denorm_tree'),
        config = 'pg_catalog.english', # this is default
        search_field = 'search_index', # this is default
        auto_update_search_field = True
    )


ERROR: Error: image priceboard/elasticsearch:2.3.3 not found

Getting error while doing docker-compose up

@muke5hy Sorry I forgot to merge upadte_stack to master
It should be fine now. https://github.com/PriceBoardIn/aws-elk-billing/commit/01725313e60c0fd63e74e7565753a398a92e7471


[OneToolchain] Returns the output value as it is

This commit returns the output value as it is.
This allows the log to be displayed and the output to be handled.
ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>fix this bug: https://github.com/Samsung/ONE-vscode/pull/1333#issuecomment-1268162214, #1335

Is this to see logs when prerequisites fails?

Is this to see logs when prerequisites fails?

The #1335 error does not occur in my test environment. However, printing the log will help you determine what happened. So I want to merge this PR.


undefined is not a function (evaluating 'ReactComponentTreeHook.purgeUnmountedComponents()')

Is this a bug report?
(I don't know but it seems to be)

Have you read the Contributing Guidelines?
(Yes)
Environment

Steps to Reproduce

()

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(I deleted the node_module then i installed used the npm install after i run the app using react-native run-android then i got the error

)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Even I had this issue. Fixed it by updating my 'react-native' version to '0.50'.

ok, I will try that.

@kckunal2612 how can I update my react-native? a command please

In your project's root directory, there would be a "package.json" file. In there, there would be a dependencies block like this -
"dependencies": {
...
react-native": "^0.50.3",
...
}
In case you don't have version 0.50 here, you can change the version value for 'react-native' and then run the command 'npm-update' from the terminal. This will update the node-modules directory as well (update contents for this module).

ok
I have also tried this " npm install -git react-native-git-upgrade"
but i am having this warning
"git-upgrade WARN The upgrade process succeeded but there might be conflicts to be resolved. See above for the list of files that have merge conflicts.
git-upgrade info Upgrade done"
and had some errors
error: patch failed: android/app/build.gradle:72
Falling back to three-way merge...
Applied patch to 'android/app/build.gradle' cleanly.
error: patch failed: android/app/src/main/java/com/taximoto/MainApplication.java:25
Falling back to three-way merge...
Applied patch to 'android/app/src/main/java/com/taximoto/MainApplication.java' cleanly.
error: patch failed: ios/TaxiMoto.xcodeproj/project.pbxproj:36
Falling back to three-way merge...
Applied patch to 'ios/TaxiMoto.xcodeproj/project.pbxproj' with conflicts.
U ios/TaxiMoto.xcodeproj/project.pbxproj
any help with this

Got the same error here.
Already tried to update React, react native, all packages and npm but
it dont work:
undefined is not a function (evaluating 'ReactComponentTreeHook.purgeUnmountedComponents()')
I'll keep up and any news I bring here

Hello guys.
I've found this solution
https://reformatcode.com/code/ios/react-native---reactcomponenttreehookpurgeunmountedcomponents-is-not-a-function

In the end, I figured that the versions of react and react-native packages that I were installed didn't "match". I saw the message npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed. (I had a previous version installed because of another warning that I got).

As soon as I installed<EMAIL_ADDRESS>instead, the problem was solved. Apparently facebook has removed the function ReactComponentTreeHook.purgeUnmountedComponents from the code, it is not to be used
It helped me too.

I was facing the same issue after going to  react-native' '0.50'.
now the issue Solved Thanks  @kckunal2612 c

I was facing the same issue after going to react-native version 0.50 issue resolved
Thanks @kckunal2612


Rust dynamic dependencies

It seems when building the plugins within cuckoo miner, cargo adds some dynamic dependencies to rust DLLs, causing loading to fail if they're not on the dynamic linker path. You don't see this issue in cargo, because cargo sets all the environment variables properly, but when running standalone, you might get a message that the plugin directory isn't able to load.
This may propagate into grin... at the moment there are two solutions:
Either add the rust DLLs to the linker path, e.g:
export LD_LIBRARY_PATH=/home/user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib

OR
Build via the plugins via the cmake project, which is at:
https://github.com/mimblewimble/cuckoo-miner-plugins
When building via cmake, these dependencies aren't included, and the DLLs don't have the rust dependency.
I think the long term fix here is to include and use the cmake build instead of building the plugins internally, which will have benefits in that platform can be detected, the presence of CUDA/opencl can be detected and used if present and the right versions of the libraries can be built, etc. The downside is that anything that includes cuckoo-miner (just thinking of grin at the moment,) will need to have cmake installed as a build dependency, and it will take a little while to iron out the cmake build to ensure it works on all platforms.

I agree on using the cmake build instead. We may also eventually publish a binary for each platform to make that easier.


[PW-8057] PaymentResponse does not work on the FraudResult field

Describe the bug
This Go library's definition on the fraudResult field of latest /payments endpoint is wrong. In fact, each FraudCheckResult is nested rather than a flat array.
The actual JSON format is:
"fraudResult": {
    "accountScore": 90,
    "results": [
        {
            "FraudCheckResult": {
                "accountScore": 0,
                "checkId": 2,
                "name": "CardChunkUsage"
            }
        },
    ...
    ]
}

Current definition in this library:
type FraudResult struct {
	// The total fraud score generated by the risk checks.
	AccountScore int32 `json:"accountScore"`
	// The result of the individual risk checks.
	Results *[]FraudCheckResult `json:"results,omitempty"`
}

type FraudCheckResult struct {
	// The fraud score generated by the risk check.
	AccountScore int32 `json:"accountScore"`
	// The ID of the risk check.
	CheckId int32 `json:"checkId"`
	// The name of the risk check.
	Name string `json:"name"`
}

Correct implementation should be:
type FraudResult struct {
	// The total fraud score generated by the risk checks.
	AccountScore int32 `json:"accountScore"`
	// The result of the individual risk checks.
	Results *[]FraudCheckResultContainer `json:"results,omitempty"`
}

type FraudCheckResultContainer struct {
         FraudCheckResult *FraudCheckResult `json:"FraudCheckResult,omitempty"`
}

type FraudCheckResult struct {
	// The fraud score generated by the risk check.
	AccountScore int32 `json:"accountScore"`
	// The ID of the risk check.
	CheckId int32 `json:"checkId"`
	// The name of the risk check.
	Name string `json:"name"`
}

To Reproduce
To reproduce, make a call to /payments endpoint (with fraud-related additional data enabled in Adyen CA), and you will find out the elements inside results array under fraudResult field in API response could not be unmarshalled correctly.
Expected behavior
Should fix the implementation, the Java library implements it correctly, see https://github.com/Adyen/adyen-java-api-library/blob/develop/src/main/java/com/adyen/model/FraudCheckResultContainer.java

Hey @yunpengn,
Thanks for reporting this issue! It has been fixed in the v7 release. The new models reflect server responses correctly now.


Characters.json not needed on Superpower machine

Characters.json not needed on Superpower machine, as it is provided by power source

I think we got to the bottom of this, can this issue now be closed @gtfisher ?


Automatically Validate Docstrings

After changing batches -> iterations, we have some significantly out-of-date documentation. Let's grep over this all over the codebase and figure out what we need to update

Personally I'd vote for just having type annotations in the function signature, which sphinx auto-generates. So (3) wouldn't fail anything. But this decision might have already been made, so ignore me if it has.

Going to use this issue to track automatic docstring validation. Any broken docstrings should either be fixed via PRs or have issues created for them -- it's too broad as written.


Unit test fixes

Recent changes to hipscat package cause tests to fail (and last night's smoke test caught it and emailed me! WAI!).
This addresses new epoch parameter and hive-style directory structures.
Additionally, introduces the pytest-timeout package. This will fail tests that take too long (if not marked for a longer timeout). This is a proxy for code performance monitoring (see https://github.com/lincc-frameworks/python-project-template/issues/79).

Also addresses a sneakier change that makes the destination_pixel_map contain integers.
Code coverage increased with recent commit. See https://app.codecov.io/github/astronomy-commons/hipscat-import/pull/38


Get sample00_rep00_smpl_params.npy

Thank you for your great work! Could you please upload one sample file like sample00_rep00_smpl_params.npy? I have some difficulties when generating motion using MDM and I hope to inference your anime.py first. Thank you very much.

Hi,
Here is the AIST motions you can try.
aist.zip
https://drive.google.com/file/d/1hfKTOudKBVxyPumGowpymGlTXGgHKmPa/view?usp=drive_web
Yuzhou @.***> 于2024年2月12日周一 09:43写道：

Thank you for your great work! Could you please upload one sample file
like sample00_rep00_smpl_params.npy? I have some difficulties when
generating motion using MDM and I hope to inference your anime.py first.
Thank you very much.
—
Reply to this email directly, view it on GitHub
https://github.com/TingtingLiao/TADA/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK473GDLFTTKREROGPESLKDYTGTWXAVCNFSM6AAAAABDEFLQPCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDSNBVG4ZTSMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Please download from here AIST .

Thank you very much for your reply, and I have solved this problem. I have another question, when I use TADA for a motion sequence(e.g., 120-frame), it will output 120 obj and mtl files, do you know how to convert them into a single fbx file and show it in blender? Thank you very much for your attention.

By the way，how to run animate script by using AIST，I got things blow：


Gradle task assembleDebug failed with exit code 1

I am using Ubuntu 20.04 and vscode.
After the two steps:

flutter create
run without debugging

I get the following error message in the debug console:

FAILURE: Build failed with an exception.

A problem occurred configuring root project 'android'.
Could not resolve all artifacts for configuration ':classpath'.
Could not resolve com.google.protobuf:protobuf-java-util:3.4.0.
Required by:
project : > com.android.tools.build:gradle:3.5.0
project : > com.android.tools.build:gradle:3.5.0 > com.android.tools.build:bundletool:0.9.0
Could not resolve com.google.protobuf:protobuf-java-util:3.4.0.
Could not get resource 'https://jcenter.bintray.com/com/google/protobuf/protobuf-java-util/3.4.0/protobuf-java-util-3.4.0.pom'.
Could not HEAD 'https://jcenter.bintray.com/com/google/protobuf/protobuf-java-util/3.4.0/protobuf-java-util-3.4.0.pom'. Received status code 502 from server: Bad Gateway

[...]

BUILD FAILED in 41s
Exception: Gradle task assembleDebug failed with exit code 1

Flutter doctor gives me:
[✓] Flutter (Channel stable, 1.22.5, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[!] Android Studio
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (1 available)
! Doctor found issues in 1 category.
Could you please let me know how to resolve this issue?
Cheers!

I just fixed it. I have multiple java versions installed and had to change it to the java-11-openjdk one using the following command:
sudo update-alternatives --config java
The error messages above were not really helpful for troubleshooting the issue..


Chrome Dump memory consumption

When using models with large file in it  (like Chrome Dump (System.Data.SQLite.dll))
the empire agent process is loading memory to 600k-500k for the task to be completed.
after it's finish the process normalize to ordinary memory usage - around 35k ~
this thing is very not normal and can cause anomaly detection to find my Agent while it is overloading.
This issue appear to be in more modules that send large file in it.
like PsInject and Mimikatz

This is because the module is using the embedded dll. Once the dll is put into memory, the memory usage should normalize. This is a tradeoff when using capabilities that contain dlls that need to be loaded and is expected.


Dev tools for html preview

Are there dev tools for the html preview window? It seems the preview window shares the same dev tools as the Atom editor itself and that means when your code hits a breakpoint, it blocks your entire editor's event loop. I think it should be completely isolated.

This may not be possible for the same reason CodePen, JSFiddle, and JSBin, cannot have completely isolated devtools environments.
Otherwise, we would be looking for a much much more advanced implementation than what the objective of this package is looking at.


Crash on 1.20

Game crashes when i try to scroll in resourcepack list
https://mclo.gs/WklyWVu

Can you reproduce this problem with Ok Boomer only? I haven't been able to make this happen in my development environment and it seems to be a compatibility problem.
If you can't reproduce the issue with the mod alone, it'd be great if you can try to figure out which other mod is causing it happen
Cheers

it was ok zoomer, xd, sorry

After some of bytecoding seems it tweakermore https://mclo.gs/iKJqr5w

hmmm, im try to reproduce it with only these mod but it doesnt work

i think it only redirect mixins from other mod

okay, after some test i can say that is it replay mod

if ok boomer get higher index that replay mod it will be crash when i scroll my mouse wheel

bump

oh

If you have indeed isolated it to ReplayMod, I need a log where this crash occurs with only ReplayMod installed to know where to look when debugging

okay, ill try to do it

https://mclo.gs/E9Gwk3A

message (1).txt


fix_third_party: set install libdir and fix spdlog includes

With the update of the third-party libraries, qcor's compilation
crashes when try to link to the gtest and spdlog installed by
xacc. This PR fix that and allows for compilation of qcor without
touching qcor's configuration files.

Hi @acastanedam,
Thanks for the contribution. This all looks good.
Could you please create an Eclipse account and sign the CLA? I can merge this after the ECA validation passes.
Also, please make sure you sign off all the commits with the same email as the email in your Eclipse account. Your git commit didn't have a signature yet.
Thanks!

Hi @1tnguyen ,
thanks for checking it. I did the registration process with ECA and signed the ECLA. About the signature I am not sure, what is happening. On the other, I am not sure if the changes are breaking some of the CI tasks, or this is coming from #569.

The CI check failures above should be fixed in master now. Would you mind merging main into your branch since I don't have write permission? Thanks!

Hi @1tnguyen , excuse me for the delay. I've just re-based on the last master and push.


TS2315: Type 'Event' is not generic.

I've upgraded to latest version:
"jquery.terminal": "^2.5.0",
But seeing the following errors:
ERROR in node_modules/jquery.terminal/js/jquery.terminal.d.ts(403,86): error TS2315: Type 'Event' is not generic.
node_modules/jquery.terminal/js/jquery.terminal.d.ts(404,83): error TS2315: Type 'Event' is not generic.
node_modules/jquery.terminal/js/jquery.terminal.d.ts(531,82): error TS2315: Type 'Event' is not generic.
node_modules/jquery.terminal/js/jquery.terminal.d.ts(531,82): error TS2315: Type 'Event' is not generic.
node_modules/jquery.terminal/js/jquery.terminal.d.ts(531,82): error TS2315: Type 'Event' is not generic.
This is my versions:
"jquery": "^3.4.1",
"@types/jquery": "^3.3.29",
"typescript": "~2.9.2",
I'm assuming something needs to be upgraded. Any suggestions to what?
Thanks.

Latest typescript is 3.4 not sure if it will work with 2.9 can you test if upgrading typescript fix the issue. The repo don't include typescript because it only use it to test type checking, and users may don't use typescript.

Or maybe the issue is jQuery 3.4 will check later today.

the problem is @types/jquery they made breaking change without changing version to 4.x.x it works with version 3.3.6

The problem is that in jQuery Terminal I use same names as in jQuery I use inherit from JQuery and overwrite the function but because of TypeScript I need to write same signature for original function from jQuery and those changed, they don't affect code that use jQuery but if affect jQuery Terminal (because terminal instance of jQuery object with additional methods) and it will break the code each time they change the signature of overwritten functions.
Will update the typescript definition and set fixed version of @types/jquery, I hope this will not break other peoples code in the future.

We've downgraded to types version 3.3.6, that seems to work.
Thank you for addressing this.
And thank you for a very cool project. Keep up the good work :-)

The types got fixed and the version of types got freezed.


verasaw logo update

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Hi, I am getting same error but couldn't fix it
As I see you already fix it , could you please let me know how you did it?

Hi, I am getting same error but couldn't fix it As I see you already fix it , could you please let me know how you did it?

where are you getting the error and what type of error

https://github.com/solana-labs/token-list/pull/11652

Hi, I am getting same error but couldn't fix it As I see you already fix it , could you please let me know how you did it?

where are you getting the error and what type of error

#11652

I am trying to change logo


Restore OSSF Scorecard pipeline

closes #50

Running on https://github.com/ada-url/idna/actions/runs/12438767777/job/34731292350


moved Tips for Using CLI from Azure/azure-cli repo

Docs Build status updates of commit 3d6dc81:
:clock10: Full build: the average full build time is 7 min(s) 56 sec(s), this is based on the last 772 build(s) for this repository.

Docs Build status updates of commit 3d6dc81:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/TOC.yml
:warning:Warning
View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid) View (azure-cli-latest)
Details

docs-ref-conceptual/use_cli_effectively.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/TOC.yml

Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).

docs-ref-conceptual/use_cli_effectively.md

Line 108: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/overview?toc=./ref/toc.json&view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 108: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/overview?toc=./ref/toc.json&view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 108: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/overview?toc=./ref/toc.json&view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/resources/application?view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/application-update?view=graph-rest-1.0&tabs=http' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/resources/application?view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/application-update?view=graph-rest-1.0&tabs=http' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/resources/application?view=graph-rest-1.0' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/graph/api/application-update?view=graph-rest-1.0&tabs=http' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 132: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_quoting_rules' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 132: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_quoting_rules' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 132: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_quoting_rules' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).
Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).
Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).
Line 155: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_splatting' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 155: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_splatting' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 155: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_splatting' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4868be2:
:clock10: Full build: the average full build time is 7 min(s) 56 sec(s), this is based on the last 773 build(s) for this repository.

Docs Build status updates of commit 4868be2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/TOC.yml
:warning:Warning
View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid) View (azure-cli-latest)
Details

docs-ref-conceptual/use_cli_effectively.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/TOC.yml

Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).

docs-ref-conceptual/use_cli_effectively.md

Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).
Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).
Line 133: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/quoting-issues-with-powershell.md).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 64ea3a4:
:clock10: Full build: the average full build time is 7 min(s) 57 sec(s), this is based on the last 775 build(s) for this repository.

Docs Build status updates of commit 64ea3a4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/TOC.yml
:warning:Warning
View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid) View (azure-cli-latest)
Details

docs-ref-conceptual/use_cli_effectively.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

docs-ref-conceptual/TOC.yml

Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).
Line 0: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-conceptual/use-cli-effectively.md).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


DBeaver Freezes and Has High CPU Usage with Large Scripts

Description
DBeaver 24.0.3 and 24.0.4 freeze when performing certain actions on large script files (5,000 lines for example).  This behavior began with 24.0.3 and I have verified that 24.0.2 behaves normally with the same large files.  At first, I thought the app had completely hung, but I eventually realized that it will return to normal if I let it sit for 5 - 15 minutes depending on the script and system specs.  During this time, the app is constantly using 10% - 25% CPU depending on system specs.  I tried a clean install of 24.0.4 on a system that never had DBeaver and I get the same bug.  If I then uninstall it and install 24.0.2, everything is fine.  Some of the actions that cause the freeze are:

Open or save the file
Change the active datasource
Change the active catalog/schema

As mentioned above, the app eventually returns to normal after a considerable wait.  When executing the script, everything runs normally.  In previous versions of DBeaver I have worked with scripts up to 50,000 lines with no issues, but now it trips up on even a few thousand.  Below is an example of the types of statements in these scripts.  So far I have had the problem with INSERT or UPDATE statements, but haven't tried any deletes lately.
Example script lines:
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '17-20AR-29' AND REVISION_LEVEL = '';
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '33K1-4-716-1' AND REVISION_LEVEL = '';
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '33K2-4-46-1' AND REVISION_LEVEL = '';
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '33K3-4-2925-1' AND REVISION_LEVEL = '';
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '33K3-4-3410-1' AND REVISION_LEVEL = '';
UPDATE PROCS SET IS_ACTIVE = '0' WHERE PROC_NAME = '33K3-4-3554-1' AND REVISION_LEVEL = '';
DBeaver Version
24.0.3 Community
Operating System
Windows 10 Pro
Database and driver
Database:  Microsoft SQL Server 2014
Driver Name:  MS SQL Server / SQL Server
Steps to reproduce
No response
Additional context
No response

Could you try switching this setting to Always?

Does it help?

Yes, setting that to Always fixed the issue.  Looks like I gave Smart too much to think about!

Thank you. I think we should disable this heuristics for big scripts.

We turned off Smart mode for Blank line is statement delimiter setting by default. However, we still need to fix the issue


Ignition configuration with VMware not aligned with stable image 2345.3.0

We are currently in the process of transitioning from Core OS on VMWare as its EOL has been announced.
There is a section in the documentation about migrating from Core OS with regards to VMWare .
It states the following:

Optional: Instead of coreos.config.data and coreos.config.data.encoding for the VMware guestinfo.VARIABLE command line options you need to use ignition.config.data and ignition.config.data.encoding. As for the kernel parameter this change was done upstream by the Ignition project.

When following this information the virtual machine cannot be started. Instead an error is produced stating that these vApp properties do not exist.
Having a look into the current stable (2345.3.0) image the following entries surface:
<Property ovf:userConfigurable="true" ovf:type="string" ovf:key="guestinfo.coreos.config.data" ovf:value="">
  CoreOS config data
  <Description>Inline cloud-config data</Description>
</Property>
<Property ovf:userConfigurable="true" ovf:type="string" ovf:key="guestinfo.coreos.config.url" ovf:value="">
  CoreOS config url
  <Description>URL to cloud-config data</Description>
</Property>
<Property ovf:userConfigurable="true" ovf:type="string" ovf:key="guestinfo.coreos.config.data.encoding" ovf:value="">
  CoreOS config data encoding
  <Description>Encoding for cloud-config data</Description>
</Property>

So the current stable image does not align with what is stated in the documentation (not sure if the documentation is ahead of the stable image). Usage of former variables guestinfo.coreos.config.data and guestinfo.coreos.config.data.encoding is still required.
Affected version: 2345.3.0
Platform: VMWare

Yes, correct, we got a report already and fixed it for the next release (not yet published) by adding the new generic variables to the OVF XML template. We have to fix it in the docs until the release is done.

Thanks for reaching out.
Let me know if contribution is wanted.

I've tried to make this temporary situation clearer here: https://github.com/flatcar-linux/docs/pull/59
Pointing out bugs is already very helpful, also in the docs (PRs are welcome). Thanks for reporting!

Reopening as we've received information on this issue still affecting some users after the 2345.3.1 release.

https://github.com/flatcar-linux/ignition/pull/11 fixes support for both guest variables. In https://github.com/flatcar-linux/scripts/pull/56 the old variables are removed from the OVF metadata but will continue to work when specified via ovftool --X:guest:coreos.config.….


proxy/envoy image build fix

Currently when building images on MAC for linux overriding OS with  GOOS=linux, make ignores GOOS and copies envoy binary matching local os. With his PR, when GOOS specified, envoy of correct OS gets installed into the image.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ldemailly
Assign the PR to them by writing /assign @ldemailly in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: sdake
Assign the PR to them by writing /assign @sdake in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3d6cde9c2fb3e1c8ea7b091de487219334f1bed3
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
0e69f9288884714552e42dcfd9517c6ff8ba0dce
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo

@costinm Tiny fix for image building, appreciate your input..

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Maintain send window only if ExchangeMergeSortSourceOperator

Continue of previous pr pr-2051 、pr-2170
Since normal ExchangeSourceOperator needn't keep order at receiver side, therefore, the sender does not need to maintain the sending window

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest


[TUS] Cleanup/expire unfinished uploads

As far as I remember we still need to implement something.
Tusd doesn't implement the expiration extension: https://github.com/tus/tusd/issues/176
We might want to sync this up with token validity, because after that one expires there is anyway no way to resume.
@butonic please add your thoughts, I remember you worked on token but not sure if expiration was implemented as well.
In my local dev env I see stray unfinished uploads from a few days ago, so I assume it's isn't implemented.
@micbar FYI

still needed.

Any information about theme?

Any information about theme?

@mobilesfinks what do you mean? This issue is about TUS upload functionality, don't see how it connects to theme/theming? 🤔

Please open again if the ticket is still relevant

Cleanup commands were implemented.


[Feature Request] - Add Bot Auto Assign Lable

Is your feature request related to a problem ? Please describe. ✍
To automatically add a bot based on the assigned label when creating an issue via Github Actions

Describe breifly how would you implement the same.
1. Create a GitHub Actions workflow file, such as .github/workflows/issue-labeler.yml, in project's repository.
2. create support advanced-issue-labeler.yml in .github to mapped connnection
3. Final Integration

Additional context
No response
Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the CONTRIBUTING GUIDELINES of this project.

Successfully Implemented


Query on integrating pytest-fastest to CI tool travis

Hi team, we had travis as ci tool, where the existing pytest module takes almost ~49 min time. My ask is, I understood pytest-fastest, but the query I had in my mind is the file generated by this pkg i.e. .fastest.coverage, how come the master .fastest.coverage file will get updated by PR. When running travis ci env. If I run locally, it may skip existing but in ci tool all test will be skipped if I am correct.  The updated file .i.e .fastest-coverage at ci run, should need to be merged or not?
OR
my understanding here, .i.e locally generated file .fastest.coverage can ignored as a commit, as pytest-fastest depends on git diff?
Please assist with the information.

just raised to get some info, NP. Got some alternative for now. Thanks


Add scipy.interpolate API

Adds a number of classes that replicate most of the functionality of the corresponding classes from scipy.interpolate:

scipy.interpolate.PPoly -> interpax.PPoly
scipy.interpolate.Akima1DInterpolator -> interpax.Akima1DInterpolator
scipy.interpolate.CubicHermiteSpline -> interpax.CubicHermiteSpline
scipy.interpolate.CubicSpline -> interpax.CubicSpline
scipy.interpolate.PchipInterpolator -> interpax.PchipInterpolator

Resolves #6
Resolves #19

Codecov Report
Attention: Patch coverage is 97.36842% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 97.92%. Comparing base (3c66c30) to head (0fa0231).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
+ Coverage   91.56%   97.92%   +6.35%
==========================================
  Files           6        7       +1
  Lines         759      965     +206
==========================================
+ Hits          695      945     +250
+ Misses         64       20      -44

Files
Coverage Δ

interpax/__init__.py
100.00% <100.00%> (ø)

interpax/_fd_derivs.py
99.52% <100.00%> (+23.44%)
:arrow_up:

interpax/_spline.py
97.73% <100.00%> (ø)

interpax/utils.py
87.50% <100.00%> (+20.83%)
:arrow_up:

interpax/_ppoly.py
96.93% <96.93%> (ø)


Since "docker tag" does not validate IP address, docker pushes images that can never be pulled

"docker tag" does not validate IP address and port. Due to this issue, docker pushes images that can never be pulled. <IP_ADDRESS> below is a valid local IP address on the host and can be pinged.
$ docker version
Client:
Version:      1.10.1
API version:  1.22
Go version:   go1.5.3
Git commit:   9e83765
Built:        Thu Feb 11 19:27:08 2016
OS/Arch:      linux/amd64
Server:
Version:      1.10.1
API version:  1.22
Go version:   go1.5.3
Git commit:   9e83765
Built:        Thu Feb 11 19:27:08 2016
OS/Arch:      linux/amd64
$ docker info
Containers: 2
Running: 2
Paused: 0
Stopped: 0
Images: 344
Server Version: 1.10.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 321
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.2.0-27-generic
Operating System: Ubuntu 14.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.42 GiB
Name: kolla-ubuntu
ID: CH5Y:PDT2:ZGWS:F6OG:HNUG:6A2D:DZ3D:M7WZ:2O5W:EFOJ:Y47G:IRDZ
WARNING: No swap limit support
Additional environment details:
Ubuntu 14.04, Docker version 1.10.1 (build 9e83765),
Storage Driver: aufs, Kernel version (4.2.0-27-generic)
Docker daemon running:
$ ps aux | grep docker
root      3493  1.0  0.1 1156028 59376 ?       Ssl  17:57   0:32 /usr/bin/docker daemon --insecure-registry <IP_ADDRESS>:4000
root      3566  0.1  0.0<PHONE_NUMBER>6 ?        Sl   17:57   0:05 docker-proxy -proto tcp -host-ip <IP_ADDRESS> -host-port 4000 -container-ip <IP_ADDRESS> -container-port 5000
root      3585  0.1  0.0<PHONE_NUMBER>0 ?        Ssl  17:57   0:04 /bin/registry /etc/docker/registry/config.yml
Steps to reproduce the issue:

Run the following commands. <IP_ADDRESS> below is a valid local IP address on the host and can be pinged.

`
$ docker tag ubuntu <IP_ADDRESS>:4000/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7778:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7779:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7780:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7781:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7782:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7783:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7784:99999999/myfirstimage
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage`
Result received:
`$ docker images | grep myfirstimage
1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7778:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7779:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7780:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7781:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7782:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7783:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7784:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage   latest              14b59d36bae0        2 days ago          188 MB
<IP_ADDRESS>:4000/myfirstimage                           latest              14b59d36bae0        2 days ago          188 MB
The images with invalid IP address and port cannot be pulled ever. See below.
$ docker pull 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7777:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v1/_ping: dial tcp: unknown port tcp/99999999
$ docker pull 1111.2222.3333.4444.5555.6666.7778:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7778:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7778:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7778:99999999/v1/_ping: dial tcp: unknown port tcp/99999999
$ docker pull 1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7785:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7785:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7785:99999999/v1/_ping: dial tcp: unknown port tcp/99999999
`
The image with valid IP address and port can be pulled fine.
$ docker pull <IP_ADDRESS>:4000/myfirstimage
Using default tag: latest
latest: Pulling from myfirstimage
Digest: sha256:cf852d4ef13b95dd3f33dbe19f673e0d45d0716f27eaa8b62964766532f81918
Status: Downloaded newer image for <IP_ADDRESS>:4000/myfirstimage:latest
Results expected:
`
$ docker images | grep myfirstimage
<IP_ADDRESS>:4000/myfirstimage                           latest              14b59d36bae0        2 days ago          188 MB
`
No other image with invalid IP address and port should be pushed as they cannot be pulled.

I don't see anywhere that you did a push. When I try I get an error:
# docker tag ubuntu 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage

# docker push 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage
The push refers to a repository [1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage] (len: 1)
unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7777:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v2/: dial tcp: lookup 1111.2222.3333.4444.5555.6666.7777: no such host
 v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v1/_ping: dial tcp: lookup 1111.2222.3333.4444.5555.6666.7777: no such host

I do not have to push manually. I see docker automatically pushes when I run docker tag. Check docker images after doing docker tag.
$ docker tag ubuntu 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage
Docker pushes 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage too at this point.
$ docker images | grep my first
1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage                latest              14b59d36bae0        2 days ago          188 MB

Docker does not push images when you tag them.
The docker images command shows your local images, not remote ones.

These images I see in "docker images" cannot be pulled at all. Is there a way to pull these ?
Docker should check if the tag has an invalid IP address or invalid port, and should not add such images (with invalid IP address or invalid port) when tagged ? Right ?
$ docker images | grep myfirstimage
1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7778:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7779:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7780:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7781:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7782:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7783:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7784:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB
1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage latest 14b59d36bae0 2 days ago 188 MB

I recommend taking a look at the getting started docs: http://docs.docker.com/mac/started/
They should help clear up some of the confusion. I recommend going through the whole thing, but note the "Tag, push, and pull your image" section.

I read the docs. I see these errors when I pull.
$ docker pull 1111.2222.3333.4444.5555.6666.7777:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7777:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7777:99999999/v1/_ping: dial tcp: unknown port tcp/99999999
$ docker pull 1111.2222.3333.4444.5555.6666.7778:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7778:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7778:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7778:99999999/v1/_ping: dial tcp: unknown port tcp/99999999
$ docker pull 1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage
Using default tag: latest
Error response from daemon: unable to ping registry endpoint https://1111.2222.3333.4444.5555.6666.7785:99999999/v0/
v2 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7785:99999999/v2/: dial tcp: unknown port tcp/99999999
v1 ping attempt failed with error: Get https://1111.2222.3333.4444.5555.6666.7785:99999999/v1/_ping: dial tcp: unknown port tcp/99999999

You can't pull images from another docker instance anyway. You wouldn't be able to push these either unless the address is valid.
A tag is just a reference to an image and an image can have many tags.

It it ok to show images in the output of docker images that can neither be pushed nor pulled ?
An image like 1111.2222.3333.4444.5555.6666.7785:99999999/myfirstimage can neither be pushed nor pulled. Shouldn't there be a note about this in the documentation for docker tag in https://docs.docker.com/engine/reference/commandline/tag/ ?

docker images shows images that exist on the host. Having a push/pull-able tag does not matter.