Add readme

Signed-off-by: Mengyi<EMAIL_ADDRESS>

The readme is very good. I added some inline comments.
I'm yet to test the commands and provide feedback on those.

I noticed that the README is missing instructions for running the tests in the snap. This would be very useful to run tests in isolation. It should actually be the preferred way to run tests.

@farshidtz  Thanks a lot for your review. I have add a Run tests using checkbox-edgexfoundry snap in isolation (recommend) section.

Excellent. Can we then delete the old draft document at https://docs.google.com/document/d/1KK3vfxANapKqkzNlP_ai1yczlvp3gfqQnvhRXv-v12Y/edit#heading=h.qjjnvsuim13r ? Is there anything in there that's not covered here?

Thanks. I'm going to merge and defer minor polishing to another PR.
Thanks a lot @MonicaisHer

@siggiskulason I think this README covered your HOWTO documentation. Thank you!

I forgot to squash before merging and that created a mess. I force pushed a squashed version.


eCarePlanner 3.1.1 - no option to select eGFR dataset

There are supposed to be datasets displayed here for user selection, but this dropdown is blank:

Removed per design

eGFR is calculated from 2 other labs. The formula that was used included a variable for black/not-black which introduces a racial bias. Look at LOINC codes and what's being returned by labs.
Jacqueline to ask Michelle and/or Dr. Dorr.


Page  Appears as the Last Element in  in Svelte 5

Describe the bug
After updating a SvelteKit project to Svelte 5, the page title appears last in the  section. The order of elements shows the title after the og tags, description, and other metadata. You can observe this by visiting any Svelte 5 project, such as svelte.dev.

Reproduction
Visit any Svelte 5 Deployed site. ex: svelte.dev and view the page source code.
Logs
No response
System Info
noun

Severity
annoyance
Additional Information
No response

Who is this annoying?

👍


#each property value is not shown

Hey,
I tried to use the each argument by using:
	{{#each LoggerExceptions}} 				<div class="row"> 					Message: {{Message}} 				</div> {{/each}}
but it does not seem to emit the values of each item in the collection. the each itself does work and is omitting multibel div's but non is filled with values

It seems to be a problem when the collection that is used in the each, contains complex objects. With primitive values it is working but not with complex ones

Steps to Reproduce:
Use the latest NugetPackage.
Create model:
class TestObj
{
	public string Test { get; set; }
}
dynamic temp = new ExpandoObject();
temp.LoggerExceptions = new List<TestObj>();
temp.LoggerExceptions.Add(new TestObj() { Test = "TD" });
var body = templateModel.ParsedTemplate(temp);

Template is:
`{{#each LoggerExceptions}}

	Message: {{ Test }}

{{/each}}`


Suricata and moloch?

What is the relationship between Suricata and moloch? What requirements can this plugin solve?

For support questions use https://moloch-fpc.slack.com (sign up at http://slackinvite.molo.ch/)
https://github.com/aol/moloch/wiki/Settings#Suricata


FOPTS-215 - Budget Alerts Policy Redux

Description
New budget API policy
Issues Resolved
Create a new budget alerts policy to use the new budget API.
Contribution Check List

[x] All tests pass.
[ ] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

Can we see the demo ? Have few questions in the JavaScript code


Bug with showing branch

The git branch is missing if inside a folder inside a submodule.
To recreate:
Create a repository "test" and add a submodule-repository "test2" inside "test". Then create a normal folder "src" inside the submodule. The branch will not show inside the folder "src"

can you show dir tree?

Inside "src" it is not showing the branch, but it works when inside "test" and "test2". Note that "test2" is a submodule inside "test", and "src" is just a regular folder

-- test
   -- .git
   -- test2
        -- src
           --- somefile

like this right?

Yes pretty much.
-- test
-- .git (folder)
-- .gitmodules
-- test2
-- .git (file)
-- src
--- somefile

hmm  -- .git (file) what does mean? test 2 has a .git folder?

No it's a file which is named .git. I think it's created when adding a submodule. It's only one line in it, which is:
gitdir: ../.git/modules/test2

so  we got gitdir = ../.git/modules/test2

Yes. To get the exact same setup as me, create two private repos on github named "test" and "test2". Then do this:
git clone git@github.com:glepnir/test.git
git submodule add git@github.com:glepnir/test2.git
cd test/test2
mkdir src
cd src
vim testfile

Then you will see that there is no branch showing up

if you delete the .git file it will work

Ok, but is it possible to create a fix for this with the .git file there? Since it is created by default when adding a submodule

should be fix by default. but I don't have today. @joshuachp can you take a look at this .PR welcome:)

It's has_git_dir in provider_vcs.lua which is the problem. When inside src it does not find a file or directory named .git, so it goes back to test2. Here it finds the .git file and returns the relative path from this folder and not the starting-folder.

Yes the relative path is the problem, writing PR with fix.

Tested locally and seams to work. Please let me know :)
I'm letting lua io:open work out the absolute path for the HEAD file, so we don't have to implement a function to compute the absolute directory

Sorry there was an error checking for the parent_path. Forced pushed the new changes

It works for me as well! Thank you!


Adding scripts to deploy required plugins on sandbox from CDAP hub.

Added a script to deploy required plugins from Hub which are not present by default in CDAP studio. Using the Hub API for the Plugin deployment. (Hub API)
Flow :-

Add the plugin name and version in  required_plugins.yaml which you want to deploy on the sandbox.
Once the sandbox is created we read the plugin name and plugin version added in  required_plugins.yaml and the upload_required_plugins.py script is called which will upload each plugin one by one on default namespace.

2 tests failing due to intermittent issue, merging the PR as it is approved.


During the process of synchronizing directories using UploadDirectory, if a directory gets deleted, an exception will be thrown immediately, causing termination.

During the process of synchronizing directories using UploadDirectory, if a directory gets deleted, an exception will be thrown immediately, causing termination.

Does it?
Details? Logs? Under which circumstances?

Throw a File Not Found exception, it can be caught using catch.
RecordFileToUpload()
catch (FileNotFoundException e)
{
ftpResult.IsFailed = true;
ftpResult.Exception = e;
results.Add(ftpResult);
logger.LogError($"未找到文件:{e.Message}");
}


Undo_Send XHR observe not working

Just noticing the undo_send observe event is not firing... created this small example from boiler plate to test it.  https://github.com/petegordon/gmailjs-node-boilerplate

Hum... I do remember adding it for my project back then and pushing, but my project died a long time ago so I'm not using it anymore. I'm sorry but I won't be able to provide a fix soon - but it should be pretty straightforward to debug. I would say simply log action before line https://github.com/KartikTalwar/gmail.js/blob/master/src/gmail.js#L963 and check if the action_map is still fine, maybe Google changed it since then?
Good luck


DS-295 remove xsmall icon size

Jira
https://pegadigitalit.atlassian.net/browse/DS-295
Summary
Removes xsmall size from Icon component that was added by mistake.
Details

Removed xsmall from icon schema.
Removed size prop value from 2 Academy pages where it's not needed at all.

How to test
Run the branch locally and check the the 2 Academy pages: Dashboard and Dashboard (My Missions). Make sure the chevron down icon for the decision hub version dropdown is matching the text's font size.

...the "right" thing to do is deprecate it, but it does feel a lot cleaner to just remove it.

@remydenton the icon schema change this PR reverts hasn't actually been released yet. So there shouldn't be any conflicts downstream. The Academy edits just proactively remove invalid usage.

...the "right" thing to do is deprecate it, but it does feel a lot cleaner to just remove it.

@remydenton the icon schema change this PR reverts hasn't actually been released yet. So there shouldn't be any conflicts downstream. The Academy edits just proactively remove invalid usage.


请教下composer执行报错如何处理?

首先非常感谢作者的付出,想尝试用这套东西对生产环境进行java和php代码的deploy,希望可以得到你的支持,多谢~
OS:CentOS 6.7 x64
PHP:5.4.45
[root@CentOS67 walle-web]#  /usr/local/bin/composer install --prefer-dist --no-dev --optimize-autoloader -vvvv
Loading composer repositories with package information
Installing dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- yiisoft/yii2 2.0.6 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.5 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.4 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- Installation request for yiisoft/yii2 >=2.0.4 -> satisfiable by yiisoft/yii2[2.0.4, 2.0.5, 2.0.6].
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion for more details.

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

上面的问题OK了
执行composer install --prefer-dist --no-dev --optimize-autoloader -vvvv的时候报如下错误
Could not fetch https://api.github.com/repos/jquery/jquery, please create a GitHub OAuth token to go over the API rate limit
Head to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+CentOS67+2015-11-15+0543
to retrieve a token. It will be stored in "/root/walle-web/auth.json" for future use by Composer.
Token (hidden):
No token given, aborting.
You can also add it manually later by using "composer config github-oauth.github.com "
这个token应该设置为什么呢?多谢!

搞定了,在github上生成一个token就OK,不过哦之后的install操作很慢...应该是墙的关系


Feature Request: Public Mobile

Since PM is owned by telus I was wondering if it was possible to include in the support as it would fall in the scope
https://www.publicmobile.ca
Thank you

Hey I haven't done much with this script for a while, but let me take a look to see what I can do.


:art: Charge Distribution Surface changes from the ClusterComplete PR

Description
Since Clang-Tidy cannot handle too large diffs, we can try phasing it. Perhaps Clang-Tidy will work on the CC PR after this is merged.
Many files are changed since assign_phyiscal_parameters is now assign_simulation_parameters. I found this to be consistent with the renaming introduced with the pybindings merge.
Additionally, I removed an unnecessary mutex lock (in QuickSim) that I spotted back in november.
Also: I spotted duplicate sidb_charge_state functionality in the CDS bindings, which have their appropriate place and are thus duplicate there.
Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[x] I have created/adjusted the Python bindings for any new or updated functionality.
[ ] I have made sure that all CI jobs on GitHub pass.
[x] The pull request introduces no new warnings and follows the project's style guidelines.

I should mention: CodeCov might complain a little, but this should be ignored. The functionality that is not used (and thus not tested) is used in the CC PR, where CodeCov passes

Confirmed to the bones.
This code is problematic for Clang-Tidy:
    //    /**
    //     * This function can be used to reset all external local electrostatic potentials to 0 Volt. All important
    //     * attributes of the charge layout are updated automatically.
    //     */
    //    void reset_local_external_potentials() noexcept
    //    {
    //        strg->local_external_pot.clear();
    //        this->update_after_charge_change();
    //    }

New insights: it worked earlier because of an unresolved function name error


Obfuscate literals other than strings

Add obfuscation for other literals such as integers, byte slices etc.

Some thoughts:

Zero-value literals might not be worth obfuscating.
Obfuscating all integers might make some code really slow, if those integer literals are in nested/hot loops.
With simpler literals, such as integers or runes, we could perhaps use simpler techniques like xors, additions, shifts, etc instead of encryption.


(Q) How do I insert text or string label into cell?

Hello, WenchaoD
I have a question for you about how to insert text or string label into cell on FSCalendar.
As a swift beginner, I've already executed your demo codes and then found fake title when using interface builder. But I have no idea that how to do.
So my plan is to populate text with cell from Firebase database like the attached file.
Please let me know any tips, APIs and examples.
Thanks in advance!

Jinho

My Development Environment

Device modal and iOS version - iPhoneX and  iOS 11.4.
Xcode version - xCode 9.4, Swift 4.1
FSCalendar version - FSCalenda 2.7.9

func calendar(_ calendar: FSCalendar, willDisplay cell: FSCalendarCell, for date: Date, at monthPosition: FSCalendarMonthPosition) {
    let labelMy2 = UILabel(frame: CGRect(x: 10, y: 20, width: cell.bounds.width, height: 20))
    labelMy2.font = UIFont(name: "Henderson BCG Sans", size: 10)
    labelMy2.text = "abc"
    labelMy2.layer.cornerRadius = cell.bounds.width/2
    labelMy2.textColor = UIColor.init(hex: "#32C77F")
    cell.addSubview(labelMy2)

}

Check link : https://stackoverflow.com/questions/62016056/show-event-label-string-on-calendar-view-ios/62047338#62047338

@synabreu Do you have above demo?


chore: Update go.mod to latest version of k8s/karpenter-provider-aws

Fixes #N/A
Description
Update go.mod to latest version of k8s/karpenter-provider-aws i.e v0.34.1
How was this change tested?
N/A
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.491%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5008

Relevant Lines:
6071

💛  - Coveralls


Add libgflags-dev explicitly

Previously we inherited this from drake/setup/install_prereqs, but as of recently Drake only adds the shared library, not the headers.

This change is

I think the only CI failure is #158.
@EricCousineau-TRI or @jamiesnape (whoever gets here for first) for all review, please.


use diffrent items/blocks to load a schem

im requesting to add more blocks or stuff you can use to generate the schem as i play on a server that dosnt allow armour stands due to lag and exploits.

It can't be a block. I don't plan on doing this. No item other than an
armor stand supports enough queries
On Wed, Aug 18, 2021, 8:25 PM FredTheFriendlyFox @.***>
wrote:

im requesting to add more blocks or stuff you can use to generate the
schem as i play on a server that dosnt allow armour stands due to lag and
exploits.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RavinMaddHatter/Structura/issues/109, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBUC5GLRXURKCUIC4RHCRTT5R2TZANCNFSM5CNJ5LTA
.

thats understandable, a lite version could be made maybe where it can be just a block and the structure dosnt have a layer mode, its a shame it cant be done through an in game menu thats for sure

It is open dice
Source. Feel free to submit a pr. I won't be doing it.
On Wed, Aug 18, 2021, 8:31 PM FredTheFriendlyFox @.***>
wrote:

thats understandable, a lite version could be made maybe where it can be
just a block and the structure dosnt have a layer mode, its a shame it cant
be done through an in game menu thats for sure
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RavinMaddHatter/Structura/issues/109#issuecomment-901581844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBUC5EUTV2OXR7RC4MA3QLT5R3HRANCNFSM5CNJ5LTA
.

no its fine it was only a suggestion, its good that you made this its good work. im not one to ”make” or ”try to make” some one do stuff i know how long this stuff takes so you keep doing what you do my guy


Standalone broker on MacOS often fail to start after workstation sleep or reboot

Describe the bug
Often, but not always, if I start Pulsar standalone on my workstation and then close/reopen my laptop lid or restart the computer, subsequent attempts to start the standalone broker fail. The JVM process keeps running and emits some errors in its logs (see attachment), but never reaches a connectible state.
Repeatedly restarting the broker usually causes this condition to go away. Sometimes that doesn't work, and I have to remove all broker data files (i.e. reinstall Pulsar) to make it start.
This only seems to happen when publishes have been recorded to a persistent topic.
This does not happen when using Pulsar Standalone in Docker, or on my Linux laptop. It appears to be MacOS specific.
To Reproduce

brew install apache-pulsar
brew services start apache-pulsar
Verify that Pulsar is connectible on localhost:6650.
Publish some messages to a persistent topic such that the message data and the topic itself are not automatically deleted (i.e. at least one ledger is created and persists).
Close laptop lid or otherwise induce sleep.
Reopen laptop and attempt to connect to Pulsar; it will sometimes fail.
brew services restart apache-pulsar and attempt to connect to Pulsar; it will sometimes fail.

Expected behavior

Sleep/resume should not break Pulsar. It should either be available after resumption, or the service/JVM process should fully crash so that it reports not-running if it cannot handle connection requests after resumption.
Restarting the service should result in Pulsar either being connectible or not having a JVM process. If Pulsar Standalone can't come up in a connectible state, its process shouldn't hang around (if the process stays around, service managers think it's still running and thus won't report a failure or auto-restart it).

Desktop (please complete the following information):

OS: MacOS monterey, intel.
Pulsar standalone 2.9.2 and 2.9.1 both exhibit this issue.

Additional context
brew services is likely not the problem. It doesn't do anything special, and Pulsar does sometimes work when restarted via brew services.
Attached is a copy of my logs from a broker start attempt that did not become connectible after 5min.
nostart.log

Hmmm, nope; I'm now able to reliably induce this issue on 2.10. Nothing's bound to Pulsar's ports, but it fails to come up.
The logs from a recent start attempt are attached.
pulsar_start.log

I didn't realize you could start pulsar that way, thanks for sharing!
Your issue helped me solve a question I have been wondering about for a while (thank you!).
I think I found the likely root cause of your issue, but you will need to confirm. If I am correct, here is the TLDR: Pulsar discovers its IP address for things like advertisedAddress using a lookup of the hostname, and if your machine's hostname is not defined in the /ect/hosts file, then (based on my troubleshooting) the JVM will perform a DNS lookup on the address and issues can arise when the resulting IP does not route to the right Pulsar process.
Based on your logs, I noticed that some of your stack traces indicate trying to connect to <IP_ADDRESS>:4181:
2022-06-02T13:29:02,974-0400 [client-scheduler-OrderedScheduler-28-0] ERROR org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - Reason for the failure
io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
	at io.grpc.Status.asRuntimeException(Status.java:535) ~[io.grpc-grpc-api-1.45.1.jar:1.45.1]
	at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:533) ~[io.grpc-grpc-stub-1.45.1.jar:1.45.1]
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:562) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:743) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:722) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) ~[io.grpc-grpc-core-1.45.1.jar:1.45.1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: io.grpc.netty.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /<IP_ADDRESS>:4181
Caused by: java.net.ConnectException: Connection refused
	at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
	at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946) ~[?:?]
	at io.grpc.netty.shaded.io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:710) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	at io.grpc.netty.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
	... 1 more

