Dockerbuild is failing when running the action

Since around yesterday the action is failing to build the docker container and thus run the action itself.
If I am not mistaken there is already a pr in place (#37) to switch to a JavaScript based action.
Here is the log output when running the action:

Hi, this one looks unrelated to the docker build itself but an error when downloading dependencies from GitHub. A build worked well just now with the same dependency so I'll assume it was a transient error, can you confirm if it worked well?

I'm having the same issues since this morning. Already retried several times, but still getting this error:
  Step 12/13 : RUN go build -o action ./cmd
   ---> Running in 9ffdc10dd92c
  go: finding github.com/kr/pretty v0.1.0
  go: finding github.com/waigani/diffparser v0.0.0-20190828052634-7391f219313d
  go: finding github.com/google/go-github/v35 v35.0.0
  go: finding github.com/google/go-cmp v0.3.1
  go: finding github.com/go-yaml/yaml v2.1.0+incompatible
  go: finding golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be
  go: finding github.com/kr/text v0.1.0
  go: finding github.com/davecgh/go-spew v1.1.1
  go: finding github.com/stretchr/testify v1.4.0
  go: finding github.com/pmezard/go-difflib v1.0.0
  go: finding github.com/kr/pty v1.1.1
  go: finding github.com/davecgh/go-spew v1.1.0
  go: finding github.com/stretchr/objx v0.1.0
  go: finding github.com/golang/protobuf v1.3.2
  go: finding github.com/google/go-querystring v1.0.0
  go: finding golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2
  go: finding golang.org/x/net v0.0.0-20190311183353-d8887717615a
  go: finding google.golang.org/appengine v1.1.0
  go: finding golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a
  go: finding golang.org/x/text v0.3.0
  go<EMAIL_ADDRESS>unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())
  go<EMAIL_ADDRESS>unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())
  go<EMAIL_ADDRESS>unrecognized import path "gopkg.in/check.v1" (parse https://gopkg.in/check.v1?go-get=1: no go-import meta tags ())
  go: error loading module requirements
  The command '/bin/sh -c go build -o action ./cmd' returned a non-zero code: 1

  Warning: Docker build failed with exit code 1, back off 6.118 seconds before retry.
  /usr/bin/docker build -t 94859b:7ded1259ef884377b27f48b9871cf62c -f "/home/runner/work/_actions/srvaroa/labeler/master/Dockerfile" "/home/runner/work/_actions/srvaroa/labeler/master"

This could be related to https://github.com/go-yaml/yaml/issues/887

Adding a GOPROXY fixes the issue: https://github.com/go-yaml/yaml/issues/887#issuecomment-1214290330


Update flowise 2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: cloniumagent:x: vvchrYou have signed the CLA already but the status is still pending? Let us recheck it.


Add 'low' & 'high' options for the gpio direction setting

This pull request is a proposed fix for issue #25 by allowing the developer to choose which state the gpio pin should be initially set to. This is especially helpful for dealing with certain hardware setups that operate in reverse logic (0 is hot, 1 is cold).
Thanks!

???

Thanks for going to the effort of submitting this patch and I'm sorry it has taken so long to get back to you.
I'm keen to merge, but is it possible please to add some extra test coverage just so that we can see the module working with these new options? There are some existing tests for direction and I think they can just be copied.
Also is there any chance you could update the readme to provide some info for the extra options?
Cheers.

I found that channel 7 is the only one that defaults to high, the rest (11, 12, 13, 15, 16, 18, 22) defaulted to low.  I also found that the proposed fix does not work for me.
I used it like this:
gpio.setup(11, gpio.DIR_LOW, gpio.EDGE_BOTH);

Hey guys, sorry I haven't been watching this thread lately.
Anyways, I'm happy to add some test coverage and explain in the read me what I am trying to achieve with this pull request.
More coming soon...

@karlstulik, I did not notice the EDGE_ options when originally using this fix. My code skips the edge option altogether and just has a callback function. Perhaps not using a callback function is contributing to it not working for you? Mine works like this:
function startServer() {
  /*
  code that starts an http server and listens for requests to turn
  the pin on and off. the pin start "hot" because I used HIGH as the
  direction.
  */
}

gpio.setup(7, gpio.DIR_HIGH, startServer);

I don't have a good setup to test right at the moment, but if memory serves me correctly, using DIR_HIGH was necessary for me, and made the pin start "hot", which I remember it wasn't doing originally.

@JamesBarwell, I've added the requested tests and added some documentation to the read me. the tests passed on my Pi running NodeJS 4.4.0. I did not run or edit the integration test since the Pi is not wired properly for it.
Let me know if you need me to do anything else. Thanks again.
Cheers! 🍺
Zach

Apologies for the delay, but I wanted to give it a proper test myself. I've been testing the patch this morning on my Model B running node 6.2.1 and I'm happy with it. I'll update in a bit with new module version details. Much appreciated, cheers.

Published as<EMAIL_ADDRESS>

Tested this in my library on raspberry pi 1 model b, works great! Huge thanks


Persistent configuration for projects

Describe your feature request
I believe that most developers are not working on many projects at once. So there is no point to fulfill the connecting config on every new tab. This will be best if there will be another select menu to choose the current project.
For example:
Select menu with the options somewhere in top of UI, near the Surrealist logo maybe:

Project 1
Project 2
Custom-named project
Add a new project

Selecting option 1 will load project 1, so every new tab will use preconfigured connection details for this project.
If you then select for example option 2 will load project 2. Every tab from project 1 will hide. Every new tab under project 2 will use preconfigured connection details for this project.
This has also expansion potential. For example: to enable the user to save queries to global or per project.

Thanks for the suggestion!
I would prefer avoiding adding additional UI elements to the general layout for simplicity sake unless we can't find another way. Instead, would it be an idea to have the creation of new tabs copy over the configuration of the previously active tab? It might be a simple enough solution for your problem.
Would love to hear your opinion!

I personally think your solution is a minimum requirement to improve UX in this case. However, I think per project environments will be a great UX improvement and this may open doors for other features (if you even have plans to go there).
One select list is enough to handle this feature on the main screen. And there is a window-wide URL input, which is not needed to be that wide. It potentially can share the space with something and keep it simple.

I've overhauled the tab system and implemented a way to group tabs under so called environments in which default connection details can be specified. Besides that, it also greatly improves tab organization.

I'll mark this issue as closed since this should suffice for your use-case


Escrow Application

This issue is meant to document the creation of a new application namely an Escrow.
Features

[x] #29
[ ] #30

Closing in favor of https://github.com/FuelLabs/sway-applications/issues/30


Motion Sensor Icon in Chip Cards

Currently, when a motion sensor entity is added to a chip card, it defaults to a checkbox-marked-circle icon. The out of box icon for a motion sensor depends on its state, using either motion-detector or motion-sensor-off. It would be great if this was also the default behavior in Mushroom

We currently use custom-cards for the icon definition : https://github.com/custom-cards/custom-card-helpers/blob/master/src/domain_icons.ts but it's not updated with latest icon rules based on icon domain AND device_class.

I am happy to move the issue over to the custom card helpers repo. Paul, I think the correct approach here is that binary sensor domain should look to the device class to determine the correct icon.

Added an issue in the upstream library
https://github.com/custom-cards/custom-card-helpers/issues/57

Yup!! Same Problem here. I am not a developer, but if it will look for the device class to determine the correct icon, the icons will loose previous customizations right (like in customize.yaml)?


Handle AWS secret manager empty response

We've received this exception
{"level":"error", "msg":"runtime error: invalid memory address or nil pointer dereference:
goroutine 25579 [running]:
github.com/go-kratos/kratos/v2/middleware/recovery.Recovery.func2.1.1()
	/home/runner/go/pkg/mod/github.com/go-kratos/kratos/v2@v2.5.3/middleware/recovery/recovery.go:53 +0xa7
panic({0x2185140, 0x3b16820})
	/opt/hostedtoolcache/go/1.20.2/x64/src/runtime/panic.go:884 +0x213
github.com/chainloop-dev/chainloop/internal/credentials/aws.(*Manager).ReadCredentials(0xc0006747b0, {0x28df088, 0xc000f01740}, {0xc000e8a660, 0x58}, {0x213dea0, 0xc000e0b2c0})
	/home/runner/work/chainloop/chainloop/internal/credentials/aws/secretmanager.go:123 +0x150
github.com/chainloop-dev/chainloop/internal/blobmanager/oci.(*BackendProvider).FromCredentials(0xc000752e20, {0x28df088, 0xc000f01740}, {0xc000e8a660, 0x58})
	/home/runner/work/chainloop/chainloop/internal/blobmanager/oci/provider.go:39 +0x93
github.com/chainloop-dev/chainloop/app/controlplane/internal/biz.(*OCIRepositoryUseCase).PerformValidation(0xc000704040, {0x28df088, 0xc000f01740}, {0xc0010e5260, 0x24})

The nil pointer is raised here
https://github.com/chainloop-dev/chainloop/blob/08cd26fd89c0d6d653c201b5e7db296069e1a173/internal/credentials/aws/secretmanager.go#L123
It seems that for some reason both resp and err were nil?

It seems that for some reason both resp and err were nil?

When we check if err != nil we also do if errors.As(err, &apiErr). If err cannot be asserted as of type smithy.APIError, the function does not return when it should, I believe.

In fact, in the AWS documentation at this page:
https://aws.github.io/aws-sdk-go-v2/docs/migrating/
the following example can be found:
}
	var apiErr smithy.APIError
	if errors.As(err, &apiErr) {
		code := apiErr.ErrorCode()
		message := apiErr.ErrorMessage()
		// handle error code
		return
	}
	// handle error
	return

The code is implementing the block // handle error code but it's missing the block // handle error. At least, I think this is the cause of the problem.

hi @buccarel, thanks for looking into this; I think you are right! We don't handle an error that's not an APIError 🤦🏼
https://github.com/chainloop-dev/chainloop/blob/38505dc72147e018fa3d2ba33d40add579a37356/internal/credentials/aws/secretmanager.go#L112-L122
Would you like to add a patch for this? If so, ptal at the expected commit format in our contribution guide
Thank you!


auto patch webhook objectSelector label on workload

Ⅰ. Describe what this PR does
Rollout patch webhook label on workload
Currently rollout will webhook all workloads update requests, include Deployment, StatefulSet, CloneSet, Advanced StatefulSet. But not all workloads have to be rollout released, and if kruise rollout crashes will lead to workload update failed. So we can add configuration in MutatingWebhookConfiguration yaml.
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
...
  objectSelector:
      matchExpressions:
        - key: rollouts.kruise.io/workload-type
          operator: Exists

And the rollout controller patches the above label to the workload according to the Rollout objectRef.

Codecov Report

Merging #158 (1e0d1b7) into master (7139171) will decrease coverage by 0.13%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master     #158      +/-   ##
==========================================
- Coverage   43.67%   43.55%   -0.13%
==========================================
  Files          50       50
  Lines        5259     5283      +24
==========================================
+ Hits         2297     2301       +4
- Misses       2575     2595      +20
  Partials      387      387

Flag
Coverage Δ

unittests
43.55% <0.00%> (-0.13%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/controller/rollout/rollout_status.go
16.66% <0.00%> (-2.57%)
:arrow_down:

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

/approve


Requirements for multimatic not found: ['pymultimatic==0.6.11'].

HomeAssistant 2023.1 - Requirements for multimatic not found: ['pymultimatic==0.6.11'].
after HA update integration not starting- errors below:
Setup failed for custom integration multimatic: Requirements for multimatic not found: ['pymultimatic==0.6.11'].
Unable to install package pymultimatic==0.6.11: ERROR: Cannot install pymultimatic==0.6.11 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip available: 22.3 -> 22.3.1 [notice] To update, run: pip install --upgrade pip

had no information about update - I update manually - WORKS :)


[CSM-332] Optimize history derivation

Got rid of cached utxos, cached the history fully and used BListeners to update cache on block updates and rollbacks.

why did you checkout from master, not from cardano-0.5-rc?

@flyingleafe this also implements https://issues.serokell.io/issue/CSM-331 right ?

@akegalj yes, CSM-331 is also done here.

@flyingleafe didn't we say we will merge this into 0.5-rc , not master?

@akegalj I'm preparing another PR for 0.5-rc right now


Multiple runs of predict method with ML backend

Describe the bug
When a new task is opened to be annotated, the predict method is called two times.
To Reproduce
Steps to reproduce the behavior:

Start ML backend via label-studio-ml start ml_annotation_backend
Start Label studio with ML backend connection via label-studio start annotation_project --template text_named_entity --ml-backends http://localhost:9090
UI opens up in Tasks page
Click on a random task

Expected behavior
Only one predict run when a task is opened.
Screenshots
Console log outputs (18:55 is where I click the task and the annotation panel opens after running the below 2 predicts):
[2021-02-27 18:55:19,498] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:19] "GET /health HTTP/1.1" 200 -
[2021-02-27 18:55:21,570] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:21] "POST /setup HTTP/1.1" 200 -
In predict() method...
[2021-02-27 18:55:24,924] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:24] "POST /predict HTTP/1.1" 200 -
[2021-02-27 18:55:27,454] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:27] "GET /health HTTP/1.1" 200 -
[2021-02-27 18:55:29,530] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:29] "POST /setup HTTP/1.1" 200 -
In predict() method...
[2021-02-27 18:55:32,333] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [27/Feb/2021 18:55:32] "POST /predict HTTP/1.1" 200 -

