Uncaught SyntaxError: Unexpected token )

Whether I use the 0.10 release or git clone master, I get errors like this in the DOM:
Uncaught SyntaxError: Unexpected token )
index.js:641 Creating new search session for query ""
index.js:244 Uncaught TypeError: Cannot read property 'getAspect' of undefined
    at Object.getAspects_ (index.js:244)
    at Object.render (index.js:178)
    at p._renderValidatedComponentWithoutOwnerOrContext (react-dom.min.js:11)
    at p._renderValidatedComponent (react-dom.min.js:11)
    at performInitialMount (react-dom.min.js:11)
    at p.mountComponent (react-dom.min.js:11)
    at Object.mountComponent (react-dom.min.js:12)
    at performInitialMount (react-dom.min.js:11)
    at p.mountComponent (react-dom.min.js:11)
    at Object.mountComponent (react-dom.min.js:12)
    at i (react-dom.min.js:12)
    at r.perform (react-dom.min.js:13)
    at s (react-dom.min.js:12)
    at r.perform (react-dom.min.js:13)
    at Object.batchedUpdates (react-dom.min.js:12)
    at Object.a [as batchedUpdates] (react-dom.min.js:12)
    at Object._renderNewRootComponent (react-dom.min.js:12)
    at Object._renderSubtreeIntoContainer (react-dom.min.js:12)
    at Object.render (react-dom.min.js:12)
    at render (perkeep.privte.ch/:109)
    at perkeep.privte.ch/:113
react-dom.min.js:11 Uncaught TypeError: Cannot read property '_currentElement' of null
    at p._updateRenderedComponent (react-dom.min.js:11)
    at p._performComponentUpdate (react-dom.min.js:11)
    at p.updateComponent (react-dom.min.js:11)
    at performUpdateIfNecessary (react-dom.min.js:11)
    at Object.performUpdateIfNecessary (react-dom.min.js:12)
    at s (react-dom.min.js:12)
    at r.perform (react-dom.min.js:13)
    at o.perform (react-dom.min.js:13)
    at o.perform (react-dom.min.js:12)
    at Object.k [as flushBatchedUpdates] (react-dom.min.js:12)
    at r.closeAll (react-dom.min.js:13)
    at r.perform (react-dom.min.js:13)
    at Object.batchedUpdates (react-dom.min.js:12)
    at Object.u [as enqueueUpdate] (react-dom.min.js:12)
    at r (react-dom.min.js:12)
    at Object.enqueueForceUpdate (react-dom.min.js:12)
    at Object.r.forceUpdate (react-with-addons.min.js:10)
    at Object.<anonymous> (index.js:644)
    at cam.SearchSession.goog.events.EventTarget.fireListeners (eventtarget.js:284)
    at Function.goog.events.EventTarget.dispatchEventInternal_ (eventtarget.js:381)
    at cam.SearchSession.goog.events.EventTarget.dispatchEvent (eventtarget.js:196)
    at cam.SearchSession.searchDone_ (search_session.js:284)
    at cam.ServerConnection.handleXhrResponseJson_ (server_connection.js:161)
    at goog.net.XhrIo.goog.events.EventTarget.fireListeners (eventtarget.js:284)
    at Function.goog.events.EventTarget.dispatchEventInternal_ (eventtarget.js:381)
    at goog.net.XhrIo.goog.events.EventTarget.dispatchEvent (eventtarget.js:196)
    at goog.net.XhrIo.onReadyStateChangeHelper_ (xhrio.js:868)
    at goog.net.XhrIo.onReadyStateChangeEntryPoint_ (xhrio.js:814)
    at goog.net.XhrIo.onReadyStateChange_ (xhrio.js:798)

Any idea what the problem is?  Thanks.

@elimisteve hey. I cannot reproduce. Can you give more detail please?
Like, the browser you're using. And what were the circumstances? what were you trying to do in the web UI?

I get this error when visiting /ui in Chromium 57 on Linux, but there's no error on Firefox 60 nor Chrome 70 (all on Linux).

How old is chromium 57? (i.e. is this error actually worth spending time on?)

https://en.wikipedia.org/wiki/Google_Chrome_version_history says 2017-03-09 -- 21 months ago.
Chromium 57 is the default on Debian 8.7.  If I need to use Firefox to use the Perkeep UI, then it's not the end of the world :-) ; sounds like an issue with the build system only building for newer browsers?

Hmm given that Jessie is supported until 2020, we should support it.
However, can you not install a newer chrome through the official google repo, instead of the debian one (i.e. deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main)?
it's what i do on my ancient ubuntu (trusty), which allows me to run Chrome 67 without any problem.
I have not looked into it, but fwiw, I think the issue is that a js or dom feature is not supported on your older chrome, rather than a build problem.

It seems that this issue can be closed right now based on comments here :)

@adrm Fine by me :+1: Closing.


Placement option for both popper and target element?

Hi guys, I'm considering migrating my project to Popper from Tether (because Popper doesn't change the DOM the way Tether does, which has been causing me problems), but it doesn't seem to provide some of the basic functionality that Tether (and jqueryui's position plugin) does, which is to allow for alignment information for both the source and the target elements.
Let's say, for example, that I want my source element's top left corner to meet the bottom right corner of the target. It's easy with Tether:
http://jsfiddle.net/nngLr41a/25/
With popper, it doesn't seem possible:
https://codepen.io/shmax71/pen/pPbadO
With Tether (and jqueryui), there are 81 different arrangement possibilities between the two operands, but with Popper there are only 9 12.
Do I have that right? Or am I missing something in the documentation?
Thanks for your time.

You may use the offset modifier providing a value of 100%p.
I'm from my smartphone now and I'm not able to give you a working example. I'll follow up tomorrow morning.

But that's not really the same thing at all, is it? Yes, the end result is the same with these particular conditions, but that's not really addressing the spirit of the thing. With your approach I would have to manually twiddle the offset every time I wanted to change the height of one of my operands, but with the other libraries it's not necessary (though they support offsets as well).

Hmm, I had another look at your offset documentation--I didn't notice that it supports percentage offsets to both the element and the target. I'll await your sample, thanks.

That's it:
https://codepen.io/FezVrasta/pen/XRKPOY

Thanks, that's helpful. I'll work with this a bit and see if I can achieve the same kind of effects I was getting with Tether. Closing for now...

One more thing: how would I add a little constant spacing between the two shapes? With Tether, it looks like this:
http://jsfiddle.net/nngLr41a/26/

Offset modifier can take x and y offsets, use them

Right, but according to the documentation:
It accepts the following units:

unitless, interpreted as pixels
% or %r, percentage relative to the length of the reference element
%p, percentage relative to the length of the popper element
vw, CSS viewport width unit
vh, CSS viewport height unit

Whereas in my use case what I would need is a combination of the offset percentage AND a pixel amount, which doesn't seem to be supported. Do I have that right?

You can define a combination of measurements. It's written in the documentation

Is it? Can you direct me to the section you're talking about? I don't see anything in there about a "combination of measurements". No arrays, no compound strings, etc.  What exactly is your suggestion?

You can provide a single value (as Number or String), or a pair of values as String divided by one white space.
Valid examples are:
offset: 10
offset: ‘10%’
offset: ‘10 10’
offset: ‘10% 10’

Look at my Tether example again:
http://jsfiddle.net/nngLr41a/26/
It's aligned such that the two corners are touching, and then beyond that, I've added a constant pixel offset of 20px. This is something that comes in useful for tooltip widgets that go beyond the most basic vanilla alignment scenarios. The two values you are talking about would be the vertical and horizontal offsets, which is fine, but it still doesn't allow for the kind of alignment scenario I'm demonstrating with Tether (and jqueryui). Using your percentage offset model, I would need to ALSO add a constant pixel offset. It's apparently not possible with Popper, but it would, in theory, look something like this:
new Popper(ref, pop, {
  placement: 'left',
  modifiers: {
    offset: { offset: '100%r20px' }
  }
});

But really that only takes care of one axis.  In my Tether example, I'm offsetting on both axes.
With Popper, even with my imaginary syntax it starts to get a little awkward, as I have to provide a completely different offset for the horizontal component:
new Popper(ref, pop, {
  placement: 'left',
  modifiers: {
    offset: { offset: '100%r20px 20px' }
  }
});

Consider again how easy this is with Tether (and jqueryui):
var tether = new Tether({
	element: $('#popup'),
  	target: $('#target'),
  	attachment: 'top left',
  	targetAttachment: 'bottom right',
    offset: '-20px -20px'
});

By the way, it's not clear to me why '100%r' is the correct offset value in your original example. I would expect 100% of the reference value to put the popper element floating off in space below the reference element. 50% puts the popper's left middle right at the reference element's lower right. which is expected, but a value of 100% or greater seems to cap the popper's position such that it's top won't go below the reference element's bottom, which feels like a bug to me:
https://codepen.io/shmax71/pen/WjxqPV
Any thoughts?

I wonder why you can't simply apply a padding with CSS.
By the way, you can define a custom modifier and apply any kind of offset you desire.

I wonder why you can't simply apply a padding with CSS.

