Using keyvault reference in ACI environment variables

Is there a way to use a keyvault referenced environment variable in ACI ?
I am running azure functions within a container instance and I would like to reference the secret using the following construct:
@Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/ec96f02080254f109c51a1f14cdb1931)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7feaa3d0-7233-a3cb-cb9b-a9a55b1f0d7a
Version Independent ID: f41f9d51-52f8-1f45-1043-1344a3b74458
Content: Use Key Vault references - Azure App Service
Content Source: articles/app-service/app-service-key-vault-references.md
Service: app-service
GitHub Login: @mattchenderson
Microsoft Alias: mahender

@proguru Thank you for the question! In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

Hello Bhargavi,
I was looking at the following documents:
https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references
https://azure.microsoft.com/en-us/updates/azure-functions-key-vault-integration/
https://azure.microsoft.com/en-us/blog/simplifying-security-for-serverless-and-web-apps-with-azure-functions-and-app-service/
I am just wondering if you have a similar support for Azure Container instances. There doesn't seem to be any mention of it and I am running an azure function within ACI.

@proguru Thank you for the response! I've routed this to the appropriate Team to investigate and update.

@SnehaAgrawal-MSFT Do you have an update for me ?

@proguru Thanks for asking question! If I have understood right, you want to pass secrets as environment variables using ACI. Azure Container Instances supports secure values for both Windows and Linux containers.
You may refer to below doc link might be helpful:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-environment-variables#secure-values
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-managed-identity

@proguru Since We didn’t hear back from you. We will now close this out but if you feel you need more information please just let us know.

I'm not the original author of this issue, but I have the same requirement and I don't think this has been answered.
The OP asked about using a keyvault secret in an environment variable not using a secret variable, though the solution may end up being related.
You have provided a link to how to use secret variables, but is there is a way of passing a keyvault secret to an environment variable programmatically or through the web gui?
It doesn't appear to work using a keyvault reference in an ARM template, for example.

I agree, the actual question was not answered. I would also love to see this feature. Link environment variables to keyvault and have them refresh when a container is restarted. Similar to how app services work.

I would make sure to file something for that on https://feedback.azure.com under ACI.
This GitHub issue is tracked as relating to the doc on the App Service feature, and I do think it is reasonably closed in that context. However, we should absolutely make sure this request is tracked somewhere for the ACI team to see.

It seems there is still no update on this. So i created a request here:
https://feedback.azure.com/d365community/idea/2c5a9150-8666-ee11-a81c-6045bdb7ea56
Please upvote.

Still no update?


Unable to load initial_data.json (docker)

I am updating the docker image to install longclaw from pip, basically just removed the uneccesary packages and the longclaw build step.
https://github.com/Johnstone-Tech/longclaw_demo/commit/d199c18ec34acc8832b4e7b7088549f5455cf5f2
However when i try to load the initial_data.json file the build fails with the following error.
root@2f30c55f3315:/src# python3 manage.py loaddata /src/data/initial_data.json
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/sqlite3/base.py", line 337, in execute
    return Database.Cursor.execute(self, query, params)
sqlite3.IntegrityError: UNIQUE constraint failed: django_content_type.app_label, django_content_type.model

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "manage.py", line 12, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 367, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 359, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 294, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 345, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/commands/loaddata.py", line 64, in handle
    self.loaddata(fixture_labels)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/commands/loaddata.py", line 104, in loaddata
    self.load_label(fixture_label)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/commands/loaddata.py", line 167, in load_label
    obj.save(using=self.using)
  File "/usr/local/lib/python3.5/dist-packages/django/core/serializers/base.py", line 201, in save
    models.Model.save_base(self.object, using=using, raw=True, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/base.py", line 824, in save_base
    updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/base.py", line 889, in _save_table
    forced_update)
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/base.py", line 939, in _do_update
    return filtered._update(values) > 0
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/query.py", line 654, in _update
    return query.get_compiler(self.db).execute_sql(CURSOR)
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/sql/compiler.py", line 1148, in execute_sql
    cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
  File "/usr/local/lib/python3.5/dist-packages/django/db/models/sql/compiler.py", line 835, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/utils.py", line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line 94, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python3.5/dist-packages/django/utils/six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/sqlite3/base.py", line 337, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.IntegrityError: Problem installing fixture '/src/data/initial_data.json': Could not load contenttypes.ContentType(pk=20): UNIQUE constraint failed: django_content_type.app_label, django_content_type.model

The initial data is already loaded when running docker build so I suspect this why the UNIQUE constraint is failing

No sorry, scratch that. Its my mistake - I have left objects in initial_data which are created automatically when migrating


hyper-rustls: add ring Rustls backend & use it by default

Recently rustls crate switched to the aws-lc-rs crypto backend by default (probably because it's FIPS certified) which requires a C compiler to build, which adds unnecessary complexity.
This PR makes hyper-rustls use pure Rust ring backend by default with an option to use aws-lc-rs through rustls-tls-aws feature.

@blind-oracle

... requires a C compiler to build, which adds unnecessary complexity.
This PR makes hyper-rustls use pure Rust ring backend by default with an option to use aws-lc-rs through rustls-tls-aws feature.

Isn't ring non pure-Rust? https://github.com/briansmith/ring/blob/7c0024abaf4fd59250c9b79cc41a029aa0ef3497/build.rs#L348

they were somewhat inaccurate, build issues tend to be NASM related on Windows, but it's been improving: https://github.com/rustls/rustls/issues/1913


Replacing the font icons by proper SVG icons

Otherwise it can lead to a crappy rendering like

For instance, the vote arrows could be replaced by those you can find here and there (designed by the people at useiconic.com)

it can lead to a crappy rendering like

That's because of a misconfiguration on the server side, which made it load from http and was not making firefox happy. i've fixed it

For instance, the vote arrows could be replaced by those you can find here and there (designed by the people at useiconic.com)

Well.. since it was a config error, is that really necessary ? the actual font may be loaded from SVG depending on your browser, and useiconic.com seems to be commercial.

Well.. since it was a config error, is that really necessary ?

Not anymore, indeed :)

useiconic.com seems to be commercial.

Not those ones because they are freely available on The Nount Project.


Clean old/duplciate  versions fo VT in AgroPortal

Hello @zhilianghu @zhiliangme
Can you ou tell us if its ok to clean some duplicate of 11.4 in AgroPortal ?

Idem for 12.1
If you want us to do it, please confirm whcih one we shall keep (the last? )
Related to https://github.com/agroportal/project-management/issues/140

Yes, it is fine to get rid of the duplicates. Please retain the first one, from February 17, 2021. Thank you!

ok I will do it with a script soon

Closing as done in AgroPortal. I have also kept only one version per month since 2024


Loosing all tokens modification when quiting whitout synchronizing ...

Describe the bug
After modifying tokens if I quit without pushing my modification to Github and then if I'm come back I loose all my work. Seems that a pull is done from Github and it override everything. Huge waste of time !!!
To Reproduce
preriquisite : sync with Github.
Steps to reproduce the behavior:

Open Figma-Token
change some token
quit
come back and everything is lost

Expected behavior
If i quit and come back everything is like I left.

Yes, super annoying. No way to store current progress to Figma file @six7 ?

Will be fixed in the next release 👍

This is now released 🎉


KAFKA-8725: Improve LogCleanerManager#grabFilthiestLog error handling

KAFKA-7215 improved the log cleaner error handling to mitigate thread death but missed one case. Exceptions in grabFilthiestCompactedLog still cause the thread to die.
This patch improves handling to ensure that errors in that function still mark a partition as uncleanable and do not crash the thread.

This PR is a continuation of https://github.com/apache/kafka/pull/7127 (see discussion there)


[Feature Request] Internal allowlist of @fs serving files

Description
Since v2.3.0, we restrcit access to filesystem to avoid secrity issues:

See #2820, #2850

However, this may cause potential breaks for projects using vite <2.3.0

There are some different types of fs url requests:
Type A - Files that users want to access intentionally.
For example, user writes import<EMAIL_ADDRESS>explicitly in their code.
Users are responsible for their own code, so these kind of requests should NOT be restricted.
Setting server.fsServe.root could help, but we may only want to allow<EMAIL_ADDRESS>file, instead of the whole parent path.
Type B - The resolved file path is outsite project root.
Example 1 (bare imports):
The project root is dev/:
export default {
  root: path.resolve(__dirname, 'dev')
}

import 'foo' in the dev/main.ts, then the resolved file is outside project root.
├── node_modules
|   └── foo         # resolved, outside project root
├── dev             # project root
|   ├── index.html
|   └── main.ts     # import 'foo' here
└── vite.config.ts

