Improve error when native helper gives empty output

If native helper output is empty, an empty string is unparseable JSON and we end up getting an error about that, but no information about the underlying culprit.
In this case, show the native error output, which is likely to contain something useful.
Before
Dependabot::Bundler::UpdateChecker::VersionResolver#latest_resolvable_version_details with a gemspec and a Gemfile with an upper bound that is lower than the current req
Failure/Error: raise Dependabot::DependencyFileNotEvaluatable, msg

Dependabot::DependencyFileNotEvaluatable:
  Error evaluating your dependency files:
# ./lib/dependabot/bundler/update_checker/shared_bundler_helpers.rb:82:in `handle_bundler_errors'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:119:in `rescue in fetch_latest_resolvable_version_details'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:75:in `fetch_latest_resolvable_version_details'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:44:in `latest_resolvable_version_details'
# ./spec/dependabot/bundler/update_checker/version_resolver_spec.rb:52:in `block (3 levels) in <top (required)>'
# ./spec/dependabot/bundler/update_checker/version_resolver_spec.rb:414:in `block (5 levels) in <top (required)>'
# ./spec/spec_helper.rb:50:in `block (2 levels) in <top (required)>'
# /home/dependabot/common/spec/spec_helper.rb:63:in `block (2 levels) in <top (required)>'
# ./.bundle/ruby/3.1.0/gems/webmock-3.18.1/lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# JSON::ParserError:
#   unexpected token at ''
#   ./.bundle/ruby/3.1.0/gems/json-2.6.3/lib/json/common.rb:216:in `parse'

After
Dependabot::Bundler::UpdateChecker::VersionResolver#latest_resolvable_version_details with a gemspec and a Gemfile with an upper bound that is lower than the current req
Failure/Error: raise Dependabot::DependencyFileNotEvaluatable, msg

Dependabot::DependencyFileNotEvaluatable:
  Error evaluating your dependency files: No output from command. Error from command: /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/definition.rb:432:in `validate_ruby!': Your Ruby version is 3.1.3, but your Gemfile specified 2.4.10 (Bundler::RubyVersionMismatch)
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/definition.rb:407:in `validate_runtime!'
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler.rb:155:in `setup'
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/setup.rb:20:in `block in <top (required)>'
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/ui/shell.rb:136:in `with_level'
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/ui/shell.rb:88:in `silence'
  	from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/lib/bundler/setup.rb:20:in `<top (required)>'
  	from <internal:/usr/local/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
  	from <internal:/usr/local/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
  	from /opt/bundler/v2/run.rb:4:in `<main>'
# ./lib/dependabot/bundler/update_checker/shared_bundler_helpers.rb:82:in `handle_bundler_errors'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:119:in `rescue in fetch_latest_resolvable_version_details'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:75:in `fetch_latest_resolvable_version_details'
# ./lib/dependabot/bundler/update_checker/version_resolver.rb:44:in `latest_resolvable_version_details'
# ./spec/dependabot/bundler/update_checker/version_resolver_spec.rb:52:in `block (3 levels) in <top (required)>'
# ./spec/dependabot/bundler/update_checker/version_resolver_spec.rb:414:in `block (5 levels) in <top (required)>'
# ./spec/spec_helper.rb:50:in `block (2 levels) in <top (required)>'
# /home/dependabot/common/spec/spec_helper.rb:63:in `block (2 levels) in <top (required)>'
# ./.bundle/ruby/3.1.0/gems/webmock-3.18.1/lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# JSON::ParserError:
#   unexpected token at ''
#   ./.bundle/ruby/3.1.0/gems/json-2.6.3/lib/json/common.rb:216:in `parse'

So this would be super useful, I was literally debugging an error like this just last night.
However, is there a security risk here? Historically I thought we intentionally suppressed stderr output from the native helpers in prod because we don't control what they might output, and it could potentially include secrets.

Fair concern.
In my opinion, if a package manager is including secrets in its error output, that'd be a bug in the package manager (at least that's how Bundler & RubyGems treat it).
If this is a concern though, we should review the whole codebase, because we're already including error output in other places. For example, whenever stderr_to_stdout is fed to this method.

Sorry for long comment and I know this has been in work in progress for a while, but I think it is worth revisiting.  I was run down a rabbit hole tonight trying to figure out what exactly what was happening and causing the JSON parser error.  I had to dig into the dependabot-core source code to figure out what was happening.  Not intuitive or user friendly.
If an error happens in the native subprocess helper, a more meaningful message can and should be raised with a valid error class associated with it.
The proposed solution in this PR:
raise HelperSubprocessFailed.new(
        message: stdout.empty? ? "No output from command. Error from command: #{stderr}" : stdout,
        error_class: "JSON::ParserError",
        error_context: error_context
      )

Is still problematic because the error class of JSON::ParserError in the resulting output message.  The parser was not an error, it wasn't the cause of the issue, heck it had nothing to do with the issue, it was a red herring, because it was passed an empty string, which can and should be checked.
I propose if stdout is empty or has a Json parse error, then process stderr and raise with a different error class.  If worried about if the message has secrets, then the message could be as simple as a base message of "Error while running #{command}".
We can mimic what is currently being done in the main branch for out of memory errors.  If we attempt to detect some of the common ones, then we can append a much more meaningful message to the base message.
For instance, 'command not found', 'Versionmismatch', and any other potentially common ones. (obviously, this would require some trial and error to get a few of the common ones).  Below is untested, unlinted, non-ide written example of what I am trying to explain.
stdout = "#{stderr}\n#{stdout}" if stderr_to_stdout

     error_context = {
       command: command,
       function: function,
       args: args,
       time_taken: time_taken,
       stderr_output: stderr ? stderr[0..50_000] : "", # Truncate to ~100kb
       process_exit_value: process.to_s,
       process_termsig: process.termsig
     }

     check_out_of_memory_error(stderr, error_context)

     if stdout
       response = JSON.parse(stdout)
       return response["result"] if process.success?

       raise HelperSubprocessFailed.new(
         message: response["error"],
         error_class: response["error_class"],
         error_context: error_context,
         trace: response["trace"]
       )
     end
    raise_command_errors(stderr, error_context)
   rescue JSON::ParserError
     raise HelperSubprocessFailed.new(
       message: stdout || "No output from command",
       error_class: "JSON::ParserError",
       error_context: error_context
     )
   end

def self.raise_command_errors(stderr, error_context)
    base_error = "Error running #{errror_context['command']}"
    if stderr&.include?("command not found")
        error_msg = "#{base_error}: command not found"
        error_class = "Dependabot::CommandNotFound"

    elsif stderr&.include?("VersionMisMatch")
        error_msg = "#{base_error}: version mismatch"
        error_class = "Dependabot::Version Mismatch"
    else
        error_msg = "#{base_error}: unknown error"
        error_class = "Dependabot::UnknownError"
    end
    raise HelperSubprocessFailed.new(
       message: error_msg ,
       error_class: error_class ,
       error_context: error_context
     )
end

I get the idea and it makes sense. Rather than trying to parse empty output as JSON and rescue the parse error, we can detect the situation and raise something more explicit.
Even if privacy of error messages not under our control is still a concern, we can still raise a more accurate error class than JSON::ParseError in this case like Dependabot::UnknownSubprocessError, and not even try to parse the empty output.
Feel free to raise a PR for this, I'll close this one for now since the privacy bit is unclear right now.


Add support for full addresses to the temphs command

Tor's HiddenServicePort directive takes a remote port number and an address - an IP and a port number.  This can be used to create a service backed by a server not on localhost.  carml temphs seems to only accept remote port number and a port number on localhost.
Extend carml temphs so it can specify a non-localhost "local" address for the service.
I'd suggest something like carm temphs <remote port>[:<target address>]:<target port> (and perhaps allow multiple such positional arguments to set up multiple services.

Possibly this feature exists already but is not discoverable in the documentation.  Reading the implementation of the temphs command I found it uses the txtorcon API create_onion_service which in turn uses an internal API _validate_ports.  Reading that method's docstring suggests that a "port" like "remote a.b.c.d:local" might already work.  If so, this is really a documentation ticket, instead, to make this feature discoverable.