I assume you mean 'margin'. I'll experiment with it a bit and get back to you, thanks...

By the way, you can define a custom modifier and apply any kind of offset you desire.

Well, yes, but the reason I use a library is to minimize the amount of custom code I have to write.

You have to understand that the goal of this library is to outsidel provide a solid foundation to position your elements. It can't support all the possible use cases out of the box but it does provide a powerful way to integrate additional features writing a minimal amount of code.
This said, if you think your use case could be shared by others, you may write a modifier to achieve what you need and publish it on npm.
Doing so other users will be able to add your modifier to Popper and take advantage of the features it provides.

You have to understand that the goal of this library is to outsidel provide a solid foundation to position your elements.

It doesn't, though. :( Even though it's new and shiny it doesn't provide the same foundational basics that jqueryui and Tether do.

It can't support all the possible use cases out of the box but it does provide a powerful way to integrate additional features writing a minimal amount of code.

Well, no, it apparently requires me to write plugins just to bring it up to the same basic level as Tether and jquerui, which seem to be your "competition".

It can't support all the possible use cases out of the box but it does provide a powerful way to integrate additional features writing a minimal amount of code.

No one's asking for all the possible use cases, but the basics that the two other major libraries provide would be lovely.

it does provide a powerful way to integrate additional features writing a minimal amount of code.

But I don't have to write any code if I use one of the other libraries. :(
Sorry, I know I probably sound a bit antagonistic, but I don't have time at the moment to get involved with bug fixing or writing add-ons for another project; I need something that just works.
I don't feel that my use case is unusual or exotic or unreasonable--I would expect a library such as yours to handle it well out of the box, especially when it has so many other nice features and is designed to be a good foundation for things like tooltips.
At this point jqueryui is looking like my best option--it's been around longer, and is the result of the collaboration of hundreds of talented developers. This is not to slam Popper, you've done a great job with it!
Thanks for your time.

You are welcome. I think you miss what actually this library does since you are still comparing it to libraries that support just very basic situations. Popper.js aims to position the elements no matter where they are in the DOM. Tether and others can work only if the popper is a direct child of the body element.
At the moment I'm replying from my smartphone because I'm not working (I'm with my girlfriend on the sofa) and I'm the only maintainer of this project. But I'll be happy to code for you a codepen that shows you what you need to achieve with just few lines of code tomorrow morning as soon I get on my PC.

Sorry I didn't read your concern about a possible bug.
That behaviour is the result of the keepTogether modifier. You can disable it to allow the popper to detach from the reference on its main axis.

Tether and others can work only if the popper is a direct child of the body element.

You can't mean that. Both libraries do just fine with any amount of nesting:
http://jsfiddle.net/nngLr41a/27/
It's really why they exist in the first place--their main purpose is to walk the ancestral DOM tree and sort out all the position: absolute and position: relative and god-knows-what-else sort of situations and do the positioning you want, anyway.
I'll await your further samples with interest, thanks.

Tether moves the popper to make it live as direct child of the body, you can check it for yourself. I can't talk for the other plugin you mention because I never used it, but I'm quite sure it does the same.

Oh, and just to bring it full circle, I have two reasons to want to move away from Tether:

It reparents the 'popper'. While it doesn't require it to be a direct child of body, it does move it there for the purpose of solving z-index sorting issues (neither Popper or JqueryUi take on the problem of z-index sorting), but this 'feature' of theirs causes all sorts of subtle issues related to the fact that they compute the height of the popper while it's still in its original home, which can differ from the computed height once it's
been moved to the tail of body. Groan.

It has a bug with collision detection and offset. If a popper has an offset applied, and it hits the edge of the window and needs to flip around, it does not invert the offset amount, which causes it to appear in the wrong position.

I know your library doesn't have the first problem, not sure about the second.

Tether moves the popper to make it live as direct child of the body, you can check it for yourself. I can't talk for the other plugin you mention because I never used it, but I'm quite sure it does the same.

Yes, it moves it to body after the fact (which is not the same as saying that it requires your popper to be a direct child of body--it may or may not--it moves it there for z-sorting reasons). jqueryui does not do any reparenting.

No, it moves it there because the position computation is much easier in this case.
The z-index reason is a no sense, z-index is very delicate and specific problem that must be handled carefully case by case.

Well, rather than get in an argument over it let's make it easy and remove Tether from this part of the discussion, then. jqueryui's position add-on most definitely does not do any re-parenting (which is why I'm leaning towards using it).

Please read my edit.

Also, I think you edited your previous JSfiddle because I can't see the same result I was seeing from my smartphone?

I remember it was something like this maybe?
https://codepen.io/FezVrasta/pen/bWeXaE

Sorry, was on the phone with the bank. I looked at your jqueryui sample, but it wasn't clear to me what you were trying to prove. Here's one of my own that shows some sem-complex nesting:
https://codepen.io/shmax71/pen/ZKOgvJ/
Everything looks fine to me, and there is no re-parenting.

new Popper(ref, pop, {
  modifiers: {
    keepTogether: { enabled: false },
    offset: { offset: '100%' },
    addMargin: {
      order: 890,
      enabled: true,
      function: function(data) {
        data.offsets.popper.top += 10;
        data.offsets.popper.left += 10;
        return data;
      }
    }
  }
});

Sure, that works, but basically you're telling me to just "write your own code", and if I wanted to do that then why am I using a library? Compare that to the jqueryui solution:
$( "#pop" ).position({
  my: 'left top',
  at: 'right+20px bottom+20px',
  of: '#ref'
});

Can you guess which option looks better to me?

Oh, regarding using margins:
On this point, your library has a different behavior: it respects the margins when doing the alignment, whereas jquery ignores them:
jqueryui:
https://codepen.io/shmax71/pen/ZKOgvJ/
Popper:
https://codepen.io/shmax71/pen/WjxqPV
Which is interesting. I have to say I prefer the idea of controlling the offset via CSS much better than using configurable offsets, so I'll give you points on this one.

Sorry, it's midnight here, a bit tired 🙃
https://codepen.io/FezVrasta/pen/qmNeVM
scroll the purple container and you'll notice that the popper doesn't follow the reference element.
I'm not saying my library is perfect, but it handles (almost) all the positioning issues that can be encountered. What you are asking is just sugar on top, which, at the moment, can be achieved writing few lines of code (or using some CSS to make it easier?).
jQuery UI (with only the position module) is a 8KB library, with the jQuery dependency (87KB). With almost ~100KB you get some basic positioning functionality that breaks in any medium to complex case. (but also some basic case like a simple scrolling element).
jQuery is sponsored by big companies like Microsoft (that, nonetheless, uses Popper.js in its WebClipper project), while Popper.js is supported by... umh.. me?
This is the first time someone asks for this very specific behavior, and I provided a solution that requires you to simply disable a built-in modifier, define an offset, and add a line of CSS.
Do you want better support for it? I'm super happy to review PRs and give you any information you need to write a modifier to add this behavior.
My point is, with Popper.js, you have a strong foundation you can use to write anything you need without worrying about all the mess that happens under the hood to give you the initial basic positions. I'm happy to see new contributors willing to add new features to the library, both via PRs or via external modifiers.

I forgot to add that, while you are here talking about these missing functionalities, I released a version to fix a problem that affected your use case.

Ah, okay, so now we're talking about binding during scrolling (and presumable animations?). Great, that's a nice feature, and I could certainly make use of it.

jQuery UI (with only the position module) is a 8KB library, with the jQuery dependency (87KB). With almost ~100KB

Ah, not in my case. I'm working in an Ember app, so we already have jquery, anyway. It's not necessary to include jqueryui to use the position plugin. It's standalone, and weights in at around 2.7KB, minified. popper.min.js seems to be around 6.4KB.

you get some basic positioning functionality that breaks in any medium to complex case. (but also some basic case like a simple scrolling element).

I haven't seen any evidence of that. You may have a point about the scrolling, though.

jQuery is sponsored by big companies like Microsoft (that, nonetheless, uses Popper.js in its WebClipper project), while Popper.js is supported by... umh.. me?

Is that supposed to be an argument for or against using it? And I wasn't aware that Microsoft was a sponsor of jquery. Not sure what you mean by that.

This is the first time someone asks for this very specific behavior, and I provided a solution that requires you to simply disable a built-in modifier, define an offset, and add a line of CSS.

Your "simply" requires 10 more lines of code and knowledge of around half a dozen API properties and concepts. Sure, it works but it's not exactly intuitive or easy to use.  You and I had to argue about it for half a day to arrive at some semblance of a solution.

Do you want better support for it? I'm super happy to review PRs and give you any information you need to write a modifier to add this behavior.

What, you mean to make an API similar to jqueryui and Tether? I'll think about it--I may do that. I was sort of sold on using jqueryui, but I do like the way your library handles margins and scrolling/animation binding. If it had a friendly API similar to Tether/jqueryui I think you would have a clear winner. I'll think it over.

I forgot to add that, while you are here talking about these missing functionalities, I released a version to fix a problem that affected your use case.

Did you? I see a commit from 6 hours ago, but it has something to do with documentation?

Tether developers have abandoned their library and point here (I don't blame them, it's hard to maintain such libraries).

True! I found that very frustrating, and if they had bothered to make that clear somewhere I wouldn't have used their library.

I can't speak for jquery, but jqueryui has a very active and agressive devb cycle. I opened a bug report myself last night and they've already closed it. Amazingly, the position plugin only has one open issue:
https://bugs.jqueryui.com/report/10?P=position
But I totally know what you mean, in general. It breaks my heart when maintainers lose interest in their own projects and can't be arsed to hand them over or come up with an exit strategy.

You should run my whole test suite against jQuery UI Position to see how many edge cases aren't covered by it. Right now I'm really tired and I haven't a way to provide you additional pens with broken cases.
About the point of Microsoft, feel free to use whatever fits your needs. I'm maintaining this project using my free time because I think it can be valuable to many. If you think other projects are better you should use them or, if you think it makes sense, invest time in Popper.js and help improving it.
About the fact that it took so much to reach to a conclusion is because it's Sunday and I replied to you with my smartphone almost all the time. I'm sorry for that.
I don't I'd like to see the same placement configuration provided by Tether and jQuery because most of the times it's really overkill.
But I think it would be valuable to add a way to perform basic operations in the offset modifier using the available units. Such as 10% + 5px.

But I think it would be valuable to add a way to perform basic operations in the offset modifier using the available units. Such as 10% + 5px.

That sounds good to me. 👍

1.8.3 was released after I replied to you and noticed the bug while I was playing with the pen I provided.

Ah, very nice.

Anyway, thanks for all the feedback. Good night, and I'll probably be in touch about some API improvements along the lines of what you suggested.

Thank you. Check out ember-popper, you may find it useful.

Hah, it's got the same problems that ember-tether did (namely, it assumes that your component is not tagless). Thank you, though.

Maybe open an issue to let them know, they could fix it.

Naw, there's not enough code there to warrant getting involved. I've already got all the foundational work done in my own component--all I really need to do is swap out Tether for something else.

Open source it then 😋

I'm trying, but I have to convince my employer, first.

But I think it would be valuable to add a way to perform basic operations in the offset modifier using the available units. Such as 10% + 5px.

That sounds good to me. 👍

https://github.com/FezVrasta/popper.js/pull/229 implements this feature.

@jackson-sandland 	I already answered your question on the other issue, please don't repost questions/concerns everywhere.
Thank you.


Agateau/fix extended match

Context

What has been done

Validation

PR check list

[ ] As much as possible, the changes include tests (unit and/or functional)
[ ] If the changes affect the end user (new feature, behavior change, bug fix) then the PR has a changelog entry (see doc/dev/getting-started.md). If the changes do not affect the end user, then the skip-changelog label has been added to the PR.

Replaced with #905.


I want to decode from the bytes in memory

I want to decode the sound from include_bytes!.
That doesn't seem to be possible since rodio currently requires a static lifetime to decode.
Why do we need a static lifetime for the decoder's generic parameters?
let mut buf = Cursor::new(include_bytes!("example.ogg").to_vec());
let source = rodio::Decoder::new(&mut buf)?;

Does removing the &mut work?

Oh, I'm sorry.
The code worked.


Correctly set backup_dir for pre/post upgrades

In order for the post upgrade neutron router tests to inspect state
prior to upgrade, we had to add number of backup_dir-related vars to
the post upgrade role.  Additionally, we added those vars to
group_vars/all.yml so that the pre and post upgrade roles would share
those vars.  What we missed unfortunately is that those vars reference
additional vars, which are evaluated at run-time.  This means if
someone runs an upgrade at 11 PM at night, the backup_dir would be (for
example) /root/rpc13-upgrade-2017-06-16.  By the time the post upgrade
runs, it'll be past midnight, and now backup_dir will be
/root/rpc13-upgrade-2017-06-17.  While this won't cause the post
upgrade role to fail, it won't see the router data from pre upgrade and
not provide any meaningful data to the deployer.
In a nutshell, this commit simply adds an override for backup_dir to
/etc/openstack_deploy/user_upgrade_variables.yml (created temporarily by
test-upgrade.sh) and removes all the unnecessary overrides added to
group_vars/all.yml.  A doc change and note for support will follow.

Looks good, but I'm going to hold off for gating.
Also, a wise person once recommended to me to change the docs on editing of test-upgrade.sh.

recheck_cit_trusty_majorupgrade_swift


Support Trusted CA Indication extension

Are there any plans to support the "Trusted CA Indication" extension?
Supposing:

an application had its own PKI with multiple roots
clients know about subset M of N total roots and have certificates from each of them
clients want to communicate with each other and mutually authenticate

Client A need to be able to indicate to their peer which M0 roots it knows about, so that Client B can choose which of its M1 roots intersect and which certificate to use in its "server hello", such that Client A will trust its certificate chain.
As far as I know, this problem is solved by Trusted CA Indication, and is a compelling use case for implementing it in my opinion.
Second, given this extension is not supported at present by OpenSSL is there a way with the current TLS support to accomplish this same goal? Thank you!

There are no plans to implement it at this time.  A PR would help :)  How useful is this?  Do servers often have multiple trust chains to present to a client?

Tried to illustrate the usefulness above. This is obviously not for an HTTPS web server scenario, but an application where different clients are communicating to each other with mutual TLS auth.

Okay, I get it.  Can you do it with the client sending the CA DN's list?  It's a reasonable thing to want, but it's not on our radar now.

Not sure what you mean by the client sending the CA "DN's list".
I suppose we can probably hack it together with encoding something into SNI for client->server as well as using SSL_add_client_CA for server->client. Not as clean as this TLS extension, but that would probably work.

oops, it's the certificate_authorities list  and it's sent by the server.  sorry.

Okay, well, you can feel free to close this issue I guess if supporting this isn't on your radar. Duly noted that PR's are welcome, and I may get to that one day, but probably not soon. :)

