map_blocks to receive xarray

Can the callable in map_blocks receive an xarray if the source array is an xarray?
I can think of some crazy ways to achieve this, but none of them are particularly elegant.  Hoping the community has a better solution for this.

Generally dask arrays contain numpy-like arrays.  Usually xarray datasets
contain dask arrays, so the arrangement here is somewhat reversed.
The Xarray equivalent of dask array's map_blocks function is apply_ufunc.
I wonder if that would solve your problem. cc @shoyer
On Mon, Mar 11, 2019 at 10:43 PM Tony Tung<EMAIL_ADDRESS>wrote:

Can the callable in map_blocks receive an xarray if the source array is
an xarray?
I can think of some crazy ways to achieve this, but none of them are
particularly elegant. Hoping the community has a better solution for this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4582, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszMmAu8dKKXAMY4Zrhrk9x2f0-ijEks5vVz51gaJpZM4bqHA7
.

+1 to everything @mrocklin said

There are intrinsic advantages to knowing your dimension names, and it's certainly plausible there are computations where knowing your labels are helpful.  In many ways, it's like typing your variables in code.  It's not strictly required, but it is a boon for the long-term maintainability of code.  xarray as the fundamental building block of scipy (rather than numpy) would be a huge improvement.

I agree that Xarray is generally great.
I'm not sure what your last comment is intended to convey though.  If you're trying to encourage Dask array to support xarrays internally then I disagree.  There is no reason for Dask Array to support Xarrays internally.  The relationship between the two projects is that Xarray wraps around Dask Arrays.  If you like the Xarray interface then I encourage you to use Xarrays rather than using Dask arrays directly.  You'll still get all of the parallelism and out-of-core operation that Dask offers while also getting all of the virtues of Xarray that you list above.

The callables in for map_blocks and apply_ufunc are not able to received "typed" arrays.  That's what I perceive is missing in the current arrangement.  Of course, it's quite likely I'm completely wrong, as I don't know the internals as well as either of you. :)

I'll defer to @shoyer on that.  I'm not super-familiar with the Xarray API.
Alternatively you might want to raise this question on the Xarray issue
tracker, where more Xarray folks will be able to help.
On Tue, Mar 12, 2019 at 10:59 AM Tony Tung<EMAIL_ADDRESS>wrote:

The callables in for map_blocks and apply_ufunc are not able to received
"typed" arrays. That's what I perceive is missing in the current
arrangement. Of course, it's quite likely I'm completely wrong, as I don't
know the internals as well as either of you. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4582#issuecomment-472114485, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszE389n1M9nC5E_3hytiJku18wXHiks5vV-sSgaJpZM4bqHA7
.

Cool, I'll try that.  I wasn't sure where to raise this issue as it's the intersection between the two projects. :)

No worries
On Tue, Mar 12, 2019 at 11:05 AM Tony Tung<EMAIL_ADDRESS>wrote:

Cool, I'll try that. I wasn't sure where to raise this issue as it's the
intersection between the two projects. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4582#issuecomment-472116970, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszDc8T-M_Z39aNTQ22UbFNqh6ahptks5vV-x3gaJpZM4bqHA7
.

Filed as https://github.com/pydata/xarray/issues/2807


Duplicate ID

On a user edit page i have several forms using formstatic but formstatic is duplicating the ids, i would like to know if have a way to change this issue. here a exemple:
<form accept-charset="UTF-8" action="/users/test" class="formtastic user" id="edit_user_1" method="post" novalidate="novalidate">
the edit_user_1 is duplicating on the others forms.
thank's

See the "Namespaced forms all multiple Formtastic forms to exist on the one page without DOM id clashes and invalid HTML documents." in the documentation of semantic_form_for.
That should solve your problem.

@mikz  thank's for your reply, i placed the namespace  and did not solve.

@dcalixto you can still pass :html option to it. So something like this would solve your problem:
semantic_form_for(@user, html: { id: 'prefixed_form' })

thank you very much @mikz , and unintentionally abuse, the same probem seems to appear on submit:
i've tried the same logic but seems not solve.
Duplicate ID "user_submit_action"
  <%= form.actions do %>
        <%= form.action(:submit, :label => "Save",  :button_html => { :class => "btn", id: 'button_address'}) %>
        <% end %>

@dcalixto could you post the generated html ? It is weird, that button_html would not work.

@dcalixto I check the source and the tests and I don't see any possibility why :namespace option should not work. Could you paste an example how you were trying to use it?
It would help us a lot. To improve documentation, we need to learn how people use it and what mistakes they make.

I too am experiencing the same problem with the namespace option. The versions used are: formtastic (3.1.4) and formtastic-bootstrap (3.1.1). (I wonder if it's a formtastic-bootstrap problem.)
Using the plain old Rails form builder:
= form_for(@animal, namespace: 'cat', url: zoo_animal_path) do |f|

gets me:
<form id="cat_edit_zoo_animal_249" class="edit_zoo_animal" method="post" accept-charset="UTF-8" action="/zoo/animals/249">

whereas using Formtastic:
= semantic_form_for(@animal, namespace: 'cat', url: zoo_animal_path) do |f|

gets me:
<form id="edit_zoo_animal_249" class="formtastic zoo_animal" method="post" accept-charset="UTF-8" action="/zoo/animals/249" novalidate="novalidate">

So the cat namespace is missing in the id.

@fredngo Thanks for the report! I made a PR (#1212) with a regression test to verify it surely fails. And it does.
I'm not sure why, how to fix it or how much time I'll have to work on that. If you feel like, feel free to chip in.

Wow, thanks for the quick response @mikz ! For now that the issue is documented at least.

I'm experiencing the same problem with duplicate ids on the submit buttons and forms.
I think this is happening because the :namespace option isn't being passed to the original implementation of form_for. It gets remapped as custom_namespace.
@mikz Do you know if there's a reason it was remapped like this?

I made https://github.com/justinfrench/formtastic/pull/1065to to fix https://github.com/justinfrench/formtastic/issues/904. It was doing nasty stuff and changing class variables when rendering forms.
It is possible I did not fully understand the implications and it has a bug that prevents using the :namespace option. We should verify the regression test https://github.com/justinfrench/formtastic/pull/1212 failed/passed before these changes. If so then it indeed broke it.

@justinfrench https://github.com/formtastic/formtastic/pull/1212 doesn't seem to be merged yet; did some other fix solve this bug?

@fredngo I closed this as part of a mass clean-up. If you have the time to pull all this together in one PR, I'd really appreciate the help, as I don't have the time to maintain this like I used to.


[Bug]: Container does not have "Height" Property.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Container does not have "Height" Property. It only has "Visible" and "Animate Loading". This on Self Hosting version.
Steps To Reproduce
Container does not have "Height" Property. It only has "Visible" and "Animate Loading". This on Self Hosting version.
Add a container to any Page.
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Appsmith Community v1.18

Additional Details -
I see Height when switched to "Fixed Layout". When you have a container has a table and that table has more rows than the height, you don't have a way to scroll those table rowsd!

@rbudigelli I'm not able to fully understand your issue.
By default the container has auto height and will wrap any widget you drop inside it
If you change it to fixed, you can manually resize the height


Add OpenAPI spec generation step in CI

This will be used with fuzzer tools

I don't think the fuzzer should run as part of the CI. It should be run at worst manually, or on a cron schedule. Tests should be easily reproducible and the fuzzer is the opposite of that.

Any way we can keep it in sync ? :/

Any way we can keep it in sync ? :/

Through sheer willpower


FR: "howto" get bundleId?

I recognize this is likely mac-generic, but it's not abundantly clear to me the best/canonical ways to get bundle Ids and window names. For instance, one window I like to be able to switch to is simply "R" (yes, that's the whole window name). I haven't been using this spoon long enough to know for certain, but I fear that can bite me when I have other windows with titles that contain an upper-case "R".
(Further, not sure if HS supports this, but ... that window is a graphics canvas created by the R programming language. The underlying executable comes from the R.app, but calling that app is not the same as the window with the "R" title. Is there a way to more clearly identify windows that can be much more specific, like a window class? Or can we use regex for window titles, so "^R$" would work for me here?)
Thanks for the spoon!

Here's the English translation:
Hey! Thanks for your feedback!
There are simple ways to get the bundle ID:

Using the command line: Run osascript -e 'id of app "Application Name"' to output the corresponding bundle ID. For example: osascript -e 'id of app "Safari"'
Or you can right-click the application in Applications folder, select "Show Package Contents", then find the CFBundleIdentifier in Contents/info.plist file - this is the bundle ID (Note: this method requires you to have software installed that can open plist files to view their contents).

Regarding your second question, since I haven't used R language, I can't speak to that aspect. However, it seems your question is: "When an application has multiple windows open, is it possible to open a specific window (based on window name) using custom hotkeys?"
From what I understand, Hammerspoon should have APIs that can get all windows opened by an app, and then filter them based on specific conditions (simple string matching or regex matching). Theoretically, it should be possible to get the specific window you want.
However, due to my limited knowledge of Hammerspoon and Lua programming, I can only answer this far - I apologize for that. If you're willing, you're welcome to submit a PR to help improve this functionality. I believe this would be a very useful feature.

Hey! Thanks for your feedback!
There are simple ways to get the bundle ID:

Using the command line: Run osascript -e 'id of app "Application Name"' to output the corresponding bundle ID. For example: osascript -e 'id of app "Safari"'
Or you can right-click the application in Applications folder, select "Show Package Contents", then find the CFBundleIdentifier in Contents/info.plist file - this is the bundle ID (Note: this method requires you to have software installed that can open plist files to view their contents).

Regarding your second question, since I haven't used R language, I can't speak to that aspect. However, it seems your question is: "When an application has multiple windows open, is it possible to open a specific window (based on window name) using custom hotkeys?"
From what I understand, Hammerspoon should have APIs that can get all windows opened by an app, and then filter them based on specific conditions (simple string matching or regex matching). Theoretically, it should be possible to get the specific window you want.
However, due to my limited knowledge of Hammerspoon and Lua programming, I can only answer this far - I apologize for that. If you're willing, you're welcome to submit a PR to help improve this functionality. I believe this would be a very useful feature.

Thanks for the feedback, that's helpful. I'm new to macos and new to HS, so a double-whammy trying to appease my muscle-memory coming from my previous laptop. This is definitely helpful, though personally I find macos hides a lot of really easy/useful information behind obscure APIs and command line interfaces. All of my years of windows/linux administration are not very insightful here on this shiny new mac :-/
FYI, I suggest it might be very useful to some users if you put something like that call to osascript in the documentation. If I'm the first since you started, then maybe I'm wrong, but I suspect it could help somebody. :-)

