Support Dynamic Partition

Implement of this issue #2262 , Later will complete Document and UT.

Have a few questions

The TableProperty class needs to be more general.
For example, there may be only one variable in class: Map<String, String> properties
For dynamic partition related properties, uniformly use the following key-value format:
"dynamic_partition.prop1" = "val1",
"dynamic_partition.prop2" = "val2"

Just put a map, and then different categories of properties are distinguished with different prefixes.
The map is mainly to facilitate the subsequent addition of other categories of properties,
and o need to modify the FeMetaVersion.
After that, you can write a class named, for example, DynamicPartitionProperty, separately.
This class is built from properties map, and no need to be persisted to meta data.
For example, in the readFields() method of TableProperty, you can write:
public void readFields () {
	... read the property map first ...
	this.dynamicPartitionProperty = buildDynamicPropertyFromPropertyMap(properties);
	this.someOtherProperty = buildSomeOtherPropertyFromPropertyMap(properties);
	...
}

In subsequent use, you can directly use the parsed content in dynamicPartitionProperty
without having to get it from the properties map and then parse it.

In my opinion, the TableProperty class, is a kind of static class, and only need to be modified.
when the user changes the relevant property's meta-information (such as modifying the information about how to create dynamic partition).
In other words, you should only modify the contents of the TableProperty in the operations of
create a table, stop dynamic partitioning, modify dynamic partition metadata, or start dynamic partition.
The DynamicPartitionScheduler does not need to modify the TableProperty class when it automatically creates partitions.
First, after the partition is automatically created, the new partition information has been saved and persisted in the table's partition information.
Secondly, infos which ShowDynamicPartitionStmt needs to be displayed, such as LastSchedulerTime, does not actually need to be persisted.
The user usually only cares about the success of the last time and the current state, so this information will be available after the FE restarts and the 	DynamicPartitionScheduler is executed again.


api time out

const tronWeb = new TronWeb(fullNode, solidityNode, eventServer, privateKey)
tronWeb.setHeader({ "TRON-PRO-API-KEY": 'your api key' });

the timeout error always happened, how to set timeout config when init TronWeb

Could you please show the timeout host server or DNS ? There is no timeout config for TronWeb initiation at present.


Upgrade deprecated runtime nodejs8.10

CloudFormation templates in amazon-fsx-workshop have been found to include a deprecated Lambda function runtime (nodejs8.10). The affected templates have been updated to a supported runtime (nodejs10.x).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This has been updated to nodejs12.x in the latest version of the workshop.


Add basic support for autojoin/v0/node/register

This change adds basic support for node registration. This includes defining v0 response structures as well as dependencies on loading Maxmind and ip2prefix ASN datasets needed to calculate a hostname. The hostname is not registered in DNS as part of this PR.

This change is

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-21 of 82 (74.39%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-8.6%) to 91.358%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

handler/handler.go
61
82
74.39%

Totals

Change from base Build<PHONE_NUMBER>:
-8.6%

Covered Lines:
222

Relevant Lines:
243

💛  - Coveralls

Obsolete


add accessibilityLabel for overlay

Any way to vote on this?  Seems like a fairly minor patch to verify.
OR is this project dead?

Added in v4.0 take a look at the changes made in v4.0
https://github.com/AdelRedaa97/react-native-select-dropdown?tab=readme-ov-file#-major-changes
Feel free to open the issue again if it still exists


Stochastic Action sample seems not right to me

In "SOTA-RL-Algorithms/common/policy_networks.py" line 337, the random sampling from the normal distribution is done by z = normal.sample().
While this samples a single value, it works for a single action space. For multiple action space, this does not seems right. What about z = normal.sample_n(self._action_dim) ?

Hi,
I think you are right. Bugs fixed.
Thanks!


fix: returning from the executor function should not cause the promise to be rejected

Implemented in latest version 👍🏻


FEATUE : Add bash completion for wpscan

WP Scan is a Wordpress Security Auditing Tools

Sure
On Sat, 5 Jan 2019, 19:59 Nils Winkler<EMAIL_ADDRESS>wrote:

Please feel free to provide a PR for this if you would like to see this
functionality.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Bash-it/bash-it/issues/1301#issuecomment-451660136,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbEloQ5cjqQPMQ1CpXgxPXVi-RqJ7Yccks5vALa0gaJpZM4ZwcPB
.


Add ability to use the 'OFFSET' parameter with a Select object

