double height text doesn't line-wrap properly

Windows Terminal version
No response
Windows build number
No response
Other Software
No response
Steps to reproduce
Create double-height text and then use it to write a line longer than the width of the current console window/pane
Expected Behavior
that it would wrap into another double-height line
Actual Behavior
It actually breaks the double-height line into two and ruins the effect, and then wraps the remainder twice as single height lines

Perhaps the wrapped text of a "big" line can be buffered and if it matches the wrapped text of the next line and that line is also "big", then a new "big" line can be created with the wrapped text and inserted after?

Here's another more carefully constructed example, and a rendition of what in my opinion I think should have happened:

Perhaps the wrapped text of a "big" line can be buffered and if it matches the wrapped text of the next line and that line is also "big", then a new "big" line can be created with the wrapped text and inserted after?

Yeah. this is something I had hoped we might be able to do one day. I don't think it even matters if the lines don't match. As long as you've got a top and bottom double-height pair, I think that should be enough to trigger a combined wrap.
That said, there are a bunch of edge cases which will likely make this more complicated than it seems at first glance. So as an interim solution we might want to consider just truncating any double height lines when they're resized. That at least would be a visual improvement, although the downside is that you're losing content in the process.

I guess under-the-hood it's more complicated than "just store what you truncate and later spit it out" :)
You're right, it shouldn't matter if the lines match.  If someone wants mismatched lines, that's their prerogative. There's some neat/funny things that can be done with that.

Just to be clear here, when you're referring to the text wrapping, do you mean when an application outputs text that doesn't fit on one line? Or are you talking about text that was originally on one line, but was later forced to wrap by the terminal when the window was resized?
I assumed the latter, because window resizing is the terminal's responsibility. However, if you actually meant the former, then that's up to the application to handle correctly. If you've got double height text that isn't expected to fit on a single line, it's the app's responsibility to split that in two, and write out the two instances of each half with appropriate line renditions.

Yea i meant the first.
That seems weird that it's the app's responsibility to handle line-wrapping.

It's not like this is something unique to Windows Terminal though. This is a standard level 1 VT capability that has existed for decades. We're just following the standard.
And typically these attributes would be used for things like headings, which wouldn't be expected to wrap. Although it's not particularly difficult for an application to manually wrap double-height text if they really wanted to.

I really liked the "truncation" hot-fix so I implemented it in #15701. I'm personally not intending to implement better alternatives (like wrapping double height rows in pairs).

Amy chance we could just truncate the 1st of the two?  that way the 2nd one can still line-wrap to normal size and no output is lost, but the double-height visual isn't perturbed either.
Basically just, don't truncate a line if the last one was?

Hi!
As a follow-up, and possibly the same or a different bug, I wanted to illustrate this phenomenon with a better example that you should be able to easily reproduce yourself:
Something is happening prematurely. This isn't even really a wrap bug. Somehow, getting within ≈7 (but not always 7?) characters of the right of the screen inserts a blank line that shouldn't be there.
The more I think about this, the more I think this isn't a wrapping situation, so I think this is actually a separate bug that I should file, so I'm going to paste this into a new bug report.
rem Adjust terminal width to 209 columns first...
pause

set big_bot=←#4
set big_top=←#3
set message=there are 209 columns...there are 209 columns...there are 209 columns...there are 209 columns....
rem length of message is 97
echo %message%

echo -----------
echo %big_top%%message%
echo %big_bot%%message%
echo -----------

rem This message is one character shorter:
set message=there are 209 columns...there are 209 columns...there are 209 columns...there are 209 columns...

echo -----------
echo %big_top%%message%
echo %big_bot%%message%
echo -----------


Allow devs to disable the colors by light/dark mode and instead let them decide which colors to use

Is this open for contribution??

I'm ready to take up this issue, Please assign it to me @earrietadev

@earrietadev  i would like to contribute to this

Hi @earrietadev I would like to take this task. This would be my firts issue on this project.
I estimate no more than a 3 days  for the changes to be ready.

Hello, Can I get assigned to this??

Can I be assigned this?

I would love to contribute to this project.

Thank you 🙏🏾

Is this open for contribution? If yes, please I'll love to be assigned this issue please. This is my first time contributing to Stellar and I will love to be given the opportunity to proof my skills. To solve this issue I will:

Introduce a configuration option to disable light/dark mode colors.
Allow developers to specify custom colors.
Use TypeScript interfaces to ensure type safety.
Update color handling logic to apply custom colors when configured.

I’ll submit a PR within 3-5 working days once I’m assigned.
Here is my Onlydust profile link https://app.onlydust.com/u/od-hunter , it might not look like it yet because I’m new to Onlydust, please give me the opportunity.

@od-hunter I just assigned this to you, you can ask question here. For the implementation keep in mind that the configuration needs to be "dead simple" so any the configuration needs to be at the creation level, something like this:
const kit: StellarWalletsKit = new StellarWalletsKit({
  network: WalletNetwork.TESTNET,
  selectedWalletId: XBULL_ID,
  modules: allowAllModules(),
  styles: {
    ...configuration_here
  }
})

Since is not going to change with the system mode, you also need to allow developers to update the color after it was created so it needs to have something like a function kit.updateStyles({ ...configuration_here })

Hi i want to work on this issue @earrietadev

Hi i want to work on this issue @earrietadev

Sorry I’m working on it already. I’ll send my PR soon🙏🏾

@earrietadev please review

hello @earrietadev sorry .I have been busy lately but now I'm free.
so I have been having issues lately with the opening/starting the live server and can you please enlighten me more on the issue

hello @earrietadev sorry .I have been busy lately but now I'm free.
so I have been having issues lately with the opening/starting the live server and can you please enlighten me more on the issue

Hello @earrietadev I’m still yet to hear from you

@od-hunter I answered you a week ago: https://github.com/Creit-Tech/Stellar-Wallets-Kit/pull/23#issuecomment-2187825002

Hello @earrietadev sorry I didn’t know, can you please describe how I'm supposed to start the live server because it's not described in the package.json file. So sorry for the delay.

Hi @earrietadev  I want to work on this issue

Hello @earrietadev please I’d not be able to continue this issue, kindly assign to someone else🙏🏾
Sorry for the inconveniences caused.

Hey @earrietadev Can I take on this now?

Hi @ikemHood, thanks but I'm already doing it myself

Too bad. i had already implemented it.

@ikemHood you're always free to submit your pull request if you want

Merged at https://github.com/Creit-Tech/Stellar-Wallets-Kit/pull/33


bug "then" callback

In "then" callback the result of the request is in "data" property

Oh snap, I went a little too fast there. Thanks for fixing this! :)

Should be live as 2.0.1 if I didn't mess it up.


Target not focused correctly on accordions

Hi Chris, big fan of your very useful modules here!
I've been used Houdini quite a bit recently and I found a problem with the accordion configuration. To reproduce:

Create an accordion group with Houdini
Have a very long (height-wise) collapsible followed by a very short one
Have some content AFTER the accordion that will always overflow the viewport's height
Open the first (long) collapsible, all works fine
Open the second (short) collapsible, you'll end up seeing the content after Houdini (scroll position not set correctly)

Here's a reduced test case. Just click on "Section 2" and you'll end up in the middle of the "Long content after Houdini". Expected result would be to end up seeing the contents of Section 2.

Hey, thank you SO much for the reduced test case! Without it, I probably wouldn't have fully grasped what you were describing.
The reason this happens (as you may have already worked out) is because Houdini doesn't actually change your scrolled position on the page at all. As the second content area is much smaller, and there's content after it, the content gets pushed above the visible viewport.
The focus is correct (in that the element in :focus for keyboard navigation purposes is the new content area). Visibility is the problem.
I could address this by adding a function to jump the position on the page, but I think this is better handled by individual developers using the callbackOpen and callbackClose setting options.
Examples:

If you have a fixed header you may need to scroll not to the element itself, but to the element PLUS some extra space so it's not obscured by the header.
You may wish to animate scrolling to the content with something like Smooth Scroll instead of just jumping there.
Depending on your content structure you may not need to or want to jump to the content at all (think show more/less on YouTube videos, where the link appears after the content instead of before it).

Hope that clears things up!

You're right, callbacks where the way to go. Thanks!
If anyone is interested, here's the little function I created (called at some point on callbackOnOpen):
function scrollIfNotVisible(element) {
	var windowTop = window.pageYOffset;
	var windowBottom = windowTop + window.innerHeight;
	var top = element.offsetTop;

	if (top < windowTop || top > windowBottom) {
		smoothScroll.animateScroll(element.offsetTop - 100);
	}
}

Where the element param is the toggle received by the callback. The -100 can be tweaked to the desired offset.

Thanks for sharing that for others!