Thank you for your suggestion. I will update the documentation to help others who might have similar questions. The main reason for creating this project was that I originally had a dedicated software called Manico (in case you need similar functionality like I did) to achieve this effect, but after updating my macOS version, the software temporarily stopped working. So I created this spoon, and initially didn't expect others would be interested in it, but habitually made the repository public. Perhaps this is the true spirit of open source: "Maybe this could be useful for others!" Therefore, I really appreciate your suggestion, which has given me a deeper understanding of open source and the idea of "doing something beneficial for others." Thank you again, and have a great day :)

heh, I just realized that this repo is not the same spoon as https://github.com/Hammerspoon/Spoons/tree/master/Source/AppWindowSwitcher.spoon, sorry for assuming you were the author/maintainer of the published spoon :-)


expand escaped characters in osx plugins

Help message for feature of controlling iTunes contains escaped tab(\t). But it is not unescaped when is printed.  This PR is for fix that.

What case is this necessary in? -e is the default for zsh's echo, and itunes -help is working fine for me as is.

This happens if the BSD_ECHO option is enabled: http://zsh.sourceforge.net/Doc/Release/Shell-Builtin-Commands.html#index-BSD_005fECHO_002c-use-of. Anyhow, we could maybe standardise the use of print instead, which doesn't depend on that option:
$ setopt bsdecho
$ echo "\tabcde"
\tabcde
$ print "\tabcde"
	abcde

Ah, didn't even know about that option.
Preferring print to echo sounds good. We could also use emulate -L zsh inside functions for broader protection against portability-affecting options. Maybe doing both is best.
(I've been trying to get in the habit of using print/printf instead of echo myself, due to echo's portability issues across different shells and platforms.)


GrpcService with default serialization formats does not show a debug form in DocService

Unlike THttpService, a user has to enable more serialization formats to make DocService show the debug form for a GrpcService. Perhaps we should:

make it less surprising,
update our documentation, or
add some instructions to the DocService page without the debug form

What do you think, @anuraaga ?

Yeah with some more documentation and with text in DocService or at least a logger.info, it would be much clearer. I think the default for it to be off is safer, at least for servers that might be exposed to external traffic since exposing unframed JSON can be a huge DDoS opportunity - it's the main reason I didn't default those on.
I have been thinking for some time, and a little related to this, perhaps we could have the concept of modes in armeria. Something along the lines of

Internal vs external
RPC vs REST
Unary vs streaming
... etc (though not too many or it's just spaghetti soup)

which group together best-practice defaults / flags for each use case. In this case, I would default on in Internal and off in external. Defaults for things like the path parsing cache, timeouts, logging, and probably many things could also be tuned for these use cases.


Scripts/compileExtensions.js:84 syntax error

Describe the bug
The ? in packageJSON?.main seems to be causing an issue:

Version
2.0.0-test
Node v12.20.0

Browser

[ ] Electron distribution
[x] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/microsoft/BotFramework-Composer.git
cd BotFramework-Composer
yarn install
yarn build

Expected behavior
Install composer successfully
Screenshots

Additional context
When I remove the ? install works fine. I also have to update the "mongodb-client-encryption" to ^1.2.0 for the install to work. Otherwise I see the following error when running yarn install and yarn build :

@zachgoz This seems to be an issue with building with Node 12 version. Could you try with the Node LTS version and see if this issue reproes there?

@srinaath Thanks, using node 14.17.0 sorts out the compileExtensions issue. However I still see the mongoStorage install issue unless I remove the yarn lockfile and update to "mongodb-client-encryption": "^1.2.0".

Hi @benbrown Could you please take a look at this issue?

@zachgoz thanks for the report. I will look into updating the dependencies in that sample extension to resolve this.
I am not able to reproduce this error -- does this occurs during the main yarn build process or are you reproducing the error by building the mongoStorage extension directly?

@benbrown yes this occurs when running the main yarn build process after cloning the repo or downloading release source.

@zachgoz thanks for confirming.  Do you happen to have a very old set of xcode tools by any chance? It appears like some part of the mongo crypt package is failing to compile.

I am not running the latest version, I can try updating this.

I upgraded xcode tools but still see the same issue:

@zachgoz before you do yarn and yarn build (since you recently switched to later version of node) make sure you remove all the node_modules from extensions. For example delete node_modules under BotFramework-Composer/extensions/mongoStorage path

Closed due to inactivity.  If you still have an issue, please reopen.


Merge refs/heads/clean/unused-cases into alpha

Merge refs/heads/clean/unused-cases into alpha

This PR has been merged into alpha and tagged as 2.0.0-alpha-202308301457. Thanks for your contribution!


Fix documentation to mention new Octal notations

Octal notation was updated to support the "0o" and the "0O" prefixes.
Updated documentation to reflect the same.
Reference:

Introduced in commit? c17e66c5c0acd5038f1eb3d7b3049b64bb6ea30b
Where in code? https://github.com/vim/vim/blob/e8209b91b9974da95899b51dba4058b411d04d5b/src/charset.c#L1849-L1871

To Discuss

Do we plan to deprecate the zero prefix for octal numbers?
If yes, can we add a warning of some sorts to indicate this?

The zero prefix is not used in Vim9 script.  I'll add a remark about that.


Feature/level with index content

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question: input from eye-tracker or head-tracker?

The GLFW wiki says the library can handle joystick, keyboard, and mouse inputs. Is it possible extending the input methods using eye-tracker, or head-tracker? Is there any kind of documentation for doing that?

For hardware like that I recommend to use the hardware manufacturer's SDK. If you need native handles to integrate it with GLFW, like NP_RegisterWindowHandle for TrackIR, see the native access functions.


Improved AddClosingBraces feature

fix for nested braces not adding extra closing braces
fix for closing single/double quote not overwriting existing closing quote
plus a small typo fixed

Can you should example codes demonstrating the change?

you mean can I show*?? :)

fix for nested braces not adding extra closing braces

inserting a left parenthesis after another:
Before:  After:
Closing of nesting braces also work perfectly.

fix for closing single/double quote not overwriting existing closing quote

Before:  After

I found a bug while trying to add support for escaped quotes not overriding.
ASComplete.OnShortcut() is sometimes not called when key == Keys.Back.
It seems completely random, and it is quite frustrating because sometimes I can't tell whether it's the bug or error in my code that is not deleting what should be deleted. Moving the caret up and down several times before pressing backspace seems to be the only solution.

Maybe something (main app or a plugin or Scintilla itself) captures the key in some conditions.

Yep, I know about this, the problem is how FD is currently handling the key strokes for the completion list and the call tip. Currently the call tip is consuming the key. I have it fixed in a branch... and it would allow for more new features, so if you could go to this board topic and help with the 64 bits testing so it gets merged soon, I'll commit the work for the refactored completion list, that fixes this issue along with some others and have some usability improvements among other things.

Another improvement I'd suggest for auto-closing braces: do not insert a closing brace when it's likely to be undesirable. Like: var foo = |bar; I'd like to wrap bar with parenthesis but I have to delete the closing brace inserted.

@Neverbirth That's a good news! However, I'm sorry I can't help you with the 64 bit testing; I'm one of those who still has 32 bit computers.
@elsassph I'm already working on that :)
Right now, I'm trying to sort out the style values that would most likely to be the ones that should be wrapped around. However the trouble is that some braces have different meanings and uses than others - () and []  are very similar, but they are quite different from {} and "" in many cases.
I feel like I'll end up modifying the Braces class or other things, but shouldn't be too hard.

Even if you don't have 64bits you can help by reporting that the normal version is working as always without any problem.
I'll try to update another of the branches to the latest development commit and upload more builds soon.

About 45c9cee: please ignore this. I'm very new to GitHub (this is the first time ever using it) and I just downloaded the GitHub Desktop whatever and was playing around with it when this merge thing happened.
I added an option for the user to choose when to automatically add closing braces for each set of braces.
This turned out to be quite cool, because it allowed me to support the generic type braces <> as well as enable users to add custom 'braces', such as the the tertiary operator ?:. To try this out just adding a new brace with Opening = '?' Closing = ':' AfterStyle = DEFAULT will do.
Users can also manually add&remove default braces or their automatic closing options.
I ended up adding a new resource string to PluginCore, and if it will be used they would need to be translated for languages other than en_US.

