Lease events have wrong time stamp

Provider: akash1f6gmtjpx4r8qda9nxjwq26fp5mcjyqmaq5m6j7
Lease event of type "reason": "Scheduled" has a correct timestamp:
{
  "type": "Normal",
  "reportingController": "default-scheduler",
  "reportingInstance": "default-scheduler-mainnet-ewr1-provider-master",
  "time": "2021-07-26T18:21:05.891718Z",
  "reason": "Scheduled",
...
}

However, every other Lease event has an incorrect time stamp. Example:
{
  "type": "Normal",
  "time": "0001-01-01T00:00:00Z",
  "reason": "SuccessfulCreate",
  "note": "Created pod: web-75979bd7df-rqvm5",
  "object": {
    "kind": "ReplicaSet",
    "namespace": "5hi5um9qfk7ve4lce1dech3qne9qlna38bhgr93thbqae",
    "name": "web-75979bd7df"
  }
}

@coffeeroaster can you give us a bit more detail in the ticket, incase we are unable to pull logs before we get to this.

Fixed.

Based on the time displayed, we're substituting a 0 value for a unix time stamp and then creating the one you see there. Thanks for reporting this.

I was able to reproduce this pretty quickly & it is still an issue.
{
  "type": "Normal",
  "time": "0001-01-01T00:00:00Z",
  "reason": "Started",
  "note": "Started container redis",
  "object": {
    "kind": "Pod",
    "namespace": "39pfap27vjj338nv5db0rqk2uvqscih0vss9i0q3op9b2",
    "name": "redis-6df85cfc55-rlcpx"
  },
  "lease_id": {
    "owner": "akash1zmjsezgj3ul8dqunx8dhah38t9tr2gn2cf5pqj",
    "dseq": 1211,
    "gseq": 1,
    "oseq": 1,
    "provider": "akash1gx4aevud37w4d6kfd5szgp87lmkqvumaz57yww"
  }
}

I'll track this down and figure out where we need to be adding a timestamp

Is this on mainnet @hydrogen18?

No it's on my testnet which is ahead of mainnet

The .EventTime field from the kube API is always 0.
I just rant kubectl get events --watch -A --output=json in a terminal and I don't event think event time is a real thing that comes from kubernetes? It shows stuff like this
{
    "apiVersion": "v1",
    "count": 1,
    "eventTime": null,
    "firstTimestamp": "2021-09-14T19:54:06Z",
    "involvedObject": {
        "apiVersion": "apps/v1",
        "kind": "Deployment",
        "name": "web",
        "namespace": "6hvm3538ll2b52unpvsb6lear1psftb60drs7uj520h5g",
        "resourceVersion": "2573",
        "uid": "3977d7b3-116e-4e63-8e1a-7b2e44558073"
    },
    "kind": "Event",
    "lastTimestamp": "2021-09-14T19:54:06Z",
    "message": "Scaled up replica set web-5b59b959d6 to 1",
    "metadata": {
        "creationTimestamp": "2021-09-14T19:54:06Z",
        "name": "web.16a4c8584c9f0da7",
        "namespace": "6hvm3538ll2b52unpvsb6lear1psftb60drs7uj520h5g",
        "resourceVersion": "2802",
        "uid": "bbeac50b-cf0f-4018-9c65-e8d53994188e"
    },
    "reason": "ScalingReplicaSet",
    "reportingComponent": "",
    "reportingInstance": "",
    "source": {
        "component": "deployment-controller"
    },
    "type": "Normal"
}

The CreationTimestamp is literally when the resource was created, so it isn't accurate for the event. Maybe we just fill it in on provider side with time.Now() and call it done?
It looks like eventTime being null is an expected behavior: https://github.com/kubernetes/kubernetes/issues/90482#issuecomment-619440160

The LeaseEvent struct doesn’t seem to have a time field in master.
Closing this issue
https://github.com/ovrclk/akash/blob/c89507db22a272436f0707360a2c695d832e9cb5/provider/cluster/types/types.go#L153-L160


DDEV-Live images must be swappable so they can be tested

Bug Description:
As we discussed in our meeting last Wednesday, there is currently no way to change the images that DDEV-Live uses for nginx or php. That means there's no way to test these images in context.
So it's absolutely critical that DDEV-Live provide a way to use custom images (these images) for testing in the DDEV-Live context.
This issue was delegated to @dclear and @unn at the meeting. It should probably be moved to the ddev-live issue queue when you're ready to do so.
Related links or issues:
Definition of Ready Checklist:

[ ] Provides steps to reproduce
[ ] Dependencies identified
[ ] Sized by team

RProduct Owner AScrum Master CEng. Lead ITeam
Definition of Done Checklist:

[ ] Deployed on test environment
[ ] Steps do not reproduce
[ ] Unit test and E2E coverage updated (if applicable)
[ ] Builds without errors
[ ] Internal documentation updated (if required)

REng. Lead, Team AScrum Master CIProduct Owner

Issue moved to drud/ddev-live #331 via ZenHub


Providing ground truth maps to prevent purely black or purely white maps

I have ground truth masks and source images for normal and anomalous data samples in my dataset and I have arranged them in the following format:
datasets/custom/test/class1/normal/  # 59 source images
datasets/custom/test/class1/anomalous/  # 53 source images

datasets/custom/test_maps/class1/normal/  # 59 ground truth maps \in {0, 255}^(1, W, H)
datasets/custom/test_maps/class1/anomalous/  # 53 ground truth maps \in {0, 255}^(1, W, H)

datasets/custom/train/class1/normal/  # 2370 source images
datasets/custom/train/class1/anomalous/  # 6 source images

datasets/custom/train_maps/class1/normal/  # 2370 ground truth maps \in {0, 255}^(1, W, H)
datasets/custom/train_maps/class1/anomalous/  # 6 ground truth maps \in {0, 255}^(1, W, H)

With the above arrangement, I use the following command:
python runners/run_custom.py --supervise-mode other --ground-truth-maps --blur-heatmaps
The code runs without any errors. However, when I go into the results folder, then I see that the ground truth maps are completely black or completely white images. They do not include the maps that I stored in the folder above. I am not sure why this is happening.
Thank you in advance for your help and suggestions.

As an update, I also get this message at the end of training:
Computing GT test score...
Skipped computing the gtmap ROC score. for some samples no ground-truth maps were found

It is not able to recognise the gt maps in the folder for some reason.

My first guess is that the names in, e.g., datasets/custom/test_maps/class1/anomalous/ do not match the ones in datasets/custom/test/class1/anomalous/. For example, there is a datasets/custom/test/class1/anomalous/cute_cat_xyz.png but the corresponding ground-truth map is named datasets/custom/test_maps/class1/anomalous/cute_cat_xyz_map.png. The file names need to be exactly the same for the code to recognize them as pairs.
Have a look here. This defines the list of all ground-truth filepaths. You can log/print self.gtm_samples to see which ground-truth samples it found. Can you check that?
PS: You don't need any normal ground-truth maps. The code automatically creates those as completely black images. Missing anomalous training ground-truth maps are also automatically interpolated as completely white images. So you don't need a training ground-truth map for every sample. However, you need all ground-truth maps for anomalous test images. Otherwise, the code skips computing the pixel-wise AUC.

@liznerski Thank you for the link to the code. I did have a difference in the file names - the source images were .jpg while the masks were .png. I thought this would not matter, but the code clarified it. I changed the extensions and now the gt maps are loaded in the ds_preview.png file.


Release/0.3.1

Description

Motivation and Context

Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[x] The changes introduced by this pull request are covered by existing or newly introduced tests.
[x] The package documentation and framework documentation in signac-docs are up to date with these changes.
[x] I have updated the changelog and added any related issue and pull request numbers for future reference.

@cbkerr Have you run bumpversion patch? That's the next step this needs, I think.


UI Tests check is failing on CI

Opening a new issue since the check is failing on the latest commit on master: https://github.com/widgetti/ipyvolume/commit/1c08f9fdde4219be873f7c45e02ecec2540d5876

Opening the report shows some differences with the UI elements:

Not sure if this was introduced in a previous PR, but probably updating the reference snapshots should help fix it.

Also the UI Tests setup could be updated to use a newer @jupyterlab/galata: https://github.com/jupyterlab/jupyterlab/tree/master/galata
For example:

https://github.com/voila-dashboards/voila/tree/main/ui-tests
https://github.com/jupyter-widgets/ipyleaflet/tree/master/ui-tests

Upgrading to the newer setup would also allow for integrations like automated snapshots updates with a bot: https://github.com/jupyterlab/maintainer-tools#update-snapshots

Partially fixed in https://github.com/widgetti/ipyvolume/pull/424
(not yet upgraded, will keep that in mind!)


Add flip operator refactoring

Suggestion

🔍 Search Terms