Port 4181 is a bookkeeper port, and for some reason the client is trying to connect to a non-local host, but we already know that the bookkeeper should be running on localhost. I see the same behavior on my host machine:
Caused by: io.grpc.netty.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /<IP_ADDRESS>:4181
Caused by: java.net.ConnectException: Connection refused
        at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
        at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946) ~[?:?]
        at io.grpc.netty.shaded.io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:710) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        at io.grpc.netty.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[io.grpc-grpc-netty-shaded-1.45.1.jar:1.45.1]
        ... 1 more

Interestingly, in my case, Pulsar fails when I am off my work VPN, but it works when I am on the VPN. I've see the same behavior when running Pulsar Standalone, which makes sense since the brew installation is Pulsar Standalone. The nuance comes here: https://github.com/apache/pulsar/blob/76646cfd9496820a6a6dbee225067045235838c0/pulsar-broker-common/src/main/java/org/apache/pulsar/broker/ServiceConfigurationUtils.java#L43-L51. If Pulsar does not have its advertisedAddress configured, it performs this lookup, and that lookup relies on a reverse lookup of your hostname, as described here https://stackoverflow.com/a/18488982. After updating my /etc/hosts file to map my hostname to map my hostname to <IP_ADDRESS>, standalone now works and I've confirmed that 2.10.1 works after putting my Mac to sleep and waking it up again. (I only just realized tonight that Standalone was not previously working because my hostname was not correctly resolving to <IP_ADDRESS>.)
I also noticed that running nslookup on my host name resulted in <IP_ADDRESS> before updating my /etc/hosts file and when off the VPN.
Let me know if this helps.

I've just realized that <IP_ADDRESS> is for network routers, so it is likely that my analysis might not solve your problem. Let me know if any of this is helpful.

@michaeljmarshall you may still be onto something; just because the IP in my logs is an RFC1918 address doesn't mean it necessarily resolves to my host (or a router). I'll try setting advertisedAddress; if that makes the problem disappear, I can check that into the Homebrew formula for Pulsar.

That seems useful. Which of the broker.conf, proxy.conf, standalone.conf and bookkeeper.conf config files should I set advertisedAddress in for a standalone broker?

The brew service command uses standalone mode, which you can see in the formula code: https://github.com/Homebrew/homebrew-core/blob/9441684087afc2c59ef7c6341bc434e3b818a950/Formula/apache-pulsar.rb#L60.
When running Pulsar as a standalone broker, all configuration is passed via the standalone.conf file, so you only need to configure that file.

if that makes the problem disappear, I can check that into the Homebrew formula for Pulsar.

I agree that this configuration makes sense as a default for the Homebrew formula, though it might be worth mentioning it on the dev@ mailing list.
You can set the advertisedAddress in the standalone.conf or on the command line (e.g. bin/pulsar standalone --advertised-address localhost).
https://github.com/apache/pulsar/blob/5bad9b37c183033e597c9cbbe300c20bad429342/pulsar-broker/src/main/java/org/apache/pulsar/PulsarStandaloneStarter.java#L71-L79

@michaeljmarshall sounds good, I'll put that on my to-do list. In the mean time, this bug should probably stay open: the appropriate fix, I think, is to either:
a) Always default advertisedAddress to <IP_ADDRESS> or <IP_ADDRESS> when in standalone mode, or.
b) Find a better way to probe whether the default advertisedAddress is correct; could ARP lookups or something be used? Is that more trouble than it's worth?


Build system should honor CC, CFLAGS, CXX, CXXFLAGS

Build systems for native binaries should honor the environment variables CC, CFLAGS, CXX, CXXFLAGS, LDFLAGS and pass them to compiler and linker invocations.
The idea is that it should be easy to enable special build features like Address Sanitizier, or to comply with distribution hardening best practices.
If these variables are set, they should not override critical flags required by the existing build system.

Here's a proposed tweak:

Build systems for native binaries SHOULD honor the relevant compiler and linker environment variables passed in to them (e.g., CC, CFLAGS, CXX, CXXFLAGS, and LDFLAGS) and pass them to compiler and linker invocations.  A build system MAY extend them with additional flags; it SHOULD NOT simply replace provided values with its own.
DETAILS: It should be easy to enable special build features like Address Sanitizier (ASAN), or to comply with distribution hardening best practices (e.g., by easily turning on compiler flags to do so).

Colin Walters had the same idea: https://github.com/cgwalters/build-api

I've added this as a proposed criterion for the "passing+1" badge level (making it a MUST).


[AutoPR cognitiveservices/data-plane/LocalSearch] add Go SDK codegen for cognitive services localsearch

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4863

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/3664


ReadOnly: "NotInRepo" for workloads that are in the repo.

We're having trouble matching up whats in the repo and whats running in the cluster sometimes.
This has been seen to happen:

when a manifest has changed its namespace.
maybe other times, I'm still having a play..

You can repro it by following this katakoda: https://www.weave.works/docs/tutorials/core/interactive/part-2-deploy-continuous-delivery/

I think anything after the first workload that is NotInRepo also receives NotInRepo. Which covers the two cases I've seen:

namespace change
kube-system < sock-shop


Debugging build issues -> cache problem

Hi there,
when I get errors during my build, they usually look somewhat like this:
PHP Notice:  Undefined variable: translatedBaseUrl in /Users/myusername/Sites/st-website/cache/9db0d9a664659c0f43f0f0e559631e11df734c95.php on line 56
Now because of the file name of the cache file, I don't know where this error occurs. When I click on the file in my console, it can't be opened because it's not there anymore after the build.... how can I debug these problems?
Thank you!