Not everyone has Visual Studio 2015 ;).

Also, I'd flag your fix for the backspace as not 100% valid, because there are cases where the backspace would stop working, for example if the calltip is available, but the underlying scintilla control isn't using ASComplete or if the setting ASContext.CommonSettings.AddClosingBraces is false.

@Neverbirth All I actually did in the fix is to make sure that CompletionList does not handle backspace itself (not calling sci.DeleteBack() and not setting e.Handled = true) - just as what would happen when the completion list is not available.
I tested and it does seem to still work when AddClosingBraces is false or ASComplete is disabled.

Can anyone test this and give me some feedback on how this works?

I can test the night

I'll also test it asap.

Thanks :)

Is there anything I have to do about the "conflicts"?

I think that you need to pull fdorg/development into your branch, and resolve conflict after.
ps
Please write me an email<EMAIL_ADDRESS>I can not find any other way to contact you

So did anyone give it a try?

@elsassph doesn't seem like it... lol

Possibly closes #370.

It looks like the feature is specialized for the cpp-lexer. What happens when you open an XML/HTML/python/etc. file?

It seems like ASCompletion doesn't work for XML/HTML/Python/JavaScript.
This feature doesn't work for those and fortunately doesn't screw them up :)

Hey I'm giving a try and it's pretty good.
One rather annoying thing is the insertion of closing quote when it's really not desired:
var foo = |bar  -> var  foo = "|"bar
a = { |foo:"value" } -> a = { "|"foo:"value" }

So generally quotes shouldn't auto-close if there is a non-whitespace character at the cursor position.

Yea, string were quite difficult to manage, because the style value after an opening quote is always StringEOL, so with the default setting of BeforeStyles set to { StringEOL }, string always auto-closes, except at the end of file.
If there is a way to bypass this, quotes will be as configurable as the other braces. Got any method you know?
For now, try setting the " and ' to have BeforeStyles empty, and BeforeChars to ABCDEF...wxyz([{<... and BeforeStyleMode to Exclusive. A cheap way but still would work...
Speaking of whitespaces, I should probably enable users to enter escaped characters.

Progress on this?

From my side I'd like to wait a bit to see it merged (even if the conflicts are resolved I mean).

Ah yes, I'm still working on this.
Strings like below: (| is a caret)
var a:String = "| + "b";

screws everything up by Scintilla reporting " + " is STRING and b"; is STRINGEOL.
Simple solution I thought was to delete the inserted char and get the base style value afterwards, but then it seems like the style values don't get updated immediately T^T.

Yes, style values are not updated immediately depending of when you check them. You'd have to use sci.Colourise method.

Oh, so that method is like an update for the styles? Will try.

@wise0704: Let us know when you can complete this.

Hey I'm giving a try and it's pretty good.
One rather annoying thing is the insertion of closing quote when it's really not desired:
var foo = |bar  -> var  foo = "|"bar
a = { |foo:"value" } -> a = { "|"foo:"value" }

So generally quotes shouldn't auto-close if there is a non-whitespace character at the cursor position.

I am currently working on this, but the examples you provided aren't really likely to occur in real practice. Like, if they wrote ... = bar already, chances are that bar is already an identifier, and they might want to do something like "value = " + bar.
This will be customizable by the user using AddClosingBracesData, but we would need to decide what to use as the default setting though.

I think it's ok to colourise with (0, -1).
I really think the behaviour should be to not insert the closing brace if you type a brace at the beginning of a word: it's better to have to add the closing brace if it wasn't inserted automatically than to remove a useless one.

By "word" I assume you mean Style.Identifier and Style.Keyword?

I see those two are already excluded from the "" and '' braces. Can you try them out?
Also, are the other braces closures working as you would expect them to?

The configuration can be removed from setting by just removing it from the settings object, but that doesn't do anything performance-wise or code structure-wise. Also this configuration is really just a suggestion and depending on the programming language each user uses and their taste, many users would want to modify a few options. E.g. In AS3, generics not even are written as Vector.<T>, thus after '.'. In Haxe, they are written as Array<T>, thus after Type. (I did try to compromise by setting it to after Type or Operator.)

Alright, I like the defaults now, but the rules would require an entire WIKI to make sense :D
The setting may be called "Add Closing Brace Options" though.
Good to merge.

Oh BTW I had to add a reference to System.Design in ASCompletion.

In ASCompletion?
I already moved the DescriptiveCollectionEditor<T> class to PluginCore, so ASCompletion shouldn't be using System.Design. I can compile without problems?

No compile issues here. This looks good to me for merge.

Seems like git is not familiar with .resx files.

Conflicts again.

Git obviously doesn't like .resx files...

Fixed conflicts.

This was marked good to merge, so if nobody complains I'll merge it before the weekend.

This has conflicts again. Soon as fixed, i will merge this.

Something is wrong with the resource files and causes +/-6k lines from each. Probably line endings.
Sec.

Fixed conflicts.


Summary of Parameters (trainable & non-trainable)

It would be nice to see in the overview of the model summary of parameters (trainable & non-trainable) for the whole model.

For which model format and how is this determined from the model file?

Sry for the late answer. For keras-models its possible to get the weights with mode.weights(). This returns all the weights for the different layers. To count all the weights this function can be used:
np.sum([np.prod(v.get_shape().as_list()) for v in model.weights])

What summary do you expect to see - only the total number of layers?

Exactly, the total number of (trainable & non-trainable) weights tensors.

@lutzroeder  It's necessary to view the total number of models.

This would be a good thing to add.


Support in-toto as a provider to allow users to use an existing attestation framework

What would you like to be added?
in-toto provides a framework to protect the integrity of the software supply chain. It has an Attestation framework that provides a specification for generating verifiable claims about any aspect of how a piece of software is produced. Users can then validate the origins of the software before using it, and establish trust in its supply chain, using in-toto attestations.
The typical workflows of sign and verify attestation are as follows:

Generate attestation using in-toto with a known predicate
Sign this artifact using Notation
Apply policy on that artifact with Gatekeeper and Ratify. It requires us to write a lot of logic to extract the in-toto predicate out of the attestation

If Ratify has a plugin provider for in-toto, it will be able to extract the attestation predicate in a way that REGO policies can be validated easily. The extraction logic shouldn't be something the end user has to be concerned with. A well-defined in-toto framework/envelope for embedding the attestation predicate can help users easily validate the origins of the software.
We still need to investigate the use cases with in-toto and figure out the attestation verification scenarios with Ratify.
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this feature?

[ ] Yes, I am willing to implement it.

Some initial thoughts I had. Disclaimer: I'm very new to in-toto so my understanding is quite limited.
The envelope, which usually packages the output of a step defined in the security chain, contains a predicate. There is support for custom predicates but there are more common pre-defined predicates such as SBOM and other provenance standards like SLSA.
Like @FeynmanZhou mentions, the simplest integration would be to support a separate in-toto external verifier. From Ratify's perspective, I assume that the envelope will be the artifact verified instead of the individual predicate like we have support for now (SBOM, Licensechecker, etc.). This would allow the us to support other envelope types easily in the future too. If we go down this route, there are some design considerations we have to resolve:

Will there be a separate in-toto verifier per predicate type?
Ratify already has support for multiple "predicate" verifiers directly. However, since the artifact itself is the envelope, the existing verifiers will not work out of the box. Currently there's no way for a verifier to call another verifier which would mean that we could potentially have duplicate verifiers (apart from the envelope extraction logic in each).

Does artifact type for the envelope needs to be dependent on the underlying predicate type?
Ratify matches verifiers to artifacts by using the artifact's artifactType field. If we have multiple in-toto envelope artifacts with different predicates, we would need a predicate-specific artifact type to distinguish which verifier should be run. Note: There might be ways around this using an annotation on the artifact to hint to predicate type but we'd need to flush this out.

The other implementation approach would be to consider building envelope support built into ratify. Logically, this might make more sense since the envelope predicate aligns closest with a Ratify verifier. This approach, however, might require quite a bit of change. Curious what others thoughts are about this? cc: @binbin-li @susanshi

There's recently been more interest in supporting this. I think we need to consider maybe a first class Attestation type to handle scenarios where attestation are used. Intoto is just one attestation type. Notation does not support intoto and may introduce their own in the future.

@susanshi @FeynmanZhou should we use this issue for tracking attestation work or make a new one?

@susanshi @FeynmanZhou should we use this issue for tracking attestation work or make a new one?

@dasiths Could you pls help confirm which attestation predicate type used in your scenario? If that is different from this issue, we can create a new one to track.

@susanshi @FeynmanZhou should we use this issue for tracking attestation work or make a new one?

@dasiths Could you pls help confirm which attestation predicate type used in your scenario? If that is different from this issue, we can create a new one to track.

Yes this is the scenario we would like to cover. We use a mix of SLSA SPDX, SLSA Provenance and other custom predicates types in our own use cases. While the policies for known in-toto predicates can be pre defined, it would be useful to allow the end user to specify...

What predicate type they want to run the policy on
Explicitly define the REGO or CUE  policy (You will need to define a known shape of the output of the policy result + errors so they can be surfaced easily. i.e. Allow, Err etc)