In addtion, npm link or npm install ../local-path should also cause this problem. (like #3347)
Example 2 (alias):
The project root is dev/, and set alias @some-alias:
export default {
  root: path.resolve(__dirname, 'dev')
  resolve: {
	alias: {
       '@some-alias': path.resolve(__dirname, 'src/index.ts')
    }
  }
}

import '@some-alias' in the dev/main.ts, then the resolved file is outside project root.
├── src
|   └── index.ts    # resolved, outside project root
├── dev             # project root
|   ├── index.html
|   └── main.ts     # import '@some-alias' here
└── vite.config.ts

These files are resolved according to the resolution rules, which should NOT be restricted.
Setting server.fsServe.root could help, but I think we should make it work by default without any extra configs.
Type C - Random traversal via url request
Visiting /@fs/ urls randomly, like #2820, #3281 reported.
This type of requests should be restricted.

In fact, I think Type C is the only thing that should be restricted by default, but now we simply restrict all fs requests outside project root.
Proposed Solution
As https://github.com/vitejs/vite/pull/3321#issuecomment-838171665 recommended, we can provide a configurable allowlist & disallowlist. This could help, but I think we should make Type A and Type B requests work out of the box.
I propose to also maintain an internal allowlist:
If a fs path is specified explicitly in source code (Type A), or resolved from the source code (Type B), we should add the path into the allowlist.
With the help of the internal allowlist, all intentional fs requests are allowed by default, and random visits are restricted.

Sounds good to me. WDYT @vitejs/team?
For the case in type B (commonly see in vitepress), the workspace root should actually be resolved to . instead of ./dev (should serve the dir for the closest package.json if no workspace found)

For type B, I agree, setting a root shouldn't affect the fsServe root.
For type A, AFAIU, users should not be using /@fs/ directly in their code, that is an undocumented internal feature, no? Still, if this is breaking things in the ecosystem because they are already using it, then it is good to allow it (but I don't understand why somebody would use this as the project will not be portable).

Still, if this is breaking things in the ecosystem because they are already using it

For the reference, I do that in Slidev to resolve paths from theme. Which is generated based on user's env. But this does not matter to Slidev as the themes are supposed to be lying under node_modules anyway.

As #3321 (comment) recommended, we can provide a configurable allowlist & disallowlist

I think it is very useful for users.The users should know the loaction of requesting files and configure it if they want to access.  Vite dev server should be serious for files access, I think it is a trade-off with work out of box.

For the case in type B (commonly see in vitepress), the workspace root should actually be resolved to . instead of ./dev (should serve the dir for the closest package.json if no workspace found)

@antfu. I don't think the work will help us out, it will add project maintainer cost because we may encouter another case like this. The allowList is enough for  many case.

should serve the dir for the closest package.json if no workspace found

Yes, that would help for most cases, but we still need to handle linked deps and local deps.

users should not be using /@fs/ directly in their code, that is an undocumented internal feature, no?

Yes, but tools built on top fo vite may use it, (vitepress, vuepress-vite, slidev as @antfu mentioned) lol:

https://github.com/vuejs/vitepress/blob/master/src/node/plugin.ts#L103
https://github.com/vuepress/vuepress-next/blob/cf3d50039e738893b8f7151809fad5a03d91b1b0/packages/%40vuepress/bundler-vite/src/plugin/createPlugin.ts#L96-L98

In fact, Type A and Type B are somehow the same type: resolved fs path is outside the serve root - no matter it is wrote explicitly or resolved implicitly.

In short, if we resolved a fs path from the source code, we should add it to the internal allowlist.


Look Into Replacing ListViews with RecyclerViews

User Requirement: N/A
Description: Read this. Might help with performance issues we have been having.
Story Points: 8
Related Issues: N/A

Links that might be helpful:
https://traversoft.com/2016/01/31/replace-listview-with-recyclerview/
https://codeburst.io/android-swipe-menu-with-recyclerview-8f28a235ff28

This issue can be closed because we have decided to completely move to using RecyclerViews. Implementation is to be done under Issues #133 and #53.


X3D Parser first cut

Supports importing geometry, materials, textures and animations

no specialized nodes (proximity, switch, etc)
no sharing (def/use)

Please consider avoiding "git merge" in the future; it makes the history that much harder to understand, makes bisect more complicated and yields all these extra commits. I find this article helpful https://randyfay.com/content/rebase-workflow-git.
--
You can use this article to produce one commit out of all these: http://stackoverflow.com/questions/5308816/how-to-use-git-merge-squash.

I just quickly looked over this pull request. Here are a few general comments:

The Javadocs are missing.
Remove comments that are not required, unless they help with readability.
Try maintaining camelcase when naming classes and files: https://en.wikipedia.org/wiki/CamelCase
Files are missing copyright headers.

Javadocs are critical. At least short summaries for key classes and methods so we know the intended purpose.
I actually kept skipping over X3Dobject.java. It too large for github. Seems it can (and should) be refactored and cleaned up anyway.

Appreciate all the comments.  To avoid duplication of on-going work, the recommendations here will be included in a new branch (I believe that is the plan).

If there will be a new branch does it mean another pull request? What should happen with this one? Thanks.

Good question.
I’m working with Nola on that.
I believe the plan is for a new branch (tentatively “x3d-usedef”).  I addressed the issues identified by the reviewers in my current code, rather than fix the issues in two places.  Nola will address a few other issues as we are also making changes to GVRAssetLoader.java to enable X3D files to be read from the SD card and remotely.
Part of the problem was my working part-time remotely last week.  I’m also coming up to speed on the workflow for incorporating new branches.
However, I believe Nola would be the best person to confirm this.
Mitch
From: Mihail<EMAIL_ADDRESS>Sent: Friday, June 24, 2016 12:35 PM
To: Samsung/GearVRf<EMAIL_ADDRESS>Cc: Mitchell Williams<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Samsung/GearVRf] X3D Parser first cut (#607)
If there will be a new branch does it mean another pull request? What should happen with this one? Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Samsung/GearVRf/pull/607#issuecomment-228441162, or mute the threadhttps://github.com/notifications/unsubscribe/ARSfvoOcvLzBU87BgyuiDOczkLnsPEe8ks5qPDF_gaJpZM4Izc37.

We will make a new pull request today.
From: Mihail<EMAIL_ADDRESS>Sent: Friday, June 24, 2016 12:35 PM
To: Samsung/GearVRf<EMAIL_ADDRESS>Cc: Nola Donato<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Samsung/GearVRf] X3D Parser first cut (#607)
If there will be a new branch does it mean another pull request? What should happen with this one? Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Samsung/GearVRf/pull/607#issuecomment-228441162, or mute the threadhttps://github.com/notifications/unsubscribe/AQw1S51Hvclve_p7AFmNFxXbk9JSsf9kks5qPDF_gaJpZM4Izc37.


Optional object prop fails to read when specified the key returned from a function

Here's the gist. Why's this failing?
https://flow.org/try/#0C4TwDgpgBAysCuAzRUC8UDeAoKUwCcB7MAfgC5MBtAZ2HwEsA7AcwF0LaGWBfLXrAMaFGtKAEMKcJCnQZ+QkcCgAjSQmRpMOPETAUMAcgDWEEAYoGAbmIA28CAd79E8RgOD1hUZhGABpUwAKAEoOOiZmLVx8X3h8RigDakIAWwgTMz4sQWFRDLCuSPQk1PTTA2ysZQA6AmIoADIGlVrdSgzWKtb6ppa6sEoffyDg1igAenG0AD4oAHcACxAAQlWgA

This looks like an overzealous refinement invalidation. In general,
calling a function invalidates all refinements (because getKey might
mutate b), but here the function is only invoked after b.prop has
already been dereferenced. Indeed, even if getKey is defined as
const b: {prop?: {[string]: string}} = {prop: {key: "value"}};
function getKey(): string {
  delete b.prop;
  return "key";
}

the expression b.prop && b.prop[getKey()] evaluates to "value" (it
does not raise a runtime exception).
I don’t see why the refinement should be invalidated; this looks like a
bug to me.

This now works


[spk] Introspection npm package needs updated unit tests

As a: developer/operator on spk
I want: to be confident that the code coming from the spektate npm package is well tested
Describe the solution you'd like:

[ ] Move the old unit tests from src/tests folder up into the new package
[ ] Improve unit testing for the libraries such as Deployment.ts, AzureDevOpsPipeline.ts, and all other files that compute logic in the spektate package.

Acceptance Criteria:

Unit tests in the spektate repo

Describe alternatives you've considered:
There used to be unit tests until the CLI was moved over to spk, leaving the rest of code behind
Does this require updates to documentation?: No

@samiyaakhtar ideally every pull request you make that is related to that area should just have a little goodness in it that works towards closing the testing gap. Creating a task strictly about testings is always difficult. Adding testing after the fact is really add to predict. I'm marking this as low priority and would prefer we incrementally do this when ever we make changes to the area

@andrebriggs That's right, ideally I don't want to create a task around this. Created this because currently the testing framework is missing from the npm package and pipelines.


[feature fix] Pointer created by Swagger docs belongs to wrong node

Purpose:

https://github.com/CenterForOpenScience/osf.io/issues/3536 Fixes Swagger Doc issue that would create a pointer to itself.

Changes:

Changed variable name in nodes/serializers.py from 'node_id' to 'target_node_id'.

Side Effects:
None.
Notes:
Closes issue:
https://github.com/CenterForOpenScience/osf.io/issues/3536

You didn't need to change any tests for this? If not, that probably means we're missing some tests.

ill look into that right now


fix(cloud_firestore_odm): Better reference typing for query and collection

Description
This PR improves cloud_firestore_odm ergonomics by providing a more specifically typed Reference on collection references and queries.
I found this especially useful for using ODM queries with flutterfire_ui's builders. With this change .reference conversions no longer need a cast, i.e. before we needed:
FirestoreQueryBuilder<User>(
  query: usersRef.reference as Query<User>,
  builder: ...
);

but now this can just be:
FirestoreQueryBuilder<User>(
  query: usersRef.reference,
  builder: ...
);

Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Thanks! Could you add tests for this?

I had some issues running the tests today, but I'll try to figure it out :)

I'll close this PR for now because I haven't managed to get back to it. I'll reopen if I manage to finish it up :)


[NEW ALGORITHM] Find Critical and Pseudo-Critical Edges in Minimum Spanning Tree

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
[NEW ALGORITHM]
MST Tree
Given a weighted undirected connected graph with n vertices numbered from 0 to n - 1, and an array edges where edges[i] = [ai, bi, weighti] represents a bidirectional and weighted edge between nodes ai and bi. A minimum spanning tree (MST) is a subset of the graph's edges that connects all vertices without cycles and with the minimum possible total edge weight.
Find all the critical and pseudo-critical edges in the given graph's minimum spanning tree (MST). An MST edge whose deletion from the graph would cause the MST weight to increase is called a critical edge. On the other hand, a pseudo-critical edge is that which can appear in some MSTs but not all.

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

@pankaj-bind assigned this task to add mst tree probelm !

assigned


什麼時候可以指定server和client端的內網ip

目前默認是<IP_ADDRESS>和2，有考慮單獨分出來做參數可以自行設定嗎

因為有n個client同時連一台server或者n個server到一個client的需求

Hello @hsly109,
Please use the --tun-local and --tun-peer config options. You can run the binaries with -h to see detailed usage.

BTW you can have concurrent UDP clients to the same Phantun client, but you will need multiple Phantun  clients if they connect to different Phantun servers/UDP servers.

thanks


Need support for Google Tasks

What component of google-cloud-cpp is this feature request for?
Google Tasks
Is your feature request related to a problem? Please describe.
I would very much appreciate support for Google Tasks. At the very least be able to create and receive tasks from a Queue (the v2beta3.projects.locations.queues.tasks API) whilst maintaining the Queues using the SDK is not a high priority from C++ backends.
I know, yet another service I cry about but I thought I'd create this ticket to let you know there is need for that.
Describe the solution you'd like
I would like to be able to create and receive tasks from a queue using a high level interface.
A low level interface would also do for now if there's a roadmap to make it a real citizen.
Describe alternatives you've considered
I have considered writing my own HTTPS access against the REST API but decided against it as using the various authentication mechanism is too much difficulty, code, complexity and effort.
Additional context
For addition in https://github.com/MrMoose/CloudConnector this would be particularly helpful.

Whoa, that was unexpected. Will check it out asap.
Thanks!


helm install failure  due to invalid: spec.ports: Required value

I am trying to deploy a ambassador api gateway using helm. Dry run was successful however i am getting the below error while doing helm install
helm install ambassador-6.1.0.tgz --name ambassador --namespace uaw-dev
Error: release ambassador failed: Service "ambassador" is invalid: spec.ports: Required value
Values.yaml https://github.com/naishanair4/ambassador-6.1/blob/master/ambassador/values.yaml
Output of helm version:
$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Output of kubectl version:
@TEMPORA-R51AGI5 /ambassador-6.1.0
$ kubectl version --short
Client Version: v1.16.2
Server Version: v1.12.7+1.2.3.el7
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
oracle kubernetes engine

.spec.ports are already defined in my service template. below service.yaml s generated during dry run
``
Source: ambassador/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
name: quieting-quoll-ambassador
namespace: default
labels:
app.kubernetes.io/name: ambassador
app.kubernetes.io/part-of: quieting-quoll
helm.sh/chart: ambassador-6.1.0
app.kubernetes.io/instance: quieting-quoll
app.kubernetes.io/managed-by: Tiller
app.kubernetes.io/component: ambassador-service
spec:
type: LoadBalancer
ports:
- name: http
port: 80
targetPort: 8080
- name: https
port: 443
targetPort: 8443
selector:
app.kubernetes.io/name: ambassador
app.kubernetes.io/instance: quieting-quoll
``
services.yaml
``
metadata:
name: {{ include "ambassador.fullname" . }}
namespace: {{ .Release.Namespace }}
labels:
app.kubernetes.io/name: {{ include "ambassador.name" . }}
app.kubernetes.io/part-of: {{ .Release.Name }}
helm.sh/chart: {{ include "ambassador.chart" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
app.kubernetes.io/component: ambassador-service
{{- with .Values.service.annotations }}
annotations:
{{- toYaml . | nindent 4 }}
{{- end }}
spec:
type: {{ .Values.service.type }}
{{- if .Values.service.loadBalancerIP }}
loadBalancerIP: "{{ .Values.service.loadBalancerIP }}"
{{- end }}
{{- if .Values.service.externalTrafficPolicy }}
externalTrafficPolicy: "{{ .Values.service.externalTrafficPolicy }}"
{{- end }}
ports:
{{- toYaml .Values.service.ports | nindent 4 }}
selector:
app.kubernetes.io/name: {{ include "ambassador.name" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
{{- with .Values.service.loadBalancerSourceRanges }}
loadBalancerSourceRanges:
{{- toYaml . | nindent 4 }}
{{- end }}
``

You’ve got a template for a Service resource in mapping.yaml too, though, and that looks like the one Helm is complaining about.  (Also it would, if it did render, create a service with a fixed name of “ambassador”, which is probably not what you want to do.)  Maybe this one was an initial draft that was supposed to be removed?

I believe that @omkensey 's response is correct. Closing this due to inactivity.

Have the same issue. spec.ports are defined in values.yaml, but Helm is complaining like could not find it. @omkensey templates could be wrong, but why is the error message then so weird if it has nothing to do with spec.ports?


[bazel] migrate targets that depend on deprecated targets to difs

CC @cfrantz @timothytrippel @a-will anything left to do here?

I think there is not enough information to even understand what this issue was about.
I'll just go ahead and close this. Please re-open if I've missed something.


Make Step 0 visible again

This reverts commit 05e3146.
The Start course button needs more updates for Global Campus.
Summary

Step 0 is invisible now.
Changes

revert 05e3146
Edit the Start course button (template_owner and template_name)
Resolve the conflict (just delete the incoming)
Cherry-pick skills/introduction-to-github@d97b4c6
Update the discussions link in X-finish.md

Task list

[x] For workflow changes, I have verified the Actions workflows function as expected.
[x] For content changes, I have reviewed the style guide.

I haven't generated a repository from this template.
The Start course should be changed to generate a repository in the organization @Exp-Intro-to-GitHub-Flow-Cohort-1 or something.

@mockra @ericdrosado Please review this PR. Any comments or suggestions are welcome.

Hi @mockra, thank you for your comment.
I would really appreciate it if you could let me know the details about the classroom assignment flow.
Is it the Start course button or the welcome step itself that breaks the classroom assignment flow?
How do you generate for learners a new repository in the organization @Exp-Intro-to-GitHub-Flow-Cohort-1 from this repository?

Due to how we use the template, we're not able to leverage the flows in the Welcome step. It breaks the classroom assignment flow we use on the experience back-end. That's part of why we start users off on the Create a Branch section.
If you're okay removing those changes from this pull request, I'd be happy to merge in your other improvements. 🙇🏻♂

Hey @sinsukehlab, this repository is intended to be used for a GitHub Classroom assignment that can be accessed through this page.
The key piece that we can't support at the moment is the Start course button. We're using a different flow than the Skills templates since it's the Classroom assignment that creates the repository for the student. Student will have already gone through a "welcome" flow before seeing the repository.

I have tried the assignment.
I will remove the Start course button, which is not compatible with the Classroom assignment flow. The rest of the welcome step should be visible, for the page you provided doesn't have the contents of the welcome step.
Now the remaining point of concern is the trigger of the Step 0 workflow. The step 0 workflow will update README.md and -step.txt to Step 1 when the initial commit is pushed. There is a possibility that a generated assignment repository will be already in Step 1 when students wait too long before seeing the repository, for they have to click on the link to see the repository.


Add Node&Validator genesis validator.

Genesis phase is over, if you want to become a validator - follow our docs and get enough NLS allocation to get into the active set of validators
https://docs-nolus-protocol.notion.site/Run-a-Mainnet-Validator-f64624c3423c4c41922c3a1d0d342e17


Windows VM memory metric not right

What happened:
Windows VM memory metric not right.
kubevirt_vmi_memory_resident_bytes  value is equal vm guest.memory, not real usage of windows vm.
kubevirt_vmi_memory_available_bytes metric is empty.
What you expected to happen:
How to get the real memory useage of windows vm
How to reproduce it (as minimally and precisely as possible):
create a windows vm.
Additional context:
Add any other context about the problem here.
Environment:

KubeVirt version (use virtctl version):
v0.49
Kubernetes version (use kubectl version):
v1.18

you should install virtio-balloon driver for your windows vm.

Hi,
as @rootdeep pointed out, you need to install the driver. I am wondering if we documented this somewhere.


[image_picker_platform_interface] Migrate image_picker to package:cross_file

Removed the PickedFile implementations and migrated the platform interface to make use of the cross_file library.
Changes have been based on #3388.
Web implementation can be found in: #4083.
Android/iOS implementation can be found in #4073.
Relevant issue:

flutter/flutter#70886

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@BeMacized I've been going back and forth with this one for a couple of days, but we have some internal customers that would benefit greatly from this being a non-breaking change.
Instead of changing the signature of the methods to return an XFile, could we add a new set of methods that return the new type, while keeping the old methods available (and mark them as deprecated?)
That way our customers are going to be able to see the incoming change before forcing them to update their apps.
At a later date, after a few months, or when the next inescapable major version comes, we can delete the deprecated methods and the PickedFile class :/
What do you think?

@ditman If you believe this is something important enough that we should take that route, I'd say we do it.
The only thing I'm a bit vague on atm is what the naming should be for the new alternatives to pickImage, pickVideo and LostData. Just putting a "XFile" suffix on them feels a bit odd, especially considering they will be the only ones left after their deprecated counterparts have been removed in a later version.
Do you happen to have any suggestions?

@BeMacized I think we're at a point where we can reuse the names from v0.6, that have already been removed from everywhere :)
I'd say we replace pick by get, maybe? getImage, getVideo, getMultipleImages... It's not great because we can trigger the camera with this, but at least it doesn't need to use XFile anywhere in the name.
As for the LostData, we might reuse the names from the earlier version? LostData class -> LostDataResponse, and retrieveLostData -> getLostData?
There's some notes about the old method names here: https://pub.dev/documentation/image_picker/latest/#deprecation-warnings-in-pickimage-pickvideo-and-lostdataresponse

@ditman Ah, that indeed sounds like a good idea! I'll see if I can update the PRs for this tomorrow.

Thanks for the patience and extra work @BeMacized!

@ditman Would it be possible for you to take another look? :)

Really looking forward to this merged

Apologies, I was working in fixing a framework P2, I'll get on this today.

I just realized that making things @Deprecated here will break other packages when this gets published, see for example the image_picker with this patch:
dit@dit:~/github/plugins/packages/image_picker/image_picker$ flutter analyze
Warning: You are using these overridden dependencies:
! image_picker_platform_interface 2.2.0 from path ../image_picker_platform_interface
Running "flutter pub get" in image_picker...                       807ms
Analyzing image_picker...

   info • 'LostData' is deprecated and shouldn't be used. Switch to using LostDataResponse instead • test/image_picker_test.dart:313:17 •
          deprecated_member_use
   info • 'LostData' is deprecated and shouldn't be used. Switch to using LostDataResponse instead • test/image_picker_test.dart:326:17 •
          deprecated_member_use

For other users the breakage might be different. It's a little bit late today, but tomorrow I'll update this PR removing the @Deprecated annotations. We'll add the deprecation warnings to the image_picker package directly, when people attempt to use the old methods that return PickedFile, instead of the new ones that return XFile. That way people will get the deprecation warnings only once everything is in place for them to switch to the new code.
My bad, I'll fix this PR ASAP!

@googlebot I consent.

This needs another refresh from master... refreshing now...

@ditman I can confirm the changes have no effect on the implementation PRs, they have been updated accordingly.

Finally published: https://pub.dev/packages/image_picker_platform_interface/changelog#220

cross_file cannot be used in Image.file(File(uri), fit: BoxFit.cover); while universal_io File can.  What is the reason for using the former ?


fix: runsFactor in benchmark

Description
Fix runsFactor in protobuf benchmark. The result on Mac M1:
protobuf
    ✔ decode Attestation message using protobufjs                          3310020 ops/s    302.1130 ns/op   x1.003     395672 runs    120 s
    ✔ encode Attestation message using protobufjs                          2419082 ops/s    413.3800 ns/op   x1.040     288753 runs    120 s

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!.


Add progress bar when downloading the dataset

Get inspiration from this : https://github.com/googleapis/python-storage/issues/27#issuecomment-651468428
We should need to use requests instead of download_to_filename, or to call gsutil via subprocess call..?

Closed with https://github.com/DeepChainBio/bio-datasets/pull/9


73 bdd add a scenario for create in features file and steps file

Codecov Report

Merging #90 (546c90c) into master (962b604) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   95.70%   95.70%
=======================================
  Files           7        7
  Lines         349      349
=======================================
  Hits          334      334
  Misses         15       15

Help us with your feedback. Take ten seconds to tell us how you rate us.


Adding properties grid enhancements in execution plan

Adding a popup viewer for long texts so that people can select and copy from them.

Also fixed an issue with the execution plan editor caching

do you really need to add a custom text viewer? a tooltip could work even better in my opinion since you can see all text at once with text wrapping.

Looks good to me, but please address Alan's comment before merging.

do you really need to add a custom text viewer? a tooltip could work even better in my opinion since you can see all text at once with text wrapping.

@alanrenmsft , the tooltips do not let the users select a portion of text to copy. This gives the users more flexibility on what they want to copy.
@erinstellato-ms, what do you think about this change?

@aasimkhan30, To me it doesn't see to be a big issue, user can simply copy the whole thing to an text editor which is much more convinient to find a part from a long string.
more importantly, is this feature accessible?

@aasimkhan30 @alanrenmsft I don't know the specifics of how this is implemented, but the idea is to provide the capability for users to select and copy the text.  Ideally this is a one-step operation.

@alanrenmsft I sync'd with @aasimkhan30 offline and we reviewed the changes.  There are multiple options for users now in terms of copy:

click on the cell, use CTRL + C
click on the cell, right-click and select copy
click on the cell, press Enter, select some or all text and copy

Bonus: multiple cells can be selected and copied.  I'm good with this change.

@erinstellato-ms how about the keyboard only experience?
@aasimkhan30 Can we use existing slickgrid editor experience to achieve the same? you can make the editor read-only.

@aasimkhan30 To confirm, by "keyboard only experience", you mean a user navigating within the Properties window (without a mouse)?  We didn't test that.  If you can navigate with tab in the Properties window, and then with a cell selected use CTRL + C (or enter and then CTRL + A and CTRL +C), I would deem that acceptable.  However, I don't know if SHIFT + arrow key would then allow you to select multiple cells, and then do CTRL + C.  Let me know if there are additional scenarios.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 40 (7.5%)  changed or added relevant lines in 3 files are covered.
110 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.03%) to 41.66%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesView.ts
0
1
0.0%

src/sql/workbench/contrib/executionPlan/browser/executionPlanView.ts
0
2
0.0%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesViewBase.ts
3
37
8.11%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesViewBase.ts
1
18.75%

extensions/arc/src/common/utils.ts
3
81.23%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

extensions/arc/src/models/controllerModel.ts
32
0%

extensions/azcli/src/az.ts
70
23.41%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
27836

Relevant Lines:
62253

💛  - Coveralls


The syntax of the xUac resource doesn't show the possible values for the Setting property

The syntax of the xUac resource doesn't show the possible values for the Setting property :

According the README.md, this property takes a fixed set of possible values, so we should see them in the syntax.
Also, because of this, the ISE cannot autocomplete the values for this Setting property.

This module have been deprecated and the resource xUac have been replaced by refactored resource UserAccountControl in the module ComputerManagementDsc. Please report any issues in that repository when using the new resource.
We should add conceptual help to the ComputerManagementDsc repo, but it would still not make it possible to autocomplete the values. 🤔 I opened a issue for the conceptual help.


JavascriptOperators::IsIterable can lead to script code getting executed twice instead of once

JavascriptOperators::IsIterable calls JavascriptOperators::GetProperty when the object in question is a JavascriptProxy.  This will lead to code execution in the case that the property is a getter or the proxy has a get trap handler installed.
The use of IsIterable appears to be to check whether or not to go down the slow iterable iteration code paths rather than fast paths.  These code paths however will then again do a GetProperty on the property, which in the proxy case would call that getter or trap handler again.
IsIterable should be removed and uses of it fixed to follow the correct spec semantics.

Is this a 1.2 issue? Would be great to have some 2nd opinions.
@abchatra @bterlson ?

What is the test case for this?

We don't have a real-world test case right now.
The idea is to make a getter function that has side effect and use it to override [Symbol.iterator] of an object, then use the object (possibly through a proxy) to construct a TypedArray.

This has an easy repro.  This bug affects any clients of JavascriptOperators::IsIterable which fortunately is few for now, including JavascriptArray::EntryFrom, TypedArrayBase::EntryFrom, and TypedArrayBase::CreateNewInstance.
Here is an example repro using Array.from()
let iterable = {
    count: 0,
    [Symbol.iterator]() {
        print("iterable[Symbol.iterator]() called: " + this.count);
        return {
            i: 0,
            a: [ 'a', 'b', 'c', 'd', 'e' ],
            next() {
                return {
                    value: this.a[this.i],
                    done: this.i++ >= this.a.length
                };
            }
        };
    }
};

let handler = {
    count: 0,
    get(target, propKey, receiver) {
        if (propKey === Symbol.iterator) {
            print("get trap propKey=Symbol.iterator called: " + ++this.count);
        }
        return target[propKey];
    }
}

let p = new Proxy(iterable, handler);
let a = Array.from(p);
print(a.join(''));

Running this with ch.exe prints the following output
get trap propKey=Symbol.iterator called: 1
get trap propKey=Symbol.iterator called: 2
iterable[Symbol.iterator]() called: 0
abcde

Notice that the trap handler is called twice but iterable[Symbol.iterator]() is only invoked once.
The spec is written such that the trap handler should only be called once, as well as iterable[Symbol.iterator]() being called only once.

Leaving JavascriptOperators::IsIterable in our code base would let to this bug multiplying as the API gets used elsewhere when we implement more features in the future that might make use of it.
I recommend we change the API to JavascriptOperators::GetIteratorFromIterable so that it can make the query and return the iterator so that the property get on Symbol.iterator is only performed once as the spec dictates.

Another repro:
`function getIterator (array)
{
return  ()=> {
return {
next: () => {
return {
value: array.shift(),
done: array.length == 0
};
}
};
}
}
function getcobj () {
var count = 99;
return {
get [Symbol.iterator] () { return getIterator([count--,0]); }
}
}
var d = getcobj();
var b = new Int8Array(d);
print(b);
b = new Int8Array(d);
print(b);
Output:98
96`

Talked to Brian, and he is most interested in the following test case:
var obj = {
  get [Symbol.iterator]() { print("Got!"); return getIterator([1,2]); }
}
for(p of obj) {}

Output
Got!
The test case behaves correctly.
So I would recommend not making this 1.2 but otherwise fix it ASAP before this issue becomes more widespread.

Sounds good to me

Same issue in: OS: Bug 5204357: ES6 Spread over zealous optimization for Arrays ignores user changes to %ArrayIteratorPrototype%.next property


Adding Indian Institute of Management Ahmedabad

https://www.iima.ac.in

@animator Pull request merged. Thank you!


Create Representations “this-is-my-painting”

Automatically generated by Static CMS

👷 Deploy Preview for endearing-maamoul-70d6fa processing.

Name
Link

🔨 Latest commit
ab65cc4fb5a1a1afd8612d12e9a78e3387060371

🔍 Latest deploy log
https://app.netlify.com/sites/endearing-maamoul-70d6fa/deploys/65f19b390db12e00087268e8


Php7

Updated to reflect latest version of PhpStrom

Fantastic, I haven't had a moment to upgrade the container yet. Can you update the README.md and then I'll merge this.
Thanks

Done .
Note that i also updated the Docker image referenced in the Readme run command to:
iainmckay/phpstorm:2016.3-php7
So make sure you re-build/tag the image in your Docker repo :)


ssh-agent not working in fnal-wn-sl7 and fnal-wn-sl7-dev

The following was reported by @vitodb via Slack
Tom tested the SL7 dev container on SBND nodes. Using the DDT debugger distributed through forge_tools UPS package,
he is getting an error related to  ssh-agent  permissions.
In the container distributed via CVMFS, permission for this executable are
Apptainer> ls -lh /usr/bin/ssh-agent
-rwx--x--x 1 65534 65534 374K Aug  1  2023 /usr/bin/ssh-agent

this is causing permissions issues to execute the command.
On the host node it has permissions
[vito@sbndbuild03 ~]$ ls -lh /usr/bin/ssh-agent
-rwxr-xr-x 1 root root 281K Mar  5 16:34 /usr/bin/ssh-agent

this is working fine.
Another check I have done is on the local container in /exp/sbnd/data/...
it got permissions
Apptainer> ls -lh /usr/bin/ssh-agent
---x--s--x 1 vito sbnd 374K Aug  1  2023 /usr/bin/ssh-agent

this is also working, it looks like has the setgid bit on, so this seems to allow it to work

I checked on a stock SL7, the file is in openssh-clients and the permissions ha SGID, appatrently to avoid a strace vulnerability
[root@1a401ba6d143 /]# yum install openssh-clients
...
[root@1a401ba6d143 /]# ls -al /usr/bin/ssh-agent
---x--s--x 1 root nobody 382208 Aug  1  2023 /usr/bin/ssh-agent
[root@1a401ba6d143 /]# ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-DCBiHmjYcJFy/agent.52; export SSH_AUTH_SOCK;
SSH_AGENT_PID=53; export SSH_AGENT_PID;
echo Agent pid 53;

The permission on other RHEL versions is different.

The fnal-dev-sl7 container that we build has SGID set and works fine (I pulled it off Docker Hub)
[root@fermicloud826 ~]# podman run -it docker.io/fermilab/fnal-dev-sl7:latest /bin/bash
[root@d803b189831e /]# ls -al /usr/bin/ssh-agent
---x--s--x 1 root nobody 382208 Aug  1  2023 /usr/bin/ssh-agent
[root@d803b189831e /]# ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-jdMGuDfFFO41/agent.21; export SSH_AUTH_SOCK;
SSH_AGENT_PID=22; export SSH_AGENT_PID;
echo Agent pid 22;
[root@d803b189831e /]#

There may be some changes in the process creating the Apptainer image or expanding in CVMFS.
It may remove SGID permissions.
Will have to check with @DrDaveD or OSG

Apptainer has the No New Priviileges kernel feature set.  Even if the SGID bit is set, it is not used.

Vito made on Ceph a dump of the container with apptainer build --sandbox and the resulting container works,
possibly is a CVMFS feature that could need to handle permission in a specific way

When starting the apptainer container from CVMFS, for example using
/cvmfs/oasis.opensciencegrid.org/mis/apptainer/current/bin/apptainer exec /cvmfs/singularity.opensciencegrid.org/fermilab/fnal-dev-sl7:latest /bin/bash
and an application, or user, tries to run ssh-agent it report permission denied:
$ /cvmfs/oasis.opensciencegrid.org/mis/apptainer/current/bin/apptainer exec /cvmfs/singularity.opensciencegrid.org/fermilab/fnal-dev-sl7:latest /bin/bash
Apptainer> ssh-agent
bash: /usr/bin/ssh-agent: Permission denied
Apptainer> ls -lh /usr/bin/ssh-agent
-rwx--x--x 1 65534 65534 374K Aug  1  2023 /usr/bin/ssh-agent
Apptainer>

This seems to happen with all SL7 container I tested from CVMFS. While, as mentioned in te previous post, if the container is dumped on Ceph volume it has permissions that allow users to use it,
On the other side, testing EL8/EL9 or even SL6 container, ssh-agent works:
$ /cvmfs/oasis.opensciencegrid.org/mis/apptainer/current/bin/apptainer exec /cvmfs/singularity.opensciencegrid.org/fermilab/fnal-wn-el9:latest /bin/bash
Apptainer> ls -lh /usr/bin/ssh-agent
-rwxr-xr-x 1 nobody nobody 281K Mar  5 16:34 /usr/bin/ssh-agent
Apptainer> ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXl3DkwY/agent.167678; export SSH_AUTH_SOCK;
SSH_AGENT_PID=167687; export SSH_AGENT_PID;
echo Agent pid 167687;
Apptainer>

somehow this seems to be an issue with the combination SL7 contained deployed on CVMFS.

I'm skeptical that it works with the SL7 container inside apptainer from a sandbox.  It didn't work for me.  Can you please double-check that @vitodb ?
I did
$ apptainer build --sandbox /scratch/tmp/fnal-dev-sl7 docker://fermilab/fnal-dev-sl7
...
$ apptainer exec /scratch/tmp/fnal-dev-sl7 /bin/bash
Apptainer> ls -l /usr/bin/ssh-agent
---x--s--x 1 dwd fnalgrid 382208 Aug  1  2023 /usr/bin/ssh-agent
Apptainer> ssh-agent
mkdtemp: private socket dir: No such file or directory

On the other hand, if I change those permissions to 711 and execute outside of apptainer it works.  So I'm not exactly sure why the creation of a private socket dir is failing.

It also seems like not a good security model to run ssh-agent inside an apptainer container.  Maybe the user has an alternative.  Normally ssh-agent is run on a desktop or laptop and forwarded everywhere through ssh.

Ok I have done more investigation.  The error I was seeing was because I had set TMPDIR=/scratch/tmp but I didn't that in from the host.  If I add -B /scratch then I see the same problem symptoms as Vito.
The problem is not a missing SGID bit, however.  ssh-agent works fine without it; I don't know what it is for.  It is something about that being mode 711 while not being the owner of the file.  If I build my own sandbox I am the owner so it doesn't matter.  If I change the owner and group of the file in my sandbox to someone else, it also fails with Permission denied.  If I then change the mode to 755, it works ok.  So a workaround is to do chmod 755 /usr/bin/ssh-agent in the Dockerfile of that container.


Repository Upgrade according to guide-open-source v22 version

https://github.com/Ruben-Arushanyan/secure-event-emitter/releases/tag/v4.1.0


Configure pull request

Closes #57

Coverage increased (+1.5%) to 95.816% when pulling cba8642e9b1600997b542a998c4e27ad313e8cbb on feat/config-pr into 417b74bf3b8d07bb06f42791899672c73b7537d5 on master.


Test Issue created at Tue, 25 May 2021 15:27:03 GMT

Test issue body  Tue, 25 May 2021 15:27:03 GMT

Comment on issue at Tue, 25 May 2021 15:27:05 GMT


accounts: backport improvements from INSPIRE profile page

Backport support for Gravatar and email verification icon to upstream.

https://github.com/inspirehep/inspire-next/blob/master/inspire/base/templates/accounts/settings/profile.html

--
cc @jmartinm @tiborsimko

Issue moved to inveniosoftware/invenio-accounts #140 via ZenHub


feat: Implement outlines converter model for structured output (#1211)

Description
Integrate outlines library to produce the structured output.
Motivation and Context
Close #1211.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[x] Implement outlines converter class.
[x] Add examples.

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[x] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[x] I have updated the documentation accordingly.

Thanks @harryeqs, updated!

Thanks @harryeqs, updated!

Thanks @MuggleJinx !


Suggested changes for HPX V1.5 release notes

I have addressed the review comments, thanks!

Thanks for doing this :)


Location data edits not saving

From @aimeehan1:
I corrected Admin 2 from Miami Dade to Broward County, FL.  I removed Admin 3 and Lat Long data points that were also incorrect.
However, after I committed the changes and went back to check the updated case data, the location still read as ‘Miami, Florida, United States.’ There is no way to clear this data.

I am unable to reproduce this locally.

@jim-sheldon View at Case ID37.
I corrected the Location Data to Broward County, however the 'Location' field still reads as Miami.
If you Edit the Case, when you scroll to the location section - there is no way to clear the field, it doesn't event appear!


Build stopped with error in /node_modules/tachyons-build-css/index.js

Just cloned Tachyons for test purposes and build stopped with error (see attached screenshot). I corrected the line in index.js and it works. Could you have a look please?

This works for me at the moment. Can you check what version of node and npm you are using?

node-version 4.4.1, npm version 5.0.4.
I installed it again and had the same error. Then I downloaded the zip file from Github, unzipped it to my hard drive and looked into the index.js in "node_modules/tachyons-build-css“ and found the same error. Please see attached screenshots, Adam.
Best regards from Germany,
Leo
Leo Merkel
Buchhorststr. 13 | 31860 Emmerthal
T +49 5286 990922 | M +49 176 248 248 48
<EMAIL_ADDRESS><EMAIL_ADDRESS>| www.confidea.de http://www.confidea.de/
Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten.  Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte den Absender und vernichten diese Mail. Vielen Dank.
This e-mail, including attachments, is intended for the person(s) or company named and may contain confidential and/or legally privileged information. Unauthorized use, disclosure or copying of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender. Thank you for your cooperation.

Am 20.07.2017 um 13:08 schrieb Adam Morse<EMAIL_ADDRESS>This works for me at the moment. Can you check what version of node and npm you are using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tachyons-css/tachyons/issues/408#issuecomment-316671611, or mute the thread https://github.com/notifications/unsubscribe-auth/ACW3xQ6z5d9BmUmJqAfjA8zPgM5lgayWks5sPzUhgaJpZM4Odzhw.

I would suggest updating to the latest versions of both npm and node although I suspect node is the culprit here as Node is currently at version 6.11.1 (stable) 8.2.0 (latest). Please let us know if you can't get it to work on one of the latest versions of node.

Works now after updating node to 8.2.0 and npm to 5.3.0. Tnx for your help!


KAFKA-8717: Reuse cached offset metadata when reading from log

Although we currently cache offset metadata for the high watermark and last stable offset, we don't use it when reading from the log. Instead we always look it up from the index. This patch pushes fetch isolation into Log.read so that we are able to reuse the cached offset metadata.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for the PR. Concretely, does this mean we save one index look up in the usual consumer reading to the end of the log (hw or lso) case? Even though one would expect the index to be in the page cache, always good to do less work when possible.

@ijuma Yes, that's right. This came up in the context of KIP-392 because we realized that, unlike the leader, the follower would always need one lookup to fetch the high watermark or LSO. However, we saw that the leader was already doing an extra lookup whenever it read from the log, so we thought we could eliminate that lookup and bring the follower fetch at least up to parity with the leader's current behavior.
To be perfectly honest, I am slightly skeptical of the benefit of this offset metadata caching. I did some brief consumer performance testing with this patch and saw basically no difference. But it's a bit harder to say in a more general context with more partitions and more consumers. In any case, I thought this presented a nice opportunity to simplify some of the internal fetch APIs a little bit.

retest this please

retest this please

retest this please


Add efm-langserver

Oops. Sorry. I broke something?
https://microsoft.github.io/language-server-protocol/implementors/servers/

@mattn It looks okay to me. What are you seeing?

Actually the table rendering (grid lines) broke

If my memory is certain, when I saw the list in a few weeks ago, there was a border on the table.

@mattn correct it should look like this:

Let me have a look to find out what happened.

Fixed it. Was the extra newline before {: .table .table-bordered .table-responsive}

Thank you!


dependent library version old?

It seems that numpy matplotlib 's version maybe a little old?

Thanks for pointing out. Will change it to latest.

Great package!!
I have the same issues, I wonder if it should be updated again

Will update soon. Hope you're still able to use it by reinstalling the latest version of numpy and pandas after installing featexp.

Thanks! :) please let us know when it happens!


Prevent unneccessary Navigation on "Back" caused by HighlightCorrectButton

HighlightCorrectButton updates the Selected hamburger button, the property itself triggers methods and navigation requests. This causes some useless navigation events when "Back" button is used or on application startup. This PR will fix this, #1376

The UpdateInternalBindingValues call is not absolutely neccessary, but during my tests, I have had a serious problem where one button was suddenly disabled. This is why I decided to update the internal state whenever the state is updated.


Bottom half of the Pledge button is not clickable

Title: Bottom half of the Pledge button is not clickable.
Platform / OS: Windows Desktop
Browser: Google Chrome
Description: The Pledge button is not clickable when user hovers then click/tap on the bottom half of the button.
Steps to Reproduce:

Go to about us link of the page -- https://www.sleepbus.org/about-us
Scroll down until you see the pledge button in the middle
Hover on the bottom half then try to click on the button. Notice that the bottom part is not clickable.

Expected Behavior: All parts of the button are clickable.
Additional Info: This only happens on the “about us” section but works fine on other pages wherein the pledge button is scene. There is also a noticeable “---“ extra characters after the word pledge.

The problem is also present in the donate and fundraise button.
The extra character "--" is also present on this page:
https://dev.sleepbus.org/connect

still not clickable the bottom half of the donate, pledge and fundraise button in https://www.sleepbus.org/about-us

@mop13 my bad, thought it was due to other common issue. Have pushed a new fix up now, should be sorted on prod.

@leonstafford one last thing "Pledge--" is still present in https://www.sleepbus.org/donate

copy that. will put back in dev column, need to find where that content is coming from... the theme of today's work 🔎

Verified fixed in prod build


Fix Vertical Health Bar

Now that OSU! Stuff is gone I should rewrite this or something, I saw that ProjectFNF had the vertical health bar stuff, I should probably base the actual code on that one or something

Discontinued lol


fix(RHTAPWATCH-847): some gitlab MR snapshots missed

There are multiple event-types that can be associated with GitLab MRs. Instead of trying to enumerate them all, we change the logic to spot push events (either missing the event-type label or it has value of push/Push) and consider the rest PR snapshots.
Maintainers will complete the following section

[x] Commit messages are descriptive enough (hints)
[x] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

/retest-required

/retest-required


talk a code snap from line to line

be able to export from line-to-line code
would be nice if it had an interactive way, but I can work on a solution that cut it from line to line as an option, my solution would be instead of passing the whole file, pip it through cut or select then give the output to freeze
cat src/index.ts | head -n 2 | tail -n +1 | freeze code.ts -o test.png --language javascript
This is what I do to do that mission, so it would be nice if we could do it within freeze auto

Hey @Mahmoudgalalz, thanks for opening this issue!
Have you tried the --lines flag?
freeze src/index.ts --lines 3,-1 --output test.png --language javascript

oh, it works
Thanks, need to document that


Processors listed as deployed despite installation failed

Bug Description
If a processor failed while running the install.sh script, it is still listed as deployed.
Steps To Reproduce
Deploy a processor with a failing installation.
Expected behaviour
Deployment to fail and user to be informed accordingly.
Actual behaviour
Processor listed as deployed.

Unless the exit code of install.sh returns a non-zero value, the RTI cannot pickup any issues. In general, processor deployment is more robust since #395. However, this issue is primarily with the install.sh script itself. Not going to improve but instead wait for planned redesign to focus on containerisation which will make this issue obsolete.


Importing config and data from previous OpenLDAP installation

Hi,
I am trying to migrate my OpenLDAP server form a previous (non-dockerised) installation to a dockerised one. On my previous server, I did the following to export the configuration and the users (from serverfault):
slapcat -n 0 -l config.ldif
slapcat -n 1 -l users.ldif

Accoding to the same stop, what I should do on the new server is:

Stop the LDAP server;
Delete the content of the slapd.d folder;
Run slapadd -n 0 -l config.ldif.

Unfortunately, I cannot (or do not know how to) do that with your image. I tried the following:
docker cp config.ldif openldap:/config.ldif
docker exec openldap slapadd -n -0 -l config.ldif

But I get the following:
slapadd: could not add entry dn="cn=config" (line=1):

Which, according to this, is because the slapd service is still running and/or the /etc/ldap/slapd.d folder is not empty.
I am fairly new to docker and certainly not an LDAP expert... Is there a way to import my previous configuration and users into this docker image?
Note: I am using a data volume container for both /var/lib/ldap and /etc/ldap/slapd.d.

Hello,
it's hard with this image because it's a single process container, so if you stop openldap the container stops but this can be done more easily with openldap-backup image:
https://github.com/osixia/docker-openldap-backup

start a new openldap-backup container
copy the ldif files to /data/backup in the container
execute in the container the following commands:
slapd-restore-config config.ldif
slapd-restore-data users.ldif

let me know if you have any problem :)

Thanx for this entry, it took me hours to figure this way out. This is quite easy and shall really be documented to the image readme. Now its easy to dockerize an already populated installation.

@Boldie I am trying to do the same thing as op here but there is no such command as slapd-restore.
Am i missing something or do i need to take another step first?
I am aware this is pretty old but fingers crossed

Im not really sure what I did, but I think, I used a clean install of the docker container, add my ldif files and then use the restore command. Sure first you need to make a backup of your old installation.


Handle go-md2man absent in add_help plugin

Improved unit test:

Use caplog so we get to see the log output from failed tests
For some reason flexmock won't replace check_output but will replace Popen so do that
Using unicode_literals just makes things worse, parametrizing breaks due to it

Coverage decreased (-0.5%) to 89.451% when pulling 48d454bc8d06e5b8e6af71ea658c15ab59155fc0 on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.5%) to 89.451% when pulling ee19b39388a3e0f97b1e46affb9faa9590e8b2c1 on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.5%) to 89.451% when pulling b148ef7f29c9afa35afc6d99a91bce05d2c9f6ae on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.02%) to 89.939% when pulling 224ad49800c12485561caad65c3f2a2d57bcc997 on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.02%) to 89.939% when pulling 224ad49800c12485561caad65c3f2a2d57bcc997 on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.02%) to 89.939% when pulling 725a62e30943ecba405ad08de5591970b72f914b on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.