If you get an error like that, the cache directory should still be around, at the top level of your Jigsaw project's directory; 9db0d9a664659c0f43f0f0e559631e11df734c95.php will be in there. That file might be a little cryptic—it's very likely been processed by Blade, so it will be filled with <?php echo statements—but there's also a PATH comment at the bottom of the file that can help you trace the original file, if you don't recognize it from the markup.

Thank you @damiani, you’re right!
Am 27. Aug. 2020, 16:30 +0200 schrieb Keith Damiani<EMAIL_ADDRESS>
If you get an error like that, the cache directory should still be around, at the top level of your Jigsaw project's directory; 9db0d9a664659c0f43f0f0e559631e11df734c95.php will be in there. That file might be a little cryptic—it's very likely been processed by Blade, so it will be filled with <?php echo statements—but there's also a PATH comment at the bottom of the file that can help you trace the original file, if you don't recognize it from the markup.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


About Me Page Familiarization Project Steps 1-4

Closed with
PRs:
https://github.com/FluffySheep/CodeU2019-Team28/pull/27
https://github.com/FluffySheep/CodeU2019-Team28/pull/26
https://github.com/FluffySheep/CodeU2019-Team28/pull/21


Add public traffic configuration for admin/managed servers

-- Add nsgNestedTemplate.json to append NSG rules for admin/managed server
-- Update mainTemplate.json to adopt NSG rules configurations
-- Update clusterTemplate.json to adopt the WebLogic load balancer port configuration
-- Add UI for the configurations
-- Remove legacy sample code

@edburns Hi Ed, could you pls review this PR? It seems that I don't have the authority to add reviewers.

@edburns Hi Ed, could you pls review this PR? It seems that I don't have the authority to add reviewers.


Remove references to exercises from concept docs.

Fixes #1581
Note that there's still a reference right now in the functions concept, I'll address that in PR#1720 to avoid merge conflicts

Thanks for taking care of this. Added some minor changes so I can merge it right away.


Intermediate state in HA

Hi,
Is there a way to read an intermediate state in HA? For example, I set the query interval to 1s, when I put the lock into Lock n Go I see the state in the Nuki Hub FW changes to unlockedNgo - is this reflected in HA somehow? If yes, how can I build an automation off of this? Which entity do I monitor?

This could work, but has some drawbacks:

You'll drain the battery very fast. Unless you've connected your lock to a permanent power source, I'd advice against it.
You block a lot of air time, which could interfere with communication from other devices with the lock.
It could still miss an intermediate state from time to time. I wouldn't automate anything that depends on this to work all the time.

With lock'n'go specifically, there is still the extant issue that locked > lock'n'go > locked does not send the unlocked state via BLE.

@technyon why do you think there would be such a big power waste? I guess the Lock and ESP are in a connection already so I would assume there is not so much data exchanged between them when the topic updates. I would guess that the locking/unlocking operations eat up much more battery than BLE traffic each second. Perhaps I’m missing something tho 🙃
Anyway, I’m using auto discovery, can I continue doing so and register to the state via the MQTT integration or give up the automatic discovery completely?

Normally the lock would be sleeping most of the time, which is obviously not possible when you query it every second. While each query will only use a small fraction of the power used for a lock operation, you will have > 85.000 of those per day.

If the lock and esp are connected then the lock should be sleeping between the BLE connection events anyway. If I query it every second then at one of those connection events it will also send some data. Doesn’t sound like a huge waste but again maybe I’m missing something.

For every query the ESP has to reconnect to the lock, which in itself takes a moment. During this time the lock has isn't sleeping and has to use power for CPU, bluetooth communication and so on. There's a reason why usually the lock notifies the ESP that the state has changed.

Why not just stay connected?
If the lock state changes, will that reflect in the topic immediately?

Because the lock would need to maintain an active connections, which drains the battery
The lock signals that the lock state has changed. NUKI Hub then queries the lock state, which can take a moment. It depends on what your defintion of immediately is, but for most use cases it's fast enough. What's problematic is the "unlatched" state, because it's often too short to be notified via MQTT.

In this case the lock is the advertiser so it needs to send adv packets on all 3 primary adv channels with non-empty payload. When the lock and esp are connected, the payload is an empty packet which is only 10 bytes long and is transmitted only on a single channel.

TLDR, Power profile in Connected state can be better than in adv state.
Only caveat is if the Nuki guys force the locks main cpu (if such exists) to stay awake when the BLE chip is connected which would be very bad practice.

If my query interval is 100 seconds and state changes , this won’t reflect in HA right?

I have no insight of how exactly the NUKI firmware works. They have implemented things in a certain way, and the library that NUKI Hub uses works according to their API documentation.
If you set the query interval to that number, it doesn't take 100 seconds to change. When a state change occured, the lock actively signals that the state has changed using BLE beacons. Once the ESP picks up such a beacon it queries the lock for the new state.

Ah I see, I thought the Hub has some proprietary implementation.
I tried setting the query interval back to what it was but for some reason it didn’t update that way, I’ll try again and report back :)

So I played around a bit with the status entity and what I found is that if I set query interval to default then the status won’t always correctly reflect in the entity I created, especially not for the unlockedNga status. Locked and unlocked does reflect fairly reliably.
Setting the query interval to 2 seconds solves the issue (probably because it forces the esp to go into a connection with the lock and perform a GATT read).
Anyway, IMO, using the adv payload to indicate whether to connect and read the state is not best practice in my opinion.
Staying connected to the lock is probably the way to go. I would guess that the official hub maintains a connection with the lock at all times for both reliability and power consumption.

Hi,
as far as I understand it the Bridge does it the same way. I'd refer you to this thread:
https://developer.nuki.io/t/bluetooth-specification-questions/1109/3
Quoting the important parts:

Normally, the rssi value within the iBeacon data is -60 (0xC4).
If the status of the smart lock changes in any way, that would trigger a new entry in the activity log, the rssi value within the iBeacon changes to -59 (0xC5) and that triggers the bridge.
Once the bridge has connected to the smart lock and fetched the new status, the rssi value changes back to -60.

The last sentence suggests that the bridge opens a new connection to fetch the new status, just as NUKI Hub does.

Oh, thanks for that :)
I guess it’s done to service multiple devices..
In that case the esp should show ulockedNga status even when query interval is long but for some reason it doesn’t …
I guess the scan params of the esp are as Nuki suggests ? 40ms window 40ms interval 3s duration..

Closing as this issue has been stale for 9 months.
Intermediate states can since this issue has been raised now be shown in HA, but usually don't unless setting query interval to a very low amount, which is unfeasible for battery usage. This is a limitation of the BLE communication and can't really be solved. On Nuki Locks with MQTT (3.0 pro, 4.0, 4.0 pro) a combination of WiFi/Thread and BLE can probably be used in the near future to alliviate this problem.


added nginxplus_exporter to list of exporters

NGINX Plus exporter. Exporter using the ngx_http_status_module module which provides access to various status information. This module is available as part of NGINX Plus commercial subscription.
http://nginx.org/en/docs/http/ngx_http_status_module.html

Have you discussed adding this to the existing nginx exporter? I'd prefer that users not to have to run a separate module for every nginx module they use.
You're using direct instrumentation, you should really be using MustNewConstMetric in exporters.

@brian-brazil
Thank you for your feedback.
The other NGINX exporters which are listed on the Prometheus Exporters page are based on custom community nginx modules such as "nginx-module-vts" or using custom lua code.
This exporter is using the official "ngx_http_status" module from NGINX self (only available with the commercial edition of NGINX). Therefore this exporter can only be used when you have a subscription. Besides that this exporter is exposing much more metrics than the other exporters.
I have will have a look at direct instrumentation. The current implementation is based on the official haproxy_exporter.

I don't see how that precludes a merge with others. Can you discuss it with the VTS exporter maintainer?

I did do some research on the the VTS exporter and found that are a lot of differences with the metrics provided by the ngx_http_status_module. Some metrics and labels provided by the VTS module are not available in the NGINX Plus version and vice versa.
I think it 's not a good idea to have one exporter which exposes different set of metrics and labels based on the module you are using. It will require some redesign work of the metrics and labelling if you want to have one exporter to support all nginx status modules (and which are we going to support, because there are many).
I prefer to keep the implementation simple and in line with the metrics provided by the ngx_http_status_module.

Such difference are not at all unknown, both the mysqld and node exporters have that for example. Please chat with the existing exporter maintainer to see if there's a way ye can work together.

Allright. I will try to have a chat with the maintainer of the nginx vst exporter.

Will close this PR. Maintainer of the other nginx exporter did not answer my email.
Besides that NGINX has created a official exporter for both NGINX and NGINX Plus.
Maybe it is a good idea to add this one to the list of exporters, see:
See https://github.com/nginxinc/nginx-prometheus-exporter


Add ASN enrichment to misphunter-host objects

ASN org, City/Country of origin

Potentially use this in the integration - https://github.com/mlaferrera/asparser


Add fork testing chain "base"

if these tests pass good to merge

can also now add a changeset with npx changeset - or that can be done in main


OL8 EPEL Repo comps.xml includes reference to @core with invalid/unavailable package

I'm seeing an issue with the OL8 EPEL Repo, where the RHC package has been added to the core group in the comps.xml file, however this package is not included in the EPEL repo, and so far as i'm aware it's not supposed to be in here as per the 8.4 release notes, https://docs.oracle.com/en/operating-systems/oracle-linux/8/relnotes8.4/ol8-PackageChangesfromtheUpstreamRelease.html
This can be tested for with dnf install @core after adding the epel repo, I am assuming that the epel repo should not have a core group at all.
See: https://yum.oracle.com/repo/OracleLinux/OL8/developer/EPEL/x86_64/repodata/a28d4cdaedc2f2b2d26d86fe24723494622c50c6ed7bd3b14bca095af074900c-comps.xml
  <group>
    <id>core</id>
    <name>core</name>
    <description/>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="default">rhc</packagereq>
    </packagelist>
  </group>

Oracle Linux customers, please file your issue at https://support.oracle.com
Thanks for filing an issue with Oracle Linux.
GitHub Issues is not an official support channel and we don't offer
product support here. If you're not yet an Oracle Linux customer,
consider signing up at https://linux.oracle.com.
Even if you're not a customer, if we can confirm that an issue is a
bug we will do our best to fix it and to update this issue
once it has been fixed. We don't guarantee a fix or feedback and
for now, we will close this issue. If you have Oracle Linux support,
please use support.oracle.com to report issues.

Should be fixed now.


UI: Update AdminUI to use implicit auth flow

Now that we have the implicit auth flow implemented, update the Admin UI login to use it.

We have dropped the UI


Pointers leading to empty objects will stop the queries and show results

I'm using Swift and I had a reference of an object (Pointer Relation). When I queried for the rows of the parent object using includeKey, it returned all objects but the child object didn't indicate a nil object (as it used to in the usual Parse). In this open source server, it seems that object returns even when there isn't any object available but the code breaks when you try to access that child object. I used a little hack by basically checking if the createdAt attribute (which is available for all objects) is nil or not.
I don't know where the issue arises exactly but I'm fairly sure the code breaks in the iOS SDK and probably in other SDKs too. Just letting you guys know that if you see empty results when only one row's child object is pointing to a deleted object doesn't really mean that ALL rows are empty. Something in the SDK is definitely messing up.

That should be fixed by now by #777


Added app.js

Provide a description of your code and a screenshot as  comments.

Created a digital clock using react js

But your code doesn't reflect the output you've given me.
Did you only post the app.js and not the whole project ??
If it is a React project you have to push the whole folder .

Yes this is just a part of it i have many codes

But it would be too much if i push all

It won't be too much. Push your code folder on the Reactjs folder in this repo.
I'll accept it. The output looks really good.


Worker throws exception

