build failed

my build os Ubuntu20.0 ，all step i finished /build-all-native-libs.sh init can be executed successfully, but when it reaches the last step of ./build-all-native-libs.sh build, it error build libconv failed and ./configure not such file or directory found is displayed

my build os Ubuntu20.0 ，all step i finished /build-all-native-libs.sh init can be executed successfully, but when it reaches the last step of ./build-all-native-libs.sh build, it error build libconv failed and ./configure not such file or directory found is displayed

pls refer to #1  ,  so we could fix the issue, thanks

Host Operating System & Version：
Ubuntu 20
Kernel Version (Linux Only)：
4.14.13
Branch:
dev-baseon-latest-k0.8.8
Android Studio Version
4.2.1
NDK Version
r14b
Language
C
Section
build
Issue Description
<Describe your issue / question / feature request / etc..>
fully log is welcomed
steps to reproduce issue is welcomed
fudev-baseon-lat… ll sequence of commands used is welcomed

sanity check in a stand-alone dev-envs  successfully according to
https://github.com/zhouwg/kantv/blob/kantv/README.md


testing OpenSSL old ver.

Hi , I've been interested in this work. To extend it I tried to use it to fuzz older version of OpenSSL, like openssl 1.1.0, 1.0.1.
But I found that the coverage begins with 20+ and after one-day fuzzing it only came to 40+. While the coverage of fuzzing 3.0.0 and 1.1.1 begins with 4000+.
I tried to modify compilation options and other approaches but I couldn't fix this trouble. So, I'm writing this issue to see if you've countered this kind of problem and know what's wrong with it.

It is likely because the old version of OpenSSL is not correctly executed, not only the compilation options.
Perhaps you can use gdb to step into the execution and check where the process exits.


tests: new test case asserting resty.core is compatible with the current version of this module.

This is based on top of https://github.com/openresty/stream-lua-nginx-module/pull/126, which should be merged first, and this should be rebased afterwards.
This will give us visibility in case this scenario happens again. Currently, it is not explicit why the balancer tests are failing. This test makes it explicit to the reviewer.
If this test is judged acceptable, I will port it to the ngx_lua module as well. Suggestions for other similar tests on resty.core <-> ngx_[stream]_lua compatibility are very much welcome. I was considering a plain resty.core require, which ngx_lua's 154-semaphore.t does, but it seems like https://github.com/openresty/stream-lua-nginx-module/commit/394591783006d5edbd891558895708e4b9c622b4 did not port this test suite to this module.
Curious to hear your thoughts here @dndx @agentzh.

Since we are about to load resty.core by default from ngx_lua (and ngx_stream_lua), I am reconsidering merging this, and wait instead for a proper test suite around loading resty.core within this module.


Configure monitoring service for RUCIO in the new cluster

Data from the K8s cluster is already published to the new eosc-future producer. Rucio events from the new instance should be published to https://monit-grafana.cern.ch dashb and then picked up by the same dashboard from there.
Rucio monitoring docs: https://rucio.cern.ch/documentation/monitoring

Minimal monitoring display of the VRE infra is currently working: https://monit-grafana.cern.ch/d/PJ65OqBVz/vre-rucio-events?orgId=51
Dashboards could be improved, however details can be done/discussed/developed in different tickets.


Ramda vs Immutable

Mostly just a comment. We've switched in our este based project from ImmutableJS to Ramda. We've had issue both from a performance perspective and usage perspective with a lot of going back and forth between POJO and Immutable. We've found that using Ramda, which provides pretty much the same functionality as ImmutableJS, solves most of these issues.
Map.setIn => R.assocPath
Map.getIn => R.path
Map.deleteIn => R.dissocPath

I know Ramda. It's brilliant.  It's just fancy Haskell like function composition, but without structure sharing.

Actually !== works just fine. Not sure why you would think it doesn't work?

As for "going back and forth between POJO and Immutable", it's really a problem? I think revive and toJS is fine, feel free to correct me. Can you describe your use cases in more details please?

We have a more of a socket based real-time app with a lot of data going back and forth. So basically need to constantly got back and forth between POJO and Immutable and it totally trashes the GC.

Another reason we switched is that we prefer to have our React components as regular dumb components without any "magic" from Immutable. Spread operators work, PropTypes work and also easier for new members to the project to get started with the React component development.

@ronag I think that all these problems can be solved by using Records and reselect (or something similar). I do not use any methods from Immutable in Components and still enjoy the power of the library in the reducers and selectors. Plus there is the performance benefit (pure everything).

The only problem with Immutable is integration with third-party components. Records make our life easier, but Lists still need to be converted to plain arrays and back.

@Xeed: Unfortunately, no they can't. Still need to convert back and forth and the usability still isn't there.
You have the same pure everything performance benefit with e.g. Ramda.
The only advantage Immutable have over e.g. Ramda (as far as I know) is that operations on the Immutable structures themselves is more efficient.

@ronag Destructuring works just fine with Records.
Reselect allows you to pick and convert the objects before they enter the component.
I speak from our experience, we have about 20 developers working with Este based stacks and we do not feel any pain working with Immutable, in fact it quite the opposite.

Also, we use react-immutable-proptypes and it helps a lot, you can even specify shapes for Maps, values of Lists etc.

This thread has been really helpful. I would love to hear more about different modules you have found useful with este. Perhaps thread for each competing set of modules? Or perhaps this is not for github?

@XeeD: Hm, yes, you are correct about destructing. However, we still need to do <Foo {...foo.toObject}/>

Reselect allows you to pick and convert the objects before they enter the component.

Yes, we did this as well.

I speak from our experience, we have about 20 developers working with Este based stacks and we do not feel any pain working with Immutable, in fact it quite the opposite.

Well, we did start out with Immutable and yes we used react-immutable-proptypes. We couldn't get it to work technically due to performance issues. After switching to Ramda we noticed that we could remove A LOT of workaround stuff (immutable-proptypes, toJS, fromJS etc...). Not saying that Immutable is bad, just that we found Ramda much simpler, and performant for our specific application.

@ronag Thanks for sharing! Our apps are not very large in terms of data that they need to show, there are just lots of screens. Maybe I would speak differently if we used it for different kind of app.
Anyway, I will take a look into Ramda, thanks for recommending it!

@rkoberg :+1: I love to hear stories from other people using similar stack as we do, it helps broadens the knowledge. It is always good to know the alternatives and what works for other people.
What do you think @steida, maybe a few Wiki pages might come out of these discussions?

As I said, Ramda is beautiful, but it operates on native Arrays and Objects without structural sharing. It's hard to imagine how it can leverage shouldComponentUpdate. Also, using native objects it's easy to mutate them accidentally, and sooner or later some developer will do that.
Regarding to performance issues you mentioned, I can only imagine you are using really huge datasets with dozens thousands deeply nested values. I would rather optimize amount of transported data then switching entirely to Ramda. Btw, I am not using immutable-proptypes, simple check to "object is required" is good enough for me. Ramda also lacks lazy Seq, another performance boosts from Immutable.js
Still, thank you for your comment. Nothing is sure in our industry and we all have to continuously rethink our tools.

As for wiki pages, we already have some, check it and feel free to update or reorganize :-)

Btw, as far as I know, there is internal debate in Facebook whether React should be immutable by default, so let's wait. But, if shouldComponentUpdate somehow magically works, then we can reconsider it. We can freeze current app state frame anyway. Closing for now, but feel free to reopen or discuss.

It's hard to imagine how it can leverage shouldComponentUpdate.

Why is this? I seem to be missing something since both of you seem to point this out.
Consider:
const data1 = {
  A: {
     foo: {
       title: "FOO"
     },
     bar: {
       title: "BAR"
     }
  }
  B: {
     bar: {
       title: "BAR"
     }
  }
}
const data2 = R.assocPath(['A', 'foo', 'title'], 'FOOBAR', data1)
assert(data2.B === data1.B)
asset(data2.A.bar === data1.A.bar)

assocPath Object - Makes a shallow clone of an object, setting or overriding the nodes required to create the given path, and placing the specific value at the tail end of that path. Note that this copies and flattens prototype properties onto the new object as well. All non-primitive properties are copied by reference.
As far I understand that, Ramda makes plain shallow clones, while immutable.js uses smarter data structures - https://en.wikipedia.org/wiki/Persistent_data_structure, Therefore immutable.js can provide more advanced manipulations like lazy Seq.
I think it's trade-off we need to decide. Ramda or immutable.js? I see you already concluded:

The only advantage Immutable have over e.g. Ramda (as far as I can see) is that operations on the
Immutable structures themselves are more efficient. However, at least in our case, that efficiency
improvement is not worth the overhead."

I would say that in general Immutable will have better performance in most applications. However, at the same time I would say that in my opinion Ramda brings more simplicity and easier use. Also, there is the saying "premature optimisation is the root of all evil".

I see one compelling reason for Ramda - no casting. Immutable Record is nice and all, but casting effectively makes live app state update from localStorage impossible. The revive is good for initial state only.  So, comparing various pros and cons, Ramda with dev freeze seems to be more frictionless and practical.

I think Ramda and immutable.js should be merged somehow. Native [] and {} should be allowed everywhere, with freeze for dev ofc. Ramda should use immutable persistent data structures inside for cheap manipulations. Etc.

Depends what you mean by cheap and whether it matters at all or not. Having written few GA recently with Immutable.js, I've found falling back to native data structures & using some immutable helpers to be a couple of times faster. (No casting was involved at all, just concatenation and pushes on arrays)

Since I saw structure sharing... https://github.com/dustingetz/react-cursor ?

We use Object.freeze in development mode.

One problem with just using Object.freeze on the state atom is that it's only a shallow freeze- child properties are freely mutable.

Also see this https://github.com/rtfeldman/seamless-immutable which is said to work with Ramda just fine and looks like its persistent as well:

Looking at the code, it seems like seamless-immutable recursively calls Object.freeze on all object properties, which is quite nice, but there's no structural sharing going on under the hood. I haven't tried this, but it seems like using Ramda to assoc a property on a seamless-immutable object would result in a mutable object with every property frozen except the assoced one:
// Ramda's assoc implementation:

