LAN ipv6 track interface does not work when WAN v6 prefix changed

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
My opnsense setup does receive its WAN v6 prefix via dhcpv6. Unfortunately my ISP gives me a dynamic v6 prefix.
LAN is configured as "track interface". Now everytime when there is a reconnect on ISP side, the LAN v6 connection doesn't work again. It still has the old prefix and advertises that to the LAN. The WAN interface is perfectly fine and ping6 google.com from the opnsense CLI works.
I found out that configctl interface reconfigure fixes the problem immediately. The only downside here is that the clients do not lose their old prefixes.
I already searched the forums and found similar issues, but no solution yet. I use the latest 20.7.7 version.

I have exactly the same problem from time to time. I'm not sure since when exactly, but I never noticed IPv6 related problems in the past and I haven't recently changed any configuration so either it might have been introduced with one of the last updates, or my provider changed something. I'm currently running 20.7.7_1-amd64.
The problem is very obvious in the network as all clients are extremely slow as they try connecting via IPv6 at first until a timeout happens and then possibly try again using IPv4.
Here the relevant section from the WAN interface when the problem is present. The WAN interface has two IPs, the old one (blue) and the new one (green). All clients in my LAN still use the old prefix and thus don't get any responses from foreign servers.

After pressing the DHCP reload button the old IP is gone and everything is working again for an undefined time

It might have something to do with preferred/valid IPv6 addresses. However, I'd expect even if the "old prefix" is not preferred any longer it should still work.

I have exactly the same problem from time to time. I'm not sure since when exactly, but I never noticed IPv6 related problems in the past and I haven't recently changed any configuration so either it might have been introduced with one of the last updates, or my provider changed something. I'm currently running 20.7.7_1-amd64.
The problem is very obvious in the network as all clients are extremely slow as they try connecting via IPv6 at first until a timeout happens and then possibly try again using IPv4.
Here the relevant section from the WAN interface when the problem is present. The WAN interface has two IPs, the old one (blue) and the new one (green). All clients in my LAN still use the old prefix and thus don't get any responses from foreign servers.

After pressing the DHCP reload button the old IP is gone and everything is working again for an undefined time

It might have something to do with preferred/valid IPv6 addresses. However, I'd expect even if the "old prefix" is not preferred any longer it should still work.

I cannot be certain but suspect the issue partly is related to #4338 since the RA should be sent out with zero valid and preferred lifetime (RFC7084 sec. 4.3 L-13) when such prefix delegation change happens, so that LAN client knows the prefix is not in effect anymore. and subsequent Router Solicitation will supplement them with new prefix.
These actions hinge on a reliably working router advertisement daemon. My current workaround is periodically renew WAN and following with a radvd restart cronjob after a short delay. (the "invalidating old prefix" RA may still miss but at least RA with new prefix gets out as soon a possible)
Waiting for 20.7.8 or 21.1 to see if I can kill the workaround.

I cannot be certain but suspect the issue partly is related to #4338 since the RA should be sent out with zero valid and preferred lifetime (RFC7084 sec. 4.3 L-13) when such prefix delegation change happens, so that LAN client knows the prefix is not in effect anymore. and subsequent Router Solicitation will supplement them with new prefix.
These actions hinge on a reliably working router advertisement daemon. My current workaround is periodically renew WAN and following with a radvd restart cronjob after a short delay. (the "invalidating old prefix" RA may still miss but at least RA with new prefix gets out as soon a possible)
Waiting for 20.7.8 or 21.1 to see if I can kill the workaround.

So when using DHCP v6 there is no mechanism to look for a prefix change. I tried to research how other projects deal with this but you can find a lot of dead ends in discussions basically saying the prefix change is not working, especially when the prefix change is forced ahead of the end of the lifetime.
If anyone has any real world solution please let me know...
Cheers,
Franco

So when using DHCP v6 there is no mechanism to look for a prefix change. I tried to research how other projects deal with this but you can find a lot of dead ends in discussions basically saying the prefix change is not working, especially when the prefix change is forced ahead of the end of the lifetime.
If anyone has any real world solution please let me know...
Cheers,
Franco

@fichtner .. PM me on this.

@fichtner .. PM me on this.

@marjohn56 you on IRC?

@marjohn56 you on IRC?

Can be... gimme a mo

Can be... gimme a mo

Would be great if there is a proper solution. Perhaps a cronjob running every minute that checks for changed dhcp prefix on wan side would be sufficient. It's not great, but at least it should work.

Would be great if there is a proper solution. Perhaps a cronjob running every minute that checks for changed dhcp prefix on wan side would be sufficient. It's not great, but at least it should work.

It's not that simple I can assure you. :)

It's not that simple I can assure you. :)

But at least it works. Just tried it on 21.1rc1. Script checks v6 on wanif every minute. If that changes, the script runs a 'configctl interface reconfigure' and the lanif gets its new address and so do the clients. I also tried just restarting radvd, but that did not help.

But at least it works. Just tried it on 21.1rc1. Script checks v6 on wanif every minute. If that changes, the script runs a 'configctl interface reconfigure' and the lanif gets its new address and so do the clients. I also tried just restarting radvd, but that did not help.

The problem is assuming the issue is simple and fixing it will cause many complaints quickly with restarting connectivity every minute in a loop for users who didn't know they had an issue. ;)

The problem is assuming the issue is simple and fixing it will cause many complaints quickly with restarting connectivity every minute in a loop for users who didn't know they had an issue. ;)

@fichtner Ok, now I understand what you meant :) I fully agree with you:  This is an ugly hack and should not be implemented in opnsense. It just works for me locally.

@fichtner Ok, now I understand what you meant :) I fully agree with you:  This is an ugly hack and should not be implemented in opnsense. It just works for me locally.

Any new information on this issue aside from the hacky cron-job solution?

Unfortunately not. I disabled IPv6 currently as the cron "solution" stopped working after upgrading to some 21.7 release. I did not debug it further, but it seemed that restarting the interface stack doesn't help anymore. I decided to switch to PPPoE Passthrough on my fritzbox.


mkpr package.json sed s/"npm-pkgbuild":.*/"npm-pkgbuild":"^6.3.6",/

Pull Request Test Coverage Report for Build 1518

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.399%

Totals

Change from base Build 1515:
0.0%

Covered Lines:
301

Relevant Lines:
302

💛  - Coveralls


Refactor DeleteByID

This PR introduced a new generic method DeleteByID[T any](ctx context.Context, id int64), so no more deleteByID methods need to be implemented for current models or future models.

Is this PR still alive?


Sounds like we need to add a version number soon, warning on HA core 2021.3

