postgres production profile does not work

pgtest.zip
The sample app should use the new drivers.
package.json db kind is configured as "sql".
With production profile, postgres is not used and cds looks for the hana drivers.
Seems like something with the cds-plugin lookup does not work as expected.
Changing to "kind": "postgres" works.

this works with @sap/cds-dk @ 7.0.1


Upgrade aiohttp to 2.2.1

2.2.1

Relax yarl requirement to 0.11+
Backport #2026: session.close is a coroutine (#2029)

Tested with:
http:

I think we should move to 2.2.2


How  serialization   large  queryset?

I have  a  large  queryset.
Now   get a  gejson  is very slow.  Can  i  used  raw(sql)?  or  Do other  exist  variants?

I'm not sure there's an easy solution to this. You may need to use caching or split the data in smaller chunks.


Allow to see what's new in a version easily and in a way that looks good on pub.dartlang.org

It would be nice for pub.dartlang.org propose a way of easily seeing what's new in a package with respect to the previous version.
It could be made by including a "changelog" field in pubspec.yaml, that would contain the changelog itself or a link to a changelog file. It could also be done by having pub.dartlang.org computing a diff between two versions of the package on demand, like http://hdiff.luite.com/ for haskell. Or it could be both at the same time.
Relevant discussion: https://groups.google.com/a/dartlang.org/d/msg/misc/Ho6aLvB91y4/X6olegDEa8YJ

This issue has been moved to dart-lang/pub-dartlang#295.


[BUILD] warning fix: new does not have an alignment parameter

The below warning is shown with environment GCC 7.2 and -std=c++11
This PR will fix the below warnings tvm/vta/src/sim/sim_driver.cc: In constructor _vta::sim::DRAM::Page::Page(size_t, size_t)_: tvm/vta/src/sim/sim_driver.cc:196:33: warning: _new_ of type _vta::sim::DRAM::Page::DType {aka std::aligned_storage<4096, 256> 	::type}_ with extended alignment 256 [-Waligned-new=]                                    		   data = new DType[num_pages];                                                      									 ^                                                        tvm/vta/src/sim/sim_driver.cc:196:33: note: uses _void* operator new [](std::size_t)_, which does not have an alignment parameter     tvm/vta/src/sim/sim_driver.cc:196:33: note: use _-faligned-new_ to enable C++17 over-aligned new support tvm/vta/src/sim/sim_driver.cc: In instantiation of _vta::sim::SRAM<kBits, kLane, kMaxNumElem>::SRAM() [with int kBits = 8; int 	kLane = 256; int kMaxNumElem = 1024]_:                                                  tvm/vta/src/sim/sim_driver.cc:345:12:   required from here tvm/vta/src/sim/sim_driver.cc:226:13: warning: _new_ of type _vta::sim::SRAM<8, 256, 1024>::DType {aka std::aligned_storage<25 	6, 256>::type}_ with extended alignment 256 [-Waligned-new=]                             		 data_ = new DType[kMaxNumElem];                                                     				 ^~~~~~~~~~~~~~~~~~~~~~                                                      tvm/vta/src/sim/sim_driver.cc:226:13: note: uses _void* operator new [](std::size_t)_, which does not have an alignment parameter     tvm/vta/src/sim/sim_driver.cc:226:13: note: use _-faligned-new_ to enable C++17 over-aligned new support tvm/vta/src/sim/sim_driver.cc: In instantiation of _vta::sim::SRAM<kBits, kLane, kMaxNumElem>::SRAM() [with int kBits = 32; in 	t kLane = 16; int kMaxNumElem = 2048]_:                                                  tvm/vta/src/sim/sim_driver.cc:345:12:   required from here tvm/vta/src/sim/sim_driver.cc:226:13: warning: _new_ of type _vta::sim::SRAM<32, 16, 2048>::DType {aka std::aligned_storage<64 	, 64>::type}_ with extended alignment 64 [-Waligned-new=]                                  tvm/vta/src/sim/sim_driver.cc:226:13: note: uses _void* operator new [](std::size_t)_, which does not have an alignment parameter     tvm/vta/src/sim/sim_driver.cc:226:13: note: use _-faligned-new_ to enable C++17 over-aligned new support
This PR will avoid the issue
Reference: https://github.com/google/flatbuffers/pull/4621/files

please also check if the compiler itself is g++ as we can also use clang

Thanks @joyalbin ! This is now merged


Sync kcp "KUBECONFIG"s to workloads

Is your feature request related to a problem? Please describe.
Many "off the shelf" controllers and kubernetes client consumers assume that they receive a valid KUBECONFIG from the cluster's service account.
This is fine if the controller creates objects or updates status.
However, if the controller/client deletes objects, the state is not synced properly.
Rather than deleting the object on KCP, the syncer will attempt to re-reconcile the state of the "deleted" object.
Describe the solution you'd like
Provide a mechanism where a kubeconfig (or equivalent) can be injected into a workload that is tied to a corresponding KCP service account, and allow this mechanism to be used by standard k8s workloads (Deployment, CronJob, etc.)
Describe alternatives you've considered
Alternative - sync deletes from workload clusters to KCP.
Unclear if this is feasible or compatible with KCP's architecture.
Additional context
This issue was discovered when trying to configure the Tekton Operator's pruner on workload clusters whose Tekton PipelineRun objects are synced via KCP.
The pruner is not a single workload, but rather a set of CronJobs that are deployed to all namespaces on a cluster.
Admins can use namespace labels to tune the deployed CronJob - the operator configuration provides the defaults.
We would like to replicate the CronJob on KCP - but it appears for this to work the container that does the pruning needs to prune objects on KCP, not on the workload cluster.

Note, we already do this for deployments in the deployment mutator. We'll need something similar for the various other things that are pod-speccable.

@adambkaplan I don't believe it's documented, but the code is https://github.com/kcp-dev/kcp/blob/716d71056c8494b5583205936c94c1ec68828570/pkg/syncer/spec/mutators/deployment.go.
If you create a deployment in kcp, when it's synced to a real cluster, the deployment in the real cluster will have

Overridden environment variables

KUBERNETES_SERVICE_PORT points to kcp, not the real cluster
KUBERNETES_SERVICE_PORT_HTTPS points to kcp, not the real cluster
KUBERNETES_SERVICE_HOST points to kcp, not the real cluster

Overridden service account volume

/var/run/secrets/kubernetes.io/serviceaccount/token comes from a secret that kcp syncs down to the real cluster (from the ServiceAccount token secret in kcp)
/var/run/secrets/kubernetes.io/serviceaccount/namespace comes from a secret that kcp syncs down to the real cluster (from the ServiceAccount token secret in kcp)
/var/run/secrets/kubernetes.io/serviceaccount/ca.crt comes from a configmap kcp-root-ca.crt that kcp creates in the namespace in the real cluster

Any downward API environment variable references to metadata.namespace are converted to use the kcp namespace, not the real cluster namespace

Still not done yet:
#1198

/label appstudiokcp

@ncdc is there a notion that the mutator can be generalized to things that are "pod-speccable", or any custom resource?
Tekton TaskRuns come to mind here. If a TaskRun needs to create other Kubernetes resources (to say, deploy an application), it may need a KCP ServiceAccount.

@ncdc revisiting this item.
One need that Pipeline Service needs to do is regularly prune Tekton PipelineRun and TaskRun objects, re-implementing the Pruner feature of the Tekton Operator (see https://tekton.dev/vault/operator-main/tektonconfig/#pruner and https://docs.openshift.com/container-platform/4.11/cicd/pipelines/automatic-pruning-taskrun-pipelinerun.html). Without pruning, the service risks destabilizing physical clusters via etcd object exhaustion. Pruning also helps ensure we reap persistent volume claims. This is most effectively done by deploying a CronJob.


Added functionality to share image directly.

#1144
Implemented for both Android and iOS :)

