permission to delete pages on the wiki

Hey, can I get permission to delete pages?  I found some new spam ones like this https://wiki.creativecommons.org/index.php?title=Call_Florida...(<IP_ADDRESS>.<IP_ADDRESS>.2.3.0_Quickbooks_p.r.o_s.u.p.p.o.r.t._p.h.o.n.e_n.u.m.b.e.r,_Quickbooks_t.e.c.h_s.u.p.p.o.r.t_n.u.m.b.e.r&redirect=no
And I've already pulled permission from that user.
~Mari

Eek how are they getting through?
I'll make sure you have the relevant permissions then show you how to clean
up quickly after them. Do you have ten minutes for a call about this on
Monday?
On 24 Jul 2016 3:28 p.m., "Mari Moreshead"<EMAIL_ADDRESS>wrote:

Hey, can I get permission to delete pages? I found some new spam ones like
this
https://wiki.creativecommons.org/index.php?title=Call_Florida...(<IP_ADDRESS>.<IP_ADDRESS>.2.3.0_Quickbooks_p.r.o_s.u.p.p.o.r.t._p.h.o.n.e_n.u.m.b.e.r,_Quickbooks_t.e.c.h_s.u.p.p.o.r.t_n.u.m.b.e.r&redirect=no
And I've already pulled permission from that user.
~Mari
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/wiki/issues/42, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABU8sbssBOY2ud9xwg3wyr8cRuSEoXeks5qY-cWgaJpZM4JTr0m
.

@robmyers Let me catch up on regular stuff today and we can talk on Tuesday!

OK cool! :-)
On Mon, Jul 25, 2016 at 6:48 AM, Mari Moreshead<EMAIL_ADDRESS>wrote:

@robmyers https://github.com/robmyers Let me catch up on regular stuff
today and we can talk on Tuesday!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/wiki/issues/42#issuecomment-234957884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABU8tMkDLzaKkKaj2KW-qe7bniQ_K-iks5qZL6rgaJpZM4JTr0m
.

Thanks @robmyers - I've now started asking people what they plan on editing (not in mean way like detective might ask, more like how a cheerleader might ask a pledge why they want to join the best squad around sort of way).  I promise to use my powers for good.

That sounds great.  checkbox but I'm not sure spammers would go for it...


Expand test coverage

There is currently at least one test (test_power_a) where the combination of floated parameters is not actually picked up by the estimate_parameters function of the model.
We need to check if this is the only test where this is the case and fix them all.

Agreed: we should expand the test coverage to cover every heuristic path.
It would also be good to get some tests which use noisy, sparsely-sampled data rather than relying on the noise-free, uniformly-sampled data we have in these tests. We did some of this kind of testing when developing the original fit functions (e.g. checking how FFT-based heuristics behave with sparsely-sampled data) but they never made it into the test suite.
It would also be nice to have some data which is not generated from exactly the same model we're fitting to -- e.g. real lab data where the model is a reasonable approximation of the underlying distribution, but there are still some noticeable systematics. We should still expect robust fits in this case.
A related question is more generally what we want to do about testing heuristics. At present we just check that the fit converges and take a view that "heuristics working means they get us close enough for the main solver to pass." That's a pretty decent functional definition, however it allows for the possibility that heuristics are considered working when they functioning as intended but aren't sufficiently broken to cause the fit to fail to converge. That seems rather unsatisfactory and allows bugs to hide undetected. Ideally we would have some tests specific to heuristics.
That is probably easy to implement but we need to decide what we want first. IME it's hard to put a tolerance on heuristics that is tight enough to catch errors but not so tight that they fail regularly. I'm not sure what the best approach here is.

would be nice to set some heuristic tolerances as well. That will catch gross errors in the heuristics

One thing we really need is a way of running tests where the datasets are passed in


spotify_player stop music when quitting it