From release notes:
Custom integrations now require a version key in their manifest file, this also means that all custom integrations now require a manifest file.
If you are using a legacy custom integration like custom_components/awesome.py this now needs to move to custom_components/awesome/init.py so you can add custom_components/awesome/manifest.json to it.
For more information about integration, manifests have a look here: https://developers.home-assistant.io/docs/creating_integration_manifest
For now, this will create a warning on startup. But this will eventually be blocked from loading if it’s missing a version in the manifest.
If you see these warnings, please report the issue with the author of that custom integration.
(@ludeeus - #45919)

@Rydcal you suggest to delete old componenet and install this one?
https://github.com/xerxes87/pyfujitsu_for_homeassistant

Yep,  this original branch was last updated in 2019.

why we can't open issue on repository https://github.com/xerxes87/pyfujitsu_for_homeassistant?

can we add homekit section to manifest.json?
{
"homekit": {
"models": [
"FUJITSU"
]
}
}
https://developers.home-assistant.io/docs/creating_integration_manifest/

why we can't open issue on repository https://github.com/xerxes87/pyfujitsu_for_homeassistant?

The maintainer of that fork probably hasn't enabled issues in the github settings. This project is in need of a fork that will accept merge requests. I think the maintainer over at https://github.com/xerxes87/pyfujitsu_for_homeassistant will probably accept pull requests if you can get in contact with him (probably the best bet would be the HA Community Forum)


support rolling clean up log file,based size and time policy.

Coverage decreased (-0.08%) to 52.118% when pulling 862950837ee35af5c515246dc55cbf8d1a7de2d1 on JaredTan95:master into bafd02c2593ff2e18a4871b7345ac875aafcd59a on ctripcorp:master.

I upgraded apollo's spring boot to 2.0 recently, so that we could use spring boot's built-in feature (logging.file.max-size and logging.file.max-history) to do the job instead, see #1530


Added daemon set

Added feature for helm chart to include daemonset
Bumped version of helm chart
This will aid in issue #309

@richarddli  Can you pleas take a look

Thanks for working on this! On a quick glance, this looks good. The main comment I have is that we ship standard Kubernetes YAML as well (not just the Helm chart):
https://github.com/datawire/ambassador/tree/master/templates/ambassador
(In fact, most of our users just use the Kubernetes YAML and not the Helm chart). Our regression tests as well use the Kubernetes YAML in general, too. Would you be able to create the Kubernetes YAML equivalent?  This way we can do automated testing of the DaemonSet as well if necessary.
Finally, I'd love some comments (in here is fine) or documentation around your deployment model with a DaemonSet so that we could share it with other people. If you want to add to the documentation directly, you could create a section here: https://github.com/datawire/ambassador/blob/master/docs/reference/running.md.

@richarddli
I have updated documentation for daemonset scenario.
Reverted version bump.
Kubernetes YAML file for daemonset will be lot of duplication with already exisiting YAML files. It's just two lines change which i added to the documentation.
Let me know your thoughts!

Works perfectly with both helm and yaml deploys.

Thanks so much!


Multiple deployment of letta sever pointing to same db results in duplicate persona and human entries

Describe the bug
I have requirement where I need more than one letta service (server per workflow). But when I install the server, seems like duplicate data's being ingested for Human and persona blocks. May be its part of boostraping server. We can make all the name fields of entities with unique constraint, so that we will not allow any duplicate entities creation with same name.
Refer attached screenshot
Please describe your setup

[ ] How did you install letta?

I install letta using helm per workflow..but it points to same db instance

[ ] Describe your setup

Letta is deployed on k8s...
using docker  which runs letta startup scripts

Screenshots
Attached

Why do you need multiple letta servers? The service is designed to support multiple agents. There are probably conflicts between the servers since they are connecting to the same DB.

Hi Sarah,
The discussion is outlined here: GitHub Issue Comment
https://github.com/letta-ai/letta/issues/2021#issuecomment-2468817753.
A single server could suffice if the tools didn’t rely on local resources.
However, in my case, I embedded Letta alongside my service because the
tools need to operate on local resources. For example, tasks like cloning,
Docker build and deploy, and other similar use cases require local
processes. Additionally, scenarios like analytics may not necessitate
executing tools on the Letta server itself, as they depend on interacting
with local resources and processes.
Hope my understanding is clear ! And may be there is a better way to do
this .
Best regards,
_lnr
On Thu, 21 Nov 2024 at 10:24 AM, Sarah Wooders @.***>
wrote:

Why do you need multiple letta servers? The service is designed to support
multiple agents. There are probably conflicts between the servers since
they are connecting to the same DB.
—
Reply to this email directly, view it on GitHub
https://github.com/letta-ai/letta/issues/2079#issuecomment-2490077404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGPZOPKMQY7C55XBGJDSPT2BVRRDAVCNFSM6AAAAABSGCE5W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQGA3TONBQGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Woocommerce api V2?

Does your wrapper also support the V2 api, I mean WC V3?
Thanks for your awesome Laravel wrapper. It's cool 👍

You'll just need to update WOOCOMMERCE_VERSION to v2 in your configuration
// app/config/woocommerce
 'api_version' => env('WOOCOMMERCE_VERSION', 'v2'),

and it will work.
With the next version which will also support Laravel 5.5 v2  will be the default


[WIP] Use WebSockets for IPC instead of file I/O

@vladikoff
I think someone disabled Travis CI for this repo. Any thought on this ?

Never mind, force pushed and it's working now :)

This PR needs review!

Could anyone, please, review this PR ?

@Arkni - hey, I'll try to review this week. Works for you?

I mean not sure if me reviewing it matters :D Still I can provide feedback.

Sure! Any help is welcome :)
Thanks :)

Closing as PhantomJS is deprecated.


Generate a verifier.sol file for the chunked zkey

Currently, we load the zkey in chunks to ensure that we can actually fit it into memory. However, there is no verifier.sol generated. So, we either need to fork snarkjs to generate a verifier.sol from the chunked zkeys, or also output a raw zkey that corresponds to the same chunked zkey, that we can call the normal snarkjs verifier generation from.

Done with https://github.com/zk-email-verify/zk-email-verify/blob/main/dizkus-scripts/3_gen_both_zkeys.sh


Notes for spawnpoints?

So I often want to make some notes about Spawnpoint X. I.e. "Lapras spawned on Tuesday at hour 3pm" so I can check the Spawnpoint when I forgot the day or time and it's not needed to create an extra Textfile just for that^^ Would be cool!

click on stats, full stats, clickon the wanted pokemon and get a heatmap and the appearance times

Well thanks but I know that^^
1st: I don't want to search in the Stats for the pokemon that appeared there (maybe I already forgot which one it was). Would be faster to remember the spawnpoint and read the note.
2nd: That was just an example for notes :)

if you scan on different pc's, i guess thats not doable if not without a shared database?

Well that's the point. I see Pokemon X on my sisters PC and want to make a note with spawntime on my PC.

Also "Full Stats" doesn't show all found pokemon. Yesterday I scanned and found a vaporeon but it's not listed anymore..

@ultimate2106 have you fiddled with options?
try changing duration to "map lifetime"
duration is default at "last day"


Color struct and class type keywords

I think the keyword int and struct type Int32 should be colored the same way as they are one and the same. This little change does just that.

A similar feature was just merged.
Thank you for the inspiration!

You are welcome.


Update Documentation for Wiki sources

Links to code definitions within the Wiki (under classes) lead to dead pages. I'm sure that most code references do this at the moment. Pretty minor issue.

Fixed in dc9f485. Turns out Jekyll was removing the files that had a leading underscore (and all html files that are related to source files have it). This removes Jekyll and fixes the broken links.