Check the tests.

Updated 👍

Updated 👍

Looks good 👍


Remove default runner and update gssh runner build tag

Removes the default runner and updates the gssh runner's build condition.

Deletes the cmd/frpc/default_runner.go file, removing the default runner from the codebase.
Updates the build tags in cmd/frpc/gssh_runner.go from gssh to !nssh, allowing the gssh runner to compile in the absence of nssh.

For more details, open the Copilot Workspace session.

Remove default runner implementation and update build tags for gssh runner.

Removes the default_runner.go file, eliminating the default runner implementation.
Updates the build tag in gssh_runner.go from // +build gssh to // +build !nssh, aligning with the task to remove separate build tags for gssh.
Modifies the Makefile to remove the -tags gssh option from the gssh build command, reflecting the task's objective to simplify build tags handling.

For more details, open the Copilot Workspace session.


DELETE? BlockExp: Network Params incorrect format for network parameter

The network parameter entitled: governance.proposal.updateAsset.requiredMajority
Shows up in a currency format with 4 decimal places - whereas it should show as a percentage

Fixed at some point in the past


Test simulator submission

Instructions
Please use this issue to contribute a containerized simulation tool, contribute another version of a simulation tool, or update a version of a simulation tool. Specifically, edit the YAML syntax between the --- below and then click the Submit new issue button.
Instructions for containerizing simulation tools and examples are available at https://biosimulators.org/help.
Pre-submission checklist
Is your containerized simulation tool compliant with BioSimulators' conventions?

[ ] The container provides a BioSimulators-compliant command-line interface that supports the COMBINE/OMEX archive and SED-ML formats
[ ] The entrypoint of the container is set to this command-line interface
[ ] The specifications of the simulator follow the BioSimulators format
[ ] Optional, the source code for the simulation tool is publicly available
[ ] Optional, the simulation tool is available through a software repository such as CRAN or PyPI
[ ] Optional, examples, tutorials, and documentation for the simulation tool are publicly available
[ ] Optional, the simulation tool is registered with bio.tools
[ ] Optional, the container uses labels to provide BioContainers-compliant metadata
[ ] Optional, the container is registered with BioContainers

Submission
What is the name, version, and URL of the specifications of your simulation tool?
Please follow the template YAML syntax below.

name: COPASI
version: 4.27.214
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_COPASI/master/properties.json

Post-submission approval workflow
Once you submit this issue, BioSimulators will use the following workflow to validate, approve, and commit your simulator to the BioSimulators database:

An issue will be created with the label Submit simulator.
An automated action will review your submission:

Retrieve the specifications of your simulator.
Validate these specifications.
Validate the containerized simulator specified in your specifications.

If the validation fails, any errors will be posted to this issue. After fixing these issues, please edit the first block of this issue to re-initiate the automated validation.
If the validation succeeds, the Validated label will be added to the issue.
The BioSimulations Team will review your simulator.
If there are any concerns about your submission, the BioSimulations Team will use this issue to communicate with you about resolving them.
Once your simulator is approved, the BioSimulations Team will add the label Approved to this issue.
The simulator will automatically be committed to the BioSimulations database and the issue will automatically be closed.

Re-submission change list
If you need to revise your simulator to pass the validation, please use this section to briefly describe the changes that you made.

debugged biosimulations_utils
debugged again again again again again again agian again again again again again again

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! We will review your submission and discuss any issues here.

Your containerized simulator is valid!

The specifications of your simulator is valid!

A member of the BioSimulators team will review your submission before final committment to the registry.

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! We will review your submission and discuss any issues here.

The specifications of your simulator is valid!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! We will review your submission and discuss any issues here.

The specifications of your simulator is valid!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! We will review your submission and discuss any issues here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- No test cases are applicable to your container. Please use this issue to share appropriate test COMBINE/OMEX files with the BioSimulators Team.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   get_data_in_issue() missing 1 required positional argument: 'issue'

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324762616 is reviewing your submission. We will discuss any issues with your submission here.

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324764972 is reviewing your submission. We will discuss any issues with your submission here.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   No module named 'docker'

The specifications of your simulator is valid!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324767117 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- No test cases are applicable to your container. Please use this issue to share appropriate test COMBINE/OMEX files for the BioSimulators test suite. The BioSimulators Team will add these files to the test suite and then re-review your simulator.

Your submission was committed to the BioSimulators registry. Thank you!

Action 324774723 is committing your submission to the BioSimulators registry.

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324861380 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- No test cases are applicable to your container. Please use this issue to share appropriate test COMBINE/OMEX files for the BioSimulators test suite. The BioSimulators Team will add these files to the test suite and then re-review your simulator.

Action 324774723 is committing your submission to the BioSimulators registry.

Your submission was committed to the BioSimulators registry. Thank you!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324868228 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

Action 324892027 is committing your submission to the BioSimulators registry.

Your submission was committed to the BioSimulators registry. Thank you!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324892185 is reviewing your submission. We will discuss any issues with your submission here.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   'dict' object has no attribute 'name'

Action 324893404 is committing your submission to the BioSimulators registry.

Your submission was committed to the BioSimulators registry. Thank you!

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324901917 is reviewing your submission. We will discuss any issues with your submission here.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   'dict' object has no attribute 'name'

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324906248 is reviewing your submission. We will discuss any issues with your submission here.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   'Submit simulator' is not a valid IssueLabel

resettted

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324913611 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- Sorry. We encountered an unexpected error. Our team will review the error.
-
-   here

reset

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324917342 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- No test cases are applicable to your container. Please use this issue to share appropriate test COMBINE/OMEX files for the BioSimulators test suite. The BioSimulators Team will add these files to the test suite and then re-review your simulator.

rest

Thank you @jonrkarr for your submission to the BioSimulators registry of containerized simulation tools! Action 324923405 is reviewing your submission. We will discuss any issues with your submission here.

The specifications of your simulator is valid!

Your container passed 0 test cases.

- No test cases are applicable to your container. Please use this issue to share appropriate test COMBINE/OMEX files for the BioSimulators test suite. The BioSimulators Team will add these files to the test suite and then re-review your simulator.


Add custom class names to input

Hi,
It could be great to customize the input style with custom class :)

Custom classNames is a solid addition!
One nit: Maybe add react and react-dom as peer dependencies? I believe that's the norm, it's friendlier for importing into existing projects.

@MilllerTime seems like a good idea, I'll do the changes and push them over the weekend.


fix: mobile touch on focusable elements jumps element to first position

Fix:

check if focus event triggered by touch
don't jump the slide element

The problem has been discussed several times and a solution has already been implemented for desktop click events.
On mobile devices with touch gestures, however, the error is still present. If a UI element like select field or button is clicked in a slide element, the slide jumps to the first position.
Exactly as it is desired for the focus events. (if you navigate with tabulator key through the slider).
--> The problem was, with a touch event, the focus event is always triggered. For this I have now implemented a query.
Similar problems:

#5962
#5878
#5814
#5513
#5625

Always follow the contribution guidelines when submitting a pull request.

Merged, thanks!


Refactor classes and update comments

Timetable class has been refactored into a DateUtil class.

Shift, Date, Time and Capacity classes have been moved from seedu.ptman.model.outlet to seedu.ptman.model.shift.

Comments and annotations updated.

Pull Request Test Coverage Report for Build 330

13 of 14 (92.86%) changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 91.712%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/ptman/commons/util/DateUtil.java
10
11
90.91%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/ptman/model/outlet/OutletInformation.java
1
97.33%

Totals

Change from base Build 329:
0.02%

Covered Lines:
3021

Relevant Lines:
3294

💛  - Coveralls


How to use it?