Hello,
I was looking for the official support of Trusted CA Indication extension (rfc 6066) in openssl and I found this issue written two years ago.
From OpenSSL changelog I understand that rfc 6066 is only partially supported.
Is there any plan to add this support the "Trusted CA Indication extension" in the future?
Thanks.
BR, Paolo

There are no plans to add support for this extension at the moment. However we would consider a PR that added it.

closing, as it seems we still haven't gotten to this.  Extensions other than trusted_ca_keys were added several years ago.  If there is a desire to see trusted_ca_keys implemented, I would suggest the best approach would be to open a new issue that we can triage and consider.


GDT: storage size limit

GoogleDataTransport simple storage size limit (b/129492246).

@mikehaney24 I updated the API docs. Please let me know if you would like to see more details.

lgtm

Will be merged after M79 release branch cut.

Profiler doesn't indicate any significant performance regressions attributed to the changes. The most resource demanding part is still writing the event data to the disk.
GDT Size Limit.trace.zip


Request to Update Bellsoft Liberica Buildpacks to 9.4.2 as default

Currently the default version of the default JVM , paketo-buildpacks/bellsoft-liberica:9.4.1 is using jdk version <IP_ADDRESS>2-7 for java 8 which has been identified to have various critical vulnerabilities. Request to bump up the version of liberica buildpacks to 9.4.2 which has a fix for this by including the new version <IP_ADDRESS>5 which addresses the vulnerabilities.
Expected Behavior
The Java buildpacks should by default pull bellsoft-liberica buildpacks version 9.4.2.
Current Behavior
The latest release of java buildpacks are using version 9.4.1 version of bellsoft-liberica buildpacks by default
Possible Solution
Needed a new release that includes the latest version of the bellsoft-liberica buildpacks ( 9.4.2)

jdk version <IP_ADDRESS>2-7 for java 8 which has been identified to have various critical vulnerabilities

The 8u342 has all of the fixes from Oracle's July 2022 quarterly release. I'm checking with Bellsoft to see what is fixed in 8u345 but their release notes do not indicate any CVE patches.

Request to bump up the version of liberica buildpacks to 9.4.2 which has a fix for this by including the new version <IP_ADDRESS>5 which addresses the vulnerabilities.

This will happen on Friday (two days). The normal release cadence for the paketo-buildpacks/java composite buildpack is every Friday, with the exception of patches for critical CVEs. Since there were not any listed in the release notes, we had planned for this release to go out in the normally scheduled release. I did check with the vendor, so if they come back and confirm there are CVE patches in this release, we can release this buildpack sooner.
In the meantime, I believe you can follow these instructions with the gcr.io/paketo-buildpacks/bellsoft-liberica:9.4.2 image and swap in the 9.4.2 release.

Bellsoft confirmed that there are no CVE fixes in 8u345. There was a functional regression in 8u342 which impacts Gradle. This was severe enough that it triggered an off-cycle release. It has this one fix, nothing else. This did not impact Java 11 or 17 so no new releases there.

Closing as this release has since shipped.


Crashes LLDB on Windows

