Add ~/.config/jwm/jwmrc as an alternative location for the local configuration file

Most of my file configurations are kept in ~/.config, which allows better organization of the files on my home directory. It would be nice if jwm could also look for its configuration file in  ~/.config/jwm/.
The directory for the configuration would also accommodate other files that may be included in the configuration file.

I like this idea.  I think making JWM search "~/.config/jwm/jwmrc" first probably makes sense as well.

not to mention that this is part of the XDG spec.
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
I also have some scripts to handle the autostart spec that works with jwm's startup command if you would like to include it in a contrib directory... as well as a decent (but a bit dated) config generator that I can update if desired.  Now that we have dynamic menus, I can eliminate the gtkdialog/yad dependency and do most of it using the menu system.

This is implemented as of snapshot 1621.

I'll have to think about a contrib directory with more stuff (currently it's just images).  Even if it is named "contrib", the JWM repo will end up owning it, which is good in that it gives users more options, but it adds baggage to JWM releases, etc.

I'm afraid the current hard-coded path $HOME/.config/jwm/jwmrc is not what XDG is designed for. There is an important first step missing. Namely looking at the content of $XDG_CONFIG_HOME and only if it's empty use a the default value dictated by XDG, namely $HOME/.config.
@joewing could you please consider adding this tiny bit instead of hardcoding the fallback path?
By the way the contrib directory is not a bad idea - you could e.g. create a policy, that every item in contrib/ would need to be a separate repository. You would then only "link" them using git submodules. If some submodule would stop being maintained, you could simply remove the "link" from the main repository (but leave some reference in the README in a section "Abandoned/unmaintained contributions").

That patch was kinda weird.  The previous method used getenv("HOME") and constructed the path, but the new one just uses $HOME in the hard coded path... does that even work?

It’s not really my intention to support XDG, but it’s easy enough to look at XDG_CONFIG_HOME too.
@technosaurus The config parser is smart enough to look up environment variables, so the old way was just duplicated code.

this powerful line in ~/.jwmrc adds real value to jwm from a user's perspective. XDG is doing a good job here:

    <Include>exec: xdgmenumaker -n -i -f jwm</Include>


Calling jpy.get_type() too many times causes a memory access error

Running jpy 0.9, ran into this problem (running Windows):
Process finished with exit code -1073741819 (0xC0000005)

briefly googling, appears this is a memory access error code, which is easily reproducible like so
import jpy
for i in range(200):
    jpy.get_type("java.lang.String")

The number of iterations it takes to bring up the error varies by class. I'd try to fix it myself, but I'm no expert with C.

Thanks for reporting this. Hope to fix it ASAP.

I can confirm it's an issue on macOS as well, so it's platform independent. Better error message, though:
Running /Users/dave/src/sisu-llc/jpy/src/test/python/jpy_gettype_test.py
....python(93039,0x7fffb94183c0) malloc: *** error for object 0x10f74a010: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
setting environment variable 'PYTHONPATH' to None
1 Python unit test(s) failed. Installation is likely broken.

See PR. Looks like a reference counting issue. The joys of embedded Python!

Seems to be fixed now. Carefully closing it.


Document the list of all font project git repos that need to be automatically checked.

After fixing #1240, I'd like to increase the list of font projects git repos being checked by the dashboard's worker container.
It seems to me that the canonical list of font projects to check against should be whatever we currently have at prod. I know it is 800-something families, but I don't know where to find an official list of them all other than automatically querying Google Fonts itself.
Is there a similar list for the git repos for each of those? I was able to compile a list of a bit more than 104 repos by scraping the google/fonts repo for URLs referencing other repos. (the list is here: https://github.com/googlefonts/fontbakery/issues/1158#issuecomment-273958297) This would be roughtly only 13% of all projects. Does it mean 87% of the projects simply lack a git repo? Or the repos are there and I simply don't know exactly where?

They are scattered around github. Many don't have upstream repos set up yet
but I have SRC data in the old hg repo or my emails archive lol
A CSV or json or .py or whatever list of them needs to be maintained
On Mar 9, 2017 1:48 PM, "Felipe Corrêa da Silva Sanches" <
<EMAIL_ADDRESS>wrote:

After fixing #1240 https://github.com/googlefonts/fontbakery/issues/1240,
I'd like to increase the list of font projects git repos being checked by
the dashboard's worker container.
It seems to me that the canonical list of font projects to check against
should be whatever we currently have at prod. I know it is 800-something
families, but I don't know where to find an official list of them all other
than automatically querying Google Fonts itself.
Is there a similar list for the git repos for each of those? I was able to
compile a list of a bit more than 40 repos by scraping the google/fonts
repo for URLs referencing other repos. This would be roughtly only 5% of
all projects. Does it mean 95% of the projects simply lack a git repo? Or
the repos are there and I simply don't know exactly where?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/fontbakery/issues/1241, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAP9yyh9plMeSRJppH4Iy2E2OTPvMLRSks5rkElCgaJpZM4MYeoD
.

Sure! This kind of info is crucialy important. We definitely need to compile this list somewhere.

CSV should be fine
On Mar 10, 2017 5:46 PM, "Felipe Corrêa da Silva Sanches" <
<EMAIL_ADDRESS>wrote:

Sure! This kind of info is crucialy important. We definitely need to
compile this list somewhere.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/fontbakery/issues/1241#issuecomment-285806016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP9y0VxMxLQhhsY2TBM0xWbqFVK6rGdks5rkdK6gaJpZM4MYeoD
.

if by HG you mean Mercurial on Google Code, that's not readable anymore: https://code.google.com/archive/p/googlefontdirectory/source/default/source (I get a 404, actually!)
I also looked up this: https://github.com/blipvert/googlefontdirectory-hg
But I could not find the info in there as well.
@davelab6 Can you clarify where this kind of info could be found online? Or maybe it is only available in your personal data archives?

@m4rc1e has made a Google Docs spreadsheet to collaborative live-edit this data, and there is a public CSV export URL to fetch the data here:
https://docs.google.com/spreadsheets/d/1ampzD9veEdrwUMkOAJkMNkftqtv1jEygiPR0wZ6eNl8/pub?gid=0&single=true&output=csv
I suggest setting up FB to pull from that URL :)

Sure! I've been chatting with @m4rc1e aobut that earlier today and that's our plan :-)

Regarding the hg repo, yes that's what I meant; lasse has a copy on his
bitbucket.org/graphicore account iirc
On Apr 3, 2017 2:06 PM, "Felipe Corrêa da Silva Sanches" <
<EMAIL_ADDRESS>wrote:

Sure! I've been chatting with @m4rc1e https://github.com/m4rc1e aobut
that earlier today and that's our plan :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/fontbakery/issues/1241#issuecomment-291224685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP9yx9BQ8O5JkExOgfNGlXufNK2VJVaks5rsTUVgaJpZM4MYeoD
.

it's here: https://bitbucket.org/lassefister/old-googlefontdirectory

@graphicore Is there any info about URLs of upstream font project repos in there ?

I don't know.

After a quick glance, I had the impression it does not have that kind of info in there. At least not consistently throughout the family folders. And it may also be outdated info, if any.
But thanks for pointing out the existence of the repo anyway! :-)

Migrating to fontbakery-dashboard issue tracker per #1383


Upgrade Instructions.

@mesosphere-ci please retest this.

Hi @mohitsoni,
We'll also need to inform the user that all the keyspaces and tables in Cassandra must need to exist prior to a new restore.    With the current backup and restore documentation, if they go though the restore, they'll notice it wont work for restores across different Cassandra clusters. The logs will say Skipping file la-1-big-Data.db: table <INSERT_KEYSPACE_HERE>.<INSERT_TABLE_HERE> doesn't exist. They would assume this would be created for them during restore which is not the case.
Another thing to note is that I couldn't get Cassandra [1.0.5-2.2.5] and [1.0.13-2.2.5] to run simultaneously.
I have a questions from these findings:

Can we get the backup and restore to automatically create the keyspace and table? For example
CREATE KEYSPACE IF NOT EXISTS and CREATE TABLE IF NOT EXISTS should work but I am not sure how the backup and restore was implemented in this case. If the restore can create the keyspace and tables then we wont need to add it in the documentation.

If indeed that a user can't run both Cassandra [1.0.5-2.2.5] and [1.0.13-2.2.5] then we'll need to explicitly mention that the proper upgrade would be to remove the old C* cluster entirely and perform the proper restore steps on the new cluster. If you have some cycles, you can test this as well but I couldn't get both of them to work on my end even when cleaning out ZK and running janitor.py.

I got in touch with @gabrielhartmann and he mentioned that a different method needs to be performed for my question 1. At this point question 2 remains.

@bernadinm Just curious to understand why you were not able to run both Cassandra [1.0.5-2.2.5] and [1.0.13-2.2.5] on one DC/OS cluster. What was the size of your DC/OS cluster (private nodes) ?
And, what errors did you see in logs?

@mohitsoni, I wish I got the logs from my previous test. However I did test again just now with 6 private agents and I see it did work this time. The last time I had 5. Do we need a minimum of 3 per C* instance? If so, maybe I can add this requirements to the "Pre-Install Notes" of the Cassandra package.json in the universe.

@bernadinm Currently, we launch 1 Cassandra node per host/agent. The default cluster size of C* instance as configured in Universe is 3 instances, that's why you need 3 agents to run the default configuration.


Lifetime issues when trying to return a reference to an element

Since all the frame and element types have an explicit lifetime parameter, I was hoping that I could write a function that takes a reference to bytes and return a reference to an element. Something like this:
pub fn borrow_element<'a>(packet: &'a [u8]) -> Option<VendorSpecificElement<'a>> {
    let frame = packet.pread::<IEEE80211Frame>(0).unwrap();

    if let IEEE80211Frame::Management(mgmt) = frame {
        if let ManagementFrameBody::Beacon(beacon) = mgmt.body {
            if let Some(vendor_specific) = beacon.elements.get_first_element::<VendorSpecificRepr>() {
                return Some(vendor_specific);
            }
        }
    }

    None
}

Unfortunately this does not compile, because the lifetime of the element is for some reason tied to the lifetime of beacon.elements itselt, not the bytes contained within. Compiler error:
error[E0515]: cannot return value referencing local data `beacon.elements`
   --> src\read_frame.rs:174:24
    |