module.exports = _curry3(function assoc(prop, val, obj) {
  var result = {};
  for (var p in obj) {
    result[p] = obj[p];
  }
  result[prop] = val;
  return result;
});

I think Ramda and immutable.js should be merged somehow.

I'm all for this, but it seems really difficult. If we want to keep Ramda's native JS API, you'd need to regenerate the HAMTs/ persistent vectors every call, which means you wouldn't even be getting the performance benefits those data structures provide. I guess it's possible the native JS object could be used as a key into a map of generated persistent data structures, but that sounds like you'd be fighting the GC pretty hard. Then again, who knows, it might work for a lot of use cases.
FWIW, I use Ramda + a shallow Object.freeze, and I've never been in a situation where the lack of structural sharing has been a bottleneck, and I really enjoy the Haskellish feel Ramda provides. Of course, if the lack of structural sharing does become an issue, switching to immutable-js would be an absolute nightmare, so there's that to factor in too.

@joashc: Great comment, thank you!

So, after long rethinkning, I decided Este should stay with immutable.js. Reasons:

performance
stability
Records are invaluable as they enforce known keys

Ramda is beautiful, but the Elm is that next level we need for haskellish (not only) feel.

Does anyone want to share its opinion? I can imagine Ramda can be better for beginners because no reviving stuff.

We are using transit (https://github.com/glenjamin/transit-immutable-js) to serialize app state, therefore there's no reviving. The only drawback is that you have to name&register all records.

I won't add anything to the technical debate because it's been well discussed above by people way smarter than me.
I agree that it would probably be easier to start with.
Ramda is much more than an immutable library though. Bringing it to the party has the nice side effect (haha) to help us write functional stuff OOTB.

The article Lenses with Immutable.js shows how Ramda lenses can abstract over any get/set interface, like the ones provided by the various immutable libraries. Lenses compose nicely, so they're great for writing modular object updating code.
So we get the ability to access and update object properties with native Ramda lenses- which are nicer than R.prop and  R.assoc anyway- and still get the structural sharing of Immutable.js data structures. If that was the whole story, I'd say this was a clear win for integrating Ramda with Immutable.js. But a huge part of Ramda involves list operations, which the linked article proposes to address by defining an isomorphism over Immutable.js and native lists. Here, I'm less convinced; it only saves us from writing one conversion step, and we lose performance. I don't think the performance is actually a huge issue, but  ultimately I think transducers are going to be the "correct" solution, though I'm unsure how far Immutable.js transducers have come.
I definitely agree with @cbioley that Ramda and Immutable.js address very different (though overlapping) areas of the problem space.
Anyway, I'm not on any particular side of the fence on this one; it really depends on the project priorities and the userbase!

@joashc Nice reply, full of terms I'm just getting used to see (and like). Thank you.
I'm off to read Brian's article then :)

I have to say I had a problem with conversion busywork especially when a large part of apps state is persisted in storage, which is must to support offline in React Native apps, but since I simplified state reviving a lot https://github.com/este/este/blob/master/src/common/configureReducer.js#L28, I think we don't need Ramda so badly. Also, @joashc made a good point with "having currying-by-default, point-free style, lenses, and possibly transducers, all dropped on your plate at once." Closing it for now :-)

Two most serious arguments in favor of immutablejs are:
a) structure share and resulting performance benefits
b) safety against unwanted mutations
So let's look at both of these.
Structure share and performance
actually, this is far more subtle issue than one might think. (As was already pointed out in this thread) deep changes (ramda style) also reuse as much as possible from the original object! The only difference is, that Ramda's structure sharing can share only whole Lists / Maps. With Immutable.js you can share also parts of individual maps. Although this is cool, I have a challenge for you:
Design an (say react + redux) example, where this plays a role, i.e. where immutablejs appstate has performance advantage over POJO using ramda-style deep mutations.
I don't want anyone to spend their precious time with coding, benchmarking, just provide a quick sketch of an example, where immutablejs-style structure share performs significantly better over ramda-style structure share. Surprisingly, this is hard!
Safety against unwanted mutations
Two alternatives, how you can achieve this:

https://github.com/rtfeldman/seamless-immutable
in development mode, make a deep copy and copy-by-reference of the whole appstate. After dispatch, check that dispatch did not mutate anything:

oldState = state;
oldStateDeep = state;
dispatch(action);
if (!deepEqual(oldState, oldStateDeep) {
  throw new Error(`Don't you dare to mutate appstate in dispatch! You mutated: <some useful info here>`)
}

of course, the second approach prevents only mutations in appstate, you are free to mutate the other objects. This, however, will still buy you 90+% of the security you might want!
Some background: we (as a company) used immutablejs on several projects, we created https://github.com/vacuumlabs/babel-plugin-extensible-destructuring to help us use immutablejs in a more friendly way. Now on newer projects we stop using immutablejs at all. We are happy with the change.
Not that immutablejs was a bad library (for certain tasks, it rocks), but using it for the appstate brings a lot of constant mental overhead: What is this thing I have? Is it mutable / immutable? How I should access / mutate it? It's hard to escape this burden, since the whole js ecosystem is built upon mutable primitives.

btw, feel free to close the issue again, I'm not saying this is so serious.

Hmm, immutablejs is just fine for me well. Everything is Record (no need for destructing), revive pattern works well, I don't have any mental overhead with it. Are you using Ramda instead?

Plain js structures and ES7 operators with redux

We don't actually use Ramda, because:
a) I find out about it too late, only because of this thread
b) it lacks features such as immutable.updateIn or immutable.mergeIn
so we wrote a small custom lib that provides the basic 'deep operations' on mutable data (doing as much structure sharing as possible). It is nothing fancy, it's about 200 LoC.
If anyone likes immutablejs API, I have no problem with that. I just wanted to stress that the performance argument is not there at all (at least, I'm not aware of it).

There is an issue in Este where someone described how he replaced Immutable.js with Ramda. Yes, there is updateIn and mergeIn. I highly recommend reading Why Ramda intro. It's good introduction into Haskell in JavaScript :-)

So we wrote a small

Nooooo :-) Do not write already written code. Ramda is brilliant, use it :-)

Thanks for the info, I'll check it out.

It will blow your mind. Especially this http://fr.umio.us/why-ramda/

@tomaskulich Some people from BlueBerry ( entirely Este company :-P ) are using https://github.com/glenjamin/transit-immutable-js so they don't have to revive anything. Looks promising.

It's certainly nice idea.
As for us, we managed to get all the immutable goodness even with mutable data structures and it work really well for us.
From the long-term perspective, I'd like to start using something more powerful than just JSON (by which I mean nested structure of maps and lists) for the app state. Think something as https://github.com/tonsky/datascript (but maybe with a more user-friendly API). Also, I'd like to give my appstate a schema.

Immutable Records enable schema.

Yeah, but if I'm to lose the 'standardness' of plain js objects and lists, I want back more than just schema (and the speed is not being the benefit). I'm not sure if you are familiar with Datascript, but check out, how beautifully it can work with references between entities!

@tomaskulich, @ronag
Este is finally without reviving and still with the beautiful immutable.js API. I am pretty sure this is the best of all worlds. It's super fast, convenient, safe, and with strict Record schema.
As for Datascript, it's too much for the Este - the best of the mainstream.
https://github.com/este/este/commit/0ef0a762357e752a21ad0b47e472c8d765d090b5

@ronag You were correct. I am removing immutable.js right now.

@steida could you elaborate more as to what you mean and why?

Immutable.js does not play well with Flow in my experience. Maybe someone can prove me wrong, but most notably, you can't type the shape of a Map (in an object-literal-like notation), and the fromJS() method is typed as any. I feel like Flow loses a lot of intelligence about your application if your data lives underneath Immutable.js primitives.

@joncursi Correct. That's one of several reasons why I removed immutable.js from Este.

@steida I just inspected este's package.json and saw Ramda. Any issues between flow and ramda that you've experienced, or has it been smooth sailing? Have you evaluated seamless immutable by chance?

To add to the conversation, another pain I've had with immutable.js is maintaing mutable and immutable versions of my prop shapes and flow types. I've tried my best to use Immutable throughout, but it's just not possible especially if your app relies a lot on 3rd party libs. Here is a props example that I must pick on a per-component basis:
const coinsShape: Function = PropTypes.arrayOf(
  PropTypes.string.isRequired,
);

const coinsShapeImmutable: Function = ImmutablePropTypes.listOf(
  PropTypes.string.isRequired,
);

And same for flow types:
export type NavigatorLeftActionFlowType = {
  icon: IconFlowType,
  onPress: Function,
  text: string,
};

export type NavigatorLeftActionImmutableFlowType = Record<{
  icon: Record<IconFlowType>,
  onPress: Function,
  text: string,
}>;

It's getting out of control. Can someone enlighten me if Ramda or seamless-immutable bypass these issues? From what I understand about Ramda, data is still stored in vanilla JS primitives, so I am hopeful that only one shape or one flow type would ever be needed to describe the shape of any model?

Read Este source code. We don't need Record types with algebraic types. We don't need immutable object, we need immutable operations. Can be enforced by FP eslint.


Bring back the blinking nodes, please!

Hi there and thank you very much for your work on Mappy!
Mappy is my all-time favorite minimap addon even though its best feature has been cropped years ago:  -The blinking (flashing) mining/herb/fishing nodes. That was the key feature that made Mappy so unique among the other tons of minimap addons a decade ago. I'm not sure if you can remember this feature but I remember Mundocani used 2 node icons of the same pin texture (1 colored to yellow and 1 colored to blue) and used them continuously switching several times in a second to make a blinking effect to display flashing nodes on the minimap. This draws attention of a human eye a lot more farther of the screen and therefore we didn't miss any nodes around. The addon was once a gatherers' dream.
The tickable option is called: ### "Flash gathering Nodes" in the options. It was a brilliant idea indeed. However somewhere in the last decade the actual maintainer of Mappy have cut this feature off. :(
Anyhow, Mappy still looks good and stylish but it would be a miracle if you could restore the original blinking nodes to it. Would you please check if the feature could return in 10.x ?
Either way, thank you for your hard work!