A thing to also consider is that there could be multiple attestations of the same type signed with the same key. So your policy needs to be smart about parsing all, any one or select one based on a condition.
Here is an example of a REGO policy that we use. This policy checks for a custom predicate type. It even reads a value from the environment. It only looks at the latest predicate from a list of all matching ones.
We use cosign to find the matching attestations that have been signed using a particular key, then collect all of those attestations to a json array before passing that array as the input to the REGO policy (using opa eval).
package policy_validation

default allow = false

default deny = false

default latest_match = null

default latest_ts = null

uat_type_param := opa.runtime().env.UAT_TYPE
uat_type_to_match := concat("", ["https://www.yourorg.com/public/ssc/spec/attestations/uat_check/v1/", uat_type_param])

matching_objects := [obj |
	obj := input[_]
	obj.predicateType == uat_type_to_match
]

matches_found {
	count(matching_objects) > 0
}

latest_ts := max([val | val := to_number(matching_objects[_].predicate.timestamp)])

latest_match := [obj | obj := matching_objects[_]; to_number(obj.predicate.timestamp) == latest_ts][0]

latest_is_allowed {
	latest_ts != null
	latest_match != null
	latest_match.predicate.result == "passed"
}

allow {
	matches_found
	latest_is_allowed
}

err[msg] {
	not matches_found
	msg := sprintf("No matching statement(s) were found: %v", [input])
}

err[msg] {
	matches_found
	not latest_is_allowed
	msg := sprintf("A matching statement was found but they did not pass the UAT check: %v", [input])
}

We can then subsequently look at the known allow, deny and error output shapes.
      if ! (opa eval -i "$extractedPayloadFile" -d "$policy_file" 'data.policy_validation' > "$validationResultFile"); then
          echo "[Error] Policy validation failed"
          cat "$validationResultFile"
          exit 1
      fi

      echo "Result from validating policy against attestation statement:"
      < "$validationResultFile" jq .

      allowed="$(< "$validationResultFile" jq -r '.result[0].expressions[0].value.allow')"
      echo "Allow=$allowed"

      denied="$(< "$validationResultFile" jq -r '.result[0].expressions[0].value.deny')"
      echo "Deny=$denied"

      errors="$(< "$validationResultFile" jq -r '.result[0].expressions[0].value.err')"


Webview layer scroll position jumps around when scrolling up

Version: 1.45.0-insider (user setup)
Commit: abb4a35cfc26102f93fd00df7b59ce1a19c2017a
Date: 2020-04-28T05:36:25.810Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Recording: https://memes.peet.io/img/20-04-9263f800-d242-4cbf-917f-b1c919ec9f84.webm

@connor4312 do you see this issue all the time? I think it's because some scroll events are missed and then the view position are not set correctly.

Hm, I'm not able to have this happen on a new instance today / after updating Insiders.

Fixed via https://github.com/microsoft/vscode/commit/e58fca86ce62a874f229df908c2ea2a78c9cda9e . @connor4312 please help try again from master or with tomorrow's Insiders, if you can't reproduce it, you can call it a verified.


Script for downloading and preprocessing CIFAR and svhn dataset

Hi thanks a lot for your work! In the readme you said you have the script for downloading and preprocessing CIFAR and svhn dataset, but I didn't find it in the repository. Could you please describe how you preprocess the data for training?
Thank you!

Yes, see https://github.com/brain-research/realistic-ssl-evaluation/blob/master/build_tfrecords.py


Reviewer Improvements required asap

There must be a feature called Project wise reviewer selection as well as service wise, because many a times different person is involved for different project and service. It shows all projects pending for review which create cumbersome list for them.

Service wise Reviewer is now available


Fix webclient.change_song_metadata

webclient.change_song_metadata been broken, and needs to be updated to use jsarray. I had removed it with the expectation that mobileclient.change_song_metadata duplicated it, but as of #209 that isn't true.

format=json appears to work now, and might make this significantly easier.

Can this be closed now as of #490? And I think #229 could be closed as well with the status given to the Webclient and the fact that it's been dead for over 2 years.

Fine by me.


docs: document cli usage

Document the usage of the CLI following a step by step case for each branch (e.g. dev, prod).

Blocked until https://github.com/ppanero/docs-invenio-rdm can be moved to the inveniosoftware organization and there is a place/domain to put it up.


JupyterHub picker item title consistency

Testing #14202
Here the title for the second item should say URL, not Url, to match the description

This issue just a hacky prototype at this stage


Always run pipeline on tags and nightly tests

This PR merges the same changes introduced for conjur at these PRs:
https://github.com/cyberark/conjur/pull/1946
https://github.com/cyberark/conjur/pull/1951
Recently, we introduced a change to skip running the CI tests when the
only changed files were markdown files, so that design doc and other
non-code PRs wouldn't block on the CI.
However, this had the unintended side-effect of skipping our nightly
builds, because the criteria for "only markdown files":
git diff origin/master --name-only | grep -v "^.*\.md$" > /dev/null'
will also always be true when a nightly build is auto-triggered.
This commit ensures that the nightly builds and tag release builds will always be run.
What ticket does this PR close?
Resolves #264
Checklists
Change log

[ ] The CHANGELOG has been updated, or
[x] This PR does not include user-facing changes and doesn't require a CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code changes, or
[x] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR, and/or there is a follow-on issue to update docs, or
[x] This PR does not require updating any documentation

What about trigger from conjur , it will work as well?

I guess not, since someone needs to add it explicitly.
@hughsaunders  - do you have a suggestion how to handle this?

@abrahamko I added 'upstreambuild' to getTrigger() so you can use that to determine if the build is caused by an upstream. https://github.com/conjurinc/jenkins-pipeline-library/blob/master/vars/getTrigger.groovy
expression { getTrigger() == "upstreambuild" }


Problem instantiating a module with a RECURSIVE operator

Hello!
Currently TLAPS does not handle recursive operators. But recursive operators and (unrelated) theorems can coexists in the same module without problem, i.e. we can have:
RECURSIVE f(_)
f(x) = ...

LEMMA ...  \* no problem if we invoke TLAPS here

However, i found that TLAPS crashes if a module where there is some recursive operator defined is instantiated, i.e. it seems we can't have:
--- A ---
RECURSIVE f(_)
f(x) = ...
---

--- B ---
INSTANCE A
LEMMA ...   \* error if trying to invoke TLAPS here
---

As a "workaround", commenting the recursive definition in module A when we want to use TLAPS in module B makes the problem disappear.
This behavior is undesirable because recursive operators are fine for the model checker and possibly other tools. If they are not supported then they should be ignored by TLAPS.

Note that while this fails at the semantic level, TLAPM fails much earlier during syntax parsing if given a RECURSIVE declaration inside a LET-IN block:
---- MODULE Test ----
op ==
  LET
    RECURSIVE f(_)
    f(n) == IF n =< 0 THEN 1 ELSE n * f(n-1)
  IN f(5)
====


[Container] disableGutters class not applied after migration to emotion

Container disableGutters not working properly.

[X] The issue is present in the latest release.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Gutters still applied codesandbox

Expected Behavior 🤔
No gutters codesanbox

Steps to Reproduce 🕹
Updated version from "@material-ui/core": "5.0.0-alpha.21" to "@material-ui/core": "5.0.0-alpha.22"

@povilass Ah, right, by bad. The property keeps its initial position:
{
    foo: '1',
    bar: '2',
    ...({ foo: '3' })
}

returns
{foo: "3", bar: "2"}

What do you think about this fix? :)
diff --git a/packages/material-ui/src/Container/Container.js b/packages/material-ui/src/Container/Container.js
index cb1c7413ca..f942a85ff6 100644
--- a/packages/material-ui/src/Container/Container.js
+++ b/packages/material-ui/src/Container/Container.js
@@ -50,16 +50,14 @@ const ContainerRoot = experimentalStyled(
     marginLeft: 'auto',
     boxSizing: 'border-box',
     marginRight: 'auto',
-    paddingLeft: theme.spacing(2),
-    paddingRight: theme.spacing(2),
     display: 'block', // Fix IE11 layout when used with main.
-    [theme.breakpoints.up('sm')]: {
-      paddingLeft: theme.spacing(3),
-      paddingRight: theme.spacing(3),
-    },
-    ...(styleProps.disableGutters && {
-      paddingLeft: 0,
-      paddingRight: 0,
+    ...(!styleProps.disableGutters && {
+      paddingLeft: theme.spacing(2),
+      paddingRight: theme.spacing(2),
+      [theme.breakpoints.up('sm')]: {
+        paddingLeft: theme.spacing(3),
+        paddingRight: theme.spacing(3),
+      },
     }),
   }),
   ({ theme, styleProps }) =>

@povilass Ah, right, by bad. The property keeps its initial position:
{
    foo: '1',
    bar: '2',
    ...({ foo: '3' })
}

returns
{foo: "3", bar: "2"}

What do you think about this fix? :)
diff --git a/packages/material-ui/src/Container/Container.js b/packages/material-ui/src/Container/Container.js
index cb1c7413ca..f942a85ff6 100644
--- a/packages/material-ui/src/Container/Container.js
+++ b/packages/material-ui/src/Container/Container.js
@@ -50,16 +50,14 @@ const ContainerRoot = experimentalStyled(
     marginLeft: 'auto',
     boxSizing: 'border-box',
     marginRight: 'auto',
-    paddingLeft: theme.spacing(2),
-    paddingRight: theme.spacing(2),
     display: 'block', // Fix IE11 layout when used with main.
-    [theme.breakpoints.up('sm')]: {
-      paddingLeft: theme.spacing(3),
-      paddingRight: theme.spacing(3),
-    },
-    ...(styleProps.disableGutters && {
-      paddingLeft: 0,
-      paddingRight: 0,
+    ...(!styleProps.disableGutters && {
+      paddingLeft: theme.spacing(2),
+      paddingRight: theme.spacing(2),
+      [theme.breakpoints.up('sm')]: {
+        paddingLeft: theme.spacing(3),
+        paddingRight: theme.spacing(3),
+      },
     }),
   }),
   ({ theme, styleProps }) =>

Not working also check

Not working also check

Probably should be like this code

Probably should be like this code

https://github.com/mui-org/material-ui/issues/24278#issuecomment-754681215 this wasn't the proposed patch.

https://github.com/mui-org/material-ui/issues/24278#issuecomment-754681215 this wasn't the proposed patch.

Yes but I applied your described change to a Container file maybe misunderstand something?

Yes but I applied your described change to a Container file maybe misunderstand something?

Nevermind missed 2 lines of code it's ok fix :D

Nevermind missed 2 lines of code it's ok fix :D

@povilass Great, thanks for the confirmation, feel free to get the regression fixed :)