Okay, cool -- of note here, I've changed this to "carml onion" in the "post-python3" branch, which is probably the better place to fix/improve this (and yeah, no docs for it at all... :/ )
(carml will become python3-only after I merge the above; see also https://github.com/meejah/carml/pull/27)

This is in the latest release now.


Not all transactions and rewards displayed

Account :0x40a21738d8a48805d390ffa1473b5ec24236b4f1
App version: 0.0.7 (internal) os x.
Behavior: Smapp displays only 3 txs and no rewards. Balance doesn't correspond to txs history.
Expected: Display all account txs and rewards.
Notes:

Data via node API on same node used by smapp: 11 transactions and 4 rewards.
Tried setting layerNumber in wallet file to 0 for the txs

@IlyaVi - the transactions is a node issue but the rewards is not.

fixed as part pof #495
now app on start will retrieve all tx and rewards which happened while app was logged out/closed


Misleading statement in the README

The README states:

The two pipe proposals just differ slightly on what the “magic” is, and thus on precisely how you spell your code when using |>.

That statement ignores the fact that there is a lot of libraries that developed their own pipes despite the limitations of the language, with thousands developers using them already, that would greatly benefit from the minimal proposal, and would be thrown aboard with the Hack one. It seems quite important difference to me.

Thanks for the feedback. I don’t think there’s much actionable here for now, but here are my thoughts:
The primary benefit of any pipe operator would be being able to untangle deeply nested expressions like f(g(h(i(j(x))))) into linear, left-to-right flows of data.
Any existing library would get this untangling benefit from any of the pipe-operator proposals. All three pipe-operator proposals allow for this untangling of nested expressions. It’s just a matter of which gets to be slightly more concise: unary function calls or everything else.
Existing libraries that use pipe functions that compose unary functions would still benefit from Hack pipes (and F# pipes), just as existing libraries that use a lot of n-ary function calls would benefit from F# pipes (and Hack pipes).
With Hack pipes, unary function calls require adding on an explicit (%) or whatever. This is a very similar tradeoff that would be made by F# pipes with requiring adding x=> onto n-ary function calls, arithmetic expressions, yield expressions, and any other kind of non-unary-function expression.
I wouldn’t say that F# pipes throw libraries that use n-ary function calls, arithmetic expressions, yield expressions, etc. overboard, just as I wouldn’t say that Hack pipes throw libraries that use unary function calls overboard.
@TabAtkins originally wrote that statement you quoted, and I still find it true. Neither proposal throws any kind of expression overboard. It really is a small tradeoff in all cases, no matter the library.


Unify socket into file system to avoid the code duplication

Summary
Unify socket into file system to avoid the code duplication. #2833 this issue link associated with this patch.
Key modification points:

This patch refines the interaction between fs and net, we will address socket api by fs api, example:
fs:       ->          socket:
socket->...->psock_socket
close  ->...->psock_close
write   ->...->psock_send
read   ->...->psock_recv
ioctl    ->...->psock_ioctl
poll     ->...->psock_poll
dup    ->...->psock_dup2

this patch  deletes the wraper api net_xxx, eg:net_close，net_dup，and so on to avoid the code duplication.

This patch delete config CONFIG_NSOCKET_DESCRIPTORS and group.tg_socketlist.

Bind the socket to each file and set file->f_priv to socket.

Impact
Reduce duplication code and unified management of socket and fs.
Testing
daily test.

Should not this also be updated/removed:  https://github.com/patacongo/incubator-nuttx/blob/master/TODO#L1902

Should not this also be updated/removed: https://github.com/patacongo/incubator-nuttx/blob/master/TODO#L1902
Perhaps a better thing to do would be to convert all items in the TODO list to either issues or to Wiki pages???
There is also some crazy using pipes to account for the the fact that the stdin, stdout, stderr cannot be sockets in apps/netutils/thttpd. Should that also not be corrected?

Should not this also be updated/removed: https://github.com/patacongo/incubator-nuttx/blob/master/TODO#L1902
Perhaps a better thing to do would be to convert all items in the TODO list to either issues or to Wiki pages???
There is also some crazy using pipes to account for the the fact that the stdin, stdout, stderr cannot be sockets in apps/netutils/thttpd. Should that also not be corrected?

Okay, i have modified it, and modified nuttx/app in patch:https://github.com/apache/incubator-nuttx-apps/pull/601. Thanks~

Should not this also be updated/removed: https://github.com/patacongo/incubator-nuttx/blob/master/TODO#L1902
Perhaps a better thing to do would be to convert all items in the TODO list to either issues or to Wiki pages???
There is also some crazy using pipes to account for the the fact that the stdin, stdout, stderr cannot be sockets in apps/netutils/thttpd. Should that also not be corrected?

Okay, i have modified it, and modified nuttx/app in patch:apache/incubator-nuttx-apps#601. Thanks~

@Donny9 - Nice - how much smaller is this then master?

@Donny9 - Nice - how much smaller is this then master?

I use config stm32f4discovery:ipv6 to compare this change, and use bloaty tool to analyse.
nuttx$ bloaty -n 20 -d sections,symbols this_patch -- master
FILE SIZE        VM SIZE

+3.4%     +28  +3.6%     +28    .data
[NEW]     +24  [NEW]     +24    g_sock_inode
+100%      +2  +100%      +2    g_devno_sem
+100%      +2  +100%      +2    g_spawn_parmsem
-1.4%      -2  [ = ]       0    .shstrtab
-2.6%     -24  -2.7%     -24    .ARM.extab
-1.0%     -80  -1.0%     -80    .ARM.exidx
-0.5%    -154  [ = ]       0    .strtab
[NEW]     +21  [ = ]       0    g_last_tcp_port.5480
[NEW]     +21  [ = ]       0    g_last_udp_port.5260
[NEW]     +18  [ = ]       0    FUNCTION.5936
[NEW]     +18  [ = ]       0    FUNCTION.6321
[NEW]     +18  [ = ]       0    FUNCTION.6329
[NEW]     +18  [ = ]       0    FUNCTION.6337
[NEW]     +18  [ = ]       0    FUNCTION.6347
[NEW]     +18  [ = ]       0    notifier_key.6174
-43.2%     -16  [ = ]       0    g_icmpv6_connections
[DEL]     -16  [ = ]       0    net_releaselist
[DEL]     -18  [ = ]       0    FUNCTION.5971
[DEL]     -18  [ = ]       0    FUNCTION.6356
[DEL]     -18  [ = ]       0    FUNCTION.6364
[DEL]     -18  [ = ]       0    FUNCTION.6372
[DEL]     -18  [ = ]       0    FUNCTION.6382
[DEL]     -18  [ = ]       0    notifier_key.6209
[DEL]     -20  [ = ]       0    nxsched_get_sockets
[DEL]     -21  [ = ]       0    g_last_tcp_port.5512
[DEL]     -21  [ = ]       0    g_last_udp_port.5292
-7.7%     -33  [ = ]       0    [38 Others]
-0.8%     -69  [ = ]       0    [section .strtab]
-0.3%    -224  [ = ]       0    .symtab
[NEW]     +48  [ = ]       0    FUNCTION.5936
[NEW]     +48  [ = ]       0    buffer.5951
[NEW]     +48  [ = ]       0    g_sock_inode
[NEW]     +48  [ = ]       0    inited.5901
[NEW]     +32  [ = ]       0    FUNCTION.6321
[NEW]     +32  [ = ]       0    g_last_udp_port.5260
[NEW]     +32  [ = ]       0    g_sock_fileops
+40%     +32  [ = ]       0    icmpv6_input
[NEW]     +32  [ = ]       0    labels.6531
[DEL]     -32  [ = ]       0    FUNCTION.6356
[DEL]     -32  [ = ]       0    g_last_udp_port.5292
[DEL]     -32  [ = ]       0    labels.6566
[DEL]     -32  [ = ]       0    net_checksd
[DEL]     -32  [ = ]       0    net_close
[DEL]     -32  [ = ]       0    net_dup
[DEL]     -48  [ = ]       0    FUNCTION.5971
[DEL]     -48  [ = ]       0    buffer.5986
[DEL]     -48  [ = ]       0    inited.5936
[DEL]     -48  [ = ]       0    nxsched_get_sockets
-7.8%     -64  [ = ]       0    [47 Others]
-0.8%    -128  [ = ]       0    [section .symtab]
-0.4%    -504  -0.4%    -504    .text
[NEW]     +46  [NEW]     +46    sock_file_open
[NEW]     +44  [NEW]     +44    g_sock_fileops
+56%     +28   +56%     +28    nx_vfcntl
+1.9%     +24  +1.9%     +24    proc_read
[NEW]     +20  [NEW]     +20    sock_file_close
[NEW]     +20  [NEW]     +20    sock_file_read
[DEL]     -18  [DEL]     -18    net_dup
[DEL]     -22  [DEL]     -22    net_vfcntl
[DEL]     -22  [DEL]     -22    netdev_vioctl
[DEL]     -22  [DEL]     -22    poll_fdsetup
[DEL]     -26  [DEL]     -26    psock_release
[DEL]     -30  [DEL]     -30    net_checksd
[DEL]     -34  [DEL]     -34    net_releaselist
[DEL]     -38  [DEL]     -38    net_poll
[DEL]     -40  [DEL]     -40    sockfd_release
-0.6%     -42  -0.6%     -42    [section .text]
-25.0%     -46 -25.0%     -46    psock_vfcntl
-14.8%     -62 -14.8%     -62    nx_poll
[DEL]     -76  [DEL]     -76    net_dup2
[DEL]     -90  [DEL]     -90    psock_dup
-3.3%    -118  -3.3%    -118    [60 Others]
-0.4%    -960  -0.4%    -580    TOTAL
And this patch run in sim, memory usage:
this patch:
nsh> free
total       used       free    largest
Umem:     67108864     378080   66730784   66730304
master:
nsh> free
total       used       free    largest
Umem:     67108864     381568   66727296   66726816
reduce<PHONE_NUMBER>80)/1024=3.4kbytes

This patch pass our internal test, does anyone have more concern to address?

@Donny9 @xiaoxiang781216
Hmmm, it seems that the telnetd does not work after this change.
You can try lm3s6965-ek:discover with qemu.
nsh> renew eth0
nsh> ps
  PID PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK   STACK   USED  FILLED COMMAND
    0   0 FIFO     Kthread N-- Ready              00000000<PHONE_NUMBER>24 100.0%!
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

@xiaoxiang781216 @Donny9
I think we should revert this PR until the above issue is fixed.

We are looking the issue, please give us sometime to investigate. let's revert it if we can't fix it today.

lm3s6965-ek:discover

how to run lm3s6965-ek:discover on qemu? use command: qemu-system-arm -semihosting -M lm3s6965evb -device loader,file=nuttx.bin,addr=0x00000000 -netdev user,id=user0 -nographic -kernel nuttx ? I don't connect it with arm-none-eabi-gdb. please tell me the way. Thank you @masayuki2009

lm3s6965-ek:discover

how to run lm3s6965-ek:discover on qemu? use command: qemu-system-arm -semihosting -M lm3s6965evb -device loader,file=nuttx.bin,addr=0x00000000 -netdev user,id=user0 -nographic -kernel nuttx ? I don't connect it with arm-none-eabi-gdb. please tell me the way. Thank you @masayuki2009

@Donny9
$ qemu-system-arm -net nic,model=stellaris -net user,hostfwd=tcp:<IP_ADDRESS>:10023-<IP_ADDRESS>:23,hostfwd=tcp:<IP_ADDRESS>:10021-<IP_ADDRESS>:21 -M lm3s6965evb -kernel nuttx -nographic -s -S
$ arm-none-eabi-gdb-py -i=mi -ix=./tools/nuttx-gdbinit nuttx
(gdb) target extended-remote:1234

lm3s6965-ek:discover

how to run lm3s6965-ek:discover on qemu? use command: qemu-system-arm -semihosting -M lm3s6965evb -device loader,file=nuttx.bin,addr=0x00000000 -netdev user,id=user0 -nographic -kernel nuttx ? I don't connect it with arm-none-eabi-gdb. please tell me the way. Thank you @masayuki2009

@Donny9
Firstly, you need to add CONFIG_TIVA_WITH_QEMU=y
$ qemu-system-arm -net nic,model=stellaris -net user,hostfwd=tcp:<IP_ADDRESS>:10023-<IP_ADDRESS>:23,hostfwd=tcp:<IP_ADDRESS>:10021-<IP_ADDRESS>:21 -M lm3s6965evb -kernel nuttx -nographic -s -S
$ arm-none-eabi-gdb-py -i=mi -ix=./tools/nuttx-gdbinit nuttx
(gdb) target extended-remote:1234
$ telnet localhost 10023

hello, @masayuki2009, please try this patch #2978 thanks.


unconfigured table schema_keyspaces when cassandra is 3.3

Hi,
I am using Cassandra 3.3
When I try to do anything with the plugin e.g. createKeyspace I get:
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /<IP_ADDRESS>:9042 (com.datastax.driver.core.exceptions.InvalidQueryException: unconfigured table schema_keyspaces))
But not older version of Cassandra.
Is it related to to this?
Regards,
Masood