Hey,
After #26 got merged to master, the worker now throws an exception
Error: The script will never generate a response.

I checked to an earlier commit, and it works fine.
Steps to reproduce:

Deploy from latest commit in master
Visit the /dashboard route, and you should see something like this:

Can be reproduced in dev as well, without deploying.
I think it is due to the code involving invariant, but not sure.

Also curious, is there any particular reason why all the async functions/promises are written like this (async IIFE inside a Promise constructor):
async function getVisitorCountByColumn(): Promise<any> {
    const returnPromise = new Promise<any>((resolve, reject) => (async () => {
        const response = await this.query(query);

        if (!response.ok) {
            reject(response.statusText);
        }

        const responseData = await response.json() as AnalyticsQueryResult;
        resolve(responseData.data.map((row) => {
            const key = row[_column] === '' ? '(none)' : row[_column];
            return [key, row['count']];
        }));
    })());
    return returnPromise;
}

Can we not write the above like:
async function getVisitorCountByColumn(): Promise<any> {
    const response = await this.query(query);

    if (!response.ok) {
        throw new Error(response.statusText);
    }

    const responseData = await response.json() as AnalyticsQueryResult;
    return (responseData.data.map((row) => {
        const key = row[_column] === '' ? '(none)' : row[_column];
        return [key, row['count']];
    }));
}

+1 I'm also getting this when trying to run the dev server. I've tried running it on both Window 10 and 11 machines with and without WSL.
This is the error I'm seeing in the terminal:
[REMIX DEV] 37ccc3f6 ready
[wrangler:inf] GET / 200 OK (53ms)
Can't save datapoint: Analytics unavailable
[wrangler:inf] GET /collect 200 OK (16ms)
[wrangler:inf] GET /dashboard 500 Internal Server Error (1026ms)
X [ERROR] Uncaught (in response) Error: The script will never generate a response.

Thanks for reporting – and sorry about this. I obviously did not deploy/verify the change. I think I got swept up by "this is mostly types and some runtime checks" and was too casual about it. I've opened #31 and #32 to hopefully minimize this going forward.

is there any particular reason why all the async functions/promises are written like this

The goal was to invoke the query without immediately calling await, so that all the API queries could be parallelized. But you've highlighted that my version doesn't do this correctly. It needs to be changed to invoke this.query, then return the promise.

Closing this now that the issue is resolved, and 24a68f5 addresses the query promise/fetch issue @anurag-roy discovered.

Awesome, sounds good and thanks for resolving things so swiftly! @benvinegar


added missing backslashes to example commands

Coverage remained the same at 100.0% when pulling 90573425d091b11b1230ed375703a53eb304ce49 on modularTaco:patch-1 into 67c7667011d5dc9616ad998f9fa72ac28886c4af on lets-fiware:main.

Coverage remained the same at 100.0% when pulling 90573425d091b11b1230ed375703a53eb304ce49 on modularTaco:patch-1 into 67c7667011d5dc9616ad998f9fa72ac28886c4af on lets-fiware:main.

LGTM. Thanks for the contribution!

LGTM. Thanks for the contribution!


Cannot load such file -- optparse (LoadError)

Hi guys, anyone encountered this issue while installing 2.7.1?
$ rbenv install 2.7.1
Downloading ruby-2.7.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.1.tar.bz2
Installing ruby-2.7.1...

BUILD FAILED (Pop 20.04 using ruby-build 20200224-73-g0a5e059)

Inspect or clean up the working tree at /tmp/ruby-build.20200821113417.841610.nXIFsy
Results logged to /tmp/ruby-build.20200821113417.841610.log

Last 10 log lines:
        LC_CTYPE =
        MFLAGS =
gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

./tool/file2lastrev.rb:6:in `require': cannot load such file -- optparse (LoadError)
        from ./tool/file2lastrev.rb:6:in `<main>'
make: *** [uncommon.mk:1130: revision.tmp] Error 1

fixed this by uninstall rbenv and reinstall with homebrew for ubuntu

10 days ago I've installed rbenv and ruby-2.7.1 with success as usual. Today, side-by-side I wanted to install ruby-2.7.2 and same error occured.
[09:51] [gencer] [bf ~/.rbenv] $ rbenv install 2.7.2
Downloading ruby-2.7.2.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.bz2
Installing ruby-2.7.2...

BUILD FAILED (Ubuntu 20.04 using ruby-build 20201118-6-g4a0c87c)

Inspect or clean up the working tree at /tmp/ruby-build.20201206095154.809205.OWRJt4
Results logged to /tmp/ruby-build.20201206095154.809205.log

Last 10 log lines:
linking shared-object ripper.so
make[2]: Leaving directory '/tmp/ruby-build.20201206095154.809205.OWRJt4/ruby-2.7.2/ext/ripper'
make[2]: Entering directory '/tmp/ruby-build.20201206095154.809205.OWRJt4/ruby-2.7.2'
./tool/file2lastrev.rb:6:in `require': cannot load such file -- optparse (LoadError)
        from ./tool/file2lastrev.rb:6:in `<main>'
make[2]: *** [uncommon.mk:1130: revision.tmp] Error 1
make[2]: Leaving directory '/tmp/ruby-build.20201206095154.809205.OWRJt4/ruby-2.7.2'
make[1]: *** [exts.mk:86: ruby] Error 2
make[1]: Leaving directory '/tmp/ruby-build.20201206095154.809205.OWRJt4/ruby-2.7.2'
make: *** [uncommon.mk:295: build-ext] Error 2

I've pulled all rbenv + ruby-build changes. Not worked.

Looks like I have managed to reproduce this issue. Clean install rbenv and ruby-build then install 3.0.0 and 3.0.1.
Here are steps to reproduce on Ubuntu 20.10 x86_64

Remove ~/.rbenv and install rbenv by "Basic GitHub Checkout" method as follows.

$ rm -rf .rbenv/
$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv
Cloning into '/home/yahonda/.rbenv'...
remote: Enumerating objects: 2886, done.
remote: Total 2886 (delta 0), reused 0 (delta 0), pack-reused 2886
Receiving objects: 100% (2886/2886), 562.66 KiB | 2.08 MiB/s, done.
Resolving deltas: 100% (1801/1801), done.
yahonda@myryzen:~$ cd ~/.rbenv && src/configure && make -C src
make: Entering directory '/home/yahonda/.rbenv/src'
gcc -fPIC     -c -o realpath.o realpath.c
gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib  -o ../libexec/rbenv-realpath.dylib realpath.o
make: Leaving directory '/home/yahonda/.rbenv/src'
$ echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.profile
$ ~/.rbenv/bin/rbenv init
# Load rbenv automatically by appending
# the following to ~/.bashrc:

eval "$(rbenv init -)"
$ vi ~/.bashrc # to add `eval "$(rbenv init -)"`
$ exec $SHELL -l
$ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | bash
Checking for `rbenv' in PATH: /home/yahonda/.rbenv/bin/rbenv
Checking for rbenv shims in PATH: OK
Checking `rbenv install' support: not found
Unless you plan to add Ruby versions manually, you should install ruby-build.
Please refer to https://github.com/rbenv/ruby-build#installation

Counting installed Ruby versions: none
  There aren't any Ruby versions installed under `/home/yahonda/.rbenv/versions'.
  You can install Ruby versions like so: rbenv install 2.2.4
Checking RubyGems settings: OK
Auditing installed plugins: OK

Install ruby-build as "rbenv plugin" and install Ruby 3.0.0

$ mkdir -p "$(rbenv root)"/plugins
$ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build
Cloning into '/home/yahonda/.rbenv/plugins/ruby-build'...
remote: Enumerating objects: 162, done.
remote: Counting objects: 100% (162/162), done.
remote: Compressing objects: 100% (114/114), done.
remote: Total 11469 (delta 115), reused 73 (delta 39), pack-reused 11307
Receiving objects: 100% (11469/11469), 2.43 MiB | 4.02 MiB/s, done.
Resolving deltas: 100% (7582/7582), done.
$ rbenv install 3.0.0
Downloading ruby-3.0.0.tar.gz...
-> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.0.tar.gz
Installing ruby-3.0.0...
Installed ruby-3.0.0 to /home/yahonda/.rbenv/versions/3.0.0

$ rbenv global 3.0.0
$ which ruby
/home/yahonda/.rbenv/shims/ruby
$ ruby -v
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]

Install Ruby 3.0.1 and it gets the error below

$ rbenv install 3.0.1
Downloading ruby-3.0.1.tar.gz...
-> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.1.tar.gz
Installing ruby-3.0.1...

BUILD FAILED (Ubuntu 20.10 using ruby-build 20210405-2-g693a28e)

Inspect or clean up the working tree at /tmp/ruby-build.20210407222345.480785.HSbVgV
Results logged to /tmp/ruby-build.20210407222345.480785.log

Last 10 log lines:
linking shared-object ripper.so
make[2]: Leaving directory '/tmp/ruby-build.20210407222345.480785.HSbVgV/ruby-3.0.1/ext/ripper'
make[2]: Entering directory '/tmp/ruby-build.20210407222345.480785.HSbVgV/ruby-3.0.1'
./tool/file2lastrev.rb:6:in `require': cannot load such file -- optparse (LoadError)
	from ./tool/file2lastrev.rb:6:in `<main>'
make[2]: *** [uncommon.mk:1156: revision.tmp] Error 1
make[2]: Leaving directory '/tmp/ruby-build.20210407222345.480785.HSbVgV/ruby-3.0.1'
make[1]: *** [exts.mk:88: ruby] Error 2
make[1]: Leaving directory '/tmp/ruby-build.20210407222345.480785.HSbVgV/ruby-3.0.1'
make: *** [uncommon.mk:300: build-ext] Error 2
$

It does not reproduce on macOS 11.3 Beta (20E5224a). I do not have other non-beta versions of macOS.

The same for me with Ruby 2.7.3 version. 3.0.1, 2.6.7 and 2.5.9 installed without errors.

@yahonda same error here on Ubuntu 20.04.2 LTS.

@mislav No such environment variables.

@mislav Finally I install 3.0.1 success as following step

Install 2.7.3
Set global version to 2.7.3
Install 3.0.1 again, no error.

None of these environment variables configured.
$ echo $RUBYOPT

$ echo $RUBYLIB

$

@hsbt Do you know if building a Ruby version is dependent or at all affected by having another Ruby version installed on the system? The reproduction steps so far suggest that the LoadError pops up depending on which Ruby version is being installed and which other Ruby version was selected as "global".

https://github.com/rbenv/ruby-build/issues/1484#issuecomment-814918917 is a strange behavior for me. Because I never faced that with my macOS and linux boxes.
I try to reproduce it.

I ran into the same error installing 3.0.1 with asdf on Ubuntu 20.04.
Following similar steps to @smoothdvd, I was able to install 3.0.1:

Switching the global version from 3.0.0 to 2.7.2 with asdf global ruby 2.7.2
Install ruby 3.0.1 with asdf install ruby 3.0.1

@mislav , You are correct on our comment. This hapenned to me from version 2.6.8 to version 2.7.3. I solved it as follows:
I am using CentOS 7 on a corporate environment. For that reason my options are quite limited.

Install rbenv

$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv
$ cd ~/.rbenv
$ src/configure && make -C src

Add $HOME/.rbenv/bin to your $PATH

Install ruby-build

$ git clone https://github.com/rbenv/ruby-build.git ~/ruby-build
$ cd ~/ruby-build
$ sudo PREFIX=/usr/local/ ./install.sh

Ensure /usr/local/bin is in your $PATH.

Install version 2.6.8 and set it as global