Coverage decreased (-0.02%) to 89.939% when pulling 725a62e30943ecba405ad08de5591970b72f914b on handle-md2man-absent into cefca23bd10faf46249713d6fb144833b470a0a0 on master.


[FEAT] Update Customer Details API

Description
Create an API endpoint to update customer details. This endpoint will allow administrators to update customer information from the Customer Details Page efficiently and securely.

Acceptance Criteria

Endpoint Definition:

API endpoint to update customer details.

Functionality:

Admin can update customer details successfully.
Ensure only authorized users (admins) can update customer details.

Implementation Steps:

Define API Endpoint:

Define the API endpoint to update customer details.

Implement Logic:

Implement the logic to update customer information in the database.

Handle Responses:

Handle success and error responses, including invalid customer ID and unauthorized access.

Write Tests:

Write tests for the endpoint to ensure proper functionality.

Purpose
The purpose of this endpoint is to provide administrators with a secure and efficient way to update customer details. This will enhance the system's ability to maintain accurate and up-to-date customer information.

Requirements

[ ] The API should follow RESTful standards.
[ ] Ensure only authorized users (admins) can update customer details.
[ ] Implement validation for the provided data.
[ ] Handle both success and error responses appropriately.

Expected Outcome

Successful implementation of the update customer details endpoint.
Administrators can securely and efficiently update customer details.
The system returns appropriate success and error responses based on the request.
The endpoint is well-tested, ensuring reliability and correctness.