Switch Windows CI to build Release instead of Debug

This PR sets the Windows build to Release instead of Debug. ~This should fail CI, which is good because there is a bug that only shows with Release builds. If this fails CI then we can move forward with the fix.~
Success in failure. cmake is configured correctly to make a Release build which triggers the Internal compiler error in commit 3ca2d252062995978fb8c6aa5ec17dc961c4496a
D:\a\incubator-tvm\incubator-tvm\src\arith\solve_linear_inequality.cc(410): fatal error C1001: Internal compiler error.
Compiler optimization needed to be disabled for a single function in order to build Release using MSVC.
I updated the docs to include how to use visual studio 2019 for building.

Thansk @rkimball @tmoreau89 !


FileDataStore default location change

This message came in as a comment on my website.    Cross posting it here for reference.
Thank you very much for your advice. Yes i have noticed this option to provide full path like FileDataStore(@”c:\datastore”,true) and i changed my program to use full path, now it is working fine.
we have integrated google calendar api with one of our asp.net web application and for the past 3 years it was working perfectly with only store name. but after upgrading the library locally it works fine, but on deployment server we noticed that the store path is like “‘C:\Windows\system32\config\systemprofile\AppData\Roaming\Calendar.Auth.Store\”. Older version on same deployment server still using “C:\Users\LOGONUSER\AppData\Roaming\Calendar.Auth.Store” so that means some changes happened with google calendar api .net libraries. But not able to find any documents on this change.