flip operator, flip operators, refactoring
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[ x This could be implemented without emitting different JS based on the types of the expressions
[ x This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Implement flip operator refactoring for swapping left and right operands and update operator if needed
📃 Motivating Example
Before:
const a = 1 < 2

After
const a = 2 > 1

@RyanCavanaugh Just to clarify, the motivation here is to help developer flip pieces of code without having to copy/paste and rewriting the code. For example we used to write comparisings in the following way: variable > literal value, because it is easier to understand. Code example:
// harder to understnad
if (5 < position) {
    // ...
}
// much easier
if (position > 5) {
    // ...
}

The refactoring activation range is operator only (>), so it shouldn't be annoying for existing users. So this refactoring can be small, but really nice addition to TypeScript IDE possibilities.


Implement add video from gallery

Hi, and happy new year! 🎉 🎉
This PR:

implements functionality for adding videos from gallery
implements functionality for trimming videos
adds optional support for force scaling videos of different aspect ratios, and validation checks for unsupported videos
adds minor bug fixes and improvements
adds translations for new UI-related functionalities.

Please let me know if you'd like any changes, thanks!

[x] I have added a description of the change in CHANGELOG.md.
[x] I have added my name in the CONTRIBUTORS.md file if it wasn't already present.

Ahh I see, thanks, I just pushed a commit following the same approach as in getToday
Please let me know if you still experience the same issue 😊

Also, I am making some changes on trimmer package and will let you know when it's done!

Alrighty!

It worked with the first model of date format selected (the one that goes in the top right), but I've got a few more problems:
1 - Save button can be pressed if location is enabled but loading or failed, causing this:
[Geolocation] - Failed to decode location: PlatformException(IO_ERROR, A network error occurred trying to lookup the supplied coordinates (latitude: -22.595104, longitude: -46.526899)., null, null)
2 - Movie created is broken, is skips all videos but the gallery one, which is played in slow motion. I suspect this is because the bitrate is not being set, please check the movie first conversion. It may also be possible that we need to set codec for audio stream. A good way to check if everything is correct is printing all streams of the video after processed and compare it with the ones recorded by the app, everything necessary for concat demuxer should match (codecs, number of streams, bitrate, resolution and maybe a few more I don't remember).
3 - If the date format selected is the second one (written, on the bottom left), video is not saved with that same error, it constains the month in the path instead of the correct filename, I think you're grabbing the wrong method for it still.
4 - UI in calendar editor is overflowed on my device, I think it's related to the widget added next to the edit subtitles button.
5 - Video resolution popup is broken, saying "yes" does nothing and the loading in the save button starts before it shows up. After exiting the popup, save button does not work anymore.

I just pushed a commit intended to fix 1, 3, 4 & 5 🙏🏽

Thanks @daoxve!
1 - Seems fixed
3 - Fixed
4 - Still happens, overflows by 7 pixels. Please check with device_preview for testing in different screen sizes.
5 - It still has some weird behavior and the scale is not a good option after giving it some thought, I think we should really block the addition of videos that are not 16:9 for this release. So the popup can become only "This video is not accepted" titled even before we go to edit recording page.

Another idea, I think we should make the saving process a not dismissable popup on top of the screen instead of showing the loading on the button. This way we make it impossible to click on all the elements while it is still processing.

Thanks @daoxve!
1 - Seems partially fixed, the error does not occur but the save button is available even if the locale has not appeared on top of the videoplayer yet 3 - Fixed 4 - Still happens, overflows by 7 pixels. Please check with device_preview for testing in different screen sizes. 5 - It still has some weird behavior and the scale is not a good option after giving it some thought, I think we should really block the addition of videos that are not 16:9 for this release. So the popup can become only something in the lines of "This format of video is not accepted yet. Make sure it was recorded in landscape (16:9 aspect ratio)" even before we go to edit recording page.
Also, the video count update has some issue, it added 2 or 3 a couple times when I was testing.

Okies... 1 & 4 should be fixed with the latest commits.
I'm also working on 5; should the validation check for portrait videos also be moved?

Thanks @daoxve!
1 - Seems partially fixed, the error does not occur but the save button is available even if the locale has not appeared on top of the videoplayer yet 3 - Fixed 4 - Still happens, overflows by 7 pixels. Please check with device_preview for testing in different screen sizes. 5 - It still has some weird behavior and the scale is not a good option after giving it some thought, I think we should really block the addition of videos that are not 16:9 for this release. So the popup can become only something in the lines of "This format of video is not accepted yet. Make sure it was recorded in landscape (16:9 aspect ratio)" even before we go to edit recording page.
Also, the video count update has some issue, it added 2 or 3 a couple times when I was testing.

Okies... 1 & 4 should be fixed with the latest commits.
I'm also working on 5; should the validation check for portrait videos also be moved?

I think it's better, we can check before navigating to video editing page and show a popup if it's not supported

Done ;)

Another idea, I think we should make the saving process a not dismissable popup on top of the screen instead of showing the loading on the button. This way we make it impossible to click on all the elements while it is still processing.

Do you mean like a dialog?

Yes!

Also done :)

Now I think we just have the movie issue 😅

2 - Movie created is broken, is skips all videos but the gallery one, which is played in slow motion. I suspect this is because the bitrate is not being set, please check the movie first conversion. It may also be possible that we need to set codec for audio stream. A good way to check if everything is correct is printing all streams of the video after processed and compare it with the ones recorded by the app (not in the code, I mean just visually comparing video streams info), everything necessary for concat demuxer should match (codecs, number of streams, bitrate, resolution and maybe a few more I don't remember).

Fixed now, thanks!!


Topology-aware Environment for looking up API management endpoints and their credentials

Client code should be shielded from how settings specific to an environment are injected
as this mechanism might change.
The "environment" package provides abstraction for settings and all their sources to evolve
independently from clients like k8s extensions or operators. Environment here should be understood
as least common denominator across any consumers. Ideally the package resides in a common golang
library shared between consumers like k8s extensions and operators. Most environment setting
influence how clients interact with Prism, like which credentials to use. Hence prism-go-client can serve as common golang library.
Moreover multiple clients like Kubernetes clusters might share certain properties of an environment
like the categories and project. However idea is that each k8s cluster environment is unique to
allow infrastructure resources created on behalf of a k8s cluster to be associated with this particular k8s cluster.
We envision the following sources for environment settings:

"Local" using OS environment variables as source
"SecretDir" expecting k8s secret to be mounted as directory into container
"ConfigMap" expecting k8s config map to b mounted as directory into container
"Kubernetes" expecting access to k8s via informers for reading secrets directly

Following is the interface through which environment is accessed.
// Environment in which a Kubernetes has been deployed.
type Environment interface {
	// GetManagementEndpoint retrieves managment endpoint
	GetManagementEndpoint(topology Topology) (*ManagementEndpoint, error)
	// Get retrieves settings applicable to the environment like project
	// or category to which resources created on behalf of Kubernetes cluster are
	// assigned to.
	// These settings might have to be explicitly propagated to resources.
	// Return whether lookup was successful to distinguish from nil as value.
	Get(topology Topology, key string) (interface{}, error)
}

The same interface is implemented by all environment sources/providers.

LGTM


documentation and defaults improvements

Codecov Report

Merging #286 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #286   +/-   ##
=======================================
  Coverage   71.66%   71.66%
=======================================
  Files           8        8
  Lines        1094     1094
=======================================
  Hits          784      784
  Misses        263      263
  Partials       47       47

Flag
Coverage Δ

#unittests
71.66% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

main.go
62.43% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Nope. Until merged10:34, 27 ноября 2017 г., Sergey Korol notifications@github.com:@sskorol commented on this pull request.
In docs/video.adoc:

@@ -0,0 +1,75 @@
+== Video Recording
+NOTE: This feature only works when browsers are run in containers. VNC type containers should be used from <> section.

+Selenoid can capture browser screen and save it to https://en.wikipedia.org/wiki/MPEG-4[MPEG-4] video file using https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC[H264] codec.
+Video recording works by attaching a separate container with https://www.ffmpeg.org/[video capturing software] to running browser container.
+
+To setup this feature you should:
+
+. Pull video recorder image once: docker pull selenoid/video-recorder
+
+Without docker videos will be stored in video directory, relative to binary.
+
+With docker:
+
+. Mount host directory for video to /opt/selenoid/video/ (this is default value for video-output-dir selenoid arg in docker)
just curious when did this path /opt/selenoid/video/ change?..
when I tested video recording feature, it was required to map host folder with /output (at least @vania-pooh said that it should be default)...
@lanwen just to confirm: should we use this path for mapping now?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
-- Kirill Merkushev


[SMALLFIX] Removed explicit parameter type in UnderFileSystemRegistry

Removed an explicit parameter type in the UnderFileSystemRegistry class.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9982/
Test PASSed.

Merged build finished. Test PASSed.

LGTM


File Explorer reverts to origin size in FancyZones everytime it is opened.

Microsoft PowerToys version
0.35.0
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Windows File Explorer opens in its native size, or at least the last size it was when I last used it and never snaps back into the FancyZone I had put it in.
✔ Expected Behavior
For File Explorer to snap to last FancyZone position
❌ Actual Behavior
Opens anywhere on the screen, usually bottom centre and in the last dimentions it was used.
Other Software
No response
I have a 43" TV Monitor, so I use FancyZones to create a quad monitor with approx four HD screens.
If I use the Microsoft Key + right or left arrow to move File Explorer to the FancyZone I want it in, then resize, ever so slightly so that it fits exactly to the FancyZone size, then File Explorer window will snap-ish back to that what appears to be that position when it is closed and reopened, but it is slightly mis-sized.  Yet to try it on reboot, but will report back.

It will indeed snap-ish to the last FancyZone it was in but still slightly misplaced.  If I move it to a different FancyZone, close it and reopen it will snap-ish back to the previous zone, so, still appears not to be snapping properly.
Any advice, greatly accepted.

@IanC2059
there are some known limitations when it comes to Explorer and the way it is snapped to the last known zone.
To make sure we have a full picture of your scenario, can you please use ScreenToGif or any other screen capturing tool to record the exact sequence of steps to replicate the problem?
Thanks.

Thanks, Enrico for your response.
If there is a known issue with Explorer I may just need to live with it.
If I open File Explorer, then use  Win + > to move it into the bottom left of my FancyZones quad screen layout on my 43" monitor, it does indeed works as expected, what the image enclosed shows is when I close File Explorer and reopen it, File Explorer overlaps all other quadrants by a few, maybe five pixels, which means it is not snapping back to the last position.
As I said above, if there is a known issue with Explorer, I suppose I just need to live with that, and I thank you for answering.
All the best,
Ian

@IanC2059
to you have a multi monitor configuration?

No, Enrico, as I said above I have a 43 inch TV as a Monitor which is divided into a quad monitor configuration using FancyZones

File explorer is known to modifies its windows positions, so, as @IanC2059 stated, we shouldn't interfere with its logic.


Automatically reload houston when app.debug is True

Set flask reloader to the same as app.debug so during development,
houston restarts when the code changes.

/rebase


[No QA] Display workspaces in settings page

Details
Displays free policies (workspaces) in the settings page.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/166038
Tests

Make sure you pull and rebuild auth.
Comment out these lines on dev.
Go to https://expensify.com.dev/ and sign in
Go to https://www.expensify.com.dev/api?command=Policy_Create&policyName=WorkspaceTest&type=free to create a new policy w/ type free
Run E.cash and sign into the same account you used on E.com
Go to settings, verify that you see workspaces at the top of the list.
Repeat step 4 (except with a different policy name)
Verify that you see both free policies.

QA Steps
No QA for now.
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[ ] Android

Screenshots
Web

Mobile Web

Desktop

iOS

Android

Looks good to me. I do wonder if we want to make the Workspace icon consistent across the board and have it use a green background everywhere? I think it uses a green background in the Create menu, so we might want to use it here as well as the workspace editor itself.

I kinda like the idea of randomizing it to one of our colors like the default profile icons?

Random design feedback but curious if this hover style is correct as all the other hover styles are darkening the already grey areas e.g.
What we have now for non workspace icon on hover...

workspace icon in this PR

what I'd expect to see based on the behavior of darkening the grey area further...

anyways pretty small detail but curious if @shawnborton has a preference here.

I agree with you Marc, but if we make this icon use a green background to match the other areas where we show the new workspace, I would say we don't even need a hover style for the icon itself. Especially when we plan to have user uploaded avatars there, I don't think we need a hover style for the avatar that is shown.

Style and code updated 👍

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging in version: 1.0.71-1🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.73-3🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Help us avoid credential leak into containers - Use a default credential file path

TL;DR
Use google's usual default path (google_credentials.json) for generated application credentials, or alternatively allow us to specify the path of the credentials file that gets created.
This will help us avoid by default a significant vulnerability that it's easy to introduce by mistake: baking credentials into images for all to see.
Detailed design
Lets say I use this action to do a typical thing: build a container and push it to GCR:
name: build_container_and_push_to_gcr

on:
  workflow_dispatch:

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1

      - name: Authenticate with GCP Workload Identity
        id: auth
        uses<EMAIL_ADDRESS>        with:
          create_credentials_file: true
          workload_identity_provider: REDACTED
          service_account: REDACTED

      - name: Setup gcloud
        uses: 'google-github-actions/setup-gcloud@v0'

      - name: Configure Docker to push images to GCP
        run: gcloud auth configure-docker

      - name: Build
        uses: docker/build-push-action@v2
        with:
          context: .
          file: Dockerfile
          tags: this-contains:the-account-credentials

      - name: Other stuff
         run: echo "Do testing stuff which might require the credentials file"

The auth step creates a credentials file with a randomised name - like /home/runner/work/me/myrepo/4c33e43f60be11e1a7b5d5f4.
The problem occurs when Dockerfile contains the following extremely common line:
COPY . .

If you're like me, you'll have a .dockerignore file will include something like:
# NEVER bake in environment variables or credentials
.env
.env*
google_credentials.json

But, because in this case the credentials file name cannot be known a priori, the .dockerignore can't be configured not to copy it in.
Proposed solution

Revert to a predictable file name, or make user specify as a required argument
[Optional, but nice] Check for presence of .dockerignore and if it doesn't contain the file then warn the user
[Optional, but nice] Add a  boolean--update-dockerignore option, true by default, that creates or updates a .dockerignore file with the credentials file name

A possible workaround
As one possible workaround, I'd have to introduce a step something like
    - name: Prevent secret from getting into container
      # WARNING UNTESTED!!!
      run: touch .dockerignore && echo ${${{ steps.auth.outputs.credentials_file_path }}##*/} >> .dockerignore

    - name: Now its safe to build
      #...

Additional information
I also think it's a bit more intuitive for it to end up in google_credentials.json, the location given in most of google's tutorials on application credentials.

Hi @thclark - thank you for opening an issue.

Use google's usual default path (google_credentials.json) for generated application credentials, or alternatively allow us to specify the path of the credentials file that gets created.

This is not a default that I'm aware of. gcloud definitely doesn't use that naming, and I haven't seen it anywhere else. It's not mentioned anywhere on cloud.google.com.

The credentials are checked out into the workspace because that's the only way to ensure they are available for Docker-based actions to authenticate seamlessly. The auth action also automatically removes the credential at the end of the job via a post step, so the credential will never persist between jobs. I described this in more detail in https://github.com/google-github-actions/auth/issues/109#issuecomment-1017916947.
I think the most elegant solution is to re-arrange your steps. You don't need authentication to build the image, so:

Build
Auth
Push

Additionally, if you only need to push to GCR/GAR, you don't need to install and configure gcloud. You can authenticate using an access token generated from the auth action, and then set create_credentials_file to false to prevent creation entirely, as shown in https://github.com/google-github-actions/auth/issues/104#issuecomment-1004891427.
Alternatively, you could do as suggested and add ${{ steps.auth.outputs.credentials_file_path }} to your dockerignore.
I'm opposed to any tight coupling of this action to anything related to Docker.

@sethvargo we had a few issues about pushing to GAR/GCR (https://github.com/google-github-actions/auth/issues/104#issuecomment-1004891427, https://github.com/google-github-actions/auth/issues/50#issuecomment-973450688) should we have an example that showcases this?

@bharathkkb created a new issue to track that.

If that example were to cover this use case and note it, that'd be a good step to addressing this - people are most likely to piece together steps off the net (like I did) unless they see a full example.
I'm working on mapping application default credentials into my test container, avoiding the need for creating the creds file, which I think might be a more elegant solution overall (inspired by this very useful article). If I get it working I'll put something in #126.

Hi,
I'm facing a problem that is somehow related to this issue.
I'm trying to use goreleaser to build and publish artifacts to GCS and GCR, but goreleaser will not run because the repo is in a dirty state after the gcp credential file is created.
If I'm able to configure e.g. a subdirectory where the credential file is generated, I can add that to the .gitignore file and goreleaser should ignore the generated file when validating for a dirty state.
ref: https://goreleaser.com/errors/dirty/

Thanks @sethvargo that makes things way simpler :)

I still need to cut v0.6.0 - want to get a few other changes in.


Fix content-index self-to-self entry not found issue

I found this issue when doing the other test. It seems for the self-to-self index, the value object does not have the origin (null) which make the caller think the index not exist.

Actually I'm not quite sure about this part of code too. So @jdcasey  maybe you can give use some introduction of your thoughts on this to help understand.


Explore if/how we can make use of DocC custom headers/footers instead of parsing the content

https://twitter.com/ethankusters/status/1533114184572862465

@0xTim @_sa_s Swift-DocC also has experimental support for placing a custom header.html and footer.html in your DocC catalog. That’s how the documentation on http://Swift.org is built: https://www.swift.org/documentation/docc/

Here’s the header.html in DocC’s documentation: https://github.com/apple/swift-docc/blob/41f116f72cd3cf6392c2f82d7b72ed3c5ccb735a/Sources/DocCDocumentation/DocCDocumentation.docc/header.html
And then you pass this experimental flag when building: https://github.com/apple/swift-docc/blob/41f116f72cd3cf6392c2f82d7b72ed3c5ccb735a/bin/preview-docs#L115
Definitely something I’d be interested in working with you all to formalize as a (non-experimental) feature!


Can't change the directory where the VMs get stored

I can't change the directory where new VMs get stored and quickgui looks for existing ones. When I click on the current path (/home/seb for me) nothing happens.
I am using the window manager qtile (X11). My distro is NixOS and I'm running the latest release, installed through the nix package manager.
Thanks for the help and your time.

Same issue here on artix with i3wm.

Fixed via https://github.com/quickemu-project/quickgui/pull/130 which makes sure zenity is included as a dependency.


[WFLY-13917] The org.jboss.resteasy.resteasy-crypto module requires t…

…he bouncy castle dependencies be exported.
https://issues.redhat.com/browse/WFLY-13917

It sounds like these modules may need a review, if resteasy-crypto is being added to the classpath of the deployment this means private API is being made available (This isn't the only case, just the one I happen to see today).
Instead does the deployment really need these modules or is RestEasy relying in the ClassLoader of the deployment when really it should be using it's own?

Instead does the deployment really need these modules or is RestEasy relying in the ClassLoader of the deployment when really it should be using it's own?

This I'm not entirely sure of. I don't really know how the providers are loaded, but they seem to be processed on the deployments class loader. I'm not yet familiar enough with JAX-RS or RESTEasy to know if that is correct or not. Maybe @asoldano or @ronsigal have an idea there.

I'm thinking we should put this on hold for a while, as it's really an improvement to avoid requiring users to add the dependency manually to their deployment, right? I think we need to evaluate which are the documented usage scenarios of resteasy-crypto and verify if the BC api are really needed for those or not. @liweinan has some experience on this, but he will be back after the holidays in China are over.

Also if we are going to have a review I think we should review what is the relationship between the cryptographic requirements of Rest Easy and the security services provided by the application server.
From the perspective of the security team we are moving to focus more on the streamlining of common security requirements so will likely be exploring our relationship with JAX-RS quite a bit over the next 12 months.

My main concern is for a user to use a multipart/signed content type for an accept header they have to add a dependency to a private module. It's been like this forever as far as I can tell, but seems wrong to me. An example is the MultipartSignedWriter which directly uses Bouncy Castle.
As to why it needs to be on the deployment class path, that part I do not know. My guess was it had something to do with it being a provider. That is a guess though as I'm still learning the JAX-RS spec and RESTEasy :)

I generally don't like the 'hold' label as it leads to PRs that should progress getting ignored, but I'll put it on this one given the open discussion above and the fact that all the participants have the perms to remove it when appropriate. :)

Reviewing bouncy castle use is something we want to look at this year, maybe now is time to resurrect this discussion?

@jamezp this looks like a stalled one to catch up on soon.

@jamezp / @fjuma This maybe sounds like a discussion for the new year to check what is really needed here with the other work that is happening?

+1 I'll take another look too as I know RESTEasy better now :)

@jamezp Is this PR still relevant? There haven't been any updates on it in a long time and there are also conflicts that need to be resolved.

I'll go ahead and close it. I would imagine it still doesn't work, but doesn't seem like it's an issue for anyone.


perf(transformer): inline enter_expression methods

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6125  👈
#6124
#6123
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f03c6d13c4340e6331bc43b39e4d9b53ecc234c8
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Change default CPU resource to 1000m in both Platform and Platform Operator charts

https://hivemq.kanbanize.com/ctrl_board/22/cards/25820/details/

The examples are fixed as well now.


Unable to use context menu when zoomed out to hide labels

When zoomed out and the labels for the nodes are hidden, I can hover over a node and see the label and the context menu kebab. If I try to use the kebab, I cannot because it disappears when I try to get to it.

You can see it live at: https://pf-v5.surge.sh/ by choosing Node options and turning on Context menus then zoom out until the labels disappear, hover on a node and try to use the kebab menu.

Fixed by #249


[react-form-state][docs]Correct doc example: validateArray => validateList.

@rox163 if you rebase this you can merge :)

Since I'm dealing with these form components atm, do you want me to add some CodeSandbox links for these examples?


chore: Add API designer card to Overview page

Signed-off-by: hemahg<EMAIL_ADDRESS>What this PR does / why we need it:

Add API designer card to Overview page

Which issue(s) this PR fixes
fixes https://issues.redhat.com/browse/MGDX-229
Where to find Story
https://619e1921b3e38b003afeb2be-dehmitbijy.chromatic.com/?path=/story/appservices-overviewpagev4--overview-page-v-4

lgtm!


Wait for Cloud-Init To Complete

Version Reports:
Distro  version of host:
cat /etc/*release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu 18.04.1 LTS"

Terraform Version Report
terraform --version
Terraform v0.11.8
+ provider.libvirt (unversioned)
+ provider.template v1.0.0

Libvirt version
virsh --version
4.0.0

terraform-provider-libvirt plugin version (git-hash)
0.5.0 (Downloaded binary from releases)

Description of Issue/Question
I've got cloud-init setup to install an Ansible playbook on the VM. Is there any way to wait until the cloud-init script has completed before outputting values?

Additional Infos:
SELinux is disabled, ufw is inactive. Nothing special about my config.

Hi ! Check this out https://github.com/hashicorp/packer/issues/2639. Adding this would make the codebase rely on unstable 3party changes, an would impact much the codebase for this.
You can solve this e.g in your workflow with a remote exec and looping.p

@kjenney are you satisfied with the answer more or less ? to me we can close this because in a realistic world you can use remote-exec and wait for it or doing other workflow around the core.
In the terraform-libvirt part i see this really far away from a future implementation ( is not what i would prioritize as high, imho).
feel free to ask any add info

Closing for additional question feel free to join the gitter chat! Thx


Using custom stack of technologies

If I want to switch generated application to have react.js and asp.net core 8+,
what would I need to do?
Can you provide some guide on what files to change?

i would like to know as well i had a similar problem


dbus idle inhibitors leak

I've noticed a few times some games will increase the inhibit count but never decrease it again.
Checking the spec I noticed this part:

Inhibition will stop when the UnInhibit method is called, or the application disconnects from the D-Bus session bus (which usually happens upon exit).

Afaict from a skim of the code the latter part is not implemented, I don't see anything that resembles watching for disconnects.
Can be tested via:
> busctl --user call org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver org.freedesktop.ScreenSaver Inhibit ss 'test' 'foobar'
u 1412

and you'll see the lock count just increase in the logs:
[LOG] ScreenSaver inhibit: true dbus message from test with content foobar
[LOG] Inhibit locks: 10
[LOG] Cookie 1411 sent
[LOG] ScreenSaver inhibit: true dbus message from test with content foobar
[LOG] Inhibit locks: 11
[LOG] Cookie 1412 sent

I am also having this issue, I don't know what is filling up the inhibitors but after a while they are always above 1. I hope someone can look into fixing this, would really like this to work for the sake of my oled monitor.

I don't think this is a problem with hypridle but with applications not properly releasing inhibit requests. Steam is one such application, it requests an inhibit lock on startup and doesn't release it on shutdown (I have checked this with dbus-monitor).

it sends an inhibit dbus message on startup and doesn't release it on shutdown

The quoted part of the specification says this is not necessary, the inhibition should be implicated released on shutdown.

Sorry, I should have read the issue description. I'll make a PR to implement this.


Add way to access name for tiles by identifier

Possibly {tile:?}
Also consider item use.

are you talking about tile code (TileSideAlley1) or the name you give to a tile when you create it?
The problem with the Tile Code is that the tiles list has been translated so you can't see its code.
Almost all tiles appearing in a text are related with the addTile event so these texts could be automated #321
The tile dict creation can be done quickly but the prefered mode should be that the asset importer could read the localization file and automate the creation of the tiles dictionary. I supose there will be a new expansion for the game including new tiles and the atomatic creation of the dictionary could be regenerated dinamicly.
Same for items.

Automating it would be great. This would allow options to completely disable the dialogs of place ? events or show the event text in a different way, like shorter texts, only graphics (3x ).
Something like {tile:?} would be needed regardless of those options, if you want to refer to it. For example, in an event like: "Herber West takes out his syringe and pushes the remainig serum into a corpse. Place a {monster:ZOMBIE} in the {tile:KITCHEN}. All investigators in the {tile:KITCHEN} become {effect:dazed} by the musky smell of the liquid. If one investigator inside the {tile:KITCHEN} has the item {item:brass_key}, it drops to the floor."

I am leaning towards {component:TileScenarioEntry} for the name of the tile used there {component:QItemInBox} for the name of the item picked by QItemInBox and so on.  Could also just overload qst with {qst:TileScenarioEntry}

qst elements are translated in the text editor.
If you have {qst:quest.name}. when you edit the scenario, the text field will have "Exotic Material" not {qst:quest.name}
but we are talking about a tag that isn't translated in the editor but in the gameplay (Like {rnd:hero})
For this, its better to have another tag for referencing components. Can be: q, this, component, com or something like this.
I will start coding asuming the q tag, but if we decide anoter one it can be changed fast.

Sound good. Elements like {strength} are nice to read, but could be replaced with {q:strength} to simplify parsing and validation. Just do the rest using naming conventions, like {q:tile.mom1.kitchen}.

I would prefer for consistency that this only works with quest components, so it won't affect symbols and you can't reference a tile name directly, only a Tile component, which it will use the name from.

This is the last feature for 1.1 before the freeze. If you are in this that is fine, but if your haven't started is it ok if I do it?

It's almost done. It can only reference quest components and are resolved:

Event: Replaced with the text of the event
Tile: Replaced with the name of the Tile
Token: Replaced with the text of the token
CustomMonster: Replaced with the custom monster name
Spawn: Replaced with the text shown in the spawn
QItem: I want to show the QItem name but it has many i'm not sure. I will print a name of the first element in the list.

For QItem use game.quest.itemSelect[]

ok

As they are components and to not make confusion with the {qst: variables, I think the best name for these variables are {c:NameOfComponent}. instead of {q:NameOfComponent}

OK, I would like to suggest some changes though:
Spawn: Replaced with the text shown in the spawn
Probably more useful to put the monster name in (this works the same as QItem).  This is redundant with {qst:Spawn.text}.
Token: Replaced with the text of the token
As above, probably not useful.
Event: Replaced with the text of the event
As above and I want to use this for a hero name from a previous rnd:hero (#186)

The spawn is a good idea to place the monster. The spawing text can be even automated this way;
SpawnHumanoid1:
"Place the monster {c:SpawnHumanoid1} in the space shown."
by refering itself if you want a spawn by trait.
But for the rest, I think the qst variables shouldn't be used inside the editor. They are directly replaced so the only way to use it is outside valkyrie. I think that using these news should be the best way to do inside valkirie and not needing to edit inside and outside valkirie at time,.

I am saying I would like this new text reference in 1.2, and please write up how you would like it to work in an issue.

I have changed the way that c:Event works and removed c:Token.  I would like a bigger picture look at text references before adding the direct text reference in.

I don't agree with the removal of the Token item text. It's really useful to avoid duplicated texts for every tokens. All token related texts are duplicated in localization files. The good structure would be a token with an specific texts and the event showing the token should reference the token text in a more stable mode than writing in the event text {qst:x} reference. Something that if you click inside the text element accidentally will translate the texts. Think about translators who will edit your scenario and translate every text inside de app . all qst references will be lost.
Agree with the new "event" text use to get the random hero selection of an event but not for the token. it was removed not replaced.
Now I don't know how to insert automatic text to token spawns without using the "volatile" {qst: system.

What I am trying to say is don't use c: for this purpose, use something else, either qst with modifications or something new, because this behaviour should work for all components equally not just Tokens.  The solution should also apply to other texts such as buttons, so I would prefer either some sort of toggle to change the qst behaviour in the editor or an alternative to qst which is the same except that it isn't replaced in the editor.  I don't want to push out a feature in 1.1 without a plan for how this would work because removing a feature is harder than adding.
Does that make sense?


use UserVolume to describe container image

To work with corresponding runv change https://github.com/hyperhq/runv/pull/269

travis failed because this needs hyperhq/runv#269

LGTN


Core systems

[x] Displaying Images
[x] Handling button clicks
[x] Handling activation of different systems with button clicks
[x] Audio integration
[x] Config file structure

Done


Race condition when importing Menagerie descriptions concurrently from multiple processes

Bug description
When import import MuJoCo Menagerie descriptions concurrently from more than one process, the git clone fails. I was expecting (or at least hoping) for this to work.
Reproduction steps
Steps to reproduce the bug:

Install GNU parallel and robot_descriptions
Run:

rm -rf ~/.cache/robot_descriptions/ && \
parallel --verbose -j 4 "
    python -c 'from robot_descriptions import fr3_mj_description; print({1}, fr3_mj_description.MJCF_PATH)'
" ::: {1..4}

See error

Code
See above
Logs

Full error:
$ rm -rf ~/.cache/robot_descriptions/ && \
$ parallel --verbose -j 4 "
    python -c 'from robot_descriptions import fr3_mj_description; print({1}, fr3_mj_description.MJCF_PATH)'
" ::: {1..4}

    python -c 'from robot_descriptions import fr3_mj_description; print(1, fr3_mj_description.MJCF_PATH)'

    python -c 'from robot_descriptions import fr3_mj_description; print(2, fr3_mj_description.MJCF_PATH)'

    python -c 'from robot_descriptions import fr3_mj_description; print(3, fr3_mj_description.MJCF_PATH)'

    python -c 'from robot_descriptions import fr3_mj_description; print(4, fr3_mj_description.MJCF_PATH)'

Cloning https://github.com/deepmind/mujoco_menagerie.git...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/fr3_mj_description.py", line 14, in <module>
    REPOSITORY_PATH: str = _clone_to_cache(
                           ^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 138, in clone_to_cache
    clone = clone_to_directory(
            ^^^^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 80, in clone_to_directory
    os.makedirs(target_dir)
  File "<frozen os>", line 225, in makedirs
FileExistsError: [Errno 17] File exists: '/Users/user/.cache/robot_descriptions/mujoco_menagerie'
Cloning https://github.com/deepmind/mujoco_menagerie.git...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/fr3_mj_description.py", line 14, in <module>
    REPOSITORY_PATH: str = _clone_to_cache(
                           ^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 138, in clone_to_cache
    clone = clone_to_directory(
            ^^^^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 80, in clone_to_directory
    os.makedirs(target_dir)
  File "<frozen os>", line 225, in makedirs
FileExistsError: [Errno 17] File exists: '/Users/user/.cache/robot_descriptions/mujoco_menagerie'
Cloning https://github.com/deepmind/mujoco_menagerie.git...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/fr3_mj_description.py", line 14, in <module>
    REPOSITORY_PATH: str = _clone_to_cache(
                           ^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 138, in clone_to_cache
    clone = clone_to_directory(
            ^^^^^^^^^^^^^^^^^^^
  File "/Users/user/github/Code/code-worktree-3/.venv/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 80, in clone_to_directory
    os.makedirs(target_dir)
  File "<frozen os>", line 225, in makedirs
FileExistsError: [Errno 17] File exists: '/Users/user/.cache/robot_descriptions/mujoco_menagerie'
Cloning https://github.com/deepmind/mujoco_menagerie.git...
4 /Users/user/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml
100%|██████████| 1058.0/1058.0 [00:24<00:00, 43.20it/s]

System

OS: macOS Sequoia 15.0.1
robot_descriptions version: 1.13.0

Additional context
I spent a bit of time trying to get some sort of locking mechanism to work for clone_to_cache. I never got to finishing it but below's what I had so far. Just putting it out here in case someone finds useful and wants to pick it up.

`clone_to_cache_with_lock`
def clone_to_cache_with_lock(description_name: str, commit: Optional[str] = None) -> str:

    lock_file_path = pathlib.Path(
        os.environ.get(
            "ROBOT_DESCRIPTIONS_CACHE",
            "~/.cache/robot_descriptions/CLONE_LOCK",
        )
    ).expanduser()
    lock_file_path.parent.mkdir(parents=True, exist_ok=True)

    print(f"{lock_file_path=}")

    timeout = 300
    poll_every = 5
    start_time = time.time()
    while True:
        try:
            # Attempt to create the lock file atomically
            lock_fd = os.open(str(lock_file_path), os.O_CREAT | os.O_EXCL | os.O_RDWR)

            try:
                print(f"Process {os.getpid()} is cloning the repository...")
                clone_to_cache(description_name, commit)
                print(f"Process {os.getpid()} completed cloning.")
            except subprocess.CalledProcessError as e:
                print(f"Process {os.getpid()} failed to clone the repository.")
                raise e
            finally:
                os.close(lock_fd)
                lock_file_path.unlink()
            break
        except FileExistsError as e:
            # Lock file exists, wait for cloning to complete
            print(f"Process {os.getpid()} detected cloning in progress. Waiting...")
            time.sleep(poll_every)
            elapsed_time = time.time() - start_time
            if elapsed_time > timeout:
                print(f"Process {os.getpid()} timeout exceeded. Removing stale lock file.")
                try:
                    lock_file_path.unlink()
                except FileNotFoundError:
                    pass
                continue
        except Exception as e:
            print(f"Process {os.getpid()} encountered an error: {e}")
            raise e

Thank you for this detailed report and proposing a first idea :+1: From the logs I'm guessing processes are trying to clone concurrently as Menagerie is not in cache yet when they start.
Actually, even if it the description is already in cache, we will run into a similar error. I've adapted your parallel command to run on my machine but it does the same thing:
parallel -i python -c 'from robot_descriptions import fr3_mj_description; print({}, fr3_mj_description.MJCF_PATH)' -- 1 2 3 4

Error: Another git process seems to be running in this repository, ...
3 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml
Traceback (most recent call last):
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 90, in clone_to_directory
    clone.git.checkout(commit)
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 800, in <lambda>
    return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 1386, in _call_process
    return self.execute(call, **exec_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 1183, in execute
    raise GitCommandError(redacted_command, status, stderr_value, stdout_value)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git checkout 3d593a327ff8d5efd10f4926ccc477820e9252c1
  stderr: 'fatal: Unable to create '~/.cache/robot_descriptions/mujoco_menagerie/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/robot_descriptions/fr3_mj_description.py", line 14, in <module>
    REPOSITORY_PATH: str = _clone_to_cache(
                           ^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 139, in clone_to_cache
    clone = clone_to_directory(
            ^^^^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/robot_descriptions/_cache.py", line 98, in clone_to_directory
    clone.git.checkout(commit)
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 800, in <lambda>
    return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 1386, in _call_process
    return self.execute(call, **exec_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "~/.micromamba/envs/robot_descriptions/lib/python3.12/site-packages/git/cmd.py", line 1183, in execute
    raise GitCommandError(redacted_command, status, stderr_value, stdout_value)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git checkout 3d593a327ff8d5efd10f4926ccc477820e9252c1
  stderr: 'fatal: Unable to create '~/.cache/robot_descriptions/mujoco_menagerie/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.'
Commit 3d593a327ff8d5efd10f4926ccc477820e9252c1 not found, let's fetch origin and try again...
Commit 3d593a327ff8d5efd10f4926ccc477820e9252c1 not found, let's fetch origin and try again...

Found commit 3d593a327ff8d5efd10f4926ccc477820e9252c1 successfully!
1 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml

At first read I had a hunch this error is related to the quick-and-dirty way we pass arguments via environment variables, which won't work well when we run in parallel. But in this instance the exception is rather raised from:
https://github.com/robot-descriptions/robot_descriptions.py/blob/380aa5a4d8c81c48ab152f74e9cff523f4d5562a/robot_descriptions/_cache.py#L89-L95
And the (currently uncaught) exception message reads:
Unable to create '~/.cache/robot_descriptions/mujoco_menagerie/.git/index.lock': File exists.

We can probably make a quick workaround for this one.

OK, after https://github.com/robot-descriptions/robot_descriptions.py/pull/116 we can at least do:
$ parallel -i -j 4 python -c 'from robot_descriptions import fr3_mj_description; print({}, fr3_mj_description.MJCF_PATH)' -- 1 2 3 4
3 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml
4 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml
2 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml
1 ~/.cache/robot_descriptions/mujoco_menagerie/franka_fr3/fr3.xml

Thus, if all the descriptions we import are from the same commit of the same repository, one thing that works now is:

Import the description once from a single process, waiting for it to be cloned to cache, then
Run in as many parallel imports as needed.

The case where we clear the cache right before running in parallel is not handled yet, as the rest of the initialization/recovery logic in clone_to_directory still assumes exclusive access to the cache.


Implementation for Portable Uninstall and Upgrade

Related to:

#182
#1315

This PR adds the implementation for supporting the uninstall and upgrade scenario for the portable installerType:
Changes:

Rearranges the write to registry order so that if the upgrade scenario fails, the existing registry values are preserved.
Adds the uninstall flow so that the uninstall flow removes the appropriate installed files related to the portable.
Adds cleanup functionality to the install flow if install fails.
Adds support for --purge and --preserve

Tests:

Added unit tests to workflow for update and uninstall
Added E2E tests for upgrade with the uninstallPrevious upgrade behavior
Added E2E tests for uninstall as well as incorporating uninstall in the cleanup process for install tests

Microsoft Reviewers: Open in CodeFlow

/azp run


Event: ATX Holiday meetup

event added: ATX Holiday Meetup

✅ By submitting this PR, I have verified the following

[x] Checked to see if a similar PR has already been opened 🤔
[x] Reviewed the contributing guidelines 🔍
[x] Added my name to the bottom of the list under the Contributors section in the README.md with a link to my personal website or GitHub profile 👥 (Optional)

this one looks almost identical to #595 - maybe we can just combine all these changes into 1 PR? will make it easier to review :)


Support Python 3

What does this PR do?
Support Python 3 on Riak CS. This one just required a simple iteritems change.
Motivation
The Python 3 🚂is leaving the station!
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[x] Git history is clean
[x] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[x] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2780 into master will increase coverage by 3.68%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2780      +/-   ##
==========================================
+ Coverage   84.75%   88.43%   +3.68%
==========================================
  Files         657        6     -651
  Lines       37463      147   -37316
  Branches     4502       17    -4485
==========================================
- Hits        31750      130   -31620
+ Misses       4397       12    -4385
+ Partials     1316        5    -1311


MB-4564 Step Component Number Alignment + Home Page Header Full Bleed Background

Description
This PR implements small css changes on the home page components to acheive the following:

align the number in the step component to the center of the circle
makes the number inside the step component circle bold
moves the  on the Home page out of the .usa-prose container it was in, and wraps it's internal contents with a div with the same classes to ensure that the contents of the header stay aligned to the content of the page while the background of the header extends to be full width.

Reviewer Notes
I had to change some of the paths in imports in the app to get it to run locally. Let me know if those changes are a problem.
Setup
make server_run
make client_run

pick a user in local sign in that will route you to the Home page.
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-4564

  Generated by :no_entry_sign: dangerJS against 2dad711d63ee7820309f842dd503894e86b9fe5e


Fixup dot dot require

This fixes up tracing for require('..') without a trailing slash, which was resulting in some inaccurate analysis.

Codecov Report

Merging #92 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master     #92   +/-   ##
======================================
  Coverage    90.8%   90.8%
======================================
  Files          12      12
  Lines        1044    1044
======================================
  Hits          948     948
  Misses         96      96

Impacted Files
Coverage Δ

src/resolve-dependency.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[UT] move time-consuming cases to benchmark test

Why I'm doing:
Reduce fe ci time cost.
What I'm doing:
move time-consuming cases to benchmark test
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[x] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@Mergify backport branch-3.2 branch-3.1


Definition of Events/Commands/Messages is contrary to commonly accepted definition

https://github.com/confluentinc/event-streaming-patterns/blob/15ca13177fb5bb0078561756b7a2d4f4f9a00f71/site/event/command-event.html#L240
This section of the document states:

Events often fall into one of two categories: messages and commands.

The more commonly accepted definition would be that:

Messages fall into one of two categories: commands and events

For example:
https://event-driven.io/en/whats_the_difference_between_event_and_command/
This page states that when comparing commands and events, we can say that: "Both are messages".
The important distinction is that commands and events are related, but different things. One is not a subclass of the other.
Commands are used to initiate an action in a system (i.e. Please do this).
Events are used to record the action in the system (i.e. I did this).
Should this page be updated to reflect the more commonly accepted categorization of these items?

addressed by PRs 262 and 263

Thank you for these updates.


focal-point.js unit-tests

focal-point.js unit-tests
gulp file updated
package.json updated
jquery simulate added

lgtm

:+1:


IceCubes Logo

ICUBE Contract: 0x951c8a8dee33bd5039a71e7bd4244d5659cf1517

can u use 200X200 PNG log and send PR?

Hi, Here you go!  https://ibb.co/Wvx2jC0 Thanks. From: robotmurlocSent: Tuesday, 2 November 2021 8:51 amTo: traderjoe-xyz/joe-tokenlistsCc: icecubesfinance; AuthorSubject: Re: [traderjoe-xyz/joe-tokenlists] IceCubes Logo (Issue #72) can u use 200X200 PNG log and send PR?—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.


Added 'CommitChart' component; Adjusted 'Badge' and 'Profile' components

Description

Created CommitChart component that displays the user's commit history of last 30 days.

Utilizes react-chartjs-2 and chart.js node packages

Adjusted the size of Badge icons in the Badge component to deal with responsiveness issues.
Replaced the implementation of Box with Grid in Profile component to deal with responsiveness issues.

NOTE: There are still some slightly visible oddities in the sizing of CommitChart and Badge components when displayed in lower browser resolutions. This can be treated as an issue and fixed by someone who's more familiar with making responsive components with Material UI.

Related Issue

Fixes #34
Type of Change:

Code
User Interface
New Feature

How Has This Been Tested?

Tested on my local node environment.
Checklist:

[x] Pull request is made against development branch.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings

[x] My UI is responsive
[x] UI made replicates the design provided

Screenshots (if appropriate):

Normal res

Low res

Looks Awesome


Feature request: Use current date for unreleased section

Is it possible to add an option to use current date for unreleased section?
Motivation:
I am generating changelog as a part of package publishing process, which has the following steps:

Change version number in package.json
Generate change log
Create and push commit
NPM package is published by GitHub actions.

My .auto-changelog configuration:
{
  "package": true
}

This is what I get:

Thanks to "package" option:
I get unreleased commits included - great
I see upcoming version number (1.5.0) as a title - also great
But date is missing - bad.
With new option, auto-changelog could add current date in such situation.
Current date make sense here because the next release is going to be created right now.

Thx for response.
I described it in detail in my first message.

Otherwise, if I generate change log before version commit I don't get date.
But this is not practical to create two commits for each release.

You don’t have to do it in two commits - i use auto-changelog on hundreds of projects and it does it in one commit. Here’s an example: https://github.com/inspect-js/object-inspect/blob/main/package.json#L36-L37


cat and dog commands

Pull request

[ ] I have read and agreed to the CODE OF CONDUCT.
[ ] What I'm implementing was assigned to me or was not being worked on and is a somewhat requested feature. For reference see our trello.
[ ] I have tested all of my changes.
[ ] I have followed the style of the rest of the project.

Added/Changed
What did you add and/or change for this.
Feature
If this is a new feature, why should we add it to the bot.

TODO: Add utils method for requests :P


fixes #27

Codecov Report

Merging #41 into master will increase coverage by 0.15%.
The diff coverage is 32.58%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   26.43%   26.59%   +0.15%
==========================================
  Files           6        8       +2
  Lines         401      455      +54
==========================================
+ Hits          106      121      +15
- Misses        295      334      +39

Impacted Files
Coverage Δ

jupyterlab_celltests/lint.py
14.52% <100%> (-5.48%)
:arrow_down:

jupyterlab_celltests/tests_vendored.py
100% <100%> (ø)

jupyterlab_celltests/define.py
48.93% <48.93%> (ø)

jupyterlab_celltests/tests.py
15.2% <7.69%> (-2.28%)
:arrow_down:

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 ab4a820...cd162a4. Read the comment docs.


In IE 7-9, HTML5 required attribute has problems

See this minimal test case for an example of the following problems:

IE 10: works fine.
IE 9: the required attribute doesn't trigger validation of a field.
IE 7 & 8: the required attribute appears to prevent validation of a field.

I first noticed these issues while using the validation plugin with jQuery 1.6.4, but they still seem to happen with 1.7.1 as well.
I've found that I can work around this issue by adding the following code before invoking the plugin:
if ($.browser.msie && $.browser.version < 10) {
	$('#form_to_validate [required]').addClass('required').removeAttr('required');
}

An update: testing with the Windows Phone emulator indicates that the same problem exists there, and the same work-around applies.

Hi all
is any plugin or file available for resolving this types of issues which are not support in IE9 related to html5 ? pla revert back


switch to 1.2 and new k256 patch

Just opening for visibility. Likely only worth pulling in when a patch commit is tagged and on 1.2 stable
pointing at #115

Release/docker builds will be fixed by https://github.com/risc0/risc0/pull/2635, otherwise these changes should be good to go


Is this crate dormant or developing elsewhere?

I'll try to use it in another crate... ;)

Haha, yeah I have been dealing with other projects 😅, I no longer had that much motivation for a crate that I didn't think much people were using.
Should you have a well-defined use-case objective you'd like to see added here, it may give me an objective towards which to work 🙂

Well, I'm in a compiler for Clojure, and I'm dealing a lot with trait objects as the runtime is fully based on dynamic dispatch. I fall on your code and part of it seemed useful to be integrated to ease the code generation of the core library and eventually in the compiler code generation.
But I'm not in a hurry for now... ;)

I wanted to write a crate with a similar functionality, but decided to search for one first. Found this one at it probably fits my use case, which is representing Factorio prototypes as rust structs: https://github.com/JohnTheCoolingFan/factorio-lib-rs


04/19/2018 02:50 : Create Pull Request for branch prTesting_2018041902 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


nmap: 7.93 -> 7.94

Description of changes
Package bump and remove last traces of zenmap support which hasn't been enabled for a while.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

this breaks cross compilation:
$ git show ddf2d4e8ea0109225caaea58c5e666a38c492279
nmap: 7.93 -> 7.94
$ git checkout ddf2d4e8ea0109225caaea58c5e666a38c492279~1
$ nix build '.#pkgsCross.aarch64-multiplatform.nmap'
<success>
$ git checkout ddf2d4e8ea0109225caaea58c5e666a38c492279
$ nix build '.#pkgsCross.aarch64-multiplatform.nmap'
...
make[1]: Leaving directory '/build/nmap-7.94/libnetutil'
aarch64-unknown-linux-gnu-g++ -c -I./liblinear -I./liblua -I/nix/store/b6dc0lljn4lkylyrv3mj8z4bfslafxj1-lua-aarch64-unknown-linux-gnu-5.3.6/include -I./libdnet-stripped/include -I./libz  -I./nbase -I./nsock/include -DHAVE_CONFIG_H -DNMAP_PLATFORM=\"aarch64-unknown-linux-gnu\" -DNMAPDATADIR=\"/nix/store/885x4inw6hqnxwmyzanp5cyh9gs9cdiq-nmap-aarch64-unknown-linux-gnu-7.94/share/nmap\" -D_FORTIFY_SOURCE=2 -g -O2 -Wall -fno-strict-aliasing   TargetGroup.cc -o TargetGroup.o
aarch64-unknown-linux-gnu-gcc -O2 -Wall -Wextra -DLUA_COMPAT_5_3  -g -O2 -Wall   -DLUA_USE_POSIX -DLUA_USE_DLOPEN   -c -o linit.o linit.c
aarch64-unknown-linux-gnu-ar liblua.a lapi.o lcode.o lctype.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o lcorolib.o ldblib.o liolib.o lmathlib.o loadlib.o loslib.o lstrlib.o ltablib.o lutf8lib.o linit.o
aarch64-unknown-linux-gnu-ar: libdeps specified more than once
make[1]: *** [Makefile:60: liblua.a] Error 1
make[1]: Leaving directory '/build/nmap-7.94/liblua'
make: *** [Makefile:166: build-lua] Error 2
make: *** Waiting for unfinished jobs....

@fpletz please see https://github.com/NixOS/nixpkgs/pull/240440 for the cross compilation fix. also consider linking or inlining upstream changelogs into future PRs: it makes it easier for reviewers to spot this sort of thing (dependency changes/mismatches) in advance.


Goenrichment

I've added a Workflow. Basically I downloaded one from usegalaxy.org after running the tutorial.
I hope this one is good enough like that, as I'm not sure of other ways to easily generate it.
One file in Zenodo slipped through the cracks so I had to change it again.

I think Travis failed due to some timeout with conda...

@dsobral Is it possible to change the data library to the latest format? #1255 will convert all data-libraries to that format.
for more information: https://galaxyproject.github.io/training-material/topics/contributing/tutorials/create-new-tutorial-technical/tutorial.html

@dsobral Is it possible to change the data library to the latest format? #1255 will convert all data-libraries to that format.
for more information: https://galaxyproject.github.io/training-material/topics/contributing/tutorials/create-new-tutorial-technical/tutorial.html

planemo training_fill_data_library seems to be failing for some reason:
 File "/home/dsobral/miniconda3/lib/python3.7/site-packages/planemo/training/utils.py", line 19, in init_from_dict     self.title = dict['title'] KeyError: 'title'
Although title is defined in tutorial.md
I've tried with other tutorials and I get the same error...

I came across several of these problems when I used planemo training_fill_data_library on all tutorials. I've made some changes to the planemo module in how he reads the meta data from the tutorial.md file to get it working. I was planning to talk about it with @bebatut /or open an issue.
I did quickly did it for you:
---
destination:
  type: library
  name: GTN - Material
  description: Galaxy Training Network Material
  synopsis: Galaxy Training Network Material. See https://training.galaxyproject.org
items:
- name: Transcriptomics
  description: Training material for all kinds of transcriptomics analysis.
  items:
  - name: GO Enrichment Analysis
    items:
    - name: 'DOI: 10.5281/zenodo.2565417'
      description: latest
      items:
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/drosophila_gene_association.fb
        src: url
        ext: tabular
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/go.obo
        src: url
        ext: obo
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/goslim_generic.obo
        src: url
        ext: obo
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/mouse_brain_vs_heart.difgenes.txt
        src: url
        ext: txt
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/mouse_brain_vs_heart.txt
        src: url
        ext: txt
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/mouseOverexpressed.txt
        src: url
        ext: txt
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/mouseUnderexpressed.txt
        src: url
        ext: txt
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/Mus_musculus_annotations_biomart_e92.tab
        src: url
        ext: tabular
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/trapnellPopulation.tab
        src: url
        ext: tabular
        info: https://zenodo.org/record/2565417
      - url: https://zenodo.org/api/files/a4583abd-0a85-457e-a5c0-1fc323535db7/trapnellStudy.txt
        src: url
        ext: txt
        info: https://zenodo.org/record/2565417

OK, Thanks. I updated it then.

@dsobral, @bedroesb I know the error. I am working on fixing this issue

@dsobral looks good can you fix the merge conflict?


auxiliary input

Hi, I'm wondering if you could help me. I'm trying to build a WaveNet-style vocoder in TensorFlow which uses acoustic features as auxiliary input, but I'm struggling to understand how auxiliary input is feed to the network, is it added in parallel (two parallel layers) to the sample values and the output combined at a later layer? If you can point me in the direction of a text-book/article on auxiliary input/conditioning network I would be eternally grateful, I've looked many times and I can't find anything that gives a general undestanding of this.

Hi,
Appendix A in this paper  should be helpful.
You'll probably get more responses if you post your questions on StackOverflow in the future.

^ sorry forgot to add https://arxiv.org/pdf/1702.07825.pdf


Update convert-unmanaged-to-managed-disks.md

Corrected
Start-AzureRmVM -ResourceGroupName $rgName -Name $vmName   #Note the missing '.'
to
Start-AzureRmVM -ResourceGroupName $rgName -Name $vm.Name

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@GoonerW : Thanks for your contribution to the Azure documentation! The author, @cynthn, has been notified to review your proposed change.

#sign-off @GoonerW thank you for catching that! :)


Upgrade

Thank you for contributing to meli.
Every contribution to meli is important to us.
Contributor offers to license certain software (a “Contribution” or multiple
“Contributions”) to meli, and meli agrees to accept said Contributions,
under the terms of the MIT License.
Contributor understands and agrees that meli shall have the irrevocable and perpetual right to make
and distribute copies of any Contribution, as well as to create and distribute collective works and
derivative works of any Contribution, under the MIT License.
Now,
What(What have you changed/added/removed?)

upgrade docker

Why(Why did you change/add/remove it?)

docker no longer uses semantic versioning; it uses a time-based[1] versioning scheme
The latest release on github is now v17.03.2-ce [2]
Although that release(from june 2017) is still very old compared to the version running on my machine;
 docker version

Client:
 Version:           18.06.0-ce
 Built:             Wed Jul 18 19:09:54 2018

Server:
 Engine:
  Version:          18.06.0-ce
  Built:            Wed Jul 18 19:07:56 2018

so we need to investigate how to download the new clients, since they do not appear to be released on github
The issue for that is; https://github.com/komuw/meli/issues/108

https://medium.com/@nagarwal/dockers-new-versioning-scheme-introduced-9bf594a278cf
https://github.com/moby/moby/releases/tag/v17.03.2-ce

Codecov Report

Merging #109 into mod will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              mod     #109   +/-   ##
=======================================
  Coverage   54.23%   54.23%
=======================================
  Files           8        8
  Lines         555      555
=======================================
  Hits          301      301
  Misses        200      200
  Partials       54       54

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 ffdca6c...0dd4fde. Read the comment docs.


Make plugin actually use scss formatter

The actual formatting is absolutely off however!
But maybe someone with better knowledge of Python will chip in

#265 mention some things not working - probably worth closing because actual formatter currently used in plugin is cssbeautifier not scssbeautifier

@rolandas-valantinas did you tested and everything works?

@akalongman well I've only did fix so codeformatter picks correct formatter  (https://github.com/akalongman/sublimetext-codeformatter/blob/master/codeformatter/lib/scssbeautifier/init.py) and new line is added after new rule.
That part is tested and works fine. However scssbeautifier/__init__.py formatter itself is far from properly formatting scss files. I have very little knowledge in python, sublime plugins and how to write formatting scripts.
Someone has to use https://github.com/beautify-web/js-beautify/blob/master/python/cssbeautifier/init.py and transform it into scss formarter


Demon Slayer

For demon slayer the plugin only lists 25 bones as an item requirement. The quest also requires 1gp(you have to give gypsy aris 1gp when you start the quest) and a bucket of water(it does show you where to pick up a bucket, though. So not really a big deal). Edit: Also found the quest doesn't list food+armor and varrock/draynor teleports. And in the enemies to defeat section Delrith isn't listed.
Just wanted to add I'm really liking the plugin quite a bit, and I hope you continue working on it. It's great! I'll continue to report any issues I come across. Thanks!!

Thanks, I've added all of that with https://github.com/Zoinkwiz/quest-helper/commit/017c56a8633610e0c5a953ee6583df6903f08162. Glad you've been enjoying it, appreciate any reports on issues you find!


need to update minified file

The minified file is out of date.  Angularjs2 team is using the outdated version in their shims_for_IE.js file.  I stumbled across the svg issue in IE11.  I'll be sending them pull request for this as well.
I minified the file using uglifyjs as follows:
uglifyjs classList.js > classList.min.js -m
Not sure what you were using to minify the file originally. :)

Oh thanks for catching that. I forgot to update it.

There may be a problem with the new file. We have been using classList.min.js (via rawgit) and now IE11 acts as though it has no shim.

thanks, I'll retest and comment back here.

Can you try this plunkr? https://plnkr.co/edit/jALLcYE3zvxYeYZ0O5Dh
I am only testing for the existence of the classList function, as I simply minified the lastest unminified code.
I get the same results in both minified and unminified version of the file. If we don't include either polyfill, the classList function does not exist on svg elements on IE11, as expected.
If the latest unminified file has other functional changes you're seeing from the older minified file then perhaps that's a separate issue :)

It's the older-minified-file situation. I found it in the Issues here: https://github.com/eligrey/classList.js/issues/44
I'm pulling https://cdn.rawgit.com/eligrey/classList.js/e87db36a95b2381a8c3ed44582a3926185cede70/classList.min.js now.

ah, that's interesting. so failing the check doesn't simply skip the polyfill, it runs different code that patches just a couple of the classlist functions (which you need).  That's not that clear if you're just looking at that initial test :)
So the work to include the polyfill for svg elements should probably be separated out, so it could be applied to svg elements only (if needed), leaving the dom element prototype intact.
and then, that second branch that patches those specific functions should be run in every case, and updated to handle svg elements as well.

@RoyEJohnson, I have a change that might resolve your issue while still applying the polyfill for SVG elements.  I understand you might not care about SVG support, but would you mind trying this:
https://rawgit.com/allannienhuis/classList.js/master/classList.min.js
or https://rawgit.com/allannienhuis/classList.js/master/classList.js
This change applies the full polyfill if needed, so that svg elements get the polyfill, but also applies the partial patch to support IE that is being skipped in the latest version here (the cause of the problem you saw).  If it passes your test, I'll submit PR for Eli.
I'm not really certain this will work, as the partial polyfills should not pass their tests to be applied after receiving the full polyfill, but I'm not sure exactly what failed for you to know for sure. :)
Cheers,


More meaningful chain snapshots name

add environment name to the filename
use node public IP address instead of hostname

https://www.pivotaltracker.com/story/show/156612994

WIP until test/example build


Stock price just stopped updating

Have had this working for some time.  Rebooted.  Uninstalled, re-installed.  Not working.

I believe the Yahoo Finance API must have changed, as the BarRaider YahooFinance stock ticker is also not working.

Fixed in v1.1.3


cherry-pick commits from main into release/v0.3

Here are the commands I ran
git checkout -t remotes/upstream/release/v0.3
git cherry-pick -x -s 7639637d1573bb0c0fc215794653f818d5d6668b^..d7a2e195528e0419d846f80caa14c5db9b79f60c
git push origin release/v0.3

Here is the range of commits https://github.com/envoyproxy/gateway/compare/7639637d1573bb0c0fc215794653f818d5d6668b^...d7a2e195528e0419d846f80caa14c5db9b79f60c

Codecov Report

Merging #1024 (2c3a51b) into release/v0.3 (ffa4bad) will decrease coverage by 0.14%.
The diff coverage is 46.05%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@               Coverage Diff                @@
##           release/v0.3    #1024      +/-   ##
================================================
- Coverage         62.09%   61.95%   -0.14%
================================================
  Files                55       55
  Lines              8779     8801      +22
================================================
+ Hits               5451     5453       +2
- Misses             2958     2973      +15
- Partials            370      375       +5

Impacted Files
Coverage Δ

internal/gatewayapi/filters.go
79.57% <0.00%> (-0.79%)
:arrow_down:

internal/gatewayapi/runner/runner.go
28.26% <0.00%> (-0.32%)
:arrow_down:

internal/gatewayapi/translator.go
97.10% <ø> (ø)

internal/infrastructure/kubernetes/deployment.go
54.97% <0.00%> (ø)

internal/infrastructure/kubernetes/infra.go
27.63% <0.00%> (ø)

internal/infrastructure/kubernetes/service.go
40.81% <0.00%> (-0.57%)
:arrow_down:

internal/xds/translator/route.go
81.08% <37.50%> (-1.53%)
:arrow_down:

internal/xds/translator/runner/runner.go
75.67% <44.44%> (-10.54%)
:arrow_down:

internal/xds/translator/translator.go
76.12% <60.00%> (ø)

internal/xds/translator/ratelimit.go
93.33% <66.66%> (-2.78%)
:arrow_down:

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.