SpeciesFileGroup/taxonworks

Workbench for biodiversity informatics.

Matt

@mjy

Welcome to the joys of open APIs.

Especially very desireably open APIs

### Webpack out of memory

I think that is no longer an issue for Troubleshooting?

José Luis Pereira

@jlpereira

nope

Hernán Lucas Pereira

@LocoDelAssembly

Link?

Matt

@mjy

Native instructions troubleshooting section, I'm editing now

should I remove?

José Luis Pereira

@jlpereira

yah

That problem don't exist anymore

Hernán Lucas Pereira

@LocoDelAssembly

If macos yes, those instructions are not what I'd use on Linux (if it is the same problem)

Matt

@mjy

os x

I will remove

José Luis Pereira

@jlpereira

Even on Linux, its not longer needed increment the memory for webpack

Matt

@mjy

@LocoDelAssembly thinking- should we target one of the sandboxes in particular for TaxonWorks Together ACcounts?

Hernán Lucas Pereira

@LocoDelAssembly

If sandbox is not suitable we might need a new one? Can't remember if we still have one unused.

Matt

@mjy

Any would be suitable, but also envisioning possiblity of sharing a snapshot/dump to everyone vs. stuff we collaboratively edit. Maybe a new one?

Hernán Lucas Pereira

@LocoDelAssembly

Were seed data will come from?

Matt

@mjy

Humans.

Hernán Lucas Pereira

@LocoDelAssembly

So completely empty database you mean?

Matt

@mjy

No- we'd want to have the geo/standard install.

There is a rake task that initializes that world, not sure if we can access it in containers thou.

I suppose we could just take one dump, and use project#nuke 1 or 2 times :)

Hernán Lucas Pereira

@LocoDelAssembly

sandstone?

Matt

@mjy

Sure- it's empty now it looks like?

I.e. not used?

Hernán Lucas Pereira

@LocoDelAssembly

Not used, is listed in wiki as available name.

Matt

@mjy

Sounds good to use.

Not a priority to setup before the install session tho

Hernán Lucas Pereira

@LocoDelAssembly

Yeah, I figured we wouldn't do this with 5 minutes margin XD

Matt

@mjy

Hernán Lucas Pereira

@LocoDelAssembly

Created issue though

Matt

@mjy

Thanks.

Matt

@mjy

Crossed my mind, likely not the issue with Brian, but is there some default Rosetta stuff going on in Big Sur that he might have turned on?

Hernán Lucas Pereira

@LocoDelAssembly

I guess it shouldn't do anything. Images are x86 and his hardware is also x86. The thing about time machine is perhaps worth exploring. Don't remember if we have seen in Activity Monitor IO performance (if metric is available)

Matt

@mjy

@/all curious as to what we each have on our plates that blocks us from doing a new release?

For me:

content, images, notes, people endpoints/API etensions (done 3 of the 4) and testing that the refinement
A couple minor cosmetic bugs
whatever @jlpereira needs for Uniquify updates

José Luis Pereira

@jlpereira

we already finished image filter?

almost done the new changes on uniquify people task

Matt

@mjy

From the limited tests I did on it I think it's OK for now.

It's already merged to development, right?

José Luis Pereira

@jlpereira

mmmmm i think

Im on other branch right now

Matt

@mjy

I'm setting up a couple of PRs to do specs, please don't merge development INTO those branches quite yet.

Yah, we merged image_filter, destroying the branch.

Hernán Lucas Pereira

@LocoDelAssembly

I disabled Travis, check results in Github Actions.

Matt

@mjy

I also need coldp_export merged.

Hernán Lucas Pereira

@LocoDelAssembly

@mjy you need to resolve conflict before Github can start building the pull request

Where communities thrive

People

Repo info

Activity