text:
Improve the Journalism Example

This should be made better over time. Current wishlist items include:

Rip out the 'editor' form as a single angular directive to be more DRY
Make the photo_adjustment step more realistic:

More realistic operations, e.g. rescaling/recoloring/thumbnails
More realistic workflow, e.g. creating multiple copies of each image and having the copy-editor
caption the thumbnails
Write tests for the new google apps convenience/service methods (convenience.upload_file, convenience.download_file, service.list_folder, service.get_file_content)

Also---create journalism-requirements.txt or some other way to capture requirements not core to Orchestra.
From our discussion: I think we discussed having a setup_orchestra.sh script in the pypi package--when we write that I'd say it's reasonable to give it commandline arguments like --journalism-workflow to indicate that those requirements are needed.

orchestra/static/orchestra/task/js/controllers.js copies variables from data onto vm but also points vm.taskAssignment at data.  We should stick to accessing variables via vm.taskAssignment and clean up throughout.

authors: marcua thisisdhaas

repo: unlimitedlabs/orchestra


text:
Addition of welcome bot

Would like to add a welcome and greeting bot that welcomes anyone who comes and opens an issue or makes a pr on this project
Would like to work on this issue

@unnati914 would like to make this can you please assign it to me

welcome bot config file will be  having a proper message that will show up when any user will open up an issue or pull-request for the first time.
For reference, check out and download the bot from here and I will be adding another file
https://github.com/apps/welcome

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
The 'api' role has too many dependencies

In the spirit of keeping things light weight, I find it quite troublesome that so many external deps are required to run the api role.
It would be best if it could install a binary (yum/deb) package containing the pre-compiled binaries for the API (picoLisp, compiled json parser, etc).

The api is not a dependency for future versions of the Jidoteki Admin. It can now be installed separately (i.e: as a binary package), and the api role will soon be removed.

repo: unscramble/jidoteki-admin

license: mit

license_source: bigquery


text:
Protect server.js and assets.json

These files should not be accessible publicly.
Closes #86

@robin-drexler understood - I just updated this PR to make sure things work as you proposed. For reference, see the Express docs.

source: gharchive/pull-request

repo: untool/untool


text:
Find a way to make the configuration file containing keys private

Rishavjeet and SHivam needs to find a way to make the configuration file containing keys private

There's no particular solution for this, we can directly insert keys into heroku app.

closing as it is a duplicate of #89 of the admin site

repo: uoForms/App-CANBeWell


text:
Updating Add to Homescreen button of the English page to Install App

Fix for Issue #660

I have merged the code


text:
Update maddpg_learner.py

Duplicate logging "agent_grad_norm"

I've also noticed this issue and have raised an issue on it, which references your merge request: https://github.com/uoe-agents/epymarl/issues/67.

Hi, thanks for creating this PR!
This has now been resolved in the recent PR so I will close this PR.

repo: uoe-agents/epymarl


text:
Request for aws_codeguruprofiler_profiling_group resource

What resource do you need?
Terraform Resource Name:

aws_codeguruprofiler_profiling_group

Depends on https://github.com/hashicorp/terraform-provider-aws/issues/16768
What is your use case?
Help Java-developers diagnose performance issues.
### Tasks

I'm looking at adding this to upstream - currently blocket on https://github.com/hashicorp/terraform-provider-aws/pull/34355
But will this be a dedicated provider for basically one or two resources under the codeguruprofiler API? Or do you ever merge resources @turkenf ?

But will this be a dedicated provider for basically one or two resources under the codeguruprofiler API? Or do you ever merge resources @turkenf ?

No resources from this API group have been added yet, so yes there will be a new family provider containing the relevant resources.

authors: chlunde turkenf

repo: upbound/provider-aws


text:
Adding google_apigee_nat_address, google_artifact_registry_repository, google_beyondcorp_app_connection, google_beyondcorp_app_connector, google_beyondcorp_app_gateway, google_bigquery_analytics_hub_data_exchange, google_bigquery_analytics_hub_listing to v1beta1 version

Description of your changes
Adding apigee (1) resources to v1beta1 version

[x] google_apigee_nat_address

Adding artifactregistry (1) resources to v1beta1 version

[x] google_artifact_registry_repository

Adding beyondcorp (3) resources to v1beta1 version

[x] google_beyondcorp_app_connection
[x] google_beyondcorp_app_connector
[x] google_beyondcorp_app_gateway

Adding bigqueryanalyticshub (2) resources to v1beta1 version

[x] google_bigquery_analytics_hub_data_exchange
[x] google_bigquery_analytics_hub_listing

Fixes #173
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Manual:
google_apigee_nat_address - An organization resource requires a real project ID

google_beyondcorp_app_connection - The resource requires a real Project ID

Manual & Uptest:
google_artifact_registry_repository -
google_beyondcorp_app_connector -
google_beyondcorp_app_gateway -
google_bigquery_analytics_hub_data_exchange -
google_bigquery_analytics_hub_listing -

/test-examples="examples/bigquery/analyticshubdataexchange.yaml"

/test-examples="examples/artifact/registryrepository.yaml"