I just started with Sketch plugin development and wanted to use TypeScript instead of directly using JavaScript. I therefore used this template. But I don't understand how to use it - where can I find the types that are available in this TypeScript template? For example I would expect something like SketchDocument as interface or class. There is MSDocument, but this contains only showMessage.
Could you give some starting support? Thanks and thanks for this TypeScript plugin :-)
Hint: I am using Visual Studio Code. Would be interested in auto-completion etc.

Hi @wondering639! Unfortunately there are no typings provided by this template. It only scaffolds initial build environment so you can use TS to write Sketch plugins. To use this template successfully you will have to add required typings manually into sketch.d.ts file.
I tried to implement automated definition generation previously here https://github.com/romansp/sketch-headers-typescript based on the work from this repo https://github.com/skpm/sketch-headers/issues. I don't work on that anymore, but i guess it's still doable.

@romansp Sad to hear that, but thanks for the clarification :-) Guess for my beginner project I will stay with pure JavaScript, doing all the TypeScript stuff manually is currently too much for me.


Make compatible with Node.js require()

TL;DR: Use UMD to let users still use GuavaJS as a global in the browser context, but also enable CommonJS (i.e. Node.js) and AMD style requires.
This pull request does the following:

Add build step that combines all of GuavaJS, via grunt-contrib-concat
Add build step that wraps GuavaJS with a UMD wrapper, via grunt-umd
Set UMD output as the Node.js entry point

So if this package gets published to npm (#12), these changes will make it possible to:
npm install guava-js

or
yarn add guava-js

then
var GuavaJS = require("guava-js");
var Splitter = GuavaJS.Strings.Splitter; // example
var dashSplitter = Splitter.on('-'); // example

Any reason why you've included the build outputed files?

Consistency with the repo having all build outputs checked-in.
A follow-up issue could be created for removing all the build outputs from the repo.

(Happy to contribute a follow-up PR to remove the build outputs!)


[FEATURE] Examples of ML Remote Models

Is your feature request related to a problem?
At the moment we have blueprints for Remote ML model connectors. This allows users to know in a straightforward way how to create connectors. We don't however have samples of how to create models that utilize those connectors at least that I could find.
The two examples out there are dramatically different and may leave developers confused on how to deploy a model for their remote connector.
https://github.com/opensearch-project/ml-commons/blob/f5c20fb31bf80c0cd048b8bceee72ada355f2920/docs/tutorials/remote_inference.md?plain=1#L244C1-L244C31
https://github.com/opensearch-project/documentation-website/blob/b024b6ccc2e81abab6d07771bd145f71c1ada3c3/_ml-commons-plugin/extensibility/connectors.md?plain=1#L80
What solution would you like?
We should either have a guide or a set of blueprints ready for new developers to utilize to connect to some of the most common models. I feel like we should consider breaking docs/remote_inference_blueprints into a structure more like the following:
remote_inference_blueprints
├── open_ai
│   ├── connector_blueprint.md
│   ├── gpt-3.5-model.md
│   └── gpt-4-model.md
├── cohere
└── ...

What alternatives have you considered?
With excluding these we will cripple the adoption of our ML Framework.
Do you have any additional context?
n/a

Turns out this was just due to the documentation page referencing the local connector creation settings where it should have a different sample. Getting closed with https://github.com/opensearch-project/documentation-website/pull/5017

@dtaivpp can we close this issue now?

Feel free


Improve Informational Email templates to include missing information

The templates we are using for the Informational meetings are obsolete now.
There's also information missing, like:

Please remember that you'll need to provide the meeting requirements documents as explained in this link:

And then no link was provided in the email.

We decided GH issue is no longer needed for Informational meeting

This will be included with issue https://github.com/Azure/azure-sdk-tools/issues/3788


Didx 305 optimize cicd

@wdbasson I'm cleaning up some old PRs. Is this still work in progress, or safe to close?


fix: revert "feat: Add resource option configuration (#47)"

Which problem is this PR solving?
This implementation of adding resource attributes with code clobbers resource attributes set from environment variables which is against spec.
Short description of the changes
This reverts commit 6365f2db2824c5a112dfdad5f9a215a0b83790ff.

With this revert, we're at a No Bump because it undoes the additional behavior currently in main.
For further efforts to get WithResources implemented see #48


AZ-204_lab_01.md

English:
blobs
Current Translation:
blob
Suggested Translation:
Blob
Description:
Inconsistent translation. Global check

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run bugfix tool and waiting for result ICMS QUERY


Feat/119 slicing advantage score

Resolves #119.
@blauertee sorry I renamed the branch which automatically closed the pull request you had created :\

@marisanest I pushed the notebook which uses the new analysis class into the repo but you can also access it here: https://colab.research.google.com/drive/11kCsn36bjHYzVutthEjyHsvho5zJBqOX?usp=sharing
it uses the pytorch model.
The other notebook which uses tf privacy works with the tf model and you can access it here:
https://colab.research.google.com/drive/1hC1lDMBjthhJhXiuqXcnvYqHfk6qpdkG?usp=sharing
I wanted to share the kaggle notebooks but they require e-mails so I copied them over to Colab.

I will try to add some tests, thanks for the detailed review :)

Ok sure. I will merge this PR for now, because I need the changes in order to update the notebooks. If you or someone else want to change or add something, we can open a new PR :)


Max Besties Exceeded Error While Adding Followers to Close Friends List

Max besties exceeded Error While Adding Followers to Close Friends List
Description
While adding followers to the close friends list, I encountered a 400 Bad Request error with the message "max besties exceeded" after adding 9,999 followers. There were no issues during the process of adding followers in batches up to this point, but once the close friends list reached 9,999 users, the error consistently appeared. The error occurred after attempting to add more followers using the setBesties endpoint.
The error encountered:
Retry failed: IgResponseError: POST /api/v1/friendships/set_besties/ - 400 Bad Request; max besties exceeded
    at Request.handleResponseError (C:\Users\hamza\Desktop\instagram-close-friends-automation-ts\node_modules\instagram-private-api\src\core\request.ts:172:12)
    at Request.send (C:\Users\hamza\Desktop\instagram-close-friends-automation-ts\node_modules\instagram-private-api\src\core\request.ts:83:24)
    at async FriendshipRepository.setBesties (C:\Users\hamza\Desktop\instagram-close-friends-automation-ts\node_modules\instagram-private-api\src\repositories\friendship.repository.ts:76:22)

Relevant code section:
await ig.friendship.setBesties({ add: batch, remove: [] });