173 |             if let Some(vendor_specific) = beacon.elements.get_first_element::<VendorSpecificRepr>() {
    |                                            --------------- `beacon.elements` is borrowed here
174 |                 return Some(vendor_specific);
    |                        ^^^^^^^^^^^^^^^^^^^^^ returns a value referencing data owned by the current function

I believe the problem starts with this signature:
pub fn get_first_element<ElementType: ElementTypeRepr>(
    &'a self,
) -> Option<<<ElementType as ElementTypeRepr>::ElementType<'a> as Element>::ReadType<'a>>

For my snippet to work the lifetime of &self should not be tied to 'a:
pub fn get_first_element<ElementType: ElementTypeRepr>(
    &self,
) -> Option<<<ElementType as ElementTypeRepr>::ElementType<'a> as Element>::ReadType<'a>>

Taking a quick look at the code, it seems that the problem is relatively pervasive. A number of other functions also have the same issue or something similar. It would be nice if this could be fixed, to make the library more flexible.
PS: Taking a quick look at the code, it seems to me that this should be fixable simply by tweaking some lifetime parameters, with no other changes necessary.

Hi, thanks for the issue. I'm gonna reproduce it on my end, and it should be fixed soon.

I tested 0.2.2 from crates.io. Latest master did not compile.

Oh yeah, I accidentally pushed the module declaration, before the module was done. This will be fixed in a few minutes, because I'm just finishing up the VHT elements.

Just pushed VHT support and CI goes through now.

Yeah it has, I'm working on it rn.

This should've been fixed by the latest commit. The solution is (surprisingly), to just use self instead of &self, which makes absolutely no difference performance wise, since ReadElements is just a slice internally. I added a test, for this. Let me if this resolved the issue for you.

The issue with elements does seem to be fixed. ProbeRequestBody.ssid and BeaconLikeFrameBody.ssid also have a similar problem and there might be some more that I have missed. For those two it should be as simple as replacing &'a self with &self to decouple the borrow from the lifetime of the returned value.

I pushed another commit, which also resolves this for the SSID. Thanks a lot for helping catch this. This was my first real issue, apart from an incorrectly declared module and it makes me really happy to see someone use my library. I hope it's doing its job otherwise.

Haven't done any heavy testing as I only need a couple of vendor specific elements from beacon and action frames, but so far it has been working fine. I wish you luck, the 802.11 standard is huge, but having a reliable and fast dissector in Rust is valuable.

Thanks, love to hear that. I wish you good luck, with your project, as well. I'm gonna close this issue as completed.


[question/request] documentation on worldsets

I can't get them to work for the life of me, I've only managed to crash the game through tinkering. Can someone explain how to use them?

Will do. Besides, please switch the title to the camelcase?


Is Development Time + Execution Time Less Optimal on Neuromorphic Hardware?

Title
Is Development Time + Execution Time Less Optimal on Neuromorphic Hardware?
Leaders
...
Collaborators
No response
Brainhack Global 2022 Event
Brainhack Australasia
Project Description

It is often hard to access neuromorphic hardware as it is normally proprietary hardware and allocated based on competitive application. Is applying for Neuromorphic hardware time efficient?
By contrast, many researchers have access too, or can afford a GPU enabled computer that can run Julia. Making Julia+GPU a more Democratic programming paradigm.
A lot of simulated biological network development time, is time spent debugging and developing models. Debugging execution runs, should be factored into the total execution time of a mode, ie the debugging and execution loop, should be profiled too. In the past there may have been a tendency to overlook model construction delays that are caused by human errors.
From a green computing and environmental computing perspective, the total time from model conception to final model deploy is interesting.
How to get started?
Where to find key resources?
https://github.com/hangxingliu/vscode-coding-tracker

Link to project repository/sources
https://github.com/SpikingNetwork/TrainSpikingNet.jl
https://github.com/SpikingNetwork/distributedActivity
A lot of the implied work is in wrangling the Pandas data-frame (drosophila) and Sonata HDF5 connectomes into Julia compatible HDF5 and or compressed arrays saved as JLD2.
Code for getting Python connectomes is here:
https://github.com/russelljjarvis/getConnectomes
Goals for Brainhack Global
Applying SNNs dynamic simulations to pre-existing connectome data.
Reproducing pre-existing computational research but using different more Democratic tools.
Good first issues

issue one:
Wrangle drosophila, andrat V1 Connectomes from here (Sonata/HDF5) to Julia JLD2 (also HDF5). This is not easy at all, and I am still working on this.

issue two:
Make dynamic time varying simulations by applying Ben Arthur's Spiking Neural Network code, to large scale spiking neural networks.

https://github.com/SpikingNetwork/TrainSpikingNet.jl

https://github.com/SpikingNetwork/distributedActivity

Issue three Benchmark Ben Arthur's Julia code against PyGENN/CUDA, and ultimately Neuromorphic hardware applied to similar wired connectome.

issue Four use PCA and UMAP on the output raster plot spike trains in Julia and or Python in order to understand and compare the output of the simulation.

Communication channels
https://mattermost.brainhack.org/brainhack/channels/spikenetopt.jl
Skills

Julia
Python
github
PCA, UMAP, dimensionality reduction

Onboarding documentation
https://github.com/russelljjarvis/SpikeNetOpt.jl/blob/main/CONTRIBUTING.md
What will participants learn?
Julia
Data to use

Janelia FlyEM drosophila connectome.
Allen Brain V1 connectome encoded in Sonata.

https://github.com/russelljjarvis/getConnectomes
Number of collaborators

=1

Credit to collaborators
I used all-contributors last year, and I think that will keep working well :)
Also co-authorship is a possibility? The goal is to publish something.
https://github.com/russelljjarvis/SpikeNetOpt.jl/pull/17
Image
Leave this text if you don't have an image yet. Pending
Type
coding_methods, method_development, visualization
Development status
0_concept_no_content
Topic
causality, connectome, data_visualisation, physiology, reproducible_scientific_methods
Tools
other
Programming language
Julia
Modalities
other
Git skills
0_no_git_skills, 1_commit_push, 2_branches_PRs, 3_continuous_integration, 4_not_applicable
Anything else?
The other tool is really Julia code:
https://github.com/SpikingNetwork/distributedActivity
https://github.com/SpikingNetwork/TrainSpikingNet.jl
Things to do after the project is submitted and ready to review.

[X] Add a comment below the main post of your issue saying: Hi @brainhackorg/project-monitors my project is ready!
[X] Twitter-sized summary of your project pitch.

@russelljjarvis
thanks for opening the issue
we are still sorting it out who is in charge of project reviews: will get back to you once this is done

No worries @Remi-Gau, this was just a draft PR. I am still trying to figure out the exact details so I am happy for non immediate feedback.

Testing things: stand back. 😄

OK this looks good to go for me.

@russelljjarvis
Your project is on the website: https://brainhack.org/global2022/projects/

Hi @RyanGreenup,
Let me know if you want to be added as a collaborator above.


[opentitantool] Add tests for usr_access module

Is this a unit test or is this needed for ROM e2e testing?

unit. this might be closed because we will revisit the way we handle this workflow.

CC @timothytrippel @cfrantz


Add support for talkback users

So after much deliberation over how to add support for talkback users, I have landed on this solution.
I have taken another open-source PDF rendering library and integrated it into this library as it has the ability to strip text from a PDF for use in the contentDescription with each page. This definitely isn't a perfect solution but a step in the right direction in my opinion.
Video example:
https://user-images.githubusercontent.com/16602828/228078236-1a1aecbd-5a17-41a7-bf56-51bbb13b7eab.mp4
I did a comparison of the sample apps minified size before and after this change and while it does add some weight it is quite minor thankfully.

Before
After

3.8MB
8.4MB

In terms of how talkback may handle potentially very large amounts of text in the contentDescription I came across this page for how to use talkback.
It appears there is good support for handling these situations which is fantastic. That being said I think this PR should be a first step to more nuanced accessibility support within each page.

@JBayangosB I think it would be nice to have a flag in the state to be able to activate and deactivate text extraction because if it is not the user's intention to use it, it is an unnecessary load in the page rendering phase.

@JBayangosB I think it would be nice to have a flag in the state to be able to activate and deactivate text extraction because if it is not the user's intention to use it, it is an unnecessary load in the page rendering phase.

I have just pushed another commit adding a new flag to the state. I added it to the end of the existing state arguments to ensure that it doesnt affect any existing implementations of the library and it is also disabled by default.


The use of the .where instead of piping in the export-excel module does not work with powershell 3

The use of the .where instead of piping in the export-excel module does not work with powershell 3

Sorry. Thurs has only been tested on the latest version of Powershell. There my be other places the module is not backward compatible.


[FLINK-19699][e2e] Improve error reporting for failing Prometheus test.

What is the purpose of the change
The prometheus e2e test might get killed by the oom killer. This adds more infrastructure for generally logging received signals in the test, and collecting the kernel messages at the end of the e2e tests.

The class is in flink-runtime. We could move it to flink-core, but so far the junit testing utils have no Flink dependencies. I didn't want to mess with the dependencies.

Thanks for your review. Will merge once CI has passed (tomorrow 😂 )


Refactor avatar overlapping and masking

Fixes #25
Fixes #26
Implementation is based on https://github.com/vaadin/vaadin-avatar/issues/26#issuecomment-652430572
Note: this requires user to set width & height by changing --vaadin-avatar-size custom CSS property, which might be a bit inconvenient in terms of DX (setting width and height directly is not be picked up by mask-position calculation).
I had to update "scaled" visual tests accordingly, which illustrates the implications of this approach.

Tests for avatar-group.html are failing in IE11 with a SyntaxError and I have no idea what could cause it 😓

@yuriy-fix noted, thanks. The current approach also breaks IE11, so I'm going to refactor it.

Reverted the changes related to --vaadin-avatar-size CSS custom property because of IE11 issues.
Users overriding width and height for avatar group will now need to also set mask-position.


ForgeAPI seems to not pull latest modpack version

Describe the problem
Currently running this docker on unRAID and have MODS_FORGEAPI_RELEASES="Beta" and the project id set to the one for Better Minecraft (482878), the container seems to be pulling v4 instead of v4.5 (latest). I'm wondering if this is just an issue with the forge API not updating or something with the image. Also as a feature request it might be nice in the future if there was someway to poll the API once a day (or a variable interval)  to check if the local version is behind the remote, and to update it if so.