I couldn't figure out any way to add the 'OFFSET' parameter to a sqlite query besides using custom sqlite queries. ie I want to be able to do Select.class(Car.class).limit(3).offset(15);
I see in your code (https://github.com/satyan/sugar/blob/master/library/src/com/orm/query/Select.java) that there is already a variable called 'offset', however there are no functions for the user to set the value?

@drojf Did you ever figure this out?

Nope, unless you change the source code yourself or use a custom sql query
 public Select<T> offset(String prop) {
        this.offset = prop;
        return this;
    }

You could issue a pull request to add the above code into 'Select.java' as well if you have time, I haven't done it cause I don't know how to use git properly lol. That's all you'd need to change I think.

added in grade version 1.5
#400

It does not work with .list() function.
The offset param is completely ignored.
https://github.com/satyan/sugar/issues/682


Serialize/deserialize IReadOnlyList

I'm not sure what are the limitations here, but why is IList and array valid types for serialization but IReadOnlyList isn't? Worst case scenario, you can just cast an array to it.

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!


@opentelemetry/instrumentation-graphql Error when running synchronously

Description
Instrumenting a graphql application which uses the synchronous method graphqlSync causes  Error: GraphQL execution failed to complete synchronously. App is working fine when not istrumented.
System Info

What version of OpenTelemetry are you using?
 "@opentelemetry/instrumentation-graphql": "^0.29.0"
 "@opentelemetry/instrumentation": "^0.29.2"
 "@opentelemetry/sdk-trace-node": "^0.25.0"

With:
 "graphql": "^15.8.0"

What version of Node are you using?
v16.14.2
Reproducing
What did you do?

Create a async.js with "Hello World!" example as per: https://graphql.org/graphql-js/

const { graphql, buildSchema } = require('graphql')

// Construct a schema, using GraphQL schema language
const schema = buildSchema(`
  type Query {
    hello: String,
  }
`)

// The rootValue provides a resolver function for each API endpoint
const rootValue = {
  hello: () => {
    return 'Hello world!'
  }
}

// Run the GraphQL query '{ hello }' and print out the response
graphql({
  schema,
  source: '{ hello }',
  rootValue
}).then((r) => {
  console.log(r)
})

Create a sync.js with a synchronous version of "Hello World!"

const { graphqlSync, buildSchema } = require('graphql')

// Construct a schema, using GraphQL schema language
const schema = buildSchema(`
  type Query {
    hello: String,
  }
`)

// The rootValue provides a resolver function for each API endpoint
const rootValue = {
  hello: () => {
    return 'Hello world!'
  }
}

// Run the GraphQL query '{ hello }' and print out the response
const r = graphqlSync({
  schema,
  source: '{ hello }',
  rootValue
})
console.log(r)

Create a tracing-gql.js script as per: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-graphql

'use strict'

const { GraphQLInstrumentation } = require('@opentelemetry/instrumentation-graphql')
const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node')
const { registerInstrumentations } = require('@opentelemetry/instrumentation')

const provider = new NodeTracerProvider()
provider.register()

registerInstrumentations({
  instrumentations: [
    new GraphQLInstrumentation({
    // optional params
      // allowValues: true,
      // depth: 2,
      // mergeItems: true,
    })
  ]
})

Run node -r ./tracing-gql.js async.js ✅

Run node -r ./tracing-gql.js sync.js ❌

What did you expect to see?
node -r ./tracing-gql.js async.js   ✅

opentelemetry
{ data: [Object: null prototype] { hello: 'Hello world!' } }

What did you see instead?
node -r ./tracing-gql.js sync.js ❌

opentelemetry
/usr/src/instrumented/graphql/node_modules/graphql/graphql.js:63
    throw new Error('GraphQL execution failed to complete synchronously.');
    ^

Error: GraphQL execution failed to complete synchronously.
    at graphqlSync (/usr/src/instrumented/graphql/node_modules/graphql/graphql.js:63:11)
    at Object.<anonymous> (/usr/src/instrumented/graphql/sync.js:18:11)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47
root@8f40b7e64865:/usr/src/instrumented/graphql#

Additional context

App works fine when NOT instrumented. Instrumenting and modifying graphql internals is causing the error.
node sync.js ✅

{ data: [Object: null prototype] { hello: 'Hello world!' } }

It might not even be a bug. The home page mentions supported versions: >=14 <16
https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-graphql#readme

It might not even be a bug. The home page mentions supported versions: >=14 <16 https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-graphql#readme

He is using "graphql": "^15.8.0" which falls in the range

@obecny originally contributed this component but is no longer a maintainer. I'm looking into this

Tests for<EMAIL_ADDRESS>failing: https://github.com/open-telemetry/opentelemetry-js-contrib/actions/runs/3077464972/jobs/4972348257

debugged it and found the issue here
instrumentation code wraps each resolver with safeExecuteInTheMiddleAsync which turns sync functions into async. This is why graphqlSync throws. It also changes the behavior of the package, degrading performance, and making things parallel where they are not supposed to be:

This is a timeline screenshot for the resolvers which should run synchronous, but the instrumentation causes them to appear to run in parallel


Docker error with build 1.1.0

Describe the bug
Recreated pd_zurg container with the latest build on Docker Hub - 1.1.0 and now get this in the logs.
Traceback (most recent call last):
File "/main.py", line 1, in
from base import *
File "/base/init.py", line 2, in
from dotenv import load_dotenv, find_dotenv
ModuleNotFoundError: No module named 'dotenv'
To Reproduce
Run the latest docker build
Expected behavior
Container runs.
Please complete the following information:

OS: Ubuntu
Version: Ubuntu 22.04.3 LTS
Supporting Applications: Docker 24.0.7

I had re-pulled it a couple of times already and reverted to previous image which worked.
The 1.1.0 build is working now and pip list shows dotenv installed. I suspect it was a container networking problem.
Thanks for the response and thanks even more for the software!


Hide Illegal decks by default

Currently, if someone posts an illegal deck, or one gets bumped back into view, It shows up on the main page.
There is no obvious sign it's illegal until you go into the deck view.
We need to either Hide it, or indicate that it's illegal.

My personal preference is to add Set Symbols showing which seasons the deck is legal for.
This would require #458 to be implemented.

Something like this:

Set Symbols care of https://andrewgioia.github.io/Keyrune/

That font is very nice. I wonder if a big [1], [2] graphic is more comprehensible though? Either one would be good.

Yeah, we can change the size easily enough.
That screenshot was a minimum viable mockup
On Wed., 2 Nov. 2016, 18:20 Thomas David Baker<EMAIL_ADDRESS>wrote:

That font is very nice. I wonder if a big [1], [2] graphic is more
comprehensible though? Either one would be good.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PennyDreadfulMTG/Penny-Dreadful-Tools/issues/457#issuecomment-257790303,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL2ztQLX7pDcf1Pn7B9Bx8TZrFvKIBMks5q6DmugaJpZM4Km4k1
.

It wasn't really the size so much as just ... do people link the seasons with the sets that clearly in their minds? I know I don't. There aren't any legal KLD cards.

True.  I'd much rather call S1=SOI, and S2=EMN
But that's what @binarySwordsman codified the seasons as, so we either need to retroactively change the names at source, transform the names after we import legality lists, or find another way of signifying seasons.

EMN for the current season definitely leaves a lot of room for confusion, too, esp as you say some things are standardized the other way.
As boring as it is I think maybe just a big stylized "1", "2", etc. might be clearest. We can experiment.

That said, most people don't have EMN_legal_cards.txt on their mind, so both of the first two are probably fine.

This is currently KLD season if you're thinking of classifying it that way.

Defining what is a current season deck is actually kind of interesting.
If you make a deck now what happens to be legal again in two seasons time should it suddenly show up again on lists and in stats? Probably not. Especially not stats on who it beat and so on.
Then again if you make a deck on tapped out and update it across multiple seasons it should show as current.
So I think bizarrely enough that updated_date is the best guide we have to "things to show by default". For tournament and league decks this will forever be the same as created date and one day we may update based on tapped out. It does mean some decks people made that ARE legal will be HIDDEN by default because they are from a past time. But that should be rare and I think it's ok.

This relies on us picking up a "real" updated_date from Tapped Out which I don't think we are currently doing? I don't see a tapped out API key in the config.json on prod. @silasary – is there meant to be?

Relatedly, does anyone know how you get a Tapped Out API key? :)

def season_query():
return '(d.updated_date > {rotation})'.format(rotation=dtutil.dt2ts(rotation.last_rotation()))

I know how to get a key.  Bu no clue how to use it.
The documentation on the TappedOut API is pretty useless.

That's why we're using user/pass, and authenticating via Cookie.

I think we're happy with the current state of affairs now that it's clear in all views whether a deck is legal or not.


iox-#1938 fix unfair iceperf

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed (except task-list-completed)
[x] All touched (C/C++) source code files from iceoryx_hoofs are added to ./clang-tidy-diff-scans.txt
[x] Assign PR to reviewer

Notes for Reviewer

Checklist for the PR Reviewer

[x] Commits are properly organized and messages are according to the guideline
[x] Code according to our coding style and naming conventions
[x] Unit tests have been written for new behavior
[x] Public API changes are documented via doxygen
[x] Copyright owner are updated in the changed files
[x] All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
[x] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #1938

@FerdinandSpitzschnueffler

LGTM but have you checked if the readme needs to be updated?

I checked it and the readme does not require any update. I just changed the technology implementation for send/receive for uds and mq which does not imply any change in the public or even private API.
Only the benchmark numbers are now fair.


Filter in variables by name

Hello, could you please add a filter to return the variables by name, in the HistoricActivity query?

Hey there, your request has been developed and is in the pull request process. It'll be available in the next release.


Verbose when logging

When using the logger, the verbose is turned off with no output (verbose=0), is there any way to turn it back on
optimizer = BayesianOptimization(f=model,
                                     pbounds=pbounds,
                                     verbose=2,  # verbose = 1 prints only when a maximum is observed, verbose = 0 is silent
                                     random_state=1)
#Create Logger
logger = JSONLogger(path = './file_name.json')
#Update Logger for each hyperparameter combination
optimizer.subscribe(Events.OPTIMIZATION_STEP, logger)
optimizer.maximize(init_points=10, n_iter=10)

Use ScreenLogger(verbose=verbose), and subscribe to start, step, and end events.
In fact, that's what's going on by default when verbose is set: https://github.com/fmfn/BayesianOptimization/blob/master/bayes_opt/bayesian_optimization.py#L147


Add additional text in block menus

Expected Behavior
As a user I would like to get extra information in the "block menus". An example of this could help me read the <, >, = signs.

So you're looking to make it so what shows up in the block is different from what shows up in the menu.

Hi @BryceLTaylor, Yes exactly. The goal is to keep the block text itself short, but provide extra information to the users in the menu. Another example could be when using abbreviations such as m for metres or n for newton.


iPhone 11 Pro 16.6 - Got "Done - OK" , BUT ...

after choosing "Tips" for TrollStore Help, It says "Done, OK", but automatically resprings or not,
It JUST WOULD NOT show TrollStore
(Changes are NOT committed or retained ??)

Please try:

