Converting floats to strings produces commas as decimalls in certain countries

Divide 3 by 4 and you'll get 0.75.  But if you set the phone language to Italian, you'll get 0,75.
On the other hand, in Italian, 0,75 is not recognized as a number.
A quick fix could be to always generate 0.75.   It would be better to make something that works internationally.

fixed in pr #343


Make Bazel building the Bazel java-tutorial out of the box

Describe the bug
When following the Bazel Java tutorial, more steps and Bazel arguments are required to build the proposed example with Bazel coming from nixpkgs.
The tutorial can be reduced to this commands:
# Install Java 8 JDK.
$ export JAVA_HOME="$(dirname $(dirname $(realpath $(which javac))))"
$ bazel build //:ProjectRunner

While to build this project with Bazel from nixpkgs, I needed to specify the  --host_javabase to Bazel:
nix-shell -I nixpkgs=https://github.com/nixos/nixpkgs/archive/fce7562cf46727fdaf801b232116bc9ce0512049.tar.gz -p bazel -p jdk11_headless -p gcc
$ export CC=$(which gcc)
$ export JDK=$(dirname $(dirname $(which javac)))
$ echo ${JDK}
/nix/store/2mr83nlzf2zw6f1idi0x3r4bdx9s7z2c-openjdk-headless-11.0.6-ga
$ bazel build //:ProjectRunner --host_javabase=@bazel_tools//tools/jdk:absolute_javabase --define=ABSOLUTE_JAVABASE=${JDK}