from @chrisdunelm
It looks like this is due to a change in how the default FileStore location is determined from v1.25.0 to v1.26.2.
In v1.25.0 (on Windows Desktop) it uses Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData)
In v1.26.2+ it uses Environment.GetEnvironmentVariable("APPDATA")
On my test system these evaluated to identical directories, but it looks like this isn't the case on the user that asked the question, or perhaps isn't true generally on ASP.NET deployments.
The reason for this change is to support FileDataStore on .NET Core (which doesn't support SpecialFolder), and it was not intended to affect other customers, so this is unfortunate.
The fix would be to use an #if in the code to continue to use Environment.SpecialFolder.ApplicationData only on the .NETFramework4.5 DLL in the package.
I could do a 1.27.2 release with just this change, but I think I'd rather not. It's probably now better just to leave things as they are, seeing as this new behaviour has been released now for about six weeks.

A FAQ entry added about this in #1053.

Fixed by FAQ entry in #1053.


Update fbsync

Mainly to update GH workflow, since CI is not triggered on fbsync branch somehow.
Generated via
git cherry-pick 4d9e90af28bcb7bf97278f26008d6254d473baef^..5732d84b99b669499cb73295dc9237d6c76dc47c

on a fork of fbsync branch

merged as https://github.com/pytorch/torcharrow/commit/143c6acb9994591473b284a5d23f62c9bf9a6c97


Publish to gh-pages

Should be something like:
# Makefile
.PHONY: publish

publish:
  if [ -n "$(git status --porcelain)" ]; \
  then echo "You have uncommitted changes.";  exit 0; \
  fi

  git checkout gh-pages
  git reset --hard master

  npm run build
  rsync -a ./dist/** ./
  git push -f origin gh-pages

and then Travis can be setup to run it.

@samccone Were you working on this?

Note: will need to figure out something for the api.

yeah I will do this

Closing this as part of cleaning out old issues. I think http://marionettewires.com/ solves this anyways.


236 - SIM-Add signatures to transactions

What

Added transaction encode / decode utils and tests to the frontend
Added transaction signature to the frontend when call a contract deployment
Added new rpc endpoint send_raw_transaction that verify the transaction signature and decode the data

Why
We should add ethereum like transaction processing
Testing done

run unit testing in frontend
verify transaction signatures in front end and backend

Decisions made

We keep a single lib in frontend in this case viem to not add another

Checks

[ ] I have tested this code
[ ] I have reviewed my own PR
[ ] I have created an issue for this PR
[ ] I have set the PR name to the issue name

@bradleySuira let's do the following:

Remove the unused code from the front-end
Encode and sign the transactions just like Ethereum does it
Cristiam will fix and finish the backend side of it

@bradleySuira let's do the following:

Remove the unused code from the front-end
Encode and sign the transactions just like Ethereum does it
Cristiam will fix and finish the backend side of it

done @cristiam86 you can pull it


Avoid using RNKeychainManager

Hi. Tried to install this widget, but it requires RNKeyhainManager. It fails with "SECURITY_KEY_ANY". The known issue. After many attempts to fix it, following multiple issues and guides, after attempting manually installing it I decided to not use it.
The readme of this project states that if you decide to not use keychain manager then you have to provide your own, by setting storePin prop. I did that, but it still uses RNKeychainManager and it still fails with SECURITY_KEY_ANY == "Null" error.
How to avoid using keychain manager?
Or alternatively how to make KeyChain to not fail? And btw - I don't have it in my package.json. Previously I had, and it was of 6.1.1 version.
My example of pincode widget:
        <PINCode
          status={"choose"}
          handleResultEnterPin={(pinCode) => this.handleResultEnterPin(pinCode)}
          storePin={(pin) => {
            this.handleResultEnterPin(pin);
          }}
        />

The additional information on the issue. I use expo, and it bring problems of it's own. So the problem actually in expo, and here is an additional info: https://github.com/oblador/react-native-keychain/issues/319
Currently in attempts to solve the issue.

Yes. The question still stands. How to avoid using keychain manager in favor of alternate solutions, including provided by expo.

Hi,
Sorry for the delay.
We won't have time to invest into solving this issue atm so please feel free to open a PR if you find a good solution :)

Was this your error?: null is not an object (evaluating 'RNKeychainManager.SECURITY_LEVEL_ANY')
I got this error and fixed it per https://github.com/oblador/react-native-keychain/issues/388
You need to change a line within react-native-keychain, but it's within the node_modules directory of react-native-pincode which is itself within your own app's node_modules. So it took me a bit of poking around to find it.
change directories into node_modules/\@haskkor/react-native-pincode/node_modules/react-native-keychain/
open index.js with your favorite editor
Replace the  follow line, which is contained within export const SECURITY_LEVEL = Object.freeze({...}); :
ANY: RNKeychainManager.SECURITY_LEVEL_ANY,
with
ANY: RNKeychainManager && RNKeychainManager.SECURITY_LEVEL_ANY,
and don't change anything else.
It looks like this needs to be PR'd into react-native-keychain so that it becomes a permanent fix. (I believe reinstalling node_modules will undo your local changes).
For development purposes, this short-term fix worked for me.

Thank you for the answer. I fixed it moving from expo to react-native.
The problem is occurring with expo, since it has a "special way" handling native java components.
Not sure will I try your suggestion, but it is useful anyway to have it for anybody else facing it.

@Xeizzeth have you fixed it just moving from expo to react-native and with out applying @omorkved solution.? If so, Can you please let me know how could you do that?

@Xeizzeth have you fixed it just moving from expo to react-native and with out applying @omorkved solution.? If so, Can you please let me know how could you do that?

@Yandamuri yes, I just moved from expo to react-native, and in order to do that you need to eject. I.e. expo eject.

@Yandamuri yes, I just moved from expo to react-native, and in order to do that you need to eject. I.e. expo eject.

@Xeizzeth I didn't use expo. I just installed react-native-pin and react-native-keychain. But still facing the issue. Can you please tell me what should I do to avid this error?

@Xeizzeth I didn't use expo. I just installed react-native-pin and react-native-keychain. But still facing the issue. Can you please tell me what should I do to avid this error?

If only I knew what I did back then.
I remember doing something in java package, tweaking some settings and what not but it was like in august. A lot of water moved since then so sorry I cannot help with that in any way. I don't work on this project since september as well.
But one thing I do remember - it used specific version of keymanager, or keymanager used specific version of dependency.
So take a closer look at keymanager and it's dependencies. The only I can suggest.

If only I knew what I did back then.
I remember doing something in java package, tweaking some settings and what not but it was like in august. A lot of water moved since then so sorry I cannot help with that in any way. I don't work on this project since september as well.
But one thing I do remember - it used specific version of keymanager, or keymanager used specific version of dependency.
So take a closer look at keymanager and it's dependencies. The only I can suggest.

@omorkved I have installed both react-native-pin and react-native-keychain. But I didn't find the path node_modules/\@haskkor/react-native-pincode/node_modules/react-native-keychain. in fact there is no node_modules folder inside react-native-pincode. Can you please guide me on how to reach the mentioned path?

@omorkved I have installed both react-native-pin and react-native-keychain. But I didn't find the path node_modules/\@haskkor/react-native-pincode/node_modules/react-native-keychain. in fact there is no node_modules folder inside react-native-pincode. Can you please guide me on how to reach the mentioned path?

react-native-keychain has fixed this issue. but react-native-pincode is still using the old version. so to overcome this issue, you have to add the new version in the resolutions of your package.json file to force all packages to use only this version or create a patch file. (a patch file stores your node_module changes)
    "react-native-svg": "^12.1.1",
  },```


Add an option to export webpack compilation stats

I have a very long renderer build and i need to investigate it.
the best way to do this is to enable stats in webpack and analyze them here:
http://webpack.github.io/analyse/
But for that we need to way to @electron-forge/plugin-webpack to export json stats.
Maybe a jsonStats option in mainConfig and renderer```?
Thanks

I'd probably call it statsFile, but otherwise this seems reasonable to me (as someone who doesn't use webpack).

@malept thanks! By the way on the same note do you know if it is normal for the "stats" webpack config not to work. I tried to put it to "verbose" for my renderer config. But in the web console i still get normal stats.
Can create another issue if necessary

As I mentioned, I don't use webpack (and I didn't write the Forge plugin), so I don't know those sorts of details

By the way on the same note do you know if it is normal for the "stats" webpack config not to work.

Yes, that option is only respected by webpack if webpack-cli or webpack-dev-server is the thing running / owning the compiler.  In this case forge is manually spinning up and controlling the compilers.  Forge is manually logging out those stats.
https://github.com/electron-userland/electron-forge/blob/master/packages/plugin/webpack/src/WebpackPlugin.ts#L233
https://github.com/electron-userland/electron-forge/blob/master/packages/plugin/webpack/src/WebpackPlugin.ts#L281-L286


[ALS-5060] Jenkins https

Add script to enabel https in Jenkins
Add documentation
Add to initial config flow

@Luke-Sikina Should this be pointing to the release branch?

@Luke-Sikina Should this be pointing to the release branch?

FWIW, I caught this before I read your comment.


public key denied?

When I run reapp new:
Creating new reapp folder for: example...
Running git clone --depth=1 git@github.com:reapp/reapp-starter.git /home/vagrant/example...
Error
{ [Error: Command failed: Cloning into '/home/vagrant/example'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
] killed: false, code: 128, signal: null }

Make sure you have github's publickey setup:
https://help.github.com/articles/error-permission-denied-publickey/

Thanks!


TypeError: 'module' object is not callable

Code:
import telepot
import pprint
import time
from telepot.loop import MessageLoop

bot = telepot.Bot("<BOT_TOKEN>")
# chat_id = "<CHAT_ID>"

response = bot.getUpdates()
pprint(response)

def handle(msg):
    pprint(msg)
    content_type, chat_type, chat_id = telepot.glance(msg)
    print(content_type, chat_type, chat_id)

MessageLoop(bot, handle).run_as_thread()

while 1:
    time.sleep(10)

Error I'm getting:
Traceback (most recent call last):
  File "/home/sjs/Projects/prodipto-telegram-bot-sjs/test.py", line 11, in <module>
    pprint(response)
TypeError: 'module' object is not callable

What should be the problem?

Okay, pprint() not working, but print() is working. But pprint() was in doc. Something isn't working?

Oh, my bad. I should import like from pprint import pprint.


visit properties in ObjectPattern - fixes #95

This should fix it @ide

I've checked it with that issue in react-bootstrap.
It works! :rainbow: :sparkle:

Thanks @hzoo!

Ok pushed 3.1.14!

Thanks @hzoo! :cherries:


Remediating Azure Artifacts Configuration Issues in your Repository

For status checks on the develop branch, please use TransportPackage-Foundation
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=57248)
and run the build against your PR branch with the default parameters.
For status checks on the main branch, please use microsoft.ProjectReunion
(https://dev.azure.com/ms/ProjectReunion/_build?definitionId=391&_a=summary)
and run the build against your PR branch with the default paramters.

/azp run


Can not see relabeled labels in queries

What did you expect to see?
relabeled labels in queries
What did you see instead? Under which circumstances?
can not see relabeled labels in queries

Prometheus version:
quay.io/prometheus/prometheus:v1.3.0

Prometheus configuration file:

    - job_name: 'kubernetes-service-endpoints'
      kubernetes_sd_configs:
      - role: endpoints

      relabel_configs:
      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
        action: keep
        regex: true
      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
        action: replace
        target_label: __scheme__
        regex: (https?)
      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
        action: replace
        target_label: __metrics_path__
        regex: (.+)
      - source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
        action: replace
        target_label: __address__
        regex: (.+)(?::\d+);(\d+)
        replacement: $1:$2
      - action: labelmap
        regex: __meta_kubernetes_service_label_(.+)
      - source_label: [__meta_kubernetes_pod_host_ip]
        action: replace
        target_label: host_ip
      - source_labels: [__meta_kubernetes_service_namespace]
        action: replace
        target_label: kubernetes_namespace
      - source_labels: [__meta_kubernetes_service_name]
        action: replace
        target_label: kubernetes_name

During quierying i can not see relabeled labels in job configuration, f.e querying node_load1 i get:
node_load1{app="node-exporter",instance="<IP_ADDRESS>:9100",job="kubernetes-service-endpoints",kubernetes_name="node-exporter",name="node-exporter"}	3.21
node_load1{app="node-exporter",instance="<IP_ADDRESS>:9100",job="kubernetes-service-endpoints",kubernetes_name="node-exporter",name="node-exporter"}	2.87
node_load1{app="node-exporter",instance="<IP_ADDRESS>:9100",job="kubernetes-service-endpoints",kubernetes_name="node-exporter",name="node-exporter"}	4.37
node_load1{app="node-exporter",instance="<IP_ADDRESS>:9100",job="kubernetes-service-endpoints",kubernetes_name="node-exporter",name="node-exporter"}	2.13

so i don't see my label:
- source_label: [__meta_kubernetes_pod_host_ip]
        action: replace
        target_label: host_ip

That's interesting! I just tried this on a local minikube cluster and I don't seem to have the meta label __meta_kubernetes_pod_host_ip available either. I'll investigate!

I was a bit too quick there. It does seem to be there for me: __meta_kubernetes_pod_host_ip="<IP_ADDRESS>". I'll try to reproduce with the exact same config.

I use kubernetes 1.3.4 btw

and __meta_kubernetes_pod_host_ip is not the only one label that i don't see there is also __meta_kubernetes_service_namespace and probably few others.
I use node-exporter as a daemon in kubernetes from CoreOS manifest

There is a typo in your config source_label -> source_labels 🙂

what about
- source_labels: [__meta_kubernetes_service_namespace]
        action: replace
        target_label: kubernetes_namespace

That would actually just be __meta_kubernetes_namespace as selection in kubernetes is namespace scoped, so it doesn't make much sense to include endpoints_namespace, service_namespace and pod_namespace just to get the same value in all of them 🙂

Is there anything else that doesn't seem to work @widgetpl ?

I am trying to reload Prometheus configuration with curl -XPOST http://<IP_ADDRESS>:9090//-/reload but it seems that it dosen't work. I havent setup any persistent storage for Prometheus yet so probably I will loose all the data. What about __meta_kubernetes_endpoints_namespace, __meta_kubernetes_service_namespace and __meta_kubernetes_pod_namespace i don't even see them in Prometheus before relabeling in Kubernetes 1.3.4

Yes that's what I said, __meta_kubernetes_endpoints_namespace, __meta_kubernetes_service_namespace and __meta_kubernetes_pod_namespace don't exist. It's only __meta_kubernetes_namespace. Prometheus doesn't reload your config if there is an error. Have a look at the logs and the prometheus_config_last_reload_successful as well as the prometheus_config_last_reload_success_timestamp_seconds metrics exposed by Prometheus. But to make sure before trying to reload you can always use promtool to check whether your config is valid.

thanks for advice about promtool as i haven't heard about that. It looks that everything is ok now so issue can be closed.

@brancz just one more question. I have updated configuration in ConfigMap and checked it with promtool inside Prometheus pod but i don't see any updates in Prometheus /targets UI.
Does curl -XPOST http://<IP_ADDRESS>:9090//-/reload is the correct way of reloading configuration?

I'm not sure it makes a difference but I use http://localhost:9090/-/reload, so maybe there is one / to much in your url.


N-gram statistic model

Hi,
I would like to ask how to implement the bi-directional 3-gram model for the generator. Could you please share the codes or any other material？
Thanks a lot.
Best.

We simply use a statistics-based language model. We first calculate the tri-gram distribution on the training data and then predict mask words.


Support virtual line to be floating

This is a beautiful plugin, can you help support a flag to allow virtual line float on the buffer? instead of insert a new line in the below, insert new line always change the character positioning when switch line.

Do you mean that:

The suggestion line should be in a fixed position? Similar to the default command line?
The suggestion line should cover or prepend the text in the line below the cursor line?

If option 1 then, I don't know if the plugin would work as intended if the line wasn't directly below the line that it references.
If option 2, then I think that would be equally distracting.
I am not against the idea, I am just not sure how you envision it working.

I was going to ask for this!
The current implementation causes lines to constantly shift when moving up or down.
The idea is to show the hints using floating windows like those that popup for completion and code signatures for example. The difference is that the popup would always be left aligned with the active buffer in order for the hints to align.

I can see the advantages. I want to release 1.0.0 as a stable version with a feature set, then we can work on some of the more experimental stuff

I was playing trying to mockup as if the popup was a ruler from 0 to $ and │ as the current position:

This is what I came for the following line with cursor at the T
  This can begin to become be cool
  ^

and then after pressing fb with curson at the b
  This can begin to become be cool
           ^

thanks @lpanebr describe the needs more detail

The comments around the virtual line causing lines to constantly shift when moving up or down are valid. I'd just like to note that the suggestion here of a floating window brings its own downsides; the window obscures other text. Some people, myself included, would probably find this behaviour more intrusive than the the current virtual line implementation. So I hope the current implementation might also remain.

Yes, I agree that having the pop-up hide content will also be annoying.
What about having the pop-up fake transparency by using colors and replacing characters of the hidden text?
Suppose the following text and mockup, with the cursor going to and back to the T:
  This can begin to become be cool
Here is another line of text to think about the pop-up interference.

I love the look of this @lpanebr
Although the implementation might be a nightmare especially in the edge cases with multibyte chars etc
But I do like the way it looks

I agree, that looks awesome! Might be a bit tricky but winblend and overlay extmarks should cover it I think

What about having the pop-up fake transparency by using colors and replacing characters of the hidden text?

It looks fancy but IMO from a usability perspective it's the worst of both the virtual line and the floating window combined.

Is it possible to add the virtual line above (as it is currently)? I often accidentally remove a line, because my brain interprets the line below as extra space.I somewhat more orientate to what comes next than the previous line. Maybe I just I have to get more used to it as I only started using the plugin, but maybe the option to have the virtual line above could also help.

I proposed something similar in #54 but it was closed in favour of this ticket. I have a fork with these changes that I tried for a while, which also has a dynamic line position option. If you want to try it you're welcome. It's a few commits behind this repo and I'm probably not going to maintain it since it was more proof-of-concept and also might have some bugs): https://github.com/josh-nz/precognition.nvim/tree/feature/dynamic-virt-line
I'm undecided if I prefer it above or below or dynamic, above has the same issues as below IMO - you sometimes delete the line above, or misinterpret it as blank. I don't think there is really a solution for this other than to adapt to the display. This issue outlines some alternatives, but they have their own drawbacks IMO.

Thanks! Yes I agree the alternatives discussed here have their own drawbacks. I hope to find the time to check out your adaptation.


GitHub Action for demo generation

Generates sample projects on every tag push or after a manual run.
#94

More or less. Seems to be the most popular action for publishing.


fix build problem

ex5 2 ../../exercise5/acycpos-1.gph does not work (with 1 it works). Please correct.


error using single file upload with (php/index.php)

Hi,
if you use php with single file upload-field UploadHandler did not seems to work - handle_file_upload gets wrong parameters.
isset($_SERVER['HTTP_X_FILE_NAME']) ?
$_SERVER['HTTP_X_FILE_NAME'] : (isset($upload['name']) ?
isset($upload['name']) : null),
should be
isset($_SERVER['HTTP_X_FILE_NAME']) ?
$_SERVER['HTTP_X_FILE_NAME'] : (isset($upload['name']) ?
$upload['name'] : null),
and so on...

Thx for this information...


test: synchronizing gherkin spec

What
APM agent specs automatic sync
Why
Changeset

https://github.com/elastic/apm/commit/8b4578b [META 388] Proposal for collecting Azure App Service cloud metadata (https://github.com/elastic/apm/pull/365)

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1066 opened

Start Time: 2021-03-11T12:50:59.724+0000

Duration: 26 min 14 sec

Commit: e387a5776c2b97ea53d10293f253375583e613e1

Test stats :test_tube:

Test
Results

Failed
0

Passed
7948

Skipped
5735

Total
13683

Trends :test_tube:

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
7948

Skipped
5735

Total
13683


Logs and restore process

Hi,
Your program is excellent piece of software which ticks most of our boxes.
We have been testing backup process and it looks very good. Now that we have moved to our next phase of testing, which is restoring.
When we did our first restore, i have seen that it has created a snapshot and then volume which is ready to connect which is good. however one small issue is, the task screen is showing it as red in color and the temp volume is still attached to the instance.
I tried to find the issue but cant really a place to check the logs from the UI.
I also been checking few other past issues where i found that you mentioned new version is coming, Is there any date range ?
Everytime, i login into the account via UI, it says me that there is a new version

Is there any way, where i can find out what is the current version of the system and what is the new version of the system is.?
Thank you.

@NareshDealer This message should not be appearing in the about to be released version. If you go to the apache tomcat logs and view catalina.out and related details it will tell what the issue is. Post some details of the log. Timeout could be part of it.

@rabay108  thank you for your quick response. I went through the log and found the following...
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status ispendingprogress:63%
Snapshot status iscompletedprogress:100%
2016-07-27 22:19:39.903 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:
2016-07-27 22:19:39.903 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 0
com.amazonaws.AmazonServiceException: Volume vol-68aab6bb is currently attached to i-8644b919 (Service: AmazonEC2; Status Code: 400; Error Code: VolumeInUse; Request ID: 25c35d56-bab7-4a48-b70b-acdb7b52085f)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1182) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:770) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11783) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.deleteVolume(AmazonEC2Client.java:3168) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at sun.reflect.GeneratedMethodAccessor164.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_91]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.1.RELEASE.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sungardas.enhancedsnapshots.components.RetryInterceptor.invoke(RetryInterceptor.java:25) [RetryInterceptor.class:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sun.proxy.$Proxy60.deleteVolume(Unknown Source) [?:?]
at com.sungardas.enhancedsnapshots.service.impl.AWSCommunicationServiceImpl.deleteVolume(AWSCommunicationServiceImpl.java:295) [AWSCommunicationServiceImpl.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.restoreFromBackupFile(AWSRestoreVolumeTask.java:220) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.execute(AWSRestoreVolumeTask.java:87) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:148) [WorkersDispatcher$TaskWorker.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
2016-07-27 22:20:10.110 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:
2016-07-27 22:20:10.110 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 1
com.amazonaws.AmazonServiceException: Volume vol-68aab6bb is currently attached to i-8644b919 (Service: AmazonEC2; Status Code: 400; Error Code: VolumeInUse; Request ID: 4ecf9002-18dd-44a6-8d22-ed8b56a3d43b)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1182) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:770) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11783) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.deleteVolume(AmazonEC2Client.java:3168) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at sun.reflect.GeneratedMethodAccessor164.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_91]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.1.RELEASE.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sungardas.enhancedsnapshots.components.RetryInterceptor.invoke(RetryInterceptor.java:25) [RetryInterceptor.class:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sun.proxy.$Proxy60.deleteVolume(Unknown Source) [?:?]
at com.sungardas.enhancedsnapshots.service.impl.AWSCommunicationServiceImpl.deleteVolume(AWSCommunicationServiceImpl.java:295) [AWSCommunicationServiceImpl.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.restoreFromBackupFile(AWSRestoreVolumeTask.java:220) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.execute(AWSRestoreVolumeTask.java:87) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:148) [WorkersDispatcher$TaskWorker.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
2016-07-27 22:20:40.255 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:
2016-07-27 22:20:40.255 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 2
com.amazonaws.AmazonServiceException: Volume vol-68aab6bb is currently attached to i-8644b919 (Service: AmazonEC2; Status Code: 400; Error Code: VolumeInUse; Request ID: 40acba95-2fdb-4de8-8727-4c115700137f)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1182) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:770) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) ~[aws-java-sdk-core-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11783) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.deleteVolume(AmazonEC2Client.java:3168) ~[aws-java-sdk-ec2-1.10.11.jar:?]
at sun.reflect.GeneratedMethodAccessor164.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_91]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.1.RELEASE.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sungardas.enhancedsnapshots.components.RetryInterceptor.invoke(RetryInterceptor.java:25) [RetryInterceptor.class:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sun.proxy.$Proxy60.deleteVolume(Unknown Source) [?:?]
at com.sungardas.enhancedsnapshots.service.impl.AWSCommunicationServiceImpl.deleteVolume(AWSCommunicationServiceImpl.java:295) [AWSCommunicationServiceImpl.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.restoreFromBackupFile(AWSRestoreVolumeTask.java:220) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.tasks.AWSRestoreVolumeTask.execute(AWSRestoreVolumeTask.java:87) [AWSRestoreVolumeTask.class:?]
at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:148) [WorkersDispatcher$TaskWorker.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]

The volume vol-68aab6bb is currently attached to the server where the application is running. So if im not wrong, the restore process will be creating the volume from backup, creating a snapshot of volume, cloning of volume and delete the volume which was attached to server before cloning.
now i can see the cloned/restored volume and also the volume attached to the server.
I have attached the restored/clonned volume to the instance as root device and trying to start the instance.
the state of instance goes to running but the initialization checks fails and cant login to the server.

@NareshDealer This issue is fixed in the latest version 2.0 which is in the Develop Branch and we are in the process of merging it to Master. How much volume was the disk that was tried.

@rabay108  it was for 60GB volume. Is there any date when 2.0 will be out.? as currently it is only doing part of the work and we cant test it any further.
Thanks.

@rabay108  I m just wondering is there any ami build which i can use to deploy ver 2.0.?
Or is there any way i can copy those files which are fixed to use in ver1.0 which will fix the issue which i had.
Really appreciate if you can help me on this.  Thanks..

@NareshDealer ver 2.0 will be available in the nearest future, also if you are short in time you can build AMI with ESS v2.0 by your own, please refer to BuildDeploy.md document for the instructions

@iradaik Thank you for the reply. I have just noticed there is a version 2.0 AMI and quickly jumped on it to test. Instance created good and during my initial setup, i m facing some issue.
this the log output when error occurs.
2016-08-23 15:31:07.125 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - List db structure: [BackupList, Configurations, Retention, Snapshots, Tasks, Users]
2016-08-23 10:31:12 UTC-5
2016-08-23 15:31:07.126 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Check db structure is present: false
2016-08-23 10:31:12 UTC-5
2016-08-23 15:31:07.128 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - sdfs already exists...
2016-08-23 10:31:12 UTC-5
2016-08-23 15:31:49.624 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-10] InitConfigurationServiceImpl - Creating bucket enhancedsnapshots.i-ff3bf86e in us-east-1 region
2016-08-23 10:31:55 UTC-5
2016-08-23 15:31:49.916 [ERROR] [http-nio-<IP_ADDRESS>-8080-exec-10] InitController - com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 23AC0A28097B6004), S3 Extended Request ID: G8oOwdoeD3K2BHefcbxHQzzDP+CifWfjRm/1MkqMkZwgz9JKT+srQaFVYB8ma6e7xzwXjigRJC8=
2016-08-23 10:31:55 UTC-5
2016-08-23 15:48:15.405 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-9] InitConfigurationServiceImpl - Creating bucket enhancedsnapshots.i-ff3bf86e in us-east-1 region
2016-08-23 10:48:21 UTC-5
2016-08-23 15:48:15.678 [ERROR] [http-nio-<IP_ADDRESS>-8080-exec-9] InitController - com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 70FA7D8FBAA841F7), S3 Extended Request ID: i4emvYDHHa8ZHwnZDnpEV9vnKCZUwOKtjuQHQL8pBh1mvBt51r8FsmTVshXqmt3xnvpDOA4N+yY=
2016-08-23 10:48:21 UTC-5
My Role policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"ec2:AttachVolume",
"ec2:CreateSnapshot",
"ec2:CreateTags",
"ec2:CreateVolume",
"ec2:DeleteSnapshot",
"ec2:DeleteTags",
"ec2:DeleteVolume",
"ec2:DescribeAvailabilityZones",
"ec2:DescribeInstanceAttribute",
"ec2:DescribeInstanceStatus",
"ec2:DescribeInstances",
"ec2:TerminateInstances",
"ec2:DescribeRegions",
"ec2:DescribeSnapshotAttribute",
"ec2:DescribeSnapshots",
"ec2:DescribeTags",
"ec2:DescribeVolumeAttribute",
"ec2:DescribeVolumeStatus",
"ec2:DescribeVolumes",
"ec2:DetachVolume",
"ec2:EnableVolumeIO",
"ec2:ModifyInstanceAttribute",
"ec2:ModifySnapshotAttribute",
"ec2:ModifyVolumeAttribute",
"ec2:ResetSnapshotAttribute",
"s3:ListAllMyBuckets",
"dynamodb:ListTables",
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents",
"logs:DescribeLogStreams"
],
"Resource": "",
"Effect": "Allow",
"Sid": "1"
},
{
"Action": [
"dynamodb:DescribeReservedCapacity",
"dynamodb:DescribeReservedCapacityOfferings"
],
"Resource": "arn:aws:dynamodb:::",
"Effect": "Allow",
"Sid": "AllowReservedCapacityDescriptions"
},
{
"Condition": {},
"Action": "dynamodb:",
"Resource": [
"arn:aws:dynamodb:us-east-1:796676131367:table/BackupList",
"arn:aws:dynamodb:us-east-1:796676131367:table/Configurations",
"arn:aws:dynamodb:us-east-1:796676131367:table/Retention",
"arn:aws:dynamodb:us-east-1:796676131367:table/Snapshots",
"arn:aws:dynamodb:us-east-1:796676131367:table/Tasks",
"arn:aws:dynamodb:us-east-1:796676131367:table/Users",
"arn:aws:dynamodb:us-east-1:796676131367:table/BackupList/index/",
"arn:aws:dynamodb:us-east-1:796676131367:table/Configurations/index/",
"arn:aws:dynamodb:us-east-1:796676131367:table/Retention/index/",
"arn:aws:dynamodb:us-east-1:796676131367:table/Snapshots/index/",
"arn:aws:dynamodb:us-east-1:796676131367:table/Tasks/index/",
"arn:aws:dynamodb:us-east-1:796676131367:table/Users/index/"
],
"Effect": "Allow"
},
{
"Condition": {},
"Action": "s3:",
"Resource": "arn:aws:s3:::enhancedsnapshots.",
"Effect": "Allow"
},
{
"Condition": {},
"Action": "s3:",
"Resource": "arn:aws:s3:::enhancedsnapshots../",
"Effect": "Allow"
}
]
}

I have changed the resource name for s3 bucket but still no luck.. Please help. thanks.

@NareshDealer You have 2 choices (1) Use the latest marketplace version for 2.0 with the cloud creation stack and it will be self sufficient to create everything that you need and only inputs required from you is the key pair and the IP/32 that goes in to the SSH and Http/Https security group parameters that can also be reset - https://aws.amazon.com/marketplace/pp/B01CIWY4UO
(2)  Depending on the region select the AMI from that link for eg. ami-9a5ad28d for us-east-1 and prerequisite is to create the admin role using  - https://github.com/SungardAS/particles-enhanced-snapshots/blob/develop/particles/cftemplates/xpl_sungardas_enhanced_snapshots_admin_role.template.json
Note: We will also merge the particles project develop branch to master this week..

@rabay108  Thank you for your quick response. I have tried the first choice and it did went well, however we dont want a public ip address so i skipped that step in the stack. Now when i tried to login and setup initial settings, i got this error failed to start SDFS. I have attached the log below.
23-Aug-2016 17:41:51.710 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 7311 ms
2016-08-23 12:42:07 UTC-5
2016-08-23 17:45:19,289 DEBUG Using default SystemClock for timestamps
2016-08-23 12:45:25 UTC-5
2016-08-23 17:45:19.293 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-2] InitConfigurationServiceImpl - List db structure: [BackupList, Configurations, Retention, Snapshots, Tasks, Users]
2016-08-23 12:45:25 UTC-5
2016-08-23 17:45:19.294 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-2] InitConfigurationServiceImpl - Check db structure is present: false
2016-08-23 12:45:25 UTC-5
2016-08-23 17:45:19.295 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-2] InitConfigurationServiceImpl - sdfs already exists...
2016-08-23 12:45:25 UTC-5
2016-08-23 17:45:56.243 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating bucket enhancedsnapshots.i-31fb39a0 in us-east-1 region
2016-08-23 12:46:02 UTC-5
2016-08-23 17:45:56.730 [DEBUG] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Config file /opt/apache-tomcat-8.0.24/conf/EnhancedSnapshots.properties stored successfully.
2016-08-23 12:46:02 UTC-5
2016-08-23 17:45:56.818 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_BackupList ...
2016-08-23 12:46:02 UTC-5
2016-08-23 17:46:06.883 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_BackupList was created successfully.
2016-08-23 12:46:13 UTC-5
2016-08-23 17:46:06.928 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_Configurations ...
2016-08-23 12:46:13 UTC-5
2016-08-23 17:46:11.965 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_Configurations was created successfully.
2016-08-23 12:46:18 UTC-5
2016-08-23 17:46:12.007 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_Retention ...
2016-08-23 12:46:18 UTC-5
2016-08-23 17:46:22.066 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_Retention was created successfully.
2016-08-23 12:46:28 UTC-5
2016-08-23 17:46:22.111 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_Tasks ...
2016-08-23 12:46:28 UTC-5
2016-08-23 17:46:27.152 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_Tasks was created successfully.
2016-08-23 12:46:33 UTC-5
2016-08-23 17:46:27.212 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_Snapshots ...
2016-08-23 12:46:33 UTC-5
2016-08-23 17:46:37.268 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_Snapshots was created successfully.
2016-08-23 12:46:43 UTC-5
2016-08-23 17:46:37.301 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Creating table ENHANCEDSNAPSHOTS_i-31fb39a0_Users ...
2016-08-23 12:46:43 UTC-5
2016-08-23 17:46:47.352 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitConfigurationServiceImpl - Table ENHANCEDSNAPSHOTS_i-31fb39a0_Users was created successfully.
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:47.434 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] InitController - Context refresh process started.
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.151 [DEBUG] [http-nio-<IP_ADDRESS>-8080-exec-3] RetentionServiceImpl - Retention started
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.169 [DEBUG] [http-nio-<IP_ADDRESS>-8080-exec-3] RetentionServiceImpl - Finished
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.183 [INFO ] [pool-2-thread-1] WorkersDispatcher$TaskWorker - Starting worker dispatcher
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.492 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] AWSCommunicationServiceImpl - awslogs restarted successfully
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.492 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] CreateAppConfigurationImpl - Initialization started
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.941 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] CreateAppConfigurationImpl - Initialization restore
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.941 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] CreateAppConfigurationImpl - Starting SDFS
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.941 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - Executing script: [/opt/apache-tomcat-8.0.24/webapps/ROOT/WEB-INF/classes/sdfs.sh, --state]
2016-08-23 12:46:53 UTC-5
Determine sdfs state
2016-08-23 12:46:53 UTC-5
sdfs is not running
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.948 [DEBUG] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - SDFS is currently stopped
2016-08-23 12:46:53 UTC-5
2016-08-23 17:46:48.965 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - Executing script: [/opt/apache-tomcat-8.0.24/webapps/ROOT/WEB-INF/classes/sdfs.sh, --configure, 500GB, enhancedsnapshots.i-31fb39a0, US, 1GB]
2016-08-23 12:46:53 UTC-5
Configure SDFS
2016-08-23 12:47:23 UTC-5
SDFS volume size: 500GB
2016-08-23 12:47:23 UTC-5
Bucket name: enhancedsnapshots.i-31fb39a0
2016-08-23 12:47:23 UTC-5
Location: US
2016-08-23 12:47:23 UTC-5
Local cache size: 1GB
2016-08-23 12:47:23 UTC-5
Attempting to create SDFS volume ...
2016-08-23 12:47:23 UTC-5
Volume [awspool] created with a capacity of [500GB]
2016-08-23 12:47:23 UTC-5
check [/etc/sdfs/awspool-volume-cfg.xml] for configuration details if you need to change anything
2016-08-23 12:47:23 UTC-5
SDFS is configured
2016-08-23 12:47:23 UTC-5
2016-08-23 17:47:18.685 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - SDFS is configured
2016-08-23 12:47:23 UTC-5
2016-08-23 17:47:18.685 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - Executing script: [/opt/apache-tomcat-8.0.24/webapps/ROOT/WEB-INF/classes/sdfs.sh, --mount, false]
2016-08-23 12:47:23 UTC-5
Mounting
2016-08-23 12:47:32 UTC-5
SDFS restore: false
2016-08-23 12:47:32 UTC-5
Failed to mount SDFS
2016-08-23 12:47:32 UTC-5
2016-08-23 17:47:26.000 [ERROR] [http-nio-<IP_ADDRESS>-8080-exec-3] SDFSStateServiceImpl - com.sungardas.enhancedsnapshots.exception.ConfigurationException: Failed to start SDFS
2016-08-23 12:47:32 UTC-5
java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at java.lang.Thread.sleep(Thread.java:340) at java.util.concurrent.TimeUnit.sleep(TimeUnit.java:386) at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.sleep(WorkersDispatcher.java:168) at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:147) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
2016-08-23 12:47:32 UTC-5
2016-08-23 17:47:26.005 [WARN ] [pool-2-thread-1] WorkersDispatcher$TaskWorker - Stopping worker dispatcher ...
2016-08-23 12:47:32 UTC-5
2016-08-23 17:47:26.015 [ERROR] [http-nio-<IP_ADDRESS>-8080-exec-3] InitController - org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'CreateAppConfiguration': Invocation of init method failed; nested exception is com.sungardas.enhancedsnapshots.exception.ConfigurationException: Failed to start SDFS

@rabay108  Can you please guide me..?

@NareshDealer  - We want to make sure the normal scenarios works fine for you (a) Marketplace (b) AMI using the public IP and not sure you can do it for test on your environment. For the issue attach
/var/log/sdfs_mount.log so we could understand why SDFS was not mounted. BTW, User can find all logs also in CloudWatch service, since we store them

@rabay108  thank you for your response.
Please find the log below.
Running Program SDFS Version 3.1.11
reading config file = /etc/sdfs/awspool-volume-cfg.xml
java.net.UnknownHostException: ip-10-102-0-114: ip-10-102-0-114: unknown error
at java.net.InetAddress.getLocalHost(InetAddress.java:1505)
at org.opendedup.util.RandomGUID.(RandomGUID.java:36)
at org.opendedup.sdfs.notification.SDFSEvent.(SDFSEvent.java:95)
at org.opendedup.sdfs.notification.SDFSEvent.mountEvent(SDFSEvent.java:283)
at org.opendedup.sdfs.servers.SDFSService.start(SDFSService.java:51)
at fuse.SDFS.MountSDFS.setup(MountSDFS.java:203)
at fuse.SDFS.MountSDFS.init(MountSDFS.java:238)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207)
Caused by: java.net.UnknownHostException: ip-10-102-0-114: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getLocalHost(InetAddress.java:1500)
... 11 more
Loaded entries 0
Mounted Filesystem
~

@rabay108  this is etc/sdfs/awspool-volume-cfg.xml

It seems that InetAddress.getLocalHost() ignores the /etc/resolv.conf but
only looks at the /etc/hosts file.  Please add the IP and hostname to this
file solves the problem.
On Fri, Aug 26, 2016 at 12:40 PM, NareshDealer<EMAIL_ADDRESS>wrote:

@rabay108 https://github.com/rabay108 thank you for your response.
Please find the log below.
Running Program SDFS Version 3.1.11
reading config file = /etc/sdfs/awspool-volume-cfg.xml
java.net.UnknownHostException: ip-10-102-0-114: ip-10-102-0-114: unknown
error
at java.net.InetAddress.getLocalHost(InetAddress.java:1505)
at org.opendedup.util.RandomGUID.(RandomGUID.java:36)
at org.opendedup.sdfs.notification.SDFSEvent.(SDFSEvent.java:95)
at org.opendedup.sdfs.notification.SDFSEvent.
mountEvent(SDFSEvent.java:283)
at org.opendedup.sdfs.servers.SDFSService.start(SDFSService.java:51)
at fuse.SDFS.MountSDFS.setup(MountSDFS.java:203)
at fuse.SDFS.MountSDFS.init(MountSDFS.java:238)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.commons.daemon.support.DaemonLoader.load(
DaemonLoader.java:207)
Caused by: java.net.UnknownHostException: ip-10-102-0-114: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getLocalHost(InetAddress.java:1500)
... 11 more
Loaded entries 0
Mounted Filesystem
~
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SungardAS/enhanced-snapshots/issues/68#issuecomment-242831938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADa7qPHOJrefAj7gj45OX3BVIwVDbIaYks5qj0EsgaJpZM4JWj_F
.

@opendedup  Thank you for your reply.
2016-08-26 20:23:38.625 [INFO ] [http-nio-<IP_ADDRESS>-8080-exec-1] InitConfigurationServiceImpl - Check db structure is present: true
2016-08-26 15:23:38 UTC-5
2016-08-26 20:23:38.713 [ERROR] [http-nio-<IP_ADDRESS>-8080-exec-1] InitController - com.amazonaws.AmazonServiceException: User: arn:aws:sts::xxxxxxxxxxx:assumed-role/AWSMPEnhancedSnapshotstoolcreationstack-EsAdmin-N6W2EG3H4K26/i-bcba7a8d is not authorized to perform: dynamodb:Scan on resource: arn:aws:dynamodb:us-east-1:xxxxxxxxxxx:table/Users (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: AccessDeniedException; Request ID: E5OIK83LG23MP5L4MECQT1T8LBVV4KQNSO5AEMVJF66Q9ASUAAJG)

@NareshDealer Please use this admin role template to create es-admin role(This will soon to be merged to master) https://github.com/SungardAS/particles-enhanced-snapshots/blob/develop/particles/cftemplates/xpl_sungardas_enhanced_snapshots_admin_role.template.json
(Incidentally all the latest jsons are available in this branch until we move to Master early next week)
Let us know

@rabay108 i have given the role full admin access to make sure it was role issue but still i cant login. I was able to see that error on cloudwatch but now cloudwatch doesnt show any error. So dont know where to check.
But i can create the role from the template above, if needed.

@NareshDealer if you are using the AMI then you need to create the role and use it in AMI at the time of launch by selecting the IAM Role.. changing afterwards will not help.Best is to have a "reference purpose" instance created from marketplace just in case until all the issues are resolved.

@rabay108 I have now got it to working.. When i added full access policy to the role, i was able to login with admin@enhancedsnapshots username and then it took me straight to configuration.
When i continued with setting up the user, it finally gave me congratulations screen and now i can login with account created.
So now i need to drill down and use the policy from the template you gave to test and if it allows me.

@rabay108  I tried do some tests and i get the error below:

13:01:19
2016-08-30 19:00:00.000 [DEBUG] [taskScheduler-1] VolumeServiceImpl - Getting volume list ...
2016-08-30 19:00:00.000 [DEBUG] [taskScheduler-1] VolumeServiceImpl - Getting volume list ...

14:00:07
2016-08-30 19:01:00.848 [INFO ] [pool-2-thread-1] AWSBackupVolumeTaskExecutor - SnapshotEntry created: {SnapshotId: snap-a9f6d332,VolumeId: vol-420bd891,State: completed,StartTime: Tue Aug 30 19:00:07 UTC 2016,Progress: 100%,OwnerId:<PHONE_NUMBER>67,Description: vol-420bd891__2016.08.30_T07:00:07,VolumeSize: 22,Tags: [],Encrypted: false,}
2016-08-30 19:01:00.848 [INFO ] [pool-2-thread-1] AWSBackupVolumeTaskExecutor - SnapshotEntry created: {SnapshotId: snap-a9f6d332,VolumeId: vol-420bd891,State: completed,StartTime: Tue Aug 30 19:00:07 UTC 2016,Progress: 100%,OwnerId:<PHONE_NUMBER>67,Description: vol-420bd891__2016.08.30_T07:00:07,VolumeSize: 22,Tags: [],Encrypted: false,}

14:00:07
waitForAvailableState.current state: available

14:01:00
2016-08-30 19:01:16.277 [INFO ] [pool-2-thread-1] AWSBackupVolumeTaskExecutor - Volume created: {VolumeId: vol-225f4df0,Size: 22,SnapshotId: snap-a9f6d332,AvailabilityZone: us-east-1b,State: available,CreateTime: Tue Aug 30 19:01:00 UTC 2016,Attachments: [],Tags: [],VolumeType: gp2,Iops: 100,Encrypted: false,}
2016-08-30 19:01:16.277 [INFO ] [pool-2-thread-1] AWSBackupVolumeTaskExecutor - Volume created: {VolumeId: vol-225f4df0,Size: 22,SnapshotId: snap-a9f6d332,AvailabilityZone: us-east-1b,State: available,CreateTime: Tue Aug 30 19:01:00 UTC 2016,Attachments: [],Tags: [],VolumeType: gp2,Iops: 100,Encrypted: false,}

14:01:00
2016-08-30 19:01:16.541 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:
2016-08-30 19:01:16.541 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:01:16.542 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 0
2016-08-30 19:01:16.542 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 0

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 81a44d4e-c5b5-4bae-a5fc-e87207b272ee
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 81a44d4e-c5b5-4bae-a5fc-e87207b272ee)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1383) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:902) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:607) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:376) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:338) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:287) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11132) ~[aws-java-sdk-ec2-1.10.60.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.attachVolume(AmazonEC2Client.java:842) ~[aws-java-sdk-ec2-1.10.60.jar:?]
at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_101]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.1.RELEASE.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sungardas.enhancedsnapshots.components.RetryInterceptor.invoke(RetryInterceptor.java:34) [RetryInterceptor.class:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) [spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sun.proxy.$Proxy63.attachVolume(Unknown Source) [?:?]
at com.sungardas.enhancedsnapshots.service.impl.AWSCommunicationServiceImpl.attachVolume(AWSCommunicationServiceImpl.java:291) [AWSCommunicationServiceImpl.class:?]
at com.sungardas.enhancedsnapshots.tasks.executors.AWSBackupVolumeTaskExecutor.createAndAttachBackupVolume(AWSBackupVolumeTaskExecutor.java:290) [AWSBackupVolumeTaskExecutor.class:?]
at com.sungardas.enhancedsnapshots.tasks.executors.AWSBackupVolumeTaskExecutor.execute(AWSBackupVolumeTaskExecutor.java:92) [AWSBackupVolumeTaskExecutor.class:?]
at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:114) [WorkersDispatcher$TaskWorker.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]

14:01:00
2016-08-30 19:01:46.741 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:01:46.741 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 1

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: cc77e057-ab43-4abe-8900-2e68529662e2

14:01:00
2016-08-30 19:02:16.933 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:02:16.933 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 2

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 25ebbad9-28bc-4a3e-9f6d-869c25a939ac

14:01:00
2016-08-30 19:02:47.293 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:02:47.293 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 3

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: d0995378-6fe3-4db4-8895-960beed6bad6

14:01:00
2016-08-30 19:03:17.486 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:03:17.486 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 4

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 4bb8d922-81dc-4e05-b8b7-b28dfdbfb1fa

14:01:00
2016-08-30 19:03:48.212 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:03:48.212 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 5

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: d9506765-eda0-4891-8b61-ae511512fd45

14:01:00
2016-08-30 19:04:18.775 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:04:18.775 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 6

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 8245ee74-9a2e-4a18-872c-4b6f4d7e1403

14:01:00
2016-08-30 19:04:48.969 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:04:48.969 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 7

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 002a2eb7-8ec8-4dd7-b3c8-7f3b31e27228

14:01:00
2016-08-30 19:05:19.227 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:05:19.227 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 8

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: d5b14e70-92f1-479d-8acd-c24787d42110

14:01:00
2016-08-30 19:05:49.419 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:05:49.419 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 9

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 733b0042-9123-4faf-8f5e-7908e2436efd

14:01:00
2016-08-30 19:06:19.709 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:06:19.710 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 10

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 8128c9c1-8c7d-4c4c-9ad4-5d8f63f41aa3

14:01:00
2016-08-30 19:06:49.945 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:06:49.945 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 11

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: db417349-f35f-44a2-a2c7-2109420b30e0

14:01:00
2016-08-30 19:07:20.177 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:07:20.178 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 12

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 586cccd6-a479-45ca-9b0e-d8cd0224b04a

14:01:00
2016-08-30 19:07:50.611 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:07:50.611 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 13

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: e0d89773-0b17-4aeb-ab32-2e3dbcfeab32

14:01:00
2016-08-30 19:08:20.829 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:08:20.829 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 14

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 74d8a158-a79e-424a-bf44-f5ce29903ba0

14:01:00
2016-08-30 19:08:51.238 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:08:51.238 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 15

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 090b0259-d3d7-459e-9cf2-a0483bf0a274

14:01:00
2016-08-30 19:09:21.426 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:09:21.426 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 16

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 9ea82f63-335c-4783-9595-68127de260c9

14:01:00
2016-08-30 19:09:51.664 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:09:51.664 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 17

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 4847407e-f577-4cd4-b25c-c1a8dc86f30f

14:01:00
2016-08-30 19:10:21.871 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:10:21.872 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 18

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 6e8360d4-9391-4b4f-ab54-77871b46b2f1

14:01:00
2016-08-30 19:10:52.092 [DEBUG] [pool-2-thread-1] RetryInterceptor - Exception while method invocation:

14:01:00
2016-08-30 19:10:52.092 [DEBUG] [pool-2-thread-1] RetryInterceptor - Amazon service exception, try: 19

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: b88e04a4-1b8e-4e5d-aa16-179790ad87a3

14:01:00
2016-08-30 19:11:22.094 [ERROR] [pool-2-thread-1] AWSBackupVolumeTaskExecutor - Backup process for volume vol-420bd891 failed

14:01:00
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: b88e04a4-1b8e-4e5d-aa16-179790ad87a3
com.amazonaws.AmazonServiceException: The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=f43esaa8ztmypqlmn802ok5o3 for more information about supported instance types, regions, and operating systems. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: b88e04a4-1b8e-4e5d-aa16-179790ad87a3)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1383) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:902) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:607) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:376) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:338) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:287) ~[aws-java-sdk-core-1.10.60.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11132) ~[aws-java-sdk-ec2-1.10.60.jar:?]
at com.amazonaws.services.ec2.AmazonEC2Client.attachVolume(AmazonEC2Client.java:842) ~[aws-java-sdk-ec2-1.10.60.jar:?]
at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_101]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.1.RELEASE.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sungardas.enhancedsnapshots.components.RetryInterceptor.invoke(RetryInterceptor.java:34) ~[RetryInterceptor.class:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) ~[spring-aop-4.1.1.RELEASE.jar:4.1.1.RELEASE]
at com.sun.proxy.$Proxy63.attachVolume(Unknown Source) ~[?:?]
at com.sungardas.enhancedsnapshots.service.impl.AWSCommunicationServiceImpl.attachVolume(AWSCommunicationServiceImpl.java:291) ~[AWSCommunicationServiceImpl.class:?]
at com.sungardas.enhancedsnapshots.tasks.executors.AWSBackupVolumeTaskExecutor.createAndAttachBackupVolume(AWSBackupVolumeTaskExecutor.java:290) ~[AWSBackupVolumeTaskExecutor.class:?]
at com.sungardas.enhancedsnapshots.tasks.executors.AWSBackupVolumeTaskExecutor.execute(AWSBackupVolumeTaskExecutor.java:92) [AWSBackupVolumeTaskExecutor.class:?]
at com.sungardas.enhancedsnapshots.components.WorkersDispatcher$TaskWorker.run(WorkersDispatcher.java:114) [WorkersDispatcher$TaskWorker.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]

14:01:00
2016-08-30 19:11:22.143 [ERROR] [pool-2-thread-1] WorkersDispatcher$TaskWorker - java.lang.NullPointerException
2016-08-30 19:11:22.143 [ERROR] [pool-2-thread-1] WorkersDispatcher$TaskWorker - java.lang.NullPointerException

@rabay108  Any clue on above error..?

@NareshDealer The volume you are backing is created part of the AWS Marketplace launch? Based on your earlier message you had success backing up some volume, is this any different and also for manageability better to separate out issues than running them on the same comment. Consider closing this if the original issues were met and open new issues as needed with specific test cases failing.

Closing the issue and reopening new one as its too long and different issue(maybe).


Correct the kubectl run output.

I have kubectl {Major:"1", Minor:"2"} and it does not display the table, just a
simple message.

PR #244 created with the correct author email.


Please reopen issue #131384 ... Trace/breakpoint trap (core dumped)

Does this issue occur when all extensions are disabled?: No

VS Code Version: OpenSuse 15.2
OS Version: 1.56 and higher

Steps to Reproduce:

Run any version of VS code higher than 1.55 (which works correctly!)
On start, I get this error:
./bin/code: line 53:   344 Trace/breakpoint trap   (core dumped) ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" "$@", Its unclear if this is the same error as #131384 or not, but its similar. The code will not start from a gui icon either.
I have tried many versions, pulled from the Microsoft yum repository for OpenSuSE. I have also tried Chormium versions with the same result. A completely virgin install (ie,delete all code parts, ~/.vscode, and ~/.config/Code) makes no difference. I have tried the "standalone" version from a tgz file as well. The difference between 1.55 and 1.56 seems to be the later is using ELECTRON 12.
I have attached an strace of an attempted run from version "code-stable-x64-1631295096.tar.gz". You can see its some sort of memory allocation issue.  Computer is i7-6700k (4 core Skylake), 32 GB memory, btrfs as root, 2 nVidia GPUs GTX-950 + V100). I have also tried to disable extensions, no gpu, etc.
Also attached is listing of ldd on the code.
code_strace.txt
code_ldd.txt

We have a winner! I had set both memoryuse and vmemoryuse to 31g with the csh limit command (in .cshrc). Pushing vmemoryuse up to 48g in a test shows new versions of code now start and work. This is about as low as it can be. This may explain some other issues I have with electron-based applications (eg, discord). At least discord now tries to start for me, but it still crashes. I expect that is some other issue.
I have spend months on this issue and it was driving me crazy. Its not that I could not live without an update to code, but I was looking for hardware errors, and all sorts of other software issues (eg, memory is failing, disks are failing, cpu + MB is failing, ... there is a tread here).
I would propose the developers put in an explicit test and print a message if code fails to allocate memory, and suggest the fix.

It would be nice if there was a different workaround for this. Ie- a way to run 1.56+ on boxes where ulimit -a != unlimited.

This is a limitation from the runtime to surface the error in these cases, closing as not actionable.

Do you have any further details about this limitation that could help somebody file an appropriate issue to an upstream project?  (e.g. to electron or chromium)

The error in this case happens before the application code gets a chance to execute, so it is upto the runtime to surface allocation errors. You can file a feature request in https://github.com/electron/electron/issues/new/choose with a minimal repro.


Integrate MongoDB

Integrate MongoDB with the project to save image data.
When adding each label or face to model save image matrix into MongoDB with the label. Train new model with that data from the database. And delete the images from a directory.
MongoDB must be a docker container for the initial development.
Database Name: Atom
Collection Name: Faces

Need to analyze the optimal way of saving the image data. Because of documents data size higher than "training_images" data size.


Cursor is not pointing to correct position after scrolling

Testing the sample cursor moving effect in readme, when a page scrolls the previous position saved does not consider the scroll position difference, so event.X and event.Y are not the same when moving again.

@adsonvinicius sorry for the late reply, GitHub decided to not notify me ¯_(ツ)_/¯. Anyway I am unable to replicate your issue since the preview does not have scrolling (the canvas fills the whole viewport). Did you encounter this issue somewhere else?


chore: change the target closed exception public

When we make a call to the playwright when the browser is disconnected, the method may throw the TargetClosedException, but due to the TargetClosedException is marked as internal, it is hard to catch this exception as the user. this is a trivial change to make this possible

We recommend catching PlaywrightException instead and looking at the message if necessary. We don't feel comfortable exposing this exception, since its an internal implementation detail which might change over time (did in the past). Closing by that. Thanks for your understanding!


Ensure serial message printed and proper termination when RTC not found.

3f379ab (PR #166) added connection verification for the PCF8523 and DS1307 matching that of the DS3231. For each RTC, if begin() returns false, the intended behavior is to print a message, "Couldn't find RTC" to an attached serial terminal and then terminate.
This change is a follow-on that corrects two issues which were not seen as long as begin() always returned true, across all RTClib examples:

The method of termination in place was an endless loop: while(1)
However, as pointed out in PR #168, the behavior of such a loop is undefined. (See PR for interesting reading!) The abort() command effectively starts an endless loop, but without any side effects. It also makes clear to new users what the program is doing. H/T to contributor @edgar-bonet for this advice.

The message text "Couldn't find RTC" was not guaranteed to actually print on screen before the processor entered the endless loop.
This has to do with the way serial data is actually buffered and transfered down the line. On some boards, serial data is processed using interrupts. On others, such as the Feather nRF52840 which uses the TinyUSB stack, interrupts are not used at all, and serial processing waits for the CPU to become available. Whatever the case, Serial.flush() allows serial processing to finish before terminating with the endless loop.

An alternate way of handling 1 and 2, recommended by the TinyUSB author, is to enter the endless loop immediately, but call yield() inside to instruct the processor to go ahead and handle any latent requests that come in. This also makes the loop have defined behavior. E.g.:
  if (! rtc.begin()) {
    Serial.println("Couldn't find RTC");
    while (1) {
      yield();  // delay(1) would also suffice
    }
  }

A fuller discussion of termination methods can be viewed in PR #166.

Pretty cool test and verification harness you guys have set up. Is there a way to put branches in my fork through it before submitting a PR?
I read this guide https://learn.adafruit.com/the-well-automated-arduino-library and that helped me check some things over locally, but it looks like this repo is using GitHub actions instead of Travis CI. Any tips or pointers?

it should 'just work' if you have Actions activated for your github account :)

@drak7, @ladyada, thanks! I found the 'Desk of Ladyada GitHub Actions' video shortly after posting here. What perfect timing!
It turns out I needed to add GH_REPO_TOKEN as a "secret" to my fork of this repo in order to make the gh-pages push work. Now I'm looking for some way to set that globally so it applies to any Adafruit repo I fork now or later. If you have any hints, I'd appreciate them.
I used to manage continuous build/test/release for Perforce Software, so CI is near and dear to me. I'm thrilled to see this system you've set up for hardware libraries. Among the many advantages, it's a nice safety net for new contributors like me. 👍

https://github.blog/changelog/2020-05-14-organization-secrets/