Example API Endpoint:

Endpoint: PUT /api/v1/customers/:customerId

Request Example:
{
  "firstName": "John",
  "lastName": "Doe",
  "email"<EMAIL_ADDRESS>  "phone": "+1234567890",
  "address": "123 Main St, Anytown, USA"
}

Successful Response Example:
{
  "status": "success",
  "status_code": 200,
  "message": "Customer details updated successfully.",
  "customer": {
    "id": "customerId",
    "firstName": "John",
    "lastName": "Doe",
    "email"<EMAIL_ADDRESS>    "phone": "+1234567890",
    "address": "123 Main St, Anytown, USA"
  }
}

Error Response Examples:

Invalid Customer ID:
{
  "status": "error",
  "message": "Invalid customer ID.",
  "status_code": 400
}

Unauthorized Access:
{
  "status": "error",
  "message": "Unauthorized access.",
  "status_code": 401
}

Unit Testing

[ ] Test that the customer details are updated successfully if a valid customer ID and valid data are provided.
[ ] Test that an error is thrown when an invalid customer ID is passed as a parameter.
[ ] Test that an error is thrown when a request is made without a valid token or by a non-admin user.

Slack ID: SCCSMARTCODE


Random events not being logged or causing 'Eligible In' timer to reset

Random events don't seem to be going into the log or resetting the 'Eligible In Overestimate' timer, it seems to have started with yesterday's Runelite update.  I still got a notification for the spawn ( Which I think was from this plugin) but no logging. Others in my CC had the issue as well.