Can you re-pull your Minecraft image? I believe I pushed a fix for this 5 days ago. https://github.com/itzg/docker-minecraft-server/pull/1451 Let me know if that does work, I can revisit it.

This really has to do with how forgeApi filters the mods, they only filter on major version, I had mistakenly assumed higher IDs meant higher minecraft versions, but if a mod maker keeps deploying for older sub minecraft versions they would be picked up instead. The last fix I pushed now sorts by highest ID, and filters on the full minecraft version.

Can you re-pull your Minecraft image? I believe I pushed a fix for this 5 days ago. #1451 Let me know if that does work, I can revisit it.

Image seems to be the latest version, here is a link to the modpack. It does appear that the v4.5 ID is > the v4 ID

3728722 <- v4.5, 3728331 < v4 and they both support 1.18.2, So this really is a forge bug as they do not include a version field for the mod itself.

Can you verify you have pulled the latest image? Because latest is working for me.
[init] Resolved version given LATEST into 1.18.2 and major version 1.18
[init] Resolving type given CUSTOM
Downloading https://edge.forgecdn.net/files/3732/702/voicechat-fabric-1.18.2-2.2.32.jar
Downloading https://edge.forgecdn.net/files/3728/616/architectury-4.1.39.jar
Downloading https://edge.forgecdn.net/files/3689/20/fabric-api-0.48.0+1.18.2.jar
Downloading https://edge.forgecdn.net/files/3728/711/Better Minecraft [FORGE] v4.5.zip

@Hayden-J-C if you could run docker container inspect -f '{{json .Config.Labels}}' CONTAINER_ID_OR_NAME, that'll let us confirm you have the latest image with the fix.

@Hayden-J-C if you could run docker container inspect -f '{{json .Config.Labels}}' CONTAINER_ID_OR_NAME, that'll let us confirm you have the latest image with the fix.

{
"org.opencontainers.image.authors" : "Geoff Bourne<EMAIL_ADDRESS>"org.opencontainers.image.created" : "2022-04-02T20:38:34.183Z",
"org.opencontainers.image.description" : "Docker image that provides a Minecraft Server that will automatically download selected version at `startup",
"org.opencontainers.image.licenses" : "Apache 2.0",
"org.opencontainers.image.revision" : "e0b4a819b1a533609197ef88035ca8f84eab9528",
"org.opencontainers.image.source" : "https://github.com/itzg/docker-minecraft-server",
"org.opencontainers.image.title" : "docker-minecraft-server",
"org.opencontainers.image.url" : "https://github.com/itzg/docker-minecraft-server",
"org.opencontainers.image.version" : "java17"
}

Yep, that's the latest image revision.

@Hayden-J-C so I can better test this, do you have your command or compose file you are using? Because my tests are coming back with the mods.
Thanks!

@Hayden-J-C, if you could add DEBUG=true and provide that out then @shotah can compare with his testing.


API keys & Endpoints for certain automation

[ ] Allow the use of long-standing API keys
[ ] Create API endpoints for the automation of certain tasks, such as creating/deleting users

Can now create service accounts and use Authorization: Bearer xxx


Provide proxy functionality

Added proxy functionality for users that want to use the API and cannot access the Internet directly

Hi @sebix - yes, sure. I had to rewrite code and missed that.

Thank you for the update! merged!!


Support Ruby 2.2 on Windows

Currently (<IP_ADDRESS>) we only cross-compile for 1.9.3, 2.0.0 and 2.1.3.

+1, have the same problem.
I have a load error with the following nokogiri versions installed:
gem list nokogiri
nokogiri (<IP_ADDRESS> x64-mingw32, 1.6.5 x64-mingw32)

Tried to load it irb:
C:\Users\XXXXXX\Documents\projects\ruby_drafts\lib>irb
irb(main):001:0> require 'nokogiri'
LoadError: cannot load such file -- nokogiri/nokogiri
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in `rescue
 in <top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:25:in `<top (
required)>'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        from (irb):1
        from C:/Ruby22-x64/bin/irb:11:in `<main>'
irb(main):002:0>

OS: Windows 7 Pro
Ruby: ruby 2.2.1p85 (2015-02-26 revision 49769) [x64-mingw32]
Any idea ? Thank you

Hello,
Thanks for asking this question. To be clear, we do not yet support window 2.2, as mentioned on the mailing list and in this issue. "+1"s are not necessary. :)

ok, thank you.

I think it works on my system (Win7 x64, Ruby 2.2.1)

that is so annoying. any timelines/plans to fix that? maybe there are some way/hack to alleviate the problem?

I think Nokogori team should release new version including #1266,
if MinGW Ruby 2.2 supporting takes long time.

You could try http://stackoverflow.com/questions/28985328/rubyinstaller-2-2-1-and-rails-rake-cannot-load-nokogiri/29196632#29196632

0
down vote
@Rich Peck: I tried your suggestion to compile nokogiri, but I got error iconv.h not found in mkmf.log, did exact setup as your example command. Any thoughts?

In order for me to get it to work, I had to download the following packages from XMLSoft

iconv-1.9.2.win32.zip
libxml2-2.7.8.win32.zip
libxslt-1.1.26.win32.zip

I extracted the packages and copied the binaries into my Ruby bin directory (So I didn't have to edit my PATH)
After that, I ran the following to install the nokogiri gem successfully
gem install nokogiri -- --use-system-libraries --with-iconv-config=C:/Ruby22/bin --with-xml2-config=C:/Ruby22/bin --with-xslt-config=C:/Ruby22/bin

Lastly, I had to edit the file "\Ruby22\lib\ruby\gems\2.2.0\specifications\nokogiri-<IP_ADDRESS>-x86-mingw32.gemspec" and change:
  s.require_paths = ["lib/"]

to
  s.require_paths = ["lib/nokogiri"]

I am new to Rails and this isn't going quite as "easy" as the tutorials, but I guess I have been through worse...  Concurrency is bad thing sometimes, good instruments being developed within one environment become non-maintainable when ported to another one... Thank you for all your work, guys,
I'm also waiting for updates by this problem. Thanks.

@billmurrin Thanks for the detailed instructions.
I still cannot get nokogiri to run on Windows.
When you say

... copied the binaries into my Ruby bin directory ...

do you mean the dll and exe files?
Could you get a simple Ruby file with the following require statement to work?
require 'nokogiri'

I wonder what's preventing Nokogiri to be built for Ruby 2.2 on Windows? What's status, what are blockers?

It is indeed strange.
I downgraded to Ruby 2.1 and it worked.
I could live with this downgrade, since all I needed was a scraping task
with Mechanize & Nokogiri.
Amnon
On Tue, May 12, 2015 at 7:10 PM, Dāvis<EMAIL_ADDRESS>wrote:

I wonder what's preventing Nokogiri to be built for Ruby 2.2 on Windows?
What's status, what are blockers?
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1256#issuecomment-101332895
.

Rails 5 requires Ruby 2.2.2, so we cannot run Rails 5 on Windows without this issue fixing.
https://github.com/rails/rails/pull/19753

+1

+1
Any updates on Ruby v2.2 support for Windows?

Same here. Is there anything we can do to help?

Considering a cross-build issue has been addressed on the Ruby side and there's a PR for the build environment that works, I think all we need to do is release a new version.  /cc @flavorjones

I have the same error and just wanting to pick up Ruby on Rails.
Would it be better for me to remove everything and get 2.0.0 instead?

@adrianwtx90 for now, ruby 2.1 or ruby 2.0 would solve your problem. Other people have reported that nokogiri worked well on windows with ruby 2.1.
If you have the choice of 32 bit vs. 64 bit, i'd recommend 32 bit on windows. There are some gems with problems with 64 bit builds (net-ssh, for example; nokogiri in earlier versions), so you'd likely just run into the next problem.

This issue should remain open ?

I guess so, there isn't a solution for Ruby 2.2 yet.

So there is no way for windows developers for Ruby 2.2 ? I am using Windows 8

Not that I'm aware of...

I think the only solution for developers to be up to date with Ruby development is if you use Vagrant =)

We are having same issue, is this gonna be fixed soon?

The previous version Ruby 2.1 is working well. But does not support some features
Depending on your version of ruby, you may need to install ruby rdoc/ri data:
<= 1.8.6 : unsupported
= 1.8.7 : gem install rdoc-data; rdoc-data --install
= 1.9.1 : gem install rdoc-data; rdoc-data --install

= 1.9.2 : nothing to do! Yay!

@knu has already mentioned that there are possible fixes in place. Thoughts?

The only blocker is finding the time to build the release, which is a bit time-consuming. I hope to do this in the next day or so.

I can't wait until you release the next build for windows ruby 2.2 - My rails console is crying without it.

For you rails Windows devs keep in mind that sqlite also doesn't yet support Ruby 2.2 but does support 2.1: https://groups.google.com/forum/#!topic/sqlite3-ruby/cNqvONJmocU. So be prepared to get another DB running as well.

jmthomas
c:>ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x64-mingw32]
c:>irb
irb(main):001:0> require 'sqlite3'
=> true

Any update on potential windows 2.2 build?

@richww You could try this: https://github.com/sparklemotion/nokogiri/pull/1302

+1, I really need this.

when are you gonna release 1.6.7? I really need this fix.

+1, need this as well

You can build your own nokogiri gems for Rubyinstaller x86/x64 on Windows-x64 by using https://github.com/sparklemotion/nokogiri/pull/1302 as long as 1.6.7 isn't released. Install boot2docker for Windows and do this:
  git clone https://github.com/larskanis/nokogiri
  cd nokogiri
  git checkout make-use-of-rake-compiler-dock
  bundle
  rake gem:windows

It then takes a while to download and build everything, but in the end there should be some gems in the pkg directory for install.
Please leave a comment, if it works for you!

+1

+1

@larskanis It can't find docker even it was installed and running :(
WARNING: cross compilation not available: No MinGW tools or unknown setup platform?
rake-compiler-dock bash -c "bundle && rake cross native gem MAKE='nice make -jnproc' RUBY_CC_VERSION=1.9.3:2.0.0:2.1.6:2.2.2"
Get http://<IP_ADDRESS>:2375/v1.19/version: dial tcp <IP_ADDRESS>:2375: ConnectEx tcp: No connection could be made because the target machine actively refuse
d it.. Are you trying to connect to a TLS-enabled daemon without TLS?
rake aborted!
RakeCompilerDock::DockerIsNotAvailable: Docker is not available
C:/virvit/2/nokogiri/Rakefile:358:in `block in <top (required)>'
Tasks: TOP => gem:windows
(See full trace by running task with --trace)
Docker is not available. Please download and install boot2docker:
https://github.com/boot2docker/windows-installer/releases
Then execute 'boot2docker start' and follow the instuctions