To Reproduce
If I follow the tutorial, it fails with:
nix-shell -I nixpkgs=https://github.com/nixos/nixpkgs/archive/fce7562cf46727fdaf801b232116bc9ce0512049.tar.gz -p bazel -p jdk11_headless -p gcc
$ export CC=$(which gcc)
$ type -P javac
/nix/store/2mr83nlzf2zw6f1idi0x3r4bdx9s7z2c-openjdk-headless-11.0.6-ga/bin/javac
$ export JAVA_HOME="$(dirname $(dirname $(realpath $(which javac))))"
$ /nix/store/2mr83nlzf2zw6f1idi0x3r4bdx9s7z2c-openjdk-headless-11.0.6-ga/bin/javac
bazel build //:ProjectRunner
INFO: Build options --define and --host_javabase have changed, discarding analysis cache.
INFO: Analyzed target //:ProjectRunner (0 packages loaded, 331 targets configured).
INFO: Found 1 target...
ERROR: /home/lewo/.cache/bazel/_bazel_lewo/d784f1ca0f7dffa1c13b66ed45bdf65e/external/bazel_tools/tools/jdk/BUILD:314:1: Action external/bazel_tools/tools/jdk/platformclasspath_classes/DumpPlatformClassPath.class failed (Exit 1) javac failed: error executing command external/remotejdk11_linux/bin/javac -source 8 -target 8 -Xlint:-options -cp external/remotejdk11_linux/lib/tools.jar -d ... (remaining 2 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
src/main/tools/linux-sandbox-pid1.cc:427: "execvp(external/remotejdk11_linux/bin/javac, 0x191ea20)": No such file or directory
Target //:ProjectRunner failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.209s, Critical Path: 0.02s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

Expected behavior
It would actually be really nice to be able to just follow the tutorial when using Bazel from nixpkgs.
How could we make our Bazel building this project without any additional command line arguments?

I assume the Bazel Java tutorial tries to automatically download a Java distribution. That’s a degenerate case of course, and the downloaded Java compiler won’t run on NixOS.
If that’s the case there’s not much we can do here, upstream makes a wrong assumption “every system can execute arbitrary executables downloaded from the internet”.
Can you link the WORKSPACE file of the tutorial? Then I can give more insight.

@Profpatsch
https://github.com/bazelbuild/examples/tree/master/java-tutorial
https://github.com/bazelbuild/examples/blob/master/java-tutorial/WORKSPACE
Bazel fetches @remotejdk11_linux by default and should fail on attempting to fetch instead of at runtime. The fetch failed for me when I tried to run some cc tests w/o networking, and led to #98611 .

cc @NixOS/bazel. This might require a patch or a wrapper.


Tilemap.createDynamicLayer fails to set a default values when called without x and y.

Version

Phaser Version: 3.16.2

Operating system: mac os

Browser: latest chrome (73) and firefox (66)

Description
For some strange reason Tilemap.createDynamicLayer fails to set a default y value when called without x and y.
Test with:
Call map.createDynamicLayer('MyLayer', 'MyTileset') without specifying x and y, the layer is created with an x of 0 (or offsetx) but y is set to undefined.
Expected:
The y value should be set to 0 or the offsety that was parsed from tiled, just like the x value.
From src/tilemaps/Tilemap.js:
        //  Default the x/y position to match Tiled layer offset, if it exists.
        if (x === undefined && this.layers[index].x) { x = this.layers[index].x; }
        if (y === undefined && this.layers[index].y) { y = this.layers[index].y; }

        // ---> Here 'y' is left being undefined !!
        var layer = new DynamicTilemapLayer(this.scene, this, index, tileset, x, y);

EDIT: After a some debugging the error was quite obvious. The if fails every time when this.layers[index].x or this.layers[index].y are 0 (they are falsy values!). Also LayerData will always have x and y defined and by default they are 0 so these if will always fail unless offsetx and offsety values in the map file are defined and different from 0.
SOLUTION
Change those lines for these and everything works as intended:
        if (x === undefined) { x = layerData.x; }
        if (y === undefined) { y = layerData.y; }

        var layer = new DynamicTilemapLayer(this.scene, this, index, tileset, x, y);

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Get is urgent needing a remake

Basicly the package is abandoned, and a lot of thinks that work in past are not the same. The last update is 2 months ago, so that only comprove my sugested, so bugs were found but the Getx Team don't fixed it.
I cannot believe that the most famous package in flutter was simply ignored, please or you do something like call some people to help you or pass the administration to a active person.
@jonataslaw

For sure everyone loves the package because it is very useful, robust and of course free, but also if the important functions starts to show some problems it needs maintenance and atention.

getx and Propaganda  from others in flutter community
is communication that is primarily used to influence or persuade an audience to further an agenda objective  and may be selectively presenting facts to encourage a particular synthesis or perception, or using loaded language  to produce an emotional rather than a rational response to the information that is being presented.
GetX community never give up

getx and Propaganda from others in flutter community
is communication that is primarily used to influence or persuade an audience to further an agenda objective and may be selectively presenting facts to encourage a particular synthesis or perception, or using loaded language to produce an emotional rather than a rational response to the information that is being presented.
GetX community never give up

? I realy didn't understand your comment

This is undid a big problem.
There have been a lot of undocumented breaking changes (Nav2 has been there for more than a year and has still no documentation), (It has introduced a lot of breaking changes even on the stable release).
The package is not properly tested which makes it currently a bug bomb.

To be honest, the master version has a full state manager refactor, a full navigation refactor, and a full dependency manager refactor.
I sincerely wish I had more time, and I will probably have it from the 16th of next month.
The reason I haven't sent getx 5 to pub dev yet is that:
1- he has no documentation
2- Navigator 2's nested navigation still has bugs
3- still need to rewrite the modals. Nav 2 introduced a bunch of issues into Flutter, such as:
-It's impossible to use it without using the nav 1 api, especially for overlays. We need to rewrite the dialogs and bottomsheets and use a custom overlay to fix show them.
If anyone is willing to help maintain the library, I'm also willing to explain how each feature works and is built.

Well, i can help a bit if needed.
Was it not a bit too ambitious to refactor all of that?
Will it haven't been easier to first test everything and then start to refactor?
Was it a good idea to start to refactor in v4.6.5? and not wait for 5.0.0?
My main concern is that going into Listenable for _RxImpl from 4.6.5 introduced a major bug.
See #2521 which completely destroys GetX performace.
It also means that #2518 (broken toggle) is still in 4.6.5.
Would it not be better to make sure v4 is stable, tested and documented before going to release v5?
I'm at the moment trying to fix #2521 but i cannot figure out we that other observable is added to the disposers field of the StatelessObserverComponent. But since i'm not familiar with StatelessElement i must be missing something...

@jonataslaw when you return, can you please work in #2336?

Well, i can help a bit if needed.
Was it not a bit too ambitious to refactor all of that? Will it haven't been easier to first test everything and then start to refactor? Was it a good idea to start to refactor in v4.6.5? and not wait for 5.0.0?
My main concern is that going into Listenable for _RxImpl from 4.6.5 introduced a major bug. It also means that #2518 (broken toggle) is still in 4.6.5.
Would it not be better to make sure v4 is stable, tested and documented before going to release v5?

There are also many opened pull requests

@jonataslaw when you will return to update GetX?

Can Getx ever bring context in future package versions? And still, make it the most simple state management?

To be honest, the master version has a full state manager refactor, a full navigation refactor, and a full dependency manager refactor.
I sincerely wish I had more time, and I will probably have it from the 16th of next month.
The reason I haven't sent getx 5 to pub dev yet is that:
1- he has no documentation
2- Navigator 2's nested navigation still has bugs
3- still need to rewrite the modals. Nav 2 introduced a bunch of issues into Flutter, such as:
-It's impossible to use it without using the nav 1 api, especially for overlays. We need to rewrite the dialogs and bottomsheets and use a custom overlay to fix show them.
If anyone is willing to help maintain the library, I'm also willing to explain how each feature works and is built.

@jonataslaw are you returning to active development of the package?

Looks like the package is abandoned 👎  .... probably time to start working on a major transition to something else
4.6.5 (7 months ago) / 5.0.0-beta.52 (5 months ago)

A leader is needed.  There is talent willing to support the project but there is a lack of someone to manage it.  Sorry for my English

This really needs @jonataslaw to support a transition. I'd put my hand up to lead and support this, but if Jonny isn't willing then it would be difficult to undertake
Best outcome is for Jonny to assign someone owner of the existing repo... still viable but hard to facilitate is the copy / fork and duplicate approach


HTTP 1 versus 2 namespacing

I decided to investigate how easy it would be to take the current method of suffixing _v1 to names and include things using _v2, with ideally no collisions while each produces the same functionality. The process was basically:

copy all files with _v1 in the name to an equivalent _v2 file.
rename all of the things in the _v2 files from _v1 to _v2.
fix up includes.
compile and hope it works.

Unfortunately, there are many declarations in the _v1 files which basically pollute the namespace with unversioned names. So, I tried adding suffixes to the names that conflicted, either _v1 or _v2, as appropriate. This took a few hours but eventually worked.
However, I don't think this approach is reasonable and I'd prefer if the approach taken by asio with regard to ipv4 and ipv6, namely, namespaces. I think this situation would be much better with a beast::http::v1::* and beast::http::v2::*. Especially since implementing HTTP/2 will require tracking a 'session' per connection, because connections have state and multiplex streams, unlike HTTP/1 where Beast currently assumes that serializing a message to a stream is sufficient.
I have some preliminary ideas for how HTTP/2 could be represented in Beast, but I'd rather focus on ensuring that the current interface doesn't make implementing HTTP/2 inelegant due to weird naming issues (for lack of a better way of putting it).

Thank you for your interest in Beast! I think its great that you're looking into this!
However, while the free function approach to parsing HTTP/1 messages is certainly elegant and simple, HTTP/2 is a different matter entirely. First I want to point out that I have designed Beast from the ground up with HTTP/2 in mind, so the design choices that you take it into account (there are also some other bigger changes coming to the message model and free function, to permit certain behaviors required by RFC7230 and RFC7231).
The thing about HTTP/2 is that it is stateful. Its not possible to decode HTTP/2 messages without having a context in which to store metadata. A couple of examples:

Header compression has to keep a sliding window and dictionary state
Multiple messages can be incrementally received, requiring intermediate state to hold the data as it is received

So we aren't going to be able to use the simple read and write interfaces that we have for HTTP/1.
I'm leaning towards providing a "HTTP/2 session" object, modeled after boost::asio::ssl::stream and beast::websocket::stream. Something like this:
template<class NextLayer>
class http::stream_v2
{
  NextLayer next_layer_;
  ...
public:
  ...
  /** Deserialize a HTTP message from the stream.

    @param id The message-identifier, unique for each message.
    @param msg The received message.
    @param ec Set to the error, if any occurred/
  */
  template<bool isRequest, class Body, class Headers>
  void
  read(
    std::size_t& id,
    message<isRequest, Body, Headers>& message,
    error_code& ec);
};

I think this would work pretty well. The scope of HTTP/2 is much bigger than HTTP/1, covering things like flow control and multiplexing. An object-based approach instead of free functions gives us much more flexibility in interface choice. And its a proven model (see ssl::stream and websocket::stream).
I'd love to hear your thoughts on this design

Oh, that's exactly what I was thinking. I suppose the specific point I'm attempting to raise here is that Beast as it stands, effectively has namespace pollution, which wouldn't exist if suffixing were used more often or if namespaces were used for v1 vs v2.
HTTP/2 being implemented as a stream is the obvious choice and in fact, you probably want it to be a session of streams, since stream is actually a term used to name a specific concept in HTTP/2. It'd be better to discuss this in another thread, though.
However, the specific goal of this issue is about namespaces/naming, not really, HTTP/2 design.
A good example of namespace pollution is that parser_v1.hpp declares the following in the beast::http namespace:

detail::parser_request
detail::parser_response
skip_body
parser_v1

Only parser_v1 is versioned and the others would likely have analogs in future parser implementations for v2 (and beyond, I suppose). Even the names in the detail namespace matter, since even though they are supposed to be private, they will conflict with a similar detail namespace used for implementing a parser for v2.
However, if namespaces were used, this wouldn't be an issue, since you would have:

v1::detail::parser_request
v1::detail::parser_response
v1::skip_body
v1::parser

And therefore, there would be no concern of collisions.
Does the example help my point make more sense?

Yes, I see what you mean now. As I am still making some design changes (see https://github.com/vinniefalco/Beast/commits/message), there are likely to be naming problems such as the ones you pointed out. My plan is to iron these things out during the Boost formal review, but your input is valuable here.

you probably want it to be a session of streams, since stream is actually a term used to name a specific concept in HTTP/2.

That's true. I've edited my prototype code to say http::session_v2 instead.

Even the names in the detail namespace matter

I'm not so sure about that. Since detail identifier names are not public, they are free to be renamed. When I add HTTP/2 support I can rename detail identifiers however I please to resolve conflicts.

...since you would have:

You listed the HTTP/1 parser and its accompanying options. So we're clear, you are proposing putting all HTTP/1 parser related routines in namespace v1? What about beast::http::read? And what about beast::http::parse (which is not specific to HTTP at all, works with any Parser concept)?
What do we do later if we want to version the API, not for HTTP but for non backward compatible improvements? We would have burned the v1 and v2 namespaces.

I'm only proposing that the names in *_v1.hpp files be placed in a beast::http::v1 namespace.
This means that if the name is generic enough, it could be placed in another file. Like, skip_body can probably be placed in a file that's shared between v1 and v2, since in both cases, you may want to skip the body. But for example, the parser would be v1::parser and v2::parser.

Okay, that's something to consider. Note that message_v1.hpp (and the message_v1 class) will disappear in b16 or b17.

Ah, I just looked at the branch that you linked. It seems you moved the version to the headers object? Is there a reason for that, as opposed to the message object?

...you moved the version to the headers object? Is there a reason for that

Yes. To support "Expect: 100-continue", Beast must provide an interface that allows you to send and receive a message without the body. And then conditionally finish sending or receiving the message body. response_headers and request_headers represent that part of the message, without the body.
There is also another use-case, when building a server it might be desired to make a choice of the Body template type based on the contents of the headers. Having these additional classes makes that implementation possible.

Yeah, I just realized that request_fields was renamed to request_headers. I commented that I like the name request_fields slightly better, but now that I think more about it, I'm not so sure. In the use case you describe, it is quite literally, the request_headers, so it's not inaccurate at all.

There's going to be some identifier name volatility as we build out these changes so I'm not terribly worried about it at the moment - suggestions for alternatives are of course always welcomed (even if the conclusion is to not change something). And I'm certain that there will be a fair amount of bike shedding during the formal review :-)

request_headers is probably a better name. After all, my confusion only lasted 5-10 minutes, which probably means it's a great name. Significantly better than x. :)

See #123

This is all done, the library has undergone extensive renaming and tuning of the interfaces. I think its in a really good place now.


Drop without disconnect causing resource leak

When Client or Server are dropped, the reference within them, to Arc<ClientInternal> or Arc<ServerInternal> may remain active in the handler cycle.
Suggestion: implement Drop for Client and Server, and ensure that they are marked as disconnected, as mentioned in the suggestion here.

Fixed in #8.


Add deployment action; remove travis yml

@gnosis/mobile-devs

A more general comment: it would be nice to have a PR description that either links to an issue or explains in itself why the changes in the PRbhave been done and what the expected change in behavior is.


⚠ ClamAV has degraded performance

In b74c0e5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 1704c4b after 5 minutes.


Added new application written in Semantic-UI react

Just added our new web app written in Semantic-UI react.

Codecov Report

Merging #1913 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1913   +/-   ##
=======================================
  Coverage   99.77%   99.77%
=======================================
  Files         148      148
  Lines        2637     2637
=======================================
  Hits         2631     2631
  Misses          6        6

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 82259a7...b11cd00. Read the comment docs.

Fantastic, thanks!

Released in<EMAIL_ADDRESS>


Feature Request: Keybinding to prevent creation of close tag

I frequently want to insert an open tag somewhere in my HTML, and then later choose where I want to close tag. Is there (or could there be) a way for a simple keybinding to prevent the automatic creation of the close tag? Say, something like Option-> to just generate the '>' but not the  part?  Thanks.

I achieved this by creating a custom function for inserting a plain > like so:

Add this to your init.coffee:

atom.commands.add 'atom-text-editor',
  # Inserts a closing angle bracket '>' without triggering autoclose-html
  'custom:insert-plain-closing-angle': ->
    atom.workspace.getActiveTextEditor()?.insertText('>')

Add this to your keymap.cson:

'atom-text-editor':
  'alt-.': 'custom:insert-plain-closing-angle'

Restart Atom

Now you can press alt-. to insert a plain > without triggering the autoclose behavior.

Very nice. Thanks, Ben!


New version: martinrotter.RSSGuard version 4.5.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

[Policy] Needs-Attention

Automatic Validation ended with:

Exception during executable launch operation System.AggregateException: One or more errors occurred. (The specified executable is not a valid application for this OS platform.)  ---

@wingetbot waivers Add Validation-Executable-Error


Add dominicgifford CCLA

As discussed with @mcleo-d , please add me to IHSM CCLA

Hi @dominicgifford - Your CCLA has been verified through EasyCLA. Can you make a small change to your commit and push so we can test?
Many thanks,
James 🚀

@mcleo-d - this looks better - I think we're done?

@mcleo-d - this looks better - I think we're done?

Yes, thanks so much for your help and support.
I'm now making sure we're good for https://github.com/finos/FDC3/pull/419 😸 👍🏻
James 🚀


Documentation Still Refers to 'Getting Started' folder, which has been Renamed

Documentation Still Refers to 'Getting Started' folder, which has been Renamed

Thank you @essenbee2  It should be fix with #55.
I'll close this issue.


doc uses outdated commands

My issue is about that documentation:
http://docs.docker.com/v1.5/articles/networking/#ipv6
route -A inet6 add 2001:db8:0:2::/64 dev docker0
should be replaced by
ip -6 route add 2001:db8:0:2::/64 dev docker0
ifconfig should be replaced by ip addr ; ip link
The first part correctly uses the doc-prefix 2001:db8::/32
But later 2002:: is used, this prefix is reserved for  6to4 and could confuse the reader.
I think it is also better to use
sysctl net.ipv6.conf.eth0.accept_ra=2
instead of
echo 2 > /proc/sys/net/ipv6/conf/eth0/accept_ra
to ipv6 itself, I tested only the first scenario

@thomasschaeferm I see there's a pull-request opened to fix the issues you mentioned, perhaps you could have a look at those changes as well, to confirm they address the issues you mentioned here; you can find the PR here; https://github.com/docker/docker/issues/10751

The first part is solved.
But the prefixes...
I know IPv6-Adresses are long and 2001:db8::/32 may be a long string in some (svg)-images.
But in my point of view it is a must be. Documentation should be recognised as documentation. And people who accidentally take over the examples without thinking should have a limited damage.
2001::/32 is teredo
2002::/32 is 6to4
2003::/19 is Deutsche Telekom
Please do not increment to 2004, this network is not assigned yet.
Also please don't use fc00:/7. This could people lead to have bad minds.

Thanks for looking, @thomasschaeferm, because I'm no IPv6 myself, I'm going to politely
/ping @MalteJ and @estesp

@thomasschaeferm yes, you are right with all the points you have mentioned.
Indeed I have used 2001, 2002, 2003 for space reasons. Yes, I am not happy with this, too. Probably this should be corrected.

@MalteJ @estesp I think this issue can be closed now that https://github.com/docker/docker/issues/10751 is merged (GitHub didn't close it automatically for some reason)

Thanks, absolutely.  @thomasschaeferm let me know if you have any additional feedback on IPv6 documentation, but I believe all current comments are handled.


[0.20.x] vitest no longer works with yarn pnp

Describe the bug
After upgrading to 0.20.x, tests are no longer able to run due to yarn being unable to find a module
events.js:377
      throw er; // Unhandled 'error' event
      ^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/user/git/vitest_yarn2/.yarn/__virtual__/vitest-virtual-3235595f85/0/cache/vitest-npm-0.20.2-9730ec2bf1-eea156689f.zip/node_modules/vitest/dist/loader.mjs' imported from /home/user/git/vitest_yarn2/
Did you mean to import /home/user/git/vitest_yarn2/.yarn/__virtual__/vitest-virtual-3235595f85/0/cache/vitest-npm-0.20.2-9730ec2bf1-eea156689f.zip/node_modules/vitest/dist/loader.mjs?

Reproduction
Here is a repo that exhibits the problem. I purposefully left it in a working state with vitest at 0.19.1, to show that 0.19.1 worked. The README.md has details on how to reproduce.
https://github.com/jereklas/vitest_yarn2
System Info
System:
    OS: Linux 5.14 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 465.59 MB / 15.36 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.20.0 - /usr/bin/node
    Yarn: 3.2.2 - /usr/bin/yarn
    npm: 6.14.17 - /usr/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Firefox: 102.0

Used Package Manager
yarn
Validations

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

Try disabling deps.registerNodeLoader for now

I was just doing that and was about to report back that deps.registerNodeLoader is a work around! You beat me to it.

It's not possible to use custom experimental loader with Yarn PnP at the moment. We need https://github.com/nodejs/node/pull/43772 to be resolved first.
For now we will detect, if running under Yarn PnP and disable registerNodeLoader in #1773.

Experienced similar issue in a SolidJS project maintained with pnpm. Tests worked flawlessly with 0.19.x and started failing with a cryptic You appear to have multiple instances of Solid. This can lead to unexpected behavior. in 0.20.x. Workaround to disable deps.registerNodeLoader also works in this scenario.

Experienced similar issue in a SolidJS project maintained with pnpm. Tests worked flawlessly with 0.19.x and started failing with a cryptic You appear to have multiple instances of Solid. This can lead to unexpected behavior. in 0.20.x. Workaround to disable deps.registerNodeLoader also works in this scenario.

Solid example was updated, you no longer need to inline solid.


Fix proxy generation based on public interfaces nested in internal ones

This applies the same fix for generation of local proxies as https://github.com/microsoft/vs-streamjsonrpc/pull/1072 added for RPC proxies.

The new test will fail for the RPC proxies until the StreamJsonRpc dependencies in this repo is updated to a version that includes https://github.com/microsoft/vs-streamjsonrpc/pull/1072.


HDFS-17177. ErasureCodingWork reconstruct ignore the block length is Long.MAX_VALUE

Description of PR
https://issues.apache.org/jira/browse/HDFS-17177
As noted in https://issues.apache.org/jira/browse/HDFS-14720,
ErasureCodingWork reconstruct maybe also need to ignore the block lengths of Long.MAX_VALUE.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 39s

trunk passed

+1 :green_heart:
compile
0m 52s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 43s

trunk passed

+1 :green_heart:
mvnsite
0m 53s

trunk passed

+1 :green_heart:
javadoc
0m 48s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 58s

trunk passed

+1 :green_heart:
shadedclient
22m 57s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 43s

the patch passed

+1 :green_heart:
compile
0m 46s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
0m 46s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 32s

the patch passed

+1 :green_heart:
mvnsite
0m 45s

the patch passed

+1 :green_heart:
javadoc
0m 36s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m  2s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 51s

the patch passed

+1 :green_heart:
shadedclient
21m 55s

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

_ Other Tests _

+1 :green_heart:
unit
196m 27s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

291m 30s

Subsystem
Report/Notes

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

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

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

uname
Linux bcf040e9237f 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4b69d6db080354fd696eb695a53a0125ebf83077

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Thanks @ZanderXu @zhangshuyan0 help me review.
yeah, use getBlock().isDeleted() can better intuitively indicate that the current block has been deleted,
In the current code, ReplicationWork#chooseTargets and DatanodeManager#handleHeartbeat maybe can be changed to getBlock().isDeleted(),  what do you think about?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
43m 21s

trunk passed

+1 :green_heart:
compile
1m 30s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 16s

trunk passed

+1 :green_heart:
mvnsite
1m 32s

trunk passed

+1 :green_heart:
javadoc
1m 15s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 45s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 33s

trunk passed

+1 :green_heart:
shadedclient
35m 54s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 18s

the patch passed

+1 :green_heart:
compile
1m 20s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 20s

the patch passed

+1 :green_heart:
compile
1m 12s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  6s

the patch passed

+1 :green_heart:
mvnsite
1m 19s

the patch passed

+1 :green_heart:
javadoc
1m  1s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 28s

the patch passed

+1 :green_heart:
shadedclient
35m 51s

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

_ Other Tests _

+1 :green_heart:
unit
224m 27s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

365m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/3/artifact/out/Dockerfile

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

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

uname
Linux 2242d61bea7b 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b9ea3fe053d7a63b0e723891a5e4737a64443272

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/3/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 31s

trunk passed

+1 :green_heart:
compile
1m 28s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 21s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 17s

trunk passed

+1 :green_heart:
mvnsite
1m 30s

trunk passed

+1 :green_heart:
javadoc
1m 16s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 48s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 31s

trunk passed

+1 :green_heart:
shadedclient
36m 45s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 15s

the patch passed

+1 :green_heart:
compile
1m 20s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 20s

the patch passed

+1 :green_heart:
compile
1m 12s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  2s

the patch passed

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 35s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 27s

the patch passed

+1 :green_heart:
shadedclient
36m 19s

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

_ Other Tests _

+1 :green_heart:
unit
224m 22s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 52s

The patch does not generate ASF License warnings.

368m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/2/artifact/out/Dockerfile

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

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

uname
Linux 69572b2943f7 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b9ea3fe053d7a63b0e723891a5e4737a64443272

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/2/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6024/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Thanks @haiyang1987 for your work and thanks @zhangshuyan0 for your review.

Thanks @ZanderXu @zhangshuyan0 help me review and merge it!


Build a peptide from a starting residue

Hi,
First of all, congratulations on this nice piece of software. I would like to know if it's possible to use PeptideBuilder to build a peptide starting from a PDB file which contains a single residue and use its atom coordinates in the process.
Thank you in advance for your time and help!

Hi,
Can you clarify the statement "and use its atom coordinates in the process"?

Sure, I mean using the only residue from the PDB file as an anchor and build the rest of the peptide given a sequence.

PeptideBuilder cannot modify an existing PDB file. If the peptide anchor coordinates in (x,y,z) space is important for your purposes, you can investigate the method "def initialize_res(residue: Union[Geo, str]) -> Structure." An override of this method will allow you to specify the (x,y,z) coordinates of your anchor residue instead of how it is currently written to start at (0,0,0). You will be able to take your PDB file and create a new PDB that can build peptides of your given sequence.
I hope I am understanding your question correctly?

Amazing, that is basically what I needed :)
Thanks a lot for your quick and useful answer!

PeptideBuilder cannot modify an existing PDB file.

Matthew, is this fully true? If I understand correctly how PeptideBuilder works, it appends residues to the end of chain A model 0 of a biopython structure object. Shouldn't it be possible to read a PDB file that has only a single chain, A, (containing one or more residues) and then append to that chain?

Claus, you are correct, in that this is not "fully true". From the tester scripts we have provided, one can "read" the geometries of a PDB file (lets call it "A.pdb") and then start the construction of a biopython structure object. This will not modify the original read A.pdb file, but will create an object that can be used to append residues to their specified anchor during the reading. The created object during reading and construction will anchor the first read residue at (0,0,0). If the user wants to retain the (x,y,z) coordinates of A.pdb, then that will take a more sophisticated approach to the "initialize_res" method. However, if the user is ok with this nuance, they in essence can modify an existing A.pdb, and should write the modified biopython PDB as  "A_modified.pdb" for instance.

Ah, I see.
@brianjimenez There's also always the option of first constructing the peptide you need anchored at (0, 0) and then using the PDB module of biopython to translate/rotate the peptide in space to where you need it.

Thanks a lot for the answers and discussion. @clauswilke , we plan to use PeptideBuilder starting from an anchor residue which has been predicted to be in a specific binding position with a receptor protein molecule (kind of threading, but in complex context). For that reason the approach of building and after superimposing won't be good enough.

Hello, I am having difficulties installing your software. have you ever tested it on Mac?
which version of python do you use ?

All the testing scripts provided in the Github were tested on Mac.

As stated in "NEWS.md" PeptideBuilder 1.1.0 has dropped version Python 2.7 compatibility and is compatible with Python 3.


Support RETURNING for SQLite

@billy1624 I'm not sure what the original problem was, but could RETURNING be supported for SQLite now?
Motivation
I have a query that has an ON CONFLICT and I want to use exec_with_returning, however last_insert_rowid is not set for SQLite when there's a conflict, so there's no way to figure out which row was updated. My query looks like:
Model::insert().on_conflict(...).exec_with_returning(db)

This works fine on Postgres but not SQLite
Proposed Solutions
Get RETURNING working for SQLite
Current Workarounds
You can do an extra SELECT query instead of using ON CONFLICT

I think the blocker is we needed a way to tell if the linked SQLite version supports RETURNING.
A less ideal solution would be to detect that on runtime, and adjust the logic accordingly. This would actually be a bigger change.


Few Features

This would work well on local as well as internet/hosted in server
#1 - Is it possible to add import song option -> title, song name, singer, lyrics, file (mp3 or m4a)
#2 - Is it possible to provide search song by any word in lyrics content or song name or song type
#3 - Possible to provide equalizer support
Example
https://stackoverflow.com/questions/34854976/write-a-preamp-with-html5-audio-api
https://codepen.io/Merevy/pen/egYrmB
https://github.com/bitgapp/eqMac
Thanks

It is already possible to "import" a song, all you need to do is copy the file to the folder you are currently playing from and it'll show up in the playlist.
Features 2 and 3 are outside the scope of this project.


Community page to be retrieved from documentation repo

What would you like to be added:
During website publishing Community Page shall be retrieved from documentation repo
Why is this needed:
Currently it is taken from   hugo/layouts/community/list.html but exists also in documentation repo: https://github.com/gardener/documentation/tree/master/website/community

/invite @n-boshnakov


bpf: add missing drop notifications

End goal was to get rid of the stray drop notification that's currently buried in __encap_and_redirect_with_nodeid(). Getting there took quite a few additional drive-by fixes :).
The last two patches can be dropped from the backport (encap_and_redirect_with_nodeid_opt() didn't exist in v1.13).
Add drop notifications for various error paths in the datapath.

/test

/test

BPF checkpatch complains about

CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#21: FILE: bpf/bpf_host.c:1278:

  		ret = encap_and_redirect_with_nodeid_opt(ctx,
  						  ctx_get_xfer(ctx,

which was already bad before. And fixing it means triggering checkpatch again, because we're then exceeding max line width :shrug:. Think I'm good leaving it as is, we're planning to remove this code during the current release cycle anyway.

@ldelossa :wave: how can I help with making your review easier?

One static checker complaint (https://github.com/cilium/cilium/pull/25183#issuecomment-1527379993) that is ok to ignore imo. The e2e workflow is marked as still expected, but that's just because when the PR was opened this was still called ci-datapath (which is green).
So Ready-to-merge (cc @youngnick :pray:)


Usage of reflection reduces usefulness with Spring

If the lookup of Query, Mutation were not by class.getSimpleName() and instead by either annotation or interface/parent type, it would allow the Query class etc to be enhanced by Spring for validation, security, etc
Unfortunately, any attempt to do this now will fail as the proxy class generated by Spring etc will have a different name...

Check out the latest version - Root query resolvers are now indicated solely by annotation and can be spread across multiple resolvers.

https://github.com/graphql-java/graphql-java-tools/blob/master/README.md#root-resolvers

Cool.  Will test it out.

@martin-walsh did that fix your issue?

Works a treat, nice one !


Add information regarding --cairo-compiler-manifest

Usage related changes

Adds additional information to the documentation.


Present interim results immediately when reading from pipe (like fzf)

The behaviour of the two commands:
find / | fzf

find / | fzy

Is quite different.  With fzf, results start appearing immediately.  Could fzy also behave the same?

This has already been discussed in detail. I believe results appearing before they are ready to be a UI anti pattern. Even though it "feels" better, it results in mistakes, as incorrect data is presented to the user (sort order matters in a fuzzy finder)


go_1_22: 1.22.2 -> 1.22.3

Description of changes
Changelog: https://go.dev/doc/devel/release#go1.22.minor

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Duplicate of https://github.com/NixOS/nixpkgs/pull/310004
https://nixpk.gs/pr-tracker.html?pr=310004


Add CI config files

works with https://github.com/omec-project/omec-project-ci/pull/70

Please dont merge any change in Nucleus/Master... Else @badhrinathpa  need to do git pull again.. He has massive difficulty in getting this merge done. We are avoiding all the merges for now.

retest this please

retest this please


App cannot handle empty views

The App hits an error when trying to load an empty view, e.g., Exists("field_that_does_not_exist").

I'm not seeing this on develop.

Disregard, I am able to find issues like this when there are labels present. Working on it.

https://github.com/voxel51/fiftyone/pull/459


"name 'banner' is not defined" error

"Traceback (most recent call last):
File "/root/TNT-sms/main.py", line 49, in
banner()
NameError: name 'banner' is not defined"
what's the solution?

I will check

"Traceback (most recent call last): File "/root/TNT-sms/main.py", line 49, in banner() NameError: name 'banner' is not defined"
what's the solution?

It's done, try again and install the presets from the beginning


Number of seconds per step

Please, I have a simple question.
I'm training WaveNet with the VCTK corpus dataset in a CPU only machine (Intel i5) running to 20 sec/step. At this rate, I can reach about 4000 steps per day, 30.000 at week. Question is: ¿How much steps do we need to get a loss from about 2? And, another question: Can anybody tell me what is the seconds per step rate that a good GPU can reach? By the way, what's the rate in which each of you are working on guys?
Regards,
Samu.
Note. I'm using the default params:
{
"filter_width": 2,
"sample_rate": 16000,
"dilations": [1, 2, 4, 8, 16, 32, 64, 128, 256,
1, 2, 4, 8, 16, 32, 64, 128, 256],
"residual_channels": 32,
"dilation_channels":16,
"quantization_channels": 256,
"skip_channels": 256,
"use_biases": false
}

Using default params I get loss of ~2 quite fast, in about 300 steps. You just need to lower learning rate, otherwise loss does not get lower that ~2.5.
I get 0.6-0.9 sec/step on TitanX GPU, using batch_size of 2

"I get 0.6-0.9 sec/step on TitanX GPU, using batch_size of 2"
Wow!!
I would love to have enough money to buy one of those.
Thank you for the info, @r-zemblys

I get about 0.5 sec / step on a K40 using batch_size = 1.

0.5 sec/step!! You can run more than 7k steps per hour!! I can run only  4k per day :P
Definitely, I have to buy a GPU for my computer.

@Zeta36: Right, there's an issue on it now: #112.

How do you lower the learning rate?

In my case 3 sec per step. Learning rate was annealed by scheduled shell
script.
2016년 12월 13일 (화) 오후 7:39, Alexander Claussen<EMAIL_ADDRESS>작성:

How do you lower the learning rate?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ibab/tensorflow-wavenet/issues/99#issuecomment-266705031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWXU7dcYYk9OSbAlK7_ZkL-t_di0weSks5rHnXsgaJpZM4KIft8
.

I have 0.1 sec/step is that good?

yeah thats pretty good, i'm averaging 0.8 sec/step on a v100 using a custom dataset


Connection Request failed

Every time I'm running Provision or Readall commands for unit ACS propose to reboot device to initiate provisioning. I suppose it is related with following message:
"Kick failed at 10:32:39 - require reboot to initiate provisioning :: Neither a public ConnectionRequestURL nor any UDPConnectionRequestAddress was found"
Although "IGD.ManagementServer.ConnectionRequestURL" is provisioned
Any CPE-initiated sessions are running ok, so I can check reading and provisioning by setting low periodicinforminterval value (set frequency >2000).

There are some difficulties regarding the use of stun service. Its not just plug and play. Network and firewalls must be open etc. But in your case maybe its regarding something much simpler. I can make a rough check on the implementation.

I'm testing in a local network. Stun should not be involved at all, althoug unit status shows NAT=true

not currently sure why but the code requires public ip address property aka System.X_FREEACS-COM.Device.PublicIPAddress. Its name has changed since i have removed old name references to old products. The ip address is used to replace the host of the connection request url. As a simple test can you try to set this, and then we can discuss what we need to change

hmm i am not sure if my advice is totally correct. But you can try. There is also a problem in the code where it checks if the connection request url is public. It can be toggled off, the public check i mean.

to disable public ip check set KICK_CHECK-PUBLIC-IP=false in etc default

the latter is the best option to test locally. But you could also use the public ip approach

I updated System.X_FREEACS-COM.Device.PublicIPAddress parameter with real CPE IP, but it doesn't impact result. From logs server still believes that IP is <IP_ADDRESS>.

KICK option in default also has no effect
and system public IP parameter is updating when try to ReadALL or Provision

if you can read the code, can you check if this test is reasonable?
https://github.com/freeacs/freeacs/pull/142/commits/c10eb269734252ced4f6595b06fa357641ffaa01#diff-cec36b535f75a4c4c5e16ffc5b0d222eR67

If the above test is reasonable it might be problems with dbi layer not syncing properly betwewn modules. But need to investigate if that is the case

Sorry, I hardly can understand this code

There exists a connection request url parameter.
Kick is initated with check public ip set to false.
Kick is successful.

But i will try to replicate this manually in the application too. Did you remember to restart stun service with systemctl restart freeacs-stun after changing etc default?

My fault. I didn't double-checked with you which module properties should include this option.
I added it to TR069 properties file. Is it wrong?
And afair I didn't restart stun, I just tried to stop it in the end of all my attempts

ok, stun is the thing about disabling public ip check :) try that and then restart.

nope. I tried to specify CPE IP as PublicIPAddress, tried empty, with both Public-IP-Check enabled and disabled.
And PublicIPAddress parameter is auto-updated to <IP_ADDRESS> after CPE comes to ACS by itself (with 2 PeriodicInform)

We will definitely found out whats wrong. It might take some time, since I am abroad atm. But I feel that we narrowed it down to such a level that I can try to test this by making a fake stun client server (connection url). This will enable me to see that if there is a defined unit with a connection request url defined, it can be kicked. The only difference is that i am not testing provisioning. But i am sure it will uncover the problem you are facing. However, it might take some time before i can do this.
Its great that you are testing therefore i appreciate your ongoing patience.

I got the same problem.  My CPE and FreeACS is in the same subnet not behind the NAT.  the System.Device.PublicIPAddress is the ip address of CPE exactly. But FreeACS still cannot init a provision to CPE actively. Should I do any thing more?

@ujeisharon can you provide logs for the kick you initated that didnt go through?

What below is tr069.log of mine after press "Provision".
2018-07-02 09:50:18.764 NOTICE wr850n                              Added/changed 644 unittype parameters
2018-07-02 09:50:18.818 WARN   wr850n                              GPVres contained error, try once more and ask for all parameters
2018-07-02 09:50:33.236 INFO   wr850n                              No job found (filter: Status/Type:0, )
2018-07-02 09:50:33.239 WARN   wr850n                              The parameter InternetGatewayDevice.DeviceInfo.VendorConfigFile. is defined in the database,but does not exist in the CPE. Delete it from the unittype or update the firmware! This situation will impact on the performance of the system.
2018-07-02 09:50:33.239 WARN   wr850n                              GPV has been issued twice, but apparantly the reason for the failure of the first GPV-response is not due to missing parameters in the CPE.
2018-07-02 09:50:33.239 NOTICE wr850n                              Sent to CPE: 1 parameters.
2018-07-02 09:50:34.000 NOTICE wr850n                              	InternetGatewayDevice.ManagementServer.PeriodicInformInterval : 82079
2018-07-02 09:50:34.001 NOTICE wr850n                              Added unit parameter InternetGatewayDevice.ManagementServer.PeriodicInformInterval with value 82079
2018-07-02 09:50:34.001 NOTICE wr850n                              Added unit parameter System.X_OWERA-COM.Device.PeriodicInterval with value 82079
2018-07-02 09:52:18.825 INFO    ActiveDeviceDetectionTask: Will check if some devices scheduled to return before Mon Jul 02 08:52:18 CST 2018 are too late
2018-07-02 09:52:18.825 INFO    ActiveDeviceDetectionTask: Have found 0 inactive devices
2018-07-02 09:57:18.825 INFO    ActiveDeviceDetectionTask: Will check if some devices scheduled to return before Mon Jul 02 08:57:18 CST 2018 are too late
2018-07-02 09:57:18.826 INFO    ActiveDeviceDetectionTask: Have found 0 inactive devices
2018-07-02 09:58:25.074 NOTICE  Send challenge to CPE, located on IP-address <IP_ADDRESS>
2018-07-02 09:58:25.092 NOTICE wr850n                              Authentication verified (CPE IP address: <IP_ADDRESS>)
2018-07-02 09:58:25.437 INFO   wr850n                              Periodic Inform recorded too early (-81580 sec). Deviation: -99 %
2018-07-02 09:58:25.439 INFO   wr850n                              EM-Decision is GPV since everything is normal and previous method was either IN or TC (updating LCT and possibly FCT)
2018-07-02 09:58:25.779 WARN   wr850n                              GPVres contained error, try once more and ask for all parameters

clean the fusion-tr069.log  and  re-press the privision on webUI, but no logs append to the fusion-tr069.log file. Did I check the wrong file? I 've checked the ConnectionRequestURL has been seen from Current value. Should I edit extra profile config for provisioning from ACS ? Thanks.

I have done some changes to how this works. Please set ConnectionRequestUsermame and ConnectionRequestPassword and PublicPort to port defined in cpe and PublicProtocol to https/http. It will then dynamically try to create kick url based on PublicIp if Connectionrequesturl is not present as an parameter on the unit.

If all units use the same public port for connection request url you can set PublicPort and PublicProtocol in profile.

But wait. I havent updated release yet. So it only works in docker atm. I think I'll just release 2.0.0 today. I have fixed many issues the last months and i feel it's ready for primetime . Ill add a messages here when New release is ready.

Is the fix you made released yet?

Currently there is v2.0.0 out. But i dont have any documentation for the New kick functionality. I have a couple of commits since last version so I'll make a minor release for it and inform you here when it's done.

I have now released a minor release candidate. Mostly minor fixes. But at least there is a current release reflecting the contents of the master branch.

I have been testing kicking unit a lot over the last couple of releases. So it works now. Not sure however how good local software units work. I use an actual cpe to test with. I  would like some feedback on this, and would like you test latest version 2.0.3, but best option is to close this issue and have you comment it or reopen if stil an issue


Bugfix-SPL-object-hash-table

Using the SPL object hash to uniquely identify objects isn't safe, PHP reuses SPL object hashes.
Trimmed trailing whitespace

I've shashed commits and made some changes in the code. The merged commit is: https://github.com/psliwa/PHPPdf/commit/ca8c370c4b21f9fc00b2599d278b4c6db304fa8e. Thanks.


Clarification on Sleuth and Feign with Hystrix

Does Sleuth support Feign with Hystrix? I've read some conflicting information, and just wanted to find a concise answer.
At the moment I'm having to disable it with the following, otherwise I get an error in the Feign call.
feign:
    hystrix:
        enabled: false

Yes we do support Feign with Hystrix. http://cloud.spring.io/spring-cloud-sleuth/spring-cloud-sleuth.html#_hystrix

How come I get an exception then? My feign interfaces are basic and don't have any hystrix annotations or objects in their specification.

@nickcodefresh it would be most helpful if you told us what exception you get.

Yes sorry, I wasn't at my computer. My bad. I'll upload one tomorrow
On Wed, 6 Apr 2016 20:34 Spencer Gibb<EMAIL_ADDRESS>wrote:

@nickcodefresh https://github.com/nickcodefresh it would be most
helpful if you told us what exception you get.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/spring-cloud/spring-cloud-sleuth/issues/229#issuecomment-206525275


Phinch visualization in "16S Microbial Analysis with mothur" tutorial

Dear all
I have problem with the visualization the  composition of microbial community with Phinch, the output of the tool "Make.biom" as shown below

I tried many times to repeat the step but the output failure, metadata file was downloaded again to the history to confirm there is no problem with earlier downloading, however the result is the same

thank you in advance

Dear @Jalalalzanin thank you for reporting this issue. Can you look at the standard error message if available, from an error dataset and/or can you maybe share your history so we can investigate in details?
Thank you

Dear yvanlebras thank you for response
no error not message
https://usegalaxy.eu/u/jalal_alznin85/h/16s-microbial-analysis-with-mothur-extended

Dear yvanlebras thank you for response
no error message wad detected
https://usegalaxy.eu/u/jalal_alznin85/h/16s-microbial-analysis-with-mothur-extended

Dear yvanlebras thank you for response
no error message was detected
https://usegalaxy.eu/u/jalal_alznin85/h/16s-microbial-analysis-with-mothur-extended

Thank you. I can't look at the datasets as I think you have to unshared the history then reshare it specifying you want to share also all elements of the history (checking the corresponding box). Can you try and re paste here the link if the history (will normally be the same but just to be sure)

that's clear @yvanlebras
https://usegalaxy.eu/u/jalal_alznin85/h/16s-microbial-analysis-with-mothur-extended
thank you

Ok, will look at it ASAP. ITM, here you can't have access to stderr because you "only" have a data collection as output, but if you check the box ~"output log file: yes" so you can then look at the error on the failed output log file through the "bug" button

The error message is not interesting here unfortunately. But looking at the standard output, here is a message who can help:
'ERROR]: can't find metadata information for F3D0_, quitting.'
But not sure I submit the same job... But trying without metadata file as input seem ok. When specifying the metadata file I have this aforementioned message.
Here are my rapid tests: https://usegalaxy.eu/u/ylebras/h/imported-16s-microbial-analysis-with-mothur-extended

Thank you @yvanlebras
That's correct I tried without metadata file.

and here the result with Phinch

Yes, but After that, if you select "taxonomy bar chart" phinch say that the metadata file is required :( so you have to look into details to find the error with the metadata file and maybe more with the filtered otu input file...

that's right @yvanlebras
I will check the metadata file and repeat this step
I appreciate you help


Typing "." causes quicksilver to crash every time

As the title says, typing a period always causes the app to crash.
Quicksilver 1.3.2
Mac OS X El Capitan 10.11.1

Please see #2111


feat(Alerts): AlertArea + FadeInStacked

Overview

AlertArea + FadeInStacked - migrated from Aaron's original PR

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.42-alpha.304a22.0@codecademy/gamut-labs@28.6.5-alpha.304a22.0@codecademy/gamut@43.1.1-alpha.304a22.0@codecademy/monaco@0.5.31-alpha.304a22.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61e1dc30a71e1e1ce773af21--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.42-alpha.8156ce.0@codecademy/gamut-labs@28.6.5-alpha.8156ce.0@codecademy/gamut@43.1.1-alpha.8156ce.0@codecademy/monaco@0.5.31-alpha.8156ce.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61e1e5af10fde3265ca705ad--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.44-alpha.8b16c5.0@codecademy/gamut-labs@28.7.1-alpha.8b16c5.0@codecademy/gamut@43.1.2-alpha.8b16c5.0@codecademy/monaco@0.5.32-alpha.8b16c5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61eb2fc99f289bb31304e93c--gamut-preview.netlify.appDeploy Logs


Count parameter error for blog / page

So i got everything installed, but i get an error when i click on specific posts or page.
count(): Parameter must be an array or an object that implements Countable (View: /home/vagrant/code/ozz/resources/views/application/article/index.blade.php)
ErrorException (E_ERROR)
count(): Parameter must be an array or an object that implements Countable (View: /home/vagrant/code/ozz/resources/views/application/page/index.blade.php)
I suppose it has to do with this.
PHP changed count() behavior?
https://wiki.php.net/rfc/counting_non_countables

As I have php 7.2 installed, i will get this error.
I have just removed the if count statement for now.
Maybe there is another work around to check the the pages/blog, which is suitable for 7.2.

That is not related with PHP 7.2, the variable is not countable when there are not any items there, so it's better to check with !empty instead of count, I updated the code.
Feel free to reopen another issue if something unexpected occurs again.


change uses of unique_ptr(new T) to absl::make_unique [phab:D1945]

Created by shahms at 2017-09-25 20:06:15:
change uses of unique_ptr(new T) to absl::make_unique

zarko wrote at 2017-09-25 20:08:09:
toot

zarko accepted this revision at 2017-09-25 20:08:09

shahms closed via commit 16345f5d94930ce979679b8959ed78cfd2ed7a17 at 2017-09-25 20:09:46


[Bug]: Inconsistent compile time behavior when deprecating record fields

Description
I need to deprecate a field in http:ListenerConfiguration.
public type ListenerConfiguration record {|
    # interceptors - An array of interceptor services
    # # Deprecated
    # Defining interceptor pipeline in `http:ListenerConfiguration` is deprecated. Define the interceptor pipeline
    # via `http:InterceptableService` service type
    @deprecated
    Interceptor|Interceptor[] interceptors?;
|};

This configuration is used in the http:Listener initialization as follows and accessed inside the init function.
public isolated function init(int port, *ListenerConfiguration config) returns ListenerError? {
   Interceptor|Interceptor[]? interceptors = config.interceptors;
}

Here, what we want is to show a deprecation notice to the users when the user tries to do the following.
http:Listener 'listener = check new (9090, interceptors = new RequestInterceptor());

This shows the deprecation warning when we build the http module (which is expected as we try to access the field). And when we build a user's module using the built http module, it doesnt show any warnings. Is this the expected behaviour? If so, how do we do something like that? (We had a case like this for http:ServiceConfig as well and used the compiler plugin to show a warning to the user.)
Apart from the above clarification question there's another weird behavior as well.
As mentioned, we get the compiler warning when building http module.
WARNING [ballerina/http/2.7.1::http_service_endpoint.bal:(55:55,55:74)] usage of construct 'ballerina/http:2.7.1:ListenerConfiguration.interceptors' is deprecated

Then we publish this module to local central and build a simple user's project.
Here also, we get the above warning. But this warning comes only when we do the project build for the first time. If we do a second bal build it is not present. To reproduce, we had to build, pack and push the module to the local central again.
Steps to Reproduce
Described above
Affected Version(s)
U5
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
https://github.com/ballerina-platform/ballerina-standard-library/issues/4300
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Apart from the above clarification question there's another weird behavior as well.
As mentioned, we get the compiler warning when building http module.
WARNING [ballerina/http/2.7.1::http_service_endpoint.bal:(55:55,55:74)] usage of construct 'ballerina/http:2.7.1:ListenerConfiguration.interceptors' is deprecated

Then we publish this module to local central and build a simple user's project. Here also, we get the above warning. But this warning comes only when we do the project build for the first time. If we do a second bal build it is not present. To reproduce, we had to build, pack and push the module to the local central again.

This is because the HTTP module is built only on the first compilation. From the second compilation onward, the cached BIR will be used since available.

Simplified sample
type Rec record {|
    @deprecated
    int[] x;
|};

public function main() {
    Rec r = {
        x: [] // no warning
    };
    r.x = []; // warning
    var x = r.x; // warning

    fn(x = []); // no warning
}

function fn(*Rec f) {
}

We don't seem to be logging warnings on initialization (extends to named args for fields of an included record param too).
The spec says warnings shouldn't be logged only when

a deprecated API element is used within another deprecated API element

We need to consider the following scenarios as well
type Rec record {
    @deprecated
    int[] x;
}

public function main() {
    // Scenario 1: variable reference for the field
    int[] x = [10];
    Rec t1 = {
             x
     };

    // Scenario 2: variable reference as a rest
    var val = { x : [1, 2]};
    Rec t2 = {
        ...val
    };
}

function test() {
    name([]);
}

function name(@deprecated int[] x) {
}

The above example also doesn't give any warnings for deprecated usage.

Have an Impact from https://github.com/ballerina-platform/ballerina-lang/issues/40902


User testing for Quantum 301

Now that the first page of Quantum 301 is nearing completion, we should do some user testing to validate the content and design

Yep! I think there are two potential audiences we can test with:

Students: we have many interns who we can test with, segmented by CS / Physics disciplines
Instructors: we have multiple internal instructors including @quantumjim and @amirhassank who can review this

I think we can do a phased approach. We could start by circulating the preview link internally with our own technical experts and just ask them for feedback (informally). We could use any insights from them (plus our own thoughts) to create a survey. Then, we could share the preview link and survey link with the Qiskit Advocates and the textbook-reading-group slack channel.
Neither of those slack channels specifically include students or professors, so it would be good to try to target them specifically too. But I think we can get a good set of feedback from the advocates and the reading group.

@JRussellHuffman @pandasa123 is this still going on or should we close this issue?


perf!: call executePackageManagerRequest directly

Opening as a draft for now.
Ref https://github.com/nodejs/corepack/pull/425#issuecomment-2000189938
Depends on https://github.com/nodejs/corepack/pull/428

Didn't notice it was targetting my fork.


Support container/infra/cloud provider policies in the UI

Enable provider policies definitions.
Control panel ( added option for providers policies )

Control panel Add Policy

Providers panel ( added policies actions )

@cben @simon3z @enoodle please have a look.

@miq-bot remove_label wip

depends on: https://github.com/ManageIQ/manageiq/pull/11369

@Fryguy Looks OK now?

@zeari @cben please go over.

LGTM but im no policy expert in this project.

LGTM :+1: cc @chessbyte
@miq-bot assign Fryguy

@miq-bot add_label euwe/yes

Pushing this over to UI team, as the model code has all been removed.

@dclarizio #11369 was merged, could you please review?

@dclarizio according to talk, images added and changed title.

@alongoldboim

@dclarizio #11369 was merged, could you please review?

Is this the wrong PR? It doesn't seem to have anything to do with policies.  Is there another PR with back end code to actually use these policies?
This PR is for Container Provider policies, but the screen shots just show Provider policies.  I'm worried users might think they are creating policies for all providers, but we have no support for anything but container providers. @Loicavenel are we planning to add other providers support or should we name this such that it only pertains to container providers?
I see no tests . . . @h-kataria can you review the code and also suggest some tests that could be added?
When I run this branch, I get a postgresql error on user.region.  Please rebase so we can run the branch.
Thx, Dan

@dclarizio yes, I did confirm with @alongoldboim this will work for all provider which is fine.

@dclarizio This pr support policies for infra/cloud/container, the backend functionality is supported by including the mixins.

@alongoldboim can you add some spec tests around new toolbar buttons and also around new method in controller to verify that task was queued up and correct flash message was set to be display when Compliance check button was pressed, update existing routing specs to add newly added routes in this PR.

@dclarizio @h-kataria Added tests, anything else? :)

@alongoldboim can you please address:
https://github.com/ManageIQ/manageiq/pull/11002#discussion_r86191637
https://github.com/ManageIQ/manageiq/pull/11002#discussion_r86367897
https://github.com/ManageIQ/manageiq/pull/11002/files#r86375467

@h-kataria any idea why the tests are failing?

@h-kataria tests are passing, anything else is missing? :)

@h-kataria fixed.

looks good now.

@alongoldboim compliance events need icons:

@alongoldboim is there a BZ for this?

Alon left the team.  The feature was motivated by "CM-Ops" effort, probably doesn't have a BZ.  @simon3z?
The missing icons I mention above also don't have BZ.  And while I look at it, shouldn't say "ExtManagementSystem".  => ManageIQ/manageiq-ui-classic#94, ManageIQ/manageiq#13388.

Created BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1411337

Euwe backport details:
$ git log -1
commit 11bace9720205ed40505c9c4c510259bf1534fc4
Author: Harpreet Kataria<EMAIL_ADDRESS>Date:   Tue Nov 22 12:15:50 2016 -0500

    Merge pull request #11002 from alongoldboim/enable_proider_policies

    Support container/infra/cloud provider policies in the UI
    (cherry picked from commit<PHONE_NUMBER>856b340a5628e4fade95b1848e77f6)

    https://bugzilla.redhat.com/show_bug.cgi?id=1411364


Error at the image_window() overlay

Traceback (most recent call last):
File "face-rec.py", line 58, in
win.add_overlay(shape)
RuntimeError:
Error detected at line 25.
Error detected in file C:\bld\dlib_1504193025992\work\dlib-19.4\dlib..\dlib/image_processing/render_face_detections.h.
Error detected in function class std::vector<struct dlib::image_display::overlay_line,class std::allocator > __cdecl dlib::render_face_detections(const class std::vector<class dlib::full_object_detection,class std::allocator > &,const struct dlib::rgb_pixel).
Failing expression was dets[i].num_parts() == 68.
std::vector<image_window::overlay_line> render_face_detections()
Invalid inputs were given to this function.
dets[0].num_parts():  5

Read the error message.  You can't call that function with a 5 part annotation.


Configfile & Websocket

i really dont understand the "Wiki"! What is the right config file? And where i get this websocket url and port?

if you don't change anything the default will work.
wss://[computer]:[port]
computer is the name or ip the your computer (localhost for current pc), port is the port you defined in the bot config file.

I opened "config" and put "wss://IPOFMYCOMPUTER:14251" and pressed "save" - nothing happens and if i open "index" the bot just wait for GPS coordinates.

Which bot are you using ? necro or mobbot ?
Which version ? Compiled or from the source ?
(not if the bot and the UI are on the same computer you can just leave default settings)

Necrobot - Newest Version (0.5.0?)
Compiled
Bot and UI is both using with my Laptop

does it work better with all new release?

Yes!!! Works like a charm! Thanks!!!!


Distribute/publish app to Apple TestFlight

How can I use the CLI to push new native builds to TestFlight? It is available through the AppCenter website but I don't see an equivalent CLI target.
This is desirable so that we can perform publishing through our automated build process.

This has been implemented in #647, #656 and #657. We will publish a release shortly.

To answer to this question specifically, TestFlight is a just track of the Apple App Store, so you simply would need to publish to the store using the correct track name (eg. "App Store Connect").


xSQLServer: All tests should load the stubs without using ''

Details of the scenario you try and problem that is occurring:
This is an issue is a reminder that we should fix so that all tests load stubs using this or something similar:
Add-Type -Path (Join-Path -Path (Join-Path -Path (Join-Path -Path (Join-Path -Path $script:moduleRoot -ChildPath 'Tests') -ChildPath 'Unit') -ChildPath 'Stubs') -ChildPath 'SMO.cs')

The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

This should also be added to the specific contribution guidelines.


Fix for objects not bound when their handle is added in detached container

Fixes https://github.com/microsoft/FluidFramework/issues/9127.
Note: This change isn't backwards compatible right now as it is pretty complicated to do so. I would like to get some feedback if the PR is in right direction before working on compatibility.
This PR does the following:

In data store runtime, it combines bind state and graph attach state into one state - localAttachState. Also, combines attachGraph and bindToContext into a single method.
In data store runtime, there are two states currently tracked - localAttachState and globalAttachState (or just attachState). localAttachState tracks whether the data store is visible locally in the container via root. globalAttachState tracks whether the data store is visible globally to other clients in the document.
When data store runtime is created, if it an existing on, its localAttachState is set to Attached. This fixes https://github.com/microsoft/FluidFramework/issues/7927.
When a data store's handle is added to a DDS, if the DDS is locally attached, the data store is also locally attached by called attachGraph on the data store's handle. Note that the DDS's local attach state is tracked in its handle (FluidIObjectHandle class).

Closed in favor of https://github.com/microsoft/FluidFramework/pull/9548 which is backwards and forwards compatible.


Pod status not reported promptly in integration test (potentially due to watch delay)

Probably not the same as #6261?
 It is probably the same as # #6261.

I thought they might be different because this one has a bunch of "failed creating ... already exists" messages in it, but #6261 doesn't.

It is essentially the same problem -- the watch was delayed so kubelet kept seeing the old snapshot of the pods where the mirror didn't exist.  That's why it's flaky and only happens on shippable (which I suspect has poorer performance) :(
This becomes worse every time a new test is added. I think we need to limit the number of concurrent tests in integration.go
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cmd/integration/integration.go#L981

#6655 limits the number of concurrent tests on travis/shippable to 4. Let's see if this helps reduce the timeout flakes.

Another example: https://app.shippable.com/builds/55275c45aa50c00b001ed2d9

Here is yet another example: https://app.shippable.com/builds/5528571f892aba0c00bd674c
Retitled the issue since limiting the concurrent tests doesn't work. It could be that the server is heavily loaded and the test timed out, or there was a delay/drop in kubelet's pod watch stream.

Now example: https://app.shippable.com/builds/552c02f56206490c0097314d

If, for whatever reason, a watch update for pod creation is dropped, kubelet would need to wait until re-listing to notice that. This would certainly cause the test to time out. @lavalamp, would it be useful to shorten the re-listing interval for tests like this?

I am not quite sure how this works--let's chat about it tomorrow?

From this failulre, we can see that kubelet was lightly loaded as the update channel was mostly empty while waiting.
I0416 20:47:36.975546    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:37.976479    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:38.977073    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:39.978154    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:40.111029    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:40.978537    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:41.978930    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:42.724643    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:42.979593    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:43.980301    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:44.981798    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:45.982255    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
I0416 20:47:46.982765    2903 config.go:186] 0/50 updates in the channel; merge finished in 0.00 seconds.
F0416 20:47:47.207091    2903 integration.go:914] FAILED: pod never started running timed out waiting for the condition

This corroborates the theory that watch might be at fault.

cc: quinton-hoole

The WIP reflector benchmark (#6697) may shed some light on this issue once it's integrated with the continuous e2e performance suite.
I will keep this issue open for now to gather more data (since this is not reproducible locally at all), and to see if there are other potential causes.

The PR above disables the static pod test temporarily so that we can track down the root cause without spamming people with the failures. Note that other tests in the same file (integration.go) may still trigger the flaky failure, though less frequently.

@yujuhong Can this be closed yet?

@yujuhong Can this be closed yet?

No, integration test is still flaky. See https://app.shippable.com/builds/5582458f3d07800f00077736 for example.
Many tests in cmd/intergration/intergration.go rely on checking the pod status with a preset timeout. I disabled one test which failed most often, but other tests still fail from time to time.

The issue has been inactive for months, and there have not been any new reports. Closing.


[Lecture10][0507] Small error in the lecture slide

I found a really minor error in the lecture slide p25 & p32.

As you can see, PReLU is incorrectly written as 'max(0, x)'.
I think it can be revised as
'max(x, αx) for α ∈ (0,1)'.
Thank you.
Jaeyung Kim

@goals4292  Oh, Thank you for the comment:) I will correct the typo in the final version


[Forge 1.16.5] Compatability with Serene Seasons

This message relates to #6 because the coloring issue with Serene Seasons may have returned. The first screenshot is with BBB and the second is without BBB. For some reason, Serene Seasons is not applying its seasonal changes with BBB installed. This was reproduced on a minimal mod list: LazyDFU to speed loading, Optifine G8, BBB, and Serene Seasons.
EDIT: I just did some more testing, and it would appear that while BBB is installed, the textures will not change immediately when a season changes. Instead, you have to leave the world and then rejoin for the full changes to take effect. This is not necessary when BBB is absent.
Forge version: 36.2.0
Serene Seasons version: 1.16.5-<IP_ADDRESS>-universal
Better Biome Blend version: 1.16.4-1.2.3-forge

Ah yes you see I'm actually not smart

I caused this in the recent updates. Thank you for reporting. I'll be releasing a fix shortly. Until then use the 1.1.x versions. They should be fine.

1.2.4 fixes the issue. Thank you for doing additional testing, that made it very easy for me to know what went wrong.


Error in order of column names in declaration of foreign key

Click on a table name in Database navigator
Open tab "Properties"
Click "DDL" button"
If table contain a foreign key with 2 or more columns then these columns may be have different order in declaration part and in reference part:
For example:
...
CONSTRAINT FK__XXXXXX__176F17C2 FOREIGN KEY (COL1,COL2) REFERENCES YYYYY_OTHER_TABLE(COL2,COL1),
...

DBMS: Microsoft SQL Server 2017 (RTM-CU19) (KB4535007) - 14.0.3281.6 (X64)
Jan 23 2020 21:00:04
Copyright (C) 2017 Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Standard 10.0  (Build 17763: )
DBeaver version: <IP_ADDRESS>003211804

thanks for the bug report

Can't reproduce. We use ORDER BY constraint_object_id, constraint_column_id when querying foreign_key_columns.
Could you post table DDL which will let to reproduce the issue?


sorting code/algorithms to sorting_searching

Hey guys I noticed that there are only a few sorting algorithms on the archive.
I think we should add these:
merge sort
insertion sort
quick sort
breadth-first search
depth-first search
etc.
especially because most classes first teach algorithms using sorting algorithms.

A lot of people have suggested these, but we have been avoiding them thus far specifically because they are covered well in other places.
There are a few PRs up for a few chapters for these methods, so we'll see how them go.
Thanks for the suggestion!

no problem man, I get it. Are you saying you still allow pull request for things like that or that you're moving away from that kind of stuff at the moment

this is an implementation of selection sort by reference in c++:
void selectionSort(vector &v) {
if (!v.empty()) {
size_t indexMin;
for (size_t i = 0; i < v.size() - 1; ++i) {
indexMin = i;
for (size_t j = i + 1; j < v.size(); ++j) {
if (v.at(j) < v.at(indexMin)) indexMin = j;
}
swap(v.at(i), v.at(indexMin));
}
}
}

Hi, thank you for your interest for improving the AAA.
However, in effect, your code is unusable for us. In the future, if you want to contribute code, please open a pull request and follow the instructions laid out in the wiki (https://github.com/algorithm-archivists/algorithm-archive/wiki/How-to-Contribute)
We are trying to add better and more extensive explaining chapters to the sorting, so we decided to remove the sorting chapters from the AAA for now, with the plan to re-add them later, better than they used to be.
I hope to see you contribute further to the AAA if you will.


Fix bug where user can't type disabled option into combobox

Pull Request
🤨 Rationale
Fixes #2252
👩💻 Implementation
The options getter should not revert to returning all the options (i.e. _options) when filteredOptions is empty. Doing so can lead to setting a selectedIndex that points to an option that is filtered out or disabled.
🧪 Testing
Added new tests
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@atmgrifter00 it looks like there were changes since your last review, could you give it another check JIC?


⚠ Fetchers has degraded performance

In 22fea71, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 102 ms

Resolved: Fetchers performance has improved in 540e134.


Failed to resolve assembly: 'CarouselViewControl.FormsPlugin.Abstractions, Culture=neutral, PublicKeyToken=null'

Hi, lastest stable version of Xamarin Studio, Xf version <IP_ADDRESS>, I can't use CarouselViewControl in xaml page, I get
Failed to resolve assembly: 'CarouselViewControl.FormsPlugin.Abstractions, Culture=neutral, PublicKeyToken=null'
(if I use compiled xaml)
or
Could not load file or assembly 'CarouselViewControl.FormsPlugin.Abstractions' or one of its dependencies
(at runtime)
Bye,
Dottor Pagliaccius

Android or iOS?

pardon, iOS

Did you update to latest Xamarin.iOS?

Of course, all components are up to date, stable channel. The issue happens when compiling the PCL project only (if I use compiled xaml)

The issue must be on your end because i can compile and run the demo with latest Xamarin update and latest XCode. There's a confirmed bug on Xamarin.Android 7, you must downgrade to previous version.

By the way, i add [assembly: XamlCompilation (XamlCompilationOptions.Compile)] at Application level and not in the page.

How did you resolve this? I'm on the latest version of Xamarin.Forms (<IP_ADDRESS>) and CarouselViewControl version 2.3.0. I get the same error. Also Xaml Compilation is turned on.

I've resolved using a CarouselPage :/

Found the issue. The used namespace in the ReadMe is wrong. It shoud be xmlns:controls="clr-namespace:CarouselView.FormsPlugin.Abstractions;assembly=CarouselView.FormsPlugin.Abstractions" instead of xmlns:controls="clr-namespace:CarouselViewControl.FormsPlugin.Abstractions;assembly=CarouselViewControl.FormsPlugin.Abstractions"

Good to know (for the next time ;))

Let me fix the readme.

If my work is helping you, please help me back: https://xamarinhq.wufoo.com/forms/nominate-a-xamarin-mvp/

This is what i have done that is community visible:

Alex has been pretty active sharing his knowledge and answering questions in StackOverflow, GitHub and Xamarin Forums.
Alex has been open sourcing Xamarin components and plugin with the community, with more of 10 repositories being maintained on GitHub.
One of Alex's Xamarin.Forms plugin, the CarouselView, is currently being pulled into the Xamarin.Forms core (xamarin/Xamarin.Forms#853). As an stable widget, this control has become the standard for Xamarin.Forms carousel screens with more that 16K downloads in NuGet and more than 100 solved and not open issues.
Another Alex's plugin, the SegmentedControl (https://github.com/alexrainman/SegmentedControl), is a big candidate to be also pulled into Xamarin.Forms core.
Plus Xamarin.Forms UI related plugins, Alex shares plugins to set app icon Badge, Google Analytics and KeyChain access.
Alex shares his knowledge about cutting edge technologies like Couchbase NoSQL and MobileIron integration with Xamarin Apps.


Change color button from grey to blue

In the settings, remove an account, I would suggest changing the colour of the buttons. Make the "cancel" button blue, and the "confirm" button grey. Thus, the focus shifts from deleting an account to cancelling.

What do you think @onvisions ?

I think otherwise. Buttons should be consistent everywhere.
If some change is needed I would vouch for lower opacity on the confirm button rather than switching colors.

Ok. This is just my suggestion. Service providers always make a focus on desired user actions.

@onvisions what do you think?

@mradkov is right that we should keep the colors consistent.
We can solve this issue that @Liubov-crypto raised with some better approach and a little bit more efforts.
I suggest the following:

add link to text "backed up your seed phrase" (green, underlined) leading to Backup functionality;
make the button Confirm disabled by default (40% opacity, cursor is arrow) and add a checkbox between the text and the buttons with the following text:

I understand that this is a cryptocurrency wallet and I am responsible for backing up my account recovery seed phrase.
When checkbox is checked the disabled Confirm button gets enabled.
What do you think @mradkov and @Liubov-crypto ? I can make design for this if needed although we have already the same checkbox here:

I agree with the initial proposal, it is easy to implement and it looks consistent with user experience in other apps. For example, here is a remove dialog from macOS:

I don't know if it makes sense to send the user to the seed phrase after he/she presses the confirm button (delete account) and then back. Since the warning about deleting the account and backing up the seed phrase is already on the remove account page. But since I am not a designer, I will trust your decision @onvisions

Something more on the topic to support my reasoning:
https://uxmovement.com/buttons/why-cancel-buttons-should-never-have-a-color/

Let's make this dialog according to it:
https://uxmovement.com/buttons/how-to-design-destructive-actions-that-prevent-data-loss/

The old design. Can be closed.