Authenticate using Auth-Token

Hello,
I am building a docker-container to compile and run a standard go program, which utilizes a module located in a private artifact-registry go repository. The docker build is executed with cloud-build using a repository-push trigger, meaning that all data required for the build should be located exclusively inside the repository.
I can't find a good way to authenticate to artifact-registry from within the docker-container using artifact-registry-go-tools.
The issue
In order to authenticate to the gcloud artifact registry at build time within the docker-container, I must copy a json_key into the container (i.e. I can't use a volume mount to get ADC). This is fine for a multi-stage build, as it would be discarded from the container itself, but I don't want the json_key inside the repository at all.

EXPOSE 8080
ENTRYPOINT ["./app"]

I can't use buildkit to provide another build-context containing the ADC from outside the repository, as I get the following error:
https://www.docker.com/blog/dockerfiles-now-support-multiple-build-contexts/
--build-context test="~/.config/gcloud"

failed to get build context test: stat ~/.config/gcloud: no such file or directory

It is possible to use go mod vendor to fetch the dependencies locally in an authenticated environment and ship them in the repository, but I would prefer it if I didn't maintain local copies all the time and every trigger of cloudbuild would fetch the latest dependencies automatically. Cloudbuild still couldn't update the vendor files automatically, unless I authenticate!!!
Finally, I could use the cloudbuild secret manager but it would have to contain the entire json_key file, and then pass this into the container using an environment variable, which then extracts it again into the file to pass into artifact-registry-go-tools.
The Question
Could it be possible to pass a raw auth token to the artifact-registry-go-tools instead of a json_key, so that I could set an environment variable using e.g. $(gcloud auth print-access-token)? I believe this would be a more elegant method.
This way, my local build could define an access token easily using gcloud auth, and I could get the access token in cloudbuild easily using the secret manager interface in cloudbuild.
If you have other suggestions, I would be glad to hear them.

+Hanzhen Yi @.>  +kavala-team @.>
Hi Nick, apologies for the delay in responding.  I've included Hanzhen on
the thread as he is the author of artifact-regsitry-go-tools.
I don't completely follow all the phases of your build here - e.g.
Cloud Build, the DockerFile or equivalent docker container build, and the
actual running of the container.
However I think I understand what you're asking for. The authentication
plugin currently does the following, in order:

Uses the google auth libraries to look for ADC.  This will look at the
GOOGLE_APPLICATION_CREDENTIALS environment var for a json key, then will
try getting a token from the metadata service (in the case of GCE VM) etc.
It will fall back to running gcloud to get an auth token

I think what you're asking is if the plugin could also directly support
looking for an auth token from an environment variable, e.g. if there is a
var named, say 'ARTIFACT_REGISTRY_TOKEN', it would expect the value to be
the equivalent of (gcloud auth print-access-token) and pass it directly to
AR.
Is this correct?
On Fri, Mar 17, 2023 at 7:05 AM Nick McDonald @.***>
wrote:

Hello,
I am building a docker-container to compile and run a standard go program,
which utilizes a module located in a private artifact-registry go
repository. The docker build is executed with cloud-build using a
repository-push trigger, meaning that all data required for the build
should be located exclusively inside the repository.
I can't find a good way to authenticate to artifact-registry from within
the docker-container using artifact-registry-go-tools.
The issue
In order to authenticate to the gcloud artifact registry at build time
within the docker-container, I must copy a json_key into the container
(i.e. I can't use a volume mount to get ADC). This is fine for a
multi-stage build, as it would be discarded from the container itself, but
I don't want the json_key inside the repository at all.
I can't use buildkit to provide another build-context containing the ADC,
as I get the following error:
https://www.docker.com/blog/dockerfiles-now-support-multiple-build-contexts/
--build-context test="~/.config/gcloud"
failed to get build context test: stat ~/.config/gcloud: no such file or directory
It is possible to use go mod vendor to fetch the dependencies locally in
an authenticated environment and ship them in the repository, but I would
prefer it if I didn't maintain local copies all the time and every trigger
of cloudbuild would fetch the latest dependencies automatically. Cloudbuild
still couldn't update the vendor files automatically, unless I
authenticate!!!
Finally, I could use the cloudbuild secret manager but it would have to
contain the entire json_key file, and then pass this into the container
using an environment variable, which then extracts it again into the file
to pass into artifact-registry-go-tools.
The Question
Could it be possible to pass a raw auth token to the
artifact-registry-go-tools instead of a json_key, so that I could set an
environment variable using e.g. $(gcloud auth print-access-token)? I
believe this would be a more elegant method.
This way, my local build could define an access token easily using gcloud
auth, and I could get the access token in cloudbuild easily using the
secret manager interface in cloudbuild.
If you have other suggestions, I would be glad to hear them.
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/artifact-registry-go-tools/issues/9,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGA2TTBCMCSFZX36GTTCFTW4RVSXANCNFSM6AAAAAAV6SN3CY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@weigert If you are building on GCB can you try leaving the flag --json_key as empty? the auth tool should then look up Application Default Credentials (ADC) and will eventually use the credentials of the GCB service account.
We could add an additional flag to let the caller pass in the auth token, but I think if ADC works here (no so sure since you are within a docker image) it's the easiest way.

@yihanzhen thanks for the response. I will try to be slightly more specific
I am building locally with buildkit and remotely with GCB. This is a multi-platform build (hence buildkit), which is why the golang binary has to be compiled inside the docker container, not simply mounted. This means that authentication is required inside the container (or alternatively: shipping with go mod vendor, which I don't want).
The issue is that I can't get ADC into the container using a volume mount at build time (i.e. to compile the container), only at runtime. Therefore, any credentials have to be inside the Dockerfile build root, which means having a service account key in my repository (or passed in through secret manager, but only on GCB, not locally).
So, sadly, ADC can't be made available inside the Docker container, and getting the json_key in instead is rather cumbersome and can lead to a discrepancy between local and remote builds.
Alternatively, if I can use a simple auth token with the registry tools, then I can pass this into the container as an environment variable at build-time easily locally and in the cloud, authenticate to my private registry and have a uniform multi-platform build system with GCB within the docker container.
In effect this means that a multi-platform build of a docker container running a go binary, which uses dependencies in a private GCP artifact-registry, would be much simpler and would not require insecure storage of service-account-keys in the repo or an inconsistent build between GCB and local by using the secret manager.
I hope this makes sense!

Since posting this though, I had thought of an alternative solution, which is to utilize go mod vendor in a preceding cloudbuild step to make the dependencies available to the Dockerfile build root that way. This is effectively the "safe" workaround, and lets you authenticate outside of the docker container, circumventing the issue. Then you add the vendor-files to your .gitignore and you can do the same locally. You just need to make sure to refresh them explicitly every time you build.
Still, it's good to note that authenticating with ADC at build-time for a go container with private GAR dependencies is currently not possible (but would be with a token!), and using the json_key alternative is not trivial and potentially insecure if done naively.

Hi.
I would just like to note that the fix resolves my issue nicely.
Within the Dockerfile, one can now write:
#...
ARG GCP_AUTH_TOKEN
ENV GOPROXY="https://LOCATION-go.pkg.dev/PROJECT_ID/REPOSITORY_NAME,https://proxy.golang.org,direct"
ENV GONOSUMDB="MY_DOMAIN/*"
ENV GONOPROXY=github.com/GoogleCloudPlatform/artifact-registry-go-tools
RUN GOPROXY=proxy.golang.org go run github.com/GoogleCloudPlatform/artifact-registry-go-tools/cmd/auth@latest \
      add-locations --locations=LOCATION
RUN GOPROXY=proxy.golang.org \
               go run github.com/GoogleCloudPlatform/artifact-registry-go-tools/cmd/auth@latest refresh \
      --token ${GCP_AUTH_TOKEN}
#...

and can authenticate within the container at build time using:
docker build --build-arg GCP_AUTH_TOKEN="$(gcloud auth print-access-token)"

which is valid locally and in GCB.
Thanks again!

Awesome, thanks for letting us know!
On Fri, Mar 31, 2023 at 2:21 AM Nick McDonald @.***>
wrote:

Hi.
I would just like to note that the fix resolves my issue nicely.
Within the Dockerfile, one can now write:
#...ARG GCP_AUTH_TOKENENV GOPROXY="https://LOCATION-go.pkg.dev/PROJECT_ID/REPOSITORY_NAME,https://proxy.golang.org,direct"ENV GONOSUMDB="MY_DOMAIN/"ENV GONOPROXY=github.com/GoogleCloudPlatform/artifact-registry-go-toolsRUN GOPROXY=proxy.golang.org go run @.**
add-locations --locations=LOCATIONRUN GOPROXY=proxy.golang.org
go run @.*** refresh
--token ${GCP_AUTH_TOKEN}#...
and can authenticate within the container at build time using:
docker build --build-arg GCP_AUTH_TOKEN="$(gcloud auth print-access-token)"
which is valid locally and in GCB.
Thanks again!
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/artifact-registry-go-tools/issues/9#issuecomment-1491615479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGA2TUZCH6VKWORHNUPDNTW62O2FANCNFSM6AAAAAAV6SN3CY
.
You are receiving this because you commented.Message ID:
@.***
.com>


update missing urls

some cmtes were missing urls . this fixes #281 .
--timball

last commit fixes #283
--timball

This looks good to me. Note that it's creating a new field: minority_url. We had url, rss_url, and minority_rss_url, but we didn't have minority_url. Seems only helpful, assuming they're being used by someone. :)

issue is that minority cmte offices are actual offices w/ like staff and fons and websites and addresses all the other associated jazz like that . the hack of just throwing in the "minority_url:" is a stopgap for me for a thing that i'm typing today .
a better thing would be to have a structure like :
- type:
  name:
  thomas_id:
  house_committee_id:
  subcomittees:
  - # various subcomittee things
  office_of:
   - majority: # all associated data
   - minority: # all associated data

the pain is that congress does not maintain a contact repo like this that would be updated by a person who had duties to update it and ensure accuracy rather than me using the data and finding bugs .
--timball

did this get merged ?

I rang in above with a :+1:, deferring to at least one other person for theirs. @JoshData ?

Sorry for the delay, yes +1 wonderful thanks.


Typescript support

Hi guys,
I would like to know if there's gonna be a typescript typings file available for elementalui?

@sqrtroot we'll likely implement flow at some point.


CSL-2175 make things more polymorphic by removing HasConfiguration

Nice, happy to see this. I'll go through it now. Ideally, we'd get rid of these constraints altogether and just take the relevant thing as an argument, but this is a fine step in that direction.


vue ssr  refresh iframe on the client.

Version
2.6.10
Reproduction link
https://github.com/vuejs/vue-hackernews-2.0/
Steps to reproduce
reproduce by vue-hackernews-2.0 (vue ssr official demo)
edit ./App.js
add the code bottom:
</transition>
<iframe v-if="src" :src="src" frameborder="0"></iframe>
</div>

export default {
    computed:{
      src(){
        let items = this.$store.state.items
        return items[Object.keys(items)[1]].url
      }
    }
  }

What is expected?
iframe load once
What is actually happening?
Iframe begin loading when the page is downloaded, but it will refresh the url when the client hydrated.

It certainly appear in Firefox.

If it's refreshed, it's because the src attribute changed value.

Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

If it's refreshed, it's because the src attribute changed value.
Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

Actually i got the src from store, and the server store is the same as the client store.
I tried to find the answer from forum and stackoverflow, but no answer helped, so i reproduced it by add that code to your official demo, and it refresh as well, i have no idea about it.
Thanks for your reply.


re #1169: Added a property to preserve locations on tserver shutdown

Here is a possible mechanism to allow the tablets to be hosted to the same tserver when restarting a system.  Still looking for any cleaner solutions.

IIRC:

The last column is where the tablet was located when a file was written last
The loc column is its current location
The future column is the where it will be located
loc is set and future is cleared when a tablet is hosted, and loc is cleared and future is set when the tablet is not hosted.

I haven't run this down yet, but I'm wondering if:

My description of the columns is correct
If loc remains set on a normal shutdown.

If both of these are yes, then it should be the case on system startup that we can take the set of servers that are alive (after waiting MASTER_STARTUP_TSERVER_AVAIL_MIN_COUNT or MASTER_STARTUP_TSERVER_AVAIL_MAX_WAIT) and immediately re-assign the tablets to those servers before the normal assign/balance process takes place.

The problem is that loc is cleared when a tserver is shutdown.  So there is nothing preserved that specifies where the tablet was last hosted.  Another thought was to set the future location but I feel that can get us into inconsistent states as well.
How can the last location denote a dirty shutdown if at the time that happens it may or may not be equivalent to the current location?  In our case it really does not matter what tserver was hosting the tablet when the data was written.  A good portion of our data is not rewritten and yet the tablet is hosted on a different tserver because of balancing activities.
I don't mind using a property to change the semantics of the last location.  That would work just as well for us.  I will look into doing that.

The problem is that loc is cleared when a tserver is shutdown.

I'm thinking we should not clear on shutdown. loc doesn't get cleared on abnormal shutdown and things still work fine. On startup, after waiting MASTER_STARTUP_TSERVER_AVAIL_MIN_COUNT or MASTER_STARTUP_TSERVER_AVAIL_MAX_WAIT, assign tablet to loc if that tserver is up. If it's not up, then clear loc and let the balancer decide.

Just throwing out another possibility - not sure how this would work (or if at all possible) but maybe it sparks an idea (or its just rubbish)
If you are doing a planned shutdown and if we could create a list of server / tablet assignments (sort of like being able to listSplits) and then we could persist that to an external file.  On startup, have a flag that passes the file with those assignment to something that would then make those bulk assignments were possible.  You may need to account for servers that never came back.
Not sure if it could be a custom balancer that runs once on start-up or if it would be better to run right after the upgrade code - but the idea is that you know you are about to shutdown, you have time to take an assignment snapshot, so maybe it could be handled outside of the "normal" metadata / balancer operations?

I would be curious what would happen on a restart after killing (-9) the master, then performed a normal shutdown of the tservers.

A normal shutdown of tservers will clear out the current location entries.  The tservers would need to be all hard killed to test whether the current location entries would be used on startup.

Tried other options which all had issues:

Avoid clearing the current location.  This will prevent the master from cleanly shutting down because it thinks all of the tablets are still hosted.
Set the future location instead of the last location.  This will prevent the systems from shutting down because the tablets simply get reassigned back to the tserver as soon as they are unloaded.

Hence I am back to using the last location or creating a new entry in the metadata table.  @EdColeman 's idea I expect would work but I would like to avoid creating a separate file.

Opened a new PR against main instead.


fix(sbb-title): move font-smoothing into scss mixin

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@a74f28d). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2355   +/-   ##
=======================================
  Coverage        ?   93.56%
=======================================
  Files           ?      222
  Lines           ?    23267
  Branches        ?     2082
=======================================
  Hits            ?    21770
  Misses          ?     1460
  Partials        ?       37

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Popular tags

Improve the popular tags system in order to add time in it.
Currently, a tag very popular at a time is still popular several weeks/months after.

And deduct tags when a post is edited/deleted.


[WIP] subs.js compose.js: Validate subscriptions without hitting server

Fixes #3629.

Sorry for the very slow review!  I just merged this as 7b2ef7c1a930053c832e8bdc4ed4a5c94f2fead5 after doing a bit of prerequisite refactoring.  Thanks @refeed!


enhancement

@Sarthak-Rout   thanks for making your first contribution, I will be merging your Pull Request, also look at the issues so that you can get a chance to win a limited community Swag from me.
If you like the project and Repo please give it a star and Follow me on Github (would be appreciated)


Stub newer subscriptions API endpoint

The stripe-ruby library uses Stripe's newer subscription API by
default after version 1.42.0 (released 2016-05-04).
Relevant PR here: https://github.com/stripe/stripe-ruby/pull/411

This was merged in as 83b5ec72a1b1b0602bce71af692619b0bfb0284f


Repository sync with upstream from InterUSS

The OpenAPI def of the versioning API should be included as well: https://github.com/interuss/automated_testing_interfaces/tree/main/versioning
My suggestion is to copy the definition statically, to the folder /interfaces/versioning/
As for the openapi-to-go-server, I think the versioning OpenAPI should NOT be included in the makefile "dss_apis", because this specific endpoint is not meant to change frequently, so it would just add overhead to the code generation. When one wants to update the versioning schema, the code generation should be done by hand

The OpenAPI def of the versioning API should be included as well: https://github.com/interuss/automated_testing_interfaces/tree/main/versioning
My suggestion is to copy the definition statically, to the folder /interfaces/versioning/
As for the openapi-to-go-server, I think the versioning OpenAPI should NOT be included in the makefile "dss_apis", because this specific endpoint is not meant to change frequently, so it would just add overhead to the code generation. When one wants to update the versioning schema, the code generation should be done by hand

Done ✅


config/v1: operatorhub API improvements

Improve godocs
Replace name and configuration map with HubSource that will reflect the current state of the default OperatorSources

/cc @smarterclayton @shawn-hurley

@shawn-hurley I have made the changes you requested. Please take a look.

/lgtm

This doesn't look like it allows someone to disable all hub sources?

This doesn't look like it allows someone to disable all hub sources?

Why do you think so? You can put all three defaults in HubSources and mark them as disabled, then they will be removed from the cluster.

@smarterclayton, here is what the cluster OperatorHub object look on a fresh cluster:
(default-config {2} U:4 ✗) operator-marketplace oc get operatorhub cluster -o yaml
apiVersion: config.openshift.io/v1
kind: OperatorHub
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"config.openshift.io/v1","kind":"OperatorHub","metadata":{"annotations":{"release.openshift.io/create-only":"true"},"name":"cluster"},"spec":{}}
    release.openshift.io/create-only: "true"
  creationTimestamp: "2019-08-10T13:35:54Z"
  generation: 3
  name: cluster
  resourceVersion: "368836"
  selfLink: /apis/config.openshift.io/v1/operatorhubs/cluster
  uid: c6b59db1-bb73-11e9-8d5e-0277548b887e
spec: {}
status:
  Sources:
  - disabled: false
    name: redhat-operators
    status: Success
  - disabled: false
    name: certified-operators
    status: Success
  - disabled: false
    name: community-operators
    status: Success

Now if we want to disable all three default sources, this is what it looks like:
(default-config {2} U:4 ✗) operator-marketplace oc get operatorhub cluster -o yaml
apiVersion: config.openshift.io/v1
kind: OperatorHub
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"config.openshift.io/v1","kind":"OperatorHub","metadata":{"annotations":{},"name":"cluster"},"spec":{"sources":[{"disabled":true,"name":"community-operators"},{"disabled":true,"name":"redhat-operators"},{"disabled":true,"name":"certified-operators"}]}}
  creationTimestamp: "2019-08-10T13:35:54Z"
  generation: 4
  name: cluster
  resourceVersion: "369270"
  selfLink: /apis/config.openshift.io/v1/operatorhubs/cluster
  uid: c6b59db1-bb73-11e9-8d5e-0277548b887e
spec:
  sources:
  - disabled: true
    name: community-operators
  - disabled: true
    name: redhat-operators
  - disabled: true
    name: certified-operators
status:
  Sources:
  - disabled: true
    name: redhat-operators
    status: Success
  - disabled: true
    name: certified-operators
    status: Success
  - disabled: true
    name: community-operators
    status: Success

And to prove the sources are not present on the cluster:
(default-config {2} U:4 ✗) operator-marketplace oc get operatorsources -n openshift-marketplace
No resources found.

Please let me know if you have more questions.

How do I know what defaults to add to mark them all disabled?
The following scenario has to be possible:

A 4.2 user installs a cluster and disables all hub sources (using whatever mechanism is available)
In ANY FUTURE 4.Y version, if a new hub source is introduced, it has to be disabled, because the user's intent was "disable all hub sources"

If the mechanism you currently have doesn't allow that to happen, we need to change the shape of the API.

I see your point now. I will spin up a follow up PR that adds to the API that allows a user to do this.

@smarterclayton I have addressed your requirement in https://github.com/openshift/api/pull/409


Warning 'BuildTarget.StandaloneLinux' is obsolete - 2019.2+

I get the following warnings on 2019.3 (went to the beta because of a SSAO rendering bug.. first version I could find without it)
I also get a few other errors (LInux build seems to work for me)
Assets/unity-build/Editor/Build/Platform/BuildLinux.cs(33,39): warning CS0618: 'BuildTarget.StandaloneLinux' is obsolete: 'StandaloneLinux has been removed in 2019.2'

Assets/unity-build/Editor/Build/Platform/BuildLinux.cs(32,39): warning CS0618: 'BuildTarget.StandaloneLinuxUniversal' is obsolete: 'StandaloneLinuxUniversal has been removed in 2019.2'

Yeah, it looks like I need to update the build architectures for these newer 2019 releases of Unity. Should be a quick fix.

Looking forward to 2019 compatibility!


Crash when trying to Load

Hello ! Why, no matter what version of the application I'm using, when I try to start it (sometimes) or I try to hit "Load" the application gives me "crush", exactly like in the picture.
I have Java updated to the latest version.
What can i do? Thank you !

Hey, thanks for reporting!
Could you attach the savegame you are trying to load as a zip?
And is the crash log (the message in the screenshot) the same when it crashes at launch?

Mine happens too, but  with a different error.
Log:
java.lang.IllegalAccessError: class com.github.weisj.darklaf.compatibility.SwingUtil (in unnamed module @0x358cbd13) cannot access class sun.awt.SunToolkit (in module java.desktop) because module java.desktop does not export sun.awt to unnamed module @0x358cbd13 	at com.github.weisj.darklaf.compatibility.SwingUtil.grab(SwingUtil.java:109) 	at com.github.weisj.darklaf.ui.popupmenu.MouseGrabber.grabWindow(MouseGrabber.java:68) 	at com.github.weisj.darklaf.ui.popupmenu.MouseGrabber.stateChanged(MouseGrabber.java:106) 	at java.desktop/javax.swing.MenuSelectionManager.fireStateChanged(Unknown Source) 	at java.desktop/javax.swing.MenuSelectionManager.setSelectedPath(Unknown Source) 	at java.desktop/javax.swing.plaf.basic.BasicMenuUI.appendPath(Unknown Source) 	at java.desktop/javax.swing.plaf.basic.BasicMenuUI$Handler.menuDragMouseDragged(Unknown Source) 	at java.desktop/javax.swing.JMenuItem.fireMenuDragMouseDragged(Unknown Source) 	at java.desktop/javax.swing.JMenuItem.processMenuDragMouseEvent(Unknown Source) 	at java.desktop/javax.swing.JMenuItem.processMouseEvent(Unknown Source) 	at java.desktop/javax.swing.MenuSelectionManager.processMouseEvent(Unknown Source) 	at com.github.weisj.darklaf.ui.popupmenu.MouseGrabber.eventDispatched(MouseGrabber.java:205) 	at java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Unknown Source) 	at java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Unknown Source) 	at java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Unknown Source) 	at java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Unknown Source) 	at java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Unknown Source) 	at java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Unknown Source) 	at java.desktop/java.awt.Component.dispatchEventImpl(Unknown Source) 	at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source) 	at java.desktop/java.awt.Window.dispatchEventImpl(Unknown Source) 	at java.desktop/java.awt.Component.dispatchEvent(Unknown Source) 	at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source) 	at java.desktop/java.awt.EventQueue$4.run(Unknown Source) 	at java.desktop/java.awt.EventQueue$4.run(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) 	at java.desktop/java.awt.EventQueue$5.run(Unknown Source) 	at java.desktop/java.awt.EventQueue$5.run(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) 	at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source) 	at nl.paulinternet.gtasaveedit.view.EventQueueProxy.dispatchEvent(EventQueueProxy.java:14) 	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 	at java.desktop/java.awt.WaitDispatchSupport$2.run(Unknown Source) 	at java.desktop/java.awt.WaitDispatchSupport$4.run(Unknown Source) 	at java.desktop/java.awt.WaitDispatchSupport$4.run(Unknown Source) 	at java.base/java.security.AccessController.doPrivileged(Unknown Source) 	at java.desktop/java.awt.WaitDispatchSupport.enter(Unknown Source) 	at java.desktop/java.awt.Dialog.show(Unknown Source) 	at java.desktop/java.awt.Component.show(Unknown Source) 	at java.desktop/java.awt.Component.setVisible(Unknown Source) 	at java.desktop/java.awt.Window.setVisible(Unknown Source) 	at java.desktop/java.awt.Dialog.setVisible(Unknown Source) 	at nl.paulinternet.gtasaveedit.view.EventQueueProxy.dispatchEvent(EventQueueProxy.java:21) 	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) 	at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

I've solved it (mine) by changing  the GTA  SA location. Don't forget to apply!


SPARKC-84: Rename batch level "all" to "any" and "replicaset" to "replic...

...a_set".

+1

Created a new PR from branch SPARKC-84-3.


Provide a third notification timer :before

:immediately and :delayed are not enough.
There are so many situations, when we do not want to use either of both notification timers. The standard usecase is the orchestration of service and multiple configuration resources. If there is more than one configuration resource, that needs the services to be restarted in case of a change, we do not want the service to be restarted multiple times in a single chef run. We can of course use the delayed timer but then we cannot place another resource that depends on that configuration to be active in the same chef run. Alternatively, we could do the trick and notify a ruby_block resource that modifies the service resource to run a restart action instead of start. That’s what we currently do but it feels wrong and is nothing but intuitive.
I would suggest, that a third timer should be introduced, that simply allows to add the action right before the resource default action takes place. In this case we would see a service[restart] and immediately after a servicestart.
In case its the first run, a second common problem would be addressed too. The common start, restart problem using a package resource and a subscribes notification from the service to the package.

We have an RFC for this already: https://github.com/chef/chef-rfc/blob/master/rfc058-before.md

(ie, we agree, and thank you for filing the report. But we need someone to implement it!)

I think this is actually shipping today as part of 12.7, so you don't have long to wait.


Trailing comma after rest parameter not handled correctly

class Foo {
  hello(
    name: string,
  ) { }

  works<TOutput>(
    ...extraProps: Array<any>
  ): void { }

  fails<TOutput>(
    ...extraProps: Array<any>,
  ): void { }
}

Throws:
11:     ...extraProps: Array<any>,
                                 ^ Rest parameter must be final parameter of an argument list
11:     ...extraProps: Array<any>,
                                 ^ Unexpected token ,
12:   ): void { }
      ^ Unexpected token )
12:   ): void { }
       ^ Unexpected token :
13: }     ^ Unexpected end of input

Tryflow: https://dl.vc/1d

AFAIK, it's the correct behavior to error on the trailing comma here, but we should swallow the comma so we don't barf on the rest of the file.
cc @mroch

Just as a point of reference, node currently errors on the trailing comma, while babel allows it.

@asolove I don't think trailing commas are standard (yet) so Node.js would likely error on them even when not using rest parameters.

@Daniel15 Testing node.js 8.4.0:
Works:
function demo(arg1,) {}

Doesn't work:
function demo(...args,) {}

Works:
function demo(arg1,) {}

Oh cool, i didn't know that it was standard now :D

But it means that formatting is inconsistent and trailing commas can't actually be used everywhere :(

What is the desire to use trailing comma after a rest parameter? Unlike normal formal parameters, if you tried to add another parameter after a rest parameter it will be syntactically incorrect.

What is the desire to use trailing comma after a rest parameter?

Consistent formatting. "Always use trailing commas" is easier than "always use trailing commas except for after a rest parameter"

But when formatting conflicts with semantics the latter should always come first. A comma after a rest parameter is just plain wrong, semantically.

This probably can be closed.
/cc @vkurchatkin


Add Dockerfiles and travis config for MaK and Portico LRCs

Similar to Pitch, add Dockerfiles and Travis config for other RTIs (VTMaK and Portico).
Also include RTI flavor in container tag, e.g. for Pitch use:

tc-runner:pi-dev-latest
tc-runner:pi-dev-1.0.1
tc-runner:pi-latest
tc-runner:pi-1.0.1

General format: <containername>:<rti>[-dev]-<version>
Where <rti> ::= pi | ma | po

This has been added on the development branch in commit 095b2c65622b72264677b679c76be3325e29712a. Travis automatically builds the images for Pitch, MAK and Portico. See: https://hub.docker.com/r/msg134/tc-runner/tags/
Did not test the resulting images yet.

@bergtwvd can you try these out?

Just fired up the vtmak based composition (tc-runner + shipsim).
Initialisation is ok.
Once the test case is started there is a stack trace. See block A below.
There still a Pitch RTI built-in dependency in the TcParam: /root/conf/IVCTsut/vrf/TS_HLA_EncodingRulesTester-2017/TcParam.json refers to the Pitch RTI.
Should be rtiexec, port 4000
After manually changing this, there is another problem. See block B below.
Block A
tc-runner_1                     | 2018-10-04 14:48:55,513 : JMSTestRunner:onMessageConsumer:run: de.fraunhofer.iosb.tc_encodingrulestester.TC0001
tc-runner_1                     | 2018-10-04 14:48:55,514 : JMSTestRunner:onMessageConsumer:run: tsRunFolder is /root/conf/TestSuites/TS_HLA_EncodingRulesTester-1.0.1/bin
tc-runner_1                     | 2018-10-04 14:48:55,516 : JMSTestRunner:onMessageConsumer:run: setCurrentDirectory true
tc-runner_1                     | 2018-10-04 14:48:55,521 : JMSTestRunner:onMessageConsumer:run: TC DIR is /root/conf/TestSuites/TS_HLA_EncodingRulesTester-1.0.1/bin
tc-runner_1                     | 2018-10-04 14:48:55,522 : JMSTestRunner:onMessageConsumer:run: The test case class is: de.fraunhofer.iosb.tc_encodingrulestester.TC0001
tc-runner_1                     | 2018-10-04 14:48:55,539 TC0001: TEST CASE PARAMETERS -------------------------------------- BEGIN
tc-runner_1                     | 2018-10-04 14:48:55,555 TC0001: {"somFiles":[{"fileName":"\/root\/conf\/IVCTsut\/vrf\/TS_HLA_EncodingRulesTester-2017\/BasicSimpleTypes.xml"},{"fileName":"\/root\/conf\/IVCTsut\/vrf\/TS_HLA_EncodingRulesTester-2017\/RPR_FOM_v2.0_1516-2010.xml"}],"fomFiles":[{"fileName":"\/root\/conf\/IVCTsut\/vrf\/TS_HLA_EncodingRulesTester-2017\/RPR_FOM_v2.0_1516-2010.xml"},{"fileName":"\/root\/conf\/IVCTsut\/vrf\/TS_HLA_EncodingRulesTester-2017\/BasicSimpleTypes.xml"}],"rtiHostName":"crc","federationName":"TheWorld","sleepTestTimeWaitSeconds":"60","rtiPort":"8989","sutFederateName":"VRF\/UG"}
tc-runner_1                     | 2018-10-04 14:48:55,555 TC0001: TEST CASE PARAMETERS -------------------------------------- END
tc-runner_1                     | Using MAK Technologies' RTI version 4.5 HLA 1516-2010 for GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-11).
tc-runner_1                     | 2018-10-04 14:48:55,676 TC0001:
tc-runner_1                     | ---------------------------------------------------------------------
tc-runner_1                     | TEST PURPOSE
tc-runner_1                     | Test if a federate correctly encodes the attribute and parameter data
tc-runner_1                     | fields
tc-runner_1                     | Use the SOM files to discover which classes the federate publishes and
tc-runner_1                     | subscribe to these. For each attribute or parameter data received, use
tc-runner_1                     | the OMT encoding rules to test if the buffer is consistent to the OMT
tc-runner_1                     | encoding rules: length, padding and enumerator values.
tc-runner_1                     | This does not imply correctness of the data item values
tc-runner_1                     | ---------------------------------------------------------------------
tc-runner_1                     |
tc-runner_1                     | 2018-10-04 14:48:55,677 TC0001: TEST CASE PREAMBLE
tc-runner_1                     | 2018-10-04 14:48:55,677 TC0001:
tc-runner_1                     | ---------------------------------------------------------------------
tc-runner_1                     | OPERATOR INSTRUCTIONS: Start the test federate before starting the test case with the same
tc-runner_1                     | OPERATOR INSTRUCTIONS: federate name as in the TcParam.json file
tc-runner_1                     | OPERATOR INSTRUCTIONS: The federate should run for the full duration of all the encoding
tc-runner_1                     | OPERATOR INSTRUCTIONS: rules test
tc-runner_1                     | ---------------------------------------------------------------------
tc-runner_1                     |
tc-runner_1                     | Loading Config File: /etc/makrti/rid.mtl
tc-runner_1                     | DtRIDParameters:: applying expression  crcAddress=crc:8989
tc-runner_1                     | Caught exception loading LISP expression: Propagating DtException. (MAKRti::DtlObjPtr MAKRti::DtcEval(const MAKRti::DtlObjPtr&, const MAKRti::DtlObjPtr&) [eval.cxx:352] )
tc-runner_1                     | DtException: MTL Error: Unbound symbol crcAddress=crc:8989 (MAKRti::DtlObjPtr MAKRti::DtcHaltAndCatchFire(char*) [io.cxx:22] )
tc-runner_1                     |
tc-runner_1                     | DtRIDParameters: Error parsing arguments passed in:
tc-runner_1                     |  crcAddress=crc:8989
tc-runner_1                     | terminate called after throwing an instance of 'MAKRti::DtTemplatedException<2>'
activemq_1                      |  WARN | Transport Connection to: tcp://<IP_ADDRESS>:57768 failed: java.io.EOFException
tc-runner_1                     | Aborted (core dumped)
tc-runner_1                     | /root/application/start.sh: wait: line 32: Illegal number:
ivct_tc-runner_1 exited with code 2

Block B
tc-runner_1                     | Loading Config File: /etc/makrti/rid.mtl
tc-runner_1                     | DtRIDParameters:: applying expression  crcAddress=rtiexec:4000
tc-runner_1                     | Caught exception loading LISP expression: Propagating DtException. (MAKRti::DtlObjPtr MAKRti::DtcEval(const MAKRti::DtlObjPtr&, const MAKRti::DtlObjPtr&) [eval.cxx:352] )
tc-runner_1                     | DtException: MTL Error: Unbound symbol crcAddress=rtiexec:4000 (MAKRti::DtlObjPtr MAKRti::DtcHaltAndCatchFire(char*) [io.cxx:22] )
tc-runner_1                     |
tc-runner_1                     | DtRIDParameters: Error parsing arguments passed in:
tc-runner_1                     |  crcAddress=rtiexec:4000
tc-runner_1                     | terminate called after throwing an instance of 'MAKRti::DtTemplatedException<2>'
activemq_1                      |  WARN | Transport Connection to: tcp://<IP_ADDRESS>:51896 failed: java.io.EOFException
tc-runner_1                     | Aborted (core dumped)
tc-runner_1                     | /root/application/start.sh: wait: line 32: Illegal number:

The problem is in the settingsDesignator. The value is RTI specififc, and the test case TS_HLA_EncodingRulesTester hardwires in settingsDesignator = "crcAddress=" + this.rtiHost + ":" + this.rtiPort;. The name crcAddress is only correct for the Pitch RTI.
I close this issue and open a new one for the RTI settings designator issue.

Just to add that I successfully ran the test with Portico, although several errors where raised in the test results, similar to Pitch. Some of the errors are different w.r.t. Pitch because the Portico EncoderFactory is used which I believe deviates at some points from the standard encoding rules. But as such the various bases images for the different RTIs work fine.


Text style changed from primary font file name to txt

See issue #89
Thanks @tarikjabiri  for finding the fix!

@ognjen-petrovic once merged, please advise on when the latest version of this package is available 👍

Can please add the auto generated files to .gitignore (.DS_Store ... dxf ... yarn.lock)

Can please add the auto generated files to .gitignore (.DS_Store ... dxf ... yarn.lock)

Done apologies for the commits, getting used to a new setup.


Fix linting in pipeline

Currently, the pipeline is failing in the lint step with the following log output:
run golangci-lint
  Running [/home/runner/golangci-lint-1.55.1-linux-amd64/golangci-lint run --out-format=github-actions] in [] ...
  Warning: dot-imports: should not use dot imports (revive)
  Warning: dot-imports: should not use dot imports (revive)
  Warning: dot-imports: should not use dot imports (revive)
  Error: import 'github.com/go-playground/validator/v10' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/cloudfoundry/libbuildpack' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/cloudfoundry/libbuildpack' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/cloudfoundry/libbuildpack' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/supply/env' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/open-policy-agent/opa/download' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/open-policy-agent/opa/plugins/bundle' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/common/services' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/supply/env' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/uploader' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/supply' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/uploader' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/common/services' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/stretchr/testify/assert' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/resources/testdata' is not allowed from list 'Main' (depguard)
  Error: import 'code.cloudfoundry.org/buildpackapplifecycle/buildpackrunner/resources' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/golang/mock/gomock' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/open-policy-agent/opa/config' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/open-policy-agent/opa/plugins/bundle' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/open-policy-agent/opa/plugins/rest' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/supply/env' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/uploader' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/resources/testdata' is not allowed from list 'Main' (depguard)
  Error: import 'github.com/SAP/cloud-authorization-buildpack/pkg/supply' is not allowed from list 'Main' (depguard)

  Error: issues found
  Ran golangci-lint in [81](https://github.com/SAP/cloud-authorization-buildpack/actions/runs/6694959079/job/18189434385#step:4:83)167ms

I found the fix here: https://github.com/golangci/golangci-lint-action/issues/759


Deadline plugins deployment

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
Deadline plugins are now inside client codebase, but it would be much better if they would be in private folder supplied in custom deadline Web UI with more information. E.g. which plugins are available, which version of the plugin (we should version the plugins BTW) and in which deadline addon was the plugin version released.
It would reduce size of client codebase and would be much easier for TD to deploy the plugins to deadline.
How would you imagine the implementation of the feature?
Requirement would be frontend that would show available plugins with their versions, the list would be prepared during create_package.py. Current content of client/ayon_deadline/repository/custom would be moved to root of repository. Each plugin would have own subfolder where would be content plugin itself and metadata with version and addon version when the version changed - this might be hard to follow. Content of plugin would be added to tar file (tar keeps file permissions on linux/mac) and metadata would be stored to single file, all located in private folder so they can be downloaded.
Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

I think separation may help - but I'm not entirely sure how we would serve these private files and why that would eventually be nicer "for the TD". Unless you meant, easier for the studio admin/TD who might not do development but does download the AYON addons from the market, then they'd access the files directly through the front-end?

I think separation may help from client - but I'm not entirely sure how we would serve these private files and why that would eventually be nicer "for the TD". Unless you meant, easier for the studio admin/TD who might not do development but does download the AYON addons from the market, then they'd access the files directly through the front-end?

 Yes, private files that can be downloadable via web frontend.

I think separation may help from client - but I'm not entirely sure how we would serve these private files and why that would eventually be nicer "for the TD". Unless you meant, easier for the studio admin/TD who might not do development but does download the AYON addons from the market, then they'd access the files directly through the front-end?

Also for reference, let me quote
https://github.com/ynput/ayon-documentation/blob/d1fc3d884f9561ac982488e72026a8e0d40e4a55/website/docs/dev_addon_creation.md?plain=1#L539-L556

the versioning part is even more important
the similar "issue" we have with other plugins (like Adobe zxp files) these should be handled the same way as suggested here for deadline

We should explore using LakeFS for all those, like we do for USD.

We should explore using LakeFS for all those, like we do for USD.

For files like this I must admit I have my worries about "obfuscating" downloadables like this to behind a fairly non-transparent wall. Having it part of the repository in a way adds maintainability of the files (which of course could auto-upload to lakefs if that makes any sense) but it also ensures that it works locally, offline, etc.
Note that these files are usually very small in size - and they are not dynamic (as far as I know) within the addon version. They are tied to the addon version and separating the distribution would mean just more maintenance.
Having it download from a LakeFS url it's unclear to me what the files may actually contain (and whether they are hence secure?). They may be just as secure as whatever the Git repo provides of course. But just wanted to mention it's definitely something that stands out to me already that it gives me the creeps because "I'm not sure what I'll get" but if it's in the repository I can see the code clearly. Also, note that studios may maintain, in a custom branch, their own custom code version of these files as well - which they'd of course also like to easily deploy to the artists in questions if they need to.

I think it should live in the private folder of the addon.
But, not sure how it should be exposed for artists to download. one idea is to have a frontend where there are download links that uses the ayon api to download the files.
Maybe there are other solutions, but I think they will be generic that also help with other addons with the same situation.
So, we may move this discussion to another issue/epic.

Note that these files are usually very small in size - and they are not dynamic (as far as I know) within the addon version. They are tied to the addon version and separating the distribution would mean just more maintenance.

In this case those files are indeed not artifacts, and keeping them close to the code is indeed paramount :+1:
But what about Murphy's statement then:

the versioning part is even more important
the similar "issue" we have with other plugins (like Adobe zxp files) these should be handled the same way as suggested here for deadline

We should definitely move this discussion to a broader topic and see if there's a one for all solution.


dSYMs and BCSymbolMaps are placed outside of xcframework

I am using this plugin as follows:
create_xcframework(
	workspace: 'Framework.xcworkspace',
	scheme: 'Framework',
	destinations: ['iOS'],
	xcframework_output_directory: 'output'
)

This results in having a separate Framework.xcframework, Framework.dSYMs and Framework.BCSymbolMaps
I would expect the symbols included inside the xcframework, next to the frameworks for the separate architectures.

Hi @gdetari,
thanks for opening this issue.
Can you please test that the BCSymbolMaps & dSYMs are properly generated once the include_debug_symbols param is explicitly set to true?
Eg.
create_xcframework(
	workspace: 'Framework.xcworkspace',
	scheme: 'Framework',
	destinations: ['iOS'],
        include_debug_symbols: true,
	xcframework_output_directory: 'output'
)

Thanks

Thank you, it does include it properly this way.

Good candidate for the Readme imo


尝试执行示例代码出错了ValueError: operands could not be broadcast together with shapes (0,) (3011,)

❓ Questions and Help
前面安装配置一切OK
官方说明是使用qrun benchmarks/LightGBM/workflow_config_lightgbm.yaml
但是我目录下没有这个文件，只有类似的以yaml结尾的两个文件，于是不管执行
qrun benchmarks/LightGBM/workflow_config_lightgbm_Alpha360.yaml 还是
qrun benchmarks/LightGBM/workflow_config_lightgbm_Alpha158.yaml   都提示
ValueError: operands could not be broadcast together with shapes (0,) (3011,)
似乎是数据上格式不匹配，没有对数据及文件进行任何修改，执行XGBOOST目录下其他yaml都是同样的问题！

Thanks for find the link error on the README. It is fixed now.
Did you follow these steps download the data?
You can try these steps to check if the data works

Thanks for find the link error on the README. It is fixed now.
Did you follow these steps download the data?
You can try these steps to check if the data work

Thanks for your reply. I have solved it. The reason is that my pandas and numpy version are too early

Very glad to see that it works for you.
I'll close this issue now.


tests: improve test case descriptions of some interrupt APIs

To add some test case descriptions for testing irq_lock(), irq_unlock(), irq_enable(), irq_disable(), includes descriptions, test step and pass criteria, etc.
Signed-off-by: Enjia Mai<EMAIL_ADDRESS>

@mengxianglinx , please take look at it.

@mengxianglinx , please take look at the PR.


Add uniqueness criterion parameter to "Merge FASTA" tool

To allow merging on unique accession and allowing unique sequences to remain (e.g. identical protein isoforms, gene paralogs/homologs); also enforce accession (header) uniqueness in both modes

Does anyone see a problem with enforcing uniqueness of the header lines even in the "unique sequences" mode? I wasn't able to think of a legitimate case for when the header lines would be the same but the sequences different. But my FASTA experience is almost entirely from the proteomics world, so I could be missing a genomics case.

A header should be unique I think. But I'm worried if you create yourself a FASTA file, give it some dummy names, merge it and loose sequences just because your name was not unique. Can/Should we add an option to rename the header automatically - with a suffix?

What about the following, we leave this PR as it is but we include more output to the stdout, so a user can ready what was happening. In the help section we encourage people to use fasta-to-tabular and tabular-to-fasta for more complicated use-cases?

@bgruening you read my mind.  I was just writing a comment to that effect.  Write a summary of what the tool did to stdout. Also my 2c is that I think uniqueness should on accession not header.  Many tools require unique accessions and completely ignore the headers.

Ira makes a good point about the "uniqueness should on accession not header".  Compomics goes to great lengths to pick the accession out of the header: https://github.com/compomics/compomics-utilities/blob/master/src/main/java/com/compomics/util/protein/Header.java

Accession is part of the header, of course. The FASTA format only defines that there is a header line, it doesn't say how it must be delimited into an accession, description, and god knows what else. That's why tools like Compomics and Mascot have to go to great lengths to parse them to get just the accession. However, my understanding is that that parsing is not really intended for uniqueness detection, but for better presentation of the data and cross-referencing to other resources.
@iracooke , @jj-umn For the most part, unique accessions and unique headers should be the same thing. There are very few cases where the non-accession part will change while the accession part stays the same (and both entries should be kept in the output). Unfortunately, the first and only case that comes to mind is customProDB, which inserts the RPKM value of the protein's transcript into the FASTA header. That makes the header different between different samples even for identical variant proteins.
@PratikDJagtap , I guess what you're asking for is to accommodate the customProDB case where we have multiple variant proteins that may be identical in sequence, but we suffix their accessions with the sample they were found in. You want to keep all those sample names in the header but only keep one instance of the protein sequence, right? I don't think that's necessary except to optimize searching speed. The protein assemblers should take care of that. For example, if there are identical variant proteins from pre-pro-B and pro-B, we should see a protein group like: ABC123_pre-pro-B, ABC123_pro-B. In any case, doing what you ask would require 2 scans through all of the input FASTAs and would be a bigger restructuring of the current script. The current modification is minimal. But if that behavior is really desired, we can talk about it for another PR.
@bgruening It makes perfect sense to add duplicate notifications to stdout. I will do that. Can I test stdout in the tool wrapper without making it a separate output (e.g. mpileup log, tophat log)?

Hi! Just a question concerning memory. When requiring sequence uniqueness, the dictionary stores the entire set of merged sequences. I don't know if this could lead to a memory issue.

Eh, you're right. We should store a hash instead.

This was just a question. If the FASTA output fits in memory, your current code is OK.
Hash is typically used in UniPARC. Computing hash sounds time consuming but might prevent memory failure. May be you should benchmark how much time hash computing will take. For example a loop of 10k hash on a defined-once string of 500 random characters.

@chambm @jj-umn Sorry I raised the ugly head of accessions.  As you say a unique header line works almost all the time.  If you were to "parse" accessions I'd say the only sensible approach is to treat everything up to the first whitespace as an accession.  Almost every fasta file I've seen has this structure.  What comp-omics does is to try and sub-parse what I would consider the fasta accession into other database specific accessions (uniprot, genbank etc) which is definitely not a good idea for this tool.

@iracooke Totally agree. Accession stops at whitespace or line end if there is no description.


#10270: yolov4 implementation

This PR contains ttnn yolov4 implementation with new conv API.

The performance sheets of the following submodules are added herewith:

Downsample1:
ops_perf_results_downsample1_2024_07_11_05_59_20.csv

Downsample2:
ops_perf_results_downsample2_2024_07_11_06_02_41.csv

Downsample3:
ops_perf_results_downsample3_2024_07_11_06_03_58.csv

Downsample4:
ops_perf_results_downsample4_2024_07_11_06_05_30.csv

Downsample5:
ops_perf_results_downsample5_2024_07_11_06_06_58.csv

Performance sheet for neck sub-module : ops_perf_results_neck_2024_07_12_16_43_36.csv
We are not able to generate perf sheets for head sub-module as the test hangs after completing the sub-module and also the yolov4 pipeline fails due to OOM issue in DS5 sub-module first conv itself ,but DS5 sub-module is passing when tested separately.
Currently, Using torch maxpool in neck sub-module as ttnn.maxpool are making issues for those configuration #7746.
And the current pipeline of neck sub-modules outputs face low PCC.

Latest neck and head sub-module perf sheets:
Neck sub-module: ops_perf_results_neck_latest_2024_07_15_17_20_08.csv
Head sub_module: ops_perf_results_head_2024_07_15_17_21_58.csv

All the sub-modules work fine, the YOLOv4 model produces three outputs, and their PCC are greater than 0.95, 0.96, and 0.98, respectively.
Performance sheets of all modules:
Downsample1 sub_module : ops_perf_results_downsample1_17_2024_07_16_12_42_56.csv
Downsample2 sub_module : ops_perf_results_downsample2_17_2024_07_16_12_44_45.csv
Downsample3 sub_module : ops_perf_results_downsample3_17_2024_07_16_12_45_27.csv
Downsample4 sub_module : ops_perf_results_downsample4_17_2024_07_16_12_46_15.csv
Downsample15sub_module : ops_perf_results_downsample5_17_2024_07_16_12_46_55.csv
Neck sub_module : ops_perf_results_neck_17_2024_07_16_12_48_17.csv
Head sub_module : ops_perf_results_head_17_2024_07_16_12_47_31.csv
yolov4 module : ops_perf_results_yolov4_17_2024_07_16_12_49_50.csv

Latest performance sheet,
Downsample 1: ops_perf_results_down_1_18_2024_07_18_17_35_49.csv
Downsample 2: ops_perf_results_down_2_18_2024_07_18_17_36_29.csv
Downsample 3: ops_perf_results_down_3_18_2024_07_18_17_37_22.csv
Downsample 4: ops_perf_results_down_5_18_2024_07_18_17_38_27.csv
Downsample 5: ops_perf_results_down_5_18_2024_07_18_17_38_27.csv
Neck : ops_perf_results_neck_sub_18_2024_07_18_17_39_51.csv
Head : ops_perf_results_head_sub_18_2024_07_18_17_39_12.csv
Yolov4 : ops_perf_results_yolov4_18_latest_2024_07_18_17_41_31.csv
Below are the current FPS,

FPS (MatMul/Conv Ops only): 263.297
FPS (Other Device Ops): 415.307
FPS (All Ops): 187.65

Note :  Currently using 3 torch maxpool which is not visible in the perf sheets.

Latest perf sheet,
yolov4 model: yolov4_19_07_2024.csv
Below are the current FPS,

FPS (MatMul/Conv Ops only): 263.459
FPS (Other Device Ops): 15.494
FPS (All Ops): 14.826

Closing this PR since it's outdated and the YOLOv4 model is in the main.


[3.0]fix, check empty version

Codecov Report

Merging #7933 (9f0d2d2) into 3.0 (e4a8ca1) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.0    #7933      +/-   ##
============================================
- Coverage     58.96%   58.93%   -0.04%
+ Complexity      326      323       -3
============================================
  Files          1081     1081
  Lines         43840    43844       +4
  Branches       6536     6537       +1
============================================
- Hits          25852    25841      -11
- Misses        15112    15127      +15
  Partials       2876     2876

Impacted Files
Coverage Δ

.../org/apache/dubbo/rpc/model/ServiceRepository.java
68.25% <100.00%> (+2.15%)
:arrow_up:

...e/dubbo/remoting/transport/netty/NettyChannel.java
52.27% <0.00%> (-7.96%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
89.65% <0.00%> (-6.90%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
43.47% <0.00%> (-4.35%)
:arrow_down:

...he/dubbo/remoting/transport/netty/NettyServer.java
70.17% <0.00%> (-3.51%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
85.47% <0.00%> (-2.57%)
:arrow_down:

.../dubbo/remoting/transport/netty4/NettyChannel.java
64.35% <0.00%> (-1.99%)
:arrow_down:

...pache/dubbo/registry/support/AbstractRegistry.java
76.92% <0.00%> (-1.47%)
:arrow_down:

...he/dubbo/registry/multicast/MulticastRegistry.java
67.43% <0.00%> (-0.92%)
:arrow_down:

...apache/dubbo/common/extension/ExtensionLoader.java
76.67% <0.00%> (+0.21%)
:arrow_up:

... and 4 more

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 e4a8ca1...9f0d2d2. Read the comment docs.


Helm Charts Improvements and Tests

Proposed Changes:
This PR improves the charts management in CI. It adds a workflow for the Helm charts testing:

Check Version: ensures current_version in setup.cfg and appVersion in Chart.yaml are the same
Lint Helm chart
Test chart deployment on a kind cluster with docker build and check deployment health

PR Checklist:

[X] This PR has no breaking changes.
[X] I have added my changes to the CHANGELOG

🙏 thanks @emmanuelmathot
I think I introduced a breaking change in rio-cogeo 🤦 let me see if I can fix this before we merge

@emmanuelmathot as usual Helm is not my forte. I approved the PR so you can merge whenever you want ;-)

Thank you @vincentsarago. I still want to check that the new workflow do not interfere with a new release. I still perform some test in my fork. I let you know.

To make sure it tests properly before a release, a temporary image is built to be test in the kind cluster.

@emmanuelmathot as usual Helm is not my forte. I approved the PR so you can merge whenever you want ;-)

I do not have the rights to merge actually.

@emmanuelmathot is it ready to be merged?

yes it is. Thx


[BUG] spacy component ValueError: "A token can only be part of one entity"

Describe the bug
When QuickUMLS concept matches occur over the same token, Spacy reports an error like the
To Reproduce
Using QuickUMLS version 1.5 or higher, run the following sample.  Note that if the matching threshold is set higher (e.g. 1.0) this exception may not occur.

nlp = spacy.load('en_core_web_sm')

quickumls_component = SpacyQuickUMLS(nlp, 'PATH_TO_QUICKUMLS_DATA', threshold = 0.25)

nlp.add_pipe(quickumls_component)

doc = nlp('Pt c/o shortness of breath, chest pain, nausea, vomiting, diarrrhea')

**Environment **

OS: Any (@soldni got this in Linux and @burgersmoke got this in Windows)
QuickUMLS version 1.5 (upcoming)
UMLS version 2019AA
SpaCy 2.3

Additional context
@soldni originally reported in this pull request.
The comments are reproduced here:

I was doing some tests and notice that, in the latest version of spaCy (2.3), I get an error if two entities overlap:

Traceback (most recent call last):
File "test.py", line 10, in
doc = nlp('Pt c/o shortness of breath, chest pain, nausea, vomiting, diarrrhea')
File "/home/ubuntu/anaconda3/envs/quickumls/lib/python3.7/site-packages/spacy/language.py", line 449, in call
doc = proc(doc, **component_cfg.get(name, {}))
File "/home/ubuntu/qumls_1.4/QuickUMLS/quickumls/spacy_component.py", line 78, in call
doc.ents = list(doc.ents) + [span]
File "doc.pyx", line 553, in spacy.tokens.doc.Doc.ents.set
ValueError: [E103] Trying to set conflicting doc.ents: '(8, 10, 'C0008031')' and '(8, 10, 'C2926613')'. A token can only be part of one entity, so make sure the entities you're setting don't overlap.
According to this GitHub issue, this seems to be the expected behavior since at least spaCy (2.1.3)
I am planning to solve this by either (a) adding a custom extension type called quickumls to docs, or (b) have each span be a list of matches. Any preference? In the first case, you'd access matches as follows:
for ent in doc..quickumls:
print(ent.text, ent.label, ent..semtypes, ent..similarity)
In the latter, you'd use the following syntax:
for ent in doc.ents:
for match in ent._.quickumls:
print(ent.text, match.cui, match.semtypes, match.similarity)
I personally prefer the second one, as it makes more sense to me to just have an entity with multiple labels, but please do let me know which one you think would make more sense.

This is indeed one of the conventions of current spaCy versions as you noted from this GitHub issue.
So yes, there are a few ways to expose more of the high level match data so that multiple CUI matches might be attached to each entity.  I like the idea of adding additional metadata about candidate matches.
That said, I also really like the idea of entities that can be emitted and used "out of the box" for other downstream tasks such as visualization (e.g. displaCy), and later stage processing like what our group is doing with medspacy.   Specifically, I'm thinking that it would be valuable to keep within spaCy conventions as much as possible so that downstream components like cycontext that @abchapman93 has been working on.
So I still owe some extra due diligence and testing on this, but right now my proposal is going to be whether we can do both.
In other words, as a general principle, could we emit spaCy-standard entities while also adding extensions in the "underscore" but not make this necessary?
Finally, I wanted to do some better debugging to find out why these overlap matches were still returned when I set the overlapping_criteria.  I'll do my part on this question and report back.

@soldni I apologize.  Sometimes I need to type something out before I realize my mistake.  In this case, I previously read your documentation incorrectly.  Specifically, I just looked at what happens with overlapping_criteria in implementation.  I see now that there's not a "winner" selected, but this drives a sorting function.  This makes sense.
So here's what I propose: I'm going to change SpacyQuickUMLS to use the ordering of matches as criteria for the component to prevent overlapping entities.  I see this as "minimum viable" and then I could take more time to think about how to add additional matching information via an extension to the Span.
How does this plan sound?


Factor in start time

Follow up to #4: we should keep track of the last time we entered a task, and use that as the current entry's approximate start time.

As noted in the history, I did this about a week ago.


fix enum + spaces in comments

@natabal this addresses duplicate enums issue and extra spaces issues when entity description not available in spec


When calling state.setHtml(html) method for rendering a HTML Ordered list , each  tag is rendered as a new Ordered list

if you add a OL with three LI as follows:
test1test2test3
it is rendered as :
1 test1
1 test2
1 test3
refer screenshot attached
expected:

test1
test2
test3

This basically happens because of the RichtextHTMLParser creates new OL for each LI. Line number 106

I created a counter for each li and updated the number in constructor of OrderedList ParagraphType. This fixed the issue for now, however I believe all the LI has to be a part of same OL object.

Can you check with the latest version, it's working fine now.


fix: manually bump projen to fix upgrade failure

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #298 (259d30a) into main (2974dfe) will increase coverage by 12.10%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main     #298       +/-   ##
===========================================
+ Coverage   83.33%   95.44%   +12.10%
===========================================
  Files           2        1        -1
  Lines         126      395      +269
  Branches       31       46       +15
===========================================
+ Hits          105      377      +272
+ Misses         21       18        -3

Impacted Files
Coverage Δ

src/index.ts
95.44% <100.00%> (+13.44%)
:arrow_up:

example/src/main.ts

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 fa27629...259d30a. Read the comment docs.


Remove check for cta to display sign up button

Fixes #4336
Fixed a bug where, when the persistent nav setting is turned on, the sign up button would only display if there was a secondary call to action. Now, the sign up button will display even if there is no secondary call to action.
Also, switched import statements to require statements in lib.js for a quick fix for a hoisting issue causing jquery not to be ready before libraries need to use it.
@DoSomething/front-end

:+1: :ship:


rlsf_override is missing some symbols

Namely, C++ allocation functions (used by many) and malloc_usable_size (used by libudev).

Fixed by 0effeec74a7b8d570cc7609bf154db9a64a8e094 and d03f6b31b931e344267ce99c3ccec2487b4e3ea6


Ubuntu 15.10

Hi there,
i tested your cookbook on a Ubuntu 15.10 Server. Its working, but there are many things removed. I think this should not be the way for production.
For example logging or UsePrivilegeSeparation, are things that should not removed by default.
I think seperate each distribution and maybe version (attributes) is a way to go for a better cookbook. Chef-solo / local or chef-zero is build on a ssh connection and from that case it should be a perfect build cookbook like apache2.
Chef Team, please invest some time here!

template[/etc/ssh/ssh_config] action create

update content in file /etc/ssh/ssh_config from 6005ad to 738d96
--- /etc/ssh/ssh_config	2015-04-09 09:48:17.000000000 +0000
+++ /etc/ssh/.chef-ssh_config20160411-7179-1qindz9	2016-04-11 21:19:57.978480519 +0000
@@ -1,55 +1,6 @@
+# This file was generated by Chef for domoticz
+# Do NOT modify this file by hand!

-# This is the ssh client system-wide configuration file.  See
-# ssh_config(5) for more information.  This file provides defaults for
-# users, and the values can be changed in per-user configuration files
-# or on the command line.
-# Configuration data is parsed as follows:
-#  1. command line options
-#  2. user-specific file
-#  3. system-wide file
-# Any configuration value is only changed the first time it is set.
-# Thus, host-specific definitions should be at the beginning of the
-# configuration file, and defaults at the end.
-# Site-wide defaults for some commonly used options.  For a comprehensive
-# list of available options, their meanings and defaults, please see the
-# ssh_config(5) man page.
Host *
-#   ForwardAgent no
-#   ForwardX11 no
-#   ForwardX11Trusted yes
-#   RhostsRSAAuthentication no
-#   RSAAuthentication yes
-#   PasswordAuthentication yes
-#   HostbasedAuthentication no
-#   GSSAPIAuthentication no
-#   GSSAPIDelegateCredentials no
-#   GSSAPIKeyExchange no
-#   GSSAPITrustDNS no
-#   BatchMode no
-#   CheckHostIP yes
-#   AddressFamily any
-#   ConnectTimeout 0
-#   StrictHostKeyChecking ask
-#   IdentityFile ~/.ssh/identity
-#   IdentityFile ~/.ssh/id_rsa
-#   IdentityFile ~/.ssh/id_dsa
-#   Port 22
-#   Protocol 2,1
-#   Cipher 3des
-#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
-#   MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
-#   EscapeChar ~
-#   Tunnel no
-#   TunnelDevice any:any
-#   PermitLocalCommand no
-#   VisualHostKey no
-#   ProxyCommand ssh -q -W %h:%p gateway.example.com
-#   RekeyLimit 1G 1h

SendEnv LANG LC_*
HashKnownHosts yes
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
+UseRoaming no

template[/etc/ssh/sshd_config] action create

update content in file /etc/ssh/sshd_config from 70157d to bfb1d0
--- /etc/ssh/sshd_config	2016-03-20 21:17:14.298343064 +0000
+++ /etc/ssh/.chef-sshd_config20160411-7179-p7xacl	2016-04-11 21:19:58.010480303 +0000
@@ -1,89 +1,8 @@
-# Package generated configuration file
-# See the sshd_config(5) manpage for details
+# This file was generated by Chef for domoticz
+# Do NOT modify this file by hand!

-# What ports, IPs and protocols we listen for
-Port 22
-# Use these options to restrict which interfaces/protocols sshd will bind to
-#ListenAddress ::
-#ListenAddress <IP_ADDRESS>
-Protocol 2
-# HostKeys for protocol version 2
-HostKey /etc/ssh/ssh_host_rsa_key
-HostKey /etc/ssh/ssh_host_dsa_key
-HostKey /etc/ssh/ssh_host_ecdsa_key
-HostKey /etc/ssh/ssh_host_ed25519_key
-#Privilege Separation is turned on for security
-UsePrivilegeSeparation yes
-# Lifetime and size of ephemeral version 1 server key
-KeyRegenerationInterval 3600
-ServerKeyBits 1024
-# Logging
-SyslogFacility AUTH
-LogLevel INFO
-# Authentication:
-LoginGraceTime 120
-PermitRootLogin yes
-StrictModes yes
-RSAAuthentication yes
-PubkeyAuthentication yes
-#AuthorizedKeysFile	%h/.ssh/authorized_keys
-# Don't read the user's ~/.rhosts and ~/.shosts files
-IgnoreRhosts yes
-# For this to work you will also need host keys in /etc/ssh_known_hosts
-RhostsRSAAuthentication no
-# similar for protocol version 2
-HostbasedAuthentication no
-# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
-#IgnoreUserKnownHosts yes
-# To enable empty passwords, change to yes (NOT RECOMMENDED)
-PermitEmptyPasswords no
-# Change to yes to enable challenge-response passwords (beware issues with
-# some PAM modules and threads)
ChallengeResponseAuthentication no
-# Change to no to disable tunnelled clear text passwords
-#PasswordAuthentication yes
-# Kerberos options
-#KerberosAuthentication no
-#KerberosGetAFSToken no
-#KerberosOrLocalPasswd yes
-#KerberosTicketCleanup yes
-# GSSAPI options
-#GSSAPIAuthentication no
-#GSSAPICleanupCredentials yes
-X11Forwarding yes
-X11DisplayOffset 10
-PrintMotd no
-PrintLastLog yes
-TCPKeepAlive yes
-#UseLogin no
-#MaxStartups 10:30:60
-#Banner /etc/issue.net
-# Allow client to pass locale environment variables
-AcceptEnv LANG LC_*
-Subsystem sftp /usr/lib/openssh/sftp-server
-# Set this to 'yes' to enable PAM authentication, account processing,
-# and session processing. If this is enabled, PAM authentication will
-# be allowed through the ChallengeResponseAuthentication and
-# PasswordAuthentication.  Depending on your PAM configuration,
-# PAM authentication via ChallengeResponseAuthentication may bypass
-# the setting of "PermitRootLogin without-password".
-# If you just want the PAM account and session checks to run without
-# PAM authentication, then enable this but set PasswordAuthentication
-# and ChallengeResponseAuthentication to 'no'.
+PasswordAuthentication no
UsePAM yes
+

@florian-asche thanks for investing the time to report this issue. Can you give some more information about the documentation you are including in here? the - headers with the information below? Are you suggesting that those should be the default options? Thanks!

@florian-asche Please do reopen when you have time to update the request for more information.


Matplot backend

Not sure if this issue is generalisable to others or just something I've caused for myself but wanted to report it for posterity. I get the following error:
file "/home/yonni/anaconda3/envs/XeGas/lib/python3.8/site-packages/matplotlib/pyplot.py", line 273, in switch_backend                                              raise ImportError( ImportError: Cannot load backend 'TkAgg' which requires the 'tk' interactive framework, as 'headless' is currently running
I can fix it by adding the following lines into plot.py just before pyplot is imported
import matplotlib
matplotlib.use('Agg')

Hi Yonni! This is an issue I have had before and what I found was that this arises from the the way you set up the environment in which you are running the pipeline. I tried a number of things to try to fix the environment when I had this issue, but ran into all sorts of other dependency issues when I did. However, like you said, changing the backend to 'Agg' will fix the issue and will not impact the way the code runs. Because this issue really depends on the environment of the individual user, there is not much we can do to the pipeline, so I think making that little code change locally is the best way to proceed!

Thanks @annacostelle! Closing this bug as no code change needed at this time.


[22994] - Proper BiometricDidChange Validation.

Ticket

[22994] - Proper BiometricDidChange Validation.

Github Issue

ISSUE-

Description

Store the biometricPolicyState associated with the item in the keychain.
Validate the current biometricPolicyState against the stored one to verify if there was a change.

Commit message

Screenshot

Testing

[x] Added unit tests
[x] Ran unit tests successfully
[ ] Added documentation for public APIs and/or Wiki

Code coverage
Total coverage: 94.54%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
71.43%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
92.21%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 94.55%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
71.43%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
91.82%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 94.57%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
71.43%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
92.72%

Powered by Slather

  Generated by :no_entry_sign: Danger

Code coverage
Total coverage: 94.57%

File
Coverage

TwilioVerifySDK/TwilioSecurity/Sources/Biometrics/BiometricError.swift
71.43%

TwilioVerifySDK/TwilioSecurity/Sources/Storage/AuthenticatedSecureStorage.swift
92.76%

Powered by Slather

  Generated by :no_entry_sign: Danger


Filename column in Document Libraries has Format this column option, but is not supported and doesn't return @currentField

Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
According to the documentation for Column Formatting, the Filename (in Document Libraries) column is not supported.
However, the Format this column option exists in the UI:

And according to this issue on the sp-dev-column-formatting repo it actually worked for some time.
The expectation is that it would either move to supported and work, or the option in the UI would not be available.
Observed Behavior
Format this column option is available despite not supporting the Name column type. This results in nothing being evaluated for @currentField.
However, you can totally get the value of the filename by using a format like this:
{
  "$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json",
  "elmType": "div",
  "txtContent": {
    "operator": "+",
    "operands": [
      "[$FileName]",
      ".",
      "[$File_x0020_Type]"
    ]
  },
  "style": {
    "color": "orange"
  }
}

This looks like this:

Steps to Reproduce
Go to a modern document library and choose Column settings > Format this column for the Name column using the @currentField keyword and get no results.

doesno't work in SharePoint Online …
format text is removed from column settings (cleared)

Hello,
Default column name for files in sharepoint online document library is "LinkFilename".
You can try to use it to get filename.

This issues should be fully solved and fixed, given the work we have done in engineering in this area. To ensure that we clean up the backlog of the issues, we will be closing this one. If you still have issues on this particular area, please open up a new issue so that we can get updated issue description and reproduce steps. We do apologize the non-optimal handling of these old issues and are looking into improving this in future.


After upgrade to 1.5.0, extension not working any more

Expected Behavior
Expected to see the remote explorer icon in the left bar and the usual SFTP-related menu items on right click
Actual Behavior
after extension upgraded to 1.5.0, remote explorer icon disappeared and when right-clicking a file/dir I have no more sync/download/upload items
Steps to Reproduce the Problem
just let the extension upgrade from 1.4.x to 1.5.0
Requisites (important to diagnose the problem!)
Extension Logs
Can't reproduce because extension is already upgraded
Didn't find any logs generated upon startup even with printDebugLog set to true
Specifications

Version: 1.5.0
Platform: Ubuntu 16.04.5 LTS

Any log?

Try v.1.5.2. I think this is because of  the case style for file names.

Try v.1.5.2. I think this is because of the case style for file names.

Version 1.5.2 doesn't work for me. Running SFTP: config, trigger error  command 'sftp.config' not found and the extension doesn't recognize the sftp config.

Same problem here command 'sftp.config' not found also the icon in the left bar disappears...

@mts88 @jmsosso Could you provide some logs?

I have similar problem with 1.5.2.
Automatic synchronisation doesn't work and manual upload trigger error: command 'sftp.upload.activeFile' not found
I have set printDebugLog to true, but didn't find any log.

@mts88 @jmsosso Could you provide some logs?
I can't find any log in debug console.
Downgrading to 1.4.1 suggested by @kataklys works.

@mts88 @kataklys @jmsosso @pet3r @bezbeli I think this should be fixed in v1.5.3.

@mts88 @kataklys @jmsosso @pet3r @bezbeli I think this should be fixed in v1.5.3.

Sorry still not working :(
If I run the command Developper: Show running extensions SFTP doesn't appears in the list.
This is what I see in exthost1.log:
[2018-09-14 14:09:12.779] [exthost1] [info] ExtensionService#_doActivateExtension liximomo.sftp {"startup":true,"activationEvent":"workspaceContains:.vscode/sftp.json"}
[2018-09-14 14:09:12.779] [exthost1] [info] ExtensionService#loadCommonJSModule /home/jmsosso/.vscode/extensions/liximomo.sftp-1.5.3/out/src/extension

But seems the extension is not enabled... but it is. I cannot see nothing more in the logs.

Try 1.5.4.

it's fixed for me ! Thank you so much for your great work !
I can close FileZilla :-D
Cheers


feat: Cloudrun integration with urlmap example

Created a new example of setting up a cloudrun instance(s) with custom routing where /app1 goes to instance 1, and /app2 goes to instance 2.
Included architecture diagram and documentation on how to get started

/gcbrun

Lint test is failing.
Error: submodule's files generation has not been run, please run the
'make build' command and commit changes
./examples/cloudrun-urlmap/main.tf:185:
Error: Trailing whitespace found in the lines above.
Checking for missing newline at end of file
Error: No newline at end of file ./examples/cloudrun-urlmap/main.tf
Also execute terraform fmt on main module and sub-modules.

@shakeebshams r u still working on this PR?

@imrannayer I'm going to close out the PR and start a new in a few weeks. Going to make a few changes


fix(core): Fix service-discovery config

I'm getting an error when trying to use the base as a github link, which I believe is because we are trying to access a resource in a sibling directory. It looks like this may be a bug in kustomize, but I think we can just move this to the core/ directory as a workaround.

Let me know if I'm missing something here and there's a reason this won't work!


use GA metrics

What did this pull request do?
Update metrics library version to support GA metrics recently released
User Case Description
Use the current GA metrics package for OTEL based applications

@dblooman Thank you for your PR. The previous PR https://github.com/go-gorm/opentelemetry/pull/12 has already made the same changes.


move things around to pave the way for future changes

Watch #78 for the next beta containing this change.


Lack of subkey and value for 1000-1005 metadata keys

These metadata transactions do have value on chain. I think these are WMT tokens transactions or something but with metadata on chain.

@matiwinnetou thanks for reporting. I was able to reproduce. I'm looking into it.


Artemis: cb: Support to update boot1 firmware when nvme not ready

Description:

Support to update boot1 firmware when nvme not ready.

Because the currently supported QSPI/PSOC firmware update is when boot1 is loaded, if the OS can't be booted but the Artemis module has power, we need to load boot1 through SMbus to update the QSPI/PSOC firmware.

Motivation:

Support to update boot1 firmware when nvme not ready.

Test Plan:

Build code: Pass
Update boot1 firmware when nvme not ready:

Log:
root@bmc-oob:~# fw-util cb_accl7 --update dev1_boot1 at_cb_psoc_qspi_boot1.pldm Note: Host can't be used to load boot1 during the update process. RequestUpdate Success.
PassComponentTable Success.
UpdateComponent Success.
Download offset : 0x00024800/0x00024880, size : 0x00000080 TransferComplete.
VerifyComplete.
Wait for loading firmware, no more than 20s...
ApplyComplete.
ActivateFirmwareComplete.
Upgrade of cb_accl7 : dev1_boot1 succeeded

We find a issue during the stress test. Temporary close this PR


Increase test timeout for LogsFollowGoGoRoutines

Signed-off-by: John Howard<EMAIL_ADDRESS>@swernli
I've seen this test timeout a couple of times on Jenkins. Increasing timeout from 30 seconds to 60 seconds should hopefully fix it.

Yeah, already done this once from 5s to 30.

Not to be rude or anything, but NOT LGTM because we've tried increasing the timeout already and that's certainly not a solution of any kind.

Oh the irony - Jenkins failed as it hit 60 seconds. Looking at alternate fixes...

Ignore this PR for the moment - pending some discussion on IRC about what the right fix is.


Wrong (non-Haskell) code and table layout

Looking at https://ci.haskell-lang.org/package/aeson, I'm noticing that the GHCi and table mark-up didn't get converted to HTML properly. The table markdown just gets put into a p element, while the non-Haskell code is just inserted as it is.

I fixed the issue with non-haskell code.
The problem with the table is that the markdown package does not support table syntax. I converted it to a (lamentable) HTML table.

Brilliant! It looks great - thanks!


[SPARK-7726] Fix Scaladoc false errors

Visibility rules for static members are different in Scala and Java, and this case requires an explicit static import. Even though these are Java files, they are run through scaladoc, which enforces Scala rules.
Also reverted the commit that reverts the upgrade to 2.11.6

Can one of the admins verify this patch?

Jenkins, add to whitelist

ok to test

Merged build triggered.

Merged build started.

Test build #33075 has started for   PR 6260 at commit f2e998e.

Test build #33075 has finished for   PR 6260 at commit f2e998e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33075/
Test FAILed.

Jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #33079 has started for   PR 6260 at commit f2e998e.

Test build #33079 has finished for   PR 6260 at commit f2e998e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33079/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

LGTM - I tested the reproduction and it worked fine. I can pull this in.


Fix misspelled EnableMCMPReceive option

Once https://github.com/modcluster/mod_proxy_cluster/pull/202 gets merged.

Just fix for the misspelled misspell :smile:

(I was thinking about adding a note about the misspelled variant, but I don't think it's necessary.)

(I was thinking about adding a note about the misspelled variant, but I don't think it's necessary.)

I am afraid we have to include it.... e.g. for CTRK+F use cases...

@rhusar  Note added. I also spotted a typo, so I dared to add a fix here instead of opening a new PR...

@rhusar Note added. I also spotted a typo, so I dared to add a fix here instead of opening a new PR...

haha, that's totally fine :) thx

Well, that was fast. :D Thanks for the merge.


nix-zsh-completions: 0.3.8 -> 0.3.9 ,  nix-bash-completions: 0.6.5 -> 0.6.6

Motivation for this change
For ZSH this adds stuff like nix-build channel:<tab> and the new --options to the legacy commands (this was already fixed for Bash).
Also a few bug fixes. For both shells this fixes a bug in darwin where completing attribute paths of urls would fail if the user hadn't installed sha256sum to the PATH (thanks to @LnL7).
Please backport to 18.03.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build nix-bash-completions nix-zsh-completions

Success on x86_64-darwin (full log)
Attempted: nix-bash-completions, nix-zsh-completions
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/qlbfmf0wsinyp2qdljh439n2arc4q40m-nix-zsh-completions-0.3.9
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/2k5ivwwmhkn0sf560vmyyyzl5bjb84hr-nix-bash-completions-0.6.6
/nix/store/2k5ivwwmhkn0sf560vmyyyzl5bjb84hr-nix-bash-completions-0.6.6
/nix/store/qlbfmf0wsinyp2qdljh439n2arc4q40m-nix-zsh-completions-0.3.9

Success on aarch64-linux (full log)
Attempted: nix-bash-completions, nix-zsh-completions
Partial log (click to expand)
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/fyimixbwdsgfd3c8v8xmzgwh20lcs1dj-nix-zsh-completions-0.3.9
checking for references to /build in /nix/store/fyimixbwdsgfd3c8v8xmzgwh20lcs1dj-nix-zsh-completions-0.3.9...
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/b7gw0pi77kb1ayx0bm7jyw4f4i9h54n8-nix-bash-completions-0.6.6
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/b7gw0pi77kb1ayx0bm7jyw4f4i9h54n8-nix-bash-completions-0.6.6
checking for references to /build in /nix/store/b7gw0pi77kb1ayx0bm7jyw4f4i9h54n8-nix-bash-completions-0.6.6...
/nix/store/b7gw0pi77kb1ayx0bm7jyw4f4i9h54n8-nix-bash-completions-0.6.6
/nix/store/fyimixbwdsgfd3c8v8xmzgwh20lcs1dj-nix-zsh-completions-0.3.9

Backported to 18.03 in e249e593778.

Thanks :) yeah, been putting it off for too long :slightly_frowning_face:

Success on x86_64-linux (full log)
Attempted: nix-bash-completions, nix-zsh-completions
Partial log (click to expand)
these paths will be fetched (0.01 MiB download, 0.05 MiB unpacked):
  /nix/store/6bx0cj8b9gj9zl5jj3qrjysbkdj90b1j-nix-zsh-completions-0.3.9
copying path '/nix/store/6bx0cj8b9gj9zl5jj3qrjysbkdj90b1j-nix-zsh-completions-0.3.9' from 'https://cache.nixos.org'...
/nix/store/a3fc6qhd34flnh9y4mi0gxlmz94ff6dl-nix-bash-completions-0.6.6
/nix/store/6bx0cj8b9gj9zl5jj3qrjysbkdj90b1j-nix-zsh-completions-0.3.9


Add Designate monitoring support

Similar to check_neutron_agents, check_nova_services and the recently added check_gnocchi
we need to add check_designate.
Evaluate to use Service Statuses API https://docs.openstack.org/api-ref/dns/#service-statuses

Imported from Launchpad using lp2gh.

date created: 2019-09-19T15:47:24Z

owner: peppepetra

assignee: None

the launchpad url

(by peppepetra)
The implementation of a smart check for designate is blocked by the bug LP#1761503. Due to this bug designate services are always reported as UP. For that reason there isn't any benefit on developing that check which won't work for now.
To track the work of a smart designate check a new bug has been opened:
https://bugs.launchpad.net/charm-openstack-service-checks/+bug/1845293


optional but favoured: iOS handles reörg

From Weiwu:
This was actually thought to be part of the project "transaction status" UX (which was carried into "Activities" by Tomek), but I (weiwu) put it as an optional task now. The requirement is for reörg to be handled without implementing the UX for it.
In the transaction status, there was a plan to mark transactions as 1) sent, 2) pending; 3) rejected; 4) gone stale;
There is an additional flag, that is 5) changed due to fork (i.e. reörg).
Basically, when reörg happens, check a transaction:

if it is included in the new fork, do nothing.
if it was included in the old fork, but not in the new fork, enter status 5; (note that it may still either be sent or rejected or pending or gone stale).

It is in my belief that during a reörg transactions not included in the new branch is automatically resubmitted (i.e. fed back to mempool), so the client doesn't have to resubmit it. I could be wrong. I believed so because that's how I would designed it.
How to detect reörg: maybe there are APIs for that, but if not, one idea is to mark new transactions as 'unstable' and if they are found to still exist after a revisit more than 10 mins later, mark them as 'stable'.

Dropping this from schema phase 1


fix for debug flags

A combination of some debug flags leads to an internal writing failure. This is a workaround to address #362

@weiyuan-jiang :
I suggest a revised fix, see commit 443291b
Please take a look.  (I did not yet make sure that the fix even compiles.)
I guess the ultimate source of the problem is that subroutine get_io_filename() was called with "option=3" and a "date_time" argument that did not have the pentad field set properly.  BUT, I don't see a call to get_io_filename() with "option=3" anywhere in develop.  Is this something that came up in a developer's new branch?

@gmao-rreichle I got this error today on not so up to date branch (October clone). But than same error was reproduced with current develop. @weiyuan-jiang  was able to reproduce it as well.

The run didn't exit successfully. Can you post the run time error?

1:
sacct: error: slurm_persist_conn_open_without_init: failed to open persistent connection to rmdb5:6830: Connection timed out
sacct: error: slurmdbd: Sending PersistInit msg: Connection timed out
sacct: error: Problem talking to the database: Connection timed out

@gmao-rreichle @weiyuan-jiang  Just by re-running tests now GNUGLOBAL/assim passed. Its was obviously some glitch in post processing. Good news is this PR is zero diff now.


Error: You called Tooltipster's "content" method on an uninitialized element

Hi,
I'm having an issue trying to use functionInit.
I'm trying to use that function to create tooltips with about 12 lines that I want to initialize upon start-up.
The data is already available and I don't need an AJAX call as suggested in the doc example.
Here's my code sample where it shows what I want to do showing only 1 of the 12 lines for the sake of simplicity.

   $('.tooltip').tooltipster({
           position: 'right',
           contentAsHTML: true,
           functionInit: function(origin, content) {
              var userData = userStatus[content]
              if( userData ) {
                  origin.tooltipster('content',
                      "Change Time:"+userData.change_time);
              }
            }
         });

What am I missing?
Thanks in advance!

Hi,
$('.tooltip').tooltipster({
           position: 'right',
           contentAsHTML: true,
           functionInit: function(origin, content) {
              var userData = userStatus[content]
              if( userData ) {
                 return "Change Time:"+userData.change_time;
              }
            }
         });

Merci Louis!
Jérôme  / Blog http://provensal.com/lbb/ / FB
https://www.facebook.com/jerome.provensal / LinkedIn
http://www.linkedin.com/in/jeromeprovensal / IG
http://instagram.com/jeromeig / Tumblr http://creativejp.tumblr.com/ /
On Tue, Feb 10, 2015 at 1:17 AM, Louis Ameline<EMAIL_ADDRESS>wrote:

Hi,
$('.tooltip').tooltipster({
position: 'right',
contentAsHTML: true,
functionInit: function(origin, content) {
var userData = userStatus[content]
if( userData ) {
return "Change Time:"+userData.change_time;
}
}
});
—
Reply to this email directly or view it on GitHub
https://github.com/iamceege/tooltipster/issues/344#issuecomment-73667438
.

De rien :) You're welcome.


Use device_map value when device is unspecified

Closes #299

Could the docs be updated to indicate how to load with an auto device_map? I'm loading with outlines.models.transformers and it's loading to cpu by default