@virvit you must call "boot2docker start"and set the environment variables,
that it prints, before calling "rake gem:windows".

Hi larskanis,
I have an error similar to virvit's and my variables are set correctly when I do "boot2docker".
My error :
WARNING: cross compilation not available: No MinGW tools or unknown setup platform?
rake-compiler-dock bash -c "bundle && rake cross native gem MAKE='nice make -j'nproc' RUBY_CC_VERSION=1.9.3:2.0.0:2.1.6:2.2.2"
An error occurred trying to connect : Get https://<IP_ADDRESS>:2376/v1.19/version: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not 192.168.103
rake aborted !
RakeCompilerDock::DockerIsNotAvailable: Docker is not available
C:/wwww/2/nokogiri/Rakefile:358:in `block in ' <top >'
Tasks: TOP => gem:windows
(See full trace by running task with --trace)
Docker is not available. Please download and install boot2docker:
https://github.com/boot2docker/windows-installer/releases
Then execute 'boot2docker start' and follow the instuctions
As far as I understand, the IP is not correct. But I do not know where I can change it. However the instructions of boot2docker ask me to set DOCKER_HOST=tcp://<IP_ADDRESS>:2376
If I change <IP_ADDRESS>:2376 by <IP_ADDRESS>:2376, I obtain exactly the same message as virvit.
Do you have any idea of what is happening ?

I've found that you need to put <IP_ADDRESS> boot2docker into hosts file + set ENV variables. Then it works.

It do not undertand which hosts file you are refering to.

:+1:

windows/system32/drivers/etc/hosts

The commands of larskanis finally worked. I needed to change the require path for nokogiri specification to lib/nokogiri.
However, I am still stuck with rails, getting loofah cannot load such file -- nokogiri.
Thanks to all ^^

I got it compiling with the instructions I posted to 1302.  Problem has to do with either permissions or symlinks during the autoload of the ::win:: directory into ::dev-vm::.  Craps out with a Gemfile/.bundler not present because (they aren't, or the user loaded by rake-compiler-docker can't get'em).  solution is to shell into ::dev-vm:: using rails-compiler-docker (no args), reload the source, bundle, change the permissions (chmod 777), re-bundle (so it can write the gemlock), then exit and rerun rake gem:windows from the ::win:: machine.

Also, if you have a space in your windows user account name, you may have to change it - using User Accounts (display name) doesn't change the user account name (i.e. cmd.exe: echo %username%).  Just open up computer management, find the user (in the tree display!), and right-click on rename.  MS doesn't have a rename on the user's properties tab.  Verify name changed using cmd (echo...).  Some of my earlier problems seemed to come from the escaping of the space in the User (like the rake-compiler-docker was trying to execute a command using the ::vm:: user autocreated by it form ::win:: username and crapping out because only half the username was being properly passed).  If you are going to have to do this on a regular basis, suggest stripping out the space from the username account.  Won't change anything else on your machine, and it will probably save you alot of aggravation (in case it's not being escaped properly).

might be something buggy with my virtualbox install; have the guest extensions installed & machine settings shared folders shows read-write access, but no change made in ::vm:: is replicated out to ::win:: or vice versa.  Not sure why.  build worked, but now I'm trying to find a way to get it the .so's off.

deleted my comments as it is quite likely it is a virtual box issue. ;) VERY irritating way to discover a known problem.  Got the so's, getting the aforementioned loofah problem; manually copying over the gem into rubydir/gems just yields nokogiri no constant errors.

If one of you guys manage to make a build, do you think you could help @flavorjones prepare a release through a pull request (if that even works)? You would have my eternal gratitude ^^,

The only blocker is finding the time to build the release, which is a bit time-consuming. I hope to do this in the next day or so.

14 days ago... Usual thing in open-source but it's sad anyway.

give this a shot.  let me know if it works, else I'll take down the repo.
https://github.com/paulgrant999/nokogir-2.2.2-win64-mingw-gem/blob/master/README.md

Here's a Vagrantfile for building the gem.
Usage:
mkdir build-nokogiri; cd build-nokogiri
wget https://gist.githubusercontent.com/nonsequitur/60cd7db1cbd61a74b62d/raw/d942a98dea7f22f3e34f94a3b2006b1b3792d0bd/Vagrantfile.rb
vagrant up
gem install --local nokogiri-<IP_ADDRESS>-x86-mingw32.gem # Pick your preferred version
vagrant destroy -f

@paulgrant999 , I've downloaded your gem to give it a try, and it seemed to work all right. Thanks. But now the problem is with bcrypt gem.
Facing the same error like described here:
https://github.com/codahale/bcrypt-ruby/issues/102#issuecomment-102936804

@paulgrant999 Thank you very much! With your files I can finally run a Rails 5 application on Windows. (with PostgreSQL)
@fera2k Until this is fixed, you can compile the .so file yourself: Just switch into the ext/mri directory of the gem path, call ruby extconf.rb and then make (You need DevKit of course) Then you can copy the newly compiled bcrypt_ext.so into lib\2.2.

@daniel-rikowski I've done as you said, and now its working beautifully! Thank you so much!

So, gem can be updated with Windows support on Ruby 2.2? :)

what @toncid said :)

What is status of this issue?
#1310 passes tests on AppVeyor.

Thanks @paulgrant999. Your version is working for me. Here is what I did for Win7x64 (should work with x32 the same way):

Download @paulgrant999 's version:  nokogiri-<IP_ADDRESS>-x64-mingw32.gem
gem uninstall nokogiri
gem install --local C:\Users\$user$\Downloads\nokogiri-<IP_ADDRESS>-x64-mingw32.gem

Worked for me as well (Windows 7 Pro). Nevertheless, (sure it is an sqlite issue this time), after creating a simple rails project, sqlite3 fails:
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:6:in `require': cannot load such file -- sqlite3/
sqlite3_native (LoadError)
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:6:in `rescue in <top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:2:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:76:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:76:in `block (2 levels) in require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:72:in `each'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:72:in `block in require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:61:in `each'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:61:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler.rb:134:in `require'
        from C:/Users/c59scam/Documents/soft/draft_rails/config/application.rb:16:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in `block in server'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `tap'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `server'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands.rb:17:in `<top (required)>'
        from bin/rails:4:in `require'
        from bin/rails:4:in `<main>'

despite the gem sqlite3 is installed:
C:\Users\c59scam\Documents\soft\draft_rails>rails s
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:6:in `require': cannot load such file -- sqlite3/
sqlite3_native (LoadError)
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:6:in `rescue in <top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x64-mingw32/lib/sqlite3.rb:2:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:76:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:76:in `block (2 levels) in require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:72:in `each'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:72:in `block in require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:61:in `each'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler/runtime.rb:61:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.5/lib/bundler.rb:134:in `require'
        from C:/Users/c59scam/Documents/soft/draft_rails/config/application.rb:16:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in `block in server'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `tap'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `server'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands.rb:17:in `<top (required)>'
        from bin/rails:4:in `require'
        from bin/rails:4:in `<main>'

@Javix You could install these gems: https://github.com/sparklemotion/sqlite3-ruby/pull/159

@fsauter, thanks for making installation crystal clear, and thanks @paulgrant999 for putting this together.

spoke too soon. the gem downloads fine, but I try to start the server and I get the "cannot load such file" error.

@larskanis: worked like a charm after downloading the specified sqlite3 gem version :+1:

All right, great!
So, what is the of the gem so that gem install nokogiri works on Windows with Ruby 2.2.x?
If not like that, can you please summarize how to install it on Windows?
Thanks

@toncid , I`ve summarized the steps in the last answer here:
http://stackoverflow.com/questions/28985328/rubyinstaller-2-2-1-and-rails-rake-cannot-load-nokogiri

@larskanis thank you so much it works! now rails is up and running...thanks...

@fsauter, thanks for making installation crystal clear, and thanks @paulgrant999 for putting this together.
Ditto.  I hope the gem maintainer gets time to fix the official gem.

@Javix, what did you change in your Gemfile to make it use the new version of sqlite3, mine was default to sqlite3 3.1.10, after I install it from https://github.com/larskanis/sqlite3-ruby/releases/tag/1.3.11-pr159, I got 2 different versions of sqlite3, but my server is still using the old 3.1.10

I used
gem 'sqlite3', '1.3.11.pr159'
and it worked :)

@jjgh, it errored out for me
ERROR:  While executing gem ... (Gem::CommandLineError)
Unknown command sqlite3,

@jjgh , I figured it out, what you said is actually a change in the gemfile of project. Sorry, I am quite new to Ruby.

@paulgrant999 @fsauter , thanks for your tips guys! worked for me

@jianchen: I've just updated the used sqlite3 gem version to the newest one in the Gmefile of the Rails application:
#before
gem 'sqlite3'

#after
gem 'sqlite3', '1.3.11.pr159'

and run bundle install.
Then just run as usual rails s to check if the app starts without problems.

@jianchen glad you did it. I wish you a good stay in the Ruby ecosystem. I hope the Windows support will get less bumpy with time :) Anyway for when you just starting with learning the basics of the language and simple Rails projects it should be just ok. I hope you enjoy it!

Hey please help me.I tried the solution of @paulgrant999 but now my console say me :ERROR:  While executing gem ... (Gem::Package::FormatError)
package metadata is missing in ruby-2.2.2-nokogiri-<IP_ADDRESS>-x86-x64-mingw32.g
em
What can i do?

Try to follow the steps described by @fsauter before

Can you explain me this step?

Just reperat them one by one:

Download @paulgrant999 's version: nokogiri-<IP_ADDRESS>-x64-mingw32.gem
gem uninstall nokogiri
gem install --local C:\Users$user$\Downloads\nokogiri-<IP_ADDRESS>-x64-mingw32.gem
If you have problems using sqlite3 ("cannot load such file...") do the following:

To fix sqlite3 issue:

Download @larskanis 's version: sqlite3-1.3.11.pr159-x64-mingw32.gem
gem uninstall sqlite3
gem install --local C:\Users$user$\Downloads\sqlite3-1.3.11.pr159-x64-mingw32.gem
To be sure that this version is used replace gem 'sqlite3' with gem 'sqlite3', '1.3.11.pr159' in your Gemfile and run bundle install

