Allow passing React elements to certain props

I noticed that the message prop on <Input /> only accepts a string. I'm sure there are other places where this is the case as well. I think it would be much more flexible if these instances could take React elements as well as strings.
Would you be in favor of easing up the PropTypes checks to allow passing React elements to these props?
This is important in particular for react-intl, where the idiomatic way of using translated messages is via the <FormattedMessage /> component:
<Input
  type='text'
  message={
    <FormattedMessage
      id='error'
      defaultMessage={`Whoops, that's an error.`}
      />
  }
  />

It can also be used for composing styles:
<Input
  type='text'
  message={
    <strong>
      This field is required.
    </strong>
  }
  />

In fact, both of these use-cases work currently, but React complains about the PropTypes checks in development.

Hey @maxdeviant I agree that it would be helpful, and even valid, for PropTypes of certain fields to allow any react element instead of just strings.
I opened this PR as a proof of concept for the label prop of an Input component: https://github.com/jxnblk/rebass/pull/194
Is this what you were thinking of? I think the message prop could benefit from the same change.

@theopak Yep, this is exactly what I was referring to :smile:

The API has significantly changed in v1, where this shouldn't be an issue anymore

@jxnblk v1 looks great, btw :tada:


Vulnerability roundup 90: mruby-2.1.0: 1 advisory [9.8]

search, files

[ ] CVE-2020-15866 CVSSv3=9.8 (nixos-20.03)

Scanned versions: nixos-20.03: b50d55871fb. May contain false positives.
Cc @nicknovitski

20.03 is frozen and EOL.
Closing issue.


Non integer nuclear charge

Hi,
I was wondering if it is possible to modify the nuclear charge of a given atom without changing the number of electrons, for example Z=8.4 instead for oxygen atoms. This "trick" is sometimes use to stabilize and obtain electronic resonances for unstable anion states.

Sorry @MilaimKas I don't think you can

There's no way to do this in the input. However, if you supply a custom
function for the 1-electron integrals, by scaling the nuclear-electron
integral, then it will work. This is pretty straightforward, see e.g.
https://github.com/pyscf/pyscf/blob/master/examples/gto/20-ao_integrals.py
for an example to call the nuclear-electron integral, and look inside
https://github.com/pyscf/pyscf/blob/master/examples/scf/40-customizing_hamiltonian.py
to see how you can customize the Hamiltonian.
On Tue, May 5, 2020 at 8:34 AM James E T Smith<EMAIL_ADDRESS>wrote:

Sorry @MilaimKas https://github.com/MilaimKas I don't think you can
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf/issues/601#issuecomment-624127679, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN5NREVAL3VRFAQP4MKK6LRQAWWRANCNFSM4MZNAA5Q
.

Thank you very much for your respond !
Scaling the nuclear-electron integral would imply the total nuclear charge of the molecule to be modified. Even though it would be nice to have control over the nuclear charge of individual atoms, this is already very useful.

In relatively new release (>=1.7.1), there is a function created to handle MM particles. This might be even simpler to handle the non-integer nuclear charge
from pyscf.qmmm.mm_mole import create_mm_mol
mm_mol = create_mm_mol(coords_of_MM_particles, charges_of_MM_particles)
mol = pyscf.M(atom='...',...)
vmat = (mol + mm_mol).intor('int1e_nuc')

The relevant module is implemented here
https://github.com/pyscf/pyscf/blob/master/pyscf/qmmm/mm_mole.py


Change JMXReporter.GaugeMBean to MXBean

Sometimes gauge the callback might run a non-trivial operation that collects several data items. Instead of running the whole operation for each data item, it is preferable for the gauge to return composite data. MXBeans support composite data better than regular MBeans.
All that is required to implement this is change the name of GaugeMBean to GaugeMXBean or to annotate the type declaration with @javax.management.MXBean. It is a trivial code change that provides a useful functionality.

Hmm. Will this affect remote querying? That is, will JMX clients need to do anything differently because of this?
If it's backwards compatible, I'll slot this for 2.1.0.

@codahale Nope. See here.
However, I did notice that the GangliaReporter assumes that gauges return an int type.

You can find more detailed information about MXBeans and how they easily allow for composite types here and here.

@codahale Sorry to bother, but will this make it into the next version? It's a tiny change.


http proxy settings not used in container

I'm trying to spin up a micropcf, but we're behind an HTTP proxy. I noticed with the released Vagrant file that it's using the same setup as Lattice with regards to the vagrant-proxyconf plugin. I vagrant up the machine with http_proxy and https_proxy exported, and find that micropcf starts correctly and when I vagrant ssh the proxy settings are set.
vagrant@micropcf:~$ echo $http_proxy
http://proxy:3128
vagrant@micropcf:~$ echo $https_proxy
http://proxy:3128
vagrant@micropcf:~$ echo $no_proxy
localhost,<IP_ADDRESS>,<IP_ADDRESS>,local.micropcf.io

I've also left the http(s) proxy and no_proxy settings on my Mac too before pushing.
arthur@hephaestus $ echo $http_proxy
http://proxy:3128
arthur@hephaestus $ echo $https_proxy
http://proxy:3128
arthur@hephaestus $ echo $no_proxy
localhost,<IP_ADDRESS>,<IP_ADDRESS>,local.micropcf.io

But when I push up the application, which is just a simple Ruby app, it fails to download bundler. But I can download bundler from the VM itself:
vagrant@micropcf:~$ wget https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz
--2015-12-14 21:21:19--  https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz
Resolving monty.ms.otpp.net (monty.ms.otpp.net)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to monty.ms.otpp.net (monty.ms.otpp.net)|<IP_ADDRESS>|:3128... connected.
Proxy request sent, awaiting response... 200 OK
Length: 244764 (239K) [binary/octet-stream]
Saving to: ‘bundler-1.9.7.tgz’

100%[====================================================================================================================================================================================================================================>] 244,764     --.-K/s   in 0.1s

2015-12-14 21:21:20 (1.83 MB/s) - ‘bundler-1.9.7.tgz’ saved [244764/244764]

It just seems that the proxy settings aren't making their way to the garden containers. I poked around a bit to see where garden is being initialized, but I haven't found anything yet (no upstart/init script I can see).
Here's the full logs from the push:
arthur@hephaestus $ cf push badges
Creating app badges in org local.micropcf.io-org / space test as admin...
OK

Using route badges.local.micropcf.io
Binding badges.local.micropcf.io to badges...
OK

Uploading badges...
Uploading app files from: /Users/arthur/work/ruby/badges
Uploading 10.9K, 21 files
Done uploading
OK

Starting app badges in org local.micropcf.io-org / space test as admin...
Creating container
Successfully created container
Downloading app package...
Downloaded app package (7.2K)
No buildpack specified; fetching standard buildpacks to detect and build your application.
Downloading buildpacks (ruby_buildpack, nodejs_buildpack, go_buildpack, python_buildpack, php_buildpack, staticfile_buildpack, binary_buildpack, java_buildpack)...
Downloading python_buildpack...
Downloading nodejs_buildpack...
Downloading php_buildpack...
Downloading ruby_buildpack...
Downloaded ruby_buildpack
Downloading go_buildpack...
Downloaded php_buildpack
Downloading staticfile_buildpack...
Downloaded python_buildpack
Downloading binary_buildpack...
Downloaded staticfile_buildpack
Downloading java_buildpack...
Downloaded binary_buildpack
Downloaded java_buildpack
Downloaded nodejs_buildpack
Downloaded go_buildpack
Downloaded buildpacks
Staging...
cat: ../VERSION: No such file or directory
-------> Buildpack version 1.6.9
       Downloaded [https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz]
 !
/tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/shell_helpers.rb:50:in `run!': Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 10 --max-time 90 https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz -s -o - | tar zxf - ' failed unexpectedly: (LanguagePack::Fetcher::FetchError)
 !     Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 10 --max-time 90 https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/shared/bundler-1.9.7.tgz -s -o - | tar zxf - ' failed unexpectedly:
 !
 !     gzip: stdin: unexpected end of file
 !     tar: Child returned status 1
 !     tar: Error is not recoverable: exiting now
 !
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/fetcher.rb:24:in `fetch_untar'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:118:in `block (2 levels) in fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:117:in `chdir'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:117:in `block in fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:84:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:114:in `fetch_bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/helpers/bundler_wrapper.rb:33:in `install'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/ruby.rb:32:in `bundler'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/rails5.rb:9:in `block in use?'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/base.rb:48:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/rails5.rb:8:in `use?'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:17:in `block (2 levels) in detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `each'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:16:in `block in detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack.rb:13:in `detect'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/bin/compile:19:in `block in <main>'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `call'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `block in trace'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:17:in `block in instrument'
        from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:16:in `instrument'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/lib/language_pack/instrument.rb:35:in `trace'
        from /tmp/buildpacks/3de781907107e5d281f03f8dc06414be/bin/compile:18:in `<main>'
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223

FAILED
BuildpackCompileFailed

@amaltson  i'm not surprised at this.  lattice had custom logic around passing the cluster proxy configuration to the CLI so it could set environment variables appropriately during staging and app runtime.  now we're relying on cf, and it's probably an atypical configuration to put a CF behind a proxy.
i don't have an estimate when we'll get to look at this with the holidays coming up, but we'll start looking into proxy support on microPCF.

@davidwadden I've found that if I upload the offline buildpack into microPCF it actually works fine. Thanks!

I'll leave the issue open to track proxy work on microPCF.

i'm going to go ahead and close this for now as we're not considering proxy support in the near term.  instead, we're looking to make MicroPCF match PCF, so we'll probably address working offline (all the buildpacks are currently offline already) before supporting proxies.

Sounds good, offline buildpacks work great.


Extend cmake to generate find module and optionally build shared lib

After 'make install' you can use the jwt-cpp library in another CMake project as follows:

find_package(Jwt "1.1.0" REQUIRED)
add_executable(foo foo.cpp)
target_link_libraries(foo Jwt::jwt)
If jwt-cpp has been installed in a non-standard location than you will have to include the install path in CMAKE_PREFIX_PATH.

When you add option -DBUILD_SHARED_LIBS=ON to the CMake invocation, jwt-cpp will be built as a shared library.

Question: is there a reason that jwt-cpp searches for OpenSSL with custom commands i.s.o. using the standard CMake find module FindOpenSSL.cmake ?
best regards,
Winfried

Correction to the pull-request comment:
If jwt-cpp has been installed in a non-standard location than you will have to include the install path in CMAKE_PREFIX_PATH.

Is it possible to lower the required cmake version? It breaks the integration

Yes, it will probably work from CMake 3.0 and maybe even with the last release of the 2.x cycle. However I don't have such old came versions installed and thus was not able to test with cmake < 3.4.
In the integration build log I see you use cmake 3.2.2. I will download that release from cmake.org and check that this change will work with it.

After testing I have changed the minimum cmake version to 3.2

Thank you!


[TEST ONLY] use test TF branch

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Closing as this was for test alone.


cert-shifter starts failing is not run within 24 hours of an update

The find used by cert-shifter checks for changes which occurred in the past 24 hours (1 d)
see https://github.com/dlangille/anvil/blob/master/cert-shifter#L31
DIRS=`${FIND} ${CERT_SRC} -mtime -1 -type d -d 1`

I had a power outage and the server did not come back up within that 1 day period.
I suspect the power outage occurred after the certs had been renewed, but before they were copied over to the destination.
I solved it by changing from -mtime 1 to -mtime 70
Why 70? Why so large? This thing takes a long time to surface. You wouldn't notice until cert renewal time comes around (these are valid for 90 days). When my Nagios check start saying < 28 days left.

I think the best solution: change -mtime 1 to -mtime N where N is how many days you think you might be powered off.
This means any time you run the script, changes to a script are copied over at least three times:

within the first day
on the second day
on the third day

I think this is a better solution. It uses the mtimes on the fullchain.cer file, then invokes dirname. The result is the same higher-level directory names which the original find was supposed to locate.
DIRS=`${FIND} ${CERT_SRC} -mtime -10 -type f -d 2 -name fullchain.cer -exec dirname {} \; `

See also: https://twitter.com/DLangille/status/1148663213346742272


scrollBottom() core function does not work when most recently visible message has style display: none

need to write a new function for this, possibly also setting display: none messages to visibile: false or something to make sorting possible without pain. then add a new event listener to the jump to bottom button.

turns our the visible property idea is nonsense 🤔 back to the drawing board

of course, using flags would be the way to go here, except i refuse to do that.


Feature Release and Clean Up for v1.0.o

The big push to v1.0!

adds #29
fixes #53
closes #50
closes #51

Current coverage is 100% (diff: 100%)

Merging #54 into master will not change coverage

@@           master   #54   diff @@
===================================
  Files           5     6     +1
  Lines         162   191    +29
  Methods        24    27     +3
  Messages        0     0
  Branches       17    15     -2
===================================
+ Hits          162   191    +29
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update eed7651...7496f6d

Changes Unknown when pulling 7496f6dfe99e94ce72d52e0317dcedc955c9bf0e on major-release into ** on master**.


Aircraft somehow 'crash' and stay on the radar

For some reason, I've just had this aircraft in the simulator that was cleared for takeoff, and for some reason just randomly 'crashed'.
http://prntscr.com/bedekh
The aircraft was climbing, and all of a sudden, it was at 0 feet at 0 knots.
Error console is here: http://prntscr.com/bedfl8
I can also assure you that all of the SIDS have ICAOs!
EDIT: After 7 minutes, for some reason I'm able to clear it for takeoff from it's current position too...

I'd have a close look at the SID he was using, as it may be that the fms thought there was an altitude and speed to comply with, but they weren't given a value, so it assumed zero... that theory would explain the behavior at least. Strange though.

@indianbhaji Are you able to reproduce this?

I can't say, this issue is very rare it seems.

Closing due to lack of reproducibility. :disappointed:


Refactoring

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #32   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         111    107    -4
=====================================
- Hits          111    107    -4

Impacted Files
Coverage Δ

easyfile/core.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


feat: renames package to aind_data_transfer

I'll rename the repo to aind-data-transfer after this is merged

I'll also re-enable the github version bump action after this is merged


[Language Text] Mitigation for modifiedOn

Mitigation for the incorrect name used in for the lastUpdatedDateTime property in the job states. The service currently returns it as lastUpdateDateTime instead.

API change check
API changes are not detected in this pull request.


modify ui

If I want to modify ui, what should I do?
I modify locally harbor/src/ui_ng/src/app/base/navigator/navigator.component.html and make install, but it does not work!
ui using ui_ng?
why?
I use harbor 1.2.2

@fenghui2013
Can we know which parts you need to change? All the UI code is in the ui_ng folder. And some of the UI components are built into lib folder as sharable components which are imported into harbor by npm package.

thank you for your answer. I knew how to build.
The target "compile_clarity" in Makefile failed when running "make install".


NIFI-1020

Bumping Kafka API version to prevent PutKafka from writing to only one partition.

Looks good.  Did some testing to confirm Get/Put continued to work as anticipated.  Thanks!


Calculate Accessibility Matrix and Calculate Travel Time Statistics : Type Error

I Don't know what to do with this error or the source of this error. Any suggestion would be really helpful.

It looks like the tool's validation is freaking out about something. It is likely a bug.
Can you tell me what version of ArcMap you're using? I will see if I can reproduce the problem and fix it.

Thanks for your reply. I am using Arcmap version 10.5.
Pranav Gairola
Research Scholar
Department of Civil Engineering
Indian Institute of Technology Delhi
New Delhi-110016
On Sat, 13 Feb 2021, 21:29 Melinda Morang<EMAIL_ADDRESS>wrote:

It looks like the tool's validation is freaking out about something. It is
likely a bug.
Can you tell me what version of ArcMap you're using? I will see if I can
reproduce the problem and fix it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Esri/public-transit-tools/issues/150#issuecomment-778637673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMFYTR5Z4UGIN6S6NHQZLSTS62OWHANCNFSM4XSAIKLQ
.

Hmm.  I cannot reproduce this problem in ArcMap 10.8.1, which is what I have installed right now.  I can spin up a machine with 10.5 if needed.  However, I remembered that another user encountered a similar problem before when running the tool in ArcGIS Pro, which makes me think the problem is not version specific.
https://community.esri.com/t5/arcgis-for-public-transit/calculate-accessibility-matrix-error/m-p/447796
I could not reproduce the problem at that time either, and my best guess was that the user also had the BetterBusBuffers tool saved somewhere on their machine. BetterBusBuffers also has a function called allow_YYYYMMDD_day(), and it's almost as if the two tools are getting mixed up about whose function to call. I really have no idea how that would happen. My best idea at this point is for you to delete both BetterBusBuffers and Transit Analysis Tools from your machine, re-download them, and make sure they are saved to completely different folders.
Let me know if that helps...?

(If you do, in fact, have both of these tools on your machine currently, it would help me to know how/where you have them saved so maybe I can finally reproduce the problem and fix it.)

Yes, Initially I had BetterBusBuffers in the same place with Transit-Network-Analysis-Tool. But I had already gone through this thread you are referring to and I re-installed both the tools and placed them in different folders of my PC.

Looks like you were right. Now when i closed my ArcMap and re-open it and  the tool seems to be working alright. Thanks for your help. I Really appreciate this.

That's very weird.  I...still don't really understand what happened, but I'm glad it's working now.

Probably you were right about mixing up of these tools in calling the same named function. As soon as I changed the directory of these tools, re-installed both tools and restart ArcMap, it worked like magic.
Thanks again!


nodeos tests don't shutdown nodeos when test fails.

this can cause subsequent tests to fail for environmental reasons
it is just poor test behavior to leave background processes running

@cj-oci is this done?

Yes
On Tue, Jul 3, 2018 at 4:37 AM Andrianto Lie<EMAIL_ADDRESS>wrote:

@cj-oci https://github.com/cj-oci is this done?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EOSIO/eos/issues/2009#issuecomment-402079326, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AgG7CdH-ATwvgvv72cgaxcdLLm7TK_fEks5uCztYgaJpZM4TCke1
.

Thanks for the confirmation!


Installation fails on Windows/Jruby <IP_ADDRESS>

Trying to upgrade from rails 5 to a new installation, installed jruby last version <IP_ADDRESS> and trying to
gem install sass-rails
returns
C:\asset\applications\asestero_new>gem install sass-rails
Building native extensions. This could take a while...
ERROR:  Error installing sass-rails:
ERROR: Failed to build gem native extension.
current directory: C:/asset/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/sassc-2.

4.0/ext
C:/asset/jruby-<IP_ADDRESS>/bin/jruby.exe -I C:/asset/jruby-<IP_ADDRESS>/lib/ruby/stdlib -
r ./siteconf20221110-8908-oh7pcn.rb extconf.rb
creating Makefile
current directory: C:/asset/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/sassc-2.4.0/
ext
make DESTDIR= clean
current directory: C:/asset/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/sassc-2.4.0/
ext
make DESTDIR=
make failedCannot run program "make" (in directory "C:\asset\jruby-<IP_ADDRESS>\lib\r
uby\gems\shared\gems\sassc-2.4.0\ext"): CreateProcess error=2, The system cannot
find the file specified
Gem files will remain installed in C:/asset/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/g
ems/sassc-2.4.0 for inspection.
Results logged to C:/asset/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/extensions/univers
al-java-1.8/2.6.0/sassc-2.4.0/gem_make.out

The problem is the requirement of sassc-rails, if I delete that requirement the gem is installed (but it does not work because it still requires sassc for some reason). I have version 5.0.6 and it does not require sassc. That was introduced in 6.0.0 beta 2 (why? jruby was forgotten?)

SassC requires a C compiler.
install a devkit https://rubyinstaller.org/downloads/
run ridk enable
jruby -S gem install sassc
this way you should be able to install and use the gem on JRuby + Windows. see https://github.com/sass/sassc-ruby/issues/182
there are ways that could improve the situation and remove the requirement, but it's unlikely to ever happen since the gem isn't maintained anymore.


Can't get directives to work

Sorry, but the explanation about directives lacks informations about the module and the directives file contents and where to put them or how to load them.
I've no luck, trying to get it work. :(

@Jehu Did you manage to get it working?

@urecio nope. we used another generator.

What other generator did you find that works with AngularJS directives?  I'm starting to incorporate directives into my style guide and am having problems also and agree that the documentation is lacking.

@jaynnasc we've done it with fabricator. With fabricator we don't need AngularJS directives.

@Jehu Would you mind leaving this ticket open?  I still need it to be fixed.

@jaynnasc ok, i reopen this.


1.15.1-rc.1 is throwing Uncaught object "[object Object]" was thrown. Throw Error instead.

What is your Test Scenario?

The test is clicking a button. Currently I get
Uncaught object "[object Object]" was thrown. Throw Error instead.
https://hub.docker.com/layers/testcafe/testcafe/1.15.1-rc.1/images/sha256-eff6bea6e23556bd041d47a3a02b74a8fd123710d4c2b21f0785a0d93ffed6d6?context=explore
What is the Current behavior?

rajbalaebail@Rajs-MacBook-Pro e2e-tests % docker run -v /Users/rajbalaebail/amount-repos/e2e-tests/testcafe:/tests -it testcafe/testcafe:rc chromium /tests/tests/uil/apply/eloan-tests/personal-application-page/personal-application-page-tests.spec.js
 Running tests in:
 - Chrome 91.0.4472.164 / Linux 0.0

Personal application page tests - eLoan
App ID: 49
 ✖ eLoan - Step 1 - PA Page: Verify person age <18 is declined

   1) Uncaught object "[object Object]" was thrown. Throw Error instead.

      Browser: Chrome 91.0.4472.164 / Linux 0.0

What is the Expected behavior?

rajbalaebail@Rajs-MacBook-Pro e2e-tests % docker run -v /Users/rajbalaebail/amount-repos/e2e-tests/testcafe:/tests -it testcafe/testcafe:1.15.0 chromium /tests/tests/uil/apply/eloan-tests/personal-application-page/personal-application-page-tests.spec.js

 Running tests in:
 - Chrome 91.0.4472.124 / Linux 0.0

Personal application page tests - eLoan
App ID: 51
 ✓ eLoan - Step 1 - PA Page: Verify person age <18 is declined

What is your web application and your TestCafe test code?

Execute this command...
See the error...

Your Environment details:

testcafe version:
node.js version:
command-line arguments:
browser name and version:
platform and version:
other:

Looks like this is happening when you try to press the TAB button.
import { Selector, t } from 'testcafe';

fixture('DevExpress/testcafe/issues/6405')
  .page('https://eloan.stg.internal.amount.com/apply')

test('test', async t => {
  console.log('here')
  await t.pressKey('tab')
  console.log('here 1')
})

rajbalaebail@Rajs-MacBook-Pro e2e-tests % docker run -v /Users/rajbalaebail/amount-repos/e2e-tests/testcafe:/tests -it testcafe/testcafe:rc chromium /tests/tests/uil/apply/eloan-tests/personal-application-page/test.spec.js
 Running tests in:
 - Chrome 91.0.4472.164 / Linux 0.0

 DevExpress/testcafe/issues/6405
here
 ✖ eLoan - Step 1 - PA Page: Verify fields, field errors, tooltips, dropdowns

   1) Uncaught object "[object Object]" was thrown. Throw Error instead.

      Browser: Chrome 91.0.4472.164 / Linux 0.0

 1/1 failed (19s)

I was not able to reproduce the issue. It looks like the website is unreachable for me. Please provide us with access to your website or prepare a separate sample. Thank you in advance.
If you need to share some credentials to us you can send it at<EMAIL_ADDRESS>Please note that our policy prevents us from accessing internal resources without prior written approval from a site owner. If we need to access non-public parts of your website or pass through authorization pages, please ask the website owner to send us (support@devexpress.com)) a written confirmation. It must permit DevExpress personnel to remotely access the website and its internal resources for research/testing/and debugging purposes.

@AlexKamaev you can try this on https://www.my.eloan.com/apply instead.

I was able to reproduce the issue. Thank you for your assistance.


Inconsistent  'answers' types in the nq_reader_train data

I found that a few 'answers' which are distantly supervised have 'dict' types while most of the 'answers' have 'list' types as values.
Example.

Thank you for reporting. We will fix it.


Badge component attributes only work partially in pre- and suffix actions inside tables

Package
filament/filament
Package Version
v3.2.28
Laravel Version
10.43.0
Livewire Version
v3.4.4
PHP Version
8.3.1
Problem description
Adding a Badge component inside a ->prefix() or ->suffix() (via view or Blade::render) only accepts attributes partially. For example it accepts color, size and class whereas icon or tooltip will be ignored. No errors thrown either. If you were to add a heroicon that does not exist, it will throw and error, so it recognizes those attributes.

Expected behavior
To work the same as it does in ->description (and generally anywhere else)
Steps to reproduce
Return a view with a badge component inside to either the prefix or suffix of TableColumn::
Reproduction repository
https://github.com/dissto/filament-badge-issue
Relevant log output
No response

The reproduction repository does not appear to reproduce the problem. Please point me to the place in the repository where it does, or add it, or we will need to close this

@dissto, could you check if this is still an issue on the 3.x branch?
Might have been related to https://github.com/filamentphp/filament/pull/11346.


SDK-47: Add support for creating haddop2 cluster

use_hadoop2 flag, to allow creation of hadoop2 clusters.

Squash merged: https://github.com/qubole/qds-sdk-java/commit/4d583df8aaaa98630614c806dd58921427b93cd6


Fix most ports being built without optimizations (e.g. -O3) on *NIX

Issue
Using vcpkg I built OpenCV on Linux (Ubuntu 18.10), but I was highly surprised with OpenCV's plain horrible performance for its release builds.
All I did was:
./vcpkg install opencv

After some debugging it turns out that OpenCV was built without ANY kind of optimization flags for the release build.
Same for libjpeg-turbo, libtiff etc. though. :warning:
Fix
tl;dr: See down below in section "Commit message"
In your local vcpkg setup you'll find a folder at:
./downloads/tools/cmake-*/cmake-*/share/cmake-*/Modules/Compiler

This folder contains various compiler-specific definitions for those that CMake supports.
For gcc (i.e. GNU.cmake) for instance this entails the following very important definition:
string(APPEND CMAKE_${lang}_FLAGS_RELEASE_INIT " -O3 -DNDEBUG")

But those flags only apply if the user hasn't set the corresponding (e.g.) CMAKE_${lang}_FLAGS_RELEASE variable yet, which we did though using e.g. set(CMAKE_CXX_FLAGS_RELEASE ...) etc.
The optimal solution would be that we only use the _INIT variables from now on like above in our toolchains, but unfortunately this doesn't guarantee that the VCPKG_CXX_FLAGS_RELEASE flags take precedence anymore.
(In fact, as can be seen above, CMake appends -O3 -DNDEBUG and would thus overwrite whatever you set in VCPKG_CXX_FLAGS_RELEASE.)
So as far as I can see, without breaking backwards compatibility, the only solution is the one I'm proposing in this PR. :slightly_smiling_face:
P.S.: I know this might sound rude, but I am seriously whondering why no one noticed the horrendous performance of libraries built with vcpkg on *NIX before... :thinking:
Commit message
Don't set CMAKE_*_FLAGS* unless necessary

If a CMAKE_*_FLAGS* variable is set, cmake's compiler-specific
toolchain settings will not be applied.
The way the previous scripts/toolchain/*.cmake code was written
these flags where set to empty or whitespace-only strings and
caused cmake to not apply any compiler-specific settings,
like e.g. the common "-O3 -DNDEBUG" for release builds.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: lhecker sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks a bunch for the PR and noticing this issue!
We very recently also found this due to a build break in release by not setting -DNDEBUG (https://github.com/Microsoft/vcpkg/issues/4731, though I failed to record the specific details).
I completely concur with your analysis about this being the only solution that doesn't change behavior of VCPKG_CXX_FLAGS (save the fact that it would "overwrite" -fPIC, but see below).
However, I think in this case, it is desirable to have VCPKG_CXX_FLAGS apply to CMAKE_CXX_FLAGS_INIT instead of CMAKE_CXX_FLAGS. The intention is really to have a mechanism similar to $CXXFLAGS[1] where you can just add a small tweak to the build; for users who need to totally replace everything, we'd recommend they write a proper full toolchain file.
I've been testing dev/roschuma/4731[2], does that look like it would also solve the issue to you? (Edit: aha, I accidentally skipped freebsd!)
[1] In the core CMake files, $CXXFLAGS is applied to XYZ_INIT as well https://github.com/Kitware/CMake/blob/master/Modules/CMakeCXXInformation.cmake#L200
[2] https://github.com/Microsoft/vcpkg/commit/cc20d43686217009f94c60dd8c54290a5e76aa61

@ras0219-msft Yes that branch would work as well. 🙂
Since you said that you're fine with the slight behavior change of the VCPKG_*_FLAGS* variables I've taken the liberty to rebase my PR from e429aa0 to 390a517, which contains my original attempt.
Incidentially this is then almost identical to your branch.
So please feel free to close this PR and merge your changes if you want to. 🙂

Fixed in 4d1fd42fca46f4c4dfe35011c8c96ff941db3ca6 :point_right: Closing.
cc: @ras0219-msft


System error in /sys/fs/cgroup/cpu,cpuactt

I'm on Debian Unstable with the docker.io images (debian no longer repackages). This is what happens when I try to run any image:
~ docker run -it debian:jessie
Error response from daemon: Cannot start container c35192b15227f0a93170415f688bd7ff974aaf7af63a168398d865d857ed2f75: [8] System error: open /sys/fs/cgroup/cpu,cpuacct/init.scope/system.slice/docker-c35192b15227f0a93170415f688bd7ff974aaf7af63a168398d865d857ed2f75.scope/cpu.shares: no such file or directory

and indeed, that structure does not exist on my directory
~ ls /sys/fs/cgroup/cpu,cpuacct/init.scope/
cgroup.clone_children  cgroup.procs  cpuacct.stat  cpuacct.usage  cpuacct.usage_percpu  cpu.shares  notify_on_release  tasks

i.e. no system.slice.
I'm running a very new linux kernel, has the sys directory perhaps changed to the point that docker breaks?

~ uname -a
Linux Samskara 4.1.0-2-amd64 #1 SMP Debian 4.1.6-1 (2015-08-23) x86_64 GNU/Linux

~ docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64

~ docker -D info
Containers: 3
Images: 13
Storage Driver: devicemapper
 Pool Name: docker-8:5-27000835-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 1.601 GB
 Data Space Total: 107.4 GB
 Data Space Available: 105.8 GB
 Metadata Space Used: 1.978 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Data loop file: /mnt/archive/docker/devicemapper/devicemapper/data
 Metadata loop file: /mnt/archive/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.104 (2015-08-10)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.0-2-amd64
Operating System: Debian GNU/Linux stretch/sid (containerized)
CPUs: 4
Total Memory: 15.62 GiB
Name: Samskara
ID: EM6A:FAHK:YV4K:3AUD:LWIU:RJ2Q:ZPOP:Q4C7:IIAX:ZIR6:P5UY:67GB
Username: fommil
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

that auto response is very useful... are you using a service for that or did you hack something up? (I want to use it for my projects if it is possible to customise it to only respond once to a submitter to avoid spamming people)

Hi @fommil
If you are on Debian Unstable, there is a chance you have just upgraded to systemd 226, which introduces the init.scope and places init (pid 1) inside it:
$ cat /proc/1/cgroup
9:cpuset:/
8:memory:/
7:devices:/init.scope
6:cpu,cpuacct:/
5:perf_event:/
4:net_cls,net_prio:/
3:freezer:/
2:blkio:/
1:name=systemd:/init.scope

source: http://news.softpedia.com/news/systemd-226-adds-new-features-to-the-dhcp-implementation-of-networkd-more-491265.shtml
I have the same error message as you.

Downgrading all systemd components to 225 on Debian resolves the issue.
Bug #798778 opened against debian sid's systemd package.
Long term, docker should handle systemd's new init.scope.  4 days notice is insufficient :-).
Short term, no distribution should release new versions of systemd that make major changes to cgroup space without testing them against other packages that use cgroup space first.

Agreed!
Romain

On 12 Sep 2015, at 16:48, Chris Dukes<EMAIL_ADDRESS>wrote:
Downgrading all systemd components to 225 on Debian resolves the issue.
Bug #798778 opened against debian sid's systemd package.
Long term, docker should handle systemd's new init.scope. 4 days notice is insufficient :-).
Short term, no distribution should release new versions of systemd that make major changes to cgroup space without testing them against other packages that use cgroup space first.
—
Reply to this email directly or view it on GitHub.

You can use fs cgroups if you want, they're much more stable and has more features.
--exec-opt native.cgroupdriver=cgroupfs to daemon flags.

Alexander,
Interesting.  That does appear to resolve the issue.
Thank you.
I have questions.

If cgroupfs is preferable to systemd, why is the default to check for
systemd then fallback to cgroupfs?
Has systemd done other experiments with cgroup space with similar
fallout?
If not, what were the other historical instabilities?
What are the additional features provided by cgroupfs as the driver?
https://docs.docker.com/reference/commandline/daemon/
is somewhat silent on the above questions.

I see the differences in /sys/fs/cgroup between the two.  But the context
on the nature of the differences eludes me.
Again, Thank You.
On Sat, Sep 12, 2015 at 11:54 PM, Alexander Morozov <
<EMAIL_ADDRESS>wrote:

You can use fs cgroups if you want, they're much more stable and has more
features.
--exec-opt native.cgroupdriver=cgroupfs to daemon flags.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16256#issuecomment-139842930.

--exec-opt native.cgroupdriver=cgroupfs works for me! :-)

@LK4D4 are there changes to be made, or docs to be added w.r.t https://github.com/docker/docker/issues/16256#issuecomment-139844449? I don't know the answers to those, but let me know if the documentation should have extra information about that :+1:

It would be good if this setting was automatically enabled for relevant systems

@fommil feel free to create a separate issue for that, if you can clearly describe what you think needs to be done (and please add a link to this issue as well, for reference).

Or libcontainer should handle the fact that with systemd >225 cgroups paths are different?

Hi, i'm running in the same problem (debian sid) how/whre should I use the option :   --exec-opt native.cgroupdriver=cgroupfs ?

/etc/default
On Sep 14, 2015 2:03 PM, "epifanio"<EMAIL_ADDRESS>wrote:

Hi, i'm running in the same problem (debian sid) how/whre should I use the
option : --exec-opt native.cgroupdriver=cgroupfs ?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16256#issuecomment-140161308.

I tried .. that's what i got :
service docker stop
service docker start
docker daemon --exec-opt native.cgroupdriver=cgroupfs
docker: 'daemon' is not a docker command.
See 'docker --help'.

@epifanio the docker daemon command was added in docker 1.8, so either upgrade to docker 1.8, or use docker -d, which was the "old" way of starting the docker daemon

@thaJeztah , thanks!
docker -d --exec-opt native.cgroupdriver=cgroupfs
works fine (eventually I'll upgrade my docker installation).
Question, i runned docker -d ... from a standard ssh shell on my server using nohup to avoid to kill the demon when i close the ssh session. How can i make those changes permanent, so that I don't need to issue it and leave supervisord to do the job?

btw, it's still an issue, it breaks oom for systemd as well. I'm not sure from where this init.scope crap is came, because mine devices is in user.slice, but inside container it's mounted as /init.scope/system.slice

Take a peek at /proc/1/cgroup.
devices and blkio are in /init.scope.
In systemd 225 and older, those are in /.
Suspicion:
native.cgroupdriver=systemd uses systemd's cgroups in creating paths for
docker cgroups.
The release notes for systemd 226 does not address the why.
systemd/init's metrics are easy to track when fenced in a separate cgroup
hierarchy.
I have not rebooted since enabling memory cgroups and swap accounting, but
I suspect I will be pleasantly surprised.
On Tue, Sep 15, 2015 at 12:42 PM, Alexander Morozov <
<EMAIL_ADDRESS>wrote:

btw, it's still an issue, it breaks oom for systemd as well. I'm not sure
from where this init.scope crap is came, because mine devices is in
user.slice, but inside container it's mounted as /init.scope/system.slice
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16256#issuecomment-140457533.

@cdd-aix funny. Seems like we're messed /proc/self with /proc/1 somehow.

Seems no such issue exists in Fedora rawhide:
rpm -q docker systemd
docker-1.9.0-2.gitf8950e0.fc24.x86_64
systemd-226-1.fc24.x86_64
cat /proc/1/cgroup
10:hugetlb:/
9:memory:/init.scope
8:cpuset:/
7:net_cls,net_prio:/
6:perf_event:/
5:devices:/init.scope
4:blkio:/init.scope
3:freezer:/
2:cpu,cpuacct:/init.scope
1:name=systemd:/init.scope
docker run fedora echo hi
hi

docker -d --exec-opt native.cgroupdriver=cgroupfs works on current Debian/Unstable.

The issue only seems to manifest when using -c (though I guess some other options that utilize cgroups would also cause the issue).
% docker version
Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Sat Aug 15 17:29:10 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Sat Aug 15 17:29:10 UTC 2015
 OS/Arch:      linux/amd64

 % pacman -Qi systemd
Name           : systemd
Version        : 226-1
Description    : system and service manager
Architecture   : x86_64
URL            : http://www.freedesktop.org/wiki/Software/systemd
Licenses       : GPL2  LGPL2.1
Groups         : None
Provides       : nss-myhostname  systemd-tools=226  udev=226
Depends On     : acl  bash  dbus  iptables  kbd  kmod  hwids  libcap  libgcrypt  libsystemd  libidn  lz4  pam  libseccomp  util-linux  xz
Optional Deps  : cryptsetup: required for encrypted block devices [installed]
                 libmicrohttpd: remote journald capabilities
                 quota-tools: kernel-level quota management
                 systemd-sysvcompat: symlink package to provide sysvinit binaries [installed]
                 polkit: allow administration as unprivileged user [installed]
Required By    : accountsservice  android-udev  bluez-utils  chromium  colord  device-mapper  dhcpcd  docker  gnome-system-monitor  lib32-systemd  libgusb  libinput  libpulse
                 libusb  lvm2  media-player-info  mesa  mkinitcpio  netctl  pcmciautils  pcsclite  plymouth-legacy  polkit  python-pyudev  qt5-base  qtwebkit  rtkit  subversion
                 systemd-sysvcompat  udisks2  upower  xf86-input-evdev
Optional For   : None
Conflicts With : nss-myhostname  systemd-tools  udev
Replaces       : nss-myhostname  systemd-tools  udev
Installed Size :  27.24 MiB
Packager       : Dave Reisner<EMAIL_ADDRESS>Build Date     : Tue 08 Sep 2015 01:57:54 PM EDT
Install Date   : Sun 20 Sep 2015 03:17:27 PM EDT
Install Reason : Installed as a dependency for another package
Install Script : Yes
Validated By   : Signature

 % uname -r
4.1.6-1-ARCH

 % docker run --rm ubuntu echo hi
hi

 % docker run --rm -c 1 ubuntu echo hi
Error response from daemon: Cannot start container c44478b6b516c75fa72e090e61db49a08453f25c7fe59e877e641214dc3dd721: [8] System error: open /sys/fs/cgroup/cpu,cpuacct/init.scope/system.slice/docker-c44478b6b516c75fa72e090e61db49a08453f25c7fe59e877e641214dc3dd721.scope/cpu.shares: no such file or directory

[root@alarm services]# docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/arm
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/arm

uname -r
4.2.0-1-ARCH

Same error

On arch, the fd it is looking for exists at /sys/fs/cgroup/cpu,cpuacct/system.slice/docker-blahblah/cpu.shares instead of /sys/fs/cgroup/cpu,cpuacct/init.scope/system.slice/docker-blahblah/cpu.shares
It's there, just not under the init.scope directory

docker -d --exec-opt native.cgroupdriver=cgroupfs works on Arch.
docker
$ docker version
Client:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.5.1
 Git commit:   0a8c2e3-dirty
 Built:        Mon Sep 14 12:09:36 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.5.1
 Git commit:   0a8c2e3-dirty
 Built:        Mon Sep 14 12:09:36 UTC 2015
 OS/Arch:      linux/amd64

kernel
uname -a
Linux e6050a 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64 GNU/Linux

systemd
$ pacman -Qi systemd
Name           : systemd
Version        : 226-1
Description    : system and service manager
Architecture   : x86_64
URL            : http://www.freedesktop.org/wiki/Software/systemd
Licenses       : GPL2  LGPL2.1
Groups         : None
Provides       : nss-myhostname  systemd-tools=226  udev=226
Depends On     : acl  bash  dbus  iptables  kbd  kmod  hwids  libcap  libgcrypt  libsystemd  libidn  lz4  pam  libseccomp  util-linux  xz
Optional Deps  : cryptsetup: required for encrypted block devices [installed]
                 libmicrohttpd: remote journald capabilities
                 quota-tools: kernel-level quota management
                 systemd-sysvcompat: symlink package to provide sysvinit binaries [installed]
                 polkit: allow administration as unprivileged user [installed]
Required By    : accountsservice  android-udev  chromium  colord  device-mapper  dhcpcd  docker  lib32-systemd  libgusb  libinput  libmbim  libpulse  libusb  lvm2  media-player-info  mesa  mkinitcpio  modemmanager  netctl  pcmciautils
                 polkit  qt5-base  qtwebkit  rtkit  subversion  systemd-sysvcompat  udisks2  upower  xf86-input-evdev
Optional For   : None
Conflicts With : nss-myhostname  systemd-tools  udev
Replaces       : nss-myhostname  systemd-tools  udev
Installed Size :  27.24 MiB
Packager       : Dave Reisner<EMAIL_ADDRESS>Build Date     : Tue 08 Sep 2015 02:57:54 PM BRT
Install Date   : Mon 21 Sep 2015 07:45:44 AM BRT
Install Reason : Installed as a dependency for another package
Install Script : Yes
Validated By   : Signature

Note that on Debian testing (with systemd), you have to add the option --exec-opt native.cgroupdriver=cgroupfs in /lib/systemd/system/docker.service:
...
[Service]
ExecStart=/usr/bin/docker -d -H fd:// --exec-opt native.cgroupdriver=cgroupfs
...

You really should be making that change in "/etc/default/docker" not directly to the systemd service file. In /etc/default/docker add the argument to the DOCKER_OPS variable.

@dubwoc agreed, however note that the /etc/default/docker file is no longer used in the newer packages; using drop-ins is the recommended method. See https://docs.docker.com/articles/systemd/#custom-docker-daemon-options for reference

Well, in the package http://get.docker.io/ubuntu/ , /lib/systemd/system/docker.service does not declare /etc/default/docker as an environment file — so its settings are not used anymore.

@Chris00 see the article I linked, which contains instructions on how to override the default settings, or add an environment file, without changing the default docker.service

@thaJeztah Right. I read your linked page more carefully and it suffices indeed to add a file /lib/systemd/system/docker.service containing:
[Service]
ExecStart=
ExecStart=/usr/bin/docker -d -H fd:// --exec-opt native.cgroupdriver=cgroupfs

Thanks.

I have this problem and can not resolve it. I run Debian Testing (kernel 4.2.0-1-amd64) and as a result have Docker 1.7.1~dfsg1-1 . Going to packages.debian.org it looks like that's the absolute latest version; it's the same version for Debian Unstable.

@Corwin7 yeah.. I know the feeling :smile_cat:

@Corwin7 In Debian just edit /etc/default/docker. I have:
DOCKER_OPTS="--dns <IP_ADDRESS> --dns <IP_ADDRESS> --exec-opt native.cgroupdriver=cgroupfs"
And works fine.

I also came across this issue using Arch Linux. Passing --exec-opt native.cgroupdriver=cgroupfs to the Docker daemon fixed the issue. Downgrading from system-d 227-1 to 225-3 also fixed the problem so system-d is definitely the problem (226 is also broken)
I had a quick look at system-d's NEWS file was version 226. This looks interesting
https://github.com/systemd/systemd/blob/1e0adaa45d2c1a300199069bfdeb494281b54086/NEWS#L252
        * systemd now optionally supports the new Linux kernel
          "unified" control group hierarchy. If enabled via the kernel
          command-line option 'systemd.unified_cgroup_hierarchy=1',
          systemd will try to mount the unified cgroup hierarchy
          directly on /sys/fs/cgroup. If not enabled, or not
          available, systemd will fall back to the legacy cgroup
          hierarchy setup, as before. Host system and containers can
          mix and match legacy and unified hierarchies as they
          wish. nspawn understands the $UNIFIED_CROUP_HIERARCHY
          environment variable to individually select the hierarchy to
          use for executed containers. By default, nspawn will use the
          unified hierarchy for the containers if the host uses the
          unified hierarchy, and the legacy hierarchy otherwise.
          Please note that at this point the unified hierarchy is an
          experimental kernel feature and is likely to change in one
          of the next kernel releases.  Therefore, it should not be
          enabled by default in downstream distributions yet. The
          minimum required kernel version for the unified hierarchy to
          work is 4.2. Note that when the unified hierarchy is used
          for the first time delegated access to controllers is
          safe. Because of this systemd-nspawn containers will get
          access to controllers now, as will systemd user
          sessions. This means containers and user sessions may now
          manage their own resources, partitioning up what the system
          grants them.

I tried passing systemd.unified_cgroup_hierarchy=0 as a kernel parameter when using system-d 227 but unfortunately I still experienced the issue :(

also see https://github.com/docker/docker/issues/16238

fedora rawhide seems to have the same issue btw (need to specify -c):
[root@localhost ~]# docker run -c 2 busybox echo hello
[  738.765697] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[  738.921473] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[  738.952694] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[  738.955775] device veth955a37f entered promiscuous mode
[  738.956541] IPv6: ADDRCONF(NETDEV_UP): veth955a37f: link is not ready
[  738.988624] eth0: renamed from veth1f32ef3
[  738.989210] IPv6: ADDRCONF(NETDEV_CHANGE): veth955a37f: link becomes ready
[  738.989777] docker0: port 2(veth955a37f) entered forwarding state
[  738.990189] docker0: port 2(veth955a37f) entered forwarding state
[  739.003745] docker0: port 2(veth955a37f) entered disabled state
[  739.006178] veth1f32ef3: renamed from eth0
[  739.008221] docker0: port 2(veth955a37f) entered disabled state
[  739.008776] device veth955a37f left promiscuous mode
[  739.009252] docker0: port 2(veth955a37f) entered disabled state
Error response from daemon: Cannot start container a76b4423b7d02ef76c68eae8f6d9263ae06cd0406fe4338575888da425d88b73: [8] System error: open /sys/fs/cgroup/cpu,cpuacct/init.scope/system.slice/docker-a76b4423b7d02ef76c68eae8f6d9263ae06cd0406fe4338575888da425d88b73.scope/cpu.shares: no such file or directory

@jeremyeder

:+1: --exec-opt native.cgroupdriver=cgroupfs works for CentOS 7.1 too. I wish docker-machine create would configure this automatically.

@johnjelinek we recently merged a PR to use if as default for docker 1.10; https://github.com/docker/docker/pull/17704 there's still some discussion on that though.
@LK4D4 should this be resolved with the changes in https://github.com/docker/docker/pull/17704?

hrmm .. I think I spoke too soon:
$ eval "$(docker-machine env --swarm my-swarm)"
$ docker run --rm redis

                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 3.0.5 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 1
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           http://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'
...

but then, with this docker-compose.yml:
web:
  build: .
  command: python app.py
  ports:
     - "5000"
  hostname: hello.weave.local
  environment:
     - "affinity:container!=app_web_*"
redis:
  image: redis
  hostname: redis.weave.local

it fails on the redis spin up:
$ docker-compose up -d --force-recreate
Recreating app_web_1
Recreating app_redis_1
ERROR: Cannot start container 3d19005a57b6237bddbd868d5f158126001eed9cbcc8027e0c330f3410b23d69: [8] System error: write /sys/fs/cgroup/memory/system.slice/docker/3d19005a57b6237bddbd868d5f158126001eed9cbcc8027e0c330f3410b23d69/memory.swappiness: invalid argument

All the swarm dockers are configured with --exec-opt native.cgroupdriver=cgroupfs.

@johnjelinek could that be related to https://github.com/docker/docker/issues/15159?

I don't think so -- I didn't unmount anything. The problem existed before I did the --exec-opt native.cgroupdriver=cgroupfs fix above. How can I troubleshoot further?

@johnjelinek hm actually, it looks like https://github.com/docker/docker/issues/17879, could be related to some API changes w.r.t default values, but not sure

I manually created this file: /sys/fs/cgroup/memory/system.slice/docker/8983d7cd867be40dcfd68747c79fac2f713243a979c3011dc1997dcdf8665150/memory.swappiness because that's what was complaining. When I did docker-compose up -d again, the 898...150 folder went missing. I guess it was deleted when the container was recreated.

@thaJeztah: I think you're right. It's likely #17879.

Just for the sake of completeness since I didn't see it explicitly stated, for recent versions of systemd that use init.scope for pid 1 libcontainer should not be including it in this join: https://github.com/opencontainers/runc/blob/master/libcontainer/cgroups/systemd/apply_systemd.go#L384

Instead of assuming things about systemd's cgroup behavior it could be asked instead:
$ busctl get-property org.freedesktop.systemd1 /org/freedesktop/systemd1/unit/system_2eslice org.freedesktop.systemd1.Slice ControlGroup
s "/system.slice"

That should work regardless of systemd version

@marineam are you still seeing this on docker 1.11.1? We're using runC now for the runtime, and a lot has changed since this was reported

This code is in runc and unchanged since docker 1.10 but I haven't actually tried docker 1.11 yet.


proxy_cache giving 404 on rewritten resources

Using <IP_ADDRESS> dynamic module and nginx 1.9.11 with proxy cache downstream configured https://developers.google.com/speed/pagespeed/module/downstream-caching for both

http://centminmod.com port 80
https://centminmod.com port 443

I am only getting sometimes 404 errors on rewritten pagespeed resources over centminmod.com port 443 but not port 80
From https://developers.google.com/speed/pagespeed/module/downstream-caching it gives example of purging on port 80, but what about if i purge on both port 80 and 443 for the same site ?

For example, if you're running a cache on port 80 that reverse proxies to your site on port 8080, then you'd need to tell PageSpeed to send its PURGE requests to port 80:

I have this set in pagespeed.conf
pagespeed DownstreamCachePurgeLocationPrefix http://localhost:80;
So i have to have separate DownstreamCacheRebeaconingKey key values for 80 and 443 port sites ?
should i place DownstreamCachePurgeLocationPrefix in each server context instead of pagespeed.conf
so in port 80 site
pagespeed DownstreamCachePurgeLocationPrefix http://localhost:80;
and port 443
pagespeed DownstreamCachePurgeLocationPrefix http://localhost:443;

nginx -V
nginx version: nginx/1.9.11
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
built with OpenSSL 1.0.2f 28 Jan 2016
TLS SNI support enabled
configure arguments: --with-ld-opt='-ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib' --with-cc-opt='-m64 -mtune=native -mfpmath=sse -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2' --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-http_stub_status_module --with-http_secure_link_module --with-openssl-opt=enable-tlsext --add-module=../nginx-module-vts --with-libatomic --with-threads --with-stream=dynamic --with-stream_ssl_module --with-http_gzip_static_module --add-module=../ngx_brotli --add-dynamic-module=../ngx_pagespeed-release-<IP_ADDRESS>-beta --with-http_sub_module --with-http_addition_module --with-http_image_filter_module=dynamic --with-http_geoip_module=dynamic --with-http_realip_module --add-module=../nginx-accesskey-2.0.3 --add-module=../nginx-http-concat-master --add-module=../ngx-fancyindex-0.3.6 --add-module=../ngx_cache_purge-2.3 --add-module=../ngx_devel_kit-0.2.19 --add-module=../set-misc-nginx-module-0.29 --add-module=../echo-nginx-module-0.58 --add-module=../redis2-nginx-module-0.12 --add-module=../ngx_http_redis-0.3.7 --add-module=../lua-nginx-module-0.10.1rc1 --add-module=../lua-upstream-nginx-module-0.04 --add-module=../lua-upstream-cache-nginx-module-0.1.1 --add-module=../nginx_upstream_check_module-0.3.0 --add-module=../openresty-memc-nginx-module-4f6f78f --add-module=../openresty-srcache-nginx-module-ffa9ab7 --add-module=../headers-more-nginx-module-0.29 --with-pcre=../pcre-8.38 --with-pcre-jit --with-http_ssl_module --with-http_v2_module --with-openssl=../openssl-1.0.2f

I also have set
pagespeed LoadFromFile "http://centminmod.com" "/path/to/web/root";
pagespeed LoadFromFile "https://centminmod.com" "/path/to/web/root";

FYI, if i disable https LoadFromFile, no page css/js get rewritten at all

Also if centminmod.com is on a cluster of servers behind route53 geo dns, would i need to set proxy_cache_purge to all the ips for all servers in the cluster ?
proxy_cache_purge PURGE from <IP_ADDRESS> ip2 ip3 ip4;
from

  # What servers should we accept PURGE requests from?  If PageSpeed isn't
  # running on the same server as your cache, list the IP(s) of the
  # PageSpeed machine(s) here.
  #
  # This requires rebuilding with the ngx_cache_purge module:
  #   https://github.com/FRiCKLE/ngx_cache_purge
  proxy_cache_purge PURGE from <IP_ADDRESS>;

@centminmod
Re: DownstreamCacheRebeaconingKey
I think you can share the same key for http and https.
Re: DownstreamCachePurgeLocationPrefix
Looks good to me, but I'm wondering what you are precisely doing for https. Are you de-encryping at the proxy and re-encryping when you go to the backend?
Re: LoadFromFile
If optimization doesn't work without LoadFromFile, pagespeed's http fetching is failing. You may have to use MapOriginDomain to point ngx_pagespeed to a server that it can use to fetch css/js from, or look at setting up https support. See these two documentation entries:
https://developers.google.com/speed/pagespeed/module/domains#mapping_origin
https://developers.google.com/speed/pagespeed/module/https_support
Re: proxy_cache_purge
If I understand correctly, each node in the cluster consists of a pagespeed-enabled webserver plus a proxy cache for the downstream caching feature. In that case, I think you need to set up proxy_cache_purge on each server{} block for each proxy cache to (only) accept purges from the pagespeed-enabled webserver that is running behind it. I can't see why purges would need to go across nodes in the cluster, but perhaps I am misinterpreting something?
Closing this issue - if you have any more questions, could we we take them to [ngx-pagespeed-discuss] (https://groups.google.com/forum/#!forum/ngx-pagespeed-discuss)?


[stable/cluster-autoscaler] Allow overriding the Capabilities.KubeVersion.GitVersion

Signed-off-by: Mike Tougeron<EMAIL_ADDRESS>What this PR does / why we need it:
This PR allows you to specify a Kubernetes version to target instead of using .Capabilities.KubeVersion.GitVersion. This is needed when Tiller is not in use (e.g., when using helm template)
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/mychartname])

Thanks! This looks good to me. Is this a pattern used in other charts too? I'd love to get some feedback from others, if possible.
/ok-to-test

I first saw this pattern in the prometheus-operator chart.

Sounds good. Will you please bump to 6.2.0 as this is a new feature? I'll approve after that. Thanks!

/lgtm
/approve

Thanks!


Will FutureProofing be getting an update soon?

@thomvis if you have no time for FutureProofing add me as collaborator
I can update it to swift 3 (after merging my PR https://github.com/Thomvis/FutureProofing/pull/6 of course)

Thanks for the offer @phimage. I've added you as a contributor to FutureProofing. Looking forward to Swift 3 support!

FutureProofing updated to swift 3 https://github.com/Thomvis/FutureProofing/commit/94d42367ab25938a13fe994cf9d6d0cf6ff16ab4
I create a file BrightFuture+FutureProofing.swift to be able to use generic Error into completion handler (It's inspired from PR #108)
Then I add @escaping to materialize function
Later some code could be reported to BrightFuture


remove duplicated code for find master session by handle

remove all duplicated code for finding master session by session handle.

Can one of the admins verify this patch?

@mrry I'm sorry for my mistake, I have fixed it.

Jenkins, test this please

Jenkins, test this please


Push the 0.6.0 gem?

I just switched off sql-parser to pg_query and it's perfect but I need the deparser. Is there anything blocking a 0.6.0 gem release that I could help with?

For sure, I'm planning for the release this week :)
Ideally I'd like to get https://github.com/lfittl/pg_query/pull/10 by @mme in - but its not a blocker, so happy to already shoot out a stable version tonight if it helps.

Awesome :)

@lfittl I might find time tomorrow morning to do it :)

Thanks for your help - pushed 0.6! :guitar:


action is outside the authorized scopes

It tried the mastodon-bot with twitter & my mastodon server (ver. 2.9.2) and get these message:
root@6b3c928e7c96:/app/mastodon-bot# ./mastodon-bot.cljs
This action is outside the authorized scopes

Unsure whether this message comes from twitter or mastodon ... but google search seems to know this message as mastodon client issue - correct?
I reviewed all my api keys, the mastodon api url is working e.g. for https://social.meissa-gmbh.de/api/v1/accounts/1.
The mastodon app has the permissions to read* write* follow push  ... any idea what could be wrong?

Hmm, it does seem like the problem is on Mastodon side, but not sure what's causing that specifically.

Found similar for mastodon.el: https://github.com/jdenen/mastodon.el/issues/1
But I estimate, your using a js-client ... ;-)

Yeah that's the one, so I guess the client needs to be updated upstream then. I haven't had a chance to look, but might be easy enough to call the API directly using the request module. I think the client just constructs the request using the token.

I will try to solve the issue, but I will need some time to get into cljs & js. I try to explore your code by getting dirty hands - what do you think about starting with a refactoring
(separate mastodon / rss / thumbler / twitter in namespaces & define the input / output using spec) ?
First steps I tried here: https://github.com/DomainDrivenArchitecture/mastodon-bot/blob/refactoring/mastodon_bot/mastodon_api.cljs
Do you like the idea or should I handle my learning-journey just as some kind of coding-kata?

Splitting things up sounds good to me, and definitely not opposed to having some specs around things. A PR is very welcome if you get it all working the way you like. :)

Can no longer reproduce this issue.


[Feature]  I think that the submit button on all popup windows should have an event listener, click Enter to submit the data directly

I think that the submit button on all popup windows should have an event listener, click Enter to submit the data directly
我认为所有的弹窗上的提交按钮都应该有一个事件监听，点击回车直接提交数据

does this cause misoperation?

No, when you click enter, a prompt box pops up, and the user clicks OK to submit the data, so you can delete it by mistake.
不会的呀，当点击enter ，弹出提示框，用户点击确定提交数据，这样就可以误删除了呀

Close this issue since no updates for long time


DLP: Check quasi_id types

cc @lukesneeringer
For DLP's kAnonymityConfig and lDiversityConfig, can we check that the quasiIds field's sub-objects specify a columnName property?
For example, the following is currently (as of #2668) not caught clientside:
const badCfg = "kAnonymityConfig": {
 "quasiIds": [
   {
     "shouldBe_columnName": "Name"
   },
   {
     "shouldBe_columnName": "Age"
   }
 ]
}

So one way we could do this is to add a check to all request objects to make sure that there are no fields that do not conform to the schema provided in the proto.  I'd have to look at what that would mean for streaming calls though.
@lukesneeringer do you think it's reasonable to add this validation step before shooting off a request?

Probably not. We consistently get bitten when we do client-side validation.

This issue was moved to googleapis/nodejs-dlp#3


"Fișer" is listed in the drop-down menu

Description:
"Fișer" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Fișer" in the search bar.
Expected results
The location is listed in the drop-down menu as "Oraș Fișer, BRAȘOV (RUPEA)".


Clarification of meaning of parameter 'tol'

Hi! Thanks for sharing this package, it's simple and effective!
I want to signal that the definition of tol as given in the readme is a bit misleading. The readme says

tol : absolute tolerance on |f(x)-x|

suggesting (at least to me) that if the algorithm converges (i.e. ends up using strictly less runs than the provided number of iters) the following inequality will always hold:
res = afps(f, x)
grad_norm( f( res.x ) - res.x ) < tol

This seems to be not always true.
The reason is that the update step is computed as
trial = x_n + β * v_n
g = f(trial) - trial
v_n = β * v_n + ϵ * g
x_n = x_n + v_n
runs += 1
if grad_norm(g) < tol
     break
end

and one sees that even if the iteration stops when grad_norm(f(trial) - trial) < tol, it is not x = trial that is returned, but x = trial + ϵ * g.
It may be that the current behaviour is the desired one, I just wanted to signal this in case it is not.
A modification of the update step satisfying the inequality above is
trial = x_n + β * v_n
g = f(trial) - trial
if grad_norm(g) < tol
    x_n = trial
    break
end
v_n = β * v_n + ϵ * g
x_n = x_n + v_n
runs += 1

(requiring also the initialisation runs = 1 I think).

That's a good point. The current package code also makes redundant computations.


Bad links on UniversalStorage2's SpaceDock page

Broken link to a mod mainpage, possible phishing

Operating System: Win 8.1
CKAN Version: v1.30.0
KSP Version: many. Problem appeared on a 1.10.1 version but shouldn't be linked with KSP version.

Have you made any manual changes to your GameData folder (i.e., not via CKAN)?
Yes, added the recompiled RSSVE for 1.9+, but it shouldn't be related.
Problem
Mod : Universal Storage II (by Paul_Kingtiger, DMagic, Daishi)
The link to the main page (http://www.kingtiger.online//uvsii/) sent me to a phishing page - an obviously fake "windows defender" alert. Multiple tests sent me to multiple different webpages, mostly commercials.
The link to spacedock works as intended though.
I haven't tried the mod on 1.10.1 (mainly because it hasn't been updated).
Steps to reproduce

Go to CKAN indexed mod Universal Storage II
Click on the main page link
See where it sends you

Expected behavior
Screenshots (if applicable)
https://drive.google.com/file/d/1V56DMi6j81bQul4hbdz6y4qCTFUeMzbm/view?usp=sharing
CKAN error code (if applicable):
None
PLACE CODE HERE !

Thanks for the report.
Looks like that one was a personal domain by one of the authors, KingTiger, which expired.
The links are coming directly from SpaceDock:

It has also already been reported on the forum thread, but the author hasn't been online in almost a year, so it's unlikely they'll come back (soon) and renew the domain.
I've changed the links to point to the forum thread + their OneDrive source code archive which will also propagate to CKAN for the latest release, but we should probably also replace all the links in older metadata.


remove reduncant parentheses

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The cpplint check failed, please solve it.

If we want to provide the expression literal same with user input query better to store the origin expression literal in parser like mysql.


Empty namespace in composer.json file for autoloader

There is empty namespace for auto-loading classes which decreases code performance  and also interferes while adding custom namespaces.
{
"name": "providr-packages/package-303",
"description": "Package generated from main.wsdl using wsdltophp/packagegenerator",
"require": {
"php": ">=5.3.3",
"ext-soap": "*",
"wsdltophp/packagebase": "~1.0"
},
"autoload": {
"psr-4": {
"": "./src/"
}
}
}

What would you propose then?

It would be easy to implement my custom classes if you can add a namespace instead of leaving it empty.
I donot know how to update all of the code files  if I add the namespace myself.
It will be convenient if the package generator implements it.
And is providr.io updated with latest changes made on package generator in github ?
Please consider my request if this is a progressive change.
Thanks,
Pushpa Raj

You can already set a namespace for the generated classes using the namespace option (Use your namespace prefix on providr.io), maybe this is what you're looking for?
Otherwise, all I can think of would be to specifically define all the possible namespaces such as:
{
  "name": "providr-packages/package-303",
  "description": "Package generated from main.wsdl using wsdltophp/packagegenerator",
  "require": {
    "php": ">=5.3.3",
    "ext-soap": "*",
    "wsdltophp/packagebase": "~1.0"
  },
  "autoload": {
    "psr-4": {
      "StructType\\": "./src/StructType/",
      "ArrayType\\": "./src/ArrayType/",
      "EnumType\\": "./src/EnumType/",
      "ServiceType\\": "./src/ServiceType/"
    }
  }
}

Except that the ClassMap class would still not have a namespace so it would need to add this sort of thing:
{
  "autoload": {
      "files": ["src/MyLibrary/functions.php"]
  }
}

Currently I don't think it's crucial according to the fact that you can set your own namespace.
What do you think?

The providr.io platform currently uses the 2.6.0 release 😞

Yes, using the namespace function solved my issue. Thank you very much for pointing this out.
And do you own providr.io platform , I would like to message them to update to latest release.
Again thank you very much for this handy tool , it has made my life easier with SOAP.
Thanks,
Pushpa Raj

And do you own providr.io platform , I would like to message them to update to latest release.

Yes I do 😉

Okay thats very nice, I hope you till update the package soon.

If you like it, you should start it 😉

@brainyprb the platform providr.io has been updated with the latest version of the generator just a minute ago 😄

Thank you , thats a good notification I got today 👍


https://openedx.atlassian.net/browse/MA-1737

User profiles - Design Feedback
https://openedx.atlassian.net/browse/MA-1737

Just needs a couple small changes. Also you'll need to rebuild the snapshot tests.

:+1:


Webtoon reading mode displaying breaks between imagines

Device information

Neko version: 2.6.2
Android phone & version: Google Pixel 2 XL - Android 11

Steps to reproduce

Open webtoon not tagged Long Strip on mangadex
Change reader mode from default to webtoon

Expected behavior

There should be no boarders between the images

Actual behavior

There are boarders between imagines causing breaks in the image stream.

Screenshot

this working as designed.  Non Webtoons are forced to have space to make them "paged".  Open a request on MangaDex website and mention its missing the longstrip tag.  Once they add that you will be good.


StyleUrl for GMUPlacemark not matching up with any GMUStyle within the _styles property of GMUGeometryRenderer.

I have found that when the below kml document is parsed by GMUKMLParser, the resulting GMUPlacemark object does not have a valid string within the StyleUrl property that references a GMUStyle object.  Thus no style is applied to the given placemark despite being set and exported via Google Earth Pro desktop Mac app.
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="http://www.w3.org/2005/Atom">
<Document>
	<name>KW Path.kml</name>
	<Style id="sn_ylw-pushpin">
		<IconStyle>
			<scale>1.1</scale>
			<Icon>
				<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
			</Icon>
			<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
		</IconStyle>
		<LineStyle>
			<color>ff00c2ff</color>
			<width>2</width>
		</LineStyle>
	</Style>
	<Style id="sh_ylw-pushpin">
		<IconStyle>
			<scale>1.3</scale>
			<Icon>
				<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
			</Icon>
			<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
		</IconStyle>
		<LineStyle>
			<color>ff00c2ff</color>
			<width>2</width>
		</LineStyle>
	</Style>
	<StyleMap id="msn_ylw-pushpin">
		<Pair>
			<key>normal</key>
			<styleUrl>#sn_ylw-pushpin</styleUrl>
		</Pair>
		<Pair>
			<key>highlight</key>
			<styleUrl>#sh_ylw-pushpin</styleUrl>
		</Pair>
	</StyleMap>
	<Placemark>
		<name>KW Path</name>
		<styleUrl>#msn_ylw-pushpin</styleUrl>
		<LineString>
			<tessellate>1</tessellate>
			<coordinates>
				-95.40955451587095,29.68319223122121,0 -95.41162049810978,29.68311038759943,0
			</coordinates>
		</LineString>
	</Placemark>
</Document>
</kml>

I am having same problem. It looks like GMUKMLParser is not properly parsing the  tag in

https://github.com/googlemaps/google-maps-ios-utils/pull/228

Unfortunately I don't think your change fixes the problem. I've put the change into my code, and I still have issues with styling placemarks.


Introduce theme app extensions buyer facing translations

We are introducing Locales directory for the theme app extension app blocks buyer/storefront facing translations strings.

nit: should we add some non-default locales, or is it unnecessary?

We are waiting for translations platform to create those other locale files


haskell-docs 4.2.6 not building with GHC 7.8.4

Apparently haddock-library needs to be included for GHC 7.8.4 as well as for GHC 7.10. When building 4.2.6 I get the message below while 4.2.5 builds fine.
src/haddock-api/Haskell/Docs/HaddockDoc.hs:14:18:
    Could not find module ‘Documentation.Haddock.Types’
    It is a member of the hidden package ‘haddock-library-1.1.1’.
    Perhaps you need to add ‘haddock-library’ to the build-depends in your .cabal file.

Seeing the same thing on my end, worth looking into.

I believe this should now be fixed.


Update regression docs

Codecov Report
Base: 58.76% // Head: 58.76% // No change to project coverage :thumbsup:

Coverage data is based on head (1de77e1) compared to base (2d13a25).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #2009   +/-   ##
=========================================
  Coverage     58.76%   58.76%
  Complexity     1093     1093
=========================================
  Files           187      187
  Lines         10267    10267
  Branches       1412     1412
=========================================
  Hits           6033     6033
  Misses         3756     3756
  Partials        478      478

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Mod prints the class name of every screen opened to the client log

Minecraft 1.20.1
Inventory Tweaks Refoxed 1.1.0
Forge 47.3.0
Mod pack: Project Architect 2 version 2.6
Every time an inventory screen is opened, Inventory Tweaks Refoxed prints the name of the class responsible for the inventory screen to the client-side log. For example, the following lines in the log are logged when opening the player's inventory, then a Sophisticated Backpack, and finally a Wireless Crafting Terminal from AE2WTLib.
[23:34:21] [Render thread/INFO] [invtweaks/]: net.minecraft.client.gui.screens.inventory.InventoryScreen
[23:39:08] [Render thread/INFO] [invtweaks/]: net.p3pp3rf1y.sophisticatedbackpacks.client.gui.BackpackScreen
[23:39:11] [Render thread/INFO] [invtweaks/]: de.mari_023.ae2wtlib.wct.WCTScreen

Where in the code is causing these lines to be logged, and can it be disabled so as to not clog up the logs?

It's on purpose to help with configuring, but it should have been writing to the debug log not the regular log. I'll get it moved and maybe put a config for it as well.


BUG: Creating a scroll from spell no longer keeps spells icon

Looks like at some point the scroll creation stuff stopped keeping the spells icon. It now has a generic scroll icon.
Forgive me if this was intended :)

It was indeed intended: https://github.com/foundryvtt/dnd5e/issues/4287

Ah!


Closes #156 - Adds Profile Card with Action Icons

Closes #156
I think this time preview image is good enough and is good to go without updates

Poke @rafibomb @kball @canterberrie
If anyone of you can look into it ??

This looks good to me! Great preview image too :) Merging this in!


Markdown formatting error

Documentation page:
https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/SharePoint/SharePointServer/upgrade-and-update/overview-of-the-services-upgrade-process.md
In this page there is an extra space placed after "Summary:" that doesn't allow for the markdown to process the bold.
**Summary: ** Create a

updated and republished


WIP -- Setting up Configure command for CLI

[x] Prompt for what kind of monitoring the user would like to set up
[ ] Iterate through selections and prompt for required info:

[x] nginx
[x] Apache
[x] Postgres

[ ] If error logging is selected, should we set up logging output to a file for user?

[x] Mongo
[x] Host machine
[ ] Custom app

Add functionality to keep a running summary of choices at the top of the screen, despite console.clear()


Vendor Goose to ensure we don't inadvertently bring in a breaking change.

In order to prevent the possibility of breaking changes being introduced into the https://github.com/shopify/goose package we should vendor the package.
This is only needed until #254 is completed.
Vendor Documentation: https://golang.org/src/README.vendor

Vendoring is now an all or nothing affair.
Fork this repo in CDS-SNC org instead of vendoring to prevent breaking changes.


428 stars watchers forks

This PR fixes #428

It retrieves the repository data.
It shows stars, forks and watchers in Home.

Preview:

@raulraja @dialelo Could you take a look please? Thank you.

Maybe squash all the merges into one commit?

:+1: Are we doing authenticated calls to GitHub? I'm worried about rate limiting.
In the future we could move this request to be performed in the client but as long as we don't get rate limited we can make the requests in the server for the moment.

@dialelo Yes, we are requesting the repo data with an authenticated call to avoid the rate limit. Given that we are retrieving the environment variable for others Github calls, I decided to re-use it as well:
https://github.com/scala-exercises/scala-exercises/pull/449/files#diff-7ed401ce2d238c772383c0972c539c5aR110
Makes sense?

Nice, makes sense :+1: LGTM

This is going to be an issue with rate limiting specially in the home page. We need to cache these values and only have them refreshed every so often. for example rerender them once every 30 mins. Aomething in these lines but adapted to Future.
val repo = cache.getOrElse[User]("home.repo.info", duration) {
  GH.getRepo(owner, repo)
}

http://stackoverflow.com/questions/34612363/cache-getorelse-on-futures-in-playframework


page.evalute with execution inconformity results on different OS

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.11.0
Platform / OS version:  MacOS 10.12.6,  docker(node:8.4.0)
URLs (if applicable):
Node.js version: 8.4.0

What steps will reproduce the problem?
app.js:
const puppeteer = require("puppeteer");

let sleep = ms => {
  return new Promise(sv => setTimeout(sv, ms));
};

process.on("uncaughtException", function(err) {
  console.log("process uncaught exception", err);
});

process.on("unhandledRejection", (reason, p) => {
  console.log("process unhandled rejection", p, "reason", reason);
});

async function start() {
  let browser = await puppeteer.launch({
    // headless: false,
    defaultViewport: {
      width: 1366,
      height: 786
    },
    ignoreHTTPSErrors: true,
    args: [
      "--no-sandbox",
      "--disable-setuid-sandbox",
      "--remote-debugging-port=9222",
      "--remote-debugging-address=<IP_ADDRESS>"
    ]
  });

  let url = "https://www.21jrr.com/funds/jijindongtai/2018/1022/354915.html";

  let page = await browser.newPage();
  console.log(`go to url: ${url}`);
  await page.goto(url, {
    timeout: 0,
    waitUntil: "domcontentloaded"
  });

  await sleep(3000);
  console.log(`start scroll`);

  await page.exposeFunction("cl", console.log);

  await page.evaluate(async () => {
    window.cl("start 1");
    window.scrollBy(0, 100);

    await new Promise((sv, rj) => {
      setTimeout(() => {
        // will not work && stuck
        window.cl("start 2");
        window.scrollBy(0, 100);
        setTimeout(() => {
          window.cl("start 3");
          sv();
          window.scrollBy(0, 100);
        }, 1000);
      }, 1000);
    });
  });

  await sleep(3000);

  console.log(`scroll done`);
}

try {
  start();
} catch (err) {
  logger.warn("Exec Error: %s", err.message);
  process.exit(1);
}

dockerfile:  copyed from troubleshooting.md#running-puppeteer-in-docker
FROM node:8-slim

# See https://crbug.com/795759
RUN apt-get update && apt-get install -yq libgconf-2-4

# Install latest chrome dev package and fonts to support major charsets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)
# Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer
# installs, work.
RUN apt-get update && apt-get install -y wget --no-install-recommends \
    && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
    && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \
    && apt-get update \
    && apt-get install -y google-chrome-unstable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst ttf-freefont \
      --no-install-recommends \
    && rm -rf /var/lib/apt/lists/* \
    && apt-get purge --auto-remove -y curl \
    && rm -rf /src/*.deb

# It's a good idea to use dumb-init to help prevent zombie chrome processes.
ADD https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 /usr/local/bin/dumb-init
RUN chmod +x /usr/local/bin/dumb-init

# Uncomment to skip the chromium download when installing puppeteer. If you do,
# you'll need to launch puppeteer with:
#     browser.launch({executablePath: 'google-chrome-unstable'})
# ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true

# Install puppeteer so it's available in the container.
RUN npm i puppeteer

# Add user so we don't need --no-sandbox.

USER pptruser

ENTRYPOINT ["dumb-init", "--"]
CMD ["google-chrome-unstable"]

excute command:
# build
docker build -t puppeteer-chrome-linux .
# run
docker run -i --rm --cap-add=SYS_ADMIN  --name puppeteer-chrome puppeteer-chrome-linux node -e "`cat app.js`"

build dockerfile
excute docker run

What is the expected result?
go to url: https://www.21jrr.com/funds/jijindongtai/2018/1022/354915.html
start scroll
start 1
start 2
start 3
scroll done
What happens instead?
got result below when run in docker, and process not exit:
go to url: https://www.21jrr.com/funds/jijindongtai/2018/1022/354915.html
start scroll
start 1
run same code in macOS, got result below:
go to url: https://www.21jrr.com/funds/jijindongtai/2018/1022/354915.html
start scroll
start 1
start 2
start 3
scroll done

also stuck in docker,  if you try to screenshot
await page.screenshot({
          path: path,
          type: 'jpeg',
          quality: 80,
          fullPage: true
        })


Implement __isset function in Model class

For using the model classes in Twig templates the __isset function needs to be implemented. Like explained here: http://twig.sensiolabs.org/doc/recipes.html#using-dynamic-object-properties

Thanks!


Add documentation about detail of image type

connectedComponents and connectedComponentsWithStats in
imgproc accept 8-bit single channel image only for input.

:+1:


[WIP] Rosgraph extractor - runtime inspection and system model extractor

the xtext of the ros model had to be updated to accept the character "/" . Extracting from runtime the data the name of the nodes usually includes the namespace

Thanks @ipa-led :smiley:

@ipa-nhg
Update : https://github.com/ipa-led/ros_graph_parser
It's catkinized (but don't install yet).
To create the .ros and the .system files, use the  java_snapshot with 4 arguments:

name of the ros model file
name of the system model file
name of the system
name of the package

It should create the two files in the result folder (for now, I will make the path a bit more flexible).


Implement toggle panel

Componentizes and glues together Explore Page with Toggle state and a couple example boundary/data points as described from the first iteration

I just shared this branch with the Greenwood Mapping project in the Tulsa, Oklahoma brigade!  Nice work.


Export SelectProps and Option

In order to create a wrapper around Select, it's would be useful to be able to import the SelectProps and Option type.  Currently this isn't exported.  I can to this myself using some TS magic:
type SelectProps = (typeof Select) extends React.FC<infer X> ? X : never;
type Option = SelectProps["formatOptionLabel"] extends ((data: infer X) => JSX.Element) | null | undefined ? X : never;

but exporting the types would be the best solution

Hi @onesine, in order to use the SelectProps, currently we need to import it from the dist folder like this
import { SelectProps } from 'react-tailwindcss-select/dist/components/type'
Generally, the packages would allow something like this
import Select, { SelectProps } from 'react-tailwindcss-select'
Is it ok to keep importing from the dist or do you have any plans on updating it?
Thanks in advance!


Feature: dart json_serializable annotation support

json_serializable with json_annotation is widely used by Flutter community. It would be great if quickType has support for this. It's similar to freezed library.

PR raised for this:
https://github.com/quicktype/quicktype/pull/2266

PR as been merged


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in ada749b.


⚠ Bofrost.es has degraded performance

In 70536b6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1589 ms

Resolved: Bofrost.es performance has improved in fadaee9 after 6 minutes.


New package: DW.Spectrum.Client version 4.2.32842

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

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

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

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116548&drop=dogfoodAlpha

https://github.com/microsoft/winget-pkgs/issues/107639


Division by 0?

New to NCalc, testing basic functionalities but when I've tried this expression
"10 / 0"
surprisingly the result evaluated to "8"...
Did I miss something?

can you provide a code sample or Unit test with this result?

Here is the main "Program" (console application) I've used to test some functionality. Some of the formulas are taken directly from the main source code, I've added a couple of formulas with one direct division by zero and one with two parameters that are set to "7" and "0" before evaluation. I've attached also an image with the console results.
class Program
{
    static void Main(string[] args)
    {
        var expressions = new[]
        {
            "0 / 10",
            "2 * (3 + 5)",
            "2 * (2*(2*(2+1)))",
            "10 % 3",
            "false || not (false and true)",
            "3 > 2 and 1 <= (3-2)",
            "3 % 2 != 10 % 3",
            "[A] + [B]",
            "10 + 3 * 4",
            "7 == 7",
            "5 / 0",  //odd result
            "[X] / [Y]"  //odd result
        };

        foreach (string expression in expressions)
        {
            Expression myExpr = new Expression(expression);

            if (expression.Contains("[A]"))
            {
                myExpr.Parameters["A"] = "I am running";
            }

            if (expression.Contains("[B]"))
            {
                myExpr.Parameters["B"] = " along the road";
            }

            if (expression.Contains("[X]"))
            {
                myExpr.Parameters["X"] = 7;
            }

            if (expression.Contains("[Y]"))
            {
                myExpr.Parameters["Y"] = 0;
            }

            Console.WriteLine($"{expression} => {myExpr.Evaluate()}");

            if (myExpr.Parameters.Count > 0)
            {
                foreach (KeyValuePair<string, object> myExprParameter in myExpr.Parameters)
                {
                    Console.WriteLine($"  Parameter {myExprParameter.Key} => {myExprParameter.Value.ToString()}");
                }
            }
        }

        Console.ReadKey(true);
    }
}

Stupid question. Is it possible that the eight is really an infinite symbol and it is showing wrong?

https://dotnetfiddle.net/qrfQPQ

In fact you are right :)
looking at the "real" result of the evaluation through the watch window the evaluation states "infinity"
I didn't think to look here... sorry :)
Thanks or you patience,
All the best


Using advanced ssl_params with Redis connections

Hi all! Just curious on what's the advice for handling custom ssl_params to the Redis connection?
I am using RedisLabs and have self-signed certificates and CA files from them. With that I basically do something like the below when initializing redis connections (for Sidekiq and Rails' cache redis store):
cert_store = OpenSSL::X509::Store.new
cert_store.add_file(Rails.root.join('config', 'redislabs_ca.pem').to_s)

ssl_params = {
  cert_store: cert_store,
  cert: OpenSSL::X509::Certificate.new(File.read(
    Rails.root.join('config', 'redislabs_user.crt')
  )),

  key: OpenSSL::PKey::RSA.new(
    Rails.application.credentials.redis[:client_key]
  ),

  verify_mode: OpenSSL::SSL::VERIFY_PEER }
}

redis = Redis.new(url: ENV['REDIS_URL'], ssl_params: ssl_params)

I suspect there isn't really a great way to pass all this configuration via yaml. Happy to open a PR which exposes more configuration options but would love some guidance on what I should look to refactor and extend? Maybe Kredis::Connections could have a user-extendable hash that maps the supplied name to configured_for to an optional proc. This proc could receive the results of configurator.config_for("redis/#{name}") and let the user update the hash with more options.
My current "solution" is super hacky and it just preemptively populates the connections hash in an initializer:
 Kredis::Connections.connections[:shared] = Redis.new(
  url: ENV['REDIS_URL'], ssl_params: ssl_params
)

Great stuff as always though! This gem is super helpful to some new stuff we're working on.

I think your "hacky" solution is the right one. We should just document that this is how to do it.

Sounds good! I can submit a PR with some README.md updates.