Environment (please complete the following information):

OS: Windows 10
Label Studio Version: 0.9.1.post1

Additional context
The first time I started the ML backend and label-studio, label-studio didn't show any connected ML backends in the UI Model tab so I had to add it via the textbox in the Model tab. --> Can this cause it to register the port twice thus sending two requests? I only see one model on the right hand side panel when the task is opened though.

@atakanokan Sorry for a long answer. I hope it's fixed in LS 1.0, you could try it.


Problem

Greetings Sir ! I have used your app after installing in my android...and the great thing was that it worked for few time but after that it stopped working...even on temporary mails too...except these issues the app is great. Sir you did a very hard work...

Greetings, ghost
I'm so sorry, the hosting that the smtp I used to make the API of the apk just died. I have made another API similar with the old one. I'm working on the new project, FazSpammer. It will also include the FazMail ability, that to send emails to people's email address.
Regards,
M.Fazri Nizar

Greetings sir ! Hello sir please don't say sorry...

Greetings Anonycodexia,
Once again I do apologize for the late response. I also currently stopped working at any open source project I have, due to jobs and assignments I got. After the pandemic, nowadays everything started to be normal again. A lot of assignments in real life I need to deal with so I don't have time to continue my open source project.
Regards,
M.Fazri Nizar

Greeting sir ! I hope youll be fine..
Umm..i really understand you sir...and i respect your decision... But please sir try to work on project too..whenever you get free time..thankyou so much sir for giving your response and precious time..😊


conflict

I really like this library, but when my project contains
compile 'com.android.support:design:23.3.0' and compile 'com.afollestad.material-dialogs: core: <IP_ADDRESS>'
I can not run the project, the question is Caused by: android.view.InflateException: Binary XML file line # 17: Error inflating class android.support.design.widget.CollapsingToolbarLayout

This library isn't updated for 23.3.0 yet. Your app has to use a matching version, or exclude the version used on this library from your Gradle file.

Oh you're using an old version, actually. You need to use 24.x.


Run tests under MIRI

Not only does this fix a double-free in <MoveRef as DerefMove>, but it also found a soundness issue in PinEx::as_move, which I've removed altogether, since it can't be made to work at all (see commit messages for details).
Closes #15.

See #25 for a better implementation that makes as_move sound.


Refresh XWing-Data for Wave X

Need to bring down and refresh the xwing-data files for Wave X.

All data through Tie Striker has been included.  Will do one final update before release.


Restore and redact previously scrubbed MakeMKV log lines

Restores all log entries that were stripped in 5629c462fcb4e32b836b750d6df7b022a3585629, with sensitive information redacted. Accomplished by restoring the non-stripped log entries from 0c3886ef72eb6a3f21d8d772d28fbe7c4db61b83 and then applying the updated CleanLog algorithm from #30.
~Marking as draft, as #30 should be reviewed first - any changes to redactions can then be made to this PR.~
Closes #27.

This PR has been updated to use the new redaction string, ***.


[4.2] When moving a NavigationRegion2D the NavigationServer2D does not update.

Godot version
4.2.stable, 4.2.stable.mono
System information
Godot v4.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon RX 5700 XT (Advanced Micro Devices, Inc.; 31.0.22011.4008) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)
Issue description
According to the "Using NavigationRegions" documentation https://docs.godotengine.org/en/stable/tutorials/navigation/navigation_using_navigationregions.html
"While changing the transform of a NavigationRegion node does update the region position on the NavigationServer, changing the scale does not."
This is true in 4.1.1.stable
However it is not working in 4.2.stable
Using either a RemoteTransform Node or setting the transform of the region directly.
Does not update the NavigationServer.
I'm using specifically the .Net release of 4.1.1.stable and 4.2.stable
But my scripts are in GDscript, doubt that matters, but just in case.
I may have missed if a new variable was added to set if the server automatically updates region changes.
(I promise I looked.)
Steps to reproduce
Create a scene with a NavigationRegion2D.
Add a NavigationPolygon
Add a script which moves the NavigationRegion2D
To see the lack of update connect NavigationServer2D.map_changed to any print function.
In 4.1.1 this will emit/print every physics frame in which the map changes.
In 4.2 this will emit/print once on the first frame.
Minimal reproduction project
In the minimal reproduction project you can use the arrow keys to move the NavigationRegion2D around the screen.
The console will print out when NavigationServer2D.map_changed is emitted.
NavigationRegionUpdateBug.zip

Just tried using NavigationServer2D.region_set_transform()
NavigationServer2D will emit map_changed however, it does not appear that the region's position actually changes.
It's not reflected with Debug>Show Navigation, nor while printing the region's position.

The NavigationRegion2D transform notification is currently broken. See pr https://github.com/godotengine/godot/pull/85258 that fixes it.
The debug visuals are part of the node, so any change that is done on the server-only will not be shown with the debug. E.g. moving the region with the NavigationServer API will not move the debug. A lot of the debug in Godot is currently node-based and has the same issue because the node updates are usually one-way tickets to the server and not the other way. See proposal https://github.com/godotengine/godot-proposals/issues/7208 that wants to change this.

Yes it is basically a duplicate, that linked issue about the not updating edge connections has the same problem that the transform notification does not work for the NavigationRegion2D.


Bunch of site fixes.

Correct the use of OpenGraph annotations. I used the wrong attribute name, so the
annotations were never recognized.

Added support for Twitter cards to our site, improving the experience of referencing
the site from Twitter posts.

Added support for the twitter: front matter field for use in blog posts. Specifying this
front-matter entry will show the author's twitter address on the blog post, and will
add a Twitter card entry to the page noting the author's address.

Renamed the page_icon front matter field to just icon to be consistent with other
entries.

Made it so the subtitle front matter field can be used anywhere, not just on blog post.

Added a lint check to ensure subtitles don't end with a period.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add relationship validation to puppet 3.x test.

This addresses #10 for Puppet 3.x only. I could not get Puppet 4.x to work locally (and we use 3.x anyway), but I suspect this could easily be ported.

Updated this patch today to address a bug found by a coworker where the main Stage resource return a symbol for #title, so requiring other stages on it fails the catalog test. I just coerced the titles to strings always in the validation.
Any chance this could be merged so my team can stop using my branch? :D

Hi askreet, I'm currently on vacation till end of august. As soon I'm back I'm going to release a new version.

Better late than never - https://github.com/invadersmustdie/puppet-catalog-test/commit/780e449787a3ac5e63ee1862703fe78c56f5a795
Thanks for the contribution