Hi, thanks for your work. Awesome app! I use it and love it a lot!
Describe the bug
When I launch a song in spotify_player (the Spotify app launches but does not play anything), it works but stops as soon as I quit the app from the terminal. However, if I launch a song from Spotify itself first, other manipulations work as expected.
When I play music from spotify_player, I can relaunch it after quitting spotify_player using the "play" button on my keyboard, but it would be better if the music didn't stop at all. I don't know if something can be done about this.
To Reproduce
On macOS (I don't know about other systems):

Launch the Spotify app.
Play a song in spotify_player.
Quit spotify_player (the music should stop).

Expected behaviour
Music shouldn't stop after quitting spotify_player.
Log and backtrace
Only infos in logs (nothing intersting) and no backtrace on the issue.
Environment

OS: MAC OS 15.0 (Apple silicon)
Application version: spotify_player v0.19.1, spotify <IP_ADDRESS>4.gf06e5cee

Additional context
I've install spotify_player with homebrew.

hmm music stops when you close the app is kinda unexpected when streaming is handled by the app. Not sure what is the bug here. Do you specifically mean if you stream music from an external source and use spotify_player as the remote control device, quitting the app stops the music played the external source?

this also happens for me.
if i start streaming from the spotify app it will keep playing, but if i start playing from spotify_player it will stop as soon as spotify_player is quit.
if tested these scenarios

spotify app is running, but not playing anything

start with spotify_player

quit spotify_player

music stops

spotify app not running

start music with spotify_player

quit spotify_player

music stops

start music with spotify app

change track with spotify_player

quit spotify_player

music still plays

spotify app is running, but not playing anything

start music with spotify_player

change music with app

quit spotify_player

music stops

so it seems to be only when streaming originates from spotify_player

look expected to me. Not sure why you guys expect music to continue playing when exiting the spotify_player app

I don't think we expected it to keep running. It makes sense that it doesn't.
I think we were just saying it would be nice if it could continue running after exiting (like with a daemon or something)


fix num_bits always returning full size

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (main)
[ ] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[ ] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

Apparently lint job is broken if there're changes done to md files

@Pratyush CI is green


Slack Integration

It would be great to have the ability to send information to a Slack channel when an event occurs.
It should be configure on project level, like the Web Hook integration.
The picture is from the Bugsnag configuration in Slack. Looks like they just uses the Slack Webhook.

This is the Slack setup instructions for a Webhook.

+1

Setup an Incoming WebHook in Slack.
Use the Webhook URL from Slack in the web.config
https://gist.github.com/a045a02611900f4db7d3.git

I'm closing this as it's now merged into 177.


Admins can or not control the client updates?

But also you wrote on the VDI section:
You must uninstall the current version to update to a newer version.
I'm reading this so, that there IS a possibility to control the updates on regular workstations like on the VDIs. So perhaps you should be a bit more specific on this?

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

ID: f6da28da-eb7b-d3ae-4c2f-8f87803b1830
Version Independent ID: 8c42d7a2-80c6-86dd-347a-ed6d8d909c41
Content: Teams updates - Microsoft Teams
Content Source: Teams/teams-client-update.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Hi @Petri-X,
I think the article clearly states that they are different processes:

Non-VDI clients: update automatically
VDI clients: you must run the MSI

Any process not included in the article is not supported, like running the VDI MSI to update Teams desktop client.

Hi @dariomws,
We could of course discuss if the message is "clearly" as this:
Can admins deploy updates. . .
Does not make any differences between non VDI and others.
But you made that very clear now.
Someone else of course could ask: what makes so big difference between VDI and non-VDI for Teams client that there must be so strong lines (supported vs. not supported). As at the end, it is still the same client.
But thank you for your reply.


Roll engine c28d23068fc3..85e6b01ae263 (7 commits)

https://github.com/flutter/engine/compare/c28d23068fc3...85e6b01ae263
git log c28d23068fc3..85e6b01ae263 --first-parent --oneline
2020-03-12<EMAIL_ADDRESS>Roll src/third_party/dart 33349076ee7f..7c2f62406bef (23 commits) (flutter/engine#17120)
2020-03-12<EMAIL_ADDRESS>[fuchsia] Change vsync trace name back to "vsync callback" on Fuchsia (flutter/engine#17118)
2020-03-12<EMAIL_ADDRESS>Roll src/third_party/skia 9b449b73d367..bb7684276afd (12 commits) (flutter/engine#17117)
2020-03-12<EMAIL_ADDRESS>build a precompiled SDK with canvas kit enabled (flutter/engine#17115)
2020-03-12<EMAIL_ADDRESS>Fix link in readme (flutter/engine#17119)
2020-03-12<EMAIL_ADDRESS>Define embedding dependencies in Gradle (flutter/engine#17116)
2020-03-12<EMAIL_ADDRESS>Roll src/third_party/skia 1743144ab839..9b449b73d367 (5 commits) (flutter/engine#17113)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Commit queue failed; closing this roll.


pakka gui hash dropdown

Hi,
Using the pakka gui, could the list of drop down hashes be updated.
My benchmarks are:
WHIRLPOOL:    98.04 MB/s (done   490.19 MB)
SHA-3:   221.25 MB/s (done     1.08 GB)
SHA-256:   231.40 MB/s (done     1.13 GB)
SHA-1:   450.44 MB/s (done     2.20 GB)
MD5:   529.40 MB/s (done     2.58 GB)
HIGHWAY64:   813.60 MB/s (done     3.97 GB)
BLAKE3:     2.03 GB/s (done    10.14 GB)
XXHASH64:     4.06 GB/s (done    20.32 GB)
XXH3:     4.40 GB/s (done    21.94 GB)
CRC-32C:     4.86 GB/s (done    24.22 GB)
WYHASH:     6.05 GB/s (done    30.17 GB)
CRC-32:     6.14 GB/s (done    30.61 GB)
NILSIMSA:     6.15 GB/s (done    30.67 GB)
So, would using NILSIMSA make more sense (for speed) than using the defaut pakka hash of xxhash ?

NILSIMSA is the contrary of an hash (!)
It is a very rough measure of SIMILARITY and not of DIFFERENCE between files. It is used to identify emails that differ by only a few details (the .eml files that contain them). The goal is to determine if, in large quantities of emails (typically hundreds of thousands), there are many duplicates. This cannot be done with a 'true' hash, where even a single bit of difference results in a completely different hash value.
You cannot use NILSIMSA (or wyhash) as an internal hash for zpaqfranz. Only for the sum, hash, d (deduplicate) etc

In your case XXHASH64 is faster than (realistically) your media
If you have (for example) an SSD capable of transferring (say) 400MB/s real-world and you use whirlpool (~100MB/s) you will get a huge slowdown
For a 4GB/s hash (vs. 400MB/s) this will be much smaller
=>
the xxhash64 is very fast even on not very powerful CPU
=>
a good default choice
XXH3 (aka xxhash-128) is even better BUT runs poorly on older 32 bit CPU => then XXH64 instead of XXH128

Here you can find other infos
https://github.com/fcorbelli/zpaqfranz/wiki/Voodoo-checksums
LSS
If are paranoid, you can use BLAKE3 (very good, fast indeed)
If you have a newer CPU (with HW support) you can choose SHA256 (very fast, very widespreaded, ~2GB/s)
Or you can use the default, fast & good enough


[Port dspace-7_x] Fix minor collection form bugs

Port of #2350 to dspace-7_x.

Verified this is an exact port of #2350 to dspace-7_x.  Code was tested/approved in #2350, so merging immediately.


This if statement doesn't seem to do anything, safe to remove?

git blame goes to @dmitrig01
https://github.com/BranchMetrics/Smart-App-Banner-Deep-Linking-Web-SDK/blob/master/src/0_storage.js#L18

this one?
if (TITANIUM_BUILD) {
	/** @typedef {{listProperties: function(), setString: function({string}, {string}), getString: function({string})}}*/
	Ti.App.Properties;
}

Yes. Just a cautionary check in case we missed some logic. :)

Well, this doesn't belong in this file (it belongs in externs), but it is important: https://developers.google.com/closure/compiler/docs/api-tutorial3#externs
(it's really worth reading the entire "Advanced Topics" section of the closure compiler docs)

Cool. Thanks for the info. I will investigate the possibility of either:
1, rewrite this so that it doesn't trigger the lint.sh warning
2, add a jshint comment to suppress the said warning.
Thanks very much, @dmitrig01 !


Don't throw InvalidArgumentException if passed an anonymous class

Partial fix for phpDocumentor/ReflectionDocBlock#180

Heya @iggyvolz, Thanks for the contribution. Can you perhaps add a test for this behaviour change? It sounds like a good addition!


Handle unimplemented optional arguments in _wraps

In the _CheckAgainstNumpy tests, any unimplemented optional arguments are effectively the numpy defaults. If these unimplemented arguments are passed into the jax version, for some arguments the value is checked against the default, for other arguments an unexpected argument TypeError is raised.
Would it make sense to move this validation and error handling into _wraps? Specifically, if an unexpected argument is passed into a _wraps function, if the value doesn't match the default value for numpy, raise NotImplementedError.
Possible benefits are (1) more valid inputs that are consistent with numpy, (2) some cleanup in lax_numpy, and (3) less maintenance when upgrading the reference numpy version. On the other hand, inspect.getfullargspec doesn't seem to be working on numpy==1.18.4, possibly related to this issue. There are probably other barriers that I'm overlooking.

Assuming it's technically feasible, this makes sense to me. Although I'm guessing this would require creating an extra wrapper function to do the argument handling, which might be irritating or confusing when debugging (jax creates enough stack frames already).

One thing to keep in mind: any extra processing done by _wraps will be done every time the package is loaded. Import of jax.numpy is already noticeably slow because of the wrapping and docstring munging that’s happening in _wraps. For something like this that is essentially a static check, I’d lean toward a test instead.

this would require creating an extra wrapper function to do the argument handling, which might be irritating or confusing when debugging

Good point. And maybe there is some value to explicit handling, almost as a form of documentation in lax_numpy of where the priority gaps are in the implementation.

any extra processing done by _wraps will be done every time the package is loaded

Maybe this comes down to the cost of inspection. @jakevdp How did you use inspect.signature with numpy? Tried a few versions without success.

It works for some objects, but not others:
import numpy as np
import inspect
inspect.signature(np.linspace)

<Signature (start, stop, num=50, endpoint=True, retstep=False, dtype=None, axis=0)>

I think this has been addressed as well as it can be.


GdipGetPathGradientTransform for paths with preset blends returns WrongState but should succeed

Dupe https://github.com/mono/libgdiplus/issues/467


Add note on "+1 comments" to CONTRIBUTING

cc @atom/core
In my heart I just want to say that "+1 comments will be deleted" but that's a strong hand. Let's start with a kind suggestion.

+1 :laughing:
Sorry, couldn't resist :wink:

I should have expected that.

Part of me kind of likes them now. It shows interest. It separates the popular or painful issues from the rest. I ignore then 100% of the time, but they are useful when going back to an issue to gauge popularity.

the conversation to date sounds a bit weird to me.  Why not just the conversation?
Also, how about ...the conversation and also sends notifications...?

Adding on to @benogle, +1 comments are helpful to a new/empty issue, but once multiple people have started to +1, then it becomes useless.

then it becomes useless

Maybe after an insane amount. But difference between 1, 10, and 50-100 is significant.

I agree that +1s have a definite diminishing returns facet to them. Also, I feel like many +1s are not looking at the whole issue. There have been multiple occasions where I've had to point out that an issue has been solved when people just read the initial bug report, jump to the bottom and +1 it.
On the other hand, I think this is an opportunity for GitHub. I filed a feature request a while back for Starring Issues. This would:

Allow me to mark Issues that I want to remember, come back to or check up on (over and above the gigantic swath of Atom issues I look at in my notifications)
Allow me to register "me too" ... equating to a +1

This feature would remove the noise from the comment stream and still afford the function that @benogle is suggesting.

I personally do not mind the :+1: comments, though I wouldn't mind having them aggregated into the body of the issue or something. I'm not subscribed on as many issues as you guys, but seeing a :+1: pop into my email for the one's I do watch can be a helpful gauge for me.

Voting for issues can be a useful feature indeed. It's used to great success in Jira for example.
But it should really be a default feature on each comment, rather than adding a new one.
Zenhub adds a +1 box accordingly:

Voting for issues can be a useful feature indeed

I disagree. Everyone seems to agree that "design by committee" is bad, but still wants issue voting at the same time. People will come in with the expectation that the folks working on the software full time are beholden to the vote count, no matter what expectations are set. Would you put your software project on reddit and add whatever feature gets the most upvotes?

There's really no need to go to the extreme.
Like @benogle said, it can be very useful to gauge the demand for an issue, without committing yourself to be "beholden to the vote count". More of an indicator for informational purposes than a mandate.
If it's implemented as a little +1 or :+1:  box in the corner, it also helps preventing this from becoming spam, while allowing you to ignore the vote count if you wish.

People will come in with the expectation that the folks working on the software full time are beholden to the vote count, no matter what expectations are set.

People already come in with that expectation. Just look at the spate of anti-metrics-package bugs lately, even including ones that see that it has been asked, answered and closed ... but file a new bug anyway. Or the "Remove Trailing Whitespace shouldn't be the default" issue that has been closed for nearly a year now yet has been commented on as recently as two days ago. The "tyranny of the majority" is something that has to be dealt with on any open source project ... whether we have voting buttons or stars or just :+1: in the comments.

Worth pointing out that Google Code has issue starring, but Chromium still gets the occasional issue with hundreds of +1s comments.

Everyone seems to agree that "design by committee" is bad, but still wants issue voting at the same time.

I definitely dont think we should blindly make something in a super popular issue, but it is a nice indicator for pain people are having.

If the majority ruled we'd still have slaves in the US.  Or at least for
many more years.
It's obvious that instead of majority rule everyone should just do what I
want.
On Wed, Feb 25, 2015 at 9:45 AM, Ben Ogle<EMAIL_ADDRESS>wrote:

Everyone seems to agree that "design by committee" is bad, but still wants
issue voting at the same time.
I definitely dont think we should blindly make something in a super
popular issue, but it is a nice indicator for pain people are having.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/pull/5729#issuecomment-76015375.

Closing this out, I think we've found a nice middle ground of locking issues when appropriate and this doesn't need to be explicit in the docs.


too much D:

auto-commit: .github, for test
auto-commit: .github, for test
too much D:

This is a lot of refactor right before the demo tomorrow. Could we just make the necessary changes for now and focus on refactoring down the road?

I  agree that this not ideal, and I also don't like it, but facts are that the demo will only be possible if I don't take the time to separate these changes right now. I apologize and will strive to do better.


enh(clojure) Adds global definitions with class name title

https://github.com/highlightjs/highlight.js/issues/2420

@agrison Look good to you?

Awesome, looks good @yyyc514 I will take a close look this evening !

@agrison Did you have a change to take a look?

Yes it looks good, nice work !


add illumos support

This pull request adds support for building on illumos systems (e.g., OmniOS, OpenIndiana, etc).  I have been using this library with the rtdlib Rust crate for a while now on my illumos system.

The pull request looks very promising. It seems that most changes must be applied to build TDLib also on Solaris and aren't specific to illumos. I.e. CMAKE_SYSTEM_NAME STREQUAL "SunOS" can be used instead of ILLUMOS and TD_SOLARIS can be used instead of TD_ILLUMOS.
Also, the function td_set_up_compiler is supposed to be self-sufficient, so it shouldn't depend on include(illumos) in the main CMakeLists.txt, It can detect illumos itself, but there are seems to be no reasons to ditinguish it from other SunOS-derived operating systems.

Solaris doesn't have epoll and eventfd, so TD_ILLUMOS is still needed, but it would be better to identify it using a define as identified all other operating systems.

The pull request looks very promising. It seems that most changes must be applied to build TDLib also on Solaris and aren't specific to illumos. I.e. CMAKE_SYSTEM_NAME STREQUAL "SunOS" can be used instead of ILLUMOS and TD_SOLARIS can be used instead of TD_ILLUMOS.
Solaris doesn't have epoll and eventfd, so TD_ILLUMOS is still needed

Right, Oracle have diverged with their proprietary fork over the last ten years.  Support for epoll is just one thing that's different in illumos.  Over time we expect there will be more differences, so we generally feel pretty strongly about not being lumped in with Solaris anymore -- we're a different platform.

Also, the function td_set_up_compiler is supposed to be self-sufficient, so it shouldn't depend on include(illumos) in the main CMakeLists.txt, It can detect illumos itself, but there are seems to be no reasons to ditinguish it from other SunOS-derived operating systems.

There is at least one divergence: illumos requires -lnsl -lsocket whereas, say, Oracle Solaris 11.4 probably doesn't anymore.
I would have used a macro, but unfortunately we don't have one available at present that distinguishes us from Solaris systems; hence the detection logic in illumos.cmake.
I have added include(illumos) into td_set_up_compiler() and tested that it still appears to build correctly -- is that sufficiently self-contained?

There is at least one divergence: illumos requires -lnsl -lsocket whereas, say, Oracle Solaris 11.4 probably doesn't anymore.

If these libraries still exist on Solaris, it should be fine to explicitly link them.

I have added include(illumos) into td_set_up_compiler() and tested that it still appears to build correctly -- is that sufficiently self-contained?

This would be much better.

-ffunction-sections -fdata-sections also needs to be disabled on illumos, because without linker support of --gc-sections --exclude-libs,ALL they only increase binary size.
Is there are any alternative to them for removing unused functions on illumos?

authorizationStateWaitTdlibParameters

CMake/illumos.cmake

https://github.com/tdlib/td/blob/eb80924dad30af4e6d8385d058bb7e847174df5e/example/java/org/drinkless/tdlib/example/Example.java#L304

-ffunction-sections -fdata-sections also needs to be disabled on illumos, because without linker support of --gc-sections --exclude-libs,ALL they only increase binary size.
Is there are any alternative to them for removing unused functions on illumos?

We have -z ignore, which does something that sounds similar but might end up doing more things.  From ld(1):
       -z ignore | record

           Ignores, or records, dynamic dependencies that are not referenced
           as part of the link-edit. Ignores, or records, unreferenced ELF
           sections from the relocatable objects that are read as part of the
           link-edit. By default, -z record is in effect.

           If an ELF section is ignored, the section is eliminated from the
           output file being generated. A section is ignored when three
           conditions are true. The eliminated section must contribute to an
           allocatable segment. The eliminated section must provide no global
           symbols. No other section from any object that contributes to the
           link-edit, must reference an eliminated section.

I can try and built the library with that option in effect and see how it goes.
As an aside, are the comments from VChernomYA just spam that I can ignore?  It's hard to understand what's going on there...
Cheers.

@jclulow

As an aside, are the comments from VChernomYA just spam that I can ignore?

Yes, comments from VChernomYA are completely unrelated.

I can try and built the library with that option in effect and see how it goes.

I would like to see the result. If it works as expected, then adding the option will make illumos on par with other operating systems. Otherwise the options -ffunction-sections -fdata-sections will also need to be disabled.

@jclulow In my tests -z ignore had no considerable impact on shared library or executable file size.


New feature ideas - Voice Recognition for myanmar colors

I think there should be voice recognition for Myanmar colors - ဝါ, စိမ်း, နီ, ပြာ, ဖြူ, နက်

I confirm this idea and will try to implement this soon...


fix: urlencode proxy username and password

Fix for proxy credentials containing special characters such as ?.

Thanks :octocat:


Fix bug of hatoba model has not array of string

Summary

Fix bug of hatoba model has not array of string

Test

[x] LGTM

🐛 🐭


X_new, Y_new paramters not used in GPyOpt.models.gpmodel.UpdateModel

The code segment is as follows:
def updateModel(self, X_all, Y_all, X_new, Y_new):
        """
        Updates the model with new observations.
        """
        if self.model is None:
            self._create_model(X_all, Y_all)
        else:
            self.model.set_XY(X_all, Y_all)

        # WARNING: Even if self.max_iters=0, the hyperparameters are bit modified...
        if self.max_iters > 0:
            # --- update the model maximizing the marginal likelihood.
            if self.optimize_restarts==1:
                self.model.optimize(optimizer=self.optimizer, max_iters = self.max_iters, messages=False, ipython_notebook=False)
            else:
                self.model.optimize_restarts(num_restarts=self.optimize_restarts, optimizer=self.optimizer, max_iters = self.max_iters, verbose=self.verbose)

The paramters X_new, Y_new do not seem to be considerd...

Pretty sure that was reserved for some "future" functionality that never got implemented. It is probably safe to clean up now. Happy to accept a PR!

The design behind this API is that some wrapper model may be able to take the advantage of incremental data such as online learning. As the GP model always needs the full dataset, it just discards the X_new and Y_new.


Hyperlink not working

If we use  tag for hyperlink in html template and convert to pdf. link is not clickable in pdf file.

Did you find the solution? @ubaidengr


feat: misc niceties & improvements

This PR adds a better CI workflow, eslinit code formatter/linter, and added the queries from the nvim-treesitter PR
Thanks,
-Amaan

Thank you for your interest, but this is unnecessary.

I'm not interested in enforcing a codestyle via eslint.
I'd rather not have to maintain the queries in two places.
Using a script to download and parse the examples is overkill.


feat: Allow skipping setup

If a user is invoking the action multiple times then the trivy binary gets installed multiple times.  Users can avoid this by managing the installation themselves and setting the skip-setup input to true, or by letting the action install in on their first invocation and then setting skip-setup to true on subsequent invocations
This is an alternative solution to aquasecurity/setup-trivy#7 as discussed in that PR to address aquasecurity/setup-trivy#6
By allowing users to control whether the call to the setup-trivy action is made they can control how the trivy binary is installed, and avoid installing it multiple times if they have workflows that call trivy multiple times.
Added an example test at https://github.com/rvesse/setup-trivy-debugging/blob/main/.github/workflows/setup-trivy-indirect-fixed.yml with job output at https://github.com/rvesse/setup-trivy-debugging/actions/runs/11342576655/job/31543286568 where we can see that Trivy is no longer installed multiple times

Can you add examples to README.md using setup-trivy action + skip-setup-trivy input?

Yes, added examples of both calling setup-trivy directly and relying on the implicit call to it

Would love to use this. Could we have a v0.29.0 release for the action?

Hello @antoninbas
Unfortunately, we are busy with other tasks.
But you can use commit number or master branch.


Adds a failing test for ListFile.

This reliably reproduces #732.

Note the test is currently skipped so that CI will pass. The test should be unskipped once the pfs refactor is merged.

meme lgtm


aws_lambda_function fails with 'open lambda.zip: no such file or directory.'

I'm testing the tf-controller with localstack and the following repo:
https://github.com/localstack/localstack-pro-samples/tree/master/terraform-resources
It creates a lambda function which requires uploading a zip file. I've added the zip file to my repository but the tf-controller fails with:
NAME           	READY	MESSAGE                                                                          	PLAN PENDING	SUSPENDED
localstack-test	False	error running Plan: rpc error: code = Unknown desc = exit status 1               	false       	false

               	     	Error: Error in function call

               	     	  on localstack-test.tf line 106, in resource "aws_lambda_function" "authorizer":
               	     	 106:   source_code_hash = filebase64sha256("lambda.zip")

               	     	Call to function "filebase64sha256" failed: open lambda.zip: no such file or
               	     	directory.

Any ideas on how to get this to work?

Hi @magnusboman
Thank you for reporting this. It is a known issue, and the fix for this issue is being addressed by a new feature (refreshBeforeApply) in the next version.
spec:
  refreshBeforeApply: true

The backstory of this bug was that we split plan and apply into two steps. Each step was in each reconciliation loop, and we used a random tmp directory for each loop with cleaning up at the end of each cycle. We implemented it this way because of a security concern.
To address this issue,

we now use a fixed tmp name directory
we will introduce refreshBeforeApply to help users to correct some Terraform behavior required before the apply process.

Please feel free to test it in v0.9.5-rc.3.

Hi @magnusboman
Are you still getting blocked by this bug?

@chanwit i tried to upload a file to s3 like this and i am also getting the no such file or directory errors, even with the refreshBeforeApply option:
resource "aws_s3_object" "index" {
  bucket       = aws_s3_bucket.example.id
  key          = "index.html"
  source       = "${path.module}/content/index.html"
  content_type = "text/html"
}

Any idea what could cause this? Locally it works just fine.
Also tried to place it in the same folder as the terraform file, no success either...

@al-lac - in your use case, the ${path.module} reference will point to the location within the repo where the expression is placed - and it should be a relative path as outlined in the docs - can you give a bit more detail of the file system layout, and where this is stored within the source?
You can also try and use the break-glass functionality to check the directory path on disk within the runner pod, to see whether the path exists on disk during the run, and whether a terrafrom plan is able to find it when run in this way.

Hey @madAndroid, the issue here was that the file was excluded by the default exclusions of the git repository if I remember correctly.
I just added all files like this, which also fixed the issue for .png files i tried to use:
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: GitRepository
metadata:
  name: tf-aws
  namespace: flux-system
spec:
  interval: 30s
  url: https://github.com/al-lac/tf-aws
  ref:
    branch: main
  ignore: |
    # include all
    !/**

Thanks again to @chanwit for pointing this out on the weaveworks slack!

Amazing, glad to hear that this was a relatively simple fix 🎉  - I'll go ahead and close this issue.


Full URLs in /swagger-resources no longer works after 2.7.0 -> 2.8.0 Upgrade

We are using multiple SwaggerResource objects to aggregate swagger-definitions from multiple hosts, which are not the same as the one hosting swagger-ui. This works fine in 2.7.0, the json generated /swagger-resources looks like this (example):
[
    {"name":"xxx-Service",
     "location":"http://localhost:8080/api/swagger",
     "swaggerVersion":"2.0"}
]

With springfox-swagger-ui hosted on localhost:8014 this renders fine.
After upgrading to 2.8.0 the generated /swagger-resources changes to
[
    {"name":"xxx-Service",
     "location":"http://localhost:8080/api/swagger",
     "swaggerVersion":"2.0",
     "url":"http://localhost:8080/api/swagger"}
]

and when swagger-ui attempts to render the documentation, the location gets prefixed with an additional base URL, resulting in the following error message in swagger-ui:
Failed to load API definition.

http://localhost:8014http://localhost:8080/api/swagger is not a valid URL.

As far as I can see the issue happens in https://github.com/springfox/springfox/blob/36c53cf6d4dec0b720be6fc5dce2058a45d1725c/springfox-swagger-ui/src/web/js/springfox.js#L14 where the baseUrl should maybe only be prefixed in case the resource URL is a relative path. I can attempt a fix if you agree that should be changed.

Thanks for reporting @gloeglm

Did this break again in 3.0.0?
https://github.com/springfox/springfox/blob/3.0.0/springfox-swagger-ui/src/web/js/springfox.js#L57

I'm seeing this bug at 3.0.0. Is this now intended functionality?

@TJReinert That is a regression! thank you for catching that!

Not a problem, thanks for being so speedy!


Don't build an amd64 binary in the arm64 image

Not entirely sure what's going on, but /function is definitely compiled for amd64 inside an image that is otherwise arm64.

Seems to work - I see an aarch64 binary when I download the packages artifact from the build. I'm guessing it was the TARGETARCH/TARGETOS placement that was the issue. It's unclear whether ARGs inherit from a base.


Build status should show up as ImagePullBackoff when a container has an ImagePullBackoff error

Details
When one of the containers (Detect, Build, etc) is erroring due to ImagePullBackoff, the Build will continue running for a significant amount of time and the Build status will return as Unknown.
This can show up for many reasons but one use case is Builds not having access to ClusterBuilders (previously CustomClusterBuilders).
To improve the experience, we should radiate this error to the user via the status.
Acceptance Criteria
When my Build is having ImagePullBackoff errors
Then I see ImagePullBackoffError in the Build status

I am going to close this as it was resolved with: https://github.com/pivotal/kpack/pull/461


feat(dashmate): platform status should show latest platform block seen by other nodes

Expected Behavior

It would be nice if dashmate status platform would indicate if the current block matches (or is near) the highest block seen on the network.
Current Behavior

A node on testnet got stuck on 5027, but the rest of the chain progressed. We should add a field to indicate that other nodes are e.g. on 6040, and give an indication that this node might be stuck by changing the colour red.
Possible Solution

Inspect TD voting traffic and if other block numbers being voted on are at a significantly greater height than our node.

Alternatives Considered

Additional Context

@pshenmic what do you think about it?


The init template creates a gitignore file instead of .gitignore file

What version of Turborepo are you using?
1,4.0
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Mac
Describe the Bug
Described in the issue title and next sections.
Expected Behavior
It should create a .gitignore
To Reproduce
Run yarn dlx create-turbo@latest it creates a new repository with a gitignore file instead of .gitignore.

Hey @HosseinAgha, thanks for the report. I just followed your repro steps (and double checked a few other versions / package managers) and was unable to reproduce this. We do have an explicit step to rename the gitignore - so maybe your install hit an error before it reached this step?
https://github.com/vercel/turborepo/blob/main/packages/create-turbo/src/index.ts#L163-L167

Okay, I tried again and it does not happen anymore. As you suggested maybe it is due to a crash.


[Feature Request]

Ist of all  love ur work this helps.non tech savvy ppl  get into xenia.
Now you think it might be possible to add a per gane config?

it already does.

How to do it? I dont see it in added games
On Fri, Oct 18, 2024, 4:50 PM AleNaz @.***> wrote:

it already does.
—
Reply to this email directly, view it on GitHub
https://github.com/xenia-manager/xenia-manager/issues/174#issuecomment-2422657162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC2V4QPA6BCNJ43NWTQDF3TZ4EN4BAVCNFSM6AAAAABQF4JUG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRSGY2TOMJWGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Already implemented. Check Xenia Settings


schemas: add remote-manifest-v0

This introduces a new schema to describe a remote via JSON manifest,
adding support for remote sources for addons.
This will be consumed in the future to automatically populate
the local store from a remote source.

Assuming https://github.com/coreos/torcx/pull/105 is at its final round, this is the next one queued to get in.
@squeed @euank rebased on latest profile-v1, PTAL.

This looks reasonable to me, though I'm not much a fan of the templating code.
I think it may end up being easier to review this in conjunction with the 'fetch' logic for the well-known manifest at base url, especially if the majority template code were moved into its own package and handled separately.

@squeed un-hardcoded the os-release path logic and added a test to exercise all template variables.
@euank vendored gotmpl and got rid of the previous poor substitution logic.
Rebases, PTAL.

@euank ping, I'm leaving this open for a chance in case you want to have a final pass on this. Let me know if otherwise.

Other than the question above, this looks good to me, but I would like to resolve that question before merging.

@euank I've clarified the docs in that regard.


the format of corpus

hello!
I see you say that the input needs to be in BioC or PubTator format, but the corpus you give is not in such format.
I know the Corpus is standard annotation.
Could you please provide the datasets with correct input format of GSC+ and JAX, such as Pubtator format?
Thank you very much!

I have uploaded the PubTator_input_format.zip file. It includes GSC and JAX input files in the PubTator format. You could download it.


Feature Request: Emailing webhook

Thanks for this extension and all the other A1111 work. Possibly not widely useful, but it occurred to me that in addition to discord, an option to email a tunnel link, e.g. cloudflare in my case, to one or more recipients could be useful. If someone is sharing access with a very limited distribution, e.g. just one person, email might be preferable.

Sending an email is more complex than a webhook request, and requires authentication. I'll look into it.


tsdb: Unit test query overlapping in order and ooo head

The test passes before https://github.com/prometheus/prometheus/pull/14354 , so this is a regression test for that.

Superseded by #14693


pagination_decorator not passing kwargs to function

I might be interpreting this incorrectly or maybe I missing something:
pagination_decorator (moto/utilities/paginator.py) pops the kwargs (used for the pagination model) for the function that it is decorating before invoking the function.  This means that the values for those named arguments cannot be validated within the function because those arguments will no longer have a value.
The named arguments could be validated in responses.py before the decorator and function are invoked.  But if the other functions are processing parameters in models.py, then it's inconsistent.

That is correct @kbalk. The reasoning was that these kwargs can be validated within the paginator, and the model doesn't have to worry about them at all. I'm open to changing it if causes problems for you though.

I just moved the check to the response logic, so it's not causing me problems, it's just not consistent with the other checks in the code I wrote.
I can understand if the paginator did the limit check, but at the moment it doesn't.  I think there are now three suggestions for paginator:

check for a limit that exceeds the allowable value for limit,
pass an exception function instead of using "fail_on_invalid_token" true/false,
rename the "page_ending_range_keys" config value.

None are important or critical, just a "nice to do sometime, if ever" sort of thing.    ;-)

This is the second time I've gone down a rabbit hole on this:   param_values_to_check=kwargs.  If you have a kwargs that is a list, you get a error:  *** TypeError: unhashable type: 'list', which makes no sense at all and when you finally step through the code, and if you read the message:
 # We pop the pagination arguments, so the remaining kwargs (if any)
 # can be used to compute the optional parameters checksum.

It finally makes sense.  So annoying.  Because then you have to avoid using kwargs for those arguments simply to get around this issue.

Sounds like improving this decorator is becoming a "should have" instead of "nice to do sometime, if ever", if it's giving you so much grieve. Appreciate the debugging on this @kbalk.


Tye's dashboard should support structured logging

What should we add or change to make your life better?
Add support to the dashboard for extracting the good parts from structured log messages in JSON formats.
Why is this important to you?
.NET 5 is adding support for JSON formatting for logs in the box. It's annoying to have to switch back and forth between JSON depending on the environment, and using something like ELK isn't incredibly fast locally.

Maybe a tab on the logs page that tries to parse the logs as JSON

Or a copy button that lets you choose to copy as text or copy as json.
However it would be best to also let us copy only a small part of the logs.

Im also facing this problem..


Setting ENVIRONMENT configuration via Environment Variable

Setting ENVIRONMENT configuration via Environment Variable CI_ENV (in .htacess with SetEnv)
In your .htaccess:
SetEnv CI_ENV development
In your index.php
$env = getenv("CI_ENV");
$env_default = "development";
if ($env === false) { $env = $env_default; }
define('ENVIRONMENT', $env);

This is a good tip but it doesn't belong in the core because not everyone can set environment variables. And not every one uses Apache.

if you don't use environment variable, don't worry,  you can change $env_default = "development"; like now.
Every system has environment usually has variable.
If you use php-cli you can set environment variable in your shell.
In lighttpd you have directive like setenv.add-environment
in nginx you can use the directive like env ... and so on.
i'm really interested in your feedback.

Roberto, when multiple environment support was integrated with CodeIgniter, one of the wishes was that the way the environment is determined, is left to the individual developer. As @ericbarnes, every environment is different and it's not up to us to force people to use a certain method for determining the environment.

ok but this code:
$env = getenv("CI_ENV");
$env_default = "development";
if ($env === false) { $env = $env_default; }
define('ENVIRONMENT', $env);
permits you to manage your environment in the codeigniter classic way.
If you want to use "production": you can change $env_default to "production".
If you want to use "development": you can change $env_default to "development".
This is the same like today.
BUT the value added of this solution is that enable some developer to manage the environment with environment variable.
So, the developer can choose the way to define the environment: or changing the index.php (like today) or managing env var.
But if you don't agree with me... it's ok ;) It was just my personal suggestion. :)

That code is crazy complicated, if we do this we'll use this one:
define('ENVIRONMENT', isset($_SERVER['CI_ENV']) ? $_SERVER['CI_ENV'] : 'development');

I am tempted to do this with 3.0 but will need to run it past the team.

Hi All,
I am new to PHP I am facing an issue. I have a constant file where I have kept my constant file.


autocomplete, errors highlights, and code formatting don't work on Linux

I've just migrated from windows on Linux ubuntu 16.04 and faced the issue.
Ctrl+F+T has no result ( as command typescript_format_document )
Sublime doesn't show errors and autocomplete.
But Typescript package is installed and code highlights works well.

I just did. There is no solution for the issue.
I want to mark that everything work just fine on Windows, but the issue comes when I open ts file on linux.
I tested that on several computer - same result.

Problem fixed.
I didn't have typescript globally installed.


Is APPLE_AUTOMATION_BEARER_TOKEN and PODCAST_ID both needed?

Do we still need both of those env vars, as the popdcast name is mapped from the token in https://github.com/openpodcast/apple-automation/blob/main/.env.sample ?
APPLE_AUTOMATION_BEARER_TOKEN=<APPLE_AUTOMATION_BEARER_TOKEN>
PODCAST_ID=<PODCAST_ID>

https://github.com/openpodcast/open/blob/1fadf0a55602799537e1737751606090448c2a48/apple/.env.sample#L3

👍
Thanks for fixing that in https://github.com/openpodcast/pipelines/pull/24.


Add metrics reporter test for ut#1569

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1585 (11b8e04) into master (4998973) will decrease coverage by 0.35%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1585      +/-   ##
============================================
- Coverage     63.62%   63.27%   -0.36%
- Complexity     2231     2233       +2
============================================
  Files           450      450
  Lines          9417     9428      +11
  Branches        960      961       +1
============================================
- Hits           5992     5966      -26
- Misses         2949     2985      +36
- Partials        476      477       +1

Impacted Files
Coverage Δ

...enyu/client/tars/TarsServiceBeanPostProcessor.java
25.33% <0.00%> (-65.34%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <0.00%> (-8.74%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
56.84% <0.00%> (-7.37%)
:arrow_down:

...in/alibaba/dubbo/cache/ApplicationConfigCache.java
75.86% <0.00%> (-4.60%)
:arrow_down:

.../shenyu/admin/service/impl/AppAuthServiceImpl.java
89.79% <0.00%> (-4.26%)
:arrow_down:

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
:arrow_down:

...pache/shenyu/metrics/reporter/MetricsReporter.java
93.33% <0.00%> (+93.33%)
:arrow_up:

Continue to review full report at Codecov.

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


example commit

thanks for such a treasure of examples. Please change everything to avi_credentials so we can transition everyone to start using that.

@grastogi23 we will need to wait a couple weeks as some of the changes you requested effects non-avi specific tasks and @sparampalli needs to make changes to avi saas code
Can you add @sparampalli to the DevOps repo?

made changes that should fix any of the issues @grastogi23


Api change

Merging the new API into master. This is the basis for the 2.0 release.
API is pretty much stable, although we may need a few small changes here and there.

Codecov Report

Merging #476 into master will decrease coverage by 35.5%.
The diff coverage is 25.73%.

@@              Coverage Diff              @@
##             master     #476       +/-   ##
=============================================
- Coverage     85.46%   49.96%   -35.51%
+ Complexity     2282      926     -1356
=============================================
  Files           159      105       -54
  Lines          6841     4445     -2396
  Branches       1016      644      -372
=============================================
- Hits           5847     2221     -3626
- Misses          670     2106     +1436
+ Partials        324      118      -206

Flag
Coverage Δ
Complexity Δ

#fixedclientenvironment
3.39% <3.79%> (?)
61 <22> (?)

#integration
17.23% <16.9%> (?)
248 <84> (?)

#livelocal
3.41% <3.72%> (?)
63 <22> (?)

#unit
41.25% <15.22%> (?)
820 <90> (?)

Impacted Files
Coverage Δ
Complexity Δ

...enter/xenon/adaptors/filesystems/ftp/FtpQuery.java
0% <ø> (ø)
0 <0> (?)

...enter/xenon/credentials/CertificateCredential.java
100% <ø> (ø)
3 <0> (?)

...xenon/adaptors/filesystems/EndOfFileException.java
100% <ø> (ø)
2 <0> (?)

...s/schedulers/ssh/SshInteractiveProcessFactory.java
100% <ø> (ø)
7 <0> (?)

...ciencecenter/xenon/InvalidCredentialException.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

...ter/xenon/adaptors/schedulers/StreamForwarder.java
0% <ø> (ø)
0 <0> (?)

.../adaptors/schedulers/SchedulerClosedException.java
50% <ø> (ø)
1 <0> (?)

...ecenter/xenon/adaptors/shared/local/LocalUtil.java
6.45% <ø> (ø)
6 <0> (?)

.../adaptors/filesystems/ConnectionLostException.java
100% <ø> (ø)
2 <0> (?)

...ncecenter/xenon/UnsupportedOperationException.java
100% <ø> (ø)
2 <0> (?)

... and 166 more

Continue to review full report at Codecov.

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


[Feature]there needs chest Upgrade Tool

Describe the solution you'd like
there needs chest Upgrade Tool
Chests can be upgraded with tools, Normal chests can be upgraded to copper chests by using a one-time copper upgrade item，Iron chests can be upgraded to golden chests by using a one-time golden upgrade item. And so on
Additional context
In the early stage of survival, there were not so many copper, iron, gold, and diamonds, etc., to build chests, In the later stage, when there are many items that can be used to build chests and use them, it is very troublesome to move the items from the old chests before new chest can be used

Thank you for your suggestion. However, I prefer simple mods and do not wish to create too many things. Therefore, I have no plans to implement this. It is the same as #19.


Division by zero error when passing a custom profile via the transformerConfig (+suggested fix)

I'm currently getting a 'Division by zero' error when passing in a custom profile via the transformerConfig.
{% set transformedImage = craft.imagerx.transformImage(image, { width: width}, {}, {transformerConfig: { profile: imagerProfile }}) %}

I think $profile should be passed as the fourth parameter here when you're creating an instance of ImagekitTransformedImageModel.
https://github.com/spacecatninja/craft-imager-x-imagekit-transformer/blob/03bdbb7a1eae6e2496d768e0085c77ff0935af25/src/transformers/Imagekit.php#L77
This fixes it for me:
return new ImagekitTransformedImageModel($url, $image, $params, $profile);

Should be fixed now. Curious where the error was thrown though, I wasn't able to reproduce when quickly testing it.

@aelvan thanks! That's fixed it.
I realised it only happened when the custom profile being used is a web proxy. Sorry, I should have noticed that and mentioned it.
{% set transformedImage = craft.imagerx.transformImage(
    "https://s1.geograph.org.uk/photos/16/80/168021_1f28e99b.jpg",
    { width: '500' },
    {},
    { transformerConfig: { profile: 'proxy' } }
) %}

Config...
....
'proxy' => [
    'urlEndpoint' => 'https://ik.imagekit.io/afsdf',
    'isWebProxy' => true
]

Stack trace if it helps...
https://pastebin.com/NsjFXeEm


The welcome README.md is not filled with the right information (false informations under project image)

Bugs : The repository is not well linked with the readme (false informations under project image).

fixed with #5


[Persist] time:Utc type values mismatch on retrieval

Description:
When a time:Utc type is persisted and retrieved, the value obtained is different.
Steps to reproduce:
type TestEntity record {|
    readonly int id;
    time:Utc utcType;
|};

public function main() returns error? {
    time:Utc insertUtc = check time:utcFromString("2007-12-03T10:15:30.00Z");
    test_entities:TestEntity insert = {
        id: 5,
        utcType: insertUtc
    };

    test_entities:TestEntitiesClient teClient = check new();
    _ = check teClient->/testentity.post([insert]);

    test_entities:TestEntity retrieved = check teClient->/testentity/[5].get();
    test:assertEquals(insertUtc, retrieved);
}

Output
error: Assertion Failed!

expected: <TestEntity> '{"id":5,"utcType":[1196657130,0]}'
actual  : <[int,decimal] & readonly> '[1196676930,0]'

The difference is 19800, which corresponds to 5.5 hours, indicating this may be an issue with time zones

The same value is stored in the database, but the problem is in converting SQL to the ballerina type when executing the read command.  In the SQL, the timestamp[1] is converted to milliseconds by using getTime()[2].
The getTime() value of the above sample is<PHONE_NUMBER> and the equivalent time is 2007-12-03T04:45:30Z. This time is equals to  Given time - 5.30.
[1]
[2] https://github.com/ballerina-platform/module-ballerina-sql/blob/master/native/src/main/java/io/ballerina/stdlib/sql/parameterprocessor/DefaultResultParameterProcessor.java#L550
@niveathika @daneshk Is it expected behavior?

This is the correct behaviour from the sql module perspective. AS sql module only stores and retrieves data and does not manipulate this.
IMO this is not suitable for persist module as this is the data layer of an application. Shall we check how this is handled in other ORM libraries?

@kalaiyarasiganeshalingam According to your comment,
There is no issue with the value when storing it in the database. the database stores the same value we passed to the persist module and also the internal SQL module.
The problem is when retrieving the data from the database. database returns the correct GMT value without local offset, but the value returned from the SQL connector has local offset. it converts GMT time to the local time when we are converting the time value to milliseconds.
is this correct?

Yes, there is no issue with the value when storing it in the database and retrieving the data from the database.
The problem is in converting the retrieved data.
The given time 2007-12-03T10:15:30.00Z in Millis =<PHONE_NUMBER>.
But, in the SQL, timestamp.getTime() returns time in Millis = 119665713(GMT -5.30).
If it returns GMT time to local time, it should return the value by adding 5.30 hours (GMT +5.30) but it subtracts that value(GMT -5.30).
Please correct me if I am wrong, it considers this value a local time and converts it to GMT time. So, it subtracts that value by 5.30. But users will want to get back the same value they saved. But neither the GMT time nor the corresponding local time is returned for the given time.


FreeBSD port

Encouraged by a comment in ByteSwap.h, I am trying to understand what it would take to build ChakraCore on FreeBSD.
I understand that this might not be a priority, but I will appreciate any pointers or suggestions.

Hi @ppenzin - my advice would be to just try it out and see what you run into- we currently depend on clang 4, libc and ICU60. Additionally, a lot of platform specific code is abstracted away under /pal, which was forked from the CoreCLR which does support FreeBSD.
I don't know the details of differences between FreeBSD and Linux but if those components are available on FreeBSD, the port shouldn't be too bad.
This does seem like something @obastemur would have looked at in the past- maybe he has pointers?

@digitalinfinity thanks for the reply! Clang is used to build FreeBSD (11.1 comes with clang 4), and something ICU related is available, I would need to check. Unless there is a dependency on a specific LIinux feature or on a library that is hard to build, it should work.
So far I am sorting through undefined errors due to differences in build process. I did enable byteswap the way @obastemur suggested in the comment,

For what its worth, ICU should work on FreeBSD without too much fanfare. I would be happy to know what issues you run into with it :)

So, I'm trying to build ChakraCore on FreeBSD. Here is the command I used:
./build.sh --arch=amd64 --system-icu --ninja --lto --target=freebsd
I built ICU 63.1, Unicode 11.0, before this. here's the output I get whenever I run this command:
Warning: Installation script couldn't detect host OS..

Build path: /usr/home/ethin/chakracore/out/Release
-- /usr/home/ethin/chakracore/bin/ch/DbgController.js.h is created

Compile Target : amd64
Generating Release makefiles

-- The C compiler identification is Clang 6.0.0
-- The CXX compiler identification is Clang 6.0.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:256 (message):
  This OS is not supported

-- Configuring incomplete, errors occurred!
See also "/usr/home/ethin/chakracore/out/Release/CMakeFiles/CMakeOutput.log".
ninja: error: loading 'build.ninja': No such file or directory
See error details above. Exit code was 1

What's odd about this error is that it seems like the makefile is assuming that my OS is OSX, as evidenced by the code that causes this error (lines 241-257 of CMakeLists.txt):
    if(NOT CC_XCODE_PROJECT)
      set(OSX_DEPLOYMENT_TARGET "$ENV{MACOSX_DEPLOYMENT_TARGET} CC")
      if (${OSX_DEPLOYMENT_TARGET} STREQUAL " CC")
        set(OSX_DEPLOYMENT_TARGET "10.9")
        add_compile_options(-mmacosx-version-min=10.9)
        set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} \
          -mmacosx-version-min=10.9 -std=gnu99")
        set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
          -mmacosx-version-min=10.9 -std=gnu++11")
      else()
        set(OSX_DEPLOYMENT_TARGET "$ENV{MACOSX_DEPLOYMENT_TARGET}")
        message(WARNING "-- !! macOS Deployment Target was set to $ENV{MACOSX_DEPLOYMENT_TARGET}. Using it as is.")
      endif()
    endif()
else()
    message(FATAL_ERROR "This OS is not supported")
endif()

I'm using clang/clang++, as the build.sh script requires. So I'm not sure how else to build this. But I'd like to try and integrate it into one of my projects.

Ah. I was hoping something could be done. I can wait, I guess. :)
On 11/28/18, Oguz Bastemur<EMAIL_ADDRESS>wrote:

IIRC few changes are required to make that. Answer your question; not doable
as is.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Microsoft/ChakraCore/issues/5199#issuecomment-442610392

--
Signed,
Ethin D. Probst

I've tried to get it to build and this is how for it got: https://github.com/ppenzin/ChakraCore/tree/freebsd
I am hoping to return to this one day, but haven't found time :)
It should be theoretically doable, as Chakra does not seem to depend on anything unavailable on FreeBSD, but you would have to make minor edits. There are usual issues with porting something that runs on OSX and LInux to FreeBSD -- include directories, link libraries paths and so on.


Fix two typos in engines.html

Fix two typos: "vvm" -> "vm", "stablesort" -> "tablesort".

Shipyard v3 has been released and is a major refactor. Could you please do a fresh checkout and rebase?  Thanks!

Closing as this has gone inactive.  Please open a new PR if you want to add this.  Thanks!


HELP ME PLEASE

Describe your problem here.
IM WORKING ON MY FRIENDS MOD AND EVERYTIME I INPUT A NOTE CLICK OR KEYBOARD PRESS IT CRASHES WHAT DO I DO PLEASE HELP
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
I editied a lot of things today Playstate, Achiements, Credits, AchiementsMenuState and some image assets

We can't see your code, how do you expect us to help you?

send the whole playstate code?

send the whole playstate code?

It'd be nicer if you could create a diff between all modified code (i.e. publishing your code to GitHub).

Sounds like a duplicate of #343
Plus no replies since 2 days so i will suppose OP fixed it.


Unable to load playground | Manually having to add endpoint to address bar in Console's Playground

[ ] GraphQL Playground

What OS and OS version are you experiencing the issue(s) on?
Windows 10 64bits
What is the expected behavior?
Should add endpoint in the address bar next to the history button to run any query/mutation
What is the actual behavior?
Nothing is added into that field, and it looks like the whole functionality is derived from getting the value from there, so all the schema is disabled.
What steps may we take to reproduce the behavior?
Upgrade npm package to latest version.

Fixed in the latest version. Please let us know if you still have that issue, then we reopen it!


Self-managed on-premises only cleanup

Remove docs that self-managed on-prem replaces.

Deploy preview for calico ready!
Built with commit 0dc9cfd495c9016d8b13a3122ccf97c93c9359be
https://deploy-preview-3213--calico.netlify.com


License for Code

Right now the repository is licensed under CC0, which is appropriate for public discussions, but arguably a bit less appropriate for code.
If this is to be a repository not just for discussions about common tooling for trackers, but actually for that tooling, we might want to pick a different base license, e.g. MIT or Apache.  (Or we could put that license file in a code directory, and somehow make it clear that the code isn't CC0.)

Agreed, for at least three reasons

According to the CC0 FAQ and
https://creativecommons.org/weblog/entry/27081:

One important reason why Creative Commons licenses should not be used to release software is that they aren’t compatible with existing free software licenses, most importantly the GPL from the Free Software Foundation, which is used by over half of free software projects. A commons fractured by legal incompatibilities is a weak commons

According to the [creative commons FAQ]((https://wiki.creativecommons.org/wiki/Frequently_Asked_Questions#Can_I_use_a_Creative_Commons_license_for_software.3F):

Unlike software-specific licenses, CC licenses do not contain specific terms about the distribution of source code, which is often important to ensuring the free reuse and modifiability of software. Many software licenses also address patent rights, which are important to software but may not be applicable to other copyrightable works. Additionally, our licenses are currently not compatible with the major software licenses, so it would be difficult to integrate CC-licensed work with other free software. Existing software licenses were designed specifically for use with software and offer a similar set of rights to the Creative Commons licenses.

The rest of the OpenWorm repositories use the MIT license.

So, since @aexbrown and @Ichoran are ok with MIT, I've taken the liberty of replacing the CC0 license with the MIT one.

@MichaelCurrie - All right, I'll rebase my code reorganization on your patch, I guess?  (I'd already made the change in that PR, except it was MIT for code and CC0 for everything else.)

Is there some advantage to having CC0 for non-code stuff?  If so, perhaps we should go your route.
Otherwise, if it's okay with you perhaps we could keep it simple and stick with MIT - then OpenWorm can continue to say we are MIT-licensed across the board.

The only practical advantage to CC0 that I can think of is that people who are good enough at bioinformatics to grab data but not good enough to keep track of which license is which can scrape the text without any worry about violating anything.  I'm not sure this is a very compelling "advantage".  MIT is fine with me.


Update prometheus-cpp and Metric API unit tests

[x] Update Prometheus API usage for new prometheus-cpp version for metter support in managing duplicate metrics/metric families. Before this bump:

Duplicately named metric families of different types (counter, gauge, etc.) could be added to the registry which is against the prometheus spec
Duplicately named metric families (even of same type) would keep being added as separate objects to registry. Now duplicates will return a reference to the same family.

[x] Update unit tests to more thoroughly test duplicates and edge cases
[x] Think about out-of-order deletion: i.e. calling MetricFamilyDelete() before MetricDelete() where Metric->family_->Remove() reference is called in destructor even though family_ should be invalid memory now.
[x] Check if existing metric families from core (nv_request..., nv_gpu_util..., etc.) can be inadvertently removed by creating a duplicate MF with Metrics API and then calling registry->Remove() on it in destructor

it can, delaying registry removal until explicitly asked for, see DLIS-4072

New unit tests:
[==========] Running 9 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 9 tests from MetricsApiTest
[ RUN      ] MetricsApiTest.TestCounterEndToEnd
[       OK ] MetricsApiTest.TestCounterEndToEnd (241 ms)
[ RUN      ] MetricsApiTest.TestGaugeEndToEnd
[       OK ] MetricsApiTest.TestGaugeEndToEnd (1 ms)
[ RUN      ] MetricsApiTest.TestDupeMetricFamilyDiffKind
[       OK ] MetricsApiTest.TestDupeMetricFamilyDiffKind (0 ms)
[ RUN      ] MetricsApiTest.TestDupeMetricFamilyDiffDescription
[       OK ] MetricsApiTest.TestDupeMetricFamilyDiffDescription (1 ms)
[ RUN      ] MetricsApiTest.TestDupeMetricFamily
[       OK ] MetricsApiTest.TestDupeMetricFamily (1 ms)
[ RUN      ] MetricsApiTest.TestDupeMetricLabels
metric1 value: 7.5 == metric2 value: 7.5
[       OK ] MetricsApiTest.TestDupeMetricLabels (0 ms)
[ RUN      ] MetricsApiTest.TestDupeMetricEmptyLabels
metric1 value: 7.5 == metric2 value: 7.5
[       OK ] MetricsApiTest.TestDupeMetricEmptyLabels (1 ms)
[ RUN      ] MetricsApiTest.TestOutOfOrderDelete
[       OK ] MetricsApiTest.TestOutOfOrderDelete (0 ms)
[ RUN      ] MetricsApiTest.TestCoreMetricAccess
[       OK ] MetricsApiTest.TestCoreMetricAccess (0 ms)
[----------] 9 tests from MetricsApiTest (250 ms total)

[----------] Global test environment tear-down
[==========] 9 tests from 1 test suite ran. (250 ms total)
[  PASSED  ] 9 tests.


Lecture 2 slide 94 very minor typo

incident of a double spaced nature between "i" and "to"

Beautiful pedantry. I love it. Let's say 1 point


[AVM Module Issue]: service-bus\namespace\topic\subscriptions support

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/res/service-bus/namespace
(Optional) Module Name if not listed above
No response
(Optional) Module Version
No response
Description
Currently it's possible to create service bus namespace and topics using the AVM module.
Creating topic subscriptions, however, is not supported.
Topic with no subscriptions make little sense.
Using AVM module and manually creating subscriptions for a topic is challenging due to one-to-many namespace-topic-subscription fanout (a single namespace may have one or more topics, a single topic may have many subscriptions).
Request is to add support for Microsoft.ServiceBus/namespaces/topics/subscriptions resource creation as a child resource to Microsoft.ServiceBus/namespaces/topics, if topic property contains subscription sub-property
(Optional) Correlation Id
No response

Hi @andlommy.
Thanks for submitting this issue and I can certainly align this in #722 for future release. Can I also ask if you have been using this module in is previous form residing in CARML (https://aka.ms/carml) or have you picked up using this module natively to AVM?

@ChrisSidebotham, neither CARML nor AVM have subscription resource support. We're using the AVM module

@ChrisSidebotham, neither CARML nor AVM have subscription resource support. We're using the AVM module

Thanks for response. Just wanted to understand where your usage was - I will add this into the VNext updates for Service Bus module.


Merging PDFs

Have you considered having the tool merge PDFs? If so, were there difficulties that de-prioritized that functionality? Would you consider a PR that adds that functionality?

Hey @jrhorn424, there was no real consideration! We would love to have that capability, and would happily accept a PR to add it!
Just FYI the library we use to do a lot of the conversions is Photosorcery, so improvements probably have to be made there first 🙂


Update values.py

Added Fingerprint for Highlander LE PLUS 2018.

Adding as a new model is not a good idea, you'd better add it as Highlander(ICE)'s trim. Take a look "CAR.PRIUS" as reference.


EPMRPP-64837: Remove "AZURE DEVOPS" tab from project settings

https://jiraeu.epam.com/browse/EPMRPP-64837

It seems that these changes are already merged in https://github.com/reportportal/plugin-bts-azure/pull/14


Support more parameters for AD and KMEANS command, and update related documentation

Description

Support more and orderless parameters for AD command.
Support more and orderless parameters for KMENAS command.
Update documentation for AD and KMEANS command to include new parameters.

Issues Resolved
(https://github.com/opensearch-project/sql/issues/462)
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[x] New functionality has javadoc added
[x] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

A question about resource release: is there any problem that MachineLearningNodeClient is created in getMLPredictionResult() without close manually?

A question about resource release: is there any problem that MachineLearningNodeClient is created in getMLPredictionResult() without close manually?

@dai-chen MachineLearningNodeClient is a singleton, it will only be created as a single instance through the lifetime of this application, so I don't think we need to care much about disposing it?

A question about resource release: is there any problem that MachineLearningNodeClient is created in getMLPredictionResult() without close manually?

@dai-chen MachineLearningNodeClient is a singleton, it will only be created as a single instance through the lifetime of this application, so I don't think we need to care much about disposing it?

Okay. Asking just in case we need to close it manually. Thanks!


[RIP-46] [ISSUE #5994] add pop and timer metrics

close #5994

Codecov Report

Merging #5995 (1f88689) into develop (a1d1cf8) will decrease coverage by 0.11%.
The diff coverage is 27.50%.

@@              Coverage Diff              @@
##             develop    #5995      +/-   ##
=============================================
- Coverage      43.44%   43.34%   -0.11%
- Complexity      8824     8837      +13
=============================================
  Files           1090     1093       +3
  Lines          76617    76832     +215
  Branches       10006    10012       +6
=============================================
+ Hits           33289    33302      +13
- Misses         39166    39365     +199
- Partials        4162     4165       +3

Impacted Files
Coverage Δ

.../rocketmq/broker/metrics/BrokerMetricsManager.java
11.58% <0.00%> (-0.16%)
:arrow_down:

...he/rocketmq/broker/metrics/PopMetricsConstant.java
0.00% <0.00%> (ø)

...tmq/store/metrics/DefaultStoreMetricsConstant.java
0.00% <ø> (ø)

...ieredstore/metrics/TieredStoreMetricsConstant.java
0.00% <ø> (ø)

...tieredstore/metrics/TieredStoreMetricsManager.java
57.86% <0.00%> (ø)

...cketmq/broker/processor/PopBufferMergeService.java
33.33% <16.66%> (-0.08%)
:arrow_down:

...apache/rocketmq/store/timer/TimerMessageStore.java
54.15% <21.42%> (-0.14%)
:arrow_down:

...etmq/store/metrics/DefaultStoreMetricsManager.java
18.18% <21.53%> (+18.18%)
:arrow_up:

...he/rocketmq/broker/processor/PopReviveService.java
38.71% <27.77%> (-2.04%)
:arrow_down:

...che/rocketmq/broker/metrics/PopMetricsManager.java
28.70% <28.70%> (ø)

... and 24 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


PS still running after tfjob is complete

Copying kubeflow/kubeflow#1334
Hi,
I have an issue that the PS pod keeps running after the tfjob is complete, even after several days.
kubectl get pods returns
'''
trainer-180804-004108-master-0 0/1 Completed 0 4d
trainer-180804-004108-ps-0 1/1 Running 0 4d
trainer-180804-004108-worker-0 0/1 Completed 0 4d
'''
And, kubectl get tfjob returns
'''
tfReplicaStatuses:
MASTER:
succeeded: 1
PS:
active: 1
Worker:
succeeded: 1
'''

Looks like we aren't verifying that pods are deleted
https://github.com/kubeflow/tf-operator/blob/d2509aae732ae1eb23dd8754bcc3b74f19df51cd/py/test_runner.py#L555

@gaoning777
What version of tfjob are you using? The cleanPodPolicy might not work in earlier versions of tfjob
I used cleanPodPolicy in my tfjob spec and it cleaned up all pods as expected after the job completed. Here is my complete tfjob spec
apiVersion: "kubeflow.org/v1alpha2"
kind: "TFJob"
metadata:
  name: "linear09"
spec:
  cleanPodPolicy: All
  tfReplicaSpecs:
    PS:
      replicas: 1
      restartPolicy: Never
      template:
        spec:
          containers:
            - name: tensorflow
              image: gcr.io/agwlkubeflow/linear-regression-estimator:latest
              command: ["python", "/train.py", "--model_dir=/mnt/kubeflow-gcfs/linear09"]
              volumeMounts:
              - mountPath: /mnt/kubeflow-gcfs
                name: kubeflow-gcfs
          volumes:
          - name: kubeflow-gcfs
            persistentVolumeClaim:
              claimName: kubeflow-gcfs
    Worker:
      replicas: 1
      restartPolicy: Never
      template:
        spec:
          containers:
            - name: tensorflow
              image: gcr.io/agwlkubeflow/linear-regression-estimator:latest
              command: ["python", "/train.py", "--model_dir=/mnt/kubeflow-gcfs/linear09"]
              volumeMounts:
              - mountPath: /mnt/kubeflow-gcfs
                name: kubeflow-gcfs
          volumes:
          - name: kubeflow-gcfs
            persistentVolumeClaim:
              claimName: kubeflow-gcfs
    Chief:
      replicas: 1
      restartPolicy: Never
      template:
        spec:
          containers:
            - name: tensorflow
              image: gcr.io/agwlkubeflow/linear-regression-estimator:latest
              command: ["python", "/train.py", "--model_dir=/mnt/kubeflow-gcfs/linear09"]
              volumeMounts:
              - mountPath: /mnt/kubeflow-gcfs
                name: kubeflow-gcfs
          volumes:
          - name: kubeflow-gcfs
            persistentVolumeClaim:
              claimName: kubeflow-gcfs

The default is to leave pods running.
https://github.com/kubeflow/tf-operator/blob/1fa0779840816b772a1c113c14220a2464d04ac0/pkg/apis/tensorflow/v1alpha2/defaults.go#L91

I was using the default clean policy.
I tried the  cleanPodPolicy: All, but to no avail. the PS is still running after 10 minutes. I'm using kubeflow v1alpha2.

My yaml looks like this:
apiVersion: kubeflow.org/v1alpha2
kind: TFJob
metadata:
generateName: trainer-
spec:
cleanPodPolicy: All
tfReplicaSpecs:
MASTER:
replicas: 1
restartPolicy: OnFailure
template:
spec:
containers:
- command:
- python
- -m
- trainer.task
image: ******
name: tensorflow
PS:
replicas: 1
restartPolicy: OnFailure
template:
spec:
containers:
- command:
- python
- -m
- trainer.task
image: *****
name: tensorflow
Worker:
replicas: 1
restartPolicy: OnFailure
template:
spec:
containers:
- command:
- python
- -m
- trainer.task
image: *****
name: tensorflow

@gaoning777 What are the events for the TFJob? I'd like to know if we tried to delete the pod.
There are instructions here for dumping the events
https://www.kubeflow.org/docs/guides/monitoring/#default-stackdriver
You can ping us internally in the Kubeflow chat room with relevant stackdriver information.

#750 is for E2E test for CleanPodPolicy.

@ankushagarwal The default CleanPodPolicy is Running
https://github.com/kubeflow/tf-operator/blob/1fa0779840816b772a1c113c14220a2464d04ac0/pkg/apis/tensorflow/v1alpha2/defaults.go#L94
That means we will delete pods that are still Running which is the right default.
https://github.com/kubeflow/tf-operator/blob/master/pkg/controller.v2/tfcontroller/tfjob.go#L88

@jlewi @ankushagarwal
I think I found the root cause.
The reason is when the last time we refactored the code (#767 ), we put functions like GetPodsForJob, GetServicesForJob, DeletePod, DeleteService under JobController rather than TFJobController.
We cannot call these function under tc.XXX(), therefore, this issue happened.
See #776
Thanks!

@ChanYiLin I think https://github.com/kubeflow/tf-operator/pull/767 is ok as we used embedded field in TFJobController struct.

Can anyone reproduce the problem with the prods not being deleted?

I've tested it using GCP with KUBEFLOW_VERSION=0.2.2 and tf-operator v1alpha2.
Kubeflow killed all the pods after the job succeeded as expected.
The yaml file I used is as follow
apiVersion: kubeflow.org/v1alpha2
kind: TFJob
metadata:
  name: test
spec:
  cleanPodPolicy: All
  tfReplicaSpecs:
    MASTER:
      replicas: 1
      restartPolicy: OnFailure
      template:
        spec:
          containers:
          - command:
            - python
            - tf_cnn_benchmarks.py
            - --batch_size=8
            - --model=resnet50
            - --data_format=NHWC
            - --device=cpu
            - --variable_update=parameter_server
            - --flush_stdout=true
            - --num_gpus=1
            - --num_batches=10
            - --sync_on_finish=false
            - --cross_replica_sync=false
            - --num_warmup_batches=0
            image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
            name: tensorflow
            workingDir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
    PS:
      replicas: 1
      restartPolicy: OnFailure
      template:
        spec:
          containers:
          - command:
            - python
            - tf_cnn_benchmarks.py
            - --batch_size=8
            - --model=resnet50
            - --data_format=NHWC
            - --device=cpu
            - --variable_update=parameter_server
            - --flush_stdout=true
            - --num_gpus=1
            - --num_batches=10
            - --sync_on_finish=false
            - --cross_replica_sync=false
            - --num_warmup_batches=0
            image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
            name: tensorflow
            workingDir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
    Worker:
      replicas: 1
      restartPolicy: OnFailure
      template:
        spec:
          containers:
          - command:
            - python
            - tf_cnn_benchmarks.py
            - --batch_size=8
            - --model=resnet50
            - --data_format=NHWC
            - --device=cpu
            - --variable_update=parameter_server
            - --flush_stdout=true
            - --num_gpus=1
            - --num_batches=10
            - --sync_on_finish=false
            - --cross_replica_sync=false
            - --num_warmup_batches=0
            image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
            name: tensorflow
            workingDir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks

Where can I find the new version? The most recent v0.2.2 release(https://github.com/kubeflow/kubeflow/releases) was published on July 12nd.

@gaoning777 What is the docker image for tf-operator that you are using?

@jlewi I also put some comments here: https://github.com/tensorflow/tensorflow/issues/20833
but it may well apply to tf-operator.
Strangely enough if I used Tensorflow 1.8.0 the TfJob and marked as Succeeded but with Tensorflow 1.9.0 it remains running indefinitely, however when using 1.8.0 I see this in kubetail logs, although the jobs are marked as Succeeded 🤔
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-1-wgdla] INFO:root:Session from worker 1 closed cleanly
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] INFO:tensorflow:Coordinator stopped with threads still running: QueueRunnerThread-dummy_queue-sync_token_q_EnqueueMany
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] Exception in thread QueueRunnerThread-dummy_queue-sync_token_q_EnqueueMany:
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] Traceback (most recent call last):
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] self.run()
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/lib/python3.5/threading.py", line 862, in run
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] self._target(*self._args, **self._kwargs)
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/training/queue_runner_impl.py", line 268, in _run
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] coord.request_stop(e)
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/training/coordinator.py", line 213, in request_stop
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] six.reraise(*sys.exc_info())
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] raise value
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/training/queue_runner_impl.py", line 252, in _run
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] enqueue_callable()
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1244, in _single_operation_run
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] self._call_tf_sessionrun(None, {}, [], target_list, None)
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1409, in _call_tf_sessionrun
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] run_metadata)
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] tensorflow.python.framework.errors_impl.CancelledError: Step was cancelled by an explicit call to `Session::Close()`.
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy]
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] INFO:root:Finished on task 0 in<PHONE_NUMBER>568817 seconds
[my-tf-dist-8a0d7766-d562-4e19-827f-00c62-worker-vm6i-0-emdpy] INFO:root:Session from worker 0 closed cleanly

This can be consistently reproduced if the tf operator is using image tf_operator:v0.2.0. The latest tf operator image (I was using tf_operator:v20180809-d2509aa) does not have this issue.

@gaoning777
This should be fixed in 0.2.3. If you have a dependency on Kubeflow 0.2.2, you can fix this by doing something like:

export KUBEFLOW_DEPLOY=false
Run deploy.sh
ks param set tf-job-operator tfJobImage gcr.io/kubeflow-images-public/tf_operator:v20180809-d2509aa
export KUBEFLOW_DEPLOY=true
Run deploy.sh again

Thanks Richard for looking into this.
The ideal would be to enable the user to specify the tf-operator version to the deploy script such that there is a clear decoupling of these two projects. As such, user will not depend on the new release of kubeflow to upgrade their tf-operator version on the assumption that we need one-click deployment.

The TFJob operator image on master is already pointing to the latest image. I believe @gaoning777 is depending on the 0.2.2 release.

This release has the fix: https://github.com/kubeflow/kubeflow/releases/tag/v0.2.4-rc.0

Closing this since the issue is fixed. Will send out a separate PR for the e2etest.


Atomic function pointers

Following the discussion in https://github.com/rust-lang/rust/issues/51559 I am opening this to track the lack of atomic function pointers in the std library (and the ecosystem in general).
We currently have std::sync::atomic::AtomicPtr but it does not work with function pointers by design:
fn foo() {}
static Foo: AtomicPtr<fn()->()> = AtomicPtr::new(foo);

emits
error[E0308]: mismatched types
 --> src/main.rs:5:50
  |
5 | static Foo: AtomicPtr<fn()->()> = AtomicPtr::new(foo);
  |                                                  ^^^ expected *-ptr, found fn item
  |
  = note: expected type `*mut fn()`
             found type `fn() {foo}`

This is at the pure brainstorming stage, but enabling this use case is probably going to need an AtomicFnPtr or similar type unless we retrofit AtomicPtr to also work with fn items.

EDIT: relevant threads/rfcs:
[0] pre-RFC: Extended atomic types proposes a generic atomic type that uses constraints to be generic. I don't know if that approach can be feasible extended to function pointer types.
[1] RFC 1543 (merged): Add more integer atomic types. Only mentions AtomicPtr, but it does not mention pointers to functions.
[2] Function pointers can be stored in atomic usizes just fine.

The main issue that I can see here is that we would need variadic generics to make this work for all possible argument lists for the inner function type.
Also have you considered whether AtomicFnPtr should allow a "null" value? In which case it would wrap a Option<fn()> rather than a raw fn().

Variadic generics aren't even enough, since fn types can have higher rank lifetimes (e.g., fn(&str) -> &str is actually a for<'a> ... binder). That issue isn't specific to atomics (e.g., it also affects trait impls for function pointers, except the magic compiler-generated ones), so there's motivation for some way to abstract over those HRLBs, but I don't know if that's even really possible and I certainly haven't heard of any proposals for how to add it to Rust.

The main issue that I can see here is that we would need variadic generics to make this work for all possible argument lists for the inner function type.

Thinking of: fn<'a, 'b, T, U>(x: &'a T, y: &'b U) -> &'a T vs fn<'a, T, U>(x: &'a T, y: &'a U) -> &'a T vs fn<'a, T, U>(x: &'a T, y: U) -> &'a T, would variadic generic be enough?

Also have you considered whether AtomicFnPtr should allow a "null" value?

I think "null" is a perfectly valid value for a raw fn pointer, but I don't know if it is possible to have one in Rust.

fn types are non-null. Unsafely type-punning a null pointer to a fn is instant UB.

Then I think we need AtomicFnPtr<Option<fn()->()>> . . .

At this point you might as well just use my crate.

Ping @gnzlbg; what's the state of this?
( You can do: AtomicPtr::new(foo as *mut _) )

Creating a null-valued fn pointer can't be UB, because it is safe:
fn main() {
    let foo = std::ptr::null() as *const fn() -> i32;
}

@kazcw That's not a null function pointer, that's a null pointer to a function pointer.

This would be very useful for defining global handlers in a safe way:
type Handler: fn(usize) -> bool;

static HANDLER: AtomicFnPtr<Handler> = AtomicFnPtr::new(None);

fn set_handler(h: Handler) {
    HANDLER.store(h, Ordering::SeqCst);
}

fn run_handler(u: usize) -> bool {
    let h: Option<Handler> = HANDLER.load(Ordering::SeqCst);
    let h = h.expect("No handler set");
    h(u)
}

This can be implemented in Rust right now by either:

Using a Mutex w/ std
Using AtomicUsize and transmute

It would be nice to have a safe way to do this w/ no_std.

@Amanieu It works for me, thanks! But I wonder why does it work while the std one does not? In other words, why std forbid "AtomicFnPtr", while your implementation can allow us to do that - what magic do you do ;) ?


Improve usability

this repository looks great and impressive but the main problem is that it is not clear enough to use
some steps are confusing and there are multiple files that seem to do same thing, could you please try to rewrite the workflow steps more clearly to make it easier for us to understand and implement
i hope i can help with this so I will try to understand the steps more deeply to make it happen.
thanks!

Hi @AhmadHakami , thank you for your interest. I will try to find some time updating this repositry. However, I moved my workflow to another repository using different tools from the OCRD community.
Maybe this helps you in the meantime:
https://github.com/linxOD/ocrd-image-enhancement
As for this repository:
It required the tools from here: https://github.com/linxOD/hocr-img-line-extraction to extract the lines from images.
To start the tesseract model training use the docker image. I have updated the script in the readme file. Make yourself familiar with the docker --volume argument. It mounts a local folder to the container. This way it's easy to create and move files.
After you created the ground-truth move the files to the /data dir of the docker container. Naming convention: your_model_name-ground-truth.
I hope this helps!


It is possible to run ng2-admin via angular-cli boilerplate?

I'm submitting a ...
[*] question about the decisions made in the repository

What is the current behavior?
Ng2-admin runs via custom webpack setup

What is the motivation / use case for changing the behavior?
Use vendor-provided CLI-tool to run/rule the project

Hey @dbykadorov, please track the progress in here https://github.com/akveo/ng2-admin/issues/6. Closing this one as dup. Thanks!


Add Mobility category and the following companies

Amenitiz
BVNK
Epos Now
FAIRTIQ
Glia
PagerDuty
Stream
SwissBorg

@marmelo @vpereira01 what do you think here?

I have mixed feelings with companies that are fully Remote and not based in PT.
If we allow them to enter the list, virtually all companies in the world are eligible, thus defying the purpose of this list.
What do you think?

@marmelo @vpereira01 what do you think here?

I have mixed feelings with companies that are fully Remote and not based in PT. If we allow them to enter the list, virtually all companies in the world are eligible, thus defying the purpose of this list.
What do you think?

From the previous discussion, the rule has been full remote is OK if the company has a policy to recruit from Portugal. Preferably the company has already employees with residence in Portugal.
Most remote companies have restrictions from where they recruit so this approach reduces the risk of too many companies.

@marmelo @vpereira01 what do you think here?

I have mixed feelings with companies that are fully Remote and not based in PT. If we allow them to enter the list, virtually all companies in the world are eligible, thus defying the purpose of this list.
What do you think?

From the previous discussion, the rule has been full remote is OK if the company has a policy to recruit from Portugal. Preferably the company has already employees with residence in Portugal.
Most remote companies have restrictions from where they recruit so this approach reduces the risk of too many companies.

I am OK with this rule.

@marmelo @vpereira01 what do you think here?

I have mixed feelings with companies that are fully Remote and not based in PT. If we allow them to enter the list, virtually all companies in the world are eligible, thus defying the purpose of this list.
What do you think?

From the previous discussion, the rule has been full remote is OK if the company has a policy to recruit from Portugal. Preferably the company has already employees with residence in Portugal.
Most remote companies have restrictions from where they recruit so this approach reduces the risk of too many companies.

I agree with these rules.
TL;DR it is OK to have companies fully remote that comply with any of:

Careers page explicitly seeks remote people from PT / EU;
Some PT engineers are already working remotely in the company.

If we all agree with this, I have added my PR comments.
All companies are OK except Amenitiz.
@jcoelho93 can you tell us why should Amenitiz be part of this list?
Thanks!

TL;DR it is OK to have companies fully remote that comply with any of:
Careers page explicitly seeks remote people from PT / EU;
Some PT engineers are already working remotely in the company.

I'll add this to our Contributing page!

TL;DR it is OK to have companies fully remote that comply with any of:
Careers page explicitly seeks remote people from PT / EU;
Some PT engineers are already working remotely in the company.

I'll add this to our Contributing page!

Thank you! :pray:

:+1: tks @jcoelho93


docs(translate): Add Korean translation

Hello all,
I've added Korean translation file README_ko.md and I've updated translation section too.
If I missed something, please feel free to tell me.
I'll keep working on other docs too.
Thanks,
Jisu

As those translations tend to outdate themselves when we work on the core itself and are able to update only the english one, I think it would be good to add a note at the top about last update + version of the saga at the moment of the update. Exact same note should be added in other translations too, I'll try to confront them with git history and add it appropriately when i have time.

@Andarist Thank you for the feedback. I agree with that. So I added NOTE section at the top. It will notes last version with exact commit history.


style: increase code font size

🧰 Changes
Jaclyn and I noticed that the font size for code blocks was a little small:

So this PR bumps it to 95%
next PR #915
🧬 QA & Testing

Broken on production.
Working in this PR app.

This PR was released!
🚀 Changes included in v6.75.0-beta.61


Correct spelling error on cut-on-resolve.yml

just doing a simple pull request to see if I understand the organizational structure of the site

Amazing, THANK YOU!


Added offline support (pwa-service worker)

Fixes #1
Added offline support using service worker.
Files created : 1) sw.js  2) main.js
Added style of tailwind which is came by cdn locally in style.css
link main.js file in index.html

Thanks @aakash18012!