@povilass Great, thanks for the confirmation, feel free to get the regression fixed :)

@oliviertassinari  ok one more thing just saw that while using maxWitdh=false with  "@material-ui/core": "5.0.0-alpha.21" does not have classes

But

And only classes defined are
const containerClasses = generateUtilityClasses('MuiContainer', [
  'root',
  'disableGutters',
  'fixed',
  'maxWidthXs',
  'maxWidthSm',
  'maxWidthMd',
  'maxWidthLg',
  'maxWidthXl',
]);

@oliviertassinari  ok one more thing just saw that while using maxWitdh=false with  "@material-ui/core": "5.0.0-alpha.21" does not have classes

But

And only classes defined are
const containerClasses = generateUtilityClasses('MuiContainer', [
  'root',
  'disableGutters',
  'fixed',
  'maxWidthXs',
  'maxWidthSm',
  'maxWidthMd',
  'maxWidthLg',
  'maxWidthXl',
]);

@povilass Interesting, no preferences, we could add the class name back.

@povilass Interesting, no preferences, we could add the class name back.

Something interesting happening to clsx if classes.disableGutters is undefined or classes.fixed is undefined

But both combination produces just first undefined?

Overall this probably should be changed to this.
const useUtilityClasses = (styleProps) => {
  const { classes = {}, fixed, disableGutters, maxWidth } = styleProps;

  const maxWidthClassName = `maxWidth${capitalize(String(maxWidth))}`;

  return {
    root: clsx(
      containerClasses.root,
      classes.root,
      typeof maxWidth === "string" && getContainerUtilityClass(maxWidthClassName),
      typeof maxWidth === "string" && classes[maxWidthClassName],
      fixed && containerClasses.fixed,
      fixed && classes.fixed,
      disableGutters && containerClasses.disableGutters,
      disableGutters && classes.disableGutters,
    )
  };
};

Reference playground

Something interesting happening to clsx if classes.disableGutters is undefined or classes.fixed is undefined

But both combination produces just first undefined?

Overall this probably should be changed to this.
const useUtilityClasses = (styleProps) => {
  const { classes = {}, fixed, disableGutters, maxWidth } = styleProps;

  const maxWidthClassName = `maxWidth${capitalize(String(maxWidth))}`;

  return {
    root: clsx(
      containerClasses.root,
      classes.root,
      typeof maxWidth === "string" && getContainerUtilityClass(maxWidthClassName),
      typeof maxWidth === "string" && classes[maxWidthClassName],
      fixed && containerClasses.fixed,
      fixed && classes.fixed,
      disableGutters && containerClasses.disableGutters,
      disableGutters && classes.disableGutters,
    )
  };
};

Reference playground

@povilass Nice, do you want to open a new issue for it? I have proposed a solution in https://github.com/mui-org/material-ui/pull/24250#issuecomment-753641789 for it.

@povilass Nice, do you want to open a new issue for it? I have proposed a solution in https://github.com/mui-org/material-ui/pull/24250#issuecomment-753641789 for it.

Pull request https://github.com/mui-org/material-ui/pull/24284

Pull request https://github.com/mui-org/material-ui/pull/24284


Automated Package Upgrade

:tada: This PR is included in version 2.2.183 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ORV2-1496 Change Payment gateway From MotiPay to PayBC

Description
This PR has changes for payment gateway. MotiPay is replaced by PayBC. FE redirect url has been changed. hash validation for PayBC response has been added.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Manually tested using Swagger.
[ ] Integration testing with Frontend.

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have already been accepted and merged

Further comments

a future suggestion for work like this (IMHO) would be to split out the OpenShift changes and just add any necessary ENV configs in the first PR on its own. Makes it much smaller. Then when work is merged to actually cutover and use the new ENV, make another small PR for cleanup of the unused. I dunno. Smaller PR's are always easier to get moving then larger ones.


eslint and React

I'm depending on this to be a peer of eslint:
    "eslint-plugin-react": "^2.0.2",

Otherwise, I get errors like this:
/Users/justin/j/react/react-webpack-rails-tutorial/client/assets/javascripts/Comment.jsx
  3:0  error  'import' and 'export' may appear only with 'sourceType: module'

You can reproduce this issue with this repo:
https://github.com/justin808/react-webpack-rails-tutorial
And running gulp lint
Compare to running the bin/lint script.
Basically, the issue comes down to how should sibling eslint dependencies be handled.

It appears that react-webpack-rails-tutorial has a direct dependency on the "react" plugin (eslint-plugin-react) within its .eslintrc file. Since the project has the direct dependency, it is currently correct to include it as a dependency in the package.json file.
When running bin/lint, I find the following included in the output:
Cannot read config file: [...]/react-webpack-rails-tutorial/client/.eslintrc
Error:  Unexpected token p

This suggests that, when bin/lint scans for an eslint command, it likely finds an old version of eslint that is unable to read the YAML .eslintrc and therefore doesn't load the "react" plugin.
Try checking the eslint version by adding the -v flag to the find command, like so:
find . -path ./node_modules -prune -o -name "*.js" -o -name "*.jsx" -exec eslint -v {} \;

This will repeat the eslint version number for each file it finds.
If bin/lint is updated to use a local install of eslint, the results are the same as gulp-eslint.
node_modules/eslint/bin/eslint.js .

In fact, you can even remove the direct dependency on eslint and just use gulp-eslint as long as you have the eslint-plugin-react dependency included in your project.json.

Since the issue is not with gulp-eslint, I'm closing this. Let me know if you need any further detail.


Add AppSync perms to lambda function

Note: If your feature-request is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Is your feature request related to a problem? Please describe.
I am accessing the graphql api this way:
const AWSAppSyncClient = require('aws-appsync').default;

// on the handler

const client = new AWSAppSyncClient({
  url: process.env.API_WRGDGRAPHQLAPI_GRAPHQLAPIENDPOINTOUTPUT,
  region: process.env.REGION,
  disableOffline: true,
  auth: {
    type: 'AWS_IAM',
    credentials: AWS.config.credentials
  }
});

Then I can do:
client.mutate({ mutation, variables });

or
client.query({ quer, variables });

But the problem is, if I add the graphql api to the resource access list of the lambda function, it doesn't add the other necessary appsync permissions:
{
  "Effect": "Allow",
  "Action": [
    "appsync:GraphQL"
  ],

But it needs to be:
{
  "Effect": "Allow",
  "Action": [
    "appsync:Create*",
    "appsync:StartSchemaCreation",
    "appsync:GraphQL",
    "appsync:Get*",
    "appsync:List*",
    "appsync:Update*",
    "appsync:Delete*"
  ],

So I have to manually add this, which is a VERY BAD THING because when I do update function and change the api access, this will be rewritten, the best way is for amplify to offer a way to add these perms because amplify itself is modifying these files.
Describe the solution you'd like
Something like amplify update function then AppSync is one of the options OR add these perms by default when I give a function API access.
Describe alternatives you've considered
N/A
Additional context
N/A

The IAM role permission that amplify cli generate has changed.  I have confirm this was changed as early as 4.41.2 and confirmed it is still broke in 4.44.0
Currently the amplify cli generate function api permissions in -cloudformation-template.json as:
 {
              "Effect": "Allow",
              "Action": [
                "appsync:GraphQL"
              ],
              "Resource": [
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:appsync:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":apis/",
                      {
                        "Ref": "apiknotGraphQLAPIIdOutput"
                      },
                      "/types/create/*"
                    ]
                  ]
                },
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:appsync:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":apis/",
                      {
                        "Ref": "apiknotGraphQLAPIIdOutput"
                      },
                      "/types/read/*"
                    ]
                  ]
                },
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:appsync:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":apis/",
                      {
                        "Ref": "apiknotGraphQLAPIIdOutput"
                      },
                      "/types/update/*"
                    ]
                  ]
                },
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:appsync:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":apis/",
                      {
                        "Ref": "apiknotGraphQLAPIIdOutput"
                      },
                      "/types/delete/*"
                    ]
                  ]
                }
              ]
            },

