Tester feedback: language

Page title
Edit users

language
I would remove the signature image from this table. Maybe replace it with an e-sign form? checkbox? or have it as a separate question to be edited (and not part of this table)?

Other information

Variable being sought
users.revisit

Package version
1.1.4

Maturity target
Level 4 - this is purely an enhancement to improve user experience

Tester contact info
mnewsted

this relates to how e-signature will work in the interview. i'm still leaning toward just do you want to e-sign Y/N? if that's the case, we can just have a checkbox here.


feat: 🔥 build locales

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/ngneat/falso/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #1
What is the new behavior?
The build-locales target can build all locales under packages/falso/src/lib/locales folder.  Only a barrel file per locale (ru/index.ts, es/index.ts`, etc.) is required.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Not sure about the build errors.
I also can't run the normal build, without adding seedrandom and uuid to the root package.json 🤔

The build-locales target can build all locales under packages/falso/src/lib/locales folder. Only a barrel file per locale (ru/index.ts, es/index.ts, etc.) is required.
The result would have the respective locales as secondary entry points:

The locales src folder and output folder can be configured through target options in project.json:
    "build-locales": {
      "executor": "./tools/executors/build-locales:build-locales",
      "options": {
        "localesOutputPath": "dist/packages/falso/locales",
        "falsoSourcePath": "packages/falso/src",
        "localesSourcePath": "packages/falso/src/lib/locales"
      }
    },

The build-locales target would build all locales:

Thanks. Looks good. I have a few questions:

Have you tested it using npm link?
The goal is to make this process automatic by marking the files we want to translate with the .i18n extension (e.g. word.i18n.json). Then we can copy the corresponding typescript file and translate the data using an automated tool or manually. What do you think about it?

I have tested it with a local npm registry using verdaccio. I will do another test with npm link
This increment is currently only about the build process. It requires the translated data and typescript files, already be in place. I thought, maybe the translate executor is capable of doing the translation part? But I can also have a look into that and adapt if necessary. 😊

Though I have questions regarding the translation:

The goal is that the translations are also stored in the repository, right?
Would we allow to push new generators without translations, even if they are supposed to be translated?
If yes, should the automatic translation kick in in such cases and provide an automated translation, as part of the CI?

The goal is that the translations are also stored in the repository, right?
Yes

Would we allow to push new generators without translations, even if they are supposed to be translated?
Yes, we can't enforce contributors to provide localized versions.

If yes, should the automatic translation kick in in such cases and provide an automated translation, as part of the CI?

It'll be great if we can use something like Microsoft translate service ( Google translate has limitations). We can start with manual translations and automate them in separate PR. In the meantime, I'd add what I suggested with the i18n extension and copy the typescript file.

Sounds good. I would love to automate the translations in a separate PR. 👍
Do you have a list of languages on your mind, that we want to start with?

https://www.berlitz.com/en-uy/blog/most-spoken-languages-world

You can choose 5 from here and yours :)

Using the package with npm link worked seamlessly.
I also added the randBird translations and introduced the *.i18n.json pattern.

@michaelxvoelker, thanks for the great work. We need to do the following:

Copy the typescript file from the main locale so it'll be the single source of truth.
Mark the files we want to translate and run a script that uses a translation service.

And we should remove the i18n folder with the types after build

@michaelxvoelker, instead of copying the typescript file, it'll be better to think about a way we can use the original with data we load from a locale file.

One suggestion:

import { FakeOptions, fake } from './core/core';
import { data } from './bird.i18n.json';

/**
 * Generate a random bird.
 *
 * @category animals
 *
 * @example
 *
 * randBird()
 *
 * @example
 *
 * randBird({ length: 10 })
 *
 */
export function randBird<Options extends FakeOptions = never>(
  options?: Options
) {
  return fake(options.locale ?? data, options);
}

The consumer:
import { randBird, useLocale } from '@ngneat/falso';
import ruBird from '@ngneat/falso/i18n/ru/bird';

randBird({ locale })

I have an idea, will try it out.

I'm not sure about this:

import { randBird, useLocale } from '@ngneat/falso';
import ruBird from '@ngneat/falso/i18n/ru/bird';
randBird({ locale })

Do you mean:
import { randBird } from '@ngneat/falso';
import ruBird from '@ngneat/falso/i18n/ru/bird';

randBird({ locale: ruBird })

I like the idea. So far, the data was an implementation detail and not even typed. I'm a bit worried about adding it to the API. 🤔  What do you think?

What else can we do?

Hmm, for now probably not much without losing tree shakeability.
Anyways, it's not a blocker. I will provide an initial implementation, as proposed. 😊

Cool, thanks.

:eyes: Any way to use for example fileReplacements option to switch locales before each locale build, instead of duplicating code? 🤔

With this suggestion, what happens if you import a locale in your application? You'll have two copied versions of the randBird function?

True 🙂

The goal is to avoid this :)

@michaelxvoelker any news here :) ?


Can't use pagination methods from Github

Hi there,
I've been using the module for a while now, but I've found one issue I'm not sure what the best way around it is, but it's that the pagination methods from the Github module don't work on a cached request, and from what I can tell, it's because the headers aren't saved anywhere, so it can't access the link header from the request, so it throws an error.
Is there any way to accomplish this?
Thanks!

Can you show me how you are using it? Using pages has worked for me in the past but I haven't tested lately.

On Jun 21, 2016, at 15:43, Nate Cavanaugh<EMAIL_ADDRESS>wrote:
Hi there,
I've been using the module for a while now, but I've found one issue I'm not sure what the best way around it is, but it's that the pagination methods from the Github module don't work on a cached request, and from what I can tell, it's because the headers aren't saved anywhere, so it can't access the link header from the request, so it throws an error.
Is there any way to accomplish this?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm using bluebird to promisify all of the methods (all of which works fine, since it doesn't mutate the data in anyway), but here's an example method call:
var myRepos = github.getAllPages(
        github.repos.getAllAsync,
	{
		per_page: 100,
		type: 'owner'
	}
);

I also get the same errors if I use the regular API as well.

I'm not at my computer at the moment but the get AllAsync looks custom? Is it? I don't recall that being in the API.
Sent from my iPhone

On Jun 21, 2016, at 15:53, Nate Cavanaugh<EMAIL_ADDRESS>wrote:
I'm using bluebird to promisify all of the methods (all of which works fine, since it doesn't mutate the data in anyway), but here's an example method call:
var myRepos = github.getAllPages(
github.repos.getAllAsync,
{
per_page: 100,
type: 'owner'
}
);
I also get the same errors if I use the regular API as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

It's from bluebird's promisification, so the method that accepts the callback is github.repos.getAll, and bluebird's method is github.repos.getAllAsync.
But I should have stripped it down to eliminate Bluebird in my example, but here's the default way (throws the same error):
github.getAllPages(
	github.repos.getAll,
	{
		per_page: 10, //set to 10 just to force it to paginate
		type: 'owner'
	},
	function(err, res) {
		console.log('callback response', err, res);
	}
);

The exact error I get is:
Uncaught TypeError: Cannot read property 'link' of undefined
Let me know if you need any other info.

Oh yeah,
It might also work on the first request, just because since it's not cached, it would have the header, but all subsequent requests to the cache don't have the header, so it bombs out trying to read it.

@natecavanaugh so I was only checking the emails on this issue because I've been on vacation. Looks like you gave me links in the first issue. I know what is going on now.
I believe the getAllPages is a relatively new function, at least new to me, and I never accounted for its behavior.
It looks like it wants to see the meta object on the end of each request. Up until this point I've always stripped the metadata on cached requests. I think I'll try and modify it to give the etag, a status of 304 to indicate its cached and the link field. This shouldn't break any existing functionality, but need to do some testing.
I'll make the changes and publish a version to the @next tag and let you know when it is up.

@natecavanaugh I just pushed the next branch. Give it a try, works for me locally. I didn't try every combination, but this adds back in the meta object its looking for, just slightly modified, with a cached result, I don't return any of the x- headers and I change the status to 304 Not Modified

@ekristen Thanks a lot for looking at this while on vacation, as well as the fix.
I just tested it out locally, and it all seems to be working :)
Thanks again!

I'll publish the update to npm soon.
Sent from my iPhone

On Jun 22, 2016, at 13:47, Nate Cavanaugh<EMAIL_ADDRESS>wrote:
@ekristen Thanks a lot for looking at this while on vacation, as well as the fix.
I just tested it out locally, and it all seems to be working :)
Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Resolved by https://github.com/ekristen/node-github-cache/commit/d3fb26e48701375dfa9eb161565f468ae393dcd4

@natecavanaugh looks like version 2.0.0 was just published and they just yanked the getAllPages helper methods entirely :(
I'm looking at releasing a newer version of this library that will let you pass in your own version for the github api lib instead of having to use the one the comes with it.

@ekristen I actually really like that idea as well :) The last upgrade of node-github-cache broke for me because of the underlying major change in node-github, but your update had it as a minor.
I think allowing us to pass in any lib we like gives us a lot of safety and freedom, so def a 👍 from me :)
Thanks for the heads up!

Interesting ... what broke? (just curious)
AFAIK, all the updates I have delivered have only upped the minor version of github library. I haven't delivered a version supporting 2.0.0 yet.

I went from 1.0.1 of github-cache to 1.3.0, in which time, and your dep on github went from 0.2.4 to 1.1.0.
So, according to semver rules, I believe that a minor upgrade just means additive, non-breaking changes, but since github-cache is a proxy, technically your API broke as well.
(That, and since I'm using my own CacheDB implementation, I didn't have the batch method, but that was totally my fault).
Overall, it wasn't a huge issue, just a bit of a surprise :)
Thanks again!

Sorry about that, I definitely try not to break things ;)
I'm working on my next major version which will have the following changes ...

support any version of github that you want to use (theoretically, but there may be some edge cases)
most likely use https://github.com/ekristen/node-libkv so you can use more than just level (if you'd like to look into creating a wrapper for couchdb for libkv, that'd be awesome)

Any comments, questions, or other would be appreciated.


BODY_25_ALL not compatible with BODY_135

There is the implicit assumption in some of the formats here that BODY_25_ALL is somehow compatible with BODY_135, but this is not the case. This opens up the possibility of:

If possible, conversion from BODY_25 to BODY_25B could be implemented if reasonable
Either BODY_25_ALL or a variant thereof including two key points for wrists (actually wrist and "heel of hand") which are currently being collapsed together

Now we just save all keypoints by default, which probably resolves this issue.


Separate mocks for dogs and cats profiles

Test for testFirstAnimalImage() is working only when mockBackend is set on true. This endpoint is for https://i.imgur.com


Please make it possible to add gutter (margin) before the text area

Please consider making an option to add gutter before the text area to improve usability.
Currently it is problematic to use the mouse to place the caret in the beginning
of the line because there is no gutter to trap the mouse selection cursor:
On the screenshot below I try to place the cursor before the dot, and need to be
pixel-precise to make so.

Also I find it annoying when something "sticks" to the text/code, whether
it is folding icons or line numbers (if folding is off) so I personally always want some
extra margin to the left to improve readability.
The setting could be named something like:
"editor.leftMargin": 5,

The number would indicate the margin width in characters, I suppose.
In addition, an option to control how the mouse click behaves in this area should be added,
I suggest "line selection" mode or "standard selection" mode.
For "standard selection" a placeholder cursor would be shown just like in text.
For "line selection" pointer cursor would be shown, like by clicking on the line number area.

Please take care of this as it is poorly usable right now, hard to place cursor at the beginning of line...
https://github.com/microsoft/vscode/issues/78087

If this will go into production someday, I think it is also worth implementing
optional extra margins for other purposes, and make them customizable.
Currently, e.g. bookmarks (available in extension) utilizes the same margin as breakpoints for icons, and it's not good. E.g. also there is still no possibility to adjust the line number margin width.
For reference you could see how it is made in Scintilla:
https://www.scintilla.org/ScintillaDoc.html#Margins

I believe the bug I just opened at https://github.com/microsoft/vscode/issues/127025 is making it harder to select text in the left margin.


Adding GitHub actions workflow for python testing

Purpose
Introducing a GitHub Actions workflow designed to automate testing across multiple Python versions (as of the current release, the only supported Python version is 3.8).
Approach
This change integrates a continuous integration pipeline using GitHub Actions that performs the following:

Tests the codebase against multiple versions of Python to catch compatibility issues.
Executes pylint to ensure code quality.
Builds and tests documentation across the same range of Python versions.

Tests for New Behavior
No tests were added.
Checklist
Not applicable.
Learning
The implementation was based on the CircleCI workflow already available in the repo.
The integration of multiple Python version testing was based on the following documentation: https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs

Excellent first PR for this repo!
Thank you for your contribution.


Specific mention to private peering for failback

Specific mention to private peering for failback

@JackStromberg : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

@JackStromberg : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

Thanks! #sign-off


How to serve a directory of msgpack files?

Is there a configuration example for a file directory of msgpack files?  Such as prepared by databroker-unpack or a temporary databroker catalog?

Ok.  I was hoping to provide some of the catalog I use for CI testing.  Here is my initial config, that failed to recognize the msgpack files:
# config.yml

# tiled serve config --public --host <IP_ADDRESS> config.yml
# http://SERVER.xray.aps.anl.gov:8000/

trees:

  - path: examples
    tree: files
    args:
      directory: /tmp/examples
      key_from_filename: tiled.adapters.files:identity
      mimetypes_by_file_ext:
        .msgpack: application/x-msgpack

That makes sense; sample data for testings on CI is a use case we should make sure we cover well.

Since you've answered my question, I'll close this issue.
Thanks, @danielballan !

Which makes this related to #535.


Support SDK examples for DPG to be shown in Rest API document on Docs

The samples section we have today on the REST API reference docs isn't something that customers can easily use and run within their code. It's usually the case that we want customers viewing REST API documentation to not make the request using the REST API itself but through some sort of client library that is native to their programming language.
Solution:  On REST API document on Docs, show SDK code samples corresponding to REST API examples from Azure REST API Specifications. (Example: Create Event - Microsoft Graph v1.0 | Microsoft Docs).
We could follow the same approach of mgmt SDK to store DPG code samples in Azure/azure-rest-api-specs-examples: SDK examples for azure-rest-api-specs (github.com).
REST API document and SDK code samples should be of the same version.

I would like to have the feature to be enabled into DPG as this would be very helpful for end users. But this is low priority compared with other work we have.


⚠ Bofrost.lu has degraded performance

In e918051, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 845 ms

Resolved: Bofrost.lu performance has improved in bf97471.


Desktop config

🤖 Generated by lychee action
Summary

Status
Count

🔍 Total
1245

✅ Successful
374

⏳ Timeouts
0

🔀 Redirected
0

👻 Excluded
870

❓ Unknown
0

🚫 Errors
0

Full action output
Full Github Actions output


 It, however, suggests contracts, e.g. function parameters, be documented (otherwise where would be the contract?).
We would therefore need to agree upon documenting function params, but otherwise throw all type checks out the window.
I was thinking this project might be a good opportunity to give this design paradigm a try, you in?

Where did you read that? I don't think documentation will make your code less error prone. I would rather invest the time in writing good tests than in writing documentation.
If we do the extra work I would go with FlowTypes and have the extra benefit of static type checking.

Nah, no type-stuff on the beautiful JS 👎  for FlowTypes.
I read about DBC in "The Pragmatic Programmer". And it's not about writing full fledged docs. Rather, when you write a function you add a signature comment above it, e.g.
// @param foo: string
// @param bar: array
const doStuff = (foo, bar) => {
  //
};

PR open https://github.com/haensl/js-performance/pull/52

Done in v1.14.0


Cannot apply the cInlineImage class for images

Description:
The cInlineImage class does not get applied to images even though it is added as follows in either of the valid formats (markdown or HTML).
Markdown format:
{.cInlineImage-full}
HTML format:

This should be because now, we have not added stylesheets to override the styles of the default material theme after migrating to it.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This is fixed via https://github.com/wso2/docs-ballerina-vscode-extension/pull/220/.


DCOS-8898: Change history embed with historySummary embed on jobs request

This changes the emebed parameter for the jobs request and we only request the history
summary from metronome now. This will remove a lot of overhead in request size for
clusters which are using a lot of jobs.

LGTM 🎆 🚢 🇮🇹


"JointBERT" vs. "BertForMaskedLM" in model config json file

Hi,
This is a great repo! I was using your code to train Bert on my own data, but I noticed that the architecture field in the model config json file changed. The code and data are exactly the same, but the architecture changed which is wired.
Please see the attached screenshots.
Do you know why this changed over time?
Thanks!

@monologg Same problem for me

Hi!
@haomiao-li  Can you tell me the version of transformers library that you used? When I'm tried to reproduce this one, my config.json shows JointBert on acrchitectures attributes.

What I did for training on new data is add task name on processors dict (in data_loader.py)

Then run the code as follow.
$ python main.py --task wow --model_type bert --model_dir wow_model --do_train

By the way, when I was making this repo, the version of transformers library was low, and the architectures attributes wasn't in the config.json:(

It seems like that the older version of transformers library has the bug. When I tried with the version under 2.4, the architectures is saved as BertForMaskedLM as default. But with new version (2.4.1), the architectures is correctly saved as JointBert.
@haomiao-li  @pttzty Can you try with transformers version of 2.4.1?

@monologg Will try it asap. The error looks weird because the performance for the intent detection part did drop significantly with Bert Masked LM

@monologg Will try it asap. The error looks weird because the performance for the intent detection part did drop significantly with Bert Masked LM

I've just checked this one. But even with ver 2.2.2 (config is also saved as BertForMaskedLM), the performance looks same. Below is the steps that I've tried. If my step is different with yours,  just let me know the steps you tried:)
[Reproducing steps]
0. transformers==2.2.2

In main.py, change the code to evaluate the dev set when --do_eval
(I've change the code to load all three dataset at the beginning)

Run the code

$ python main.py --task atis --model_dir atis_model --do_train --do_eval --num_train_epochs 1

Check the difference be

@monologg Problem fixed after we upgraded to the latest version of the transformers. Thanks!
Just another side note that I think you were trying to use ignore_index to exclude pads from the loss function and the final predicted output, and it actually worked well for the two sample datasets. However in my case I was getting lots of "PAD" for the final prediction results where it should actually be "O" category, and I think the pad was actually not excluded.

@monologg Problem fixed after we upgraded to the latest version of the transformers. Thanks!
Just another side note that I think you were trying to use ignore_index to exclude pads from the loss function and the final predicted output, and it actually worked well for the two sample datasets. However in my case I was getting lots of "PAD" for the final prediction results where it should actually be "O" category, and I think the pad was actually not excluded.

Great! Thank you for reporting the bug:) I'll close this issue.


Onchain price

Description
What's done:

Balancer on-chain price.
Update index.go to handle UniswapGetter, BalancerGetter index types.

WIP

UniswapGetter price calculation logic needs some tests.

Refs
closes #280

Pull Request Test Coverage Report for Build 463995246

168 of 306 (54.9%)  changed or added relevant lines in 5 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage increased (+1.2%) to 36.787%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/tracker/index.go
11
14
78.57%

pkg/rpc/abiCodec.go
4
8
50.0%

pkg/tracker/balancer.go
60
86
69.77%

pkg/rpc/mock.go
0
42
0.0%

pkg/tracker/uniswapTWAP.go
93
156
59.62%

Files with Coverage Reduction
New Missed Lines
%

pkg/tracker/retryFetcher.go
2
90.7%

pkg/ops/util.go
3
0%

pkg/rpc/contractRPC.go
13
0%

Totals

Change from base Build 461408608:
1.2%

Covered Lines:
1619

Relevant Lines:
4401

💛  - Coveralls

Pull Request Test Coverage Report for Build 463995246

168 of 306 (54.9%)  changed or added relevant lines in 5 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage increased (+1.2%) to 36.787%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/tracker/index.go
11
14
78.57%

pkg/rpc/abiCodec.go
4
8
50.0%

pkg/tracker/balancer.go
60
86
69.77%

pkg/rpc/mock.go
0
42
0.0%

pkg/tracker/uniswapTWAP.go
93
156
59.62%

Files with Coverage Reduction
New Missed Lines
%

pkg/tracker/retryFetcher.go
2
90.7%

pkg/ops/util.go
3
0%

pkg/rpc/contractRPC.go
13
0%

Totals

Change from base Build 461408608:
1.2%

Covered Lines:
1619

Relevant Lines:
4401

💛  - Coveralls


Include inherited members in documentation of class

Update the markdown generator to optionally include inherited members of a class. Mark them as inherited.

:tada: This issue has been resolved in version 0.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.12.0
GitHub release

Your semantic-release bot :package::rocket:


terminal-icons: Add version 0.9.0

[x] I have read the Contributing Guide.

Add a note "Nerd font is required for this module to work".
(suggest cannot be added because there can be multiple nerd-fonts).


Maybe we can remove it?

@caarlos0 we could remove the entries but someone could just add them back unfortunately. We need a better way of determining what can go into high scores. We might want the repo to have a minimum number of stars for example. Something that makes it easier to distinguish the real repos from the fake ones.

@caarlos0 either way I'll go in and remove them. Maybe people will be nice and not add fake repos before we figure out a long term solution 😄

@caarlos0 they're removed now. We can revisit if this happens again. Thanks!

Thanks :D

but someone could just add them back unfortunately.

that's why we can't have nice things :(

great project, by the way 🍻


Standardize identifiers

Ready for merge now. ./run_tests.sh pass locally.

I don't see any CI runs.

I strongly advice you to adjust your core so no errors are triggered by sanitiizers.
Next up is:
./run_tests_with_gcc_sanitizers.sh
parser/metac_parser.c:2760:22: runtime error: store to misaligned address 0x7f80b9a5da24 for type 'struct decl_parameter_t *', which requires 8 byte alignment
0x7f80b9a5da24: note: pointer points here
  80 7f 00 00 00 00 00 00  00 00 00 00 00 00 00 00  be be be be be be be be  be be be be 68 00 00 00

.

yeah the alignment constraints are a problem.
In theory, but not in practice.
I am going to squash your PR into one commit and merge it as a whole.

Thanks for approving!


Neural Network Ansatz of the WF

We can use NN to define the WF and optimize it. There is a notebook that does VMC with NN ansatz for 2D Ising lattice :
https://colab.research.google.com/drive/1LHvyDpfj5GwooqyDKi02hj1xchemPWko.

Someone master thesis
Qflow (VMC with Neural Net)
https://bsamseth.github.io/thesis/index.html


Add optional requirements to a txt file for Docker caching

Closes #478
Code Changes

[ ] add a file for optional dependencies
[ ] Update the dockerfile to copy and install these before pip install -e .

Steps to Confirm

[ ] all of the checks pass
[ ] local commands work as normal
[ ] local builds take much less time

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
[ ] Documentation Updated
[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created

Description Of Changes
Write some things here about the changes and any potential caveats

new build process took 13.1 seconds when the requirements were cached via optional_requirements.txt
old build process took 35.1 seconds when the requirements were loaded at pip install -e . command
This gap will grow much wider when dealing with less resources, definitely worth the change


Provide a better "raw sql" escape hatch for full queries that we don't support in the query builder

Today we have some form of an escape hatch in the form of the sql function. However, it's meant for use with small fragments, not full queries. It's limited because it requires specifying the full SQL type of the output, and cannot handle bind parameters. I'd like to introduce a new function that is a more ergonomic API for raw SQL as an escape hatch for queries we don't support in the query builder yet.
Ultimately I've resisted introducing this, as we want to support all possible safe queries in the query builder eventually, but I think we need a proper escape hatch for us to go 1.0.
I'd like this API to be fully untyped, and named to make it clear that no verification of the query is occurring. For deserialization, it should not go through Queryable, as I do not think enforcing column order is ergonomic when writing raw SQL (and Queryable needs a SQL type to work). Instead I'd like to introduce an UntypedQueryable, which takes a row directly, and is able to fetch fields by name. I'm fine with the API requiring specifying the SQL type on this call if type inference can't pick it up. e.g. let updated_at: NaiveDateTime = row.get::<Timestamp>("updated_at")?. I suspect for most types which only implement FromSql for a single DB type type inference will handle it, but we should explore our options here and see what feels best.
I'm less clear what we should do with bind parameters. I do know that I don't want to go the route that the postgres crate went where we take &[&UntypedToSql], as constructing that value is painful, it forces dynamic dispatch (which then usually also forces boxing), and requires &[] for queries with no bind parameters. We could potentially still pass tuples here as long as type inference does what we want. I also think conn.raw_query("SELECT * FROM users WHERE id = $1").bind(id) could work (as an aside, I think we will likely need to pass the connection in before the bind parameters for this to work, which will lead to a semi-weird api of conn.raw_query().bind().execute()). I'm fine with also sometimes requiring giving a SQL type for the bind here as long as type inference is able to handle the most common cases.

I'm new to Rust and Diesel. but what I love is type safety and all great things LoadDsl does. That's why I'd prefer "better sql" instead of new untyped API.
Nice ORMs like ActiveRecord and Django's ORM allows to put bits of SQL but keep the rest of code working with typed models.
I'm playing with Diesel and see a lot of limitations (like inability to make multiple joins or multiple belongs_to) and that's ok. Even with raw SQL Diesel is still great.
I created couple workarounds to solve issues with raw sql queries.
First is obvious -- no binds so I just use PQescapeString.
Second one is unpredictable order of columns in queries with *, so this ugliness was born https://gist.github.com/andy128k/b3cae82d13e38f51c4c5bf56f5d6540a


Security Oversight

I think it might be fair to expect device manufacturers to take some responsibility for how data is processed and security managed by each of their contractors that process data on their behalf. For example, we could ask manufacturers to require evidence of independent security assessments of systems from their service providers (that process user data on behalf of the manufacturers). It may seem strong but it is in line with some of the recommendations and requirements set by governments (e.g., I believe compliance with GDPR also means that companies must ensure that third-parties who process data on their behalf implement the required technical and organizational measures.)
What are your thoughts @j-br0 ?

So under Security Oversight we would add an indicator that states: "The company ensures that third-parties who process data for the company implement the required technical and organizational measures."? Or should the language be broader?
And thanks for offering this issue, @TatevSarg :)

Interesting. I created https://github.com/TheDigitalStandard/TheDigitalStandard/pull/118 to see how it feels in place.


Cannot build GmsCore against local version of SafeParcel

I'm trying to compile both SafeParcel and GmsCore locally (trying to fix a crash in SafeParcel). I have both git repo. I'm compiling SafeParcel with:
./gradlew assembleRelease
./gradlew publishToMavenLocal

This creates safe-parcel-1.6.0-dirty in my local maven repository (it's "dirty" because I changed the log string for unknown field ID, as a tag to make sure GmsCore is using my local SafeParcel version).
In GmsCore, I've made the following changes to make it use my local maven repository:
diff --git a/build.gradle b/build.gradle
index de25a6f..1ba285a 100644
--- a/build.gradle
+++ b/build.gradle
@@ -6,7 +6,7 @@
 buildscript {
     ext.nlpVersion = '2.0-alpha3'
     ext.remoteDroidGuardVersion = '0.1.2'
-    ext.safeParcelVersion = '1.6.0'
+    ext.safeParcelVersion = '1.6.0-dirty'
     ext.wearableVersion = '0.1.1'

     ext.kotlinVersion = '1.3.72'
@@ -109,6 +109,7 @@ def versionName() {

 subprojects {
     repositories {
+        mavenLocal()
         jcenter()
         google()
     }

However, the resulting GmsCore APK still uses official upstream safe-parcel-1.6.0, and I can't make it to use my local version. How can I achieve that?

It turns out org.microg.gms:remote-droid-guard has also a dependency on safe-parcel, and when using the upstream release, gradle resolves to use the upstream version instead of the local one. The solution is to also compile RemoteDroidGuard locally, against local version of SafeParcel. Then use the local version of RemoteDroidGuard in GmsCore.


How Can I change the Dark theme to light

I have Purchase React Admin Panel v4 Pro version which comes with Default theme. Can you Please guide me how can I change that to Light theme

@muhammadadnan97 please go to src/components/AppSidebar.js add add  colorScheme="light" to <CSidebar> component

@mrholek  Thanks it's work now. but looks like scrollbar style is missing still.

@muhammadadnan97 what is your browser and OS, I will check it.

Google Chrome, Windows 11

Google Chrome, Windows 11
On Tue, Feb 15, 2022 at 3:49 AM Łukasz Holeczek @.***>
wrote:

@muhammadadnan97 https://github.com/muhammadadnan97 what is your
browser and OS, I will check it.
—
Reply to this email directly, view it on GitHub
https://github.com/coreui/coreui-react/issues/256#issuecomment-1039650752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEVSBHCNBYMBR4464D2NR3U3GBHJANCNFSM5OMRKB6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


(PUP-6148) Fix problem with Callable#assignable? and undefined method

The Callable#assignable? would raise an undefined method when passed
a callable that didn't have any parameter definition. This commit fixes
that problem.

CLA signed by all contributors.


Exceptions are being lost at InpcPropertyAccessorPlugin.SendCurrentValue

Current implementation of InpcPropertyAccessorPlugin swallows all the exceptions:
https://github.com/AvaloniaUI/Avalonia/blob/38e839997d2c204548e6fad396c178780a010cb1/src/Avalonia.Base/Data/Core/Plugins/InpcPropertyAccessorPlugin.cs#L180
Probably no need to elaborate the outcome of an application silently resuming after a failure? In best case it's just difficult to spot and debug.
In my case stacktrace is about 'property changed' -> 'ui updates' -> 'binding reads a value' -> 'exception happens' -> 'exception lost':

I think this catch can be just removed? not sure what it is supposed to do besides hiding bugs.
Just as an idea, may be, an analyzer of ca1031 can be introduced into the project to prevent such issues in the future?

Is workaround possible here? Can the plugin be replaced?

There's a draft PR to improve the binding system. Can you probably test it's preview package with your usecase and feedback if it works better for you? https://github.com/AvaloniaUI/Avalonia/pull/13970#issuecomment-1878906233

It is by design, as with InpcPropertyAccessorPlugin enabled developer can throw validation exception from properties, which shouldn't break the app, but instead should populate visual Control with the error state (normally, using DataValidationErrors control, that is integrated into most controls).
And InpcPropertyAccessorPlugin is enabled by default, and can be disabled as you did, or just removed from the list.

There's a draft PR to improve the binding system. Can you probably test it's preview package with your usecase and feedback if it works better for you? #13970 (comment)

Thank you. Will take time to check.

It is by design, as with InpcPropertyAccessorPlugin enabled developer can throw validation exception from properties, which shouldn't break the app, but instead should populate visual Control with the error state (normally, using DataValidationErrors control, that is integrated into most controls). And InpcPropertyAccessorPlugin is enabled by default, and can be disabled as you did, or just removed from the list.

But it catches not only validation exceptions, but all exceptions like OutOfMemoryException for instance.

You can use any kind of exception for validation purposes. And OutOfMemoryException cannot be caught as well as StackOverflowException.

You can use any kind of exception for validation purposes. And OutOfMemoryException cannot be caught as well as StackOverflowException, that's a platform/.NET limitation.

OOM was always possible to catch, you can try yourself:
try
{
    _ = new byte[int.MaxValue];
}
catch (OutOfMemoryException)
{
    Console.WriteLine("OOM Exception");
}

Console.WriteLine("Hello, World after OOM!");

OOM sure has different behavior on different versions of linux, but in general it can be raised and caught, especially on windows.
Besides OOM there are number of exceptions which are generated by platform, like FileLoadException on dll failure or TypeInitializationException. It just looks strange that all of this are considered as validation errors.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: f05ee35231a5f783e8861a91697c0f1ab2533ea6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


angular7-example-app to 7.0.99

Promote angular7-example-app to version 7.0.99

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


RFP: Collective Archive Maintenance

Foundation Mission (RFP) – Collective Archive Maintenance

Foundation Mission Summary: Make the Collective DAO Archives easier to use, update, and understand
S4 Intent: Improve Governance Accessibility
Proposal Tier:  Ember
Baseline grant amount: 30k OP
% of total available Intent budget: X%
Should this Foundation Mission be fulfilled by one or multiple Alliances: One
Optimism Foundation point-of-contact: Justine (@justine-hy)
Submit by: June 28th at 19:00 GMT
Selection by: July 13th at 19:00 GMT

How will this Foundation Mission (RFP) help accomplish the above Intent?:
The Collective Archives were open sourced as a public good to advance the development of DAOs in the ecosystem. However, the Collective Archives are currently hard to navigate and there is no scalable framework for contributors to update, maintain, and/or expand these resources. Making the Archives easier to use, understand, and update these resources will allow more people to learn, and share their own learnings, improving the accessibility of our governance research and advancing our collective governance intelligence.
What is required to execute this Foundation Mission (RFP)?

Create an open source framework for anyone to update the Collective Archives
Create an improved user interface so the Collective Archives are easier to navigate

How should the Foundation measure progress towards this Foundation Mission (RFP):

Number of accepted updates to the Collective Archives during the Season (may be approved pull requests)
Number of contributors actively updating the Collective Archives
Number of views of the Collective Archives (ideally on a dedicated hosted site for the Archives)

How should badgeholders measure impact upon completion of this Foundation Mission (RFP)?

Number times the Collective Archives are referenced externally
Any personal benefit from using the Collective Archives

Application instructions
To apply for this RFP, please complete the form in the expandable section below and leave. Submissions will be open until [June 27], at which time the Foundation will review all submissions and select one individual/team to complete the work defined here.

Submission form
Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary.
Foundation Mission (RFP) Application
Please verify that you meet the qualifications for submitting at the above Tier

Alliance Lead: Please specify the best point of contact for your team
Contact info:
L2 recipient address:
Please list the members of your Alliance and link to any previous work:

_What's an Alliance?_
Alliances are groups of contributors that *temporarily* work together to accomplish a Mission start-to-finish. This can be an established protocol or project or a group of contributors working together for the first time. Name your group, now you’re an Alliance :)

What makes your Alliance best-suited to execute this Mission?

[...]
[...]

Please describe your proposed solution based on the above Solution Criteria (if applicable):

[...]
[...]

Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:

[...]
[...]

Please define the critical milestone(s) that should be used to determine whether you’ve executed on this proposal:

[...]
[...]

Please list any additional support your team would require to execute this mission (financial, technical, etc.):

[...]
[...]

Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant: (Note: there is no guarantee that approved Missions will receive up-front cash grants.)

[...]

Please check the following to make sure you understand the terms of the Optimism Foundation RFP program:

[ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the Operating Manual
[ ] I confirm that I have read and understand the grant policies
[ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
[ ] I understand that I will be expected to following the public grant reporting requirements outlined here

-- end of application --

Hello! I want to express my interest in pursuing this RFP and ask some clarifying questions:

Can I have access to the Collective Archive?
How are these collective archives currently stored? Is the goal to expand on their current form or use a different structure?
Can I schedule sometime with the current maintainer (@justine-hy) to get more information?

You can reach me here or:

email<EMAIL_ADDRESS>telegram: @sbvegan

Kind regards,
soyboy

Hi! Can I get clarification on two points:

This link in the application is private - is there a separate Tier verification process we should be following?

Please verify that you meet the qualifications for submitting at the above Tier(https://www.notion.so/Collective-Trust-Tiers-need-links-from-Vee-f2f0c9dafaf9419d8d79bae125042c3b)

Is the link referencing an example discussion to set expectations for clarity of milestones?

Please define the [critical milestone(s)](https://gov.optimism.io/t/ready-gf-phase-1-proposal-karma-discourse-forum-plugin/3412/11) that should be used to determine whether you’ve executed on this proposal:

Indicating that we have been in touch with @sbvegan to clarify the above questions
@amy-jung links have been updated, thanks for flagging!

Hello ! Is there any updates on this topic ? Otherwise i think i can quickly build an alternative with better experience (using no code) while waiting for a development

Hi @JeanGuillemont! Thanks for your interest in this Foundation Mission. Applicants have until June 28th to submit their applications. I believe there are some contributors that have made some progress on this, but tagging in @sbvegan and @amy-jung to provide updates if they have any.
The Foundation will make a selection by July 13th (end of Voting Cycle #13.)
I'll update the text above to make sure this is clear, thanks for raising!

Hey @JeanGuillemont, for some context, @amy-jung has been working hard to iteratively improve the Collective Archives. The bulk of the proposal has been completed and I believe she's getting ready for submission. You should reach out to her directly and see if she can use any additional help!

Hi ! Thanks for the update ! I'll let @amy-jung ping me if she needs any help

Hey @JeanGuillemont! Do you have telegram (Mine is @rawhaus)? If not, shoot me your email. We can talk there :)

Hello! Very excited to officially submit this application with my friend @carletex
Please verify that you meet the qualifications for submitting at the above [Tier] (Ember):
Yes, Ember
Alliance Lead: Amy Jung
Contact info:
Email<EMAIL_ADDRESS>L2 recipient address:
oeth: 0xEb31303Be09e9279F2046e6019502901AB2B6437
Please list the members of your Alliance and link to any previous work:

Amy Jung (Product Lead, Design)

Background in Design, Operations, and Community Development. Previously, she served as Head of Community Development at MakerDAO. (Her work is highlighted in the Wizard of Dapps podcast.) Currently writing a book on DAOs and Progressive Decentralization.

Carletex (Development)

Software developer for over 12 years. He has been working in the Ethereum ecosystem since 2021, focused on developing OSS & public goods such as Scaffold-Eth-2, AbiNinja, and SpeedRunEthereum. Currently he is a core member of BuidlGuidl.

What makes your Alliance best-suited to execute this Mission?
Our team’s experiences and skillsets in open source projects provide a strong foundation for bringing this Collective DAO Archives Catalog to life. Between our team, we cover the range from design to engineering. Additionally, our team's contributions to relevant open source projects demonstrate our commitment to open collaboration and public goods:

Scaffold-Eth-2, an open-source, up-to-date toolkit for building decentralized applications (dapps) on the Ethereum blockchain.
SpeedRunEthereum, a structured learning path for onboarding developers to Ethereum.
MakerDAO Community Portal, a fully community developed, open source resource site, which grew to 25+ contributors, and was eventually forked by Kernel.

Please describe your proposed solution based on the above Solution Criteria (if applicable):
The Collective DAO Archives Catalog aims to create the most user-friendly, open-source platform that captures, indexes, and archives a comprehensive list of events and challenges from existing DAOs. This site will enable anyone to navigate and contribute to a knowledge base that leverages the power of collective intelligence. By collecting and sharing information about DAOs, the Catalog will allow new and existing DAOs to learn from each other's experiences and identify patterns that can inform their development.
The Catalog will be designed to be user-friendly and intuitive, with clear categorization and search functions that enable easy navigation. In addition, the platform will be built with flexibility in mind, allowing for the addition of new features as the DAO ecosystem evolves.
User Type

DAO Builders: The Catalog is intended for contributors or leaders of DAOs who are looking for insights into commonly used practices and roadmaps for building DAOs/orgs.
DAO Tooling/Service Providers: The Catalog can also be used by tooling and service providers who need to contextualize the challenges across many DAOs and shed light on unmet needs and opportunities for improvement.

Contributor Type

Technical Maintainers and Contributor: The Technical Maintainer(s) is a key role for the longterm success of this project. Their roles would be the technical maintenance and hosting as well as the qualitative assessment for PRs being merged. Additionally, contributors who would like to extend the functionality and features of the platform can submit PRs.
Content Creators: The Catalog will engage content creators who are interested in contributing to or expanding on topics related to DAOs, helping to build a comprehensive knowledge base.

Desired Outcomes

User Friendly: The Collective DAO Archives Catalog will prioritize easy navigation, search, and discovery to ensure accessibility to a wide range of users.
Encourages Contribution: The Catalog will actively promote community participation through clear contribution guidelines, marketing, and outreach.
Minimum Viable Foundation: The Catalog will provide a flexible and adaptable framework for organizing information and extending platform features.

The MVP will contain:

A more accessible, user-friendly web interface with:

Advanced search and filtering, allowing users to filter by time range and other metadata for easier navigation and discovery of content in the Catalog.
Records page view, allowing users to view short details and source links to each DAO event.
Collections, allowing users to save and publish search results into one collection.

The site will be built with:

NextJS: Full-stack framework
Tailwind: CSS framework
wagmi / rainbowkit: connect wallet / Sign with Ethereum
Hosted on Vercel

Recategorizing the content and establishing a standardized structure to make it easier for users to find what they are looking for and/or contribute. Feedback and insights will be gathered through user interviews.
Detailed contribution guidelines and processes to encourage contributions from the community. The contribution process will include review and approval by moderators to ensure the accuracy and relevance of the content.

This is a video walk through (slightly out of date version) that visualizes what we’d like to build.
Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each piece of work:

Please define the critical milestone(s) that should be used to determine whether you’ve executed on this proposal:
Please note, all milestones dates are dependent on proposal acceptance.
Milestone 1: Site Scaffolding

User interviews to review contribution process and UI/UX
Clean and updated database with categories and tags
Migrate records from Notion to Github
Set up domain, NextJS project + dependencies
Auto-deployment to Vercel with GH repo connection

Milestone 2: Front-End Pages

Setting front-matter / markdown
Site Pages

Home Page
About Page
Contribute Page
Records Page
Collections Page

Milestone 3: Search and Collections Functionality

Search and Filter Records. Keyword search all records and filter fields (i.e. categories, organizations, etc).
“Collections”. Save and publish search results into one collection, using SIWE.

Milestone 4: Outreach and Launch

Technical and Content Contributor Guidelines
Twitter and Forum Post Announcements
V2 Ideas queued for contributors.

Please list any additional support your team would require to execute this mission (financial, technical, etc.):

Work with Justine (@justine-hy) to include her recent updates to the database
Marketing support post-launch to drum up interest in the resource and source potential contributors and maintainers.
Determine if website hosting, licensing, and repository should live under the Optimism Foundation’s control

Note: All work will be open source and forkable

Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant: (Note: there is no guarantee that approved Missions will receive up-front cash grants.)
No
7. Please check the following to make sure you understand the terms of the Optimism Foundation RFP program:

[x]  I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the Operating Manual
[x]  I confirm that I have read and understand the grant policies
[x]  I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
[x]  I understand that I will be expected to following the public grant reporting requirements outlined here

Hello!
Carlos and I wanted to give an update since our submission.
In the past weeks, we chatted with a few collaborators who reached out. These discussions prompted some interesting conversations, including one with Rafa who is interested in building an AI chatbot with the Collective Archives. (We have a shared channel with the OP team to test and better understand the boundaries of a conversational bot. Timing wise, we’ve discussed collaboration / integration towards the end of our V1 build. 🥳)
TL;DR: Through these discussions, we saw a lot more ways to grow the Collective Archives. We will continue to build a user friendly interface to improve the readability and contribution to the Collective Archives. However, instead of focusing on a static site to read data, we will lean into how contributors can actively integrate and build ways to engage with the data.
Our Expanded Vision:
The core mission of the Collective DAO Archives Catalog still aims to create the most user-friendly, open-source platform that captures, indexes, and archives a comprehensive list of events and challenges from existing DAOs.

📌 For short, we reference these DAO events and challenges as “DAO Events”, which is any relevant occurrence in a DAO or DAO-adjacent org’s lifecycle, currently indicated by a public document on any platform like Discourse or Twitter.
An example is a post of Uniswap introducing V4, Launching a Grants Program, or a Temperature Check Proposal to create the Uniswap Foundation.

We believe there’s invaluable insight in how people access off-chain DAO Events and their discussions. Our big vision is to expand the existing Collective Archives by building the largest, most reliable database for querying across all these DAO Events. This bridges qualitative information across all DAOs into one searchable, source of truth. This enables anyone to contribute, integrate, and extend ways to engage with that data. For example, a chatbot is a conversational way for users to ask, read and understand the data. Or Tally.xyz could provide the link to on-chain data results of discussions.
How It Affects Our Build:
We will still ship a simple user friendly interface where people can contribute to the archiving of DAO Events (i.e. posts), as well as have the ability to search, read, save, and share their searches (“Collections”). All the milestones remain the same. However, with the expanded vision in mind, it became clear we needed a more scalable option. Therefore instead of a markdown / static site generator approach, we’ve started to take a database approach.
Updates on Our Build:
While it’s still early, you can follow our current development in our Github Repo: https://github.com/amy-jung/collectivedaoarchives.catalog. What we’ve been working on thus far:

Site scaffolding is up!
Wallet integration is complete.
We’re developing and architecting the database so we design toward our vision for future extensibility.
We’ve updated and cleaned up the current Collective Archives data (We’re now at 1089 entries! 🚀)
We’re researching on how we can best automate fields from source links to simplify contribution UX.

Our V2/ Near Future goals: We’re looking into simplifying the contribution UX by auto-populating content with just a submission link (similar to https://archive.ph/), and reducing platform dependability by archiving posts using Arweave or IPFS. We’d also like to launch an API for people to integrate and build ways to engage with that data.
Please feel free to reach out with any questions! 🙂

Hello everyone! Super excited to submit our plan to successfully execute this mission, and help the Collective Archive to thrive!
Alliance Lead: Max Lomuscio
Contact info: Github, Twitter, Telegram: @maxlomu
L2 recipient address: 0xd333bc5c9670c9ceb18f9a2cf02c6e86807a8227
Please list the members of your Alliance and link to any previous work:

Max Lomuscio, protocol expert from Connext, and delegate for several DAOs. Previously a protocol delegate for the Optimism Collective
The Duke of Content team (Preetham): experts in OpenAI and automation, the team has been working on an independent solution to interpret, digest and repurpose content using artificial intelligence.

What makes your Alliance best-suited to execute this Mission?
Max's extensive knowledge in DAO & online organizations, and Preetham's proficiency in user-centric design and AI technology leadership form the backbone of our project, making us uniquely qualified to execute this mission. Our blend of technical expertise and solution-oriented vision enables us to dream big and execute fast.
Please describe your proposed solution based on the above Solution Criteria (if applicable):
In the era of AI and advanced chatbot technologies, user expectations around information discovery have fundamentally shifted. Rather than having to sift through potentially dense and jargon-laden resources (or intricated directories), users now expect immediate, concise, and accessible answers that draw on best practices.
The Archives should embrace this paradigm shift to drastically improve accessibility and understanding of DAO-related resources.
Our plan is to create a chat-and-dashboard interface, utilizing OpenAI's technology to deliver organized, cohesive answers based on the collective knowledge derived from DAOs. The objective is to significantly improve the navigation, exploration, and understanding of the Collective Archives, transforming the way users interact with DAO-related resources.
The platform will analyze all the forum posts, proposals, and entries currently in the Collective Archives and create a structured, indexed database. Our tailored AI solution, built on top of OpenAI, will reconstruct answers in a user-centric format based on specific queries, with the capacity to continuously learn and improve from user feedback.
Users can ask questions like "How do I structure a new DAO?", "How should contributors be rewarded?", or "Best practices for liquidity mining programs". The system then provides the best possible synthesized answer, referencing the breadth of collective wisdom within the DAO community.
To ensure the ongoing accuracy and relevance of the resources, the platform will also facilitate community contributions. Users can add new resources by submitting a link through a webpage. A whitelist system will be in place to prevent spam and maintain the quality of submissions. This approach ensures that the platform remains an up-to-date, dynamic repository of DAO knowledge.

MVP
For the initial launch, the team will focus on delivering a highly functional, user-friendly system. The MVP will contain the following key features:
AI-Driven Interface: Users can interact directly with an AI model trained on the Collective Archives. This AI will be capable of parsing user inquiries and providing relevant, comprehensive responses based on the knowledge extracted from the archives.
Database of Indexed Resources: The system will have a comprehensive, structured database created from existing Collective Archives resources. This database will be regularly updated and maintained for the AI to draw upon.
Community Contribution System: An easy-to-use web interface for the community to submit new resources. These submissions will undergo a review process before being added to the structured database.
Whitelist System: To maintain the quality of the resource database and prevent spam submissions, the MVP will include a whitelist system. This will permit only approved users to contribute new resources to the platform.
User Feedback Mechanism: A system to collect and process user feedback on AI responses. This will serve as a critical input for the ongoing training and improvement of the AI model.
Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each piece of work:

Set up the necessary infrastructure to analyze and catalog existing Collective Archives resources (2 weeks)
Train the AI model on the structured database (1 month)
Implement the interface and integrate the AI model (2 weeks)
Conduct thorough testing and iterate based on feedback (2 weeks)
Official launch of the Collective Archives new interface

Please define the critical milestone(s) that should be used to determine whether you’ve executed on this proposal:

Successful cataloging of existing resources: have all governance forum posts linked here been indexed?
Training and integration of the AI model: is there an interface that can be used to query the indexed resources? Are the answers coherent with the questions?
Beta testing and user feedback: receive feedback from at least 30 people. Achieve a minimum average rating of 6/10.
Official launch and community contribution initiation: has there been an announcement of the project? Are people able to submit new resources?

The team will periodically share data on the progress of the project:

User feedback and AI learning improvements
Number of questions answered by the AI
Usage statistics of the platform
Number of new resources added by the community

Please list any additional support your team would require to execute this mission (financial, technical, etc.):

Marketing support to promote the projects among DAOs and other contributors

Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant: (Note: there is no guarantee that approved Missions will receive up-front cash grants.)
While the initial grant is anticipated to cover the setup, training, and first year of maintenance, we acknowledge that the project’s innovative nature presents a different cost structure compared to a traditional static directory. After 1 year, we propose that the Optimism Collective evaluates the project's impact and potential for a recurring grant to ensure its continued operation.
To reiterate on previous answers, this is more than a chatbot, this is much more than a directory. It's a great mix tailored to the needs of DAO members and builders.
By adopting a cutting-edge AI solution to navigate the Collective Archives, we believe we can make DAO-related resources more accessible, contributing to the growth and development of the broader DAO ecosystem.

Please check the following to make sure you understand the terms of the Optimism Foundation RFP program:

YES I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the Operating Manual
YES I confirm that I have read and understand the grant policies
YES I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
YES I understand that I will be expected to following the public grant reporting requirements outlined here
Thank you for reading, and looking forward to your feedback!

Submissions for this RFP are now closed. Thanks to everyone who submitted a proposal!
Someone from the Optimism Foundation will reach out on or shortly after July 13 to communicate which proposal(s) have been accepted and schedule a kickoff. We may also reach out individually using the contact info you've provided if we want to discuss your proposal in more detail.
In the meantime, feel free to tag me here or reach out directly<EMAIL_ADDRESS>with any questions.

Thank you all for your submissions! We are very excited to move forward with Amy Jung's submission  to convert the Archives into an extensible database and open source contribution framework.
Once this foundational infrastructure is built, we may decide to open additional RFP(s) to layer on add AI or other capabilities.
@amy-jung, Anton, from our Finance team, will be in touch with you shortly to process your grant!

July Update
Hello! We're so excited to be recipients of this grant :) Big thank you to the OP team!
Moving forward, we'll be giving updates at the end of each month here in this Github Issue.
You can follow our updates in real time in our Github Repo: https://github.com/amy-jung/collectivedaoarchives.catalog
Context
Our Goal: Build the largest, most reliable database for querying across all DAOs to bring qualitative information of DAO Events into one searchable, source of truth.
As we mentioned in our previous update, we've switched from building just a static front-end to a database model with a particular focus on openness of the data and people integrating their app/models with our data.
What We’ve Been Working On

We’ve added Damu to our team for extra support when Carlos’ baby arrives 🐣
As part of our updated database goals, we redesigned the architecture (backend + database + front-end):

Split the original NextJS/full-stack APP solution into a back-end (NodeJS/ExpressJS) and front-end (NextJS) to avoid bottlenecks with NextJS API routes when scaling the API.
Switched to a monorepo structure.
We have a backend with a basic API: https://dao-catalog-api-5a6466df16c9.herokuapp.com/
We have a live, working front-end (that uses the backend API as data source): https://collectivedaoarchives-catalog.vercel.app/
Updated the README with dev instructions to run locally.
Added docker-compose file to spin a Postgres database locally.

UX & UI:

Simplified contribution flow. People interested in contributing DAO Events can just submit one or multiple URLs (where we will auto-populate content) instead of Github/ Manual Form. 🥳
We've been working on auto-populating content from a URL in the back-end. We will now have content from the original source to be available on our site. It will also open up the option for us to future proof / archive the content.
We've included 2 new fields for each record: author and original post date.

Changes:

We will be backlogging "Collections" feature for now.
For now, we are only including information that is publicly available (ie. no token gated posts).

In Paris, we caught up with Dennis from Tally to discuss using their API for linking on-chain data.

🔮 Next Up
We’ll be focusing on implementing search and turning the Figma UI prototypes into reality.
Til next time! 🚀
Amy, Carlos, and Damu

August Update
Hello! It’s been a slow month for us. Amy has been splitting time with another project and Carlos shipped his biggest PR yet! 👶 He’s on paternity leave 🥳
🛠 What We’ve Been Working On:

Content: We did a huge clean up, updating all of the content (broken links, correcting titles, etc). Part of this process is cleaning and stylizing the raw html content to be available on our site.
Search: Damu got the starting points of search set up. PR is awaiting review for when Carlos is back https://github.com/amy-jung/collectivedaoarchives.catalog/pull/24
UX & UI: Amy’s been working on developing the brand and UI components. This will introduce a new logo and brand style guide.

🔮 Next Up:
We’ll continue to build out the front-end pages, as well as test and improve search.
Til next time! 🚀
Amy, Carlos, and Damu

Hi @amy-jung! Checking in to see if you have another progress update to share with the community?

Sept/Oct Update
Hello! Apologies for missing the last update. We had a brief hiatus but great news, Carlos is back from paternity leave ☺
We’ve been slowly pushing updates. The staging site has technically been up for awhile, but we’ve been polishing and improving UI + functionality before pushing live.
🛠 What We’ve Been Working On:

Search is live 🥳 Check it out. (Try searching topics like ”governance framework” or “grants.”) We’ll have a more formal user testing session coming soon, but if you find any initial errors or bugs, please ping us or leave a Github issue.
Design / UI:

UI improvements on the long-form records: For most records, we’ve managed to pull the original content then clean and reformat the html to display on our UI. However, we’ve been discussing the best way to stylize given the content is varied and inconsistent. We knew it was a difficult challenge to approach, but we’re determined to ship something crisp 🍂
Created a logo and brand style guide.

Improved documentation (especially the prisma/data) for project contributors.
Updated Database: We’ve been updating the database as we go to ensure it’s synced with the Collective Archives when it’s live.

🔮 Next Up:

Design: We still have small UI updates and improvements, including finalizing long-form content style for the Records page.
Contributions Page: We added an additional feature for contributors to submit multiple URLs through a CSV file. Once we finalize the contribution flows, we’ll update the Github repo’s contribution wiki.
Add About / Footer.
Add Advance Search: Search by categories.
User Testing Sessions

Til next time! 🚀
Amy, Carlos, and Damu

November Update
Hello! It’s only been two weeks, but we have some updates 🚀
🛠 What We’ve Been Working On:

Fixed a few bugs
Pages:

Home Page: Added logo and updated with brand style guide.
Records Page: Improved and finalized long-form content style so text looks much cleaner 🥳 (example)
Added About Page and Footer.
Designed No Results Page.

Contribution Flow: We mapped out content/URL contributions flow from user to backend.
Started outreach for User Testing Sessions.

🔮 Next Up:

User Testing Sessions: We’ll be organizing sessions with an initial set of users to better understand contribution and search behaviors as well as get user test/get feedback our current staging site.
Contributions Flow: We’ll build out a single URL and textarea logic for now and finalize CSV via user testing.
Search:

Improve search experience https://github.com/amy-jung/collectivedaoarchives.catalog/issues/46
Build “Advanced Search” filters and explore categories

Adding small UI updates (page loader, styling tweaks, etc)
Updates to database: We’ve been updating the database as we go to ensure it’s synced with the Collective Archives when it’s live. We’ll do another sweep.

We’re aiming for a soft launch by end of the year for folks to test and play around during the holidays. Then we’ll have official marketing push for January ❄
Til next time! 🚀
Amy, Carlos, and Damu

December Update
Hello! Here’s our final update of the year before we break for the holidays ❄
🛠 What We’ve Been Working On:

Pages:

Damu & Carlos shipped the Contribute Page: Now individuals can submit URLs to contribute to the database! To prevent sybil and spam (and enable potential POAPs or attestations in the future), submitting URLs will require a signature. In the next iteration, we aim to automate attestations to streamline the process! For now, we'll handle it manually.
Backend development of “Advanced Search” is complete and we’ve finalized the front-end design.

UI Updates:

We’ve introduced a page loader.

User Testing Sessions: We've reached out to 10 users, conducted 3 sessions so far, and have one more scheduled in the new year. The feedback on the site concept has been great! Here are some initial insights:

"Past Events vs. Most Recent Events": As we've focused on older, archived content, we've discovered that DAO researchers play a more significant role as core users and contributors. Our initial assumption that "Operators" were the power users shifted when we learned that Operators search to "retrieve what we already know happened" (Past events) but struggle to find "what we don't know" (patterns). It'll be intriguing to see how the Catalog can help unearth insights about "what we don't know."
Users are unaware that the records are manually curated, and not all forum results are in our Catalog. We should manage expectations regarding the database (explaining why certain posts aren't included or why a specific version of something might not be available) to foster trust and enhance the user experience.
It would be ideal to display the outcome and/or version of each event.
Social aspects (popularity/engagement on source posts, popular searches) are considered "nice-to-haves" but not an immediate priority. (This aligns with our initial assumption, so it's great to have it validated).

We've initiated a Launch Marketing Plan and finalized the V1 feature checklist.

🔮 Next Up:
January is all about completing Milestone 3 and progressing to Milestone 4: Outreach and Launch.
Finalize V1 features for completeness:

Implement UI of advanced search (filters, etc)
Implement a No Results Page
Finalize site analytics for measuring metrics
Database update: We'll perform a final database update via our Contribution page when it goes live!
Update documentation & create template for submitting Github issues
Minor improvements:

Ensure UI consistency
Improve search experience

Milestone 4: Outreach & Launch

User Interviews: User interviews have not only been invaluable for testing but have also helped raise awareness about the Catalog! We'll continue conducting these as part of our marketing efforts.

While we take a holiday break, we're eagerly anticipating the final stretch in the new year 🥳
Til next time! 🚀
Amy, Carlos, and Damu

Final Update
Hello! Here’s our final update 🥳
🛠 What We’ve Been Working On:
We implemented advanced search, no results page, polished UI, cleaned up mobile view, privacy-enabled site analytics, completed more user interviews and final updates to our database, and updated our contribution documentations!
Completion of Milestone 4: Outreach and Launch
Help us spread the word!
Twitter: https://twitter.com/itsamyjung/status/1759596645799334238
Mirror: https://mirror.xyz/amyjung.eth/rTJqs6I7p2AI-98GIcGS70RMQT0HI_hqKdsfFf46nOM
🔮 Next Up:
We’ve added V2 Features in our Github as well as created a template for submitting Github issues.
We really appreciate the patience and encouragement as we shipped this. Thank you all for your support! 🚀
Amy, Carlos, and Damu

Amazing to see this launch! I've put a request into our marketing team to amplify your launch tweet and we will also link to the DAO Catalogue in the Collective DAO Archives (which are getting an update at ethDenver!)


enhance build to generate pdf version

pdf needs to be

generated (either directly via asciidoc or via docbook-backend)

copied to download-location (please suggest proper location/URL)

download might be referenced from aim42.org site

wontfix for now- having content in nicely rendered html seems enough for now.


Feat: Create todolist

✅ Pull Request Checklist

[x] PR Title: [Feature/Fix/Refactor...] Brief summary of the work (branch name) #IssueNumber
[x] Verify that the commit messages are appropriate.
[x] Confirm that the request is made to the correct branch.
[x] Add Assignees and Labels.
[x] If there is someone who needs to review specific details, add them as a Reviewer.
[x] After the PR is approved, delete the branch.

🔄 Changes

This PR does the following:
I made

Create searching todolist
modify todolist api
delete todolist api

📎 Reason for Changes

to make function of todolist part

closes: #IssueNumber
👨🏻💻 Test Checklist

Performed these tests!

📌 Additional Changes or Important Notes

Wow, it seems to have implemented very important functions. Great job!

Todolist is represented in your code, goob job!

I think it is prefect logic!! LGTM


aggregator: hide "Allocating new metric"

This is useless and bloats the logs, move it to
debug.

Codecov Report

Merging #796 into master will decrease coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #796      +/-   ##
==========================================
- Coverage   49.89%   49.83%   -0.06%
==========================================
  Files          36       36
  Lines        3349     3349
  Branches      476      476
==========================================
- Hits         1671     1669       -2
- Misses       1572     1574       +2
  Partials      106      106

Impacted Files
Coverage Δ

lib/carbon/aggregator/buffers.py
93.58% <100%> (ø)
:arrow_up:

lib/carbon/log.py
58.33% <0%> (-1.52%)
:arrow_down:

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 c38400d...5d15dca. Read the comment docs.


CosmosDBTrigger: Get params from config. Errors":["Resource Not Found"]}

When I try to get params from config file with '%paramName%' to CosmosDBTrigger constructor for databaseName and/or collectionName, I get the exception: "Errors":["Resource Not Found"]
Investigative information
Environment:
Visual Studio 2017 15.3.4
Packages referenced:
Microsoft.NET.Sdk.Functions 1.0.6
Microsoft.Azure.WebJobs.Extensions.DocumentDB 1.1.0-beta4
Microsoft.Azure.WebJobs 2.1.0-beta4
Microsoft.Azure.WebJobs.Extensions 2.1.0-beta4
Microsoft.Azure.WebJobs.Extensions.Http 1.0.0-beta4
Repro steps
Scenario 1 (local computer):

Create a new Azure Function Project from Visual Studio
Add a function (I didn't find any option for CosmosDB Binding so I created using HttpTrigger)
Replace the definition of Run method with the code from below.
Define values in local.settings.json. Ex: "cosmosdbvalue": "cosmosdb"
Run the function
You can see the exception in Azure Function Cli

Scenario 2 (Azure portal):

Create a new Azure Function Project with CosmosDBTrigger.
Replace the definition of Run method with the code from below.
Add a parameter in function Application Settings. Ex: "cosmosdbvalue": "cosmosdb"
Change the Database Name of the trigger in Integrate section of the function, or change it directly in the definition of Run method with the code from below.
Save and Run the function.
Exception shown in a popup.

Expected behavior
Replace/take the values from config section.
Actual behavior
Replacement of the connection string works.
Scenario 1 (local computer):
A ScriptHost error has occurred
The listener for function 'FlightsChangeTrigger' was unable to start. Microsoft.Azure.Documents.Client: Message: {"Errors":["Resource Not Found"]}
ActivityId: f4cee1c2-d59e-4270-be44-1be024a7b9d3, Request URI: rntbd://db5prdddc03-docdb-1.documents.azure.com:11087/apps/cbec8afc-ed09-4565-be2a-46723dded3c3/services/96e5b6fe-1e52-4c3a-a392-b6a4c769ed87/partitions/fe5255a7-48cf-4c08-a402-34a296cee726/replicas/131528566198135814s/.

Scenario 2 (Azure portal):
Exception in a popup and create database with name %cosmosdbvalue%
Function ($FlightChanged1) Error: The listener for function 'Functions.FlightChanged1' was unable to start. Microsoft.Azure.WebJobs.Extensions.DocumentDB: Either the source collection 'flights' (in database '%cosmosdbvalue%') or the lease collection 'flightsleases' (in database '%cosmosdbvalue%') does not exist. Both collections must exist before the listener starts. To automatically create the lease collection, set 'CreateLeaseCollectionIfNotExists' to 'true'. Microsoft.Azure.Documents.Client: Message: {"Errors":["Resource Not Found"]}
 ActivityId: dbabbd27-f6ce-4396-a9b2-6f67ec164860, Request URI: /apps/cbec8afc-ed09-4565-be2a-46723dded3c3/services/96e5b6fe-1e52-4c3a-a392-b6a4c769ed87/partitions/fe5255a7-48cf-4c08-a402-34a296cee726/replicas/131528036531580289s.

Code
public static async Task Run([CosmosDBTrigger("%cosmosdbvalue%", "flights", ConnectionStringSetting = "XXX",LeaseCollectionName = "flightsleases")]
    IReadOnlyList<Document> input,
    TraceWriter log)

Wrong repository. Reopened: https://github.com/Azure/azure-webjobs-sdk-extensions/issues/316


WindowsEventLog MaximumSizeInBytes needs IsEnabled Parameter

The Ressource WindowsEventLog doesn't do anything with MaximumSizeInBytes if the Parameter IsEnabled is not set.
I think that behavior is based on the GUI, where the MaximumSizeInBytes Control gets deactivated if you disable the log.
I'd be nice if the Documentation would state, that you need the Parameter IsEnabled set to $true in order to use MaximumSizeInBytes.
This Ressouce does nothing:
        WindowsEventLog 'Microsoft SharePoint 2019\Operational'
        {
            LogName =  'Microsoft-SharePoint Products-Shared/Operational'
            MaximumSizeInBytes = 10240KB
        }

But this does:
        WindowsEventLog 'Microsoft SharePoint 2019\Operational'
        {
            LogName =  'Microsoft-SharePoint Products-Shared/Operational'
            IsEnabled = $true
            MaximumSizeInBytes = 10240KB
        }

Hi @ChristophHannappel - thanks for raising this and good point. This should be documented and also an example should be included. I've marked as Help Wanted for now because I'm completely snowed under till beginning of Dec.

I can help :) Since the knowledge is fresh. Since this is my first time, should i try a pull request on the wiki md file? Or does it work different?

Hi @ChristophHannappel - would love the help. Just submit a PR against the README.MD in the source\DSCResources\DSC_WindowsEventLog folder and add a new example to the source\Examples\Resources folder. The Wiki gets updated automatically from those files.

I'm working on another issue with WindowsEventLog (#355) so I'll update the README.MD to include this when I submit the PR.

@ChristophHannappel I submitted the PR and waiting for the code review process. I rewrote part of the code so you won't need to configure 'IsEnabled' in order to achieve what you're looking for. Your first resource example will work with this release.


Generated Webapp Footer: Copyright Date Out of Date

Describe the bug
Footer says:

v2.8.0 © 2019 jc21.com. Theme by Tabler

To Reproduce
Steps to reproduce the behavior:

Log in
Scroll down to bottom of page
Observe typo

Expected behavior
Perhaps change to:

v2.8.0 © 2019–2021 jc21.com. Theme by Tabler

(Assuming 2019 was the year of the first release?)

How about close?


unit_tests_cpp error

Followed your steps for Windows but getting this error when trying to build your starter project
> Executing task: ninja <

[2/4] Building CXX object CMakeFiles/unit_tests.dir/tests/unit_tests.cpp.obj
FAILED: CMakeFiles/unit_tests.dir/tests/unit_tests.cpp.obj
C:\PROGRA~1\LLVM\bin\CLANG_~1.EXE  -IC:/Users/jbonastre/Documents/CodinGame/tools/include -IC:/Users/jbonastre/Documents/CodinGame/MyTest1/src -IC:/Users/jbonastre/Documents/CodinGame/MyTest1/tests -O3 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ggdb3 -D_GLIBCXX_ASSERTIONS=1 -std=c++17 -Wall -Wextra -Wconversion -Wshadow-all -Wno-shadow-field-in-constructor -Wno-format-security -m64 -MD -MT CMakeFiles/unit_tests.dir/tests/unit_tests.cpp.obj -MF CMakeFiles\unit_tests.dir\tests\unit_tests.cpp.obj.d -o CMakeFiles/unit_tests.dir/tests/unit_tests.cpp.obj -c C:/Users/jbonastre/Documents/CodinGame/MyTest1/tests/unit_tests.cpp
C:/Users/jbonastre/Documents/CodinGame/MyTest1/tests/unit_tests.cpp:2:11: fatal error: 'catch.hpp' file not found
# include "catch.hpp"
          ^~~~~~~~~~~
1 error generated.
[3/4] Linking CXX executable ..\bin\bot.exe
FAILED: ../bin/bot.exe
cmd.exe /C "cd . && C:\PROGRA~1\LLVM\bin\CLANG_~1.EXE -fuse-ld=lld-link -nostartfiles -nostdlib -O3 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ggdb3 -D_GLIBCXX_ASSERTIONS=1 -fuse-ld=lld -Xlinker /subsystem:console CMakeFiles/bot.dir/src/bot.cpp.obj -o ..\bin\bot.exe -Xlinker /MANIFEST:EMBED -Xlinker
/implib:..\lib\bot.lib -Xlinker /pdb:..\bin\bot.pdb -Xlinker /version:0.0  -LC:/Users/jbonastre/Documents/CodinGame/tools/lib -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -loldnames  && cmd.exe /C "cd /D C:\Users\jbonastre\Documents\CodinGame\MyTest1\build &&
python C:/Users/jbonastre/Documents/CodinGame/MyTest1/merge_source_files.py C:/Users/jbonastre/Documents/CodinGame/MyTest1/src/bot.cpp C:\Users\jbonastre\Documents\CodinGame\tools\include C:/Users/jbonastre/Documents/CodinGame/MyTest1/package/bot.cpp""
lld-link: error: <root>: undefined symbol: mainCRTStartup
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command ninja" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

You're right. I've let  catch header include in the starter project. I'll remove it.
In the meantime, you can either:

install catch2 and set the include directories in the CMakeLists.txt
or remove the line add_executable( unit_tests "tests/unit_tests.cpp") from CMakeLists.txt

Gotcha, it has been fixed removing the line from CMakeLists.txt. Now I'm facing another issue. Should I open a new issue or can we have a look with this one?
Thank you for the quick response!
> Executing task: ninja <

[0/1] Re-running CMake...
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/jbonastre/Documents/CodinGame/aaaaa/build
[1/1] Linking CXX executable ..\bin\bot.exe
FAILED: ../bin/bot.exe
cmd.exe /C "cd . && C:\PROGRA~1\LLVM\bin\CLANG_~1.EXE -fuse-ld=lld-link -nostartfiles -nostdlib -O3 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ggdb3 -D_GLIBCXX_ASSERTIONS=1 -fuse-ld=lld -Xlinker /subsystem:console CMakeFiles/bot.dir/src/bot.cpp.obj -o ..\bin\bot.exe -Xlinker /MANIFEST:EMBED -Xlinker /implib:..\lib\bot.lib -Xlinker /pdb:..\bin\bot.pdb -Xlinker /version:0.0  -LC:/Users/jbonastre/Documents/CodinGame/tools/lib -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -loldnames  && cmd.exe /C "cd /D C:\Users\jbonastre\Documents\CodinGame\aaaaa\build && python C:/Users/jbonastre/Documents/CodinGame/aaaaa/merge_source_files.py C:/Users/jbonastre/Documents/CodinGame/aaaaa/src/bot.cpp C:\Users\jbonastre\Documents\CodinGame\tools\include C:/Users/jbonastre/Documents/CodinGame/aaaaa/package/bot.cpp""
lld-link: error: <root>: undefined symbol: mainCRTStartup
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command ninja" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

I guess we could look at this problem in the same issue.
This error reminds me of what I got when I first tried the clang + lld configuration on Windows. I add to pass extra cmake arguments to make it work. Go to the extension settings and enter -DCMAKE_SYSTEM_NAME="Generic" into the field Codin Game: Cmake Extra.
I really wanted to keep using clang on Windows for the nice error/warning messages, but it's still a pain to make it work ^^.

Same error, these are my settings:

For some reasons, I remember that I also specified the C compiler path, however, I think it won't help with your issue. Did you reconfigure the build after you changed the CMake Extra value?

yes, I tried with Debug and Release config

s

Ok, I'll try and check the whole process on a new computer

Interesting, I've created a new project and we can move one step forward
It complains about python now, py is the keyword recognized on Win

> Executing task: ninja <

[2/2] Linking CXX executable ..\bin\bot
FAILED: ../bin/bot
cmd.exe /C "cd . && C:\PROGRA~1\LLVM\bin\CLANG_~1.EXE -O3 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ggdb3 -D_GLIBCXX_ASSERTIONS=1 -fuse-ld=lld CMakeFiles/bot.dir/src/bot.cpp.obj -o ..\bin\bot -LC:/Users/jbonastre/Documents/CodinGame/tools/lib  && cmd.exe /C "cd /D C:\Users\jbonastre\Documents\CodinGame\testProject1\build && python C:/Users/jbonastre/Documents/CodinGame/testProject1/merge_source_files.py C:/Users/jbonastre/Documents/CodinGame/testProject1/src/bot.cpp C:\Users\jbonastre\Documents\CodinGame\tools\include C:/Users/jbonastre/Documents/CodinGame/testProject1/package/bot.cpp""
'python' is not recognized as an internal or external command,
operable program or batch file.
ninja: build stopped: subcommand failed.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command ninja" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

Changed CMakelist, it seems to have been finished

Executing task: ninja <

[0/1] Re-running CMake...
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/jbonastre/Documents/CodinGame/testProject1/build
[1/1] Linking CXX executable ..\bin\bot
Terminal will be reused by tasks, press any key to close it.

That reminds me of something. I think that went I set up the CMake Extra variable I had to remove the whole build to see the effect of changes: you cannot change toolchain on a CMake build, you have to recreate it from scratch.
For the python issue, the most probable reason is it is missing from the path. Did you add the python's binary directory to the path? I had to add C:\Users\atom\AppData\Roaming\Python\Python39\Scripts to mine.


feat(test): add tests for

add tests for <UserDigest.Mini>, <UserDigest.Plain> and <UserDigest.Rich>;
bypass onClick on <UserDigest.Rich>;

merged into https://github.com/thematters/matters-web/pull/3948


⚠ Bofrost.at has degraded performance

In 9137746, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1827 ms

Resolved: Bofrost.at performance has improved in 50662b9.


Remove default response from Sessions

Remove default response from Sessions to bring them inline with the remaining artifacts
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

@annatisch That's fine. This is all part of a current versioning up that we are doing. Found this issue when generating and testing out the .Net SDK


Implement JSON binary encoding

Added binary support for JSON along with tests

I think we need to handle other possible types such as JsonArray

Will implement array as part of this PR.

Have JSON array working fine, the pain point is the scalar queries. Working on that in order to complete this PR

Closing PR due to issues with scalar bind queries. Needs a bit more tinkering. JsonObject and JsonArray completed


Add support for "readonly" tables

Similar to #81 and #82, I think there's room for a "readonly" mode. A readonly table would be a physical SQL table that VALVE would load from a TSV file, but would not be editable.

in the "table" table the "path" for a readonly must point to a TSV/CSV file
VALVE will not create any SQL tables or views related to the readonly table, i.e. *_conflict or *_view
VALVE will not save the readonly table, but it will create, drop, truncate, and load it
VALVE will not edit rows in the readonly table with insert_row, delete_row, etc.
it would be nice if VALVE could still validate a row from a readonly table using validate_row(), since its columns will be defined

I feel like I'm running together two use cases here:

VALVE does everything it normally does, including validation and *_conflict, but does not edit rows or save
VALVE just loads a plain table, without creating a *_conflict table; maybe it validates, but it can't handle conflicts

My actual use case is just loading large tables quickly, without need for validation or handling conflicts, so they can be used by other tables that are editable.

Update: See this comment on issue #81.


Getting siteAreas with parameter "WithChargingStations=true" doesn't work anymore

SiteAreas don't contain lists of ChargingStation objects anymore, and the paremeter WithChargingStations seems to be there still.
This is the API call I've been successfully using for a year basically.

Thanks

I fixed the issue, you should have the charging station IDs in an array tomorrow (after tonight's deployment)

I fixed the issue, you should have the charging station IDs in an array tomorrow (after tonight's deployment)

Hey Serge, thanks for a very fast response.
The thing is - previously we could fetch all of the Charging Stations (complete objects) in a single call while fetching all existing Site Areas and it was extremely convenient.
Being able to see ChargingStation IDs wouldn't provide much since we can fetch ChargingStations for a certain SiteArea ID already, but making an API call for each SiteArea isn't that great compared to how it was earlier.
If it was an intentional change - ok, we can obviously work around it, but being able to fetch a whole SiteArea in every single charging station object while fetching charging stations, but not the other way around doesn't seem logical.
Thanks once again

@LucasBrazi06
Thanks for the fast reply once again.
It's fine, at least I know that it's working as intended and I should work around it :)
Why I'm asking for all this if you're interested - I'm creating a map filter on our mobile app, and I want to exclude certain SiteAreas from showing based on the connector type of the ChargingStations in that SiteArea.
It was extremely convenient to have all the information after a single API call instead of fetching all the SiteAreas and then fetching ChargingStations for each SiteArea separately.

@vladajanjanin
Thanks for the explanation of your use case !
But this is a specific dev at server side to take into account the connector type and filter out the sites/site areas accordingly.
It's a better solution that retrieving all the data and doing the filter in the front-end.
If you have your mobile app then you should also have your own server and you can implement this feature very easily ;-).


Deleted methods do not save to JAR

Due to a bug in IntelliJ's GUI designer, a certain method is created multiple times in the target JAR. In order to get rid of the duplicates, which cause the whole application JAR to crash with a java.lang.ClassFormatError, I used Recaf.
After deleting the duplicate methods in Recaf, I verified the code after decompiling it again using Recaf as well and saved the new JAR since I only saw one copy of the method left. However, the JAR did not get updated analogously to the deleted methods. All duplicates are still there. Why is that? This literally defeats the purpose of a bytecode editor when it does not edit the JAR like you did in the GUI. I'm using the as of now latest release.
Can you please fix this? Thanks a lot. I appreciate this application but it would be nice if it can deliver what it promises.

Oh yeah, just reproduced this by duplicating a member and renaming it to be the same. Deletion failed. I'll fix that and post a new release with some other fixes in a few minutes.

Fixed in dff56cdd9fc659b0e7028ab7446c1a76690ea629 I'll create a new release


[Discover] thoughtworksbooks: update compontent

update  thought works books compontent
create domain detail page compontent
create domain detail page item compontent
add compontent test

Coverage increased (+0.6%) to 54.723% when pulling 9b5fca6024a3df0e7eb093e63134d0fa538fe6ac on travelgeezer:thoughtworks-books into 3f22e5ccca5fe96dbc876ea964dece6b885e3355 on phodal:master.


csrf_cookie is created even if i have csrf_protection set to false

like the title says

I wasn't able to reproduce this with v2.0.3

i observed this on the development version i will cleanup test again and report

tested again and in the development version the cookie gets created no mater what your settings are

@quasiperfect Can you verify if #1087 fixes this for you?

@narfbg yep it works or atleast it dosen't set the cookie anymore. thanks