$ sudo yum install -y openssl-devel readline-devel
$ rbenv install 2.6.8
$ rbenv global 2.6.8

You can check if it is correct using this command:
$ rbenv versions
  system
  2.6.8 (set by ~/.rbenv/version)

Install optparse using this newly installed version:

$ ~/.rbenv/versions/2.6.8/bin/gem install optparse

Install version 2.7.3 and set it as global:

$ rbenv install 2.7.3
$ rbenv global 2.7.3

You can check if it is correct using this command:
$ rbenv versions
  system
  2.6.8
* 2.7.3 (set by ~/.rbenv/version)

I believe this issue started from version 2.6.x to version 2.7.x as to update from 2.5.x to 2.6.x i did not have this issue.
I believe that the same steps need to be made from 2.6.x to 3.x

I'm facing the same issue with 2.7.0 in Void Linux x86_64.
My solution, based on previous comments, was to set RUBY_CONFIGURE_OPTS to indicate the "BASERUBY" (which I don't know what it means) and then install as usual:
$ rbenv versions
* system
  2.5.7
  2.6.6
$ export RUBY_CONFIGURE_OPTS=" --with-baseruby=$HOME/.rbenv/versions/2.6.6/bin/ruby"
$ rbenv install 2.7.0
Installing ruby-2.7.0...
Installed ruby-2.7.0 to $HOME/.rbenv/versions/2.7.0

From the log, when rbenv install 2.7.0 fails, I can see the next message:
   * BASERUBY -v:         ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) \
                          [x86_64-linux]

---
	BASERUBY = $HOME/.rbenv/shims/ruby --disable=gems

And notice that ruby 2.7.4p191 is system:
$ rbenv shell system
$ ruby --version
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]

Now, reading https://github.com/ruby/ruby/blob/master/configure.ac#L50 makes me wonder if a previous version of Ruby is needed to build Ruby >= 2.7.0?: "executable host ruby is required.  use --with-baseruby option".
Whats your opinion? 🤔

makes me wonder if a previous version of Ruby is needed to build Ruby >= 2.7.0?: "executable host ruby is required. use --with-baseruby option".

@hsbt Do you know anything about this?

Same problem on my machine. Unable to install Ruby 2.7.2 via rvm. I have 2.7.0.

I met same issue on Ubuntu 21.04 amd64.
I used system ruby instead of ruby-build's ruby :sweat_smile:
sudo apt install ruby
rbenv global system
rbenv rehash
rbenv install 2.7.4

refs: ruby-buildでRubyをインストールしようとしたらoptparseが無いって言われる - ser1zw's blog

This issue happen on, when install new ruby version use RVM, but current, selected version is system ruby.
that is, this is a issue come from system ruby, don't use it, you can just remove system ruby use package manager, or switch to use a more older version ruby which installed use RVM.


Add files via upload

Intro and order
Suggestions welcome

@Salil-Jain  @Mihir1996  add the id numbers of all four of us in the intro

@Mihir1996  nice work buddy 👍


ProgrammingError at / - relation "cart_cart" does not exist

Hi folks,
I just started today with checking out this amazing project! I hope my question/problem is a legit one ...
I have cloned the repository. I changed the Dockerfile to include a line: ENV ALLOWED_HOSTS <IP_ADDRESS> to be able to access the page using the host's internal IP. Then I started the containers with docker-compose up -d. All containers seem to run as intended.
Anyways, when I try to connect hat http://<IP_ADDRESS>:8000, I get this error:

ProgrammingError at / - relation "cart_cart" does not exist
(full error message in pdf below)
ProgrammingError at _.pdf

Am I missing something?

 It looks like database tables were not created at all.

@devax Preparing the database should solve your problem:
docker-compose run web python manage.py migrate

Thank you guys - sorry, I missed that one! I finally got it working. I'm leaving some additional information here, in case it will help someone else in future.
Next error was "OSError at / ...". I finally found the relevant installation manual: https://saleor.readthedocs.io/en/latest/development.html#docker-dev.
It took me some time to figure out that yarn must be run on the host, not inside the container.
On the Synology NAS, these are the steps that worked for me:

From package manager, install Node.js 6 (beta)
In terminal, install yarn in the version needed: sudo npm install --global<EMAIL_ADDRESS>Even after re-login, yarn was not a recognized command in my case. So I used the output from nmp install command to point to yarn binary directly, like so: sudo<EMAIL_ADDRESS>sudo<EMAIL_ADDRESS>run build-assets
Then proceed with the next steps from installation manual (docker-compose build etc.)
This made my installation on my Synology NAS work.


When the log file is too large, it hangs when viewing the instance log

Describe the bug

When the log file is too large, it hangs when viewing the log
Steps to reproduce
The log file is 7.8M.
-rw-r--r-- 1 root root 7.8M 10月 25 21:34 3.log

Environment

GPUStack version: main 985b1a7
UI version: abdc78e

Additional context
Add any other context about the problem here.

Verified on main fe77175, UI version 343ada1


Make password reset form customisable

Sometimes, it's helpful to have a captcha in the password reset form.
I made it possible to use the same method for customising the login form to customise
the password reset form.
Now it's possible to render an arbitrary amount of extra fields in the password reset view.

Use a setting called WAGTAILADMIN_PASSWORD_RESET_FORM to allow
users to specify a custom form for use in PasswordResetView.

Add an extra_fields property to the base password reset form so
that fields other than the mandatory email field can be easily rendered in the template.

Add extra blocks to the default template to allow users to
easily add their own stuff.

Render extra fields in the template like we're doing in the
login template.

I have added tests in the test_views.py and test_forms.py files and
ran all the code quality tools.

No problems. Maybe if you can double check the merged docs for me and confirm it's all done correctly.
Really appreciate the time you took to put this together.


Supports Apple Silicon

Because of matter of the version of MacOS used in CI,The output is not a universal binary.
This change updates CI
I haven't verified if kirikiri plugins work,Maybe I should make pull requests for plugins to make universal binary.

about the diff of CMakeLists

Without the diff of CMakeLists.txt,I got this error message on CI

mixing declarations and code is incompatible with standards before C99

Thanks!


[INSTALL]: Add<EMAIL_ADDRESS>-> 2024.01.01 -> 2024.01.02 -> 2024.02 (in addition to or to replace current version in spack-stack-1.8.0)

Package name
fms
Package version/tag
2024.01 -> 2024.01.01 -> 2024.01.02 -> 2024.02 are small patch releases that we should use instead.
See https://github.com/NOAA-GFDL/FMS/releases/tag/2024.02
Build options
Current
Installation timeframe
For spack-stack-1.8.0.
Other information
This version has a bug fix for linking the OpenMP-enabled version on macOS. It would be great to update to that version if possible.
WCOSS2

[X] Check this box if and only if your package should be installed on WCOSS2 Cactus and Dogwood (all spack-stack packages will be installed on Acorn). If not, you may disregard the rest of the items below and submit this request.

WCOSS2: General questions
Upgrade
WCOSS2: Installation and testing
Current
WCOSS2: Technical & security review list