Sure, you should adapt the specidied gem path to your PC (place where you saved the downloaded gems).

Already done,but it gave me the same error

Let the folks correct me if I'm wrong, but It seems like either your downloaded gem was corrupted or you are behind a proxy.

No i'm not using a proxy.I'll try to re-dwnload the nokogiri gem.

Ok now the installation is succesfully done.
But it give me Another error
C:/Ruby22/lib/ruby/2.2.0/rubygems/dependency.rb:315:in to_specs': Could not fin d 'nokogiri' (>= 1.5.9) - did find: [nokogiri-<IP_ADDRESS>-x64-mingw32] (Gem::LoadErr or) Checked in 'GEM_PATH=C:/Users/Giovanni Giordano/.gem/ruby/2.2.0;C:/Ruby22/lib/ru by/gems/2.2.0', execute gem env` for more information
Tell me what i've to do please

Display your gem list:

gem list nokogiri

You should get something like ths:
C:\Users\XXXXX>gem list nokogiri

*** LOCAL GEMS ***

nokogiri (<IP_ADDRESS> x64-mingw32)

run irb in your Windows console (terminal) and require nokogiri as follows:

C:\Users\XXXXX>irb
irb(main):001:0> require 'nokogiri'
=> true
irb(main):002:0>

If not, post your results here.

1 step it's ok,2 step log me this
LoadError: cannot load such file -- nokogiri/nokogiri
from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
require'         from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib
/nokogiri.rb:29:in rescue in <top (required)>'         from C:/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib /nokogiri.rb:25:in <top (required)>'
from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in
require'         from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in  rescue in require'
from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in
require'         from (irb):1         from C:/Ruby22/bin/irb:11:in '

Do you have Development Kit installed ?

yes i have

Do you have Ruby 64 bit or 32bit?

x32 Ruby 2.2.2

i believe the gem is a 64 bit one. In this case (compiled native stuff) this matters. If the download page has "x64" and "x86", you'd need to choose the x86 ones. x86 stands for the "old fashioned x86, 32bit architecture".

I re download Again thiAggem Waits for me please xD

Gem sorry

When I started the thread, I pointed the 64-bits version.

I tried x64 and x32 version of Nokogiri but nothing,it say me:
ERROR:  While executing gem ... (Gem::Package::FormatError)
package metadata is missing in nokogiri-<IP_ADDRESS>-x86-mingw32.gem
it say the same thing if i try to install directly with gem install nokogiri...

i'm waiting for help...

What I' have done is:

remove (uninstall) all the existing nokogiri gem versions: gem uninstall nokogiri -a
reinstall the nokogiri gem with respecting to your OS version (32 or 64 bits)
post your installation stack traces with ruby -v displayed.

Now the error is changed (i reinstalle nokogiri with the online method,not with the gem file because my command give me error trying do this thing)
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x86-mingw32/lib/sqlite3.rb:6:i
n `require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
my ruby -v=ruby 2.2.2p95 (2015-04-13 revision 50295) [i386-mingw32]

ok i tried to change sqlite3/sqlite3_native in sqlite3 in the gem file (ruby\gems\2.2.0\gems\sqlite3-1.3.10-x86-mingw32\lib),and now my console return me this:
C:/Ruby22/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x86-mingw32/lib/sqlite3/databa
se.rb:296:in <class:Database>': undefined method busy_timeout=' for class `SQL
ite3::Database' (NameError)

@Gionnix: if you continue to do your way instead of the one described earlier which was confirmed to work for everybody, I don't think anybody could help you. Try not to read in diagonal but line by line, and follow it step by step. If the folks advised to use the specified gem version, there is a reason for that. The same for all the other steps.

Although i very much sympathise with everyone having gem problems, i'd also prefer if we could discuss an sqlite problem in their bugtracker, not in a ticket that actually tries to solve a nokogiri problem on windows.

I follow what you tell to me but it doesn't work
i removed (uninstall) all the existing nokogiri gem versions
i reinstalled the nokogiri gem respecting my OS version
i displayed my ruby version (is this ->ruby 2.2.2p95 (2015-04-13 revision 50295) [i386-mingw32])
but nothing work.The thing that i tell to you is after that i did your step.
What i must display to you? tell me please @Javix

I'm really sorry if i disturb you @javix i'm a newbie,is the first time for me

@Gionnix it does not disturb me, it just pollutes the thread and nokogiri issue tracker as @ccoenen told.

@Gionnix copy/paste in order the result of the below commands executed in your terminal:
ruby -v
gem list nokogiri

Let's test your DevKIt installation, run the below command and copy-paste the result in your future response:
gem install json --platform=ruby

JSON should install correctly and you should see with native extensions in the screen messages. Next run
ruby -rubygems -e "require 'json'; puts JSON.load('[42]').inspect"

to confirm that the json gem is working.
Initially, the issue was with 64-bits version of nokogiri gem. @ccoenen , @paulgrant999 is it correct ? I'll be able to test it tomorrow on a 32-bits box.

@Javix I have ruby 2.1.6 and ruby 2.2.2 installed on my machine. Both are the 32bit builds from rubyinstaller.
On 2.1.6 and 2.2.2 i can run gem install nokogiri, so far it's the same.
When i enter require 'nokogiri' in the irb, it will work in ruby 2.1.6. It will, however, not work in ruby 2.2.2. The error message is identical to the one in the second post in this thread.
In short: 2.2.2-32bit is broken, too.

I've just tried it on a 32-bits PC:
C:\Users\Serge>gem install nokogiri -N
Fetching: mini_portile-0.6.2.gem (100%)
Successfully installed mini_portile-0.6.2
Fetching: nokogiri-<IP_ADDRESS>-x86-mingw32.gem (100%)
Nokogiri is built with the packaged libraries: libxml2-2.9.2, libxslt-1.1.28, zlib-1.2.8, libiconv-1.14.
Successfully installed nokogiri-<IP_ADDRESS>-x86-mingw32
2 gems installed

C:\Users\Serge>irb
irb(main):001:0> require 'nokogiri'
LoadError: cannot load such file -- nokogiri/nokogiri
        from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:29:in `rescue in
<top (required)>'
        from C:/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:25:in `<top (requ
ired)>'
        from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
        from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        from C:/Ruby22/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        from (irb):1
        from C:/Ruby22/bin/irb:11:in `<main>'

I tried to install the 32-bit version from https://github.com/paulgrant999/ruby-2.2.2-nokogiri-<IP_ADDRESS>-x86-x64-mingw32.gem, it failed:
:\Install>gem install --local nokogiri-<IP_ADDRESS>-x86-mingw32.gem
RROR:  While executing gem ... (Gem::Package::FormatError)
   package metadata is missing in D:/Install/nokogiri-<IP_ADDRESS>-x86-mingw32.gem

It seems like 32x version for Ruby ruby 2.2.2p95 (2015-04-13 revision 50295) [i386-mingw32] is broken as well :(

@flavorjones
https://github.com/sparklemotion/nokogiri/issues/1256#issuecomment-111169685

The only blocker is finding the time to build the release, which is a bit time-consuming. I hope to do this in the next day or so.

When will you do?
Many comments are very annoying.
Why do not other contributors (who have write access to repository) take this issue?

ruby -v = ruby 2.2.2p95 (2015-04-13 revision 50295) [i386-mingw32]
gem list nokogiri =*** LOCAL GEMS ***  nokogiri (<IP_ADDRESS> x64-mingw32 x86-mingw32)
gem install json --platform=ruby
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
Successfully installed json-1.8.3
Parsing documentation for json-1.8.3
Done installing documentation for json after 4 seconds
1 gem installed
ruby -rubygems -e "require 'json'; puts JSON.load('[42]').inspect"
[42]

@Gionnix as you couild see from earlier comments by @ccoenen :

When i enter require 'nokogiri' in the irb, it will work in ruby 2.1.6. It will, however, not work in ruby 2.2.2. The error message is identical to the one in the second post in this thread.
In short: 2.2.2-32bit is broken, too.

the only solution (for the moment) to use Ruby 2.1.6 and wait for fixing the issue.

Ok thanks i'll try

thanks of all

Are there any plans to fix this issue?

It is said that 2.1.3 is supported, but there is no rubyinstaller for 2.1.3.  Will it work with 2.1.6?

As @ccoenen said:

When i enter require 'nokogiri' in the irb, it will work in ruby 2.1.6. It will, however, not work in ruby 2.2.2. The error message is identical to the one in the second post in this thread.

it works with 2.1.6 x32, 2.2.2 x64 without problems.

Javix, can you please clarify what you said to my post this morning?  It looks like you are saying that it works on 2.2.2 x64 without problems, but it is definitely not working on 2.2.2p95 x64 for me.

I just followed the steps described earlier in this thread by @fsauter and here is the output for a Windowxs 7 PC x64:
C:\Users\XXXXX>ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x64-mingw32]

C:\Users\c59scam>gem list nokogiri

*** LOCAL GEMS ***

nokogiri (<IP_ADDRESS> x64-mingw32)

C:\Users\XXXXX>irb
irb(main):001:0> require 'nokogiri'
=> true
irb(main):002:0>

I just installed ruby 2.2.2-x64 on my windows 7 machine. In my case it does the same as in 32 bit
possible difference: my ruby 2.2.2-x64 is not on the system path.
C:\Users\...> C:\Tools\Ruby22-x64\bin\ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x64-mingw32]

C:\Users\...> C:\Tools\Ruby22-x64\bin\gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 2.4.5
  - RUBY VERSION: 2.2.2 (2015-04-13 patchlevel 95) [x64-mingw32]
  - INSTALLATION DIRECTORY: C:/Tools/Ruby22-x64/lib/ruby/gems/2.2.0
  - RUBY EXECUTABLE: C:/Tools/Ruby22-x64/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Tools/Ruby22-x64/bin
  - SPEC CACHE DIRECTORY: C:/Users/...../.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: C:/ProgramData
  - RUBYGEMS PLATFORMS:
    - ruby
    - x64-mingw32
  - GEM PATHS:
     - C:/Tools/Ruby22-x64/lib/ruby/gems/2.2.0
     - C:/Users/..../.gem/ruby/2.2.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - C:\Tools\cmder\bin
     - C:\Tools\cmder\vendor\msysgit\bin
     - C:\Tools\cmder\vendor\msysgit\mingw\bin
     - C:\Tools\cmder\vendor\msysgit\cmd
     - C:\Tools\cmder\vendor\msysgit\share\vim\vim74
     - C:\Tools\cmder
     - C:\Tools\cmder\vendor\conemu-maximus5\ConEmu
     - C:\Tools\cmder\vendor\conemu-maximus5
     - C:\Program Files\ImageMagick-6.9.0-Q16
     - C:\Tools\Perl64\site\bin
     - C:\Tools\Perl64\bin
     - C:\Program Files (x86)\AMD APP\bin\x86_64
     - C:\Program Files (x86)\AMD APP\bin\x86
     - C:\Windows\system32
     - C:\Windows
     - C:\Windows\System32\Wbem
     - C:\Windows\System32\WindowsPowerShell\v1.0\
...(and a few more)...

C:\Users\...> C:\Tools\Ruby22-x64\bin\gem install nokogiri
Fetching: mini_portile-0.6.2.gem (100%)
Successfully installed mini_portile-0.6.2
Fetching: nokogiri-<IP_ADDRESS>-x64-mingw32.gem (100%)
Nokogiri is built with the packaged libraries: libxml2-2.9.2, libxslt-1.1.28, zlib-1.2.8, libiconv-1.14.
Successfully installed nokogiri-<IP_ADDRESS>-x64-mingw32
Parsing documentation for mini_portile-0.6.2
Installing ri documentation for mini_portile-0.6.2
Parsing documentation for nokogiri-<IP_ADDRESS>-x64-mingw32
Installing ri documentation for nokogiri-<IP_ADDRESS>-x64-mingw32
Done installing documentation for mini_portile, nokogiri after 5 seconds
2 gems installed

C:\Users\....> C:\Tools\Ruby22-x64\bin\irb
irb(main):001:0> require 'nokogiri'
LoadError: cannot load such file -- nokogiri/nokogiri
        from C:/Tools/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Tools/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Tools/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in `rescue in <top (required)>'
        from C:/Tools/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:25:in `<top (required)>'
        from C:/Tools/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
        from C:/Tools/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        from C:/Tools/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        from (irb):1
        from C:/Tools/Ruby22-x64/bin/irb:11:in `<main>'