/test-examples="examples/beyondcorp/appconnector.yaml"

/test-examples="examples/beyondcorp/appgateway.yaml"

/test-examples="examples/bigquery/analyticshublisting.yaml"

repo: upbound/provider-gcp


text:
Fix e2e tests

I noticed a minor wrong test

Well the test won't work

repo: updatecli/updatecli


text:
Drop node < v16 support & get rid of CommonJS bundles

BREAKING CHANGE: Removed AbortController node polyfill in favour of native one from Node v16
BREAKING CHANGE: Removed CommonJS bundles
Added separate bundle for react-native
Updated dev deps

@shipjs prepare

repo: uploadcare/uploadcare-upload-client


text:
Allow operator to manage PVC and PV

... otherwise you got the error below
time="2017-08-10T08:28:03Z" level=error msg="Could not get pvc!
User "system:serviceaccount:logging:elasticsearch-operator" cannot list
persistentvolumeclaims in the namespace "logging". (get persistentvolumeclaims)" ```

Thanks @gianrubio!

authors: gianrubio stevesloka

repo: upmc-enterprises/elasticsearch-operator


text:
+https alters state somewhere

Suppose that +http://mysite.com works as expected, but then you do:
~zod:dojo> +https://mysite.com
error code: 14090086
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Fair enough, but then subsequent attempts at +http://mysite.com (no s) fail with the same error.
Also, instead of handling the failed verification gracefully, you're left with %dy-no-prompt.

Anton, any comments?
On Thu, Feb 2, 2017 at 2:17 PM, hoclun-rigsep notifications@github.com
wrote:

Suppose that +http://mysite.com works as expected, but then you do:
~zod:dojo> +https://mysite.com
error code: 14090086
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Fair enough, but then subsequent attempts at +http://mysite.com (no s)
fail with the same error.
Also, instead of handling the failed verification gracefully, you're left
with %dy-no-prompt.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/341, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALyAdAQJ5cb_OuhC1O6Ecp6Al8DY_9Tks5rYlYVgaJpZM4L1tbu
.

Can't immediately find anything in dojo or eyre that would retain hostnames at all, let alone across secure/insecure; does the problem persist if you restart the pier?

Problem persists on fresh fakezod using urbit/master and arvo/master.

Can't reproduce this using various examples from the really convenient https://badssl.com.

authors: cgyarvin hoclun-rigsep jtobin ohAitch

repo: urbit/arvo


text:
Fix issue where we were hashing a seed string

The first instance is in the  childNodeFromSeed  function. It returns the seed in a human readable hexadecimal format which we think is okay, but it also passes the childSeed to the  walletFromSeed  function as a hexadecimal string instead of a buffer, which is problematic because the  walletFromSeed  function will call hash on that string. This will work, but the result will not be the same as hashing the underlying seed directly. In other words, SHA-512(buffer) != SHA-512(buf2hex(buffer)).