[ ] The code is mature, stable, and production ready
[ ] The code is does not and cannot use the internet, and does not contain URLs (http, https, ftp, etc.) except in comments
[ ] The package does not contain prebuilt binary files that have not been approved by NCO security review
[ ] The code has no publicly disclosed cybersecurity vulnerabilities and exposures (search https://cve.mitre.org/cve/)
[ ] The code is not prohibited by DHS, DOC, NOAA, or NWS
[ ] The code comes from a trusted source. Trusted sources include other NWS, NOAA, or DOC, agencies, or other Federal agencies that operate at a FISMA high or equivalent level. Additionally, trusted sources could be third-party agencies through which there is an existing SLA on file (such as RedHat).
[ ] The code is actively maintained and supported (it continues to get updates, patches, etc.)
[ ] The code is not maintained by a private entity operating in a foreign country (if it is, make a note below)
[ ] There is sufficient documentation to support maintenance
[ ] There are no known security vulnerabilities or weaknesses
[ ] Installing and running the code does not require privileged processes/users
[ ] There are no software dependencies that are unapproved or have security concerns (if there are, make a note below)
[ ] There are no concerns related to SA, SI, and SC NIST control families

WCOSS2: Additional comments
No response

can we use a newer, yet-to-be-created tag that includes the cmake bug fixes for shared builds?

@climbfuji add latest version


Large errors in brown.edu mapping(?)

See the suggestions on https://www.wikidata.org/wiki/Q17428400 for example, they make no sense.

In order to ease us (the Wikidata dev team) to track the issues of the primary sources tool, we have created a Phabricator ticket for this issue: https://phabricator.wikimedia.org/T148142
Moving forward, please drop your comments onto that Phabricator ticket.


[cluster-test] fixed local swarm

Local swarm failed because of wrong if condition, which does not need to require to load vasp account
Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan

test local swarm:
cargo run -p cluster-test -- --mint-file "/private/var/folders/qd/tg50mr0d7k75qvztr_8yk2km0000gn/T/5ad50f412fbe14da9d0d95dce85b2323/mint.key" --swarm --peers "<IP_ADDRESS>:8080" --diag --chain-id TESTING

Getting faucet account sequence number on <IP_ADDRESS>:8080(<IP_ADDRESS>)...seq=0
Submitting txn through <IP_ADDRESS>:8080(<IP_ADDRESS>)...seq=1
Waiting all full nodes to get to seq 1
[<IP_ADDRESS>:0]
[<IP_ADDRESS>:1]
Looks like all full nodes are healthy!

cargo run -p cluster-test -- --mint-file "/private/var/folders/qd/tg50mr0d7k75qvztr_8yk2km0000gn/T/192d83c5834e189d60ca5169e00c3722/mint.key" --swarm --peers "<IP_ADDRESS>:8080" --emit-tx --chain-id TESTING
czh@czh-mbp libra-libra % cargo run -p cluster-test -- --mint-file "/private/var/folders/qd/tg50mr0d7k75qvztr_8yk2km0000gn/T/192d83c5834e189d60ca5169e00c3722/mint.key" --swarm --peers "<IP_ADDRESS>:8080" --emit-tx --chain-id TESTING
    Finished dev [unoptimized + debuginfo] target(s) in 0.59s
     Running `target/debug/cluster-test --mint-file /private/var/folders/qd/tg50mr0d7k75qvztr_8yk2km0000gn/T/192d83c5834e189d60ca5169e00c3722/mint.key --swarm --peers '<IP_ADDRESS>:8080' --emit-tx --chain-id TESTING`
2020-10-08T21:33:15.943062Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:234 Will use 10 workers per AC with total 10 AC clients
2020-10-08T21:33:15.943154Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:246 Will create 15 accounts_per_client with total 150 accounts
2020-10-08T21:33:15.943555Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:375 Creating and minting faucet account
2020-10-08T21:33:16.615386Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:393 DD account current balances are<PHONE_NUMBER>427387903, requested 150000000 coins
2020-10-08T21:33:16.615485Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:406 Creating and minting seeds accounts
2020-10-08T21:33:17.269890Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:417 Completed creating seed accounts
2020-10-08T21:33:18.044533Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:457 Completed minting seed accounts
2020-10-08T21:33:18.044568Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:458 Minting additional 150 accounts
2020-10-08T21:33:28.393636Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:496 Mint is done
2020-10-08T21:33:28.394545Z [main] INFO testsuite/cluster-test/src/tx_emitter.rs:280 Tx emitter workers started
submitted: 60 txn/s, committed: 45 txn/s, expired: 0 txn/s, latency: 2593 ms, p99 latency: 2700 ms
submitted: 60 txn/s, committed: 60 txn/s, expired: 0 txn/s, latency: 2642 ms, p99 latency: 2850 ms
submitted: 53 txn/s, committed: 60 txn/s, expired: 0 txn/s, latency: 2629 ms, p99 latency: 2800 ms
submitted: 51 txn/s, committed: 45 txn/s, expired: 0 txn/s, latency: 2591 ms, p99 latency: 2650 ms
submitted: 60 txn/s, committed: 60 txn/s, expired: 0 txn/s, latency: 2676 ms, p99 latency: 2850 ms
submitted: 60 txn/s, committed: 60 txn/s, expired: 0 txn/s, latency: 2596 ms, p99 latency: 2800 ms
Total stats: submitted: 3450, committed: 3450, expired: 0
Average rate: submitted: 57 txn/s, committed: 57 txn/s, expired: 0 txn/s, latency: 2625 ms, p99 latency: 2850 ms

test with premainnet fullnodes:
./target/debug/cluster-test --swarm -p a72ffeb94e81111ea81b70e75131a869-1894457723.ap-northeast-1.elb.amazonaws.com:80,<IP_ADDRESS>:80,ada61ba47e80d11ea9bcd0a7a792c33e-1496143175.ap-southeast-1.elb.amazonaws.com:80,<IP_ADDRESS>:80,libra-breakthrough-full-node.man.bdi.sh:80,ab6b29969132f484db9fdc9d302b92e1-9b15e1987ad0319f.elb.eu-west-1.amazonaws.com:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80,ad49a6c1e472c4f82ac8507df2d81f58-e2858d056c4dfef9.elb.us-east-2.amazonaws.com:80,aeb83d6e0bf8f46f7bb25dd68c82f021-db6448367d0c7b7b.elb.us-east-1.amazonaws.com:80,<IP_ADDRESS>:80,premainnet.libra.novi.com:80,ae5dfb87ce81311ea8c230282fe68c3b-1804125671.us-west-2.elb.amazonaws.com:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80,libra-slow-full-node.man.bdi.sh:80,<IP_ADDRESS>:80 --chain-id 18 --premainnet --diag

Getting faucet account sequence number on a72ffeb94e81111ea81b70e75131a869-1894457723.ap-northeast-1.elb.amazonaws.com:80(a72ffeb94e81111ea81b70e75131a869-1894457723.ap-northeast-1.elb.amazonaws.com)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on ada61ba47e80d11ea9bcd0a7a792c33e-1496143175.ap-southeast-1.elb.amazonaws.com:80(ada61ba47e80d11ea9bcd0a7a792c33e-1496143175.ap-southeast-1.elb.amazonaws.com)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on libra-breakthrough-full-node.man.bdi.sh:80(libra-breakthrough-full-node.man.bdi.sh)...seq=122
Getting faucet account sequence number on ab6b29969132f484db9fdc9d302b92e1-9b15e1987ad0319f.elb.eu-west-1.amazonaws.com:80(ab6b29969132f484db9fdc9d302b92e1-9b15e1987ad0319f.elb.eu-west-1.amazonaws.com)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on ad49a6c1e472c4f82ac8507df2d81f58-e2858d056c4dfef9.elb.us-east-2.amazonaws.com:80(ad49a6c1e472c4f82ac8507df2d81f58-e2858d056c4dfef9.elb.us-east-2.amazonaws.com)...seq=122
Getting faucet account sequence number on aeb83d6e0bf8f46f7bb25dd68c82f021-db6448367d0c7b7b.elb.us-east-1.amazonaws.com:80(aeb83d6e0bf8f46f7bb25dd68c82f021-db6448367d0c7b7b.elb.us-east-1.amazonaws.com)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on premainnet.libra.novi.com:80(premainnet.libra.novi.com)...seq=122
Getting faucet account sequence number on ae5dfb87ce81311ea8c230282fe68c3b-1804125671.us-west-2.elb.amazonaws.com:80(ae5dfb87ce81311ea8c230282fe68c3b-1804125671.us-west-2.elb.amazonaws.com)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Getting faucet account sequence number on libra-slow-full-node.man.bdi.sh:80(libra-slow-full-node.man.bdi.sh)...seq=122
Getting faucet account sequence number on <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=122
Submitting txn through a72ffeb94e81111ea81b70e75131a869-1894457723.ap-northeast-1.elb.amazonaws.com:80(a72ffeb94e81111ea81b70e75131a869-1894457723.ap-northeast-1.elb.amazonaws.com)...seq=123
Waiting all full nodes to get to seq 123
[a72ffeb94e:122]  [34.68.123.:122]  [ada61ba47e:122]  [34.73.243.:122]  [libra-brea:122]  [ab6b299691:122]  [<IP_ADDRESS>:122]  [<IP_ADDRESS>:122]  [ad49a6c1e4:122]  [aeb83d6e0b:122]  [35.198.155:122]  [premainnet:122]  [ae5dfb87ce:122]  [34.107.49.:122]  [35.241.88.:122]  [<IP_ADDRESS>:122]  [libra-slow:122]  [104.197.15:122]
[a72ffeb94e:123]  [34.68.123.:123]  [ada61ba47e:123]  [34.73.243.:123]  [libra-brea:123]  [ab6b299691:123]  [<IP_ADDRESS>:123]  [<IP_ADDRESS>:123]  [ad49a6c1e4:123]  [aeb83d6e0b:123]  [35.198.155:123]  [premainnet:122]  [ae5dfb87ce:122]  [34.107.49.:123]  [35.241.88.:122]  [<IP_ADDRESS>:123]  [libra-slow:123]  [104.197.15:123]
[a72ffeb94e:123]  [34.68.123.:123]  [ada61ba47e:123]  [34.73.243.:123]  [libra-brea:123]  [ab6b299691:123]  [<IP_ADDRESS>:123]  [<IP_ADDRESS>:123]  [ad49a6c1e4:123]  [aeb83d6e0b:123]  [35.198.155:123]  [premainnet:123]  [ae5dfb87ce:123]  [34.107.49.:123]  [35.241.88.:123]  [<IP_ADDRESS>:123]  [libra-slow:123]  [104.197.15:123]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=124
Waiting all full nodes to get to seq 124
[a72ffeb94e:123]  [34.68.123.:123]  [ada61ba47e:123]  [34.73.243.:123]  [libra-brea:123]  [ab6b299691:123]  [<IP_ADDRESS>:123]  [<IP_ADDRESS>:123]  [ad49a6c1e4:123]  [aeb83d6e0b:123]  [35.198.155:123]  [premainnet:123]  [ae5dfb87ce:123]  [34.107.49.:123]  [35.241.88.:123]  [<IP_ADDRESS>:123]  [libra-slow:123]  [104.197.15:123]
[a72ffeb94e:123]  [34.68.123.:123]  [ada61ba47e:123]  [34.73.243.:123]  [libra-brea:123]  [ab6b299691:123]  [<IP_ADDRESS>:123]  [<IP_ADDRESS>:123]  [ad49a6c1e4:123]  [aeb83d6e0b:123]  [35.198.155:123]  [premainnet:123]  [ae5dfb87ce:123]  [34.107.49.:123]  [35.241.88.:123]  [<IP_ADDRESS>:123]  [libra-slow:123]  [104.197.15:123]
[a72ffeb94e:124]  [34.68.123.:124]  [ada61ba47e:124]  [34.73.243.:124]  [libra-brea:124]  [ab6b299691:124]  [<IP_ADDRESS>:124]  [<IP_ADDRESS>:124]  [ad49a6c1e4:124]  [aeb83d6e0b:124]  [35.198.155:124]  [premainnet:124]  [ae5dfb87ce:124]  [34.107.49.:124]  [35.241.88.:124]  [<IP_ADDRESS>:124]  [libra-slow:124]  [104.197.15:124]
Submitting txn through ada61ba47e80d11ea9bcd0a7a792c33e-1496143175.ap-southeast-1.elb.amazonaws.com:80(ada61ba47e80d11ea9bcd0a7a792c33e-1496143175.ap-southeast-1.elb.amazonaws.com)...seq=125
Waiting all full nodes to get to seq 125
[a72ffeb94e:124]  [34.68.123.:124]  [ada61ba47e:124]  [34.73.243.:124]  [libra-brea:124]  [ab6b299691:124]  [<IP_ADDRESS>:124]  [<IP_ADDRESS>:124]  [ad49a6c1e4:124]  [aeb83d6e0b:124]  [35.198.155:124]  [premainnet:124]  [ae5dfb87ce:124]  [34.107.49.:124]  [35.241.88.:124]  [<IP_ADDRESS>:124]  [libra-slow:124]  [104.197.15:124]
[a72ffeb94e:124]  [34.68.123.:124]  [ada61ba47e:124]  [34.73.243.:124]  [libra-brea:124]  [ab6b299691:124]  [<IP_ADDRESS>:124]  [<IP_ADDRESS>:124]  [ad49a6c1e4:124]  [aeb83d6e0b:124]  [35.198.155:124]  [premainnet:124]  [ae5dfb87ce:124]  [34.107.49.:124]  [35.241.88.:125]  [<IP_ADDRESS>:124]  [libra-slow:124]  [104.197.15:124]
[a72ffeb94e:125]  [34.68.123.:125]  [ada61ba47e:125]  [34.73.243.:125]  [libra-brea:125]  [ab6b299691:125]  [<IP_ADDRESS>:125]  [<IP_ADDRESS>:125]  [ad49a6c1e4:125]  [aeb83d6e0b:125]  [35.198.155:125]  [premainnet:125]  [ae5dfb87ce:125]  [34.107.49.:125]  [35.241.88.:125]  [<IP_ADDRESS>:125]  [libra-slow:125]  [104.197.15:125]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=126
Waiting all full nodes to get to seq 126
[a72ffeb94e:125]  [34.68.123.:125]  [ada61ba47e:125]  [34.73.243.:125]  [libra-brea:125]  [ab6b299691:125]  [<IP_ADDRESS>:125]  [<IP_ADDRESS>:125]  [ad49a6c1e4:125]  [aeb83d6e0b:125]  [35.198.155:125]  [premainnet:125]  [ae5dfb87ce:125]  [34.107.49.:125]  [35.241.88.:125]  [<IP_ADDRESS>:125]  [libra-slow:125]  [104.197.15:125]
[a72ffeb94e:126]  [34.68.123.:126]  [ada61ba47e:126]  [34.73.243.:126]  [libra-brea:126]  [ab6b299691:126]  [<IP_ADDRESS>:126]  [<IP_ADDRESS>:126]  [ad49a6c1e4:126]  [aeb83d6e0b:126]  [35.198.155:126]  [premainnet:126]  [ae5dfb87ce:126]  [34.107.49.:126]  [35.241.88.:126]  [<IP_ADDRESS>:126]  [libra-slow:126]  [104.197.15:126]
Submitting txn through libra-breakthrough-full-node.man.bdi.sh:80(libra-breakthrough-full-node.man.bdi.sh)...seq=127
Waiting all full nodes to get to seq 127
[a72ffeb94e:126]  [34.68.123.:126]  [ada61ba47e:126]  [34.73.243.:126]  [libra-brea:126]  [ab6b299691:126]  [<IP_ADDRESS>:126]  [<IP_ADDRESS>:126]  [ad49a6c1e4:126]  [aeb83d6e0b:126]  [35.198.155:126]  [premainnet:126]  [ae5dfb87ce:126]  [34.107.49.:126]  [35.241.88.:126]  [<IP_ADDRESS>:126]  [libra-slow:126]  [104.197.15:126]
[a72ffeb94e:127]  [34.68.123.:127]  [ada61ba47e:127]  [34.73.243.:127]  [libra-brea:127]  [ab6b299691:127]  [<IP_ADDRESS>:127]  [<IP_ADDRESS>:127]  [ad49a6c1e4:127]  [aeb83d6e0b:127]  [35.198.155:127]  [premainnet:127]  [ae5dfb87ce:127]  [34.107.49.:127]  [35.241.88.:127]  [<IP_ADDRESS>:127]  [libra-slow:127]  [104.197.15:127]
Submitting txn through ab6b29969132f484db9fdc9d302b92e1-9b15e1987ad0319f.elb.eu-west-1.amazonaws.com:80(ab6b29969132f484db9fdc9d302b92e1-9b15e1987ad0319f.elb.eu-west-1.amazonaws.com)...seq=128
Waiting all full nodes to get to seq 128
[a72ffeb94e:127]  [34.68.123.:127]  [ada61ba47e:127]  [34.73.243.:127]  [libra-brea:127]  [ab6b299691:127]  [<IP_ADDRESS>:127]  [<IP_ADDRESS>:127]  [ad49a6c1e4:127]  [aeb83d6e0b:127]  [35.198.155:127]  [premainnet:127]  [ae5dfb87ce:127]  [34.107.49.:127]  [35.241.88.:127]  [<IP_ADDRESS>:127]  [libra-slow:127]  [104.197.15:127]
[a72ffeb94e:128]  [34.68.123.:128]  [ada61ba47e:128]  [34.73.243.:128]  [libra-brea:128]  [ab6b299691:128]  [<IP_ADDRESS>:128]  [<IP_ADDRESS>:128]  [ad49a6c1e4:128]  [aeb83d6e0b:128]  [35.198.155:128]  [premainnet:128]  [ae5dfb87ce:128]  [34.107.49.:128]  [35.241.88.:128]  [<IP_ADDRESS>:128]  [libra-slow:128]  [104.197.15:128]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=129
Waiting all full nodes to get to seq 129
[a72ffeb94e:128]  [34.68.123.:128]  [ada61ba47e:128]  [34.73.243.:128]  [libra-brea:128]  [ab6b299691:128]  [<IP_ADDRESS>:128]  [<IP_ADDRESS>:128]  [ad49a6c1e4:128]  [aeb83d6e0b:128]  [35.198.155:128]  [premainnet:128]  [ae5dfb87ce:128]  [34.107.49.:128]  [35.241.88.:128]  [<IP_ADDRESS>:128]  [libra-slow:128]  [104.197.15:128]
[a72ffeb94e:129]  [34.68.123.:129]  [ada61ba47e:129]  [34.73.243.:129]  [libra-brea:129]  [ab6b299691:129]  [<IP_ADDRESS>:129]  [<IP_ADDRESS>:129]  [ad49a6c1e4:129]  [aeb83d6e0b:129]  [35.198.155:129]  [premainnet:129]  [ae5dfb87ce:129]  [34.107.49.:129]  [35.241.88.:129]  [<IP_ADDRESS>:129]  [libra-slow:129]  [104.197.15:129]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=130
Waiting all full nodes to get to seq 130
[a72ffeb94e:129]  [34.68.123.:129]  [ada61ba47e:129]  [34.73.243.:129]  [libra-brea:129]  [ab6b299691:129]  [<IP_ADDRESS>:129]  [<IP_ADDRESS>:129]  [ad49a6c1e4:129]  [aeb83d6e0b:129]  [35.198.155:129]  [premainnet:129]  [ae5dfb87ce:129]  [34.107.49.:129]  [35.241.88.:129]  [<IP_ADDRESS>:129]  [libra-slow:129]  [104.197.15:129]
[a72ffeb94e:130]  [34.68.123.:130]  [ada61ba47e:130]  [34.73.243.:130]  [libra-brea:130]  [ab6b299691:130]  [<IP_ADDRESS>:130]  [<IP_ADDRESS>:130]  [ad49a6c1e4:130]  [aeb83d6e0b:130]  [35.198.155:130]  [premainnet:130]  [ae5dfb87ce:129]  [34.107.49.:130]  [35.241.88.:130]  [<IP_ADDRESS>:130]  [libra-slow:130]  [104.197.15:130]
[a72ffeb94e:130]  [34.68.123.:130]  [ada61ba47e:130]  [34.73.243.:130]  [libra-brea:130]  [ab6b299691:130]  [<IP_ADDRESS>:130]  [<IP_ADDRESS>:130]  [ad49a6c1e4:130]  [aeb83d6e0b:130]  [35.198.155:130]  [premainnet:130]  [ae5dfb87ce:130]  [34.107.49.:130]  [35.241.88.:130]  [<IP_ADDRESS>:130]  [libra-slow:130]  [104.197.15:130]
Submitting txn through ad49a6c1e472c4f82ac8507df2d81f58-e2858d056c4dfef9.elb.us-east-2.amazonaws.com:80(ad49a6c1e472c4f82ac8507df2d81f58-e2858d056c4dfef9.elb.us-east-2.amazonaws.com)...seq=131
Waiting all full nodes to get to seq 131
[a72ffeb94e:130]  [34.68.123.:130]  [ada61ba47e:130]  [34.73.243.:130]  [libra-brea:130]  [ab6b299691:130]  [<IP_ADDRESS>:130]  [<IP_ADDRESS>:130]  [ad49a6c1e4:130]  [aeb83d6e0b:130]  [35.198.155:130]  [premainnet:130]  [ae5dfb87ce:130]  [34.107.49.:130]  [35.241.88.:130]  [<IP_ADDRESS>:130]  [libra-slow:130]  [104.197.15:130]
[a72ffeb94e:131]  [34.68.123.:131]  [ada61ba47e:131]  [34.73.243.:131]  [libra-brea:131]  [ab6b299691:131]  [<IP_ADDRESS>:131]  [<IP_ADDRESS>:131]  [ad49a6c1e4:131]  [aeb83d6e0b:131]  [35.198.155:131]  [premainnet:131]  [ae5dfb87ce:131]  [34.107.49.:131]  [35.241.88.:131]  [<IP_ADDRESS>:131]  [libra-slow:131]  [104.197.15:131]
Submitting txn through aeb83d6e0bf8f46f7bb25dd68c82f021-db6448367d0c7b7b.elb.us-east-1.amazonaws.com:80(aeb83d6e0bf8f46f7bb25dd68c82f021-db6448367d0c7b7b.elb.us-east-1.amazonaws.com)...seq=132
Waiting all full nodes to get to seq 132
[a72ffeb94e:131]  [34.68.123.:131]  [ada61ba47e:131]  [34.73.243.:131]  [libra-brea:131]  [ab6b299691:131]  [<IP_ADDRESS>:131]  [<IP_ADDRESS>:131]  [ad49a6c1e4:131]  [aeb83d6e0b:131]  [35.198.155:131]  [premainnet:131]  [ae5dfb87ce:131]  [34.107.49.:131]  [35.241.88.:131]  [<IP_ADDRESS>:131]  [libra-slow:131]  [104.197.15:131]
[a72ffeb94e:131]  [34.68.123.:131]  [ada61ba47e:132]  [34.73.243.:131]  [libra-brea:131]  [ab6b299691:131]  [<IP_ADDRESS>:131]  [<IP_ADDRESS>:131]  [ad49a6c1e4:131]  [aeb83d6e0b:131]  [35.198.155:131]  [premainnet:131]  [ae5dfb87ce:131]  [34.107.49.:131]  [35.241.88.:132]  [<IP_ADDRESS>:131]  [libra-slow:131]  [104.197.15:131]
[a72ffeb94e:132]  [34.68.123.:132]  [ada61ba47e:132]  [34.73.243.:132]  [libra-brea:132]  [ab6b299691:132]  [<IP_ADDRESS>:132]  [<IP_ADDRESS>:132]  [ad49a6c1e4:132]  [aeb83d6e0b:132]  [35.198.155:132]  [premainnet:132]  [ae5dfb87ce:132]  [34.107.49.:132]  [35.241.88.:132]  [<IP_ADDRESS>:132]  [libra-slow:132]  [104.197.15:132]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=133
Waiting all full nodes to get to seq 133
[a72ffeb94e:132]  [34.68.123.:132]  [ada61ba47e:132]  [34.73.243.:132]  [libra-brea:132]  [ab6b299691:132]  [<IP_ADDRESS>:132]  [<IP_ADDRESS>:132]  [ad49a6c1e4:132]  [aeb83d6e0b:132]  [35.198.155:132]  [premainnet:132]  [ae5dfb87ce:132]  [34.107.49.:132]  [35.241.88.:132]  [<IP_ADDRESS>:132]  [libra-slow:132]  [104.197.15:132]
[a72ffeb94e:133]  [34.68.123.:133]  [ada61ba47e:133]  [34.73.243.:133]  [libra-brea:133]  [ab6b299691:133]  [<IP_ADDRESS>:133]  [<IP_ADDRESS>:133]  [ad49a6c1e4:133]  [aeb83d6e0b:133]  [35.198.155:133]  [premainnet:133]  [ae5dfb87ce:133]  [34.107.49.:133]  [35.241.88.:133]  [<IP_ADDRESS>:133]  [libra-slow:133]  [104.197.15:133]
Submitting txn through premainnet.libra.novi.com:80(premainnet.libra.novi.com)...seq=134
Waiting all full nodes to get to seq 134
[a72ffeb94e:133]  [34.68.123.:133]  [ada61ba47e:133]  [34.73.243.:133]  [libra-brea:133]  [ab6b299691:133]  [<IP_ADDRESS>:133]  [<IP_ADDRESS>:133]  [ad49a6c1e4:133]  [aeb83d6e0b:133]  [35.198.155:133]  [premainnet:133]  [ae5dfb87ce:133]  [34.107.49.:133]  [35.241.88.:133]  [<IP_ADDRESS>:133]  [libra-slow:133]  [104.197.15:133]
[a72ffeb94e:134]  [34.68.123.:133]  [ada61ba47e:134]  [34.73.243.:133]  [libra-brea:133]  [ab6b299691:133]  [<IP_ADDRESS>:133]  [<IP_ADDRESS>:133]  [ad49a6c1e4:133]  [aeb83d6e0b:133]  [35.198.155:133]  [premainnet:133]  [ae5dfb87ce:133]  [34.107.49.:133]  [35.241.88.:134]  [<IP_ADDRESS>:133]  [libra-slow:133]  [104.197.15:133]
[a72ffeb94e:134]  [34.68.123.:134]  [ada61ba47e:134]  [34.73.243.:134]  [libra-brea:134]  [ab6b299691:134]  [<IP_ADDRESS>:134]  [<IP_ADDRESS>:134]  [ad49a6c1e4:134]  [aeb83d6e0b:134]  [35.198.155:134]  [premainnet:134]  [ae5dfb87ce:134]  [34.107.49.:134]  [35.241.88.:134]  [<IP_ADDRESS>:134]  [libra-slow:134]  [104.197.15:134]
Submitting txn through ae5dfb87ce81311ea8c230282fe68c3b-1804125671.us-west-2.elb.amazonaws.com:80(ae5dfb87ce81311ea8c230282fe68c3b-1804125671.us-west-2.elb.amazonaws.com)...seq=135
Waiting all full nodes to get to seq 135
[a72ffeb94e:134]  [34.68.123.:134]  [ada61ba47e:134]  [34.73.243.:134]  [libra-brea:134]  [ab6b299691:134]  [<IP_ADDRESS>:134]  [<IP_ADDRESS>:134]  [ad49a6c1e4:134]  [aeb83d6e0b:134]  [35.198.155:134]  [premainnet:134]  [ae5dfb87ce:134]  [34.107.49.:134]  [35.241.88.:134]  [<IP_ADDRESS>:134]  [libra-slow:134]  [104.197.15:134]
[a72ffeb94e:135]  [34.68.123.:135]  [ada61ba47e:135]  [34.73.243.:135]  [libra-brea:135]  [ab6b299691:135]  [<IP_ADDRESS>:135]  [<IP_ADDRESS>:135]  [ad49a6c1e4:135]  [aeb83d6e0b:135]  [35.198.155:135]  [premainnet:135]  [ae5dfb87ce:135]  [34.107.49.:135]  [35.241.88.:135]  [<IP_ADDRESS>:135]  [libra-slow:135]  [104.197.15:135]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=136
Waiting all full nodes to get to seq 136
[a72ffeb94e:135]  [34.68.123.:135]  [ada61ba47e:135]  [34.73.243.:135]  [libra-brea:135]  [ab6b299691:135]  [<IP_ADDRESS>:135]  [<IP_ADDRESS>:135]  [ad49a6c1e4:135]  [aeb83d6e0b:135]  [35.198.155:135]  [premainnet:135]  [ae5dfb87ce:135]  [34.107.49.:135]  [35.241.88.:135]  [<IP_ADDRESS>:135]  [libra-slow:135]  [104.197.15:135]
[a72ffeb94e:135]  [34.68.123.:135]  [ada61ba47e:135]  [34.73.243.:135]  [libra-brea:135]  [ab6b299691:135]  [<IP_ADDRESS>:135]  [<IP_ADDRESS>:135]  [ad49a6c1e4:135]  [aeb83d6e0b:135]  [35.198.155:135]  [premainnet:135]  [ae5dfb87ce:136]  [34.107.49.:135]  [35.241.88.:135]  [<IP_ADDRESS>:135]  [libra-slow:135]  [104.197.15:135]
[a72ffeb94e:136]  [34.68.123.:136]  [ada61ba47e:136]  [34.73.243.:136]  [libra-brea:136]  [ab6b299691:136]  [<IP_ADDRESS>:136]  [<IP_ADDRESS>:136]  [ad49a6c1e4:136]  [aeb83d6e0b:136]  [35.198.155:136]  [premainnet:136]  [ae5dfb87ce:136]  [34.107.49.:136]  [35.241.88.:136]  [<IP_ADDRESS>:136]  [libra-slow:136]  [104.197.15:136]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=137
Waiting all full nodes to get to seq 137
[a72ffeb94e:136]  [34.68.123.:136]  [ada61ba47e:136]  [34.73.243.:136]  [libra-brea:136]  [ab6b299691:136]  [<IP_ADDRESS>:136]  [<IP_ADDRESS>:136]  [ad49a6c1e4:136]  [aeb83d6e0b:136]  [35.198.155:136]  [premainnet:136]  [ae5dfb87ce:136]  [34.107.49.:136]  [35.241.88.:136]  [<IP_ADDRESS>:136]  [libra-slow:136]  [104.197.15:136]
[a72ffeb94e:137]  [34.68.123.:137]  [ada61ba47e:137]  [34.73.243.:137]  [libra-brea:137]  [ab6b299691:137]  [<IP_ADDRESS>:137]  [<IP_ADDRESS>:137]  [ad49a6c1e4:137]  [aeb83d6e0b:137]  [35.198.155:137]  [premainnet:137]  [ae5dfb87ce:137]  [34.107.49.:137]  [35.241.88.:137]  [<IP_ADDRESS>:137]  [libra-slow:137]  [104.197.15:137]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=138
Waiting all full nodes to get to seq 138
[a72ffeb94e:137]  [34.68.123.:137]  [ada61ba47e:137]  [34.73.243.:137]  [libra-brea:137]  [ab6b299691:137]  [<IP_ADDRESS>:137]  [<IP_ADDRESS>:137]  [ad49a6c1e4:137]  [aeb83d6e0b:137]  [35.198.155:137]  [premainnet:137]  [ae5dfb87ce:137]  [34.107.49.:137]  [35.241.88.:137]  [<IP_ADDRESS>:137]  [libra-slow:137]  [104.197.15:137]
[a72ffeb94e:138]  [34.68.123.:138]  [ada61ba47e:138]  [34.73.243.:138]  [libra-brea:138]  [ab6b299691:138]  [<IP_ADDRESS>:138]  [<IP_ADDRESS>:138]  [ad49a6c1e4:138]  [aeb83d6e0b:138]  [35.198.155:138]  [premainnet:138]  [ae5dfb87ce:138]  [34.107.49.:138]  [35.241.88.:138]  [<IP_ADDRESS>:138]  [libra-slow:138]  [104.197.15:138]
Submitting txn through libra-slow-full-node.man.bdi.sh:80(libra-slow-full-node.man.bdi.sh)...seq=139
Waiting all full nodes to get to seq 139
[a72ffeb94e:138]  [34.68.123.:138]  [ada61ba47e:138]  [34.73.243.:138]  [libra-brea:138]  [ab6b299691:138]  [<IP_ADDRESS>:138]  [<IP_ADDRESS>:138]  [ad49a6c1e4:138]  [aeb83d6e0b:138]  [35.198.155:138]  [premainnet:138]  [ae5dfb87ce:138]  [34.107.49.:138]  [35.241.88.:138]  [<IP_ADDRESS>:138]  [libra-slow:138]  [104.197.15:138]
[a72ffeb94e:139]  [34.68.123.:139]  [ada61ba47e:139]  [34.73.243.:139]  [libra-brea:139]  [ab6b299691:139]  [<IP_ADDRESS>:139]  [<IP_ADDRESS>:139]  [ad49a6c1e4:139]  [aeb83d6e0b:139]  [35.198.155:139]  [premainnet:138]  [ae5dfb87ce:139]  [34.107.49.:139]  [35.241.88.:138]  [<IP_ADDRESS>:139]  [libra-slow:139]  [104.197.15:139]
[a72ffeb94e:139]  [34.68.123.:139]  [ada61ba47e:139]  [34.73.243.:139]  [libra-brea:139]  [ab6b299691:139]  [<IP_ADDRESS>:139]  [<IP_ADDRESS>:139]  [ad49a6c1e4:139]  [aeb83d6e0b:139]  [35.198.155:139]  [premainnet:139]  [ae5dfb87ce:139]  [34.107.49.:139]  [35.241.88.:139]  [<IP_ADDRESS>:139]  [libra-slow:139]  [104.197.15:139]
Submitting txn through <IP_ADDRESS>:80(<IP_ADDRESS>)...seq=140
Waiting all full nodes to get to seq 140
[a72ffeb94e:139]  [34.68.123.:139]  [ada61ba47e:139]  [34.73.243.:139]  [libra-brea:139]  [ab6b299691:139]  [<IP_ADDRESS>:139]  [<IP_ADDRESS>:139]  [ad49a6c1e4:139]  [aeb83d6e0b:139]  [35.198.155:139]  [premainnet:139]  [ae5dfb87ce:139]  [34.107.49.:139]  [35.241.88.:139]  [<IP_ADDRESS>:139]  [libra-slow:139]  [104.197.15:139]
[a72ffeb94e:140]  [34.68.123.:140]  [ada61ba47e:140]  [34.73.243.:140]  [libra-brea:140]  [ab6b299691:140]  [<IP_ADDRESS>:140]  [<IP_ADDRESS>:140]  [ad49a6c1e4:140]  [aeb83d6e0b:140]  [35.198.155:140]  [premainnet:140]  [ae5dfb87ce:140]  [34.107.49.:140]  [35.241.88.:140]  [<IP_ADDRESS>:140]  [libra-slow:140]  [104.197.15:140]
Looks like all full nodes are healthy!

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/libra/developers.libra.org, and link to your PR here.)