Added a bit more clarity to selecting the correct version. Previously it...

... was possible tell what was wrong, but no what was correct!

merged this to master. Thanks!


Figure 1-2. SOA architecture. Incorrect diagram.

Figure 1-2. SOA architecture. Diagram is incorrect, service providers do not share persistent storage/relational database in the ESB pattern

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

ID: 769db633-2483-c4f5-61f7-c56ca63cee05
Version Independent ID: 315f36c3-3294-be2d-cc04-19e4d446c9c2
Content: The world is distributed
Content Source: docs/architecture/dapr-for-net-developers/the-world-is-distributed.md
Product: dotnet-architecture
GitHub Login: @robvet
Microsoft Alias: nanil

Thanks for suggestion. Will recommend removing database from diagram in upcoming v 1.1.

The document has been updated as per the suggestion. The issue can be closed now.


EVE reconfig

Description
Errors when executing the eden reconf command.
Steps to Reproduce

Standard EDEN's initialisation:

make build-tests
eden setup
eden start
eden eve onboard
eden status

Get current config:

eden reconf --get e01

Reload config:

eden reconf e01

Actual Results
$ eden reconf e01 -v debug
configName:  default
configFile:  /home/sadov/.eden/contexts/default.yml
DEBU[0000] Will use config from /home/sadov/.eden/contexts/default.yml
DEBU[0000] Try to add config from /data/tmp/eve/confs/002/eden-config.yml
DEBU[0000] bad status (400 Bad Request) in response (failed to marshal json message into protobuf: json: cannot unmarshal string into Go struct field NetworkConfig.networks.type of type config.NetworkType
)
DEBU[0000] error PUT URL : <nil>
INFO[0000] Attempt to re-establish connection (0) of (20)
DEBU[0005] bad status (400 Bad Request) in response (failed to marshal json message into protobuf: json: cannot unmarshal string into Go struct field NetworkConfig.networks.type of type config.NetworkType
)
DEBU[0005] error PUT URL : <nil>
INFO[0005] Attempt to re-establish connection (1) of (20)
DEBU[0010] bad status (400 Bad Request) in response (failed to marshal json message into protobuf: json: cannot unmarshal string into Go struct field NetworkConfig.networks.type of type config.NetworkType
)
DEBU[0010] error PUT URL : <nil>
INFO[0010] Attempt to re-establish connection (2) of (20)
...

Increasing id.version does not solve the problem.
Expected Results
Reload config without errors.
Additional Information

@sadov can we close this?

Yes -- fixed.


refactor: lowercase structure member preservesFiniteLimits

From this Zulip thread.

#2828 moves the trailing-space-stripping to a new file, which should make this easier to review.


Consider renaming/prefixing Rust imports to avoid clashes with developer-defined code

We are currently prefixing Rust functions and some variables to ensure that we don't clash with Rust code generated from the developer's Python code. We may need to do the same with our Rust imports.

Duplicate of https://github.com/demergent-labs/kybra/issues/306


fix: proper LOCAL_ONLY example

Prefab::Options.new(data_sources: LOCAL_ONLY) isn't valid at all:

data_sources isn't a valid key
LOCAL_ONLY should be a string, not a constant.

After further debugging, you can pass the following, however, you also then need to explicitly provide an API key here instead.
Prefab::Options.new(prefab_datasources: 'LOCAL_ONLY')

As a result, I believe recommending that folks use the built in ENV var of PREFAB_DATASOURCES makes the most sense.

TYSM!


feat(@kadena/react-ui): Tooltip Component

Updates the tooltip component to use react-aria and already updates the tools app.
NOTE: Design changes have been made with Isa

Somewhat of a more general question; do we expect the tooltip to close when clicking the handler, looking at storybook examples? 🤔

Somewhat of a more general question; do we expect the tooltip to close when clicking the handler, looking at storybook examples? 🤔

That is only in the controlled state. The tooltip will appear and disappear based on hover or focus by default


div inside h3

Hi,
I got the following html text:
``html

  Title

``
The img is a child of a but not the h3. I know a div in a h3 is not allowed. How can I get the h3 node anyway?
Edit:
rendering all a.Nodes also omits the h3 node and it's content.

Seems like doing doc.Find("h3") works, although it does seem like the HTML parser makes some automated corrections. Render the h3.Html() gives me  Title

.

This is the code I experimented with: https://gist.github.com/marshauf/2ac1f5b8720385d448ef
I am probably not considering something and that's why the one line works and the other doesn't


False Positive on Kotlin

When reporting a false positive please include:

The location of the dependency (Maven GAV, URL to download the dependency, etc.)
The CPE that is believed to be false positive

Please report the CPE not the CVE

Example
False positive on kotlin stdlib - reported as https://nvd.nist.gov/vuln/detail/CVE-2019-10101
It is an issue exclusive to 1.3.30 but owasp is reporting it inclusive (we are on 1.3.30).

I've tried a few kotlin libraries at 1.3.30 and I'm not seeing this issue.  Can you provide the exact library location/coordinates/GAV?

Hi Jeremy, it happens on my work project.

Apparently, we have dependency which we forced version to specific kotlin library that is influencing report.
I'm really-really sorry for the false positive issue and your time!

As an addendum: I've seen some false-positives here for 1.3.31 and 1.3.41, but finally updating to 5.1.1 has fixed them.


Use BackendStatus to show BE's infomation in show backends;

The infomation is displayed in JSON format.For example:
{"lastTabletReportTime":"2020-05-28 15:29:01"}

For #3698

Please update the doc SHOW BACKENDS.md, both in English and Chinese.

Done

The status mainly reflect BE's status, if some error happends, it should be FE's problem?Our mainly purpose is to monitoring BE's status, so maybe we can leave it to make sure that BE's status is OK?

The status mainly reflect BE's status, if some error happends, it should be FE's problem?Our mainly purpose is to monitoring BE's status, so maybe we can leave it to make sure that BE's status is OK?

I remember this PR is to solve some problems that BE cannot report successfully because of the version out of data.
If there are other problems in the reporting process, it is equivalent to this BE not reporting successfully. SO I think it should also be able to be reflected in this status field. We should focus on the final result, not the success or failure of a certain part of the entire reporting process.

The status mainly reflect BE's status, if some error happends, it should be FE's problem?Our mainly purpose is to monitoring BE's status, so maybe we can leave it to make sure that BE's status is OK?

I remember this PR is to solve some problems that BE cannot report successfully because of the version out of data.
If there are other problems in the reporting process, it is equivalent to this BE not reporting successfully. SO I think it should also be able to be reflected in this status field. We should focus on the final result, not the success or failure of a certain part of the entire reporting process.
So actually, lastTabletReportTime means lastSuccessTabletReportTime

Ok, I change the logic and rename the filed name~


build AxonFramework with Gradle

Enhancement Description
By way of experiment I started writing Gradle build scripts for Axon Framework, effectively porting the Maven pom files to Gradle.
I'm made good progress so far but there is a long road ahead. Before continuing my pursuit I'm wondering whether there is an interest in this effort from AxonIQ?
Regards,

We'll have an internal chat about it @bliessens, thanks for sharing your efforts on the matter.