use misaka to respring.
after respring, start Tips to install trollstore.


v0.6 Update

Many small updates but here are the highlights:
Materials have been moved to MaterialData.json
Materials are now objects that contain a MarketPrice and a GrindIndex
GrindIndex is a weight for material spent that is supposed to represent how difficult it is to go out and mine it yourself.
Materials are in a data table much like recipes. GrindIndex and MarketPrice are editable by the user.
Object Data has been renamed to Recipe Data
Recipes now stored in RecipeData.json
Added 56 new recipes, updated over a dozen more to correct names/values.
Overall, this update allows someone to more accurately plan their research grind by allowing them to prioritize certain materials over others to better reflect both what they have easy access to or lots of.

Wow, that is amazing! Thank you so much for all this hard work! I took a quick look into the diff, and just have one question before I go ahead with the merge. I noticed that some of the recipes are getting their CraftingTime changed from whatever number they had to 0.0, in other words, they are losing their CraftingTime value; is this intentional?

They should only be changed for recipes that got updated recipe costs, I'll give it a once over. Alot of them need to be re-timed.

Reverted Hinge B back to its original value, but the other tool bench updates need to be retimed. It is currently unknown if material composition affects crafting times. I've been working with some of my homies to get the resources to properly time all these recipes, but its been slow going.


Configure test runner and coverage reports

This sets up a test runner (based on Django's built-in testing framework) and coverage reports (created by Coverage.py and uploaded to Codecov.io on CI).

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Fixes: #29

commit MERGED in pull request #47


short opt handling: fix parsing

Only split a given string (e.g., "-abc") into short options (e.g., "-a",
"-b", "-c") if all those are flags.  To further avoid mistakenly
transform common arguments, catch "flag provided but not defined" errors
to iteratively transform short options.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>Fixes: https://github.com/projectatomic/libpod/issues/714

.\command_test.go:296:3: value declared but not used
I am not sure that this PR's causing the issue.

@baude PTAL

@jszwedko PTAL

Ping @meatballhat, @jszwedko, @gravis, @jamescun, @muraty, @thesyncim, @tianon, @txgruppi.
Sorry for the noise, but it looks like this project is transitioning to a zombie. Is there anything we can do to get revive it? It's used by a vast amount of projects and this PR addresses an issue that affects quite some users.

@vrothberg, thanks for tagging me.
I'm quite busy this week but I will have some time during the weekend to take a look at this.

@txgruppi Awesome, thanks a lot!

@vrothberg it looks good to me but can you write tests for your change? Cheers.

@vrothberg it looks good to me but can you write tests for your change? Cheers.

Thanks, @txgruppi! I just added tests.

@txgruppi friendly ping. The appveyor CI breaks of changes prior to this one.

@vrothberg sorry for the delay, I'm having some really busy days over here.
LGTM 👍

@vrothberg sorry for the delay, I'm having some really busy days over here.

No worries, I fully understand :) I just rebased the PR. Can you merge it?

@vrothberg, the problem is... I don't write access to this repo. I'm just someone that has a vote sometimes because some of my contributions a long time ago. =/

@vrothberg, I'm trying to talk to someone with write access to solve this.

So what happens now if those are not flags?

I didn't realise this was coming from the standard library

So what happens now if those are not flags?

In that case the strings remains remain unchanged. You can find some examples in the unit test:
https://github.com/urfave/cli/pull/758/files#diff-2fc2009ba1969a36b69136d7fb7b2072R60

As part of this, can you fix the vet warning? Don't want to do a forced merge.

Thanks a lot, @AudriusButkevicius and @txgruppi!

I also assume you want this released?
Not sure if I can do that.

Cool


Change images

How can I change the images on runtime?

Hi, now they are static in resourcedictionary. You can change it dynamically, you can find this approach in google.
Another approach is completely change the logic where the control takes these picture, all code is available so you can change it as ever you want.


Incompatible with cordova-plugin-wkwebview

cordova-plugin-wkwebview bundles a web server in order to serve content, and it is somehow incompatible with the way chcp sets the location on the webview.
It sets an url which looks like:
http://localhost:12344/file:///Users/user/Library/Developer/CoreSimulator/Devices/EC1D4B9C-9582-4592-AD29-988B1D2C9247/data/Containers/Data/Application/D4B4B4EF-4C96-4D52-976C-565FEB50DEF3/Library/Application Support/app.bundle.name/cordova-hot-code-push-plugin/www/index.html
However, a proper url would be
http://localhost:12344/Library/Application Support/app.bundle.name/cordova-hot-code-push-plugin/www/index.html
I'm not sure if there's a workaround I can apply or it needs a PR. Any pointers would be appreciated.

I think this can be fixed in cordova-plugin-wkwebview so I sent a PR to that repository: https://github.com/Telerik-Verified-Plugins/WKWebView/pull/195

Alright, this is now fixed by Telerik-Verified-Plugins/WKWebView#195 and Telerik-Verified-Plugins/WKWebView#196.
Closing. :)

Nice!


notification module is not constrained to the screen

When the user has many notifications the drop down exceeds the screen space at the bottom. This makes it hard to scroll within the drop down and click see more.
Current:

Ideal?

@bhalt how should we handle this? Do we want to limit it to like 3 notifications or something?

Yes.. My vote would be 2-3 max @wski

Also, has a word count limit been implemented on the dropdown yet? Now that the word count has expanded on notifications inside the modal, the dropdown message should cutoff with an "..." after a few lines. We don't want entire notifications shown in the dropdown. @wski

It hasn't I planned to add that when @mannyrivera2010 gets around to increasing the limit on the backend. I'll go ahead and limit the count of notifications, would you like me to toss a word limit and add the ellipsis at the end. What should this limit be?

First part done here https://github.com/ozone-development/ozp-react-commons/pull/59

Maybe keep the dropdown character limit to what the notification used to be before the expansion?

150 was the previous limit, However I found a bug inadvertently; If a notification has no spaces, it looks like this:

@wski can you add word-wrap: break-word; to .UserNotification in ozp-react-commons? That should fix that...

Yeah, and I'll set the drop down limit to 150 chars. Perhaps we should do some other css magic to remove line breaks.

I added 10 new notifications and one with a lot of words.  Looks good.

Mistake in previous test.. This fails on Staging and Master. ( DI2E is down so cant verify on latest)
Test Case #1
STR-
Go to Center Settings | Notifications
Create a really long 150 char notification without spaces.
Send
RESULTS - Notifications are truncated in Navigation bar | Notifications drop down
EXPECT RESULTS - Notifications should word wrap.

@wski - what is the status on this?

Test Case 1 - Failed
Test Case 2 - Passed

passed on Latest.

Passed on Staging - IE, FF and Chrome


Initial Challenge Setup - Social Recovery

The setup is like this; eth-tech-tree is a CLI for downloading, submitting and managing which challenges a user has completed. The repo that houses all the challenges in called eth-tech-tree-challenges. Each challenge is a new branch on that repo.
Follow the example left by the Token Wrapper WETH challenge and see how that challenge is configured in the challenges.json file in the eth-tech-tree repo.
{
    "type": "challenge",
    "level": 1,
    "name": "token-wrapper-weth", // Branch name
    "label": "Token Wrapper - WETH",
    "repo": "https://github.com/escottalexander/scaffold-eth-2",
    "testHash":"cdef2b9c0051c45a8ce2c1ec14a7446419496a018a6dc114735cce9de3a4f249",
    "testFileName":"WrappedETH.t.sol",
    "tags": ["DeFi"]
  },

Here are the steps for adding a new challenge:
Creating a new challenge

