text:
D2_COTD Multiplizität Issue

D2_COTD Framework Concept Definition Viewpoint
https://saf.gfse.org/devdoc/SAF Development Domain/Framework Concept Definition Viewpoint.html
Bitte die Multiplizität des SE Concept Elements abhändern in [1] ... [1..*]. Ein SE Concept Baustein kann mit vielen in Verbindung stehen.
Anlage

Am 3. November 2024 22:31:05 MEZ schrieb Christian Lalitsch-Schneider @.***>:

D2_COTD Framework Concept Definition Viewpoint
https://saf.gfse.org/devdoc/SAF Development Domain/Framework Concept Definition Viewpoint.html
Bitte die Multiplizität des SE Concept Elements abhändern in [1] ... [1..*]. Ein SE Concept Baustein kann mit vielen in Verbindung stehen.
Anlage

--
Reply to this email directly or view it on GitHub:
https://github.com/GfSE/SAF-Specification/issues/77
You are receiving this because you were assigned.
Message ID: @.***>
Da steht schon * .. *.
Das heißt any .. any

Ist m.E. eine spitzfindigkeit (bei selbstreferentiellen Relationen) ob man da 1-- 0..* oder 1 - * oder * - * schreibt.
Alles besagt das beliebige Beziehungen existieren können aber nicht müssen.
Und genau das ist gemeint.
Gruß,
Alexander

Mit ist noch etwas anderes aufgefallen:
Es fehlen folgende Aussagen

Wir können Relationen auf Relationen abbilden

Eine spezielle Relation ist die Spezialisierung.

Diese Möglichkeiten sollte man m.E.  sichtbar machen. Dann kann man sich im Profildiagramm darauf beziehen.

Ich ziehe die Eindeutigkeit der Lesbarkeit / Definition immer Spitzfindigkeiten wie "any" vor. Rahmenwerk Regeln sind nur auf Basis eindeutiger Definitionen zu definieren.
Kann es überhaupt den Fall geben, dass SE Concept keine relation zu anderen SE Concepts aufweist? Was wäre ein Beispiel? Ist der Fall sinnvoll und im Rahmen der SE Ontologie Definition beachtenswert?

authors: clalitsc haarer

repo: GfSE/SAF-Specification


text:
🛑 MCSkinHistory is down