So, we have had a chat about this internally @bliessens, which provides a conclusion to some extent.
We feel that this boils down to a matter of taste really. Do you want to craft (arguably ugly) XML or will you program your build file yourself? There are pros and cons to be called for both in this space, but what's most important for us on the matter is a form of consistency. Thus changing it for framework, would impose requirements for every extension right now.
We feel that it currently isn't the right moment in time to actually make that change.
Regardless I'd like to thank you for sharing that you are working on this; any insights are always much appreciated.
Obviously feel free to come with extra pointers if you feel strongly that we should move this direction, @bliessens. This freedom extends to anybody reading this issue of course. For the time being though, the issue will be closed.

I'm ok with that @smcvb. If transitioning to Gradle is not planned in any foreseeable future this should not be your focus either.


Unexpected token ] in JSON when trying to deploy to SST

I am trying to deploy a NextJs site, which works locally when running "npm run dev" and also build succeeds by running "npm run build", but fails when running "npx sst deploy".
It seems there are a few extra characters in the end of the JSON - specifically ]}
Here is the excerpt from terminal (some info obfuscated or stripped):
npx sst deploy --stage prod
SST v2.38.3

➜  App:     sst-next
   Stage:   prod
   Region:  eu-west-1
   Account:<PHONE_NUMBER>123

Next.js v14.0.4
OpenNext v2.3.1

┌─────────────────────────────────┐
│ OpenNext — Building Next.js app │
└─────────────────────────────────┘

><EMAIL_ADDRESS>build
> next build

   ▲ Next.js 14.0.4
   - Environments: .env

 ✓ Creating an optimized production build
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (5/5)
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                              Size     First Load JS
┌ λ /                                    1.22 kB         106 kB
├ ○ /_not-found                          0 B                0 B
├ λ /[slug]                             1.22 kB         106 kB
├ λ /[slug]/[type]                     1.22 kB         106 kB
└ λ /[slug]/[type]/[id]             176 B            87 kB
+ First Load JS shared by all            81.8 kB
  ├ chunks/938-97f845deaffc21a2.js       26.7 kB
  ├ chunks/fd9d1056-ea4f02c0a4383bef.js  53.3 kB
  ├ chunks/main-app-8265353934748fac.js  220 B
  └ chunks/webpack-c27cd9c8c8d6140c.js   1.64 kB

ƒ Middleware                             135 kB

○  (Static)   prerendered as static content
λ  (Dynamic)  server-rendered on demand using Node.js

┌──────────────────────────────┐
│ OpenNext — Generating bundle │
└──────────────────────────────┘

Bundling static assets...
Bundling cache assets...
undefined:1
{
"kind":"FETCH",
"data":{
"headers":{
"access-control-allow-headers":"X-Access-Token, access_token, X-Requested-With, Content-Type, Accept, Origin, Authorization",
"access-control-allow-methods":"GET, POST, PUT, DELETE, OPTIONS",
"access-control-allow-origin":"*",
"cf-cache-status":"DYNAMIC",
"cf-ray":"855d2389sasb518-OLA",
"connection":"keep-alive",
"content-encoding":"br",
"content-language":"fi",
"content-type":"application/json",
"date":"Thu, 15 Feb 2024 12:29:02 GMT",
"nel":"{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}","report-to":"{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.b.com\\/report\\/v3?s=XfFTW5szfRV%2B7%2FQzxkoiwWak32dscJmgLVLoj7Hyh0SBHED7Zrwm0f6riQoml3H4DPi1DxXzsVsVas8a73OMbrCd36QONZdwUVQXXqNBepSVI54Ri%2Fq7QQWOqqskTTg%3D%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}","server":"b","transfer-encoding":"chunked","vary":"Accept-Encoding"
},
"body":"W3sic3RhdHVzIjoiZm9yc2FsZSIU3RhbXAudWxsLCJpc...thiscontentisstripped...015RmF2b3JpdGUiOm51bGwsImlzSGlkZGVuQWQiOm51bGx9XQ==",
"status":200,
"url":"https://api.hidden.dev/rest/items/search?page=1&rows=30"},
"revalidate":31536000,
"tags":[]
}]}