Yes, it seems you need PR #5. But I think we can merge and release soon. @MarcoPriebe WDYT?

I have just released version 2.0.0 where PR #5 is included.
BR,


intrusive_ptr bug fix

I realized that if intrusive_ptr<T>::reset(T*) is called with a pointer
to the same object it already refers to, it could be erroneously freed
because it was decrementing the existing refcnt before incrementing the
refcnt of the new value. So rewrote reset() to be safe under that
circumstance.

LGTM


Text style and icon in accordion item

Description
Page: Home
Two visual improvements:

The answer displayed in the accordion item looks too similar to the question. That's because of the styles of both texts. My suggestion is to apply a bold style for question text.
The arrow aligns on the right should be 20px size (1.25rem).
The same icon does not rotate when opening the question to see the answer. It should rotate in 180º to indicate the box expanded.

Screenshot

note: the green outline is visible when the user focuses with their keyboard (tabbing trough the accordions) but not when they click the accordions with the mouse cursor.

note: the green outline is visible when the user focuses with their keyboard (tabbing trough the accordions) but not when they click the accordions with the mouse cursor.


Nested dependency - how to with browserify?

I have a module that i use browserify -t sheetify app.js -o bundle.js .. however within app.js requires another module that requires sheetify transform. The nested dependency doesn't transform correctly as it doesn't inline the css.. How do i correctly do this? I'm guessing the dependency has to specify the transform within its package.json, is that correct?

yea, an npm package that uses sheetify should specify it as a transform in its package.json.
barring that you can try running sheetify globally using -g sheetify, or selectively on the dependency using tfilter:
browserify -g [ tfilter --include 'node_modules/depname/**/*.js' sheetify ]

That worked, thank you!


Add leeyspaul as Spanish reviewer for localization content

Per: https://groups.google.com/a/tensorflow.org/g/docs/c/jHIR1HbWXxE discussion on contributing to localization content in Spanish.

@googlebot I signed it!

ptal @lamberta :]. Please let me know if I need to do anything else, definitely interested in helping out with the project!

Closing per this discussion on REVIEWERS flow now being deprecated: https://groups.google.com/a/tensorflow.org/g/docs/c/G23C6ZxjiUI

(Sorry, I've been out of office)
Yes, this system has been deprecated but try using the GitLocaize project to review and submit pull requests: https://gitlocalize.com/tensorflow/docs-l10n
Thanks!

Perfect, I took a look and I'll try opening a PR there. I also opened up a discussion here: https://github.com/tensorflow/docs-l10n/discussions/442 on how to help out with reviews/being a moderator.
Thank you for the response. :]


Speed up windows CI/CD

Description
This PR contains several improvements to E2E tests for both linux and windows tests.

Rather than do a multistaged windows build from servercore and nanoserver, we'll use a prebuilt nanoserver image that already has the dependancies we need. This saves us 5-10 minutes.
Don't wait for container termination to start the next test. Container termination, in some cases, takes longer than the actual test. This saves us ~10 minutes
Run 2 test apps at a time. Since each test app is independent from all the others, we can run more that one without issue. This saves us ~10-20 minutes

These improvements gets the tests down to ~20 minutes for linux and ~30 minutes for windows. Since this is even better than our current test runtime (~30-40 minutes) we should be able to run both in parallel each time we do /ok-to-test
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1944
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-wintest

/ok-to-wintest

/ok-to-test

/ok-to-wintest

/ok-to-wintest

/ok-to-wintest

/ok-to-perf

/ok-to-test

/ok-to-test


UOM status reports incorrect action

Hi Jimbo,
The following is not very important as it is usually hidden from the user.  If it is easy to fix it will be shown correctly on the mobile apps.
The UOM status is reporting as 1 when set to Fahrenheit and should report as 2.
EDIT
Also, it is reporting a uom of 56, I think the numeric uom can be omitted as other nodes on the ISY which report UOM omit this.
END EDIT
From rest/config UOM, 1Celsius, 2Fahrenheit

Thanks Javi, I'll take a look

Thanks, also it looks like the uom should be set to "0"

@JavierRefuerzo Finally all NS's moved to PG3 and can start working on old problems
I'm not clear what needs to be done here?  I see rest/config has this.
<control ID="15">
<name>UOM</name>
Unit
<readOnly>true</readOnly>
<isQueryAble>true</isQueryAble>
<isNumeric>false</isNumeric>
<actions>
<action>
<name>1</name>
Celsius
</action>
<action>
<name>2</name>
Fahrenheit
</action>
</actions>
</control>

But I'm not sure what you are asking me to change?

Hi Jim,
It appears the profiles have changed since this report?  To be honest it was so long ago I only vaguely remember this issue.

what does UOM stand for?

Unit of measure.  There is one UOM to report value as Fahrenheit,  on e UOM tor report value as Celsius, and one UOM to report select temperature measurement (Fahrenheit or Celsius).


ConditionalObserverTest#testConditionalObserverMethodNotInvokedIfNoActiveContext

Hello,
I recently came across the test in title and I think that it has unfounded expectations.
Namely, the test does the following steps:

Create instance of a bean that holds observer method with reception IF_EXISTS
Manually deactivate context of the bean created in 1. (deactivate, not destroy)
Fire an event to verify that observer of the bean from step 1. isn't notified
Manually re-activate context of the bean from step 1.
Fire a new event and verify that the exact same bean instance from step 1. now got notified

Now, what I find dubious is the step 5. where the test assumes that after reactivating context, the very same bean instance is again present in that context, hence OM with IF_EXIST reception will go through.
Note that activation and deactivation of contexts happens through CDI TCK SPI Contexts. This doesn't have much documentation apart from its javadoc and a mention that it exists in TCK docs.
I couldn't find any part of spec that would support this test in terms of deactivation and subsequent activation implicating that the context state is renewed with the same set of contextual references.
Note 1: The specific part of spec that the test checks (denoted by @SpecAssertion on it) is checked by steps 1 to 4 so the test can be easily altered.
Note 2: Both, Weld and Arc (Quarkus) are able to pass this test, so this is nothing blocking, I am mostly curious whether I am missing something in the spec that would warrant this test.

We discussed this in the meeting today and here are some notable things:

The Contexts SPI is pretty underspecified in terms of not saying what should happen to the instances in context between deactivation and activation
This might be (to be verified) the only test that relies on reactivation and using the exact same instance
Same test would not work with RequestContextController as it explicitly stated that between activations, the instances will differ
On top of that RequestContextController can only deactivate a context it previously activated
The test can be "fixed" by calling tarantula.ping() before attempting to send the event after context reactivation as that will spawn new instance of the bean

Given the discussion we had back in the call, I went ahead and sent a PR that simply adds some javadoc to the SPI class making it clear the re-enablement requires restoring context state.
What I am not sure about is if we need to keep this as a challenge and if not then if we can still get it into next release?


Test and Game Improvements

Finished the basic logic of the game and added incomplete tests

Coverage decreased (-6.7%) to 44.444% when pulling 6fc78ea4962afe7fc58cb25819b69b1010043bb1 on test-improvements into 4fe1f1dca0b2172617935702350d0bce04001d16 on master.

Coverage decreased (-6.7%) to 44.444% when pulling 6fc78ea4962afe7fc58cb25819b69b1010043bb1 on test-improvements into 4fe1f1dca0b2172617935702350d0bce04001d16 on master.

Coverage decreased (-6.7%) to 44.444% when pulling 6fc78ea4962afe7fc58cb25819b69b1010043bb1 on test-improvements into 4fe1f1dca0b2172617935702350d0bce04001d16 on master.


bug: use_diagnostic_signs = true no longer works due to a recent Neovim change (0.10+)

Did you check docs and existing issues?