I've actually fixed this feature already!
I've fixed a few features that were broken for a few years, including the coords, profile selection (dropdown menus were broken for a while) and gathering nodes blinking and/or being larger.
It works on my end in the prepatch. Since DF, WoW is using separate graphics for fish, herbs and mining nodes, so I've reused these. I can add an option to use pre-DF graphics (the same dot for all node types), if this is what you want. But the feature itself is already fixed and working, it just uses new art now ^^

This is how they look now:
Normal:

Blinking normal:

Large:

Blinking large:

And a gif example in-game:

Btw, I've uploaded a release. This will land on CurseForge, hopefully soon, in a new project "Mappy Continued". Please let me know what you think about this release.

Wow! Just wow!
Pretty nice work, I still can't believe you brought it back! <3
Still can't find it on CF so I just tried it from here and it looks pretty good already!
One thing I noticed during the test, the gathering nodes get appeared only when the character gets very close to them. The range is way too short. Compared to rare mob icons or battle-pet icons the gathering nodes are visible only from halfway of them or even less. I don't know if there's anything you can do about it or it's stock wow but it's somewhat annoying especially when flying over a field and have to turn back continuously because the nodes just appear when you fly over it. First I thought it's a latency issue but if it was it had to be the same with other minimap icons too but they're good.
The special gathering icons aren't an issue for me, but they're surely way too small. The option to enlarge nodes could enlarge them a bit more.
Once again I can't thank you enough for reviving this masterpiece. God bless you m8!

I've uploaded the project to CF, but it's still under review. Their next work day is on Sunday (afair) so the earliest the project will arrive there is next week.
Heh, I couldn't abandon this addon, it's too good! Thankfully I've started learning Lua and addon writing a few weeks ago, when creating my own addon DragonSpeedway, so I had enough knowledge to fix this one by the time prepatch came. And the original code is written very cleanly, which really helped. I'm a Python dev by trade, which kind of contributes to my hate of unclean code. Mappy was written very cleanly and neatly, Mundocani did a great job.
I've checked this just now with the stock minimap and it's definitely Blizzard's fault. The gathering node range must have gotten shorter in prepatch.
I've checked with fishing nodes and I see that I need to get much closer for the actual ingame model of the node to spawn. When it spawns, the icon appears on the minimap instantly. When I move away, the range is longer. The ingame node model unloads at a greater range.
So this seems like an issue with model loading ingame. Nodes are requiring a much shorter range from player to actually render. Weird issue, I don't remember it happening on Beta.
Hmm, I'm not sure if I can even enlarge them more. The addon works by overwriting the stock texture map for those icons. It doesn't overwrite individual icons, but the whole map that contains all of them at once. I've tried to make them as big as the empty space around them, but it's Blizzard that's shrinking them so harshly when they're actually placed on the minimap.
I think a dot would help just because it has less negative space in that 32x32 pixel square that holds the icon texture. I might add this option anyway to help with visibility.

-Ok, I'll keep looking forward to the CF project.
-So the range thing is set, we have to live with it or they may revert it in the upcoming DF retail.
-Don't worry about enlarging them even more then, maybe the original fat dot node texture will do the job anyway. I hope you can make that to flashing too.
-I've started learning Lua and addon writing a few weeks ago_ - is it hard to understand? In early 2000s I learned a language to create addons (mods) for the original Medal of Honor PC game and it went fine. I tried it with WoW Lua several times already but I couldn't get used to it, still. Can you recommend a good web guide for beginners please?
Thank you very much!

I will make these dots flashing, don't worry.
It's a bit hard to answer if it was hard, tbf. Depends on your experiences. I'm working as a software dev, I write in Python with smaller dabbles into Bash scripting, I also wrote a few Ansible playbooks. My job focuses on cloud networking code, precisely the Neutron component of Openstack. I constantly get tasks where I need to learn an entire new thing with my only documentation being the code itself. Makes you learn how to quickly jump into a new thing and soak as much knowledge as you can.
Lua is actually so stupidly simple that it's harder than Python just because it's so limited. A lot of things I took for granted in Python have to be reimplemented into Lua manually.
One example from Mappy, actually: I had a need to check if a global objects belong to a list of objects. I basically knew that I want to do a line of code only if the object in question was X, Y or Z. In Python, I'd just do a set of X, Y, Z and do a "if object in set" and call it a day. In Lua I had to hack it a bit - I implemented a function that checks if a table has a provided key. Then I had to put X, Y, Z into a pseudo-dict, where the key is the X, Y or Z and the value is true. The function then takes this table and the object and checks if the object is a key in that table. If not, return nil (none). A lot of bother for something that's just built into the language in Python, lmao.
Lua is easy and simple. It's just so simple that it forces you to do weird stuff sometimes that higher level languages would do by themselves.
I recommend going on wowpedia and searching for an article "how to create an addon in 15 minutes". There's also a page that lists all API changes in 10.0.0 patch. And somewhere on wowpedia is a linked repository that holds all UI code for Blizzard stock UI. It's useful for referencing how certain functions or XML frames are built.
Ingame tools are also plenty - /fstack shows you info about the frame you're mousing over and even a path and line of the file that contains its implementation. /dump allows you to dump certain global variables into the chat window. /api is amazing, it's actually an addon made by Blizzard, it holds the current documentation of all globals, events, functions and whatnot. Amazing for searching if something is even possible to use by addons.
I'd suggest going through the "15 minutes" article first, branching out into linked pages that explain in more detail, then picking a subject you want to make an addon about and slowly going through it, searching for info on wowpedia and using ingame tools to check stuff.
Also, looking at other addon's code is a godsend. This is the best source of knowledge by far.
I also remember a series of YT videos someone made about how to make an addon from scratch. It's AMAZING and also fairly recent. I cannot recall the channel name tho, but should be easy to search, that series is looong.

I've just remembered this website too:
https://wow.tools/

I've added old dot icons for nodes. I will upload a new release in a moment.

Thank you for all the information, I'll definitely give it another try on my upcoming holiday.
Also huge thanks for the work on Mappy too!

Have fun! Programming is awesome, I bet you'll have lots of fun with it! The rush you get when you create something from nothing is just great.
I'll close this issue for now. Feel free to HMU via CurseForge or here if you have any more questions!
Also, the latest release 4.2.1 fixes a nasty bug with coords in instanced content, so I recommend to update.

@Voxxel
It's on CurseForge now - https://www.curseforge.com/wow/addons/mappy-continued

Nice, thank you!

@Voxxel
Another news, this time about the gathering nodes requiring a shorter range to pop in. Apparently there's an issue with asset pop in in the game atm, introduced with the prepatch. This seems connected to ppl experiencing weird stuttering in-game (myself included). That would align with the thing I've noticed before about in-game node models. Just letting you know it's most likely connected, which means it's probably just a bug and should be fixed after Blizz discovers what's going on. I hope. It's weird to experience stuttering on a 3080 and Ryzen 9 lmao
This also happens on beta, btw. I've just checked.


Less an issue - more banging a hammer at 1.5B

Hi everyone, and of course Kijai!
1.5B is out, thanks for the update to the wrapper. Took a spell to fix the nodes man..so many changes but that is alright!
Thank you very much for the hard work.
In messing around I see we can reduce the FPS in saving from 16 down to 12/10ish and it does in fact extend the video length by a second or two but there has to be a better way. Using Img2Vid model, 1.5B, gives me a 3 sec hard limit on the best settings.
Anyone figure out a way to preserve the 16fps and get those coveted 10 second long videos??
Also the quality output of the 1.5B is vastly superior to anything so far - so good!
https://github.com/user-attachments/assets/75562e5f-7265-4dfb-8626-2cc6ed444bcb
https://github.com/user-attachments/assets/2b0872a3-9d26-4e07-ae1c-63ef005345b4

This is exact settings as above just with FPS in the saving node set to 12. (gives us 4sec video)
https://github.com/user-attachments/assets/8a754bde-ae64-48b9-b686-b30c17a096f1

And last one to not spam up the thread too much -> this is using FPS 8 in the save box. This gives us 6 sec it seems.
https://github.com/user-attachments/assets/c37a3876-66c5-485c-b112-83d301a41e82

I'll be experimenting with a few things but please if anyone else has a tweak for the I2V to get those 10 sec vids, please post up.
Also if anyone has a Text2Vid json for the 1.5 could you post it up please?? I have not written my node update one yet I'll make it later if someone has would save some time. Thanks!

The FPS in the video combine is literally just the frame rate the video is played at, they have claimed the model could do 161 frames which would be 10 seconds at 16fps. I find that 81 frames is more reasonable target, which when played at 8fps would be 10 seconds long as well.

Let it take forever it is doable. I have done 185 with 4090. Offload everything.

52min for rubbish. Some tweaks needed eh! lol
https://github.com/user-attachments/assets/2ae9fc84-f32d-4aa3-95eb-54b06c3c8968

What were your prompts?

The image is from my own custom SDXL unpublished model fyi, but I was messing around with this only -> "one classic proportion burger, intricate, elegant, highly detailed, glossy haze, concept art, soft, sharp focus, bar background"
I wanted to know more the length control before going nuts. I am now running a 81 num_frame for fun to see and will post up but with what you all replied this thread can pretty much be closed after as info.  We nailed this down to what is what here.
And yes, zazoum the prompt isn't complex enough to really work the model I'm aware. I'll move probably to this prompt next
"Create a cinematic video showcasing a classic proportion burger. Begin with a close-up of glossy, fresh ingredients (lettuce, tomato, onion, cheese) falling gracefully in slow motion onto the patty, layered on a toasted bun. Show the burger being assembled with intricate, elegant detail, highlighting the textures and glossy surfaces. Add a soft haze in the background, transitioning to a sharp focus as the final burger is revealed. The setting is a warmly lit, sophisticated bar with soft ambient light, and gentle reflections dance across the counter. End with a 360-degree slow rotation of the completed burger, emphasizing its elegant design and intricate craftsmanship."
All the video models require dictionary level prompting to really wry everything from them - I learned this while doing my ice rally car videos phew...if there isn't enough description the model just fills in whatever hehe.

