Failed to parse http response when receiving unexpected interface type response

On version 1.0.0, when I have the following types:
type Query {
  blocks(): [Block!]!
}
interface Block {
  index: Int!
  featured: Boolean!
}
type BlockParagraph implements Block {
  index: Int!
  featured: Boolean!
  content: String!
}

and my app has these 2 queries, both queries doing the same thing, only different that BlockV2 is using Fragment.
query BlockV1 {
  blocks {
    index
    featured
    ... on BlockParagraph {
      content
    }
  }
}

query BlockV2 {
  blocks {
    ... BlockFragment
  }
}
fragment BlockFragment on Block {
  index
  featured
  ... on BlockParagraph {
    content
  }
}

Later, I add another implementation of Block below
type BlockParagraph2 implements Block {
  index: Int!
  featured: Boolean!
  content: String!
  content2: String!
}

Without updating app with the new schema, BlockParagraph2 is considered an unexpected type of interface Block.
Anyway, BlockV1 is still able to handle BlockParagraph2 and parse it to just a normal Block. Great!!!
But BlockV2 is unable to handle BlockParagraph2 and gives an error message Failed to parse http response
I have a look in generated code. The query BlockV2 has these lines of code which prevent it from fallback the unexpected BlockParagraph2 type to Block
@Override
public @NotNull Fragments map(ResponseReader reader, @NotNull String conditionalType) {
  BlockFragment blockFragment = null;
  if (BlockFragment.POSSIBLE_TYPES.contains(conditionalType)) {
    blockFragment = blockFragmentFieldMapper.map(reader);
  }
  return new Fragments(Utils.checkNotNull(blockFragment, "blockFragment == null"));
}

Questions

What is the expected behaviour when client received an unexpected type like this? Should it failed like BlockV2 or handle the unexpected type as its based interface like BlockV1?
If the expected behaviour is BlockV1. Can we remove these POSSIBLE_TYPES checking from generated code? I think by removing this checking, BlockV2 will be working the same way as BlockV1.

Yeah, seems like an issue for this particular case. We wanted to be too smart for the nullability in case of fragments and this is the context https://github.com/apollographql/apollo-android/issues/382
Not really sure how to properly handle this case.

I would prefer this case to be handled like BlockV1 so I can write my code to handle unexpected type gracefully like this.
when (blockFragment) {
  is BlockFragment.AsBlockParagraph -> // Handle Paragraph
  is BlockFragment.AsBlahBlahBlah -> // Handle BlahBlahBlah
  else -> // Handle unknown block type gracefully
}

The parser should only failed when there is a critical incompatibility such as when it found null value for non-nullable field. In this case "Failed to parse http response" will be suitable. Does this make sense?

After looking into it more carefully, it seems that what we need to do is check if the fragment is defined on the same type as the parent field (in the example above with BlockV2  query the fragment fragment BlockFragment on Block is defined on the base interface Block) we shouldn't even generate this check BlockFragment.POSSIBLE_TYPES.contains(conditionalType) as it will always correctly resolve fragment that defined on the interface. I'm going to work on this fix.


Add Message.get_all_attributes/2 function

Codecov Report
Patch coverage has no change and project coverage change: -2.83 :warning:

Comparison is base (2feefe6) 82.22% compared to head (e02e1a0) 79.39%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
- Coverage   82.22%   79.39%   -2.83%
==========================================
  Files          15       15
  Lines         225      233       +8
==========================================
  Hits          185      185
- Misses         40       48       +8

Impacted Files
Coverage Δ

lib/ex_stun/message.ex
90.72% <0.00%> (-8.16%)
:arrow_down:

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


add javascript.code-snippets file

Addresses https://github.com/microsoft/azuredatastudio/issues/24785 where an error was showing in the console looking for this file so that now the file is found. This copies over the javascript.code-snippets from the 1.82 vs code branch, which is vscode version brought in by the latest merge: https://github.com/microsoft/vscode/blob/release/1.82/extensions/javascript/snippets/javascript.code-snippets

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 41.573%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
30786

Relevant Lines:
69356

💛  - Coveralls

bringing in one more file - brought up in https://github.com/microsoft/azuredatastudio/issues/24785#issuecomment-1789478534


Upgrade requirements

Codecov Report

Merging #33 (048529c) into main (b5a2c8c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           28        28
  Branches         8         8
=========================================
  Hits            28        28

Continue to review full report at Codecov.

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


chore: release 1.1.1

:robot: I have created a release *beep* *boop*
1.1.1 (2021-07-21)
Bug Fixes