When using clang++ with c++20 the debugger crashes with the following message
error: example.exe :: Class 'std::strong_ordering' has a member 'less' of type 'std::strong_ordering' which does not have a complete definition.
error: example.exe :: Class 'std::partial_ordering' has a member 'less' of type 'std::partial_ordering' which does not have a complete definition.
error: example.exe :: Class 'std::weak_ordering' has a member 'less' of type 'std::weak_ordering' which does not have a complete definition.
Debug adapter exit code=3221225477 (0xc0000005), signal=null.

Repository with simple reproductible example: https://github.com/everdrone/clang_signals2

Clang version:

clang version 15.0.7
Target: x86_64-pc-windows-msvc
Thread model: posix

Windows 11, 22621
Boost 1.81.0
CMake 3.26.3
C++20

I don't use windows, so I can't reproduce your problem.  FWIW, I was able to build your example on Linux and debug it with gdb without seeing any problem.

I was also able to debug with lldb without seeing any problem.

I guess I'll wait for other people to try to reproduce as it only happens on windows.
Closing for now


The breakpoints UI is really confusing

(i'm using vscode-cpptools over ssh to a linux box debugging with gdb)
For example:

there's right-click menu items for "Enable/Disable All Breakpoints", but that seems to be different from whatever this button does:
 what's the difference between 'active' and 'enabled' ?

there seem to be 3 different 'enable' / 'active' states:

the red circle, which can also be grey, or hollow. what do those even mean? it can also be white, for some reason.
the checkbox
the whole line can be greyed out, does this mean the code isn't loaded or the breakpoint is disabled, de-activated?

shouldn't there be a right-click menu item in the breakpoint list to enable/disable a breakpoint. How about 'Activate All Breakpoints' ?

if you click the 'Deactivate Breakpoints' button, then toggle the checkbox on one breakpoint (or add another breakpoint in the code), the whole lot seem to be re-activated, is this intentional? seems weird.

if you click on a breakpoint in the breakpoints list) then the line is highlighted (and the circle turns white always, even if it was grey or hollow before, hiding the current state, why?). then if you use the cursor keys to move the selection to a different breakpoint, the original one stays selected (with its white circle), but hitting space toggles the checkbox of the other breakpoint. which one is supposed to be selected here? how many highlights do you need?

there's a checkbox that can be toggled with the space bar, why no multi-select?

THanks for the feedback however all of these are by design. We felt that makes the nicest experience.
We were inspired by chrome dev tools who also support this mechanism of enabling / disabling and deactivation on top.
The only things which we could support from the list is multi select, and for that I can leave this open as a feature request.


Fix creating huge pages

hugepages shoudn't have mounted path, only name
Conflicts:
roles/edpm_extra_mounts/defaults/main.yml
roles/edpm_extra_mounts/molecule/default/converge.yml
conflcits were resolved by accpeting the incoming version
Closes: OSPRH-10215
(cherry picked from commit ca0fe3ced6ebb837ad0d0b0994857d986c2c9cd4)

Do we need to cherry pick this now that 18.0.2 closed? I assume 18.0.3 is the same as FP1 and that its content will be from main not from 18.0.0-propose (or 18.0.0-proposed will be reset to main)

Do we need to cherry pick this now that 18.0.2 closed? I assume 18.0.3 is the same as FP1 and that its content will be from main not from 18.0.0-propose (or main will be merged into 18.0.0-proposed)

this should have been cherry-picked for 18.0.2 because it was merged before the code freeze for it on main but we forgot to do that at that time. I am actually debating if this is worth escalating as an expectation for 18.0.2 which was the main reason I created this cherry pick but strictly speaking this is not required.
18.0.3 and FR1 may not be the same the feature release, FR1 can be deferred at most once if required which would align with 18.0.4 depending on the state of verification.
While the intent is to be time-based fi there are infra issues then that is what we would do.

/lgtm


A few things I would like to improve

--force option would add a gem to the Gemfile whether it's detected or not. Alternatively, it would update/overwrite the line that already specifies the gem. One of the problems I ran into is that some gems in my Gemfile aren't qualified with versions, which I personally prefer for any non-development dependencies. I kind of want to use gemrat to simply append the version, but it doesn't let me do that.
Use Bundler's API instead of regex to detect the presence of gems. I think this would be less brittle, but I was wondering if you had a rationale for not going this way. I implemented this in a fork yesterday and specs passed. There is also presently a bug where a commented out gem in a Gemfile will be detected, which is what originally prompted me to use Bundler's API instead of grep.
Add gems to a group, e.g. gemrat guard --group development. I would really like for this to be able to throw the gem in a group :development do block as opposed to gem 'guard', group: :development, although I'm not sure how easy this would be.

Thoughts?

can't wait to see groups option implemented

Would love the groups option to be added.

Doesn't look like it, but is the groups option a thing yet?

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @


[Build] Update management module version

Modifications
Update package org.apache.pulsar:pulsar-package-management from 2.7.0-SNAPSHOT version to 2.8.0-SNAPSHOT.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

The MACOs test is failing with:
Run apache/pulsar-test-infra/diff-only@master
Error: Container action is only supported on Linux

IMHO we can ignore it and merge the patch

@eolivelli Yes, we are still trying to find a solution to verify the build process on different os. So it's not a required CI test. I have merged this PR, and I will close https://github.com/apache/pulsar/pull/8698 first.


Error: Invalid arguments: hostname must be a string or falsey

This may happened when host is invalid:
  async connect({host, port}, callback) {
    logger.info(`[socket] [${this._id}] connecting to: ${host}:${port}`);
    this._tracks.push(`${host}:${port}`);
    try {
      const ip = await dnsCache.get(host);
      this._fsocket = net.connect({host: ip, port}, callback);
      this._fsocket.on('error', this.onError);
      this._fsocket.on('close', this.onClose);
      this._fsocket.on('data', this.onBackward);
    } catch (err) {
      - logger.error(err.message);
      + logger.error(`[socket] [${this._id}] connect to ${host}:${port} failed: ${err.message}`); // log details to see what host is
    }
  }

Catch the details:
{"level":"error","message":"[socket] [8819] connect to :2561 failed due to: Invalid arguments: hostname must be a string or falsey","timestamp":"2017-03-27T13:49:12.290Z"}

Here host is empty but port is 2561.


How to train on custom dataset?

Can anyone guide me, how to train on the Custom dataset for example CORD (https://github.com/clovaai/cord)

Here is how you can do it:

Write a dataset class, which reads an image address and the labels associated with it (like for sequence labeling, in which we need to predict what is the class for each text, we would have a label of (seq_len, 1), since each would have a single class)
Now, extract the features using the create_features function
And from the dataset object, return the 5 parameters (1. resized_scaled_img, 2.x_features, 3.y_featuers, 4. input_ids, 5l. labels)
Use a collate function in PyTorch for handling multiple inputs from a single dataset and then pass it as follows:

Use ResNetFeatureExtractor, to get the image feature of the resized_scaled)img
Use DocFormerEmbedding, to get the extracted features of x_features, y_features
Use LanguageFeatureExtractor, to get the features of the tokenized words

Having obtained these things, pass it through the DocFormerEncoder
And then, attach a linear layer according to your task requirement
Take the loss and backward propagate it

Hope this helps
We would shortly include these things in a smaller boilerplate, so that code becomes more clear and more concise, but I hope this helps.

Here is how you can do it:

Write a dataset class, which reads an image address and the labels associated with it (like for sequence labeling, in which we need to predict what is the class for each text, we would have a label of (seq_len, 1), since each would have a single class)
Now, extract the features using the create_features function
And from the dataset object, return the 5 parameters (1. resized_scaled_img, 2.x_features, 3.y_featuers, 4. input_ids, 5l. labels)
Use a collate function in PyTorch for handling multiple inputs from a single dataset and then pass it as follows:

Use ResNetFeatureExtractor, to get the image feature of the resized_scaled)img
Use DocFormerEmbedding, to get the extracted features of x_features, y_features
Use LanguageFeatureExtractor, to get the features of the tokenized words

Having obtained these things, pass it through the DocFormerEncoder
And then, attach a linear layer according to your task requirement
Take the loss and backward propagate it

Hope this helps
We would shortly include these things in a smaller boilerplate, so that code becomes more clear and more concise, but I hope this helps.

@uakarsh Thanks for detailed step by step explanation, i'll have a go at it.


Snapshot not working with localStorage with base configured

Environment
Unstorage: 1.6.0
Node: 19.9.0
Reproduction
import { createStorage, snapshot } from 'unstorage'
import localStorageDriver from 'unstorage/drivers/localstorage'
const storage = window.localStorage
const localStorage = createStorage({
  driver: localStorageDriver({ base: 'app', localStorage: storage })
})
await localStorage.setItem('key', 'value')
const data = await snapshot(localStorage, "app");
console.log(JSON.stringify(data))

Result will be: {"key":null}
Describe the bug
When localStorage is configured with a base the snapshot function does not work.
This is because in the snapshot function in storage.ts:
export async function snapshot(
  storage: Storage,
  base: string
): Promise<Snapshot<string>> {
  base = normalizeBaseKey(base);
  const keys = await storage.getKeys(base);
  const snapshot: any = {};
  await Promise.all(
    keys.map(async (key) => {
      snapshot[key.slice(base.length)] = await storage.getItem(key);
    })
  );
  return snapshot;
}