[X] I have read all the trouble.nvim docs
[X] I have searched the existing issues of trouble.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0-dev-1856+gf4f7e2946-dirty
Operating system/version
Gentoo Linux
Describe the bug
Due to a recent change in Neovim (https://github.com/neovim/neovim/pull/26193 I believe), diagnostics signs are now configured differently.
As a result, trouble displays "E" ; "W" ; "H" ; "I" letters instead of respective configured signs, despite using use_diagnostic_signs = true.
Steps To Reproduce

trouble config:

return {
  "folke/trouble.nvim",
  cmd = { "Trouble", "TroubleToggle" },
  dependencies = "nvim-tree/nvim-web-devicons",
  opts = {
    use_diagnostic_signs = true, -- Use the signs already defined in LSP
  },
}

neovim/nvim-lspconfig config:

return {
  "neovim/nvim-lspconfig",
  event = { "BufReadPre", "BufNewFile" },
  config = function()
    vim.diagnostic.config({
      signs = {
        text = {
          [vim.diagnostic.severity.ERROR] = " ",
          [vim.diagnostic.severity.WARN] = " ",
          [vim.diagnostic.severity.INFO] = " ",
          [vim.diagnostic.severity.HINT] = " ",
        },
      },
    })
  end,
}

Using Neovim nightly, trigger a diagnostic in any file
The diagnostic sign is correctly displayed in the SignColumn
Open trouble with :Trouble
The default letter is displayed in trouble instead of the configured sign:

Expected Behavior
trouble displays signs instead of letters
Repro
No response

Note that with https://github.com/neovim/neovim/pull/26618, https://github.com/neovim/neovim/pull/26193 is no longer a breaking change. Plugins should still migrate to the new configuration format, but there is no immediate need to do so.

I have a neovim config only using the new way to define diagnostic signs, so I decided to fix this by myself. You can see my pr above. Feel free to checkout and give your feedback.

Development on the main branch is EOL.
Trouble has been rewritten and will be merged in main soon.
This issue/feature either no longer exists or has been implemented on dev.
For more info, see https://github.com/folke/trouble.nvim/tree/dev

Dear @folke  is it possible that it is not yet enabled on dev branch? (I still see the E/W letters instead of icons).
Thanks

Trouble now always uses the configured Neovim diagnostic signs.

I configured neovim diagnostics, but somehow they are not picked up (just moved to dev today)

Did you use vim.diagnostic.config? And not sign_define? sign_define is deprecated

No, could find that in the dev docs.
Could you point me there?
In the lsp handlers I have
vim.diagnostic.config(lsp.diagnostic)

Can you show me the exact table you pass to diagnostics config?

Interestingly, everything works on
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1713773202,
but it fails on
NVIM v0.10.0-dev Build type: RelWithDebInfo, LuaJIT 2.1.0-beta3.
The table you asked for:
`local M = {}
function M.setup()
-- LSP handlers configuration
local lsp = {
float = {
focusable = true,
style = "minimal",
border = "rounded",
},
diagnostic = {
-- virtual_text = true,
virtual_text = { spacing = 4, prefix = "●" },
underline = true,
update_in_insert = false,
severity_sort = true,
float = {
focusable = true,
style = "minimal",
border = "rounded",
},
},
}
-- Diagnostic signs
local diagnostic_signs = {
{
name = "DiagnosticSignError",
text = ""
},
{
name = "DiagnosticSignWarn",
-- text = ""
text = ""
},
{
name = "DiagnosticSignHint",
text = ""
},
{
name = "DiagnosticSignInfo",
text = ""
},
}
for _, sign in ipairs(diagnostic_signs) do
vim.fn.sign_define(sign.name, { texthl = sign.name, text = sign.text, numhl = sign.name })
end
-- Diagnostic configuration
vim.diagnostic.config(lsp.diagnostic)
-- Hover configuration
vim.lsp.handlers["textDocument/hover"] = vim.lsp.with(vim.lsp.handlers.hover, lsp.float)
-- Signature help configuration
vim.lsp.handlers["textDocument/signatureHelp"] = vim.lsp.with(vim.lsp.handlers.signature_help, lsp.float)
end
return M
`

like I said, on 0.10, you need to pass signs as an option to vim.diagnostic.config. Please check the docs


As a beginner of the app, I should be able to access an in-app help sheet

...so that I can reference instructions quickly.

This Issue is related to #120 , where we are unable to implement WebView for the User Guide.
Hence, there won't be an in-app help sheet for Milestone v1.3.


Use PartialTypeSignatures to deal with the Tickish mess

Through clever use of PartialTypeSignatures, we can write some code
that will work with both the patched and unpatched GHC, rather than
having to explicitly discriminate.
I built the package with both our patched GHC and a vanilla 8.10.7 and it worked fine.
FYI @angerman @sevanspowell

This works, so I'm just going to go ahead and merge it.

Thanks @michaelpj :+1:

Elegante!


Have I Been Pwned (Independent Publisher) issue

Api Name - shared_haveibeenpwnedip
Bug description - The last update for the connector was 1/13/2022 and not all calls from v3 are supported.
See: https://haveibeenpwned.com/api/v3
I wanted to inquire if the publisher has any plans to update the connector before I attempt to recreate it using the v3 documentation.  Thanks.
Is this a security bug? - No
What is the severity of this bug? - Limited functionality

Hi Steven,
I am the publisher of the connector. I did not know there was a new API version, and I will work to update the connector.
Troy

Hi @troystaylor, I was just curious if you had an estimate on updating this connector?   No pressure, I just want to set a reasonable expectation for myself on when to check back.  Thanks.

@stevenmaske The update should be submitted in the next two weeks

@vmanoharas Please close this issue.

Sure @troystaylor


Personalize text per platform?

We´ve seen other apps that do sharing and personalize the text by platform (not necessarily they use branch).
I am aware that this is not possible in Titanium SDK.
My question is is it possible to do in native SDK?

On iOS specifically? Yes but it's a bit more complicated. You can basically subclass UIActivityItemProvider and check the channel prior to sending back the data.

Well, I was asking if Branch iOS SDK (on which Titanium SDK is based) is doing it or not...
I have read the theory, but I really hope that the client won´t make me recompile branch iOS SDK (even though the competing app does provide different texts for different providers)... or at least not now

Ah - yea.. we currently don't support it and don't have plans to add it soon. You could hack the iOS SDK and update the Titanium wrapper? Sorry :(

Ok, that's fine.


Make special config resolver for shifting exog features.

🚀 Feature Request
ToDo
Proposal
ToDo
Test cases
No response
Additional context
No response

Closed by #1234.


Using Frame() to send multiple PNs and failure

When using a frame to send many PNs how would I keep track when a specific PN fails? I.E. if I have a list of 1000 tokens I need to send to and a failure occurs on token number 556 how do I resume the sending of PNs by skipping 556 and continuing with 557?
Is this possible at all? I know that I can check the feedback service for invalid tokens before sending but it's not always that a token has been invalidated before sending, often another kind of error can occur to halt the send_notification_multiple process.
Any feedback would be greatly appreciated.
Thanks!

Hello, @zac156! You need to use enhanced mode to track errors. But Enhanced mode doesn't work with frames #103 #90 #92. So I guess it is better not to use frames, but track errors with Enhanced mode.

Thanks denisov, does that mean that I'll have to send PNs one by one? Wouldn't this process prove to be quite as then I'd be opening and closing the socket connection each time I send an individual PN?
Thanks for your help so far!

@zac156
PyAPNs will try to RE-USE socket connection as much as possible if you are sending PN with the same instance
apns = APNs(use_sandbox=True, cert_file='cert.pem', key_file='key.pem')
...
apns.gateway_server.send_notification(token_hex, payload)
apns.gateway_server.send_notification(token_hex, payload)
apns.gateway_server.send_notification(token_hex, payload)

FYR.

This is more of a support request than a bug, I am closing.


Strange behaviour while seeking for code snippets

Issue Type: Bug
since the last patch I have a strange behaviour.
I got around 100 Snippets in my extension to make working more efficient for our customer-devs.
since the last patch it seems the "auto suggestion" for my snippets is working odd.
i got 2 snippets as follows:

If I try to seek for them via quick suggestion that wont work anymore:

Just one of the two snippets are returned...
Is there a new setting that I did not mention that controls the behaviour? I have "no" user-specific settings concerning snippets as i know...
Any advice ?
I have a release soon with this extension so this comes a bit unhandy atm...
VS Code version: Code - Insiders 1.29.0-insider (931c22033db3cc8d5dff265889307ed4076ac2d3, 2018-10-12T05:17:15.739Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (8.61GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

Bookmarks
ale
9.1.0

xml
Dot
2.3.2

todo-tree
Gru
0.0.92

ilspy-vscode
ics
0.7.0

easy-icons
jam
0.3.1

vscode-language-pack-de
MS-
1.28.2

PowerShell
ms-
1.9.0

snippet-creator
nik
0.0.5

f-script
Opa
16.20.1

opacc-fscript-debug
Opa
16.20.1

this is still working in the "stable" version

if i write IBOS and hit  i get this now:

/duplicate of  #60746


DXP-335 Universal-ts-utils doc

Changes
Improving some methods doc, standardising it and filling readme
Checklist

[x] Apply one of following labels; major, minor, patch or skip-release
[x] I've updated the documentation, or no changes were necessary
[x] I've updated the tests, or no changes were necessary

How lucky we are to have you @CarlosGamero ❤

Yes!!!!


Feat/update deployment and doc

Reviewer: @amiraliemami
Estimate: 1h30mins

Ticket
Fixes: AAQ-359 & AAQ-360 & AAQ-357
Description, Motivation and Context
This PR is the 3rd part of the refactoring to be able to use Pgvector. This PR is the last before merging to main. So should we reviewed carefully.
Goal
Changes
The following changes have been made.

Update the CI/CD and deployment scripts
Update terraform
Update documentation
Update tests

How has this been tested?
This was tested end-to-end. The enpoints were individually tested using swaggerUI, then the admin app was tested to make sure they could communicate. And the app was deployed and tested to make sure deployment works fine.
Checklist
Fill with x for completed. Delete any lines that are not relevant

[x] My code follows the style guidelines of this project
[x] I have reviewed my own code to ensure good quality
[x] I have tested the functionality of my code to ensure it works as intended
[x] I have resolved merge conflicts
[x] I have updated the automated tests (if applicable)
[x] I have updated the requirements (if applicable)
[x] I have updated the README file (if applicable)
[x] I have updated affected documentation (if applicable)

@lickem22 Just double-check the cosine-distance stuff to make sure the order is correct and monotonous. Maybe add a line to the docs somewhere that the "lower the score the better"?

I actually do not think it is necessary since the definition of the distance implies that. But happy to discuss it during next tech session.


Push Notifications on Android (MicroG)

I have a OnePlus device running /e/ OS which has fully functioning MicroG built in, including Google Cloud Messaging.
Currently there are 20+ apps registered with GCM and their push notifications work just great.
But the Databag app installed via F-Droid is not showing as being registered for GCM and I am not getting any Push Notifications.
What Notification Daemon is expected for use with Databag? I'm wondering if there is something else I need to install/enable to get working notifications.

f-droid requires open source software, so as far as I know google cloud messaging is not permitted.
To get push notifications working with the f-droid build of databag, you need to use UnifiedPush. To enable this you can install the ntfy app which will relay the push notifications for databag.

Got it.
Or I could try the playstore version via Aurora and it would probably work. I'll give that a try.
Thanks!
-------- Original Message --------
On 11/20/24 9:20 PM, Pierre Balzack  wrote:

f-droid requires open source software, so as far as I know google cloud messaging is not permitted.
To get push notifications working with the f-droid build of databag, you need to use UnifiedPush. To enable this you can install the ntfy app which will relay the push notifications for databag.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


#2768 Removed auto unindent on new line after delimiter.

This is a fix for issue #2768.
My reasons for removing the auto unindentation is because:

It doesn't work properly/consistently.
It forces unindentation instead of letting the user keep control.

Agreed, this "unindention" was a bit messy.


setup.py should describe abstract (non-version numbered) dependencies only

It is a best practice to have only abstract, non-version numbered, dependencies in setup.py.
For exact tested known good set of versions (KGS) one can distribute requirements.txt which usage is described in the installation instructions.

The developer can install this file directly using pip install -r requirements

For the application, which is using counterparty-lib, the application maintainer can merge requirements.txt to the application specific requirements.txt or similar package version list (There are other Python package management tools like Buildout).

Please note that not having exact version pinnings will break counterparty-lib installation if any of dependency packages gets a new non-API-compatible release.
For more information

https://caremad.io/2013/07/setup-vs-requirement/

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

ACK.
Great article thanks!
If @adamkrellenstein and @robby-dermody are OK, I will remove version number in counterparty-lib, and use a requirements.txt for counterparty-cli.

ACK

done here and here.

Sure. im not sure if it'll fully work with counterblock as well, as there are some particular versions we have to rely on there (due to upstream bugs)... But I'll read the article


Agent login does not work for me

I tried with different servers using login_with_agent. It always fails with the following error on my machine:
Unhandled exception: Failed to authenticate username root with SSH agent (SSH2::SSH2Error)
  from lib/ssh2/src/agent.cr:0:5 in 'authenticate'
  from lib/ssh2/src/session.cr:122:7 in 'login_with_agent'

(Arch Linux, openssh 8.1p1-1, Crystal 0.31.1)

I added some error handling so the message now reads
Unhandled exception: Failed to authenticate username root with SSH agent, error code -37, Would block (SSH2::SSH2Error)

Well, i just added a @session.perform_nonblock do block around the LibSSH2.agent_userauth call, and I am able to login.
(Disclaimer: I don't really know what I am doing here.)

Yeah I haven't used agent auth for any of my programmatic SSH usage.
I was actually going to caution you on using agent auth as I am not sure how the C-Lib implements the comms and it might block the crystal reactor.
But it seems perform_nonblock is the solution to that.

Okay, I will try using this for a while. I can create a PR if it turns out to be working reliably.

That would be awesome! Thanks!

Seems to be working good.


[Feature Request] Custom Screen Sizes Option

Problem Description
The tool currently only supports preset screen sizes for mobile, tablet, and desktop. Users may need to define custom screen dimensions to better suit their specific design needs, such as creating screenshots for devices with uncommon resolutions or specific web layouts.
Example: "The current implementation only provides preset sizes, which limits the flexibility for users who require custom dimensions."
Desired Enhancement
I would like to introduce an option that allows users to input custom screen sizes in addition to the default mobile, tablet, and desktop sizes. This would allow users to design and export mockups in any resolution they need.
Alternatives Considered
I explored using external tools to crop or resize screenshots after export, but having this feature built directly into the tool would save users time and provide a more streamlined experience.
Possible Implementation

[ ] Add a custom size option where users can input their desired width and height in pixels
[ ] Ensure the aspect ratio can be locked or unlocked for flexibility
[ ] Validate custom sizes to avoid unintended rendering issues
[ ] Add this option alongside the preset sizes in the UI for easy access

Optional Sections:

Priority: Medium
Are you willing to submit a PR for this enhancement? Yes
Does this enhancement require changes in documentation? No

Hi @suryanshsingh2001, I would like to work on this enhancement.

Hey @rahulchaudhary2244
Sure! Please make sure that the changes work with the existing screen sizes and ensure the design is responsive. Also, follow the same UI design patterns used for the previous controls. Looking forward to your contribution!


Label in front of input field

Hi,
There is an example for putting a icon in front of the input field:
{
"key": "fixedIcon",
"type": "lx-input",
"templateOptions": {
"type": "text",
"fixedLabel": true,
"icon": "account",
"label": "With Icon"
}
}
Is it possible to just show a text label in front of the input field?
Ayaz

Hi Ayaz,
The true power of Angular-Formly is when you realize you can customize everything to your own liking.
I can think of three good approaches for inline labels. One is to use lx-flex, but if you're going to put labels in front of a lot of fields, this is not the best choice.
I would recommend making your own custom template. There's a good video and docs explaining how.
Your template would look something like this, with a class of "text-label" & "form-field" styling the positions:

{{to.label}}
<lx-text-field model="::model[options.key]"
               icon="{{::to.icon}}"
               fixed-label="::to.fixedLabel"
               theme="{{::to.theme}}"
               disabled="to.disabled"
               valid="fc.$valid && fc.$touched"
               error="fc.$invalid && fc.$touched">
	<input ng-model="model[options.key]"
	       type="{{::to.type}}"
	       aria-label="{{::to.label}}"
	       ng-class="::to.className"/>
</lx-text-field>

A final option would be to create your own "wrapper". This could wrap around any element getting the same effect.

       {{to.label}}
	<formly-transclude></formly-transclude>

You could call it "label-wrapper", and add it.
key: 'someKey',
type: 'lx-input',
wrapper: 'label-wrapper',
templateOptions: {
  label-wrapper: {
     label: 'Some label'
  }
}

Let me know if you have any questions.

Thanks ShMcK, I will try this later today.


Add support for redisgraph / GORM

Something like:  https://gorm.grails.org/6.1.x/neo4j/manual/index.html

@owentechnologist I will have the basic graph annotations in near the end of the year. Then I'm merging this https://github.com/bsbodden/jredisgraph-qb with it after refining it


Two instances of MuiSvgIcon in project.

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

Current Behavior 😯

There are 2 instances of MuiSvgIcon <style ... data-meta="MuiSvgIcon">...</style> in project head one with MuiSvgIcon-colorPrimary-2 class which is setting icons color to default MUI blue color.
Some icons have proper styling - color from my theme and some of them have default material blue color.
Expected Behavior 🤔

All icons have color set by theme and there is only one instance of <style ... data-meta="MuiSvgIcon">...</style>.
Steps to Reproduce 🕹
It's hard to reproduce as it's large project.
Context 🔦
i'm trying to have consistent UI without using style or with-styles

Your Environment 🌎

Tech
Version

Material-UI
v4.7.1-0

React
16.9

MUI Icons
3.0.1-0

Browser
chrome - latest

It's hard to reproduce as it's large project.

This is paramount in this case. We don't have the bandwidth to debug large applications for you. Without a reproduction we won't be  able to help you.

Give me some time, I'll need to create sample sandbox for you.
I'm thinking that there could be two instances of theme in my app as ...-colorPrimary-2 is incremented from ...-colorPrimary.

@MMaicki Make sure you bundle a single version of the modules, it should solve your issue.

I have a same issue. I have a component with theme specified where i override MuiSvgIcon.colorPrimary.color property.
This component is bundled with @material-ui/core sepcified as external dependency in webpack.config.
		'@material-ui/core': {
			commonjs: '@material-ui/core',
			commonjs2: '@material-ui/core',
			amd: '@material-ui/core',
			umd: '@material-ui/core',
			root: 'MaterialUI'
		}

when using this component in another react app with material installed, 2 versions of "MuiSvgIcon" style tags are created with identical class names inside.
The second one overrides the color of icons in component but also color of icons everywhere in hosting app and all icons has default blue color.

Any updates on this issue ?

Adding @material-ui/styles to external dependencies worked for me

I had this problem when I was using the react-redux-toastr and I discovered that I was called this tag  out of (or before) of called the tag to , maybe your problem be with some import.


XLA Warning

I am receiving this warning,
W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1412] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.

in one of my travic ci builds. AFAIK, XLA is going through active development and therefore I prefer not to use, TF_XLA_FLAGS=--tf_xla_cpu_global_jit. However, I cannot figure out how to silence this warning, permanently during future builds. If any such technique exists then I would suggest to add that to warning itself.
Please let me know, if it can be done by manipulating env variables. Thanks.

Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Please.provide reproducible code. If you are unclear what to include see the issue template displayed in the Github new issue temhttps://github.com/tensorflow/tensorflow/issues/new/chooseplate.
We ask for this in the issue submission template, because it is really difficult to help without that information. Thanks!

Below is the complete Build System Information,
Build system information
Build language: python
Build group: stable
Build dist: trusty
Build id: 553259216
Job id: 553259233
Runtime kernel version: 4.4.0-101-generic
travis-build version: 7b7f39e22
Build image provisioning date and time
Tue Dec  5 19:58:13 UTC 2017
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty
Cookbooks Version
7c2c6a6 https://github.com/travis-ci/travis-cookbooks/tree/7c2c6a6
git version
git version 2.15.1
bash version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
gcc version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
docker version
Client:
 Version:      17.09.0-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:42:38 2017
 OS/Arch:      linux/amd64
Server:
 Version:      17.09.0-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:41:20 2017
 OS/Arch:      linux/amd64
 Experimental: false
clang version
clang version 5.0.0 (tags/RELEASE_500/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/clang-5.0.0/bin
jq version
jq-1.5
bats version
Bats 0.4.0
shellcheck version
0.4.6
shfmt version
v2.0.0
ccache version
ccache version 3.1.9
Copyright (C) 2002-2007 Andrew Tridgell
Copyright (C) 2009-2011 Joel Rosdahl
This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 3 of the License, or (at your option) any later
version.
cmake version
cmake version 3.9.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
heroku version
heroku-cli/6.14.39-addc925 (linux-x64) node-v9.2.0
imagemagick version
Version: ImageMagick 6.7.7-10 2017-07-31 Q16 http://www.imagemagick.org
md5deep version
4.2
mercurial version
Mercurial Distributed SCM (version 4.2.2)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2017 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
mysql version
mysql  Ver 14.14 Distrib 5.6.33, for debian-linux-gnu (x86_64) using  EditLine wrapper
openssl version
OpenSSL 1.0.1f 6 Jan 2014
packer version
Packer v1.0.2
Your version of Packer is out of date! The latest version
is 1.1.2. You can update by downloading from www.packer.io
postgresql client version
psql (PostgreSQL) 9.6.6
ragel version
Ragel State Machine Compiler version 6.8 Feb 2013
Copyright (c) 2001-2009 by Adrian Thurston
subversion version
svn, version 1.8.8 (r1568071)
   compiled Aug 10 2017, 17:20:39 on x86_64-pc-linux-gnu
Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/
The following repository access (RA) modules are available:
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.3
  - handles 'http' scheme
  - handles 'https' scheme
sudo version
Sudo version 1.8.9p5
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn --with-logging=syslog --with-logfac=authpriv --with-env-editor --with-editor=/usr/bin/editor --with-timeout=15 --with-password-timeout=0 --with-passprompt=[sudo] password for %p:  --without-lecture --with-tty-tickets --disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail --with-timedir=/var/lib/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo --with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux
Sudoers policy plugin version 1.8.9p5
Sudoers file grammar version 43
Sudoers path: /etc/sudoers
Authentication methods: 'pam'
Syslog facility if syslog is being used for logging: authpriv
Syslog priority to use when user authenticates successfully: notice
Syslog priority to use when user authenticates unsuccessfully: alert
Send mail if the user is not in sudoers
Use a separate timestamp for each user/tty combo
Lecture user the first time they run sudo
Root may run sudo
Allow some information gathering to give useful error messages
Require fully-qualified hostnames in the sudoers file
Visudo will honor the EDITOR environment variable
Set the LOGNAME and USER environment variables
Length at which to wrap log file lines (0 for no wrap): 80
Authentication timestamp timeout: 15.0 minutes
Password prompt timeout: 0.0 minutes
Number of tries to enter a password: 3
Umask to use or 0777 to use user's: 022
Path to mail program: /usr/sbin/sendmail
Flags for mail program: -t
Address to send mail to: root
Subject line for mail messages: *** SECURITY information for %h ***
Incorrect password message: Sorry, try again.
Path to authentication timestamp dir: /var/lib/sudo
Default password prompt: [sudo] password for %p:
Default user to run commands as: root
Value to override user's $PATH with: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
Path to the editor for use by visudo: /usr/bin/editor
When to require a password for 'list' pseudocommand: any
When to require a password for 'verify' pseudocommand: all
File descriptors >= 3 will be closed before executing a command
Environment variables to check for sanity:
	TZ
	TERM
	LINGUAS
	LC_*
	LANGUAGE
	LANG
	COLORTERM
Environment variables to remove:
	RUBYOPT
	RUBYLIB
	PYTHONUSERBASE
	PYTHONINSPECT
	PYTHONPATH
	PYTHONHOME
	TMPPREFIX
	ZDOTDIR
	READNULLCMD
	NULLCMD
	FPATH
	PERL5DB
	PERL5OPT
	PERL5LIB
	PERLLIB
	PERLIO_DEBUG
	JAVA_TOOL_OPTIONS
	SHELLOPTS
	GLOBIGNORE
	PS4
	BASH_ENV
	ENV
	TERMCAP
	TERMPATH
	TERMINFO_DIRS
	TERMINFO
	_RLD*
	LD_*
	PATH_LOCALE
	NLSPATH
	HOSTALIASES
	RES_OPTIONS
	LOCALDOMAIN
	CDPATH
	IFS
Environment variables to preserve:
	JAVA_HOME
	TRAVIS
	CI
	DEBIAN_FRONTEND
	XAUTHORIZATION
	XAUTHORITY
	PS2
	PS1
	PATH
	LS_COLORS
	KRB5CCNAME
	HOSTNAME
	HOME
	DISPLAY
	COLORS
Locale to use while parsing sudoers: C
Directory in which to store input/output logs: /var/log/sudo-io
File in which to store the input/output log: %{seq}
Add an entry to the utmp/utmpx file when allocating a pty
PAM service name to use
PAM service name to use for login shells
Create a new PAM session for the command to run in
Maximum I/O log sequence number: 0
Local IP address and netmask pairs:
	<IP_ADDRESS>/<IP_ADDRESS>
	<IP_ADDRESS>/<IP_ADDRESS>
Sudoers I/O plugin version 1.8.9p5
gzip version
gzip 1.6
Copyright (C) 2007, 2010, 2011 Free Software Foundation, Inc.
Copyright (C) 1993 Jean-loup Gailly.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.
Written by Jean-loup Gailly.
zip version
Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license.
This is Zip 3.0 (July 5th 2008), by Info-ZIP.
Currently maintained by E. Gordon.  Please send bug reports to
the authors using the web page at www.info-zip.org; see README for details.
Latest sources and executables are at ftp://ftp.info-zip.org/pub/infozip,
as of above date; see http://www.info-zip.org/ for other sites.
Compiled with gcc 4.8.2 for Unix (Linux ELF) on Oct 21 2013.
Zip special compilation options:
	USE_EF_UT_TIME       (store Universal Time)
	BZIP2_SUPPORT        (bzip2 library version 1.0.6, 6-Sept-2010)
	    bzip2 code and library copyright (c) Julian R Seward
	    (See the bzip2 license for terms of use)
	SYMLINK_SUPPORT      (symbolic links supported)
	LARGE_FILE_SUPPORT   (can read and write large files on file system)
	ZIP64_SUPPORT        (use Zip64 to store large files in archives)
	UNICODE_SUPPORT      (store and read UTF-8 Unicode paths)
	STORE_UNIX_UIDs_GIDs (store UID/GID sizes/values using new extra field)
	UIDGID_NOT_16BIT     (old Unix 16-bit UID/GID extra field not used)
	[encryption, version 2.91 of 05 Jan 2007] (modified for Zip 3)
Encryption notice:
	The encryption code of this program is not copyrighted and is
	put in the public domain.  It was originally written in Europe
	and, to the best of our knowledge, can be freely distributed
	in both source and object forms from any country, including
	the USA under License Exception TSU of the U.S. Export
	Administration Regulations (section 740.13(e)) of 6 June 2002.
Zip environment options:
             ZIP:  [none]
          ZIPOPT:  [none]
vim version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:43:18)
Included patches: 1-52
Extra patches: 8.0.0056
Modified by<EMAIL_ADDRESS>Compiled by buildd@
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           +mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
-clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   -perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl    -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
iptables version
iptables v1.4.21
curl version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
wget version
GNU Wget 1.15 built on linux-gnu.
rsync version
rsync  version 3.1.0  protocol version 31
gimme version
v1.2.0
nvm version
0.33.6
perlbrew version
/home/travis/perl5/perlbrew/bin/perlbrew  - App::perlbrew/0.80
phpenv version
rbenv 1.1.1-25-g6aa70b6
rvm version
rvm 1.29.3 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io]
default ruby version
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
CouchDB version
couchdb 1.6.1
ElasticSearch version
5.5.0
Installed Firefox version
firefox 56.0.2
MongoDB version
MongoDB 3.4.10
PhantomJS version
2.1.1
Pre-installed PostgreSQL versions
9.2.24
9.3.20
9.4.15
9.5.10
9.6.6
RabbitMQ Version
3.6.14
Redis version
redis-server 4.0.6
riak version
2.2.3
Pre-installed Go versions
1.7.4
ant version
Apache Ant(TM) version 1.9.3 compiled on April 8 2014
mvn version
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z)
Maven home: /usr/local/maven-3.5.2
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-98-generic", arch: "amd64", family: "unix"
gradle version
------------------------------------------------------------
Gradle 4.0.1
------------------------------------------------------------
Build time:   2017-07-07 14:02:41 UTC
Revision:     38e5dc0f772daecca1d2681885d3d85414eb6826
Groovy:       2.4.11
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_151 (Oracle Corporation 25.151-b12)
OS:           Linux 4.4.0-98-generic amd64
lein version
Leiningen 2.8.1 on Java 1.8.0_151 Java HotSpot(TM) 64-Bit Server VM
Pre-installed Node.js versions
v4.8.6
v6.12.0
v6.12.1
v8.9
v8.9.1
phpenv versions
  system
  5.6
* 5.6.32 (set by /home/travis/.phpenv/version)
  7.0
  7.0.25
  7.1
  7.1.11
  hhvm
  hhvm-stable
composer --version
Composer version 1.5.2 2017-09-11 16:59:25
Pre-installed Ruby versions
ruby-2.2.7
ruby-2.3.4
ruby-2.4.1

About the tensorflow version, below snippets of logs will be relevant,
Environment Location
environment location: /home/travis/miniconda/envs/test-environment

Version
tensorboard            1.14.0
tensorflow             1.14.0
tensorflow-estimator   1.14.0

Most probably, installed via conda.
Miscellaneous Details
2019-07-02 12:35:55.175246: I tensorflow/core/platform/cpu_feature_guard.cc:145] This TensorFlow binary is optimized with Intel(R) MKL-DNN to use the following CPU instructions in performance critical operations:  SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in non-MKL-DNN operations, rebuild TensorFlow with the appropriate compiler flags.
2019-07-02 12:35:55.206996: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-07-02 12:35:55.207182: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x55ee8fd713e0 executing computations on platform Host. Devices:
2019-07-02 12:35:55.207198: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): <undefined>, <undefined>
OMP: Info #212: KMP_AFFINITY: decoding x2APIC ids.
OMP: Info #210: KMP_AFFINITY: Affinity capable, using global cpuid leaf 11 info
OMP: Info #154: KMP_AFFINITY: Initial OS proc set respected: 0,1
OMP: Info #156: KMP_AFFINITY: 2 available OS procs
OMP: Info #157: KMP_AFFINITY: Uniform topology
OMP: Info #179: KMP_AFFINITY: 1 packages x 1 cores/pkg x 2 threads/core (1 total cores)
OMP: Info #214: KMP_AFFINITY: OS proc to physical thread map:
OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 0 thread 1
OMP: Info #250: KMP_AFFINITY: pid 24554 tid 24554 thread 0 bound to OS proc set 0
2019-07-02 12:35:55.208209: I tensorflow/core/common_runtime/process_util.cc:115] Creating new thread pool with default inter op setting: 2. Tune using inter_op_parallelism_threads for best performance.