Fork and download the eth-tech-tree-challenges repo
Create a new branch based on the main branch (which is set up to be a template for any challenge) with the name of the challenge e.g. 'social-recovery'
Write out a solution to the challenge in solidity using best industry standards as generically as possible by editing Challenge.sol and changing it's name to match the challenge
Write tests that cover the most common pitfalls and guarantee the contract operates as expected (Challenge.t.sol) - change it's name to match the contract
Update README in your challenge to give the user clarity about what they must accomplish and also any helpful resources (see the token-wrapper-weth challenge for an example)
Commit and push your changes to your remote repo, creating a new branch on your remote git push
Submit a PR to the main eth-tech-tree-challenges repo pointed to the branch that matches your challenge name e.g. 'social-recovery'

Adding the new challenge to eth-tech-tree CLI app

Edit challenges.json (in eth-tech-tree) to have proper values for each property

name: should match your branch name
repo: should be your repository
testName: should be the name of the test file
testHash: should be the hash of the test file. Use console.log to get this when taking the "submit challenge" action on your challenge when running eth-tech-tree CLI

Test downloading and submitting the challenge using the eth-tech-tree CLI yarn build && yarn cli
Commit and push changes to the eth-tech-tree in your own fork and branch called 'adding-[challenge branch name]' and submit a PR to the main repo 🎉

Later, in another task, we will erase your specific solution code from the git history for your new branch in eth-tech-tree-challenges.

Social Recovery challenge specifics
This challenge will require users to create a contract where a user can define a set of addresses that can restore access to the 'wallet' contract. The wallet contract can be intentionally simple since the challenge will be the social recovery aspect. Here is a description of what it should look like: https://www.argent.xyz/learn/what-is-social-recovery/
Feel free to ask any questions or express any ideas that will help the end user learn through this challenge.
It already has an object in challenges.json which has the name field 'social-recovery'.

Hey all, I can start working on this one


Neither the CRD (nodetopology.openshift.io/v1) nor the resource (NUMAResourcesOperator) in clusters...but kube-compare still attempts to render

This case should be handled more gracefully
error: template: nrop.yaml:9:13: executing "scheduling/nrop.yaml" at <len .spec.nodeGroups>: error calling len: reflect: call of reflect.Value.Type on zero Value

This issue might be fixed with the latest commit but will need to reset
/kind bug

Resolved


JSON attribute should be initial_options instead of initial_option

@CGA1123  Either this is a bug or Slack actually allows singular version of the attribute.

MultiExternalSelect https://github.com/CGA1123/slack-ruby-block-kit/blob/371f2f2698d07d2ba2f361ae6bfca0539cf48889/lib/slack/block_kit/element/multi_external_select.rb#L52-L52

https://api.slack.com/reference/block-kit/block-elements#external_multi_select__fields

MultiStaticSelect https://github.com/CGA1123/slack-ruby-block-kit/blob/371f2f2698d07d2ba2f361ae6bfca0539cf48889/lib/slack/block_kit/element/multi_static_select.rb#L80-L80

https://api.slack.com/reference/block-kit/block-elements#static_multi_select__fields

I didn't test it properly. It should be initial_options, initial_option is for single choice. You could verify it here
Could you help to open a PR to fix it? @caalberts
if you're busy, I'll back to fix it tomorrow. Thanks :)

Hey @caalberts
This is correct. MultiConversationsSelect, MultiChannelsSelect, and MultiUsersSelect are also affected by being singular rather than plural.


Build new Devkit b03 using updated bootstrapped script

We need to create a new Linux Devkit b03 builds using the bootstrapped method, ready for the July releases.

In-progress: https://ci.adoptium.net/job/build-scripts/job/utils/job/devkit/job/gcc-11.3.0/


Add temperature support for MCCGQ11LM

The MCCGQ01LM uses the same adapter but does not seem to have a temperature sensor. So I think think a separate adapter is needed. Already have it running on my setup and I could make it a pr if you want. Note that the temperature reading is about 4 degrees to high on both my MCCGQ11LM.

Didn't think about the dependency, makes sense to create a different adapter then.. will you take care of this @d-EScape?
I also have some deviations in temperature on some devices, some have +3, some -4, but this can be managed in the configuration.yaml via the temperature_calibration feature.

Good tip about calibration, thanks. Didn’t think of that.
I will push a pr this weekend.

I submitted PR #566
You should probably close this one, otherwise they might both be merged.

Onsolete due to PR 566

Implemented in #458


Update content to include warning that MSFT support is needed if you put in the wrong IP range

We've had several customers mis-set their allowable IP ranges. When applied, they get locked out and can't fix the mistake they've made. Admins have been banging their heads trying to figure out how to self serve, but you can't - you have to call support. Can we be more explicit about the risk of mis-setting and the fact that if you do mis-set, you will need to contact support to get unblocked?
The other bit of feedback we received was: specifically say "not only will this change restrict your user facing onedrive and SharePoint sites, but it will also restrict your access to the OneDrive Admin site, thus preventing your ability to undo this change outside of the specified IPs.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4128fad9-2907-9f45-592f-2336dbd25ee3
Version Independent ID: 6e105343-1f95-c061-dc48-187c2fb6870d
Content: Control access to SharePoint Online and OneDrive data based on network location
Content Source: SharePoint/SharePointOnline/control-access-based-on-network-location.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@hdonaldMSFT Thank you for this feedback.
I will get this information to the SharePoint team for investigation.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@kaarins Hi Kaarin, any updates on this? Thanks!

I added this right away months ago, but missed closing it.


Add GitHub action to check if tests pass

