text:
🛑 orkut is down

In 9a43280, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 1003 ms

Resolved: orkut is back up in d97528f.


text:
🛑 ojolink is down

In 1cf62bf, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 505 ms

Resolved: Ojolink is back up in 396ae4b.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 ojolink is down

In 66a36cc, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 386 ms

Resolved: Ojolink is back up in 3d079c2.


text:
🛑 benjohnson is down

In 43accde, benjohnson (benjohnson.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: benjohnson is back up in 0c8051c.


text:
🛑 orkut is down

In ee11f33, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 823 ms

Resolved: orkut is back up in b648595.


text:
🛑 orkut is down

In 481620b, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 1b515e8.


text:
🛑 ojolink is down

In 0725239, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in d3590a4.


text:
🛑 ojolink is down

In 5389316, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in c2c870a.


text:
🛑 ojolink is down

In 1b7d22e, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 52de93a.


text:
🛑 ojolink is down

In f2be55a, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in c080b80.


text:
🛑 ojolink is down

In 06033f8, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 50addec.


text:
🛑 ojolink is down

In af33c95, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 056cd91.


text:
🛑 orkut is down

In 935f5a9, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 79212e3.


text:
🛑 ojolink is down

In ac5090d, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 25c355b after 10 minutes.


text:
🛑 youjizz is down

In 90c5ae1, youjizz (youjizz.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: youjizz is back up in d689913 after 27 minutes.


text:
🛑 hcr is down

In ca65764, hcr (hcr.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hcr is back up in dfd2fb5 after .


text:
🛑 youjizz is down

In 0c2543f, youjizz (youjizz.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: youjizz is back up in 85e69ad after 17 minutes.


text:
🛑 carlinha is down

In 396a85f, carlinha (carlinha.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: carlinha is back up in e9ec28b after 2 hours, 59 minutes.


text:
🛑 inkcityusa is down

In f6a0908, inkcityusa (inkcityusa.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: inkcityusa is back up in 86dd029 after 13 hours, 48 minutes.


text:
🛑 uzboys is down

In 8f836f4, uzboys (uzboys.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: uzboys is back up in 221483f after 9 hours, 25 minutes.


text:
🛑 ojolink is down

In 2e2ce57, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 5c3b749 after 13 minutes.


text:
🛑 rapishare is down

In ad99f3d, rapishare (rapishare.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rapishare is back up in 9983a36 after 3 hours, 6 minutes.


text:
🛑 ojolink is down

In 7b4d945, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 7872d49 after 37 minutes.


text:
🛑 ojolink is down

In 1ff7d05, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in d4095cf after 10 minutes.


text:
🛑 ojolink is down

In 2697bd9, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 5c9b25d after 9 minutes.


text:
🛑 orkut is down

In 534c092, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in e88e0bc after 13 minutes.


text:
🛑 orkut is down

In 6730694, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in d6d56e4 after 10 minutes.


text:
🛑 torrentzap is down

In 2d4acad, torrentzap (torrentzap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: torrentzap is back up in 0451a9c after 4 hours, 38 minutes.


text:
🛑 orkut is down

In 8692e1e, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in e3e2efc after 10 minutes.


text:
🛑 orkut is down

In 4d6c661, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 58e8ce8 after 8 minutes.


text:
🛑 orkut is down

In c215ab0, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 5229876 after 8 minutes.


text:
🛑 orkut is down

In f5c7b97, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 740bd79 after 46 minutes.


text:
applet.program.ice40_sram: Rewrite to use the SPIMaster applet as base

Signed-off-by: Sylvain Munaut tnt@246tNt.com

Thanks a lot!

source: gharchive/pull-request

authors: smunaut whitequark

repo: GlasgowEmbedded/Glasgow


text:
Fix for Issue #146 per my discussion with avanderhoorn

Ironically, I was not able to immediately reproduce a scenario where multiple instances of the IAuthorizationFilter are returned in the sample project.  However, I was able to test the change against my original project and it started working.
PS: this is my first pull request. I'd welcome any guidance if I messed something up, like i.e. is the merge operation from my local fixes branch need to propagate all the way to my forked repo?

@rroman81 huge thanks for the pull request. Will take a look at it over the next couple of days and try pulling it in.

repo: Glimpse/Glimpse

license_source: bigquery


text:
transports can't be converted to a sequence (JS error if there is already an enrollment)

I cannot have more than 1 fido2 key enrolled in Casa for the same user. The first enrollment succeeds but subsequent attempts throw error.
It does not matter which key I enroll first. Or if the browser session is fresh. Actually the error is shown even if I don't plug a key into the USB port.
The error is thrown in the javascript call webauthn.createCredential(request) see:

transports property is null in excludeCredentials.
In fido2 impl of CE 4.1 it was possible to enroll n fido2 keys.

Yes, transport null value should be excluded
Than you for hint

Fixed


text:
Error while trying to run the daemon

Hello! Just found out about this util after using the goxlr script from the other repo for a long time, this is awesome and thanks for the work.
Now I was able to compile the daemon and actually was able to setup everything, which seemed to be working but today I restarted the PC and when trying to open the daemon to make some changes I get the following message.
20:15:22 [INFO] Starting 8 workers
20:15:22 [INFO] Started GoXLR configuration interface at http://127.0.0.1:14564/
20:15:22 [INFO] Tokio runtime found; starting in existing Tokio runtime
20:15:24 [INFO] Connected to possible GoXLR device at Bus 001 Device 010: ID 1220:8fe4
20:15:24 [INFO] Configuring GoXLR Mini, Profile: Go XLR Linux, Mic Profile: Rode Podmic
thread 'tokio-runtime-worker' panicked at 'insertion index (is 2) should be <= len (is 1)', library/alloc/src/vec/mod.rs:1347:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This is the output with the backtrace enabled as suggested
RUST_BACKTRACE=1 goxlr-daemon                                                                                ~
20:17:53 [INFO] Starting 8 workers
20:17:53 [INFO] Started GoXLR configuration interface at http://127.0.0.1:14564/
20:17:53 [INFO] Tokio runtime found; starting in existing Tokio runtime
20:17:54 [INFO] Connected to possible GoXLR device at Bus 001 Device 010: ID 1220:8fe4
20:17:54 [INFO] Configuring GoXLR Mini, Profile: Go XLR Linux, Mic Profile: Rode Podmic
thread 'tokio-runtime-worker' panicked at 'insertion index (is 2) should be <= len (is 1)', library/alloc/src/vec/mod.rs:1347:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/panicking.rs:142:14
   2: alloc::vec::Vec<T,A>::insert::assert_failed
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/alloc/src/vec/mod.rs:1347:13
   3: alloc::vec::Vec<T,A>::insert
   4: goxlr_profile_loader::profile::ProfileSettings::load
   5: goxlr_profile_loader::profile::Profile::load
   6: goxlr_daemon::profile::ProfileAdapter::from_named
   7: goxlr_daemon::profile::ProfileAdapter::from_named_or_default
   8: goxlr_daemon::device::Device<T>::new
   9: goxlr_daemon::primary_worker::handle_changes::{{closure}}
  10: tokio::runtime::task::core::CoreStage<T>::poll
  11: tokio::runtime::task::harness::Harness<T,S>::poll
  12: std::thread::local::LocalKey<T>::with
  13: tokio::runtime::thread_pool::worker::Context::run_task
  14: tokio::runtime::thread_pool::worker::Context::run
  15: tokio::macros::scoped_tls::ScopedKey<T>::set
  16: tokio::runtime::thread_pool::worker::run
  17: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  18: tokio::runtime::task::harness::Harness<T,S>::poll
  19: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Let me know if you also need the backtrace full output, thanks again!
Edit:
Forgot to mention the UI only displays this when trying to connect.

Hi, do you have the ability to compile and test this with the dev-0.4.0 branch? I've made some fixes to profile loading which may address this.
Thanks

Perfect, and No problem! I'll look into getting those fixes into main soon, just have one more bug to fix :)

authors: FrostyCoolSlug jlimas

repo: GoXLR-on-Linux/goxlr-utility


text:
Add support for focus awareness

https://developer.oculus.com/documentation/native/android/mobile-overlays/

As mentioned in PR #98, the remaining task involves adding an export option for focus awareness support to the Godot engine.


text:
Update project versions.

Update gradle version to latest and greatest.
Update SDK version.
Update library versions.
Remove redundant minSdk version number from AndroidManifest.xml.
Add .gitignore file.

Unfortunately, we do not merge PR into this repository, please see how to contribute:
https://github.com/GoogleChrome/custom-tabs-client/blob/master/CONTRIBUTING.md

authors: IgorGanapolsky pasko

repo: GoogleChrome/custom-tabs-client


text:
Multiple examples on https://try-puppeteer.appspot.com/ no longer work

'screenshot-fullpage.js' => 'ReferenceError: require is not defined'
proxy.js => SyntaxError: Unexpected token }
search.js => Error: No node found for selector: #searchbox input

Maybe you should report that here https://github.com/ebidel/try-puppeteer ?

https://github.com/ebidel/try-puppeteer/issues/3

authors: kblok selckin

repo: GoogleChrome/puppeteer


text:
add new site

add new site

I'm still studying, please help

authors: Arumankumang nibunasah

repo: GoogleChrome/related-website-sets


text:
Author migration guide for sw-framework/goog

Library Affected:
sw-framework
Browser & Platform:
All browsers
Issue or Feature Request Description:
Let's write a guide for folks already using sw-precache and sw-toolbox to help them transition their existing code to the newer sw-framework work (I imagine this will primarily be through the higher level library @gauntface has been working on).

@jpmedley Does it make sense for us to track the docs work for the libraries via this issue tracker or would you prefer for them to live in Web Fundamentals? (I'm still trying to figure out the balance of where guides should live - in-repo vs. WF)

Doc is here: https://docs.google.com/document/d/1qN3dHKkTHG-jWjWTwNzIN7NhVzd555R6FGa3AqRya_c/edit?usp=sharing just needs writing

authors: addyosmani gauntface

repo: GoogleChrome/sw-helpers


text:
Improve speed of builds

Library Affected:
sw-appcache-behavior, sw-offline-google-analytics, etc.
A full build currently takes between 10-30 minutes to complete on Travis:

On AppVeyor/Windows, we're looking at it taking multiple minutes too.

For smaller PRs, this introduces a bit of a bottleneck for folks that are trying to land incremental work at a decent pace.

sw-precaching
sw-background-sync-queue

appear to take a while.
Some areas for exploration:

Could we speed up the build by reducing our reliance on babel? drop async/await
Are we holding RollUp wrong? We might be able to squeeze some wins out by disabling features like tree-shaking
Downloading browsers (although I believe cached..) appears to take 500+ms per package:

FWIW, a unscientific experiment on 4 year old Mac shows that removing async/await transpilation takes the sw-lib build time from 17s down to 15s, and shaves ~1.1kb from the final output size of the minified umd bundle.
Removing babili minification (which I'm not suggesting we remove) takes the build time from 17s down to 13s.
sw-background-sync-queue is a bit of an extreme case, since it requires bundling a whole bunch of individual modules for testing purposes during the build. Perhaps @prateekbh could provide some context as to whether that's really necessary, and if not, it could be rewritten to follow the patterns used by the other modules?

https://github.com/GoogleChrome/sw-helpers/pull/485 should have helped, particular with the speed of sw-offline-google-analytics and sw-background-sync-queue builds.
A lot of the latency in those screenshots has to do with running code in a throttled CI build environment, as you can see total build times vary by up to an hour depending on what the Travis infrastructure is up to: https://travis-ci.org/GoogleChrome/sw-helpers/builds

@jeffposnick as of now I can see some really super fast builds on my local. I'll see if I can work with a single build itself

I'm going to close this, I think between my testing re-write and Jeffs build tidy up, the builds are more bearable.

💨

authors: addyosmani gauntface jeffposnick prateekbh


text:
Moved document eventlistener to sideNav

Let me start by thanking you for the awesome walkthroughs. They are both enjoyable to watch and very educational.
I noticed that you bind the eventlistener to the document instead of the sideNav__container; I prefer the behaviour aswell, but I think binding to the sideNav is even more appropriate. This way everything is much nicer contained to just the elements inside sideNav.

I signed it!

+1 I was thinking about this too while watching, since that element is 100% anyway.

Did I miss something?

Woah! No you didn't. Looks like me switching to gh-pages only (no master) closed the PR. Eesh. Sorry. Can you PR it in again?

Haha, that's odd. Here you go.

authors: DanielVoogsgerd TWiStErRob paullewis

repo: GoogleChrome/ui-element-samples


text:
cache api ios device for workbox

Library Affected:
workbox-webpack-plugin
Browser & Platform:
*E.g. IOS device (Safari)
Issue or Feature Request Description:
I've found some issues , haven't test it on all browsers . I am trying to test all this on Macos safari and ios safari. @jeffposnick  @philipwalton

Is it finally resolved that workbox precache and runtime cache will work on IOS safari devices? If you look into browser support for cache API, ios safari doesn't support it. it also means that because all browsers in ios are just wrappers around safari, it shouldn't work for those browsers too on safari device.

What does workbox do to prevent this and make offline support work for IOS device ? I tried it and it didn't work for Safari. I checked compatibility on canIuse and mozilla page and it's not supported. what does workbox do to make it work ?

self.addEventListener('install', function(e){
    console.log(self.__WB_MANIFEST, " manifest");
})
precacheAndRoute(self.__WB_MANIFEST);

This doesn't work, because of the fact that i log manifest in install event. if I remove logging it from install  listener, It starts working. Basically, what happens is because of I log it in install, precacheAndRoute now gets argument as undefined. I have no idea why.

I tried this on Macos and realized that after sw got isntalled and refresh the browser, 90% of my assets in network tab in safari say that they come back from memory and only 10% percent say they come back from serviceworker. Doesn't matter how many times I refresh the tab. Why does this happen at all? I have no idea. why don't they all come back from service worker ?

The Workbox issue tracker isn't the place to ask general questions about service worker support on iOS.
The InjectManifest plugin works by replacing the first occurrence of self.__WB_MANIFEST in your swSrc file with the a precache manifest based on your webpack compilation. Your first occurrence is inside of the install handler, and that's what's being swapped out. The second occurrence doesn't get replaced, so nothing ends up being precached (you're passing an undefined value to precacheAndRoute()). You should be able to confirm this by looking at the contents of the swDest file created by the plugin.
If you want to use the precaching manifest value in multiple places, you can assign it to a variable, and then use that variable multiple times, like:
const manifest = self.__WB_MANIFEST;

self.addEventListener('install', function(e){
    console.log(manifest, " manifest");
})
precacheAndRoute(manifest);

@jeffposnick I know this is not a place for ios support, but my question is something different.

As we can see, on caniuse.com page or mozilla page, safari ios doesn't support cache api. Because of that i am curious if you do some kind of fallback to navigate from this issue .

didn't other people open any issues as far as you know? does workbox work on ios safari because of cache api?

https://caniuse.com/#feat=mdn-api_cachestorage and https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage#Browser_compatibility both show that the current version of Safari on iOS supports the Cache Storage API.

We don't do anything specific in Workbox to accommodate Safari on iOS with regard to the Cache Storage API, because it's natively supported.

Yeah, but Let's check this: https://developer.mozilla.org/en-US/docs/Web/API/Cache. If you check the compatibility, it says that ios safari not supports it. Any idea? what's the difference between those?

The Workbox issue tracker really isn't the right forum to continue this discussion.
As I've said, there's nothing in Workbox that treats the Cache Storage API differently when used on Safari for iOS.
If you've found inaccurate information on one of the MDN web pages, one option is to take the steps to report the content issue there. The page you linked to has a "Update compatibility data on GitHub" link, which points to https://github.com/mdn/browser-compat-data#mdn-browser-compat-data

authors: jeffposnick novaknole

repo: GoogleChrome/workbox

license: mit


text:
Add support for the Web Share Target API - Level 2

Squoosh would be an ideal candidate to explore the Web Share Target API - Level 2. This would allow Squoosh to act as a share target for any to-be-squooshed image files.

We are already working on that :D
https://github.com/GoogleChromeLabs/squoosh/tree/share-target?files=1

Blocked on https://bugs.chromium.org/p/chromium/issues/detail?id=916070 right now, but aside from that we're close to having something demoable.

https://github.com/GoogleChromeLabs/squoosh/pull/469

authors: jakearchibald surma tomayac

repo: GoogleChromeLabs/squoosh


text:
tests: make unique Cloud Spanner database per run to avoid teardown clashes

After a full test run, the same Spanner instance was being torn down, which cause failures and very slow running of multiple tests concurrently. This change avoids those clashes by creating a unique database Id and tearing down just the database and NOT the instance.
Updates #99

Thanks for the review @halio-g!


text:
app-tools-lib-for-java is not a great name

the name combines verbosity with ambiguity.
Additionally naming for the artifact is a bit weird.  Most Maven artifacts don't need to -for-java as a suffix. All Maven artifacts are for Java. Perhaps the github repo name doesn't need to be the same as the artifact id?
This issue is to track that we are happy with the naming of the github project and artifactId prior to GA.

@patflynn  appengine-tools? and it will appear as appengine-tools.jar in the repositories?

this is fixed, decided on appengine-plugins-core

authors: loosebazooka meltsufin patflynn


text:
Fixing Flaky Test

Description
Flaky Test found using NonDex by running the command -
mvn edu.illinois:nondex-maven-plugin:1.1.2:nondex -Dtest=com.google.cloud.tools.managedcloudsdk.install.InstallerTest#testCall_withOverrideComponents
The logged failure -
[INFO]
[ERROR] Failures:
[ERROR]   InstallerTest.testCall_withOverrideComponents:115
Argument(s) are different! Wanted:
mockCommandRunner.run(
    [scriptexec, test-install.script, --path-update=false, --command-completion=false, --quiet, --usage-reporting=true, --override-components, myothercomponent, mycomponent],
    C:\Users\Bharati\AppData\Local\Temp\junit6297198120928949252,
    {"PROPERTY" = "value"},
    mockConsoleListener
);
-> at com.google.cloud.tools.managedcloudsdk.command.CommandRunner.run(CommandRunner.java:49)
Actual invocations have different arguments:
mockCommandRunner.run(
    [scriptexec, test-install.script, --path-update=false, --command-completion=false, --quiet, --usage-reporting=true, --override-components, mycomponent, myothercomponent],
    C:\Users\Bharati\AppData\Local\Temp\junit6297198120928949252,
    {"PROPERTY" = "value"},
    mockConsoleListener
);
-> at com.google.cloud.tools.managedcloudsdk.install.Installer.install(Installer.java:99)

Investigation
The test fails at InstallerTest.testCall_withOverrideComponents:115 with the error regarding a mismatch of arguments while using the overrides variable declared on line 102. The variable is declared using the HashSet constructor. According to the documentation, the HashSet class makes no guarantees as to the iteration order of the set; in particular, it does not guarantee that the order will remain constant over time. This makes the test outcome non-deterministic. To fix this, HashSet needs to be replaced with a data structure that can guarantee the order of its elements.
Fix
LinkedHashSet preserves the iteration ordering, which is the order in which elements were inserted into the set. As this data structure is deterministic, replacing the HashSet with the LinkedHashSet removes the non-determinism without needing any further changes and ensures that the flakiness from the test is removed.

Fixed in #903.


text:
Add peering routes config for PSA in net-vpc module

The module currently doesn't allow to optionally import/export custom routes.
This can be easily achieved with the google_compute_network_peering_routes_config resource.
PR following soon!

I'm pretty sure the module already does this.

Ah, PSA I thought peering. Good point then.

Hey Luke, after the merge I got this errors in the 02-networking-vpn stage:
│
│
│   with module.dev-spoke-vpc.google_compute_global_address.psa_ranges["cloudsql-sqlserver"],
│   on ../../../modules/net-vpc/main.tf line 331, in resource "google_compute_global_address" "psa_ranges":
│  331: resource "google_compute_global_address" "psa_ranges" {
│
╵
╷
│ Error: Error waiting to create GlobalAddress: Error waiting for Creating GlobalAddress: Invalid IP CIDR range: 10.128.95.0/24 conflicts with IP range 10.128.95.0/24 that was allocated by resource projects/dcx0-prod-net-spoke-0/global/addresses/prod-spoke-0-psa-prod-1.
│
│
│   with module.prod-spoke-vpc.google_compute_global_address.psa_ranges["cloudsql-sqlserver"],
│   on ../../../modules/net-vpc/main.tf line 331, in resource "google_compute_global_address" "psa_ranges":
│  331: resource "google_compute_global_address" "psa_ranges" {```

Ciao Dani!
I think this simply has to do with how the provider works.
I guess the apply with the new module will try to create a new range/psc,
without deleting the previous one(s), thus going in conflict.
I’d suggest to comment your range definitions (I’d assume in
terraform.tfvars), apply (thus deleting the old ranges). Then, uncomment
and apply again.
Please, let me know if you run into more issues.
Hope it helps
Il giorno ven 11 mar 2022 alle 23:13 Daniel Marzini <
@.***> ha scritto:

Hey Luke, after the merge I got this errors in the 02-networking-vpn stage:
│
│
│   with module.dev-spoke-vpc.google_compute_global_address.psa_ranges["cloudsql-sqlserver"],
│   on ../../../modules/net-vpc/main.tf line 331, in resource "google_compute_global_address" "psa_ranges":
│  331: resource "google_compute_global_address" "psa_ranges" {
│
╵
╷
│ Error: Error waiting to create GlobalAddress: Error waiting for Creating GlobalAddress: Invalid IP CIDR range: 10.128.95.0/24 conflicts with IP range 10.128.95.0/24 that was allocated by resource projects/dcx0-prod-net-spoke-0/global/addresses/prod-spoke-0-psa-prod-1.
│
│
│   with module.prod-spoke-vpc.google_compute_global_address.psa_ranges["cloudsql-sqlserver"],
│   on ../../../modules/net-vpc/main.tf line 331, in resource "google_compute_global_address" "psa_ranges":
│  331: resource "google_compute_global_address" "psa_ranges" {```
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/issues/576#issuecomment-1065580250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARY7UGSBSJOF6INZ4VXZTTU7PAR7ANCNFSM5QGBKKOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***
com>

authors: LucaPrete danielmarzini ludoo


text:
Cause server launch to listen and react to server state changes

Cause server launch to listen and react to server state changes such that stopping the server terminates the launch.
Note: this only clears up the Debug situation; #614 will fix the Run situation
Also cleaned up server stopping to set state to STOPPED once the server process is reported as dead.  This was to fix strange race condition where the server could be reported as STOPPED but continued to write to the console.
Fixes #516

LGTM once the tests pass

authors: briandealwis elharo


text:
Is there any way to get a shell from running container?

Hi there,
Sometimes we need to get bash or ssh into a running container for debugging . Is it possible  to do this with these images ?

The :debug tagged images container busybox, so you can --entrypoint=sh, but the :latest images drop this to bias towards minimal containers in production.

Thanks for your reply. So there is no busybox or any kind of shell in
production images?
On Wed, Mar 7, 2018 at 02:19 Matt Moore notifications@github.com wrote:

The :debug tagged images container busybox, so you can --entrypoint=sh,
but the :latest images drop this to bias towards minimal containers in
production.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/distroless/issues/168#issuecomment-370957362,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbb2pPkevKMO_50Oy47MyYNfpARbzPMks5tbxJggaJpZM4Sfi0J
.

Not currently, no.
On Tue, Mar 6, 2018, 2:56 PM Reza Kamalifard notifications@github.com
wrote:

Thanks for your reply. So there is no busybox or any kind of shell in
production images?
On Wed, Mar 7, 2018 at 02:19 Matt Moore notifications@github.com wrote:

The :debug tagged images container busybox, so you can --entrypoint=sh,
but the :latest images drop this to bias towards minimal containers in
production.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/GoogleCloudPlatform/distroless/issues/168#issuecomment-370957362
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ABbb2pPkevKMO_50Oy47MyYNfpARbzPMks5tbxJggaJpZM4Sfi0J
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/distroless/issues/168#issuecomment-370959130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVE4kt4abAm1ViQ2L1LguAwiuC9DaxRks5tbxQLgaJpZM4Sfi0J
.

@itmard You can copy the busybox into a running container and then run it there. If you have a running container named mycontainer1, you can run:
docker cp /path/to/busybox mycontainer1:/sh
docker exec -it mycontainer1 /sh

The busybox executable can be extracted from the busybox:latest docker image, for example. Make sure it is statically linked:
$ file busybox
busybox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped

Closing as this looks addressed. Also see https://github.com/kubernetes/features/issues/277 for another take on a similar use-case.

authors: dlorenc dubek itmard mattmoor

repo: GoogleCloudPlatform/distroless


text:
chore: Updated for mono_repo 6.0.0

Updated project mono_pkg.yaml configs for latest mono_repo 6.0.0

Need to re-run mono_repo generate

@subfuzion – want me to land this?

That would be great thanks. I had a power failure and can't boot my machine
right now.
On Thu, Dec 16, 2021 at 11:44 AM Kevin Moore @.***>
wrote:

@subfuzion https://github.com/subfuzion – want me to land this?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/functions-framework-dart/pull/305#issuecomment-996130645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG76WL5QDSKOMWCEXN2G3URI6THANCNFSM5KG7MPGA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

--
Tony Pujals
Senior Developer Advocate
Google Cloud | Anthos
GitHub: @subfuzion
Twitter: @tonypujals

authors: kevmoo subfuzion


text:
How to index Blob property in datastore?

Is there a way to index a Blob property (with size < 1500 bytes)? I know about exclude_from_indexes attribute on Entity to remove the properties that would indexed by default. I am looking for a way to white-list properties that are unindexed by default like Blob Property.
In NDB you can do it by setting indexed=True on the property. Is there an equivalent in gcloud/datastore

In gcloud-python everything is indexed by default, so you only need to explicitly say when not to. The behavior is not the same as ndb since there are no Property classes to encapsulate settings.
Maybe I'm misunderstanding. Do you have a specific example code snippet in mind?

You are right. It was a bug in my implementation. Thanks for quick response.

authors: dhermes vinays

repo: GoogleCloudPlatform/gcloud-python


text:
[DO NOT MERGE] Updating all the region tags to have a prefix of datastore

[DO NOT MERGE] Updating all the region tags to have a prefix of datastore

I'll ping you when we're ready to merge.

authors: billyjacobson jmdobry

repo: GoogleCloudPlatform/golang-samples


text:
Stackdriver Profiler : Unable to load profile CPU & Contention

Client
Compiled on:
golang 1.10.1
"cloud.google.com/go/profiler" v0.21.0
Describe Your Environment
busybox:1.28.0-glibc Docker on GKE
Expected Behavior
See CPU & Contention statistics captured from profiler agent, in the Stackdriver developer console.
Actual Behavior
Can see Heap & Threads working.
I enabled debug logging and saw lots of:
2018-04-10 19:29:17.088 BST successfully created profile CPU
2018-04-10 19:29:27.133 BST start uploading profile
However nothing is ever available to view in the Stackdriver developer console.
Let me know if you need anything extra.
fyi, I did run: gcloud services enable cloudprofiler.googleapis.com

I would like to add, I ran this on my local machine. And I got CPU stats working, still no contention.

@nolanmar511

@zeroflaw What does the profiler UI looks like when you open it / refresh it? Does it have the CPU choice in the profile type combo-box?

This is what I see

I forgot to mention I use the stackdriver debugger (go-cloud-debug)
Which might be part of the problem because I think it was last compiled on go 1.7 which maybe part of the problem. Are you able to easily generate a go 1.10.1 build, which I try?
I've done the following tests:
Without debugger
base docker image busybox:1.28.0-glibc = failed
base docker image busybox:1.28.3-glibc = failed
base docker image alpine-3.7 = failed
base docker image golang:1.10.1-alpine3.7 = failed
base docker image bitnami/minideb:latest = Worked!!
with debugger
base docker image bitnami/minideb:latest = failed
I'm not sure if the above is helpful, but at no point is the debug logging from the profiler telling me anything other than its all good. So is something not being processed correctly on the stackdriver endpoint? should I go ahead a capture the messages and compare them?

One possible reason of not seeing any data is that there is little (i.e. ~zero) CPU usage in your service. What's the CPU utilization of the service process according to top command?

basically zero, i'll throw in some code to generate some extra, load.
I'll get back to you in a moment.

With some additional load busybox:1.28.3-glibc without debugger, is working.
Nothing works with the debugger attached.

I've done plenty of tests going debugger on/off and none of them have worked using go-cloud-debug.
I'm going try rebuilding go-cloud-debug with 1.10.1

Stackdriver Profiler uses Go's runtime/pprof package to get CPU profiles. The debugger agent runs the program under a debugger, see https://code.googlesource.com/gocloud/+/master/cmd/go-cloud-debug-agent/debuglet.go#108 - I wonder if running under debugger makes runtime/pprof CPU profiling not working.

The issue is not specific to the Stackdriver Profiler profiling agent, but rather to runtime/pprof CPU profiling in general. To reproduce, save the example code below as a pprof-profile.go file, then:
# Build the example
$ go build pprof-profile.go

# Run the example without debugger.
# This works as expected, collects some data.
$ ./pprof-profile
profile collected with 343 samples

# Download the debugger agent per instructions at
# https://cloud.google.com/debugger/docs/setup/go
$ wget -O go-cloud-debug https://storage.googleapis.com/cloud-debugger/compute-go/go-cloud-debug
chmod 0755 go-cloud-debug

# Run the example under debugger.
# This doesn't work as expected, zero samples are collected.
$ ./go-cloud-debug ./pprof-profile
profile collected with 0 samples

Example source:
package main

import (
  "bytes"
  "compress/gzip"
  "fmt"
  "log"
  "math/rand"
  "runtime"
  "runtime/pprof"
  "time"

  "github.com/google/pprof/profile"
)

// busywork continuously generates 1MiB of random data and compresses it
// throwing away the result.
func busywork() {
  for {
    busyworkOnce()
  }
}

func busyworkOnce() {
  const size = 1024 * 1024

  data := make([]byte, size)
  rand.Read(data)

  var b bytes.Buffer
  gz := gzip.NewWriter(&b)
  if _, err := gz.Write(data); err != nil {
    log.Fatalf("Failed to write to gzip stream", err)
  }
  if err := gz.Flush(); err != nil {
    log.Fatalf("Failed to flush to gzip stream", err)
  }
  if err := gz.Close(); err != nil {
    log.Fatalf("Failed to close gzip stream", err)
  }
  // Throw away the result.
}

func main() {
  runtime.GOMAXPROCS(2)
  go busywork()

  var b bytes.Buffer
  pprof.StartCPUProfile(&b)
  time.Sleep(5 * time.Second)
  pprof.StopCPUProfile()

  p, err := profile.Parse(&b)
  if err != nil {
    log.Fatalf("failed to parse collected profile: ", err)
  }
  fmt.Printf("profile collected with %d samples\n", len(p.Sample))
}

Update: https://go-review.googlesource.com/c/debug/+/107675 should solve the issue.

👍 how would I go about taking this change? is it the go-cloud-debug or my app that needs updating?

This change should be in the Go debug agent at head.

Works. Good job :)

okay so, I'm sometimes getting the error:
"standard_init_linux.go:178: exec user process caused "exec format error" on startup of Kubernetes pods. It sometimes works (nothing is changing, image is the same as the time it worked)
Not sure how I can provide any more details, but I'm happy to help.

authors: aalexand jba zeroflaw

repo: GoogleCloudPlatform/google-cloud-go


text:
Pubsub feature: get messages count waiting in subscription

Hi,
I need to know how many messages are waiting in the subscription, to pop new workers or monitor the health of my system. This is something AWS SQS does too.
Is it in the roadmap actually ?
Thank you

FYI: as https://code.google.com/p/cloud-pubsub/issues/detail?id=13 told me, there is a "num_undelivered_messages" endpoint to get that metric.

Considering it's "not accurate" I wouldn't use it yet and don't think we should support it in this library until we know it is accurate.

This feature could never be accurate because messages are always flowing into the subscription (depending on the publish rate), but it's crucial to know if you need to add more workers to process messages or monitor the health of your workers.

From https://cloud.google.com/monitoring/api/metrics, they list two interesting ones:
num_outstanding_messages: Current number of messages delivered but not yet acknowledged.
num_undelivered_messages: Current number of messages pending to be delivered.
Maybe we could open up a generic subscription.getMetrics('num_outstanding_msesages') and anything else from the list: topic.getMetrics('message_sizes'), as these may all be useful.

Assigned this to @callmehiphop since you had some ideas for how to implement this generically.

what about this one?

We have a few more things to implement with a higher priority before getting to this one, mostly support for the Prediction and Translate APIs, then promises.

if i will create a pull request, you will merge?

That would be great!

Great to see you guys working on this already. If its worth, right now I use stackdriver's subscription metrics capabilities to get this information, apparently, stackdriver lags behind and the count is not accurate. Just wanted to add +1 to this request and happy to be a beta tester, if need be. Let me know.

Adding link to the current related google doc page, for others like me that ended up here looking to know learn about msg depth in a sub: https://cloud.google.com/pubsub/docs/ordering#order_of_processed_messages_matters

@callmehiphop given the large Pub/Sub rewrite that happened since this issue was opened, is this request still relevant / do you have an idea for a reliable implementation?

@stephenplusplus AFAIK the re-write hasn't changed anything in regard to collecting these metrics.

This issue was moved to googleapis/nodejs-pubsub#8

authors: callmehiphop leibale mpcm pierre-b ryanseys sahas- stephenplusplus

repo: GoogleCloudPlatform/google-cloud-node


text:
Update required version of google/cloud-core

Replaces #1216.
I used v1.23 which is not yet released. The next release of the library will make that version available.

we should wait until shortly before release to merge this pull request, so as to not prevent master from being installable due to the required version of cloud-core not existing.

repo: GoogleCloudPlatform/google-cloud-php


text:
Add Pub/Sub Subscription retain_acked/retention_duration

#1274 adds the retain_acked/retention_duration values to subscriptions. Add these values to the model, create method, and update method.

cc @garrettjonesgoogle Is this going to be release blocking?

@kir-titievsky does this feature block Pub/Sub beta in any languages?

I'm working on this now.

authors: blowmage garrettjonesgoogle landrito quartzmo

repo: GoogleCloudPlatform/google-cloud-ruby


text:
add test socket

➜  security git:(image-test-socket) ✗ /manager -project hanga-testing -zone us-west1-c -images projects/debian-cloud/global/images/family/debian-10
2021/07/08 22:48:21 imagetest: Done with setup
runTestWorkflow: running security on debian-10 (ID l9ryd)
<testsuites name="" errors="0" failures="0" disabled="0" skipped="0" tests="1" time="0">
	<testsuite name="security-debian-10" tests="1" failures="0" errors="0" disabled="0" skipped="0" time="0">
		<testcase classname="" name="TestSockets" time="0.01"></testcase>
	</testsuite>
</testsuites>

this one needs to be reworked, the original test is out of date. closing in favor of a replacement PR

authors: gaohannk hopkiw

repo: GoogleCloudPlatform/guest-test-infra


text:
Consolidate flags into one place

Currently flags are spread about all over different source files. Consolidating in one place will make addition of flags more consistent & prevent accidentally reusing flag names, etc.
As an extra, can we consider switching to pflag (https://github.com/spf13/pflag/), drop in replacement for flag, but POSIX compliant flags & has shorthand flags, etc?

Could even consider viper (https://github.com/spf13/viper) so we can combine flags, env vars & config files into one runtime configuration. As we as more functionality, multiple sinks, events, etc, having a config file might be really useful, in addition to flags, etc.

I like this idea. Most of heapster can act as a library with this change. viper sounds pretty interesting. It should satisfy most of the deployment scenarios.

Think this is closeable note that sources & sinks flags are consolidated.

authors: jimmidyson vishh

repo: GoogleCloudPlatform/heapster


text:
Cloud Workstation Improvements

This update should fix the cloud workstation build to allow the workstations to automatically pull down the hpc-toolkit, install dependencies, and build it successfully.
The only issue I've seen is that the Test shell scripts with shellcheck fails during pre-commit run --all-files on files I haven't touched.
I also updated the README.md to include commands for building everything needed for a workstation if a user doesn't have a configuration, or cluster.

The only issue I've seen is that the Test shell scripts with shellcheck fails during pre-commit run --all-files on files I haven't touched.

This has been fixed by removing the apt-get install shellcheck and replacing it with a download of a specified version of the binary from github and placing it in the /bin/ folder.

repo: GoogleCloudPlatform/hpc-toolkit


text:
consolidating flex samples into single project

After looking at how how we use these samples in our docs, I think our vision of having the single app must not burden users who just want to see the single servlet Flex sample demonstrating a particular functionality. It should also not burden the contributors.
Let me know if this current approach makes sense. the samples-builder under flexible/java-runtime/samples creates the bundled app on the fly from all or a subset of the samples.

Oh, fix Circle first, however.

@lesv will do : will fix the README and also looking into the testing
concerns you brought up.
On Fri, Apr 28, 2017 at 11:19 AM, Les Vogel notifications@github.com
wrote:

Oh, fix Circle first, however.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/pull/633#issuecomment-298070422,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWfpWzT5arKd9BCU-5B056kSu9TF1py1ks5r0i2WgaJpZM4NJOjf
.

Hello,
do we have an ETA for this to land?

End of this week is what I'm targeting. Hold up : making sure we can set
the env vars correctly in app.yaml for testing.
Is this a blocker for anything ? I had n't prioritized this accordingly, if
so.
On Wed, May 10, 2017 at 10:14 AM, Ludovic Champenois <
notifications@github.com> wrote:

Hello,
do we have an ETA for this to land?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/pull/633#issuecomment-300550956,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWfpW9sV0tQTgmD2jxoYur-erP1L6Pquks5r4fB8gaJpZM4NJOjf
.

What I'm doing is different from this one.
On Wed, May 10, 2017 at 10:41 AM, Jisha Abubaker notifications@github.com
wrote:

End of this week is what I'm targeting. Hold up : making sure we can set
the env vars correctly in app.yaml for testing.
Is this a blocker for anything ? I had n't prioritized this accordingly, if
so.
On Wed, May 10, 2017 at 10:14 AM, Ludovic Champenois <
notifications@github.com> wrote:

Hello,
do we have an ETA for this to land?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/GoogleCloudPlatform/java-docs-
samples/pull/633#issuecomment-300550956>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWfpW9sV0tQTgmD2jxoYur-erP1L6Pquks5r4fB8gaJpZM4NJOjf>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/pull/633#issuecomment-300559067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFVjtu4JOhIVcHqBlapGeykhEfba5lEks5r4fa7gaJpZM4NJOjf
.

--

•  *Les Vogel
•  *Cloud Developer Relations
•  *lesv@google.com
•  *+1-4 <%2B1-650-338-7103>08-676-7023

will close this PR and re-do at a later time.

authors: jabubake lesv ludoch

repo: GoogleCloudPlatform/java-docs-samples


text:
feat: Initial structure for the Assured Workloads example

Initial structure for the Assured Workloads example using Regional Control, HSM Key and Access Justification.
Next steps to evolve this example include (will be submitted in further PRs):

Add services that use the Cloud HSM Key: GCS, BigQuery and Confidential Compute.
Add VPC-SC perimeter.

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

authors: daniel-cit kieras romanini-ciandt

repo: GoogleCloudPlatform/kms-solutions


text:
Kubernetes endpoint should not use link-local address of interface

On certain cloud providers like digital ocean the public interface has multiple addresses, one of which is a link-local address that points to a metadata server. The node is supposed to come up and contact the metadata server to bootstrap the public interface with a real address. At this point, the interface has 2 addresses, eg (from irc debugging): https://dpaste.de/T8s0/raw.
Looks like we create the kubernets endpoint using the first, link-local address and it always gets rejected. The kubernetes master service creation can keep failing (and re-checking for a valid public ip) when this happens because it knows link-local is not allowed: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/master/controller.go#L97

Is this just a case of ChooseHostInterface() not filtering link-local?
This seems like a pretty easy change, good starter change for someone who wants to get involved.

Is there a fix for this?

Not yet - it seems like a 30 minute sort of fix.  Got 30 minutes?

Sure. Is there something in the output of /proc/net/route that could be used to identify the wrong IP to use?
In the meantime is there some way to force kube-apiserver to a specific IP?

You may be able to set --advertise-address on the apiserver, but that's sort of clumsy.  I think the best fix will be to fix ChooseHostInterface() to exclude IPs which are ip.IsLinkLocalMulticast() or ip.IsLinkLocalUnicast().  The code is easy (I think) and then a test should be straight-forward.

Okay, you're right, it took me 30 seconds. I'll write up a test too and pr>

Okay @thockin, how's this?

This issue might be more complex... I filtered out the link-local addresses in finalIP util function, and while all the unit tests pass, the e2e fails. Really weird.

After the recent updates I've rebased and the tests work.

authors: bprashanth paralin thockin

repo: GoogleCloudPlatform/kubernetes


text:
REST api - some errors return as json and some as plain text

This causes overhead on client side when parsing the errors since need to recheck content type for every error in order not to parse plain text as json (some libraries fail on that).
The errors message format should be standardized.
Examples:
404: Page Not Found
Content-Type: text/plain; charset=utf-8
405 Method Not Allowed
Content-Type: text/plain
409 Conflict
Content-Type: application/json
500 Internal Server Error
Content-Type: application/json

cc @simon3z

Duplicate of #4347.


text:
missing public IP in examples/logging-demo

Hi @satnam6502 @nikhiljindal , I followed the instructions in examples/logging-demo, and there was no "external IP" field for elasticsearch-logging or kibana-logging, as shown below:
../../_output/local/bin/linux/amd64/kubectl get services kibana-logging -o json
{
    "kind": "Service",
    "apiVersion": "v1beta3",
    "metadata": {
        "name": "kibana-logging",
        "namespace": "default",
        "selfLink": "/api/v1beta3/namespaces/default/services/kibana-logging",
        "uid": "9dc6f856-f358-11e4-a58e-42010af09a93",
        "resourceVersion": "31",
        "creationTimestamp": "2015-05-05T18:57:45Z",
        "labels": {
            "kubernetes.io/cluster-service": "true",
            "name": "kibana-logging"
        }
    },
    "spec": {
        "ports": [
            {
                "name": "",
                "protocol": "TCP",
                "port": 5601,
                "targetPort": "kibana-port"
            }
        ],
        "selector": {
            "name": "kibana-logging"
        },
        "portalIP": "10.0.188.118",
        "sessionAffinity": "None"
    },
    "status": {}
}

I start up my cluster via cluster/kube-up.sh. Did I miss something or is it a bug? Thanks.

Correct. This demo does not create an ELB so there is no external IP address.
Access is via service proxy at the master.
Type:
$ kubectl cluster-info

and you should the URLs for Elasticsearch and Kibana.

@caesarxuchao please let us know whether:
a. Satnam's comment resolves your issue
b. the demo should be updated to prevent this misunderstanding
c. the issue isn't resolved
Thank you!

Yes, Satnam's comment resolve the issue. I updated the demo in #7824.

Awesome, thanks for sending the patch! We'll discuss there. Always fantastic to have docs updated regularly by folks trying them.

authors: caesarxuchao mbforbes satnam6502


text:
Problem on updating pods with file

I created a pod with 'pod1.yaml' under examples/walkthrough directory by kubectl create -f pod1.yaml,
then I modified 'pod1.yaml' changing image: nginx to image: my/nginx, then I tried to update the pod with kubectl update -f pod1.yaml
An error message returns which says:
Error: Pod "www" is invalid: spec: invalid value '{Volumes:<nil> Containers:[{Name:nginx Image:my/nginx Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:map[] Requests:map[]} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc2083c8360){Capabilities:<*>(0xc2086751d0){Add:<nil> Drop:<nil>} Privileged:<*>(0xc2081b98d8)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> Host: HostNetwork:false}': may not update fields other than container.image

I tried to use kubectl update pods www --patch='{"apiVersion": "v1beta1","desiredState": {"manifest": {"containers": [{"image": "my/nginx"}]}}}' and kubectl update pods www --patch='{"apiVersion": "v1beta3", "spec": {"containers": [{"image": "my/nginx"}]}}', they both returned the same error.
It seems that those fields which are not required while creating are required while updating. Can we use the existing value of old resources for those fields while updating? Actually I had a similar problem before, see #5907
BTW, use patch to update an resource isn't easy, look at the length of the commands, so I would prefer use -f option.

Not sure why patch is failing but update does require all the fields.
To update your object:

Run kubectl get pods www -o yaml > /tmp/pod1.yaml
Modify /tmp/pod1.yaml as you want and then
Run kubectl update -f /tmp/pod1.yaml

Re patch: What you want is a strategic merge patch as described here: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api-conventions.md#strategic-merge-patch.
Unfortunately, you cant perform a strategic merge patch via kubectl.

cc @ghodss

@nikhiljindal - I missed the container name in the patch command, now I can update it with patch.
I also tried to export the pod to file, then modify it to update the pod. It works. But it seems the exported file can only be modified and used for only once because it contains version number of old resource. I think it prevents the template to be portable.

Yes you need to do a get each time before updating.
Re: patch. Can you please post the command that works for you. The following command gives me the same error:
kubectl update pods www --patch={"apiVersion": "v1beta3", "spec": {"containers": [{"name": "www", "image": "my/nginx"}]}}

@nikhiljindal - Actually in my office there're 2 enviroments for testing k8s, one standalone hosted on my pc and another one with multi minions on a cloud enviroment. When I want to update something and keep them synchronized in two enviroments, I had to export the file and modify it twice. That's why I say it prevents the template to be portable. I think maybe we can make some improvement on this update operation, from a user's sight.
About the patch command, it's almost the same as you given except the container name is 'nginx', 'www' is the pod's name.

Not sure if something broke recently, but I just tried the following and it failed
./cluster/kubectl.sh update pods www --patch='{"apiVersion": "v1beta3", "spec": {"containers": [{"name": "nginx", "image": "my/nginx"}]}}'
Error from server: Pod "www" is invalid: spec: invalid value '{Volumes:[{Name:default-token-5cpor VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc2094f5990){SecretName:default-token-5cpor} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name:nginx Image:my/nginx Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:<nil> Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc2094e8c20){Capabilities:<*>(0xc209aa2b10){Add:<nil> Drop:<nil>} Privileged:<*>(0xc2094f5985)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> ActiveDeadlineSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:127.0.0.1 HostNetwork:false}': may not update fields other than container.image

authors: hurf nikhiljindal


text:
Update Kibana to v1.2 which paramaterizes location of Elasticsearch

Following on from #5776 this updates the image for Kibana to use the kind work done by @jonlangemak

I brought up a cluster with this PR and I looked at the Kibana dashboard and everything seems to work fine.

LGTM. Thanks!


text:
Add missing source to ubuntu/util.sh

Closes #9237. Forgot a lib import in #9227.
@adyanthaya17 let me know if this fixes issue for you.

LGTM

Something is still wrong.I run kube-up.sh.It complains
/home/vcap/kube/util.sh: line 20: /cluster/common.sh: No such file or directory
seems the KUBE_ROOT variable is empty, did you test it?

Aha, I found the reason, because this util.sh is remotely executed on the master and minion machine, not on your  machine you clone the repo.So common.sh is not there. I will fix it today.

@jlowdermilk Hi, thank you it did fix the kube-up.sh issue though I'm still facing the issue with kubectl command which tells it's an unknown command.

@adyanthaya17 I assume you messed it up.Please download from http://storage.googleapis.com/kubernetes-release/release/v0.18.2/bin/linux/amd64/kubectl
if you use linux.

@WIZARD-CXY I downloaded the kubectl from the link you specified but the kubectl still gives 'command not found'.

@adyanthaya17 whar arch do you use? Don't tell me it's not amd64 linux. You need to use arch-specific binary and chmod 755 kubectl to make it executable.Then you can definitely use it.

authors: WIZARD-CXY adyanthaya17 jlowdermilk saad-ali


text:
Restructure

This is a file restructure that move all files in /future/serving directory to /future/serving/rpc directory.
A client wrapper will resides in the future/serving/client directory later.

Can you add a comment to describe why this restructure is being done?

Done.

Sorry I meant internal/rpc/ should be the directory.

authors: jeremyje sawagh yfei1

repo: GoogleCloudPlatform/open-match


text:
Adds V2 MSSQL Metrics.

This should be identical with this PR https://github.com/GoogleCloudPlatform/ops-agent/pull/542, but instead of having a separate app called sqlserver, this adds new metrics to the existing mssql application with a version configuration parameter to differentiate between old and new.

All tests pass:

I rebased off master and now am trying to figure out why the windows tests are failing

I rebased off master and now am trying to figure out why the windows tests are failing

I think it's just missing this change from the other PR.

I rebased off master and now am trying to figure out why the windows tests are failing

I think it's just missing this change from the other PR.

@jefferbrecht oh jeez. Glad you noticed this. Thanks!

General comment for reviewers. I still think this is in a good state to merge. the SLES 12 errors seem to be non related

I had one suggestion, otherwise looks fine to me. If I were you, I'd ask ling, igor, and sophie if they want to do this review and remove them if not; if we have to wait for everybody's review, you'll be here a long time.

I'll defer to other reviewers for this one.

I had one suggestion, otherwise looks fine to me. If I were you, I'd ask ling, igor, and sophie if they want to do this review and remove them if not; if we have to wait for everybody's review, you'll be here a long time.

@martijnvans Unfortunately, I don't have a specific way to ping @igorpeshansky or @sophieyfang other than calling them out here. I just figured once the people actively reviewing this PR saw enough 👍 then they would merge.

all tests passing before rebase with master.

Windows 3rd party integration tests are failing due to supported_app_version but at least I've updated the metadata.yaml for mssql to include this and this test appears to be passing because of it

Copying here for visibility: we'd like to explore the possibility of adding functionality to metricstransform to move resource attributes to metric labels to avoid the catchall exporter config, so we'll need to hold off on merging this for a bit pending the result of that investigation. I believe this is the only issue blocking this PR.
Since this PR addresses the broken tests on master, I opened #571 to fix that separately.

@jefferbrecht Thanks for the update. Do you have any idea of a rough timeframe for these new changes addressing resource attributes?

It's hard to say, but I would think it'll be on the order of a few weeks.

I believe all kokoro failures are unrelated jetty failures
 third_party_apps_test.go:579: Test logs: https://console.cloud.google.com/storage/browser/ops-agents-public-buckets-test-logs/prod/stackdriver_agents/testing/consumer/third_party_apps/test/focal/90/20220606-145405/logs/TestThirdPartyApps_ubuntu-2004-lts_jetty third_party_apps_test.go:592: Instance Log: https://console.cloud.google.com/logs/viewer?resource=gce_instance%2Finstance_id%2F3542683822845053199&project=stackdriver-test-143416 third_party_apps_test.go:603: Non-retryable error: representative metric workload.googleapis.com/jetty.select.count not found, skipping remaining metrics

I think all feedback has been addressed

After we did a  little digging, we believe that the jetty failure is related to update the operations collector. Planning on getting the next released version into this PR

Aside from the Kokoro issue from the operations collector bump, I believe this is good to be re-reviewed

The failed Windows build is a known issue (fixed separately already).
Once rebased, this can be merged.

Test failure seems unrelated:
=== CONT  TestUpgradeOpsAgent/windows-2019
    ops_agent_test.go:1693: WaitForMetric(metric=agent.googleapis.com/cpu/utilization, extraFilters=[]) failed: exhausted retries
--- FAIL: TestUpgradeOpsAgent (0.00s)
    --- PASS: TestUpgradeOpsAgent/windows-2012-r2 (750.55s)
    --- FAIL: TestUpgradeOpsAgent/windows-2019 (1270.42s)

Happy to keep on retrying but I don't believe it should block this PR

Third party test passed, Ops Agent Upgrade failed because of
=== CONT  TestUpgradeOpsAgent/windows-2019
    ops_agent_test.go:1693: WaitForMetric(metric=agent.googleapis.com/cpu/utilization, extraFilters=[]) failed: exhausted retries
--- FAIL: TestUpgradeOpsAgent (0.00s)
    --- PASS: TestUpgradeOpsAgent/windows-2012-r2 (750.55s)
    --- FAIL: TestUpgradeOpsAgent/windows-2019 (1270.42s)

@qingling128 @ridwanmsharif  I don't believe this is a blocker, but do you have any thoughts?

authors: StefanKurek jefferbrecht martijnvans qingling128 schmikei

repo: GoogleCloudPlatform/ops-agent


text:
Integration test fix

This needs google/cloud 0.33 release

Now the tests return the logName. PTAL

repo: GoogleCloudPlatform/php-docker


text:
improvement: add mysql support for the inventory service

Description

Add support for mysql database for the inventory service

Changes

Add required dependencies
Add required annotations for the Entity class Item
Add an interface repository for the Item Entity CrudOperations on DB
Update the Springboot component scan packages to scan classes from the service-sdk module
Update the Springboot application configurations to include default DB configurations
Implement a InventoryConnector that uses the database
Update the InventoryController to ensure database does not have duplicate entries on every restart

Related PRs:

PR https://github.com/GoogleCloudPlatform/point-of-sale/pull/90 must be reviewed after this one

Couple questions:

Should these changes include README / docs changes to talk about the MySQL connection?

Yes, it should. I am hoping to add the README and docs after I have tested these on a full K8s/ABM installation. Having it merged helps me add a build pipeline to deploy this to K8s in the CI project. This gives a clearer idea as to all the details that go into the README.

Any plans to generify MySQL into "any SQL" / support for Cloud SQL / etc? (see for example: https://github.com/GoogleCloudPlatform/bank-of-anthos/tree/main/extras/cloudsql)

If I understand correctly BoA uses CloudSQL backed by a  PostGRES instance. I hope to do the same but backed by MySQL. I have tested this on a CloudSQL instance with a MySQL backend. Let me know if I have misunderstood this question.

Where does the SQL database come from? Is it stood up by the user ahead of time? Are there any instructions to do so?

This PR adds support for the application to connect and use a MySQL backend. In the final product we would have a one click install setup in GCP that will have everything pre-populated. We will also have the CI project configures with a CloudSQL(MySQL) instance. Also we would have manual steps for someone who just wants to run the application without any K8s stuff. After I get these implementations merged, Ill be working on standing up a CloudSQL in the CI project and having this properly deployed. Then, I am hoping to add READMEs to explain the flow.

Is this change going from in-database -> SQL, and if so, is there an option to opt out of the additional overhead of SQL altogether and keep the "old" way of in-database / text files?

The way it is implemented, if no environment variable is set (to use Database) then the application continues to work using in-memory datastores. This will not change.

Last question: this is getting merged into the main branch, presumably without readme / docs changes or implementation of the SQL instance. Is this a breaking change, or will this application continue to work "as-is" even without the SQL instance set-up? I think you answered that question by saying "that's correct" but I wanted to confirm

Last question: this is getting merged into the main branch, presumably without readme / docs changes or implementation of the SQL instance. Is this a breaking change, or will this application continue to work "as-is" even without the SQL instance set-up? I think you answered that question by saying "that's correct" but I wanted to confirm

Yup, it won't break anything on the main as long as they just use it as is. However, they could look at the code and try things out by enabling the Database; at which point they had decided to do it themselves.
Also after thinking a little longer, I am planning on merging all of it into a new branch v2-sql and then merging it finally into main.

Can test App at: http://35.232.88.13/

MySQL flavor (skaffold with -p dev) working, UI reachable + app working.
mysql-db-0 mysql-db 2022-03-16T20:59:53.955491Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.28'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.

In memory profile (-p dev,inmemory) working as well. LGTM.

authors: Shabirmean askmeegs bourgeoisor

repo: GoogleCloudPlatform/point-of-sale


text:
Manifests from main does not work due to read only filesystem.

This is fine on managed GMP, because we have a different flow there.
Using manifests/* from main leads to:
{"error":"create temporary certificate dir: mkdir /tmp/operator-cert2628617008: read-only file system"

Introduced by https://github.com/GoogleCloudPlatform/prometheus-engine/pull/944, but not a biggie.
Probably the best to be fixed by something like https://github.com/GoogleCloudPlatform/prometheus-engine/pull/663

Ok, actually we have chicken and egg problem with main until releases happen or no breaking changes are there. Even with https://github.com/GoogleCloudPlatform/prometheus-engine/pull/1147 which fixes readonly problem we now merged reduced permissions. Users should use release branches instead, let's update docs instead.

repo: GoogleCloudPlatform/prometheus-engine


text:
Instructions for installing ASM and ACM

installation instructions
configuration files
content for the root and namespace repos

@googlebot I consent.

authors: dkassab rutalreja-deloitte


text:
Aws sdk go v2

Moved to AWS SDK GO V2 from V1. Major reason for that is superior handling of the SDK configuration with package external (more info: https://aws.amazon.com/blogs/developer/aws-sdk-for-go-2-0-developer-preview/). It'll hopefully solve #284 because of better auth handling + solves auth issues I was also experiencing because of simplistic V1 auth implementation.
During refactoring changed some of the remaining requests to support pagination. Also added debug mode (requested in #295) to see requests to AWS to analyze potential errors and fixed ECS bug (#296 )

Thanks!

authors: meshuga sergeylanzman

repo: GoogleCloudPlatform/terraformer


text:
fix: Params for connector_dataflow YAML & JSON sample codes

Fixes #177

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

/gcbrun

repo: GoogleCloudPlatform/workflows-samples


text:
Update porch-controllers use of the Kpt Fn SDK

This PR changes the porch-controllers binary to use its own go.mod, and updates to the latest Kpt Function SDK.
By using a separate go.mod, we don't have to update all the compiled in functions and other areas.
cc @yuwenma @mortent @natasha41575

So, go mod tidy removed the Azure mods, but now the build is failing. Nested go modules :(

repo: GoogleContainerTools/kpt


text:
The homepage trams

The space around the trams that is clickable is a bit to big. It makes it hard to get to the drop down menu for quizes sometimes.

Fixed in #229

authors: Viktormes signealfonson

repo: Goteborgs-guiden/Gotehenburg-guide


text:
[Bug]: Accordion content padding missing

Describe the bug
The accordion has a span of 623px to 624px where the padding disappears according to the @container self. So when resizing the screen there is one point in which the content jumps around.
@container self (max-width: 623px) {     .content.svelte-1j9i5d0.svelte-1j9i5d0 {         padding: 1.5rem;     } }
@container self (min-width: 624px) {     .content.svelte-1j9i5d0.svelte-1j9i5d0 {         padding: 1.5rem 2rem 1.5rem 3.5rem;     } }

Provide Code
No response
To Reproduce
Add a GoAAccordion to a screen with some content that has background color.
Resize the Screen.
I'm working on a <GoAOneColumnLayout><GoAPageBlock width='800px'><GoAAccordion headingSize='medium' heading='Test'><GoAContainer type='non-interactive' accent='filled' padding='compact' width='full'>
Empty
</GoAContainer></GoAAccordion></GoAPageBlock></GoAOneColumnLayout> and the page as responsive of 687px
Relevant console log output
No response
What browsers are you seeing the problem on?
No response
Additional context
No response

I would recommend using the @container self (max-width: 623px) { .content.svelte-1j9i5d0.svelte-1j9i5d0 { padding: 1.5rem; } }
as a default styling so no need to use max-width and add the changes to the left and right on this @container self (min-width: 624px) { .content.svelte-1j9i5d0.svelte-1j9i5d0 { padding: 1.5rem 2rem 1.5rem 3.5rem; } }

I spoke with @AndreFilipeNavesDeBarros , and while I can't replicate this issue, it might just be due to my playground setup. He's willing to work on this issue

Ok so I played around with the code and here is what I did:

on the vite.config file I added, because I need a mobile type that the max was the not-mobile min.

        postcssReplace({
          pattern: /\(--up-to-not-mobile\)/g,
          replaceWith: "(max-width: 624px)"
        }),

Then I changed the Accordion.svelte I just moved some of the styles around so here it is the final for each.

  .title {
    display: flex;
    flex: 1;
    align-items: center;
  }
  .content {
    border-bottom: var(--goa-border-width-s) solid
      var(--goa-color-greyscale-200);
    border-left: var(--goa-border-width-s) solid var(--goa-color-greyscale-200);
    border-right: var(--goa-border-width-s) solid var(--goa-color-greyscale-200);
    border-bottom-left-radius: var(--goa-border-radius-m);
    border-bottom-right-radius: var(--goa-border-radius-m);
    padding: 1.5rem;
  }
  @container self (--up-to-not-mobile) {
    .title {
      flex-direction: column;
      align-items: flex-start;
    }
  }

  @container self (--not-mobile) {
    .content {
      padding-left: 3.5rem;
      padding-right: 2rem;
    }
  }

authors: AndreFilipeNavesDeBarros ArakTaiRoth

repo: GovAlta/ui-components


text:
Angular Material - SCSS compilation has errors when using @use or @import rules

Migrated from GitLab:
Original Reporter: @waltermesquita
Summary
I tried to use @use and @import rules in the stylesheet in the Angular Material Experimental Accordion Header component but both rules create compilation errors when using the build:angular-material-components script (and also the storybook run)
Steps to reproduce
@use error
@use './../../lib/styles/ads-core.scss';
.something {
  border-width: ads-core.$unit;
}

✖ Compiling TypeScript sources through NGC
ERROR: Invalid CSS after "...width: ads-core": expected expression (e.g. 1px, bold), was ".$unit;"
Invalid CSS after "...width: ads-core": expected expression (e.g. 1px, bold), was ".$unit;"
@import error
@import './../../lib/styles/ads-core.scss';
.something {
  border-width: $unit;
}

ERROR: Invalid CSS after "  color: colors": expected expression (e.g. 1px, bold), was ".$primary;"
Invalid CSS after "  color: colors": expected expression (e.g. 1px, bold), was ".$primary;"
Environment
development (branched from next)
chrome browser
What is the current bug behavior?
compilation errors
What is the expected correct behavior?
compiles correctly
Relevant logs and/or screenshots
see reproduction section
Possible fixes / Bugfix branch

(link to bugfix branch or file/line of code believed to be problem)

This is on the old version which is no longer being maintained. Will not do.


text:
don't fail if server includes ip or hostname in header.

Tweak regex to allow an optional hostname or IP in header.  Some sources (like a Palo Alto Firewall) don't do native CEF and end up including extra Syslog baggage.  Regex throws away this data anyways but allows   processing to continue.  Also include two new tests for this condition.    For completeness, instructions for reformatting Palo Alto Syslog stream in CEF format are here:
https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/technical-documentation/cef/pan-os-70-CEF-guide.pdf
msg= field from their templates needs to be moved to the end of the line to keep this parser working as expected.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Gianni D'Aprile seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

This can be solved using processing pipeline steps since the v1.2.0 release of the CEF plugin. See: https://github.com/Graylog2/graylog-plugin-cef/blob/master/README.md#usage


text:
🛑 Server Ultra is down

In 0731fbb, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 403
Response time: 1430 ms

Resolved: Server Ultra is back up in 4e43391.

repo: GreathostRo/upptime


text:
🛑 Server Gaming is down

In 0660d24, Server Gaming (https://game.greathost.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server Gaming is back up in 439f0b6.


text:
Please rename this tool

Tools should not be named after style guide PEPs. A style guide is a document written for humans, and has lots of subtlety. Issues caused by the rigidity or simplicity of the tool end up causing pointless discussion about the letter of the PEP, as if it was a law, which was never the intention of the PEP. If you want to write a tool that checks style, please give it some clever name, don't name it after a PEP, so it's clear that whenever humans don't like what the tool says, it is a tool issue, not an issue with the PEP (which is merely intended to guide humans, not to require them to follow it every time).

Thanks for speaking out about this. We'll change the name of the command-line tool, of the repository, and of the PyPI package. However, if you don't mind, we'll keep the old ones working for backwards-compatibility.

Thanks for being flexible! FWIW I am happy that this tool exists -- it's just the name I object to. :-)

This might be a good place to discuss the new tool name!
I checked PyPI for the following names and they are available:

pydoc
doclint
checkdoc
docstring-lint

I personally lean towards doclint, but please share your ideas and thoughts about this.

How about pydoclint? A bit long but clear on the scope, since it's
primarily a command-line utility -- and it follows the pattern of pylint
and pytest.

pydoclint sounds like something that will lint your documentation, not docstrings.
pydoc can't be used because that's something Python installs (e.g., pydoc optparse brings up the documentation for optparse)
pydocstrings would be my vote. Again, long but (IMO) more explicit than the other options provided other than docstring-lint.

Although my contribution to the package was minimal I would like to add my thoughts too:

pypep257lint - it might be against the intention of this issue;
pylint257 - it still refers to PEP257 :wink:;
pydoclint - it is my personal favorite;
pydust, pyfluff - just some wild ideas ...

On January 5, 2016 11:47:58 AM CST, Jiri Kuncar notifications@github.com wrote:

Although my contribution to the package was minimal I would like to add
my thoughts too:

pypep257lint - it might be against the intention of this issue;

Right. I think Guido wants us to avoid pep in the name altogether.

pylint257 - it still refers to PEP257 :wink:;

But is very tired to the name PyLint which we should avoid

pydoclint - it is my personal favorite;

I still think this is to vague but I'm not against it.

pydust, pyfluff - just some wild ideas ...

Reply to this email directly or view it on GitHub:
https://github.com/GreenSteam/pep257/issues/172#issuecomment-169078385

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

With @keleshev's approval and after speaking with @sigmavirus24, it is decided that the new tool's repository will reside under the PyCQA (Python Code Quality Authority). We'll be in good company with pep8, pylint, flake8, etc.
After we choose a name, I'll update the README here to redirect folks to the new repo and work with @sigmavirus24 on the relocation.

Regarding the name - it seems to my that while pydoclint is a little bit vague (regarding documentation in general as opposed to specifically docstrings), pydocstrings is vague about what it does about docstrings, which seems more confusing to me.

@gvanrossum , are you opposed to this package including a 257 suffix. IMO it should include 257, as it does intend to implement pep257 as best as software and time/energy of developers permits.
I feel pydoclint has an incorrect scope.  pydoc is already tightly coupled with pep 258 .  pep 258 explicitly allows different syntax/style/etc and non-English language with __docformat__.  I would strongly support an increased scope of this package which included parsing __docformat__ and reacting accordingly, such as disabling English specific checks when a non-English language is indicated, and doing rst syntax checking if the __docformat__ indicates the docstring format is rst.
As they are coming under one umbrella, why not name them consistently, such as

pycqa8 and pycqa257
pycq8 and pycq257
flake8-core and flake257

pydocstrings is vague about what it does about docstrings, which seems more confusing to me.

Agree. How about pydocstringlint? (im not a fan, as it is very long..)
I like @jirikuncar's pyfluff , but I feel it would also need some additional name component that indicates it is implementing pep 257. fluff doesnt strongly indicate that it is docstring related. Adding -docstring is very long and adds a bland part to the name.
Some other plays on 'pep':

epp257 (where epp could stand for something like electronic pep purifier,  ...) - conflicts with https://en.wikipedia.org/wiki/Extensible_Provisioning_Protocol / https://pypi.python.org/pypi/EPP
dull257 (pep means enliven)
pepper257 (pep is an abbreviation of pepper)
spice257
zest257
zap257
dsd, docstring_doctor, docstring_dr
redocstring
pydeknot

As they are coming under one umbrella, why not name them consistently, such as

pycqa8 and pycqa257
pycq8 and pycq257
flake8-core and flake257

I have no clue what you're talking about. The PyCQA is merely an organization for similar/like-minded/related projects to live in. This also allows us to make sure there are enough maintainers in case someone goes AWOL. Are you proposing naming tools that are loosely associated after the organization itself?
Of your options, @jayvdb, pepper257 is interesting but I think it might cause confusion with:

https://pypi.python.org/pypi/pepper
https://pypi.python.org/pypi/pepper8
https://pypi.python.org/pypi/pepper_kinematics

What about:

check257
checkdocstrings or check-docstrings

I'm sorry, folks, the whole point of this issue is to not tie the tool's
name directly to the PEP's name. Keeping 257 as part of the name defeats
that for me. It should be crystal clear to users of the tool that when they
perceive a difference between the tool and the PEP they should talk to the
tool's developers (who then in turn might ask the PEP authors for
clarification -- but often the PEP is intentionally vague when there's an
issue that's not easily captured in a simple rule or where reasonable
people can disagree).

Guido, the tool currently provides a --convention flag where the user can choose an option for a known convention, such as pep257, numpy, etc.
Would keeping this option be problematic in your opinion? I do think that there is a rational in wanting to follow an official style guide.

pycqa257doc with --convetion (pep257|numpy) option sounds like good candidate to me.

pros: short, no 257 in name so Guido might be happy, 'doc' in name should give us enough freedom to implement other styles and checks;
cons: missing 'strings' it might confuse users.

Another cool name is dsd/ddr (Docstring Doctor) as @jayvdb proposed.

If we're looking at such a short name, distributions will have problems packaging the project. We should at least make it pydsd or pyddr.
On January 6, 2016 2:50:41 AM CST, Jiri Kuncar notifications@github.com wrote:

pycqa257doc with --convetion (pep257|numpy) option sounds
like good candidate to me.

pros: short, no 257 in name so Guido might be happy, 'doc' in name
should give us enough freedom to implement other styles and checks;
cons: missing 'strings' it might confuse users.

Another cool name is dsd/ddr (Docstring Doctor) as @jayvdb proposed.

Reply to this email directly or view it on GitHub:
https://github.com/GreenSteam/pep257/issues/172#issuecomment-169269291

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I have no issues with using pycqa in tool names but I don't think that's clear to users or helpful in naming things.

That --pep257 option is fine. I always assumed that PCQA was an ironic
name, not something to use in the tool. To me, pydoclint or pydocstyle
sound best, but its your tool!
--Guido (mobile)
On Jan 6, 2016 7:07 AM, "Ian Cordasco" notifications@github.com wrote:

I have no issues with using pycqa in tool names but I don't think that's
clear to users or helpful in naming things.
—
Reply to this email directly or view it on GitHub
https://github.com/GreenSteam/pep257/issues/172#issuecomment-169347845.

Yeah PyCQA was a joke on the code-quality mailing list. (Much like PyCA, PyPA, etc. are not meant to be serious).

Also as part of the move of the project to the PyCQA, I think it will be cleaner if what we do is leave this repository exactly as it is with the exception of a notice of its deprecation in favor of whatever we end up calling the new project. The same notice should be published to the pep257 PyPI project with perhaps the final release being a meta-package that points people to installing "new-tool" the same way the py.test package points people at installing pytest.
The new project should effectively be a fork of this project but perhaps without the GitHub link between the two so there's no confusion as to the origins of the PyCQA project.
Alternatively, we can "move" this project via GitHub and then have GreenSteam fork it as "pep257" with the same notice. GitHub would handle redirects for us (from GreenSteam/pep257 -> PyCQA/"new name") so we don't actually need to preserve this if we'd also like to preserve the issue history in the PyCQA project. How that's handled, however, is between @Nurdok and @keleshev. I'm just offering options :)

But why not use GitHub's redirection facilities? If you rename + give away
the project, anyone going to the current project URL will be redirected to
the new repo. IMO that's cleaner than forking (some folks will miss the
notice in the README, you have two trackers, etc.)

@gvanrossum yeah, I know there was some discussion of "GreenSteam/pep257" still being a repository though. That's why I offered the other options to make that continue to be a thing. Further, any fork can turn off issues and have a bot to auto-close pull requests with a friendly message. I personally prefer the simple redirection method but that's just me.

I don't want PyCQA in the new name. It's enough to be under the PyCQA organization.
All suggestions with pep257 or 257 in them defeat the purpose.

Right now, pydoclint is my favorite, with pydocstyle as a runner up. The docstring doctor names are cute, but too long to say, IMO. I'll give it a day or two to settle in before I decide :)

I registered pydocstyle on PyPI, following discussion on the pep8 thread. @keleshev do you object transferring GreenSteam/pep257 to PyCQA? You said you wanted to create a new repository and link to it from the old one, but @gvanrossum suggests that Github's redirection facilities might be a better option. It's your call.

Whoever ends up moving this needs to give me a head's up. I need to make them an owner in the PyCQA so they can transfer the organization. Conversely, they can make me an owner here and I can transfer the repo for you.

Using GitHub redirection facilities seems like a good choice, so that https://github.com/GreenSteam/pep257 will redirect to the new repo. However, I guess that many know this project by its current name, and not by the repo link, so they will be googling something like pep257 tool and not finding the repo. That's why I thought that keeping this repo as it is with a huge disclaimer "THIS REPO IS SUNSET, USE PYDOCSTYLE INSTEAD: link" would be more educational for the users and smooth the transition to the new name.
That's my concern, but I'm fine with either way. Don't want to drag this any longer, so @Nurdok—do what you think is best.

@sigmavirus24 We'll go with transfer + rename. Could you give me the permissions?

@Nurdok done.

The repository transfer and rename are done. We're now PyCQA/pydocstyle :ok_hand:
I'll start working on changing the codebase - readme, license, docs, entry points (while still leaving the old pep257 script for now, with a deprecation warning), etc.

I tested the redirect and it works great. :tada: :cake:

I'm sad about this. I think this will mean fewer people use the tool, when it would be better if more people do - or take other steps enforce docstring coverage and conventions, PEP257 or otherwise.
We should make it clear in the README that it is intended to check conformance to PEP257 but is not a reference implementation of said PEP.

@lodagro don't worry, you will still be able to do --convention=pep257, and it will be the default convention.

@Nurdok I think you meant @lordmauve not lodagro ;)

Yep, my mistake (edited).

Done :)

project on openhub renamed
https://www.openhub.net/p/pydocstyle

authors: Nurdok gvanrossum jayvdb jirikuncar keleshev lordmauve sigmavirus24


text:
Missing option to set LOCALIZE_LOCAL_STORAGE value

It would be nice to have an option to set value for localStorage key.

Noted. I will try to add this as an configuration.

authors: meeroslav mrzepinski

repo: Greentube/localize-router


text:
Adding downshift indicator for gear

would be nice to be able to see a color change (of the number) when the gear is dropped
sometimes when you drop a gear, without audio, it's not so easy to notice. on certain maps if i drop a gear the only time i'll notice is when i gear back up

Downshift indicator is already added in Basic and BasicDigital themes:

authors: GreepTheSheep zentred

repo: GreepTheSheep/openplanet-speedometer


text:
Array Type Check?

Feature request: want to know if it is possible for you to add array to the type check when creating a table: array( 'boolean', 'integer', 'string', 'double', 'array' ).
Reason is that since you now have the set method, I would love to be able to do something like this:
$row = Lazer::table('user');

$row->set(array(
    'nickname' => 'user',
    'email' => 'user@example.com',
    'attributes' => [
        'job' => 'Developer',
        'hobbies' => 'basketball, traveling, hiking',
        'favorite_food' => 'pizza'
    ]
));
$row->save();

@parkerj Yes, it is possible to add array type. I will let you know once done.

@anant-svc Awesome, thanks!!!

@parkerj I am working on out of box filter for array type

@anant-svc Ok, thanks for working on this.

@parkerj You can use relations here and store attributes in separate table.

For example:
$users = Lazer::table('user')->with('attributes')->findAll();

foreach ($users as $user) {
   echo 'Name: ' . $user->nickname . PHP_EOL;
   foreach ($user->Attributes as $attribute) {
      echo sprintf('%s: %s', $attribute->name, $attribute->value) . PHP_EOL;
   }
}

authors: Greg0 anant-svc parkerj


text:
This.userId server side

How do you send the token to the server, so that you can access this.userId in the server

You don't need to send token to the server, its the opposite, the server sends a token to the client and associate a current DDP connection with the token. You can use https://github.com/Gregivy/simpleddp-plugin-login for Meteor.Accounts logic.

authors: Gregivy nesbtesh

repo: Gregivy/simpleddp


text:
ci: upload the latest artifacts to 'latest/' directory of S3 bucket in scheduled and formal release

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Upload the latest artifacts to 'latest/' directory of S3 bucket in scheduled and formal release. It's easy to download the latest binary from S3 without any GitHub APIs or list operations.
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

Do we need to explicitly remove previous versions under latest?

Do we need to explicitly remove previous versions under latest?

It seems we don't need to remove the previous artifacts.
For now, there are not any binaries stored in latest/. When we use aws cp, it will always force update the binaries.

repo: GreptimeTeam/greptimedb


text:
Use  inner HTML on

This is the object passing to
{                 id: k,                 Name: v.timer_name,                 Impressions: v.impressions,                 Clicks: v.clicks,                 Status: v.timer_status,                 End_Date: v.clicks,                 Actions: `

Copy Code

Edit

Duplicate

Remove

	`             }
Current Output:

The Problem is HTML inside the Actions column isn't rendering and I do not want to show:  griddleKey    column with its data. Please, Help me with this configuration. I cannot see anything in the docs like that.

+1 same issue - could not find a solution yet.

To hidde griddleKey, you need to explicitly list the expected <ColumnDefinition />s. For Actions, try a customComponent that uses dangerouslySetInnerHTML:
const htmlComponent =
  ({ value }) =>

;

class MyGrid extends React.Component {
  render() {
    return (
      <Griddle data={...}>
          <RowDefinition>
            <ColumnDefinition id="id" />
            <ColumnDefinition id="Name" />
            <ColumnDefinition id="Impressions" />
            <ColumnDefinition id="Clicks" />
            <ColumnDefinition id="Status" />
            <ColumnDefinition id="End_Date" />
            <ColumnDefinition id="Actions" customComponent={htmlComponent} />
          </RowDefinition>
      </Griddle>
    );
  }
}

@dahlbyk  Hey Thanks for your help, Can I use Object , Array instead of customComponent ?

I don't understand the question. customComponent is the prop you use to specify how a column value should be rendered. If your column value is an Object or an Array, you can teach your customComponent to render from that.

authors: MahbbRah dahlbyk mpolinowski

repo: GriddleGriddle/Griddle


text:
Don't rely on global Griddle

Not sure if this is the best solution, but it work and I don't want to mess with circular dependencies

Thanks!

authors: ryanlanciaux vkurchatkin


text:
🛑 peerscountries API endpoint is down

In ed90a07, peerscountries API endpoint (https://grinnode.live:8080/peerscountries) was down:

HTTP code: 503
Response time: 571 ms

Resolved: peerscountries API endpoint is back up in e6e3d82.

repo: Grinnode-live/upptime


text:
Leverage EventChannel to listen for the system accent color

Currently, we are hardcoding the bizarrely-named MacosColors.controlAccentColor, which is the user's selected system accent color. (Obviously this name doesn't make much sense, but that's what Apple calls it...).
Obviously, someone making a macOS application would expect that their choice of system-level accent color would be reflected in their application unless explicitly overridden. Since macos_ui is now a plugin, we can leverage Flutter's EventChannel to listen to the native controlAccentColor's value.
This would require some refactoring to MacosColors since controlAccentColor is a static value. I'm not quite certain the best way to proceed with this at this time.

Could this be of any help?

Also, a more complete way of getting the accent color.

Also, a more complete way of getting the accent color.

Okay, I have done a first pass on this feature via the code found above. It should be noted that this is done through MethodChannel, though, not EventChannel. I tried doing that and I kept getting null back for the color. See this gist for more on that attempt.

authors: GroovinChip whiplashoo


text:
🛑 Homepage is down

In fe91462, Homepage (https://www.dlya.top) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Homepage is back up in d11bb92.

repo: Guangsudalao/uptime


text:
Back repo as GDExtension

[ ] Implement AnimationNodeExtension in godot
[ ] Fix builds of MMAnimationNode
[x] Fix CI

https://github.com/godotengine/godot-cpp-template is useful!

@GuilhermeGSousa I propose we go in this order:
AnimationNodeExtension
There is a race to get this into the Godot Engine 4.4 version.
Bone features
While we wait, we can develop the bone feature.
godot-motion-matching GDExtension
When AnimationNodeExtension is in the Godot Engine master branch, we can work on this.

@fire I have some work done in godot, I needed these changes to be able to start testing things
https://github.com/godotengine/godot/pull/99181

Which version of Godot 4 will work with this GDectension?

Whichever version has this change
https://github.com/godotengine/godot/pull/99181
so probably 4.5? I dunno

Not to be unfair to you, if you could provide windows exe of this version, we could continue to follow your demo. Just a feedback

authors: GeorgeS2019 GuilhermeGSousa fire

repo: GuilhermeGSousa/godot-motion-matching


text:
Optimal Power Flow (OPF)

Description
Implements mod #42
Checklist

Implementation:

[ ] Implementation of the Mod in the gurobi_optimods installable package
[ ] Tests for the Mod implementation in tests/
[ ] Docstrings for public API, correctly linked using sphinx-autodoc
[ ] Restructure the current file structure to fit into the optimod style
[ ] Possibly restructure functions and methods

Documentation page:

[ ] Problem specification with description tab and optimzation model tab
[ ] Example of the input data format (use gurobi_optimods.datasets for loading data)
[ ] Runnable code example
[ ] Presentation of solutions

Still to do in the code:

[ ] TestOpf.test_settings isn't fit for CI, needs to be cut down to a more reasonable set to be useful. It also seems to be dependent on a parameter file.
[ ] Clean up dead code like opf.grbformulator.writemipstart
[ ] Get rid of "gurobiparamfile", solver parameters are better off being handled using optimods infrastructure
[ ] Find and fix unsafe function definitions like this one in solve_opf_model:

def solve_opf_model(..., additional_settings=dict())

Still to do in the docs:

[ ] Link to API reference, update API docstrings to numpydoc style
[ ] ACOPF/DCOPF pages still contain template sentences
[ ] Main docs page needs background. The current structure is terminology -> references -> mat.
[ ] Solutions need to be presented in the docs
[ ] Other API functions need to be demo'd in the docs, so far only solve_opf_model is shown

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Jaromil Najman:x: derdanoJaromil Najman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing in favour of #108

authors: CLAassistant JaromilNajman simonbowly

repo: Gurobi/gurobi-optimods


text:
Contributer

Description
Please include a summary of the changes and the related issue(s) this pull request addresses. Include any relevant context or background information.
Fixes: #[issue_number] (replace with the issue number, if applicable)
Use [x] to represent a checked (ticked) box.✅
Use [ ] to represent an unchecked box.❌
Type of Change

[yes ] Profile Added
[ ] Project Added
[ ] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other (please specify):

How to Test
Provide a brief description of how to test your changes. Include steps, commands, or screenshots if necessary.

Step 1
Step 2
Step 3

Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation (if applicable).
[ ] My changes generate no new warnings.
[ ] I have added tests to cover my changes (if applicable).
[ ] All new and existing tests pass.

Additional Notes
Please add any other information that is relevant to this pull request, including potential risks, alternative solutions considered, or future improvements.

You have not added your profile in between other people's profiles according to the contribution guidelines.
Read again the contribution files.

Sir i have made the necessary changes as per the contribution guidelines.

authors: Gyanthakur anushkabhansalii

license: Unlicense


text:
Update image_list.md

Minor change to the additional info lead-in

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

authors: CLAassistant philip-menzies

repo: HCL-TECH-SOFTWARE/digital-experience


text:
🛑 SkipTheCommericals is down

In d4f28ad, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in eba2eec.

repo: HDVinnie/TrackerHub