Flux needs different prompting than sd1.5. Same here.
There are prompt generators for cog.
Didn't read your whole post.

why reply if you aren't going to read everything nor post a link to the cog generators?
Pretty rude/lame, I'll just ignore you now.

Google is out there!

Thread closed info is above for anyone to ref.
Num_frames is key.
Thanks again Kijai!


fix broken path

#4 accidentally introduced the path as lf-edge/eve/api/go instead of lf-edge/eve-api/go in the new and modified files. This fixes it.

Thanks @uncleDecart ; if only I could merge it in with that approval 😄

at least I tried @deitch :D


Update README.md

remove duplicate MIT License badge (and seem like it doesn't link to any page)

Thanks!

Hello @thepriefy,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Added ability to use your own directives usage

Hi,
Description
This PR goal is to bring ability to use so custom directives, as mentioned in issue https://github.com/graph-gophers/graphql-go/issues/151.
I would be interested in having feedbacks, mainly on the way that I am currently re-using the internal/common package exported to be used publicly in pkg/common: maybe I could just copy objects I need (but I need a lot of these defined in package ;-)).
Example usage
Assuming that I have the following schema:
directive @customDirective(
	customAttribute: String!
) on FIELD_DEFINITION

schema {
	query: Query
}

type Query {
	myTestQuery: String! @customDirective(customAttribute: hi)
}

I can use the directive in my resolver by adding a new argument:
func (r *customDirectiveResolver) MyTestQuery(ctx context.Context, directives common.DirectiveList) string {
	customDirective := directives.Get("customDirective")
	customAttribute, _ := customDirective.Args.Get("customAttribute")

	return fmt.Sprintf(
		"Hello custom directive '%s' with attribute value '%s'!",
		customDirective.Name.Name,
		customAttribute.String(),
	)
}

Thank you!

@pavelnikolov,
Thanks for your quick & clear reply!

You're right, actually it only supports FIELD_DEFINITION, maybe we could add support for OBJECT and FRAGMENT too in a second time? I've tried to take a look and I don't think I am too smart with reflection to do this actually, or maybe you can point me to the right direction?

Thanks for pointing me to this PR #437, this is exactly what I need so I will wait for it to be merged and will use it afterwards.

I understand your arguments and what you want but I find it pity to loose the typing of the arguments because we will retrieve a common.Request object so users will have to do casting like this in order to retrieve their arguments and we will not benefit of schema validation anymore?

type PaginationArg struct {
    Offset int32
}

func (r *Resolver) Something(ctx context.Context, req *graphql.Request) (*SomethingResponse, error) {
    myDirective := req.Directives.Get("myCustomDirective") // No problem here, directives are graphql-go types

    myPaginationArg, ok := req.Args.Pagination.(*PaginationArg)
    if ok {
        offset := myPaginationArg.Offset
    }
}

Anyway, maybe it's acceptable, I will try to implement this in the coming days and will keep you informed.

@pavelnikolov After thinking about your suggestions, a colleague @iotafr 👋 point me to what Apollo is doing and I think this is a good way: https://www.apollographql.com/docs/apollo-server/schema/creating-directives/
I've updated the PR to use this kind of Visitor pattern. I think it takes the following advantages:

We don't touch to the current resolvers objects,
We can easily create a single directive visitor to act on multiple fields,
We could easily support objects & fragments directives (I will try to take a look at this now that I have something working).

Directive visitor must implement the following interface and can act before the resolver to be called or after:
type DirectiveVisitor interface {
	Before(directive *Directive, input interface{}) error
	After(directive *Directive, output interface{}) (interface{}, error)
}

What do you think? I've kept the old previous logic on a branch in case you don't like this one ;)

@eko I really like the visitor pattern!

@eko  #437 has been merged

@pavelnikolov Great thanks! I've just updated the PR with types exported by #437.
I've tried to take a look at how I can retrieve the object directives but without success actually, I've to spend much time to understand the internal workflow.

There are some conflicts. @eko can I help you to get this working?

Hi @pavelnikolov,
Sorry for the delay, I was off for a couple of days.
I just rebased the pull request in case you want to merge the first part. Unfortunately, I will not have any much time to work on other directives implementations.
Thank you

@eko thank you very much for rebasing this code. I left one comment re where to pass the directive visitors. I like this pattern but it will require some more work.
Regarding your comment about "on other directives implementations" what do you mean with "other"? Do you mean object, interface, union and argument directives (anything other than fields)?

Hello @pavelnikolov,
Thank you, you're right, this is so much better to have them at the schema parse section, I just updated the PR in order to add a new DirectiveVisitors() Schema option to pass them.
Concerning the other directives implementations: yes, this implementation works with FIELD_DEFINITION type. That's a first step but other types have to also be implemented later.

@eko OK, this is much better now that the directive visitors are not passed with Exec. I was thinking about adding DirectiveVisitors() method to the root resolver, but maybe your idea is better to be passed as a schema option. I like it.

I also found it was interesting to have them declared as schema options but let me know if you prefer to have them on root resolver.

Merci beaucoup, @eko! I was thinking the same thing. Then I thought to myself "What if there is a resolver field named 'DirectiveVisotrs'". I know that this is highly unlikely. The notion of Schema options is that they are optional and we can turn the options on and off. However, in the case of directives, is it possible that they are included in the schema, but not included in the options? Then what do we do? Do we error out or do we ignore them? If we ignore them, some people might be confused in the other case other people will get confused. If we leave them in the resovler, how do we pass them around so that the method for directives doesn't interfere with resolver fields/methods? 🤔

These before/after visitors are only going to be invoked if the fields have method resolvers. How about field-resolvers?
https://github.com/graph-gophers/graphql-go/pull/446/files#diff-87ea4cfcdd6bb8062908727b36ef05d305ddfbd5ed89322e2276f315ac63dd1bR204

I am closing this PR in favor of https://github.com/graph-gophers/graphql-go/pull/543


Not an Issue Just an Enquery

Hi Guys,
Excellent work and thank you for sharing.
Although I have designed a couple of custom ESP32 boards for an ongoing project, one of the major issues, as I'm sure you are aware, is finding suitable project cases/boxes for the finished article. 3D printing is an option for a few units, but to be honest they can be slow to make and butt ugly, on the other hand, unless you are making many thousands, having them manufactures can be extremely expensive.
Another option would be to use an existing form factor like the M5Stack. So my question is, would I be able to use your design with a case like the one found here.
Thank you in advance.

Hey,
Making good cases is hard, agreed!
For a small series, 3D printing is a good option, in my opinion. You can also order small batches 3D printed at acceptable prototyping costs.
Of course compared to the unit costs of a large volume production based on plastic injection or something like that, the prototype costs for 3D printing are very high.
Using a ready-made case would be great, but this won't work, unfortunately, because the OpenStack core only has compatibility with the M5 Bus header, but it doesn't follow the M5 Core's placement of any of the other ports, so it won't work in a M5 Core case...
Some ideas:
Acrylic can be easy to work with, and can be laser-cut (which unlike 3D printing is fast and can produce elegant looking results). Many maker type cases are based on acrylic, which is available in many colours and thicknesses, and can even be ordered pre-formed in angles, circles or boxes.
With a bit of care it can be drilled or also engraved. It's easy to glue with acrylic glue, and many maker-type cases are based on it. With a couple of drilled holes you can bolt your PCBs to the base, and with the laser-cutter you can cut out openings for ports and cables...
PCBs themselves can be used as part of the case - design them in the right shape to cover and protect the actual PCBs which get sandwiched in-between. You can use standoffs to interconnect the stacks of interior PCBs, and have a bolt/screw at the outside ends. Or you can just use standard headers to interconnect, and outside bolts on the case.
Ot design your PCBs to an available case format. By using things like RPi, Arduino or M5 Stack formats, you will find plenty of ready-made cases to use.
But unfortunately this module does not allow it.


Add clarity to docs

I think it's not immediately obvious (right now) to a new user that there are three ways to begin interacting with the UI. I've clarified this in the "Get Started" section of the README.

Option 1: Existing database
Option 2: Empty database with example data
Option 3: Empty database with custom data

I think this will make more sense to a new user who may have their own use case to begin exploring their data via Kùzu.
I also made it more clear that a user should specify absolute paths to the database or data files, this isn't immediately clear to a beginner. Thanks!

Hi @prrao87,
Nice PR. Thank you for your contribution. Could you please take look at our CLA and add the following sentence:

I have read and agree to the terms under [CLA.md]((https://github.com/kuzudb/kuzu-ui/blob/master/CLA.md).

to your PR description if it looks fine to you?

Hi @mewim, done, thanks!


Race conditions with other tabs

Open this URL which uses Backbone.localStorage twice in two separate tabs in the same browser:
http://backbonejs.org/examples/todos/index.html
In the first tab, add a todo item labelled "a", and open the second tab, and add a todo item labelled "b". Then refresh both tabs. Both tabs will now have a list of one item, it being "b". What should have happened is that both tabs have a list of two items, "a" and "b".
This bug happens because of this piece of code in the function create:
this.records.push(model.id.toString());
this.save();

this.records may be out-of-date at this point, and the subsequent line this.save() does not consider this, and simply overwrites what other tabs may have written.
I do not know if there is an easy way to overcome this race condition, but if there isn't, there ought to be a warning in the documentation.

You should do sync between tabs by yourself. Library like this should not do it for you (it just provide interface to use LocalStorage).
Storage feature provides event that you can listen to, and update your models. Example: http://html5demos.com/storage-events

Hi @Flimm and @mateuszwrobel, thanks for contributing this.
I agree that we don't need to document this in this case - a similar issue can happen with server-side APIs so developers should generally be aware of these possibilities.
I would definitely support adding support for events firing from localStorage, however, as this could greatly enhance the usability of this library.

What would it hurt to warn developers about this?
Intelligent and well-educated developers who already know about this race condition get a friendly reminder. Not so intelligent or well-educated developers like me who make bad assumptions about being able to use a library in multiple tabs get their faulty assumptions corrected.
I don't see a downside.
In general, server-side libraries in many languages frequently point out if there are thread-safe or not (although that isn't relevant in Node), so I don't think it would be at all unusual for a library's documentation to point out that the code is not "tab-safe".

Hi @Flimm - it's common in other libraries because being thread-safe or not is a well understood statement that is usually important to know in the context of the library. People generally need to understand the effect on memory during execution of a program as the standard assumption is that it's not affected by other parts of the program.
The localStorage is more like writing to disk (and like synchronising over a network) - you don't assume that it'll remain totally in sync without doing something. If anything, I'd be more inclined to merge #174 and put efforts into improving the ability of the system to remain in sync with your local disk.


Update generate-certificates.md

Fixed Typo
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[ ] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
Please describe your pull request.
:heart:Thank you!

Fixed with https://github.com/zowe/docs-site/pull/3574


Archiving removes wrong files (when archive and log files are in the same directory)

Bug
NLog version: 4.3.7
Platform: .Net 4.5.2
Current NLog config (xml or C#, if relevant)
<target name="file" type="File"
                        layout="${longdate} | ${level:uppercase=true} }"
                        fileName="${LogFolder}/${LogSource}.log"
                        archiveFileName="${LogFolder}/${LogSource}-${date:format=yyyy-MM-dd}#{##}.log"
        archiveEvery="Hour"
                concurrentWrites="true"
        archiveNumbering="Rolling"
        maxArchiveFiles="84"/>

Current result: Not only "nlog files" are deleted from LogFolder, but also web.config and logs from other systems when method DeleteOldArchiveFiles is called
Expected result: Only nlog files are deleting when method DeleteOldArchiveFiles is called.
Problem is that in method DynamicFileArchive.InitializeForArchiveFolderPath all files from directory LogFolder are queued and then deleting in method DeleteOldArchiveFiles.
Internal log:
2016-09-30 14:26:40.3940 Debug Fatal => file
2016-09-30 14:32:41.5089 Warn Cannot delete old archive file : 'C:\logs\SiteLogs\Test8\AvayaToolkit.log'. Exception: System.IO.IOException: The process cannot access the file 'C:\logs\SiteLogs\Test8\AvayaToolkit.log' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at NLog.Targets.FileTarget.DynamicFileArchive.DeleteOldArchiveFiles()
2016-09-30 14:32:41.5089 Warn Cannot delete old archive file : 'C:\logs\SiteLogs\Test8\EpiServer_Test8.log'. Exception: System.IO.IOException: The process cannot access the file 'C:\logs\SiteLogs\Test8\EpiServer_Test8.log' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at NLog.Targets.FileTarget.DynamicFileArchive.DeleteOldArchiveFiles()
It deletes files AvayaToolkit.log and web.config from diretory.

Could you give examples of filenames which are deleted?
Could you check and post the internal log? (level trace)

probably the same
https://github.com/NLog/NLog/issues/1681

tested this with #1681. There is indeed no mask currently on the archive files.
Creating this mask is easy: archiveFileName="c:/temp/logsource1-2016-10-10-.log", but this isn't  archiveFileName="c:/temp/logsource1-****---.log", but this isn't.
I did not tested this case in-depth yet, but could you test with a filename without #?
So ${LogFolder}/${LogSource}-${date:format=yyyy-MM-dd}#{##}.log => ${LogFolder}/${LogSource}-${date:format=yyyy-MM-dd}_{##}.log

This is an issue, but it's not trivial to fix.

Some testing results:

wrong files are deleting without # , without {##}
are deleting when archived files are in the dedicated directory and there are more than one target-rule
When “archiveFileName” like ${LogSource}-${date:format=yyyy-MM-dd}_{##} .log and new day comes, nlog starts rolling files with new day index and leaves with previous.
No logging of wrong files deleting even in internalLogLevel=Trace (one time we captured was when outlier file was locked “Warn Cannot delete old archive file”)

So for now we put maxArchiveFiles="0" to avoid deleting.

Thanks for the testing results!
Funny as it seems this never could have worked (when checking the git history)

Very strange that DynamicFileArchive.InitializeForArchiveFolderPath is activated, when having '{#}' as part of the archiveFileName.
Would this configuration  not work:
<target name="file" type="File"
         layout="${longdate} | ${level:uppercase=true} }"
         fileName="${LogFolder}/${LogSource}.log"
         archiveFileName="${LogFolder}/${LogSource}-{#}.log"
         archiveEvery="Hour"
         concurrentWrites="true"
         archiveDateFormat="yyyy-MM-dd"
         archiveNumbering="DateAndSequence"
         maxArchiveFiles="84"/>

Made the following changes:

archiveNumbering="DateAndSequence"
archiveDateFormat="yyyy-MM-dd"
archiveFileName="${LogFolder}/${LogSource}-{#}.log"

When using archiveNumbering="Rolling" (or Sequence), then it expects the archiveFileName to be completely static (Thus using date-renderer is not supported).

fixed by #1993, NLog 4.5. Thanks @snakefoot !


Click on row removed Datagrid

@fzaninotto
Hi, Francois! Right now I found new issue.
Let's look at the video:
https://drive.google.com/file/d/1GqvCtBPnVX8Xkp1qYcT-1T21KsujMb41/view
When we click on the row at the page 2 and more, content of ids array in Store (I mean admin.resources.allergies.list.ids) is removed, and we can see only one id here - id of item, which we click on.
This problem is absent only at first page of list (paginator = 1).
My assumption: it is because program don't know current page=X and perPage=Y.
Because when I try to use URL like:
/{resourseName}/{id}?page=2&perPage=10
the problem is absent:

I can try to find a way how to add page and perPage to URL when we click on row, but is it true way?

As seen together on the phone, you can pass a function as rowClick and build a URL containing the query parameters busing document.location

@fzaninotto
Hi, Francois!
I tried to use custom rowClick to solve this problem. But this solution doesn't work with custom datagrid:
function getPath(id, basePath, record) {
    console.log('++++++++++++++++++++++++++++++++++++++++++++')
    console.log('id', id);
    console.log('basePath', basePath);
    console.log('record', record);
    return 'show'
}

const CustomDatagridBody = ({ CustomRow, location, hiddenColumns, history, ...rest }) => {
    return (
        <DatagridBody
            row={<CustomRow
                location={location}
                hiddenColumns={hiddenColumns}
                history={history}
            />}
            {...rest}
        />
    );
};

const CustomDatagrid = ({ classes, history, CustomRow, CustomTableHead, hiddenColumns, location, ...rest }) => {
    return (
        <Datagrid
            rowClick={(id, basePath, record) => getPath(id, basePath, record)}
            body={
                <CustomDatagridBody
                    location={location}
                    hiddenColumns={hiddenColumns}
                    history={history}
                    CustomRow={CustomRow}
                />}
            {...rest}
        />
    );
};

const DatagridBlock = ({ classes, location, hiddenColumns, isCustomDatagrid, children, history, CustomRow, CustomTableHead, ...rest }) => {
    if (isCustomDatagrid) {
        return (

                <CustomDatagrid
                    className={classes.tableList}
                    hiddenColumns={hiddenColumns}
                    location={location}
                    CustomRow={CustomRow}
                    CustomTableHead={CustomTableHead}
                    history={history}
                    {...rest}
                >
                    {children}
                </CustomDatagrid>

        );
    }
    return (

            <Datagrid
                className={classes.tableList}
                classes={{ rowEven: classes.rowEven, rowOdd: classes.rowOdd  }}
                rowClick={(id, basePath, record) => getPath(id, basePath, record)}
                {...rest}
            >
                {children}
            </Datagrid>

    );
};

I checked it, by disabling these rows:
const DatagridBlock = ({ classes, location, hiddenColumns, isCustomDatagrid, children, history, CustomRow, CustomTableHead, ...rest }) => {
    // if (isCustomDatagrid) {
    //     return (
    //

    //             <CustomDatagrid
    //                 className={classes.tableList}
    //                 hiddenColumns={hiddenColumns}
    //                 location={location}
    //                 CustomRow={CustomRow}
    //                 CustomTableHead={CustomTableHead}
    //                 history={history}
    //                 {...rest}
    //             >
    //                 {children}
    //             </CustomDatagrid>
    //

    //     );
    // }
    return (

            <Datagrid
                className={classes.tableList}
                classes={{ rowEven: classes.rowEven, rowOdd: classes.rowOdd  }}
                rowClick={(id, basePath, record) => getPath(id, basePath, record)}
                {...rest}
            >
                {children}
            </Datagrid>

    );
};

In this case we can see console.log() results. But when we try to use rowClick={....} with CustomDatagrid, console.log() is absent.
I tried to add rowClick={....} also to:

CustomDatagridBody
DatagridBody
CustomRow

But in all cases console.log() doesn't appear in Console.
Is rowClick work with custom datagrid generally?

@tony-shannon @PhilBarrett
This issue was fixed.
I tried to use DatagridRow instead of TableRow - table not working in this case.
But I changed onClick - now it add page to URL. I forgot, that we redirect user to show page manually (not by RA-functionality), so we have possibility to control it.
And it works!!!
@djhi, thank you very much for help!


Set up GitHub issue templates.

Inspired by how Akka does it. It renders as something like https://github.com/akka/akka/issues/new/choose.

Updated. I tried to address every comment.


Bunyan log parsing

The current bunyan log version is 0 which means that the current test for bunyan log format doesn't work as parsed.v won't be truthy.
This patch fixes that issue, adds code to remove the bunyan time field after converting it to @timestamp, and adds a test for proper bunyan message parsing.

Is that a dupe of #56, but with a test?

I see that the core issue was just fixed, hopefully the time field handling and additional test are useful

@otisg it contains the same fix, plus the test and removal of the now-redundant time field

Thank you, released 2.0.53 with both PR's.

Very cool 👍


Unknown file extension ".ts"

I got past the RootSeeder problem but now I get this:
✔ ORM Config loaded
✔ Seeder imported
✖ Could not run the seed RootSeeder!
Unknown file extension ".ts" for /Users/****/Sites/s2pro.com.br/backend/src/modules/exercises/infrastructure/typeorm/entities/Exercise.ts

Here is my ormconfig.json:
[
    {
        "name": "default",
        "type": "mysql",
        "host": "localhost",
        "port": 3306,
        "username": "root",
        "password": "docker",
        "database": "s2pro",
        "logging": true,
        "synchronize": true,
        "defaultSeeder": "RootSeeder",
        "entities": [
            "./src/modules/**/infrastructure/typeorm/entities/*.ts"
        ],
        "migrations": [
            "./src/shared/infrastructure/typeorm/migrations/*.ts"
        ],
        "cli": {
            "migrationsDir": "./src/shared/infrastructure/typeorm/migrations"
        },
        "seeders": [
            "./src/shared/infrastructure/typeorm/seeders/*.ts"
        ],
        "factories": [
            "./src/shared/infrastructure/typeorm/factories/*.ts"
        ]
    }
]

RootSeeder
import { Seeder } from "@jorgebodega/typeorm-seeding"
import { Connection } from "typeorm";
import {UserSeeder} from "./UserSeeder";

export class RootSeeder extends Seeder{
    async run(connection: Connection): Promise<void> {
        await this.call(connection, [UserSeeder])
    }

}

Any thoughts on this?

Problems with type extensions on TypeScript is usually relates with ts-node, tsconfig...
Please check that options and then I will check that

@jorgebodega here is my tsconfig:
{
  "compilerOptions": {

    "target": "es2016",
    "module": "commonjs",
    "outDir": "./dist",
    "rootDir": "./src",
    "strict": true,
    "strictPropertyInitialization": false,
    "baseUrl": "./src",
    "allowJs": true,
    "paths": {
      "@modules/*": [
        "modules/*"
      ],
      "@config/*": [
        "config/*"
      ],
      "@shared/*": [
        "shared/*"
      ]
    },
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true
  },
  "exclude": [
    "./prettier.config.js",
    "./babel.config.js",
    "./coverage",
    "./jest.config.js"
  ]
}

and here is my script on package-json
"seed": "ts-node-dev -r tsconfig-paths/register<EMAIL_ADDRESS>seed"

Hi! Sorry, I've literally didn't see the issue.
Is this still happening? And with the new version?

Sorry! I notice that default is missing while exporting seeders.
I added that to the README (missing, my fault) and also improve the error description.
Try again with the new version and default, please.

For other readers, I was able to run the seeds with this script in my package.json
"seed": "ts-node -r tsconfig-paths/register<EMAIL_ADDRESS>seed -d src/orm-config.ts seeding/*.ts"

And then npm run seed.
Thanks Jorge for taking over this repo!

Closing as this is stale and probably fixed.


Build error(Failed   <<< rmf_traffic_ros2 [1min 29s, exited with code 2])

Bug report
Required information:

Operating system and version:

Ubuntu 20.04

Open-RMF installation type:

https://git.lejurobot.com/rmf/rmf-all.git

Open-RMF version or commit hash

21.09

ROS distribution and version:

Galactic

ROS installation type:

from source

Description of the bug
When I run 'colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release', I get a build error.  You can see the error code in the screen shot below.
Steps to reproduce the bug

Install ubuntu 20.04
Install ROS Galactic
install rmf for Galactic from https://git.lejurobot.com/rmf/rmf-all.git
When I run 'colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release', I get this build error.

Expected behavior
build successfully
Actual behavior
build error
Screenshots

Additional information

Hello @Alexander-ph! Sorry that you're facing this, in the future please share the logs via a gist.github.com, it helps us look at the entire build process. Also just a note, we are no longer actively maintaining the galactic release, as ROS 2 Galactic is already EOL. You'll get all the nice and shiny features in ROS 2 Humble on Ubuntu 22.04 :sparkles:
It appears that the file you are attempting to share is not available for public viewing. Please check the permissions

Hello @Alexander-ph! Sorry that you're facing this, in the future please share the logs via a gist.github.com, it helps us look at the entire build process. Also just a note, we are no longer actively maintaining the galactic release, as ROS 2 Galactic is already EOL. You'll get all the nice and shiny features in ROS 2 Humble on Ubuntu 22.04 ✨
It appears that the file you are attempting to share is not available for public viewing. Please check the permissions

sorry，I did not save it :).
sorry for that, I'm just starting to learn this.
And, I'm just a new member for that repository, I have no right.

No problems at all! Without knowing the exact releases that are being built, I'm afraid we are unable to help much other than advising to migrate to ROS 2 Humble's release.

No problems at all! Without knowing the exact releases that are being built, I'm afraid we are unable to help much other than advising to migrate to ROS 2 Humble's release.

I've made it. Yeah!!! Thank you so much!!!
But I'm facing a new problem now, and I have no idea to solve it.


Rename googledatalogger to GoogleDataTransport

This better reflects what it actually does. Consequently, much of the API has also been renamed. Comments should have been fixed.
GoogleDataLogger podspec has been renamed to GoogleDataTransport.
Prefix has changed from GDL to GDT.
Logging verbs have been changed to 'transport'.
Comments hopefully have been fixed to remove reference to logs.
There are no (on purpose) logic changes to this PR.

Is this supposed to transport any data outside of logging? Maybe add a comment in a public header explaining the purpose?

The point is more like "What is logging?", "Are we doing logging?", "How can one log something that isn't text?" None of those things has a clear answer in the context of Firebase, IMO. For sure, we leverage logging libraries in Firebase to transport data from mobile devices to Google backends. This is why we've decided to not call it a 'logger', but instead to call it 'transport'.


In 1171 exclude inactive tasks

Purpose
Currently we’re migrating tasks from Casrec with casrec_csv.sup_activity.status = ‘ACTIVE’|'INACTIVE'
Change this so that we’re only migrating tasks with status = ‘ACTIVE’
Approach
Updated spreadsheet, regenerate mapping files, update tests validation and counts
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered
Checklist

[ ] I have performed a self-review of my own code
[ ] I have done an adhoc run against preprod (only needed for high complexity PRs)
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

@farzan1990 will also need to review as this touches spreadsheets.


Rename bmsbk field

According to DCR unk4 is the respawn time for the blocks, where 0.0 means it nevers respawn and if greater than 0.0 it's the time in seconds.
@dyceron Are there other fields we could rename? There was a "always visible" thing but I don't know to which field it was related.

Thats all I saw at the moment. unk3 controls the always visible part, though it's not perfect


Reddit Community Bastyon Placeholder

Hello Bastyon community :)
I'm new to Bastyon. It's my favourite alternative to Facebook, Twitter, and all social medias.
This is to notify you that, as a volunteer, I created this placeholder Reddit community at https://www.reddit.com/r/Bastyon/ By "placeholder" I mean that I reserved the community name Bastyon on Reddit.
Volunteers interested in both Reddit and in maintaining this Reddit community are welcome to contact me Francewhoa at https://bastyon.com/francewhoa Asking to add you as moderator.
For now, I added links from this Reddit community to https://bastyon.com In turn, this might bring more people to the Bastyon community. As of 2020, Reddit claim to have 52 million active real users.
If someone is wondering about my intention. I do NOT recommend Reddit. I very seldom use it. Because of it's very long history of censorship.
In the future, if the Bastyon community need a discussion software, in addition to Bastyon itself, I suggest https://www.discourse.org The main risk with Discourse is that it's controlled by the centralized for-profit organization "Civilized Discourse Construction Kit, Inc." Which in turn, is financed by the centralized for-profit, venture capital funding from First Round, Greylock, and SV Angel. All of the above means that "Civilized Discourse Construction Kit, Inc."  and venture capital are at very high risk of prioritizing money over people.
You're welcome to ask me if you have any questions, concerns or suggestions about any of the above
Cheers,
Francewhoa

Hi @Francewhoa,
Thank you for your contribution!) I checked your issue and left some comments. I hope for a long cooperation!)


update to v0.0.3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin, please add user @marjanAlbouye

@conda-forge-admin, please add user @marjanAlbouye


Local install page is unclear

The title of the local install page is "Install DC/OS on Vagrant" - but from what I can work out, the linked installer in the first script is actually using Docker.
(It complained when I launched it and Docker wasn't available:)
➜  Downloads ./dcos_generate_config.sh
docker should be installed and running. Aborting.

Which is it? If it's Docker, we should call this out as a requirement and rename this page's title.
It would be useful to have a paragraph comparing the two installation methods too.

Is this still and issue? If not, let's close …

I figured it out - this was user error. Thanks!

I ❤ layer 8 issues. Thanks @ssk2!

This is still a problem with the current release.
Solution is to install docker (apt install docker.io on ubuntu), however this is not mentioned in the docs.


Raise PHPStan to level 6

Codecov Report

Merging #276 (8f56acd) into master (b7e109d) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #276      +/-   ##
============================================
- Coverage     90.92%   90.90%   -0.03%
+ Complexity      433      432       -1
============================================
  Files            44       44
  Lines          1289     1286       -3
============================================
- Hits           1172     1169       -3
  Misses          117      117

Impacted Files
Coverage Δ

...ExternalRedirect/WhitelistBasedTargetValidator.php
100.00% <ø> (ø)

.../Violation/Filter/InjectedScriptsNoiseDetector.php
83.33% <0.00%> (-1.29%)
:arrow_down:

...rc/DependencyInjection/NelmioSecurityExtension.php
88.78% <0.00%> (-0.94%)
:arrow_down:

...rc/EventListener/ContentSecurityPolicyListener.php
87.80% <0.00%> (-0.15%)
:arrow_down:

src/Session/CookieSessionHandler.php
66.25% <0.00%> (+0.81%)
:arrow_up:

Continue to review full report at Codecov.

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


remove unnecessary dependencies

Remove assert library which has been deprecated and just clone the functions locally for now.  In the future this should be just changed to if statements and testing.T.
Also there were a number of broken tests that were fixed.

Thank you!

Interestingly, a couple of the tests you fixed fail for me, but appears to be poorly designed tests that are affected by local time of machine you test on.  Seems to me to be what i would consider a bug in go.
https://github.com/araddon/dateparse/commit/f1f37e5e2988c73378350bc833f7dafd6aaf4628


[FLINK-14688] Add table related DDLs support in SQL Parser

What is the purpose of the change
The PR is only about parser related changes to support table-related commands and Hooking up with table env will come later. We add such parser support:

showTablesStatement:
SHOW TABLES
descTableStatement:
DESCRIBE [ EXTENDED] [[catalogName.] dataBasesName].tableName
alterTableStatement:
ALTER TABLE [[catalogName.] dataBasesName].tableName
RENAME TO newTableName
ALTER TABLE [[catalogName.] dataBasesName].tableName
SET ( name=value [, name=value]*)

Brief change log

add show tables syntax support in parsre
add describe table support in parser
add alter table support in parser

Verifying this change
This change added tests and can be verified as follows:

FlinkSqlParserImplTest#testShowTables
FlinkSqlParserImplTest#testDescribeTable
FlinkSqlParserImplTest#testAlterTable

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yno)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes )
If yes, how is the feature documented? (not applicable)