The value comes from await storage.getItem(key) but the key includes the base eg. "app:key" which return null because it's not expecting the base.
Changing to await storage.getItem(key.slice(base.length)) works in this case
Additional context
No response
Logs
No response

I found it works if I use prefixStorage instead of setting the base in the localStorageDriver options
import { createStorage, snapshot, prefixStorage } from 'unstorage'
import localStorageDriver from 'unstorage/drivers/localstorage'
const storage = window.localStorage
const localStorage = createStorage({
  driver: localStorageDriver({ localStorage: storage })
})
const prefixedStorage = prefixStorage(localStorage, "app")
await prefixedStorage.setItem('key', 'value')
const data = await snapshot(prefixedStorage);
console.log(JSON.stringify(data))

Simple switch to memory storage solve the issue, but I need fs (PS its part of "nuxt": "^3.8.1")

It's not working also with Node.js lite drive

Hi. It seems related to base support issue in local storage. Let's track via https://github.com/unjs/unstorage/issues/352


Remove uses of ArgResultAliasAttr as it is not used, specced, or supported in VHLO

Was looking at VHLO code coverage for serialization and realized the only unused attribute is ArgResultAliasAttr, because it was unsupported in VHLO legalizations. Speaking with @burmako it sounds like this attribute is unused and should not be in StableHLO/VHLO currently without an RFC first.
This is not an incompatibility since serialization would fail for programs that use this attribute currently.
Adding @sdasgup3 as reviewer as well for spec implications (should be none?)

@GleasonK Just wanted to make sure that we will be having a separate Frontend contract ticket to remove the same from StableHLO per https://github.com/openxla/stablehlo/issues/1155.  Is that right?

Removing my assignment for now to get a review from @sdasgup3 first. I'll chime in afterwards.

@GleasonK Gentle ping. If I recall correctly, the proposed changes are fairly lightweight, so I think we should be fairly close to merging this after some minor follow-up work.


KAFKA-8897 Follow-up: Consolidate the global state stores

When register state stores, add the store to globalStateStores before calling any blocking calls that may throw errors, so that upon closing we would close the stores as well.
Remove the other list as a local field, and call topology.globalStateStores when needed to get the list.

Committer Checklist (excluded from commit message)

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

ping @cadonna @ableegoldman for reviews.

@cadonna

Filed a ticket for KStreams to enforce shutdown on illegal-X exceptions as a future work.
Let the global state mgr to do closing before throwing illegal-X exception as well.
For unit tests though, they would not cover the case 2) as I mentioned in the PR.


Expose WebSocketState

Trivial improvement about exposing WebSocketState. It will eliminate the need of importing it from starlette directly.
Previously:
from fastapi.websockets import WebSocket
from starlette.websockets import WebSocketState

After:
from fastapi.websockets import WebSocket, WebSocketState

How do you use WebSocketState?

So there is an endpoint that is sending some data, usually very rarely but still, and is receiving nothing. So while we are not sending any data and the WebSocket connection was closed by the client, the task is still running. So to add functionality that if the connection is closed task will be closed also we are monitoring the WebSocket status, by simple .recevie.
The endpoint more or less looks like that:
@router.websocket("/subscribe/some/data/changes")
async def subscribe_connectors_status(
    websocket: WebSocket,
) -> None:
    async def send_some_data() -> None:
        last_data = await get_data()
        await websocket.send_json({"data": last_data})
        while True:
            await asyncio.sleep(1)
            new_data = await get_data()
            if new_data != last_data:
                # This happens very rarely that's why I would like to close all of these unused tasks.
                last_data = new_data
                await websocket.send_json({"foo": last_data})

    async def watch_status() -> None:
        while websocket.client_state == WebSocketState.CONNECTED:
            # We are not expecting any data, but this will change to the client state if the connection will be closed.
            await websocket.receive()

        tg.cancel_scope.cancel()

    await websocket.accept()
    async with create_task_group() as tg:
        tg.start_soon(watch_status)
        tg.start_soon(send_some_data)

Thanks for the contribution @matiuszka! :cake:
And thanks @Kludex for the help! :bow:
Knowing how you are using it made me feel it makes sense to have this in, so I'll take it. :rocket:
Thanks! :coffee:


Feature: Add support for UART devices

This pull request adds initial WipperSnapper support for UART devices.
Technical notes:

Initial support for the PMS5003 Air Quality Sensor is included with this PR, with more sensors down the line
WipperSnapper defaults to using the hardware UART bus unless the BSP includes a copy of SoftwareSerial.

Implementation notes:

Unlike I2C, UART devices share a common period
Unlike I2C drivers, UART drivers publish data out to IO

Other notes:

Fixed: ESP32 platforms not connecting to IO-Staging Server

Tests:
Hardware UART

[x] Create a UART device from Adafruit.io
[x] Delete a UART device from Adafruit.io
[x] Update a UART device's period from Adafruit.io
[x] Update the number of a UART device's sensor "sub-components" from Adafruit.io
[x] Verification that UART devices send data at a consistent period
[x] Re-sync a UART device

Software UART

[x] Create a UART device from Adafruit.io
[x] Delete a UART device from Adafruit.io
[x] Update a UART device's period from Adafruit.io
[x] Update the number of a UART device's sensor "sub-components" from Adafruit.io
[x] Verification that UART devices send data at a consistent period
[x] Re-sync a UART device

Resolves https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/issues/359

@tyeth  Could you re-review this again at some point this week?

Tested on hardware across all platforms ✅


Init of 0.59.10 and bundleRelease fails on 64-bit devices on Firebase Test Lab

New 0.59.10 application fails to run on at least several Pixel devices in Firebase Test Lab when uploading the Android Application Bundle. Failed on:

Pixel, API Level 26
Pixel 2, API Level 26
Pixel 2, API Level 27
Pixel 2 XL, API Level 26
Pixel 2 XL, API Level 27

React Native version:
info
  React Native Environment Info:
    System:
      OS: Linux 4.15 Ubuntu 18.04.3 LTS (Bionic Beaver)
      CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
      Memory: 784.85 MB / 15.43 GB
      Shell: 4.4.20 - /bin/bash
    Binaries:
      Node: 10.14.2 - ~/.nodenv/versions/10.14.2/bin/node
      Yarn: 1.17.3 - /usr/bin/yarn
      npm: 6.4.1 - ~/.nodenv/versions/10.14.2/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      Android SDK:
        API Levels: 23, 25, 26, 27, 28
        Build Tools: 27.0.3, 28.0.3
        System Images: android-19 | Intel x86 Atom, android-22 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-27 | Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.10 => 0.59.10
    npmGlobalPackages:
      react-native-cli: 2.0.1

Steps To Reproduce

react-native init AwesomeProject --version 0.59.10
cd AwesomeProject
touch .watchmanconfig
cd android && ./gradlew bundleRelease
Upload app.aab to Firebase Test Lab and run Robo test on Pixel, Pixel 2, or Pixel 2 XL.

Describe what you expected to happen:
Expected successful test
Snack, code example, screenshot, or link to a repository:
All five failed with:
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-4/libc++_shared.so" is 32-bit instead of 64-bit

FATAL EXCEPTION: create_react_context
Process: com.awesomeproject, PID: 15754
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-4/libc++_shared.so" is 32-bit instead of 64-bit
	at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
	at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
	at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
	at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
	at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:31)
	at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:19)
	at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:25)
	at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:944)
	at java.lang.Thread.run(Thread.java:764)

Sample logcat:
web-build_2019-08-15T13:02:43.203Z_w71r_taimen-26-en_US-portrait_logcat.log
AAB:
app.aab.gz

+1 are You able to resolve

New 0.59.10 application fails to run on at least several Pixel devices in Firebase Test Lab when uploading the Android Application Bundle. Failed on:

Pixel, API Level 26
Pixel 2, API Level 26
Pixel 2, API Level 27
Pixel 2 XL, API Level 26
Pixel 2 XL, API Level 27

React Native version:
info
  React Native Environment Info:
    System:
      OS: Linux 4.15 Ubuntu 18.04.3 LTS (Bionic Beaver)
      CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
      Memory: 784.85 MB / 15.43 GB
      Shell: 4.4.20 - /bin/bash
    Binaries:
      Node: 10.14.2 - ~/.nodenv/versions/10.14.2/bin/node
      Yarn: 1.17.3 - /usr/bin/yarn
      npm: 6.4.1 - ~/.nodenv/versions/10.14.2/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      Android SDK:
        API Levels: 23, 25, 26, 27, 28
        Build Tools: 27.0.3, 28.0.3
        System Images: android-19 | Intel x86 Atom, android-22 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-27 | Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.10 => 0.59.10
    npmGlobalPackages:
      react-native-cli: 2.0.1

Steps To Reproduce

react-native init AwesomeProject --version 0.59.10
cd AwesomeProject
touch .watchmanconfig
cd android && ./gradlew bundleRelease
Upload app.aab to Firebase Test Lab and run Robo test on Pixel, Pixel 2, or Pixel 2 XL.