In 4e6e232, MCSkinHistory (https://mcskinhistory.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCSkinHistory is back up in 6f319b2 after 1 hour, 12 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 MCSkinHistory is down

In 5aa685b, MCSkinHistory (https://mcskinhistory.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCSkinHistory is back up in 983fb2b after 24 minutes.


text:
Should the RuntimeIdentifiers property osx change to osx-x64?

https://github.com/Giorgi/DuckDB.NET/blob/18decabf2e794881af4c566982aaa6ff4106eef0/DuckDB.NET.Bindings/Bindings.csproj#L7
https://github.com/Giorgi/DuckDB.NET/blob/18decabf2e794881af4c566982aaa6ff4106eef0/DuckDB.NET.Bindings/Bindings.csproj#L24
According to rid-catalog#macos osx-x64 is macOS RIDs

Drafted modifications on #202

In that case I would need to have osx-x64 and osx-arm64 which probably means including libduckdb.dylib twice in the NuGet package.

I haven't looked into Native AOT yet. I'll close this issue and we can come back to it if needed.

Ok

authors: Cricle Giorgi


text:
All Clear Message Missing in 1.14

Environment

ggshield version: 1.14.2
Operating system (Linux, macOS, Windows): macOS
Operating system version: 12.6
Python version: 3.10.8

Describe the bug

Configure GGShield as pre-commit hook
Execute a git commit that does not include a secret

Actual result:
No output from GGShield indicating a clean scan
Expected result:
In previous versions the following message would be displayed:

No secrets have been found

Hello @rgajason,
Thanks for reporting this issue.
We indeed recently changed the content of ggshield's output. I understand that this new behavior can be less clear.
We will look into improving this shortly. I will keep you updated on this ticket.

authors: pierrelalanne rgajason

repo: GitGuardian/ggshield


text:
Update README

The goal of this PR is not to deep dive in to revamping the README, but simply to rename the env variable's name for GitGuardian API key to make it similar to the one used in ggshield.

Codecov Report

Merging #77 (28fe4c6) into master (3892245) will not change coverage.
Report is 3 commits behind head on master.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   92.18%   92.18%
=======================================
  Files           6        6
  Lines         614      614
=======================================
  Hits          566      566
  Misses         48       48

Flag
Coverage Δ

unittests
92.18% <100.00%> (ø)

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

Files
Coverage Δ

pygitguardian/__init__.py
100.00% <100.00%> (ø)

pygitguardian/client.py
79.82% <ø> (ø)

source: gharchive/pull-request

authors: codecov-commenter pierrelalanne

repo: GitGuardian/py-gitguardian


text:
🛑 twoc is down

In 58fbd1a, twoc (twoc.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: twoc is back up in 61678d9 after 30 minutes.


text:
🛑 alkon is down

In 340a182, alkon (alkon.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alkon is back up in d50b0a1 after 49 minutes.


text:
🛑 orkut is down

In 0deeb00, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 1722a15.


text:
🛑 orkut is down

In 23ae6f1, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 63ece1d.


text:
🛑 diodosled is down

In d06d3d5, diodosled (diodosled.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: diodosled is back up in 3fac162.


text:
🛑 orkut is down

In 225c773, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 4671ae7.


text:
🛑 orkut is down

In 72cbda0, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in b8fd3c1.


text:
🛑 zshareblog is down

In 00488eb, zshareblog (zshareblog.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: zshareblog is back up in f738ef2.


text:
🛑 hcr is down

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

HTTP code: 401
Response time: 1060 ms

Resolved: hcr is back up in ca8cb35.


text:
🛑 hcr is down

In 0d2846b, hcr (hcr.co.uk) was down:

HTTP code: 401
Response time: 716 ms

Resolved: hcr is back up in 2c47732.


text:
🛑 orkut is down

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

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 0f48379.


text:
🛑 hcr is down

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

HTTP code: 401
Response time: 729 ms

Resolved: hcr is back up in 4fdb69c.


text:
🛑 orkut is down

In 2d97ffb, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 69de0dd.


text:
🛑 orkut is down

In 3806edc, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in d9f2563.


text:
🛑 orkut is down

In 94cfc61, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in c72917c.


text:
🛑 ojolink is down

In f62afef, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 454 ms

Resolved: Ojolink is back up in a8518bb.


text:
🛑 orkut is down

In 755c7e2, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 697 ms

Resolved: orkut is back up in 5548e94.


text:
🛑 163 is down

In 96b6af8, 163 (163.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 163 is back up in d44ec48.


text:
🛑 bluewin is down

In 431a30f, bluewin (bluewin.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: bluewin is back up in 72b8665.


text:
🛑 ojolink is down

In 78a3421, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 459 ms

Resolved: Ojolink is back up in 35e8987.


text:
🛑 orkut is down

In 1bc34bc, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 733 ms

Resolved: orkut is back up in e36e868.


text:
🛑 163 is down

In 77118ec, 163 (163.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 163 is back up in d4c4c75.


text:
🛑 ojolink is down

In 566cd03, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 407 ms

Resolved: Ojolink is back up in 27fabaa.


text:
🛑 orkut is down

In 99bc8a7, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 1155 ms

Resolved: orkut is back up in 047f06c.


text:
🛑 ojolink is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 1fb606d.


text:
🛑 ojolink is down

In 11b7eb7, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in c5d73bc.


text:
🛑 ojolink is down

In 3db35d9, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 4d5bf15.


text:
🛑 ojolink is down

In 40c4431, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 612a583.


text:
🛑 ojolink is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in de37614.


text:
🛑 ojolink is down

In 615f2a3, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 5701263 after 13 minutes.

Resolved: Ojolink is back up in 2e06620 after 31 minutes.


text:
🛑 uzboys is down

In 4307843, uzboys (uzboys.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: uzboys is back up in 099b8c3 after 20 minutes.


text:
🛑 twoc is down

In 2a6b5a2, twoc (twoc.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: twoc is back up in 357aece after 2 hours, 28 minutes.


text:
🛑 orkut is down

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

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 25137a8.


text:
🛑 ojolink is down

In 376a911, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 9d63d9d after 9 minutes.


text:
🛑 detonics is down

In 64d20a2, detonics (detonics.com) was down:

HTTP code: 403
Response time: 339 ms

Resolved: detonics is back up in 1ee3562.


text:
🛑 ojolink is down

In 0cff801, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 96f48a2 after 28 minutes.


text:
🛑 orkut is down

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

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in bfc10c2 after 9 minutes.


text:
🛑 Wide6 is down

In dd8907c, Wide6 (Wide6.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wide6 is back up in e25727e after 17 minutes.


text:
🛑 orkut is down

In 3a8b3bc, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 34e994f.


text:
🛑 orkut is down

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

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 7a54a9b after 14 minutes.


text:
Nothing is happening

when I run the following from Project A it ran perfectly, but when I copy pasted it into Project B nothing happens, even the showLog method is not called.

Context context = requireContext();
View voew = LayoutInflater.from(context).inflate(R.layout.layout_invoiceitem,null);
PdfGenerator.getBuilder()
.setContext(context)
.fromViewSource()
.fromView(voew)
.setCustomPageSize(500,1000)
.setFileName("testbeta4")
.setFolderName("FolderB")
.openPDFafterGeneration(true)
.build(new PdfGeneratorListener() {
@Override
public void onFailure(FailureResponse failureResponse) {
super.onFailure(failureResponse);
}
@Override
public void showLog(String log) {
super.showLog(log);
}
@Override
public void onSuccess(SuccessResponse response) {
super.onSuccess(response);
}
});

Do you attached debugger in onSuccess(SuccessResponse response) and onFailure(FailureResponse failureResponse)  also? please check it.

@Gkemon You are correctI was not giving the necessary permissions.  I was not putting  in the android manifest. Thanks!

You are welcomed and also thank you for testing.

Hi @pierrekhouryy
Thank you all for the support. Please kindly star and fork and send me the app links you all are using it. If there is no confidentiality then I will list them in my readme.md file.

authors: Gkemon pierrekhouryy

repo: Gkemon/Android-XML-to-PDF-Generator


text:
page becomes mess

After creating pdf page view becomes complete mess
 PdfGenerator.getBuilder()
            .setContext(lActivity.this)
            .fromViewIDSource()

            .fromViewID(GattDetailActivity.this, R.id.scrollview)
            .setCustomPageSize(	720,1280)
           // .setDefaultPageSize(PdfGenerator.PageSize.A4)
            .setFileName("Report")
            .setFolderName("Report")
            .openPDFafterGeneration(true)
            .build(new PdfGeneratorListener() {
                @Override
                public void onFailure(FailureResponse failureResponse) {
                    Toast.makeText(Activity.this, "Error！" + failureResponse.getErrorMessage().toString(), Toast.LENGTH_SHORT).show();
                    super.onFailure(failureResponse);

                }

                @Override
                public void showLog(String log) {
                    super.showLog(log);
                }

                @Override
                public void onSuccess(SuccessResponse response) {
                    super.onSuccess(response);
                    // Toast.makeText(Activity.this, response.toString(), Toast.LENGTH_SHORT).show();
                }
            });

please help

Dose it in scrolling layout?

Hi Sanu, deepak , Good day.  please check my new release named  v.2.0 and let me know that is it working or not. Thank you. If it doesn't work then knock me again kindly.

Hi @dondeepak
Thank you all for the support. Please kindly star and fork and send me the app links you all are using it. If there is no confidentiality then I will list them in my readme.md file.

authors: Gkemon dondeepak


text:
Raster data getter/setter methods

Closes #24
get_data() and set_data() methods added to the Raster class.
I put a low level check in set_data that makes sure new data array is the same shape as the existing one. I'm not sure that addresses the check that @atedstone discussed in his issue - Ted will you review and let me know?
I'm also a bit confused as to how this set_data() method conflicts with the purpose of _update(), which seems to update the original file with new data. I'm pretty sure that is distinct from the goal of set_data(), but again, @atedstone, let me know.
I changed the tests accordingly and those are passing on my machine.
Note that this will probably break people's existing code that lives outside of GeoUtils.

Note that it is preferable to use _data rather than __data. In the latter case, the Python interpreter would rename it _Raster__data, making it unavailable for child classes. See example below.

Thanks for bringing this across the finish line!

authors: adehecq elischwat

repo: GlacioHack/GeoUtils


text:
Wrong position of an image

Hi. Sorry if you already are aware of the existence of this pb.
With the very last deliveries i noticed in an Android Build a pb with the position of the image of a unit in the activation window. There was no pb with a windows Build.

Nice find, thank you!  The anchor point was fixed instead of using the top left of the container.  Any aspect ratio wider than 16:9 would cause the misplaced icon image that you're seeing.


text:
LDC2 invalid operand for instruction

If you try to connect a signal _input_event of a CollisionObject in this case an Area, it won't compile with ldc 1.10, but works with dmd.
example
abc@abc-pc ~/Documents/Projects/godot/stu % dub --parallel --compiler=ldc
Performing "debug" build using ldc for x86_64.
godot-d 0.0.6: target for configuration "library" is up to date.
stu ~master: building configuration "library"...
/home/abc/.dub/packages/godot-d-0.0.6/godot-d/src/godot/d/register.d(128,10): Deprecation: module `godot.d.script` member NativeScriptTemplate is not visible from module app
<inline asm>:2:14: error: invalid operand for instruction
                                                        callq %rax;
                                                              ^~~~
<inline asm>:5:19: error: invalid operand for instruction
                                                        movl %edx, %rcx;
                                                                   ^~~~
LLVM ERROR: Error parsing inline asm

ldc failed with exit code 1.```

Fixed in v0.0.7. The LDC-specific assembly here was broken from the beginning, but it's no longer needed since LDC ~1.9.0, which fixes the compiler bug the assembly was supposed to work around.

authors: Supatier sheepandshepherd

repo: GodotNativeTools/godot-d


text:
Remove Distorted Screenshots for Certain Instances

These don't gel with the design, let's remove these. If we don't have a badge for an instance or group, we can just use a ? badge.
I'll work on creating more badges. The squished & distorted images look awful.

Also please provide a list of instances / groups where we don't have badges. I think it's mostly just PVP groups?

2v2, 3v3, 5v5, and all battlegrounds are the only ones I've seen @Gogo1951, but for now they are back to just using our ? icon

we could also just use the pvp icon for those and call it a day, dont think we need new badges for each bg/arena

we could also just use the pvp icon for those and call it a day, dont think we need new badges for each bg/arena

did this


text:
[FEAT] 能做一个游戏图标页面的滑动进度保存吗

每次进了游戏页面修改封面，一返回，又跳到第一行了，然后要重新找这个游戏，确实挺不方便的

这个确实不方便，目前想法是在游戏库界面可以直接双击点入对应的游戏编辑界面，应该会方便不少

我觉得可以考虑类似浏览器那样，出来个新标签页，这样就不会影响游戏库的页面滑动进度。要不就类似电脑的硬盘文件系统那样，退回来的时候还是原来滑动的位置

解决起来挺简单的，只需要在Page中加一行：
NavigationCacheMode="Required"

即可

这个功能在最新发布的1.6.1版本实装啦，非常感谢建议~

话说是不是该关了


text:
Kernel Panic on macOS Catalina 10.15 Beta1 (19A471t)

First of, thanks for providing such a kext for showing memory slots. I really like this feature.
After upgrading to macOS Catalina 10.15 Beta1 (19A471t) this kext causes a kernel panic during the system startup.
I've already used LiluBetaall to force all plugins to load.
I'll upload an image of the panic later.
Hope this issue will be solved soon.
Thank you very much!

I can look into it. Would you be able to provide a screenshot of the panic?

Not so easy. Have created a movie.
IMG_0710.mp4.zip

Should be fixed with 16689b8.

Works now great under Catalina. Thank you for your work.


text:
AI Setup for Bagel

About the PR

Updated Bagel:

Added AI Setup.
Added Cameras so the AI can see.

Media

Requirements

[ ] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Added an AI setup to Bagel.

Summary by CodeRabbit

New Features

Introduced a new job role, StationAi, enhancing job allocation options for players.
Added new SurveillanceCamera entities, improving surveillance mechanics within the game.

Changes

Adjusted numeric identifiers and properties of various game entities for better interaction and gameplay experience.
Removed certain entities, streamlining gameplay and focusing on core mechanics.

merge??

repo: Goob-Station/Goob-Station


text:
(BUG) The deleted accounts are displayed with asterisks on the invite screen

Description: The user has invited friends who deleted the account. The deleted accounts are displayed with asterisks on the invite screen.
Steps to reproduce:

Open the https://goodqa.netlify.app/
Click on the Invite button
Pay attention to the "Friends Who Joined & Need To Claim" section

Expected result:
The deleted accounts are not displayed on the invite screen
Actual result:
The deleted accounts are displayed with asterisks on the invite screen
Environment:  QA 1.11.0-1 // DEV 1.11.6
Devices list: Desktop- Windows 10 // Chrome 87.0.4280.88
Additional info:
email: 1tester8913@gmail.com
pass: Tester_11111

thats not a bug, if user deleted account we cant get his name any more

authors: AnastasiiaOdnoshevna sirpy

repo: GoodDollar/GoodDAPP


text:
Redesign researcher ui 5

Added the Lato font to base.html
Style the "Retrieve task runs" page

Thanks @floraxue for the fast work.

authors: floraxue normangilmore

repo: Goodly/TextThresher

license_source: bigquery


text:
Add min-height:0 to nested column-based flex containers to fix scroll…

… containers on Firefox and Edge
Fixes #165 and #175. Thanks to @dholbert for a concise fix description.

Codecov Report

Merging #176 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #176   +/-   ##
=======================================
  Coverage   60.59%   60.59%
=======================================
  Files          35       35
  Lines        1774     1774
  Branches      135      135
=======================================
  Hits         1075     1075
  Misses        699      699

Continue to review full report at Codecov.

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

authors: codecov-io mdittmer

repo: GoogleChrome/confluence


text:
Add MO & Lazy Props to Accordion

@robdodson @devnook PTAL! Esp. at the architecture around MO!
When merged, set a checkmark in #55 & #85

I think it looks ok but I'm not a mutation observer expert. @azakus I'm sure your'e super busy but if you have any spare cycles to review this mutation observer implementation for an accordion that would be 🎂

authors: robdodson surma

repo: GoogleChrome/howto-components


text:
Rename cacheWillMatch lifecycle event

Library Affected:
workbox-runtime-caching
There's currently a lifecycle method triggered by RequestWrapper.match() called cacheWillMatch(), which gives a plugin the opportunity to inspect the cached response that would normally be returned for a given request, and either return null if the cached response isn't valid (because it's expired, for instance) or return an alternative response instead (like a 206 Partial Content version of it).
There's been some internal discussion about renaming this method in the next major semver release, with cachedResponseWillBeUsed() as the current leading candidate. If folks have alternative suggestions, add them here.

Let's get this in for V2 - everyone seems in favor of this and no complaints found in meeting.

cachedResponseWillBeUsed() as the current leading candidate

To echo internal support for it, 👍. SG to move ahead with it for v2.

I'd like to get #710 merged to v2 first, and then I'll handle this renaming, since that open PR still using the cacheWillMatch() lifecycle name.

authors: addyosmani gauntface jeffposnick

repo: GoogleChrome/workbox

license: mit


text:
build: use JS for cross compatibility

Will leave comments on other places.
Closes #876

No they use the npm run X format.

repo: GoogleChromeLabs/chromium-bidi


text:
Webpack5 Error: Content and Map of this Source is not available (only size() is supported)

Does not support wepback5

v2.0.2 works
v3.0.0 doesn't

Any plans to support webpack v5?

I would be happy to merge a PR to add support, but I don't currently have the bandwidth to do this myself.

repo: GoogleChromeLabs/size-plugin


text:
Size report should ignore map files

I'd still like to generalise this solution, so adding some sort of callback for filtering files would be useful.

closing this one for now,

authors: jakearchibald kosamari

repo: GoogleChromeLabs/squoosh


text:
Code review for two-up, pinch-zoom, trackDragging

You can npm i && npm run start in the components folder to build the test page.
See comments for which files to ignore.

I still need to take a look at setTransform in pinch-zoom, but my brain's tired. I botched a refactor. I need to ensure that transforms can be set before the element is connected, and that bounds are checked when setTransform is called.
Also, bounds should be checked on connect.

Thanks for the review @surma! Good to see some conventions for the rest of the project coming out of this.

Closing this, as I'm rolling the components into master.


text:
fix: throw an error if thread num == 0

Related issue: #20

Actually, given that this is purely invoking JS APIs, let's move this check to startWorkers in https://github.com/GoogleChromeLabs/wasm-bindgen-rayon/blob/main/src/workerHelpers.js and https://github.com/GoogleChromeLabs/wasm-bindgen-rayon/blob/main/src/workerHelpers.no-bundler.js instead.
That will be a bit cheaper, because it won't require few extra roundtrips to JS, and, correspondingly, will also produce slightly smaller output.

Done. And make it throw if one uses a negative thread number.

done

Thanks!

repo: GoogleChromeLabs/wasm-bindgen-rayon


text:
Webpack issue

Hi,
I tried to use it to record live camera stream with a react app. I added a webpack config for the worker :
      {
        //test: /^webm-wor.*/,
        test: /webm-(.*)\.js(\.map)?$/,
        use: { loader: 'worker-loader' }
      }

But I get the following issue :
Child worker:
                             Asset      Size  Chunks                         Chunk Names
    ad9bb12747c6f5c41038.worker.js  60.2 KiB    main  [emitted] [immutable]  main
    Entrypoint main = ad9bb12747c6f5c41038.worker.js
    [./node_modules/path-browserify/index.js] 8.54 KiB {main} [built]
    [./node_modules/process/browser.js] 5.29 KiB {main} [built]
    [./node_modules/webm-wasm/dist/webm-worker.js] 39.8 KiB {main} [built]

    WARNING in ./node_modules/webm-wasm/dist/webm-worker.js
    Module not found: Error: Can't resolve 'worker_threads' in 'C:\Projets\Deepsense\deepsense-js-sdk\node_modules\webm-wasm\dist'
     @ ./node_modules/webm-wasm/dist/webm-worker.js

    ERROR in ./node_modules/webm-wasm/dist/webm-worker.js
    Module not found: Error: Can't resolve 'fs' in 'C:\Projets\Deepsense\deepsense-js-sdk\node_modules\webm-wasm\dist'
     @ ./node_modules/webm-wasm/dist/webm-worker.js 1:579-592

I also edited the 'glue code' manually in webm-wasm.js and set
var ENVIRONMENT_IS_WEB=true; var ENVIRONMENT_IS_WORKER=true;
But it changes nothing.
Do you have an idea about this issue and how to solve the dependency with 'fs' ?
Thanks !
Olivier

It seems like you might be using an old version of Node. Can you try updating it?

Thanks for your prompt reply. Just Great!
I've just updated to the latest version
v12.18.1
But it changes nothing. Same output. Same issue.   (note: my previous node version was not so old : it was v12.13.1)

I’m surprised that webpack want’s to shim fs — I don’t really need it. BUt no, I am not that familiar with webpack so don’t know how to fix this, sorry :(

I'm getting the worker_threads issue in node v14.17.0, @OlivierR1 did you ever fix this or did you move on?

In webpack 5, do:
  resolve: {
    fallback: {
      fs: false,
      worker_threads: false
    }
  }

authors: OlivierR1 surma tony

repo: GoogleChromeLabs/webm-wasm


text:
Additional configuration in the configmaps

Hi Team,
I am trying to understand how to add additional OIDC parameters like below...
OIDCSSLValidateServer Off
OIDCPassIDTokenAs serialized
OIDCRemoteUserClaim email
OIDCAuthNHeader ct-remote-user
OIDCSessionInactivityTimeout 1800
OIDCSessionMaxDuration 36000

RequestHeader set x-forwarded-for "%{HOST}e"
RequestHeader set x-forwarded-proto "https"
RequestHeader set x-forwarded-host "%{HOST}e"
RequestHeader set Authorization "Bearer %{access_token}e"
RequestHeader set X-Requested-With %{REQUEST_URI}s early

# Strip the port from the Location response, assuming the Openshift Route will always have the default port for the schema.
# This is only required because the X-Forwarded-Proto header is missing from the AVI request
Header edit Location "^http(s?):\/\/(.+):[\d]+\/(.*)$" "http://$[HOST]/$3"

<Location / >
   AuthType openid-connect
   Require valid-user
   ProxyPass http://test/
   ProxyPassReverse http://test/
   ProxyPassReverseCookiePath /test-path /test-path
</Location>

https://cloud.google.com/service-mesh/docs/security/end-user-auth#custom_claims_mapping

authors: ganesh-nadar-db srihari-gadde

repo: GoogleCloudPlatform/asm-user-auth


text:
Add windows sbom validation workflow

Add a workflow which can be used as a presubmit for windows sbom generation validation.

/cc dorileo

/lgtm

/approve

repo: GoogleCloudPlatform/compute-image-tools


text:
How to use dialogflow cx integration with terraform when there are various languages being used for the same dialogflow agent

@koverholt
How do I export various locale (language code) specific resource settings to terraform? For example, in "es-es" locale, there could be a page with "Hola" readout whereas in "fr-fr", the same page could have "Bonjour" instead of "Hola" since we are dealing with French language now. This is how my dialogflow agent is built. Each locale has its language specific readouts.
See attached. For the same flow/page/route combination, "Agent says" option changes depending upon which language is selected - "de-de" or "en-us". How to export all language resources configured in dialogflow agent to terraform?

Thanks for reaching out! This repository provides sample code and examples for working with Terraform and Dialogflow CX, but doesn't get into details about all of the possible functionality in the Terraform modules such as managing different languages. So, it would be best to reach out to Google Cloud Support, the Google Cloud Community forums, or the Dialogflow Issue Tracker. You can find links to those resources here: https://cloud.google.com/dialogflow/docs/support/getting-support.

authors: koverholt mahesh-iyer


text:
Path arguments for ancestors break

Hello. When building an API with nested entities (e.g., grandparent/parent/child), the variable _child returns 'None' (set on line 94) seemingly at random, this breaks ndb.Key on lines 138 and 142 and causes BadArgumentError: Incomplete Key entry must be last. Adding a greatGrandparent seems to break the _child variable permanently while the _parent remains somewhat unpredictable.
I've just added the log to the Gist.
Thanks.
Edit: I've just read through your update on Stackoverflow but I don't understand completely. Here's the set_key method in ParentModel:
def set_key(self):
        if self._grandparent is not None and self._parent is not None:
            key = ndb.Key(GrandparentModel, self._grandparent, ParentModel, self._parent)
            self.UpdateFromKey(key)

and in ChildModel:
def set_key(self):
        if self._grandparent is not None and self._parent is not None and self._child is not None:
            key = ndb.Key(GrandparentModel, self._grandparent, ParentModel, self._parent, ChildModel, self._child)
            self.UpdateFromKey(key)

How should I be doing this differently so I don't depend on the order that the variables are set? I'm also a little confused as to why you mentioned the exception on line 136.
Thank you for your in-depth explanations, I really appreciate it.

So you call ChildModel.set_key from ChildModel.set_grandparent, ChildModel.set_parent and ChildModel.set_child.
However, in ChildModel.set_parent you assume grandparent is already set before calling set_key:
    def set_parent(self, value):
        if not isinstance(value, basestring):
            raise TypeError('Parent name must be a string.')

        self._parent = value

        logging.warning('Check _grandparent value: %s' % self._grandparent)
        logging.warning('Check _parent value: %s' % self._parent)

        if self._grandparent is None:
            raise Exception('set_parent: self._grandparent is None')

This is the out of order assumption that breaks your app. You will do that self._grandparent is None check in ChildModel.set_key every time and eventually set the key.
The reason it isn't getting set is because the check
    def set_key(self):
        if (self._grandparent is not None and
                self._parent is not None and
                self._child is not None):
            key = ndb.Key(GrandparentModel, self._grandparent,
                          ParentModel, self._parent,
                          ChildModel, self._child)
            self.UpdateFromKey(key)

will never pass with the two methods you have implemented
    @ChildModel.method(
        name='insert',
        path='grandparent/{grandparent}/parent/{parent}/child')
    def child_insert(self, child):
        child.put()
        return child

    @ChildModel.query_method(
        name='list',
        path='grandparent/{grandparent}/parent/{parent}/child',
        query_fields=('grandparent', 'parent',))
    def child_list(self, query):
        return query

since neither one will set _child. Those are (very likely) the right inputs in both methods, but for the first, you want an incomplete key to have the backend set it and for the second you just want the ancestor key Key(GrandParent, foo, Parent, Bar) and then you want to do an ancestor query.
You could get around the first (auto-assigned ID) by allowing _child to be None in set_key.

Also, on StackOverflow you should mark my answer as accepted in addition to the upvote :grinning:

I updated the Gist. I'm not sure I have the best solution, so maybe something can be worked out there. What do you think about updating the ancestor example with a third nested entity?

I don't think adding another ancestor will clarify the example. The core issue was that we don't know the order of the ancestor components so any of them (if two, or three, or N) can set the key once everything is in place

As you pointed out, this doesn't really cover your case where you want only ancestors for query_methods. You have two sort of options

Use a separate property to accomplish a similar goal
Muck around with self._endpoints_query_info._AddFilter and try to detect if the value is being set via a query or via method

authors: dhermes lukegr


text:
Datastore Query order should use an explicit ascending/descending parameter instead of "-" in a string.

Currently:
// Sort by size ascendingly.
var companiesAscending = companyQuery.order('size');

// Sort by size descendingly.
var companiesDescending = companyQuery.order('-size');

This is bad.  It is mixing the properties of a string based query language with a json based query API.
Instead, consider just adding a boolean ascending / descending property that defaults to ascending.
var companiesAscendingImplicit = companyQuery.order('size');
var companiesAscendingExplicit = companyQuery.order('size', true);
var companiesDescending = companyQuery.order('-size', false);

This seems like a pretty reasonable request, @krisnye. I think there might be a typo in your example and you were going for this..?
var companiesDescending = companyQuery.order('size', false);

I'm not totally sold on using a boolean, only because at first glance it's not very obvious what it does and it may end up warranting a trip to the docs. I like the idea of separating the two, however I feel that a literal object (probably overkill) or simply passing in an optional sign would be more intuitive.
var companiesDescending = companyQuery.order('size', { ascending: false });
var companiesDescending = companyQuery.order('size', '-');

@stephenplusplus thoughts?

I prefer the options object.

Yes, I had a typo.  I fixed it.  My honest thoughts are that a JSON based API should have a JSON based query structure.  One that is easy to read and easy to write, while being explicit.
Here is the JSON query structure that I use to represent filters, limits, offsets and sorts.
{ "offset": 20, "limit":100, "where":{ "name": "foo", "age": { ">=": 10} }, "sort": [ { "age": true}, {"name": false} ] }

I actually combine this query format with a TYPE/ID path which captures ancestor searches in order to represent all queries.
Here are some examples.  They are all both REST urls and concise query descriptions:
/Project/23                 # gets a single entity
/Project                      # gets all Projects
/Project?{"limit":50}    # gets first 50 projects
/Project/23/Task/2      # gets a single descendant entity
/Project/23/Task?{"where":{"percentComplete":{">=":1,"<=":99"}}     # get all tasks that are in progress

If I was to design the API today, I definitely would have went with that approach as well. I'm not sure why we went with the builder approach. Obviously, at the time, it was thought to be more convenient for the developer. In the end, it's really just a style choice, so to completely change to just a plain JS object now would be an unfair amount of work to put on developers without any clear rewards.

True, but you can build such an object behind the scenes using the builder for backward compatibility and then expose the simpler interface when appropriate.
Something to think about for the future.

authors: callmehiphop krisnye stephenplusplus

repo: GoogleCloudPlatform/gcloud-node


text:
Error when importing 'vertexai.preview' and 'vertexai.language_models'

File Name
generative-ai/language/prompts/intro_prompt_design.ipynb
What happened?
During Qwiklabs - Google Cloud Skills Booster excercises, 'Generative AI with Vertex AI: Prompt Design' when running the vanilla version of the intro_prompt_design.ipynb
on the Vertex AI Workbench, based on the longs - the error similar to issue  #363 .
Relevant log output
from vertexai.language_models import TextGenerationModel
from vertexai.language_models import ChatModel
2024-03-05 18:50:42.218294: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[6], line 1
----> 1 from vertexai.language_models import TextGenerationModel
      2 from vertexai.language_models import ChatModel

File ~/.local/lib/python3.10/site-packages/vertexai/__init__.py:22
     19 __version__ = aiplatform_version.__version__
     21 from google.cloud.aiplatform import init
---> 22 from vertexai import preview
     24 __all__ = [
     25     "init",
     26     "preview",
     27 ]

File ~/.local/lib/python3.10/site-packages/vertexai/preview/__init__.py:20
      1 # -*- coding: utf-8 -*-
      2
      3 # Copyright 2023 Google LLC
   (...)
     15 # limitations under the License.
     16 #
     18 from google.cloud.aiplatform.metadata import metadata
---> 20 from vertexai.preview import developer
     21 from vertexai.preview import hyperparameter_tuning
     22 from vertexai.preview import initializer

File ~/.local/lib/python3.10/site-packages/vertexai/preview/developer/__init__.py:18
      1 # -*- coding: utf-8 -*-
      2
      3 # Copyright 2023 Google LLC
   (...)
     15 # limitations under the License.
     16 #
---> 18 from vertexai.preview._workflow.serialization_engine import (
     19     any_serializer,
     20 )
     21 from vertexai.preview._workflow.serialization_engine import (
     22     serializers_base,
     23 )
     24 from vertexai.preview._workflow.shared import configs

File ~/.local/lib/python3.10/site-packages/vertexai/preview/_workflow/serialization_engine/any_serializer.py:30
     28 from google.cloud.aiplatform import base
     29 from google.cloud.aiplatform.utils import gcs_utils
---> 30 from vertexai.preview._workflow.serialization_engine import (
     31     serializers,
     32     serializers_base,
     33 )
     34 from vertexai.preview._workflow.shared import (
     35     supported_frameworks,
     36 )
     38 from packaging import requirements

File ~/.local/lib/python3.10/site-packages/vertexai/preview/_workflow/serialization_engine/serializers.py:52
     49 SERIALIZATION_METADATA_FRAMEWORK_KEY = "framework"
     51 try:
---> 52     from tensorflow import keras
     53     import tensorflow as tf
     55     KerasModel = keras.models.Model

File /opt/conda/lib/python3.10/site-packages/tensorflow/__init__.py:37
     34 import sys as _sys
     35 import typing as _typing
---> 37 from tensorflow.python.tools import module_util as _module_util
     38 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
     40 # Make sure code inside the TensorFlow codebase can use tf2.enabled() at import.

File /opt/conda/lib/python3.10/site-packages/tensorflow/python/__init__.py:37
     29 # We aim to keep this file minimal and ideally remove completely.
     30 # If you are adding a new file with @tf_export decorators,
     31 # import it in modules_with_exports.py instead.
     32
     33 # go/tf-wildcard-import
     34 # pylint: disable=wildcard-import,g-bad-import-order,g-import-not-at-top
     36 from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
---> 37 from tensorflow.python.eager import context
     39 # pylint: enable=wildcard-import
     40
     41 # Bring in subpackages.
     42 from tensorflow.python import data

File /opt/conda/lib/python3.10/site-packages/tensorflow/python/eager/context.py:28
     25 from absl import logging
     26 import numpy as np
---> 28 from tensorflow.core.framework import function_pb2
     29 from tensorflow.core.protobuf import config_pb2
     30 from tensorflow.core.protobuf import coordination_config_pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/function_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import attr_value_pb2 as tensorflow_dot_core_dot_framework_dot_attr__value__pb2
     17 from tensorflow.core.framework import node_def_pb2 as tensorflow_dot_core_dot_framework_dot_node__def__pb2
     18 from tensorflow.core.framework import op_def_pb2 as tensorflow_dot_core_dot_framework_dot_op__def__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/attr_value_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import tensor_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__pb2
     17 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     18 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/tensor_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import resource_handle_pb2 as tensorflow_dot_core_dot_framework_dot_resource__handle__pb2
     17 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     18 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/resource_handle_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     17 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2
     20 DESCRIPTOR = _descriptor.FileDescriptor(
     21   name='tensorflow/core/framework/resource_handle.proto',
     22   package='tensorflow',
   (...)
     26   ,
     27   dependencies=[tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2.DESCRIPTOR,tensorflow_dot_core_dot_framework_dot_types__pb2.DESCRIPTOR,])

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/tensor_shape_pb2.py:36
     13 _sym_db = _symbol_database.Default()
     18 DESCRIPTOR = _descriptor.FileDescriptor(
     19   name='tensorflow/core/framework/tensor_shape.proto',
     20   package='tensorflow',
   (...)
     23   serialized_pb=_b('\n,tensorflow/core/framework/tensor_shape.proto\x12\ntensorflow\"z\n\x10TensorShapeProto\x12-\n\x03\x64im\x18\x02 \x03(\x0b\x32 .tensorflow.TensorShapeProto.Dim\x12\x14\n\x0cunknown_rank\x18\x03 \x01(\x08\x1a!\n\x03\x44im\x12\x0c\n\x04size\x18\x01 \x01(\x03\x12\x0c\n\x04name\x18\x02 \x01(\tB\x87\x01\n\x18org.tensorflow.frameworkB\x11TensorShapeProtosP\x01ZSgithub.com/tensorflow/tensorflow/tensorflow/go/core/framework/tensor_shape_go_proto\xf8\x01\x01\x62\x06proto3')
     24 )
     29 _TENSORSHAPEPROTO_DIM = _descriptor.Descriptor(
     30   name='Dim',
     31   full_name='tensorflow.TensorShapeProto.Dim',
     32   filename=None,
     33   file=DESCRIPTOR,
     34   containing_type=None,
     35   fields=[
---> 36     _descriptor.FieldDescriptor(
     37       name='size', full_name='tensorflow.TensorShapeProto.Dim.size', index=0,
     38       number=1, type=3, cpp_type=2, label=1,
     39       has_default_value=False, default_value=0,
     40       message_type=None, enum_type=None, containing_type=None,
     41       is_extension=False, extension_scope=None,
     42       serialized_options=None, file=DESCRIPTOR),
     43     _descriptor.FieldDescriptor(
     44       name='name', full_name='tensorflow.TensorShapeProto.Dim.name', index=1,
     45       number=2, type=9, cpp_type=9, label=1,
     46       has_default_value=False, default_value=_b("").decode('utf-8'),
     47       message_type=None, enum_type=None, containing_type=None,
     48       is_extension=False, extension_scope=None,
     49       serialized_options=None, file=DESCRIPTOR),
     50   ],
     51   extensions=[
     52   ],
     53   nested_types=[],
     54   enum_types=[
     55   ],
     56   serialized_options=None,
     57   is_extendable=False,
     58   syntax='proto3',
     59   extension_ranges=[],
     60   oneofs=[
     61   ],
     62   serialized_start=149,
     63   serialized_end=182,
     64 )
     66 _TENSORSHAPEPROTO = _descriptor.Descriptor(
     67   name='TensorShapeProto',
     68   full_name='tensorflow.TensorShapeProto',
   (...)
    100   serialized_end=182,
    101 )
    103 _TENSORSHAPEPROTO_DIM.containing_type = _TENSORSHAPEPROTO

File ~/.local/lib/python3.10/site-packages/google/protobuf/descriptor.py:553, in FieldDescriptor.__new__(cls, name, full_name, index, number, type, cpp_type, label, default_value, message_type, enum_type, containing_type, is_extension, extension_scope, options, serialized_options, has_default_value, containing_oneof, json_name, file, create_key)
    547 def __new__(cls, name, full_name, index, number, type, cpp_type, label,
    548             default_value, message_type, enum_type, containing_type,
    549             is_extension, extension_scope, options=None,
    550             serialized_options=None,
    551             has_default_value=True, containing_oneof=None, json_name=None,
    552             file=None, create_key=None):  # pylint: disable=redefined-builtin
--> 553   _message.Message._CheckCalledFromGeneratedFile()
    554   if is_extension:
    555     return _message.default_pool.FindExtensionByName(full_name)

TypeError: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The message on the top of the User-Managed Notebooks (request to migrate to new Workbench instance - below) confirms that issue is the same as #363  - and as a result of Qwicklabs (for me GSP1151) is still using the old VMs.

The new Workbench Instances bring the features of Managed and User-Managed Notebooks into a single offering. (Migrate)

Seems that forcing the version as second cell in each of the QwickLabs managed notebooks resolves the issue.
!pip install protobuf==3.19.3

@OWLYone Thanks for reporting this issue, I made #432 to implement your workaround.
@polong-lin I made b/328420624 to report this to the Qwiklabs team.

authors: OWLYone holtskinner

repo: GoogleCloudPlatform/generative-ai


text:
Fixes for Spanner resource management

Each of these commits is intended to be relatively isolated. Some are effectively refactorings.
I've got a bunch of other changes which are formatting and comments, but those can happen later. Likewise I want to tighten up the pool validation and roll that out more widely through the tests. I figured this PR was big enough already though :)

Thanks - will address all these nits in a new commit, rerun integration tests, then merge. Further formatting refactorings will come later.

(I definitely need to look into this more before merging. There may or may not be a new commit - will let you know, Chris.)

Merging to make it simpler to track further changes, and raising a new issue to make sure we don't release like this.

repo: GoogleCloudPlatform/google-cloud-dotnet


text:
storage: tests fail when using modules

Client
storage
Describe Your Environment
A program using modules:
#!/bin/sh
set -ex
t=$(mktemp -d)
trap 'rm -r $t' EXIT
cd $t
cat >ex.go <<.
package main

import (
	_ "cloud.google.com/go/storage"
)

func main() {
	println("example")
}
.
go mod init example
go get github.com/google/martian@master # broken
go test all

Expected Behavior
tests pass
Actual Behavior
2018/09/06 13:57:37 creating bucket "go-integration-test-20180906-64657522195962-0001": googleapi: Error 400: Unknown project id: , invalid
FAIL	cloud.google.com/go/storage	0.481s

(golang.org/x/sys/unix also fails, but that's out-of-scope)

No, I'm attempting to follow the steps outlined here.
It seems like integration tests should be skipped in this case.

go test all seems to run integration tests AFAICT. Have you tried go test all -short?
Also, go test all on my machine succeeded - likely because environment variables are set as described in the CONTRIBUTING.md that @jba linked. I'll close this issue for now since it seems like things are working as intended.

authors: hdonnay jadekler

repo: GoogleCloudPlatform/google-cloud-go


text:
Storage: Blob.compose doesn't use default content_type

Blob.compose does not use the self._get_content_type method, which means Blob.compose raises an error if the content_type is not explicitly specified. This is documented behavior, but is it intended behavior? Should compose use self._get_content_type to use the default type, or perhaps infer the type from the blobs being composed?

@frankyn I'm not sure how the GCS team would like to shape this feature.

Acking. Adding to GCS client library weekly.

@frankyn -- any updates?

Apologies on the wait.
content-type is optional and defaults to application/octet-stream based on Storage.Objects Ref docs. I don't think we should fail the method if it's not set.
Additionally, I'm looking at upload_* and these methods provide a parameter for content_type. Including this parameter would follow the pattern that exists for these methods and would be easier to understand.
@tseaver do you have objections to surfacing content_type as an optional parameter for compose()?

Great! content-type as an optional parameter (but falling back to the default through self._get_content_type) seems ideal.
Could this lead to unexpected behavior? For example, composing blobs of some non-default type but not specifying that type in compose leads them to be composed as application/octet-stream. I suppose the type can also be inferred from the types of the objects being composed, but this seems more involved.

@rasmi that sounds like a fair condition.
if content_type is not None:
  # use this
if self._get_content_type is not `None`
  # use this
else:
  # it's okay to not provide content_type as it will default to application/octet-stream.

I think inferring the content-type might be not be as helpful as simply surfacing a parameter for the content type. I think it would feel magical which is not a bad thing, but it may or may not be the desired result for everyone.

Okay, agreed.
I can submit a PR. However, I have an implementation question. Content type is not explicitly used in self.compose, but it does pass self when making a request, so presumably the blob object's content type must be set before the request is made (which is why the error is raised if it's not set).
Additionally, self._get_content_type() handles arguments/None values correctly. So I think we can simply add the content_type argument to the compose function and do:
self.content_type = self._get_content_type(content_type)

at the top of compose to ensure that the content type is set. If the argument is None, it will use the blob's content type, and if the blob has no content type, it will use the default. Is that a reasonable implementation?

@frankyn as long as the objects.compose API honors the destination.content_type field, it should work just to set content_type on the Blob instance through which we are invoking it (we already require that, in fact, because we copy the destination blob's properties into the request body).
sources = [bucket.blob(name) for name in ['source1.txt', 'source2.txt']]
destination = bucket.blob('destination.txt)
destination.content_type = 'text/plain'
# set other destination properties here
destination.compose(sources)

I don't really see the value in adding Another Way to Do It(TM).
This issue is a request that, if the destination blob does not have content_type set, we deduce the correct value by looking at the content types of the sources.  Given that we may not have loaded them (e.g., in the example I just showed), I don't know how feasible it would be.  I guess we could do something like:
    def _deduce_content_type_for_compose(self, sources):
        if self.content_type is None:
            source_types = set(
                src.content_type for src in sources if src.content_type is not None)
            if len(source_types) == 1:
                return source_types[0]
            return self.content_type

Thanks @tseaver, your comment helps.
I don't think we should infer content types from a list of objects and instead depend on the destination blob content type.
How about, not failing the compose if a content_type is not found?

How about not failing the compose if a content_type is not found?

That would be fine.  It has been a while, but I wonder if I added that check because the objects.compose API used to fail if it wasn't set.

Ah good question. I do recall this came up for Node.js and the GCS API has since changed this requirement. The code used to be correct but now the restriction has been removed.

How about not failing the compose if a content_type is not found?

PR #6031 makes that change, including a system test.  Note that the server does not set application/octet-stream as the composed object's contentType:  it remains unset.

authors: frankyn rasmi tseaver

repo: GoogleCloudPlatform/google-cloud-python


text:
Publish dialog doesn't remember the VM I most recently published to.

2 minutes ago, I published to an instance called hello-aspnet.  But when I publish again the dialog has forgotten my choices:

Sub-issue of #863

Now being tracked as part of #863.

authors: ILMTitan SurferJeffAtGoogle


text:
Tool Wanted: Install Service Account Credentials

I watched a user struggle through the process of downloading credentials and restarting Visual Studio during a presentation.  It takes time, and energy, and is easy to get wrong.
How about a menu item:
Google Cloud Tools > Download Service Account Credentials ...
Which lets you choose or create a service account, and download credentials.  They should be valid for the current session, and also set globally.

We will look into this, using service account credentials is not the recommended way to do authentication anymore. We really should coordinate with the identity team on this.

authors: SurferJeffAtGoogle ivannaranjo


text:
M2 gcs browser context menu

This PR contains new behaviors that make the use of context menu in the GCS browser more useable.
Now you can:

Right click on an item and if it is not selected it will become the selected item.
Right click on an already selected item, this will preserve the selection and show the pertinent context menu.
Right click on the background of the data grid, which allows you to create new directories and select all items.

Fixes #661

Thank you for for the review.

Thank you for the review.


text:
Remove references to gcloud-java.

We were still using the old artifactId in some pom.xml files, so dpebot
could not update these.  Also, some READMEs needed updating from my grep
search.
@lesv ptal

Current coverage is 49.73% (diff: 100%)

Merging #392 into master will not change coverage

@@             master       #392   diff @@
==========================================
  Files            82         82
  Lines          2640       2640
  Methods           0          0
  Messages          0          0
  Branches        195        195
==========================================
  Hits           1313       1313
  Misses         1284       1284
  Partials         43         43

Powered by Codecov. Last update 2e3f285...bd13489

authors: codecov-io tswast

repo: GoogleCloudPlatform/java-docs-samples


text:
Bump to v0.1.4

Block on #2 and #4.

Xref https://github.com/kubernetes/kubernetes/pull/54653.

Let's not block this on #2, since kubernetes/kubernetes#52744 isn't in yet.

$ make push
rm -f metadata_proxy
go get github.com/tools/godep
godep save
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 godep go test ./...
?       github.com/GoogleCloudPlatform/k8s-metadata-proxy       [no test files]
?       github.com/GoogleCloudPlatform/k8s-metadata-proxy/metrics       [no test files]
?       github.com/GoogleCloudPlatform/k8s-metadata-proxy/test  [no test files]
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 godep go build -o metadata_proxy
docker build --pull --no-cache -t gcr.io/google_containers/metadata-proxy:v0.1.4 .
Sending build context to Docker daemon 10.29 MB
Step 1 : FROM gcr.io/google_containers/debian-base-amd64:0.1
0.1: Pulling from google_containers/debian-base-amd64
Digest: sha256:e7248990914c1cfbaef526332bb72064819a08b513f6a87f228f82155b7714ac
Status: Image is up to date for gcr.io/google_containers/debian-base-amd64:0.1
 ---> be4292fc517f
Step 2 : LABEL maintainer "ihmccreery@google.com"
 ---> Running in fd9133daa214
 ---> 518f6e2b0fd6
Removing intermediate container fd9133daa214
Step 3 : ARG DEBIAN_FRONTEND=noninteractive
 ---> Running in 2820a1a7968e
 ---> 62ceb4c6fe3b
Removing intermediate container 2820a1a7968e
Step 4 : RUN apt-get update && apt-get install -y   apt-utils && clean-install iptables
 ---> Running in c437ee88f496
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Ign http://deb.debian.org jessie InRelease
Get:2 http://deb.debian.org jessie-updates InRelease [145 kB]
Get:3 http://security.debian.org jessie/updates/main amd64 Packages [548 kB]
Get:4 http://deb.debian.org jessie Release.gpg [2373 B]
Get:5 http://deb.debian.org jessie Release [148 kB]
Get:6 http://deb.debian.org jessie-updates/main amd64 Packages [23.2 kB]
Get:7 http://deb.debian.org jessie/main amd64 Packages [9063 kB]
Fetched 9994 kB in 3s (3132 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  libapt-inst1.5
The following NEW packages will be installed:
  apt-utils libapt-inst1.5
0 upgraded, 2 newly installed, 0 to remove and 8 not upgraded.
Need to get 537 kB of archives.
After this operation, 1333 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian/ jessie/main libapt-inst1.5 amd64 1.0.9.8.4 [169 kB]
Get:2 http://deb.debian.org/debian/ jessie/main apt-utils amd64 1.0.9.8.4 [368 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 537 kB in 0s (1523 kB/s)
Selecting previously unselected package libapt-inst1.5:amd64.
(Reading database ... 3949 files and directories currently installed.)
Preparing to unpack .../libapt-inst1.5_1.0.9.8.4_amd64.deb ...
Unpacking libapt-inst1.5:amd64 (1.0.9.8.4) ...
Selecting previously unselected package apt-utils.
Preparing to unpack .../apt-utils_1.0.9.8.4_amd64.deb ...
Unpacking apt-utils (1.0.9.8.4) ...
Setting up libapt-inst1.5:amd64 (1.0.9.8.4) ...
Setting up apt-utils (1.0.9.8.4) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Hit http://security.debian.org jessie/updates InRelease
Ign http://deb.debian.org jessie InRelease
Hit http://deb.debian.org jessie-updates InRelease
Get:1 http://security.debian.org jessie/updates/main amd64 Packages [548 kB]
Hit http://deb.debian.org jessie Release.gpg
Hit http://deb.debian.org jessie Release
Get:2 http://deb.debian.org jessie-updates/main amd64 Packages [23.2 kB]
Get:3 http://deb.debian.org jessie/main amd64 Packages [9063 kB]
Fetched 9635 kB in 3s (3038 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  libnfnetlink0 libxtables10
The following NEW packages will be installed:
  iptables libnfnetlink0 libxtables10
0 upgraded, 3 newly installed, 0 to remove and 8 not upgraded.
Need to get 358 kB of archives.
After this operation, 3818 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian/ jessie/main libnfnetlink0 amd64 1.0.1-3 [13.5 kB]
Get:2 http://deb.debian.org/debian/ jessie/main libxtables10 amd64 1.4.21-2+b1 [67.6 kB]
Get:3 http://deb.debian.org/debian/ jessie/main iptables amd64 1.4.21-2+b1 [277 kB]
Fetched 358 kB in 0s (490 kB/s)
Selecting previously unselected package libnfnetlink0:amd64.
(Reading database ... 4076 files and directories currently installed.)
Preparing to unpack .../libnfnetlink0_1.0.1-3_amd64.deb ...
Unpacking libnfnetlink0:amd64 (1.0.1-3) ...
Selecting previously unselected package libxtables10.
Preparing to unpack .../libxtables10_1.4.21-2+b1_amd64.deb ...
Unpacking libxtables10 (1.4.21-2+b1) ...
Selecting previously unselected package iptables.
Preparing to unpack .../iptables_1.4.21-2+b1_amd64.deb ...
Unpacking iptables (1.4.21-2+b1) ...
Setting up libnfnetlink0:amd64 (1.0.1-3) ...
Setting up libxtables10 (1.4.21-2+b1) ...
Setting up iptables (1.4.21-2+b1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
 ---> 9fbba94fa0e0
Removing intermediate container c437ee88f496
Step 5 : COPY start-proxy.sh /
 ---> ca2f5bb7ff0b
Removing intermediate container dbd451f2d283
Step 6 : COPY metadata_proxy /
 ---> 78f10aec4972
Removing intermediate container 77e0b732d7ff
Step 7 : ENTRYPOINT /start-proxy.sh
 ---> Running in b38171e91e0a
 ---> 77dd1c74b7ce
Removing intermediate container b38171e91e0a
Successfully built 77dd1c74b7ce
gcloud docker -- push gcr.io/google_containers/metadata-proxy:v0.1.4
The push refers to a repository [gcr.io/google_containers/metadata-proxy]
5993fcc4cf83: Pushed
34821ce034be: Pushed
0dbcd6a1282f: Pushed
d066a55459dd: Layer already exists
v0.1.4: digest: sha256:9ca02cc773e286b28942103e2482ce74e281ef2c18936610d379b26ecb89c533 size: 1157


text:
sc install fails on clusterroles.rbac.authorization.k8s.io "etcd-operator" is forbidden

I have a GKE cluster running 1.8.4 with legacy auth disabled
I have a cluster admin role. I prove that I have full access with
$ kubectl auth can-i '*' '*' --all-namespaces
yes

I run sc install and get the error clusterroles.rbac.authorization.k8s.io "etcd-operator" is forbidden
I don't know what I'm missing.
Role binding command:
$ kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=`gcloud config config-helper --format=json | jq '.configuration.properties.core.account'`
clusterrolebinding "cluster-admin-binding" created

Full output:
$ sc install
generated service catalog deployment config in dir: /tmp/service-catalog898278198
Service Catalog could not be installed
error deploying YAML files: deploy failed with output: exit status 1 :Error from server (Forbidden): error when creating "/tmp/service-catalog898278198/etcd-operator-rbac.yaml": clusterroles.rbac.authorization.k8s.io "etcd-operator" is forbidden: attempt to grant extra privileges: [PolicyRule{Resources:["etcdclusters"], APIGroups:["etcd.database.coreos.com"], Verbs:["*"]} PolicyRule{Resources:["customresourcedefinitions"], APIGroups:["apiextensions.k8s.io"], Verbs:["*"]} PolicyRule{Resources:["storageclasses"], APIGroups:["storage.k8s.io"], Verbs:["*"]} PolicyRule{Resources:["pods"], APIGroups:[""], Verbs:["*"]} PolicyRule{Resources:["services"], APIGroups:[""], Verbs:["*"]} PolicyRule{Resources:["endpoints"], APIGroups:[""], Verbs:["*"]} PolicyRule{Resources:["persistentvolumeclaims"], APIGroups:[""], Verbs:["*"]} PolicyRule{Resources:["events"], APIGroups:[""], Verbs:["*"]} PolicyRule{Resources:["deployments"], APIGroups:["apps"], Verbs:["*"]}] user=&{myemail@wherever.com  [system:authenticated] map[]} ownerrules=[PolicyRule{Resources:["selfsubjectaccessreviews"], APIGroups:["authorization.k8s.io"], Verbs:["create"]} PolicyRule{NonResourceURLs:["/api" "/api/*" "/apis" "/apis/*" "/healthz" "/swagger-2.0.0.pb-v1" "/swagger.json" "/swaggerapi" "/swaggerapi/*" "/version"], Verbs:["get"]}] ruleResolutionErrors=[]

Just FYI, this does not happen on another GCP project, with an identically created cluster. IMHO there's a problem with rbac roles not being purely additive, although they should be.

Thanks for the update @squeedee
Can you explain "there's a problem with rbac roles not being purely additive" a bit more ?

@squeedee debugged the issue. The problem is because of "extra" quotes in the username. using jq with -r option fixes the problem. You can examine current clusterrolebinding and see extra quote for the subject value. So correct command to create the clusterbinding would be:
$ kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=gcloud config config-helper --format=json | jq -r '.configuration.properties.core.account'
Pl. verify and close this bug if you get a chance. Thanks for reporting it.

authors: droot squeedee


text:
Cherry pick process

After 1.0, we've talked about the timeline for minor releases being longer (circa ~1mo), which means we'll be putting out more patch releases (1.0.1, 1.0.2, etc.) in the interim. Outside of developers, people are probably going to be running something closer to the release-X.Y branch, so release validation (#10676) is going to be very important as well.
Our current cherry pick "process" is very loose. We cobble together a list using an issue, or a label, and then we blast all of those commits together all at once as the patch version commit (e.g. #10559).
With a small amount of scripting, we can change this so that cherry picks are just proposed pull requests to the release branch. They can be completely automated, as a single commit with a small justification for the cherry pick. We could then decide on a group of people that were responsible for triage over the release branch (and maybe a small set with fastpath triage for hot stuff.)
This also has the added advantage that cherry-picks can just be trickled into the release branch gradually, and we would then either cut patch releases on cadence (i.e. "patch Tuesday") or immediately for a breakfix - and in the latter case we'd already know from validation that the other patches in the release branch are safe to ship as well.
The importance of this is also higher if the cadence of the minor releases is slower because the cherry picks will undoubtedly hit more and more conflicts towards the end of the cycle - validation after conflict resolution is doubly important.
c.f. #10709 (I'd update releasing.md after this)
cc @alex-mohr @goltermann @thockin @brendandburns @quinton-hoole

+1 - this needs to be really transparent and obvious.  Glomming commits
together into a cherry-pick is a terrible idea.
On Sun, Jul 5, 2015 at 11:09 AM, Zach Loafman notifications@github.com
wrote:

After 1.0, we've talked about the timeline for minor releases being longer
(circa ~1mo), which means we'll be putting out more patch releases (1.0.1,
1.0.2, etc.) in the interim. Outside of developers, people are probably
going to be running something closer to the release-X.Y branch, so
release validation (#10676
https://github.com/GoogleCloudPlatform/kubernetes/issues/10676) is
going to be very important as well.
Our current cherry pick "process" is very loose. We cobble together a list
using an issue, or a label, and then we blast all of those commits together
all at once as the patch version commit (e.g. #10559
https://github.com/GoogleCloudPlatform/kubernetes/pull/10559).
With a small amount of scripting, we can change this so that cherry picks
are just proposed pull requests to the release branch. They can be
completely automated, as a single commit with a small justification for the
cherry pick.
This also has the added advantage that cherry-picks can just be trickled
into the release branch gradually, and we would then either cut patch
releases on cadence (i.e. "patch Tuesday") or immediately for a breakfix -
and in the latter case we'd already know from validation that the other
patches in the release branch are safe to ship as well.
The importance of this is also higher if the cadence of the minor releases
is slower because the cherry picks will undoubtedly hit more and more
conflicts towards the end of the cycle - validation after conflict
resolution is doubly important.
c.f. #10709 https://github.com/GoogleCloudPlatform/kubernetes/pull/10709
(I'd update releasing.md after this)
cc @alex-mohr https://github.com/alex-mohr @goltermann
https://github.com/goltermann @thockin https://github.com/thockin
@brendandburns https://github.com/brendandburns @quinton-hoole
https://github.com/quinton-hoole
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/10730.

@thockin: I hacked up something in #10757 that I think meets your "not smashing commits". I wish it were slightly more automated given the way PRs get automatically generated in GitHub (because I want the subject of these things to also tell us the original PR #), but I think it gets the job done and is thoroughly straightforward.

authors: thockin zmerlynn

repo: GoogleCloudPlatform/kubernetes


text:
service.sh e2e flaky - curl against service IP doesn't find all endpoint pods - try some more?

e2e output:
service-13483 portal failed from container, expected:
    service-13483-bzy5s

service-13483-qlk9b
service-13483-vq7md
    got:

    service-13483-bzy5s

service-13483-bzy5s
service-13483-qlk9b
It looks like the test might be wrong:
https://github.com/GoogleCloudPlatform/kubernetes/blob/4a6ab7fd3698c5cc7172c5bd63efab320d1f2d17/hack/e2e-suite/services.sh#L268
It seems to try 10 curls against a service with 3 pods behind it, and fail if it doesn't find all 3 pods after 10 tries.
The probability of this happening is about 3 * 0.66^10 = 4.7% (if my high school stats still works :-)
Q

@thockin - did you write that test (long, long ago)?

While I admit the logic is suspect (why not just loop 30 times?) it is
known to have succeeded many times, no?  I do recall it being very fragile
wrt output format, and making me basically swear off shell forever...
On Tue, May 26, 2015 at 7:39 PM, Robert Bailey notifications@github.com
wrote:

@thockin https://github.com/thockin - did you write that test (long,
long ago)?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/8849#issuecomment-105733491
.

@thockin is this still open/relevant? I know you did some work here...

#8953 (which added some retries) does not seem to have fixed this test completely, although the failure mode is now different:
Test 1: Prove that the service VIP is alive.
Verifying the VIP from the host
waiting for service1 at 10.0.182.230:80
waiting for service1 at 192.168.1.1:80
waiting for service1 at 192.168.1.2:80
waiting for service2 at 10.0.200.24:80
Verifying the VIP from a container
waiting for service1 at 10.0.182.230:80
time="2015-06-13T16:22:00Z" level=fatal msg="Could not reach any registry endpoint"
ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [1].
testing service1 VIP from container failed
namespaces/services-test-8716
More comments shortly...

Failure rate is ~3.3% over the past 100 runs.  The error is pulling a busybox image from docker:
  sudo docker pull busybox >/dev/null;
  sudo docker run busybox sh -c '

We need to clone this image to gcr.io.
Dropping this to post-1.0.

Closing this one as we now pull from gcr for everything.

authors: brendandburns quinton-hoole roberthbailey thockin


text:
Upgrade go-etcd to v0.4.6 (Take 2)

In response to issue #5779
Updating the master to use etcd v.2.0.5 is in PR #5780
Replacing PR #5782
I've manually cut out dependencies that I did not expect.
@a-robinson

Does this actually build? It doesn't look like we have either of those new packages in our repo yet. And this isn't actually changing the version of go-etcd.

Thanks... let me investigate...

Updated. I will attempt to rebase this into a fresh branch from master to make sure it works and then run e2e.

Still missing package github.com/coreos/etcd/etcdserver/etcdhttp/httptypes
Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go:19:2: cannot find package "github.com/coreos/etcd/etcdserver/etcdhttp/httptypes" in any of:
/home/shippable/.gvm/gos/go1.4/src/github.com/coreos/etcd/etcdserver/etcdhttp/httptypes (from $GOROOT)
/home/shippable/workspace/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/github.com/coreos/etcd/etcdserver/etcdhttp/httptypes (from $GOPATH)

So I think I am fundamentally confused about godep.
Surely when I did the go get for the httptypes package I should see with git status what files need to be added? I did not see any httptypes files?

This is what I did:
$ go get -u github.com/coreos/go-etcd/etcd
$ godep update github.com/coreos/go-etcd/etcd
satnam@satnam-linux:~/gocode/src/github.com/GoogleCloudPlatform/kubernetes$ git status
# On branch getcd
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	modified:   Godeps/Godeps.json
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client_test.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/cluster.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/error.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/get.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/options.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/requests.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/set_curl_chan_test.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/set_update_create.go
#

Building shows we need httptypes so I did:
$ go get github.com/coreos/etcd/etcdserver/etcdhttp/httptypes
satnam@satnam-linux:~/gocode/src/github.com/GoogleCloudPlatform/kubernetes$ godep save ./...
satnam@satnam-linux:~/gocode/src/github.com/GoogleCloudPlatform/kubernetes$ git status
# On branch getcd
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	modified:   Godeps/Godeps.json
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client_test.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/cluster.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/error.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/get.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/options.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/requests.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/set_curl_chan_test.go
#	modified:   Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/set_update_create.go

Why don't I see any source files for httptypes?

The commands you're running look correct. I don't know why httptypes isn't being pulled in. I tried running the commands on my own setup, but it can't even run godep restore right now.

I ran into the same problem as @satnam6502, still digging into the detail

@satnam6502 I am going to manually upgrade the library.


text:
Tiny typo on k8s.io homepage

"share you ideas" -> "share your ideas"

Can't automatically merge. Could you sync and merge to the latest changes? Thank you.

Started again: https://github.com/GoogleCloudPlatform/kubernetes/pull/7132

authors: MikeJeffrey fabioy


text:
Fix detect-minion-names for gke provider

This fixes the services.sh test on gke-ci.

@jlowdermilk @roberthbailey @mbforbes

Test fixes ok for 1.0. Assigned reviewer

LGTM

lgtm

LGTM.

authors: cjcullen jlowdermilk mbforbes roberthbailey saad-ali


text:
WIP: Emptydir and security context

WIP for #7925
Very rough, mostly to track the downstream work I'm doing in openshift

I also expect this to fail until the mounttest-user image is pushed to gcr.io

@thockin This is the next one I'm going to bug you about -- I'm going to refactor this code but I'm carrying a patch for this in OpenShift and so it makes sense for me to begin refactoring from this state.

@pmorie - this one could use a little love too... likely goes with the other work?

@mrry550 This PR is likely not going in.  #12944 supercedes it.

Thx @pmorie - I'll watch over there instead. ;)

Superceded by #14192, closing out.


text:
Files/directories listed in .gcloudignore are still uploaded

I'm deploying a Symfony app to PHP 7.2 App Engine Standard environment.
I have a .gcloudignore file at the root directory of the project with the following content:
 .gcloudignore
 .git
 .gitignore
 /.env
 /.env.*
 #!include:.gitignore

and .gitignore:
.DS_Store
/.idea/

###> symfony/framework-bundle ###
/.env.local
/.env.local.php
/.env.*.local
/public/bundles/
/var/
/vendor/
###< symfony/framework-bundle ###

###> symfony/phpunit-bridge ###
.phpunit
/phpunit.xml
###< symfony/phpunit-bridge ###

###> symfony/web-server-bundle ###
/.web-server-pid
###< symfony/web-server-bundle ###

My problem is that all those files listed in the ignore files are still uploaded regardless. Effectively I have to manually delete /vendor and /var directories before deployment, otherwise it exceeds the 10,000 files limit and fails. My development .env file is also uploaded which prevents proper deployment.
I'm on MacOS Mojave and using Google Cloud SDK 235.0.0. The command I'm using to deploy is:
gcloud app deploy app.stage.yaml --project=MY_PROJECT

On beta channel it doesn't work neither:
gcloud beta app deploy app.stage.yaml --project=MY_PROJECT

After adding  --verbosity=debug I can actually see the .gloudignore file is found and supposedly "used", but in fact it isn't:
Beginning deployment of service [default]...
INFO: Using .gcloudignore file at [PATH_TO_MY_PROJECT/.gcloudignore].
DEBUG: Skipping upload of [config/bundles.php]
DEBUG: Skipping upload of [config/packages/dev/routing.yaml]
DEBUG: Skipping upload of [config/packages/dev/debug.yaml]
(...)
DEBUG: Skipping upload of [.gitignore]
DEBUG: Skipping upload of [.git/refs/remotes/origin/HEAD]
(...)

From what I see, "skipping upload of XXX"  actually means that the file has already been uploaded, therefore it won't be uploaded again. It doesn't mean that it has been recognized as ignored.
What's is going on here?

@gmdev What was the resolution of this issue?

Hi, @gmdev, did you figure it out? I have the same issue here, and .gcloudignore is not ignoring the filges/folders for deployment.

I have found the solution for this problem...
Remove the leading spaces in your .gcloudignore file and your problem will be solved!
I had the exact same issue because I copied the content for the .gcloudignore file from their documentation page.
So instead of:
  .gcloudignore
  .git
  .gitignore
  /.env
  /.env.*
  #!include:.gitignore

You should have:
.gcloudignore
.git
.gitignore
/.env
/.env.*
#!include:.gitignore

Yes, in my case it was the extra space at the beginning of each line too (as you can see in my first post) :)
Should have mentioned that for other people looking for solution to the same issue.

Thanks the reply. @thdk, @gmdev. In my case, somehow my .gcloudignore was disabled. After reebling .gcloudignore by running gcloud config set gcloudignore/enabled true, the problem was resolved.

Also have this problem and nothing seems to solve it. Neither removing whitespaces in the beggining nor running gcloud config set gcloudignore/enabled true

Also have this problem and nothing seems to solve it. Neither removing whitespaces in the beggining nor running gcloud config set gcloudignore/enabled true

I also had the problem, is your gcloudignore file in project root directory?

Same issue here.

.gcloudignore in the root directory
no leading space in the .gcloudignore lines
configured gcloudignore to true in gcloud

And still it tries to upload directories listed in .gcloudignore:
.env
data/

And, from the output of gcloud app deploy I spot some lines as:
copied /home/cuducos/my-project/data/.gitkeep to /tmp/tmpk_29494n/tmp5niqhou8/data/.gitkeep

Since /home/cuducos/my-project/ is the root of the project, and the directory in which .gcloudignore is, and since data/ is on .gcloudignore, why is it uploading data/.gitkeep?

@cuducos I think that's just the local copying portion of the command which will just copy everything in your project dir regardless of the gcloudignore. The actual uploading process comes later which should respect the gcloudignore (confirm which files were actually uploaded by looking at the manifest at the end of the command - make sure to have --verbosity=info set in your command)

I think that's just the local copying portion of the command which will just copy everything in your project dir to a tmp dir regardless of the gcloudignore

That's true.
Still a UX problem in my use case: some directory (data and models) in my .gcloudignore have Gb of files. COpying this seems unnecessary and just slows down the work flow.

What is this? I think I am not involved in this topic. Maybe there was a
mistake?
On Fri, Feb 12, 2021 at 5:46 PM Eduardo Cuducos notifications@github.com
wrote:

I think that's just the local copying portion of the command which will
just copy everything in your project dir to a tmp dir regardless of the
gcloudignore
That's true.
Still a UX problem in my use case: some directory (data and models) in my
.gcloudignore have Gb of files. COpying this seems unnecessary and just
slows down the work flow.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/php-docs-samples/issues/845#issuecomment-778204021,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYO5RX7YERFBZVT2HAP4WDS6UWJ7ANCNFSM4G2CUUZA
.

@cuducos yep I agree. Personally im leaning toward doing:

Creating a tmp dir locally
rsync only things i want to deploy there
gcloud app deploy...
rm tmp dir

@manoadamro if you think there's a bug, please open a new issue (this one has been closed by the author) and provide all the information so that it can be reproduced. The consensus on this bug seems to be all file are copied, but the ones that are uploaded respect the .gcloudignore file.
It should be mentioned that any issue in this file would be an issue in the gcloud utility, which would be a problem across all the languages of the platform. As this tool has been around a long time, I think this is not likely to be the case.

authors: HaipengSu Kenan7 bshaffer cuducos dpkirchner gmdev nicolasassi thdk wrunk

repo: GoogleCloudPlatform/php-docs-samples


text:
fix: Impala strings/objects now return None instead of NaN

Previously Impala strings, chars and other objects filled a dataframe with NaN
instead of NULL which caused mismatch issues when comparing with
BigQuery dataframes.
Moved _column_batches_to_dataframe and _chunks_to_pandas_array functions from the ibis.backends.impala.client into api.py to override default functionality.

/gcbrun


text:
Updating to Spark 3.2.0

We are looking to update to Scala 2.13 (and eventually Scala 3), but that requires us to update Scala to 3.2.0. Is there any plan on updating the Spark base image for the operator?

Hello,
Any update of this subject ?

We would be interested also in updating to 3.2.X

Hey Team, any plans to release an operator version that officially supports 3.2? I checked that it actually works with a custom image of spark 3.2 and the latest operator image (3.1.1), but did not deeply tested.

Hi folks! Can you please offifially support Spark 3.2.0?

+1

Hi
any news regarding this issue?
many Q's here - can you estimate when will it be supported?
thanks :)

I built an image based on spark-3.2.1-bin-hadoop3.2
Is that a problem?

@allenhaozi your image works ? Can you share it ?

@mbaron2
I am currently in the test environment and can work
Because it's still in beta, I can email you if you want, okay?
The main reference is the following items:

spark-docker-file
pyspark-docker-file
spark-operator-docker-file

Is there any new regarding this update to 3.2.0 officially?

Hi @vburenin I built a Spark 3.2.1 image which works fine but in some cases the Spark application shows this trace
22/08/18 11:14:17 WARN WatcherWebSocketListener: Exec Failure java.io.EOFException 	at okio.RealBufferedSource.require(RealBufferedSource.java:61) 	at okio.RealBufferedSource.readByte(RealBufferedSource.java:74) 	at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117) 	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101) 	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274) 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214) 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) 	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source) 22/08/18 11:14:18 WARN ExecutorPodsWatchSnapshotSource: Kubernetes client has been closed (this is expected if the application is shutting down.) io.fabric8.kubernetes.client.WatcherException: too old resource version: 12998019 (13034876)
and hangs for hours without failing.
Could this be somehow related to the image version?
Thx

Spark 3.3.0 was released, I have a custom image of 3.2.1 running with the operator without any issues, and will experiment with 3.3.0 this week.

Hi @josecsotomorales can you share the dockerfile for this?

I would also be interested in this!

I built it myself for testing
allenhaozi/base-pyspark-3.2.1-py-v3.8

if anybody curious, it all works just fine if your target execution image is spark 3.3.

I'm actually using the operator with spark 3.3 with a custom image, see this issue: https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1559

authors: Felix-neko afranzi allenhaozi jordyperlee josecsotomorales leandro-rouberte mbaron2 rahulbhatia2702 sergialonsaco sharonorman78 sousaaguilherme vburenin wolliq


text:
Adding kube-capacity

I'm not really sure what to name this. The upstream repo is just kube-capacity which the naming guide specifically says to avoid for a plugin. Capacity is probably not specific enough. Happy to change this to something like resource-capacity here if that makes more sense.

I think resource-capacity or resource-summary makes sense. Definitely not kube-* as it’s listed in the naming guide.

Do you mind doing git commit --amend --no-edit && git push -f sometime, so that the newly added testing system tests this manifest?

Thanks for the feedback! I ended up going with resource-capacity for the sake of consistency with the standalone name. The new automated testing is pretty great.

lgtm

authors: ahmetb juanvallejo robscott

repo: GoogleContainerTools/krew-index


text:
FR: some library packages rely on postint for proper dynamic resolution

Title is generic as I think other libs may do this too?
The specific example I'm dealing with today are packages libblas3 and liblapack3 that install their shared libraries into a subdirectory of the dynamic library path (e.x. /usr/lib/x86_64-linux-gnu/blas/libblas.so.3), then in post install run update-alternatives to make the symlinks in the library directory.
Postint:
% cat libblas3.postinst.in
#!/bin/sh

set -e

update-alternatives --install /usr/lib/@DEB_HOST_MULTIARCH@/libblas.so.3 \
                    libblas.so.3-@DEB_HOST_MULTIARCH@ /usr/lib/@DEB_HOST_MULTIARCH@/blas/libblas.so.3 10

#DEBHELPER#

exit 0

The binaries that try to load them fail. My testcase is installing gdal-bin and running ogr2ogr --version, which will cry:
root@d876f2ae9478:~# ogr2ogr --version
ogr2ogr: error while loading shared libraries: libblas.so.3: cannot open shared object file: No such file or directory

I'm currently hacking around it with symlinks:
# This is to hack around the fact that liblas3 and liblapack3 run a postinst to
# `update-alternates` and install their libraries in /usr/lib/$(uname -m)-linux-gnu/
#
# We don't run the postist, so just symlink the libraries to where they need to be
genrule(
    name = "libblas.symlinks_mtree",
    outs = ["libblas.symlinks.mtree"],
    # double $$ to pass through the bazel make rule expansion
    cmd = """
    for lib in libblas.so.3 liblapack.so.3; do
        DEB_HOST_MULTIARCH="$$(uname -m)-linux-gnu";
        LIBNAME="$${lib%%.so.*}"; LIBNAME="$${LIBNAME#lib}";
        echo "usr/lib/$$DEB_HOST_MULTIARCH/$$lib uid=0 gid=0 time=0 type=link link=/usr/lib/$$DEB_HOST_MULTIARCH/$$LIBNAME/$$lib"
    done > $@
    """,
)

tar(
    name = "libblas.symlinks",
    mtree = ":libblas.symlinks_mtree",
)

Filing the issue as an errata I guess, as I have a workaround in hand. Does this seem like a "best practice" for something like this? I don't really expect rules_distroless to handle this out of the box unless it was a common library pattern (and it doesn't seem to be).

We currently don't support running any lifecycle scripts as usually they require a running container, technically we could support lifecycle hooks that does basic things like these but i don't have the time do it myself, happy to review a PR

I have looked into this briefly, good news is that as we always install from scratch, we are not concerned with most of the lifecycle commands we might get away with only running post* hooks,  and the bad news is that only way to know if a package has hooks is to inspect the control layer which only downloaded when requested by a target.

It's a hard thing to support generically for sure.
I'm just spitballing, but maybe there's a class of postinst_ functions that'll accept control files to process, and output a weird compat tarball?
For this update-alternatives use case:
postinst_update_alternatives(
    name = "update_alternatives",
    srcs = ["@noble//libblas3/arm64:control"]
)

# then include ":update_alternatives" in your `tars`

The rule could grab the postinst out of each of the sources, look for dh_installalternatives signature in postinst and spit out compatibility symlinks?
Kind elaborate ... but it's more generic than the ca-certificates munging.

update_alternatives is definitely something we can support, looks like its interface is well defined and something we can mimic.
I'd be happy review a PR and debate more on the code.

authors: lazcamus thesayyn


text:
[BUG] Warning: Accessing non-existent property 'tracing' of module exports inside circular dependency

Describe the bug
Node.js Warning about circular dependency. View the trace below —
(node:62719) Warning: Accessing non-existent property 'tracing' of module exports inside circular dependency
    at emitCircularRequireWarning (node:internal/modules/cjs/loader:748:11)
    at Object.get (node:internal/modules/cjs/loader:764:5)
    at checkVariableDeclaration (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:83763:39)
    at checkSourceElementWorker (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:86977:28)
    at checkSourceElement (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:86808:17)
    at Object.forEach (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:377:30)
    at checkVariableStatement (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:83776:16)
    at checkSourceElementWorker (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:86946:28)
    at checkSourceElement (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:86808:17)
    at Object.forEach (/Users/tushar/Documents/Projects/ts-macro-schema/node_modules/typescript/lib/typescript.js:377:30)

Code to reproduce
Simply run npx ttsc --watch
Expected behavior
No warning should occur
Additional context
package.json
{
  "devDependencies": {
    "jest": "^29.3.1",
    "ts-macros": "^2.0.0",
    "ttypescript": "^1.5.13",
    "typescript": "4.8.4"
  },
  "scripts": {
    "test": "jest",
    "build": "ttsc -b"
  },
  "license": "MIT"
}

Does the transformer still work correctly after the warning?

Yes. It works just fine. Weirdly I do get this issue in watch mode only. Otherwise I don't get this warning.

authors: GoogleFeud tusharmath

repo: GoogleFeud/ts-macros


text:
[Module Port - Theme] Protoncord

This is currently marked as a draft while I await a response from the creator. A screenshot will be provided when a response is provided.

The creator has responded:

repo: GooseMod/Modules


text:
I think it's working with SOD now. Try the 3.4.3.3 release.

          I think it's working with SOD now. Try the 3.4.3.3 release.

Originally posted by @GovtGeek in https://github.com/GovtGeek/Outfitter/issues/17#issuecomment-1984945776

firstly thank you so much. it has more features then i could ever need. question i remember outfitter having stances for warriors e.g in def stance sword and shield equipped. i can physically  click on the bar with the outfits i have no idea how to bind them but its not changing stances if that makes sense. so if i have a macro for cast taunt change stance i will taunt but my gear stays as if its in arms. u just need the 3 stance options added or perhaps its there somewhere ?

I think there used to be some stance stuff for warriors, but I don't know what happened to it (I'm not the original creator). I know you can create custom scripts to get the same effect for now.
-- $EVENTS UNIT_AURA PLAYER_ENTERING_WORLD
-- $DESC Equips the outfit when you are in a stance with the specified name

if GetShapeshiftForm() == 2 then
equip = true
end

Use the above for your Defensive Stance outfit. You can get there by clicking the down arrow next to the outfit and selecting the Automation -> Script option. It may say "Script (None)".
If you're trying to get it into a macro, you can ignore the stuff above and use the command line option
/outfitter wear Tanking and replace Tanking with whatever you named your outfit. Don't forget you can't change gear in combat, except weapons. Unfortunately, the weapon swap was disabled in Outfitter because of some API changes by Blizzard, so Outfitter won't even change weapons right now.

authors: GovtGeek rygarstrong

repo: GovtGeek/Outfitter


text:
Error while launching tw plot

Hi, I'm getting this error when launching tw plot on my csv file.
File "/usr/local/bin/tw", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/src/app.py", line 49, in main
    app.run()
  File "/usr/local/lib/python3.9/site-packages/cement/core/foundation.py", line 916, in run
    return_val = self.controller._dispatch()
  File "/usr/local/lib/python3.9/site-packages/cement/ext/ext_argparse.py", line 808, in _dispatch
    return func()
  File "/usr/local/lib/python3.9/site-packages/src/controller.py", line 69, in plot
    pf.calculate()
  File "/usr/local/lib/python3.9/site-packages/src/plot/base.py", line 205, in calculate
    self.positions[t.symbol].quantity -= t.quantity
TypeError: unsupported operand type(s) for -=: 'str' and 'str'

Any idea if it's my problem?

Could be, depends on where you got the CSV from. Did you follow the instructions on the readme to obtain it? There are multiple different CSVs tastyworks will generate.
If so, sounds like something that needs to be addressed. Looks like one of the quantity fields is being typed wrong. Any chance you could figure out what line it is? If you're willing to share your CSV (you can anonymize it if you want) I can solve this quicker.

I found the problem. This is already fixed on the main branch. Let me publish a new version for you. Can you verify it works with the newest version?

Thanks for the fix, that error is solved!
But when I run it again it finds another conversion error .
/usr/local/lib/python3.9/site-packages/src/plot/commands.py", line 22, in plot     pf = Portfolio(df, net_liq=netliq)   File "/usr/local/lib/python3.9/site-packages/src/plot/csv.py", line 55, in __init__     self._calculate()   File "/usr/local/lib/python3.9/site-packages/src/plot/csv.py", line 185, in _calculate     t = Trade(trade)   File "/usr/local/lib/python3.9/site-packages/src/plot/csv.py", line 28, in __init__     self.quantity = float(trade['Quantity']) ValueError: could not convert string to float: '1,000'
I couldn't find something that in the "quantity" column had some strange numbers, I got some 0 but in the "Regulatory fee adjustment" type.
I don't know how to debug it and put a breakpoint on it, but could you add some error message that says at what row of the csv the error occurs?  Maybe that could help.
Thanks anyway!

Ah good catch! Glad the other error is fixed. I had never found this because I don't think I've ever traded that large of a quantity of something. Will address this when I can.

If this didn't fix the issue, please reopen. Hope you don't run into anything else and thanks for filing the bugs!


text:
🛑 Grammle.de is down

In 09cafad, Grammle.de (https://grammle.de) was down:

HTTP code: 421
Response time: 489 ms

Resolved: Grammle.de is back up in fee55f7 after 22 minutes.

repo: Grammle/status


text:
InternalCommand::from_precomputed is hard to understand and might be simplified

https://github.com/Granola-Team/mina-indexer/blob/9354e9fdd82d9c71ccfb4ac9efad6f780d51c64a/rust/src/command/internal/mod.rs#L74

This was reverted

repo: Granola-Team/mina-indexer