Did you check that emit_tx works as well?

(2) On line 393 - if we replace emitter.load_faucet_account with emitter.load_tc_account, will it still work with swarm?

I assume TC account is only used to create parent vasp in local network? It does not have any coin? I can take a try to mint some coin to TC account if u think that is necessary

Did you check that emit_tx works as well?

yes, it works as well, log is updated above

I am curious if this PR as is will solve problem with personal testnets
We can either merge it, or, if it is possible @mgorven could check out this PR and see if it helps his case?

we should merge it anyway since there is a bug which local network does not have vasp account

/land

@snakech :exclamation: This PR is still missing approvals, unable to queue for landing

/land

@snakech :exclamation: This PR is still missing approvals, unable to queue for landing

/land


[Feat]FAQs Page

want to add a FAQs page

Hello smty2018, thanks for opening a issue, your contribution is valuable to us. The maintainers will review this issue and provide feedback as soon as possible.

want to add a FAQs page

Assigned.Make it according to the below design using Next UI/Tailwind Css and route to /faqs

I would like to create FAQs Page @shreya024 If @smty2018 is not working.


3.0: Remove the PHPCSHelper class

... in favour of the PHPCSUtils version of that class which adds:

Improved PHPCS cross-version compatibility.
More utility methods.

For full details on the upstream class, see the PHPCSHelper class documentation for PHPCSUtils.
The removal is done in three steps, which correspond to the commits in this PR:

Deprecate the old code
Switch over any uses of the old code
Remove the old code

Doing this removal in steps allowed for testing in between, making sure every use of the old class was caught.
Commit Details
PHPCSHelper: deprecate the class and all the methods in it
As everything here is now contained within PHPCSUtils, including updated and/or improved versions of some of these.
PHPCSHelper::get_version(): remove call to the function
This function call is no longer needed now support for PHPCS < 3.5.0 has been dropped.
PHPCSHelper::get_config_data(): switch over to the PHPCSUtils version
PHPCSHelper::get_tab_width(): switch over to the PHPCSUtils version
Remove the PHPCSHelper.php file
All of the methods contained herein are now provided via PHPCSUtils and all code has been switched over to use the PHPCSUtils versions of the methods instead.

Not merged, in case this was preferred to be squashed or not.

@GaryJones As these commits "tell a story", I'm fine with merging as-is, without squashing. If would squash this, we'd need to make sure that the context if maintained in the new commit message.


feat(typescript): Support AngularTemplateCompile mnemonic

The ng_module produces actions with the AngularTemplateCompile mnemonic (not
TypeScriptCompile). The two actions should both produce extra action data that
can be processed by the same extraction config.

I'm not sure AngularTemplateCompile is available anywhere public, but it seems harmless to me to include.

@evmar I'm not sure what you mean by public, but it looks like it is here: https://github.com/angular/angular/blob/master/packages/bazel/src/ng_module.bzl#L399


Expose DataSets' quality tests

Add linked Data QA tests information in DataSets' pages
Linked frontend task: https://github.com/opendatadiscovery/odd-platform/issues/5

Done


Cannot use different instances of the same Renderer for different types

Suppose that we have a generic ViewRenderer which receives a OnClickListener and just renders a TextView. If we would like, for example, to bind it with String and CharSequence but with different click listeners this would cause the first added Renderer to be reused for both types, causing all the clicks to be handled by the click listener of the first renderer.
Failing test:
@Test
public void shouldReturnSamePrototypeInstance() {
    RendererBuilder rendererBuilder = new RendererBuilder();

    ObjectRenderer prototype1 = new ObjectRenderer();
    ObjectRenderer prototype2 = new ObjectRenderer();

    rendererBuilder.bind(Object.class, prototype1);
    rendererBuilder.bind(String.class, prototype2);

    int index = rendererBuilder.getItemViewType(new Object());

    assertEquals(prototype1, rendererBuilder.getPrototypeByIndex(index));

    index = rendererBuilder.getItemViewType("");
    assertEquals(prototype2, rendererBuilder.getPrototypeByIndex(index));
}

This could be easily solved with #13 just by checking the item type inside the Renderer or by checking the item clicked directly in the listener.