irb(main):002:0>

You should download and install @fsauter 'version nokogiri gem for 64-bits version and install it locally, NOT FROM rubygems repo.

Sorry, my bad! I edited my post above to remove the useless "finding".
You are right, the modified version does indeed work on ruby 2.2.2x64! I just confirmed that, too.

Any chances of seeing this change pushed to the RubyGems repo?

Hi all, I just emailed nokogiri-talk about a Windows release. If you don't subscribe, you should, but here's the link in any case:

https://groups.google.com/d/msg/nokogiri-talk/aJkGZz5bhRo/3yu3BNFPDgAJ

TL;DR we're going to get this out the door this week, honest. Thanks for your patience.

@paulgrant999 Thank you very much! I am just starting out with rails. I have rails 4.2.3, ruby 2.2.3, on windows 10 with mysql.

:+1: Thanks @flavorjones! And praise to @larskanis for working on this too! :)

So looking forward to this update. Thanks guys!

no prob bob :)  happy to be of service.

Hello everyone. Nokogiri v1.6.7.rc2 has been pushed, with Ruby 2.2.x support on Windows, as well as support for native builds on Windows.
Please try it and comment here on what works and what doesn't work. If I don't hear of any blockers by Friday, 4 September 2015, I'll release this as v1.6.7 final.

Still not working. Nokogiri is possible without the need for any action on Ruby 2.2.x?

@dbwls94 did you try 1.6.7? you need to install them with gem install nokogiri --pre, right now. I'm still testing various combinations, but so far everythinr worked.

@ccoenen Do I have to install nokogiri in a folder that is installed Ruby?

there's various ways to go about this, but the easiest for a quick test will be to install nokogiri with your system-wide available gems. The command you're looking for is gem install nokogiri --pre which will installed the precompiled nokogiri for your system. The files will end up somewhere in your ruby directory, but the exact location is not important - ruby will find them for you when you require 'nokogiri' in your code.

i can install (and subsequently require) nokogiri on Ruby 2.2.2 in 32 and 64 bit, without the need for --platform=ruby. I'm so glad! Thanks!
Combinations that i tried:
[x] Ruby 2.2.2 / 32bit
[x] Ruby 2.2.2 / 64bit
[ ] Ruby 2.1.6 / 32bit
[ ] Ruby 2.1.6 / 64bit
Will be updated as i go along. I'll let you know if anything comes up.

@ccoenen Thank you. I use Ruby 2.2.2 and 64 bit. I try 'gem install nokogiri --pre', but it cannot worked.

I will need an error message to help you find the problem. For now, all i can say is "it should work on a ruby 2.2.2 64 bit". Could you post the output from your terminal in here? And please also include the output from gem env