Describe what you expected to happen:
Expected successful test
Snack, code example, screenshot, or link to a repository:
All five failed with:
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-4/libc++_shared.so" is 32-bit instead of 64-bit

FATAL EXCEPTION: create_react_context
Process: com.awesomeproject, PID: 15754
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libreactnativejni.so caused by: couldn't find DSO to load: libfb.so caused by: couldn't find DSO to load: libc++_shared.so caused by: dlopen failed: "/data/data/com.awesomeproject/lib-4/libc++_shared.so" is 32-bit instead of 64-bit
	at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
	at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
	at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
	at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
	at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:31)
	at com.facebook.react.bridge.NativeMap.<clinit>(NativeMap.java:19)
	at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:25)
	at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:944)
	at java.lang.Thread.run(Thread.java:764)

Sample logcat:
web-build_2019-08-15T13:02:43.203Z_w71r_taimen-26-en_US-portrait_logcat.log
AAB:
app.aab.gz

Same is happening with me.
Did u find any solution or the same issue happens when it is uploaded on play store ?


server/tasks: add order taskss

I have a fix for the unit test failing in #3524 ;)

I have a fix for the unit test failing in #3524 ;)

Ah nice thanks!


Adding clearer language for what app we're using.

The intended app to be used in this getting started example is Convox's sample Rails app, and identifying that as "your app" is confusing, as it's not actually the user's app that's being used. The language has been amended to make it more clear that the app being referred to is the sample app.

@AlexMcConnell Nice changes. Thank  you.


install issue

Traceback (most recent call last):
File "setup.py", line 44, in
PYCLIF = check_output(['which', 'pyclif'])
File "setup.py", line 19, in check_output
return subprocess.check_output(*args, **kwargs).decode("utf-8").strip()
File "/anaconda3/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
File "/anaconda3/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'pyclif']' returned non-zero exit status 1.

Can you tell us exactly what commands you ran before python setup.py install ?

git clone https://github.com/pykaldi/pykaldi.git
cd pykaldi
python setup.py install

Well, then you did not read the install instructions in the README :)

To install pykaldi from source, you need to install its dependencies first. I suggest you install the binary package via conda unless you need to install from source.

I am closing this but feel free to reopen it if you continue having install problems.


python 3.10, ubuntu 18.04 cannot pass test

I saw that OS Independent written in setup.py, and I was working on adding an OS other than ubuntu to the action.
But uuid_7 cannot pass a single testing; function test_time of class UUIDTests in test/test_uuid6.py
Is it critically big difference? or is it safe enough?
....F............
======================================================================
FAIL: test_time (test.test_uuid6.UUIDTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/me/work/uuid6-python/uuid6-python/test/test_uuid6.py", line 102, in test_time
    self.assertAlmostEqual(uuid_6.time / 10**7, uuid_1.time / 10**7, 3)
AssertionError:<PHONE_NUMBER>2.594696 !=<PHONE_NUMBER>2.591389 within 3 places (0.003307342529296875 difference)

----------------------------------------------------------------------
Ran 17 tests in 0.592s

FAILED (failures=1)

If this was in virtual machine, I would guess either it was a slow configuration and didn't execute the commands within 0.001 seconds or the clock wasn't accurate enough.


[Enhancement] support coalesce block cache read to reduce cache read overhead.

After moving the coalesce read below block cache, we need more cache operates for reading same data, which will bring some overhead like cache lookup, access update, etc. So, we also  coalesce block cache read and cache the data in io buffer map.
To reduce the repeated cache both in io buffer map and shared buffer, we also need to duplicate the overlapped range.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.1


preferences: Deprecate Windows 2k12 preferences

What this PR does / why we need it:
Windows Server 2k12 goes EOL on October 10th [1], after which support is only available for EUS customers. This change starts the deprecation cycle for our 2k12 preferences ahead of their removal in a future release of the project.
[1] https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

The Windows Server 2012 preferences have been deprecated ahead of the EOL of the underlying OS later this year.

/retest-required


Update scenario-isolate-vnets-custom.md

Added a more descriptive alt text for the image on the page.

@cherylmc
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close


App is recognized as game on Galaxy S8

I was working in the flutter demo and it started being recognized as a game on Galaxy S8. I created a new project and it was not showing this issue. Then I copied the new project main.dart to the old project but the problem was there.
Also I was working in another project and the same thing happend.
How can I prevent this of happening?
i'm including a link to my flutter demo project that is showing this issue https://drive.google.com/file/d/133_92Zk5YHvhZnqP7c6gn1gLKRGjcmnb/view?usp=sharing

What does that mean? Sounds like some Samsung specific functionality.

Indeed that's a Samsung specific functionality.  It adds extra functionality to games such as full screen mode, no alerts mode, screen record, etc. The Game Launcher Samsung app automaticily detecs apps that are games and includes an extra button in the navigation bar to access its configurations.
I don't recall changing anythig but main.dart. And here it is:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.display1,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

My flutter doctor -v output is as following:
[√] Flutter (Channel stable, v1.0.0, on Microsoft Windows [versÃ£o 10.0.16299.125], locale pt-BR)
    • Flutter version 1.0.0 at C:\Users\Rafael Marinho\flutter
    • Framework revision 5391447fae (5 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at C:\Users\Rafael Marinho\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 23.2.1
    • Dart plugin version 171.4424
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] VS Code (version 1.30.1)
    • VS Code at C:\Users\Rafael Marinho\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 2.21.1

[√] Connected device (1 available)
    • SM G950F • ce10171a3146842304 • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

Mind trying installing an apk version manually and verifying that its still the case?

I did this and the results are were the same.
I'm also attaching 2 pictures. The following shows the issue I'm facing (notice the extra 2 buttons in the navigation Bar on the botton, it indicates the app was recognized as a game)

The following shows how it was supposed to behave.

the same here as well in Galaxy A5. I have to remove the app from game launcher each time I install it!

Not sure there's much we can do since it's an OEM feature with opaque heuristics making incorrect assignments.
There are some guesses here
https://stackoverflow.com/questions/50174122/non-game-app-gets-treated-as-game-by-samsung-game-launcher
https://stackoverflow.com/questions/49287871/react-native-app-is-recognized-as-a-game-on-samsung-note8
but not clear how it works exactly.

For some reason, the Game Launcher recognizes the com.example package as a game, changing the package to the correct one should already work without problems.

Based on https://github.com/flutter/flutter/issues/26120#issuecomment-627559617 and https://github.com/flutter/flutter/issues/26120#issuecomment-700746005, I'm going to close this issue.
Feel free to open a new issue if there are specific things we can do in the framework or engine for similar issues in the future.

For some reason, the Game Launcher recognizes the com.example package as a game, changing the package to the correct one should already work without problems.

This worked for me


Invalid SPDX Identifier Field Symbols (IDFGH-12708)

The SPDX identifier field format is not being followed correctly when using --files add command. The ESP-IDF SBOM Tool is including the plus symbol from c++ packages in the file path or filenames. This is based on esp-idf-sbom v0.14.0.
For example:
FileName: ./esp-12.2.0_20230208/xtensa-esp32s3-elf/xtensa-esp32s3-elf/include/c++/12.2.0/parallel/algo.h
SPDXID: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-algo.h
FileChecksum: SHA1: 380d250ee001305577c9d50fbd5a924c4256c0f4
FileChecksum: SHA256: 50db25a884fc8209eb7acee134ab43b6eed025ae62f0a1c301711616a2eec8ff
LicenseInfoInFile: NOASSERTION
LicenseConcluded: NOASSERTION
FileCopyrightText: NOASSERTION

The official specification https://spdx.github.io/spdx-spec/v2.3/file-information/ states:

This causes problems for the official SPDX python tool, for example, when converting to another format like RDF:
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-algo.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-algobase.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-algorithm
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-algorithmfwd.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-balanced-quicksort.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-base.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-basic-iterator.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-checkers.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-compatibility.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-compiletime-settings.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-equally-split.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-features.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-find.h
spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: SPDXRef-FILE-xtensa-esp32s3-elf-xtensa-esp32s3-elf-esp-12.2.0-20230208-xtensa-esp32s3-elf-xtensa-esp32s3-elf-include-c++-12.2.0-parallel-find-selectors.h

In this case you could replace + with p. I could see other problems arising based on how people name packages or file paths. I do see that _ gets changed to - automatically.

Hello @JeremiahGillis ,
thank you very much for pointing this out.

In this case you could replace + with p. I could see other problems arising based on how people name packages or file paths. I do see that _ gets changed to - automatically.

The tool actually has sanitize_spdxid, which is using SPDXID_RE regex to replace the chars which are not allowed. You can see that both have a comment about the allowed chars, but the regex actually contains '+' :man_facepalming:  . Meaning it's not replaced. I don't know what I was thinking about. I will fix this.
Again thank you for reaching out and reporting this!

Thanks for fixing this! Good idea using the SPDX validation.


MSL: how to query bind-point of [image]_atomic buffer?

Asking in context of image-atomics emulation.
In CompilerMSL class function both memebers atomic_image_vars_emulated and get_metal_resource_index are protected.
For application it's required to have public api to check storage image for complementary _atomic binding.

	// Same as get_automatic_msl_resource_binding, but should only be used for combined image samplers, in which case the
	// sampler's binding is returned instead. For any other resource type, -1 is returned.
	// Secondary bindings are also used for the auxillary image atomic buffer.
	uint32_t get_automatic_msl_resource_binding_secondary(uint32_t id) const;


Adding third party licenses

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2641

Relevant Lines:
9018

💛  - Coveralls


ISPN-6302 Ignore DistributedServerTaskDeploymentIT

https://issues.jboss.org/browse/ISPN-6302
Unfortunately I couldn't find any solution for fixing this test. Applying a work around and returning back to the original author.

Integrated in master. Thanks @slaskawi !


Add minimum number of hits to pathway analysis

Many pathways have significant p-values but they also have very few hits (<=5) on the transcripts/proteins/formula. Other tools usually let user discard these pathways from the results since they're considered unreliable.

Moved to PALS https://github.com/glasgowcompbio/PALS/issues/40

Have updated on PALS, but we also need to update the front-end on WebOmics.


使用 nohup 后台运行，关闭会话下载就停止

我是在 树莓派上用的。
nohup python ~/soft/bypy/bypy.py downfile "xxxx"
下载正常
但关闭会话后
[=============_______] 66% (200.0MB/300.518MB) ETA: 4m27s (385KB/s, 8m51s gone) /usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/connectionpool.py:734: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html
InsecureRequestWarning)
Signal 1 received, Abort
Frame:

Signal 1 received, Abort
Frame:

请问有更好的方法么。

nohup bypy syncdown >/dev/null 2>&1 &


overflow: hidden;

Do we need the scroll bars?

I suggest to leave the overflow: auto
and here is a stackflow answer where they can keep scrolling and the scrolling bar is hidde
hidden scroll and can keep scrolling down


userspace: fix copy from user locking

We don't actually need spinlocks here.
For user_copy(), we are checking that the pointer/size passed in
from user mode represents an area that the thread can read or
write to. Then we do a memcpy into the kernel-side buffer,
which is used from then on. It's OK if another thread scribbles
on the buffer contents during the copy, as we have not yet
begun any examination of its contents yet.
For the z_user_string*_copy() functions, it's also possible
that another thread could scribble on the string contents,
but we do no analysis of the string other than to establish
a length. We just need to ensure that when these functions
exit, the copied string is NULL terminated.
For SMP, the spinlocks are removed as they will not prevent a
thread running on another CPU from changing the buffer/string
contents, we just need to safely deal with that possibility.
For UP, the locks do prevent another thread from stepping
in, but it's better to just safely deal with it rather than
affect the interrupt latency of the system.
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

This doesn't need to go into 1.14, 1.14 has no platforms which support both userspace and SMP.


chore: Update CI versions to latest to fix doc publish workflow

What does this PR do?

Update GitHub action workflow versions to latest
Pin python version for doc publish workflow to 3.11 (3.12 might be a bit too new for the libraries used)

Motivation

https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/actions/runs/6722082456/job/18269235482

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I ran pre-commit run -a with this PR

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

sweet - doc publishing workflow is back working again https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/actions/runs/6723239957/job/18272882974


chore: replace mocha and chai with tap

Checklist

[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

It all LGTM, will just test it with my changes

Maybe we can merge this next

@kibertoad
@Eomm
@gurgunday
PTAL


Date Added: Months Filter not working in Identify

From: https://forum.inaturalist.org/t/date-added-months-filter-not-working/17962 I can replicate.
Step 1:
Go to https://www.inaturalist.org/observations/identify
Step 2:
Click “Filters”
Step 3:
Click “More Filters”
Step 4:
Click “Months” under “Date Added”
Step 5:
Select “April”
(Note that it does not matter which month)
You will see that the url is now: https://www.inaturalist.org/observations/identify?created_month=4&createdDateType=month
Expected: Seeing observations that were uploaded in April (of any year)
Actual: Seeing observations that were uploaded most recently

Has this been deployed? Not seeing it working in production.

Has this been deployed? Not seeing it working in production.

I have not seen this in prod either.

Closed prematurely I guess. Do you still want to work on this, @pleary?


Though that was fixed, guess it disapeared in some master merge

Simple stencil fix for Born. I though it was in one of my previous PR but I guess I messed up somewhere with the merge/rebase.
Anyway, it is a simple typo fix u->U in the second stencil and diff operators for Born.

I'm trusting you and just merging this.

Merged.

Trust?! Is there no test?
On Thu, 9 Mar 2017 at 07:21 Fabio Luporini<EMAIL_ADDRESS>wrote:

I'm trusting you and just merging this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opesci/devito/pull/207#issuecomment-285274741, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFJRAwuNNlIqCJagDVBymIka2sLXoV-Cks5rj6hugaJpZM4MXdJi
.

No, this is something that has been missing for quite some time. Not sure if they have tests at the Julia level. I don't know how I could write a proper test for Born

There is a test in julia (and the slim branch as the correct Born), but the memory requirements are too high for TRAVIS.

There should be a way of writing a smaller test though. That'd be useful


Counter values buffer too big in Cnc file?

Hi ,
Is the counter values buffer the correct length in the cnc file? I've just cracked open the metadata section of a command control file when running the defaults. The labels and values buffers are both equal length (67108864). But label length is 1024 and value length is one cache line (64). Shouldn't the values buffer be .. erm.. 16 times smaller than the labels buffer?
( In MediaDriver.java  the two buffers are being created with the same value...)
                CncFileDescriptor.fillMetaData(
                    cncMetaDataBuffer,
                    CONDUCTOR_BUFFER_LENGTH,
                    TO_CLIENTS_BUFFER_LENGTH,
                    COUNTER_BUFFERS_LENGTH,
                    COUNTER_BUFFERS_LENGTH);

I think you are right. The labels file should be significantly larger than the counters file by about 16X.
@tmontgomery can you have a look?

I'll look at this soon. When I moved everything to the cnc file, I used the then current sizes as specified. Which didn't seem right, but I wanted to not change them at that time. But, yes, they do need to be modified.

Reopening to set different sizes for buffers.
1MB values
1MB labels
256 bytes label size

From @mjpt777 : Label size of 124 bytes + 4 bytes for length so each is 2 cache lines. This will be the same as the counters.


Duplicated records

There are source records that are duplicated (in the source dataset) but some have address information or date information while others do not.

Fixed with b998ac970576182a10e8a3353f6d332c39f810c7


Special characters in usernames fail logins after the first

For our application users use email addresses for their username.  If this email address has a + in it like<EMAIL_ADDRESS>the username is created in wordpress as<EMAIL_ADDRESS> After the user logs out and tried to log back in authentication fails with this logged:
[20-Apr-2021 15:32:29 UTC] [AuthLDAP] The LDAP user does not have an entry in the WP-Database, a new WP account will be created
[20-Apr-2021 15:32:29 UTC] [AuthLDAP] Error creating user : Sorry, that username already exists!

If I don't get an internal ticket to fix this I am unlikely to fix it but if I do will you accept a PR?

I'd be happy to receive a PR to fix this. Though it might be an issue with WordPress' way of "sanitizing" usernames... 😕

Have a look at https://wordpress.stackexchange.com/questions/22056/where-can-i-find-documentation-on-what-characters-are-allowed-in-user-names-and


The Asset Editor "Extract All" uses seemingly legacy file explorer

Can you please use the explorer instead please? If this is meant to be fully cross-platform then maybe I can understand and if that's so please tell me, but otherwise could you please use the explorer instead?

Extract all uses the folder picker rather than file picker, which makes the most sense in that context.

If that's so, can you provide the option to manually specify the folder path? It's slightly annoying to traverse the file system with.


Re-add cold blocks tag & remove debug messages

Closes #6 #4

Hey, I'm so sorry. I never got a notification about this pull request from GitHub.
Unfortunately, I'll be unavailable this weekend to review this, but I will be back Tuesday night to have a look.
If you do not hear from me by Wednesday, ping me here. Thanks

Thank you for your update! Sorry once again, I've been extremely busy these past few weeks. I'll be working on getting this on Curseforge asap.


i18n(pt-BR): Update astro-pages.mdx translation

Description (required)
Updated astro-pages.mdx with content about Page Partials
Updated to use  and  components
Update some typo/diffs between en/pt-BR texts, like bold words and code parts.

@Fryuni, you are awesome, thanks for the great feedback! This is actually my first PR ever so I have a question, after I review these changes should I commit one by one or it's better to batch commit at the files tab?


display.image Images no Longer Zoom

In the zoom function, self.width and self.height (in panes.js lines 451 and 452) are always 0 (so the image disappears when a user tries to zoom by scrolling).  It doesn't seem to be due to an update in the display utility, but I'm wondering if anyone else has experienced this issue and has tracked down a root cause.

See https://github.com/szym/display/pull/40
I don't know know why it is not merged yet.

Thanks so much!


Upgrade to using Heroku Platform API v3

Hey, it would be great to get you on the latest and greatest API here. This would involve some transition for you, likely from the heroku-api gem to heroics. v3 is still in Beta presently, but we are nearing GA rapidly and I think there are a lot of great benefits to using the newer system.
You can find docs for the the API here: https://devcenter.heroku.com/articles/platform-api-reference
And more about heroics here: https://github.com/heroku/heroics
I'm certainly happy to answer any concerns or questions along the way, just wanted to reach out to you and start the discussion (I work at Heroku on the API team and designed the new API, so hopefully I can help with any issues you might have).
Thanks!

Done!


Explicitely mention application.rst

New applications needs to be added to application.rst. Sphinx is otherwise not picking up now applications.

Codecov Report

Merging #635 (5eb0333) into main (f0a3c5d) will decrease coverage by 0.72%.
Report is 24 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #635      +/-   ##
==========================================
- Coverage   99.28%   98.57%   -0.72%
==========================================
  Files          39       39
  Lines        3518     3518
==========================================
- Hits         3493     3468      -25
- Misses         25       50      +25

see 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I added the applications that were missing and corrected the alphabetical order. Maybe @orelgueta  can have a quick look now?


tidy deploymenmt folder

as we no longer maintain deployment files for multiple k8s versions just place sriov-cni-daemonset.yaml in images folder instead of its own subfolder.
Signed-off-by: adrianc<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.0%) to 38.027%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0%

