Add green-energy-hub to LF Energy landscape?

For the LFEnergy there is a landscape page that maps software projects in an high-level architecture. More on this technical architecture is available on the website or in this video recording of the Technical Architecture Workshop in 2020. Of course the LFEnergy are represented here, but also other software projects that exist in the same category, both open source or proprietary software.
Green Energy Hub is not on this landscape page, despite being targeted towards the energy sector and even being open source. It makes sense to add Green Energy Hub there. I'm happy to make a pull-request to the landschape git repository but decided to first come here to discuss it with you.
I was thinking of adding the following data to the landscape.yml file, under the section Shared > Data Management. I can also see this being categorized in the Customer and Market section, but that does not (yet) seem to have a data management category.
          - item:
            name: Green Energy Hub
            description:  National energy transmission system operator data hub developing to support change toward decarbonised economies.
            homepage_url: https://github.com/Energinet-DataHub/green-energy-hub
            repo_url: https://github.com/Energinet-DataHub/green-energy-hub
            logo: # Do you have a SVG image?
            twitter: https://twitter.com/energinetdk
            crunchbase: https://www.crunchbase.com/organization/energinet-dk

[ ] I would need to have an SVG image. I can only find the jpg from the git repo. I can try to remake it as a vector, but perhaps you already have an SVG available that can be submitted to the landscape page?

What do you think of this idea and details? Would you like to file the PR yourself, or should I do it?