Nokogiri 1.6.8 Install Fails on Mac OS X with xz installed from Homebrew

Action:
brew install xz
gem install nokogiri -v 1.6.8

Expected:
Nokogiri 1.6.8 installs correctly.
Actual:
Restoring gems to pristine condition...
Building native extensions.  This could take a while...
ERROR:  While executing gem ... (Gem::Ext::BuildError)
    ERROR: Failed to build gem native extension.

    current directory: /Users/austin/.gem/ruby/2.3.0/gems/nokogiri-1.6.8/ext/nokogiri
/Users/austin/.rubies/ruby-2.3.0/bin/ruby -r ./siteconf20160607-71935-1m9be2b.rb extconf.rb
Using pkg-config version 1.1.7
checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
Using mini_portile version 2.1.0
checking for iconv.h... yes
checking for gzdopen() in -lz... yes
checking for iconv... yes
************************************************************************
IMPORTANT NOTICE:

Building Nokogiri with a packaged version of libxml2-2.9.4.

Team Nokogiri will keep on doing their best to provide security
updates in a timely manner, but if this is a concern for you and want
to use the system library instead; abort this installation process and
reinstall nokogiri as follows:

    gem install nokogiri -- --use-system-libraries
        [--with-xml2-config=/path/to/xml2-config]
        [--with-xslt-config=/path/to/xslt-config]

If you are using Bundler, tell it to use the option:

    bundle config build.nokogiri --use-system-libraries
    bundle install

Note, however, that nokogiri is not fully compatible with arbitrary
versions of libxml2 provided by OS/package vendors.
************************************************************************
Extracting libxml2-2.9.4.tar.gz into tmp/x86_64-apple-darwin15.3.0/ports/libxml2/2.9.4... OK
Running 'configure' for libxml2 2.9.4... OK
Running 'compile' for libxml2 2.9.4... ERROR, review '/Users/austin/.gem/ruby/2.3.0/gems/nokogiri-1.6.8/ext/nokogiri/tmp/x86_64-apple-darwin15.3.0/ports/libxml2/2.9.4/compile.log' to see what happened. Last lines are:
========================================================================
    unsigned short* in = (unsigned short*) inb;
                         ^~~~~~~~~~~~~~~~~~~~~
encoding.c:815:27: warning: cast from 'unsigned char *' to 'unsigned short *' increases required alignment from 1 to 2 [-Wcast-align]
    unsigned short* out = (unsigned short*) outb;
                          ^~~~~~~~~~~~~~~~~~~~~~
4 warnings generated.
  CC       error.lo
  CC       parserInternals.lo
  CC       parser.lo
  CC       tree.lo
  CC       hash.lo
  CC       list.lo
  CC       xmlIO.lo
xmlIO.c:1450:52: error: use of undeclared identifier 'LZMA_OK'
    ret =  (__libxml2_xzclose((xzFile) context) == LZMA_OK ) ? 0 : -1;
                                                   ^