cc @bowenli86 @xuefuz @lirui-apache to have a review

LGTM, I can merge it once the conflict is resolved.

hi @bowen
I just rebase the master and force-pushed to resolve the conflict.


Hot restart on web resets current URL route after upgrading to 2.2

Prior to Flutter 2.2, if the application was hot restarted, the current URL displayed world persist. For example, if the application was at localhost:5555/some/route, then after a hot restart the application would boot directly to the same route (localhost:5555/some/route).
After upgrading to 2.2 (and continuing in 2.2.1), the route is cleared and reset to the default. I.e. after hot restart, the application will start at localhost:5555/, regardless of what the previous route was .
This is not a major issue, but somewhat of a minor development annoyance.
Steps to Reproduce

Start a flutter web application in debug mode
Navigate to some named route
Hot restart the application. It will now be reset to the default route.

duplicate of https://github.com/flutter/flutter/issues/82737 and https://github.com/flutter/flutter/issues/79241

Closing this as duplicate of above linked issues.


How can I set the timezone to other?

version: v0.2.1
#date
Mon May 20 08:11:46 UTC 2019
Can you  guide me to set time+8 for k3os，thanks!

In my config.yaml, I have:
boot_cmd:
  - "echo SGT+8 > /etc/TZ"

I'll add tzdata and some default symlinks soon.

