CMUG WP5.4 CCI LST with Uncertainty propagation

Following the work from CMUG WP5.3 to create a diagnostic with CCI LST data, issue #1896 and branch ESACCI-LST, here we look to include the uncertainty information that the CCI files include.
As before, the main metric will be monthly LST created from the daytime and night time overpass files of Aqua MODIS level 3 data, to be compared to CMIP model.
An region is defined in the recipe (by the user) and the LST is averaged over this region to create a time series of LST.
We will propagate the uncertainty values give in the CCI file to give a total uncertainty value for each time.
The CMIP models are then compared on a plot to the CCI LST with this total uncertainty.
Branch created: CMUG-WP5.4-LST

good stuff @morobking - pls let me and/or @axel-lauer know if any questions! :beer:

good stuff @morobking - pls let me and/or @axel-lauer know if any questions! :beer:

@valeriupredoi Moving the conversation here from emails
I have changed the Cmorizer to return individual files for each day and night variable, ie tsDay and tsNight. These tables for a custom CMOR table on the ESMValCore branch ESACCI_LST_uncerts
When I run ESMValTool I get this error message:
esmvalcore._recipe_checks.RecipeError: Could not create all tasks
following this message:
ERROR   Unable to load CMOR table (project) 'OBS' for variable 'tsUnCorNight' with mip 'Amon'
Is there something else I need to do get the recipe to see the cmor definitions and hence load the data files?

@valeriupredoi @axel-lauer
I'm still having issues getting ESMValTool to find the new variables when running a recipe.
This has worked ok for the cmorizer, but not for the next part.
I'm still getting this message:
ERROR Unable to load CMOR table (project) 'OBS' for variable 'tsUnCorErrNight' with mip 'Amon'

@morobking Theoretically, it should work if you are on the correct branch for ESMValCore (ESACCI_LST_uncerts) and if you installed everything in "developer" mode (pip install --editable '.[develop]'). Did you do that? @valeriupredoi could you maybe take a brief look?

I've tracked this down to a path issue which is now causing a different issue.
My cmorizer creates individual files for each variable, one file for each monthly timestep.
So each netcdf file has one timestep for one variable.
I get this error:
esmvalcore.cmor.check.CMORCheckError: There were errors in variable lst_unc_loc_atm:
time: Frequency  not supported by checker
in cube:
uncertainty from locally correlated errors on atmospheric scales / (kelvin) (time: 1; latitude: 3600; longitude: 7200)
Dimension coordinates:
time                                                                   x            -                -
latitude                                                               -            x                -
longitude                                                              -            -                x
Attributes:
Conventions: CF-1.7
source_file: /work/scratch-nopw/morobking/OBS/Tier2/ESACCI_LST_UNCERTS/OBS_ESACCI_L...
var: tsLocalAtmErrDay
This looks like it comes from the recipe not the diagnostic. I'm sure the diagnostic isnt being run yet.
But this started when I got the issue I previously mentioned sorted.
Is this still a path issue and ESMValTool isn't getting the right custom CMOR tables? Or something else?

@morobking I tried to reproduce this error on Mistral (DKRZ) but had no success. Instead, the preprocessor successfully produced output for variables tsLocalSfcErrDay and tsUnCorErrNight. Here is what I did:

I checkd out ESMValCore branch https://github.com/ESMValGroup/ESMValCore/tree/ESACCI_LST_uncerts and
ESMValTool branch https://github.com/ESMValGroup/ESMValTool/tree/CMUG-WP5.4-LST
successfully ran the cmorizer: cmorize_obs -c ./config-user.yml -o ESACCI_LST_UNCERT
ran recipe_esacci_lst_uncerts.yml : esmvaltool run ./ESMValTool/esmvaltool/recipes/recipe_esacci_lst_uncerts.yml --config_file ./config-user.yml

The ESMValTool preprocessor finishes successfully, but then the script lst_uncert/lst_uncert.py crashes with division by zero. I did get some warnings about the longname being changed for variable tsLocalSfcErrDay. This is probably because the cmorized ESACCI data look a bit strange, i.e. the original variable name and longname are being kept instead of being replaced by the information from the corresponding custom cmor tables. Not sure why, maybe @valeriupredoi has an idea?
Anyway, since the preprocessor successfully produces some output for the uncertainty variables, I would guess your problem might be caused by e.g. ESMValCore not being installed in 'develop mode', the wrong ESMValCore branch being checked out or possible a broken or incompatible conda environment. @valeriupredoi we might need your help here...

cheers @axel-lauer for testing :+1: @morobking can you please post the output of conda list esmvalcore && conda list esmvaltool && which esmvaltool - suspecting Axel is quite right, must be a mismatch between the needed dev Core branch and the actual use of either main or the released version - easy fix at any rate :+1:

@axel-lauer @valeriupredoi Thank you both you looking at this.
Just to say the print(0/0) is deliberate, I know its a lazy way of stopping the code while I'm still developing it.
I do have a path in my config yml file that says:
config_developer_file: /home/users/robking/ESMValTool/config-developer.yml
I think I needed this for the cmorizer to find something, but I honestly forget who told me that. Or if its true.
Running the request from Valeriu:
conda list esmvalcore && conda list esmvaltool && which esmvaltool
packages in environment at /home/users/robking/miniconda3/envs/esmvaltool:

Name                    Version                   Build  Channel
esmvalcore                2.2.0                     dev_0
packages in environment at /home/users/robking/miniconda3/envs/esmvaltool:

Name                    Version                   Build  Channel
esmvaltool                2.2.0                     dev_0
esmvaltool-sample-data    0.0.3                    pypi_0    pypi
~/miniconda3/envs/esmvaltool/bin/esmvaltool

@valeriupredoi Is there a way to fix those errors please?

Hi Rob,
I have opened two pull requests - one in  Core https://github.com/ESMValGroup/ESMValCore/pull/1308 and another in Tool https://github.com/ESMValGroup/ESMValTool/pull/2291 - this way keep things tidy and organized, and allow for multiple pairs of eyes to see and comment on the code and functionalities. Could you please have a look at this comment https://github.com/ESMValGroup/ESMValCore/pull/1308#issuecomment-915100713 and follow those steps to have both your latest branches installed in development mode and repeat your test runs? If there are any issues, I'd suggest posting straight on the relevant PR page so we keep things visible and - what do you know - you may not have to wait 3 weeks for a reply from me since I totally buried the email :grin:


pysd.read_xmile method is not found in latest version of library

Hi, James!
I use this library (0.3.2 version) for executing an XMILE formated models and in older version it has method which can translate XMILE model to Python class, but after update to lates version of this library I can't convert XMILE models, only models from VenSim. Were I can found methods for converting models from XMILE format in new version of this library?

Hey @alexprey,
Thats a great question. I pulled out the XMILE translation (temporarily) because I was putting a lot of effort into some of the more difficult Vensim features, and couldn't keep the XMILE bit up to date. (And I didn't know anyone was using it. =) ) Not an ideal state of affairs, as I imagine there are other folks wanting that functionality too.
We'll need to put some effort into rebuilding the XMILE translation with the new code. It will be some mixture of the old XMILE translation code and the new Vensim parsing structure. We'll also need to write a bunch of new XMILE test models to go in the test repo.
Do you have any interest in being involved, with either writing code or test cases? I could use some help.

Hello @JamesPHoughton this would be a great feature to integrate Stella with python (which uses XMILE by default in version 10). I would like to contribute to it in my spare time (say for 2-3h week).
At the university lab I study (Applied Ecology Laboratory at UTAD), SD models are built in Stella and converted to R scripts with StellaR for integration with data analysis tools in R, but I am python fan (and scipy stack fan) and not very keen on R.
Usually I only make with short scripts (<100 LOC) for data processing and analysis (with pandas and scipy). Nevertheless, I have some experience hacking together some simple python modules, for example I have made a module that creates xmile file with components (stocks, flows, etc) from csv files with input parameters / equations (might clean it up and put it up on git sometime).
Would studying the vensim translator and the XMILE specifications be the first steps to working on the XMILE translator? Note that I have never used vensim, would that be an issue? Is it possible for you to upload the old XMILE translator on a separate repository?
Cheers, Maxim

Hey @quipa,
I wasn't aware of StellaR - thanks for pointing it out!
It would make me exceptionally happy if you were interested in adding the XMILE translation piece. =) I have the feeling there would be some other happy folks out there as well. I don't think not being a vensim user would impact you, but you might find yourself looking at a lot of vensim .mdl files as you figure out what the current translator is doing. =)
Having a look at the old XMILE translator would be a great place to start - you can look at it in this repository's history, here's a link to an older version of xmile2py that has some of the xml reading machinery you might want to reuse, and a link to smile2py which has some of the grammar handling XMILE syntax. (I had separated bits of the parsing into two files, but the current Vensim2Py has all the pieces in the same place. I don't think it really matters one way or the other.)
The rest of PySD has changed so much since I last worked with xmile that you would certainly need to look at the current Vensim2Py for figuring out how to work with the builder and functions.
If I was you, my first steps (step zero is of course to fork the repo so you have your own working copy) would be to to extend or duplicate the integration_test_pysd.py file to run xmile test cases in addition to the Vensim cases it currently runs. (May require extending some of the functions in test_utils.py as well). There are a few xmile test cases already in the test models repo, here's an example where there is a vensim model and a stella model which both do the same thing.
Then you'll have a set of tests ready to go, and as you work you'll be able to see progress reflected in which tests are passing. It makes dev so much easier and faster to have a clean target to be working towards, and it's great for keeping momentum on the project.
I've been using PyCharm for development, you can get a student license, but even the free version is pretty full-featured. It has a nice set of tools for running tests and debugging what doesn't work.
As the tests start to pass, we can merge your git fork back into master, so that everyone can use the new features. As you start adding functionality to the XMILE translator, you'll get to a point where you want to add additional test cases to cover new functionality that you want to handle. (Currently, only a handful of the test cases have both vensim and stella versions - you'd probably want to replicate some of the existing vensim test files in stella, and probably add some new cases.) I can add you to the collaborators on the test repo when you're ready.
The hardest part of the translation process is getting your head around how parsing grammars work. When I was teaching myself, I started using parsimonious to do some really simple practice demos - parsing simple algebraic equations, for example, just to get a feel for it. In the end, it turns into a sort of game, like sudoku, but less repetitive. Geeky, yet satisfying.
When I started with PySD, I'd never even made a python module - just scripts for one-off analysis. It was a huge learning experience to start writing code for other people, using tests, git, etc. It's made me a much better programmer, and would have been a worthwhile project if that knowledge was all I got out of it. I hope that you find something similar if you decide to take it on. =) Shoot me any questions if you get stuck.
Best,
James

