PR: Adding a banner at the top of the Readme

This a proof-of-concept that consists in adding a banner at the top of the readme (like Atom did for instance).
I had to change the color of the logo, otherwise it was not looking good on a white background. I tried to use the default Spyder icon with a darker background but it was not looking as good as with a white background.
I'm open to suggestions, so please comment.

For everyone's convenience, you can view how it will look on Github on @jnsebgosselin 's repo here.

Great thanks @CAM-Gerlach 👍. This is good observations. I will try to produce a new version soon.

The slightly awkward look of the acronym CAPS in the full name takes away from the otherwise clean and polished design, IMO. Could you try going full 0,0,0 black with them instead, and/or a (not too heavy) bold?

You shouldn't chew acronyms over. Doing such thing is redundant, looks ugly and may be perceived as condescending.

Sorry, I'm not sure what you mean by this.

Doing such thing is redundant, looks ugly and may be perceived as condescending.

I might not (and in fact didn't) put it in such harsh terms, but as noted that's indeed the basic point I'm making, and why I recommended a much subtler approach if we do want to make clear the origin of the acronym (as it is arguably not necessarily redundant in this case, as it may not be immediately obvious to everyone, especially to the large proportion of non-native English speakers who use Spyder).

I meant do not overexplain it. Just writing the full form is enough, let the reader get the joy of understanding.

as it may not be immediately obvious to everyone

Overall, this is no so important, I believe. I'm quite sure not everybody knows that Python is not a snake and Forntran is an acronym. Spyder itself is quite witty name.

Thanks @CAM-Gerlach and @homocomputeris for the comments and clarifications I agree with everything and I will do the changes very soon... I just need to find a little bit of time to do it and since I felt it was not a priority... but not that I've seen it is used for the website, I'm going to take this a little bit more seriously XD

I meant do not overexplain it. Just writing the full form is enough, let the reader get the joy of understanding.

Fair enough, but I could counter with "Explicit is better than implicit" from the Zen of Python. Honestly think at that point its a matter of preference, so long as it isn't obtrusive either way (as we both agree the current form is).

Forntran is an acronym.

They are the fortunate ones, haha (assuming you mean Fortran, which technically isn't considered an acronym anymore by revisions of the standard newer than 77 and is thus title-cased)

Spyder itself is quite witty name.

Eh, not sure about "witty", but it has its moments...

Removed the CAPS in the name and the full form.
Made the dark gray a tad darker (48, 48, 48)
Removed padding on the left
Removed the copyright notice

I really like it!
@CAM-Gerlach, @homocomputeris?

Looks good to me! Awesome job, @jnsebgosselin

Isn't Python a proper name?

@jnsebgosselin Great work!
Just a couple of things.
Correct me if I'm wrong, but I believe the font used here is Candara, which is a resisted Microsoft font and can't be used without installing Office. This isn't a problem for a png but it didn't work well as a svg splash (see  #5667). In #5706 I redid the splash svg using Quattrocento Sans.  I don't think it is quite as stylized but should be easier to use in websites and other branding without worrying about availability.
I see that this is heading also on the website but it's a bit low res. Could it be an svg for both?
Also I see that "spyder" instead of "SPYDER" is used on the software splash. It doesn't matter to me but consistency is nice.

However, we can't just capitalize it and nothing else

Well, "the" is capitalized. I don't even know what distracts more: bad kerning or grammatical errors.
It can just be simplified by making the name bigger. And I've always wondered why the Ssnake doesn't make an ss

@bcolsen I can convert the text to path. Any objection about that?
@bcolsen @CAM-Gerlach I think the name written as "Spyder" looks more professional. I think the Splash should be corrected. Seems like we write "Spyder" everywhere but in the Splash.  I don't like "SPYDER" written all in caps.

Well, "the" is capitalized.

Yes, but it begins the phrase and looks much less objectionable besides, as it is the very first character, not smack dab in the middle; as such, it only minimally distracts and look awkward, unlike capitalizing the P.

I don't even know what distracts more: bad kerning or grammatical errors.

I'm afraid I don't see where anyone in this conversation brought up an issue up with either, nor is either present in @jnsebgosselin 's version. If you're referring to the above mockup, then this would make more sense, as for example the kerning is quite overly large between the d and the e of the Spyder name, and "Scientific Python development environment" does not read well grammatically (capitalization awkwardness aside), nor is it the proper full name of the our program (that being "The Scientific Python Development Environment."

It can just be simplified by making the name bigger

Oh, do you mean the tracking? Yes, the above version is better in that sense, but at the cost of making the name obnoxiously and overwhelmingly large and overstated, not to mention disrupting the balance between the logo and the text, making the line weights less cohesive, and eliminating the horizontal rule giving it a bit of understated polish.
A much better, IMO solution if others agree the large amount of tracking in the name is a problem (I usually prefer less, but in this case contextually it could be justified since its technically an acronym and doesn't feel entirely out of place and thus have no strong opinion) is to make the logo a little smaller, reduce the tracking in place, extend the horizontal rule to the left (shortening it to the right as proper) and align the text underneath both rather than just the name.  But I'm not sure that's necessary.

And I've always wondered why the Ssnake doesn't make an ss

Because you rotated our logo...

@homocomputeris

Well, "the" is capitalized.

Yes, but it begins the phrase and looks much less objectionable besides, as it is the very first character, not smack dab in the middle; as such, it only minimally distracts and look awkward, unlike capitalizing the P.

I don't even know what distracts more: bad kerning or grammatical errors.

I'm afraid I don't see where anyone in this conversation brought up an issue up with either, nor is either present in @jnsebgosselin 's version. If you're referring to the above mockup, then this would make more sense, as for example the kerning is quite overly large between the d and the e of the Spyder name, and "Scientific Python development environment" does not read well grammatically (capitalization awkwardness aside), nor is it the proper full name of the our program (that being "The Scientific Python Development Environment."

It can just be simplified by making the name bigger

Oh, do you mean the tracking? Yes, the above version is better in that sense, but at the cost of making the name obnoxiously and overwhelmingly large and overstated, not to mention disrupting the balance between the logo and the text, making the line weights less cohesive, and eliminating the horizontal rule giving it a bit of understated polish.
A much better, IMO solution if others agree the large amount of tracking in the name is a problem (I usually prefer less, but in this case contextually it could be justified since its technically an acronym and doesn't feel entirely out of place and thus have no strong opinion) is to make the logo a little smaller, reduce the tracking in place, extend the horizontal rule to the left (shortening it to the right as proper) and align the text underneath both rather than just the name.  But I'm not sure that's necessary.

And I've always wondered why the Ssnake doesn't make an ss

Because you rotated our logo...

@jnsebgosselin Right. Lowercase is definitely out for this context as I opined above, and ALL CAPS can be overstated and hard to keep consistent, so then it seems the only thing that makes sense is to change the splash. Furthermore, it would fit with the refined feel of your design overall, which feels very coherent.

Oh, do you mean the tracking?

Yup, my bad.

obnoxiously and overwhelmingly large and overstated, not to mention disrupting the balance between the logo and the text, making the line weights less cohesive

That's a mock-up. The font style may be lighter or font family may be different.

and eliminating the horizontal rule

I believe, most 'logo - text' layouts don't use the rule, which is in accordance with Tufte's data/ink principle.

t could be justified since its technically an acronym

Actually, using some nice font with small caps can be a solution for both 'problems'. SC allow tracking, writing acronyms, they are compact and look 'professional'.

Some alternate versions that addresses more or less all of your comments.

That's a mock-up. The font style may be lighter or font family may be different.

Understood, but even in a lighter weight, the physical dimensions are still rather domineering, IMO. Further, as I discuss above, I'm not sure what real problem is with the original that this one solves, other than the relatively minor issue with the tracking, in comparison with the noted advantages of @jnsebgosselin 's version (mockup issues aside).

I believe, most 'logo - text' layouts don't use the rule, which is in accordance with Tufte's data/ink principle.

Tufte's principles, while certainly well and good, are explicated designed for data visualization. Just like with statistical models, applying them blindly to every situation without considering the different context and constraints is not necessarily a wise idea. In any case, this is a banner for a readme, not a logotype.

Actually, using some nice font with small caps can be a solution for both 'problems'. SC allow tracking, writing acronyms, they are compact and look 'professional'.

Again, I'm not sure what two "problems" you are speaking of. I'm guessing you're referring to what you suggest is excessive tracking on the Spyder name, but its not obvious what the other is. To quote the Zen of Python, "Explicit is better than implicit", and on quite a few of the points in this thread I'll admit to being quite unclear what exactly is being implicitly referring to. The same caries over to the above mockup—there are a number of changes apparently without direct relation to the initial points being made, and no clear explanation/rationale for making them as would be expected.
Although I'm (probably too partial) to small caps generally, I don't see it fitting with the refined aesthetic @jnsebgosselin has cultivated here without changing the whole design language, and in general they can look quite overcooked and pretentious if not used appropriately. As you yourself stated, emphasizing the acronym can come across as rather redundant, etc., and really isn't necessary.
In any case, for the record, here's a quite mockup to illustrate what I was proposing assuming we decide to treat the amount of tracking as an actual problem, but I'm not sure I really prefer it to @jnsebgosselin 's, though certainly to the above.

Wow, thanks @jnsebgosselin . I take back what I said previously—I actually don't mind small caps in that font; its very different from how its often handles in the families I was used to.
On the other hand, I am not so much a fan of sticking the IDE in there; Spyder stands much stronger on its own from a textual standpoint, the extra whitespace isn't that bad, and the IDE being CAPS makes it visually unbalanced towards the right, when you actually want to draw the eye to the left (the name Spyder should have visual primacy over it being an IDE). I
Its also not too bad without the rule with the small caps, though for this purpose, a readme top banner, I still think I prefer it with; for e.g. a website top banner it would probably looke better without IMO. As previously mentioned, really don't like cap'ing Python and nothing else in the subhead. Therefore, my rankings are (all in order by vertical position, but -- signalling larger breaks between the groups).
#2
#6
#1 with all Title Case or lower case subhead
#0 (Orginal)
#5
#3 and #4 (appear identical to me)

@CAM-Gerlach Nice one. I think I like the logo flat better, but I like a lot the fact the the lines of the spider web are thicker though... But except for the colors, I am reluctant to change the logo in this PR...
I think I had almost this design at some point, but I changed it because I wanted to increase the horizontal over vertical ratio for the banner. I wanted the banner to span the entire width of the readme without taking too much vertical space. But this is probably not necessary anymore ... so well I don't know... I'm going to sleep on that and look at it again tomorrow.

@CAM-Gerlach Thanks for the feedback, it is much appreciated ! The second one is also the one I prefer and I agree with the rationale you've given about the "IDE" part. Also, for the line, I don't know... It probably depends where it is used like you said, but I think I still prefer with the line.
Also, yeah 3 and 4 are identical... I probably had something in mind but forgot to do it lol I'll remove the number 4 so that others do not waste time trying to find the difference.
PS: I think you should edit your last post because you've now referenced this PR in a lot of very old issues ahah

@jnsebgosselin See my nearly simultaneous comment; in terms of general layout and look I like at least the upper half, if not two thirds of your versions better; I was just trying to illustrate what I was proposing though by that point I wasn't too convinced of it.

I think I like the logo flat better, but I like a lot the fact the the lines of the spider web are thicker though.. .But except for the colors, I am reluctant to change the logo in this PR...

The particular logo I used is a total accident, just pulled from another mockup I made for the website. However, it is the real logo, pulled right from the repo and is the one visible in e.g. the About Spyder dialog; I didn't thicken the lines at all. The only changes I made were in fact to the color of the lines, making them just a little darker so they weren't invisible), and adding the light drop shadow you mentioned for the same reason. Now that I compare them, I agree with what you're saying: not 100% sure on the drop shadow but the thickness is definitely better, giving it a lot more punch and making it look more solid, and I actually prefer the dark grey center color and lighter lines overall as it just looks more pleasing. However, without the drop shadow, it doesn't really show up too well on a white BG.
I'd suggest at least switching to the wider-line version only with your colors, or perhaps more ideally with a the normal colors with off-white vs. white for visibility, if either you think the drop shadow is worth it or you can find another way to retain enough color contrast. In fact, I might suggest at some point making at least the slightly off white web the official color (in another PR), since it is actually invisible on the About dialog and other parts of the UI, at least without a dark theme.

@jnsebgosselin

PS: I think you should edit your last post because you've now referenced this PR in a lot of very old issues ahah

I noticed it as soon as I submitted my post and had it edited and saved within a few seconds, so you must have caught me at just the wrong time haha. Do I need to completely delete my post to get rid of it, or does just editing fix it?

Do I need to completely delete my post to get rid of it, or does just editing fix it?

I don't know sorry. It is still referenced in issue number 2 (with a few other non related issues as well hehe), but it may take a little bit of time before it is cleaned up?

I'd suggest at least switching to the wider-line version only with your colors

Ok, here is a revised version of the version number 2 with the proper line thickness on the logo. The line were not correct because I messed up when I scaled the logo dimension at some point. Thanks for pointing it out to me.

I'd suggest at least switching to the wider-line version only with your colors, or perhaps more ideally with a the normal colors with off-white vs. white for visibility, if either you think the drop shadow is worth it or you can find another way to retain enough color contrast. In fact, I might suggest at some point making at least the slightly off white web the official color (in another PR), since it is actually invisible on the About dialog and other parts of the UI, at least without a dark theme.

I don't know about the shadow. I would really prefer to keep it flat and I kind of like the idea of having a dark and light version of our logo. But if the majority is for keeping only one version with the standard colors and adding a shadow, I'll go for it for sure.
But yeah I agree with you the actual logo doesn't look so good without a dark theme. See the screenshot of how it looks for me in windows... not very good at all...

Repost:
Wow, thanks @jnsebgosselin . I take back what I said previously—I actually don't mind small caps in that font; its very different from how its often handles in the families I was used to.
On the other hand, I am not so much a fan of sticking the IDE in there; Spyder stands much stronger on its own from a textual standpoint, the extra whitespace isn't that bad, and the IDE being CAPS makes it visually unbalanced towards the right, when you actually want to draw the eye to the left (the name Spyder should have visual primacy over it being an IDE). I
Its also not too bad without the rule with the small caps, though for this purpose, a readme top banner, I still think I prefer it with; for e.g. a website top banner it would probably looke better without IMO. As previously mentioned, really don't like cap'ing Python and nothing else in the subhead. Therefore, my rankings are (all in order by vertical position, but -- signalling larger breaks between the groups).
# 2
# 6
--
# 1 with all Title Case or lower case subhead
# 0 (Orginal)
--
# 5
# 3 and # 4 (appear identical to me)

@jnsebgosselin

I don't know sorry. It is still referenced in issue number 2 (with a few other non related issues as well hehe), but it may take a little bit of time before it is cleaned up?

Hmm, I deleted and reposted. Hopefully that fixed it...

I don't know about the shadow. I would really prefer to keep it flat and I kind of like the idea of having a dark and light version of our logo.

Yeah, as mentioned I'm not super partial to it either if its not necessary; I just happened to have it on there from before since I didn't have your revised  version of the logo handy. Though I somewhat prefer the original version's colors all else equal, now that I can see your version rendered with the proper line widths I agree that the difference isn't worth the drop shadow since the latter really takes away from the clean design aesthetic, and we certainly should have the two versions of the logo.
Maybe substitute them in the UI depending on the theme, as part of that implementation? As a stopgap for the present, making the web off white rather than pure white would at least make it visible. But I'm getting a bit off  topic...

@jnsebgosselin Great job. I like the 6th.
@CAM-Gerlach The subtitle is quite long and dense itself, so doesn't seem necessary to me. Maybe a lighter or thinner line would be better?
Putting the subtitle below the logo looks fine too.

Thanks @CAM-Gerlach and @homocomputeris for your feedback. So far, below are the final contestant in dark and light versions.

The dark version definitely looks cool, but the problem is that with a very different BG than the rest of the readme, it would look out of place, rather than the seamlessly integrated white/transparent BG versions. Also, some of the kick of the nice dark grey in the logo was in its contrast with the white BG. Therefore, my recommendation stands: # 2 preferred over # 6 .
Also, I can't remember if I noted this before (may have forgotten), but I'd suggest shrink the logo a little since it is a little overpowering and unbalanced now that you've thickened the lines.

Also, I can't remember if I noted this before (may have forgotten), but I'd suggest shrink the logo a little since it is a little overpowering and unbalanced now that you've thickened the lines.

@CAM-Gerlach Good observation. Below are some versions addressing your comment above with and without the construction lines I used to produce the original design. Personally, I prefer 2b.

@jnsebgosselin Nice, thanks. I'm torn between 2b and 2c; I think I might slightly lean toward 2b as well but I'd have to see them in the readme to really call it.

@bcolsen good idea, I like that. I'm going to open a new issue where we can discuss various improvements that could be done on our logo more specifically. I think our logo could use a little revamping. @ccordoba12 what do you think?

@bcolsen I tried throwing a stroke on there as well, with a few different combinations, but couldn't get it to look all that great. The above is certainly better than my attempts, but I'm not sure I prefer it to what we have. Maybe with a thinner stroke, or doing something else a little different with it? Not sure.

Closing this since this is going to be solved when we get the new logo design from a professional designer as decided in #6509.

@jnsebgosselin, thanks a lot for your work on this! We're going to use one of draws in your last sketch to replace the current banner in the website.


Upgrade to Vaadin 18.0.5

vertical-menu seems broken when you open it, navigate away and navigate back, you get cannot read querySelector of 'null'

vertical-menu seems broken when you open it, navigate away and navigate back, you get cannot read querySelector of 'null'

Changed to 18.0.5 which fixes the grid problems

Changed to 18.0.5 which fixes the grid problems

Closing as obsolete as @alvarezguille did upgrade this to latest already.


removing desc height restrictions from project

Porject description heght was restricted to 80px which was causing tags to overlap on description
Fixes Issue
closes #217

Changes proposed
updating project description height from 80-px to fit-content
Note to reviewers

Screenshots

Hi @rupali-codes could you fix the build issue. Thanks

I'm not able to get details page, lemme try commiting again

I'm not able to get details page, lemme try commiting again

please try building the code at local machine. you'll get the error details.

Any updates?

I'm unable to set up project,


Add way to get configurations

When generating CMD for new bug button I try to generate for each value in special_categories from details
special_categories are defined in config it seems
It is incorrect but I have no way to do it properly
We should add new key to details like configurations or something so we can generate CMD for configurations without generating CMD for values like TS_SET etc...
should probably add to run details endpoint?
Related to https://github.com/ts-factory/bublik-ui/issues/174

Configurations are available under the Configuration key in special_categories.


Added SmartGPT workflow (issue #4463)

Added SmartGPT workflow by providing SmartLLM wrapper around LLMs
Edit:
As @hwchase17 suggested, this should be a chain, not an LLM. I have adapted the PR.
It is used like this:
from langchain.prompts import PromptTemplate
from langchain.chains import SmartLLMChain
from langchain.chat_models import ChatOpenAI

hard_question = "I have a 12 liter jug and a 6 liter jug. I want to measure 6 liters. How do I do it?"
hard_question_prompt = PromptTemplate.from_template(hard_question)

llm = ChatOpenAI(model_name="gpt-4")
prompt = PromptTemplate.from_template(hard_question)
chain = SmartLLMChain(llm=llm, prompt=prompt, verbose=True)

chain.run({})

Original text:
Added SmartLLM wrapper around LLMs to allow for SmartGPT workflow (as in https://youtu.be/wVzuvf9D9BU). SmartLLM can be used wherever LLM can be used. E.g:
smart_llm = SmartLLM(llm=OpenAI())
smart_llm("What would be a good company name for a company that makes colorful socks?")

or
smart_llm = SmartLLM(llm=OpenAI())
prompt = PromptTemplate(
    input_variables=["product"],
    template="What is a good name for a company that makes {product}?",
)
chain = LLMChain(llm=smart_llm, prompt=prompt)
chain.run("colorful socks")

SmartGPT consists of 3 steps:

Ideate - generate n possible solutions ("ideas") to user prompt
Critique - find flaws in every idea & select best one
Resolve - improve upon best idea & return it

Fixes #4463
Who can review?
Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested:

@hwchase17
@agola11

Twitter: @UmerHAdil | Discord: RicChilligerDude#7589

Agreed - will change

Requires https://github.com/hwchase17/langchain/pull/5030 to be merged. Will re-request review, when it's merged.

Hey @hwchase17 any more comments?

Nice work! 😃

Hi @hinthornw! Also pinging you here, as you're the maintainer for Agents :) Any feedback?

@UmerHA do you think this could be used for a pandas/xorbits agent? To break down complex questions before answering

Sure, why not. This is a general approach and should improve any task (at the cost of more token usage).

@UmerHA do you think this could be used for a pandas/xorbits agent? To break down complex questions before answering

Sure, why not. This is a general approach and should improve any task (at the cost of more token usage).

Interesting thanks. Must look into using this as an agent with tools!

apologies for the delay in reviewing, this is very cool! thank you @UmerHA!!


Improve error message for failed to connect

Add more info to the error message when crictl fails to connect
to the runtime either due to permissions or the runtime not being
started.
Signed-off-by: Urvashi Mohnani<EMAIL_ADDRESS>

@mrunalp PTAL


add http://stellereum.com/ as an ethereum anchor

Turned out to be a scam. Good thing I didn't add it


Support Oryx 10GigE camera

This adds support for an Oryx 10GigE (ORX-10GS-51S5M-C) camera.
The underlying implementation is shared with the previously support Blackfly camera. The advantage of this approach is that there is less code to maintain and supporting other Spinnaker based cameras could be little to no work.
The disadvantage of this approach is that the implementation related to triggers is complicated. Alternatively, we could consider completely splitting at least part of the implementation and using different parts of it explicitly based on the camera model.
This also adds tests for the Oryx camera that mirror those for the Blackfly. A test for Camera::get_meta was also added for both cameras. I also added a ctest setup fixture to ensure that the packet size is set to 1000B for the Oryx camera.
Closes #3

All tests are passing locally, but only the Blackfly tests are passing on CI as there is no Oryx camera connected to a runner right now.

Both cameras are connceted to Ghanima and I added a setup fixture to force the packet size to be 1000B. All tests pass, except the first blackfly specific test, which has failed twice in a row with a similar error that likely occurs when initializing the camera. The latest error is the following.
 Exception: Spinnaker: Error reading from Device [SN:23077028], at register address: F0F01120. Please try reconnecting the device. [-1011]

Note that all subsequent blackly tests pass and all oryx tests pass.
I don't believe I've seen this in previous runs, so it's possible that the fixture is causing it somehow.

Thanks for the reviews!


Post Balena Name to Backend

We currently have no connection of the chip-serial, pubkey in the backend. This could become a problem as more devices are added into our fleet - i.e. dead reflashed devices that should be purged.
I propose posting this information into our backend. Possibly it could be handled via bash - or a small service of its own. A bit sceptical to add it to the server as we have kept it free of balena stuff so far.

This should not be responsibility of the gateway, we let dashboard handle this


Any detail docs describe how we can use result or stdout in workflow as reference

Dear support,
Not sure if this is correct or possible way (maybe the current action_execution_id is not known to workflow?), sometimes, the python script might want to know the action execution id as its input parameters.
for instance, below action need current action_execution_id as its input parameter, can I know how to write the reference, like {{result.id}} or {{result.stdout.id}} or {{action_context.id}}?, I noticed the code part for each action from webui, but just don't know the exactly format to invoke in workflow definition file.
      t_observation:
          action: libery.manual_action
          input:
              execution_id: {{}}
              pool_id: <% $.pool_id %>
              pool_info: <% $.pool_info %>
              assigned_group: <% $.assigned_group %>
              assignee: <% $.assigne %>
              time_out: <% $.time_out %>
          publish:

BR,
Leo

@leoxhj
https://docs.stackstorm.com/mistral_yaql.html#other-yaql-functions
<% env().st2_execution_id %>
Please re-open issue if this isn't what you're looking for.

I'm not quite sure why you want to access the execution id, but you can get it using st2_execution_id - go to https://docs.stackstorm.com/mistral_yaql.html and search for execution_id
I'm not quite sure what you need it for though. What are you trying to achieve here?

It will pass to external tool as reference id to find back in stackstorm if needed.
-------- 原始信息 --------
由： Lindsay Hill<EMAIL_ADDRESS>日期: 2017/6/29 10:07 (GMT+08:00)
收件人： StackStorm/st2<EMAIL_ADDRESS>抄送： leoxhj<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>主题： Re: [StackStorm/st2] Any detail docs describe how we can use result or stdout in workflow as reference (#3517)
I'm not quite sure why you want to access the execution id, but you can get it using st2_execution_id - go to https://docs.stackstorm.com/mistral_yaql.html and search for execution_id
I'm not quite sure what you need it for though. What are you trying to achieve here?
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/StackStorm/st2/issues/3517#issuecomment-311842083, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADHy2UdnpjQ-cq27C5FvMib2XhbsHwcWks5sIwb3gaJpZM4OE8NX.

I have an Ansible action in the st2 mistral workflow and would like to post the action output into chatop.post_result action. To post the action result in chatops_post_result it required execution id. Would there be possible to get the execution id for the ansible action and assign that execution id into chatops.post_result action?
I've tried to use <% env().st2_execution_id %> with chatops.post_message however it returns the workflow execution id rather than the particular action ID.
example:
post_chat_fail:
# [625, 536]
action: chatops.post_message
input:
channel: <% $.channel %>
message: "Auto-remediation failed for <% env().st2_execution_id %>"

Have you tried
<% env().st2_action_execution_id %>?
Just my guess, docs mentioned less details about environment()
发送自我的三星盖乐世智能手机。
-------- 原始信息 --------
由： sibirajal<EMAIL_ADDRESS>日期: 2017/7/5 19:52 (GMT+08:00)
收件人： StackStorm/st2<EMAIL_ADDRESS>抄送： leoxhj<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>主题： Re: [StackStorm/st2] Any detail docs describe how we can use result or stdout in workflow as reference (#3517)
I have an Ansible action in the st2 mistral workflow and would like to post the action output into chatop.post_result action. To post the action result in chatops_post_result it required execution id. Would there be possible to get the execution id for the ansible action and assign that execution id into chatops.post_result action?
I've tried to use <% env().st2_execution_id %> with chatops.post_message however it returns the workflow execution id rather than the particular action ID.
example:
post_chat_fail:
[625, 536]
action: chatops.post_message
input:
channel: <% $.channel %>
message: "Auto-remediation failed for <% env().st2_execution_id %>"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/StackStorm/st2/issues/3517#issuecomment-313081192, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADHy2d2DZynln9sRKAS4C6bRUHPOwy8hks5sK3kNgaJpZM4OE8NX.

That's right. I've tried <% env().st2_action_execution_id %> in my workflow and it failed with error. Basically I would like to get the execution id of the particular action and use that id for chatops.post_result action.
YaqlEvaluationException: Can not evaluate YAQL expression [expression=env().st2_action_execution_id, error=u'st2_action_execution_id', data={}]
] (execution_id=4768477e-b748-4f54-893a-47f2cd479317): YaqlEvaluationException: Can not evaluate YAQL expression [expression=env().st2_action_execution_id, error=u'st2_action_execution_id', data={}]


MM-New-Task-Admin-App - Sprint 2

Description:

Build the Screen using the style guide.
Integrate Screen with the Backend

hello @Honeyloveet , I'll like to work on this task. Kindly assign it to me. Thank you

@tamsay you can work on this issue


Can't attach library sources

Library Version [tried with  v1.4.5, v1.4.6]
Affected Device(s) [any]
AndroidStudio - both ArcticFox and Bumblebee

Hi! Thank you for this library!
Unfortunately I faced a problem: I can't see library source code when add it as Gradle dependency, only as decompiled .class file.

When I press a "Download sources" button it fails with an error:
FAILURE: Build failed with an exception.

* Where:
Initialization script '/private/var/folders/z7/kjbg12m17p7b2m8n48fwm3zc0000gp/T/ijmiscinit2.gradle' line: 25

* What went wrong:
Execution failed for task ':game:impl:DownloadSources'.
> Could not resolve all files for configuration ':game:impl:downloadSources_42d1e64e-d610-4315-8794-5307186c49f6'.
   > Could not find com.github.skydoves:landscapist-glide:1.4.6@aar.
     Required by:
         project :game:impl

I tried to download sources manually and then attach them, but I looks like your -sources.jar file (in both 1.4.5 and the newest 1.4.8) is empty.
May it be any issue with your publishing script, or am I doing something wrong?

Hi @rychagovDi,
This is not a library issue, maybe you should report this gradle.
It seems your Gradle setup does not catch the jar source of your dependencies.


WebGPU: Fix viewport reset too often

See https://forum.babylonjs.com/t/webgpu-rendertargettexture-take-the-last-cameras-active/40473

Snapshot stored with reference name:
refs/pull/13816/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13816/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13816/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13816/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13816/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13816/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13816/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13816/merge#BCU1XR#0


feat(CLI): add debug command

WIP - Needs tests
Closes https://github.com/prisma/prisma/issues/21619
Example view from my terminal

Not ready to be merged, but review/feedback is welcome.


chore: Allow to configure resources for the post-install-hook pod

Description
This allows to define the postInstallHook resources so policies on our cluster can be met that require us to define resources for any container.
Does this change impact docs?

[x] Yes, PR includes docs updates

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

Closing as the post install hooks have been removed


Expand and Collapse on branches, messages, and fragments

Scope
Viewing Only
Out of scope
Persisting toggles
Context
When viewing a Sequence Diagram, sometimes, some details (be it messages, fragments or branches) become distractions. Users may want to temporarily hide it.
Design
The meaning of "hide" is important. We need to carefully design the hidden section so it does not continue distracting users' attention but still providing some indicator (and maybe some information) on what is going on there. A few example's must be provided.
Branches
Messages
Fragments
Related Issues
Feature request: toggle branch of code

What is the proper place to put the "Expand/Collapse" Button?
We may be able to incorporate this in the "context menu"? Maybe not. While styling sounds a good choice for context menu. Expand/Collapse buttons do not. This is because we want the interaction points to be more accessible and with less clicks. Another issue with context menu is that it would be difficult for users to know "what element to select". For example, how to select an "Alt fragment" vs an "Else branch"?
It seems that the button should be at a fixed position relative to the collapsable element.
For Fragments (Alt, Loop, Par, Opt, TCF), we can use the "Header".


Provide graph view over GCIs

From<EMAIL_ADDRESS>on January 24, 2013 17:15:48
OWLGraphView provides a graph view of an ontology, with edges formed by axioms such as
X SubClassOf R Some Y
==>
<X R Y>
Ontologies such as Uberon have taxon-specific relationships which have OWL semantics
(X and part_of some Taxon) SubClassOf R some Y
these are "invisible" in the graph view, as the subject is not a named class.
Some options:

Add something to materialize the class expressions on the LHS. In the above you would get a graph

{{{
Taxon    X
^     /
|    /
[p] [i]
|  /
NewClass---[R]-->Y
}}}

Fold the GCI conditions into the edge label. E.g.
X---[R,Taxon]---->Y

This is potentially dangerous, so it would be done only if the API user asks for this.
Any other options?
[Reported by Frederic Bastian]
Original issue: http://code.google.com/p/owltools/issues/detail?id=45

From<EMAIL_ADDRESS>on January 30, 2013 16:32:41
Note: should be possible to use uberon as example:
Query:
how does the lineage of the paraythroid gland vary across species?
Answer:
dorsal part of pouch 3+4 (mammals)
ventral part of pouch 3-4 (aves)
(need to check these are present in the ontology)

From<EMAIL_ADDRESS>on January 30, 2013 16:42:08
Just a note here to keep things in one place: the manually curated GCIs are missing from uberon/composite-* ontologies.
This isn't an owltools problem, but if we switch to owltools to generate the auto-GCIs the problem should go away

From<EMAIL_ADDRESS>on May 02, 2013 13:29:51
SpeciesMergeUtil now being used, fixes GCI issue

From<EMAIL_ADDRESS>on November 28, 2014 05:49:27
Solution 2 has been implemented, see issue #102 . OWLGraphEdge now has gci_relation and gci_filler attributes. OWLGraphWrapperEdgesExtended implements many methods reproducing behavior of OWLGraphWrapperEdges methods, but taking into account GCI relations. The ticket might be closed.


Let's talk about circt/node

Please propose new repos on the circt discourse forum before creating them.  I think this should be in the main circt repo for a variety of reasons.
Also, shouldn't we close the circt organization entirely?  @stephenneuendorffer what are your thoughts here?

@drom

Here is a discussion in the MLIR discourse https://llvm.discourse.group/t/nodejs-bindings

Once POC is working, I OK merging it into CIRCT or MLIR main repo.

Also, shouldn't we close the circt organization entirely? @stephenneuendorffer what are your thoughts here?

The only thing of value right now is the LLVM staging branch, which I suspect will be useful from time to time.  Keeping it seems to have little cost.

I'd prefer to have fewer load bearing repos that work together.  Keeping one for the llvm fork make a lot of sense.


Added plugin-docker-compose-build-step.yml

Description

Grant @JGalego permission to deploy docker-compose-build-step
https://github.com/jenkinsci/docker-compose-build-step-plugin
https://issues.jenkins-ci.org/browse/HOSTING-590
Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Build failed; the context from the latest run is:
Expand to view
First time build. Skipping changelog.
[Pipeline] properties
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor on java
Running on ubuntu-jenkinsinfrac7ea71 in /home/jenkins/workspace/-permissions-updater_PR-776-VOU2FGAXNHBN7MQ47DZJU2YER35QZ4D3HW44A4K3ZX4JPGV2IGRQ
[Pipeline] {
[Pipeline] stage (Clean)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Clean
Proceeding
[Pipeline] deleteDir
[Pipeline] sh
[-permissions-updater_PR-776-VOU2FGAXNHBN7MQ47DZJU2YER35QZ4D3HW44A4K3ZX4JPGV2IGRQ] Running shell script
+ ls -lah
total 8.0K
drwxrwxr-x 2 jenkins jenkins 4.0K Jul 11 21:33 .
drwxrwxr-x 5 jenkins jenkins 4.0K Jul 11 21:33 ..
[Pipeline] stage (Checkout)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Checkout
Proceeding
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
remote: Counting objects
remote: Compressing objects
Receiving objects
Resolving deltas
Updating references
Fetching without tags
Merging remotes/origin/master commit 459ba262f278b8c8b07568184e05528cad68606f into PR head commit a46aca83ee31d8ffc6c1dfdc209623ce74bcc52c
[Pipeline] stage (Archive)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Archive
Proceeding
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] archiveArtifacts
Archiving artifacts
‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
Finished: FAILURE

Powered by the Comment Logger

Build failed; the context from the latest run is:
Expand to view
Entering stage Run
Proceeding
[Pipeline] sh
[-permissions-updater_PR-776-VOU2FGAXNHBN7MQ47DZJU2YER35QZ4D3HW44A4K3ZX4JPGV2IGRQ] Running shell script
+ /home/jenkins/tools/hudson.model.JDK/jdk8/bin/java -DdryRun=true -DdefinitionsDir=/home/jenkins/workspace/-permissions-updater_PR-776-VOU2FGAXNHBN7MQ47DZJU2YER35QZ4D3HW44A4K3ZX4JPGV2IGRQ/permissions -DartifactoryApiTempDir=/home/jenkins/workspace/-permissions-updater_PR-776-VOU2FGAXNHBN7MQ47DZJU2YER35QZ4D3HW44A4K3ZX4JPGV2IGRQ/json -DartifactoryUserNamesJsonListUrl=http://reports.jenkins.io/reports/artifactory-ldap-users-report.json -Djava.util.logging.SimpleFormatter.format=%1-%1-%1 %1:%1:%1 %4: %5%6%n -jar target/repository-permissions-updater-1.0-SNAPSHOT-bin/repository-permissions-updater-1.0-SNAPSHOT.jar
Running in dry run mode
Exception in thread "main" groovy.json.JsonException: Unable to process url: http://reports.jenkins.io/reports/artifactory-ldap-users-report.json
	at groovy.json.JsonSlurper.parseURL(JsonSlurper.java:416)
	at groovy.json.JsonSlurper.parse(JsonSlurper.java:379)
	at groovy.json.JsonSlurper$parse.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
	at io.jenkins.infra.repository_permissions_updater.ArtifactoryPermissionsUpdater.generateApiPayloads(ArtifactoryPermissionsUpdater.groovy:125)
	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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
	at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite$StaticMetaMethodSiteNoUnwrapNoCoerce.invoke(StaticMetaMethodSite.java:151)
	at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:102)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:214)
	at io.jenkins.infra.repository_permissions_updater.ArtifactoryPermissionsUpdater.main(ArtifactoryPermissionsUpdater.groovy:317)
Caused by: java.io.FileNotFoundException: http://reports.jenkins.io/reports/artifactory-ldap-users-report.json
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
	at org.codehaus.groovy.runtime.ResourceGroovyMethods.configuredInputStream(ResourceGroovyMethods.java:2021)
	at org.codehaus.groovy.runtime.ResourceGroovyMethods.newReader(ResourceGroovyMethods.java:2070)
	at groovy.json.JsonSlurper.parseURL(JsonSlurper.java:410)
	... 17 more
[Pipeline] stage (Archive)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Archive
Proceeding
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] archiveArtifacts
Archiving artifacts
‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
Finished: FAILURE

Powered by the Comment Logger


Agent's informant server doesn't stop when context is cancelled

Can you provide a bit more background here, and perhaps a link to the service that you'd expect to stop?

Discovered that this is the cause of the goroutine leak we're seeing in prod. Lots and lots of goroutines with net/http.(*Server).Serve(...) in their callstack.


Adding in basic time series API implementation with tests

Part of https://jira.hecdev.net/browse/CWMS-580
Added a single time series retrieval API with tests for a retrieval of 1 month of hourly data, as well as a test for pagination of that data.
Added additional tests if the RADAR API url is not reachable and if the requested time series does not exist. Currently the RADAR API does not handle time series not existing, but should be solved in ticket: https://github.com/USACE/cwms-radar-api/issues/80

I dont have any further review changes for this PR


Add accelerator complex to BP SoC

Minor nits.  Otherwise looks good!

One last thing to add.
To bp_params_p, can you add accelerator type enums?
...
typedef logic [15:0]
{
e_sacc_vdp
} bp_sac_type_e
typedef logic [15:0]
{
e_cacc_vdp
} bp_cacc_type_e
...
sac_x_dim        : 1
sacc_type: e_sac_vdp
..
cac_x_dim         : 1
cacc_type: e_cac_vdp

And then in bp_xacc_tile, do a generate if based on that enum

Code looks good.   "
The following 3-bit expression is connected to 2-bit port "my_cid_i" of
module "bp_me_cce_to_mem_link_master", instance "dma_link".
Expression: (my_cord_i - sac_x_dim_p[0+:mem_noc_cid_width_p])
use +lint=PCWM for more details

@zaazad have you fixed the width mismatch? I think it’s just a matter of parameterization.
Try more configurations (accelerator/non-accelerator multicore / single core) to make sure the formulas aren’t hitting any more edge cases

It should be fixed now.

Hm, I don’t trust that solution. It suppresses the warning, but if cord > cid, then multiple x tiles will alias. The parameter

Ah, I see that's the way it was before.  I'll raise an issue but your fix brings it back to exactly how broken it was before :)

Okay, had to do some git surgery here because there were some bad merges where the diff ended up at 10000+ lines O_o.
Do we need a separate accelerator testbench? It doesn't seem like it's any different than the normal processor testbench?  If not, let's just delete it.
@zaazad

Yeah, we can delete it. Previously we decided to have a separate one and pass some parameters to accelerator complex from there.


Add POST support to WFS GetFeature (Issue #439)

This PR would take care of issues #439 and possibly #683
This is my first contribution to OWSLib and I'm new to the WFS standard, so I expect there might be a few things to change, either towards the standards or to integrate it better with existing code.
I added the ability to use an existing xml filter as is, like suggested in #439, but I think it might be redundant. Either way, it's self contained and only 2 lines of code, so it's easy to remove if need be.
I can already say I'm not sure about how I handled Stored Queries.

I'm not familiar with this part of the code, but the use case for us to send requests to GeoServer that exceed the size of GET requests. For example, we're sometime making queries for properties for thousands of individual features, and the list of features does not fit in GET requests. So we'd be really grateful if this could be reviewed.

test failures not related to this PR.

Just added #711 which this PR should solve

@KorkXx @f-PLT @tomkralidis If the review is ok, can we merge it?

+1

We have an issue with a usecase for one of our partners.
If it can't be handled server-side, we'll probably have a small change to add so it's possible to handle an https redirection, which doesn't seem to work with Post requests.
Right now, considering a simple flag to prevent the GetCapabilities url retrieval when needed, and force the use of the provided WebFeatureService url as is. (for reference : https://github.com/f-PLT/OWSLib/blob/wfs-getfeature-post/owslib/feature/init.py#L312-L320)

Alright, it's definitely a server-side problem so we'll fix it server-side. If there are no other objections after the testing has been done , it should be ok to merge.
As for the problem, here's a summary as it's bound to happen to other people.
Post requests are not redirected. Ever, and should never be. It's in the HTTP standards. (Learn something everyday!)
Therefore if the the Url listed in the GetCapabilities for post getFeature() is http://..., but the server is behind, say, an nginx proxy that redirects http => httpS, the post request will not work and return a very helpful error :
owslib.util.ServiceException: Could not determine geoserver request from http request org.geoserver...

The server needs to be configured to give the proper url. In the case of Geoserver, it should be the Proxy Base Url.
This doesn't happen with Get requests, because a Get can be redirected without any problem.
Hope this little bit of information can help someone someday, and if I'm wrong in any way, please feel free to correct me!

Alright, it's definitely a server-side problem so we'll fix it server-side. If there are no other objections after the testing has been done , it should be ok to merge.

@f-PLT  ok :) Give me a sign ... I can do the merge ...

Our tests have gone well!
Found and corrected a small unintended side effect while we were at it. If those last two commits pass muster, then it's good to go. If we end up finding more bugs, I'll open a new PR.

failing tests are not related to this PR ... they already fail on current master.

@f-PLT merged. Thanks 👍


container/README needs updating.

Fix:

No mention of target module.
service does not create the target group or listeners.
Should mention that NLB's don't work currently, because of bugs in the AWS provider for terraform.

See #46 for more info on NLB's.


AppSyncApi v1 construct doesn't support AWS directives

Discovered it during migration from v0 to v1.
Steps to reproduce:
Create 2 files, e.g. mutations.graphql and queries.graphql. Use any AWS directives such as @aws_iam, @aws_cognito_user_pools, @aws_api_key or scalars such as AWSDate or AWSJSON.
Pass schemas as an array:
new sst.AppSyncApi(this, `AppSyncApi`, {
      schema: [
        'schema/mutations.graphql',
        'schema/queries.graphql',
      ],
}

Run sst build/start/deploy.
Result:
Error: Unknown directive "@aws_iam".

Unknown directive "@aws_cognito_user_pools".

Unknown directive "@aws_api_key".

Unknown type "AWSDateTime".

    at assertValidSDL (/some/path/node_modules/graphql/validation/validate.js:107:11)
    at buildASTSchema (/some/path/node_modules/graphql/utilities/buildASTSchema.js:45:34)
    at buildSchema (/some/path/node_modules/graphql/utilities/buildASTSchema.js:112:10)
    at Array.map (<anonymous>)
    at AppSyncApi.createGraphApi (file:///some/path/node_modules/@serverless-stack/resources/dist/AppSyncApi.js:242:26)
    at new AppSyncApi (file:///some/path/node_modules/@serverless-stack/resources/dist/AppSyncApi.js:48:14)
    at new GraphQlStack (file:///some/path/server/.build/lib/index.js:83:23)
    at Module.main (file:///some/path/server/.build/lib/index.js:533:24)
    at file:///some/path/server/.build/run.mjs:96:22

Problem:
When schema is defined in more than 1 file sst processes them with graphql.buildSchema.
This function doesn't know about AWS directives or scalar types like @aws_iam, @aws_cognito_user_pools, @aws_api_key, AWSDateTime.
Current workaround is to combine all schemas into a single file and defined schema as a string instead of an array in the construct to bypass graphql.buildSchema.

Yes, pretty annoying. Any better workarounds?

The issue here is that if there is one file, the schema file is passed to AppSync for checking. Which is a bit annoying, as you find errors quite late. If you use an array (even with 1 file), it uses some schema merging tool, which validates the result. If you think you can fix this with scalar AWSDateTime, this is something the merge likes, but causes an internal error in appsync when you deploy....

In addition to @smacker's solution, here's how I've solved this right now:
import { print } from "graphql"
import { mergeTypeDefs } from "@graphql-tools/merge"
import { loadFilesSync } from "@graphql-tools/load-files"

export function MyStack({ stack }: StackContext) {

  ...
  // merge schema files
  const schemaTypes = loadFilesSync(path.join('./graphql/types'), { extensions: ['graphql'] })
  const mergedSchema = mergeTypeDefs(schemaTypes)
  const filePath = "./graphql/schema.graphql"
  writeFileSync(filePath, print(mergedSchema));

  const api = new AppSyncApi(stack, "AppSyncApi", {
    schema: filePath,
    ...
  }
}

Based on this I suggest sst drops the buildSchema call, as it does not verify the schema if there's just one, why do it when there are multiple if you can't do it properly?

The problem with my solution is that sst does not detect changes in my individual schema files, i.e. won't recompile.

Actually, ignore all that (deleted my previous comments, there was another error), you simply add an appsync.graphql file as follows:
  const api = new AppSyncApi(stack, "AppSyncApi", {
    schema: [
      "graphql/appsync.graphql",
      "graphql/part1.graphql",
      "graphql/part2.graphql",
    ],
  ...

And appsync.graphql is:
scalar AWSDate
scalar AWSTime
scalar AWSDateTime
scalar AWSTimestamp
scalar AWSEmail
scalar AWSJSON
scalar AWSURL
scalar AWSPhone
scalar AWSIPAddress

The only problem is that if I change graphql/part1.graphql sst does not rebuild. I.e. watcher is not picking this up.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


[docs] Use local Expo CLI in installation instructions

I noticed most of the Expo-related commands use the local CLI (npx expo ...), except for the installation instructions. Updated them accordingly.

Looks like I missed this, just merged it! Thanks.


Multi-arch images for stackrox/scanner

Hi folks! I'm creating this issue thread to discuss the relevant topics wrt the process of building scanner images.
Creating this here because stackrox/scanner does not have an Issues or Discussions tab.
As part of a broader effort, we've been trying to enable multi-arch image building so that we can run ACS jobs on Power.
So far, we've successfully built the collector-builder and collector-slim image and we're currently working on the images under stackrox tree (main, central-db, webhookserver), the PR for which is on the way. Once merged, the scanner set of images (scanner-slim, scanner-db-slim) is what we'll be looking at, but here's the deal:
As it stands today, IIUC, the scanner images are built using OpenShift-CI. This is different from the other two repos i.e collector and stackrox, both of which employ GitHub Actions to build the upstream images and as I understand, it is not straightforward to build multi-arch images on OpenShift-CI. We are aware that there are plans to move the scanner CI workflows from OpenShift-CI to Actions, however we wanted to discuss more on this.

There is a Power cluster available today to run jobs using OpenShift-CI, however since the stackrox images aren't multi-arched yet - we can't run any stackrox jobs. My question here is, is it possible, at all, to utilize this cluster to build the scanner images once we have the prerequisite images multi-arched? If so, what kind of efforts would we be looking at?

Follow up question, if we do build the ppc64le images for scanner using OpenShift-CI, how would one go about creating the multi-arch manifest?

Or instead of going through all that, is it better to just wait for the move to GitHub Actions?

Looking for some insight here from the stackrox/scanner team. Thanks!

FYI, @ghatwala @pratham-m @gavin-stackrox @robbycochran

Hi folks! So with the upcoming merge between scanner and clair, power team wanted to get some doubts cleared.

Will the CI for new image be migrated to GHA or will that remain in Openshift-CI as well?
What, if any, are the differences between scanner and clair?
Will we need to port both the images to Power (and Z)? Or with this merge is the old image unnecessary?

cc: @robbycochran @janani66 @ghatwala


[KAFKA-10722] doc: Described the types of the stores used

This is related to KAFKA-10722
Sometimes it's important to know the correct type
of the store used by streams. E.g. when iterating over
its items.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

???

Thanks for the PR @fml2! Sorry for the delay in reviewing. Sometimes it takes some time (good that you kept nagging :) )


Support file type of Kino.Input

This PR supports file type of Kino.Input.
This PR is related to https://github.com/livebook-dev/kino/pull/153.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @nallwhy, thanks for the PR :) I think we shouldn't keep the file contents in memory, because the files may be arbitrarily large (especially that Livebook operates in data-related domain). We can use path as input value instead. The file would initially be uploaded using LV uploads, this gives us a path within the local file system. However, ideally we don't want to rely on that path within the runtime, because in the future we may support runtimes on a different machine and that wouldn't work. On the other hand, in such case we would need to copy the file to the runtime whenever it's started. We haven't settled as for how we should address file inputs yet. @josevalim feel free to add your thoughts :)

@jonatanklosko
I think file input is not that different from text input. Test input also can take large input and cause memory problems.
It is just another interface of input.

@nallwhy we want to support uploading potentially 100MBs, which is not very common for text area. So we need to indeed discuss how to upload directly to disk. We also want to make sure it returns a path to a file because we may want to show the user how working with some file-related APIs work, and that would be hard to do without a file input that mimics a file.
I will discuss with @jonatanklosko what are the potential approaches here and follow up. :)

I talked to @jonatanklosko and we came up with an approach that should work:

We will use LiveView uploads for the upload
When consuming, we will transfer the file to the session process
The session process should remove the file once the input is removed
On Input.read, we will call a function in the runtime to transfer the file (if necessary). This should be a no-op for some runtimes as we can assume it runs on the same machine
file_input will then receive the filename from step 4

This may work for small uploads of a few hundred MB but for larger data I would think LiveBook would want to allow for uploads to go to S3 and/or pull from S3 or other cloud providers. For example, the liveview app I'm working on (https://github.com/mgwidmann/kart_vids) will process potentially GB+ files (these are high resolution 360 videos about 5 minutes long and around 3-4 GB each). I may not end up using Nx and LiveBook to develop the models because I'm still learning and need the greater resources available but I do want to come back and refactor to a pure Elixir approach later.

@mgwidmann the idea is to upload files into disk, then Kino.Input.read(input) will return just the path, not file content, so you can read or stream the content yourself. With this approach there should be no issue with regard to file size, since we are not storying it in the memory.
For cloud storage, such as S3, you just can upload the files directly and then use some S3 client to pull the file into Livebook.

@nallwhy thanks for the effort! I've just implemented the approach described above in #1622 :)


After attempted update package uninstalled itself!

This is the error message I got!
Updating to<EMAIL_ADDRESS>failed.Hide output…
fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/Users/<myusername>/.atom/packages/remote-ftp/package.json'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Proxy.fs.readFileSync (fs.js:508:33)
    at Proxy.fs.readFileSync (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/asar-require/lib/require.js:86:27)
    at /Applications/Atom.app/Contents/Resources/app/apm/lib/install.js:476:42
    at fn (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/async/lib/async.js:582:34)
    at Immediate.<anonymous> (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/async/lib/async.js:498:34)
    at runCallback (timers.js:649:20)
    at tryOnImmediate (timers.js:622:5)
    at processImmediate [as _immediateCallback] (timers.js:594:5)

Please check already issues https://github.com/icetee/remote-ftp/issues/1084#issuecomment-352527103
Duplicate of #1084


Fix compatibility issues with Reanimated v3

What's Changed
Reanimated v3 has brought some breaking changes. Fortunately, the changes that affect this library are not too significant.

Animated.Extrapolate is no longer available. Use Extrapolate import directly from react-native-reanimated.
All functions passed into runOnUI has to be marked as a 'worklet'.

Thanks for this. Found some things missing while looking into it and I have pushed #322 with some additional updates.
Released reanimated 3 support as 6.0.0-rc.0


Remove unused provider

what

Remove unused provider

why

Do not download the provider for local.file and local.sensitive_file as this is not required for the module to run
This makes terraform init run faster as well as download resources that are not used

references

Local provider that is being defined (https://github.com/cloudposse/terraform-aws-ecs-container-definition/issues/156)
closes #156

Failing from #155 It appears, will merge soon

/test all


Update fix shell

Update to latest package set, adds shell params to spawn/exec calls. Should fix #205 and https://github.com/nwolverson/vscode-ide-purescript/issues/223
This uses my updated fork https://github.com/wclr/purescript-psc-ide, I've made PR https://github.com/kritzcreek/purescript-psc-ide/pull/59.
Also added, Rename refactor fixes to this PR.

Done.


Add rm command to files and folders

The only command with rm right now is rm -rf /* which is used to "break" the page. There should be proper use for the commands though, such as removing folders and files.

Solved


Remove excessive coupling between sonatype commands and publishSigned

In my experience, there's an indirect dependency between publishSigned and all the sonatype commands, meaning that if publishSigned is executed concurrently the whole sonatype release will fail, detecting changes coming from other repositories.
I don't know why this is done this way, and I couldn't find the exact way it's done (I think you're polling the repo info from xml files created by publishSigned?), but I think this is undesirable:

It forces a logical dependency between the two, when they can be decoupled.
It prevents, by nature, concurrent execution of tasks.

Is there any way we can remove such decoupling? I find the way sbt-bintray handles releases ideal. bintrayRelease is completely independent of publishSigned, and can be executed concurrently.
Maybe the solution to all this is to get rid of the commands and just have tasks, as bintray does...

@jvican I don't think there is any dependency between publishSigned and sonatypeRelease command. publishSigned is an sbt task, and sonatypeRelease is an independent command.
I don't know why you are seeing this dependency, but my expectation is running publishSigned concurrently for multiple modules, but I usually would like to run sonatypeRelease command only once.
If there is a proper way to define a task which can be defined only at the root module, we can make sonatypeRelease as a task, but I struggled to define a task that can be enabled only at the root module other than setting redundant task settings in every projects (e.g., ++ sonatypeSettings in root and ++ sonatypeDisableSettings in other tasks, etc.)

The dependency comes from the fact that:

You cannot publishSigned concurrently. If a sonatypeRelease command is executed concurrently, it will fail to identify which module should be published.
The current workaround is to execute the following commands sequentially from a task ;sonatypeOpen bla;publishSigned;sonatypeRelease, and to make sure that they are exclusively for one project (two projects cannot release concurrently).
Even running ;publishSigned;sonatypeRelease fails. https://platform-ci.scala-lang.org/scalacenter/sbt-release-early/143.
sonatypeReleaseAll doesn't work and assumes that all the existing modules are aggregated in the root. Also, there's no way you can automate its execution. For example, sbt-release-early does not execute the releaseEarly task for the root project if it's not publishable.
I smell the root of the problem comes from all these things being a command and sharing the state. Wouldn't it be possible to distribute this state across keys scoped in the appropriate projects?

I don't know why you are seeing this dependency, but my expectation is running publishSigned concurrently for multiple modules, but I usually would like to run sonatypeRelease command only once.

This means there's no support for executing sonatypeRelease for a concrete module, because the id used to identify the publishing comes from Sonatype and not sbt. It also means that this is very unfriendly for sbt plugins automating publishing because it requires dependency analysis between the projects to find out who should run sonatypeReleaseAll, no?
In any case, having all these commands as tasks and decoupling the consumption of state would allow for the parallel execution of publish and sonatypeRelease, which are very long processes. On top of this, once you have them as tasks, you can always provide a command.
I'm not proposing a concrete fix to this situation yet, though I do give some hints. The goal of this comment is to make sure that we're on the same page and remove sources of miscommunication.

I think I understand your points, and a reason we cannot use tasks right now is sbt auto-plugin will enable sbtSonatypeRelease task for all projects. The early implementation of sbt-sonatype actually used tasks for sonatypeXXX, but gave it up because of this.

If we have multiple modules that needs to be published separately, we may need to explicitly enable plugin or add a setting to invoke sonatypeRelease task in each module root (an aggregated project).

Or if we may be able to skip running sonatypeRelease task in sub modules, for example, if 'sonatypePublish := true`  is not set, but e usually want to enable this only when releasing the project so using settingKey might be inappropriate...

For 5, I have no idea what scope will be appropriate. Sonatype staging profile ids will be issued after running publishSigned (or when creating a new session with sonatypeOpen). We need to find a way to pass the generated profile id between publishSigned and sonatypeRelease.

I'm not sure if this is related but i've also found that executing sbt ";sonatypeOpen ABC; publishSigned" creates staging repository with description ABC, but then publishSigned ignores that repository and creates a new one with description "Implicitly created (autostaging)."

I really don't understand how publishSigned choses the staging repository. Sometimes multiple parallel publishSigned commands choses one single (auto staging repository). But often they just creates new one...

I'm not sure if this is related but i've also found that executing sbt ";sonatypeOpen ABC; publishSigned" creates staging repository with description ABC, but then publishSigned ignores that repository and creates a new one with description "Implicitly created (autostaging)."

I've experienced the same, and I documented it here: https://github.com/scalacenter/sbt-release-early/issues/18.

@maqdev @jvican Mill's Sonatype publishing support always puts things in a single staging repository, and it will always only close/release the staging repository it published to so you don't have any weird concurrency issues I used to keep hitting with SBT

sbt-sonatype 3.0 supports concurrent publishSigned by using sonatypeSessionName as a unique identifier: https://github.com/xerial/sbt-sonatype#uploading-artifacts-in-parallel
@jvican
I'm not sure this can fully support your specific use cases, but I'm now actively testing this use case in my own project https://github.com/wvlet/airframe/pull/663
Let me close this ticket now that we have a solution for this.


⚠ DesiTorrents has degraded performance

In fff8823, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 5992 ms

Resolved: DesiTorrents performance has improved in 42ef53b.


Failing assertion provides bad test result

  1) Drafter Class parses and expands a blueprint:
     Uncaught Error: Callback was already called.
    at /Users/almad/Documents/projects/drafter.js/node_modules/async/lib/async.js:30:31
    at /Users/almad/Documents/projects/drafter.js/src/drafter.coffee:170:7
    at /Users/almad/Documents/projects/drafter.js/src/drafter.coffee:87:5
    at /Users/almad/Documents/projects/drafter.js/node_modules/boutique/lib/index.js:53:14
    at json (/Users/almad/Documents/projects/drafter.js/node_modules/boutique/lib/serializers.js:10:12)
    at /Users/almad/Documents/projects/drafter.js/node_modules/boutique/lib/index.js:50:16
    at fn (/Users/almad/Documents/projects/drafter.js/node_modules/async/lib/async.js:641:34)
    at Object._onImmediate (/Users/almad/Documents/projects/drafter.js/node_modules/async/lib/async.js:557:34)
    at processImmediate [as _immediateCallback] (timers.js:354:15)

Actually a code issue, will reopen with tests.


The difference between release version and open-source version for dmon command (>1000)

Hi
I have a question for the monitor command of dcgmi dmon -e 1009 (or any number greater than 1000). My working env is
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA A100-PCI...  Off  | 00000000:B1:00.0 Off |                    0 |
| N/A   27C    P0    34W / 250W |    475MiB / 40960MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
When I install the release deb package and input "dcgmi dmon -e 1010", it gives me the expected result.
But when I use the open-source code and build it by myself. When i input "dcgmi dmon -e 1010", it gives me an error "This request is serviced by a module of DCGM that is not currently loaded".
Is there any difference between release version and open-source for dmon command (>1000).
DCGM version: 3.0.4
Thanks

@ligeweiwu,
The OSS DCGM version does not have the profiling module required for DCP fields (>1000) on GPUs before Hopper.
You can still use them with OSS if you copy libdcgmmoduleprofiling.so from an official DCGM package.
WBR,
Nik

@nikkon-dev
Hi nik, thanks for your reply.
I have another question.
Now I want to test the api dcgmProfGetSupportedMetricGroups by means of the open source code (3.0.4). Thus, I use the command line
./dcgmi profile -l
And it give me the feedback:
Error: Unable to Get supported metric groups: This request is serviced by a module of DCGM that is not currently loaded.
So my question is,
When i want to use dcgmProfGetSupportedMetricGroups, should I also copy libdcgmmoduleprofiling.so? Does the utilization  of dcgmProfGetSupportedMetricGroups depend on libdcgmmoduleprofiling.so?
Thanks


Fix verify scenario capture ex msg

make new AppRunner().VerifyScenario(..) more useful by

capturing exceptions that escape AppRunner.Run, putting them into the result to verify as console output.
logging more context on error.  In addition to appsetttings, breaking out the argument descriptors, middleware, token transformations, parameter resolvers, help provider and dependency resolver.

Log context with appRunner.ToString();

this PR should be squashed


Add K8S v1.22.0-rc.0 into KDM

~K8S 1.22-alpha 3~  K8S v1.22.0-rc.0 will be needed for QA to test k8s 1.22.
It should not block devs from fixing the deprecated APIs because the api-server will start logging it in k8s 1.21

Currently blocked by https://github.com/kubernetes/ingress-nginx/issues/7145 causing NGINX ingress controller not compatible with k8s 1.22

Can we update this to k8s v1.22 now that it is GA?

RKE1 Standalone:

Available to test with RKE RC v1.3.3-rc1 (https://github.com/rancher/rke/releases/tag/v1.3.3-rc1)

Rancher
Steps to get a downstream RKE1 1.22 cluster:

Available to test with v2.6-head, make sure it's an image after this build https://drone-publish.rancher.io/rancher/rancher/6862. (Image ID: ffa2be0ed804, commit/version: f487c8819)
Update rke-metadata-config (Global settings -> rke-metadata-config) URL's branch from dev-v2.6 to dev-v2.6-122
Make sure v1.22.3-rancher1-1 shows up as experimental when provisioning RKE1 clusters

Verified the following on rancher server v2.6-head 96e2438
Kubernetes versions on the downstream RKE1 custom clusters with 2 worker, 1 cp , 1 etcd v1.22.3-rancher1-1

Fresh install of the RKE1 custom clusters on k8s 1.22.3 on all network providers
Network checks on the custom clusters
Creating ingress failed - https://github.com/rancher/rancher/issues/33312
Some issues that were seen while validating:
https://github.com/rancher/rancher/issues/35573
https://github.com/rancher/rancher/issues/35583

Verified the following on local rancher HA installed on k8s v1.22. v2.6-head e322f8f

HA with local RKE1 cluster with k8s 1.22 and rke 1.3.3-rc2
verified rancher server comes up Active,
verified all pods/workloads in System project of the local cluster are in Active state

Downstream RKE1 node-driver clusters:

Need to update 1.22.3 to 1.22.4 and addons with new tags.

Verified local HA installed on k8s v1.18.16 on v2.6-head 77392a6
RKE1 v1.22.4-rancher1 - Ingress tests look good.
Imported RKE1 v1.22.3 –  ingress tests look good.
Imported RKE1 v1.18.20 – ingress tests look good.
Imported RKE1 v1.22.3 - ingress tests look good.


Project cannot be started - TS compile error

node_modules/rxjs/Subject.d.ts(16,22): error TS2415: Class 'Subject' incorrectly extends base class 'Observable'.
Types of property 'lift' are incompatible.
Type '<T, R>(operator: Operator<T, R>) => Observable' is not assignable to type '(operator: Operator<T, R>) => Observable'.
Type 'Observable' is not assignable to type 'Observable'.
Type 'T' is not assignable to type 'R'.

I have the same issue, @SelAnt . Have you managed so fix it?

This fixed it. :)


Add 'use'  import on Class

When using a class, Model for example, it would be really usefull to add the 'use' at the top of the class, maybe suggest.

Unfortunately this cannot be done with Sublime Text Snippets. The snippet can only add text under your cursor
Sent with GitHawk


JavaScript block comment with arrow in HTML script - Expression expected / Unterminated regular expression literal.

Does this issue occur when all extensions are disabled?
Yes, all extensions have been disabled for the workspace

VS Code / OS

VS Code Version: 1.74.3
OS Version: Windows 10 Pro, 64-Bit

Steps to Reproduce
Create a HTML file with the following content:
<script>
/* --> */
</script>

🙁 Actual behavior
Console shows 2 problems:

Expression expected.
Unterminated regular expression literal.

Full errors:
[{
"resource": "test.html",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "Expression expected.",
"source": "javascript",
"startLineNumber": 2,
"startColumn": 8,
"endLineNumber": 2,
"endColumn": 9
}]
[{
"resource": "test.html",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "Unterminated regular expression literal.",
"source": "javascript",
"startLineNumber": 2,
"startColumn": 10,
"endLineNumber": 2,
"endColumn": 10
}]

It even shows more errors for every pair of -- within the comment block.
e.g.
<script>
/* --> ----------------------------- */
</script>

Results in a total of 16 errors logged (15 x expression expected, 1 x Unterminated regular expression literal.)
🙂 Expected behavior
Ignore whatever is in comments.

@aeschli Is the issue still open, if its not solved please assign me this issue. Thanks.

@Mayuresh0072 If you want to try to fix this, you are very welcome! Just start a PR and link to this issue. I think the problem is here: https://github.com/microsoft/vscode/blob/main/extensions/html-language-features/server/src/modes/embeddedSupport.ts#L199

@aeschli You're probably right.
I've been fiddling with the dist (htmlServerMain.js), changing
function s(e,t){return e.attributeValue||"javascript"!==e.languageId?t:t.replace("\x3c!--","/* ").replace("--\x3e"," */")}

to
function s(e,t){return e.attributeValue||"javascript"!==e.languageId?t:t}

and the messages in the console are gone.

That's too simple. We still need to remove the HTML comments from the script. But the fix could be to clear them out instead replacing with /* and */


Invalid Last Logged-In Value in Users List

After creating a user account, the Last Logged In field for that account showed "2016 years ago".

Duplicate of #6440. Already fixed in 1.10.


Support cosim-mode tests

When cosim is available on the target platform for scalar load/stores, loading the scalar values is sufficient to detect errors in vector arithmetic.

We're using single/single.go to generate stage1-only tests for cosim usage. But this is another way to do it I guess.


Discussion: Office 365 users and Skype For Business Reports

Hello guys,
We are already at a good point with the integration of the usage reports of Office 365 services. Before proceeding with the residual command requests I wanted to have a short alignment with you.
The structure and implementation of Yammer's usage commands will be a no brainer. But on the other hand, we have two other categories that do not necessarily fit in our current setup.

Office 365 users reports: Link
Office 365 activation reports: Link
These are reports that are not necessarily associable with an individual product. Where do we want to place them and how should we call these commands?

Last but not least, there are still many Skype for Business reports. The question is if we still want to invest here considering that Skype will be replaced in near future. Link
Thank you for your feedback.
Patrick

Thanks for raising this issue and starting a discussion, it is much appreciated.
My initial thoughts are that the two Office 365 reports you have mentioned should go under the 'tenant' group which at the moment only contains a single command id, this returns the ID of the Office 365 tenant. The full command path is o365 tenant id so your proposed reports could be implemented as o365 tenant report activeusers and o365 tenant report activations respectively.
For the Skype for Business reports, these could still be useful as Teams still uses the Skype for Business architecture behind the scenes to handle calls, messaging etc and as they are present in the Graph I think it will be safe to implement. We should implement these under a new command group like sfb.
As you've mentioned Skype for Business will be replaced by Teams as the communications tool of choice for Office 365 in the future, but I don't think all of the architecture will be replaced anytime soon.

@VelinGeorgiev @waldekmastykarz do you agree with the above approach?

I like the proposal for the naming convention of tenant-level reports tenant report xyz.
As for Skype reports, it's hard for me to judge the need for them. I think the community would be a better judge of that. That said, I'm not against implementing them. One suggestion I'd like to make is regarding the commands' prefix. Since we use onedrive for OneDrive for Business, I'd like to propose using skype for Skype for Business to keep things consistent and more user-friendly.

@waldekmastykarz and @garrytrinder
I am going to open the issues for these commands beginning of next year

Excellent! Shall we close this issue then and keep the command-specific issues open for tracking?


Only  tokens are generated in summary.In data.py file, when we read the vocab file, it only takes the 'rb' mode not work with 'r'.

Excuse me,Have you solve the problem?when i run "python run_summarization.py --mode=decode --data_path=/chunked/val_ --vocab_path=/vocab --log_root=*****/a/log/directory --exp_name=myexperiment" ,the generated summary is consist of UNK,could you please do me a favor?


counterpartyd 9.49.3 won't start because version page is down?

Counterpartyd checks https://counterpartyxcp.github.io/counterpartyd/protocol_changes.json to see what version is needed to run.  This file seems to be gone, now?

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@ouziel, can you put that file back?

I'm having the same problem here as well.  Counterpartyd has stopped responding to API requests due to this issue.

@robbydermody is on it. Should be fixed very soon.

Thanks.

fixed. please ping if not working for you

All good now. Thanks.

Seems to be good for me too, now.

Running into the similiar issue of missing "protocol_changes.json "  with the standalone windows counterparty cli tools (https://github.com/CounterpartyXCP/counterparty-cli/releases/tag/v1.0.0).
I have to first run the "c:\python34\scripts\counterparty-server.exe start" once first before the standalone CLI tools work

hum.. weird I just check and the standalone windows binaries contain the file in the correct place (unless you are using counterparyd develop).. can you please post the complete error message ?

I was using the one at https://github.com/CounterpartyXCP/counterparty-cli/releases/tag/v1.0.0
But the issue is not present anymore after running c:\python34\scripts\counterparty-server.exe start once.

OK, I will try to reproduce.

@ouziel-slama : Sorry, the issue only applied to the standalone C:\counterparty-cli-win32-1.0.0>counterparty-client.exe  (NOT server)