Looking into this, the randoms I've received have been logged and the timer resets.
Was it a particular random or all? RL updated the way the Frog event is handled, I wonder what else has changed -- I'll take a look. Do you happen to have the "Hide Random Events" config turned on in the Entity Hider plugin?
FWIW the only notifications this plugin currently supports is for the Strange Plant, the other randoms are handled by the RL "Random Events" plugin.

Just had it happen with a sandwich lady.

It’s at least randoms that I’ve seen today. I’ve had Giles, Jekyll, Mysterious old Man, and Drunken Dwarf today and and none were logged or reset the timer. I don’t have randoms set to hidden in the entity hider, but I do use the random event hider plugin, set to hide everyone else’s random events while showing all of my own, with the options to mute and hide the poof

I found the issue, fixing shortly.

PR was merged, should be updated on the plugin hub shortly. You'll need to relaunch the game to receive the update. My apologies to you and your clan mates, good luck out there -- let me know if you find anything else.

Had a random spawn and it logged + reset the timer. Closing for now!


Update code in "wald_friedman" and "navy_captain"

Close #170
Update the code for solving Wald-Friedman problems to adopt jitclass and abandon "function_factory" style. The belief updating function κ is now made as a method of the jitclass since "f0" and "f1" pin down a belief updating rule.
The related code in the "Bayesian" section of the "navy_captain" lecture is also updated in the same way. Some unnecessary spacings in the blank lines are deleted in this commit.