Also, you have the coolest website!

Thanks James!
Great to know I can contribute to the project! Thanks for all the pointers. I'll fork the scripts / tests you mentioned, get acquainted with them and let you know as soon as I have something going (might take a few weeks, though). It's quite encouraging to hear about your experience while developing pysd. Would you have any suggestions on learning resources (books, tutorials, etc) for python code testing? That would be a great help to get me up and running!
Yes, our lab is quite cool, hehe ;)! My supervisor and his colleagues developed a framework/methodology (called Stochastic Dynamic Methodology - StDM) where ecological field data (along environmental gradients) is fitted with generalized linear models to derive parameters for dynamic models (SD, ABM and hybrids). These models are use to dynamically model/simulate several dependent variables such as species richness, abundance, biomass, etc. In many cases these models are used to inform adaptive management practices to mitigate impacts from anthropogenic activities, such as dams, wind power farms and such.
As you can see there are some great opportunities for using pysd along with the scipy stack in our workflow and I think a lot opportunities to add machine learning algorithms, with the scikit-learn library.
Regards, Maxim

Hey @JamesPHoughton would @SDXchange SDXlate be of use for this specific feature in your view? I see it hasn't been worked on for a while, but sounds interesting and I noticed you have started it! Cheers, Maxim

@JamesPHoughton just noticed the @SDXchange SDXlate project is written in javascript..! Still will have a look for some ideas.

Hey @quipa,
I particularly like Becoming a better programmer for a practical and readable strategy for getting better at coding.
I'd love to see examples of your work, especially for bringing data to SD models. Any papers I should look at? I wonder if there are examples that could make their way into the PySD Cookbook?
SDXlate is at the moment (to the best of my knowledge) focussing on translating Dynamo code into XMILE - which would be great to combine with a parser for bringing XMILE to Python. Would make a great translation chain for folks with older models! It might give some good ideas for understanding the XMILE syntax. Also check out SDEverywhere which does a Vensim->C translation, might also give some ideas.

Thanks @JamesPHoughton for the book and repository suggestions!
In relation to papers there is a review of StDM from 2013 on works done by members of LEA. There have been some significant adaptations that have been published since then (and one which I'm working on my masters), but the review does describe the essence of StDM.
I'll clean up my hacked up csv-xmile module and scripts, put it up as a repository, so you and others can have a look. Basically it reads in csv files for stocks, flows and variables and constructs an xmile file (using python json-like data structures as intermediates; no classes though). I'm sure there are examples (land cover/use change) that once cleaned up could be in the PySD Cookbook ;).
The main focus of the module + scripts was on automating some common patterns in my model construction (some repeated 10x, which manually would lead to lots of bugs and wasted time) and outputting a XMILE which I would import into Stella for running and tweaking. Since then I've learnt some that some these patterns (not all) can be generalized with Stella modules, so I haven't worked on the module and scripts in a few months.

One question when flows and stocks are translated into functions with a @cache 'step' decorator while  auxiliary variables / functions / constants are translated into functions with @cache 'run' right? Just to understand how input relates to output. Thanks, Max

Close - anything that is expected to change gets cached within the step, so it doesn't recompute in case it is called by multiple functions, so thats stocks, flows, and auxiliaries which depend on other variables. Anything that is constant for the whole simulation gets computed once per run and then the cache value is returned with each call. This is inferred at translate time based upon if the function has any other function calls within it.
I should improve the documentation to the cache decorator class to make that more explicit...

 If you're still working to put together a parser, that should make things easier. =)

Thanks @JamesPHoughton that's great, that will make everything easier! I'm still interested in working on the parser, possibly will be able to this august. I had a look at most of the pysd repository to understand a bit the structure a few weeks ago, will look at the tests to see if it helps.

I think that after merging #151 to master this issue can be closed, because now read_xmile function back again :smile:

Sounds good. A number of failing XMILE tests remain. Would you like to track those as individual issues, group them all together somewhere, or just tackle them?

I think that it's a good idea to create issues for xmile, I create it. What do you think about create a new tags for issues like xmile & vensim?

That's a great idea. I'll add those.


wrapperFactory is not a function

Hi,
Thank you for developing this library.
I have a problem with that.
When I use the paginationFactory function, that will return the following errors.

react-bootstrap-table-next": 1.0.0
react-bootstrap-table2-overlay": 1.0.0
react-bootstrap-table2-paginator": 1.0.0
My config:

Please help me.
Thank you in advance.

@ali-master hello, seems like you use newest releases, what's the version of you React.js ?

BTW, there's not more container.js in 1.0.0, are u sure you upgrade successfully for react-bootstrap-table-next?

Hi @AllenFang,
Yes, I'm sure using the latest version.

@ali-master yes i understand, but the error message show that react-bootstrap-table-next may stay in the legacy version. Could you please remove the node_modules and run install again? thanks

Great job.
That's helped me, thanks
The problem was fixed.

@ali-master Cooool 👍

Hello, I am getting the same error with the filterFactory function even though I removed " node_modules and run install again".

Any idea how I could fix that?
Thank you in advance

Would you share your written code about the table config?

Of course! You mean the Boostrap-table?
Here it is:
`
import React, { Component } from 'react';
import ReactDOM from 'react-dom';
import Routes from './routes';
//import App from './components/landingPage';
import {
graphql,
ApolloProvider,
createNetworkInterface
} from 'react-apollo';
import 'react-bootstrap-table-next/dist/react-bootstrap-table2.min.css';
import { ApolloClient } from 'apollo-client';
import { HttpLink } from 'apollo-link-http';
import { InMemoryCache } from 'apollo-cache-inmemory';
import gql from 'graphql-tag';
import BootstrapTable from 'react-bootstrap-table-next';
import filterFactory, { dateFilter } from 'react-bootstrap-table2-filter';
const httpLink = new HttpLink({
uri: "graphql#execute"
});
let tableQuery = gql{   allBookingHotelRooms{     id     gettingBookingDate     gettingHotel     gettingRoomCategory     gettingAvailabilityPrice     gettingNRoomsAvailable   } }
const cache = new InMemoryCache();
const client = new ApolloClient({
link: httpLink,
cache,
});
class App2 extends Component {
state = {
products: [],
columns: [{
dataField: 'gettingBookingDate',
text: 'Booking Date',
//filter: dateFilter()
},
{  dataField: 'gettingHotel',
text: 'Hotel',
},
{
dataField: 'gettingRoomCategory',
text: 'Room Category'
}, {
dataField: 'gettingAvailabilityPrice',
text: 'Price',
},
{
dataField: 'gettingNRoomsAvailable',
text: 'Nbre # dispos'
}
]
}
render() {
let { data } = this.props
if (data.loading) {
return  Loading...
}
return (
  <div className="container" style={{ marginTop: 50 }}>
    <BootstrapTable
    striped
    hover
    keyField='id'
    data={ this.props.data.allBookingHotelRooms }
    columns={ this.state.columns }
    //filter={ filterFactory() }
    />
  </div>
);

}
}
const TableInfoWithData = graphql(tableQuery, {options: { pollInterval: 20000 },
})(App2);
document.addEventListener('DOMContentLoaded', () => {
ReactDOM.render(

, document.getElementById('example-app'),
)
});
`

everything is working fine until I had filter={ filterFactory() } to the <BootstrapTable /> component

Hey Ali did you see anything wrong with my code? Thank you for the help anyway

Hi @maxvia87,
apologies for the delay in replying.
It works for me.

What's the version of your React.js?
BR.

If you can, please remove your node_module folder and try again with Yarn package manager instead of NPM because npm has many problems like always for installing packages without caching.

Having the same issue, removed node_modules folder and reinstall using NPM, didnt work. reinstall using YARN , still same issue.

@paulalcabasa Please prevent to duplicate reply


Can't deploy to RSC without special rights on the server due to vanity url

The issue
As discussed, I am currently testing how to use GHA to deploy some usual R Markdown related project. I am looking at bookdown currently.
I have tested several deployment methods in https://github.com/cderv/deploy-bookdown-demo
When I tried the connect-publish action on https://beta.rstudioconnect.com, I can't publish because the action has a prerequisite of the API KEY having the right to set vanity url for a content. And this is not the case by default: https://docs.rstudio.com/connect/admin/appendix/configuration/#Authorization.PublishersCanManageVanities
That means, the content is created correctly on RSC but we have an error because the vanity path the action is creating for a new content can't be set. here is the error:
https://github.com/cderv/deploy-bookdown-demo/runs/1533824331?check_suite_focus=true#step:9:5530
Discussion about the context and possible solutions
One solution would be to have the setting change on the server, but I don't think that connect-publish action should be dependent on a server setting
I think this should evolve. I understand main questions are:

How to identify a content ?
How to create a new content (no identifier yet) and still republishing into it later without changing anything ?