For details, visit, https://api.travis-ci.org/v3/job/553259233/log.txt
Thanks.

@ravikyram I'm receiving the same error
2019-07-03 18:02:26.272503: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1412] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set. If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU. To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.
following is my Docker container details
ubuntu:18.10
RUN apt-get update && apt-get install -y --no-install-recommends software-properties-common
RUN apt-get update && apt-get install -y --no-install-recommends
python3.7
python3-dev
and following is Pipfile
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true
[dev-packages]
[packages]
numpy = ""
scikit-learn = ""
pandas = ""
pytest = ""
pytest-cov = ""
pymysql = ""
sqlalchemy = ""
alembic = ""
boto3 = ""
flask = ""
flask-restplus = ""
moto = ""
tensorflow = "*"
[requires]
python_version = "3.7"

@czgdp1807 @amitml Have you solved the warnings since i have the same warnings with you ?

@tangjie77wd I haven't figured out a way yet to silence the warnings. We are planning to leave them as it is in the travis logs.

@sanjoy @tpopp  any updates on how to silence the warning since we are not planning to use XLA for testing purposes.

@czgdp1807  Well,the performance is poor if i do not handle with it.

Sorry about this. The warning should not have been printed when you aren't using XLA at all. There's not any environment variable to hide this warning, but I will work on a fix in the code now.