The tzdata info is now included in the rootfs via #428. I'll ad a readme entry that shows how to set your timezone.

@dweomer would it be possible to have a timezone setting in the yaml file?
I'm glad I've found this ticket, having the dates in our own timezone makes scanning log files much easier.


Move benchmark to another package

phpbench use PSR container only first version: https://github.com/phpbench/container/blob/def10824b6009d31028fa8dc9f73f4b26b234a67/composer.json#L13
This prevents the use of the second version of psr/container in DI.

Let's try pull-requesting there first.

The pull requset was merged so I guess moving benchmark is no longer needed.


⚠ Bofrost.es has degraded performance

In 43815f3, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1436 ms

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


[Feature Request] ConversationalChain prints system, user and human message prompts using separate colors.

Currently the logging output from the ConversationChain is quite hard to read.
I believe implementing separate colors from System Messages, Human Messages and AI messages by role would involve modifying the prep_prompts and the aprep_prompts methods within the ConversationChain subclass.
Something like:
    def prep_prompts(self, input_list: List[Dict[str, Any]]) -> Tuple[List[PromptValue], Optional[List[str]]]:
        """Prepare prompts from inputs."""
        stop = None
        if "stop" in input_list[0]:
            stop = input_list[0]["stop"]
        prompts = []
        for inputs in input_list:
            selected_inputs = {k: inputs[k] for k in self.prompt.input_variables}
            prompt = self.prompt.format_prompt(**selected_inputs)

            _text_parts = []
            for section in prompt:
                if section.role == "Human":
                    _text_parts.append(get_colored_text(section.to_string(), "green"))
                elif section.role == "AI":
                    _text_parts.append(get_colored_text(section.to_string(), "blue"))
                elif section.role == "System":
                    _text_parts.append(get_colored_text(section.to_string(), "white"))
                else:
                    raise ValueError(f"Unknown role: {section.role}")

            # _colored_text = get_colored_text(prompt.to_string(), "green")
            _colored_text = "\n".join(_text_parts)

            _text = "Prompt after formatting:\n" + _colored_text
            self.callback_manager.on_text(_text, end="\n", verbose=self.verbose)
            if "stop" in inputs and inputs["stop"] != stop:
                raise ValueError("If `stop` is present in any inputs, should be present in all.")
            prompts.append(prompt)
        return prompts, stop

As far as I'm aware, this won't work because I don't understand how to work with the PromptValue ABC,
whether a ConversationChatPrompt's PromptValue can be iterated over.
It might also be possible to call .to_messages() on the PromptValue, iterate over the messages, getting the appropriate colored text, then returning the concatenated result.

Note this would also be possible by defining a callback function that splits the text into sections by role using a regex and color codes each section,


Snake Mini-Game Screen Creation and Rendering