The action here tries to deal with both, as the rsconnect::deployApp() function.  Let's recall that base principle for publishing on connect is (based on the API)

Create a content -> get a GUID
Deploy a bundle to the content
Activate the content

And I am guessing you are using that in the action too using the API right ?
About "How to identify a content ? ", AFAIK an app as several identifier

A GUID

internal thing but shown in the info tab for every app.
Unique server-wide.
Used in the API to identify a content.

An ID

which in the default url of the app page.
Unique server-wide, and incremental.

A name

internal thing also I believe
provided to rsconnect::deployApp or the API when creating a content
registered in the DCF file in rsconnect folder
Unique within the server or maybe within an account (which would make [ (users/api key) / (name) ] a unique thing)

A vanity path (optional)

if set, it will indeed be unique.
Otherwise, it is the id (/content/<id>)

What about those choice for the actions:

Currently the action is using the Vanity Url which is the only optional identifier - that is causing the issue above. You need admin rights or non default config on RSC server.
GUID and ID can't be chosen by the user - they are automatically attributed to new content. That means, for a new first deployment, the action would have to cache the information to be able to republish later. Like rsconnect package which cache information in dcf in the rsconnect folder.
GHA cache could be use the same way - but is it enough reliable ? If this info is lost, the ID or GUID would need to be set manually (related to #11). They are useful for deploying on an existing content though.
That leaves us with the unique app name. A user could decide which name to set, it has to be unique for RSC server-wide (or account-wide). So I think it is good properties for what is need for this action.
Only drawback: It don't seem to be useful to use the action to publish on existing content (#11) as it does not seem easy to retrieve the app unique name identifier - I can't find the info the the INFO pane in RSC - only title (non unique I think), GUID and ID (in the url). You could retrieve by the API but... you need the GUID.

So at last, maybe not using the vanity url but the app name instead would be enough for the connect-publish action. Taking the example in #11
      - name: Publish the book
        uses: rstudio/actions/connect-publish@main
        with:
          api-key: ${{ secrets.RSC_BETA_TOKEN }}
          url: https://beta.rstudioconnect.com/
          access-type: logged_in
          dir: _book
          name: demo-bookdown-deploy

I just don't know how easy it would be using the API to find if the content exist. It depends if the name is unique server-wide or account-wide maybe.
Anyway, opening this for discussion. You may have already thoughts on this.

The current behavior should be that each directory may be specified with an app identifier suffix such as a vanity path, name, or GUID, e.g.:
      - name: Publish the book
        uses: rstudio/actions/connect-publish@main
        with:
          api-key: ${{ secrets.RSC_BETA_TOKEN }}
          url: https://beta.rstudioconnect.com/
          access-type: logged_in
          dir: _book:demo-bookdown-deploy

In the case of publishing to an RStudio Connect server where vanity paths may not be changed by users with the publisher role, the request to update will fail, but publishing will continue. This is the reasoning behind the introduction of require-vanity-path, which changes the behavior to interrupt publishing when the vanity path cannot be updated. Please reopen if you're still seeing unexpected behavior :grin:

Great, thanks for the addition of require-vanity-path !
That is indeed working - vanity url is still trying to be set even if app name is provided (not a vanity url) but the request is failing and the deployment continues. I am still getting an error but that is another issue I think.


'make cluster-up' fails on mac

make cluster-up failed with error on mac
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "process_linux.go:86: executing setns process caused "exit status 21"": unknown
Docker Version 18.03.0-ce-mac60 (23751)
more specifically this is the point of failure:
docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock kubevirtci/cli@sha256:b0023d1863338ef04fa0b8a8ee5956ae08616200d89ffd2e230668ea3deeaff4 run --reverse --nodes 1 --random-ports --background --prefix os-3.9.0-alpha.4 --registry-volume kubevirt_registry --base kubevirtci/os-3.9@sha256:c214267c1252e51f5ea845ac7868dbc219c63627e9f96ec30cc0a8e9e6e9fc0d
os-3.9.0-alpha.4-node01
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "process_linux.go:86: executing setns process caused "exit status 21"": unknown
5fdd4a296738818ab1bede54ab714ccf33c249995fadf4b9a8d6fc851348614b
5fdd4a296738818ab1bede54ab714ccf33c249995fadf4b9a8d6fc851348614b
73d33961853ad11b67597f3c94ba958a95c49bd01e3294a235258a5eaca269dd
73d33961853ad11b67597f3c94ba958a95c49bd01e3294a235258a5eaca269dd
4d02a709b78fe2d62428fb6c2f690fc2be3ca81b02e25fe8d13efeb8fe263d08
4d02a709b78fe2d62428fb6c2f690fc2be3ca81b02e25fe8d13efeb8fe263d08
os-3.9.0-alpha.4-node01

@mpolednik if I remember correctly, you have a mac. Could you try to find out why
PROVIDER=os-3.9.0-alpha.4
make cluster-up

fails on mac?

It looks like it resides within the ci container at kubevirt/kubevirtci. I'm looking more into how that container works. I think it has something to do with being unable to create /dev/kvm instead container when it's on OSX but not entire sure yet. Will update when I discover more.

/proc/misc on containers on OSX do not have an entry for kvm while containers on linux do. So I'm pretty sure this stems from the KVM dependency that OSX does not support.

@gageorsburn the /dev/kvm related logic is here: https://github.com/kubevirt/kubevirtci/blob/master/base/scripts/vm.sh#L80.
Is intel haxm supported on mac? That might be a suitable alternative.

@rmohr Yeah I had found that when I looked into it and determined that to be the root cause. I was not able to get Intel haxm working with qemu.
I did come across https://github.com/geohot/kvm-kext but did not test it out.  Another thing that could be done is to look into OSX's hypervisor.framework, but I don't know how much value it will add, or we probably could just do without hardware acceleration for OSX.

I just ran into this as well:
++ local 'params=--nodes 1 --memory 5120M --cpu 5 --random-ports --background --prefix k8s-1.10.4 --registry-volume kubevirt_registry kubevirtci/k8s-1.10.4@sha256:b60a61ca03a1a6c504481020709a04f65e4dd9c929a8bcad18821c5f80d1b2b6  --ocp-port 8443'
++ [[ '' =~ windows.* ]]
++ [[ '' =~ openshift.* ]]
++ echo --nodes 1 --memory 5120M --cpu 5 --random-ports --background --prefix k8s-1.10.4 --registry-volume kubevirt_registry kubevirtci/k8s-1.10.4@sha256:b60a61ca03a1a6c504481020709a04f65e4dd9c929a8bcad18821c5f80d1b2b6 --ocp-port 8443
+ docker run --privileged --net=host --rm -v /var/run/docker.sock:/var/run/docker.sock kubevirtci/gocli@sha256:df958c060ca8d90701a1b592400b33852029979ad6d5c1d9b79683033704b690 run --nodes 1 --memory 5120M --cpu 5 --random-ports --background --prefix k8s-1.10.4 --registry-volume kubevirt_registry kubevirtci/k8s-1.10.4@sha256:b60a61ca03a1a6c504481020709a04f65e4dd9c929a8bcad18821c5f80d1b2b6 --ocp-port 8443
Downloading ......
Downloading ......
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "process_linux.go:86: executing setns process caused \"exit status 21\"": unknown
OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown
provisioning node node01 failed
make: *** [cluster-up] Error 1

@gaahrdner Yup it's because there is no KVM support on OSX. The best workaround is to use the external provider to use an external kubernetes cluster.


Add some funny food recipes

I would like to help! What do you define as a funny food recipe? Something that sounds funny or interesting recipes? Fictional or real-world recipes?
eg) Yumyumberry Pie or Bubble and Squeak?

Where can i check item list? and Can i make some items?

@RhizobiumExpat Great! I think interesting real world recipe will make very fun. :)
@Nerd-Bear You can see item drop information at data/monters.csv and you can see the recipes at items.py.

Then i'll try this! :)

Can I change HP10Food class to
`class HPFood(Food):
def init(self, amount):
self.heal_amount = amount
def execute(self, avatar):
    avatar.hp = min(avatar.max_hp, avatar.hp + self.heal_amount)
    return avatar, {
        'type': 'item_use',
        'item': self.ticker_name,
        'status_change': f'HP +{self.heal_amount}'
    }` like this?

I think give heal amount each foods.

@Nerd-Bear I think it is better than now. :) let's do that.

#84

For a while, anyone can add fun recipes even if @Nerd-Bear's PR was merged. I'll keep this issue live.

I added 3 recipes and made some typo fixes, then rearranged the classes into different tiers for improved readability. I'm sorry I couldn't add many funny recipes though. I wasn't sure if I was allowed to add more types of ingredients so I only made do with the drops available from the current monsters.
A few questions though:
Is every recipe supposed to be made from 3 items? I added one food that only uses 2 (Steak Sandwich only uses BRED and STEK).
What does RKST stand for? I searched everywhere for the documentation for what the ingredient acronyms are supposed to represent. Some are more obvious than others but I couldn't figure out what RKST and LMIL are supposed to be. I would guess that it would get more confusing as more items are added.


Make unique labels using a timestamp for svg elements.

Addresses https://github.com/gibiansky/IHaskell/issues/877 and issues raised in https://github.com/gibiansky/IHaskell/pull/1009.

Can you rebase on top of current master please? Also, did you consider using something like Data.Unique instead of the timestamp?

While Data.Unique is a good idea, it would not be preserved between sessions, so it would become non-unique if saving and reopening. The best idea would be to use the cell number, but I don't know how to get that. So if it's cell [34] then the results of that cell would always be 34 for the label.

Rebased.

Looks like the check failed because of stack-8.0. I'm changing getSystemTime to getCurrentTime and using the date + picoseconds versus seconds from unix epoch as a workaround.

Used earlier version of time for stack-8.0. The id label, using date and picoseconds, contains "-" and "." characters, but it seems to meet specs so I left it as is.