hey, I installed the new nokogiri version with Ruby 2.2.2 (x64) on Windows:
C:\Users\Ryner\ruby\MessengerApp>gem install nokogiri --pre
Nokogiri is built with the packaged libraries: libxml2-2.9.2, libxslt-1.1.28, zlib-1.2.8, libiconv-1.14.
Successfully installed nokogiri-1.6.7.rc2-x64-mingw32
Parsing documentation for nokogiri-1.6.7.rc2-x64-mingw32
Done installing documentation for nokogiri after 1 seconds
1 gem installed
But I still get the same error message, what Do I need to change?
C:\Users\Ryner\ruby\MessengerApp>rails server
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in require': cannot load such file -- nokogiri/nokogiri (LoadError)         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in rescue in <top (required)>'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:25:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-sanitizer.rb:2:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-sanitizer.rb:2:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/sanitize_helper.rb:3:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/sanitize_helper.rb:3:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/text_helper.rb:32:in module:TextHelper'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/text_helper.rb:29:in <module:Helpers>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/text_helper.rb:6:in module:ActionView'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/text_helper.rb:4:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_tag_helper.rb:18:in module:FormTagHelper'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_tag_helper.rb:14:in <module:Helpers>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_tag_helper.rb:8:in module:ActionView'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_tag_helper.rb:6:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_helper.rb:4:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers/form_helper.rb:4:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers.rb:50:in module:Helpers'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers.rb:4:in <module:ActionView>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/actionview-4.2.3/lib/action_view/helpers.rb:3:in <top (required)>'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/legacy_asset_tag_helper.rb:7:in <module:LegacyAssetTagHelper>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/legacy_asset_tag_helper.rb:6:in module:Rails'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/legacy_asset_tag_helper.rb:4:in <module:Sprockets>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/legacy_asset_tag_helper.rb:3:in <top (required)>'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/helper.rb:45:in require'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/helper.rb:45:in module:Helper'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/helper.rb:7:in <module:Rails>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/helper.rb:6:in module:Sprockets'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/rails/helper.rb:5:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/railtie.rb:6:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.2/lib/sprockets/railtie.rb:6:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass/rails/railtie.rb:3:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass/rails/railtie.rb:3:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass/rails.rb:11:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass/rails.rb:11:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass-rails.rb:1:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.3/lib/sass-rails.rb:1:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in block (2 levels) in require'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in each'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in block in require'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in each'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in require'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler.rb:134:in require'
from C:/Users/Ryner/ruby/MessengerApp/config/application.rb:7:in <top (required)>'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in require'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:78:in block in server'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in tap'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in server'         from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:39:in run_command!'
from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/railties-4.2.3/lib/rails/commands.rb:17:in <top (required)>'         from bin/rails:4:in require'
from bin/rails:4:in `'
C:\Users\Ryner\ruby\MessengerApp>

@ccoenen Thank you for your help verifying that this release works for you!
 Please uninstall <IP_ADDRESS> and make sure you're using 1.6.7.rc2.

I uninstalled version <IP_ADDRESS> @flavorjones, how do I set the "rails server" to use the new version for nokogiri ?

@KyleRyner Your question is kinda out of scope for this ticket; but I'll try to help. Check if you have a Gemfile, and if so, lock it to this version of Nokogiri by using this line:
gem "nokogiri", "=1.6.7.rc2"

If that doesn't work, you'll likely need to get help from somewhere else. Thanks!

Thanks @flavorjones , I'll give it a go.

the patch that @paulgrant999 issued worked for  rails 4.2.3, ruby 2.2.3, on windows 10x64 with mysql.
I uninstalled the patch, but when i run gem install --pre i am still getting version <IP_ADDRESS>. I have completely reinstalled all of ruby and rails. uninstalled the ver <IP_ADDRESS> and ran the install --pre twice with same results

@lightscare Rails depends on nokogiri v<IP_ADDRESS> but once is the final release of 1.6.7 is out, it should work out vast majority of the problems? (Disclaimer: I use 2.1.6 as of right now but I previously used 2.2.1 to manage Rails but this issue happened.)

Thanks @rodrigoargumedo I will reinstall the patch until the final release then try again.

Cannot make Nokogiri work with Ruby2.2.2 on windows how do I downgrade to Ruby 2.1.6

Fixed the issue, rolled back Ruby to 2.1.6 and installed nokogiri
with ruby install nokogiri --pre worked :)

@hadagali on 2.1.6, any recent nokogiri should work. I'm curious what your problem with 2.2.2 was - do you have any logs you could share?

@ccoenen Sorry I have lost the logs, I was in rush to generate the QuickFix/N templates, next time I try with 2.2.2 will update the post with errors, thx

I just shipped one more release candidate -- 1.6.7.rc3, which updates its dependency on mini_portile to 0.7.0.rc4 (because there were backwards-incompatibilities in mini_portile).
I don't expect anything to change, but if someone could give it a try and confirm there are no blockers, then I'm likely to cut 1.6.7 final this weekend.

The 1.6.7.rc3`` version worked for my PC box -Windows 7 Pro, x64):
*** LOCAL GEMS ***

nokogiri (<IP_ADDRESS> x64-mingw32)

C:\Users\frup44058>irb
irb(main):001:0> require 'nokogiri'
LoadError: cannot load such file -- nokogiri/nokogiri
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in `rescue in <top (required)>
'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:25:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        from (irb):1
        from C:/Ruby22-x64/bin/irb:11:in `<main>'
irb(main):002:0> exit

C:\Users\frup44058>gem install nokogiri -v 1.6.7.rc3 --pre -N
Fetching: mini_portile-0.7.0.rc4.gem (100%)
Successfully installed mini_portile-0.7.0.rc4
Fetching: nokogiri-1.6.7.rc3-x64-mingw32.gem (100%)
Nokogiri is built with the packaged libraries: libxml2-2.9.2, libxslt-1.1.28, zlib-1.2.8, libiconv-1.14.
Successfully installed nokogiri-1.6.7.rc3-x64-mingw32
2 gems installed

C:\Users\frup44058>irb
irb(main):001:0> require 'nokogiri'
=> true

Thanks a lot !!!!

I'll still need to figure out which gem uses the old version like that:
C:\Users\xxxx\Documents\projects\rails_app>gem dependency nokogiri --reverse-dependencies
Gem nokogiri-<IP_ADDRESS>-x64-mingw32
  hoe (~> 3.13, development)
  hoe-bundler (>= 1.1, development)
  hoe-debugging (~> 1.2.0, development)
  hoe-gemspec (>= 1.0, development)
  hoe-git (>= 1.4, development)
  mini_portile (~> 0.6.0)
  minitest (~> 2.2.2, development)
  racc (>= 1.4.6, development)
  rake (>= 0.9, development)
  rake-compiler (~> 0.9.2, development)
  rdoc (~> 4.0, development)
  rexical (>= 1.0.5, development)
  Used by
    capybara-2.5.0 (nokogiri (>= 1.3.3))
    cucumber-rails-1.4.2 (nokogiri (~> 1.5))
    loofah-2.0.3 (nokogiri (>= 1.5.9))
    rails-dom-testing-1.0.7 (nokogiri (~> 1.6.0))
    rspec-core-3.3.2 (nokogiri (~> 1.5, development))
    sprockets-3.3.4 (nokogiri (~> 1.3, development))
    xpath-2.0.0 (nokogiri (~> 1.3))

Gem nokogiri-1.6.7.rc3-x64-mingw32
  hoe (~> 3.13, development)
  hoe-bundler (>= 1.1, development)
  hoe-debugging (~> 1.2.0, development)
  hoe-gemspec (>= 1.0, development)
  hoe-git (>= 1.4, development)
  mini_portile (~> 0.7.0.rc4)
  minitest (~> 2.2.2, development)
  racc (>= 1.4.6, development)
  rake (>= 0.9, development)
  rake-compiler (~> 0.9.2, development)
  rake-compiler-dock (~> 0.4.2, development)
  rdoc (~> 4.0, development)
  rexical (>= 1.0.5, development)
  Used by
    capybara-2.5.0 (nokogiri (>= 1.3.3))
    cucumber-rails-1.4.2 (nokogiri (~> 1.5))
    loofah-2.0.3 (nokogiri (>= 1.5.9))
    rails-dom-testing-1.0.7 (nokogiri (~> 1.6.0))
    rspec-core-3.3.2 (nokogiri (~> 1.5, development))
    sprockets-3.3.4 (nokogiri (~> 1.3, development))

Because when trying to create and run a simple rails app got the below error:
C:\Users\xxxx\Documents\projects\rails_app>rails s
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in `require': cannot load such file -- noko
giri/nokogiri (LoadError)
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:29:in `rescue in <top (required)>
'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x64-mingw32/lib/nokogiri.rb:25:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in `<top (required)>'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-sanitizer.rb:2:in `require'
        from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-sanitizer.rb:2:in `<top (required)>'

@Javix I believe you need to specify the exact version when using "pre-release" gems. Try adding gem 'nokogiri', '1.6.7.rc3' to the Gemfile for your Rails project, and then bundle install.

@zetetic

FYI: The generated Rails app's Gemfile does not contain nokogiri gem declaration.
As you could see from my previous comment describing internal gems dependencies, every gem has its own ones. And you can't force any of them to use the version you need (if you don't modify the gem source code locally, of course). So declaring a nokogiri in the Gemfile is not a solution.

@Javix normally of course, the Gemfile should not include a dependency for Nokogiri. But 1.6.7.rc3 is a "pre-release" version. AFAIK adding it to the Gemfile is the only way to get Bundler to install it. Or you could wait until the "official" version is released. Understand that the version being loaded is determined by Gemfile.lock. If it specifies <IP_ADDRESS>, that's what you get, until you update the Gemfile or run bundle update.

Fixed it as follows:

add gem 'nokogiri', '1.6.7.rc3'to your rails app Gemfile
download sqlite pre version 1.3.11.pr159 and install it locally (see described earlier steps)
modifiy the declared sqlite gem as follows gem 'sqlite3', '1.3.11.pr159' in your Gemfile
delete Gemfile.lock
cd to your rails app and run bundle install
hit rails sand navigate to localhost:3000 in your browser.
enjoy :)

Just a note here about the delay in shipping a nokogiri 1.6.7 final -- @larskanis and I have been working on what do to about newly-discovered incompatibilities between the latest prerelease of mini_portile and previous versions.
The TL;DR is that we're going to cut at least one more nokogiri release candidate, to bump the dependency on mini_portile. This should happen today.

Hi All, 1.6.7.rc3 works
gem uninstall nokogiri
gem install nokogiri --pre
edit your gemlock file to match as nokogiri (1.6.7.rc3-x86-mingw32)
rails s

why i am not able to start rails server after updating nokogiri?
C:\row\dev\myblog>gem list nokogiri
*** LOCAL GEMS ***
nokogiri (1.6.7.rc3 x86-mingw32, <IP_ADDRESS> x86-mingw32)
C:\row\dev\myblog>
C:\row\dev\myblog>rails s
C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:29:in require':  cannot load such file -- nokogiri/nokogiri (LoadError)         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:29: in rescue in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:25:
in <top (required)>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in require'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/loofah-2.0.3/lib/loofah.rb:3:in `<top (required)

'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-saniti
zer.rb:2:in require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/rails-html-sanitizer-1.0.2/lib/rails-html-saniti zer.rb:2:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/sanitiz
e_helper.rb:3:in require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/sanitiz e_helper.rb:3:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/text_he
lper.rb:32:in <module:TextHelper>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/text_he lper.rb:29:in module:Helpers'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/text_he
lper.rb:6:in <module:ActionView>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/text_he lper.rb:4:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_ta
g_helper.rb:18:in <module:FormTagHelper>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_ta g_helper.rb:14:in module:Helpers'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_ta
g_helper.rb:8:in <module:ActionView>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_ta g_helper.rb:6:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_he
lper.rb:4:in require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers/form_he lper.rb:4:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers.rb:50:i
n <module:Helpers>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers.rb:4:in  module:ActionView'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/actionview-4.2.4/lib/action_view/helpers.rb:3:in
<top (required)>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/legacy _asset_tag_helper.rb:7:in module:LegacyAssetTagHelper'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/legacy
_asset_tag_helper.rb:6:in <module:Rails>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/legacy _asset_tag_helper.rb:4:in module:Sprockets'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/legacy
_asset_tag_helper.rb:3:in <top (required)>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper .rb:45:in require'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper
.rb:45:in <module:Helper>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper .rb:7:in module:Rails'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper
.rb:6:in <module:Sprockets>'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper .rb:5:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/railtie.rb:6
:in require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sprockets-rails-2.3.3/lib/sprockets/railtie.rb:6 :in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass/rails/railtie.rb:3:in
require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass/rails/railtie.rb:3:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass/rails.rb:11:in requir e'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass/rails.rb:11:in <top (
required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass-rails.rb:1:in require '         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sass-rails-5.0.4/lib/sass-rails.rb:1:in <top (r
equired)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in req uire'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in blo
ck (2 levels) in require'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in eac h'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in blo
ck in require'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in eac h'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in req
uire'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler.rb:134:in require'         from C:/row/dev/myblog/config/application.rb:7:in <top (required)>'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks
.rb:78:in require'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks .rb:78:in block in server'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks
.rb:75:in tap'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks .rb:75:in server'
from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks
.rb:39:in run_command!'         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/railties-4.2.4/lib/rails/commands.rb:17:in <top
(required)>'
from bin/rails:4:in require'         from bin/rails:4:in '

C:\row\dev\myblog>

@tomwebbi : see my previous comment explaining how to fix that.

@Javix i followed your steps but not able to start the server

@tomwebbi the error stacktace points it clearly that your Rails app uses <IP_ADDRESS> version:
C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri.rb:29

Try to add the latest (RC) nokogir version as follows:

add gem 'nokogiri', '1.6.7.rc3'to your rails app Gemfile
download sqlite pre version 1.3.11.pr159 and install it locally (see described earlier steps)
modifiy the declared sqlite gem as follows gem 'sqlite3', '1.3.11.pr159' in your Gemfile
delete Gemfile.lock
cd to your rails app and run bundle install

when i run bundle install it automatically downloads nokogiri 1.6.6 version again