Previous amplfiy cli versions generated:
  {
              "Effect": "Allow",
              "Action": [
                "appsync:Create*",
                "appsync:StartSchemaCreation",
                "appsync:GraphQL",
                "appsync:Get*",
                "appsync:List*",
                "appsync:Update*",
                "appsync:Delete*"
              ],
              "Resource": [
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:appsync:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":apis/",
                      {
                        "Ref": "apiknotGraphQLAPIIdOutput"
                      },
                      "/*"
                    ]
                  ]
                }
              ]
            }

I think this issue is a duplicate of #6595

@thibaultdalban yes this is a duplicate.  I'll add my comment over there.

Thanks guys, hopefully gets fixed soon 🙇🏻

@attilah do you have bandwidth to tackle this?

Providing an update here
It looks like it's generating the old policy format if the feature flag is not set to true. If you set the feature flag to true and update the flow again it will use the new graphql operation list as opposed to the crud list. Put up a pr to maintain the FF use when creating the iam policy for appsync.
PR #6273

@SwaySway The PR linked above is another issue. Is there an open PR that resolves this AppSync issue?

Any idea when this is going to be fixed? This was working fine before... @attilah @SwaySway What needs to be done to be able to access graphql in a lambda function again..? I'm not really wanting to add crazy custom cloud formation template workarounds :/

I am running into the same issue. Hopefully the PR gets merged asap.

@renegoretzka I added a custom amplify resource to amend the lambda execution policies to unblock myself. I too hope they fix this soon! It was working perfectly in previous versions.

@renegoretzka I added a custom amplify resource to amend the lambda execution policies to unblock myself. I too hope they fix this soon! It was working perfectly in previous versions.

How did you solve it exactly? I also would like to continue translating my App from the AppSync API to DataStore. @kylekirkby

@renegoretzka
It's a bit hacky but it's a workaround 🤷♂
https://serverlessstartup.hashnode.dev/amending-aws-amplify-lambda-permissions-with-a-custom-cloudformation-template

Still seems to be an issue. @SwaySway's solution here fixed this for me: https://github.com/aws-amplify/amplify-cli/issues/6595#issuecomment-777755187
I'm on 4.45.2. Before adding generateGraphQLPermissions I was getting the following in my CF template:
{
  "Effect": "Allow",
  "Action": [
    "appsync:GraphQL"
  ],
  "Resource": [
    {
      "Fn::Join": [
        "",
        [
          "arn:aws:appsync:",
          {
            "Ref": "AWS::Region"
          },
          ":",
          {
            "Ref": "AWS::AccountId"
          },
          ":apis/",
          {
            "Ref": "apiturnspeedGraphQLAPIIdOutput"
          },
          "/types/create/*"
        ]
      ]
    },
    {
      "Fn::Join": [
        "",
        [
          "arn:aws:appsync:",
          {
            "Ref": "AWS::Region"
          },
          ":",
          {
            "Ref": "AWS::AccountId"
          },
          ":apis/",
          {
            "Ref": "apiturnspeedGraphQLAPIIdOutput"
          },
          "/types/read/*"
        ]
      ]
    },
    {
      "Fn::Join": [
        "",
        [
          "arn:aws:appsync:",
          {
            "Ref": "AWS::Region"
          },
          ":",
          {
            "Ref": "AWS::AccountId"
          },
          ":apis/",
          {
            "Ref": "apiturnspeedGraphQLAPIIdOutput"
          },
          "/types/update/*"
        ]
      ]
    },
    {
      "Fn::Join": [
        "",
        [
          "arn:aws:appsync:",
          {
            "Ref": "AWS::Region"
          },
          ":",
          {
            "Ref": "AWS::AccountId"
          },
          ":apis/",
          {
            "Ref": "apiturnspeedGraphQLAPIIdOutput"
          },
          "/types/delete/*"
        ]
      ]
    }
  ]
}


[Migration] How to handle URLs / permalinks is there a way to match Drupal

The URL matching works, if two conditions are fullfilled:
1.) During the migration the checkbox must be enabled: SEO - Create redirects for URLs
2.) Language format for WP URLs: Select "Different languages in directories"
If these two conditions are fullfilled, the URL redirection works, e.g.:

Drupal URL https://www.scienceinschool.org/fr/2007/issue5/plastics
Will be redirected to https://dev-science-in-school.pantheonsite.io/fr/2007/11/13/plastics-2/
The URL is different, but the HTTP Response code is correct (301) and the user is properly redirected.


Use type name in RedisMessage error instead of RESP3 character

This change is made to address issue 127. Currently when a no-op type conversion happens as a result of calling To* or As* the error message produced looks like this
panic: redis message type : as map key is not supported

The RESP3 character that represents a 64 bit integer ':' is shown to be reason for the panic
With the current change applied, the error message would now look like this
panic: redis message type int64 as map key is not supported

Current unit tests are covering the changes to the error messages in message.go, let me know if more tests are desired to add to coverage of the different types.
Notes for maintainers:
For this PR I decided to keep the change small while still addressing the root problem. I see that there is quite a bit of usage of RESP3 characters throughout the library, I could sub those in for these constants if that's asked of me (In this PR or a few others).
Also I left unit tests message_test.go and resp_test.go as is in terms of RESP3 characters instead of swapping in the new constants due to creating a massive diff that would be hard to review, but I could I also get that done if that's wanted.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.01 :tada:

Comparison is base (71bd05f) 97.49% compared to head (67a6bc3) 97.51%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
+ Coverage   97.49%   97.51%   +0.01%
==========================================
  Files          69       69
  Lines       29356    29373      +17
==========================================
+ Hits        28622    28642      +20
+ Misses        615      612       -3
  Partials      119      119

Impacted Files
Coverage Δ

message.go
100.00% <100.00%> (ø)

resp.go
100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks @kevinxmorales! LGTM


Design the specification for the semvar enforcing tool for Ballerina APIs

Description:
$subject
Task 1 of the related issue. Once an initial draft is designed it can be reviewed and the final version could be derived iteratively.
Related Issues (optional):
#32368

Link to the initial design specification: https://docs.google.com/document/d/1YowcycsEcO0K67sYBAb_Gz1slFVf5CnCkgkOnMMKcSo/edit?usp=sharing

Closing since the proposed specification is available at https://docs.google.com/document/d/1STs91QTXrvivfcowGltOtoYCRlgJheGPay56G3cWuxM/edit?usp=sharing. Created https://github.com/ballerina-platform/ballerina-spec/issues/1070 to review to track the progress on reviewing and adding to the ballerina-spec repository.


Legends Quest Bravery Potion

The description in the step "To The Source" states Climb down the winch.
In order to do this you need to drink the bravery potion made in the first step of "To The Source" then try to climb down.


Alias and ISO 8859-1 encoding: "ToLower: bad conversion", "ToLower: wstring_convert::from_bytes"

I'm getting errors in command aliases since 3.3.0.
For example, this code:
CMD:test(playerid, params[])
{
	SendClientMessage(playerid, -1, "OK");
	return 1;
}

alias:test("tést", "teñst")

Works fine on a gamemode/filterscript with UTF-8 encoding. But in a ISO 8859-1 encoding gamemode it returns these errors:

"ToLower: bad conversion" (Windows)
"ToLower: wstring_convert::from_bytes" (Linux)

And the callback OnPlayerCommandReceived sometimes cuts the cmd[] string. So, if the command it's something like /hellowórld, the callback returns a cmd[] string like hellow.
I tried using LocaleName = "es_ES.ISO8859-1" in pawncmd.cfg but it does nothing.

Works fine on a gamemode/filterscript with UTF-8 encoding. But in a ISO 8859-1 encoding gamemode it returns these errors

Why can't you just use UTF-8 encoding?