Covered Lines:
424

Relevant Lines:
1115

💛  - Coveralls

CI failures not related to this PR, Merging.


预览模式下空行丢失

Feature Requested

Relevant Screenshots
If applicable, add screenshots to help explain your request.
Checklist

[ ] The feature would be useful to more users than just me. (→ If it's only relevant to you, have you considered using a CSS Snippet?)

通过自定义 Snippet 处理了


Unable to resolve "react-native-vector-icons/AntDesign" from "node_modules/react-native-elements/src/helpers/getIconType.js"

I'm trying to use react-native-elements:
import { ListItem } from 'react-native-elements'
I ran:
yarn add react-native-elements
I'm getting the error:
Unable to resolve "react-native-vector-icons/AntDesign" from "node_modules/react-native-elements/src/helpers/getIconType.js"
Failed building JavaScript bundle.

I think this is some messy dependency issue. In general, I'd like to know a foolproof way to clean up all my dependencies. I copied my package.json below.
React Native version:
info
  React Native Environment Info:
    System:
      OS: macOS 10.14.6
      CPU: (8) x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
      Memory: 1.13 GB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 8.11.2 - /usr/local/bin/node
      Yarn: 1.19.1 - /usr/local/bin/yarn
      npm: 6.13.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
      Android SDK:
        API Levels: 28
        Build Tools: 28.0.0
        System Images: android-29 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.5 AI-191.8<IP_ADDRESS>00203
      Xcode: 11.2/11B52 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1

Steps To Reproduce

yarn add react-native-elements
expo start --ios

Describe what you expected to happen:
I expected the JavaScript bundle to build and run.
Snack, code example, screenshot, or link to a repository:
My package.json:
{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "@aws-amplify/api": "^1.2.4",
    "@aws-amplify/pubsub": "^1.2.4",
    "@babel/runtime": "7.5.0",
    "aws-amplify": "^1.2.4",
    "aws-amplify-react-native": "^2.2.3",
    "eslint": "^6.6.0",
    "expo": "^35.0.0",
    "global": "^4.4.0",
    "moment": "^2.24.0",
    "native-base": "^2.13.8",
    "react": "16.8.3",
    "react-dom": "16.8.3",
    "react-native": "https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz",
    "react-native-elements": "^1.2.7",
    "react-native-gesture-handler": "~1.3.0",
    "react-native-web": "^0.11.7",
    "react-navigation": "^4.0.10",
    "react-navigation-stack": "^1.10.3"
  },
  "devDependencies": {
    "babel-preset-expo": "^7.1.0"
  },
  "private": true
}

You haven't installed react-native-vector-icons dependency which is mandatory to use react native elements. Refer to the react native elements docs.
https://react-native-elements.github.io/react-native-elements/docs/getting_started.html

@darkstar3057 You haven't installed the react-native-vector-icons dependency which is mandatory to use react native elements.
https://react-native-elements.github.io/react-native-elements/docs/getting_started.html


Enabled empty responses

If a zone exists but no records was set, it will always respond the SOA record, which is (compared to bind) the wrong behaviour. So i would push this answer instead:
res.answer.push({ name: question.name, type: question.type, data: null });

With my changes it's possible to return an empty response if the data attribute is set to null.
I hope its helpful 😊

Hi tsndr,
It is helpful.
Please keep in mind that the DNS protocol has a special flag (NXDOMAIN) that must be set for empty responses.
I have had the same issue 2 years ago, see #5 but this project is not maintained any more.
Cheers, fogs

Hi fogs,
thanks for the answer 😊
What do you think about a nodejs bade dns server in general? Only for testing or production ready? And what about the performance compared to bind, could it ever hold up?
Cheers,
Tobi 😊

If you are interested in availability, scalability, security, then choose one of the big and mature servers. PowerDNS rocks. If you like to play with the protocol, use it for stuff it was never intended to and don't think it hurts to learn more about DNS, there is no better way than building your own. We did both.
Cheers mate!

Ach. Und Grüße nach Remagen.

I've never heard of PowerDNS, I might look into that 😊
I am using bind right now, but maybe I'll switch, we'll see 😉
Viele Grüße nach Hamburg 😊


Hello world is too complicated for 1st timer

tl:dr;
The hello world should start with
func hello(_ name: String? = nil) -> String{
return "fix this"
}

Background
I am a very advanced programmer. I started the swift course today with my girlfriend as she wanted to learn swift (her team uses it). It was remarkably confusing. In the end, we googled a solution(which didn't work) submitted it anyways. Then looked at the other solutions to get the answer. This process took about 3 hours all said and done
Complexities in the Method signature
func hello(_ name: String? = nil) -> String{
return ""
}

To get this to compile. you have to write this method. Let's look at the pieces
Basic signature
func hello(name: String) -> String

I felt that this is reasonable. The documentation has pieces that show how to make a method. but it does not work. The compiler errors are confusing so I thought it might need a class
class HelloWorld{
func hello(name: String) -> String
}

this makes things worse.
The underscore
_

This means that you don't have to call the method with the parameter label.
Which you don't. So removing it breaks the build. While I've seen many languages that have optional parameter names, this is the first I've seen where the default is non-optional. optional parameter names is a decently complex language feature to have to understand for hello world.
The Question Mark ?
 String?

Nullable strings (or Nilable?) because you are passing in nil (you actually aren't but effectively are by not declaring the variable)  means you have to understand nil and ? both of which are a bit complex and ? is hard to google, although seeing it from the you just have to know to do this first, then google. it's not something we would have ever googled.
I tried to do this with method overloading (writing two method) but it didn't work, possibly because they were in a class at the time, I don't remember.
The default value
= nil

This is an other fairly advanced concept. That if you don't pass in a value one is taken care of for you.
Feedback while failing
All of this feedback is at the compiler level, because until it compiles you get nothing. Compiler messages are confusing. And there is no help for the brand new swift programmer.
This could also be solved by changing the test to require a less robust signature in the function. just removing the null case and adding the named parameters would lead to
func hello(name: String) -> String{
return "fix this"
}

Which I (as an advanced program) fell I could have reasonable figured out.
But I still think you should just include the method signature you want. I don't think that is what you are trying to focus on at the moment for Hello world.

ps, if this bug report seems a bit too long for hello world, that is kind of my point.

@isidore I agree. Can you submit a PR with this change?

I can, but would prefer not to for just one line, do you mind doing it?

Related. https://github.com/exercism/exercism/issues/4707#issuecomment-491575304

What to write in a code to pass test?

When the file first opens in the editor, and the tests have ran, what do the tests say?  It should almost give the answer there.  The code given, the string itself, is what is causing it to not pass.  We may write the string that the test run is reporting it should be, and it should pass.
I hope that helps, @darya-yilmaz .

Since the source given, the following:
func hello() -> String {
  return "Goodbye, Mars!"
}

Is the code delivered now, I think this can be closed.


Add core tests & test workflow

To make sure things are working as expected (with confidence), this project could really use some automated tests. Planning to go with Mocha and Chai.

Merged: https://github.com/nwittwer/shift/pull/78


STITCH-2212 Swift SDK: Create a skeleton for sync operations and the data synchronizer

Add the skeletons for CoreSync and DataSynchronizer. We (essentially) get the entirety CoreSync here for free, since on Swift, it is a simple delegate for the DataSynchronizer.
This includes the NetworkMonitor and AuthMonitor protocols.
I've also added an internal FatalErrorListener for the arbitrary lower-level errors that can occur due to MongoSwift or otherwise. It is meant to listen for "impossible states", and will pass along whatever information it can to the user.
Though the PR seems large, much of it is tests/comments, and many of the DataSynchronizer methods are stubs. This should allow us to not step on each other for future tickets.

As discussed, a follow-up tech debt JIRA ticket should be created to rationalize the error handling into a consistent framework -- ideal dichotomy of "recoverable errors" (passed to a handler) vs "non-recoverable errors" (propagated)