1 error generated.
make[2]: *** [xmlIO.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
========================================================================
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
    --with-opt-dir
    --without-opt-dir
    --with-opt-include
    --without-opt-include=${opt-dir}/include
    --with-opt-lib
    --without-opt-lib=${opt-dir}/lib
    --with-make-prog
    --without-make-prog
    --srcdir=.
    --curdir
    --ruby=/Users/austin/.rubies/ruby-2.3.0/bin/$(RUBY_BASE_NAME)
    --help
    --clean
    --use-system-libraries
    --enable-static
    --disable-static
    --with-zlib-dir
    --without-zlib-dir
    --with-zlib-include
    --without-zlib-include=${zlib-dir}/include
    --with-zlib-lib
    --without-zlib-lib=${zlib-dir}/lib
    --enable-cross-build
    --disable-cross-build
/Users/austin/.gem/ruby/2.3.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:366:in `block in execute': Failed to complete compile task (RuntimeError)
    from /Users/austin/.gem/ruby/2.3.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in `chdir'
    from /Users/austin/.gem/ruby/2.3.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in `execute'
    from /Users/austin/.gem/ruby/2.3.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:111:in `compile'
    from /Users/austin/.gem/ruby/2.3.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:150:in `cook'
    from extconf.rb:364:in `block (2 levels) in process_recipe'
    from extconf.rb:257:in `block in chdir_for_build'
    from extconf.rb:256:in `chdir'
    from extconf.rb:256:in `chdir_for_build'
    from extconf.rb:363:in `block in process_recipe'
    from extconf.rb:262:in `tap'
    from extconf.rb:262:in `process_recipe'
    from extconf.rb:555:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /Users/austin/.gem/ruby/2.3.0/extensions/x86_64-darwin-15/2.3.0-static/nokogiri-1.6.8/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /Users/austin/.gem/ruby/2.3.0/gems/nokogiri-1.6.8 for inspection.
Results logged to /Users/austin/.gem/ruby/2.3.0/extensions/x86_64-darwin-15/2.3.0-static/nokogiri-1.6.8/gem_make.out
gem pristine nokogiri -v 1.6.8  9.23s user 7.56s system 92% cpu 18.089 total

When I do:
brew uninstall xz
gem install nokogiri -v 1.6.8

Nokogiri 1.6.8 installs correctly.

I had the same build failure. brew uninstall xz indeed allows nokogiri to compile.

Although the brew uninstall xz workaround did work for me, I also ran across #1445, which has the same compilation error. It turns out that running xcode-select --install also worked for me, though I could have sworn I had already run that months ago.

summoning @aramprice

tl;dr => xz installs a version of liblzma which can not be linked against when building nokogiri dependencies
Here's the info I've been able to dig up when running into this issue; resolved with the similar brew uninstall xz dance.
Looking in the .../nokogiri-1.6.8/mkmf.log there is the following message (in my case not at the end of the file):
ld: warning: ignoring file /usr/local/lib/liblzma.dylib, file was built for x86_64 which is not the architecture being linked (i386): /usr/local/lib/liblzma.dylib

It turns out that that /usr/local/lib/liblzma.dylib is part of the brew xz formulae:
brew info liblzma
lzma is now part of the xz formula.

Uninstalling allows the libxml compile to succeed. The unfortunate thing is that xz is a (recommended) dependency of ag (the_silver_searcher) so most people end up with it.
> brew info ag
the_silver_searcher: stable 0.32.0 (bottled), HEAD
Code-search similar to ack
https://github.com/ggreer/the_silver_searcher
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/the_silver_searcher.rb
==> Dependencies
Build: autoconf ✘, automake ✘, pkg-config ✘
Required: pcre ✘
Recommended: xz ✘
==> Options
--without-xz
	Build without xz support
--HEAD
	Install HEAD version

ld: warning: ignoring file /usr/local/lib/liblzma.dylib, file was built for x86_64 which is not the architecture being linked (i386): /usr/local/lib/liblzma.dylib

This sounds like you want to nudge people to brew install xz --universal. I'm unable to reproduce this specific example locally though with a vanilla brew install xz in /usr/local and gem 2.5.1, ruby 2.3.1p112.
************************************************************************
Extracting libxslt-1.1.29.tar.gz into tmp/x86_64-apple-darwin15.5.0/ports/libxslt/1.1.29... OK
Running 'configure' for libxslt 1.1.29... OK
Running 'compile' for libxslt 1.1.29... OK
Running 'install' for libxslt 1.1.29... OK
Activating libxslt 1.1.29 (from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/nokogiri-1.6.8/ports/x86_64-apple-darwin15.5.0/libxslt/1.1.29)...
checking for main() in -llzma... yes
checking for xmlParseDoc() in libxml/parser.h... yes
checking for xsltParseStylesheetDoc() in libxslt/xslt.h... yes
checking for exsltFuncRegister() in libexslt/exslt.h... yes
checking for xmlHasFeature()... yes
checking for xmlFirstElementChild()... yes
checking for xmlRelaxNGSetParserStructuredErrors()... yes
checking for xmlRelaxNGSetParserStructuredErrors()... yes
checking for xmlRelaxNGSetValidStructuredErrors()... yes
checking for xmlSchemaSetValidStructuredErrors()... yes
checking for xmlSchemaSetParserStructuredErrors()... yes
creating Makefile

@DomT4 installing with --universal seemed to resolve the issue.
I also tried --without-xz which resulted in another "incompatible architecture" error for iconv

which resulted in another "incompatible architecture" error for an iconv check

That's a bit odd. Anything in brew doctor or brew list | grep iconv?

No problems reported by brew doctor and nothing listed for iconv.
The actual culprit is probably further back in the mkmf.log. I'll try to reproduce the error from having ag installed --without-xz and post them.

If it helps anyone, I was able to get it build properly after a brew uninstall xz without having to do the recommended brew uinstall -force xz thus leaving xz 5.2.1 still on the computer. I don't know if this is good or bad though.

Duplicated with on the following configuration:
→ uname -a
Darwin HOSTNAME 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

→ /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -v
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
  Gem::VERSION => 2.6.4
  Bundler::VERSION => 1.12.5

→ brew -v
Homebrew 0.9.9 (git revision 11d4; last commit 2016-06-08)
Homebrew/homebrew-core (git revision 2343; last commit 2016-06-10)

→ brew info xz
xz: stable 5.2.2 (bottled)
General-purpose data compression with high compression ratio
http://tukaani.org/xz/
/usr/local/Cellar/xz/5.2.2 (91 files, 1.4M) *
  Poured from bottle on 2016-06-10 at 14:45:50
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/xz.rb
==> Options
--universal
	Build a universal binary

→ xcode-select -p
/Library/Developer/CommandLineTools

Output from bundle:
Installing nokogiri 1.6.8 with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: tmp/ruby/2.0.0/gems/nokogiri-1.6.8/ext/nokogiri
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -r ./siteconf20160610-69863-1yfw0mn.rb extconf.rb
Using pkg-config version 1.1.7
checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
Using mini_portile version 2.1.0
checking for iconv.h... yes
checking for gzdopen() in -lz... yes
checking for iconv... yes
************************************************************************
IMPORTANT NOTICE:

Building Nokogiri with a packaged version of libxml2-2.9.4.

Team Nokogiri will keep on doing their best to provide security
updates in a timely manner, but if this is a concern for you and want
to use the system library instead; abort this installation process and
reinstall nokogiri as follows:

    gem install nokogiri -- --use-system-libraries
        [--with-xml2-config=/path/to/xml2-config]
        [--with-xslt-config=/path/to/xslt-config]

If you are using Bundler, tell it to use the option:

    bundle config build.nokogiri --use-system-libraries
    bundle install

Note, however, that nokogiri is not fully compatible with arbitrary
versions of libxml2 provided by OS/package vendors.
************************************************************************
Extracting libxml2-2.9.4.tar.gz into tmp/x86_64-apple-darwin15/ports/libxml2/2.9.4... OK
Running 'configure' for libxml2 2.9.4... OK
Running 'compile' for libxml2 2.9.4... ERROR, review 'tmp/ruby/2.0.0/gems/nokogiri-1.6.8/ext/nokogiri/tmp/x86_64-apple-darwin15/ports/libxml2/2.9.4/compile.log' to see what happened. Last lines are:
========================================================================
  CCLD     libxml2.la
  CC       testdso.lo
  CCLD     testdso.la
  CC       xmllint.o
  CCLD     xmllint
ld: warning: ignoring file /usr/local/Cellar/xz/5.2.2/lib/liblzma.dylib, file was built for x86_64 which is not the architecture being linked (i386): /usr/local/Cellar/xz/5.2.2/lib/liblzma.dylib
Undefined symbols for architecture i386:
  "_lzma_auto_decoder", referenced from:
      _xz_head in libxml2.a(xzlib.o)
  "_lzma_code", referenced from:
      _xz_decomp in libxml2.a(xzlib.o)
  "_lzma_end", referenced from:
      ___libxml2_xzclose in libxml2.a(xzlib.o)
  "_lzma_properties_decode", referenced from:
      _is_format_lzma in libxml2.a(xzlib.o)
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [xmllint] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
========================================================================
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=.
	--curdir
	--ruby=/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
	--help
	--clean
	--use-system-libraries
	--enable-static
	--disable-static
	--with-zlib-dir
	--without-zlib-dir
	--with-zlib-include
	--without-zlib-include=${zlib-dir}/include
	--with-zlib-lib
	--without-zlib-lib=${zlib-dir}/lib
	--enable-cross-build
	--disable-cross-build
tmp/ruby/2.0.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:366:in `block in execute': Failed to complete compile task (RuntimeError)
	from tmp/ruby/2.0.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in `chdir'
	from tmp/ruby/2.0.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in `execute'
	from tmp/ruby/2.0.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:111:in `compile'
	from tmp/ruby/2.0.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:150:in `cook'
	from extconf.rb:364:in `block (2 levels) in process_recipe'
	from extconf.rb:257:in `block in chdir_for_build'
	from extconf.rb:256:in `chdir'
	from extconf.rb:256:in `chdir_for_build'
	from extconf.rb:363:in `block in process_recipe'
	from extconf.rb:262:in `tap'
	from extconf.rb:262:in `process_recipe'
	from extconf.rb:555:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  tmp/ruby/2.0.0/extensions/universal-darwin-15/2.0.0/nokogiri-1.6.8/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in tmp/ruby/2.0.0/gems/nokogiri-1.6.8 for inspection.
Results logged to tmp/ruby/2.0.0/extensions/universal-darwin-15/2.0.0/nokogiri-1.6.8/gem_make.out

Contents of mkmf.log:
→ cat ruby/2.0.0/extensions/universal-darwin-15/2.0.0/nokogiri-1.6.8/mkmf.log
"xcrun clang -o conftest -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS  conftest.c  -L. -L/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib -L. -L/usr/local/lib   -arch x86_64 -arch i386   -lruby.2.0.0  -lpthread -ldl -lobjc  "
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */

"xcrun clang -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS   -arch x86_64 -arch i386  -c conftest.c"
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main() {return 0;}
/* end */

"xcrun clang -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS  -Wno-error=unused-command-line-argument-hard-error-in-future  -arch x86_64 -arch i386  -c conftest.c"
warning: unknown warning option '-Werror=unused-command-line-argument-hard-error-in-future'; did you mean '-Werror=unused-command-line-argument'? [-Wunknown-warning-option]
1 warning generated.
warning: unknown warning option '-Werror=unused-command-line-argument-hard-error-in-future'; did you mean '-Werror=unused-command-line-argument'? [-Wunknown-warning-option]
1 warning generated.
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main() {return 0;}
/* end */

have_header: checking for iconv.h... -------------------- yes

"xcrun clang -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS   -arch x86_64 -arch i386  -c conftest.c"
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: #include <iconv.h>
/* end */

--------------------

have_library: checking for gzdopen() in -lz... -------------------- yes

"xcrun clang -o conftest -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS  conftest.c  -L. -L/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib -L. -L/usr/local/lib   -arch x86_64 -arch i386   -lruby.2.0.0 -lz  -lpthread -ldl -lobjc  "
checked program was:
/* begin */
 1: #include "ruby.h"
 2:
 3: #include <zlib.h>
 4:
 5: /*top*/
 6: extern int t(void);
 7: int t(void) { void ((*volatile p)()); p = (void ((*)()))gzdopen; return 0; }
 8: int main(int argc, char **argv)
 9: {
10:   if (argc > 1000000) {
11:     printf("%p", &t);
12:   }
13:
14:   return 0;
15: }
/* end */

--------------------

have_iconv?: checking for iconv... -------------------- yes

"xcrun clang -o conftest -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS  conftest.c  -L. -L/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib -L. -L/usr/local/lib   -arch x86_64 -arch i386   -lruby.2.0.0  -lpthread -ldl -lobjc  "
Undefined symbols for architecture x86_64:
  "_iconv", referenced from:
      _main in conftest-ba1623.o
  "_iconv_open", referenced from:
      _main in conftest-ba1623.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
checked program was:
/* begin */
 1: #include "ruby.h"
 2:
 3: #include <stdlib.h>
 4: #include <iconv.h>
 5:
 6: int main(void)
 7: {
 8:     iconv_t cd = iconv_open("", "");
 9:     iconv(cd, NULL, NULL, NULL, NULL);
10:     return EXIT_SUCCESS;
11: }
/* end */

"xcrun clang -o conftest -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/universal-darwin15 -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward -I/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT    -g -Os -pipe -DHAVE_GCC_SYNC_BUILTINS  conftest.c  -L. -L/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib -L. -L/usr/local/lib   -arch x86_64 -arch i386   -lruby.2.0.0 -liconv -lpthread -ldl -lobjc  "
checked program was:
/* begin */
 1: #include "ruby.h"
 2:
 3: #include <stdlib.h>
 4: #include <iconv.h>
 5:
 6: int main(void)
 7: {
 8:     iconv_t cd = iconv_open("", "");
 9:     iconv(cd, NULL, NULL, NULL, NULL);
10:     return EXIT_SUCCESS;
11: }
/* end */

--------------------

This worked for me:
gem install nokogiri -- --with-xml2-include=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/libxml2 --use-system-libraries

This worked for me when attempting to install github/pages-gem. Thanks @md5.

xcode-select --install worked for me

Related or dupe to #1486? Given that (subjectively) the symptoms and solution were similar.

I had the same nokogiri install problem. My repo folder was in a box.com sync folder. I moved it to another folder and it installed without any problems. So make sure that you are not using a box.com folder.
Thanks

xcode-select --install worked for me.

xcode-select --install worked for me.

brew unlink xz is enough, you don't have to uninstall it. It worked for me on CentOS7

@njia Yes. You will need to relink it before you do almost anything else with brew, and xcode-select --install did not work for me recently (because I had done it more than a year ago).

before bundle install , you should run this command bundle config build.nokogiri --use-system-libraries --with-xml2-include=/usr/include/libxml2/
or add config in project project_path/.bundle/config and add the content into it
---
BUNDLE_PATH: vendor/bundle
BUNDLE_BUILD__MYSQL: "--with-mysql-config=/usr/local/bin/mysql_config"

As per @wenweih, following worked instead of doing brew uninstall xz
brew install libxml2
bundle config build.nokogiri --use-system-libraries --with-xml2-include=/usr/local/opt/libxml2/include/libxml2
bundle install
# or if updating github-pages gem
bundle update github-pages

My gemfile for github-pages based website:
source 'https://rubygems.org'

group :jekyll_plugins do
gem 'github-pages', '>= 78'
end

group :jekyll_misc_plugins do
gem 'jekyll-compose', '>= 0.4.1'
gem 'font-awesome-sass', '>= 4.6.2'
gem 'travis', '>= 1.8.2'
gem 'jekyll-mentions', '>= 1.1.2'
end

same issue ,use jekyll on mac... uninstalled xz,it works for me...but i do not really know what is xz...

I tried all of the above to no avail. For me, the solution was to use rvm to manage my version of ruby. I could then install nokogiri fine!
\curl -sSL https://get.rvm.io | bash -s stable --ruby

brew uninstall xz
gem install rails
Worked for me! Thanks y'all!

It's not particularly brew but related. I use macports and had the same issue. I could solve it by re-installing xz from sources instead of the pre-compiled binary (takes a while ;)):
sudo port -s -v install xz +universal

I had the similiar nokogiri install problem
A little bit different :
seems failed at compiler step:
checking if the C compiler accepts ... *** extconf.rb failed ***
gem install nokogiri -v '1.6.8'
or
gem install nokogiri -v 1.6.8 -- --with-iconv-dir=xcode-select -p/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr --with-xml2-include=xcode-select -p/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/libxml2
Here is the whole error log:
Building native extensions.  This could take a while...
ERROR:  Error installing nokogiri:
ERROR: Failed to build gem native extension.
/Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/bin/ruby -r ./siteconf20160916-11734-hblu9v.rb extconf.rb

Using pkg-config version 1.1.7
checking if the C compiler accepts ... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.
Provided configuration options:
--with-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/bin/ruby
--help
--clean
/Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:381:in try_do': The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first.         from /Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:491:in block in try_compile'
from /Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:441:in with_werror'         from /Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:491:in try_compile'
from extconf.rb:138:in nokogiri_try_compile'         from extconf.rb:162:in block in add_cflags'
from /Users/nywlsb/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/mkmf.rb:535:in with_cflags'         from extconf.rb:161:in add_cflags'
from extconf.rb:414:in `'
extconf failed, exit code 1
Gem files will remain installed in<EMAIL_ADDRESS>for inspection.
any ideas guys

removing macports bin from $PATH resolves this issue for me on macOS sierra (10.11)

brew doctor mentioned: Your system is ready to brew. BEFORE I ran xcode-select --install as suggested above to fix this issue!
I'm on:

macOS Sierra Version 10.12
Xcode Version 8.0 (8A218a)
xcode-select --version 2345.1. (I do not know what it was before I did the --install)
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
nokogiri-1.6.8 (now installed successfully)

If someone can boil down the advice here into a PR for the installation tutorial, I'd be very grateful.

brew unlink xz
gem install nokogiri

did the trick for me.

If someone can boil down the advice here into a PR for the installation tutorial, I'd be very grateful.

I don't think uninstalling packages should be the proper solution. What is wrong with updating the Command Line Tools (xcode-select --install)? I think the bigger problem is why brew doctor didn't mention that it needed to be done.

@esambo Because xcode-select --install doesn’t actually work for everyone. I’m completely up to date with the Xcode Command Line Tools and I cannot install Nokogiri without doing brew unlink xz; gem install nokogiri; brew link xz, or without doing the universal install (brew install xz --universal) which I never remember to do because I’ve never installed xz directly, but only as a transitive dependency (and there are lots of Homebrew things which require it transitively).
IMO, @flavorjones, this should not be closed until there is a PR as you have requested, although I would agree that this thread should probably be locked because of the mixed information in the thread. The real problem is that Homebrew (without --universal) installs versions which are x64-only, but the Nokogiri and/or Ruby builds are x86 and x64 universal, which are not compatible with x64-only libraries.

xcode-select --install did not work for me. Currently a blocking issue on updating other gems.

@halostatue I'd greatly appreciate if someone who cares deeply about OSX support would submit a PR to the documentation.
You clearly know more than I do about OSX binaries and support, and I have no way to either reproduce this error nor verify that what you're suggesting is correct, as I'm a Linux user. So I'd like to gently suggest that you're in a better position than I am to craft clear instructions for future OSX users of Nokogiri.

brew uinstall -force xz worked for me, so far, I think...

xcode-select --install worked for me.

Seemed to work for me too, thanks!
On Oct 7, 2016 9:54 PM, "Caio César"<EMAIL_ADDRESS>wrote:

xcode-select --install worked for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1483#issuecomment-252402943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCnbKdI888VXkj6EuUhn800CeQYPKHkks5qxyHvgaJpZM4IwSGE
.

As per @dyndna and @wenweih, the following worked for me for a related problem
brew install libxml2
bundle config build.nokogiri --use-system-libraries --with-xml2-    include=/usr/local/opt/libxml2/include/libxml2
bundle install

See here for complete discussion: http://stackoverflow.com/questions/39937394/gem-install-nokogiri-v-1-6-8-1-fails/
MacOSX Sierra, Ruby 2.3.1

@MtnBiker, can you please retry without the homebrew libxml2 and using the brew unlink xz; bundle install; brew link xz? At some point, I’m going to put together a PR for the installation document as @flavorjones requested, and while xcode-select --install will work for some, your solution is strongly recommended against by the Nokogiri team because they have a patched version of libxml2 that they prefer to use.

@halostatue The key word in my response was "related." I'm not (knowingly anyway) using xz. Someone posted a link to this thread in response to a problem I was having with nokigiri. So trying what you suggest probably doesn't make sense in my case. And in any case since things are working now I'm not going to mess with it.

@MtnBiker; if you’re using homebrew, you’re probably using xz whether you realize it or not. If you ran brew uses --installed xz, you will probably see results. On my system, imagemagick, io, python3, and the_silver_searcher all depend on xz.

@halostatue brew unlink xz; bundle install; brew link xz ran without problems. Does that show that it would have solved the nokogiri problem?
I was going to ask earlier how to determine dependencies, but you answered it. Hence by following through on your original request.

It seems that it would have.

bundle config build.nokogiri --use-system-libraries --with-xml2-include=/usr/local/opt/libxml2/include/libxml2 worked for me.

had the same error (unsigned short) when trying to install nokogiri.
I'd updated xcode from 7.x to 8 about an hour prior but had yet to update command line so xcode-select --install worked for me.

Documentation is now online for brew unlink xz.

Same problem here, had to: brew unlink xz; gem install nokogiri; brew link xz

xcode-select --install   worked for me

I also need to do : brew unlink xz; gem install nokogiri; brew link xz
not solved via : xcode-select --install

All of this is in the installation tutorial!
http://www.nokogiri.org/tutorials/installing_nokogiri.html#mac_os_x
Locking this issue.


Add initial install diagrams for style and content suggestions

What this PR does / why we need it:
This PR is for discussing the kots install diagrams.
Which issue(s) this PR fixes:

No issue, this is to hopefully help people understand kots workflows better.
Special notes for your reviewer:

These are incomplete and I'm putting them up here as an example for critique before spending too much more time finishing the diagrams. It took me a while to figure out a good way to display an appropriate level of detail and context without being mostly noise.
There are two charts here. The first is a sequence diagram of the communication between kots, k8s, docker, and kotsadm parts. The second is a higher level flow chart of the kots cli install process.
Steps to reproduce

To rebuild the images:
cd kots/design/diagrams
yarn install
yarn run build

Does this PR introduce a user-facing change?

NONE

Does this PR require documentation?

NONE

What do you think about the level of detail in these diagrams? Would it be useful to indicate better which function and file each step is in, maybe with boxed and colored backgrounds with this info? How about the presentation of what data kots sends to k8s (and other components) in the sequence diagram, does that make sense? Would more notes describing higher level process and the reason why it's happening help or just be clutter?

Also, these are very incomplete as they're the first iteration of the diagrams that I thought weren't confusing and way too busy

What about the level of Kubernetes details? I wasn't sure if I should explain what each Kubernetes request is doing and why it's used in the context of an install. Is everyone familiar enough with what it means to create things like configmaps, secrets, namespaces, deployments, and services?


Custom colors for lyrics

Description of the new feature / enhancement
Hi there! Is there a way to accomplish this?

Add the possibility for users to customize the lyrics colors, since the current colors are too bright and cause eye strain

If indeed it is possible but it proves it would take too much work, would it be at least possible to set as default the colors of the lyrics following the color scheme from the second picture?
Thank you!
📸 Screenshots
How lyrics  currently look like (on Spotify for Windows <IP_ADDRESS>5.g464c973a):
Colors displayed for the lyrics of the song: Godsmack - Bulletproof

How lyrics would look like if the following colors would be applied:
Background: #000000 #121212
Past lyrics: #E40909B3 <- this hex is expressed as an RGBA value, it has 8 digits (I don't know if Spotify would support that)
Current lyrics: #C2C2C2
Next lyrics: #CA861A
"Lyrics provided by Musicmatch": #C2C2C2
Lyrics hover: #C2C2C2

Can be implemented as an additional function through incoming parameters
Any ideas with other color options?
I suggest leaving the background everywhere at #121212, so as not to spoil the main theme

That's really nice! Yeah, no problem, let's keep #121212 for the background color then.
This could be another color scheme:
https://coolors.co/121212-67697c-c2c2c2-008148

I don't have any other color schemes for now, as I don't know what you might like.
You can notice in the image that I locked down the background color (#121212) and the current lyrics color (#c2c2c2) while I pressed spacebar to auto generate the other colors. If you want, you can give it a try on that site and pick some colors schemes you'd like.
A, you can also notice that the link to the color scheme has all the hexadecimals colors in the same order they appear on the site:<PHONE_NUMBER>7c-c2c2c2-008148
It even has an "Adjust palette" section, where you can tweak the colors some more, like here:

I tried to check the contrast of the colors in Firefox for Spotify web player with my first color scheme, but unfortunately it doesn't work. I did to see if the different colored text on that black background passed the checks. You can see down below that white 4 on that black orange didn't pass the check, getting a 2.45 rating.
For some reason Firefox can't analyze the colors, like it does in this example with Wikipedia:

Chrome had something similar in the past, but they removed it in the latest versions, it was called CSS Overview. I'll see tomorrow if I can get my hands on an older version of Chrome and test it out. I just want to do this mostly out of curiosity.
What do you think, should we check the color contrast or should we just wing it? From the looks of it, Spotify didn't bother with it either.
P.S:
Could you tell me how you inserted that circle to match the color of the hex?

I was wrong about CSS Overview, it's still in Chrome, it seems I read an older article. Here's the result for the first color scheme:

This issue is related to the past lyrics color being #e40909b3 (dark red), but even with this issue it seems fine to me.
There was one more issue, where "Lyrics provided by Musicmatch" color was white, but now I switched it to #C2C2C2 and it seems fine, as it passed the CSS Overview test, as seen in the top picture.
Here's how it looks now:

I also switched the lyrics hover color to #C2C2C2.
You can see the changes I've made over here, in the first post.

Added a couple of 4 color options,
1 - black and white
2 - dark yellow
3 - pink
4 - theme @CanYouJustWorkPlease
to set the desired theme, use the incoming parameter lyrics_stat
For example I want to install theme 4: -lyrics_stat 4

If you have any ideas to add new theme, then throw it here, for example:
past lyrics - #ffffff4a
current lyrics - #ffffffc7
next lyrics - #ffffff4a
background of lyrics - #121212
presented maxmatch - #ffffff94

That's really nice! Thank you! :^D
Sure, if I'll get other themes, I'll post them here.
Just one question, what color will have the hover over the lyrics, as I'm seeing it missing from the colors attributes, will it inherit the color from current lyrics?

will it inherit the color from current lyrics?

right

will it inherit the color from current lyrics?

right

I was wrong, he did not inherit the color
added a new parameter lyrics on hover in the post above, in themes that have already been added inherited the color from current lyrics.
There are also lyrics without synchronization, now they inherit the color from the current lyrics

I see. If it's not too much too ask, would it be possible to make them independent of each other, meaning current lyrics and lyrics on hover get to keep their own colors?

they are independent
but in your theme you specified the same color for current and hover (#C2C2C2)
you can suggest a new profile for your theme, i will update.

That's really nice. :^D
I picked lyrics on hover to be #0FD40F
The whole theme over here:
past lyrics - #E40909B3
current lyrics - #C2C2C2
next lyrics - #CA861A
lyrics on hover - #0FD40F
background of lyrics - #121212
txt by Musicmatch - #C2C2C2
Thank you! You are awesome! :^D

updated

Hmm, it seems past lyrics is getting applied a filter which makes the color darker, tested with Spotify for desktop with the themes implemented by you. 'past lyrics` is the only one that gets applied a filter, out of the 6 attributes. I've seen the same behavior for Spotify web player.
As an example, I used the same colors for  past lyrics and next lyrics, respectively #895502, but in turn, past lyrics received #654006, while next lyrics received #895502, as seen below:

I used Just Color Picker to get the colors:

for past lyrics:

for next lyrics:

If you're using a blue filter app, please disable it, otherwise it's possible that Just Color Picker won't pick the real color. It happened in my case with CareUEyes.
Could you make it possible for past lyrics to keep its real color, meaning to receive #895502, instead of receiving #654006, in this case?

A, it seems on Spotify web player past lyrics has been applied an opacity of 0.7

, so I guess it's the same for Spotify Desktop.

Hmm, I've done some more tests, and it seems the 0.7 opacity for Spotify web player actually makes the color brighter, not darker. So, I'm not sure what's different for Spotify Desktop.
Example using #895502 for both past lyrics and next lyrics, tested on Spotify web player:

In this case past lyrics turns brighter, respectively #8E6A30, instead of turning darker, as for the case of Spotify Desktop.

fixed attribute for past lyrics

That's really nice. :^D
I picked lyrics on hover to be #0FD40F
The whole theme over here:
past lyrics - #E40909B3 current lyrics - #C2C2C2 next lyrics - #CA861A lyrics on hover - #0FD40F background of lyrics - #121212 txt by Musicmatch - #C2C2C2
Thank you! You are awesome! :^D

how to apply this theme

@GREEKY69
-lyrics_stat brown

What about when playing on fullscreen? Since there's a feature that can either show the album art or the lyrics of the song. The theme works great but the fullscreen version still has colors based  on the album art (I assume).
Lyrics with theme (royal):

Lyrics on fullscreen mode (still with the theme applied):

Hello, I also wanted to add a theme if that's possible. it's basically a combination of a few of the existing themes. It would be great if you could add it.
Name: lavender
past lyrics - #B8A2EA
current lyrics - #8462DD
next lyrics - #575757
hover - #F2F2F2
background of lyrics - #121212
maxmatch - #C2C2C2
By the way, sorry if I'm reviving an old thread. I'm very new to GitHub and I couldn't find a way to create a new thread.

sorry if I'm reviving an old thread.

it's okay, this topic was created just for this
at first glance your theme looks like "royal" or am I mistaken?

That's cool. Yes my theme used was indeed "royal

at first glance your theme looks like "royal" or am I mistaken?

No, you're right. It's basically the royal theme with a darker background and mixed a little with the purple theme as well

@amd64fox i'm wondering if you'll be adding themes for spotX, that would be a great addition! If ever that's the case, I would suggest either integrating it into the app or (which i think would be what you'd do) is add it as options for the powershell command just like the lyric themes