Description
Task: Make SnakeScreen (#40)
Feature: Mini Games (#6)
This task involves implementing the Snake Screen for the mini-game, which will be part of the larger game interface. The Snake Screen will be designed to display the game area where the Snake game will be played. The task includes creating a new button for playing the snake mini-game, ensuring the game screen is correctly integrated and functional. This will also involve setting up the visual layout and performing some unit testing to ensure the screen operates correctly.
Examples
Button Integration: Create a new button labeled "Minigames" that, when clicked, opens the Snake Screen.
Screen Display: The Snake Screen should display the game grid, the snake, and the food items (apples), with functional game mechanics.
Testing: Conduct unit tests to verify that the Snake Screen behaves as expected, including interactions and game playability.
Milestones

[x] Get the new button as "MiniGame" button. (Aug. 19)
[x] Import all required services for a new screen. (Aug. 19)
[x] Display the new screen (Snake Screen) where the game will be played. (Aug 21)
[x] Refactor SnakeScreen Class (Aug 28)

Completion Deadline: Aug. 28
Documentation

Main description of feature
JavaDoc SnakeScreen

Member
Manandeep Singh
@24msingh24
24msingh24
@jakingy
jakingy
Nathan Chung
@0NATE4
0NATE4

Please edit and change this to reflect your own contributions

Complete


ERROR: Images had test errors

I'm getting this error during Pkg.test:
Algorithms: .................................................................................E..................................
  Error :: (line:505)
    Expression: Images.imfilter(Aimg,kern) --> roughly(permutedims(Af,[3,1,2]))
    `-` has no method matching -(::Array{Float64,3}, ::Image{Float64,3,Array{Float64,3}})
     in anonymous at no file:34
     in anonymous at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:263
     in anonymous at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:271
     in do_fact at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:333
     in anonymous at /Users/quetzal/.julia/v0.3/Images/test/algorithms.jl:271
     in context at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:474
     in anonymous at /Users/quetzal/.julia/v0.3/Images/test/algorithms.jl:135
     in facts at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:448
     in include at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
     in include_from_node1 at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
     in include at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
     in include_from_node1 at loading.jl:128
     in process_options at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
     in _start at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
Edge: ..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
ERROR: FactCheck finished with 1 non-successful tests.
 in error at error.jl:21
 in exitstatus at /Users/quetzal/.julia/v0.3/FactCheck/src/FactCheck.jl:563
 in include at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
 in include_from_node1 at loading.jl:128
 in process_options at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
 in _start at /usr/local/Cellar/julia/0.3.10/lib/julia/sys.dylib
while loading /Users/quetzal/.julia/v0.3/Images/test/runtests.jl, in expression starting on line 30

See below my julia environment details:
quetzal@MacBook-Pro:~ $ julia -E 'versioninfo()'
Julia Version 0.3.10
Commit c8ceeef* (2015-06-24 13:54 UTC)
Platform Info:
  System: Darwin (x86_64-apple-darwin14.3.0)
  CPU: Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz
  WORD_SIZE: 64
  BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3
nothing

I'm using Images v0.4.45.

I also am getting errors when running Pkg.test("Images"),  namely
Error :: (line:-1)
Expression: props[key] --> anything
anything not defined
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:259
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:271
in do_fact at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:333
in anonymous at /home/matthew/.julia/v0.3/Images/test/readremote.jl:271
in context at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:474
in anonymous at /home/matthew/.julia/v0.3/Images/test/readremote.jl:189
in facts at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:448
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in include at ./boot.jl:245
in include_from_node1 at loading.jl:128
in process_options at ./client.jl:285
in _start at ./client.jl:354
and additionally
Error :: (line:-1)
Expression: props[key] --> anything
anything not defined
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:259
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:271
in do_fact at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:333
in anonymous at /home/matthew/.julia/v0.3/Images/test/readremote.jl:271
in context at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:474
in anonymous at /home/matthew/.julia/v0.3/Images/test/readremote.jl:189
in facts at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:448
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in include at ./boot.jl:245
in include_from_node1 at loading.jl:128
in process_options at ./client.jl:285
in _start at ./client.jl:354

Oh one other thing possibly related is that I'm getting a lot of these warnings:
WARNING: Color is deprecated, please use Colors instead.

Looks like you need to update Images.jl, at the least.

If you're seeing WARNING: Color is deprecated, please use Colors instead, then that means you have local modifications of some package that is preventing you from upgrading to the latest versions of packages that Images depends on. Check Pkg.status() for anything marked "dirty" and try to resolve the issue.

@mattcbro just remove Color with Pkg.rm("Color") and install Colors instead...
BTW it didn't help me to fix the failed test...

For the PyPlot error, a new version just got tagged 3 hours ago. Pkg.update() might fix it.
@nikolaypavlov, does this not work for you? (From a fresh REPL session)
julia> using Images

julia> A = rand(5,7,6);

julia> img = grayim(A)
Gray Images.Image with:
  data: 5x7x6 Array{Float64,3}
  properties:
    colorspace: Gray
    spatialorder:  x y z

julia> A-img
5x7x6 Array{Float64,3}:
[:, :, 1] =
 0.0  0.0  0.0  0.0  0.0  0.0  0.0
 0.0  0.0  0.0  0.0  0.0  0.0  0.0
...

If that works, then the error message makes little sense because the operation it is complaining about is defined.
Are you using any other packages simultaneously? DataArrays, for example?

@mattcbro, anything was defined in FactCheck but was recently deleted. https://github.com/JuliaLang/FactCheck.jl/commit/57e4d5b48fabaefa1e7d6b06af400b02c1e05700

In general, if the error messages are different, please open a separate issue. Once #344 merges, it will close this issue automatically. Hopefully we'll have @nikolaypavlov's error resolved anyway.

@timholy It doesn't work for me. (I'm using plain julia REPL session):
julia> A-img
ERROR: `-` has no method matching -(::Array{Float64,3}, ::Image{Float64,3,Array{Float64,3}})

Here is my Pkg.status() as well:
julia> Pkg.status()
29 required packages:
 - ArgParse                      0.2.11
 - Bokeh                         0.1.0
 - Cairo                         0.2.29
 - Clustering                    0.4.0
 - DSP                           0.0.10
 - DataFrames                    0.6.9
 - DecisionTree                  0.3.9
 - Distance                      0.5.1
 - Gadfly                        0.3.14
 - HDF5                          0.5.5
 - HTTPClient                    0.1.5
 - HypothesisTests               0.2.9
 - IJulia                        0.2.5
 - Images                        0.4.45
 - JSON                          0.4.5
 - Jewel                         1.0.5
 - JuMP                          0.9.3
 - KernelDensity                 0.1.1
 - KernelEstimator               0.1.4
 - Lint                          0.1.68
 - Loess                         0.0.3
 - MLBase                        0.5.1
 - MachineLearning               0.0.3
 - Mocha                         0.0.9+             master
 - MultivariateStats             0.2.1
 - NumericExtensions             0.6.2
 - PyPlot                        2.0.0
 - RDatasets                     0.1.2
 - Winston                       0.11.12
67 additional packages:
 - ArrayViews                    0.6.3
 - BinDeps                       0.3.15
 - Blosc                         0.1.4
 - Calculus                      0.1.10
 - Codecs                        0.1.4
 - ColorTypes                    0.1.3
 - ColorVectorSpace              0.0.2
 - Colors                        0.5.2
 - Compat                        0.6.0
 - Compose                       0.3.14
 - Contour                       0.0.7
 - Cubature                      1.0.7
 - DataArrays                    0.2.17
 - DataStructures                0.3.12
 - Dates                         0.3.2
 - Devectorize                   0.4.1
 - Distances                     0.2.0
 - Distributions                 0.8.3
 - Docile                        0.5.16
 - DualNumbers                   0.1.3
 - FactCheck                     0.4.0
 - FixedPointNumbers             0.0.10
 - GZip                          0.2.17
 - Graphics                      0.1.0
 - Grid                          0.3.10
 - Hexagons                      0.0.3
 - Homebrew                      0.1.16
 - ImmutableArrays               0.0.10
 - IniFile                       0.2.4
 - Iterators                     0.1.8
 - JLD                           0.5.4
 - JuliaParser                   0.6.2
 - LNR                           0.0.1
 - LaTeXStrings                  0.1.4
 - Lazy                          0.10.0
 - LibCURL                       0.1.4
 - Logging                       0.1.1
 - MacroTools                    0.2.0
 - MathProgBase                  0.3.16
 - Mustache                      0.0.11
 - NaNMath                       0.1.0
 - Nettle                        0.1.10
 - NumericFuns                   0.2.3
 - Optim                         0.4.2
 - Options                       0.2.4
 - PDMats                        0.3.5
 - Polynomials                   0.0.3
 - PowerSeries                   0.1.13
 - PyCall                        0.8.2
 - REPLCompletions               0.0.3
 - Reexport                      0.0.2
 - Requires                      0.1.3
 - ReverseDiffSparse             0.2.10
 - Roots                         0.1.16
 - SHA                           0.1.1
 - SIUnits                       0.0.5
 - Showoff                       0.0.4
 - SortingAlgorithms             0.0.5
 - StatsBase                     0.7.1
 - StatsFuns                     0.1.2
 - TexExtensions                 0.0.2
 - TextWrap                      0.1.3
 - Tk                            0.3.5
 - URIParser                     0.0.5
 - WoodburyMatrices              0.1.1
 - ZMQ                           0.2.0
 - Zlib                          0.1.8

I can confirm this on Julia 0.3.11.  No problem on Julia 0.4

I'm a bit stumped, I don't see anything obvious that would cause this problem.  Issue appears at 8917723 in Travis.
I've ruled this out for this particular issue, but FYI there seems to be an issue with ColorVectorSpace on Julia 0.3.  After a Pkg.update(), I don't see it in my package dir even though Images lists it as a requirement.  Does ColorVectorSpace need to be tagged or something?  Also, is it "0.3-clean"?

After today's update (08/24/2015) the Color vs Colors package warnings are gone from the PyPlot module as advertised.  Pkg.test("Images") still fails with some slightly different error messages than before.
The anything not defined error still occurs in FactCheck.jl line 259 .   However now in the algorithm section we have,
Algorithms: .................................................................................E..................................
Error :: (line:-1)
Expression: Images.imfilter(Aimg,kern) --> roughly(permutedims(Af,[3,1,2]))
- has no method matching -(::Array{Float64,3}, ::Image{Float64,3,Array{Float64,3}})
in anonymous at no file:34
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:263
in anonymous at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:271
in do_fact at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:333
in anonymous at /home/matthew/.julia/v0.3/Images/test/algorithms.jl:271
in context at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:474
in anonymous at /home/matthew/.julia/v0.3/Images/test/algorithms.jl:135
in facts at /home/matthew/.julia/v0.3/FactCheck/src/FactCheck.jl:448
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in include at ./boot.jl:245
in include_from_node1 at loading.jl:128
in process_options at ./client.jl:285
in _start at ./client.jl:354
So a problem with how imfilter() is being used.

This is really puzzling. Until late yesterday, we had 3 passes in a row on Travis, then it failed with the same error reported here:
https://travis-ci.org/timholy/Images.jl/builds

OK, fixed (I hope). Pkg.checkout("Images") to test.

I've ruled this out for this particular issue, but FYI there seems to be an issue with ColorVectorSpace on Julia 0.3. After a Pkg.update(), I don't see it in my package dir even though Images lists it as a requirement. Does ColorVectorSpace need to be tagged or something? Also, is it "0.3-clean"?

Seems OK:
$ JULIA_PKGDIR=/tmp/pkgs julia-old -q
julia> versioninfo()
Julia Version 0.3.12-pre+3
Commit 1b838a4* (2015-08-16 05:51 UTC)
Platform Info:
  System: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i7 CPU       L 640  @ 2.13GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Nehalem)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3

julia> Pkg.init()
INFO: Initializing package repository /tmp/pkgs/v0.3
INFO: Cloning METADATA from git://github.com/JuliaLang/METADATA.jl

julia> Pkg.add("Images")
INFO: Cloning cache of BinDeps from git://github.com/JuliaLang/BinDeps.jl.git
INFO: Cloning cache of ColorTypes from git://github.com/JuliaGraphics/ColorTypes.jl.git
INFO: Cloning cache of ColorVectorSpace from git://github.com/JuliaGraphics/ColorVectorSpace.jl.git
INFO: Cloning cache of Colors from git://github.com/JuliaGraphics/Colors.jl.git
INFO: Cloning cache of Compat from git://github.com/JuliaLang/Compat.jl.git
INFO: Cloning cache of Docile from git://github.com/MichaelHatherly/Docile.jl.git
INFO: Cloning cache of FixedPointNumbers from git://github.com/JeffBezanson/FixedPointNumbers.jl.git
INFO: Cloning cache of Graphics from git://github.com/JuliaLang/Graphics.jl.git
INFO: Cloning cache of Images from git://github.com/timholy/Images.jl.git
INFO: Cloning cache of Reexport from git://github.com/simonster/Reexport.jl.git
INFO: Cloning cache of SHA from git://github.com/staticfloat/SHA.jl.git
INFO: Cloning cache of SIUnits from git://github.com/Keno/SIUnits.jl.git
INFO: Cloning cache of TexExtensions from git://github.com/Keno/TexExtensions.jl.git
INFO: Cloning cache of URIParser from git://github.com/JuliaWeb/URIParser.jl.git
INFO: Cloning cache of Zlib from git://github.com/dcjones/Zlib.jl.git
INFO: Installing BinDeps v0.3.15
INFO: Installing ColorTypes v0.1.3
INFO: Installing ColorVectorSpace v0.0.2
INFO: Installing Colors v0.5.2
INFO: Installing Compat v0.6.0
INFO: Installing Docile v0.5.16
INFO: Installing FixedPointNumbers v0.0.10
INFO: Installing Graphics v0.1.0
INFO: Installing Images v0.4.45
INFO: Installing Reexport v0.0.2
INFO: Installing SHA v0.1.1
INFO: Installing SIUnits v0.0.5
INFO: Installing TexExtensions v0.0.2
INFO: Installing URIParser v0.0.5
INFO: Installing Zlib v0.1.8
INFO: Building Images
INFO: Package database updated

julia> Pkg.test("ColorVectorSpace")
INFO: Computing test dependencies for ColorVectorSpace...
INFO: Cloning cache of FactCheck from git://github.com/JuliaLang/FactCheck.jl.git
INFO: Installing FactCheck v0.4.0
INFO: Testing ColorVectorSpace
Colortypes
  > Arithmetic with Gray
  > Arithmetic with GrayA
  > Arithemtic with RGB
  > Arithemtic with RGBA
213 facts verified.
INFO: ColorVectorSpace tests passed
INFO: Removing FactCheck v0.4.0

julia>

Fixed... Thanks.