@tangjie77wd set TF_XLA_FLAGS=--tf_xla_cpu_global_jit for using XLA as far as I can figure out from the warning message. This will improve the performance.

@tpopp Thanks, waiting for this issue to be closed via some PR.

@czgdp1807  Thanks very much.Do you mean export TF_XLA_FLAGS=--tf_xla_cpu_global_jit=/mytensorflowpath/tensorflow/compiler/xla:$TF_XLA_FLAGS=--tf_xla_cpu_global_jit ?

@tangjie77wd Yes

@tangjie77wd Yes

However,the warning is still the same.

The warning suggested XLA_FLAGS=--xla_hlo_profile this too. If after setting this the things don't work then please make a comment here. Probably this may need a fix. For more details read the warning message again and try the suggestions in it.
PS - Did you observe any improvements after applying https://github.com/tensorflow/tensorflow/issues/30308#issuecomment-513706301?

The warning suggested XLA_FLAGS=--xla_hlo_profile this too. If after setting this the things don't work then please make a comment here. Probably this may need a fix. For more details read the warning message again and try the suggestions in it.
PS - Did you observe any improvements after applying #30308 (comment)?

Is the specific path of XLA_FLAGS=--xla_hlo_profile the same with TF_XLA_FLAGS=--tf_xla_cpu_global_jit ?