Nope, if you add `` gem 'nokogiri', '1.6.7.rc3'to your Gemfile, remove Gemfile.lock firil and run bundle install` it will install the indicated version  - 1.6.7rc3.

Do a Bundle Update after you do a Bundle install
or try
gem uninstall nokogiri
gem install nokogiri --pre
edit your gemlock file to match as nokogiri (1.6.7.rc3-x86-mingw32)
rails s

i tried but though it installs 1.6.6 again evry time i install bundle

Edit your gemfile with the following and then do a bundle install. It seems you still have the 1.6.6 installed.
gem "nokogiri", "=1.6.7.rc3"
If it still fails, make sure the uninstall is sucessful
gem uninstall nokogiri

i updated bundle also but it downloads the 1.6.6 nokogiri and editing gemfile also prompts for removing and installing bundle again

yeah uninstall gets successful

edit your gemfile and add this
gem 'nokogiri', '1.6.7.rc3', :platforms => [:mswin, :mingw]

yeah i edited the gemfile with this strings

@DSAMPAT which rails and ruby version you using

i am uninstalling the installer of ruby and reseting the whole env..

@tomwebbi  I am using ruby "2.2.3" and rails "4.2.3" with nokogiri "1.6.7.rc3"
Maybe your issue is not related to this thread. Look on stackoverflow for your errors
http://stackoverflow.com/search?q=nokogiri

my rails version is above yours one so could it be the issue?

their is a new error i am getting after roll back to previous version of ruby, error is as follows:
Specified 'mysql2' for database adapter, but the gem is not loaded. Add gem 'mysql2' to your Gemfile (and ensure its version is at the minimum required by ActiveRecord).
Any help on solving this error message?

It is a mysql2 gem issue and nothing to do with nokogiri. Replace it in your Gemfile with the default one (gem 'sqlite3', '1.3.11.pr159').

i have specified using mysql while creating new rails app and i will be using the same database in future what are the issues related to mysql db creating using rake and running rails server with mysql ??? i am able to run simple ruby applications with databse code like show database and all the why rails is not supporting the mysql2 gem?

I suppose that the discussed issue concern nokogir gem only. Please, would you try to run a simple Rails app with its default values. If you have some related issues, post it here. Otherwise open another one on a corresponding github repo to not hack this one.

i am a beginner into rails, nokogiri was not supported for ruby2.2.3, so i moved back to ruby 2.0.0 and now nokogiri issue is stopped, but i am not able to create a database using mysql any help on this would be thankful

In this case, try to download Ruby 2.2.2 version from http://rubyinstaller.org/downloads/archives.
Choose the version depending on you Windows version (32 oe 64 bits).
Uninstall the previousely installed RUby version(s)
Remove DevKit folder
Install the corresponding DevKit version
create a simple Rails app without indicating Db to use (to use sqlite3 as default one).
follow the step described earlier to install the working nokogiri and sqlite3 versions in the created earlier Rails app.
if it works, find the steps to follow to install mysql2 gem or try these ones:

Download the ARCHIVE of connector C used by mysql2 gem (either 32bit or 64bit version depending on your OS)
from MySQL site.
Unzip it wherever you you want
Run gem install mysql2 --platform=ruby -- '--with-mysql-dir="C:\mysql-connector"'
Copy the libmysql.dll from the LIB directory of the mysql connector to the bin folder of Ruby installation.

replace sqlite3 gem in the created Rails app with mysql2
run bundle
run rails sto see if it works as needed.

Hope this helps.

@Javix how to install sqlite3?, cause i have tried before and i got sqlite3 error while starting rails server

Either download the indicated version from rubygems.org then install locally or just add it to your Gemfile by specifying the exact version and run bundle.
Sent from my iPhone

On 03 Oct 2015, at 09:32, tomwebbi<EMAIL_ADDRESS>wrote:
@Javix how to install sqlite3?, cause i have tried before and i got sqlite3 error while starting rails server
—
Reply to this email directly or view it on GitHub.

what i am asking about is standalone sqlite3, is their ? i have installed gem but though its showing error i suppose its trying to find sqlite3 on my pc which is not installed

@Javix  this is what i am getting......
C:\row\dev\myblog>gem list sqlite3
*** LOCAL GEMS ***
sqlite3 (1.3.10 x86-mingw32)
C:\row\dev\myblog>rails s
C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x86-mingw32/lib/sqlite3.rb:6:in require': cannot load such file  -- sqlite3/sqlite3_native (LoadError)         from C:/row/Ruby22/lib/ruby/gems/2.2.0/gems/sqlite3-1.3.10-x86-mingw32/lib/sqlite3.rb:6:in rescue in <top (re
quired)>'

OK, guys, discussing sqlite installation here is really off-topic. Please move it to a private conversation.

yeah toncid i can understand its not a topic of nokogir, can i get a private conversation from you for solving my issue?

I think Stack Overflow would be more appropriate. ;)

Or if it's a bug, sqlite3 has a bugtracker of their own:
https://github.com/sparklemotion/sqlite3-ruby/issues

At first glance, this might be the same problem: https://github.com/sparklemotion/sqlite3-ruby/issues/150 I think continuing there is the most helpful thing for everyone.

not able to configure rails environment sqlite3 giving still error any help will be great

thanks @ccoenen

On June 11, @flavorjones wrote:

The only blocker is finding the time to build the release, which is a bit time-consuming. I hope to do this in the next day or so.

Any update as to status, situation, ETA?

@Javix on ruby 2.2.2 nokogiri is giving error

@tomwebbi

post errors stack trace
post nokogiri version you installed

That's got nothing to do with nokogiri. Your problem is related to sqlite3, ask on StackOverflow or an sqlite3 repo about nokogiri. Nobody here can help you. You are making this unrelated ticket about an actual (?) nokogiri problem difficult to use for what it needs to be used for.

@jrochkind

@tomwebbi, do not post again and again.
It is obvious what is wrong.

i have fixed it now everything is working fine ;)

Thank you @Javix !!! It worked just with "add gem 'nokogiri', '1.6.7.rc3' to your rails app Gemfile"

On windows8.1,
ruby 2.2.2p95 (2015-04-13 revision 50295) [x64-mingw32]
rails 4.2.4
I confirm nokogiri 1.6.7 rc3 don't break rails loading.
Great news! Thanks for your work!

@Jonathan-92 It's for @fsauter, I just followed the steps he posted :)

hello guys,
this is my first time learning rubyonrails and am having this nokogiri <IP_ADDRESS> issue.
google searching leads me here.
I tried Javix's way, but unfortunately I still have issue.
my setup:
windows 8.1

from a post above:
add gem 'nokogiri', '1.6.7.rc3'to your rails app Gemfile
download sqlite pre version 1.3.11.pr159 and install it locally (see described earlier steps)
modifiy the declared sqlite gem as follows gem 'sqlite3', '1.3.11.pr159' in your Gemfile
delete Gemfile.lock
cd to your rails app and run bundle install
run rails s and navigate to localhost:3000
after I run bundle install, I got this

could someone help me, please?

I believe, the sqlite error should no longer be a problem could you try
gem 'sqlite3', '1.3.11'  instead? (no pr...)
also: this is a sqlite issue, not a nokogiri issue. If the suggestion does not fix it, please open a ticket with in the sqlite3-bugtracker here: https://github.com/sparklemotion/sqlite3-ruby/issues

@ccoenen
woww.thanks man.it works
thanks for the fast response as well.
my gemfile

thanks. I can open localhost:3000 now.

Cheers :) :+1:

What progress?
Posts of Redmine cannot run on Windows Ruby 2.2 are very annoying.
http://www.redmine.org/boards/2/topics/48548

Are you sure that it is nokogiri issue?
ср, 28 окт. 2015, 13:44, Toshi MARUYAMA<EMAIL_ADDRESS>
What progress?
Posts of Redmine cannot run on Windows Ruby 2.2 are very annoying.
http://www.redmine.org/boards/2/topics/48548
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1256#issuecomment-151797415
.

@marutosi Thanks for your patience. I understand you'd like to get this fixed. Have you tried the release candidates? Do they work for you?

Are you sure that it is nokogiri issue?

http://www.redmine.org/issues/19419#note-5
https://github.com/bundler/bundler/issues/3484

I understand you'd like to get this fixed.

I am Redmine contributor.

Have you tried the release candidates?

I don't have Windows environment I can use now.

Are you sure that it is nokogiri issue?

http://www.redmine.org/issues/19419#note-5
bundler/bundler#3484

https://github.com/sparklemotion/nokogiri/issues/1266

Rails5 uses "gem 'nokogiri', '>= 1.6.7.rc3'" for Windows.
https://github.com/rails/rails/commit/bbfd17689bfe3b94550edecd99584b66de4dfa93
https://github.com/rails/rails/pull/21602

I have requested to Rails4 uses "gem 'nokogiri', '>= 1.6.7.rc3'" for Windows.
https://github.com/rails/rails/pull/21602#issuecomment-152072820

@marutosi Rails is only using the releases candidates in its own test suite. The applications are still using the last released version that it is 1.6.6.

Have you tried the release candidates? Do they work for you?

Appveyor tests passes on Windows Ruby 2.2.
https://ci.appveyor.com/project/marutosi/redmine/build/1.0.4

This is proof revision.
https://github.com/marutosi/redmine/commit/76d887d9a8adce96514e065fcae2a0dbc154eb8a

Great, thank you.
On Oct 29, 2015 4:51 AM, "Toshi MARUYAMA"<EMAIL_ADDRESS>wrote:

This is proof revision.
marutosi/redmine@76d887d
https://github.com/marutosi/redmine/commit/76d887d9a8adce96514e065fcae2a0dbc154eb8a
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1256#issuecomment-152114833
.

Is there any blocker for 1.6.7 ?

@martinsefcik Yes, we still have some items to take care of before shipping a final. Are you offering assistance?

What kind of items ?
But I'm not sure I can help. I'm still relatively new to Ruby.

1.6.7.rc4 just shipped, which I'd like someone to try and confirm that it works for them. Unless something comes up, this will ship as 1.6.7 final in the next few days.

All good. No issues. Unless you want us to test something specific.
nokogiri (1.6.7.rc4-x86-mingw32)
  mini_portile2 (~> 2.0.0.rc2)

I've tested here on Windows 10 and CentOS Linux, both using Ruby 2.2.3.
No failures so far! Good job!

OK, let's ship this thing. No compelling blockers having been raised, I'm going to cut 1.6.7 today.
Thanks, everybody, for your patience and help.
Will update this ticket when I ship it.

v1.6.7 has been shipped.

All good. No issues.
nokogiri (1.6.7-x86-mingw32)
  mini_portile2 (~> 2.0.0.rc2)

:four_leaf_clover: :-D Thanks!

Thanks! :+1:


Provide a helpful hint to browse the repo at a particular tag

It can be confusing to browse the Halogen repo on the master branch and find that the code there doesn't work at all in your project, only to realize later that you should have been browsing at a particular tag instead! Since there is also a next branch users might expect master to be the 'stable release' branch.
Even though I know better, I've done this myself recently, and I've witnessed confusion for users of purescript-halogen-formless for the same reason in that repo. I've added this notice to Formless, and I thought it would be useful for Halogen users as well.

I think this is a good idea, I tried to mitigate it a bit by updating the readme links to point to the latest release version, but this directs people away from direct source tree browsing too. Perhaps we should use some HTML to format it rather than relying on > though? As it looks de-emphasised, but should perhaps be more eye catching.

Sure! Do you have any ideas on how you'd like that to look? Perhaps it could be as simple as prefacing it with a bold Note: and not putting it in a quote:
Note: This repo uses tagged releases...

Sure, let's go with that. If people keep running into problems we can always try something else!
Also sorry about the super slow reply even for this 😬

👍 Good to go!

Thanks!