This is that instance. Incorrect variable naming is no bueno! Pretty sure this fixes it.
Prior to making this change, one test failed. After making this change, two tests failed, because this changes the output to be more correct, which the tests don't yet account for.
(May or may not fix the tests myself, but putting this PR out so it can start being reviewed.

Nice catch, LGTM. I think we should probably have some kind of checklist for refactoring next time. @c-johnson

I think we should probably have some kind of checklist for refactoring next time.

After this gets released, the checklist for future versions/revisions is just "does it give the same output for all kinds of inputs?"

authors: Fang- gavinpatkinson

repo: urbit/keygen-js


text:
fix u3m_water obo

Resolves #372

@joemfb missed the change in semantics -- had just assumed u3m_water was always being called with posts

@joemfb Maybe I'm missing something. why not simply *low_w = u3R->hat_p? This is equal to u3a_heap(u3R) u3C.walign_w. i.e. why are you subtracting 1 in *low_w = u3R->hat_p - 1?.

@ashelkovnykov can you reset your vote? Can't merge I think until you do

repo: urbit/vere


text:
fixed typos in segment labels

This PR fixes a handful of typos in the segment labels. This only really matters when the typos are inconsistent within the same annotation (which they often are).

You should have access already? (The box was already checked)

Hi Uri,
You do need to go and generate a new access token and then use that as your password. Did you already do that?
Eran

On Oct 13, 2021, at 2:13 PM, Oriol Nieto @.***> wrote:
Weird, I'm getting this error:
Username for 'https://github.com': urinieto
Password for @.***':
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: Authentication failed for 'https://github.com/bmcfee/harmonixset.git/'```
I just checked, and I can push to my repos. Any ideas how I could fix this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/urinieto/harmonixset/pull/10#issuecomment-942586105, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACG2WTVWMOALDGBR4CBGQFTUGXD4LANCNFSM5F427FBQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

👍🏻
-Eran (iPhone)

On Oct 13, 2021, at 5:59 PM, Oriol Nieto @.***> wrote:

Hey Eran, that worked, thanks! Just pushed the changes :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

authors: bmcfee eranegozy

repo: urinieto/harmonixset


text:
Update annual vacation days from last year to next year

fix #3623

Kann es Konstellationen geben, bei denen man nicht möchte, dass der jährliche Urlaubsanspruch ins Folgejahr übertragen wird?

Kann es Konstellationen geben, bei denen man nicht möchte, dass der jährliche Urlaubsanspruch ins Folgejahr übertragen wird?

ja ich glaube das ist ggf der Standard, wenn man was verändert hat. Ich denke wir sollten schauen ob die Daten verändert wurden und wenn ja dann die veränderten Übernehmen...muss mich aber auch nochmal besser reindenken

authors: derTobsch honnel

repo: urlaubsverwaltung/urlaubsverwaltung


text:
[ID] Unable to see all "Assigned Agencies" menu options for certain grants

After clicking on the down-arrow in the "Assigned Agencies" dropdown, part of the menu is not visible. Using the down-arrow to select an item works, but after it goes 'below the modal', you can't see what's selected. Clicking and dragging the scroll bar dismisses the menu (and then the scroll bar disappears).

Making the browser window small top-to-bottom causes reverse problem:

Making it narrow 'fixes' it:

This comment shows a possible fix. I tried incorporating it as follows:
--- a/packages/client/src/components/Modals/GrantDetails.vue
+++ b/packages/client/src/components/Modals/GrantDetails.vue
@@ -81,7 +81,8 @@

           <multiselect v-model="selectedAgencies" :options="agencies" :multiple="true" :close-on-select="false"
-            :clear-on-select="false" placeholder="Select agencies" label="name" track-by="id">
+            :clear-on-select="false" placeholder="Select agencies" label="name" track-by="id"
+            style="position:fixed; top:auto; left:auto; width:fit-content">
           </multiselect>

This makes the whole menu show:

However, it makes the dropdown smaller, and puts too much (to my eye, anyway) horizontal visual separation between the dropdown and the “Assign” button:

This may happen to other Vue multiselect components in other modals, which means a better fix would be to subclass multiselect, but I don't know if this is possible.

Hey so because there's a  tag wrapped around the agency drop down and then a separate  wrapped around the assigned button. There's a set styled evenly divided width on the parent of those elements. Picture both of them sitting in 2 evenly sized columns. So when you change the width of the dropdown, the size of the columns stay the same and the assign button is still in the other column  keeping a giant distance in between if that makes sense.
I would just remove all those b-col parent tags, keep it simple and make the row being the parent container element and do some in there.

    <multiselect v-model="selectedAgencies" :options="agencies" :multiple="true" :close-on-select="false"
      :clear-on-select="false" placeholder="Select agencies" label="name" track-by="id"
      style="width: 200px"
    >
    </multiselect>
    Assign

@misspran  Thanks! I will look at this over the weekend and get back to you if I have questions. Have a good weekend.

I'm not clear why css style "position" (which I think of as affecting position in x and y axes) should affect where something is rendered in the z-axis. I read the top-voted answer to this post, but can't make sense of it.
@disambiguator : Might we have a little working session sometime in the next few days to help me understand this?
FYI, using z-index does seem to fix the problem:
--- a/packages/client/src/components/Modals/GrantDetails.vue
+++ b/packages/client/src/components/Modals/GrantDetails.vue
@@ -73,7 +73,7 @@

Assigned Agencies

           <multiselect v-model="selectedAgencies" :options="agencies" :multiple="true" :close-on-select="false"
             :clear-on-select="false" placeholder="Select agencies" label="name" track-by="id"
-            style="width: 300px; margin: 0 16px;"
+            style="z-index: 9999; width: 300px; margin: 0 16px;"
           >

@chrisxkeith Happy to have a working session on this. Did a bit of digging and I think that the z-index answer is a pretty good one.
Basically, a child div cannot "break out" of its parent element. In this case the dropdown being the child element of the modal (not directly but through a few layers).
Honestly, I think the library should be doing this for us, and this is probably annoying for all users of vue-multiselect. The z-index solution solves this by explicitly setting the dropdown to a higher z-index.
Your previous solution of position: fixed would also work because a fixed element is no longer relative and can break out. You'd lose any auto nice layouting that HTML does for you, which is why it looks crappily positioned after that. So you'd have to do manual styling to get it to play nice.
The z-index solution avoids this. Any reason not to?

@disambiguator z-index solution makes sense to me. However, it looks like Vue is doing something (when it generates html) that prevents it from working in some cases. This screenshot shows the bad dropdown behavior with the z-index styling on a parent div.
If it's easier for you to do a working session on a weekend, I'm definitely available. If you give me an email address, I will share my Google Calendar with you so you can see my schedule. Thanks for all your help!

@disambiguator @as1729 Could either of you do a few experiments to see if-and-when this happens to you? I'm trying to figure out if there is some pattern (e.g., screen resolution, window size, etc.) that causes this to happen.
I'm guessing that no end users have reported this because they can type into the text field and reduce number of items in the dropdown. If that is indeed the case, perhaps this can be de-prioritized @TylerHendrickson @mhuang-usdr ?

No partners have reported this. If it's not easily replicable, then we can deprioritize

authors: chrisxkeith disambiguator mhuang-usdr misspran

repo: usdigitalresponse/usdr-gost