Yes probably, this is what my intuition says. I suspect that is there any thing extra to be installed for using XLA. In fact, you can also take a look XLA usage in tensorflow guide. @tpopp any suggestions/corrections for @tangjie77wd 's situation.

@czgdp1807 It can not be better if there is something extra to be installed for using XLA. Do i need to do something with /mytensorflowpath/tensorflow/compiler/xla/service/BUILD ?

Yes probably, this is what my intuition says. I suspect that is there any thing extra to be installed for using XLA. In fact, you can also take a look XLA usage in tensorflow guide. @tpopp any suggestions/corrections for @tangjie77wd 's situation.

@czgdp1807 I know i can choose open XLA and AXV and SSE during the libtensorflow_cc.so building if i uninstall my tensorflow and rebuild it.However, i really do not want to uninstall  my tensorflow now.

Yes probably, this is what my intuition says. I suspect that is there any thing extra to be installed for using XLA. In fact, you can also take a look XLA usage in tensorflow guide. @tpopp any suggestions/corrections for @tangjie77wd 's situation.

@czgdp1807 Am i wrong ?Maybe it is TF_XLA_FLAGS=--tf_xla_cpu_global_jit=/mytensorflowpath/tensorflow/compiler/xla/...cc or TF_XLA_FLAGS=--tf_xla_cpu_global_jit=/mytensorflowpath/tensorflow/compiler/git/...cc when i look at https://stackoverflow.com/questions/45681405/tensorflow-xla-not-producing-the-dot-file

Well, https://www.tensorflow.org/xla/jit#step_3_run_with_xla should work. Have you tried it?

Or what about using XLA from within the code as shown in https://www.tensorflow.org/xla/tutorials/xla_compile?

Using the environment variable should be something like this:
export TF_XLA_FLAGS=--tf_xla_cpu_global_jit
It is a boolean flag, so setting it to some other string evaluated to false because it did not make sense relative to a boolean value. Also, setting it without enabling XLA with --tf_xla_auto_jit=2 will not affect performance. This message being printed was a bug because it was only supposed to occur when actually using XLA.
The change would be in tf-nightly after 1 day, and I'm not sure when it would end up in the general tensorflow package.

Or what about using XLA from within the code as shown in https://www.tensorflow.org/xla/tutorials/xla_compile?

Yeah,once i have tried to active XLA before main function in my c++ code like the following:
#include "c_api_experimental.h"
TF_SessionOptions options = TF_NewSessionOptions();*
TF_EnableXLACompilation(options,true);
However,these above make my project building failed with error collect2: error: ld returned 1 exit status ! I am not only able to get https://www.tensorflow.org/install/lang_c#compile to run but also https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/multibox_detector/main.cc to run successfully before i do this above.

Well, https://www.tensorflow.org/xla/jit#step_3_run_with_xla should work. Have you tried it?

No,i think i can not try it since i use tensorflow 2.0 c++ api with eclipse GUI on Ubuntu 16.04 .

Using the environment variable should be something like this:
export TF_XLA_FLAGS=--tf_xla_cpu_global_jit
It is a boolean flag, so setting it to some other string evaluated to false because it did not make sense relative to a boolean value. Also, setting it without enabling XLA with --tf_xla_auto_jit=2 will not affect performance. This message being printed was a bug because it was only supposed to occur when actually using XLA.
The change would be in tf-nightly after 1 day, and I'm not sure when it would end up in the general tensorflow package.

You mean that the warning (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile has no big effect on performance but i really get very poor performance after i replace libxgboost.so with libtensorflow_cc.so. Maybe the poor performance is cause by other warnings like the warning Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA or the warning Running all optimization passes in grouping 0.  Try reducing graph modifications or using SavedModel to avoid any graph modification, is it right ?

Yes probably, this is what my intuition says. I suspect that is there any thing extra to be installed for using XLA. In fact, you can also take a look XLA usage in tensorflow guide. @tpopp any suggestions/corrections for @tangjie77wd 's situation.

Sorry for my negligent reply . The warning 2019-07-23 10:17:57.259354: E tensorflow/core/util/command_line_flags.cc:106] Couldn't interpret value =/mytensorflowpath/tensorflow/compiler/xla:=--tf_xla_cpu_global_jit for fl_jlag tf_xla_cpu_globait. occurs after i set environment variable export TF_XLA_FLAGS=--tf_xla_cpu_global_jit=/mytensorflowpath/tensorflow/compiler/xla:$TF_XLA_FLAGS=--tf_xla_cpu_global_jit . I observe it just now. I think this new warning means setting environment failed, is it right?

AFAICT, Yes.

AFAICT, Yes.

Well,how do you set the environment variable of XLA_FLAGS or TF_XLA_FLAGS since add export TF_XLA_FLAGS=--tf_xla_cpu_global_jit=/mytensorflowpath/tensorflow/compiler/xla:$TF_XLA_FLAGS=--tf_xla_cpu_global_jit to /etc/profile is wrong ?

@tangjie77wd I use linux and on that probably using the suggestion in https://github.com/tensorflow/tensorflow/issues/30308#issuecomment-513985618. If you are facing problems in using XLA with environment flags then I would suggest you to use xla.compile in your code for compiling the model. I have given the associated link in https://github.com/tensorflow/tensorflow/issues/30308#issuecomment-513751793

@tangjie77wd I use linux and on that probably using the suggestion in #30308 (comment) should work. If you are facing problems in using XLA with environment flags then I would suggest you to use xla.compile in your code for compiling the model. I have given the associated link in #30308 (comment)

Thanks anyway. I have looked at  #30308 (comment) once but it maybe is not suitable for me because i do prediction with C++ API not Python.

@tpopp Is there any C++ API for XLA compile. May be if it exists then it can be added to https://www.tensorflow.org/xla/tutorials/xla_compile . Or any trick for using xla.compile in C++ code will be helpful. Thanks.

@tpopp Is there any C++ API for XLA compile. May be if it exists then it can be added to https://www.tensorflow.org/xla/tutorials/xla_compile . Or any trick for using xla.compile in C++ code will be helpful. Thanks.

I think sentenses below  maybe is XLA C++ API:
#include "c_api_experimental.h"
TF_SessionOptions options = TF_NewSessionOptions();
TF_EnableXLACompilation(options,true);
It can not be built successuffly because it need some XLA libraries .However, i do not find any .so file in /mytensorflowpath/tensorflow/compiler/xla/client/lib and there are only some c++ source file and c++ header file .

There is not a C++ API for XLA compile. If you think there would be use in this, feel free to open another issue, and someone with more insight than me can respond.
I will close this issue as the bug this was opened for is now fixed at head.
Regarding the other issues for @tangjie77wd, It looks like you're still adding other information when setting the flag. It should be exactly TF_XLA_FLAGS=--tf_xla_cpu_global_jit while it looks like you're adding other path information leading to it being unable to parse. As you said in one issue though, you don't have Tensorflow built with XLA, so it doesn't matter anyway. The reason you are seeing this message is just because of a bug in the logging information and won't make a difference anyway.
I would advise just ignoring the message for now if you can. And regarding the Tensorflow being slower than Boost for your use case, you'll probably get the best result looking for help with the stack overflow community.

@tpopp Thank you,i have already solved the problem.


Pull policy default during upgrade

What does this PR change?
Pull policy default during upgrade

change pull policy default to Always during upgrade
change pull policy default for migration image to Never during upgrade

Test coverage

No tests
[x] DONE

Links
Issue(s): #

[ ] DONE

Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:

[ ] No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)
Before you merge
Check How to branch and merge properly!

@mcalmer JFYI this if for always download the new image during upgrade


Comments with no indent are not toggled

Anything with a comment that has no indent is not toggled, like this  for example:
--local test = 0

Actual:
-- --local test = 0

Expected:
local test = 0

This also happens with any language with a comment that has no indent.

I'm unable to replicate this issue, can you see if it still persists when you are using latest commit and you load a file with:
 vi -u NONE <SOME FILE GOES HERE> -c "packadd nvim-comment | lua require('nvim_comment').setup()"
Note that this assumes that you plugin is in the 'opt' directory and usings vim's default package manager stucture.

Yep, it still happens.

Oh couldn't see the wood for the trees!
It assumes there is a space between the space and the rest of the line.
If you don't have the padding them there is a setting you can use to not
use the padding.
require('nvim_comment').setup({marker_padding = false })
On Fri, 12 Feb 2021, 15:02 Loaf of Bread<EMAIL_ADDRESS>wrote:

Yep, it still happens.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/terrortylor/nvim-comment/issues/4#issuecomment-778247231,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJEXTKJHDMHFNBUVSDZO63S6U7I5ANCNFSM4XO64D6Q
.

Oh that makes sense now, thanks!

I have the same issue.
Setting marker_padding to false does not solve it for me because I actually want the space between marker and comment.
Toggling the following two comments
--local test = 0
-- local test = 0

should uncomment both:
local test = 0
local test = 0

And toggling again should give me:
-- local test = 0
-- local test = 0

Is this somehow possible?

same issue as @SaraSmiseth, kommentary and vim-commentary does it correct.


Add option to skip download-binaries in pre-commit.sh

Add option to skip download-binaries in pre-commit.sh, so that when the script is called in development environment, we need not keep downloading the binaries every time.
Also added a check to successfully build hyperfed binary.
/cc @font @marun

/lgtm


websql service ?

Possible to add websql/sqlite service ?

Hi,
Maybe this will helpful : https://github.com/abellion/ngDatabase
Frequency updates.

Merci :+1:

Hey,
I have no plans right now to do this myself but any pull request would be appreciated. :)


fix dubbo-admin-server starting RuntimeException

What is the purpose of the change
Escape one  RuntimeException when the dubbo-admin-server starting!
Brief changelog
If we use dubbo-admin to manage dubbo-2.7+ apps, we just only config admin.config-center property is ok. But now there is one RuntimeException when the dubbo-admin-server starting if we not config
admin.registry.address property!
Verifying this change
dubbo-admin-server: application.properties
#admin.registry.address=nacos://<IP_ADDRESS>:2181
admin.config-center=nacos://<IP_ADDRESS>:2181
admin.metadata-report.address=nacos://<IP_ADDRESS>:2181

Change before

Change after

Codecov Report