// Function to add followers to the close friends list
async function addToCloseFriends(ig: IgApiClient, followerIds: string[], batchSize: number, requestDelay: number, batchDelay: number) {
    let totalAdded = 0;
    console.log(`Adding ${followerIds.length} followers to close friends list...`);
    for (let i = 0; i < followerIds.length; i += batchSize) {
        const batch = followerIds.slice(i, i + batchSize);
        try {
            await ig.friendship.setBesties({ add: batch, remove: [] });
            totalAdded += batch.length;
            console.log(`Added batch ${Math.floor(i / batchSize) + 1} to close friends. Total added: ${totalAdded}`);
            await new Promise(resolve => setTimeout(resolve, requestDelay))
        } catch (error) {
            if (error instanceof IgNotFoundError) {
                console.error('An API endpoint was not found:', error.message);
            } else {
                console.error('An error occurred while adding to close friends:', error);
            }
            break;
        }

        await new Promise(resolve => setTimeout(resolve, batchDelay));
    }
    console.log('All followers have been added to the close friends list.');

Key Details

No issues occurred while adding followers up to 9,999.
The error consistently appears when attempting to exceed the 9,999 follower limit.

any updates on this? im also limited

i think we should sniff traffic on mobile app (when in close friends section) to learn the new endpoint and request.

i know there are people who can add more than 1m followers to close friends.
you can't add more than 10k close friends when mimicking a desktop device using this endpoint: https://i.instagram.com/api/v1/friendships/set_besties/

you're getting this error: max besties exceeded , right

i think we should sniff traffic on mobile app (when in close friends section) to learn the new endpoint and request.

Yes I'm getting the problem Ater 9999 followers, I also know people who added around 50k+ followers to the close friends list.
And I saw on one forum, someone was saying that on desktop, the close friends list starts glitching after 9999 followers so you can't add more.
So Sniffing traffic on the mobile app sounds like a good idea to explore any different endpoints or requests.

I am able to do without problems. You are using old API, that has limit.

I am able to do without problems. You are using old API, that has limit.

Could you share how you managed to do it without any issues? Which API did you use ?

It is hidden API. Can't share
jumpshare. com/s/Ltn8lXtMoIX0daNrmVAC


local-npm not starting

Hi Orlando,
thanks for the image, it had been working great till recently. We've been getting the following error:
TypeError: requestsById[request.id].push is not a function     at /local-npm/node_modules/pouchdb/lib/index.js:247:32
In case you find the time to fix it, could you please tag a working version?
Best,
Michael

Hi @MichaelRuhwedel! This seems to be an issue with local-npm itself and is tracked in   https://github.com/nolanlawson/local-npm/issues/131


Refactoring

Description:
(copying @lobracost 's comments)
training.py:
After two bad (increasing loss), or neutral (non changing loss) epochs the training is finished. This choice might get you stucked at local minimas. A greater tolerance, for example a tolerance of 10 epoch,. would be better.
I suggest to use a learning rate scheduler (e.g. torch.optim.lr_scheduler.ReduceLROnPlateau) in order to optimize your training process.
test.py:
It would be useful if we had the ability to test a set of input data and not just a single file, so we could get some statistics.
I recommend to struct the code in a package form with init files. In this way there is no need to mess with the python path variable.

The pkl directory, where the checkpoints are stored, is missing leading to post-training errors. We have to create this directory and commit the changes.
Also in the context of this refactoring, the unused imports and the commented code lines can be removed.

The pkl directory, where the checkpoints are stored, is missing leading to post-training errors. We have to create this directory and commit the changes.
Also in the context of this refactoring, the unused imports and the commented code lines can be removed.

I've already done some unused imports removal and the pkl folder creation in task #8 (just pushed).

@tyiannak @lobracost
We can create a python package as suggested above and do all the checks (folders etc) in the __init__() or in the setup.py.
Also, we can rename some files, for example: basic_training.py and basic_test.py to training.py and test.py respectively .
We can add some documentation / wiki pages, if the project is meant to be formal.
Finally I would suggest changing names of some variables, in order the code to be as formal as possible.

@lobracost
I've started refactoring the code in this branch https://github.com/tyiannak/deep_audio_features/tree/Refactoring-%239, mainly focusing on

reorganising submodules to folders so that imports can be made easier (so that the setup_paths.sh is not needed)
adding a setup file so that we can add the lib to pip
Can you please check that basic functionality is still ok both in command line scripts and through python calls?

You can also check with the current version of the pip binary (pip3 install deep-audio-features -U) which is based on this branch

@tyiannak of course. I will let you know of the resulted behavior.

I've checked most of the functionality and it works (both with relative imports from the source code and using the pip install way), e.g.
from deep_audio_features.bin import basic_training as bt
bt.train_model(["/Users/tyiannak/Research/libraries/deep_audio_features/4class_small/music_small", "/Users/tyiannak/Research/libraries/deep_audio_features/4class_small/speech_small/"], "test")
...
from deep_audio_features.bin import basic_test as b
d, p = b.test_model("/Users/tyiannak/pkl/test.pt", "/Users/tyiannak/Research/libraries/deep_audio_features/r.wav", layers_dropped=0, test_segmentation=False)
but have not checked the combine functionalities at all (they certainly require changes)

@lobracost I've added everything (I think) in the main Readme
You can test with both command line (using the source code)
and in Python (using the latest pip version - aka 1.7)  - please test using both.
Also please add anything that you feel is missing from Readme wrt compare and then delete the compare/Readme file
When u push these changes if any let me know to merge

@tyiannak I want your opinion.
The combine.py script works as follows:
In order to extract nn features, it takes the output of the first convolutional layer (this choice is based on experimentation). These features are of shape (32, 64, 100). At the time the script functions as follows:

Squeezes the features to a 204800D vector.
Applies dimensionality reduction in order to produce a 100D vector

In my opinion, this is not efficient and has both performance issues and errors associated with memory handling (an array of size num_of_instances x 204800 has to be stored).
Do you have any better ideas in mind?
I propose simple averaging on axis 1 and 0 subsequently in order to get a 100d vector.

Two solutions a. Use a random projection to map to 100 features or b. Use features from the linear layers

I think b makes more sense

Or maybe some of the last convolutional mappings that will be lower in dimension

I will experiment with both a and b and commit the changes for the best performing solution

@tyiannak I experimented with both choices and concluded that the most effective way to extract features from this specific architecture is by taking the output of the fourth convolutional layer and applying dimensionality reduction. I committed my changes along with a minor update on the readme file.
All functionalities of the library work as expected for me, in both command line and python calls and thus I approve merging.


Schema not applied correctly in library when using library.with_data_values().

What steps did you take and what happened:
Run:
#!/bin/sh

set -x

mkdir -p resources-1/_ytt_lib/mylib

cat > resources-1/_ytt_lib/mylib/00-schema.yaml << EOF
#@data/values-schema
---
apiVersion: ""
kind: ""
#@schema/type any=True
metadata:
  name: ""
  uid: ""
#@schema/type any=True
spec: null
#@schema/type any=True
status: null
EOF

cat > resources-1/_ytt_lib/mylib/99-output.yaml << EOF
#@ load("@ytt:data", "data")
--- #@ data.values
EOF

cat > resources-1/99-output.yaml << EOF
#@ load("@ytt:data", "data")
#@ load("@ytt:struct", "struct")
#@ load("@ytt:library", "library")
#@ load("@ytt:template", "template")

#@ mylib = library.get("mylib")
#@ mylib_with_values = mylib.with_data_values(struct.decode(data.values))

--- #@ template.replace(mylib_with_values.eval())
EOF

cat > values-1.yaml << EOF
apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2021-10-13T05:54:35Z"
  labels:
    kubernetes.io/metadata.name: default
  name: default
  resourceVersion: "201"
  uid: 591eeb77-5c81-49de-8698-28ac704d0467
spec:
  finalizers:
  - kubernetes
status:
  phase: Active
EOF

ytt -f resources-1 --data-values-file values-1.yaml

This results in the error:
ytt: Error:
- library.eval: Evaluating library 'mylib': Overlaying data values (in following order: additional data values): Document on line ?: Map item (key 'metadata') on line ?: Map item (key 'creationTimestamp') on line ?: Expected number of matched nodes to be 1, but was 0
    in <toplevel>
      99-output.yaml:9 | --- #@ template.replace(mylib_with_values.eval())

With the files created from the test, if you were instead to run:
ytt -f resources-1/_ytt_lib/mylib --data-values-file values-1.yaml

In other words, directly process the files which are in the library, it works fine and produces:
apiVersion: v1
kind: Namespace
metadata:
  name: default
  uid: 591eeb77-5c81-49de-8698-28ac704d0467
  creationTimestamp: "2021-10-13T05:54:35Z"
  labels:
    kubernetes.io/metadata.name: default
  resourceVersion: "201"
spec:
  finalizers:
  - kubernetes
status:
  phase: Active

Note that there is no #@data/values file in the library.
Now run a second test where the only difference is that we add a #@data/values file to the library, but where it is only marked as such and has no actual values set:
#!/bin/sh

set -x

mkdir -p resources-2/_ytt_lib/mylib

cat > resources-2/_ytt_lib/mylib/00-schema.yaml << EOF
#@data/values-schema
---
apiVersion: ""
kind: ""
#@schema/type any=True
metadata:
  name: ""
  uid: ""
#@schema/type any=True
spec: null
#@schema/type any=True
status: null
EOF

cat > resources-2/_ytt_lib/mylib/00-values.yaml << EOF
#@data/values
---
EOF

cat > resources-2/_ytt_lib/mylib/99-output.yaml << EOF
#@ load("@ytt:data", "data")
--- #@ data.values
EOF

cat > resources-2/99-output.yaml << EOF
#@ load("@ytt:data", "data")
#@ load("@ytt:struct", "struct")
#@ load("@ytt:library", "library")
#@ load("@ytt:template", "template")

#@ mylib = library.get("mylib")
#@ mylib_with_values = mylib.with_data_values(struct.decode(data.values))

--- #@ template.replace(mylib_with_values.eval())
EOF

cat > values-2.yaml << EOF
apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2021-10-13T05:54:35Z"
  labels:
    kubernetes.io/metadata.name: default
  name: default
  resourceVersion: "201"
  uid: 591eeb77-5c81-49de-8698-28ac704d0467
spec:
  finalizers:
  - kubernetes
status:
  phase: Active
EOF

ytt -f resources-2 --data-values-file values-2.yaml

This time the test works and we get same output as when had processed the files in the library directly.
So in order for library.with_data_values() to work, you need to have a #@data/values file present.
Be warned though, that the data values file cannot actually have any values set in it, or you get an error again as seen with test:
#!/bin/sh

set -x

mkdir -p resources-3/_ytt_lib/mylib

cat > resources-3/_ytt_lib/mylib/00-schema.yaml << EOF
#@data/values-schema
---
apiVersion: ""
kind: ""
#@schema/type any=True
metadata:
  name: ""
  uid: ""
#@schema/type any=True
spec: null
#@schema/type any=True
status: null
EOF

cat > resources-3/_ytt_lib/mylib/00-values.yaml << EOF
#@data/values
---
metadata:
  name: "xxx"
EOF

cat > resources-3/_ytt_lib/mylib/99-output.yaml << EOF
#@ load("@ytt:data", "data")
--- #@ data.values
EOF

cat > resources-3/99-output.yaml << EOF
#@ load("@ytt:data", "data")
#@ load("@ytt:struct", "struct")
#@ load("@ytt:library", "library")
#@ load("@ytt:template", "template")

#@ mylib = library.get("mylib")
#@ mylib_with_values = mylib.with_data_values(struct.decode(data.values))

--- #@ template.replace(mylib_with_values.eval())
EOF

cat > values-3.yaml << EOF
apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2021-10-13T05:54:35Z"
  labels:
    kubernetes.io/metadata.name: default
  name: default
  resourceVersion: "201"
  uid: 591eeb77-5c81-49de-8698-28ac704d0467
spec:
  finalizers:
  - kubernetes
status:
  phase: Active
EOF

ytt -f resources-3 --data-values-file values-3.yaml

Which again generates the error:
ytt: Error:
- library.eval: Evaluating library 'mylib': Overlaying data values (in following order: _ytt_lib/mylib/00-values.yaml, additional data values): Document on line ?: Map item (key 'metadata') on line ?: Map item (key 'creationTimestamp') on line ?: Expected number of matched nodes to be 1, but was 0
    in <toplevel>
      99-output.yaml:9 | --- #@ template.replace(mylib_with_values.eval())

What did you expect:
Expect the following:

It should not be required to have an empty #@data/values annotated file to get it to work.
Where the #@data/values file sets values it should not error and the values passed to library.with_data_values() should me merged just like if --data-values-file was used on the command line and it was overriding a data values file included with a set of YAML files where a library wasn't involved.

Environment:
% ytt version
ytt version 0.38.0

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

@GrahamDumpleton noted:

It should not be required to have an empty #@data/values annotated file to get it to work.

Absolutely.

Where the #@data/values file sets values it should not error and the values passed to library.with_data_values() should me merged just like if --data-values-file was used on the command line and it was overriding a data values file included with a set of YAML files where a library wasn't involved.

Yes: you case would be solved with #418.
This won't be possible to do this with @ytt:library.with_data_values(), as is.
That function accepts overlays as input, today; and it would be a breaking change for it to behave otherwise.

In the meantime, you've detailed a workaround (🙏🏻 ).
@gcheadle-vmware noted a interesting variants that works for cases where you don't have authorship of the library and you're okay with leaking the name of the internal library:
$ ytt -f resources-1 --data-values-file @mylib:values-1.yaml

ref: https://carvel.dev/ytt/docs/latest/ytt-data-values/#configuring-data-values-via-command-line-flags

We have (yet another) very compelling use-case for implementing #418 — this is, in effect, a request for that feature.
Within this flow, there is a bug — and I've pulled that aside in this issue: #566.
@GrahamDumpleton, I believe you've got a workaround (or two), and we've got a more systemic solution.
Is there anything beyond those two items you think we can do here to help?

So what I understand is that you are saying my workaround to make it work is actually the bug and when that bug is fixed I will not be able to do what I want unless you separately implement #418.

Yes. And that we'll ensure that we don't fix the bug until we provide the systemic solution. 👍🏻
And that we'll be doing both ASAP.

#418 was delivered as part of v0.39.0.


chore(deps): Update yaml dependency to get fix for CVE-2023-2251

Should resolve https://github.com/appsmithorg/appsmith/security/dependabot/224.

/ok-to-test

/ok-to-test


added awattar adapter

https://github.com/iobroker-community-adapters/ioBroker.discovergy/issues/45

RE-CHECK!

RE-CHECK!

hmmm... recheck was denn? fehlt was?

AN sich stösst das nen automatischen adaptercheck an ... hm .. :-)

did manually (https://adapter-check.iobroker.in/):

[E503] "iob_npm.done" found in repo! Please add it to .gitignore
[E818] file iob_npm.done found in repository, but not found in .npmignore
[E914] file iob_npm.done found in repository, but not found in .gitignore

Please check and fix first

did manually (https://adapter-check.iobroker.in/):

[E503] "iob_npm.done" found in repo! Please add it to .gitignore
[E818] file iob_npm.done found in repository, but not found in .npmignore
[E914] file iob_npm.done found in repository, but not found in .gitignore

Please check and fix first

hab das file gelöscht, zu git und npm ignore hinzugefügt, ein neues build / release gemacht, die neue version hier eintragen und den PR aktualisiert. passt das so?

did manually (https://adapter-check.iobroker.in/):

[E503] "iob_npm.done" found in repo! Please add it to .gitignore
[E818] file iob_npm.done found in repository, but not found in .npmignore
[E914] file iob_npm.done found in repository, but not found in .gitignore

Please check and fix first

hab das jetzt vor 3 tagen gefixt. Fehlt noch was?

RE-CHECK!

Automated adapter checker
ioBroker.awattar

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "awattar" in latest repository

Add comment "RE-CHECK!" to start check anew

did manually (https://adapter-check.iobroker.in/):

[E503] "iob_npm.done" found in repo! Please add it to .gitignore
[E818] file iob_npm.done found in repository, but not found in .npmignore
[E914] file iob_npm.done found in repository, but not found in .gitignore

Please check and fix first

Wieso geht bei diesem PR nix weiter? Wenn noch was fehlen sollte, ich checks nicht. Irgendwie keine Kommunikation... :-(

i need to find time for review

Hi,
some review comments:

please add all translations to io.package. Use the iobroker translation tool
stateChange is not needed (https://github.com/sirjojo69/ioBroker.awattar/blob/master/main.js#L49)
how many states the adapter is setting? seems like many. Please use async/await to make that sequencial, because else these many of parallel requests can have bad impacts on user systems ... then also the "stop faillback" is not needed https://github.com/sirjojo69/ioBroker.awattar/blob/master/main.js#L339

@sirjojo69 Any update?

hi @Apollon77 .. i´m struggeling with your recommended refactoring regarding async/await, since this is my first adapter and i´m not that frondend guy. so that will take its time. meanwhile it is used directly out of the git repo...

@sirjojo69 If you need support or just a place to unload frustration  (;-) ) we have developer groups in Discord and Telegram and also in the Forum ...

@sirjojo69 anything where we can support?

I´m still struggeling with your recommended code change to make use of „async / await“.
Perhaps you can point me to an adapter using async/await technique, so i can learn from there….
Von: Ingo Fischer @.>
Gesendet: Donnerstag, 8. April 2021 07:35
An: ioBroker/ioBroker.repositories @.>
Cc: sirjojo69 @.>; Mention @.>
Betreff: Re: [ioBroker/ioBroker.repositories] added awattar adapter (#986)
@sirjojo69 https://github.com/sirjojo69  anything where we can support?
—
You are receiving this because you were mentioned.
Reply to this email directly,  https://github.com/ioBroker/ioBroker.repositories/pull/986#issuecomment-815460991 view it on GitHub, or  https://github.com/notifications/unsubscribe-auth/AM7L7KICQWC4EIWL4DGELWLTHU6B5ANCNFSM4TV2ZR4A unsubscribe.  https://github.com/notifications/beacon/AM7L7KOUSJRDTZIDHU4Y4SLTHU6B5A5CNFSM4TV2ZR4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGCNPE7Y.gif

Hilft das als Startpunkt?
https://gist.github.com/AlCalzone/d14b854b69ce5e8a03718336cc650a95#

@sirjojo69 The async/await logic is quite simple.
You main function is already marked as an async function. That's good!
Now you should change all adapter.setState(...) and adapter.setObjectNotExists(...) calls simply to await adapter.setStateAsync(...) and await adapter.setObjectNotExistsAsync(...).
Example:
adapter.setObjectNotExists("Rawdata", { ...

should become
await adapter.setObjectNotExistsAsync("Rawdata", { ...

Each adapter.*Async method returns a promise, which will be resolved if the asynchronous operation is done.
At each await you code will wait (without blocking other code parts) until the promise of the adapter.*Async method is resolved.
Dosing so, you can guarantee that the objects and states are set up in the right order.
An example for the async/await logic you may find here in my ioBroker.canbus adapter: https://github.com/crycode-de/ioBroker.canbus/blob/98577788574c0a5e87bb62286d586e0d5e9d8249/build/main.js#L561

thanks for this. with this helpful hints there should be no further obstacles to implement that... i will go for it at the weekend...

@sirjojo69 The async/await logic is quite simple.
You main function is already marked as an async function. That's good!
Now you should change all adapter.setState(...) and adapter.setObjectNotExists(...) calls simply to await adapter.setStateAsync(...) and await adapter.setObjectNotExistsAsync(...).
Example:
adapter.setObjectNotExists("Rawdata", { ...

should become
await adapter.setObjectNotExistsAsync("Rawdata", { ...

Each adapter.*Async method returns a promise, which will be resolved if the asynchronous operation is done.
At each await you code will wait (without blocking other code parts) until the promise of the adapter.*Async method is resolved.
Dosing so, you can guarantee that the objects and states are set up in the right order.
An example for the async/await logic you may find here in my ioBroker.canbus adapter: https://github.com/crycode-de/ioBroker.canbus/blob/98577788574c0a5e87bb62286d586e0d5e9d8249/build/main.js#L561

sadly it seems to be not that easy.
when i replace adapter.setObjectNotExists with recommended await adapter.setObjectNotExistsAsync
the whole adapter drashes in my test instance...

I expect that you also need to declare the "surrounding function" where the "await" is done as "async"

thats already implemented... must be something else...

Then try stopping adapter in admin and go to cli and execute "iobroker debug awattar" ... maybe that brings better error output

hmmmm.. that brings up the man page of command iobroker. seems that there is no command iobroker debug [adapter]. it seems that the iobroker command is different between a win and debian installation. my dev system is a win10 vm. i will setup a new proxmox vm to have a debian based test installation and give it a try....

ok... i setup a debian based dev vm...
i stopped the adapter in admin and executed "iobroker debug awattar". that bings up the following error:

and this is strange, since the the surrounding function for line 120 is "main" and this function is declared as async...

The code here is running in the callbackj function on request ... which is not async :-)
see Line 112

The callback function of you request in line 112 is not an async function, like Apollon77 already mentioned.
You may change this line to
request(options, async (error, resonse, body) => {

Note the async keyword ;-)

ok... i changed that accordingly. sadly the error remains the same... did i miss another point?

Probably an other position, where you are using await inside a callback function.
Each function with an await inside have to be declared as async.

perhaps you can have a second look at the repo. i did not push the recent version (since it does not work) but the only things i changed were your suggestions. so the structure remained untouched. Do you see any other callback functions?

perhaps i should not use request at all...?
https://stackoverflow.com/questions/45778474/proper-request-with-async-await-in-node-js

request is deprecated for a while now.
I would suggest to use axios instead.
Example for axios:
const axios = require('axios');

const api = axios.create({
  baseURL: adapter.config.aWATTarApiUrl
});

async function xyz () {
  const res = await api.get(`?start=...`);
  // res.data now holds your parsed json object, no need to call JSON.parse manually
}

I don't see any other callback (affected by the async/await logic) in your main.js at the moment.

Good things come to those who wait. ;-)
i refactored everything to make use of axios and pushed it ... plz check

Now you are mixing the "normal" promise logic (.then) and the async/await logic.
I would suggest changing
    axios({
        method: 'get',
        baseURL: urlEpoch,
        timeout: 10000,
        responseType: 'json'
    }).then(
       async (response) => {

to use await as well.
For error handling, you should wrap this into try {...} catch (e) {...}.
    let response;
    try {
       resonse = await axios({
          method: 'get',
          baseURL: urlEpoch,
          timeout: 10000,
          responseType: 'json'
      });
    } catch (error) {
      // your error handling for axios errors
      // ...
      // return from the main function
      return;
    }

    const content = response.data;

Also you should set the state values with the ack flag set to true.
Example:
await adapter.setStateAsync(stateBaseName + "start", startTime, true);

https://github.com/sirjojo69/ioBroker.awattar/blob/master/main.js#L338
There you aren't using the async functions. This should be changed as well imho.

this is fixed... plz check...

@sirjojo69 Whats the status? The comments from @crycode-de are all also great. Anything where you need support?

sorry, just no time. i will try to implement @crycode-de s suggestions by next week...

@sirjojo69 Did you found time?

Sadly not. I try to solve next issues at the weekend…
Von: Ingo Fischer @.>
Gesendet: Donnerstag, 22. Juli 2021 22:26
An: ioBroker/ioBroker.repositories @.>
Cc: sirjojo69 @.>; Mention @.>
Betreff: Re: [ioBroker/ioBroker.repositories] added awattar adapter (#986)
@sirjojo69 https://github.com/sirjojo69  Did you found time?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ioBroker/ioBroker.repositories/pull/986#issuecomment-885209838 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM7L7KJL7GLAK6RQ342JKGDTZB5GFANCNFSM4TV2ZR4A .  https://github.com/notifications/beacon/AM7L7KJ6Y4AZZMTBG64VGWLTZB5GFA5CNFSM4TV2ZR4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGTBTV3Q.gif

Just ping when I should check again

Some review according to the checklist to assist @Apollon77:
Readme
* Your readme is completely in German. In my opinion it's ok because the adapter is specific for a German service, but you should add a short description in English to let non-german people know what it is for.

* The order of the changelog entries should be reversed. The newest entry should be on top.

* Adjust the license information to include the current year like "Copyright (c) 2020-2021 ...".

Testing
* You may add Node.js 16.x to the adapter tests [here](https://github.com/sirjojo69/ioBroker.awattar/blob/master/.github/workflows/test-and-release.yml#L53)

package.json
* You should remove the [request dependency](https://github.com/sirjojo69/ioBroker.awattar/blob/master/package.json#L22) since you are using axios.

* You may remove axios from _devDependencies_ since you have it in you _dependencies_.

io-package.json
* News and title are only translated in de and en. Maybe add the missing translations using the [ioBroker translator](https://translator.iobroker.in/) service?

directories and files
* Looks good to me.

index_m.html
* You are mixing English and German texts [here](https://github.com/sirjojo69/ioBroker.awattar/blob/master/admin/index_m.html#L100). They should be in English.

* Your translations are missing in [words.js](https://github.com/sirjojo69/ioBroker.awattar/blob/master/admin/words.js). Consider using Weblate for the translations to get "cloud" translations from the community.

Adapter Logic
* Some `setStateAsync` calls may be parallelized using `await Promise.all([setStateAsync(...), ...])`.

every point has (finally) been implemented. The only thing not done was the hint for index_m.html. The only german words used there are that specific that it would be more confusing to the usual (german)  user to translate that into english. This is a phrase one could find on his bill, but not if i translate that into english....

I love to add it to the repo. Please release a new version because 1.0.5 is from november 2020.
Here some more (optional) comments:

there is a special "role" "json" for json data ... you might want to use that for Rawdata
If all logic is using await correctly and such then you do not need the timeout here https://github.com/sirjojo69/ioBroker.awattar/blob/master/main.js#L376-L378
the "desc" in io-package is still only de/en :-)

i released 1.0.6. right even now...


Fix dependencies on internal crates

We may need to refactor the dependencies somehow. So let's leave this to the end of 0.4.


Unable to change XP needed for leveling

I have this mod installed on my modpack and even after changing the xp levels in the config and making a new singleplayer world all the XP levels were still what they were originally set to

Which version of the mod?

I am having the same issue. I am using 1.10.2-1.0.1

im also using 1.10.2-1.0.1

Also having the same issue. Changed the default 500 xp to 300, saved the file. No change in game. Same version as well 1.10.2-1.0.1

Cleanup, closing old tickets.


Upgrade dependencies

[x] #12

This should be done at the end of the cleanup stage. Reason:
Some of the tests have been turned off because they take too long to run. If we upgrade now (before adjusting the tests) then we may break the tests unknowingly.

Useful https://stackoverflow.com/questions/61700920/is-it-good-practice-to-use-the-latest-versions-of-dependencies-when-publishing

Actually we still need to run the cargo command to upgrade the dependencies

curve25519_dalek_ng VS curve25519_dalek
The former has the following text:

This crate continues the curve25519-dalek series under a different package name. Unfortunately, one of the maintainers of the previous crate seized control of the dalek-cryptography GitHub organization and the subtle and curve25519-dalek crates by silently removing all other co-maintainers.

Relevant: https://github.com/dalek-cryptography/curve25519-dalek/issues/345
Does not seem like there is a legitimate security concern with the original repo.
The former has not been updated in 2 years, but the latter was updated last week.
Going to rather use the original repo.

Turns out you cannot switch from curve25519_dalek_ng to curve25519_dalek without breaking the bulletproofs dependency, because it uses curve25519_dalek_ng

I raised a question on the bulletproofs repo: https://github.com/zkcrypto/bulletproofs/issues/15

Just waiting on v5 to be published https://github.com/zkcrypto/bulletproofs/issues/22


Python 3 support

Using the first example on Python 3.5 I get the following error:
ImportError: cannot import name 'PyBingWebSearch'

I see there's already a pull request with appropriate fixes. When is it going to be merged into the main branch?

It should now support Python3 after 38b2199  . Try installing the newer version via
pip3 install py_bing_search
and it should work.


obb in dataset

When i use obboxes, the last dim of the tensor is always 6 not 7.So this bug occurs: RuntimeError:start(6)+length(1) exceeds dimension size(6). The code is "center, w, l, h, theta = torch.split(obboxes, [3, 1, 1, 1, 1], dim=-1)", obboxes.shape = (244, 6), but the last dim should be 7.

That seems a bit odd. The last dim for OBB input is indeed supposed to be 7 instead of 6. Could you please check if the correct OBB input is loaded?

But I use the OBB offered in this website, could you please give me a new link?

I'm having the same issue with hypersim data. Did you solve this issue?

I'm having the same issue with hypersim data. Did you solve this issue?
Not at all

I'm having the same issue with hypersim data. Did you solve this issue?

Can run the code normally on 3D-FRONT dataset?

I'm having the same issue with hypersim data. Did you solve this issue?

Can run the code normally on 3D-FRONT dataset?

No, I cannot run it on 3D-Front dataset. I get the same error.

This issue have been closed


fix: catalog images

Description
Handle changes with PowerVS catalog images. Easier to modify the images by using ibm_catalog.json file for Quickstart in future.
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

:tada: This PR is included in version 5.1.3 :tada:
The release is available on:

GitHub release
v5.1.3

Your semantic-release bot :package::rocket:


Add Storage network test in pre-release suit

Add the Storage network test in the pre release test suit till https://github.com/longhorn/longhorn/issues/4218 is handled. So that we don't miss executing it before major releases
Signed-off-by: Khushboo<EMAIL_ADDRESS>

cc @longhorn/qa


[READY TO BE REVIEWED] Find a way to make omnibus send CAN messages

HI ONLY LOOK AT/COMMENT ON CAN_SENDER.PY (disregard the actual sending of can messages) EVERYTHING ELSE WILL CHANGE AFTER THE PARSLEY REWRITE
clickup link
Cool things in this PR

when the data msg input boxes are full, it automatically moves the cursor forwards (if possible)
when a backspace key is pressed and the current input box is empty, it automatically moves the cursor backwards (if possible)
when there are invalid fields and the SEND button is pressed, the "invalid" fields pulse
when the message type is changed, the respective msg_data input boxes have a "datatype header" that appears and the unused input boxes are read-only and have that disabled look

demo video
https://user-images.githubusercontent.com/56371758/221425956-966947ec-14db-4273-8fd9-df26a9406a24.mp4

This change is

I didn't realize the | in DEBUG_MSG was referring to a half byte, that will be addressed after the parsley rewrite


Let's use it.
How can this be tested?

build image
execute unit tests
check basic usage scenarios

Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly

I'm having problems with the latest linter (golangci-lint v1.44.0). Is 1.18 production-ready?

Related issue: https://github.com/golangci/golangci-lint/issues/2649

Will close it until, we can actually switch to 1.18


the video on the landing page is soo cramped

the video on the landing page is soo cramped.
There is a lot of horizontal real estate; we can have a larger video there if there is enough space.

Done.


[BUG] live container says unsupported installation method using altstore

Describe the bug
I have recently switched from SideStore to altstore but when i try and setup the JITless certificate, it says it’s unsupported. “Unsupported installation method. Please use AltStore or SideStore to setup this feature.” that makes no sense because it literally says ALTSTORE in it. can i have some help with this bc i need this app
Instructions to reproduce
just press the setup JIT less certificate button
What version of LiveContainer are you using?
Version 2.1.2-release (main/fd71dd7)
Other info
No response

It seems that you have solved this issue in #186, so I close this issue now. Feel free to reopen if you still have questions.


Explicitly add .nc files for .gitignore to not ignore

Since acme_diags/driver/!acme_ne30_ocean_land_mask.nc was pushed before .nc was added to .gitignore it will remain tracked in Git. Tracked files can be modified and updated regardless if they match a pattern in .gitignore.
However, it is better to be explicit with .gitignore and list the .nc files that need to be tracked.

@chengzhuzhang @forsyth2 FYI since we want to explicitly track .nc files that need to stay in the repo.


ntr: prospore membrane biogenesis

descendant of
GO:0005628
GO:0044091
A cellular process that results in the biosynthesis of constituent macromolecules, assembly, and arrangement of constituent parts of a prospore membrane.

Added.

Can you suggest a ref?

PMID:27630265

Ta.  Added.


MKL Bug

@ykim362
Environment info
Operating System: OSX, pip install --pre mxnet-mkl
MXNet commit hash (git rev-parse HEAD): b6b8da0ac2b1ef8b84089458c757ce8b19aab0d7
Python version and distribution: Python 2.7.13
Minimum reproducible example
from __future__ import print_function
import mxnet as mx
import skimage.io as io
import numpy as np

def print_activation(net, url):
    I = io.imread(url)
    if I.shape[2] == 4:
        I = rgba2rgb(I)
    image = mx.nd.array(I).astype(np.uint8)
    image = mx.image.resize_short(image, 256)
    image, _ = mx.image.center_crop(image, (224, 224))
    image = mx.image.color_normalize(image.astype(np.float32)/255,
                                     mean=mx.nd.array([0.485, 0.456, 0.406]),
                                     std=mx.nd.array([0.229, 0.224, 0.225]))
    image = mx.nd.transpose(image.astype('float32'), (2,1,0))
    image = mx.nd.expand_dims(image, axis=0)
    out = net(image)
    return (out - out.max()).exp().sum().asscalar(), mx.nd.log_softmax(out), out
act1, log_softmax_out1, out1 = print_activation(mx.gluon.model_zoo.vision.squeezenet1_1(pretrained=True), 'https://github.com/zackchase/mxnet-the-straight-dope/raw/master/img/real_hotdog.jpg')
act2, log_softmax_out2, out2 = print_activation(mx.gluon.model_zoo.vision.squeezenet1_1(pretrained=True), 'https://github.com/zackchase/mxnet-the-straight-dope/raw/master/img/real_hotdog.jpg')
print(act1, act2)
print((out1-out2).max(), (out1-out2).min())

Expected outputs should be
1.16364 1.16364

[ 0. ]
<NDArray 1 @cpu(0)>
[ 0. ]
<NDArray 1 @cpu(0)>

Instead I got
MKL Build:20170720
3.0 nan

[ 0.]
<NDArray 1 @cpu(0)>
[ 0.]
<NDArray 1 @cpu(0)>

And the first two values are different every time I run it.
% python bug.py
MKL Build:20170720
1.0 nan

[ 0.]
<NDArray 1 @cpu(0)>
[ 0.]
<NDArray 1 @cpu(0)>

% python bug.py
MKL Build:20170720
nan 718.584

[ 0.]
<NDArray 1 @cpu(0)>
[ 0.]
<NDArray 1 @cpu(0)>

Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

pip install --pre mxnet-mkl
pip install scikit-image
Save the above code snippet into file bug.py
python bug.py

What have you tried to solve it?

Calling mx.nd.log_softmax(out) before the term (out - out.max()).exp().sum().asscalar() in print_activation function seems to make the results right.
Results are correct for variants that don't involve MKL.

is there an update on this issue? we are keen to include MKL in an upcoming project.

@ykim362 stated that he started working on this a while back, but there's no update from him yet.
Help on finding the root cause is welcome.

My MKLDNN code seems to solve the problem. The output is very deterministic. It's always
1.1635 1.1635

[ 0.]
<NDArray 1 @cpu(0)>
[ 0.]
<NDArray 1 @cpu(0)>

@zheng-da Thanks! I have been also assuming the NDArray re-factoring solves this problem. Does the NDArrady refactoring also enable gluon APIs not currently available for CPU? (Inplace operations)


Add indication handling for the pairing accept/deny for Canon EOS.

We now wait for 60s for the user to accept/reject the pairing.
Whilst here, disable the focus button so it doesn't do the unexpected.

Nope, this doesn't work on re-connection. Needs more work.


Opera: downloading older version, x86 only

The script downloads a slightly older version of Opera. It downloads only the x86 version and not the ARM version.

This is not an issue any more, it is fixed in latest 0.7beta


Can't remove shadow from user location icon

I tried to use mapbox-android-plugin-locationlayer:0.4.0. I was able to increase size of shadow using elevation:
val locationLayerOptions = LocationLayerOptions.builder(this)
                    .backgroundTintColor(Color.TRANSPARENT)  // hide the default icon background
                    .elevation(100f)  // a large shadow
                    .build()

However, when I set elevation to 0, the shadow is still there:
val locationLayerOptions = LocationLayerOptions.builder(this)
                    .backgroundTintColor(Color.TRANSPARENT)  // hide the default icon background
                    .elevation(0f)  // hiding the shadow doesn't work
                    .build()

I would like to have an option to remove the shadow completely, which doesn't seem possible in 0.4.0, so for now I'm stuck with version 0.2.0. That's how it looks with my custom icon:
val locationLayerOptions = LocationLayerOptions.builder(this)
        .foregroundDrawable(R.drawable.my_location_icon)  // custom icon
        .backgroundTintColor(Color.TRANSPARENT)  // hide the default icon
        .elevation(0f)  // hiding the shadow doesn't work
        .build()

I believe this is because you are setting the background tint color to null while also trying to hide the elevation. If the background tint was left to default the elevation would be hidden behind it. I should just look into changing the visibility of the shadow if elevations set to 0. Thanks for reporting this, looking into it now.

Unfortunately setting backgroundDrawable doesn't help, because my icon is slightly smaller than the default one, so the shadow under it is still visible. This is the code I tried:
val locationLayerOptions = LocationLayerOptions.builder(this)
.backgroundDrawable(R.drawable.my_location_icon)
.foregroundTintColor(Color.TRANSPARENT)  // hide the default icon
.elevation(0f)  // hide the shadow
.build()

Good to know. At this point then, you'd need to wait for #356 to be merged and a bug release to go ahead and upgrade.


Appveyor for Linux

Confusing issues with junit.jar not working as expected.
Will leave this for now.


findBy show all data instead of showing data by attribute

Hi,
When using findBy, it's showing all data from table instead of showing data by attribute assigned. According to what I understand, findBy should work like 'where' method.
    /**
     * Find an entity by one of it's attributes.
     *
     * @param string $attribute
     * @param string $value
     * @param array  $attributes
     *
     * @return \Illuminate\Database\Eloquent\Model
     */
    public function findBy($attribute, $value, $attributes = ['*'])
    {
        return $this->executeCallback(get_called_class(), __FUNCTION__, func_get_args(), function () use ($attribute, $value, $attributes) {
            return $this->prepareQuery($this->createModel())->where($attribute, '=', $value)->first($attributes);
        });
    }

It will work if I remove 'first' method from query. And it should not be replace with  'get', so it can use other method such as 'orderBy' etc.
Thank you. :)

Sorry. My mistake, I should use where and then findAll to show particular data.


remove 12 factor gem to allow logging to disk

addresses: https://github.com/restarone/violet_rails/issues/669
remove 12 factor gem, we have to make sure that we can still deploy to heroku without it-- the reason for removal is that it treats logs as event streams (we dont have an out-of-the-box solution for logging to stdout) and some clients need to write logs to disk

Heroku deployment works without the 12 factor gem :+1:


issues/368/subprocess outputs

Configure loguru to use RichHandler
Log subprocess outputs

Must be rebased and merged after #369.