provide all request headers (#370) (5b4c94b)

This PR was generated with Release Please. See documentation.

Release notes:
This is small patch release that fixes missing headers in requests/responses returned using the hooks system.

:robot: Release is at https://github.com/ethersphere/bee-js/releases/tag/v1.1.1 :sunflower:


Auth failing when password contains non-alphanumeric characters

Hi, I wanted to say that if the password has "@" symbol on it, it won't work. It took me 30 minutes to realise that. The perl command turned me Auth error until I changed my password and generated a new API key on last.fm web.
Sorry if my english is too bad, I'm from Spain.
Thank you @ethanndickson & @xytxytxyt !
☺

Ah yep, this is my bad. I actually knew about this when I made it but forgot to keep note of that, i'll look into fixing it tomorrow. Thanks!

Fixed in latest commit!


Add merge arguments to set metadata values on the merged BOM

I'd like to be able to do things like set the authors and supplier in the BOM's metadata when merging.

This is likely to be implemented as a specific command in #108 with this use case in mind.
Likely to end up with usage something like this...
cyclonedx merge --input-files bom1.xml bom2.xml | cyclonedx metadata --set author.name="Some Person" --set supplier.name="Some Company" --output-file bom.xml
That way in can be implemented once and made use of for multiple use cases.

Sounds great.

@coderpatros Any updates on this? I've run into this issue when merging the DT bom generated from Maven and the pre-build bom containing all the services DT relies on. I'm wanting to merge the boms but I'm loosing metadata information.

Hi @coderpatros
Do you plan on implementing this any time soon? We could really do with it in our CD - at the moment we have an extra step to insert the metadata, after the merge, but if cyclonedx-cli could do it, it would be much better.

@coderpatros I think this one can be closed as #240 has been merged?


How does pizzly work ?

Very interesting software. But how does this tool work?
I guess you do assemble all possible fusion transcripts sequence according to  GTF reference and do the quantification for these transcripts to see whether they are expressed?

Pizzly is based on detecting reads that span fusion junctions to call potential fusions. Once the fusion sequences are called kallisto can be used to quantify the expression of potential fusions. An example of this workflow is in the Snakefile in the test directory.
The preprint describing the details is coming soon.


Increment version for template releases

Increment version for template releases

Ignore this commit, just doing some testing.


Jl.mex example not working

Running the Jl.mex example causes an error.
The two first examples in the Readme work:
>> disp(Jl.eval('2+2'))
          4

>> disp(Jl.call('factorial', 10))
          3628800

The file for the third example is in the Matlab path
>> type('double_it.jl')

function double_it(outs::Vector{Ptr{Void}}, ins::Vector{Ptr{Void}})
  try
    mex_return(outs, [ 2*v for v in mex_args(ins) ]...)
  catch e
    mex_showerror(e)
  end
end

and is included
Jl.include('double_it.jl')

Make an input array:
>> a = rand(5,5)

a =

    0.2760    0.4984    0.7513    0.9593    0.8407
    0.6797    0.9597    0.2551    0.5472    0.2543
    0.6551    0.3404    0.5060    0.1386    0.8143
    0.1626    0.5853    0.6991    0.1493    0.2435
    0.1190    0.2238    0.8909    0.2575    0.9293

And call double_it.jl with a:
>> Jl.mex('double_it', a)
Error using cell
Size inputs must be scalar.

Error in Jl.mex (line 8)
        varargout = cell(nout, 1);

Looking at the following lines in Jl.m it appears that the first argument of mex should be the number of output arguments (if nout can be interpreted as "number of outputs")
    % call a MEX-like Julia function
    function varargout = mex(nout, varargin)
        varargout = cell(nout, 1);

but nout contains the file name
K>> disp(nout)
double_it

Jl.mex does now require an extra integer argument. I think you may be looking at README.md for master. The README.md for the rebranding branch includes an example of calling Jl.mex with the extra integer argument.
I hope to merge rebranding branch into master soon (this week?) to avoid this sort of confusion.
Thanks for testing mexjulia out. Please do keep opening issues as you find them.

Yes, you're right -- I was using the example in the trunk version of README.md. Sorry for the noise!
Unfortunately I now get an error that crashes MATLAB when running the double_it example. I get consistent crashes if I run each command in README.md (except Jl.include('my_own_julia_code.jl')) in order, one-at-a-time, when running Jl.mex(1, 'double_it', a). I've tried multiple times, also using a pristine installation of mexjulia, and it crashes MATLAB every time.
"Interestingly", I once tried running the double_it.m script (instead of running the commands line-by-line) which did work, and after that I could run Jl.mex(1, 'double_it', a) a few times more. Unfortunately I cannot repeat this (and not for lack of trying...). :smile:
If I instead run the double_it.m script immediately after starting MATLAB, it will run without problems multiple times. If I then call Jl.eval('warn("Oh, no!")'); I get (with MATLAB responsive):
>> Jl.eval('warn("Oh, no!")');
Error using mexjulia
OutOfMemoryError()
 in yieldto(::Task, ::ANY) at .\event.jl:136
 in wait() at .\event.jl:169
 in stream_wait(::Task) at .\stream.jl:44
 in uv_write(::Base.PipeEndpoint, ::Ptr{UInt8}, ::UInt64) at .\stream.jl:820
 in unsafe_write(::Base.PipeEndpoint, ::Ptr{UInt8}, ::UInt64) at .\stream.jl:830
 in write(::Base.PipeEndpoint, ::Array{UInt8,1}) at .\io.jl:175
 in print at .\strings\io.jl:70 [inlined]
 in with_output_color(::Function, ::Symbol, ::Base.PipeEndpoint, ::String, ::Vararg{String,N}) at .\util.jl:302
 in print_with_color(::Symbol, ::Base.PipeEndpoint, ::String, ::Vararg{String,N}) at .\util.jl:306
 in #warn#936(::String, ::Bool, ::Void, ::Void, ::Void, ::Int64, ::Function, ::Base.PipeEndpoint, ::String,::Vararg{String,N}) at .\util.jl:340
 in warn(::Base.PipeEndpoint, ::String) at .\util.jl:332
 in #warn#937(::Array{Any,1}, ::Function, ::String, ::Vararg{String,N}) at .\util.jl:350
 in warn(::String) at .\util.jl:350
 in collect(::Base.Generator{Array{MATLAB.MxArray,1},Mex.##5#6}) at .\array.jl:307
 in jl_eval(::Array{MATLAB.MxArray,1}) at F:\software\Julia\mexjulia\branches\rebranding\jl\Mex.jl:72
 in jl_mex(::Array{Ptr{Void},1}, ::Array{Ptr{Void},1}) at F:\software\Julia\mexjulia\branches\rebranding\jl\Mex.jl:54

Error in Jl.mex (line 10)
        [varargout{:}] = mexjulia('jl_mex', varargin{:});

Error in Jl.eval (line 16)
        [varargout{:}] = Jl.mex(nargin, 'Mex.jl_eval', varargin{:});

After this I can still run all the example commands in README.md without any crash. However, after a few more executions of Jl.eval('warn("Oh, no!")'); it stops giving any output.
Then Jl.eval('println("Hello, world!")'); acts up instead:
>> Jl.eval('println("Hello, world!")');
Error using mexjulia
schedule: Task not runnable
 in enq_work(::Task) at .\event.jl:77
 in uv_writecb_task(::Ptr{Void}, ::Int32) at .\stream.jl:873
 in process_events(::Bool) at .\libuv.jl:82
 in wait() at .\event.jl:147
 in stream_wait(::Task) at .\stream.jl:44
 in uv_write(::Base.PipeEndpoint, ::Ptr{UInt8}, ::UInt64) at .\stream.jl:820
 in unsafe_write(::Base.PipeEndpoint, ::Ptr{UInt8}, ::UInt64) at .\stream.jl:830
 in unsafe_write(::Base.PipeEndpoint, ::Base.RefValue{UInt8}, ::Int64) at .\io.jl:155
 in write(::Base.PipeEndpoint, ::Char) at .\io.jl:194
 in print(::Base.PipeEndpoint, ::Char) at .\char.jl:45
 in print(::Base.PipeEndpoint, ::String, ::Char, ::Vararg{Char,N}) at .\strings\io.jl:19
 in println(::String) at .\coreio.jl:5
 in collect(::Base.Generator{Array{MATLAB.MxArray,1},Mex.##5#6}) at .\array.jl:307
 in jl_eval(::Array{MATLAB.MxArray,1}) at F:\software\Julia\mexjulia\branches\rebranding\jl\Mex.jl:72
 in jl_mex(::Array{Ptr{Void},1}, ::Array{Ptr{Void},1}) at F:\software\Julia\mexjulia\branches\rebranding\jl\Mex.jl:54

Error in Jl.mex (line 10)
        [varargout{:}] = mexjulia('jl_mex', varargin{:});

Error in Jl.eval (line 16)
        [varargout{:}] = Jl.mex(nargin, 'Mex.jl_eval', varargin{:});

Finally, this makes MATLAB unresponsive:
>> Jl.eval('warn("Oh, no!")');

and I have to kill it in the Task Manager.

I wonder if the issue that you report here is related to #28.


Add functions for bitwise operations

What new feature should Elvish have?
Now that we have os:stat returning a field perm which is a unix-style permission bit pattern, we could also use better tools to interrogate such bit patterns. Hence the need for functions like bitwise AND, OR, and friends.
Perhaps this should be restricted to non-negative integers. But it could work for arbitrary-precision negative integers, assuming that negative numbers are assumed to be represented in twos-complement form, with an implicit infinite sequence of leading 1 bits. If so, a bitwise NOT operation can also be implemented. Even if the end user is not going to use this directly for negative numbers, that could be useful for the bitwise version of AND $x (NOT $y) and similar constructs.
I don't know what would be good names for the proposed functions. But in analogy with the string comparison functions ==s, <s and so forth, one possibility is +b for bitwise OR, *b for bitwise AND, and -b for bitwise subtraction – -b $a $b … would return the bits set in $a but not in $b etc., with a unary variant for bitwise NOT. Or maybe we could just use uppercase names AND, OR, NOT?
Potentially, the operators could short-circuit just like the logical operators, so that, e.g., *b 1 2 (fail foo) would succeed and return zero.
The question of bitwise operators was briefly raised in chat by Tw on 2023-11-01.
Output of "elvish -version"
0.21.0-dev.0.20240320152034-dfe675a0b467
Code of Conduct

[X] I agree to follow Elvish's Code of Conduct.

While I would like to see numeric bitops implemented there are considerable challenges for doing so in Elvish given its numeric model. What does it mean to perform a bitop on a rational number such as num 3/5? Should it throw an exception? What about an inexact-num (aka float64)? And while and, or, not are useful it seems to me we would also want to support shifting left and right and possibly rotation.

Perhaps this should be restricted to non-negative integers.

Why? While shifting or rotating a negative int introduces interesting questions given the Elvish numeric model simply masking such a value has a straightforward definition and implementation. And dealing with negative integers is straightforward with easily describe behavior if limited to platform ints  and floats; i.e., excluding big ints and rationals. But this raises the bigger question of how to do this since, even if we limit the implementation to platform ints and floats, there is the question of how to deal with 32 versus 64 bit ints since Elvish deliberately doesn't expose that information. So we still have to deal with the fact that ints requiring more than 32 bits might be represented as "big ints". This is why I opened issue #1731 to propose that all public ints be represented as 64 bit ints if possible -- even on platforms where the native int size is 32 bits. That would allow the scope of this issue to be limited to native ints (and possibly floats) -- excluding big ints and rationals.

I think bitwise operations should work for all exact integers (int and big.Int).

As for naming... I would opt for more boring and verbose names in a new bitwise: module: bitwise:and, bitwise:or and so on.

I think bitwise operations should work for all exact integers (int and big.Int).

I agree. It is easy and obvious how to implement bitwise "and", "or", and shift left/right for int and big.Int. Defining rotation (circular shift) for the big.Int case isn't practical, but rotation of an int is an operation rarely used outside of specialized applications such as cryptography. Its absence in Elvish is extremely unlikely to be an issue for users of the language. If and when someone points out a compelling need for an integer bitwise rotation command how to implement it can be revisited. The other bitwise ops are useful enough that implementing them is worthwhile to do as soon as possible.


Admin export view for ITSystemHardware, info logging during Alesco data import.

This change is

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Collection exercise cleanup

What and why?
How to test?
Trello
https://trello.com/c/O1IS4QLq/1002-collection-exercise-cleanup

/deploy harrisonj


[mxnet] Updates MXNet engine to 1.9.0

Change-Id: I17f0fb861093cd2b09c21cf063d5a39d213dc4a9
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #1429 (27d7afe) into master (bb5073f) will decrease coverage by 1.40%.
The diff coverage is 48.17%.

@@             Coverage Diff              @@
##             master    #1429      +/-   ##
============================================
- Coverage     72.08%   70.68%   -1.41%
- Complexity     5126     5291     +165
============================================
  Files           473      493      +20
  Lines         21970    23195    +1225
  Branches       2351     2527     +176
============================================
+ Hits          15838    16396     +558
- Misses         4925     5522     +597
- Partials       1207     1277      +70

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <ø> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../modality/cv/translator/YoloTranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...i/djl/modality/cv/translator/YoloV5Translator.java
5.69% <0.00%> (ø)

...odality/cv/translator/YoloV5TranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...modality/nlp/embedding/TrainableWordEmbedding.java
45.00% <0.00%> (-3.34%)
:arrow_down:

...pi/src/main/java/ai/djl/ndarray/BytesSupplier.java
54.54% <0.00%> (-12.13%)
:arrow_down:

...i/src/main/java/ai/djl/ndarray/NDArrayAdapter.java
15.23% <0.00%> (-0.83%)
:arrow_down:

... and 156 more

Continue to review full report at Codecov.

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


Make IPC module accept arbitrary text over the socket

Currently, to extend polybar, we can either use the script module or the IPC module. The script module allows to do anything, but you have to spawn a new process. With the tail directive, it's possible to avoid spawning processes at a regular interval. But, a distinct process is still needed (and it eats some memory). With the IPC module, you can trigger an update from another process, but this will run a script to make the update (and it eats CPU and battery).
Something between the two could be useful: extend the IPC module to allow sending arbitrary text to be displayed instead of just a hook number.
I am willing to implement this, but as there is already some issues around the IPC module, I would like to gather some feedback and agreement around such a feature.
See #1127 and #1670 which are somewhat related.

I think there has been demand for this in the past as well and I think this would fit in polybar.
I do have some thoughts:

Polybar already has a one-way FIFO it uses for IPC, we should also use it for this feature. In fact, we could (and probably should) just create a module action where the data is the text sent to the module.
I'm not sure if we should extend the IPC module, it's probably better to have a new module dedicated for this. Unless you have an argument why this would integrate well with the IPC module.


[EDIT] Link to r/Orfano not working

Entry
https://web3isgoinggreat.com/?id=2022-02-09-0
Changes
The link to r/Orfano links to the Jim Waterson tweet already linked above rather than (presumably) https://www.reddit.com/r/Orfano/
Agreement
By submitting this issue, I irrevocably agree to release my contribution under the CC-BY 3.0 License. I agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
No need for attribution!

Oops, thanks!


Added Italian Language

Looks good.

Instructions were very clear so i had no issues making a translation

Yep. I am sure this will be merged in soon.

See 3875b07e44f3356be3c834661f465afeeea9e5ad


[ZF2 or ZF3] Zend\Console: cli_set_process_title()

Hello together,
i started to use cli_set_process_title in my console actions (because some of them are taking longer than just a second)
(It's a PHP 5.5 feature)
if (function_exists('cli_set_process_title')) {
     cli_set_process_title('Job for xyz');
}

Wouldn't that be a good idea to integrate it into the framework?
Ideas

set the matched route name as the title
set the complete cli command as the title
set the Module\Controller\Action as the title (like it's in the dev toolbar MyModule\MyController:fooAction

Any other suggestions?

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Unturned player desconnecting

Recently with these new updates my Rocket started to '' kick '' half of the players on my server. On the server vanilla it does not. I'm sure that updated the Rocket correctly!
My internet is broadband!
I limit my server to 8 players in order to not require much of the capacity of my internet!
My TPS, according to the Rocket plugin is always 0
Thanks!

Are you using protected slots?

Usually that happens when you computer cannot keep up. You are sure its only when you have Rocket?

Zamirathe what that's? How to disable these ''protected slots''? How to find out if I am using it?
falsechicken my computer have very good processing speed!

Zamirathe what that's? How to disable these ''protected slots''? How to find out if I am using it?
falsechicken my computer have very good processing speed!

This can happen for several reasons, one is what falsechicken said, that your cpu is too slow and it can't keep up with all the players on the server. The other is if the server is freezing for extended periods of time, which can cause people to go over the set timeout value on the server causing them to DC from the server.
The freezing disconnect can potentially happen if you are using a plugin that uses a Mysql DB, but the DB that you are using isn't a local DB(on the same computer.), but one over a network(much worse if it is a over the internet DB.).
It can help somewhat if you increase the timeout value on the Timeout command(which is in miliseconds.) and put that command in the server's commands.dat file.

I not use plugins!

Also the TPS value on the server should never show up as "0", the lowest that I have ever seen it get to is 3 TPS and not lower. For example, one of my server's at the moment with 15 players is showing a TPS of 403.

cartman-2000 How to increase my TPS?

There aren't very many ways to "really" increase the TPS on a server, it is tied to the speed of the core on the cpu. The best you can do, most of the time, is to reduce the amount of other stuff running on the system that the server is running on. However, if it is really showing a TPS of 0 on your server, than something else might be wrong with it, or rocket, since that isn't supposed to happen.

Then the timeout command does not work, how can you help me? What great value to put in timeout?

You can try the value 5000 for a 5 second timeout.

cartman-2000 thank you! But if that does not work? What I can try to increase the TPS my server or him to stop ''kick'' half of the players from my server?

If your TPS is at 0 that means you get better hardware.Something is keeping your server in trouble, maybe to many items on the map, maybe autosave interval of 0, It means your server "processes" less then a frame per second,.. Pretty simple.

Thank you!


Update StorageOS Operator to version 1.4.0

Can I please get some help with the CI failure?
The new resource nfsservers expects a storageosclusters resource to be created and healthy. Since it can't find a healthy storageos cluster, it shows error.
I'm not sure if that's causing the cleanup to fail.
Is there a way to mark some custom resources to not created directly? nfsservers resource should not be created directly by a user. It's used by storageos internally.

@darkowlzz This is a limitation of the test tooling. It will try all the CRDs there. Not sure if the clean up error is caused by that. We can merge still.

@dmesser thanks for replying.
I'm aware of the OpenAPI spec we have for the custom resources. Previously, the CRD files were manually edited after the first time generation, the validation part was also manually added and it was hard. Most of them were created with SDK 0.0.x. I don't remember if the cli generate command had openapi option. This time the same CRD files were updated with operator-sdk generate openapi command. So the underlying APIs are still the same, it's just that the CRDs have more generated information.
But thanks for pointing that out, will be careful about that in the future.
BTW, this same operator bundle got published in the red hat operator marketplace after passing their metadata scanner CI. We should be good to merge this if there are no more concerns.
Thanks!


Remove test block from properties builder

Have signed the the Cap One License Agreement

@no1melman Please sign the CLA https://hygieia.github.io/Hygieia/contribute.html and let me know so that this PR can get merged

@rvema see previous comment - have done it

@no1melman we have migrated the jenkins collector to its own repository. We would appreciate if you could close this PR and recreate against the new repository - https://github.com/Hygieia/hygieia-build-jenkins-collector


adapt to newer pytorch versions

When not using docker, the changes are needed for PyTorch versions > 1.7.
In addition aten::cudnn_convolution_backward_weight and aten::cudnn_convolution_transpose_backward_weight are deperacated at the beginning of this year, so adapted it to torch.ops.aten.convolution_backward

Which pytorch version are you using?

Never mind


mq(hdpi) and height

Hello,
I use Sass-mq on several project.
I would use it for some other rules.

min and max height
hdpi

Can it be added ?

Thank you for using sass-mq, @ryuran.
min and max height can be added using the $and parameter. The reason why these use cases are not supported with their own parameters is the IE8 support (the fallback wouldn't work).
When it comes to hidpi, have you checked my other project? GitHub.com/kaelig/hidpi

Thanks @kaelig.


Drawing Manager and Indoor Manager

Hi,
A project I am working in is using this wrapper but it will require azure maps drawing and indoor modules. Will the project be open to PRs with these features? I have looked into drawing and think the best way would be to make a AzureMapsDrawingManagerProvider following the same pattern so far with layers and data source components.

Hi @dandical
Sure we are open for PR and features request.
If you can add it by yourself and create PR it will be great otherwise we can add start work on it but in next week.
Fell free to open PR with this feature.

Ok I will get it done, I noticed the drawing module has an atlas.Map type conflict with azure-maps-control 2.0.25 so will need to wait for your latest version upgrade PR to get approved as well.

No worries I will work on it. This is waiting on your latest PR to update azure-maps-control to 2.0.31 as there are some dependencies that the latest release of drawing modules preview relies on.

@dandical Ok I will merge this one so you can work on the latest version.

@psrednicki  Thankyou. A drawing manager creates it's own datasource by default. Features can be added to this data source to provide initial drawings to the user that they can modify. My suggestion is for it to be used as follows when providing initial features in the canvas.
 <AzureMapDrawingManagerProvider options={drawingOptions>
      <AzureMapFeature
          id={"polygonExample MapFeature"}
          type="Polygon"
          coordinates={[
               [-50, -20],
               [0, 40],
               [50, -20],
               [-50, -20],
           ]}
        />
</AzureMapDrawingManagerProvider>

To do this The AzureMapDrawingManagerProvider creates both a drawingManagerRef and dataSourceRef (the dataSourceRef is the data source created by the instantiation of the drawing manager).
The only problem i have encountered in this is the use of the useCheckRef hook in AzureMapFeature's useFeature which is equivalent to this useEffect
  useEffect(() => {
   if(dataSourceRef && featureRef)
    dataSourceRef.add(featureRef)
    return () => {
      dataSource.remove(featureRef)
    }
  }, [featureRef])

I need to add the dataSourceRef to the dependency array here as the dataSource is not created by the component, but is asynchronously created by when the drawingManager is created when the map is ready. Any concerns with this?

Im started work on Drawing Manager and its working, maybe not perfect but working.
Still have some issues to fix, like toolbar because now its looking like this:

@dandical So your use case is - already have some feature(point, polygon etc.) and by drawing manager you want to mutate it. Am I right?
About DrawingManger - its create dataSource and Layers by itself
Im think on this stage of development lets start by just add drawing tool, and then lets try to resolve your case. I will create PR with and mention it here.

Im fixed styles errors and created PR with my changes.
@dandical you can start work form that.
I also update playground for that feature(remember to use local version of lib). https://github.com/WiredSolutions/react-azure-maps-playground/pull/42

@psrednicki i already implemented all mode of drawing toolbar and only edit mode is throwing error so do you have any suggestions.
Error : react-azure-maps.es5.js:132 Uncaught Error: The layer '[object Object]' has not been added to the map and its rendered features cannot be retrieved.
this error is coming on edit the polygons

@psrednicki i already implemented all mode of drawing toolbar and only edit mode is throwing error so do you have any suggestions.
Error : react-azure-maps.es5.js:132 Uncaught Error: The layer '[object Object]' has not been added to the map and its rendered features cannot be retrieved.
this error is coming on edit the polygons

@Piyush925 Nice, good job! Can you open PR with your changes? Maybe I can check it by myself.
Maybe downgrade drawing tools version will fix it.

Error : react-azure-maps.es5.js:132 Uncaught Error: The layer '[object Object]' has not been added to the map and its rendered features cannot be retrieved.
this error is coming on edit the polygons

@Piyush925, @psrednicki: this issue occurs because there is multiple versions of azure-maps-control in the target bundle. (LayerManager.prototype.getRenderedShapes has var layerId = layer instanceof Layer ? layer.getId() : layer; where instances Layer is false because the layer is constructed with azure-maps-drawing-tools's azure-maps-control's Layer)
This can be verified by running:
yarn list azure-*

for me I got:
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>   └─<EMAIL_ADDRESS>✨  Done in 1.05s.

azure-maps-drawing-tools lists azure-maps-control as dependency rather then peer dependency which may result in two version of dependencies at resolution.

@psrednicki, @msasinowski:
Actually the thing that solved deduplication at bundling for me was adding azure-maps-drawing-tools to plugins.externals.exclude in rollup config (https://github.com/ambientlight/react-azure-maps/blob/4b868b6335d120b4f549f4afa0d873cb6989b6d1/rollup.config.js#L38)
I am unfamiliar with rollup, I'm checking the docs of rollup-plugin-node-externals docs and trying to make sense why externals are used for everything except azure-maps-control and azure-maps-drawing-tools, can you give me a small explanation for this?

Are we likely to see this PR being merged soon? Noticed it's been open for a while now. Really keen to see support for drawing tools.

Seconding this, can it be added soon?


Automated power control on node exit/entry from/to tenant (CASMPET-6317)

Summary and Scope
Refactor structure for versioned releases, add power control functionality.
Issues and Related PRs

https://jira-pro.it.hpe.com:8443/browse/CASMPET-6317

Testing
Verified image on redbull:
{
  "childnamespaces": [
    "vcluster-green-slurm"
  ],
  "tenantresources": [
    {
      "enforceexclusivehsmgroups": true,
      "forcepoweroff": false,
      "hsmgrouplabel": "green",
      "type": "compute",
      "xnames": [
        "x3000c0s19b3n0"
      ]
    },
    {
      "enforceexclusivehsmgroups": true,
      "forcepoweroff": true,
      "hsmgrouplabel": "green",
      "type": "application",
      "xnames": [
        "x3000c0s32b0n0"
      ]
    }
  ],
  "uuid": "7450f2d0-1a7c-4f36-9898-8a73e6c9fc9a"
}
Deployed

Was a fresh Install tested? N
Was an Upgrade tested?      N - N/A
Was a Downgrade tested?     N - N/A
If schema changes were part of this change, how were those handled in your upgrade/downgrade testing? N/A
Risks and Mitigations
Low
Requires:

Nothing

/backport stable/1.5


Texinfo failing to download on staging

Since https://github.com/NixOS/nixpkgs/pull/138063:
https://hydra.nixos.org/build/153907889/nixlog/3
error: unable to download 'https://ftpmirror.gnu.org/texinfo/texinfo-6.8.tar.xz': Couldn't resolve host name (6)
builder for '/nix/store/8x8fismhjkqwcl5qc2rq2zpm70sm9vv7-texinfo-6.8.tar.xz.drv' failed with exit code 1

cc @trofi

Fetch works locally here:
$ nix-prefetch-url https://ftpmirror.gnu.org/texinfo/texinfo-6.8.tar.xz
path is '/nix/store/ycj1q918l6852kndr75rlwmw43k5ybys-texinfo-6.8.tar.xz'
1i7yb7mrp3inz25zbzv2pllr4y7d58v818f1as7iz8mw53nm7dw

I wonder if it's related to nix-daemon's bug in fetching new tarballs:

https://github.com/NixOS/nix/issues/5089
https://github.com/NixOS/nixpkgs/pull/137197

Tl;DR is: nix-daemon sometimes does not initialize glibc's NSS before entering chroot and fails to do it afterwards. https://github.com/NixOS/nixpkgs/pull/137197 will fix it but will also require builder update.

Yes, it's certainly that nix bug.  I don't know... perhaps we can do the same as in the previous case: 28b6a91047e  I'm not aware of anything better I can do (personally) about this.

Would using nixUnstable instead of nix on hydra builder be an option until nix is fixed? (AFAIU nixUnstable already has the fix). Or too risky to get bugs creep in?

It's unblocked now, though the underlying problem still isn't fixed.


Add the INNOPATHS regions

Per email conversations with @tatar99 and the PRIMES team, this PR adds the regions from the INNOPATHS project for easier comparison between REMIND, PRIMES, and other models.
I took the liberty to come up with "readable" region names instead of the abbreviations and added the suffix (IP) such that the regions can easily be identified in a large ensemble (with many different region aggregations, similar to adding (R5) in the global region).
FYI @HauHe

To me this looks good. If I'm not mistake it is the mapping that REMIND is already using, no?
@tatar99, I don't see NEN, but for my use that is ok, since NEN didn't contain any EU countries.

@HauHe Yes, I checked this is the same mapping we were taking about, except for NEN. Looks good to me too.


[BUG] Error when music stops playing.

(node:3288) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'url' of undefined

Closed per Discord. Own code issue.

Closed per Discord. Own code issue.


Add bool for barion matter

Since it is common to use only barion matter in calculations it would be useful to attach boolean attribute to each particle that determines if it is from barion or dark matter.

Done in 53370b8847fbcae41fafa57da8e6dee715e1c757


feat/favorites

This PR includes:

The skeletal setup of the feature
The favorites view
The favorites view model

LGTM!


Feature info anzeige

Creation of configurable feature info display

Thanks for the review!

:tada: This PR is included in version 6.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Purgecss seems not working

Version
@nuxtjs/tailwindcss: v2.0.0
nuxt: v2.12.2
Steps to reproduce

Migrate 1.4.1 to 2.0.0 follow this link

npm run build

What is actually happening?
Tailwind CSS seems like not be purged.

@steven0811 @Atinux it actually seems like in my case after updating to v2.0.0 our custom config file isn't being read at all.

You confirm that you use extractCSS?
I don't know if Tailwind v1.4.0 PurgeCSS works with extractCSS, could you try without it?

Am I right, if I have some unused css classes in my eg. index.vue file, purge should remove them?
Because reading all "purge not works" fresh issues and build up the setup following the recommendations, all unused classes remain there. For example the .subtitle class which comes with the base nuxt install.

I was having issue configuring purgecss to work with nuxt, and the nuxt-purgecss plugin mentionned here was throwing errors in the build.
Evenutally I resolved it by not using the nuxt-purgecss module, and instead use the tailwind own purgecss as mentionned in the first comment.
Also, I'm using the nuxt extractCSS, and one option to extract the css as one file only:
nuxt.config.js:
  build: {
    extractCSS: true,
    // this is not required, output as one css file instead of one by page.
    optimization: {
      splitChunks: {
        cacheGroups: {
          styles: {
            name: 'styles',
            test: /\.(css|vue)$/,
            chunks: 'all',
            enforce: true
          }
        }
      }
    },

tailwind.config.js
{
  ...,
  purge: {
    enabled: process.env.NODE_ENV === 'production',
    content: [
      'components/**/*.vue',
      'layouts/**/*.vue',
      'pages/**/*.vue',
      'plugins/**/*.js',
      'nuxt.config.js'
    ],
    options: {
      whitelist: [
      ],
      whitelistPatternsChildren: [
      ]
    }
  }
}


Adds Input lookup component

Fixes #188

FormWrapper now loops through all PTs and displays components according to "type"
Lookup input field to QA that allows multiple searches/selections to be made (using react-bootstrap-typeahead component module)
Adds lookup PT to default MonographInstance RT collection

Coverage increased (+0.1%) to 82.609% when pulling f47b7bdc0689f1908ece3ca40fd5c614eb4708ea on input-lookup into 56e3787eddbf3c0a398c18dd568c2631204fd7f5 on master.

I'm interested in what @jermnelson and @SaravShah think about which PR should be merged first:  this one or the modals one?   One of us will have to rebase after ...

@ndushay @jermnelson i have no preference, i guess which ever will have least rebase conflict?

Hi @ndushay, I agree with @SaravShah on using the least rebase conflicts as an order of rebase.


Improved Postgresql compatibility and failover support

Fixes #27.
As far as I can see it was already fixed in #35, but then these changes was removed in #52 because of #50 SystemStackError and other issues.
So this PR is doing almost same stuff as #35, but a bit more deeply and also includes few more bugfixes (including fix for #50).
It allows app to start and run with any set of working/down DB servers and raises errors only on write queries when master is down and on all queries when all servers are down.

Hey @Drakula2k, thanks for putting the time into this. Let's work on getting it green. I've done an initial review and I'm on board with the desired results. I'll do a more detailed review when it's ready to ship.

Thanks, I'm working on build.

Done.

Also it fixes #78 and #79

Would it be helpful if I tested this in our staging/production systems? I'm hoping to continue our upgrade from very old Makara (we put the upgrade on hold a while ago due to time constraints), and it looks like we would want these fixes before pushing a new version to production.

@sax I'm currently using it on production, but on small microservice which is very simple and not covers all of use cases. I'm planning to use it also on a bigger project in future, so I'd appreciate any feedback.

It would be beneficial. I just now queued up a story to apply it to our staging environment, and potentially a subset of our production environment as a test. I apologize for being so unresponsive.

Awesome! I actually have time allocated this week for working on our woefully ignored infrastructure upgrades, so I hope to test this tomorrow.

When I run rake db:create:all I get an error, I think related to the change of ConnectionWrapper away from being a SimpleDelegator.
The first time it call :create_database on ActiveRecord::Base.connection, the context in method_missing somehow calls back to the method defined in databases.rake, not on the connection wrapper.
This is in Rails 3.2.21.
** Invoke db:drop:all (first_time)
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:drop:all
** Invoke db:create:all (first_time)
** Invoke db:load_config
** Execute db:create:all
wrong number of arguments (2 for 1)
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:84:in `create_database'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/proxy.rb:75:in `block in method_missing'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/proxy.rb:117:in `block in any_connection'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/pool.rb:96:in `block in provide'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/active_record/connection_adapters/makara_abstract_adapter.rb:33:in `handle'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/pool.rb:95:in `provide'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/proxy.rb:116:in `any_connection'
/Users/sax/.gem/ruby/2.1.6/bundler/gems/makara-3be697fa290f/lib/makara/proxy.rb:74:in `method_missing'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:144:in `rescue in create_database'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:85:in `create_database'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:52:in `block (5 levels) in <top (required)>'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:184:in `local_database?'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:52:in `block (4 levels) in <top (required)>'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:38:in `each_value'
/Users/sax/.gem/ruby/2.1.6/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:38:in `block (3 levels) in <top (required)>'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/opt/rubies/2.1.6/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/Users/sax/.gem/ruby/2.1.6/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
/Users/sax/.gem/ruby/2.1.6/bin/rake:23:in `load'
/Users/sax/.gem/ruby/2.1.6/bin/rake:23:in `<main>'
Couldn't create database for {"encoding"=>"unicode", "pool"=>10, "username"=>"*****", "password"=>"********", "host"=>"<IP_ADDRESS>", "port"=>5432, "min_messages"=>"WARNING", "adapter"=>"postgresql_makara", "user"=>"*****", "makara"=>{"blacklist_duration"=>30, "sticky"=>true, "master_ttl"=>5, "connection_error_matchers"=>[/pg::error: : select/, /no more connections allowed/, /result has been cleared/, /no connection to the server/, /the database system is (starting up|shutting down)/, /reset has failed/, /connection not open/i], "rescue_connection_failures"=>true, "connections"=>[{"name"=>"master", "role"=>"master"}, {"name"=>"replica_1", "role"=>"slave", "host"=>"<IP_ADDRESS>"}, {"name"=>"replica_3", "role"=>"slave", "host"=>"<IP_ADDRESS>"}]}, "database"=>"development"}

In a pry session, I find the following:

in the proxy's method_missing, the connection responds to :create_database
when I go into the connection wrapper instance and look at the source of method(:create_database), it is actually the code defined in databases.rake
every method defined in databases.rake is available in the connection wrapper

Does it make any sense why this would be happening?
You might not run into this problem in Rails 4, as all of the methods in the rake file were pushed into objects.

Ok, I get what happens. In Rails 3, the methods defined in databases.rake get defined on Object. When ConnectionWrapper was a delegator, everything got passed down to the wrapped database adapter, so there were no problems. Relying entirely on method_missing means that the methods defined on Object get used in preference to the wrapped connection.
I'll provide a gist to fix this for Rails 3, but don't think it's worth fixing in Makara.

Here's a way of fixing this problem in a Rails 3 app.
https://gist.github.com/sax/a730ec5e3a1a768ef162

Thanks, I'll try to fix it on this week.

I've done some quick testing of this in our staging infrastructure, and it appears to work well. I ran into some issues with rake db:migrate, but I suspect that that might have to do with our use of Rails 3 and PGBouncer. I'll play around with that a bit more, to see if I can nail it down.

The problems with rake db:migrate turned out to be more issues with the database.rake from Rails 3. I've updated the gist above to reflect the fact that now I'm just stealing the code from Rails 4 and monkeying it into Rails 3 (at least for PostgreSQL).

I found a workaround, check this out.

Not sure what's up with 1.9.2 builds, and 1.8.7 doesn't support .public_send. I think 1.8.7 support should be dropped, even the Ruby team doesn't support it (along with 1.9.2 and 1.9.3).

I'm not sure if this will solve the root problem, but I also don't think you necessarily need to fix it. Rails 3 will only receive security updates from here on out, and this is not a problem in Rails 4. We're only running into it because we're trying to upgrade Makara in order to upgrade out app to Rails 4.

I'm in favor of dropping < 2.0 support.

SimpleDelegator prioritizes public methods too, so this fix is not only for this case.

I integrated it to a bigger project, works pretty well.

@mnelson is this project still maintained?

Hi @Drakula2k - I realize it's been quite a long time with this PR. I'm starting off the new year with a resolution of managing this project and adding a few things.
What's the current state of this code? Are you using it in production?
Thanks for helping out.

@bleonard we have been using code from this pull request in our production site since the end of Aug 2015. Apart from our issues described above (where we have to work around the Rails 3 database.rake) it seems to be working fine.

Awesome. Thanks @sax

I'm using it on production as well. The only issue I noticed: when already connected host is going down/non-reachable, postgres adapter gives very long timeout (30 or 60 sec) before raising connection exception, which is not configurable and should be fixed somewhere inside adapter's C code. I already tried, but no luck yet, will try to fix it again later.

yes, we've something like that, too. then it doesn't get blacklisted. i believe it's a problem if the timeout time there is greater than the unicorn timeout or something else upstream. it's one of the things i want to look into. my current hope it to figure out where to set it on the mysql adapter to not be so long.

ok, i'm going to merge this and test it out on our staging / prod.

Following up with noted timeout issue here: https://github.com/taskrabbit/makara/issues/102


Update share functionality

Add Screenshot image to project for facebook and linked in sharing. Update the bookmark code to include cluster options and layer options. Look at projections map for an idea of how to implement this.

Facebook image not working.  Other share images are coming up.

<meta property="fb:app_id" content="237366436641850">
This content field needs to be updated with the correct facebook id. it is in the index.html file line 28


Create a github action to tag new commit in flutter/plugins with a "temp-release-" tag

This action will

Run in post-submit
Wait for all the other CI checks to pass
Push a git tag named "temp-release-`

This is obsolete as we will go with a different approach that doesn't require a temp tag. See: https://github.com/flutter/flutter/issues/81446


Adding a dedicated recursion logging

This feature allows recursion logging to stdout on INFO level.
Currently this is only possible using DEBUG level which is not an option in production.
Using DEBUG level in production might overload the logging platform with too many messages. We need recursion messages to analyze our dns traffic, this approach is to reduce the number of log messages.
As a followup we need to filter this with a positive list of domains, but first we try to filter the messages on our logging platform.
Co-authored-by: Matthias Vach

This feature request feels a bit like a slippery slope. If we go down this route we could end up in a situation where we would have to add a new flag for every new logline that gets introduced. So to better understand the request could you maybe elaborate on why filtering the debug logs before shipping them to the central logging infrastructure would not satisfy the same requirements?
For example, the syslog-release supports setting customer rules, which get applied before the logs are shipped.

We are only interested in requests which are resolved by the upstream dns.
For this reason, this PR introduces a configurable log category (recursion_logging).
We see bosh-dns request rates of 40req/s (with a peak of 85req/s),
only 0,25 req/s (with a peak of 17req/s) are sent to the upstream dns.
Debug logs produce 3 log entries per request for all requests (plus additional debug logs):
This results in 120 log entries per second and a peak of 255 log entries per second.
The suggested solution would only log recursions (requests which are sent to the upstream dns).
It would not log internal domains and cached domain requests:
This would result in 0,25 log entries per second and a peak of 17 log entries per second.
So the suggested approach would reduce the IO and CPU load on the instances significantly.
Furthermore, new bosh-dns releases might introduce additional debug logs, which suddenly popup and might cause additional load.

~300 messages per second doesn't sound like a terribly large volume of messages to filter out. Can you show us evidence that this volume of messages is actually a performance problem?
In general, I really like the idea of selectively logging categories of messages... BIND 9 is one DNS server that does this. However, to do that correctly would be a significant undertaking, and I'm pretty wary of only partially doing such a thing.

Please don't close the PR, we are still looking into the performance impact of debug logs and other logging options.

Please don't close the PR, we are still working on it.

It seems that the requirements in #79 would fit here, with only the source IP added to the logged lines.

Tracing external DNS request is really useful and needed feature in case of DNS issues. Filtering the forwarded logs by custom rules of the syslog-release is not easy to implement when you have many deployments which are managed by different teams. I think that BOSH DNS should provide an option to trace DNS requests with a manageable amount of log entries per request. My personal opinion is that two options make sense here:

log the entry introduced by this pr always when the log level is set to INFO
add a more generic switch to activate this entry. The switch could be called something like enable_dns_tracing. In the future we can add more log entries to that if required.

We understand that broadening the configuration surface adds complexity. Following the argumentation of @beyhan, would it be an option to log recursions on INFO? We're still hesitant to use DEBUG in production. In the end this is the log level where engineers would expect that they can dump anything in without considering scale. Following-up any changes in debug logging in the future with adjusting syslog_forwarder rules sounds very cumbersome.

@beyhan I stand by my statement made here: https://github.com/cloudfoundry/bosh-dns-release/pull/78#issuecomment-900510251, and have yet to see anything that changes my opinion.

@klakin-pivotal  In the mean time we observe ~200 req/s which will produce ~600 messages per second if DEBUG level is used. Trying to validate whether this amount of log entries causes a performance issue for the logging stack or the VMs itself is not the right path to follow IMHO. People expect that DNS just works without consuming any noticeable amount of CPU, Memory or IO. The main purpose of the VMs where BOSH-DNS is running is to run other workloads. The overhead of BOSH-DNS should be unnoticeable and shouldn't compete with the running workloads (like apps).  A reasonable goal for me is to have a default configuration of BOSH-DNS which consumes as less resources as possible and provides the need information to analyse issues. That is why I don't think that running BOSH-DNS in DEBUG mode on production is a good idea. So the latest suggestion is to change the log level of the external recursions from DEBUG to INFO because this information is required when analysing DNS issues caused by the communication with the IaaS providers DNS servers.

People expect that DNS just works without consuming any noticeable amount of CPU, Memory or IO.

I agree. But we're not talking about running DNS, we are talking about debugging DNS. Debugging DNS could take an arbitrarily large amount of resources, depending on how deep you need to go, and your request volume.

A reasonable goal for me is to have a default configuration of BOSH-DNS which consumes as less resources as possible and provides the need information to analyse issues.

I agree, to an extent. My ideal configuration for BOSH DNS would be to log nothing but infrequent INFO statements ("I am starting up!", "I am shutting down!", "I am reloading my configuration!"), and any ERROR or FATAL statements ("My configuration is invalid and I cannot start up!", "I'm crashing", etc, etc.).
Please don't forget that that the statement I linked to contains two parts. The second part is this:

In general, I really like the idea of selectively logging categories of messages... BIND 9 is one DNS server that does this. However, to do that correctly would be a significant undertaking, and I'm pretty wary of only partially doing such a thing.

I agree, to an extent. My ideal configuration for BOSH DNS would be to log nothing but infrequent INFO statements ("I >am starting up!", "I am shutting down!", "I am reloading my configuration!"), and any ERROR or FATAL statements ("My >configuration is invalid and I cannot start up!", "I'm crashing", etc, etc.).

I agree with that and even would extend it to: My ideal configuration is the one which allows me to take a decision during an outage without the need to re-deploy or to re-configure of BOSH DNS (which we are not allowed during an outage) because DNS issues have direct customers impact. At the moment logs for IaaS DNS errors are there but BOSH DNS doesn't provide any logs at INFO level for degraded state of the IaaS DNS services  which could cause issues on customers side. This pr is aiming to solve that situation for external DNS request.

In general, I really like the idea of selectively logging categories of messages... BIND 9 is one DNS server that does this. >However, to do that correctly would be a significant undertaking, and I'm pretty wary of only partially doing such a thing.

This will be a really significant undertaking and also the performance of the current implementation has been already validated. Many performance and logging improvements have been implemented to improve the production sate e.g. https://github.com/cloudfoundry/bosh-dns-release/pull/57, https://github.com/cloudfoundry/bosh-dns-release/pull/61, https://github.com/cloudfoundry/bosh-dns-release/pull/54, https://github.com/cloudfoundry/bosh-dns-release/issues/52. Also, if I understand it correctly BIND 9 doesn't recommend the selective logging for production. From their github page:

The --enable-querytrace option causes named to log every step of processing every query. The --enable-singletrace option turns on the same verbose tracing, but allows an individual query to be separately traced by setting its query ID to 0. These options should only be enabled when debugging, because they have a significant negative impact on query performance.

It looks like to me that we won't be able to take a decision based on the discussion here. I would suggest to add this as a topic for the Working Group meeting on 27th of January (the meeting this week will be on a too short notice). @klakin-pivotal  what do you think?

My ideal configuration is the one which allows me to take a decision during an outage without the need to re-deploy ... BOSH DNS ...

I agree very strongly with this.

...allows me to make a decision ... without the need to re-configure ... BOSH DNS ...

This is trickier. There are many things that can go wrong with DNS (or a DNS server), and if you don't want to be emitting tons of logs around all the time, then you will need to be able to selectively enable and disable logging.
Like Ruben said way back when, adding individual categories of things to INFO level is a slippery slope. The next time someone needed to flip on DEBUG logging to get some other piece of information, they're likely to want that at INFO level, too. Given enough time, INFO is too noisy, and folks are switching to NOTICE level to escape the noise.

BIND 9 doesn't recommend the selective logging for production.

The BIND options that I'm talking about modeling our selective logging system after are these options: http://www.zytrax.com/books/dns/ch7/logging.html
Also, my hunch is that setting the resolver log (and maybe also queries) category to debug will produce the sort of data that the fellow who opened this PR is looking to get.

I would suggest to add this as a topic for the Working Group meeting on 27th of January... @klakin-pivotal what do you think?

I know next to nothing about this Working Group, so I don't have enough information to have an informed opinion.

Would changing the configuration interface to allow for more granular control down the line, once more log topics are introduced be an acceptable solution to y'all?
Something like:
logging_categories:
  default: []
  example:
  - recursion: info
  - queries: debug

Instead of:
enable_recursion_logging:
  default: false

For me this makes sense. It also provides an approach for future log changes if required.

In general a lightweight approach to introduce logging categories with their own log levels sounds reasonable. From your example it's not yet clear to me how it would actually look like. What I understand is, that we would have the default category, which would be what all loggers currently use. Then we could add a new category, like recursion and set it to a different log level. Implementation wise that would for example require that all logging that happens in the context of recursion would need a separately instantiated logger, that would run with the specific recursion log configuration or the default one, if no specific configuration exists. So in this scenario we would configure:
logging_categories:
  default: [] # here it is not clear to me, why this is an array and why default is necessary at all
  example: # why do we need this hierarchy level, would we expect more names?
  - recursion: debug

Could it not look like:
log_level: error # the property that already exists and which is the default
logging_categories:
- recursion: debug

Or:
logging_categories:
- default: error # is doing the same as the original log_level property
- recursion: debug

With the separate log level for e.g. recursions it would be saver to run with debug. Still it could produce more logs than we have now with the original proposal, where we have a single log entry per recursion. And yes the values above don't sound big, but we have rates of 270k/min hitting the logging stack, with 99.x% being recursions and then 1 or 3 or 5 lines makes a big difference. Still it might be an acceptable approach. Extending the logs of the special categories could be something also announced in release notes of new versions and it would be a smaller target to filter out.

@friegger my example was just using the bosh job spec format. Which has the default, description and example keys. Sorry for the confusion, the idea was indeed that the rendered config passed to the bosh-dns process would be something like:
log_level: error # the property that already exists and which is the default
logging_categories:
- recursion: debug

Thanks everyone for settling on a configuration surface that's acceptable. Once an implementation is ready the PR will be reopened. It will take some time until this work can be picked up.


Add jealous by eyedress

Song Name
jealous
Artist Name
eyedress
Source
Youtube
Youtube Link
00hRrmul1F9VnRLr
Direct File Link
No response
Song ID
677785
Start Offset [ms]
1
Extra
Created from Auto Nong.
Created for level: 18834999

reject
invalid YouTube link


Sign packages on Bintray

As noted in #1595, one is currently warned about unsigned packages when one installs via the Debian (and Ubuntu) repo. I have not tried any of the others. I would very much like the packages to be signed, should we deploy this in production.
W: The repository 'https://dl.bintray.com/mashape/kong-ubuntu-xenial-0.9.x xenial Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

The behaviour of APT has changed in Ubuntu 16.04 where unsigned repositories are disabled by default. So while it was a Warning previously, it's now and Error.
In order to install Kong, one has to configure APT::Get::AllowUnauthenticated, but that is something one would like to avoid as it applies to all repositores.
So please sign the repositories. Seems to be something Bintray supports with not too much fuss, but guess it requires a premium plan.

 plain text secrets

 Sign packages on Bintray

+1 as this causes a lot of issues in deployments

any ETA for this ?

please do this it's simple.
Login in bintray go to your repository -> edit -> scroll down and click (GPG sign uploaded files using Bintray's public/private key pair)
This would be better than unsigned repos because nobody should do unsigned repos and on installation you will get troubles with the repo managers like apt / aptitude etc..

+1 from my side, a proper deployment of that dpkg package is currently not possible due to that issue

Please do this. We would love to use Kong but it won't get past our security review if you continue using an unsigned repository

we started to rehost this just to get around the unsigned package

+1

@shashiranjan84 this was fixed, right?

@p0pr0ck5 I have added changes to sign the repo, artifacts still would unsigned. Change would visible from v0.11.

 Execute the planned move of distributions to Bintray

+1
if the proposition of @bkuebler work without any issue ..
@shashiranjan84  we want to install the latest version to compare Kong with the other open source .

@llarsson  do you have an news?

just small reminder about this..

Any progress on this?

resolved now


disable non registered user to comment

hi how can i disable non registered user to post comment and access the messages?

This really has nothing to do with this package, the package should never implement something like that.
With laravel you have your Auth to use for things like that.
http://laravel.com/docs/5.0/authentication

@avlastenok but the modification to make it work between 2 user only is also not part of this package?

Actually it is this package delivers a good bunch of tools for you to use as you wish and yes you can make it work out of the box between two users only but that is your job to limit the users to that functionality.

@avlastenok thanks, is there any documentation available for this?

@dincio please take a look at the authentication docs that @avlastenok posted as well as maybe signing up for something like Laracasts. As @avlastenok stated, the tasks that you want to accomplish are supposed to be on the application level and not included in this package.


Back Date

I'm trying to update SPEC #7384 it was started on Sept 3 and i'm trying to continue with that date and i'm getting an error message saying the date conflicts replaced with today's date

date field is not working at all to update in conductor

The date box should prepopulate with today's date.  Also it would be nice if a calendar popped up similar to how it does in Admin:Scout:Contracts
The format of the date is confusing with the year, month, day when then it is displaying month, day, year (aka 10/23/15).  Also we would prefer if we didn't have to put in a specific hour/minute as that really doesn't matter.

Hour/minute is important if we want to have accurate metrics.
The calendar timepicker should pop up now.
@dormansteph a conflicting date error message will show up if you try to backdate before the start date for that stage, including the time.

Its not popping up and I still can't enter a back date or any date.  I'm
trying to update SPEC #7384
Kind Regards,
Stephanie M. Dorman
Procurement Coordinator
414 Grant Street
Room 502 City-County Building
Pittsburgh, PA 15219
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The City of Pittsburgh has launched a new opportunity site called BEACON!
Please visit  https://www.buildpgh.com/beacon/ and register for news about
upcoming opportunities.
On Fri, Oct 23, 2015 at 12:36 PM, Ben Smithgall<EMAIL_ADDRESS>wrote:

Hour/minute is important if we want to have accurate metrics.
The calendar timepicker should pop up now.
@dormansteph https://github.com/dormansteph a conflicting date error
message will show up if you try to backdate before the start date for that
stage, including the time.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/pittsburgh-purchasing-suite/issues/539#issuecomment-150627606
.

I'll look into it right now.

@dormansteph I've patched this problem and will let you know here when it is live -- it should hopefully resolve the problem. If it does, feel free to close the issue. If not, I'll continue working on it.

Ok, it should be live, please try again!

The calendar appears but it doesn't let you back date
Kind Regards,
Stephanie M. Dorman
Procurement Coordinator
414 Grant Street
Room 502 City-County Building
Pittsburgh, PA 15219
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The City of Pittsburgh has launched a new opportunity site called BEACON!
Please visit  https://www.buildpgh.com/beacon/ and register for news about
upcoming opportunities.
On Fri, Oct 23, 2015 at 1:17 PM, Ben Smithgall<EMAIL_ADDRESS>wrote:

Ok, it should be live, please try again!
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/pittsburgh-purchasing-suite/issues/539#issuecomment-150637310
.

You can't backdate a step with a completion date that is earlier than that start date for the step. It looks like you started that step today, so I'm not sure this is wrong.

I was trying to back date it for 09/03/2015 and it populated today's date
saying there is a discrepancy in the date.  It was sent to city review
09/03/2015 returned from city review 9/03/2015 and I want to make the
county review 9/03/2015 and county return 9/03/2015
Kind Regards,
Stephanie M. Dorman
Procurement Coordinator
414 Grant Street
Room 502 City-County Building
Pittsburgh, PA 15219
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The City of Pittsburgh has launched a new opportunity site called BEACON!
Please visit  https://www.buildpgh.com/beacon/ and register for news about
upcoming opportunities.
On Fri, Oct 23, 2015 at 1:43 PM, Ben Smithgall<EMAIL_ADDRESS>wrote:

You can't backdate a step with a completion date that is earlier than that
start date for the step. It looks like you started that step today, so I'm
not sure this is wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/pittsburgh-purchasing-suite/issues/539#issuecomment-150643552
.

Ok, I think this is a different need then -- you need to be able to restart a stage in the past. This is a new feature, so I'm going to close this issue and make a new one that captures that work.

Good morning,
I was trying to back date a work started (very first step) SPEC #7197 for november 10th and it would not allow

Hi @dormansteph !
I'm looking into this. When #599 gets merged and deployed, you will be able to do this more easily: check out the screencap below for more information


Add error-on-found when object found

Signed-off-by: Ricardo Pchevuzinske Katz<EMAIL_ADDRESS>Add the flag --error-on-found that exists Pug with an error when objects of a deprecated or deleted apis are found.
Fixes: #67

@grosser PTAL, the behavior here is IF there are  deprecated (not removed yet) or deleted (removed, breaking change) objects, and --error-on-found the program will exit with status code 1.
Sounds good?

by default: error on removed <-> because it blocks updates
with --error-on-deprecated: error when only deprecated <-> because you need to update to get into the deprecated state first 🤷

Great :)
I just don't think that making this a default behavior now would be good, as there might be some people using and already relying on it exiting with code 0 :)

Changed to --error-on-deprecated and --error-on-deleted, both defaults to false.

sounds safe, thx
On Tue, May 5, 2020 at 10:03 AM Ricardo Katz<EMAIL_ADDRESS>wrote:

Changed to --error-on-deprecated and --error-on-deleted, both defaults to
false.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rikatz/kubepug/pull/70#issuecomment-624180518, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAACYZ7ZJXOKLWMWKQIANVLRQBBEPANCNFSM4MZUWPEQ
.


Query blocked frequently

I'm using the presto master version, and one of my query blocked frequently on this version.
Query is
select count(distinct a) from b where c in('36','54','76','88');

The query looks like this and never finish.
Query 20150522_091853_00003_cmy9d, RUNNING, 14 nodes, 435 splits
8:40 [1.22B rows,   46GB] [2.34M rows/s, 90.6MB/s] [=========================================>] 96%

     STAGES   ROWS  ROWS/s  BYTES  BYTES/s  QUEUED    RUN   DONE
0.........R      0       0     0B       0B       0      1      0
  1.......R   819M   1.57M  12.6G    24.7M       0     13      0
    2.....R  1.22B   2.34M    46G    90.6M       0      1    420

The blocked node looks like this
20150522_091853_00003_cmy9d.2.7	<IP_ADDRESS>	BLOCKED	82.4M	0	3.11G	0B	0	1	27	0 / 13	0

I catched some http log in the blocked node:
2015-05-22T17:30:21.969+08:00	<IP_ADDRESS>	HEAD	/	null	null	200	0	0	0	10e04ef9-60e8-49c0-8b96-a40856ac66f9
2015-05-22T17:30:21.789+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7?summarize	null	null	200	0	3799	201	null
2015-05-22T17:30:21.000+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7/results/20150522_091853_00003_cmy9d.1.4/1041	null	null	204	0	0	1001	null
2015-05-22T17:30:21.803+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.1.9?summarize	null	null	200	0	1350	201	null
2015-05-22T17:30:21.093+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7/results/20150522_091853_00003_cmy9d.1.0/1045	null	null	204	0	0	1000	null
2015-05-22T17:30:21.093+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.1.9/results/20150522_091853_00003_cmy9d.0.0/0	null	null	204	0	0	1000	null
2015-05-22T17:30:21.990+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7?summarize	null	null	200	0	3799	201	null
2015-05-22T17:30:22.005+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.1.9?summarize	null	null	200	0	1350	200	null
2015-05-22T17:30:22.192+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7?summarize	null	null	200	0	3799	200	null
2015-05-22T17:30:22.206+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.1.9?summarize	null	null	200	0	1350	201	null
2015-05-22T17:30:21.429+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7/results/20150522_091853_00003_cmy9d.1.9/1038	null	null	204	0	0	1001	null
2015-05-22T17:30:21.462+08:00	<IP_ADDRESS>	GET	/v1/task/20150522_091853_00003_cmy9d.2.7/results/20150522_091853_00003_cmy9d.1.10/1043	null	null	204	0	0	1000	null

Any suggestions?

We also observed several query stalls (without using ClusterResourceManager). Need to find how to reproduce this issue.

I think the problem is caused by airlift.
When I revert presto to
SHA-1: 954ee41a9e231f576d211c280998e77f41d0ed97

* Upgrade to Airlift 0.110-SNAPSHOT

The problem still exists.
But when I revert to one commit before
SHA-1: be1e9ec024b7deac1ebb4b76218634460c486576

* Fix import

There is no problem anymore.
@dain @cberner

@yuananf can you reproduce this with the TPCH connector, or another public dataset? I don't think we're seeing this. Alternately, could you bisect the airlift commits to see which one in 0.110 is causing the problem?

This is due to a bug introduced by https://github.com/facebook/presto/commit/4b290a776aa8e8e4f81273125bb2f0f479370842 that causes operators that write to a partitioned output buffer to block when the buffer is full and never unblock due a missing notification.
@nileema is working on a fix now.

Thanks for the fix!


Alexander Aleksiyants works for ISP RAS

Thank you for contributing to stackforge/stackalytics!
stackforge/stackalytics uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


mapnik.js:26:15 procedure could not be found

Something very strange has happened. Yesterday everything was working fine, then this morning I installed Visual Studio 2015 Community RC and created a new project and did `npm install<EMAIL_ADDRESS>and everything installed without error -- However I am getting this error:
C:\Users\bh\Desktop\nodeMapnik>
C:\Users\bh\Desktop\nodeMapnik>node

var mapnik = require('mapnik');
Error: The specified procedure could not be found.
C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v14-win32-x6
4\mapnik.node
at Error (native)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\li
b\mapnik.js:26:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

I figured it has something to do with messing with the Visual C++ Redistributable Packages so I reinstalled them/repaired them. Still nothing. I reinstalled NodeJS v0.12.2 and tryed to install mapkik again and it installs without error but won't load the module.
I have  uninstalled VS2015 in hopes to fix it, but still not working. I am slowly (painfully) uninstalling all the packages VS2015 left behind one by one from control panel as a System Restore failed.
Before I go any further I want to confirm that it's possible the VS2015 did something, or a hint of what could be the issue here.

Here is the output from installing:
C:\Users\bh\Desktop\nodeMapnik>npm install<EMAIL_ADDRESS>\

<EMAIL_ADDRESS>install C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik
node-pre-gyp install --fallback-to-build

[mapnik] Success: "C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\bindin
g\node-v14-win32-x64\mapnik.node" is installed via remote
<EMAIL_ADDRESS>node_modules\mapnik
└──<EMAIL_ADDRESS>C:\Users\bh\Desktop\nodeMapnik>node

var mapnik = require('mapnik');
Error: The specified procedure could not be found.
C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v14-win32-x6
4\mapnik.node
at Error (native)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\li
b\mapnik.js:26:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

@BHare1985 two things:

for the time being, node-mapnik is still built with VS2014 CTP4, and not yet with VS2015 RC1, so you need the corresponding vcredist listed in the readme under install. Unfortunately an install of VS2015 RC1 removes the VS2014 CTP4 vcredist, thus rendering our provided binaries unusable.
node 0.12.2 is not yet supported. Please downgrade your node install to one of the versions listed here: https://github.com/mapnik/node-mapnik/blob/master/appveyor.yml#L9-L32

I'm working hard at the moment to get everything to VS2015 RC1 (including MSSQL support) and will post back when binaries are available.
If you are under pressure to get things working, you could try to build everything from scratch on your own machine, using https://github.com/mapbox/windows-builds
This (and some time) should get you everything you want:
git clone https://github.com/mapbox/windows-builds.git
cd windows-builds
settings.bat "FASTBUILD=0" "IGNOREFAILEDTESTS=1" "NODE_VERSION=0.12.2"
scripts\build

Yeah I figure that, but reinstalling VS2014 CTP4 Did not solve the issue. I also uninstalled all vcredist installed from 2015 and nothing yet. I downgraded to nodejs 0.11.13 and tried to install but it fails:
C:\Users\bh\Desktop\nodeMapnik>npm install mapnik
npm http GET https://registry.npmjs.org/mapnik
npm http 304 https://registry.npmjs.org/mapnik
npm http GET https://registry.npmjs.org/nan
npm http 304 https://registry.npmjs.org/nan

<EMAIL_ADDRESS>install C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik
node-pre-gyp install --fallback-to-build

node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.3.0/
node-v0.11.13-win32-x64.tar.gz
node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.3.0/
node-v0.11.13-win32-x64.tar.gz
node-pre-gyp http 403 status code downloading tarball https://mapbox-node-binary
.s3.amazonaws.com/mapnik/v3.3.0/node-v0.11.13-win32-x64.tar.gz (falling back to
source compile with node-gyp)
C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik>node "c:\Program Files\nodejs
\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js"
clean
C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik>node "c:\Program Files\nodejs
\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js"
configure --fallback-to-build --module=c:\Users\bh\Desktop\nodeMapnik\node_modu
les\mapnik\lib\binding\node-v0.11.13-win32-x64\mapnik.node --module_name=mapnik
--module_path=C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\nod
e-v0.11.13-win32-x64
C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik>node "c:\Program Files\nodejs
\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js"
build --fallback-to-build --module=c:\Users\bh\Desktop\nodeMapnik\node_modules
mapnik\lib\binding\node-v0.11.13-win32-x64\mapnik.node --module_name=mapnik --mo
dule_path=C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v0
.11.13-win32-x64
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.t
argets(44,5): error MSB8020: The builds tools for v140 (Platform Toolset = 'v14
0') cannot be found. To build using the v140 build tools, either click the Proj
ect menu or right-click the solution, and then select "Update VC++ Projects..."
. Install v140 to build using the v140 build tools.  System Windows_NT 6.1.7601
gyp ERR! command "node" "c:\Program Files\nodejs\node_modules\npm\node_modu
les\node-gyp\bin\node-gyp.js" "build" "--fallback-to-build" "--module=c:\Use
rs\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v0.11.13-w
in32-x64\mapnik.node" "--module_name=mapnik" "--module_path=C:\Users\bh\Desk
top\nodeMapnik\node_modules\mapnik\lib\binding\node-v0.11.13-win32-x64"
gyp ERR! cwd C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik
gyp ERR! node -v v0.11.13
gyp ERR! node-gyp -v v0.13.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd build --fallback-
to-build --module=c:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding
\node-v0.11.13-win32-x64\mapnik.node --module_name=mapnik --module_path=C:\Users
\bh\Desktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v0.11.13-win32-x64'
(1)
node-pre-gyp ERR! stack     at ChildProcess. (c:\Users\bh\Desktop\nod
eMapnik\node_modules\mapnik\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:110:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:992:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_proces
s.js:1059:5)
node-pre-gyp ERR! System Windows_NT 6.1.7601
node-pre-gyp ERR! command "node" "c:\Users\bh\Desktop\nodeMapnik\node_modul
es\mapnik\node_modules\node-pre-gyp\bin\node-pre-gyp" "install" "--fallback
-to-build"
node-pre-gyp ERR! cwd C:\Users\bh\Desktop\nodeMapnik\node_modules\mapnik
node-pre-gyp ERR! node -v v0.11.13
node-pre-gyp ERR! node-pre-gyp -v v0.6.7
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd build --fallback-to-build --module=c:\Users\bh\D
esktop\nodeMapnik\node_modules\mapnik\lib\binding\node-v0.11.13-win32-x64\mapnik
.node --module_name=mapnik --module_path=C:\Users\bh\Desktop\nodeMapnik\node_mod
ules\mapnik\lib\binding\node-v0.11.13-win32-x64' (1)
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the mapnik package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR!     npm owner ls mapnik
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "mapnik"
npm ERR! cwd C:\Users\bh\Desktop\nodeMapnik
npm ERR! node -v v0.11.13
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\bh\Desktop\nodeMapnik\npm-debug.log
npm ERR! not ok code 0
C:\Users\bh\Desktop\nodeMapnik>
I know the build tools issue is because I dont have Visual Studio 2014 but Visual Studio 2012, and I installed Visual Studio 2015  but uninstalled it.  I don't expect you to handle this mess I got myself into, I just wish I never installed VS2015 because now I can't use mapnik at all, but I wanted to let you know of the 403 of https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.3.0/node-v0.11.13-win32-x64.tar.gz

but I wanted to let you know of the 403 of https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.3.0/node-v0.11.13-win32-x64.tar.gz

We don't have binaries for 0.11.13, so the 403 is expected.
Please use one of the versions you see here:
https://github.com/mapnik/node-mapnik/blob/master/appveyor.yml#L9-L32

0.10.36
0.11.14
0.12.0

The readme says
By default, binaries are provided for:
64 bit OS X 10.9, 64 bit Linux (>= Ubuntu Trusty), and 64/32 bit Windows
Node v0.10.x and Node v0.11.13

@BHare1985 thanks for pointing that out. Will update the ReadMe.

I was able to fix it by removing new DLLs with modification dates April 2015 in the C:\Windows\System32
The list of what I removed is:
04/15/2015  10:50 PM           333,480 concrt140.dll
04/15/2015  10:50 PM           796,840 concrt140d.dll
04/15/2015  10:50 PM         5,609,632 mfc140.dll
04/15/2015  10:50 PM            47,272 mfc140chs.dll
04/15/2015  10:50 PM            47,272 mfc140cht.dll
04/15/2015  10:50 PM        10,864,800 mfc140d.dll
04/15/2015  10:50 PM            75,944 mfc140deu.dll
04/15/2015  10:50 PM            66,216 mfc140enu.dll
04/15/2015  10:50 PM            74,920 mfc140esn.dll
04/15/2015  10:50 PM            75,944 mfc140fra.dll
04/15/2015  10:50 PM            73,896 mfc140ita.dll
04/15/2015  10:50 PM            55,464 mfc140jpn.dll
04/15/2015  10:50 PM            54,440 mfc140kor.dll
04/15/2015  10:50 PM            71,848 mfc140rus.dll
04/15/2015  10:50 PM         5,637,792 mfc140u.dll
04/15/2015  10:50 PM        10,936,488 mfc140ud.dll
04/15/2015  10:50 PM           103,584 mfcm140.dll
04/15/2015  10:50 PM           133,792 mfcm140d.dll
04/15/2015  10:50 PM           103,584 mfcm140u.dll
04/15/2015  10:50 PM           132,264 mfcm140ud.dll
04/15/2015  10:50 PM           634,528 msvcp140.dll
04/15/2015  10:50 PM         1,001,128 msvcp140d.dll
04/15/2015  10:50 PM           551,080 vcamp140.dll
04/15/2015  10:50 PM         1,392,808 vcamp140d.dll
04/15/2015  10:50 PM           387,248 vccorlib140.dll
04/15/2015  10:50 PM         1,022,648 vccorlib140d.dll
04/15/2015  10:50 PM           203,424 vcomp140.dll
04/15/2015  10:50 PM           230,568 vcomp140d.dll
04/15/2015  10:50 PM            88,248 vcruntime140.dll
04/15/2015  10:50 PM           133,816 vcruntime140d.dll
04/23/2015  01:06 AM           264,360 VSPerf140.dll
Then I reinstalled Visual Studio 2014 CTP4 64bit from  https://mapbox.s3.amazonaws.com/windows-builds/visual-studio-runtimes/vcredist-VS2014-CTP4/vcredist_x64.exe
It seems one of the DLLs is left over from a VS2015 install, and doesnt get removed on an uninstall. Also, it's possible that VS2014-CTP4 doesn't replace the DLL with theirs because it's newer. None the less removing these DLLs and reinstall seems to have fixed it for me. I know it's tied to vcruntime140.dll because when trying to run nik2img.exe manually It would have entry point errors in vcruntime140.dll
This isn't really a node-mapnik issue, more of a Microsoft one but I figured id post my solution incase someone else installs VS2015 and runs into this issue.

I was able to fix it by removing new DLLs with modification dates April 2015 in the C:\Windows\System32
The list of what I removed is:
04/15/2015 10:50 PM 333,480 concrt140.dll
04/15/2015 10:50 PM 796,840 concrt140d.dll
04/15/2015 10:50 PM 5,609,632 mfc140.dll
04/15/2015 10:50 PM 47,272 mfc140chs.dll
04/15/2015 10:50 PM 47,272 mfc140cht.dll
04/15/2015 10:50 PM 10,864,800 mfc140d.dll
04/15/2015 10:50 PM 75,944 mfc140deu.dll
04/15/2015 10:50 PM 66,216 mfc140enu.dll
04/15/2015 10:50 PM 74,920 mfc140esn.dll
04/15/2015 10:50 PM 75,944 mfc140fra.dll
04/15/2015 10:50 PM 73,896 mfc140ita.dll
04/15/2015 10:50 PM 55,464 mfc140jpn.dll
04/15/2015 10:50 PM 54,440 mfc140kor.dll
04/15/2015 10:50 PM 71,848 mfc140rus.dll
04/15/2015 10:50 PM 5,637,792 mfc140u.dll
04/15/2015 10:50 PM 10,936,488 mfc140ud.dll
04/15/2015 10:50 PM 103,584 mfcm140.dll
04/15/2015 10:50 PM 133,792 mfcm140d.dll
04/15/2015 10:50 PM 103,584 mfcm140u.dll
04/15/2015 10:50 PM 132,264 mfcm140ud.dll
04/15/2015 10:50 PM 634,528 msvcp140.dll
04/15/2015 10:50 PM 1,001,128 msvcp140d.dll
04/15/2015 10:50 PM 551,080 vcamp140.dll
04/15/2015 10:50 PM 1,392,808 vcamp140d.dll
04/15/2015 10:50 PM 387,248 vccorlib140.dll
04/15/2015 10:50 PM 1,022,648 vccorlib140d.dll
04/15/2015 10:50 PM 203,424 vcomp140.dll
04/15/2015 10:50 PM 230,568 vcomp140d.dll
04/15/2015 10:50 PM 88,248 vcruntime140.dll
04/15/2015 10:50 PM 133,816 vcruntime140d.dll
04/23/2015 01:06 AM 264,360 VSPerf140.dll
Then I reinstalled Visual Studio 2014 CTP4 64bit from https://mapbox.s3.amazonaws.com/windows-builds/visual-studio-runtimes/vcredist-VS2014-CTP4/vcredist_x64.exe
It seems one of the DLLs is left over from a VS2015 install, and doesnt get removed on an uninstall. Also, it's possible that VS2014-CTP4 doesn't replace the DLL with theirs because it's newer. None the less removing these DLLs and reinstall seems to have fixed it for me. I know it's tied to vcruntime140.dll because when trying to run nik2img.exe manually It would have entry point errors in vcruntime140.dll
This isn't really a node-mapnik issue, more of a Microsoft one but I figured id post my solution incase someone else installs VS2015 and runs into this issue.

@BHare1985
Thanks for sharing. I just ran into the same problem.

Uninstalled vcredist VS2015 RC (was not listed in control panel anymore)
reinstalled vcredist VS2014 CTP4 (was listed in control panel)
but VS2015 RC file were still there

Manually deleting the files and reinstalling CTP4 solved it for me, too.