Try that, please.
pawncmd.zip (commit https://github.com/urShadow/Pawn.CMD/commit/01a9ae4219e74302853c74fdc9e4723421530f67)

Try that, please.
pawncmd.zip (commit 01a9ae4)

That works perfect with the properly LocaleName configuration in pawncmd.cfg.
It seems to be solved. Great job!

Fixed.
https://github.com/urShadow/Pawn.CMD/releases/tag/3.3.3


Add documentation

We still use README.md to record about doc, with increasing support statement readme would be large and user could not easy to find what their want, so I thinks it better to add documentation on it.
beside that, we could also record developement  part and covert detail on it

fix https://github.com/WhaleOps/airphin/pull/16


Form doesn't validating date picker

Describe the bug
Hi guys, I'm not sure if this issue duplicate or not.
as title says, if youre using datepicker in the formItem it will get ignored if it has rules
Steps to reproduce

create minimal form component
use datepicker inside formitem
set required rules for datepicker
set path , value etc
validate
datepicker will shown error even if its not null

Link to minimal reproduction
https://codesandbox.io/p/sandbox/stoic-cache-52lhts?file=%2Fsrc%2FDemo.vue%3A16%2C1
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
    Memory: 6.64 GB / 15.87 GB
  Binaries:
    Node: 18.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.7.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    naive-ui: ^2.39.0 => 2.39.0
    vue: ^3.4.37 => 3.4.38

Used Package Manager
npm
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

trigger: ['blur', 'change']

@jahnli hi, I update the minimal repro. it stills ignore datepicker, maybe i missed something, im not sure.

date: {
          type: "number",
          required: true,
          message: "Please input your date",
          trigger: ["blur", "change"],
        },

https://www.naiveui.com/zh-CN/os-theme/components/form#left.vue  对照官网例子

Ahhh I missed the type, thanks a lot!


Workspace files should include full path in prompt

Currently get_workspace_prompt gives the files from gptme.toml with the prefix ```{filename}. It would perhaps be better if it gave the path rather than just the filename, so the LLM is more aware of which file the contents are from. Especially considering files can often have the same name e.g. README.md.

Fixed in #330

Fixed in #330

Nice. Just noticed a similar issue that I'm not sure how much of an issue it is. In some of my included markdown files there is code examples using triple backtick, but since the files included in the prompt use triple backtick it becomes unclear when the file ends and when the code example from within the file begins. Perhaps using something other than triple backtick for the files would be better.

@Miyou Yeah I use XML-formatting in gptme-rag output for this reason:
<file path="...">
(content)
</file>

Might be worth doing for the context message and such too.


typo in the last code snippet, should be Authorizer and not Authoize

[Enter feedback here]
typo in the last code snippet, should be Authorizer and not Authoize

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 496addbb-39f0-09cd-4fc9-c5786bb90495
Version Independent ID: 53cd2418-bd7b-b469-8d34-f9f2f7fd1b8f
Content: Authentication with the Azure SDK for Go
Content Source: articles/go/azure-sdk-authorization.md
Service: azure
GitHub Login: @barbkess
Microsoft Alias: barbkess

@elraikhm thanks for the feedback! We'll get that fixed.


Add Add hierarchy for Epics and Features

Enhancement: For businesses this could be great for predefined epics with mandatory features and features that have predefined mandatory PBI’s/User Stories.
1 Click task could add templates from Features to 1 Epic
1 Click task could add templates for PBI’s/User to 1 Feature

Hi, thanks for your suggestion.
I have created a new extension, please check
1-Click Child-Links


feat: upgrade go 1.18 to 1.18.10

Regular updates to go version: upgrade go1.18 from 1.18.5 to 1.18.10.

/lgtm


Option <> ScVal requires infallible conversions but shouldn't

It appears that the Option type only has conversions to ScVal as infallible, and therefore only has conversions for versions of T that are also infallible:
https://github.com/stellar/rs-stellar-xdr/blob/8b9d623ef40423a8462442b86997155f2c04d3a1/src/curr/scval_conversions.rs#L507-L529
This makes the use and compatibility of Option as a Soroban type limited, since many other types are only convertible through the Try interface because they can error.
Custom types only require TryFrom and not From.
Option should be implemented for TryFrom, instead of From, so that it is usable in custom types with a wider variety of T's.
Related discussion:

https://discord.com/channels/897514728459468821/1134537602800828576/1207419634215690242

Introducing TryFrom conversions for Option may have some conflicts on other trait impls, so we'll need to test the change that attempts to fix this up most of the stack up to at least the SDK.


PAPP-22689 Mark Microsoft Azure Compute as fips compliant

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Integration test fail due to timeout: create another pipeline in Gitlab
https://cd.splunkdev.com/phantom-apps/app-tests/-/pipelines/5218774

New pipeline passed with changes: https://cd.splunkdev.com/phantom-apps/app-tests/-/pipelines/5221579


test(batch): support hive catalog for iceberg source

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Add hive integration test for iceberg source.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

https://buildkite.com/risingwavelabs/integration-tests/builds/682


Updated bootstrapper to resolve required legal entity context

Codecov Report

Merging #461 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #461      +/-   ##
==========================================
- Coverage   99.42%   99.42%   -0.01%
==========================================
  Files          71       71
  Lines        1919     1914       -5
  Branches      306      305       -1
==========================================
- Hits         1908     1903       -5
  Misses         11       11

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
95.98% <100%> (-0.08%)
:arrow_down:

#srcapp
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

runtime/bootstrapper.ts
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8fb4c9b...0d5601c. Read the comment docs.


Full run of variation_identity from 2023-04-10 does not complete

It runs through almost all of the records fine, but stops with 10-20 to go. Main upmap+doseq loop never exits, the CPU is essentially idle, and no more logs are printed, it just hangs forever. Unclear what the issue is because no exceptions are logged that indicate an issue.
Maybe an exception in a thread in the claypool threadpool that isn't surfaced? It's not the http retry loop either, since that has a log statement in it and that isn't present in the log file.

Resolved by https://github.com/clingen-data-model/clinvar-gk-pilot/commit/0836b7358bcc37a9b2f4597d82a02a3de74ae936


Go Sass

Move from CSS to Sass.
Which means redoing the whole design.
Idea: should we implement Bulma for general classes like display, font sizes, margins, padding, etc? If we do, we would only upload needed css obviously to not overload project.
What do you think @gaeVG?

Idea: should we implement Bulma for general classes like display, font sizes, margins, padding, etc?

Why Bulma? A preference or a technical superiority? When I saw this I thought of Tailwind which is obviously very flexible and allows you to use only what you need

Idea: should we implement Bulma for general classes like display, font sizes, margins, padding, etc?

Why Bulma? A preference or a technical superiority? When I saw this I thought of Tailwind which is obviously very flexible and allows you to use only what you need

Because they all work the same? Bulma, Bootstrap, Tailwind: you can download only the classes you need. Tailwind is actually the only I never used so...

It seems to me that with Tailwind it is possible, and easy, to select only what interests us, I don't know if Bulma is able to do the same thing...

Should we list the advantages and disadvantages of both perhaps?

Yep, can do the same with Bulma: https://bulma.io/documentation/overview/modular/
I think Tailwind would be better if we'd plan to use it for styling, but we're not. Not sure it's worth a debate to only use it for display, margins, etc.
My idea was to use a framework to access general classes and make sure we don't repeat any css.
The rest will be stored in sass variables anyway. Or we just do everything in variables.
So if I could avoid learning another css framework when I know how to use 2 and actually don't like them, it would make me happy :)
However, if you think even for that use Tailwind is a better choice, I'll trust you and we'll go for it!

That's just it, I don't know!I was just talking about Tailwind because I know that he has that use too, but if you say that Bulma will do, then let's go! I just don't want us to make default choices just because we've mastered the subject, but because it's best for the project 🤗

@gaeVG I'm starting to install sass in the project. However, I realised that I'm gonna need to do a little bit of refactoring and change the source of imports, etc. But if I do that before you start the refactoring of components, we're gonna face some annoying merging issues. Can you let me know when your done with your end of the matter so I can handle my part?

Sass has been installed and set up. Good to go for designing


Unable to use theme colours for certain theme variant props

Unable to use theme colours for certain theme variant props. Specifically, using a theme colour in color to set the input text color works as expected, but using a theme colour in caretColor does not work
eg:
forms {
  input: {
    normal: {
      color: 'primaryText'
      caretColor: 'primaryAccent',
      lineHeight: 'normal',
      px: 3,
      height: 80,
      fontSize: 'l',
    },
  },
}

Note, it works fine if I pass a raw hex colour code, like caretColor: '#fd9800'.

Only certain CSS properties are mapped to the theme scales by default, and caret-color is not one of them. You can use a function as a value to work around this, e.g. caretColor: t => t.colors.primaryAccent

Can functions be used like that in theme variant definitions?

It should work, yes.

Confirmed, thanks!


Questoin about tx-pps

Hello,
I am new to dperf. Thank you for maintaining great tool.

I would like to test 1 MPPS, 2 MPPS, etc by gradually increasing the rate.
Is it possible to control pps rate on TX side?
I am currently explore flood under performance/tx-pps and seems like cc can control it.
There are multiple parameters like cc, cps, and keepalive, slow_start.
Even udp has slow start and keepalive features?
Is tx-pps the best option to test it?
I am using dperf on TX side and testpmd on RX side. (one direction)

If I can measure round-trip pps (bi-directional) to check packet loss, what is the best option in dperf and which one should I take a look under test directory?

Are there any docs or articles to understand these parameters in details?

Thanks,

Hello,
I am new to dperf. Thank you for maintaining great tool.

I would like to test 1 MPPS, 2 MPPS, etc by gradually increasing the rate.
Is it possible to control pps rate on TX side?
yes. pps = cc *  ( 1s / keepalive-interval)
I am currently explore flood under performance/tx-pps and seems like cc can control it.
There are multiple parameters like cc, cps, and keepalive, slow_start.
Even udp has slow start and keepalive features?
see more about keepalive  https://dperf.org/doc/html/configuration#section5

Is tx-pps the best option to test it?
use 'cc', 'keepalive', etc to control it.
I am using dperf on TX side and testpmd on RX side. (one direction)
please use dperf at both side.
2. If I can measure round-trip pps (bi-directional) to check packet loss, what is the best option in dperf and which one should I take a look under test directory?
dperf.org

Are there any docs or articles to understand these parameters in details?
dperf.org

Thanks,


Get rid of version mechanism.

Since we've redesigned the interaction between HIL and obmd, we don't need the somewhat complicated versioning mechanism. This patch simplifies the API.
The HIL spec we merged was vague enough wrt. how invalidation worked that I don't think this introduces anything that would need changing; it's meant to work with that design.
Note that this is built on top of #2, so it's got those commits in it as well.
//cc @naved001, @knikolla

@naved001, your comments have been addressed.


Lofi button

It's a lofi button. You get lofi when you press it. nuff said

Turns out Lofi Girl provides a commercial license!
https://form.lofigirl.com/CommercialLicense
So it is potentially possible to stream here. We'd have to ask if they provide some kind of API, but I don't think it's available.

Okay I emailed them. We'll see.


TensorBoard Projector has been blocked by CORS policy: No 'Access-Control-Allow-Origin'

At http://projector.tensorflow.org/ website error.
System information

Have I written custom code:
no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
macOS 10.13.3,
Safari: Version 11.0.3 (13604.5.6)
Chrome: Version 63.0.3239.132 (Official Build) (64-bit)
TensorFlow installed from (source or binary):
no

I am trying to publish my data over official projector.tensorflow.org website.

Prepared: config, data, metadata.
Hosted them on (Gist/google storage/my own website)
With and without https.
Trying to view on projector: Published config

Receive error: Failed to load cut: Redirect from 'cut' to 'cut' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://projector.tensorflow.org' is therefore not allowed access.

There is way to launch chrome with --disable-web-security key, but that ruins idea to share data in public.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Hi,
Sorry for the delay here. Seems like the error is due to the fact that gist.github.com/VolodymyrPavliukevych/... redirects to gist.githubusercontent.com/VolodymyrPavliukevych, and the latter one has Access-Control-Allow-Origin: * in the header.
Try updating the tensorPath and metadataPath in your config.json to point to gist.githubusercontent.com instead of gist.github.com.
Hope this helps!

Hi, thanks for explanation. It works.
I have one more question, why I can't share on my own web site or Google storage?
The same error on projector.
Is that because I have to add "access-control-allow-origin:*" in headers at my hosting?

That's correct, the server that hosts your website should serve with "access-control-allow-origin:*", which is unusual for out-of-the-box hosting, since it's not an API service.


liveness e2e test is flaky

63/78% passing for last 100 runs on jenkins. Test itself is likely racy.

I wasn't sure if this was the test or not: #4406.

Should this be part of a rewrite in go?

Seems like work on this should definitely wait for the in-flight PR on #4253

I was looking at this today.
Here's a doc of my quest:
https://docs.google.com/a/google.com/document/d/1UBNp-0_3LV9-3LmsWbRGU7FTyuKCwS9IqiCS4Xqk5LQ/pub
For Googlers, you should be able to directly comment on the doc:
https://docs.google.com/document/d/1UBNp-0_3LV9-3LmsWbRGU7FTyuKCwS9IqiCS4Xqk5LQ/edit#
tl;dr: I think this is because our heavy stock pods (e.g. elasticsearch) are taking so long to come up, and we aren't waiting for them, that e2e tests that schedule pods can fail. A fix is to have the e2e test driver wait until all of a clusters' pods are "running" before starting to run tests. I'll be working on fully verifying and then fixing this.

That sounds similar to what @alex-mohr raised in #4566.

Just as an update, doing this in hack/e2e.go but requiring utils from e2e package which breaks because of flags, refactoring is a mess because of other helpers using cross-file globals for test settings. So, this is "done" but requires more pluming to be PR-able. WIP...

Can't you do this entirely in shell, in hack/e2e-internal/e2e-status.sh?
On Thu, Feb 19, 2015 at 4:04 PM, Maxwell Forbes<EMAIL_ADDRESS>wrote:

Just as an update, doing this in hack/e2e.go but requiring utils from e2e
package which breaks because of flags, refactoring is a mess because of
other helpers using cross-file globals for test settings. So, this is
"done" but requires more pluming to be PR-able. WIP...
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4501#issuecomment-75165529
.

Closed via #5135


regression: attributes double on rustfmt

I just did updated to latest rustfmt and now running it on files with attributes duplicate the attributes; not sure if all of them, but at least some of them.
Here's a repro using test files on master:
$ rustfmt tests/target/attrib.rs
$ git diff
diff --git a/tests/target/attrib.rs b/tests/target/attrib.rs
index ed152a8..0c69e23 100644
--- a/tests/target/attrib.rs
+++ b/tests/target/attrib.rs
@@ -52,10 +52,11 @@ struct Foo {
 // #1668

 /// Default path (*nix)
-#[cfg(all(unix, not(target_os = "macos"), not(target_os = "ios"), not(target_os = "android")))]
+#[cfg(all(unix, not(target_os = "macos") ), not(target_os = "ios") ),
+            not(target_os = "android")))]
 fn foo() {
     #[cfg(target_os = "freertos")]
-    match port_id {
+    #[cfg(target_os = "freertos")] match port_id {
         'a' | 'A' => GpioPort { port_address: GPIO_A },
         'b' | 'B' => GpioPort { port_address: GPIO_B },
         _ => panic!(),

This looks like a dup of #1668 which was fixed by #1669, but perhaps it is a related bug, not the same one. Could you check if your master branch includes the fix please?

Yeah, I cannot repro on dev builds on master NOR tag 0.8.6. But repros from rustfmt:0.8.6 installed by cargo install. Anyways, looks like a dup, so I'm closing.


Importing shogun makes python irresponsive to KeyboardInterrupt

As soon as I import shogun in python, it does not respond to Ctrl+c any more.
I am testing it with this simple code:
import shogun
import time
time.sleep(10)

Which version of Shogun are you using? This was a known issue (see https://github.com/shogun-toolbox/shogun/issues/4201) and it is was fixed in the most recent versions of Shogun. I suggest you to try to use the current development branch (develop) which will have the fix.

I was using the latest release (6.1.3), which did not include the fix.
I tried using the latest commit from develop branch and it does not ignore KeyboardInterrupt anymore and prints this:
[ShogunSignalHandler] Immediately return to prompt / Prematurely finish computations / Pause current computation / Do nothing (I/C/P/D)?

Which is expected. But is there a way to recover the normal behavior of KeyboardInterrupt i.e. not being handled by shogun?

Yes, it is possible to use the standard handler. In order to do that, you just need to add to your file the following line:
import shogun
shogun.get_global_signal().enable_handler(False)

It worked. Thanks.


Configure c8 to not report coverage for index.ts and types fiels.

Not sure if this is possible.
A temporary solution is to reply on branch and statement coverage as accurate metrics and then use c8 ignore to ignore the required files. c8 does not recognize that this is as excluding the file from testing.

c8 says that using the "exclude" flag in the testing or reporting step should do this, but it doesn't seem to be working.

Turns out that including the --all flag in the c8 command overrides ignore statements.


add itemid in i2i

 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.


Merge dev to master

IBM Cloud toolchain: Delivery Pipeline deployed orders to nyu-devops, including commit f54e0f404ab8c100cd423ef374fb182032721b5a


HDFS-17402. StartupSafeMode should not exit when resources are from l…

Description of PR
Refer to HDFS-17402.
After HDFS-17231, NameNode can exit safemode automatically when resources are from low to available. It used org.apache.hadoop.hdfs.server.namenode.FSNamesystem#leaveSafeMode, this function will change BMSafeModeStatus. However, NameNode entering resource low safe mode doesn't change BMSafeModeStatus in org.apache.hadoop.hdfs.server.namenode.FSNamesystem#enterSafeMode. This is not equal
Now:
a. NN enter StartupSafeMode
b. NN enter ResourceLowSafeMode
c. NN resources from low to available
d. NN safemode off
Expectations：
a. NN enter StartupSafeMode
b. NN enter ResourceLowSafeMode
c. NN resources from low to available
d. NN exit ResourceLowSafeMode but in StartupSafeMode
How was this patch tested?
Add UT
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m  6s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 39s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 12s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 44s

trunk passed

+1 :green_heart:
shadedclient
20m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 28s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  2s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 44s

the patch passed

+1 :green_heart:
shadedclient
20m 38s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
198m 13s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

286m 27s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6618/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6618

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 92963e9ffb69 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 21fb4a3fb7d6153f6c54f8486f600e8f6ac97532

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6618/1/testReport/

Max. process+thread count
3962 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6618/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 00s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
96m 45s

trunk passed

+1 :green_heart:
compile
6m 36s

trunk passed

+1 :green_heart:
checkstyle
5m 03s

trunk passed

+1 :green_heart:
mvnsite
7m 14s

trunk passed

+1 :green_heart:
javadoc
6m 33s

trunk passed

+1 :green_heart:
shadedclient
155m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 46s

the patch passed

+1 :green_heart:
compile
3m 55s

the patch passed

+1 :green_heart:
javac
3m 55s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 28s

the patch passed

+1 :green_heart:
mvnsite
4m 23s

the patch passed

+1 :green_heart:
javadoc
3m 40s

the patch passed

+1 :green_heart:
shadedclient
163m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 39s

The patch does not generate ASF License warnings.

444m 09s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6618

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
MINGW64_NT-10.0-17763 e13068a72d28 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 21fb4a3fb7d6153f6c54f8486f600e8f6ac97532

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6618/1/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6618/1/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


A question about shared weights in RNN

Hi,
I have a question about how weights are shared in RNN unrolled. I notice that since the weights in every timestamp are the same, so these weights are represented by the same variable in the rnn example. My question is when we do back propagation, how the gradients are computed? Since the gradient variables correspond to the arguments, I only get one gradient variable for each weight. So does it mean this gradient is calculated by taking weights in every time stamp in consideration and I only need to update the weight once using this gradient?

Yes you're right. It follows the mathematical derivation of the gradient.


Ability to publish as participant similar to go sdk

unfortunately this isn't possible. There isn't a viable WebRTC stack for Node for it to provide participant functionalities.