I took some time to redo the image in a white-filled SVG. (GitHub doesn't support adding svg, so I added it in a zip). I can add that one if you don't have an SVG available.
green-energy-hub.zip


[UNDERTOW-1787] Issues when undertow is setup behind apache proxy

Issue: https://issues.redhat.com/browse/UNDERTOW-1787
Fixes some issues when undertow is behind an (apache) HTTP reverse proxy. See JIRA for more information.
@fl4via No hurries with this one. I just saw this when working in another issue and there are several minor things to fix here. Review it when you have time. I have just sent it to the master branch, if you want it to any other branch just let me know.

I forgot about the proxy tests and it failed with AJP because of the same reason. The ssl_session is also sent by apache as an HEX string and it was parsed as base64. The new PR also modifies AJP in order to use HEX string for session_id and take into consideration teh key_size attribute. I think that now the failures in the test suite are not related to this changes.

@fl4via Remember this PR when you have some time. If you want me to rebase it or something else please just let me know.

I'll rebase so I can retrigger the CI tests


Fix some PHPStan errors

Closes #9

The last one is Expression on left side of ?? is not nullable.
https://github.com/archtechx/laravel-seo/blob/1b2bfb2945713f7c80cd0411fbbb27ec78c40b7f/src/SEOManager.php#L148

meta() returns a $this|string so null (usable by ??) should never be returned
https://github.com/archtechx/laravel-seo/blob/1970b01773a4b29e3c6ffda6275bf566db0ff4ab/src/SEOManager.php#L218-L220
I assume the null can come from this call:
https://github.com/archtechx/laravel-seo/blob/1b2bfb2945713f7c80cd0411fbbb27ec78c40b7f/src/SEOManager.php#L229
So the return typehint should probably be updated to $this|string|null?

I've also just merged a PR into master. There are some new changes, can you make sure that this PR covers them? Probably just merge master into your branch.

I am very happy to contribute.

okay, you can re-merge master now 👍🏻

Final review probably

Thanks!


Decide what to do about "EM 347 ZZZDNU"

This class has a very irregular and strange singleton ID. Unsure if it should be left as it is (maybe there's a good reason for the ZZZDNU??) or if there should be a special rule for the parsing of this class. If the latter, this could guide some design decisions behind #5 in adding custom rules for courses as a whole instead of in specific parsing functions.

Similar situation for HSSHSS 317 Quantitative Social Science except this one appears to legitimately just be a typo. I'm going to just edit both of them to be normal.


Implemented DatePickerDialog Widget in the Widget Catalog

https://user-images.githubusercontent.com/70368661/137623359-a92cecaa-219a-40ae-a86a-f6f321093659.mp4
Hey!!.. I have implemented the DatePicker widget . Kindly review.

Hey!! I am facing some issue in fetching upstream.
after clicking on fetch upstream I get this message - Open a pull request to fetch upstream and review changes or resolve conflicts. Have I done something wrong?

Can you share a screnshot of the same?

Sure.. I am attaching the screenshot.

Let me close this pull request for a while. I need some time to resolve this one.

Dont close it, lets try to fix the issue.


[stable/dex] run jobs as nobody instead of root

What this PR does / why we need it:
When running on a cluster with podsecuritypolicies enabled, the ssl-creation jobs fail because they're being run as root. I'm just switching to user nobody and set the current dir to /tmp to generate the certs.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign  davidkarlsen

/assign desaintmartin

Thanks!
/ok-to-test

Could you make this optional, true by default? This would break openshift AFAIK.

/lgtm


Applications crash

Describe the bug
On my S22 Ultra to apps close itslef when I click on Apps in Hub.
On my watch pro 5, I can't start the app.
To Reproduce
Steps to reproduce the behavior:
On phone

Connect to the flipper
Go to Hub
Click on Apps
The app closed itself

On watch

Click on the app
I see flipper
I see a circle with a white background
The app closed itself

Expected behavior
I want to see the app menu and use flipper with my watch.
I'm on the last version in playstore.
Hope to say everything.

LineageOS 18.1
Flipper 1.5.0 from fdroid
Failed load suggested item
java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType
	at yp.r.b(Unknown Source:2488)
	at yp.v0.c(Unknown Source:24)
	at yp.u0.invoke(Unknown Source:44)
	at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
	at $Proxy2.b(Unknown Source)
	at rb.e.g(Unknown Source:54)
	at um.a.C(Unknown Source:8)
	at rn.m0.run(Unknown Source:107)
	at androidx.appcompat.widget.j.run(Unknown Source:18)
	at xn.i.run(Unknown Source:2)
	at xn.a.run(Unknown Source:93)
Failed load suggested item
java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType
	at yp.r.b(Unknown Source:2488)
	at yp.v0.c(Unknown Source:24)
	at yp.u0.invoke(Unknown Source:44)
	at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
	at $Proxy2.b(Unknown Source)
	at rb.e.g(Unknown Source:54)
	at um.a.C(Unknown Source:8)
	at rn.m0.run(Unknown Source:107)
	at androidx.appcompat.widget.j.run(Unknown Source:18)
	at xn.i.run(Unknown Source:2)
	at xn.a.run(Unknown Source:93)
FATAL EXCEPTION: main
Process: com.flipperdevices.app, PID: 30280
java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType
	at yp.r.b(Unknown Source:2488)
	at yp.v0.c(Unknown Source:24)
	at yp.u0.invoke(Unknown Source:44)
	at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
	at $Proxy3.b(Unknown Source)
	at wb.g.b(Unknown Source:71)
	at rb.c.g(Unknown Source:45)
	at um.a.C(Unknown Source:8)
	at rn.m0.run(Unknown Source:107)
	at androidx.appcompat.widget.j.run(Unknown Source:18)
	at xn.i.run(Unknown Source:2)
	at xn.a.run(Unknown Source:93)
	Suppressed: wn.f: [y1{Cancelling}@6b7302f, Dispatchers.Main.immediate]


☂ Update 10.x documentation

[ ] All new features and stuff

[ ] OCSP request is made using FetchSM

[ ] Upgrading to 10.0.0
[ ] ...

[ ] Remove all derivative metrics from docs and mention it on the release note


Extended JMSSampler

I extended the JMSSampler as when we use byte messages then it is impossible to e.g. make any assertions (all of them fail). I added a case when message is byte message and then I converted it to string. Then assertions work as it is expected.

Hello,
Thanks for contribution.
Unfortunately it cannot be accepted as is, as converting a binary to String may trigger issues.
If you need assertions then maybe a better option would be to compute a hash of it.
Feel free to discuss implementation on dev mailing list.
Thanks


Code isn't working

I try to run the code on my machine and it's not working !

Code is working good, maybe problem come from you


Add GitHub Actions CI

[x] Testing

[x] Unit testing
[x] Code coverage?
[ ] Benchmarking?
[x] Integration testing?

[x] Clippy
[ ] rustfmt
[x] Succesfully builds

rustfmt is being handled by a pre-push hook and benchmarks can be manually run.


CI: Add script to execute/report metrics

This script execute metrics and uses emailreport
tool in order to send results by email.
Fixes: #347
Signed-off-by: Mario Alfredo Carrillo Arevalo<EMAIL_ADDRESS>

New version sent :)

Thanks for the changes. We know we will have modifications coming soon to this script, but still:
lgtm


Xiaomi Vacuum S12

Device model / 设备型号
xiaomi.vacuum.b106eu
Component version / 插件版本
0.7.15
HA core version / HA版本
2024.1.4
Integrated mode / 集成方式
Automatic (自动模式) or Token
The problem / 问题详情
Unable to discover the device <IP_ADDRESS>. It's unusable in HA Core 2024.1.4
Entity attributes / 实体属性
fan_speed_list: Slient, Standard, Medium, Turbo
friendly_name: Xiaomi Robot Vacuum S12 Robot Cleaner
supported_features: 12536
Home Assistant Logs / 系统日志
list:

did: "1055473378"
name: Xiaomi Robot Vacuum S12
host: <IP_ADDRESS>
model: xiaomi.vacuum.b106eu
token: 6a4977335665486f64516d54586e7862
miio_cmd: >-
miiocli device --ip <IP_ADDRESS> --token 6a4977335665486f64516d54586e7862
info
miio_info:
error: Unable to discover the device <IP_ADDRESS>

Problem solved. Instead of automatic connection in configuration, just force cloud connection.

I got it working too, using the force cloud solution.
However, I noticed I can define the aspiration force, but I can not select if I want it to mop only, or to do both dust & mop ...
Anyway to do that ?
I also noticed there is no setting available to select the amount of water to use (like in the app itself)
if someone figured this out, could you help please ? 👍
Thank you very much in advance

I got it working too, using the force cloud solution. However, I noticed I can define the aspiration force, but I can not select if I want it to mop only, or to do both dust & mop ... Anyway to do that ? I also noticed there is no setting available to select the amount of water to use (like in the app itself)
if someone figured this out, could you help please ? 👍 Thank you very much in advance

I have the Same Problems Here. Would be awesome If the Xiaomi s12 would be supported completely.

I can`t connect my vacuum S12, how do you did? Any help would be very appreciated!
With Integration "Xiaomi Miio" I get a message saying something like "unknown device.. cannot be configured following the config flow..."
With hacks maybe?
Thanks!

I can`t connect my vacuum S12, how do you did? Any help would be very appreciated!
With Integration "Xiaomi Miio" I get a message saying something like "unknown device.. cannot be configured following the config flow..."
With hacks maybe?
Thanks!

Just have the same issue now while before the last week it worked perfectly.


add web details command

going to glitch.com/~projectdomain
the web ui for editing the project name, description, and avatar have moved there

they put it back in the editor. could still have this new command though 🤷

fixed in v2.14.0


Updating template.html

On clicking to any button its redirecting the page to open in new tab. Updated some code to open the website in same tab rather than opening it to a new tab

Hello my friend!
 @abhi526691
I think it would be better to keep target="_blank" for linking the projects because we are referring to an external project. The idea is to let the recruiter to stay in your portfolio in case they want to see other project.
Hence I will close it.


Is there an ability to handle multiple accounts in multithreads?

I'm developing Java Spring server for telegram and whatsapp messengers, and i want to know is there an ability to handle multiple whatsapp accounts in one time? Thanks for your work

I think if you change:
.newConnection().name("YourSessionName")
```you can operate with more than 1 session per time, try and report

It worked?

It worked?

Yea, it worked in such way. Sorry for late response, was busy with another staff

No problem! If you have no further questions, you can close the issue now

I think if you change this code:
.newConnection().name("YourSessionName")

on your login logic, you can operate with more than 1 session per time. Try and report
that's an exapmle of login (after register):
var whatsapp = mobileBuilder()
    .newConnection()
    .name("Account-1")
    .device(CompanionDevice.ios(false))
    .autodetectListeners(true)
    .registered()
    .orElseThrow();

After deep testing i've found better way to implement functional i need:
Whatsapp api = Whatsapp.webBuilder()
                    .newConnection(partner.getPhone())
                    .name("your messenger tool name")
                    .unregistered(onQRCode());


Memory leak in uci_lookup_section_ref() function

It looks like the uci_lookup_section_ref() function has a memory leak.
ti is allocated with calloc(), but it's never free()-ed in the function, and as far as I'm aware, the pointer to ti is never passed out of this function.
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L76-L83

@aloisklink I had a look at the function and it seems that it has one memory leak and possibility to free a memory region which is not supposed to be freed by the uwrt_lookup_package.
Memory leek :)
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L76 - when it allocates a struct uci_type_list causing a memory leak
Freeing a pointer which is not supposed to be freed:
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L110
The pointer is freed here: https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L236
Solution memory leak:
Add a sys_free(ti) here https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L107
and remove the below line (no idea why is the purpose of it)
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L113
Solution for freeing the wrong pointer:
Replace the below line with
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L110
ret = sys_strdup(s->e.name)

Memory leek :)

🥬🧅 :laughing:
(Unfortunately, the Unicode® consortium rejected all three proposals for a leek emoji, so instead I have to combine 🥬 and 🧅 :sob:)

Solution memory leak

Your solution sounds good! Feel free to make a PR (although use os_free or just plain free() instead of sys_free())!

Freeing a pointer which is not supposed to be freed:

Actually, I don't think this is an issue. In the function uci_lookup_section_ref(), you don't need to free() the return value. Instead, you need to free(*typestr);
E.g. this is how I believe the function needs to be used:
char *malloced_memory = NULL;
const char *return_value = uci_lookup_section_ref(A, B, &malloced_memory);
free(malloced_memory); // only allocated if need be

I can make a PR that documents this behaviour.

Feel free to make PR.

and remove the below line (no idea why is the purpose of it)
https://github.com/nqminds/edgesec/blob/a3bcd1bdc25771312de474b5549d8f4e5bcd80dd/src/utils/uci_wrt.c#L113

I've figured out the purpose of it (see PR #485 for a fix!)
Basically, if you call this function again with a different section that has the same type as a previous UCI section, it should print @section_name[0], @section_name[1], @section_name[2], ...:

But since we weren't saving the increment, it was always doing @section_name[0], @section_name[0], @section_name[0] (0 each time!).


⚠ Fortnite has degraded performance

In 1249b31, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1418 ms

Resolved: Fortnite performance has improved in 36de00a.


Change cloud build to the docker gpu file

Would make more sense to ensure that our GPU file always works right? Since that is what we actually use to train

We could also just build both of them
tir. 18. jan. 2022 kl. 09.26 skrev AndersBensen @.***>:

Would make more sense to ensure that our GPU file always works right?
Since that is what we actually use to train
—
Reply to this email directly, view it on GitHub
https://github.com/magn3141/mlops_project/issues/14, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBC4QQZO4PBSS27TUBR4H3UWUP47ANCNFSM5MGQMJBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


No devices found with name or id matching 'chrome'

Steps to Reproduce

run flutter upgrade to get Flutter 1.9.1+hotfix.2
run flutter config --enable-web
run flutter devices and you will get No devices detected.
try to run flutter run -d chrome for an existing flutter web application and you will get  No devices found with name or id matching 'chrome'

Flutter Doctor Output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.14.6 18G95, locale
    en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2019.2.2)
[✓] VS Code (version 1.38.1)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Turns out you need to be on the master channel not stable.

More info about the channels: https://github.com/flutter/flutter/wiki/Flutter-build-release-channels

but the flutter docs for web suggests to be on the dev channel https://flutter.dev/docs/get-started/web

I had the same problem after do the official Flutter getting started. I solved my problem setting an environment variable CHROME_EXECUTABLE with the path of the Chrome executable on my system.


Option to apply turbo bitstream loading in full testbenches for CCFF v2.0

Is your feature request related to a problem? Please describe.
In #1140 , the CCFF v2.0 allows users to define separated clocks on each configuration chain. Accordingly, the full testbench generator is upgraded to support the feature. In the full testbench, each programming clock is enabled for a fixed number of clock cycles, one after another. In such case, the simulation will take a long run. For example, there are 8 programming clocks and each clock controls 2k configuration bits. Then, 8x2 = 16k clock cycles are required to accomplish programming.
In practice, some turbo mode may be applied. For instance, users may start a few programming blocks at the same time, to reduce the time required for bitstream downloading.
Therefore, a new feature is required to customize the turbo mode for CCFF v2.0 w.r.t. testbench generators.
Describe the solution you'd like
Some new syntax should be added the openfpga simulation setting file
The configuration file will be in XML file format
<programming frequency="50MHz">
      <turbo_mode>
        <phase id ="0" port="prog_clk[0:3]"/>
        <phase id ="1" port="prog_clk[4:7]"/>
      </turbo_mode>
</programming>

Other bugs to be fixed:
The config enable should follow the last bit of config_done
reg [0:7] __config_done__;
assign config_enable[0] = __config_done__[0]; #	-> assign config_enable[0] = __config_done__[7]
always @(negedge __prog_clock___reg__[0]) begin # -> always @(negedge __prog_clock___reg__[5]) begin
	if (bit_index5 >= `BITSTREAM_LENGTH5) begin
		__config_done__[5] <= 1'b1;
	end else if (__config_done__[4] == 1'b1 && bit_index5 >= 0 && bit_index5 < `BITSTREAM_LENGTH5) begin
		ccff_head[0:31] <= bit_mem[bit_index5];
		bit_index5 <= bit_index5 + 1;
	end
end


Consistent handling for call start time

From lib/adhearsion/call.rb:
    # @return [Time] the time at which the call began. For inbound calls this is the time at which the call was offered to Adhearsion. For outbound calls it is the time at which the remote party answered.
    attr_reader :start_time

This is inconsistent. I think this should be:

For inbound calls, the time the call was offered to Adhearsion
For outbound calls, the time at which the call was dialed

We can probably also add an :answer_time attribute which tracks the time at which the call was answered.

:+1:


DVI and MicroPython support

Is there any way being able to have DVI output from MicroPython script (eg: create a terminal, having REPL available on screen, display some graphics) ?

You can take a look at this fork where I hacked in a virtual console with DVI:
https://github.com/Wren6991/micropython/tree/dvi-vt100
It's not for the faint of heart, and IIRC I broke a few things (like flash programming). The code is there if you want to hack on it.
The approach was to steal the second core from MicroPython, and run some bare metal DVI stuff on core 1, with the MicroPython interpreter on core 0.

I followed your approach to integrate DVI in Micropython.
Yes its not so easy/possible to get flash programming running while DVI is running. I stopped trying this because of some notes from flash.h:
"* Like other hardware_flash functions, the flash is not

accessible for execute-in-place transfers whilst the command is in
progress, so entering a flash-resident interrupt handler or executing flash
code on the second core concurrently will be fatal. To avoid these pitfalls
it is recommended that this function only be used to extract flash metadata
during startup, before the main application begins to run"

After some hours of trying the flash thing, I decided to store the data on SD.
Changing the frozen modules _boot.py for SD Card Support and adding the sdcard.py
source and do some minor changes on main.c everything works fine (vscode/rshell/Thonny)
Setup:
DVI Breakout Board	on pins 12, 18, 16, clk pin 14,
MCP4822 DAC		on SPI 1
SD Card Reader		on SPI 0
Pico Probe 		on UART GPIO 0,1
DVI uses

Front/Back buffer with 320x240 8bpp, nice for gaming
or
1 Buffer 320x240 16bpp
with blinking cursor, 8x8 font, etc.

The DAC is for sound generation has 8 channels sine/saw/triangle/rectangle/noise generation
with ADSR envelope and 12 Bit sound at 22050 sample rate.
The Micropython core modules are enhanced for vga, sprite, graphic and sound.
Finally I have a nice retro computer running Python.
Thanks a lot for your work on that DVI thing.


Synthesis failed for KnowledgeGraphSearch

Hello! Autosynth couldn't regenerate KnowledgeGraphSearch. :broken_heart:
Here's the output from running synth.py:
2020-12-18 06:19:03,707 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-18 06:19:04,636 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-18 06:19:04,639 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-18 06:19:04,642 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-18 06:19:04,645 autosynth [DEBUG] > Running: git config push.default simple
2020-12-18 06:19:04,648 autosynth [DEBUG] > Running: git branch -f autosynth-knowledgegraphsearch
2020-12-18 06:19:04,651 autosynth [DEBUG] > Running: git checkout autosynth-knowledgegraphsearch
Switched to branch 'autosynth-knowledgegraphsearch'
2020-12-18 06:19:04,907 autosynth [INFO] > Running synthtool
2020-12-18 06:19:04,907 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--']
2020-12-18 06:19:04,908 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/KnowledgeGraphSearch/sponge_log.log
2020-12-18 06:19:04,911 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/knowledge_graph_search/synth.metadata synth.py -- KnowledgeGraphSearch
2020-12-18 06:19:05,131 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-knowledgegraphsearch
nothing to commit, working tree clean
2020-12-18 06:19:06,903 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpgg7sy8w4/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpgg7sy8w4/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 28 files (.ex)
Generated google_apis app

14:19:37.947 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:19:38.262 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/rest?version=v1

14:19:38.339 [info]  FOUND: https://kgsearch.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200809, new=20201113, generating=true
Creating leading directories
Writing SearchResponse to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/model/search_response.ex.
Writing Entities to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/api/entities.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

14:19:38.747 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-18 06:19:41,800 autosynth [ERROR] > Synthesis failed
2020-12-18 06:19:41,801 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--', 'KnowledgeGraphSearch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating KnowledgeGraphSearch. :sob:
Here's the output from running synth.py:
2020-12-19 06:16:47,792 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-19 06:16:48,681 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-19 06:16:48,684 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-19 06:16:48,687 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-19 06:16:48,690 autosynth [DEBUG] > Running: git config push.default simple
2020-12-19 06:16:48,692 autosynth [DEBUG] > Running: git branch -f autosynth-knowledgegraphsearch
2020-12-19 06:16:48,695 autosynth [DEBUG] > Running: git checkout autosynth-knowledgegraphsearch
Switched to branch 'autosynth-knowledgegraphsearch'
2020-12-19 06:16:48,951 autosynth [INFO] > Running synthtool
2020-12-19 06:16:48,951 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--']
2020-12-19 06:16:48,951 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/KnowledgeGraphSearch/sponge_log.log
2020-12-19 06:16:48,953 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/knowledge_graph_search/synth.metadata synth.py -- KnowledgeGraphSearch
2020-12-19 06:16:49,170 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-knowledgegraphsearch
nothing to commit, working tree clean
2020-12-19 06:16:50,985 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmprk5e1ly1/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmprk5e1ly1/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 28 files (.ex)
Generated google_apis app

14:17:21.297 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:17:21.634 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/rest?version=v1

14:17:21.847 [info]  FOUND: https://kgsearch.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200809, new=20201113, generating=true
Creating leading directories
Writing SearchResponse to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/model/search_response.ex.
Writing Entities to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/api/entities.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

14:17:22.278 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-19 06:17:25,569 autosynth [ERROR] > Synthesis failed
2020-12-19 06:17:25,570 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--', 'KnowledgeGraphSearch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating KnowledgeGraphSearch. :sob:
Here's the output from running synth.py:
2020-12-20 06:22:30,397 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-20 06:22:31,301 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-20 06:22:31,304 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-20 06:22:31,307 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-20 06:22:31,310 autosynth [DEBUG] > Running: git config push.default simple
2020-12-20 06:22:31,313 autosynth [DEBUG] > Running: git branch -f autosynth-knowledgegraphsearch
2020-12-20 06:22:31,317 autosynth [DEBUG] > Running: git checkout autosynth-knowledgegraphsearch
Switched to branch 'autosynth-knowledgegraphsearch'
2020-12-20 06:22:31,547 autosynth [INFO] > Running synthtool
2020-12-20 06:22:31,547 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--']
2020-12-20 06:22:31,547 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/KnowledgeGraphSearch/sponge_log.log
2020-12-20 06:22:31,550 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/knowledge_graph_search/synth.metadata synth.py -- KnowledgeGraphSearch
2020-12-20 06:22:31,780 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-knowledgegraphsearch
nothing to commit, working tree clean
2020-12-20 06:22:33,620 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp4elws2f1/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp4elws2f1/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 28 files (.ex)
Generated google_apis app

14:23:06.913 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:23:07.281 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/rest?version=v1

14:23:07.486 [info]  FOUND: https://kgsearch.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200809, new=20201113, generating=true
Creating leading directories
Writing SearchResponse to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/model/search_response.ex.
Writing Entities to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/api/entities.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

14:23:07.915 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-20 06:23:11,109 autosynth [ERROR] > Synthesis failed
2020-12-20 06:23:11,109 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--', 'KnowledgeGraphSearch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating KnowledgeGraphSearch. :sob:
Here's the output from running synth.py:
2020-12-21 06:14:45,345 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-21 06:14:46,202 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-21 06:14:46,205 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-21 06:14:46,207 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-21 06:14:46,210 autosynth [DEBUG] > Running: git config push.default simple
2020-12-21 06:14:46,213 autosynth [DEBUG] > Running: git branch -f autosynth-knowledgegraphsearch
2020-12-21 06:14:46,216 autosynth [DEBUG] > Running: git checkout autosynth-knowledgegraphsearch
Switched to branch 'autosynth-knowledgegraphsearch'
2020-12-21 06:14:46,508 autosynth [INFO] > Running synthtool
2020-12-21 06:14:46,509 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--']
2020-12-21 06:14:46,509 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/KnowledgeGraphSearch/sponge_log.log
2020-12-21 06:14:46,511 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/knowledge_graph_search/synth.metadata synth.py -- KnowledgeGraphSearch
2020-12-21 06:14:46,725 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-knowledgegraphsearch
nothing to commit, working tree clean
2020-12-21 06:14:48,439 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpbgvy4dy0/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpbgvy4dy0/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 28 files (.ex)
Generated google_apis app

14:15:17.708 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:15:18.021 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/rest?version=v1

14:15:18.227 [info]  FOUND: https://kgsearch.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200809, new=20201113, generating=true
Creating leading directories
Writing SearchResponse to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/model/search_response.ex.
Writing Entities to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/api/entities.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

14:15:18.635 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-21 06:15:21,749 autosynth [ERROR] > Synthesis failed
2020-12-21 06:15:21,749 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--', 'KnowledgeGraphSearch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating KnowledgeGraphSearch. :sob:
Here's the output from running synth.py:
2020-12-22 06:15:45,419 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-22 06:15:46,281 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-22 06:15:46,284 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-22 06:15:46,287 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-22 06:15:46,291 autosynth [DEBUG] > Running: git config push.default simple
2020-12-22 06:15:46,293 autosynth [DEBUG] > Running: git branch -f autosynth-knowledgegraphsearch
2020-12-22 06:15:46,297 autosynth [DEBUG] > Running: git checkout autosynth-knowledgegraphsearch
Switched to branch 'autosynth-knowledgegraphsearch'
2020-12-22 06:15:46,606 autosynth [INFO] > Running synthtool
2020-12-22 06:15:46,606 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--']
2020-12-22 06:15:46,606 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/KnowledgeGraphSearch/sponge_log.log
2020-12-22 06:15:46,609 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/knowledge_graph_search/synth.metadata synth.py -- KnowledgeGraphSearch
2020-12-22 06:15:46,830 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-knowledgegraphsearch
nothing to commit, working tree clean
2020-12-22 06:15:48,647 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp04jm0wvo/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp04jm0wvo/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh KnowledgeGraphSearch
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 28 files (.ex)
Generated google_apis app

14:16:19.587 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:16:19.897 [info]  FETCHING: https://kgsearch.googleapis.com/$discovery/rest?version=v1

14:16:20.114 [info]  FOUND: https://kgsearch.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200809, new=20201113, generating=true
Creating leading directories
Writing SearchResponse to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/model/search_response.ex.
Writing Entities to clients/knowledge_graph_search/lib/google_api/knowledge_graph_search/v1/api/entities.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

14:16:20.520 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-22 06:16:23,599 autosynth [ERROR] > Synthesis failed
2020-12-22 06:16:23,599 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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', 'clients/knowledge_graph_search/synth.metadata', 'synth.py', '--', 'KnowledgeGraphSearch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Use Traefik instead of HAProxy

This PR adds a full configuration to setup a WhatsApp proxy with Traefik, expose similar ports to existing haproxy configuration, but with a much simpler setup process and more versatile configurations.
The main advantages over HAProxy include:

No more building process. only a compose file and traefik image from docker official image, minimize maintenance cost for project maintainers. (Resolves #131)
Much simpler setup process for users. docker compose up -d is all we need.
Safer default settings. Using wildcard DNS for proxy access protect server from malicious scanners. The domain name defaults to whatsapp-<host-ip>.traefik.me but easy configurable, user can change to whatever-<host-ip>.other-wildcard-dns.provider even their own domain names.
The domain name is essentially the password for accessing the proxy, while others can only see an empty 404 page, which resolves #16, also resolves #120. The only server fingerprint is the default TLS certificate which only indicate it being a traefik server but not whatsapp proxy server. and it can also be further anonymized easily
the server name setting can even be hot reloaded (a traefik feature😉)
Easier co-existance with other web services on same server, saving precious 80/443 ports. Traefik is a container-native edge router (a reverse proxy) which is much much simpler to manage than nginx/haproxy if all your services are running in docker.
One-click ACME setup. The necessary config blocks are provided as comments inside traefik.toml and whatsapp_proxy.toml. However the certificate is not very important because WhatsApp client does not verify this certificate, and medias are sent with TLS passthrough, the connection of which is already secure.

I'd recommend Traefik to be the default option for average users, but let it be an alternative for now 😉

Copyright (c) Meta Platforms, Inc. and affiliates.

License found in the LICENSE file in the root directory
of this source tree.
version: '3.3'
services:
proxy:
container_name: whatsapp_proxy
build: ../
restart: unless-stopped
ports:
- "80:80"     # HTTP
- "443:443"   # HTTPS
- "5222:5222" # JABBER
- "8199:8199" # HAPROXY statistics page
- "8080:8080" # HTTP with accept-proxy processing
- "8443:8443" # HTTPS with accept-proxy processing
- "8222:8222" # JABBER with accept-proxy processing
- "587:587"   # whatsapp.net
- "7777:7777" # whatsapp.net
healthcheck:
test: /usr/local/bin/healthcheck.sh
interval: 10s
start_period: 5s
environment:
- PUBLIC_IP=<IP_ADDRESS>

I need to share my what's app image or file.but i Can't

@GoOd91BoY you should use markdown code block if you want to share your compose.yml config.

I need to share my what's app image or file.but i Can't

and why not?

Thanks for this! I'm a bit doubtful Meta will merge any time soon, but it's certainly a useful WhatsApp proxy with more minimal config. For others that think this sounds useful you can use it more easily on the author's branch here: https://github.com/ttimasdf/whatsapp-proxy/blob/with-traefik/traefik/README.md

Do you need two separate servers for WhatsApp proxy and Traefik? Otherwise, the ports will conflict.

Doesn't work

@ttimasdf
if I run curl -k -v https://traefik-proxy.com:587 to connect to this PR, does it still show CN=*.whatsapp.net?
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Menlo Park; O=Meta Platforms, Inc.; CN=*.whatsapp.net


refactor(core): allow adding edges with missing source or target nodes

is there a way to opt-out of this behavior? I don't know why this would be useful, and in my application, it prevents the app from automatically recovering from an error. Of course, I'm working on fixing the bug that I introduced that causes edges with a missing source/target to be added in the first place - but the bug would have caused a much smaller problem with the pre-1.24.0 behavior of refusing to add the edge. I would much rather globally turn on the behavior from before this fix in my app.

The behavior has been changed to match the behavior of ReactFlow as I don't want it to drift apart too much.
In RF you can add an "invalid" edge, it just won't be rendered.
It's still in your edges array and will just stay in there until it becomes valid (missing source/target node is added).
You can listen to these errors with the onError event though and just filter the edges out yourself if that's necessary but the previous behavior would've just removed elements from your state without you really knowing about it and when saved again those elements would be gone, which I don't want to decide for you.

Makes sense, I suppose. In my application nodes are only allowed to have one outgoing edge from each handle, and we disable that handle if there is an outgoing edge, so the behavior the user gets now if there's a bug that causes an invalid edge to be added is that the handle just seems broken and a new/replacement connection can't be made. But I see your point - I guess I can re-add this error handling myself if I want.


Replace axios with fetch based alternative

Currently, we are using axios library to make HTTP requests. It is based on an XHR client in a browser that is old and obsolete and is not further developed. fetch is the current standard for making modern requests. It for example supports streaming responses from server, which XHR does not support. And in future it will most probably support even streaming requests. We should therefore switch to either native fetch or some fetch's based library.
I propose to use ky (or its isomorphic version ky-universal) that shares a lot of the same API with fetch but adds some small but important behaviors and functionality like:

Simpler API
Method shortcuts (ky.post())
Treats non-2xx status codes as errors (after redirects)
Retries failed requests
JSON option
Timeout support
URL prefix option
Instances with custom defaults
Hooks

No upload progress is a big deal breaker for us, we'll have to drop this dependency now.
Why not giving the option to provide a custom fetch implementation? similar to what other packages do, like ccxt.

@mattiaz9 sorry to hear that, but I am happy you raised your issue!
Well, we could do that, but I am not sure if it would solve anything. Are you developing on browser-side or NodeJS?
To my knowledge, it is not possible to provide nor mock the upload tracking in browsers. If you know about a way please let me know.
It is possible to do this in NodeJS and it is something we plan to do for as per this issue: https://github.com/ethersphere/bee-js/issues/397

@AuHau I'm developing on browser not Node.
I'm not sure how it could be done, or how easy It'd be, since, if I'm not mistaken, you used a custom fetch implementation.
I found this: https://github.com/lifeomic/axios-fetch which should build a fetch like function using axios. So I believe it could be possible, but you'll need to provide an option to override the default implementation.

Well, I have not exactly used custom fetch per se, but rather a utility that extends bit its functionality (ky). That said I think it allows to use of a custom fetch implementation on its own. See it for example here: https://github.com/sindresorhus/ky-universal/blob/main/index.js#L8
But even if ky would use this custom axios-fetch implementation you would still not get any information about the upload progress right? We would have to expose that somehow...

Or I guess you could use its "Transforming requests" functionality to catch the request and append an upload-progress callback to it and then track the progress? 🤔
That said, this workaround would for example break the download streaming which was one of the reason for adopting fetch.

FYI. please also comment on this issue to push the WHATWG to implement proper upload progress tracking for fetch.

Or I guess you could use its "Transforming requests" functionality to catch the request and append an upload-progress callback to it and then track the progress? 🤔
That said, this workaround would for example break the download streaming which was one of the reason for adopting fetch.

I'm not familiar with the download streaming. That being said the option to override fetch could be implemented in only the api that allows that. Regarding the upload progress, that would be managed by the axios instance so in theory you wouldn't need to expose anything.
Example:
const axiosInstance = axios.create({
  onUploadProgress: () => {...}
})
const fetch = buildAxiosFetch(axiosInstance, ...)
const fileHash = await bee.uploadData(batchId, "Bee is awesome!",  { fetch })

I see, that is interesting. We will discuss this. Thanks for the input!

@mattiaz9 we discussed this and we are on-board for this solution. We will validate that the solution you propose indeed will yield the wanted result and if so, then we will implement it! 👍

@AuHau sounds great, thanks!

@mattiaz9 just to update. I was able to create a prototype example that made working this approach although the axios-fetch needed bit hacking, which is now put into PR. Feel free to endorse it. So will move further with implementing support for it in bee-js.


Internal Server Error - HandshakeFailed

After granting access, I receive this error:
Internal Server Error
HandshakeFailed (Error_Protocol ("certificate rejected: chain doesn't match each other",True,CertificateUnknown))

+1


feat: add shared Markdown configuration (resolves #15, resolves #158)

TODO:

[ ] update README

@jobara Now I'm wondering if we should use a totally different solution ,something like this: https://github.com/KittyGiraudel/eleventy-plugin-footnotes
It seems much better for accessibility. See: https://kittygiraudel.com/2020/11/24/accessible-footnotes-and-a-bit-of-react/


ERROR: Cannot install -r requirements.txt (line 13), -r requirements.txt (line 14) and cryptography==2.4.2 because these package versions have conflicting dependencies

Hi. Output from trying to install requirements:
ERROR: Cannot install -r requirements.txt (line 13), -r requirements.txt (line 14) and cryptography==2.4.2 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested cryptography==2.4.2
    esptool 4.4 depends on cryptography>=2.1.4
    esp-secure-cert-tool 1.0.1 depends on cryptography==36.0.0

This conflict seems to have been present in requirements.txt for some months.

Also getting the same, on a clean IDF 5.1 Docker image as well! Really need a fix here asap


Resource naming rules need to be updated

For the following entities, the 'Valid Characters' cell should include "Can't use whitespace":
virtualMachine
virtualMachineScaleSets

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

ID: 374ec8eb-64d4-3766-5c5e-39137a262ffd
Version Independent ID: 3abeeae9-6854-651a-483c-a1673eea9f9f
Content: Resource naming restrictions - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/resource-name-rules.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@arunrab - thanks for this feedback. I'll add it to the article.

The update should get published later today.
#please-close

@tfitzmac Thanks for the quick response. :+1:


fix(breadcrumb): wrong name in treemap breadcrumb

@pissang I check the code, breadcrumb doesn't support emphasis from day one, so I think it's better to remove it.


chore: Add options

Signed-off-by: Bo-Yi Wu<EMAIL_ADDRESS>

Codecov Report

Merging #32 (081322f) into master (d2b56b8) will increase coverage by 1.91%.
The diff coverage is 97.87%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   85.06%   86.98%   +1.91%
==========================================
  Files           7        8       +1
  Lines         308      315       +7
==========================================
+ Hits          262      274      +12
+ Misses         37       33       -4
+ Partials        9        8       -1

Flag
Coverage Δ

go-
?

go-1.13
86.03% <97.87%> (+0.96%)
:arrow_up:

go-1.14
86.98% <97.87%> (+1.91%)
:arrow_up:

go-1.15
86.03% <97.87%> (+0.96%)
:arrow_up:

go-1.16
86.03% <97.87%> (+0.96%)
:arrow_up:

go-1.17
86.03% <97.87%> (+0.96%)
:arrow_up:

macos-latest
?

ubuntu-latest
86.98% <97.87%> (+1.91%)
:arrow_up:

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

Impacted Files
Coverage Δ

options.go
97.29% <97.29%> (ø)

consumer.go
86.02% <100.00%> (+0.83%)
:arrow_up:

queue.go
88.23% <100.00%> (-1.51%)
:arrow_down:

worker_empty.go
57.14% <0.00%> (+42.85%)
:arrow_up:

Continue to review full report at Codecov.

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