This looks great @shizejin, thanks!!
Everything looks fine to me but, just to confirm, did you check that figures hadn't changed?

@jstac Yes I confirmed that all the figures in these two lectures remain unchanged in terms of patterns and the implied conclusions. There are small differences in the figures of simulation results as we are not controlling the seed and the sample size is small (500). For those plots without randomness, they remain exactly the same.

Thanks again for this @shizejin , it's really nice work.

@shizejin do you happen to know if this is compatible with numba=0.49 would be nice side benefit.


Test: mobile responsiveness poc

Added a simple public app and tested with multiple view ports

Closing this as it was for POC


audio key error in text to stream

>>> def text_stream():
...     yield "Hi there, I'm Eleven "
...     yield "I'm a text to speech API "
...
>>> audio_stream = generate(
...     text=text_stream(),
...     voice="Nicole",
...     model="eleven_monolingual_v1",
...     stream=True
... )
>>>
>>> stream(audio_stream)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/bbekdemir/Developer/sandbox/venv/lib/python3.11/site-packages/elevenlabs/utils.py", line 74, in stream
    for chunk in audio_stream:
  File "/Users/bbekdemir/Developer/sandbox/venv/lib/python3.11/site-packages/elevenlabs/api/tts.py", line 99, in generate_stream_input
    if data["audio"]:
       ~~~~^^^^^^^^^