Merging #553 into develop will increase coverage by 0.06%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop     #553      +/-   ##
=============================================
+ Coverage      21.52%   21.59%   +0.06%
- Complexity       303      304       +1
=============================================
  Files             84       84
  Lines           3428     3431       +3
  Branches         544      545       +1
=============================================
+ Hits             738      741       +3
  Misses          2614     2614
  Partials          76       76

Impacted Files
Coverage Δ
Complexity Δ

...va/org/apache/dubbo/admin/config/ConfigCenter.java
94.64% <100%> (+0.3%)
19 <0> (+1)
:arrow_up:

Continue to review full report at Codecov.

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

just close


[feature] Extend to support zfs

Why you need it?

openlocal is a general name, while only lvm is covered, extend it to support ZFS seem to make it better deserving the name ;)
lvm is better performance, less resource demanding, but ZFS has some nice features like ensuring data integrity make it still a valid choice in many datacenter.
How it could be?

Providing lvm and zfs is so similar for end user perspective, I am wondering if it is possible to add a ZFS driver side by side, make openlocal support zfs as backend storage option.   I see openebs have an option named local-zfs, but it is look pretty messy there. This project, seem providing much neat code. it could be better base to implement a zfs csi driver here.  If zfs is included, I believe the project will get much more attention
What do you thinkg @TheBeatles1994
Other related information

Thx for your issue~ And I believe open-local will get more attention if zfs is included. By the way, not only lvm is covered, we are also preparing to integrate spdk.
I am not familiar with zfs, I see that LVM and zfs have many similar features, like storage pool, snapshot, etc. Does zfs can restrict use of volume capacity, similar to a logical volume in LVM?

@TheBeatles1994  Absolutely, features wise, zfs is far more completed and advanced than LVM. In ZFS, your can create dataset(vol with fs ready) or zvol (plain block device can used as raw disk), both can be set quota on them.  In short,  nothing is missing in ZFS if it is available in lvm.  LVM is like a poor-man solution of ZFS. If given enough resource, zfs perform far more better than LVM.  Most important thing is that zfs ensure your data integrity, no silent bit rot could happen. Keep your data safe and last for a very long time. This is very important for large dataset in big datacenter. And it is why zfs is choosen for most of HPC system.
But, there is always a "But" when something looks so good :), zfs demand more resource, a lot more than than LVM.
If openlocal could support both LVM and zfs, then user have options to choose depend on their resource, therefore make open local get much wide users base.

I did my research and ZFS is so powerful as you said. I believe open-local can integrate this well. And it would be very grateful if you can help with this feature, we need more great contributors like you~

@TheBeatles1994
Sure, I love to help. I can even bring some more ones to join us :)
Being the project establisher,  you has the best overall knowledge of the project, especially its architecture. Maybe you could initiate some architecture work first, I then help with adding ZFS blocks or review to start with, what do you think?

Maybe you could initiate some architecture work first, I then help with adding ZFS blocks or review to start with, what do you think?

Of course I can do this~ the project needs to do more abstraction to support more local storage types.

@TheBeatles1994 looking forward to seeing that is coming soon!


[OUDS] Add "Grid" tokens, utilities, examples and documentation

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues
Closes #2609

Description

Motivation & Context

Types of change

Bug fix (non-breaking which fixes an issue)
New feature (non-breaking change which adds functionality)
Refactoring (non-breaking change)
Breaking change (fix or feature that would change existing functionality)

Live previews

https://deploy-preview-2744--boosted.netlify.app/

Checklist

Contribution

[ ] I have read the contributing guidelines

Accessibility

[ ] My change follows accessibility good practices; I have at least run axe

Design

[ ] My change respects the design guidelines defined in Orange Design System
[ ] My change is compatible with a responsive display

Development

[ ] My change follows the developer guide
[ ] I have added JavaScript unit tests to cover my changes
[ ] I have added SCSS unit tests to cover my changes

Documentation

[ ] My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

[ ] My change introduces changes to the migration guide
[ ] My new component is well displayed in Storybook
[ ] My new component is compatible with RTL
[ ] Manually run BrowserStack tests
[ ] Manually test browser compatibility with BrowserStack (Chrome >= 60, Firefox >= 60 (+ ESR), Edge, Safari >= 12, iOS Safari, Chrome & Firefox on Android)
[ ] Code review
[ ] Design review
[ ] A11y review

After the merge

[ ] Manually launch Percy tests

While looking at the preview I spotted that the docs header is a bit broken 🤕, would it be possible to adapt the Orange navbar temporarily to follow this new grid, or is it too much work?

Grid semantic updates on design side on the October, 8:
// scss-docs-start ouds-semantic-color
+ $ouds-color-content-transparent-default: $ouds-color-transparent-black-0 !default;
$ouds-color-brand-warning-lowest: $ouds-color-functional-sun-100 !default;
// ...
$ouds-color-brand-attractive-default: $ouds-color-functional-sun-500 !default;
+ $ouds-color-border-transprent-default: $ouds-color-transparent-black-0 !default;
+ $ouds-color-bg-transparent-default: $ouds-color-transparent-black-0 !default;
$ouds-color-decorative-skin-tint-900: $ouds-color-decorative-deep-peach-900 !default;
// ...
$ouds-grid-xs-margin: $ouds-grid-margin-300 !default;
- $ouds-grid-xs-column-gap: $ouds-grid-column-gap-100 !default;
+ $ouds-grid-xs-column-gap: $ouds-grid-column-gap-200 !default;
$ouds-grid-xs-column-count: $ouds-grid-column-count-400 !default;
// ..
$ouds-grid-sm-margin: $ouds-grid-margin-400 !default;
- $ouds-grid-sm-column-gap: $ouds-grid-column-gap-100 !default;
+ $ouds-grid-sm-column-gap: $ouds-grid-column-gap-200 !default;
$ouds-grid-sm-column-count: $ouds-grid-column-count-400 !default;

It also means that $ouds-grid-column-gap-200 can be uncommented.


HTTPoxy Vulnerability and Caddy

Read https://www.kb.cert.org/vuls/id/797896 an https://httpoxy.org/
This vulnerability may impact for all web servers.
Run 'wget -S --header="Proxy: <IP_ADDRESS>:8080" https://yourdomain.com' for testing. If return something like 'ERROR 403: Forbidden' that mean website is 'safe'.

Original post at https://www.lowendtalk.com/discussion/88058/info-httpoxy-vulnerability-may-impact-to-web-servers
I can confirm this vulnerability exists on Caddy-based environments:
grep HTTP_PROXY info.php

$_SERVER['HTTP_PROXY']	<IP_ADDRESS>:8080

The best solution meanwhile is dropping or blocking the proxy header. I have attempted the following:
<IP_ADDRESS>:80 {
        root domains/localhost
        fastcgi / <IP_ADDRESS>:9000 {
                ext .php
                split .php
                index index.php
                env HTTP_PROXY ""
        }
        errors
}

But the issue persists. I have also tried env proxy "" and it does the same. So, how do we strip out a header?
Running Caddy 0.9.0 and PHP 7.0.

go1.6.3 (released 2016/07/17) includes security fixes to the net/http/cgi package and net/http package when used in a CGI environment. This release also adds support for macOS Sierra. See the Go 1.6.3 milestone on our issue tracker for details.

https://golang.org/doc/devel/release.html
It´s fixed :smile:
@mholt do you use Golang 1.6.3 (build server)

Well, I thought we use the built-in transport facilities :cry:

Does PHP even use the HTTP_PROXY env variable to control where to make requests through? Trying to understand the extent of this vulnerability in this context.

After looking at the source to see how FastCGI is implemented and how environment variables are passed, Caddy (and FastCGI) does not look vulnerable.
If no one else is able to prove otherwise, I think we can close this issue.

@mholt

Does PHP even use the HTTP_PROXY env variable to control where to make requests through? Trying to understand the extent of this vulnerability in this context... if the web application is using an environment variable from headers (HTTP_PROXY in this case), that is its own fault, not Caddy's for passing it on to the application. There might not be anything to fix here, except your PHP app.

http://php.net/ChangeLog-7.php#7.0.9

Fixed bug #72573 (HTTP_PROXY is improperly trusted by some PHP libraries and applications).

http://php.net/ChangeLog-5.php#5.6.24

Fixed bug #72573 (HTTP_PROXY is improperly trusted by some PHP libraries and applications).

@abiosoft

After looking at the source to see how FastCGI is implemented and how environment variables are passed, Caddy (and FastCGI) does not look vulnerable.

https://httpoxy.rehmann.co/ --> The service has queried domain.com using httpoxy headers, but received no http_proxy request

UPDATE:
Create a file called httpoxy.php with following content
<?php
if (isset($_SERVER['HTTP_PROXY']) && $_SERVER['HTTP_PROXY'] == 'vulnerable') {
  echo 'Vulnerable!';
}
?>

Run
curl --header "Proxy: vulnerable" https://example.com/httpoxy.php
Results:
"Vulnerable!" (Ubuntu 16.04 -- non fixed PHP)
"" (Ubuntu 16.04 -- fixed PHP)
PHP Script Source (https://www.lowendtalk.com/discussion/88058/info-httpoxy-vulnerability-may-impact-to-web-servers)
@mholt / @abiosoft

Right, that's an example of a web app that would use a value from the request header to direct an HTTP request.

Right, that's an example of a web app that would use a value from the request header to direct an HTTP request.

I know :smile: -- Should we "disable" the header?

I guess since PHP patched the issue it's no longer needed to disable the header, people just have to update PHP :)

I am just caring about our beloved uses!

Update the broken software instead.

@mholt I am not using it ! To repeat it "I am just caring about our beloved uses!" :smile:
Have a nice day, thank you for Caddy -- I :heart: it

If the user chooses to do that then it is not fair if Caddy prevents him/her 😄
And as long as Caddy is not the cause as we have ascertained here, I am fine.


Add cluster deployment as owner reference to admin secrets

To ensure admin secrets are not lost when the cluster has transitioned to installed and cluster provision is deleted, we add cluster deployment as additional owner reference to the admin secrets

@twiest @staebler I wonder if we can consider changing all owner references to have blockOwnerDeletion true and controller set as false
This would require moving from SetControllerReference to EnsureOwnerRef

@twiest @staebler I wonder if we can consider changing all owner references to have blockOwnerDeletion true and controller set as false
This would require moving from SetControllerReference to EnsureOwnerRef

I suggest not tackling that as part of this PR. It is a bit more complicated than just removing the controller flag on the owner references. Many of our controllers rely on the controller flag being there to trigger a re-queue of the owner when the owned object changes.