at first glance your theme looks like "royal" or am I mistaken?

No, you're right. It's basically the royal theme with a darker background and mixed a little with the purple theme as well.

Is it possible adding it? Thanks in advance

@PetelAnavim added

@PetelAnavim added
Thanks very much

Hi, I want to add a theme if that's possible. It's basically like a spotify theme with some tweaks (I tried to match the background to the color of the lyrics bar (?) on the side panel)

Name : alter  (I don't have any idea for the name lol)
past lyrics - #9b9b9b
current lyrics - #1ed760
next lyrics - #666666
hover - #f2f2f2
background of lyrics - #242424
maxmatch- #C2C2C2

@amd64fox
Hi, I want to add a theme. It's basically like a spotify theme with some tweaks (I tried to match the background to the color of the lyrics bar (?) on the side panel)

Name : alter  (I don't have any idea for the name lol)
past lyrics - #9b9b9b
current lyrics - #1ed760
next lyrics - #666666
hover - #f2f2f2
background of lyrics - #242424
maxmatch- #C2C2C2

added it with the name spotify#2
Thanks

added it with the name spotify#2

Thank you very much

Hello! I've been using this app for awhile and just did a clean windows install so ended up on the FAQs of all my fav apps!
I noticed the BG of spotify is close to gruvbox material so here's a lyric theme based on that.
past lyrics - #282828
current lyrics - #d4be98
next lyrics - #7c6f64
hover - #e78a4e
background of lyrics - #121212
maxmatch- #282828
Also >tfw when you're trying to find what classes color the text you want

thanks, come up with a one word title for your topic, here is a list of existing ones

@GREEKY69 -lyrics_stat relish

sorry if its a dumb question, but can you tell me where do i need to type that in?

sorry if its a dumb question, but can you tell me where do i need to type that in?

iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/spotx-official.github.io/main/run.ps1') } -new_theme -lyrics_stat relish"


Locale instead of language is used in resource path when using Zend_Validate

I consider this an inconsistency:

It seems to also have made it into ZF2: https://github.com/zendframework/zend-i18n-resources/tree/master/languages
Any specific reason for this?
Based on the peferred user language we register a validator for Form Validation. However, for users with Portuguese as preferred language (either Locale: pt_BR, pt_PT, pt_AO..., resulting in 'language = pt') this fails, since the file will not exist:  resources/languages/pt/Zend_Validate.php.

@holtkamp
We need a test case for the problem. Maybe like this one?!


bug: colorscheme not loaded

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
v0.10.1
Operating system/version
ArchLinux
Describe the bug
Colorschemes for a given session are not restored.
What is the severity of this bug?
annoyance
Steps To Reproduce

Open a new session
Change the colorscheme with colorscheme
Close nvim
OPen the session again

Expected Behavior
With mksession, the colorscheme for a given session is restored.
I like to use distinct colorschemes for different projects because they fit better to that project and its programming language.

@uwla I'm seeing the same issue here. To be exact, is it the "color scheme" not loading or is it the "highlighting"? I thought it was the syntax highlighting that isn't working or at least it looks like it does not. Because, when I :TSConfigInfo, it showed highlight: { enable: false } so I :TSEnable highlight or :TSToggle highlight to get the highlighting back. But then, for some reason, the syntax highlight is gone even though highlight is enabled 😅. You can get your colors back with :e more conveniently? I guess.
I'm not familiar with neovim sessions so I might have missed out some of the steps I need to handle when dealing with sessions on my config though. Here's the resession config and neo-tree config.
return {
  "stevearc/resession.nvim",
  config = function()
    local resession = require("resession")
    resession.setup({})

    -- Get session name
    local function get_session_name()
      local is_git_repo = vim.trim(vim.fn.system("git rev-parse --is-inside-work-tree"))

      if is_git_repo == "true" then
        return vim.trim(vim.fn.system("git rev-parse --show-toplevel"))
      else
        return vim.trim(vim.fn.getcwd())
      end
    end

    -- Save session
    local function save_session()
      require("resession").save(get_session_name(), { dir = "dirsession", notify = false })
    end

    -- Load session
    ---@class LoadSessionOption
    ---@field name string?
    ---@param load_session_opts LoadSessionOption?
    local function load_session(load_session_opts)
      local session = load_session_opts and load_session_opts.name or nil

      -- load session
      local ok = pcall(function()
        resession.load(session or get_session_name(), { dir = "dirsession", notify = false })
      end)

      -- if didn't load, like in new session, instead save session
      if not ok then
        save_session()
      end

      -- @NOTE: might be a bug
      -- reload buffer because ts won't update highlight when session changes
      vim.cmd("silent! :e")
    end

    -- Delete session
    local function delete_session()
      pcall(function()
        resession.delete(get_session_name(), { dir = "dirsession" })
      end)
    end

    -- Show sessions list
    local function show_sessions()
      -- get sessions list
      local session_list = resession.list({ dir = "dirsession" })

      -- rename session names with "/" instead of "_"
      local new_session_list = vim.tbl_map(function(session)
        local name = string.gsub(session, "_", "/")
        return name
      end, session_list)

      -- show sessions a list
      vim.ui.select(new_session_list, {
        prompt = "Select Session",
        telescope = require("telescope.themes").get_dropdown({
          initial_mode = "normal",
        }),
      }, function(selected)
        if selected == nil then
          return
        end

        -- sync selected session and current session name to the same separator("/")
        local selected_session_name = selected and string.gsub(selected, "/", "_") or ""
        local current_session_name = require("resession").get_current()
        current_session_name = current_session_name and string.gsub(current_session_name, "/", "_") or ""

        -- do nothing if same session is selected
        if selected_session_name == current_session_name then
          return
        end

        -- write changes to the files that been modified before session changes
        vim.cmd("silent! :bufdo update!")
        -- before loading a new session, save the current session
        save_session()

        load_session({
          name = selected,
        })
      end)
    end

    vim.keymap.set("n", "<leader>qs", save_session, { desc = "save session" })
    vim.keymap.set("n", "<leader>ql", show_sessions, { desc = "show sessions" })
    vim.keymap.set("n", "<leader>qd", delete_session, { desc = "delete session" })

    vim.api.nvim_create_autocmd("VimEnter", {
      callback = function()
        -- Only load the session if nvim was started with no args
        if vim.fn.argc(-1) == 0 then
          load_session({})
        end
      end,
    })
    vim.api.nvim_create_autocmd("VimLeavePre", {
      callback = function()
        -- save_session()
        resession.save_all()
      end,
    })
  end,
}

return {
  "nvim-neo-tree/neo-tree.nvim",
  opts = {
    buffers = {
      follow_current_file = {
        enabled = true, -- This will find and focus the file in the active buffer every time
        leave_dirs_open = true, -- `false` closes auto expanded dirs, such as with `:Neotree reveal`
      },
    },
    filesystem = {
      bind_to_cwd = false,
    },
    ...

Made neotree(any plugin that might change cwd) file system bind to false. Thought that would be easier to manage sessions than jumping around cwds.
+ And it's not respecting the last buffer I exited again.

@uwla Yeah I see. Even though the issues may not seem exactly the same, it looks like to me, that we have to deal with or handle some left-over states of the prior session before/after loading a new session? Hence the hook functions. But not really sure though.
Maybe @stevearc can help a little? Like are we saving modified buffers(for now, if I'm not mistaken it does not? so did it myself) before leaving the session or is there anything we have to clean up before or after loading a new session? Why some of us are having tree-sitter related issues?

I have the same issue. The highlighting is not loaded.

Until now, colorscheme was actually not one of the things that resession saved & restored. I just added a built-in extension that will do that for you if you want. As for the highlights not activating on session restore, I've seen this occasionally, but it's been hard to pin down. Please file a new issue if you manage to get a solid repro.


0.13.3: SIGSEGV

when isMainModule:
  import futhark

  importc:
    path: "/Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/usr/include"
    rename "u_int", "u_intt"
    "sys/sysctl.h"

  echo "a"

0.13.2: a
0.13.3:
/Users/u/ttop/src/ttop/procfs.nim(4, 8) [DuplicateModuleImport]
SIGSEGV: Illegal storage access. (Attempt to read from nil?)

It shouldn't make a difference, but could you try to remove the : after path? It's not supposed to be there.
Not sure what might be causing this, and without a Mac to debug on it would be very hard for me to find out. Does Futhark generate bindings correctly? Or is this the Nim compiler crashing?

I fixed a SIGSEGV bug today with the 0.13.4 release, could you try that and see if it is the same one?


Update to docker package

I'm upgrading the docker graders for my course and would love to use more of the architecture provided by Coursera. However, I currently cannot run any of the running/testing environment.
It seems that the interaction with Docker is based around a package called docker-py (version 1.10.4) which is incompatible with the current version of Docker on MacOS. Currently my grader has some pytest testing which uses the docker package (version 4.4.1), which does seem to work.
I had a quick look and it looks like both packages point to the same repository, but that the former was discontinued and replaced by the latter. It would be great if you could upgrade the package to use this newer version so it is usable on more systems.

Hi Dekker1,
It is not clear to me. Are you requesting us to upgrader docker-py version? I believe we can update the version in setup.py. I appreciate making changes locally and verify the expected behavior. It looks like the next docker-py version is 1.10.6. Also what is your docker version on your MacOS?
Please feel free to create a PR and we will review/test them soon.
Thank you,
Sashi.

Hi Dekker1,
It is not clear to me. Are you requesting us to upgrader docker-py version? I believe we can update the version in setup.py. I appreciate making changes locally and verify the expected behavior. It looks like the next docker-py version is 1.10.6. Also what is your docker version on your MacOS?
Please feel free to create a PR and we will review/test them soon.
Thank you,
Sashi.

Hi Sashi,
I'm running Docker version 3.1.0 on macOS Big Sur.
What I'm referring to is not just to update the docker-py package from PyPI (https://pypi.org/project/docker-py/), which was last updated more than 4 years ago, but to switch to the newer docker package (https://pypi.org/project/docker/), which received updates until a month ago. On PyPI both packages refer to the same source location so I assume that the docker-py package is a deprecated version of the newer docker package.

Hi Sashi,
I'm running Docker version 3.1.0 on macOS Big Sur.
What I'm referring to is not just to update the docker-py package from PyPI (https://pypi.org/project/docker-py/), which was last updated more than 4 years ago, but to switch to the newer docker package (https://pypi.org/project/docker/), which received updates until a month ago. On PyPI both packages refer to the same source location so I assume that the docker-py package is a deprecated version of the newer docker package.

I made a PR in #18 you might want to try. It uses the new docker package. @Dekker1


Error 403 Forbidden on Soundcloud

[x] I've verified and I assure that I'm running youtube-dl 2016.05.01

And I have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of the issue?

[x] Bug report (encountered problems with youtube-dl)

The purpose of this issue is a bug report, output as follows:
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.05.01
[debug] Python version 3.4.3 - Darwin-15.4.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
...
<end of log>

Description of your issue, suggested solution and other information
I have used youtube-dl to download from a playlist on soundcloud. The playlist contains 238 items of various sizes. After downloading 38 items, I received an error 403 forbidden.
I then switched to another wifi in a different location altogether and tried to resume the download at item 38, with the same error. At item 39, with the same error.
I am unable to download from that soundcloud playlist, even when I use the personal credentials of the person who made that list.
The command line I have tried using are (one on each line):
youtube-dl https://soundcloud.com/evurutin/likes --playlist-start 38
youtube-dl https://soundcloud.com/evurutin/likes --playlist-start 39
youtube-dl https://soundcloud.com/evurutin/likes --playlist-start 38 --extract-audio
youtube-dl https://soundcloud.com/evurutin/likes --playlist-start 38 -u (that person's username) -p (that person's password)

And in all cases I obtain the same error
[download] Downloading video 1 of 201
[soundcloud] christineandthequeens/christine-paradis-remix: Resolving id
[soundcloud] christineandthequeens/christine-paradis-remix: Downloading info JSON
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Nothing from the database here shows me anything useful about what I can do to solve the issue.
I hope I am writing this correctly. Please let me know if any additional information is needed.
Thank you

Post the full output of youtube-dl when run with -v, i.e. add -v flag to your command line, copy the whole output and post it in the issue body wrapped in ``` for better formatting. It should look similar to this:
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.06
[debug] Git HEAD: 135392e
[debug] Python version 2.6.6 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...

Do not post screenshots of verbose log only plain text is acceptable.
The output (including the first lines) contains important debugging information. Issues without the full output are often not reproducible and therefore do not get solved in short order, if ever.

Hello,
I am sorry, I had misunderstood.
Here it is:
debug] System config: []
[debug] User config: []
[debug] Command-line args: ['https://soundcloud.com/evurutin/likes', '--playlist-start', '39', '--extract-audio', '-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.05.01
[debug] Python version 3.4.3 - Darwin-15.4.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[soundcloud:user] evurutin: Downloading user info
[soundcloud:user] evurutin: Downloading track page 1
[soundcloud:user] evurutin: Downloading track page 2
[soundcloud:user] evurutin: Downloading track page 3
[soundcloud:user] evurutin: Downloading track page 4
[soundcloud:user] evurutin: Downloading track page 5
[soundcloud:user] evurutin: Downloading track page 6
[download] Downloading playlist: EvUrutin (Likes)
[soundcloud:user] playlist EvUrutin (Likes): Collected 238 video ids (downloading 200 of them)
[download] Downloading video 1 of 200
[soundcloud] christineandthequeens/it-1: Resolving id
[soundcloud] christineandthequeens/it-1: Downloading info JSON
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 388, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1942, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 469, in open
    response = meth(req, response)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 579, in http_response
    'http', request, response, code, msg, hdrs)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 501, in error
    result = self._call_chain(*args)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 441, in _call_chain
    result = func(*args)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 684, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 469, in open
    response = meth(req, response)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 579, in http_response
    'http', request, response, code, msg, hdrs)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 507, in error
    return self._call_chain(*args)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 441, in _call_chain
    result = func(*args)
  File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 587, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

File "/Users/mehdy/anaconda/lib/python3.4/urllib/request.py", line 469, in open
Looks like you use Anaconda, an alternative distribution of Python.
It should work just as well, theoretically, but maybe try running it with another Python version, just for comparison.


server not work after lost and resume connection

Stat mqtt server in android app and simulate wifi lost broken (android os stop wifi).
After restart wifi the server not publish messages and not run exception.

Starting the server on android is not officially supported. I also don't know what happens to listening sockets when wifi is stopped.
Please create a feature request if this feature is still required.


[4.2 04-30-2018] Don't try to equate/convert GenericTypeParameterTypes computing type relations of completion results

Cherry-pick of https://github.com/apple/swift/pull/16265 for swift-4.2-branch-04-30-2018

Resolves rdar://problem/38153332

@swift-ci please test


[TW#18785] VFS/FAT get free space (IDFGH-712)

Hi @all,
I wanted to find a way to get the free space of a FAT FS, implemented like the wear_leveling example.
There is no API call within your esp_vfs* headers, but in ff.c, there is following function:
FRESULT f_getfree (const TCHAR* path, DWORD* nclst, FATFS** fatfs);
Is there any way to get the FATFS pointer after mounting the partition?
The pointer is used by esp_vfs_fat_spiflash_mount, but discarded afterwards.
Do you have any suggestions how to implement this the best way?
Or should I wait for an official release :-)?
BTW keep up your work, impressive progress!

I would also be interested in getting an answer to this.  Is it a combination of getting the free clusters as benjamineaigner suggested multiplied by the size of a cluster, or is there an easier way to get free kB or something?  Thank you.

It looks like you don't need know the FATFS pointer to call f_getfree. Here's the example code from fatfs manual:
    FATFS *fs;
    DWORD fre_clust, fre_sect, tot_sect;

    /* Get volume information and free clusters of drive 0 */
    res = f_getfree("0:", &fre_clust, &fs);
    /* Get total sectors and free sectors */
    tot_sect = (fs->n_fatent - 2) * fs->csize;
    fre_sect = fre_clust * fs->csize;

    /* Print the free space (assuming 512 bytes/sector) */
    printf("%10lu KiB total drive space.\n%10lu KiB available.\n",
           tot_sect / 2, fre_sect / 2);

(The original example uses drive 1:, however if you are only using one FATFS instance, it will map to drive 0:).

@igrr
Works like a charm :-)
Thank you very much for the code example.

How Do I find sector size for SDCard.
Is it CONFIG_WL_SECTOR_SIZE=??? define in menuconfig.
I specified allocation unit=64k for SD card mount
// This initializes the slot without card detect (CD) and write protect (WP) signals.
// Modify slot_config.gpio_cd and slot_config.gpio_wp if your board has these signals.
sdmmc_slot_config_t slot_config = SDMMC_SLOT_CONFIG_DEFAULT();
 // Options for mounting the filesystem.
// If format_if_mount_failed is set to true, SD card will be partitioned and
// formatted in case when mounting fails.
esp_vfs_fat_sdmmc_mount_config_t mount_config = {
    .format_if_mount_failed = true,
    .max_files = 5,
    .allocation_unit_size = 64 * 1024
};

For 8 GB SD card, I am getting total bytes = 3.644850176 GB.

Working now. My mistakes.
cast DWORD 32-bit to 64 bit before multiple.
u64 tmp_total_bytes = (64)tot_sect * FF_SS_SDCARD;
u64 tmp_free_bytes = (64)fre_sect * FF_SS_SDCARD;


[zh] Resync pages in concepts/overview/working-with-objects

This PR resyncs pages in concepts/overview.

/lgtm
/approve


Implement the admin dashboard - navigation menu

Description
As part of this issue, we need to create the admin dashboard - navigation menu, which should closely match the provided mockup. This will provide the admins with a way to switch between different views available for them.
Tasks

Set up the basic React components as required.
Implement the layout and design of the admin dashboard - navigation menu, following the provided mockup.
Integrate the necessary components and assets to achieve the desired functionality and visual appearance.
Ensure responsiveness and compatibility across different devices and screen sizes.

Mockup: https://www.figma.com/file/nehm2ff8aR7NkPerg39fK9/ScholarX-V2-|-Wireframes?type=design&node-id=523%3A6&mode=design&t=MusZHQ3y31nKxoli-1

Acceptance Criteria

The user interface closely resembles the provided mockup.
All required sections, elements, and content are present and displayed correctly.
The interface is responsive and works well on various devices and screen sizes.
The implementation follows best practices and coding standards.
Unit tests are written.

can i work on this?


[WIP] feature/gui

[ ] -   Handle authentication flow
[ ] -   display the images the user has access to and various info/stats like annotations
[ ] -   support various admin tasks such as deleting images or giving users access to repos etc
[ ] -   display the results of security scans etc
[ ] -   display the history of tags and images
[ ] -   allowing searching of images

This looks good! I'm actually wondering if we should put the GUI in a separate repository. What do you think?

This looks good! I'm actually wondering if we should put the GUI in a separate repository. What do you think?

I did not see this earlier,  we can have it a separate repo. I don't think it will be too inconvenient.


Add forms module to package.json

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix for Issue #65

What is the current behavior? (You can also link to an open issue here)

Fails to start

What is the new behavior (if this is a feature change)?

Starts properly

Other information:

Works for me, thanks!

Many thanks @iamdavidfrancis! Merging this now.


[decompiler] Unsupported atom in ConditionElement::update_from_stack: #f

Can be seen in target-danger-set! - https://github.com/xTVaser/jak-project/tree/decomp/target-util

Looks like this is fixed, target-util is now fully decompiling.


Add web UI notification for under voltage/throttling events

Adds a banner under the header banner showing when an active or previous under voltage or other throttling events have occured on the Raspberry Pi.  The changes use the vcgencmd Python module that provides an interface for the underlying vcgencmd utility that comes with the Rasperry Pi OS distribution.
The modes that are displayed can be configured via the python/web/src/settings.py file.
Example with current styling...
Classic Theme:

Modern Theme:

Potential TODOs

Documentation on configuration (in wiki?)
Translations for mode messages
Improved CSS
Unit tests
Mock vcgencmd for Docker development environment (non-Raspberry Pi environment)

Fixes #1199

It looks like a clean and light-weight solution. Great job!
The one major missing piece is the internationalization of the strings.
You may also want to look into adding tests to the integration test suite. The main technical hurdle there would be the mocking of the undervoltage states, I think.

Great job getting the i18n job done! I think this will work, although I haven't tested it myself yet.
Two things:
Please remove the updated pot files from the changeset. Those are updated by the translators later on.
And, look into the feasibility of adding an integration test to https://github.com/PiSCSI/piscsi/tree/main/python/web/tests/api
Since you have the mock in place now, it should be doable I think!

Two things: Please remove the updated pot files from the changeset. Those are updated by the translators later on.

I committed a revert that should reset the files back to what they were.

And, look into the feasibility of adding an integration test to https://github.com/PiSCSI/piscsi/tree/main/python/web/tests/api Since you have the mock in place now, it should be doable I think!

How can I modify values from the settings.py for a unit test?  I need to set THROTTLE_TEST_MODES = [“0”, “16”] so the UI will display notifications.  Or will it just use the output of the mock script I created for the Docker environment?  How can I run the unit tests to ensure they are doing what I expect?   Not familiar with how that works yet.

As per Discord, the tests may not be overly beneficial for this change & thus it might be best to table them.  I'll let the maintainers decide if I should pursue it more or not.
Marking this PR as ready to review so others might test it out.

I check out and ran the code. It basically works well!
One thing I noticed is that I had to put the vcgencmd library into web/requirements.txt for pip to actually install the library. It didn't pick it up from common/requirements.txt. Has this worked for you so far?
Another piece of feedback is that I think a more actionable message might be needed. What do you want users to do when they see those messages? Can you give them a little more context what this state actually means?
And finally (this is kind of minor) since only two of the states are actually used right now, I don't think we should mark the rest for gettext i18n. It's kind of rude to ask translators to translate a bunch of obscure strings that will never be used, don't you think. ;)

One thing I noticed is that I had to put the vcgencmd library into web/requirements.txt for pip to actually install the library. It didn't pick it up from common/requirements.txt. Has this worked for you so far?

I did have some issues getting the module in the right place but I thought I had it.  I'll make sure it's added to web/requirements.txt.

Another piece of feedback is that I think a more actionable message might be needed. What do you want users to do when they see those messages? Can you give them a little more context what this state actually means?

I've added more descriptive messages that look like this:

And finally (this is kind of minor) since only two of the states are actually used right now, I don't think we should mark the rest for gettext i18n. It's kind of rude to ask translators to translate a bunch of obscure strings that will never be used, don't you think. ;)

I think that since we make it configurable which errors to display that they should all be configured with potential translations.  I was under the understanding that if no translation is done for an item it will default to the English version anyhow so I'm not sure what we gain from hardcoding the English versions & complicating the logic with inconsistency.  I think all the errors are potentially useful if someone wants full insight even though we only enable 2 of them by default.

Should the vcgencmd Python requirement be in BOTH web/requirements.txt AND common/requirements.txt?  I figured it should be since it's used by common/src/piscsi/sys_cmds.py

Should the vcgencmd Python requirement be in BOTH web/requirements.txt AND common/requirements.txt? I figured it should be since it's used by common/src/piscsi/sys_cmds.py

I'm not sure to be frank... I'm not entirely sure when common/requirements.txt is actually needed.

I think that since we make it configurable which errors to display that they should all be configured with potential translations. I was under the understanding that if no translation is done for an item it will default to the English version anyhow so I'm not sure what we gain from hardcoding the English versions & complicating the logic with inconsistency. I think all the errors are potentially useful if someone wants full insight even though we only enable 2 of them by default.

Fair enough, let's do it your way. :)


[ZEPPELIN-735] Remove spark.executor.memory default to 512m

What is this PR for?
The Spark interpreter currently honors whatever is set for spark.executor.memory in spark-defaults.conf upon startup, but if you look at the Interpreter page, you'll see that it has a default of 512m. If you restart a running Spark interpreter from this page, the new SparkContext will use this new default of spark.executor.memory=512m instead of what it had previously pulled from spark-defaults.conf.
Removing this 512m default from SparkInterpreter code will allow spark.executor.memory to default to whatever value may be set in spark-defaults.conf, falling back to the Spark built-in default (which, btw, has for a few Spark versions been 1g, not 512m anymore).
What type of PR is it?
Improvement
Todos
N/A
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-735
How should this be tested?

Set spark.executor.memory to some value in spark-defaults.conf (say, 5120m)
Run a Spark paragraph in Zeppelin
The Spark application will correctly use the spark.executor.memory value from spark-defaults.conf (both before and after this change).
View Interpreter page in Zeppelin UI
Before this change: spark.executor.memory will be displayed as 512m instead of what is in spark-defaults.conf
After this change: spark.executor.memory will be blank
Restart Spark Interpreter from this page and run a Spark paragraph
Before this change: the new Spark application will incorrectly use the spark.executor.memory=512m value shown on the Interpreter page
After this change: the new Spark application will correctly use the spark.executor.memory value from spark-defaults.conf

Screenshots (if appropriate)
N/A
Questions:

Does the licenses files need update? NO
Is there breaking changes for older versions? NO
Does this needs documentation? NO

Looks good to me.

Merge if there're no more discussions


Release with subscription multiple accounts.

We need a release with features implemented in a commit https://github.com/airalab/robonomics/commit/14f27d5fb75d207401a7a6f0a8210fb780d13a69.
Master branch now is not building.

Complete