Thanks!


Fix doc comment

Looks like some collateral damage from an int -> i32 search and replace.

Thanks very much. I should be more careful with my vim use! :smile:


DOM QEs

Currently they're set to 1.0 for photon level tests. Will need to set them to the actual DOM's QE from GCD file in the future

In PR #6 , I converted the histo-generation script to just output a "raw data" pickle file and we'll then have a separate script to generate the histos.
The raw data has (per DOM) photon time, wavelength, coszen, and weight (where weight includes DOM wavelength acceptance, Cherenkov spectrum, and DOM angular acceptance effects). Also in that file is the total number of simulations so that can be divided out later.
So the (yet-to-be-written) script that generates the histos can then apply the DOM-specific quantum efficiencies contained in the GCD file (i.e., rde[string_idx, dom_idx] * 0.25).


Jobs try to run on Windows

What steps did you take and what happened:
I am running a cronjob which calls starboard with -v3 kube-bench but notice that some jobs are unable to run as they are trying to execute on windows nodes.
P.S. Thanks for the amazing tool :D
What did you expect to happen:
The windows nodes are tainted.
Anything else you would like to add:
N/A
Environment:

Starboard version (use starboard version): 0.6.0
Kubernetes version (use kubectl version): 1.17.3
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 10.15

👋 @sylus Thank you for opening this issue. What would be desired behaviour in your case? Ignoring windows nodes (or in general any tainted node) and run kube-bench only on linux nodes?

Yup @danielpacak i think that would be the solution i'd like to see :D

I'd like to test this, and try to do the fixes for this issue.
Thanks, @sylus, It seems that kube-bench doesn’t  support windows nodes. More details


feat(ts): adds connect-es generated code (#184)

This PR introduces necessary updates to support connect-es in addition to ts-proto  generated code which is needed for our indexer application. It includes the generation of provider code and updates to the package exports to include connect-es modules. Additionally, the directory structure has been updated along with the dynamic exports generator script to reflect these changes.
Key Changes

Provider Code Generation: Added necessary configurations to generate provider code using connect-es.
Package Exports: Updated to include connect-es exports, ensuring that all generated modules are correctly exposed for use in the application.
Directory Structure: Revised the project's directory structure to accommodate the new code generation strategy and organization.
Scripts Update:

make/codegen.mk: Updated commands for connect-es generation alongside existing ts-proto generation.
script/protocgen-legacy.sh: Modified to support the new generation requirements.
ts/script/generate-exports.js: Enhanced to dynamically generate exports based on the updated directory structure and generation strategies.

Implementation Details
The majority of changes in this PR involve file movements to better organize the generated code. The scripts mentioned above have been updated to facilitate these changes and to automate the generation and export of modules.
Notes
Most changes in this PR are related to the restructuring of files and directories; the most relevant code changes are found in the scripts listed above. It is recommended to review these scripts for detailed understanding of the new generation and export processes.

Would be nice to have examples of how to use both grpc clients in the ts README

Would be nice to have examples of how to use both grpc clients in the ts README

Ok, but I’ll attempt to avoid this pr first as discussed


Can we generate images by using the bot ?

Is it possible to generate images by using this bot , i mean text to image support

It's not possible by current version of Ollama, so no


how to reproduce the experiment of your paper

Hello, the author. I am very interested in the paper of "Semantic fuzzing with zest", and I want to reproduce the experiment mentioned in your paper. May I ask where I should start? (such as where the data set can be found, and whether the duplicated code can be found in the JQF framework), I really hope to get your help.Have a good day.

The replication package can be found here:
https://dl.acm.org/do/10.1145/3339069/abs/.
Unzip the large file (754MB) and go through the Readme.txt. Most of the
data and scripts are in a Docker container for reproduction.
Note that this package embeds an older version of JQF which was current
when our papers on JQF and Zest were published. If you are using these
tools in new research, I would recommend using the latest versions.
On Tue, Apr 6, 2021, 4:44 AM zheng-yan-max @.***> wrote:

Hello, the author. I am very interested in the paper of "Semantic fuzzing
with zest", and I want to reproduce the experiment mentioned in your paper.
May I ask where I should start? (such as where the data set can be found,
and whether the duplicated code can be found in the JQF framework), I
really hope to get your help.Have a good day.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rohanpadhye/JQF/issues/132, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAJQMSMHDFDEENJB63XOKDTHLCWPANCNFSM42OI6JYA
.

In the current repository, some of our experiment scripts may be found in
https://github.com/rohanpadhye/JQF/tree/master/scripts/experiments as well.
These scripts are not actively maintained, but are a good starting point if
you want to run stuff with the latest version on the same benchmarks as in
the paper.
On Tue, Apr 6, 2021, 8:40 AM Rohan Padhye @.***> wrote:

The replication package can be found here:
https://dl.acm.org/do/10.1145/3339069/abs/.
Unzip the large file (754MB) and go through the Readme.txt. Most of the
data and scripts are in a Docker container for reproduction.
Note that this package embeds an older version of JQF which was current
when our papers on JQF and Zest were published. If you are using these
tools in new research, I would recommend using the latest versions.
On Tue, Apr 6, 2021, 4:44 AM zheng-yan-max @.***>
wrote:

Hello, the author. I am very interested in the paper of "Semantic fuzzing
with zest", and I want to reproduce the experiment mentioned in your paper.
May I ask where I should start? (such as where the data set can be found,
and whether the duplicated code can be found in the JQF framework), I
really hope to get your help.Have a good day.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rohanpadhye/JQF/issues/132, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAJQMSMHDFDEENJB63XOKDTHLCWPANCNFSM42OI6JYA
.

The replication package can be found here: https://dl.acm.org/do/10.1145/3339069/abs/. Unzip the large file (754MB) and go through the Readme.txt. Most of the data and scripts are in a Docker container for reproduction. Note that this package embeds an older version of JQF which was current when our papers on JQF and Zest were published. If you are using these tools in new research, I would recommend using the latest versions.
…
On Tue, Apr 6, 2021, 4:44 AM zheng-yan-max @.***> wrote: Hello, the author. I am very interested in the paper of "Semantic fuzzing with zest", and I want to reproduce the experiment mentioned in your paper. May I ask where I should start? (such as where the data set can be found, and whether the duplicated code can be found in the JQF framework), I really hope to get your help.Have a good day. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#132>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAJQMSMHDFDEENJB63XOKDTHLCWPANCNFSM42OI6JYA .

Thank you very much for all the useful information you provided.


Fix inconsistencies in infoboxes

Currently some infoboxes are:
Note: blah blah

while others are
Note:
blah blah

Hence, this PR aims to fix the inconsistencies by adding a <br> to all infoboxes.

Codecov Report
Base: 78.42% // Head: 78.42% // No change to project coverage :thumbsup:

Coverage data is based on head (a897cea) compared to base (55d21ff).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #195   +/-   ##
=========================================
  Coverage     78.42%   78.42%
  Complexity      849      849
=========================================
  Files           118      118
  Lines          2568     2568
  Branches        324      324
=========================================
  Hits           2014     2014
  Misses          428      428
  Partials        126      126

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Correct delivery_test_kitchen typo

Trivial rename of resource file

Closing. Sent through Delivery in https://delivery.chef.co/e/chef/#/organizations/Delivery-Build-Cookbooks/projects/delivery-sugar/changes/795c70e5-2b81-490d-8cdd-18e054266004


[FEA] Return multi-column "by" as a single struct column

Decided policy for name collisions:

In the immediate short term, I'd say the struct column name could be the original names concatenated together.
If there's already a column named that, throw.

Closed in https://github.com/rapidsai/node-rapids/pull/108


Add graph models

Added

Added Graph.
Added RootedGraph.

Changed

Moved models outside the task module.
Updated dependencies.

Codecov Report

Merging #112 (d8d8800) into master (f70d741) will increase coverage by 1.68%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
+ Coverage   95.10%   96.79%   +1.68%
==========================================
  Files          91       30      -61
  Lines        1451      530     -921
  Branches      175       36     -139
==========================================
- Hits         1380      513     -867
+ Misses         67       16      -51
+ Partials        4        1       -3

Flag
Coverage Δ

cuaktask
89.47% <ø> (ø)

iocuak
?

porygon
98.58% <ø> (ø)

porygon-typeorm
98.90% <ø> (ø)

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

Impacted Files
Coverage Δ

...k/src/graph/models/domain/NodeExecutionOperator.ts
0.00% <ø> (ø)

...lectMetadata/utils/domain/updateReflectMetadata.ts

...ssMetadata/utils/domain/getDefaultClassMetadata.ts

...s/iocuak/src/container/modules/api/ContainerApi.ts

...tainerModule/utils/api/convertToContainerModule.ts

.../iocuak/src/classMetadata/decorators/injectFrom.ts

...ls/cuaktast/ContainerModuleLoadFromMetadataTask.ts

...rModule/utils/api/convertToContainerModuleAsync.ts

...els/cuaktast/ContainerModuleCreateInstancesTask.ts

...cuaktask/ContainerInstanceServiceImplementation.ts

... and 52 more

Continue to review full report at Codecov.

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


AIP-3158: Add in ability to override the template handler for a BaseOp.

Add in ability to override the default template converting function, by default this is _op_to_template, see here. This converts a kfp.dsl.ContainerOp to an Argo Workflow.spec.template dictionary.
I expect we can use this in the Metaflow on KFP codebase to support:

podSecurityContext - Needed by Spark workstream to read AWS IAM credential token file mounted within container by only accessible via the root user.
podSpecPatch - Not really needed yet (except maybe to set Spark driver pod resources dynamically if running in client mode), but unlocks dynamic setting of CPU, Memory and GPU resources within an Argo Workflow at runtime (currently we're limited to just compile time!).

This would unlock RentZest to dynamically allocate step pod sizes based on county data partition sizes.

You'd use this by doing:
from typing import Dict
from kfp.compiler._op_to_template import _op_to_template
from kfp.dsl._container_op import BaseOp

def my_template_handler(op: BaseOp) -> Dict:
    template = _op_to_template(op)
    # See https://argoproj.github.io/argo/fields/#podsecuritycontext
    # fsGroup will set the ownership of any mounted files to the group ID supplied, 65534 is the
    # default gid for default "nogroup" which all users in a linux system get added to.
    template['securityContext'] = {"fsGroup": 65534}
    return template

Then within the KFP plugin within Metaflow we'd define that and use it:
...
# See https://github.com/zillow/metaflow/blob/feature/kfp/metaflow/plugins/kfp/kfp.py#L331
step_to_kfp_component_map[step_name] = build_kfp_component(node, task_id)
step_to_kfp_component_map[step_name].set_template_handler(my_template_handler)
...

What will happen now when the flow is compiled to Argo Workflow YAML the spec.templates[...].securityContext field will be set with permissions needed to read the AWS IAM token file!
To do:

[x] Add in API for amending Argo workflow templates.
[x] Push PR up to kfp Open Source, see https://github.com/kubeflow/pipelines/pull/4955
[ ] Discuss how best to introduce integration for this in Metaflow, need to speak with @talebzeghmi on this.

PS. I'm discussing with Xiaowei about setting up a dedicated zservice group so we don't rely on the default nogroup :)

Closing as not needed. Will instead run Spark as root for the MVP.

Closing as not needed. Will instead run Spark as root for the MVP.


Terragrunt Aplly-ALL doesnt work multiple errors

[terragrunt] [/home/genaker/Downloads/Magento-Terraform-Infrastructure(3)/magento-terraform-infrastructure/us-west-1/mysql-master-rds] 2020/03/24 22:18:39 Running command: terraform apply -input=false -input=false -auto-approve
module.db_instance.data.aws_iam_policy_document.enhanced_monitoring: Refreshing state...

Error: first character of "name_prefix" must be a letter

  on modules/db_option_group/main.tf line 1, in resource "aws_db_option_group" "this":
   1: resource "aws_db_option_group" "this" {

Error: only alphanumeric characters and hyphens allowed in "name_prefix"

  on modules/db_option_group/main.tf line 1, in resource "aws_db_option_group" "this":
   1: resource "aws_db_option_group" "this" {

Error: only lowercase alphanumeric characters and hyphens allowed in parameter group "name_prefix"

  on modules/db_parameter_group/main.tf line 33, in resource "aws_db_parameter_group" "this":
  33: resource "aws_db_parameter_group" "this" {

Error: first character of parameter group "name_prefix" must be a letter

  on modules/db_parameter_group/main.tf line 33, in resource "aws_db_parameter_group" "this":
  33: resource "aws_db_parameter_group" "this" {

aws_lb.this[0]: Creating...
[terragrunt] [/home/genaker/Downloads/Magento-Terraform-Infrastructure(3)/magento-terraform-infrastructure/us-west-1/mysql-master-rds] 2020/03/24 22:18:43 Module /home/genaker/Downloads/Magento-Terraform-Infrastructure(3)/magento-terraform-infrastructure/us-west-1/mysql-master-rds has finished with an error: Hit multiple errors:
exit status 1

Error: Error creating application Load Balancer: ValidationError: At least two subnets in two different Availability Zones must be specified
	status code: 400, request id: bee0f9bb-e951-41f9-9ea0-969803b89e32

  on main.tf line 1, in resource "aws_lb" "this":
   1: resource "aws_lb" "this" {

aws_lb.this[0]: Creating...
2020/03/24 22:41:10 [DEBUG] aws_lb.this[0]: applying the planned Create change
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] setting computed for "subnets" from ComputedKeys
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] setting computed for "security_groups" from ComputedKeys
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] setting computed for "subnet_mapping" from ComputedKeys
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] ALB create configuration: {
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   IpAddressType: "ipv4",
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   Name: "mutual-foal",
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   Tags: [{
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:       Key: "Name",
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:       Value: "mutual-foal"
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:     }],
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   Type: "application"
2020-03-24T22:41:10.923-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: }
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] [aws-sdk-go] DEBUG: Request elasticloadbalancing/CreateLoadBalancer Details:
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: ---[ REQUEST POST-SIGN ]-----------------------------
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: POST / HTTP/1.1
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Host: elasticloadbalancing.us-west-1.amazonaws.com
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: User-Agent: aws-sdk-go/1.29.24 (go1.13.7; linux; amd64) APN/1.0 HashiCorp/1.0 Terraform/0.12.24 (+https://www.terraform.io)
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Content-Length: 152
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Authorization: AWS4-HMAC-SHA256 Credential=AKIAUZMFRD25Q7PATRG4/20200325/us-west-1/elasticloadbalancing/aws4_request, SignedHeaders=content-length;content-type;host;x-amz-date, Signature=db70cb9eb32e73b9650d8dc7a7eb6c0d070dda8b467be9d1091ecc48f2e35901
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Content-Type: application/x-www-form-urlencoded; charset=utf-8
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: X-Amz-Date: 20200325T054110Z
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Accept-Encoding: gzip
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Action=CreateLoadBalancer&IpAddressType=ipv4&Name=mutual-foal&Tags.member.1.Key=Name&Tags.member.1.Value=mutual-foal&Type=application&Version=2015-12-01
2020-03-24T22:41:10.924-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: -----------------------------------------------------
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] [aws-sdk-go] DEBUG: Response elasticloadbalancing/CreateLoadBalancer Details:
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: ---[ RESPONSE ]--------------------------------------
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: HTTP/1.1 400 Bad Request
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Connection: close
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Content-Length: 337
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Content-Type: text/xml
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: Date: Wed, 25 Mar 2020 05:41:10 GMT
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: X-Amzn-Requestid: 97a7dad9-a48e-4131-8b90-8f82981c0c32
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: -----------------------------------------------------
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: 2020/03/24 22:41:10 [DEBUG] [aws-sdk-go] <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2015-12-01/">
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   <Error>
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:     <Type>Sender</Type>
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:     ValidationError
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:     <Message>At least two subnets in two different Availability Zones must be specified</Message>
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   </Error>
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4:   <RequestId>97a7dad9-a48e-4131-8b90-8f82981c0c32</RequestId>
2020-03-24T22:41:10.950-0700 [DEBUG] plugin.terraform-provider-aws_v2.54.0_x4: </ErrorResponse>
``

The first error is the named validation problem.
Second Elb Module Terraform  problem

First assumption is that you have named your DB instance starting with the letter. Text labels are passed into module as argument (name_prefix) without validation (there is WIP issue already - #18).
ALB is failing because you have to specify "At least two subnets in two different Availability Zones must be specified". If you have edited this manually, make sure you set it correctly. Normally VPC resources like subnets are created across all available AZs.
If problem persists, please share a link to your blueprint by email.

Yes, but we can't manage Az in the cloud craft. It is something that scripts (module.tf) do during the import. Name prefix is
The name of the RDS instance, if omitted, Terraform will assign a random, unique identifier
type: string
identifier = "MySQL-Master-RDS"
name_prefix is not part of terragrunt configuration

Hi! I still struggling with this error.
Error: first character of "name_prefix" must be a letter
  on modules/db_option_group/main.tf line 1, in resource "aws_db_option_group" "this":
   1: resource "aws_db_option_group" "this" {

Error: only alphanumeric characters and hyphens allowed in "name_prefix"
  on modules/db_option_group/main.tf line 1, in resource "aws_db_option_group" "this":
   1: resource "aws_db_option_group" "this" {

Error: only lowercase alphanumeric characters and hyphens allowed in parameter group "name_prefix"

  on modules/db_parameter_group/main.tf line 33, in resource "aws_db_parameter_group" "this":
  33: resource "aws_db_parameter_group" "this" {

Error: first character of parameter group "name_prefix" must be a letter

  on modules/db_parameter_group/main.tf line 33, in resource "aws_db_parameter_group" "this":
  33: resource "aws_db_parameter_group" "this" {

And the weirdest one is ALB doesn't work
Error: Error creating application Load Balancer: ValidationError: At least two subnets in two different Availability Zones must be specified
	status code: 400, request id: 3cbf0f7c-24bc-4461-b9db-2a2a91886a49

  on main.tf line 1, in resource "aws_lb" "this":
   1: resource "aws_lb" "this" {

I'm trying to fix parameter name by fix name

RDS identifier is using wrong characters inside but since that value is used to create some other resources you need to update it to satisfy these error messages - "only lowercase alphanumeric characters and hyphens", "first character ... must be a letter".
ALB error is probably related to a missing subnets argument which should look like this:
inputs {
  # ... omitted
  subnets = dependency.vpc.outputs.public_subnets
}

If not, please show inputs in alb directory and I will try to help.

###########################################################
# View all available inputs for this module:
# https://registry.terraform.io/modules/terraform-aws-modules/alb/aws/5.1.0?tab=inputs
###########################################################
inputs = {
  # The resource name and Name tag of the load balancer.
  # type: string
  name = "novel-husky"

}

###########################################################
View all available inputs for this module:
https://registry.terraform.io/modules/terraform-aws-modules/alb/aws/5.1.0?tab=inputs
###########################################################
inputs = {
The resource name and Name tag of the load balancer.
type: string
name = "guided-lemur"
}

I have fixed RDS issue by removing "-" sign from the name.
but this error a little bit weird :
Error: Error creating application Load Balancer: ValidationError: At least two subnets in two different Availability Zones must be specified
	status code: 400, request id: 4844ad75-4619-4565-83c5-c80c2b44faf1

  on main.tf line 1, in resource "aws_lb" "this":
   1: resource "aws_lb" "this" {

"public_subnets": {
      "value": [
        "subnet-09d599df3f68cd2f5",
        "subnet-01920b65109f712f0"
      ],
      "type": [
        "tuple",
        [
          "string",
          "string"
        ]
      ]
    },

Add subnets = dependency.vpc.outputs.public_subnets into alb.
It was not specified automatically, because your ALB was not belonging to a VPC in a diagram, I suppose.

It is belonging to the VPC... it just doesn't generate it
Can you also provide how to add these values they are missing also .
I checked old version
security_groups = [] # @tfvars:terraform_output.security-group_5.this_security_group_id.to_list

  # A list of subnets to associate with the load balancer. e.g. ['subnet-1a2b3c4d','subnet-1a2b3c4e','subnet-1a2b3c4f']
  # type: list
  subnets = ["subnet-00703b43f38b8f971","subnet-00703b43f38b8f971","subnet-0c2dd15008a01bb51"] # @tfvars:terraform_output.vpc.public_subnets

  # VPC id where the load balancer and other resources will be deployed.
  # type: string
  vpc_id = "" # @tfvars:terraform_output.vpc.vpc_id

I have this dependencies:
dependencies {
paths = ["../vpc-cloud", "../loadbalancer-internet-securitygroup"]
}

it is an example - https://app.cloudcraft.co/view/f8abab63-0007-4ea2-8ea8-b9186d3259f1?key=iBtyR4AsIr9jWfy-sJARUg
it doesn't add a subnet to ELB

RDS name_prefix issue fixed after setting name to  "mysql" without any symbols instead of "mysql-rds".

A similar issue is when a security group is named ...-sg (and ...-vpc for VPC, if I remember correctly now).
Pretty weird requirements by AWS.

After run "terragrunt apply-all" but load balancer doesn't have target groups/listeners created and so no instances are load-balanced

That is because a lot of important information is not available in cloudcraft and user has to add it themself manually.
Here you can see an example of ALB module usage - https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/examples/complete-alb/main.tf

Thanks for your replay. I will chack
On Wed, May 13, 2020 at 2:36 PM Anton Babenko<EMAIL_ADDRESS>wrote:

That is because a lot of important information is not available in
cloudcraft and user has to add it themself manually.
Here you can see an example of ALB module usage -
https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/examples/complete-alb/main.tf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/antonbabenko/modules.tf-lambda/issues/28#issuecomment-628258739,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGJNZUXXYYOPEEH27QNUSTRRMHFBANCNFSM4LTGL5JQ
.

That is because a lot of important information is not available in cloudcraft and user has to add it themself manually.
Here you can see an example of ALB module usage - https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/examples/complete-alb/main.tf

It doesn't appear that modules covers the use case of using named or aliased security groups, yet.
Also, as most people are designing small architectures right now, does it make sense to just create the subnets for them, baked into the terraform?
Some strategies:

AWS Services in same subnet (Database subnet, compute subnet, etc.)
All in one subnet (not great, but people do this)
Have subnets match up with Security Groups (this would probably be a pain to manage, option 1 seems best)


Error on pilot

New Issue Checklist

[x] Updated fastlane to the latest version
[ ] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I run fastlane pilot and now it fails, it used to work. I am running Fastlane 2.111.
I get Spaceship::UnexpectedResponse in post_for_testflight_review
Complete output when running fastlane, including the stack trace and command used

[18-Dec-2018 08:18:50 | [08:18:50]: Login to App Store Connect<EMAIL_ADDRESS>-- | --
18-Dec-2018 08:18:52 | [08:18:52]: Login successful
18-Dec-2018 08:18:53 | [08:18:53]: Ready to upload new build to TestFlight (App: xxxxx)...
18-Dec-2018 08:18:54 | [08:18:54]: Going to upload updated app to App Store Connect
18-Dec-2018 08:18:54 | [08:18:54]: This might take a few minutes. Please don't interrupt the script.
18-Dec-2018 08:20:14 | [08:20:14]: iTunes Transporter successfully finished its job
18-Dec-2018 08:20:14 | [08:20:14]: --------------------------------------------------------------------
18-Dec-2018 08:20:14 | [08:20:14]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
18-Dec-2018 08:20:14 | [08:20:14]: --------------------------------------------------------------------
18-Dec-2018 08:20:14 | [08:20:14]: Successfully uploaded the new binary to App Store Connect
18-Dec-2018 08:20:14 | [08:20:14]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
18-Dec-2018 08:20:27 | [08:20:27]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:20:58 | [08:20:58]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:21:29 | [08:21:29]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:22:00 | [08:22:00]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:22:31 | [08:22:31]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:23:01 | [08:23:01]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:23:32 | [08:23:32]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:24:03 | [08:24:03]: Waiting for App Store Connect to finish processing the new build (0.1.2 - <IP_ADDRESS>)
18-Dec-2018 08:24:34 | [08:24:34]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:25:04 | [08:25:04]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:25:36 | [08:25:36]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:26:06 | [08:26:06]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:26:37 | [08:26:37]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:27:08 | [08:27:08]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:27:38 | [08:27:38]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:28:09 | [08:28:09]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
18-Dec-2018 08:28:40 | [08:28:40]: Successfully finished processing the build 0.1.2 - <IP_ADDRESS>
18-Dec-2018 08:28:44 | [08:28:44]: Successfully set the changelog for build
18-Dec-2018 08:28:44 | [08:28:44]: Distributing new build to testers: 0.1.2 - <IP_ADDRESS>
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 | Looking for related GitHub issues on fastlane/fastlane...
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 | /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/spaceship/lib/spaceship/test_flight/client.rb:330:in `handle_response': [!]  (Spaceship::UnexpectedResponse)
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 | Not Found
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 | Copyright © 2015 Apple Inc. All rights reserved.
18-Dec-2018 08:28:45 | Terms of ServicePrivacy Policy
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 |
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/spaceship/lib/spaceship/test_flight/client.rb:72:in `post_for_testflight_review'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/spaceship/lib/spaceship/test_flight/build.rb:217:in `submit_for_testflight_review!'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/build_manager.rb:183:in `distribute_build'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/build_manager.rb:108:in `distribute'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/build_manager.rb:61:in `upload'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/commands_generator.rb:66:in `block (2 levels) in run'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/commands_generator.rb:166:in `run'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/pilot/lib/pilot/commands_generator.rb:18:in `start'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/fastlane/lib/fastlane/cli_tools_distributor.rb:100:in `take_off'
18-Dec-2018 08:28:45 | from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.111.0/bin/fastlane:23:in `'
18-Dec-2018 08:28:45 | from /usr/local/bin/fastlane:22:in `load'
18-Dec-2018 08:28:45 | from /usr/local/bin/fastlane:22:in `'
18-Dec-2018 08:28:45 | An error occurred when executing task 'Fastlane-Deliver'.
18-Dec-2018 08:28:45 | Error: One or more errors occurred.
18-Dec-2018 08:28:45 | fastlane: Process returned an error (exit code 1).]

Environment

[
### Stack
| Key                         | Value                                                                                |
| --------------------------- | ------------------------------------------------                                                         -------------- |
| OS                          | 10.14                                                                                |
| Ruby                        | 2.3.7                                                                                |
| Bundler?                    | false                                                                                |
| Git                         | git version 2.13.0                                                                                |
| Installation Source         | ~/.gems/bin/fastlane                                                                                |
| Host                        | Mac OS X 10.14 (18A391)                                                                                |
| Ruby Lib Dir                | /System/Library/Frameworks/Ruby.framework/Versio                                                         ns/2.3/usr/lib |
| OpenSSL Version             | LibreSSL 2.6.4                                                                                |
| Is contained                | false                                                                                |
| Is homebrew                 | false                                                                                |
| Is installed via Fabric.app | false                                                                                |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/                                                                             |
| Xcode Version               | 10.1                                                                                |
System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.111.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
1.8.0

terminal-table
1.8.0

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

gh_inspector
1.1.3

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
1.0.0

faraday_middleware
0.12.2

naturally
2.2.0

simctl
1.6.5

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.2.7

digest-crc
0.4.1

google-cloud-storage
1.15.0

emoji_regex
0.1.1

tty-cursor
0.6.0

tty-screen
0.6.5

faraday
0.15.3

json
2.1.0

io-console
0.4.5

excon
0.62.0

CFPropertyList
3.0.0

libxml-ruby
2.9.0

atomos
0.1.3

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.7.0

jwt
2.1.0

memoist
0.16.0

googleauth
0.6.6

signet
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

fastimage
2.1.4

bundler
1.17.1

unicode-display_width
1.4.0

retriable
3.1.2

mime-types
3.2.2

mime-types-data
3.2018.0812

multi_json
1.13.1

os
1.0.0

psych
<IP_ADDRESS>

generated on: 2018-12-18
]

I am experiencing the same. When the log says 'distributing new build to testers it stops with a 404 Not found page. I looked in the spaceship log and it seems it can't find the following URL:
DEBUG [17:23:07]: << POST providers/****/apps/*****/builds/****/review: 404 <!DOCTYPE html><html lang="en">

@mjooms hmm, maybe apple changed something...

See https://github.com/fastlane/fastlane/issues/13903. Fixed with the next release 🚀


web3signer

add: getAddressFromPublicKey
add: required packages
add: web3Signer url in config
new: create api for web3signer
new: web3signer class
update: getAddress() for router
add: update context to wallet

The Problem

The Solution

Checklist

[ ] Test manually on test-ui using remote chains.
[ ] Run load tests.
[ ] Update documentation if needed.
[ ] Update CHANGELOG.md.

converted web3signer api methods into a class
wrote unit test cases for both the api and the signer class


Struggling with the update statement

Hello,
I'm trying to update a row into my database but even if the code seems to work, the value is not updated in the database.
I have this attached to a button:
let value = additivesTable.filter(keyColumn == passedDetails)
let update = value.update(isBookmarkColumn <- 1)
if let changes = update.changes where changes > 0 {
println("updated bookmark")
} else if update.statement.failed {
println("update bookmark: (update.statement.reason)")
}
When I click on the button, the "updated bookmark" appears but there's nothing updated in the database. Do you have any ideas why?

Hmmm...I think the reason of my problem is that I'm trying to modify the databased bundled with my project. I'm new to this and let me know if I'm wrong: the app creates a local database?

Have you read the documentation on "Connecting to a Database"?
https://github.com/stephencelis/SQLite.swift/blob/d87e05da167bdded01ae74001c5adda865346867/Documentation/Index.md#connecting-to-a-database

Hi Stephen,
Yes, and I can retrieve data from the database without any problems.

@boogdan Did you see the note there that specifically addresses bundled databases?

Note: Signed applications cannot modify their bundle resources. If you bundle a database file with your app for the purpose of bootstrapping, copy it to a writable location before establishing a connection (see Read-Write Databases, above, for typical, writable locations).

oooooh now it makes sense.
In the guide you said that I can create one in the apps' Documents directory. I suppose that I can add my existing database there instead of creating a new one, right?
Also, what is exactly "app's Documents directory"? Sorry if I'm bothering you with this...I'm sure it's something extremely easy to do but I'm new to iOS dev so I'm struggling a bit :)
Thank you so much for your terrific work that you did with this project.


Some of the editors make the layout scrollable and it's not needed

I noticed that on the JSON editor when it opens it shifts the layout and the entire page becomes scrollable. This is caused by defined values similar to calc(100vh - 22px) and not using only height: 100% and display flex. I already created a pull request to fix this issue.

Probably it will be also resolved by PR #755 which handles more related issues with scrolling.

since #912 was closed this also should be as per: https://github.com/usebruno/bruno/pull/912#issuecomment-2268946402 probably

The issue is now closed as completed. Please make sure to use the v1.25.0 version of Bruno.


Update README.md

Build.sh and init.sh should be swapped as init is required to make the dependencies for build.

Hit this same thing when walking someone else through installing ocm-container this week - agree on switching the order.
/lgtm

If you LGTM then it's good enough for me to merge


Self-signed Certificate Issue with Docker Container

I have a Docker Compose environment with openfga/openfga:latest and openfga/cli:latest containers, and I'm also using temporarily generated, self-signed certificates for development purposes.
When running the CLI container, using a basic docker compose run openfga-cli store list it outputs the following error:
Error: failed to list stores due to Get "https://openfga:8080/stores?continuation_token=": tls: failed to verify certificate: x509: certificate signed by unknown authority

Is there a recommended way to force the CLI to accept/use my self-signed certificate?

Hey @Valkryst - in general I would say you would have to follow the same steps to get the certificate loaded into the docker.
This answer on StackOverflow walks you through that: https://stackoverflow.com/a/54403068

It seems as though the openfga/cli container doesn't allow for commands to be run VIA bash. I got it working with this Dockerfile:
FROM debian:stable-slim

RUN apt-get update && apt-get install -y ca-certificates wget

RUN wget https://github.com/openfga/cli/releases/download/v0.6.2/fga_0.6.2_linux_amd64.deb -O /tmp/fga.deb \
    && apt install -y /tmp/fga.deb \
    && rm /tmp/fga.deb

# We do "&& tail -f /dev/null" to keep the container running, so that we can exec into it to run CLI commands.
CMD ["bash", "-c", "update-ca-certificates && tail -f /dev/null"]


Fix screen title translation

Description
The title of the Raise limit screen was not being translated. I haven't checked if other screens have the same problem

Error reported here: https://valora-app.slack.com/archives/C025X4WJT09/p1632932037112500
Other changes
N/A
Tested
Manually
How others should test
Choose any language and go to the Raise limit screen from the help option in the side menu.
See that the title is translated
Related issues

Fixes #

Backwards compatibility
N/A

Hey @gnardini , We have verified this issue using Test flight Build V1.21.0(1635160132) updated status in Test Quality tool
iOS (13.0):

https://valora.testquality.com/project/12128/plan/22175/run/151573/result/2540467

Verified On Device: iPhone SE (13.6.1)
CC: @MuckT


Create SECURITY.md

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: digitalnomad2 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Error when tray service  Docker Version

This a error Console with Docker version
[Error: ENOENT: no such file or directory, unlink '/tmp/undefined.mp4'] {
errno: -2,
code: 'ENOENT',
syscall: 'unlink',
path: '/tmp/undefined.mp4'
}

https://github.com/thundersquared/tikvidbot/issues/12#issuecomment-735380039


[BUG] Getting validation error during deployment of  'ros-image-demo' (fix added)

Describe the bug
I was trying to deploy the 'ros-image-demo' deployment, and during deployment I was getting a validation error for creation of a dag role. I checked and it seems that the length of the role name created at line 135 exceeds the maximum length of 64 characters.
I altered the length of the name of the role, however I start getting an error that the resource already existed. It seems like this dag role is being created twice in the stack (in different templates), thus to resolve the issue, I commented out line 150. Once done, the deployment succeeds without any issues.
To Reproduce
Deploy the  'ros-image-demo' deployment till you get a validation error in one of the stacks where the name of a role exceeds the max character length of 64 characters
Expected behavior
The deployment should have succeeded without errors .
Screenshots

Additional context

Hi @mehtaparitosh  - thanks for raising this. I refactored the manifest a bit to shorten the name lengths - this should resolve your issue.
https://github.com/awslabs/autonomous-driving-data-framework/pull/57

can we close this bug?


New tropo_corrections function to apply GACOS corrections

*NOTE, disregard previous branch concerning these changes!
To use new function, use "-tp" flag in ariaExtract.py or ariaTSsetup.py to pass path to untared directory containing extracted GACOS product or a list of tarfile paths to extract. The code can handle cases where GACOS products first need to be stitched--stitched GACOS products are exported to the "merged_GACOS" subfolder created inside the specified work directory.
The program also reports to the user if there is any spatiotemporal discrepancy between the downloaded GACOS product and the extracted phase.
A reference point for each IFG is estimated following the method outlined in the original GACOS code, e.g. the pixel closest to the nanmean of the phase-field.
Also passed a couple of miscellaneous updates: (1) in ARIAProduct only a comma-delimited input list of files is now allowed as opposed to a space-delimited list (to reflect the documentation). (2) Minor updates to the function description in the "export_products" function.

@pymonger any idea why circle CI fails even when we do not have tests?


Update the OS X deployment target from 10.8 to 10.11

Every time I build my project, I get a slew of warnings because libgit2 was built for 10.11, but ObjGit is targeting 10.8.

The Travis build failure is on the iOS target, which I didn't change. I don't know what's going on there.

I did some digging around, because it annoyed me too. It seems like this is a bug in Xcode and should not cause a warning. I am strongly against setting the deployment target up, as it breaks other apps. GitHub Desktop for example is targeting 10.9.
Please see this thread: https://forums.developer.apple.com/thread/20024

OK, sounds like this isn't the right solution then. Though I'm left wondering why libgit2 is getting built for 10.11. Maybe the build script doesn't specify, so it defaults to the latest.

@Uncommon Are the warnings coming from the linker phase of the libgit2 target?
ld: warning: object file (/usr/local/lib/libssh2.a(agent.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(channel.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(hostkey.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(session.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(userauth.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(dsa_lib.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(digest.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(rand_lib.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(rsa_lib.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(misc.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(openssl.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(global.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(kex.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(packet.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(transport.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (/usr/local/lib/libssh2.a(keepalive.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(asn1_lib.o)) was built for newer OSX version (10.10) than being linked (10.8)
ld: warning: object file (External/libcrypto.a(bio_lib.o)) was built for newer OSX version (10.10) than being linked (10.8)

These say 10.10 because I captured them last year.

Based on this SO answer, the fix may be to specify the CMAKE_OSX_SYSROOT like we do in update_libgit2_ios

Note that #570 resolves these warnings because libgit2 is built from an Xcode project instead of cmake.

The warnings show up under the ObjectiveGit-Mac target rather than libgit2, but they look just like that.

@Uncommon do you still get these errors in Xcode 8?

Yes, I still see them in Xcode 8 beta 2.

Also in Xcode 8 final.

The libgit2 link might be fixable (we're in control of that, we might just need to pass the correct MACOSX_DEPLOYMENT_TARGET through CMake. libssh2 isn't so easy — AFAIK there's no way to ask homebrew to do that...


Pagination using server side data loading

Please can you show me the steps to implement pagination using back end calls by sending limit and offset values and loading the results back to the table. I have done the client side pagination and sincey data base consist of large amount of data i need to swith to server side data loading when changing pages
Thanks in advance

var bookmark;
var self = this;

self.query = {
      'limit': 10,
      'offset': '',
      'page': 1
    };

$scope.$watch(angular.bind(this, function () {
      return this.query;
    }), function (newValue, oldValue) {
      if(!oldValue) {
        bookmark = self.query.page;
      }

      if(!newValue) {
        self.query.page = bookmark;
      }

      getData();
    }, true);

function getData() {
      self.promise = *** request to server with self.query params (need return promise)***
    }

<table class="mtable" md-table md-progress="someCtrl.promise">
</table>

<md-table-pagination md-limit="someCtrl.query.top" md-page="someCtrl.query.page"></md-table-pagination>

Hello there please let me know if your code working fine .. i would like to do same server side pagination as data is huge


Soundex bug

https://github.com/wannaphongcom/pythainlp/blob/c1f414236c7351f0a2fe7d62f0d7f33da19de606/pythainlp/soundex.py#L44
Really appreciate your great work providing soundex alg for Thai.
len(c) shoud be len(s), right?

No , c is characters from enumerate(s). https://github.com/wannaphongcom/pythainlp/blob/c1f414236c7351f0a2fe7d62f0d7f33da19de606/pythainlp/soundex.py#L31

Thanks for quick response.  (i+1<len(c) and (c[i+1] in "ึืุู"), since i is the enumerate index for string s, by no means, you will use c[i+1]. I think it should be len(s) and s[i+1].

Thank you. I have already fixed.

thank you ;)


Make ordering of AnnotationMatrix objects clear

Needs to be clear what the sorted order of these are so it's not necessary to e.g. align gold labels or store them as GoldLabel matrices... just a cleanup note...

Basically here: just make explicitly sure that the rows of all annotation matrices are sorted by cid

Nvm already done in load_matrix


Move sanitization methods to SanitizationHelperTrait + minor improvements

These methods haven't had extensive work done as they barely do any token walking themselves and the underlying functions used by the methods all have had work done to improve them.
Note: the is_only_sanitized() method could be moved to the NonceVerification sniff as it's only used by that sniff, but for now, I've elected to keep it together with the is_sanitized() method.

Rename SanitizingFunctionsTrait to SanitizationHelperTrait
The Sniff:;is_*sanitized() utility methods are about to be moved to this trait, but once they have been, the trait name is no longer correct as all other *Functions[Helper|Trait] classes/traits only deal with function lists and checking whether something is in those lists, while this trait will now do more than that.
With that in mind, I propose to rename the trait to SanitizationHelperTrait.
Move sanitization methods to SanitizationHelperTrait
This moves the last utility functions from the Sniff class to a dedicated trait.
I am also explicitly marking the trait as internal API to allow us to iterate on this (not so very clean) solution in future 3.x releases without being forced to wait for a 4.0 release.
The methods have been made stand-alone, as in, the presumption that the WPCS Sniff class is being extended has been removed by adding the $phpcsFile parameter.
Closes #1465
SanitizationHelperTrait::is_sanitized(): add some defensive coding
As this method is now stand-alone, we'd better make sure the token being examined exists.
Note: no need to do the same for the is_only_sanitized() method as the first thing that method calls is this method and if this method returns false, the is_only_sanitized() method will too.
SanitizationHelperTrait::is_sanitized(): implement PHPCSUtils
Note: The $functionPtr variable is overwritten a few lines later and the other variables being set are effectively unused (other than in these lines), so this code can be safely removed/replaced.
SanitizationHelperTrait::is_sanitized(): efficiency tweak - move unset check up
A variable which is being unset, doesn't need to be unslashed or sanitized, so bow out early.
SanitizationHelperTrait::is_sanitized(): efficiency fix/improve performance
Remove the need for a call to the performance negative array_diff_key() function by setting up the original arrays in a better way.
SanitizationHelperTrait::is_sanitized(): minor code tweaks

Get rid of an unnecessary else.
Improve readability of long condition.
Get rid of unnecessary true/false condition code.

SanitizationHelperTrait::is_sanitized(): minor doc tweaks

Also note: I still have a niggly feeling there is a logic error in the is_only_sanitized() method, but I haven't been able to figure out the reason this was originally coded this way, so I'm not touching it for now.
The logic error I suspect is in the following code:
		// The only parentheses should belong to the sanitizing function. If there's
		// more than one set, this isn't *only* sanitization.
		return ( \count( $tokens[ $stackPtr ]['nested_parenthesis'] ) === 1 );

This seems to presume that parentheses could only be for function calls, while the extra parentheses may just as well be for control structure conditions.
If the other parentheses are for control structure conditions, I believe the variable should still count as "only sanitized".
It also discounts situations where unslashing is nested within a sanitization function call (which is taken into account in the NonceVerification sniff, but that is now inconsistent).
$a = is_email( $_GET['email'] ); // is_ony_sanitized(): true
$a = is_email( wp_unslash( $_GET['email'] ) ); // is_ony_sanitized(): false
if ( is_email( $_GET['email'] ) ) {} // is_ony_sanitized(): false

This should probably be further investigated when adding dedicated tests for these methods (#2272).

Repushed to fix the order of the remaining use import statements in the Sniff class.


Update Tokens Tutorials

This PR adds two brand new tutorials for ERC-20 and ERC-721 as well as how to use Metamask with them. It also includes some updates to the ERC-1155 tutorial to include approvals.
A live preview of the new docs pages can be found at: https://nguyer.github.io/firefly/tutorials/tokens

Codecov Report

Merging #777 (c00eeb8) into main (ea38e01) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #777   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          323       323
  Lines        20181     20181
=========================================
  Hits         20181     20181

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 ea38e01...c00eeb8. Read the comment docs.


Day should be mentioned

@Archita01 Can you elaborate on where you want this? Preferably with a screenshot

@UbadahJ It should be preferably mentioned beside the date.

@Archita01 assign me

Add day alongside the current date

@UbadahJ All the best


Job release_counter is out of date and can be removed

https://ci.adoptopenjdk.net/view/all/job/release_counter/644/console
is obsolete and can be deleted

@gdams Not sure if this needs to be removed or enhanced. Homebrew data should be included as well.

Yes, probably,not removed because it's include detail per arch which is not on web dashboard.
Or update https://dash.adoptopenjdk.net/ to see stats by arch too

@douph1 you do get stats by arch https://dash.adoptopenjdk.net/version.html?version=jdk11&tag=jdk-11.0.2%2B9

@gdams  Do we still need this?

removed


Correction for raw affiliation UMR PHIM - Plant Health Institute of Montpellier (CIRAD Campus International de Baillarguet TA A-54/K
34398 Montpellier

France)

Correction needed for raw affiliation UMR PHIM - Plant Health Institute of Montpellier (CIRAD Campus International de Baillarguet TA A-54/K
34398 Montpellier

France)
raw_affiliation_name: UMR PHIM - Plant Health Institute of Montpellier (CIRAD Campus International de Baillarguet TA A-54/K
34398 Montpellier
France)
new_rors: 05kpkpg04;03fkrcm40;05y5s3h28
previous_rors: 05kpkpg04;03fkrcm40
works_examples: W3204735444;W4310978522
contact: 888b09704259eec9d82357bc5d7d80cd:98781a3491ddf89dc357599f428c5d817ee4 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


fix: banner absolute position

Problem
The banner image container is having absolute position style so when there is only a banner on a row it will collapse to zero height because no other result item is there to establish the height.
Solution
Only apply the absolute style when the column span of that banner is larger than the total number of columns.

SF-760


Basic profile is undefined in auth2.grantOfflineAccess()

First I initialized the gapi
auth2 = gapi.auth2.init({
client_id: CLIENT_ID,
fetch_basic_profile: true,
scope: 'https://www.googleapis.com/auth/gmail.readonly profile email openid',
});
Then calling grantOfflineAccess
auth2.grantOfflineAccess({
prompt: 'select_account',
}).then(function (resp) {
const permissionCode = resp.code;
const email = auth2.currentUser.get().getBasicProfile().getEmail();
});
In this case getBasicProfile() is coming undefined.

I have the same case here. I already described my issue here: https://github.com/google/google-api-javascript-client/issues/587

Perhaps it was by design that you don't get basic profile information, but just the authorization code.
I solved it by making next code on the server side:
[Route("api/test/login")]
[HttpPost]
public async Task<IActionResult> LoginAsync([FromBody]string googleAuthorizationCode)
{
  try
  {
    FileDataStore fileStore = new FileDataStore("Voda.bla");
    AuthorizationCodeTokenRequest authorizationCodeRequest = new AuthorizationCodeTokenRequest()
    {
        ClientId = ClientId,
        ClientSecret = ClientSecret,
        Code = googleAuthorizationCode,
        RedirectUri = "http://localhost:4200",
    };

    TokenResponse tokenResponse = await authorizationCodeRequest.ExecuteAsync(
      httpClient,
      GoogleAuthConsts.OidcTokenUrl,
      CancellationToken.None,
      SystemClock.Default);

    GoogleJsonWebSignature.Payload payload = await GoogleJsonWebSignature.ValidateAsync(tokenResponse.IdToken);

    // payload.Subject - Use this value as a key to identify a user.
    if (string.IsNullOrWhiteSpace(payload.Subject))
    {
        return StatusCode(StatusCodes.Status500InternalServerError, new Exception("Google UserId is missing."));
    }

    await fileStore.StoreAsync<TokenResponse>(payload.Subject, tokenResponse);

    ResponseModel responseModel = new ResponseModel()
    {
        UserId = payload.Subject,
        Message = "Successfully got access_token for authorization code."
    };

    return Ok(responseModel);
  }
  catch (TokenResponseException e)
  {
      return StatusCode(StatusCodes.Status500InternalServerError, e);
  }
}

So now I can return the Google userId back to the client, or of course with a little of modification the whole basic profile.


RateLimiter mode support parametric configuration

Is this a regression?
Yes
Description

RateLimiter mode is  kWritesOnly by default now, Rocksdb supports three mode.

Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos

Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response

This is a feature, not a bug; I make a mistake.

您好，这个参数是读和写都限流的，这边不太清楚您是想在要啥功能


how to add tracks ( .vtt)

Hello, I failed to add tracks to my video. Please give me a hand.
<div id="player"> </div>
<script>
var player = new Clappr.Player({
  source: "/wp-content/uploads/video/sample.m3u8",
  poster: "/wp-content/uploads/2018/11/emma_sample.jpg",
  track: "/wp-content/uploads/video/sample.vtt",
  width: "100%",
  parentId: "#player"
});
</script>

Take also look also at playback externalTracks parameter.


Group description should support markdown

Cannot be because it is directly the string content of the div, not a child html node