KeyError: 'audio'

change   File "/Users/bbekdemir/Developer/bookie_pepper/venv/lib/python3.11/site-packages/elevenlabs/api/tts.py", line 99, in generate_stream_input
to
if data.get("audio")

How does that help - audio key does not exist.

Having the same problem

from elevenlabs import generate, stream, play

audio = generate(
    text="Hi! My name is Bella, nice to meet you!",
    voice="Bella",
    model='eleven_monolingual_v1',
    stream=True
)

# Stream the audio directly
stream(audio)

# Saving the audio for later
with open('output.mp3', 'wb') as f:
    for i,chunk in enumerate(audio):
        if chunk: f.write(chunk)

Please try this

I just tried in the tts.py file to print the data in order to see what it contained and I saw that I was getting a 401 error, because no api key was set.
So, i just update the imports with
from elevenlabs import generate, stream, set_api_key
and later in the script added
set_api_key("<myactualapikey>")
hope that helps
i believe it'd be good that the README is updated with that

i'd suggest to add before that something like print(data) to see the API's response in case it can give you a lead

@Mascobot It should work for you then. I just subscribed to a paid membership.
Can you please give the below a try and let me know if you face any issue.
#https://github.com/elevenlabs/elevenlabs-python/issues/136
from elevenlabs import generate, stream

def text_stream():
    yield "Hi there"
    yield "I am a text"

audio = generate(
    text=text_stream(),
    voice="Nicole",
    model='eleven_monolingual_v1',
    stream=True,
    api_key = "put api key here"
)

# Stream the audio directly
stream(audio)

getting this problem too and I don't want to have to change the library code.

@cdubiel Can you please provide the code and the error ? The below code snippet worked for me. Make sure you have paid subscription.

@Mascobot It should work for you then. I just subscribed to a paid membership.
Can you please give the below a try and let me know if you face any issue.
#https://github.com/elevenlabs/elevenlabs-python/issues/136
from elevenlabs import generate, stream

def text_stream():
    yield "Hi there"
    yield "I am a text"

audio = generate(
    text=text_stream(),
    voice="Nicole",
    model='eleven_monolingual_v1',
    stream=True,
    api_key = "put api key here"
)

# Stream the audio directly
stream(audio)

@kgovind0001: Even with the paid plan, this is the error:

stream(audio)
Traceback (most recent call last):
File "", line 1, in
File "/home/codespace/.local/lib/python3.10/site-packages/elevenlabs/utils.py", line 74, in stream
for chunk in audio_stream:
File "/home/codespace/.local/lib/python3.10/site-packages/elevenlabs/api/tts.py", line 85, in generate_stream_input
with connect(
File "/home/codespace/.local/lib/python3.10/site-packages/websockets/sync/client.py", line 266, in connect
sock = ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 513, in wrap_socket
return self.sslsocket_class._create(
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 1071, in _create
self.do_handshake()
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 1342, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)

@kgovind0001: Even with the paid plan, this is the error:

stream(audio)
Traceback (most recent call last):
File "", line 1, in
File "/home/codespace/.local/lib/python3.10/site-packages/elevenlabs/utils.py", line 74, in stream
for chunk in audio_stream:
File "/home/codespace/.local/lib/python3.10/site-packages/elevenlabs/api/tts.py", line 85, in generate_stream_input
with connect(
File "/home/codespace/.local/lib/python3.10/site-packages/websockets/sync/client.py", line 266, in connect
sock = ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 513, in wrap_socket
return self.sslsocket_class._create(
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 1071, in _create
self.do_handshake()
File "/usr/local/python/3.10.8/lib/python3.10/ssl.py", line 1342, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)

This error occurs when the SSL certificate of the server cannot be verified.
Maybe the API is having issues resolving SSL certificate.

I do get this error quite often now ~50% of the time.
Error: 'audio'
Traceback (most recent call last):
  File "C:\Users\Jorge\git\core-ai\controller\waifuai\conversation.py", line 328, in stream_conversation
    response = stream_completion.generate_completion(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Jorge\git\core-ai\controller\stream_completion.py", line 247, in generate_completion
    completed_audio_stream = stream(audio_stream)
                             ^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Jorge\git\core-ai\venv\Lib\site-packages\elevenlabs\utils.py", line 74, in stream
    for chunk in audio_stream:
  File "C:\Users\Jorge\git\core-ai\venv\Lib\site-packages\elevenlabs\api\tts.py", line 99, in generate_stream_input
    if data["audio"]:
       ~~~~^^^^^^^^^
KeyError: 'audio'

Running the test code fails for me as well.
from elevenlabs import generate, stream, set_api_key
def text_stream():
yield "Hi there"
yield "I am a text"
audio = generate(
text=text_stream(),
voice="Nicole",
model='eleven_monolingual_v1',
stream=True,
api_key = "put api key here"
)
Stream the audio directly
stream(audio)
(Output)
Traceback (most recent call last):
File "/Users/peterhanlon/code/test_audio.py/main.py", line 20, in
stream(audio)
File "/Users/peterhanlon/anaconda3/envs/test_audio.py/lib/python3.11/site-packages/elevenlabs/utils.py", line 74, in stream
for chunk in audio_stream:
File "/Users/peterhanlon/anaconda3/envs/test_audio.py/lib/python3.11/site-packages/elevenlabs/api/tts.py", line 122, in generate_stream_input
if data["audio"]:
~~~~^^^^^^^^^
KeyError: 'audio'

Same here, any updates?

I edited the elevenlabs\api\tts.py file at line 99:
if data["audio"]:

The elevenlabs package is assuming "audio" is present in every websocket message, which is not the case if you want to fix it in the meantime, just change that line to:
if data.get("audio"):

Since get() throws back a None rather than erroring out, this allows the script to continue or throw the actual exeption.

@RicardoEscobar your suggestion and changing to a paid plan worked for me! thx!

I also ran into this issue while using the streaming text-to-speech API.
Here's a description of the problem, and some ways around it.
The generate_stream_input function in the tts.py module of the ElevenLabs Python library assumes successful audio data responses from the text-to-speech API. This assumption is unsafe, as the API can respond with error messages under various conditions (e.g., missing API key, unended/timed-out input stream, account usage exceeded, etc.).
Proposed Solution:
Rather than assuming success or simply ignoring the error, the maintainers should modify the function to robustly handle error responses from the API. This includes checking for the presence of the 'audio' key and handling cases where it's absent.
Workarounds:

Debug the tts.py module to inspect actual API responses.
End text input streams with an empty string ('') to avoid timeouts.
Upgrade to a paid account or add Two-Factor Authentication to mitigate usage-related errors.

make sure you subscribed

thank you
On Thu, Mar 7, 2024 at 11:39 AM roperi @.***> wrote:

Debugging the tts file as @rosscado https://github.com/rosscado
suggested, I was able to see the root cause of the issue:
{'message': 'Unusual activity detected. Free Tier usage disabled. If you are using a proxy/VPN you might need to purchase a Paid Plan to not trigger our abuse detectors. Free Tier only works if users do not abuse it, for example by creating multiple free accounts. If we notice that many people try to abuse it, we will need to reconsider Free Tier altogether. \nPlease play fair and purchase any Paid Subscription to continue.', 'error': 'detected_unusual_activity', 'code': 1008}
Changing to a paid subscription solved it.
—
Reply to this email directly, view it on GitHub
https://github.com/elevenlabs/elevenlabs-python/issues/136#issuecomment-1984091389,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDLCWG7Z4P7OSCI2T5WARLYXCQ6JAVCNFSM6AAAAAA7E5EJMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA4TCMZYHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is fixed in the latest SDK (snippet). Please reopen if the issue still persists!


Mandysack patch

Closes #45, #48. #55
Removes compiler warning by substituting deprecated List references with LinkedLists.

Hi @mandysack can please do the following locally...
git checkout master
git pull
git cherry-pick 202ef0a
git cherry-pick 322f7e6
git checkout -b mandy-patch2

In essence I need you to create an entirely new branch and create a PR from there. For emphasis, look at the number of files changed in this PR versus the files you have actually changed.

@tjstavenger-pnnl can you review this PR?

Closing in favor of #57


Library website

Description 📜

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <issue_number_here>

Domain of Contribution 📊

[x] Web Development
[ ] App Development
[ ] Flutter Projects
[ ] Python Projects
[ ] C++ Projects
[ ] Clone Projects
[ ] HTML Projects
[ ] Javascript Projects
[ ] Machine Learning Projects
[ ] Others

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.

Screenshots / Gif (Optional) 📸

This is a Library website.


Yatin: Watch SK Trainings

Yatin requests the watch of the watch_keyword SK Trainings. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

SK Trainings has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by Mast in Charcoal HQ. Reason: 'Superseded'


feat: refactor hive extractor sql query refs

Summary of Changes
Refactor sql query references in hive extractor so it's easier to subclass this extractor and provide custom sql queries.
Tests
n/a
Documentation
n/a
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

curious on what's your custom logic to get the last updated timestamp?

so far we've only introduced custom logic to extract subset of whole metastore efficiently.


[PDI-19848] - JSON Input: Double datatype is chosen by default instead of Number when selecting a field with decimal values.

For more details please check: https://hv-eng.atlassian.net/browse/PDI-19848

:white_check_mark: Build finished in 9m 41s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/json/core

:ok_hand: All tests passed!
Tests run: 107, Failures: 0, Skipped: 5    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 9m 54s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/json/core

:ok_hand: All tests passed!
Tests run: 107, Failures: 0, Skipped: 5    Test Results

:information_source:  This is an automatic message


Remove -ti in docker and kubectl calls

Description
It avoids passing stdin to the container when useless.
Please note it removes a couple of issues highlighted by [1] in airgap specs.
It also removes all useless blank chars in the files modified by this change.
[1] https://github.com/cnti-testcatalog/testsuite/pull/1949
How has this been tested:

[X] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[X] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[X] Kind cluster

[ ] Have not tested

Types of changes:

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

@HashNuke would you mind running the specs in your branch. I ran a few specs locally but this change requires a full verification. Thank you in advance.

Build passing - https://github.com/cnti-testcatalog/testsuite/actions/runs/8769450532

Resolved conflict by commenting out airgap specs as in main branch.


Type guards in decorators not updating variable types

Bug Report
🔎 Search Terms
decorators, type guards
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about decorators

⏯ Playground Link
Playground link with relevant code
💻 Code
class LogPerson {
    @isNamePresent
    log(person: Person) {
        // person.name is guaranteed to be a string due to @isNamePresent decorator, yet error is still thrown
        thisNeedsPersonName(person.name)
    }
}

interface Person {
    name: string | undefined
}

function isNamePresent(target: any, propertyKey: string, descriptor: PropertyDescriptor) {
        const originalFunction = descriptor.value;
        descriptor.value = function () {
            const person = arguments[0];

            if (person.name === null || person.name === undefined)
                return console.log("Person doesn't have a name");

            return originalFunction.apply(this, arguments);
        }
}

function thisNeedsPersonName(name: string) {
    console.log(`name is ${name}`)
}

🙁 Actual behavior
TypeScript throws the error Type 'undefined' is not assignable to type 'string'. when person.name is used as a parameter to a method guarded by the @isNamePresent decorator
🙂 Expected behavior
TypeScript should see the decorator's type guard show the person.name field as only being a string, not string | undefined.
This could be too closely related to function calls not resetting narrowing, in which case, just close this issue. Though I do think it is different enough where it might be possible to be fixed.

Duplicate of #4881.
Last I read is that the TypeScript will first focus on decorator support (the current implementation is experimental and based on a deprecated proposal), and only then they'll consider looking at mutating types via decorators.

This doesn't look like #4881 - the intention doesn't seem to be to change the contract of the class.  This is more equivalent to calling throwIfPersonHasNoName(person) and expecting TypeScript to automatically know person.name can't be undefined afterwards.

So this is more equivalent to calling throwIfPersonHasNoName(person) and expecting TypeScript to automatically know person.name can't be undefined afterwards

Yea, exactly. The way I think it might be able to be done is by basically combining the @isNamePresent function with the method below the decorator / the method it is decorating (In my example that'd be log) and then using that to figure out if any types have been narrowed by the decorator.
Not sure if it's possible, but I think it'd be a really nice thing to have implemented if it is possible.


operator: support already known contracts

There are certain contracts and their implementations that we know
are supported always. So we make sure these are allowed without the
discovery from CRDs.
/assign @dgoodwin

/lgtm


hostapp-update-hooks: Don't fail if efivars fs already mounted

This prevents the following error and hup abort when sysfs is bind-mounted in the hostapp-update container:
mount: /sys/firmware/efi/efivars: efivarfs already mounted or mount point busy.
Needs to be tested along https://github.com/balena-os/meta-balena/pull/3194

Tested locally in QEMU, with the generic-x86-64-ext image:
[INFO] Deploying /mnt/boot/config.json...file blacklisted. Ignoring.
[INFO] Deploying /mnt/boot/balenaos.fingerprint... overwriting modified file... done.
[INFO] Running rollback hook
[INFO] Switching root partition to resin-rootB......
[INFO] Automated Rollback support in grub.cfg detected
[INFO] Switch root done.
1+0 records in
1+0 records out
446 bytes copied, 0.00596215 s, 74.8 kB/s
[INFO] Re-add EFI boot entry for starting resinOS from internal media.
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0008,0000,0001,0002,0003,0004,0005,0006,0007
Boot0000* UiApp
Boot0001* UEFI QEMU DVD-ROM QM00003
Boot0002* UEFI QEMU HARDDISK QM00001
Boot0003* UEFI PXEv4 (MAC:525400123456)
Boot0004* UEFI PXEv6 (MAC:525400123456)
Boot0005* UEFI HTTPv4 (MAC:525400123456)
Boot0006* UEFI HTTPv6 (MAC:525400123456)
Boot0007* EFI Internal Shell
Boot0008* resinOS
New/Forward hooks (new os container) ran successfully.
After hooks (old os) ran successfully

with qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -drive file=/dev/loop3,format=raw,index=0,media=disk -m 6G -nic user -smp 5
Qemu needs 6GB RAM, otherwise it gets killed during HUP. Machine booted fine after the update

Still fails in qemu tests when run with leviathan with:
efivar: show variable: No such file or directory efivar: show variable: No such file or directory 1+0 records in 1+0 records out 446 bytes copied, 0.000113108 s, 3.9 MB/s EFI variables are not supported on this system. EFI variables are not supported on this system.

Pushed some more debugging, might be that /sys/firmware/efi/efivars exists but is not mounted as efivarsfs

@balena-ci I self-certify!


Style and optimization

Pull Request
Commit One

FIxed Awkware title size

Commit Two

Changed the img objects to Next.JS Image objects
The site's main page was taking up to 30 seconds to compile on a codespace and as soon as I interchanged those, it got a lot faster.

Commit Three

Fix a weird folder name that would've caused issues moving on

I have a ton of homework recently and I'll get back to this on the weekend

Also, please put this in dev

I realized that I don't need to close it for you to change branches

@Blue-Robin-Taken @RedCat888
Look throught the PR

Please maintain a branch within the repo, instead of merging a fork. However I will eventually approve this after we get the preview link this one time. Your changes/code all look good however.


Rename |{Schema|Column}Writer| to |{Record|Value}Importer|.

@muga One of the last two PRs to get this library ready (expected).
Trying to rename SchemaWriter and ColumnWriter for a reason similar to the discussion about write of PageLoadable at https://github.com/dmikurube/embulk-base-restclient/issues/22#issuecomment-276545995.
What do you think?

LGTM 👍  I think much better

Merged. Thanks!


[EJBCA] endpoint "/ejbca" is unavailable

/ca and /sign are exposed endpoints, but /ejbca is not exposed.
In the EJBCA-REST API documentation -  this endpoint /ejbca appears, but is not accessible.
API documentation needs to be updated.
Using admin's credentials
curl -X GET "${DOJOT_HOST}/ejbca/version" -H "Authorization: Bearer ${JWT}" -H "Content-Type:application/json"

<title>404 Not Found</title>

404 Not Found

nginx/1.15.7

reference: https://dojot.github.io/ejbca-rest/apiary_latest.html

I'll explain better in the documents about exposing endpoints


run.add_picture() causes the word file to launch error when oppening

Hi to all,
I'm quite new in python language and I'm loving it, as well docx lib.
Well I am bulding some automated reports from SQL DB, and managing calulations and put them in tables in a word file, since the beggining the docx is attending me incredible well.
However in my final stage I whant to insert some charts, (i will use mplotlib to generate). So I tested to include some graphic chart;
    paragraph= tpl.add_paragraph()
    paragraph.style = tpl.styles['Heading 1']
    paragraph.text = "Grafico últimas 12horas"

    ###insert image with the operation chart
    paragraph= tpl.add_paragraph()
    #paragraph.style= ['Normal']
    r1 = paragraph.add_run()

    try:
        r1.add_picture(chartPath+"chart2.png",width=Cm(19.74))
    except:
        paragraph.text = "Não foi possivel gerar o gráfico"

Everithung goes well and the file is created, I can open it and the chart is in the righ place at the document.
However when I oppen the file WORD launches the following error message:

"We're sorry.We can't open [MY FILE_NAME].docx because we found some problems in its contains"

in the datails

"Unspecified error
Location part word/header1.xml column0 line0"

When I click Ok button a new window asks if I trust the source and if I whant to try to recover, I click yes and the file opens normally.
If I don't use add_picture this event does not occur so it is only when I add the Image.

Before I posted this issue I saw another issue about this,
But I was posted ther that the feature was fixed in a release, bacause it was an old post i assumed my version had that issue fixed so it could not be the same.
I tryed to understand that code And I have applied and it worked, this way I allways before save the document I call a function to fix it,