SyntaxError: Unexpected token ] in JSON at position 201187
    at JSON.parse (<anonymous>)
    at file:///Users/t/.npm/_npx/5e5e2f11d04ee7cb/node_modules/open-next/dist/build.js:363:39
    at file:///Users/t/.npm/_npx/5e5e2f11d04ee7cb/node_modules/open-next/dist/build.js:651:13
    at Array.forEach (<anonymous>)
    at traverseFiles (file:///Users/t/.npm/_npx/5e5e2f11d04ee7cb/node_modules/open-next/dist/build.js:644:51)
    at createCacheAssets (file:///Users/t/.npm/_npx/5e5e2f11d04ee7cb/node_modules/open-next/dist/build.js:361:13)
    at build (file:///Users/t/.npm/_npx/5e5e2f11d04ee7cb/node_modules/open-next/dist/build.js:31:9)

We do not modify the fetch cache entry, so if the JSON is incorrect the issue is coming from next itself.
It might not appear as an issue in next because if it throws an exception while loading this cache item, it will consider that the item is not cached and refetch.
We could add a try catch block around the JSON.parse() during build to catch this error, but it won't solve the underlying issue.
Could you try with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>?

This looks like an error at build time, can you log the json data of the fetch request on the page?

@tseppl I also added some try catch blocks but it's not logging anything. Also I wonder this step only start after successfully generating static pages so I wonder where you added your try catch statements.

@Jdruwe
For me "npm run build" would not produce any errors before adding the try catch blocks and this was ultimately also the reason why I thought it was an issue with open-next. After adding try catch blocks around fetch json parse the build would finally fail with Dynamic Server Error.
I think Dynamic Server Error usually originates from trying to render the page statically but using dynamic resources such as headers, cookies, searchparams etc which are only available during client runtime.

Thanks for the response, what do you exactly mean by "After adding try catch blocks around fetch json parse". I am trying to find the correct place to add the try catch statement, I assume you added it to your own code and not the code provided by open-next?

I have to admit I cannot remember all the details anymore but try adding a try catch block around where you fetch data inside your components. Also if you try to access things like cookies etc. This way you will at least get an error displayed.

try {
  const response = await fetch('https://website');
} catch (error) {
  // TypeError: Failed to fetch
  console.log('There was an error', error);
}

I think there is some problems with consistency with this setup. So sometimes you have to delete the .next dir manually and then run build again. Some cache won't clear itself for some reason at times. To get a consistent result you can write a script that first deletes the .next dir and then starts the build.


An plugin error occurred when Intellij turned on.

2017-08-18
AM 1:52	Plugin Error
Problems found loading plugins:
The following plugins are incompatible with the current IDE build: .ignore
[Intellij information]
IntelliJ IDEA 2017.2.2
Build #IU-172.3757.52, built on August 15, 2017
Licensed to Hyunoh Ryu
Subscription is active until February 16, 2018
JRE: 1.8.0_152-release-915-b10 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

Oops Duplicate of #408


installer wasn't able to pop my browser

Guide says browser will open by itself. It didn't for me.
However when I opened myself and went to http://localhost:8888 it asked me for infura project id and I could proceed.

this was mozilla (,y default broswer) ubuntu

Could not reproduce with Firefox and Ubuntu. As a fallback for such situations we added a "wizard is ready" log message with the localhost URL so the user can open the page manually. (See issue #36)


Alternative remote caching hosts

Describe the feature you'd like to request
Turborepo offers remote caching, allowing to share cached artifacts with team members.
Currently two remote caches are available:

Remote cache hosted by Vercel
Custom remote cache implemented by the end-user, which mimics the Vercel API

Some users might want to store their remote caches in other object-store-like services, like:

AWS S3 (or any S3-compatible stored like MinIO)
Google Cloud Storage
Azure Blob Storage
OpenStack Swift
Anything else that can store files (HDFS, NFS, etc.)

This can be for several reasons. Here are three I can think about:

I am not using Vercel with my team, and I don't plan to in the forseeable future. I don't want to use yet another cloud provider
I do not want to share my build artifacts on a product that I can't control the security on (aka I want to manage my S3 security)
I need to store my artifacts on-prem (aka I want to store this in my own datacenter)

Describe the solution you'd like
Turborepo would offer a configuration option to choose between supported remote cache stores. Users would need to configure access parameters and credentials in the configuration file of Turborepo in their monorepo.
In this case, Turborepo would write and reads its cache from the external cache host configured (S3 bucket for example).
Implicit login would need to be supported too: in the case of S3, Turborepo should be able to use the aws CLI to authenticate its calls directly, without needing an API token / secret key. This is usually supported by the Cloud provider's SDK.
Describe alternatives you've considered
The problem with this is that Turborepo will need to implement code for each supported caching provider. This can lead to a lot of code, and possibly go outside of the scope of the project.
Here are two other solutions I can think about:
A separate proxy for each wanted cache host
Since Turborepo already supports custom HTTP endpoints (that mimic the Vercel API), we could just develop a proxy that will act as the Vercel API, and will just forward operations to the end cache provider (S3, Google Cloud Storage, etc.)
This has the advantage of not bloating the Turborepo main codebase and binary, and allowing users with exotic requirements to push a PR to Turobrepo for a very specific use-case (or forking Turborepo as a last resort).
The downside is that the proxy will have to be hosted somewhere, and that each user will need to host their own version of the proxy.
A plugin-based approach
Another way of doing this would be to delegate the communication with the remote cache to a second binary that lives in the same machine as Turborepo. Turborepo would be configured to delegate all operations to this binary.
This is similar to what Docker does with authentication to alternative registries. Here are examples of documentation: AWS ECR, Google Cloud Container Registry (their standalone helper is the closest I could find to what I'm suggesting)
Turborepo would fork a process of the provider's plugin (aka adapter), and would forward the instructions to it directly.
Again, this has the advantage of not bloating Turborepo's code, and allow for custom implementations without PRing or forking Turborepo.
Terraform also has a plugin based approach, but I'm not sure how they handle it. The Docker model will probably be easier to implement.

Note that it's not all or nothing:
Implementing a few providers does not mean that using a plugin-based or a proxy-based approach is not possible.
Turborepo could implement the most needed providers, and leave the more exotic ones to a plugin-based or proxy-based approach. This allows for most users to only depend on Turborepo, and a few to need an additional moving part.
S3 would probably be the best candidate for an in-tree provider, for two reasons:

AWS is the most used Cloud provider
The S3 API is a standard that has been re-used by multiple late-comers (MinIO, BackBlaze B2, CloudFlare R2, etc.)

The rest can be implemented by plugins or proxies.
This means that there will be some triaging involved here, as repeated requests for additional in-tree providers will likely come. A fixed list of supported providers with a clear statement that no additional providers will be added to the main repo could reduce this a bit.
I'd recommend a plugin-based approach for the less-used providers, as it is quite simple to install (just have a binary with the right name in your path and you're good to go).

I have written my own remote cache server for turbo yesterday for Google Cloud Storage

I'm also happy to help with the implementation once the correct solution has been established with the core team. I don't have a lot of experience with Go but that will make for some nice practice!

Yeah, that's a really good idea.
I am also happy to help with the implementation.

One thing the project manager should consider:
Adding different storage providers will also increase the size of the binary.

It would be great if there will be an option for a Node custom storage provider. This could be file/files that expose the correct api.

I  have talked my work and I am allowed to open-source my proof of concept server which is compatible with the remote cache of Turborepo and supports Google Cloud Storage, and Amazon S3. Azure Storage is also possible but would need someone to with a such blob storage to test it out.

@weyert when will you open-source it?

Please find it here: https://github.com/Tapico/tapico-turborepo-remote-cache :)

If this support will be added to turborepo you also need to think about companies that are for all kind of compliance reasons can not just directly connect to a cloud storage provider or might need to access via a VPN and/or IAP. For example, at work I am unable to directly access cloud storage and write to it from my computer system.
One of the reasons that I am worked on my above mentioned project to ease this problem. It's probably a good start for people that are concerned about not wanting to store build artefacts on Vercel. The project comes with binaries for amd64, windows, and arm and has docker images pre-build that can be used. I hope to find some free time to make an example how it can be ran via Cloud Run on Google Cloud.


Missing Vietnamese text when output

Hi,
I was exported  a demo excel sheet from ZDEMO_EXCEL1 with Vietnamese's character like 'ắ' or 'ớ'.
But character was missing when output.
How to solve this problem?
Please suggest me,
Thank you.
Code in program:

Output:

Hi @spacy0212
you can comment these lines in ZCL_EXCEL_WRITER_2007->RENDER_XML_DOCUMENT
`  TRY.
CALL METHOD lo_ostream->('SKIP_NON_XML_CHARACTERS')
EXPORTING
is_skipping = abap_true.
CATCH cx_sy_dyn_call_illegal_method.
ENDTRY.`
see #298

Analysis: depending on kernel and notes installed in the SAP system, and depending on abap2xlsx works with fix 298 or not (respectively calling SKIP_NON_XML_CHARACTERS or not), there will be the following effects if Vietnamese text (and any other "non-XML" character) is written to the Excel file. In most (?) of client systems, the text will not be output, so I would propose that SKIP_NON_XML_CHARACTERS is called only if a non-XML character is not serialized correctly, I propose a PR to test that.

SKIP_NON_XML_CHARACTERS available (note 1750204) (always "yes" if abap/kernel > 7.40)
Kernel as per note 2220720 (always "yes" if kernel > 7.47)
Vietnamese text output with abap2xlsx before fix 298
Vietnamese text output with abap2xlsx after fix 298

No
No
XLSX file corrupted, Excel can't open it
XLSX file corrupted, Excel can't open it

No
Yes
Vietnamese text is output
XLSX file corrupted, Excel can't open it

Yes
No
XLSX file corrupted, Excel can't open it
Vietnamese text is not output

Yes
Yes
Vietnamese text is output
Vietnamese text is not output

Concerned skipped "non-XML" characters are those encoded in ABAP character variables with internal 2-byte values 0x0000 to 0x0008, 0x000B, 0x000C and 0x0800 to 0xDFFF (1). Unicode characters U+010000 to U+1FFFFF (Emoji, etc.) are encoded in ABAP characters variables as 2 "surrogate" characters (low 0xD800-0xDBFF and high 0xDC00-0xDFFF). Examples:

Vietnamese characters ớ and ắ are respectively Unicode U+1EDB and U+1EAF, encoded 0x1EDB and 0x1EAF.
Emoji characters 🦀🤙🌎🌍🌏 (#688) are respectively Unicode U+1F980, U+1F919, U+1F30E, U+1F30D and U+1F30F, encoded 0xD83E 0xDD80, 0xD83E 0xDD19, 0xD83C 0xDF0E, 0xD83C 0xDF0D and 0xD83C 0xDF0F.
Etc.

NB (1): I checked which "non-XML" characters are skipped by SKIP_NON_XML_CHARACTERS using this program https://gist.github.com/sandraros/ed2808ce00af79e0762b08d9f4514942#file-gistfile1-txt; they are also mentioned in the note 1750204 which introduces SKIP_NON_XML_CHARACTERS.

Tks, issue has been resolved.


Prevent eternal loop by ensuring that no libxml errors with level [LIBXML_ERR_FATAL]  have occurred

Hi,
I was facing some instability issues regarding invalid XML documents. I would expect an exception but instead the Reader will (in some cases) attempt to keep parsing the same node eternally. I fixed this by adding a validation step.  The XMLReader::isValid may not be backward compatible so I made the validation step optional. Altough I did not validate this thouroughly it seems like this method will only work when the something like a XSD, DTD etc is in place.  Either way. The feature is optional, so this change should not be problematic.
Update:
The validation did not fix all scenario's. The new solution does. Basically we now check if libxml has fatal errors on each iteration. I did not implement this as a optional feature since it ensures that your application will not crash when invalid XML is provided.

Hello :-),
First, can you give us an example of your XML in order to reproduce your issue please?
Second, do you have any idea of the impact on performances?
Third, is it possible to validate the whole document once instead of each node?

Damn... lost my work in progress comment.
@Hywan One of the key concepts of the XMLReader/XMLWriter is that they can operate on streams. So if validation is possible for the whole document, I don't think it would be desired. I'm also not super concerned about speed if it's an optional feature.
@DaanBiesterbos
A few points:

@Hywan is right that this change needs a test. A unittest that checks both the valid and invalid case.
You can automatically fix all CS-related issues by running : ./bin/sabre-cs-fixer fix .
The docblocks should be expanded a bit to explain exactly what the feature does, and how to use it.
Don't return $this from the setter.

Lastly... is it possible to emit a more useful exception? It would be great if we can tell the user why their document isn't valid... i assume that XMLReader has a way to access this information?

@Hywan   @evert    Hi guys. I will prepare something to reproduce the problem and improve the commit as described above. As evert pointed out the isValid method will always only check the current node. But there is also a validation to check if the XML is valid according to the schema. This validation does work for the entire tree. This validation detects nodes that violate the schema but does completely ignore syntax errors.
I'll come back on this later. One more thing though.
I executed the the ./bin/sabre-cs-fixer fix command. But a LogicException was thrown in ./vendor/symfony/finder/Symfony/Component/Finder/Finder.php on line 698.  Message: "You must call one of in() or append() methods before iterating over a Finder."
$config->getDir() returns null in "/home/daan/Projecten/SabreXmlReader/sabre-xml/vendor/fabpot/php-cs-fixer/Symfony/CS/Fixer.php" on line 137.
It seems like adding '$out->setDir(DIR . '/../lib');' to  "/home/daan/Projecten/SabreXmlReader/sabre-xml/vendor/sabre/cs/bin/php-cs-fixer-config.php" solved the problem locally. I can now execute the command. Not sure what is causing this though. I tried downgrading to symfony 2.6.7, but that did not solve it.

Did you do sabre-cs-fixer fix . ? the last . is important =)

@evert  Ah. You are right. Missed the dot. :-)

To reproduce the issue you can run the unit test and omit the solution :) All scenario's that should fail because of missing tags or malformed XML will lead to an eternal loop.

@evert   Hi Evert. How do you feel about the provided solution? Were you able to reproduce the problem?

Hi Daan,
The reason I have not really gotten to it yet, is because this is a relatively large diff, for a relatively small change. There's a lot of unrelated changes in the source, and things could probably get simplified a bit.
Will make a few comments in-line.

The biggest thing I would want to ask is.. how small can you make this unittest? Right now there's a ton of assertions, and a lot of other stuff. Could you create a very minimal schema?

Hi @DaanBiesterbos ,
Didn't hear back in a while, and then another related issue popped up in #45.
In response to that, I created a new patch that's similar to yours, but much simpler.
Tagging this today as 1.1.0.


Bug in timepicker - cannot edit time input field in Portal mode

When i am using TimePicker plugin inside DatePicker that is in Portal mode, the hour and minute cannot be edited by clicking the textfield and type it, it can only be changed by clicking the up/down arrow.
I expected the input field to be working in both normal and portal modes. Thanks for your support.

I can't reproduce the bug you mentioned.
Please see this sandbox and let me know if it works or not.
https://codesandbox.io/s/timepicker-3c2bik


Loading Production Data in Documentation Examples

A minor question about the documentation for bluebonnet.flow:
In the documentation at: https://bluebonnet.readthedocs.io/en/latest/forecast_varying.html, in the "Fit wells" section, the production data is loaded using:
prod_file = f"https://raw.githubusercontent.com/frank1010111/bluebonnet/main/data/dataset_1_well_{well_number}.csv"
But the well data is loaded using:
well_file = f"../data/WellData_{well_number}.csv"
Would it be more consistent if the path to the production file also referred to a file in the local data folder, e.g. with
prod_file = f"../data/dataset_1_well_{well_number}.csv"?
This is part of the reviewing process for JOSS: https://github.com/openjournals/joss-reviews/issues/5255

So that people can run the tutorial without cloning or downloading the repository, I plan to standardize it on the first format.

That makes sense. Thanks.


FlashAttention

End goal is to automatically discover flash attention, but lots of work still needs to be done on an IR. For now lets hand code a kernel and find-and-replace it


fix audio voice stealing

When a sound is finished, a new music playback didn't remove entry in sound/source maps. In this case, any change using the soundID (volume, pan, pitch) applies to the music instead.
I included a test case in order to validate the issue, let me know if you don't want this test in libgdx repo or if you prefer that i move it somewhere else...

It took me a while to understand the problem here; the IDs in the current libGDX code can change while multiple sounds or music are playing, which makes changes to other audio streams unpredictable without this PR? Is that right? I like having the test here; I think the audio part of libGDX doesn't see much attention, so a test to verify behavior is good. The original code does look buggy, but I don't really know what I'm looking at.
My vote is to merge after mgsx has had a chance to look at this again and maybe think of other parts of code that might be involved. I'm slightly concerned about doing anything hastily with the audio, because it doesn't get tested by a lot of games.

I double checked, that was the only place where maps was not properly updated.
Quick explanation (i'll try my best):

idleSources, sourceToSoundId and soundIdToSource form a kind of pool.
sourceToSoundId and soundIdToSource are only used by Sound.
idleSources are used by Sound, Music, and AudioDevice.
Source can be explicitly freed (stop sound, dispose sound, stop music, stop device, etc): properly freed in all these cases.
Source can be implicitly freed when obtaining a source (that was the buggy case). It scans the pool looking for a stopped source that can be used/reused. But it didn't update the maps when obtaining a source for music.


feat(perception): add support of multiple camera frame IDs

Category

[x] Perception

What

Related to https://github.com/tier4/autoware_perception_evaluation/issues/47

Add support of multiple camera frame IDs.

evaluate multiple camera frameIDs
visualize results in each camera frameID

NOTE For 3D perception and sensing tasks only support single frame ID.
# For 3D evaluation
config3d = PerceptionEvaluationConfig(
    ...
    frame_id="base_link",  # NOTE: forbitten to specify multiple frameIDs
    ...
)

# For 2D evaluation
config2d = PerceptionEvaluationConfig(
    ...
    frame_id=["cam_front", "cam_back"],  # NOTE: allow to specify one or more frameIDs
    ...
)

Type of change

[x] New feature
[x] Update test
[x] Update document

Test performed

[ ] test.sensing_lsim

[ ] test.perception_lsim

Reference

Notes for reviewer

yolox launch was not designed to launch multiple cameras, so I use yolo launch to check


Support $this->attributes in Model

Example:
ERROR: MixedArrayAssignment - app/Models/Acme.php:110:9 - Cannot access array value on mixed variable $this->attributes['user_id'] (see https://psalm.dev/117)
        $this->attributes['user_id'] = $user_id;

I just tested on the following code:
class User extends \Illuminate\Database\Eloquent\Model
      {
        public function testMethod(): void
        {
            $this->attributes['user_id'] = 1;
        }
      }

and there is no issue anymore (plugin v2.5), Laravel 9.47
I'm closing the issue.


Add ability to specify configuration for build.

This is a great plugin that I look forward to trying out. Thanks for creating this!
It would be very useful for the build command to allow specifying the configuration (Debug, Release).
In general, it would be nice if all the commands wrapping dotnet CLI had an additional_args (anybody have a better name?) parameter to specify additional arguments for the commands, e.g. --no-restore for build.

This has been mentioned a few times already so I figured ill make a general issue for it #87. Its a great suggestion and something I want to make possible. Please feel free to share your thoughts on the issue below

#87

Just to clarify for the terminal section of your config this is already possible. But yes I would like to expose it in a better more global way
local dotnet = require("easy-dotnet")
dotnet.setup({
  test_runner = {
    vstest_path = "C:/Program Files/dotnet/sdk/8.0.108/vstest.console.dll"
  },
  terminal = function(path, action)
    local commands = {
      run = function()
        return "dotnet run --project " .. path .. " --no-restore"
      end,
      test = function()
        return "dotnet test " .. path
      end,
      restore = function()
        return "dotnet restore " .. path
      end,
      build = function()
        return "dotnet build " .. path
      end
    }
    local command = commands[action]() .. "\r"
    require("toggleterm").exec(command, nil, nil, nil, "float")

I am closing this issue since #87 covers this.

This is now supported using Dotnet build release #122


Secrets polls only work on creation, fails to sync, hangs on starting poller

We are running clusters on EKS 1.16, 1.17, 1.18. Encountered issue below:
The secrets gets pulled from SSM(Parameter Store) only at creation time, and subsequent sync just hangs on step
{"level":30,"time":1608285272199,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting poller for test/global-credentials"}
If left unintended, the pod just logs more starting poller log like above without any error
I have attached the role with SSM permission directly on to the k8s node instance.
apiVersion: 'kubernetes-client.io/v1'
kind: ExternalSecret
metadata:
  namespace: test
  name: test-credentials
spec:
  backendType: systemManager
  data:
    - key: /releng/test/test_credentials_formatted
      name: credentials

$ $k get externalsecrets -n test
NAME                LAST SYNC   STATUS    AGE
test-credentials   19m         SUCCESS   19m

Full log from KES pod:
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>start /app
> ./bin/daemon.js

{"level":30,"time":1608283897656,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"loading kube specs"}
{"level":30,"time":1608283898757,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"successfully loaded kube specs"}
{"level":30,"time":1608283898758,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"updating CRD"}
{"level":30,"time":1608283898758,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"Upserting custom resource externalsecrets.kubernetes-client.io"}
{"level":30,"time":1608283898809,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"successfully updated CRD"}
{"level":30,"time":1608283898811,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting app"}
Fri, 18 Dec 2020 09:31:38 GMT kubernetes-client deprecated .getStream use .getObjectStream, see https://github.com/godaddy/kubernetes-client/blob/master/merging-with-kubernetes.md at lib/external-secret.js:40:10
{"level":30,"time":1608283898814,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"successfully started app"}
{"level":30,"time":1608283898814,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"MetricsServer listening on port 3001"}
{"level":30,"time":1608283898855,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting poller for test/global-credentials"}
{"level":30,"time":1608284208934,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting poller for test/global-credentials"}
{"level":30,"time":1608285269905,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting poller for test/global-credentials"}
{"level":30,"time":1608285269919,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"running poll on the secret test/global-credentials"}
{"level":30,"time":1608285269931,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"fetching secret property /releng/test/test_credentials_formatted with role: pods role"}
{"level":30,"time":1608285272168,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"upserting secret test/global-credentials"}
{"level":30,"time":1608285272199,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"stopping poller for test/global-credentials"}
{"level":30,"time":1608285272199,"pid":18,"hostname":"kes-kubernetes-external-secrets-c4d65f5c4-h54nv","msg":"starting poller for test/global-credentials"}

Not sure I'm following, logs look correct. Each resource always has a poller running. Poller will restart whenever there's a change to the related resource. You can enable more verbose logging if you want. Notice the different message running poll where the poll is actually running.

Please provide more details on your configuration if you still have problems.

Please provide more details on your configuration if you still have problems.

My mistake, the DISABLE_POLLING option was turned on
env:
    DISABLE_POLLING: true

My mistake, the DISABLE_POLLING option was turned on
env:
    DISABLE_POLLING: true


Continue to see Login button after successful authentication

I was able to successfully authenticate using the "Login" button - however this application re-directs back to the login page after successful authentication.

This works after following instructions on the login page.


Synthesis failed for java-securitycenter-settings

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

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

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 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-05 21:33:40 [INFO] Running synthtool
2020-05-05 21:33:40 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:33:40,374 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-05 21:33:40,505 synthtool > Ensuring dependencies.
2020-05-05 21:33:40,517 synthtool > Cloning googleapis.
2020-05-05 21:33:40,518 synthtool > Using precloned repo /tmpfs/tmp/tmpej9unk7_/googleapis
2020-05-05 21:33:40,522 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-05 21:33:40,632 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/b049ca7315c9014a9dd0c4ca136e449b/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpej9unk7_/googleapis/hs_err_pid27383.log

2020-05-05 21:33:40,633 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:33:40 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Switched to branch 'autosynth-self'
Note: checking out '1cb9d25ce87ee4e73cda81da93f1f0f95cca4e48'.

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at ab88356 fix: make .kokoro-autosynth executable (#522)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at a3a0bf0f BREAKING_CHANGE: Removing TimeSeriesQueryLanguageCondition as an alert condition type. The condition type is unsupported and unused. It was originally added for the Monitoring Query Language Alpha feature. refactor!: Drop support for TimeSeriesQueryLanguageCondition as an alert condition type.
Switched to a new branch 'autosynth-43'
2020-05-05 21:33:40 [INFO] Running synthtool
2020-05-05 21:33:40 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:33:40,928 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-43
nothing to commit, working tree clean
2020-05-05 21:33:41,063 synthtool > Ensuring dependencies.
2020-05-05 21:33:41,073 synthtool > Cloning googleapis.
2020-05-05 21:33:41,074 synthtool > Using precloned repo /tmpfs/tmp/tmpej9unk7_/googleapis
2020-05-05 21:33:41,079 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-05 21:33:41,191 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/b049ca7315c9014a9dd0c4ca136e449b/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpej9unk7_/googleapis/hs_err_pid27419.log

2020-05-05 21:33:41,192 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:33:41 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, 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-securitycenter-settings. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpszwsqumc/googleapis'...
Cloning into '/tmpfs/tmp/tmpszwsqumc/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '1cb9d25ce87ee4e73cda81da93f1f0f95cca4e48'.

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

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 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-07 07:02:51 [INFO] Running synthtool
2020-05-07 07:02:51 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:51,892 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-07 07:02:52,030 synthtool > Ensuring dependencies.
2020-05-07 07:02:52,041 synthtool > Cloning googleapis.
2020-05-07 07:02:52,042 synthtool > Using precloned repo /tmpfs/tmp/tmpszwsqumc/googleapis
2020-05-07 07:02:52,046 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-07 07:02:52,156 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/44478a2453ade9111b501e4812a98e50/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpszwsqumc/googleapis/hs_err_pid20438.log

2020-05-07 07:02:52,157 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-07 07:02:52 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Switched to branch 'autosynth-self'
Note: checking out '1cb9d25ce87ee4e73cda81da93f1f0f95cca4e48'.

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at be74d3e build: do not fail builds on codecov errors (#528)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at 2fc2caaa chore: enable gapic v2 and proto annotation for bigquery/storage/v1beta2 API.
Switched to a new branch 'autosynth-51'
2020-05-07 07:02:52 [INFO] Running synthtool
2020-05-07 07:02:52 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:52,462 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-51
nothing to commit, working tree clean
2020-05-07 07:02:52,591 synthtool > Ensuring dependencies.
2020-05-07 07:02:52,603 synthtool > Cloning googleapis.
2020-05-07 07:02:52,604 synthtool > Using precloned repo /tmpfs/tmp/tmpszwsqumc/googleapis
2020-05-07 07:02:52,608 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-07 07:02:52,718 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/44478a2453ade9111b501e4812a98e50/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpszwsqumc/googleapis/hs_err_pid20473.log

2020-05-07 07:02:52,719 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-07 07:02:52 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, 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-securitycenter-settings. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpqwzkxie2/googleapis'...
Cloning into '/tmpfs/tmp/tmpqwzkxie2/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '1cb9d25ce87ee4e73cda81da93f1f0f95cca4e48'.

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

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 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-08 03:28:45 [INFO] Running synthtool
2020-05-08 03:28:45 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:28:46,064 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-08 03:28:46,207 synthtool > Ensuring dependencies.
2020-05-08 03:28:46,217 synthtool > Cloning googleapis.
2020-05-08 03:28:46,218 synthtool > Using precloned repo /tmpfs/tmp/tmpqwzkxie2/googleapis
2020-05-08 03:28:46,222 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-08 03:28:46,332 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/fdeabc9a6200915134058fb7280b91f1/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpqwzkxie2/googleapis/hs_err_pid30053.log

2020-05-08 03:28:46,333 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:28:46 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Switched to branch 'autosynth-self'
Note: checking out '1cb9d25ce87ee4e73cda81da93f1f0f95cca4e48'.

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 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 4674113 build: use Bazel 3.0.0 for autosynth builds (#529)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at 83816bb3 Add kokoro-specific .bazelrc file with arguments specific only for kokoro environments. This is to fix autosynth builds when it tries building older commits.
Switched to a new branch 'autosynth-56'
2020-05-08 03:28:46 [INFO] Running synthtool
2020-05-08 03:28:46 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:28:46,657 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-56
nothing to commit, working tree clean
2020-05-08 03:28:46,800 synthtool > Ensuring dependencies.
2020-05-08 03:28:46,811 synthtool > Cloning googleapis.
2020-05-08 03:28:46,812 synthtool > Using precloned repo /tmpfs/tmp/tmpqwzkxie2/googleapis
2020-05-08 03:28:46,816 synthtool > Generating code for: //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java.
2020-05-08 03:28:46,926 synthtool > Failed executing bazel build //google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/fdeabc9a6200915134058fb7280b91f1/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpqwzkxie2/googleapis/hs_err_pid30088.log

2020-05-08 03:28:46,927 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 31, in <module>
    bazel_target=f'//google/cloud/securitycenter/settings/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/settings/v1beta1:google-cloud-securitycenter-settings-v1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:28:46 [ERROR] Synthesis failed
HEAD is now at 1cb9d25 feat(v1beta1)!: remove some resource name builders (#44)
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, 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.


Try to diagnose "cannot find type SourceFile" errors better

Cargo's logic for what cfg get passed to the build script build, what to the library build, and what to the documentation build is apparently super subtle. See the discussion under https://github.com/rust-lang/docs.rs/issues/1580.

The cfg in this PR on the compile_error! is derived from:
https://github.com/dtolnay/proc-macro2/blob/3ff70daead32a9b485eea0c4d3719aff04117ab2/build.rs#L107-L109
and:
https://github.com/dtolnay/proc-macro2/blob/3ff70daead32a9b485eea0c4d3719aff04117ab2/build.rs#L115-L117
which means:
all(procmacro2_semver_exempt, wrap_proc_macro, not(super_unstable))

= semver_exempt && wrap_proc_macro && !super_unstable

= semver_exempt && (nightly || !semver_exempt) && !(semver_exempt && nightly)

= true && (nightly || !true) && !(true && nightly) || false && (nightly || !false) && !(false && nightly)

= true && (nightly || false) && !nightly || false

= nightly && !nightly

= false


win: replace alloca() with stack-based array

required_vars_value_len has a fixed number of elements. There is no
need to use alloca() to allocate it.
Refs: https://github.com/libuv/libuv/pull/2781
CI: https://ci.nodejs.org/job/libuv-test-commit/1844/

Landed in https://github.com/libuv/libuv/commit/3e5d26144085bd709a0de24dd744bee8142bae5f. Thanks!


[e2e]: generic workflow_dispatch main tagname slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4663227383
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.tagname.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.tagname.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Apr 11 02:32:17 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4664676402
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.tagname.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.tagname.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Apr 11 07:15:59 UTC 2023
Tests are passing now. Closing this issue.