[x] Create a nimble task for running tests (don't like the default one)
[x] Create the action
[x] Doc generation workflow runs only when the tests have passed or when there was a push to main

Also would be nice to make the doc generation workflow run only when the tests have passed or when there was a push to main.

Seems like it works, but it's not actually listed in the commit's run workflows:

Also I actually only pushed the inputs of the flake to my cachix cache, so nim had to be built all over again and the action took around 8-10 minutes.
I have already pushed the actual outputs and now the actions seem to take around 2 mins!
So, since all the tasks have been completing, I'm closing this issue.


Error: Not supported.at OverlayContextKeyService.createScoped

open a notebook
double click a markdown cell so edit it
🐛

ERR Not supported.: Error: Not supported.
    at OverlayContextKeyService.createScoped (file:///Users/jrieken/Code/vscode/out/vs/platform/contextkey/browser/contextKeyService.js:444:19)
    at new CodeEditorWidget (file:///Users/jrieken/Code/vscode/out/vs/editor/browser/widget/codeEditorWidget.js:126:72)
    at InstantiationService._createInstance (file:///Users/jrieken/Code/vscode/out/vs/platform/instantiation/common/instantiationService.js:89:20)
    at InstantiationService.createInstance (file:///Users/jrieken/Code/vscode/out/vs/platform/instantiation/common/instantiationService.js:60:31)
    at StatefulMarkdownCell.viewUpdateEditing (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/view/renderers/markdownCell.js:253:50)
    at StatefulMarkdownCell.viewUpdate (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/view/renderers/markdownCell.js:210:22)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/view/renderers/markdownCell.js:107:26
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at MarkdownCellViewModel.triggerfoldingStateChange (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/markdownCellViewModel.js:88:36)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/notebookViewModel.js:308:26
    at Array.forEach (<anonymous>)
    at NotebookViewModel.updateFoldingRanges (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/notebookViewModel.js:306:29)
    at FoldingController._updateEditorFoldingRanges (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/contrib/fold/folding.js:73:44)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/contrib/fold/folding.js:32:26
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at FoldingModel.recompute (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/contrib/fold/foldingModel.js:206:45)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/contrib/fold/folding.js:24:91
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at NotebookEventDispatcher.emit (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/eventDispatcher.js:58:52)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/markdownCellViewModel.js:46:33
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at MarkdownCellViewModel.set editState [as editState] (file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/viewModel/baseCellViewModel.js:67:36)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/contrib/notebook/browser/view/notebookCellList.js:107:37
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:44:93
    at Emitter.fire (file:///Users/jrieken/Code/vscode/out/vs/base/common/event.js:479:38)
    at HTMLDivElement.fn (file:///Users/jrieken/Code/vscode/out/vs/base/browser/event.js:10:35)

doesn't repro anymore


Integrating Webviz into an existing React application

Hi!

I want to say this library is beautiful -- I am in awe
I have a standalone React application that needs some sort of visualisation aspect for the ROSbags we have (live and pre-recorded). I was wondering if there is a way for me to pull Webviz (core) into an existing application?

It might be pretty straight forward and this might be a useless question, but I have no clue where to get started on doing that, or if there is some docs to do that currently.
Thank you!!! Appreciate your time.

Sure, this is how it looks on the webpage we are working on:

and this is the link to see it in action: https://jsfiddle.net/den_globotix/vrsyw490/

Amazing thank you for sharing!


Thrift Proxy: Fix tag extraction to work with filter stat_prefix

Commit Message:
Fixes issue #20201 by adding tag extraction for thrift proxy filter.
curl <IP_ADDRESS>:9901/stats/prometheus | grep this_is_a_thrift_tag
envoy_thrift_cx_destroy_local_with_active_rq{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_cx_destroy_remote_with_active_rq{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_downstream_cx_max_requests{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_downstream_response_drain_close{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_no_healthy_upstream{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request_call{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request_decoding_error{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request_invalid_type{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request_oneway{envoy_thrift_prefix="this_is_a_thrift_tag"} 0
envoy_thrift_request_passthrough{envoy_thrift_prefix="this_is_a_thrift_tag"} 0

Additional Description:
Risk Level: Small
Testing: Unit tests for tag extractor manual test.
Docs Changes: N/A
Release Notes: Added
Platform Specific Features: N/A
Signed-off-by: Sotiris Nanopoulos<EMAIL_ADDRESS>

(waiting for Green CI before I assign reviewers)

/retest

/assign @ggreenway

@ggreenway fixed (removed the tag) I wonder if  we should also add this diff:
index 097d1147f1..ff13b436dc 100644
--- a/test/integration/base_integration_test.cc
+++ b/test/integration/base_integration_test.cc
@@ -103,10 +103,7 @@ void BaseIntegrationTest::initialize() {
   createUpstreams();
   createXdsUpstream();
   createEnvoy();
-
-  if (!skip_tag_extraction_rule_check_) {
-    checkForMissingTagExtractionRules();
-  }
+  checkForMissingTagExtractionRules();
 }

 Network::TransportSocketFactoryPtr
@@ -752,8 +749,8 @@ void BaseIntegrationTest::checkForMissingTagExtractionRules() {
     // that it wasn't extracted.
     const std::string tag_extracted_name = metric.tagExtractedName();
     for (const std::string& stat_prefix : stat_prefixes) {
-      EXPECT_EQ(tag_extracted_name.find(stat_prefix), std::string::npos)
-          << "Missing stat tag-extraction rule for stat '" << tag_extracted_name
+      EXPECT_EQ(tag_extracted_name.find(stat_prefix) == std::string::npos, skip_tag_extraction_rule_check_)
+          << "Failed stat tag-extraction rule for stat '" << tag_extracted_name
           << "' and stat_prefix '" << stat_prefix << "'";
     }
   };

That way tests are failing if we fix something but forget to remove the TODO/skip_tag_extraction_rule_check_

/retest

/retest

I wonder if we should also add this diff (maybe on a followup PR):

Not every stat has the stat_prefix being tested, so I'm pretty sure that change would have failures throughout almost every test that has skip_tag_extraction_rule_check_ == true, eg all the server stats wouldn't have the thrift stat_prefix.


Added CRUD functionality

Implemented MongoDB Cloud Atlas functionality
Added Insert
Added Update
Added Delete
Added Index View

I think this is fine for now but eventually you'll want to try to refactor the mongo into a database service and have it inherit an interface that defines all the unique methods. Then your controller would have a constructor that takes in the Interface as a parameter. Then you can use dependency injection to add the service. Again, good for now can tweak later.


Images are missing on the home page of some chrome extensions. Kindly assign this issue to me

What happened?
When you open the home page, some of the extensions don't show the image, only the alt tag.

How can we reproduce this bug?
Just add the correct URL of images in the tag.
Desktop Information (Optional)
No response
Urgency (Optional)
High priority

@mayank2002-jpg Please wait for the contribution period to start, will start assigning you the issues after that

@mayank2002-jpg you can start working on it

Thanks for assigning me this issue

I have completed this and got merged into the main code. So kindly remove this issue.


Feature request: duplicateParentState via ConstraintHelper

ConstraintLayout encourages "flatten style", so we missing duplicateParentState feature, cuz widgets are sliblings now.
Would be nice to have ConstraintHelper that will share state between referenced views (e.g. state of first view in list on the rest ones).
Seems like it isn't possible to implement this feature without changes to framework or without extending views, cuz there is no listeners for View#onCreateDrawableState nor Drawable#onStateChange.

When you say state, What are the properties of a View you are thinking of?

When you say state, What are the properties of a View you are thinking of?

Drawable state (focused, pressed, etc.)
https://developer.android.com/reference/android/view/View#attr_android:duplicateParentState

Drawable state (focused, pressed, etc.)
https://developer.android.com/reference/android/view/View#attr_android:duplicateParentState

Any news or workaround on this?


vagrant: Add NFS backend for file synchronization for OSX.

Merged as 9e8ae68dfb7a82caccaf93ac932766004f72490d with an expanded commit message, thanks @lonerz!


Configure GitHub action

Hi,
I'm trying to use commitsar as a GH Action with my own config file but I don't know how to set the config in the action
I tried the following combinations:
env:
  COMMITSAR_CONFIG_PATH: ".github/linters/commitsar.yaml"
# or
with:
  COMMITSAR_CONFIG_PATH: ".github/linters/commitsar.yaml"
# or
with:
  config: '.github/linters/commitsar.yaml'
# or
env:
   config: '.github/linters/commitsar.yaml'

But at run, commitsar says there is no config file set:
Run<EMAIL_ADDRESS>  with:
    config: .github/linters/commitsar.yaml
  env:
    config: .github/linters/commitsar.yaml
/usr/bin/docker run --name bba96d741a5cf4cf59[3](https://github.com/xxxxxx/actions/runs/6265205933/job/17013518497#step:4:3)f5c[4](https://github.com/xxxxx/actions/runs/6265205933/job/17013518497#step:4:4)40e1a94fc[5](https://github.com/xxxxx/actions/runs/6265205933/job/17013518497#step:4:5)_09f511 --label 94351b --workdir /github/workspace --rm -e "config" -e "INPUT_CONFIG" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/xxxxxx":"/github/workspace" xxxxx:ba9[6](https://github.com/xxxxx/actions/runs/xxxxxx/job/xxxxxx#step:4:7)d741a5cf4cf593f5c440e1a94fc5

2023/09/21 17:44:25 config file not found, using defaults
   • Starting pipeline: commit-pipeline
   • Starting analysis of commits on branch HEAD

eg: of my action:
name: Linters

on: [pull_request]

jobs:
  validate-commits:
    runs-on: ubuntu-latest
    steps:
      - name: Check out code into the Go module directory
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: Commitsar check
        #uses: docker://aevea/commitsar
        uses<EMAIL_ADDRESS>        with:
          config: '.github/linters/commitsar.yaml'
        env:
          config: '.github/linters/commitsar.yaml'

eg of my config:
commits:
  limit: 1

Thanks a lot

I managed to make it work using the following:
(...)
- name: Commitsar check
  uses: docker://aevea/commitsar
  env:
    COMMITSAR_CONFIG_PATH : ./.github

My repository is structured like this:

.github/workflows/conventional-commits.yml contains the github action with the code from above.
.github/.commitsar.yml is the configuration file.


Error after 1 hour running python proxy.py

Hi @OneSourceConsult
Thanks for your proxy, it work well with my OpenStack. But i have one problem: after 1 hour, my proxy doesn't collect metric from ceilometer anymore. And this is error: http://codepad.org/QIFMATNd
Can you give me any discussion?

Fixed! Apologies for the delay.


Fix for issue#1981

Fix #1981
Update code sample. This is actual version for VS 17

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

#sign-off


How to visualization?

@lufficc Thank you for your good work. I want to know how to show the APs,APm,APl, mAP for COCO and every categories' AP for VOC dataset. Namely, how to use tensorboard in pytorch to show realtime results? Thank you.

Currently this repo has already implemented these.
See:
https://github.com/lufficc/SSD/blob/master/ssd/data/datasets/evaluation/coco/__init__.py#L48-L53
https://github.com/lufficc/SSD/blob/master/ssd/data/datasets/evaluation/voc/__init__.py#L44-L50
You can run tensorboard --logdir <outputs-dir> --port 6006 and open http://<IP_ADDRESS>:6006 to check the visualization.

@lufficc Yeah. Will Tensorboard opened in training phase or test phase or both?
When i run tensorboard --logdir='./outputs/vgg_ssd300_voc0712/tf_logs' --port 6006 , meanwhile a problem has arisen. The pictures are as follows,

How to solve this problem? Thank you.

Tensorboard is opened only in training phase.
I don't know why you have this problem but you can try the solutions below:

use --logdir="./outputs/vgg_ssd300_voc0712"(Double quotes) instead of --logdir='./outputs/vgg_ssd300_voc0712/tf_logs'
upgrade tensorboard.

@lufficc Yeah, it works. Thank you for your help.

Hello, I don't know why I don't have this folder tf_logs after training


How to disable "Add to Homescreen".

I want to cache for web only. I don't want the "Add to Homescreen" feature for mobile. How to configure this ?

Try adding to your manifest.json:
display: 'browser',
I


Improved Docs

Thanks for the Pull Request but in this case is not enough changes to consider it to merge it.


Sign up with google

To verify the ownership of this app we have to merge that html file only then i can add that functionality.


Does not work with M1 new mac Processor

Checklist

[x] I have searched for existing issues
[x] I have looked through the wiki
[x] I have updated MonitorControl to the latest version

Describe the bug
A clear and concise description of what the bug is.
Worked perfectly on my 2018 Mac Mini using an Intel chip with Big Sur so it is not a Big Sur issue, on the New Mac Mini with apple's M1 chip it cannot find the exact same
monitor that I used on the 2018 Mac Mini Intel w/Big Sur. Display shown in Big Sur System Preferences is correct but Monitor Control cannot find
anything so it is just blank under display
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
It says No Supported Display Found even though it found it right away on my 2018 Mac Mini with Intel Processor.
Expected to work the same as it did on my Big Sur 2018 Mac Mini Intel.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
Environment Information (please complete the following information):

macOS version: Big Sur
MonitorControl version:Latest 2.1.0
Monitor(s): LG  27UL850-W

I have exactly the same problem. MonitorControl worked great with my 2020 Intel Macbook Pro.
Now that I have the 2020 M1 Macbook Pro my monitor is not detected.
However, in the settings I can see this:

I have exactly the same problem. MonitorControl worked great with my 2020 Intel Macbook Pro.
Now that I have the 2020 M1 Macbook Pro my monitor is not detected.
However, in the settings I can see this:

dupe #323

dupe #323


feat: remove redundant fields in trace when trace is correct

Goal

avoid comparing some obvious fields, i.e. block_num, transaction_hash
main concern is the comparison of trace_root, so if the outcome is "Same", we ignore the comparison of some fields, i.e. contract_dependencies, storage_dependencies

If the trace root is Same:
{
  "block_num": "6333333", // instead of "Same(633333)"
  "post_response": [
    {
      "trace_root": "Same({n})"
      "transaction_hash": "some_hash", // instead of "Same(some_hash)"
    },
    {
      "trace_root": "Same({n})"
      "transaction_hash": "some_other_hash",
    }
  ]
}

If the trace root is Different:
{
  "block_num": "633333",
  "post_response": [
    {
      "contract_dependencies": [
          // Different {... }, Same, etc...,
      ],
      "storage_dependencies": "Same([2])",
      "trace_root": {
        "execute_invocation": {
          "call_type": "Same(CALL)",
          "calldata": "Same([8])",
          // There is something **Different** down the line
        }
      }
      "transaction_hash": "some_hash",
    }
  ]
}

Changes

update block simulation report to compare trace_root first, in each element in post_response

if trace_root is same, we return comparison of trace_root and transaction_hash without comparison
otherwise, we additionally return the comparison of contract_dependencies and storage_dependencies
this logic is encapsulated in compare_trace method

add unit test for compare_trace

Other solutions

do the comparison first for every trace, then remove the extra fields, i.e. contract_dependencies and storage_dependencies

this was the initial solution. however, this is inefficient as we would still be comparing these additional fields, which goes against the goal

Succeded by #70


Increse default sqlite_max_variable_number

If possible, increase sqlite_max_variable_number.
The default value of SQLITE_LIMIT_VARIABLE_NUMBER in the latest sqlite is 32766.
When dealing with large amounts of data, the default 32766 is too small and painful.
So please increase it.
On In Ubuntu its value is 250,000?
I suggest 1,000,000!
Thx.

Given that most Linux distros seem to set it to 250k, that's a reasonable number to commit to. But it's also a lot of work to change these options (we need separate releases for iOS and Android), we can't just patch cmake files for all platforms.
There's also no clear consensus for this - most distros use 250k, but that's not officially recommended so it's not clear where that comes from. Arch also increases the maximum expression depth to 10k for instance, Debian doesn't. Once Flutter supports native assets in a stable form, we'll be able to compile sqlite3 with a Dart build script that would be easy to configure. Given that different users will also have different requirements (and blindly increasing the amount of variables also has downsides, preparing SELECT ?1000000 will consume lots of memory).
It's not great, but you could copy the build scripts for the platforms you need and manually copy what sqlite3_flutter_libs is doing except that you'd compile sqlite3 with your preferred options.


Svg not allowed require in CRA

import { ReactComponent as Logo} from "./log.svg"; works well
require("./logo.svg").ReactComponent   throw an error
I read the webpack loader setting,.
CRA used babel-plugin-named-asset-import to rewrite  import { ReactComponent as Logo} from "./log.svg";  => import Logo from "svg-react-loader!./log.svg"; , and Svg files doesn't have loader.
That makes require not work.
If an other project build with svgr-loader.
import { ReactComponent as Logo} from "./log.svg" will be builded as require("./logo.svg").ReactComponent .
Will it works in CRA?

We will look into this, but it probably wont be a high priority because you can use import.

Is there a reason you need to use require instead of import?

@iansu
If I use a package build by @svgr/webpack like this. It can't work in CRA.

And I want to know the reason about  why not use svgr as
{
  test: /\.svg$/,
  use: ['@svgr/webpack'],
}

but
plugins: [
 [
    require.resolve('babel-plugin-named-asset-import'),
    {
      loaderMap:{
          svg:{ ReactComponent: '@svgr/webpack?-prettier,-svgo![path]'}
      }
    }
  ]
]


Change suction gripper to utilize contact point array

This modifies the suction gripper to use an array with 5 contact sensors (displayed below)
In order for suction to engage, the center and one outside contact point (left/right/up/down) must be engage OR two opposite outside contact points must be engaged (left + right/up + down).  This makes it so the gripper is perpendicular to a surface before gripping can be engaged.
To test, I have added a world with just a simple manipulation setup:
ros2 launch ros_ign_gazebo ign_gazebo.launch.py ign_args:="-v 4 -r test/simple_arm_demo.sdf"

And spawn an arm:
ros2 launch mbzirc_ign spawn.launch.py name:=simple_arm world:=simple_demo model:=static_arm arm:=mbzirc_oberon7_arm gripper:=mbzirc_suction_gripper z:=1.4

And engage suction:
ros2 topic pub /simple_arm/gripper/suction_on std_msgs/msg/Bool 'data: true'

Signed-off-by: Michael Carroll<EMAIL_ADDRESS>

nice I was able to grip the object with these commands:

I have been using a joystick node I wrote that I will put in a separate PR.

For the contact topics, once suction is enabled and successful, all contacts topics outputs False.

I don't think that's desirable, I'll make it so they output true when the joint is created.


ScreenModel is not disposed when poped and pushed a new screen

I found that a ScreenModel is not disposed (i.e. onDispose() not called; next call of rememberScreenModel() returns the existing instance) when doing:
// In `FooScreenModel`
navigator.popUntilRoot() // or pop()
navigator push BarScreen

If only popUntilRoot()/pop() is called, without a following push(), it's properly disposed.
Version: 1.0.0
Workaround
The following code works (properly disposed)
navigator.replaceAll(MyRootScreen, BarScreen)

I'm not sure if the API is designed as so; if yes, maybe we can have some docs about it?

Can you share more details, maybe a sample code?

Sure. I made a minimal reproducible app with compose desktop.
// Main.kt

// imports omitted

class HomeScreen : Screen {

    @Composable
    override fun Content() {
        val navigator = LocalNavigator.currentOrThrow
        Column(
            Modifier.fillMaxSize(),
            verticalArrangement = Arrangement.Center,
            horizontalAlignment = Alignment.CenterHorizontally
        ) {
            Text("Home Screen")
            Button(onClick = { navigator.push(ContentScreenA()) }) {
                Text("Open Screen A")
            }
        }
    }
}

class ContentScreenAModel : ScreenModel {
    val text = "Content Screen A\nCreated at ${Calendar.getInstance().time}"

    override fun onDispose() {
        println("ContentScreenA disposed")
    }
}

class ContentScreenA : Screen {

    @Composable
    override fun Content() {
        val screenModel = rememberScreenModel { ContentScreenAModel() }
        val navigator = LocalNavigator.currentOrThrow
        Column(
            Modifier.fillMaxSize(),
            verticalArrangement = Arrangement.Center,
            horizontalAlignment = Alignment.CenterHorizontally
        ) {
            Text(screenModel.text)
            Button(onClick = {
                navigator.pop()
                navigator.push(ContentScreenB())
            }) {
                Text("Pop and Open Screen B")
            }
            Button(onClick = {
                navigator.replaceAll(listOf(HomeScreen(), ContentScreenB()))
            }) {
                Text("Replace with Screen B")
            }
            Button(onClick = {
                navigator.pop()
            }) {
                Text("Pop")
            }
        }
    }
}

class ContentScreenB : Screen {

    @Composable
    override fun Content() {
        val navigator = LocalNavigator.currentOrThrow
        Column(
            Modifier.fillMaxSize(),
            verticalArrangement = Arrangement.Center,
            horizontalAlignment = Alignment.CenterHorizontally
        ) {
            Text("Screen B")
            Button(onClick = { navigator.pop() }) {
                Text("Pop")
            }
        }
    }
}

@Composable
@Preview
fun App() {
    MaterialTheme {
        Navigator(HomeScreen())
    }
}

fun main() = application {
    Window(onCloseRequest = ::exitApplication) {
        App()
    }
}

https://github.com/adrielcafe/voyager/assets/7665216/6a6264f9-beee-4235-81c8-1afba7f29ca3
In the video, you can see that:

When doing pop() or replaceAll() from screen A, the model is disposed(log printed and the created time is changed when the screen A is entered the next time)
When doing pop() + push() from screen A, the model is not disposed(the created time remains unchanged)

Source code:
voyager-test.zip

Thanks, I will have a look

Instead of
navigator.pop()
navigator.push(ContentScreenB())

Use:
navigator.replace(ContentScreenB())

I've run into this issue as well, when we need to pop x screens with .popUntil, and then push a new screen.

Ended up just pushing the screen once, and then use a .replace with the same screen

Basicly, you can't do pop and push at the same time.
Voyager in built in with Compose and it composition, so when you do a pop operation, it will have a recompisition and the lastEvent will change to pop event, when this happens, is when Voyager dispose the Screen and it ScreenModels as well.
By doing pop + push the next composition will be a PUSH event and the disposable will not happen, this is why exist the replace.
The navigator API should always be a single operation of the Voyager Stack API.

push(screen) or push(list)
replace(screen)
replaceAll(screen) or replaceAll(list)
pop
popAll
popUntil(predicate)

Understood. Maybe adding some descriptions in the Stack API doc would help users to be aware of this better?
Also I wonder if there's a way to do:
when stack is: A, B, C, D
pop until B and push E, so the stack will be: A, B, E

The stack keeps all the changes you make to it, but if you don't replace or pop, it wont cleanup resources like ScreenModels

The issue is not with Stack API it self, it can handle it.
But if you are listening a State of it in Compose, any state, not particular to Stack API, if you update two times the state, in the next composition you will receive only the last state, is how Compose composition works. The Navigator API is built with the composition events.

Thanks for the details!
Yes, I understand it's not an issue.
To me, it could be more friendly to new users to have some explanations that we are not supposed to use pop + push.
The pop + push way works at first glance: the screen stack is updated as expected.
So it might be difficult for developers to be aware there's something unexpected happening (model not getting disposed).
Another idea is to add some runtime warnings.
The current doc has full info though. People should understand the recommended usage after reading it. (I didn't read it carefully before running into this issue 😅 )

(Answering my own question) I think we can get the current stack contents via navigator.items, edit it whatever we like, and then pass it through replaceAll().

We will document it! Thanks for openning the issue, this was something that daily we understand but forgot to document!
Glad that it was not a blocker.


Rollup Timestream Query API support into existing PR

This PR adds support for the Amazon TimeStream Query API to the rusoto#1857 PR.
I thought it was best to add TimeStream Query API support to the existing TimeStream Write API PR, instead of having two separate PRs for the different TimeStream APIs (which will hopefully result in a faster merge upstream). I also included an endpoint-discovery-aware client as well, to try and keep the crates somewhat consistent.

@Spadi0, thanks for you contribution and let's hope the PR will be merged soon :-).

@Spadi0, thanks for you contribution and let's hope the PR will be merged soon :-).

:crossed_fingers: here's hoping!


MQTT discovery

Description:
This is the successor of https://github.com/home-assistant/home-assistant/pull/4918 as GitHub didn't like my -f push to the existing branch.
MQTT Discovery will enable one to use MQTT devices with only minimal configuration effort of Home Assistant. The configuration is done on the device itself. Similar to the  HTTP binary sensor and the HTTP sensor.
$ mosquitto_pub -V mqttv311 -t "hass/binary_sensor/test123/config" -r -m '{"name": "test1234", "sensor_class": "motion"}'

$ mosquitto_pub -V mqttv311 -t "hass/binary_sensor/test123/state" -m ON

At the moment only binary sensors are supported. More entities will be added to this PRs.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1952
Example entry for configuration.yaml (if applicable):
mqtt:
  discovery: "home-assistant/#"

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

After that I migrate mqtt to async

So I added tests and made some changes to the config. It is now:
mqtt:
  discovery: true
  # Optional
  discovery_prefix: homeassistant


Enable optional metadata tracking in LNLS

Add feature to track subsamples (QPU results), subproblems (BQMs sent to QPU), and samples (burndown)

@jackraymond 👀 👀

@randomir @jackraymond should tracking be placed after SplatComposer() if the intention is to capture the sample of the overall problem after the subproblem has been solved and used to update the original state?

@randomir @jackraymond should tracking be placed after SplatComposer() if the intention is to capture the sample of the overall problem after the subproblem has been solved and used to update the original state? i.e., instead of line 143 in lattice_lnls.py, should it go after the SplatComposers in the conditionals beginning line 145?

Yes, if you want to track samples after being updated with subsamples from QPU.


WIP

Figure out a stray suffix on the expected path to the windows builtins.
Also pick up a pending cleanup now that https://github.com/conda/conda-build/issues/4787 got fixed by the newest conda-build.

So the osx failures are due to https://github.com/conda-forge/boa-feedstock/issues/75


Service registrations

Addresses issues of https://github.com/MassTransit/MassTransit/issues/1372 where services.AddMassTransit() overrides existing services instead of ignoring them.

I merged this and rebased it, waiting on my branch to build, will close this one.


[Synapse] Fixed a typo in validator

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/aim-for-better/azure-cli-extensions.git@FixStatementValidationTypo#subdirectory=src/$EXT&egg=$EXT"

add to S173


Fixturize Unittests

Squash commits of #3592

Todo:

[ ] Fix conflicts between new fixtures and old unittests
[ ] Remove old unittests when suitable fixture exists
[ ] Remove fixtures that return functions, only as necessary (for tests to pass)

Hello @ivan-c! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/test_clinical.py:

Line 315:1: W293 blank line contains whitespace

In the file tests/test_identifier.py:

Line 20:32: E127 continuation line over-indented for visual indent

In the file tests/test_intervention.py:

Line 51:80: E501 line too long (87 > 79 characters)
Line 367:1: E302 expected 2 blank lines, found 1
Line 523:1: E302 expected 2 blank lines, found 1
Line 675:1: E302 expected 2 blank lines, found 1

In the file tests/test_organization.py:

Line 312:36: W291 trailing whitespace

In the file tests/test_portal.py:

Line 24:1: E266 too many leading '#' for block comment
Line 25:80: E501 line too long (99 > 79 characters)

In the file tests/test_practitioner.py:

Line 66:1: E302 expected 2 blank lines, found 1
Line 157:29: E127 continuation line over-indented for visual indent
Line 191:29: E127 continuation line over-indented for visual indent
Line 194:1: E302 expected 2 blank lines, found 1
Line 231:28: E127 continuation line over-indented for visual indent
Line 232:28: E127 continuation line over-indented for visual indent
Line 286:28: E127 continuation line over-indented for visual indent
Line 287:28: E127 continuation line over-indented for visual indent

In the file tests/test_tou.py:

Line 20:1: E266 too many leading '#' for block comment
Line 21:80: E501 line too long (99 > 79 characters)
Line 230:1: E302 expected 2 blank lines, found 1
Line 438:1: E305 expected 2 blank lines after class or function definition, found 0
Line 438:7: E225 missing whitespace around operator

@ivan-c We're at a passing state - there's clearly room for improvement, but I'd love to accept what we have and move on.


Synthesis failed for java-accessapproval

Hello! Autosynth couldn't regenerate java-accessapproval. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmp9yitphi4/googleapis'...
Cloning into '/tmpfs/tmp/tmp9yitphi4/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Note: checking out '6f8350c0df231d7e742fa10dbf929f33047715c9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-04-30 13:57:28 [INFO] Running synthtool
2020-04-30 13:57:28 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/tmpfs/src/github/synthtool/synthtool/__init__.py", line 21, in <module>
    from synthtool import update_check
  File "/tmpfs/src/github/synthtool/synthtool/update_check.py", line 19, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
2020-04-30 13:57:28 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Previous HEAD position was 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
HEAD is now at 7e1c7603 Add an OAuth scope annotation in build_service proto file
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 6b685a2 fix: synthtool path (#515)
Switched to a new branch 'autosynth-87'
2020-04-30 13:57:28 [INFO] Running synthtool
2020-04-30 13:57:28 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/tmpfs/src/github/synthtool/synthtool/__init__.py", line 21, in <module>
    from synthtool import update_check
  File "/tmpfs/src/github/synthtool/synthtool/update_check.py", line 19, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
2020-04-30 13:57:28 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 576, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 457, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 566, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 352, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 362, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-accessapproval. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmp91wxzeuw/googleapis'...
Cloning into '/tmpfs/tmp/tmp91wxzeuw/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Note: checking out '6f8350c0df231d7e742fa10dbf929f33047715c9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-04-30 14:17:18 [INFO] Running synthtool
2020-04-30 14:17:18 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 23, in <module>
    import synthtool.metadata
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 15, in <module>
    import deprecation
ModuleNotFoundError: No module named 'deprecation'
2020-04-30 14:17:18 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Previous HEAD position was 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
HEAD is now at 7e1c7603 Add an OAuth scope annotation in build_service proto file
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 6b685a2 fix: synthtool path (#515)
Switched to a new branch 'autosynth-87'
2020-04-30 14:17:18 [INFO] Running synthtool
2020-04-30 14:17:18 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 23, in <module>
    import synthtool.metadata
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 15, in <module>
    import deprecation
ModuleNotFoundError: No module named 'deprecation'
2020-04-30 14:17:18 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 576, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 457, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 566, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 352, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 362, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-accessapproval. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmppy4ans9v/googleapis'...
Cloning into '/tmpfs/tmp/tmppy4ans9v/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Note: checking out '6f8350c0df231d7e742fa10dbf929f33047715c9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-04-30 14:34:08 [INFO] Running synthtool
2020-04-30 14:34:08 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/tmpfs/src/github/synthtool/synthtool/__init__.py", line 21, in <module>
    from synthtool import update_check
  File "/tmpfs/src/github/synthtool/synthtool/update_check.py", line 19, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
2020-04-30 14:34:09 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Previous HEAD position was 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
HEAD is now at 7e1c7603 Add an OAuth scope annotation in build_service proto file
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 6b685a2 fix: synthtool path (#515)
Switched to a new branch 'autosynth-87'
2020-04-30 14:34:09 [INFO] Running synthtool
2020-04-30 14:34:09 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/tmpfs/src/github/synthtool/synthtool/__init__.py", line 21, in <module>
    from synthtool import update_check
  File "/tmpfs/src/github/synthtool/synthtool/update_check.py", line 19, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'
2020-04-30 14:34:09 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 576, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 457, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 566, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 352, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 362, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-accessapproval. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpykxloet9/googleapis'...
Cloning into '/tmpfs/tmp/tmpykxloet9/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Note: checking out '6f8350c0df231d7e742fa10dbf929f33047715c9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-04-30 14:36:45 [INFO] Running synthtool
2020-04-30 14:36:45 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 23, in <module>
    import synthtool.metadata
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 25, in <module>
    import google.protobuf.json_format
ModuleNotFoundError: No module named 'google'
2020-04-30 14:36:45 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth-self'
Note: checking out '5d34ced387775e71f9fc8565f2c90d5439eb3056'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Previous HEAD position was 6f8350c0 chore: enable gapicv2 for firestore/v1beta1 API
HEAD is now at 7e1c7603 Add an OAuth scope annotation in build_service proto file
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 6b685a2 fix: synthtool path (#515)
Switched to a new branch 'autosynth-87'
2020-04-30 14:36:45 [INFO] Running synthtool
2020-04-30 14:36:45 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 23, in <module>
    import synthtool.metadata
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 25, in <module>
    import google.protobuf.json_format
ModuleNotFoundError: No module named 'google'
2020-04-30 14:36:45 [ERROR] Synthesis failed
HEAD is now at 5d34ced chore(java): allow overriding the versioning section of the Java README (#495) (#84)
Switched to branch 'autosynth'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 576, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 457, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 566, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 352, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 362, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart: