Add "GDAL" to list of CF-aware software

GDAL is a translator library for raster and vector geospatial data formats (https://gdal.org/en/latest/index.html) under an MIT style Open Source license (https://gdal.org/en/latest/license.html).
It supports a wide list of file formats (https://gdal.org/en/latest/drivers/raster/index.html), including netCDF (https://gdal.org/en/latest/drivers/raster/netcdf.html#raster-netcdf).
GDAL can be used with various programming languages like C/C++, Fortran (via the FortranGIS wrapper), Python and Java (https://gdal.org/en/latest/api/index.html) and in addition offers a number of useful command-line tools for working with geo-referenced data (https://gdal.org/en/latest/programs/index.html#programs).
Considering these points, I think it would be a useful addition to the list of CF-aware software on the CF-Website at https://cfconventions.org/software.html

GDAL supports netcdf -- but I don't know that it has any support for CF itself?
As a rule, GDAL doesn't have any opinion about what the data mean.
Also, it attempts to interpret all files as a standard data model I.e GIS raster format. Many CF constructs don't fit into that.
Please correct me if GDAL has grown CF support since I last looked, which was quite some time ago :-).

@ChrisBarker-NOAA GDAL has support for Section 7.5 Geometries. I use GDAL and the features in section 7.5 via ogr2ogr to create geojson geometries of where my data are located for searching/visualization on in the browser.
I think GDAL is a worthy inclusion in the list of CF aware software.

Sounds good then. Let's do it.
I'm a bit confused about GDAL vs OGR, but they are maintained together, so sure.

ogr2ogr is just one of the command line tools that comes with gdal: https://gdal.org/en/latest/programs/ogr2ogr.html sorry this confusion.

Yes, it looks like it's all under the GDAL umbrella.
Now someone just needs to write a PR.
:-)

I was also thinking about the "gdal_translate" utility which can copy only subwindows of the input file. So it must somehow understand the geo-referencing of the input file. However I don't know whether this is done via the single CF-attributes or the WKT string.

Now someone just needs to write a PR.

I would be willing to create a draft for a PR. However, I've never done that.
Is there a guide somewhere how exactly this is done in the CF repo ?
Thanks!

Dear @Armin-RS
Thanks for your offer! A while ago I wrote a recipe for doing a PR in CF GitHub for someone who wasn't at all familiar with git or GitHub. That was my situation not long ago, but probably you're better-informed than I was. Anyway, in case it is useful, here it is. If that's not what you meant, please ask again.
If you or anyone else notice mistakes in the below, please say so.
Best wishes
Jonathan

Create a GitHub account for yourself on the web
You have to authenticate yourself from Linux to GitHub for all operations. This can be done with username and password and two-factor authentication, but I think it's easier to create a GitHub personal access token. The Linux command git config --global credential.helper store causes your username and token to be stored in ~/.git-credentials the next time you are asked for them. Thereafter you don't get asked again.
"Fork your own copy" of the GitHub repo. There's a button for this on the web page for each repo e.g. https://github.com/cf-convention/cf-convention.github.io for the website, https://github.com/cf-convention/cf-conventions for the conventions. This creates a copy in GitHub e.g. https://github.com/JonathanGregory/cf-conventions. You only have to do this once for each repo, since any repo contains all the branches. Your GitHub repo doesn't automatically stay up to date with the cf-convention's GitHub repo, but that doesn't matter.
Create a local clone on Linux of your GitHub repo, with the command e.g. git clone https://github.com/JonathanGregory/cf-convention.github.io which will be downloaded to a directory named cf-convention.github.io in your current working directory. Then git remote add upstream https://github.com/cf-convention/cf-convention.github.io to designate the CF GitHub repo as "upstream", meaning it's the repo you forked.
You don't have to clone your repo more than once, because you can reuse it next time. However, once you've committed your change to the GitHub repo you can rm -rf the local clone if you like and clone it again again next time.
When you make the clone, it will be up-to-date. However, on future occasions, you have to bring it up to date before starting to work on it.  To do this, change directory to the local repo e.g. cd cf-convention. Then
git fetch origin # updates the local repo from your own GitHub repo
git fetch upstream # fetches updates from the CF GitHub repo
git checkout main # change to main branch (in case it's not already)

You can ignore 'Your branch is ahead of origin/main'. This means that your main branch on GitHub is not up-to-date, but it doesn't matter because you aren't going to use it. We just need an up-to-date local version of main:
git merge upstream/main # fast-forward your main to agree with CF main

Now it's up-to-date and ready for you to prepare changes. The fetch and merge aren't needed if you've just forked your GitHub repo from CF (meaning your fork is up-to-date) and then made a local clone of it.
An important feature of git is that the local directory changes its contents when you change branches in the repo. The repo knows all the contents of all branches (stored in hidden files in the directory), but it only shows you one at a time. The branch which is eventually published on the web is the "main" branch. Modifications are prepared by copying the main branch within the repo to a new branch, and modifying the new branch. To make a new branch, first cd to the local directory of the repo, then git checkout -b NAME copies the main branch to a new branch, where NAME is some word that you choose to name the new branch. For instance, you could name it after the GitHub issue it refers to. The name is arbitrary.
Now you can modify the local files. You change and add files using any methods. In order to tell it which changes should be committed to the repo git add FILE [FILE ...] for any new or modified files. To remove files git rm FILE [FILE ...].
While you're working and when you've prepared what you want, you can do
git status # to see which files you've changed
git diff # to see the changes in files you haven't declared to git add
git diff --cached # to see changes in files declared to git add

Then git commit -a -m "COMMENT" where COMMENT is a text string to describe what you've done. This comment will appear in GitHub.  After commit, the changes are no longer "cached". Then git push origin NAME to send the changes to your corresponding GitHub repo (i.e. the "origin", where you cloned it from). NAME is the name of the branch on the GitHub repo. I suppose it doesn't have to be the same as in the local repo, but I've always made it the same. The branch will be created on your GitHub repo as a copy of your local repo. That ends the business with your local repo.
Go back to your GitHub repo on the web. Click "Pull requests" at the top left of the window, then "New pull request". Set base repo on the left to the CF one e.g. cf-convention/cf-conventions, and the base branch to main. Set the head repo on the right to yours e.g. JonathanGregory/cf-conventions, and the branch to the NAME you've just created. It will compare the two of them and show you all the changes. For each file, you have a choice between the "source diff" <> line-by-line comparison, the "rich diff" with the page icon, which shows you text with insertions and deletions, and "view file" under the ... menu.
If it's all OK, click "Create pull request". The pull request is created in the CF repo, not your own copy. It will be automatically numbered and appear in the list of pull requests. The pull request is an instruction to import the modifications from your new branch of your repo into the main branch of the CF repo. It is not enacted until someone clicks "Merge" on its web page.  You should keep the branch in your repo until the merge is done. If you need to make any amendments, you can do them locally as before and push them to GitHub, and they will get included in the pull request automatically.  Once it's merged, you can delete the branch in your repo if you like. You can delete the whole repo if you want to, and fork again next time, but then you lose the history, which might perhaps be useful.

@JonathanGregory Should we get that added to the CONTRIBUTING.md file perhaps under at "git usage" type heading?

Thanks @JonathanGregory ! That was exactly what I was looking for :-)

@Armin-RS. I am glad that my recipe looks useful. If you find mistakes or omissions, please say. In order to avoid confusing this issue about GDAL, please could you, or anyone else, make any comments about that in conventions issue 369.
@DocOtak. Yes, if the instructions are correct and likely to be useful to others, they should go somewhere for reference. Since the instructions are the same for the conventions and website repos (and any other, but those are the two most people would need to change), it might be better to put the instructions in a web page, and refer to it from CONTRIBUTING.md in both repos. The open conventions issue 369 is about the conventions CONTRIBUTING.md file. I'll make a note there about this point.


2 tests failed. diff:diff across DST (2087.17) diff:diff across DST (2087.19)

Client info
Date String   : Mon Jul 13 2015 18:50:05 GMT+0300 (Sri Lanka Standard Time)
Locale String : 7/13/2015, 6:50:05 PM
Offset        : -120
User Agent    : Mozilla/5.0 (Windows NT 6.1; rv:39.0) Gecko/20100101 Firefox/39.0

====
diff:diff across DST (2087.17)
month diff across DST, lower bound
// Expected true
// Actual   false
false === true

====
diff:diff across DST (2087.19)
year diff across DST, lower bound
// Expected true
// Actual   false
false === true

Dup #2383


Added configurable roles separator char to HTTPProxyAuthenticator

I've added a role_separator because some SSO solutions have a configurable separator char.

@wbytebier We would love to merge this PR but we need to ask to sign our CLA. Can you send us your full name and your email address via e-mail to info(at)search-guard.com (or to the addresses listed here https://floragunn.com/contact/) for that purpose?

@wbytebier ping

@wbytebier ping

Sorry, have to close this because we received to CLA feedback within reasonable time.


Consider maxSockets limits to avoid common pitfalls

Currently, maxSockets: Infinity (which is actually Node.js' default anyway) is declared and passed to teeny-request within util:
https://github.com/googleapis/nodejs-common/blob/13ae85c09bfc0ea83cf392a930ccc8ba155033b0/src/util.ts#L37-L40
During issue triage for https://github.com/googleapis/nodejs-bigquery/issues/624 it was found that the reference implementation from the OP did not take into account the async nature of the API call, and subsequently caused 40,000 concurrent HTTPS (i.e. TLSSockets) to be opened at once. This caused timeouts, ephemeral source port exhaustion, and unnecessarily large RAM usage (more details in the linked issue). This is a common mistake, and the resulting errors are obscure and don't readily indicate root cause, making it difficult to troubleshoot.
I propose 2 options to combat the common pitfall:

monitor teeny-request's concurrent socket count, and start emitting warnings when it gets to be abnormally large (depends on https://github.com/googleapis/teeny-request/issues/148)
include an internal buffer to artificially queue/throttle the number of concurrent connections (globally or per API)

As another more practical case, during an incoming request burst (e.g. in a web app) for which perhaps multiple GCP API calls are made in parallel to respond to the request, the number of outbound sockets will be a multiple of incoming sockets. While this is an indicator that the application needs to scale, any solution so this problem will also affect this scenario - perhaps negatively if outbound requests are throttled.
cc: @bcoe @JustinBeckwith

I like both of those options! Warnings would be helpful, akin to the famous EventEmitter max listeners warning. If #2 is implementable, it would be nice to do as an opt-in option, unless everybody thinks that's safe to do by default without causing any surprises for users.

I'm not a huge fan of 2., I think this level of resource management should be happening at the Node.js or operating system level, e.g., I'd rather not implement back pressure in teeny-request.
I like the idea of 1., I think we could pick a reasonable threshold where it seems like we should be warning, e.g., 512 concurrent connections, usually you'd want to limit the number of parallel requests to something below a threshold (IMO).

we could pick a reasonable threshold where it seems like we should be warning, e.g., 512 concurrent connections
This is the problem though: what is a reasonable threshold to warn? In the case of a single instance of an application capable of sustaining 2000 TPS, assuming RTT at ~500ms, 512 would not be a big enough number. On the contrary, a serverless function may only require about 50-100 for the threshold. Whatever is chosen will be highly opinionated about the architectural decisions for the software, but at least this won't be a hard ceiling.

Warnings would be helpful, akin to the famous EventEmitter max listeners warning
Correct, this would be the effect. Most importantly though is the reason behind the max listeners warning: programmatically detecting code smell. There are (rare) cases where the max listeners threshold in Node.js is too low, the implementer makes a conscious decision about this and subsequently increases the threshold.

A few thousand (2-5k) outbound requests would be a safe bet IMO: high enough to not be noisy, but low enough to detect the pitfall before things get out of control. This warning would surface during load/performance testing, or somewhat early in the life of an application.
Additionally, an easy way to suppress or change this threshold would provide an opt-out or tuning feature. See EventEmitter.defaultMaxListeners.

Decision: warn on threshold, should be configurable and the ability to disable; pick a sane upper bound.


Add multiple versions of clang to Travis CI

The c2go build system should include all versions of clang 3+ to be tested against mac and windows.

This has been fixed since v0.5.0.


run_number is not unique enough for trace_id

In some cases (rerunning?) the run_number is re-used by github, leading to broken traces:

the trace_id should use the github.run_id instead.
Apologies, I'm just crushed with work today, otherwise I'd already have put up a PR fixing this.

Thanks for the report, I can confirm this happens with my workflows as well.
I think we can either:

add the run ID to the trace components, the trace ID will become: <workflow>-<job>-<run-number>-<matrix-key>-<run ID>
use a completely random trace ID (a UUID for example)

I don't know if there is any drawback related to really long trace ID's, but the first feels most user friendly.

So adding GITHUB_RUN_ID to the trace ID does not work, this run ID remains the same across re-runs.
This is also documented that way 😅:

Environment variable
Description

GITHUB_RUN_ID
A unique number for each run within a repository. This number does not change if you re-run the workflow run.

GITHUB_RUN_NUMBER
A  unique number for each run of a particular workflow in a repository.  This number begins at 1 for the workflow's first run, and increments  with each new run. This number does not change if you re-run the  workflow run.

So adding GITHUB_RUN_ID to the trace ID does not work, this run ID remains the same across re-runs.

which is weird, given the github.run_id field in my screenshots is different. :man_shrugging:
I'd be fine with replacing the whole trace_id with a uuid or the otel style random byte[] string (see https://github.com/honeycombio/buildevents/blob/a29a075b660897b8e610b5ee479015d7da930481/cmd_cmd.go#L71)

god - I must be really stressed. There is no repo name in the trace-id - and we're running on 50 different repos - no wonder there're collisions. :facepalm:

I can confirm this is fixed now. Re-running the workflow creates a unique trace id:


FontAwesome is connected because of one icon?

If already has a fontAwesome of the other version in project, there will be no problems?

I think the font-awesome icon should be removed and replaced with an inline svg instead. This way you don't have a dependency on font-awesome.

I agree! I'll do some hunting for an SVG icon :)

Got this quickly done for you. Hope it will help


RHTAPSRE-64: allow limited set of users access to the cluster entitlement secrets

@ernesgonzalez33 @dfodorRH @gbenhaim @brianwcook @arewm @ralphbean FYI you are being given view access to the entitlement secrets on the various RHTAP clusters based on https://issues.redhat.com/browse/RHTAPSRE-64 and the discussions in https://redhat-internal.slack.com/archives/C02CTEB3MMF/p1688479083511429

Note - this level of RBAC changes does NOT require e2e testing.

/hold
there is some disagreement in https://redhat-internal.slack.com/archives/C02CTEB3MMF/p1688479083511429 on whether we should do this, vs. just let users discover their entitlement secrets through other means and copy them into their namespace


Cannot install windows edition of 1.12.3 due Windows defender

Hi,
The installation of 1.12.3 .exe is stopped by the Windows Defender SmartScreen.
My guess is that it is due to the unknown publisher.
This is the first time I encounter the problem, for example 1.12.2 installation works fine.

Duplicate of #1696

@angelaatskandia
This issue has been resolved in the latest release of v1.13.0
You can download the latest version from: https://www.usebruno.com/downloads
Please reopen the ticket if you are still facing issues.


Use JSDOM more cleverly

I haven't dive into JSDOM that deep, maybe we could simply bind feathericons function to JSDOM vm instance. I think that the implementation here is quite nasty.

c116d34 solve the problem.


0.29

Release date: Unknown. A couple of users have reporting experiencing random segfaults (#3453) and we're still investigating.

It's time for 0.29 and this is a big release as we've completely overhauled the internals of Home Assistant. When I initially wrote Home Assistant, still figuring out the ins and outs of Python, I went for an approach that I was familiar with for an application with many moving parts: threads and locks. This approach has served us well over the years but it was slower than it needed to be, especially on limited hardware.
This all changed when @bbangert came around and took on the tough job to migrate the core over to use asynchronous programming. He did an amazing job and I am happy to say that the initial port has been done and is included in this release! On top of that, we have been able to keep our simple and straightforward API at the same time. We are still in the process of migrating more and more components over to the asynchronous API, so expect more speedups and awesome features in the upcoming releases.
On the voluptuous front we have also made great progress. We were able to fully remove the legacy config helpers and have migrated 317 of the 346 components and platforms that needed migrating! This does mean that for some components the config has slightly changed, make sure to check out the breaking changes section at the bottom for more info.

Convert core from thread-based to be async-based (@bbangert, @balloob)
New SleepIQ support (first supported bed!) (@technicalpickles)
Cover: Vera is now supported (@pavoni)
Climate: Vera is now supported (@robjohnson189)
Control Home Assistant with keyboard shortcuts (@deisi)
More voluptuous config validations (@fabaff, @kellerza, @balloob)
New Nuimo controller support added (@gross1989)
Sensor: BOM Weather component (@tinglis1)
Automation: Option added to hide entity (@milaq)
Sensor: Emoncms feeds now supported (@joyrider)
Sensor: Mi Flora plant sensor now supported (@open-homeautomation)
Logbook: Allow filtering entities and hide hidden entities (@wokar)
Notify: Kodi support added (@chrom3)
Notify: Support for Simplepush added  (@fabaff)
Sensor: KNX sensors now supported (@daBONDi)
Wink improvements (@w1ll1am23)
ISY improvements (@Teagan42)
Notify - Slack: support for username/icon (@Khabi)
MQTT room detection: away timeout now supported (@mKeRix)
Climate: Nest can now control the fan (@jawilson)
Modbus: major cleanup for switches and sensors (@persandstrom)
HTTP: Allow passwordless logins from whitelisted IP addresses (@Danielhiversen)
Sensor: Yahoo! Finance stocks now supported (@tchellomello)
Sensor: Set value based on incoming e-mail (@sam-io)
Light: White value now supported (@mxtra, @MartinHjelmare)
InfluxDB: Allow attaching extra data (@lwis)
Minor features and bug fixes by @fabaff, @w1ll1am23, @turbokongen, @clach04, @mKeRix, @pvizeli, @DavidLP, @nvella, @Teagan42, @ericwclymer, @wokar, @kellerza, @nkgilley, @jawilson, @Danielhiversen, @ej81, @danieljkemp, @balloob, @philhawthorne, @LinuxChristian, @milas, @simonszu, @Cinntax.

Breaking changes:

yahooweather default name is now yweather. Also min and max temperature are now correctly called Temperature Min and Temperature Max.

https://github.com/home-assistant/home-assistant.github.io/pull/969


UNTESTED Use configured port instead of default.

Hey @trenton42 I think this is what's needed so Honeybee plays nice with Nomad.
Theoretically, Nomad should be able to serve RabbitMQ over static ports. I couldn't get it to cooperate in the short time I had, but I could try again if it's too painful to build Honeybee.
I haven't tested this yet (I haven't successfully built Honeybee).

@trenton42 also, I'm wondering if GitLab has cross-project deploy keys. That could solve some of our problems by forking this module to GitLab.


Codestar support (without lint)

Issue #, if available:
#382
Description of changes:
This PR adds CodeStar connection support for pipelines source action.
Using CodeStar connection support adds functionality needed for use-case described in #382 and is the recommended  source action for BitBucket, GitHub & GitHub Enterprise (see docs)
This PR includes tests for the new method
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@tsahiduek we use linting in the project with ESLint as described here. For each PR please run the following:
make build
make lint
make run-test
cdk list

All the commands must succeed. The same is performed in the github action on PR.
I will look into the Overall Status Check failure, that one seems to be affecting all PRs atm.

Thanks @shapirov103 . Missed that.
Apparently it's something related to ESLINT.
It should be fine now.
For the cdk list command, it fails, but not because of my change.
There's something related to the OPA add-on defined in the example stack.
If I'm commenting it out, then the command executed successfully.
See stack trace details:
➜  cdk-eks-blueprints git:(codestar-support-lint) ✗ npx cdk ls
WARN Upgrade is needed for chart argo-cd-4.10.9: latest version is 5.27.4.
INFO Chart appmesh-controller-1.11.0 is at the latest version.
INFO Chart cert-manager-1.11.0 is at the latest version.
WARN Upgrade is needed for chart kube-state-metrics-4.31.0: latest version is 5.2.0.
INFO Chart prometheus-node-exporter-4.14.0 is at the latest version.
DEBUG Core add-on adot is at version v0.66.0-eksbuild.1
INFO Chart base-1.17.1 is at the latest version.
INFO Chart istiod-1.17.1 is at the latest version.
INFO Chart tigera-operator-v3.25.0 is at the latest version.
WARN Upgrade is needed for chart metrics-server-3.8.3: latest version is 3.9.0.
INFO Chart aws-load-balancer-controller-1.4.8 is at the latest version.
WARN Upgrade is needed for chart nginx-ingress-0.16.2: latest version is 0.17.0.
WARN Upgrade is needed for chart velero-3.1.2: latest version is 3.1.5.
DEBUG Core add-on vpc-cni is at version v1.12.5-eksbuild.2
DEBUG Core add-on coredns is at version v1.9.3-eksbuild.2
DEBUG Core add-on kube-proxy is at version v1.24.10-eksbuild.2
/Users/duektsah/dev/cdk-eks-blueprints/node_modules/sync-rpc/lib/index.js:165
    const error = new Error(msg.v.message);
                  ^
Error: write EPROTO<PHONE_NUMBER>:error:140943E8:SSL routines:ssl3_read_bytes:reason(1000):../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1546:SSL alert number 0

    at extractValue (/Users/duektsah/dev/cdk-eks-blueprints/node_modules/sync-rpc/lib/index.js:165:19)
    at /Users/duektsah/dev/cdk-eks-blueprints/node_modules/sync-rpc/lib/index.js:175:12
    at request (/Users/duektsah/dev/cdk-eks-blueprints/node_modules/sync-request/lib/index.js:28:15)
    at loadExternalYaml (/Users/duektsah/dev/cdk-eks-blueprints/lib/utils/yaml-utils.ts:46:22)
    at listChartVersions (/Users/duektsah/dev/cdk-eks-blueprints/lib/addons/helm-addon/helm-version-checker.ts:73:44)
    at checkHelmChartVersion (/Users/duektsah/dev/cdk-eks-blueprints/lib/addons/helm-addon/helm-version-checker.ts:87:20)
    at Function.validateVersion (/Users/duektsah/dev/cdk-eks-blueprints/lib/addons/helm-addon/index.ts:64:49)
    at new HelmAddOn (/Users/duektsah/dev/cdk-eks-blueprints/lib/addons/helm-addon/index.ts:59:19)
    at new OpaGatekeeperAddOn (/Users/duektsah/dev/cdk-eks-blueprints/lib/addons/opa-gatekeeper/index.ts:30:9)
    at new BlueprintConstruct (/Users/duektsah/dev/cdk-eks-blueprints/examples/blueprint-construct/index.ts:103:13) {
  code: 'EPROTO'
}
****************************************************
*** Newer version of CDK is available [2.70.0]   ***
*** Upgrade recommended (npm install -g aws-cdk) ***
****************************************************

Subprocess exited with error 1

It clearly points to OpaGatekeeperAddOn.
I can comment it out for now if needed.

@tsahiduek the check succeeds now. the issue that you observed is most likely related to the helm chart checking at build time. If the chart repo is inaccessible temporarily it may fail. We now have a global issue with the overall status check from the I&A team as all open PRs are failing now, we are working with the I&A team to resolve.

@tsahiduek some minor syntax issue here


Audio: Add Background Music

Repo: https://github.com/kyleneideck/BackgroundMusic
Stars: 4042
Commit: 197
Last Commit: 20 hours ago

This is not a library.


Argument 2: cannot convert from 'Microsoft.Extensions.Configuration.IConfigurationSection' to 'System.Action'

Hi,
I"m trying to configure my options. I'm trying to use the same method in the docs, but I get the error:
Argument 2: cannot convert from 'Microsoft.Extensions.Configuration.IConfigurationSection' to 'System.Action'
My code:
public static IServiceCollection AddCustomOptions(this IServiceCollection services, IConfiguration configuration)
        {
            services.Configure<CommonSettings>(configuration.GetSection(nameof(CommonSettings)));
            return services;
        }

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

ID: ed39cb0e-aa85-8bba-ffb4-859b56a60723
Version Independent ID: dc7e3449-650b-d117-5eac-69e5ccb250cb
Content: Options pattern in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/options.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Sorry! Realised I needed to include the package "Microsoft.Extensions.Options.ConfigurationExtensions"

Ha! was looking for this too.
It is hard to search for packages that contain missing extension methods.

Same here.  Documentation for extensions is lacking to put it very nicely.  I keep running into issues like this and tracking them down is very difficult.


[Summer-2021] task group queue function 210290601

1. the necessity of task group queue
Task group queue (TGQ) can achieve cross-project and cross-process concurrent control of tasks, reducing resource pressure on scheduling systems or other big data clusters.
TGQ also supports priority-based control, which ensures that important tasks can be executed first. Users can also execute a task compulsively, ignoring the TGQ.
2. the details about TGQ
TGQ is essentially a flow limiter. By managing resources, the TGQ allows the tasks to obtain resources from the TGQ. In this way, the resources obtained by multiple tasks is limited and the worker node's pressure is avoided.
The database optimistic lock is used to solve the thread-safety problem in the distributed concurrent scenario.
Note that some tasks are not TGQ bound:

The tasks that do not need to be performed by workers;
The tasks which do not belongs to any TGQ;
The task is forcibly started by the user.

2.1 init a TGQ
The user manually creates a TGQ. The size of the TGQ is specified by the user.
2.2 how do a TGQ works
Each task configured with TGQ will apply for resources from the TGQ before being issued to the worker. If the TGQ has no available resources, the task will not be delivered to the worker, and the task will wait for the resource release and resend a request to TGQ.
2.3 recycle resources
After receiving the response from the worker, TGQ will release the resources corresponding to the task.
2.4 fault tolerance
In the distributed architecture, the fault tolerance mechanism is considerable. When the worker node is offline, the tasks with a fault tolerance mechanism running on the worker node will be re-executed by the master. In order to prevent the same task from repeatedly applying for resources, when a task succeeds in applying for resources, it should check whether the task is already in the TGQ, and if so, it will resend the task to the worker. If not, allocate resources.

hi, thank you for your contribution. I noticed that you have modified a lot of files that you don’t want to close. I will close it. You can resubmit the PR after your modification is completed.


Add Budi Erwanto to Contributors List

Hi  @sariroti, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi Roshanjossey,
I think the tutorial is already clear describing the step by step, so for me there was no problem to follow it.
Cheers.

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Add core.sys to the sidebar

Fix issue 5872.

Some html core.sys docs are missing, some don't have any content. DAutoTest failing. Probably best to close this.


ssh, variable and ansible fixes

A couple things in this PR.
On a fresh environment, some of the assumptions about the environment re: ssh are not correct. I put in some logic to account for that.
During testing, the openshift-ansible-playbooks rpm was updated, and seemed to break the openshift-install.yaml playbook. A variable was changed/added? And the cakephp template is no longer deployed. I tweaked the ansible playbook a bit to address those changes.
On my tests, the bucket for the RAW image was already present but created by a different user? So I could not delete or use it. I variable'ized it as IMAGE_BUCKET and updated the sample config accordingly.
I also screwed up a couple of installs by not updating my FQDN everywhere, so I flipped the hostnames to dervice the domain from the variable already present, $DNS_DOMAIN.

Thanks for the PR!


VS Code - “View Type Documentation” to click and open readme for module in MCR

Add “View Type Documentation” support to click and open readme for module in MCR.
Part of https://github.com/Azure/bicep/issues/8789

This is blocked by https://github.com/Azure/bicep/issues/9036


Support for the FLIF codec

Is it possible to integrate the FLIF codec https://flif.info/
This is the graph they supplied on their website:

FLIF is merged into and superseded by JPEG-XL. This talk has a lot of interesting info.

I'll give it a watch then, thanks!


Explore possibility of Viber notifications

As far as I know there is no Viber API. See this Quora question.


The JS/TS language service immediately crashed 5 times. The service will not be restarted.

Type: Bug
all of a sudden. out of nowhere.
 At first it was blaming other extensions. So I uninstall all the extensions to no avail, now it suggested me to report the issue.

/gif

From: Innomatic @.>
Sent: Monday, January 1, 2024 7:29:14 AM
To: microsoft/vscode @.>
Cc: Subscribed @.***>
Subject: Re: [microsoft/vscode] The JS/TS language service immediately crashed 5 times. The service will not be restarted. (Issue #201553)
I have the same issue. At first it was blaming other extensions. So I uninstall all the extensions to no avail, now it suggested me to report the issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/201553#issuecomment-1873012048, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXPWG66NOTZAA4J3HZBFGW3YMGVHVAVCNFSM6AAAAABBEM26EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGAYTEMBUHA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Autodetect the dialect version

Fix #1564
Requires https://github.com/hibernate/hibernate-orm/pull/6371

@gavinking (maybe @Sanne , if interested) I think this is now ready:

For SQL Server we are going to use the dialect version 10 because the latest one uses a query that doesn't work with Vert.x. This will print an additional line of log in the console to warn users.
We need a custom dialect for CockroachDB, because the one in ORM will run a query. I think we can avoid it by changing something in ORM, but I haven't looked into it yet (I wanted a workaround that doesn't require changes in ORM).

OK, great! Looks good!


optimize the SubsctiptionRegistry

Removes the previous linear search in finish_subscription and the now-unneeded Request object.
I'm pretty sure there is a little bit of RequestKind cloning that can be removed, but that's minor in comparison and can be improved upon later.

The failure sounds like https://github.com/rs-ipfs/rust-ipfs/issues/194 ... Might as well just quickly handle it so that it doesnt bother all of the time.

Raah, again the windows builds hangs on conformance tests without any console output.
bors r-

bors r+


pulumictl and pulumi are assumed to be installed for make build

What version of pulumi and pulumictl should be installed? The Makefile should not assume it is installed and should install a specific version of pulumictl into a build/work directory.
First pulumictl is run and much later pulumi is needed and run.

For pulumi, at least, there is already a copy that is installed in the working directory at .pulumi/bin/pulumi, and that copy is generally used by all tasks in the Makefile.  The script that generates examples was using pulumi, but #154 addresses that by updating the script to use the same local copy (.pulumi/bin/pulumi) as is used elsewhere.

Closed by the combination of #154 and #157


Time estimation for data collection on all routes

Thank you for providing the source code for your project.
I have two questions about the data collection process:

In order to reproduce your full dataset from the original paper, what routes are required for data collection? I noticed there are many route files, and some redundancy in the folder leaderboard/data.
Is there an estimation of simulation time/game time to complete all routes during a full data collection?

Hi！
We utilize 14 Carla servers to collect the dataset for two weeks. The specific route file can be found in the Readme. You can try the provided dataset for LMDrive first, and the only difference is the sample rate is 10Hz in that repo, instead of 2Hz of InterFuser.


Hi - trying to get in touch

Hi - apologies for leaving this as an issue but it was the only way I could find to get in touch with you.
Drop me an email on<EMAIL_ADDRESS>I'd like to chat about something related to this code :)

Thanks for reaching out Max. Will be in the irc. I created a room for the project as well. Closing this.
https://matrix.to/#/#xmrbc-rs:matrix.org


feature flow: enable SYN/FIN/RST capturing

Using this light-weight capturing we enable such features as tracking after a packet over time and detecting elements on the path with high latency.

working on the feature

merged


[move lang] Script blocks

Motivation

Added script blocks

Can now compile multiple scripts at once
Scripts must be in a block
Scripts functions no longer have to be named main! This should hopefully help

Replaced address directives with address blocks

Modules can be in an address block, scripts cannot

So any script
use 0x0::Foo;
fun main() {
  Foo::transfer()
}

is now written as
script {
    use 0x0::Foo;
    fun my_cool_script_name() {
        Foo::transfer()
    }
}

In the future, we could allow top level functions outside of the script, but it would involve copying the function code, so leaving that alone for now
For addresses, scripts no longer have an associated address. Address directives are now replaced by blocks
address <addr> {
module M {
...
}
}

I'm not sure if we want to indent under the address block as a style guideline. Its a lot of indenting for little benefit
I think we probably should indent for scripts, but I haven't to minimize code changes

Test Plan

cargo test

:umbrella: The latest upstream changes (presumably 955ee7549da7640ce52c24be33dd198d27a81a3a) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=bob-wilson

:pushpin: Commit e7867e1 has been approved by bob-wilson

:hourglass: Testing commit e7867e192a19c86affa374d20297b68c35d8b935 with merge bb48c8ae22a205d2dd9e85778bf1ec9fe26d2153...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=bob-wilson

:pushpin: Commit bfd86cb has been approved by bob-wilson

:hourglass: Testing commit bfd86cb9fd4e590f4fdb87e4282d82bfbc2f1657 with merge 04a310a9d88d67b6ff5f5f667f493500008a62a7...

@bors-libra r=bob-wilson

:pushpin: Commit 56c006b has been approved by bob-wilson

:hourglass: Testing commit 56c006b29e15bcc95e0f0b6d95a790dc478569eb with merge 3484e01a1d63282bb40d689eff1978998dac30d2...

@bors-libra retry

:hourglass: Testing commit 56c006b29e15bcc95e0f0b6d95a790dc478569eb with merge be18534f9f4fb7ddb66e50814a0d82cbd21f9373...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: bob-wilson
Pushing be18534f9f4fb7ddb66e50814a0d82cbd21f9373 to master...


update sidebar bg & minor fixes

Scope of changes
update sidebar bg & minor fixes
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[x] other (refactor)

Acceptance criteria

Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[ ]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 43.91% // Head: 43.89% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (a319b1d) compared to base (ee2f7e4).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #855      +/-   ##
==========================================
- Coverage   43.91%   43.89%   -0.02%
==========================================
  Files         623      623
  Lines       23086    23089       +3
  Branches     1412     1415       +3
==========================================
- Hits        10138    10135       -3
- Misses      11617    11623       +6
  Partials     1331     1331

Flag
Coverage Δ

unittests
43.89% <0.00%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...src/components/NetworkAnnouncements/caroussels.tsx
0.00% <0.00%> (ø)

...r-ui/src/components/NetworkAnnouncements/index.tsx
0.00% <0.00%> (ø)

...nents/OrganizationProfile/OrganizationalDetail.tsx
0.00% <ø> (ø)

web/gds-user-ui/src/components/Sidebar/index.tsx
25.00% <ø> (ø)

web/gds-admin-ui/src/utils/index.js
44.05% <0.00%> (-0.70%)
:arrow_down:

...com/trisacrypto/directory/pkg/gds/certman/certs.go
54.91% <0.00%> (-0.32%)
:arrow_down:

web/gds-admin-ui/src/sentry.js
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Bump to 0.2.2

Recent changes include better queue handling with the fake case. Makes development much easier.

:dango: :+1:


Use CF CLI v7

What
In https://github.com/alphagov/paas-docker-cloudfoundry-tools/pull/193 we started to use the generally available version of the CF CLI in our cf-cli docker image
This enables us to use cf push --strategy=rolling instead of using the blue-green plugin or autopilot plugin, and enables us to avoid the legacy buildpack parameter (instead of buildpacks) in our manifests
How to review
CI
Deploy to your development environment
Run all the deploy jobs:

[ ] pazmin
[ ] paas-accounts
[ ] paas-billing
[ ] aiven broker
[ ] post-deploy

Who can review
Not @tlwr

Deployed my DEV env with this branch, pipeline is green all the apps were deployed with the new CF CLI (v7).
Can be merged.


RFC: add the Rademacher distribution

Checklist

Please ensure the following tasks are completed before filing an issue.

[x] Read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] If this is a general question, searched the FAQ for an existing answer.
[x] If this is a feature request, the issue name begins with RFC:.

Description

Description of the issue (or feature request).

This RFC proposes adding the Rademacher distribution. Similar to other distribution namespaces, adding support for the Rademacher distribution would entail a family of packages for evaluating the PMF, CDF, mean, median, etc.
Namespace: @stdlib/stats/base/dists/rademacher
Reference: @stdlib/stats/base/dists/*
Related Issues

Does this issue (or feature request) have any related issues?

No.
Questions

Any questions for reviewers?

No.
Other

Any other information relevant to this issue (or feature request)? This may include screenshots, references, stack traces, sample output, and/or implementation notes.

No.

@justin1dennison  A good reference distribution namespace is the Bernoulli distribution namespace. You can start by contributing the @stdlib/stats/base/dists/rademacher/pmf package.  That sound okay?


Is there a way to stop the fireworks/happy new year chat messages?

Like the topic says, it started around 1pm for me and I suspect it will return in an hour

see #26
No, I never came around doing anything with Addons after we started porting Ender Io to 1.8.9...


CSS unit 'cap' (cap-height)

See https://drafts.csswg.org/css-values/#cap

+1

Available via MDN: https://caniuse.com/?search=cap unit


Skip extension install with extension bundle preview

Fixes https://github.com/microsoft/azure-gradle-plugins/issues/112
AB#1885844

Hi, is there any chance this PR can be merged?

@Zarick Sorry for the late response, related changes has been merged in https://github.com/microsoft/azure-gradle-plugins/pull/128 and released


Continue Training from a checkpoint saved in checkpoints folder

How can we continue the training of a model from a checkpoint saved in the folder.
Please write back as soon as possible. It will be of great help.

Just add the path of the checkpoint to this line https://github.com/NVIDIA/waveglow/blob/8afb643df59265016af6bd255c7516309d675168/config.json#L11


Test on our experiment bag, it look like no loop closure

Showed in this png,the long corridor doesn't match well.
How do I add loop closure detect into this package.

Hi @LiQiaopeng-1995,
this package is about mapping only. It does not contain any global optimization. If you want to try SLAM with our maps, there are scan-to-map matching functions implemented in the cslibs_ndt package that you can use e.g. with the ceres optimizer.


Graph: when applied a course filter, display all dependecies nodes too

I think this is pretty much the same as #4

Resolved in #4


[BUG] Azure Purview audience not supported

To Reproduce
curl http://localhost:50342/oauth2/token --data "resource=https://purview.azure.net/" -H Metadata:true -s

Observed Behavior
{"error":{"code":"AudienceNotSupported","message":"Audience https://purview.azure.net/ is not a supported MSI token audience. Supported audiences: https://management.core.windows.net/,https://management.azure.com/,https://graph.windows.net/,https://vault.azure.net,https://datalake.azure.net/,https://outlook.office365.com/,https://graph.microsoft.com/,https://batch.core.windows.net/,https://analysis.windows.net/powerbi/api,https://storage.azure.com/,https://rest.media.azure.net,https://api.loganalytics.io,https://ossrdbms-aad.database.windows.net,https://www.yammer.com,https://digitaltwins.azure.net,0b07f429-9f4b-4714-9392-cc5e8e80c8b0,822c8694-ad95-4735-9c55-256f7db2f9b4,https://dev.azuresynapse.net,https://database.windows.net,https://quantum.microsoft.com,https://iothubs.azure.net,2ff814a6-3304-4ab8-85cb-cd0e6f879c1d,https://azuredatabricks.net/,ce34e7e5-485f-4d76-964f-b3d2b16d1e4f,https://azure-devices-provisioning.net"}}

Expected Behavior
An access token.
Is this specific to Cloud Shell?
Yes.
Interface information
https://portal.azure.com
Additional context
Similar to Issue #109
AB#14503495

@Cheneric95 - Are we able to please add https://purview.azure.net/ as a supported audience (similar to what you did previously for Databricks #109 ).

Also relates to https://github.com/Azure/CloudShell/issues/220 as we want to add "499b84ac-1321-427f-aa17-267ca6975798/user_impersonation" as a supported token scope.

@robins1212 , can you validate that this audience in in place?


IE11 - fetch polyfill throws exception

Bug Report
What
It appears that the fetch polyfill isn't compatible with IE11 (I don't know when this happened, as I think it used to be).
Details
Including a repro and a screenshot as it's probably more useful. This is a polyfill of simply fetch and default.
https://ie-fetch-issue.now.sh

I've realised that this is because I have turned on break on all errors, not unhandled. My misunderstanding.
Closing for now until I have more detail!


all: fully deprecate dep, in favor of Go modules

We need to:
-drop the dep related files
-update the docs to reflect that we now use Go modules instead of dep
-clean up the mess that currently shows up when one tries to update the vendor/ dir with 'go mod vendor'.

Hi, anything here that has not been done and I can help with ?

Pretty sure this is complete.

Pretty sure this is complete.


Donut/rename group

The Donut image uses the Powered By MagenTys logo. This text should be removed.


Add shellharden

https://github.com/anordal/shellharden
The above mostly talks about shellhardens highlighting abilities, but if you use "--transform ''" it reformats your code with corrections. It can be useful.


Build "linux" module on *BSD (any non-macOS unix)

Thanks, that's great!

Bit of a silly question but have you tested if the linux implementation for trash actually works on a *BSD OS? I don't have a BSD at hand right now. If this actually works, I'll publish a new release with the patch number incremented to crates.io

cargo test passed of course. (I'm on FreeBSD and not running KDE, so it's using gio)

Sounds good! Thanks again.

This is now published as part of v1.0.1 on crates.io


issue with nokogiri, not being able to run the tests

So, i have upgraded my ruby version to ruby 3.0.1. I have a rails application with rspec.
When i try to run the command
bundle exec rspec spec

i get the following error
oadError:
  incompatible library version - /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/nokogiri.bundle
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:25:in `require'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:25:in `rescue in <top (required)>'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:4:in `<top (required)>'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri.rb:11:in `require'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri.rb:11:in `<top (required)>'
# ./spec/spec_helper.rb:3:in `require'
# ./spec/spec_helper.rb:3:in `<top (required)>'
# ------------------
# --- Caused by: ---
# LoadError:
#   cannot load such file -- nokogiri/3.0/nokogiri
#   /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:6:in `require'

I've tried fixing everything with rvm, but still this bug didint fix, any issues ?
Environment:
ruby : 3.0.1
nokogiri 1.11.3
rails: 6.1
Thanks

Unfortunately, this has nothing to do with RSpec.
Try require 'nokogiri' from irb and to see if it reproduces with the same error.
I'd suggest rvm reinstall && bundle pristine.
If the above doesn't help, please use our help channels https://rspec.info/help/, or StackOverflow. It's highly unlikely it's an RSpec bug and we can do anything about this.


Roam toolkit vim colors

When using roam-toolkit extension, with vim keybindings, the yellow higligth makes the text unreadable. Added code below for a nicer blue color.
.roam-toolkit-block-mode--highlight {
background-color: #6F8CAA;
}

Hi Daniel, thanks for doing this! would you mind opening a PR with that change? I will approve it immediately. Cheers!


3.0.0 stable tag

Would it be possible to publish a stable tag for 3.0.0?
Unfortunately this package is still broken with Symfony 6 if the projects minimum-stability is stable.

I also face the same issue.

same

Same here @BrainMaestro. Is the lib still maintained ?

+1

@BrainMaestro the same question.

I cant install the package with laravel 10.x, so I used the fork of another guy and it works: https://github.com/xHeaven/composer-git-hooks


PATH is an environment variable

testing.sh makes use of PATH variable, which is a "reserved" environment variable for listing bin search directories, in POSIX and Unix-like systems.
A viable solution is to change its name to something different.
As an alternative, a relative path can be used, as long as the behaviour of the script is not altered. This is the preferred solution, implemented in 2c0dee43838234be4e21622fc20281c4f72bd73f commit.

$PATH was not meaned to be the "PATH" env variable, but just as a shortcut to say "path where you stored the file in your system".
Better to change name to avoid ambiguity.

it had the same meaning of what prof. Marongiu uses as $ROOT/SRC/ecc...

$PATH was not meaned to be the "PATH" env variable, but just as a shortcut to say "path where you stored the file in your system". Was in charge of the user to change that line with its own path. Better to change name to avoid ambiguity.

Can auto-deduction be a good solution to avoid user interaction (9dfc647da94bf1d6ab618e39384ad03284c3f211)?

if it works then yes looool


Title: Tracking High score in simon game [58]

Which pre-existing JavaScript project will you be working on?
i would like to work on Simon Game - 58.
Describe your enhancement/improvement
I would like to add an improvement where the game will automatically track your high-score and keep it stored.
before - no highscore

after(for reference)

I would like to work on this enhancement. please assign this issue to me under GSSOC'24.
Anything you need to say to the Reviewers
No response
Add any other context or relevant screenshots about the enhancement here.
No response

@Dhruv-Gaba All the best 👍🏻

Sure. Do you also want me to track the current score?

@Dhruv-Gaba yes and don't change anything else.

Hello @swapnilsparsh, I'm interested in contributing to the project by implementing current score and high score functionality. Could you please assign this task to me?

hello @swapnilsparsh , I'm interested in contributing to the project. Could you please assign this task to me?

Hello
As I'm in the beginner stage of coding. Can you suggest me some projects?
Thanking you
On Mon, 20 May 2024, 11:48 pm Swapnil Srivastava, @.***>
wrote:

Closed #1414
https://github.com/swapnilsparsh/30DaysOfJavaScript/issues/1414 as
completed via #1456
https://github.com/swapnilsparsh/30DaysOfJavaScript/pull/1456.
—
Reply to this email directly, view it on GitHub
https://github.com/swapnilsparsh/30DaysOfJavaScript/issues/1414#event-12869515037,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A73BD2KBVALEOMGPWLHPTK3ZDI46FAVCNFSM6AAAAABH27TCJCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSHA3DSNJRGUYDGNY
.
You are receiving this because you commented.Message ID:
<swapnilsparsh/30DaysOfJavaScript/issue/1414/issue_event/12869515037@
github.com>


Use .luau instead of .lua for files

As you tweeted, GitHub now supports .luau files so it would make sense to move from .lua to .luau for improved syntax highlighting and so the repository is marked as Luau instead of Lua.
https://x.com/sleitnick/status/1800195657539715464
https://github.com/github-linguist/linguist/pull/6612

Done


Release 1.0.50 not installing or updating

Hi!
I downloaded the 1.0.50 release (the latest at the time of creating this ticket), and it errors out when installing or upgrading the installed version.
I downloaded the package multiple times and got the same error each time, and it complains about the package being invalid. I am using the app-arm64-v8a-release.apk file, but I didn't try the others (since I don't have devices for those). A reboot of the device and a cleaning of the cache did not fix the issue.
Sixo online APK analyzer can parse it just fine (https://sisik.eu/apk-tool), but my device doesn't agree with it... I'm running a Samsung S24 Ultra with Android 14 and the latest patch installed from Samsung.
That's the message I get:

I couldn't find any logs anywhere (either app logs or system logs) where I could see what's the actual error.
Thanks!

One thing I forgot to mention is that I'm updating from 1.0.44.
I just tried reinstalling 1.0.44, to make sure it works, and it does. Every subsequent release, starting from (and including) 1.0.45, fails to install or upgrade with the same error.
Thanks!

Do the other apks fail as well? Maybe I've tagged them wrong

Hmm doubtful they are tagged wrong since the arm64 installs on my pixel fine. I do notice a lot of this error in online forums mentioning your phone version. I'll add the universal APK to the next release and we can see if that works.

Does the universal release here https://github.com/brandonp2412/Flexify/releases/download/1.0.51/app-release.apk work?

Just tried the universal release and... same error. I'm getting suspicious there is something else at play. If it's a setting that changed itself during an update, I'll be really upset.
I'll do some tests with other APKs and see if they do the same thing.
Thanks!

Not sure if it's relevant to your device but someone I know managed to install it on a samsung S22. Weird that you aren't seeing any relevant logs in ADB when you install it, but I'm pretty sure I've run into similar problems on my previous app Massive. However that issue was to do with the signatures changing and basically I couldn't see any info about it in adb. Also that one worked once i completely uninstalled + reinstalled so this bug is indeed odd.

While waiting for my McDonald's order, I fiddled around with a few things and ended up uninstalling and reinstalling the app a few times. Installing the app started to work consistently after I cleaned the cache a few times, which is odd.
It seems that something, perhaps a signature change as you mentioned, caused anything below v1.0.45 to not be updatable with the newer releases. I'm surprised that no logs were generated by the system when that happens, and it just "fails" with no details.
I tried both the arm64 and the universal installer, and both work (as long as the app is fully uninstalled before when the version is 1.0.44 or less). I'll check the update on the next release, but I'm confident it'll work. If not, nuke and reinstall will be the first thing I do.
I think we can mark this issue as closed :)
Thanks!

It's probably because the f-droid team wanted me to override the way the versionCodes were generated by splitting per architecture, those versions might have an older code than the newer ones. Woops.

Ah, that would explain it. Mystery solved!
Thanks again!


Migrate “Services without selectors” to task section

This is a Feature Request

What would you like to be added
Create a new Task page based on the contents of
https://kubernetes.io/docs/concepts/services-networking/service/#services-without-selectors
Use tabs to document two options:

manually add an Endpoint
manually add an EndpointSlice

The content for manually add an Endpoint can come directly from the existing Service concept page.
Leave in its place a single paragraph that hyperlinks to the Task page.
Why is this needed
Service is a long page, and this text in particular is explaining how to perform a task.
Comments
/language en
/sig network

/remove-lifecycle rotten


Help with running command

Hello, I have managed to push this script to my device using platform tools, but from there I don't know how to execute this script without root. Any help will be much appreciated.

I also have the same question. How did you solve it?


BUG: Epochs.interpolate_bads_eeg fails when there are also bad MEG channels

If one or more MEG channels are marked bad, Epochs.interpolate_bads_eeg generates a very cryptic error. It should either just ignore MEG channels marked as bad or give a descriptive error message. (maybe both)

See PR #1776

can we close this?


Don't draw floating label on highlight

As an Android Develop I greatly used MPCharts and must say this is a very good port for flutter. However, in the Android version when a point is selected the highlight doesn't show a floating label, only the lines. I'm trying to achieve the same result here without success. Using LineDataSet.setDrawHighlightIndicators(false) causes the chart to not draw the lines but it still shows the label. See image for reference.
Am I missing something or is this something that needs to be fixed?

If I'm not mistaken you can just set drawMarkers to false without setting your own marker implementation.


fix: inserts clean up on failure

This fixes a bug introduced by datafusion 36
previously some operations that failed during optimization such as invalid casts now fail at runtime.
Since they now fail at runtime, it means that we would still create the catalog and table and only fail during insert afterwards. This left both the catalog and the storage in a bad state that didn't accurately reflect the operation. e.g.
create table invalid_ctas as (select cast('test' as int) as 'bad_cast');

This updated the catalog and created a table for invalid_ctas, but when you'd query it you would get an error.
This PR makes sure that the operation is successful before committing the changes. It does so by exposing some new methods on the catalog client. commit_state mutate_and_commit and mutate instead of the previous mutate.
The existing code was refactored to use the mutate_and_commit which is the same as the old mutate. The code that requires the commit semantics (create table) now uses mutate to first get an uncommitted catalog state with those changes, then does all of it's other actions

create the "native" table
Optional inserts into the table
commits the catalog state

If any of the operations before the commit fail, then the catalog mutations are never committed.

Some tests for catalog/src/client.rs
    #[tokio::test]
    async fn mutate_no_commit() {
        // Test to ensure uncommitted states aren't accessible.

        let client = new_local_metastore().await;
        let supervisor = MetastoreClientSupervisor::new(client, DEFAULT_METASTORE_CLIENT_CONFIG);

        let db_id = Uuid::nil();
        let c1 = supervisor.init_client(db_id).await.unwrap();
        let c2 = supervisor.init_client(db_id).await.unwrap();

        // Both clients have the same state.
        let s1 = c1.get_cached_state().await.unwrap();
        let s2 = c2.get_cached_state().await.unwrap();
        assert_eq!(s1.version, s2.version);

        // Client 1 mutates, no commit.
        let _ = c1
            .try_mutate(
                s1.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Client 2 should still get latest committed version.
        c2.refresh_cached_state().await.unwrap();
        let refreshed2 = c2.get_cached_state().await.unwrap();
        assert_eq!(s2.version, refreshed2.version);

        // Client 1 should also get the latest committed version, not the
        // uncommitted version.
        c1.refresh_cached_state().await.unwrap();
        let refreshed1 = c1.get_cached_state().await.unwrap();
        assert_eq!(s1.version, refreshed1.version);
    }

    #[tokio::test]
    async fn double_mutate() {
        // Test to ensure a client can mutate twice without having the
        // intermediate mutate affect anything.
        //
        // This represents the "rollback" case for when a query fails and
        // doesn't commit.

        let client = new_local_metastore().await;
        let supervisor = MetastoreClientSupervisor::new(client, DEFAULT_METASTORE_CLIENT_CONFIG);

        let db_id = Uuid::nil();
        let c = supervisor.init_client(db_id).await.unwrap();
        let state = c.get_cached_state().await.unwrap();

        // First mutation. This one doesn't get committed.
        let _ = c
            .try_mutate(
                state.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Second mutation, this one gets committed.
        let new_state = c
            .try_mutate(
                state.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "mario".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        let _ = c
            .commit_state(state.version, new_state.as_ref().clone())
            .await
            .unwrap();

        // Client should now have the new committed state.
        c.refresh_cached_state().await.unwrap();
        let refreshed = c.get_cached_state().await.unwrap();
        assert_eq!(new_state.version, refreshed.version);

        // New state version should not be the same as the original version.
        assert_ne!(state.version, refreshed.version);
    }

    #[tokio::test]
    async fn commit_arbitrary_state_version() {
        // Test trying to commit to an arbitrary version.

        let client = new_local_metastore().await;
        let supervisor = MetastoreClientSupervisor::new(client, DEFAULT_METASTORE_CLIENT_CONFIG);

        let db_id = Uuid::nil();
        let c = supervisor.init_client(db_id).await.unwrap();
        let state = c.get_cached_state().await.unwrap();

        // Mutate...
        let new_state = c
            .try_mutate(
                state.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Then commit with arbitrary version.
        let _ = c
            .commit_state(9999, new_state.as_ref().clone())
            .await
            .unwrap_err();
    }

    #[tokio::test]
    async fn concurrent_commits() {
        // Test to ensure two clients committing at the same errors as
        // appropriate.

        let client = new_local_metastore().await;
        let supervisor = MetastoreClientSupervisor::new(client, DEFAULT_METASTORE_CLIENT_CONFIG);

        let db_id = Uuid::nil();
        let c1 = supervisor.init_client(db_id).await.unwrap();
        let c2 = supervisor.init_client(db_id).await.unwrap();

        // Both clients have the same state.
        let s1 = c1.get_cached_state().await.unwrap();
        let s2 = c2.get_cached_state().await.unwrap();
        assert_eq!(s1.version, s2.version);

        // Client 1 mutation...
        let new_state1 = c1
            .try_mutate(
                s1.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario1".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Client 2 mutation...
        let new_state2 = c2
            .try_mutate(
                s2.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario2".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Client 1 commit should succeed.
        let _ = c1
            .commit_state(s1.version, new_state1.as_ref().clone())
            .await
            .unwrap();

        // Client 2 commit should error.
        let _ = c2
            .commit_state(s2.version, new_state2.as_ref().clone())
            .await
            .unwrap_err();
    }

    #[tokio::test]
    #[ignore]
    async fn error_on_commit_to_committed_catalog() {
        // Test to ensure we error when trying to commit an already committed
        // catalog.
        //
        // Once committed, a catalog version shouldn't be committed to again.
        // Other wise we could end up in a scenario where two nodes commit the
        // same version, with one overwriting the other's version.

        let client = new_local_metastore().await;
        let supervisor = MetastoreClientSupervisor::new(client, DEFAULT_METASTORE_CLIENT_CONFIG);

        let db_id = Uuid::nil();
        let c = supervisor.init_client(db_id).await.unwrap();
        let state = c.get_cached_state().await.unwrap();

        // Mutate...
        let new_state = c
            .try_mutate(
                state.version,
                vec![Mutation::CreateSchema(CreateSchema {
                    name: "wario1".to_string(),
                    if_not_exists: false,
                })],
            )
            .await
            .unwrap();

        // Commit as normal.
        let _ = c
            .commit_state(state.version, new_state.as_ref().clone())
            .await
            .unwrap();

        // Try to commit again.
        c.refresh_cached_state().await.unwrap();
        let refreshed = c.get_cached_state().await.unwrap();
        let _ = c
            .commit_state(refreshed.version, new_state.as_ref().clone())
            .await
            .unwrap_err();
    }

The ignored one is a test I'd expect to pass.

@scsmithr I added those tests & added some checks to get error_on_commit_to_committed_catalog to pass.

modulo some questions about this retry logic, I think @scsmithr should take another pass, but I think this feels correct.
[also just saying this here, if the insert is interrupted (process restart), there's still an inconsistency because the data is partially written and the catalog hasn't committed... similarly if the insert succeeds but the catalog update fails, the data is written but the table doesn't exist. I don't think that's a blocking bug right now.]


Implement new orb for giving notifications to GitHub

/fast-forward

Success! Fast forwarded main to feature/bla-bla! git checkout main && git merge feature/bla-bla --ff-only


Resizing while alt buffer is active, then disabling it, blows away renderer

WSL, in a small window
vim -u NONE
Maximize the window
Esc :q Enter
Observe the window get "stuck" on vim

It looks like we're failing to render a dirty region that is outside of the new, smaller main buffer.
It appears as though Terminal is not resizing the main buffer, as it believes it is already the correct size.
That check is happening here:
https://github.com/microsoft/terminal/blob/9edf55de7564912cb8e19ef3a3f88b689be08af7/src/cascadia/TerminalCore/Terminal.cpp#L252-L256
At the time of failure, _GetMutableViewport returns _mutableViewport, since we are no longer in the alt buffer.
Setting a write breakpoint on _mutableViewport to determine who is setting it, it's coming from EraseAll -> SetViewportPosition:
https://github.com/microsoft/terminal/blob/9edf55de7564912cb8e19ef3a3f88b689be08af7/src/cascadia/TerminalCore/TerminalApi.cpp#L42-L47
Potentially regressed in #13024 (/cc @j4james)

Yeah, it's definitely regressed in #13024. I remember thinking at the time that the assignment to _mutableViewport looked suspicious, but I got that from the original "EraseAll" implementation here:
https://github.com/microsoft/terminal/blob/6b936d9a74a5d677387f3edc9a68e6b33d566606/src/cascadia/TerminalCore/TerminalApi.cpp#L301-L303
So I'm not sure why that worked before. There must be something else different between the conhost and terminal architectures. I'll do some digging.

OK, I see now why it worked before. The terminal "EraseAll" implementation had an early exit check for _inAltBuffer() which meant the viewport wouldn't be set at all. But I think that's one of those things that only worked in Terminal because conpty would redraw the whole screen afterwards anyway. It's not actually clearing the screen in that case, so we can't do that in the current implementation.

But now that I think about it we can just make the Terminal::SetViewportPosition method a no-op when in the alt buffer - that should fix it.

That makes sense to me. The viewport in the alt buffer is always the entire buffer, right?

Yeah, if you look at the _GetMutableViewport method, it's just returning a Viewport object  with the alt buffer dimensions, so it's always at 0,0.
https://github.com/microsoft/terminal/blob/f4e0d9f2bd1f5da3a6c378453b90320fb6b1c542/src/cascadia/TerminalCore/Terminal.cpp#L970-L977


date parsing

Hi,
just discovering the project. I'm stucked with date parsing. Here are my files :
a.csv
"date"
"2019-06-04"
"2019-01-01"

a.schema.json
{
    "fields": [
        {
            "name": "date",
            "type": "date",
            "format": "default"
        }
    ],
    "missingValues": [
        ""
    ]
}

loading in node:
> let t = await Table.load('./a.csv', { schema: './a.schema.json' })
> t.read({ keyed: true })
[ { date: 2019-06-03T22:00:00.000Z },
  { date: 2018-12-31T23:00:00.000Z } ]

Where could the error come from?!
I've tried format "YYYY-MM-DD", "%y-%m-%d" with no success, default should works anyway. How should I format date by default (ISO 8601 seems a good idea).
Thanks in advance

@JDziurlaj
Hi, it seems here is a problem with a delimiter detection. It works for me if I provide it explicitly:
const {Table} = require('../src')

async function main() {
  const table = await Table.load('tmp/issue156.csv', {schema: 'tmp/issue156.json', delimiter:','})
  const rows = await table.read({keyed: true})
  console.log(rows)
}

main()
  .then(result => console.log(result))
  .catch(error => console.log(error))

Hi,
thanks for your answer... But it doesn't change anything on my Win10/node-12.4.0 version. Even with explicit delimiter set to ",", I still get
 [
  { date: 2019-06-03T22:00:00.000Z },
  { date: 2018-12-31T23:00:00.000Z }
]

As there's only one column, delimiter shouldn't be a concern anyway!
Sorry, but what's the chaining of the parsing of the date?
Thx

Sorry) Than I don't understand. What error? That's the expected output.

well the date is : "2019-06-04" -> "2019-06-03T22:00:00.000Z" or "2019-01-01" -> "2018-12-31T23:00:00.000Z... Oh, my! you're right: UTC issue, 1 or 2 hour shift winter/summer.
let d = new Date()
d.getTimezoneOffset() -> -120
d.toLocaleDateString("fr-FR")
'2019-6-11'

Is there any way to force getting the "same original date" 2019-06-04 -> 2019-06-04 . Maybe I've overlooked something in 'format' option that will be parsed?
Thanks and sorry for the confusion!

Yea I'd seen an error and was looking for something like an exception. Datetimes is a real problem for JavaScript.
The specs say nothing about it - https://frictionlessdata.io/specs/table-schema/#date. But the ISO8601 says that it's local time:

Time zones in ISO 8601 are represented as local time (with the location unspecified), as UTC, or as an offset from UTC.

So the lib acts correctly here. Let me check how to achieve your goal using formats.

This one works for me:
const {Table} = require('../src')

async function main() {
  const data = [
    ['date'],
    ['2019-06-04Z'],
    ['2019-06-01Z'],
  ]
  const schema = {
    fields: [
      {name: 'date', type: 'date', format: '%Y-%m-%d%Z'},
    ]
  }
  const table = await Table.load(data, {schema, delimiter:','})
  const rows = await table.read({keyed: true})
  return rows
}

main()
  .then(result => console.log(result))
  .catch(error => console.log(error))

Thanks a lot!


read timeout from COS

I experience weird exceptions regarding COS client that im not sure if its PyWren related.
while launching 1000 actions that each one calls for 8 objects in COS, I get read time out exception from PyWren's jobrunner code:
2019-10-27 13:49:01,474 [INFO] pywren_ibm_cloud.executor: ExecutorID 0b31-48da | JobID M000 - There was an exception - Activation ID: c6d09489f6844645909489f684f64552
Traceback (most recent call last):
  File "/action/pywren_ibm_cloud/runtime/function_handler/jobrunner.py", line 234, in run
  File "/action/pywren_ibm_cloud/runtime/function_handler/jobrunner.py", line 88, in _get_function_and_modules
  File "/action/pywren_ibm_cloud/storage/storage.py", line 102, in get_func
  File "/action/pywren_ibm_cloud/storage/backends/ibm_cos/ibm_cos.py", line 150, in get_object
  File "/usr/local/lib/python3.6/site-packages/ibm_botocore/response.py", line 81, in read
ibm_botocore.exceptions.ReadTimeoutError: Read timeout on endpoint URL: "None"
2019-10-27 13:49:01,478 [INFO] pywren_ibm_cloud.executor: ExecutorID 0b31-48da - Cleaning temporary data

and the activation c6d09489f6844645909489f684f64552 :
ok: got activation c6d09489f6844645909489f684f64552
{
    "namespace": "pywren_dev_us_east",
    "name": "omerb01_pywren-omer-runtime_3.6.16_2048MB",
    "version": "0.0.1",
    "subject"<EMAIL_ADDRESS>    "activationId": "c6d09489f6844645909489f684f64552",
    "start":<PHONE_NUMBER>024,
    "end":<PHONE_NUMBER>295,
    "duration": 63271,
    "statusCode": 0,
    "response": {
        "status": "success",
        "statusCode": 0,
        "success": true,
        "result": {
            "Execution": "Finished"
        }
    },
    "logs": [
        "2019-10-27T11:45:22.027485Z    stdout: [INFO] __main__: Starting IBM Cloud Functions execution",
        "2019-10-27T11:45:22.028148Z    stdout: [INFO] handler: Execution ID: 0b31-48da/M000/01385",
        "2019-10-27T11:45:22.034014Z    stdout: [INFO] JobRunner: Started",
        "2019-10-27T11:46:24.981342Z    stdout: ----------------------- EXCEPTION !-----------------------",
        "2019-10-27T11:46:24.991710Z    stdout: Traceback (most recent call last):",
        "2019-10-27T11:46:24.991728Z    stdout: File \"/usr/local/lib/python3.6/site-packages/urllib3/response.py\", line 425, in _error_catcher",
        "2019-10-27T11:46:24.991733Z    stdout: yield",
        "2019-10-27T11:46:24.991738Z    stdout: File \"/usr/local/lib/python3.6/site-packages/urllib3/response.py\", line 503, in read",
        "2019-10-27T11:46:24.991742Z    stdout: data = self._fp.read() if not fp_closed else b\"\"",
        "2019-10-27T11:46:24.991775Z    stdout: File \"/usr/local/lib/python3.6/http/client.py\", line 472, in read",
        "2019-10-27T11:46:24.991782Z    stdout: s = self._safe_read(self.length)",
        "2019-10-27T11:46:24.991786Z    stdout: File \"/usr/local/lib/python3.6/http/client.py\", line 622, in _safe_read",
        "2019-10-27T11:46:24.991791Z    stdout: chunk = self.fp.read(min(amt, MAXAMOUNT))",
        "2019-10-27T11:46:24.991795Z    stdout: File \"/usr/local/lib/python3.6/socket.py\", line 586, in readinto",
        "2019-10-27T11:46:24.991799Z    stdout: return self._sock.recv_into(b)",
        "2019-10-27T11:46:24.991804Z    stdout: File \"/usr/local/lib/python3.6/ssl.py\", line 1012, in recv_into",
        "2019-10-27T11:46:24.991808Z    stdout: return self.read(nbytes, buffer)",
        "2019-10-27T11:46:24.991813Z    stdout: File \"/usr/local/lib/python3.6/ssl.py\", line 874, in read",
        "2019-10-27T11:46:24.991817Z    stdout: return self._sslobj.read(len, buffer)",
        "2019-10-27T11:46:24.991821Z    stdout: File \"/usr/local/lib/python3.6/ssl.py\", line 631, in read",
        "2019-10-27T11:46:24.991825Z    stdout: v = self._sslobj.read(len, buffer)",
        "2019-10-27T11:46:24.991850Z    stdout: socket.timeout: The read operation timed out",
        "2019-10-27T11:46:24.991919Z    stdout: ",
        "2019-10-27T11:46:24.991928Z    stdout: During handling of the above exception, another exception occurred:",
        "2019-10-27T11:46:24.991932Z    stdout: ",
        "2019-10-27T11:46:24.991936Z    stdout: Traceback (most recent call last):",
        "2019-10-27T11:46:24.991972Z    stdout: File \"/usr/local/lib/python3.6/site-packages/ibm_botocore/response.py\", line 78, in read",
        "2019-10-27T11:46:24.991979Z    stdout: chunk = self._raw_stream.read(amt)",
        "2019-10-27T11:46:24.991984Z    stdout: File \"/usr/local/lib/python3.6/site-packages/urllib3/response.py\", line 529, in read",
        "2019-10-27T11:46:24.991988Z    stdout: raise IncompleteRead(self._fp_bytes_read, self.length_remaining)",
        "2019-10-27T11:46:24.992014Z    stdout: File \"/usr/local/lib/python3.6/contextlib.py\", line 99, in __exit__",
        "2019-10-27T11:46:24.992021Z    stdout: self.gen.throw(type, value, traceback)",
        "2019-10-27T11:46:24.992025Z    stdout: File \"/usr/local/lib/python3.6/site-packages/urllib3/response.py\", line 430, in _error_catcher",
        "2019-10-27T11:46:24.992029Z    stdout: raise ReadTimeoutError(self._pool, None, \"Read timed out.\")",
        "2019-10-27T11:46:24.992034Z    stdout: urllib3.exceptions.ReadTimeoutError: AWSHTTPSConnectionPool(host='s3.us.cloud-object-storage.appdomain.cloud', port=443): Read timed out.",
        "2019-10-27T11:46:24.992038Z    stdout: ",
        "2019-10-27T11:46:24.992042Z    stdout: During handling of the above exception, another exception occurred:",
        "2019-10-27T11:46:24.992046Z    stdout: ",
        "2019-10-27T11:46:24.992051Z    stdout: Traceback (most recent call last):",
        "2019-10-27T11:46:24.992084Z    stdout: File \"/action/pywren_ibm_cloud/runtime/function_handler/jobrunner.py\", line 234, in run",
        "2019-10-27T11:46:24.992090Z    stdout: loaded_func_all = self._get_function_and_modules()",
        "2019-10-27T11:46:24.992095Z    stdout: File \"/action/pywren_ibm_cloud/runtime/function_handler/jobrunner.py\", line 88, in _get_function_and_modules",
        "2019-10-27T11:46:24.992099Z    stdout: func_obj = self.internal_storage.get_func(self.func_key)",
        "2019-10-27T11:46:24.992194Z    stdout: File \"/action/pywren_ibm_cloud/storage/storage.py\", line 102, in get_func",
        "2019-10-27T11:46:24.992209Z    stdout: return self.storage_handler.get_object(self.bucket, key)",
        "2019-10-27T11:46:24.992214Z    stdout: File \"/action/pywren_ibm_cloud/storage/backends/ibm_cos/ibm_cos.py\", line 150, in get_object",
        "2019-10-27T11:46:24.992219Z    stdout: data = r['Body'].read()",
        "2019-10-27T11:46:24.992223Z    stdout: File \"/usr/local/lib/python3.6/site-packages/ibm_botocore/response.py\", line 81, in read",
        "2019-10-27T11:46:24.992238Z    stdout: raise ReadTimeoutError(endpoint_url=e.url, error=e)",
        "2019-10-27T11:46:24.992271Z    stdout: ibm_botocore.exceptions.ReadTimeoutError: Read timeout on endpoint URL: \"None\"",
        "2019-10-27T11:46:24.992278Z    stdout: ----------------------------------------------------------",
        "2019-10-27T11:46:24.994160Z    stdout: [INFO] JobRunner: Finished",
        "2019-10-27T11:46:25.009424Z    stdout: [INFO] handler: Storing execution stats - status.json - Size: 2.4KiB"
    ],
    "annotations": [
        {
            "key": "path",
            "value": "pywren_dev_us_east/pywren_v1.1.0/omerb01_pywren-omer-runtime_3.6.16_2048MB"
        },
        {
            "key": "waitTime",
            "value": 35
        },
        {
            "key": "kind",
            "value": "blackbox"
        },
        {
            "key": "timeout",
            "value": false
        },
        {
            "key": "limits",
            "value": {
                "concurrency": 1,
                "logs": 10,
                "memory": 2048,
                "timeout": 600000
            }
        }
    ],
    "publish": false
}

is there any way to avoid this behaviour  ?

@JosepSampe do you know how to prevent this timeout from COS? Are there open connections that we don't write / read them?

@JosepSampe it happens when we create thosands of invocations and then on read status - getting timeout reading from COS

@gilv We have 1 connection open per function (in jobrunner.py) to read the function itself and the data. If you write ibm_cos parameter, then there are 2 open connections per function.
@omerb01 Did you create a function with the ibm_cos parameter? or are you manually setting connections to COS to read those 8 files?

@JosepSampe with ibm_cos

@gilv Maybe some limitation in COS about parallel read? @omerb01 Are you using the free tier? Maybe something related to the cross-region us endpoin? can you try using a regional container in us-east?

@JosepSampe Thanks a lot , joined into a "standard" account and it seems ok.


Schema is marked as required

Jira ticket: https://issues.cask.co/browse/PLUGIN-251

Please squash commits.


Ajd 331 optimization 2nd stage refactor

Types of PR

[ ] New Features
[ ] Upgrade of existing features
[ ] Bugfix

Link to the issue
Description
PR for internal review
How to review this PR.
Others

LGTM


feat(workflow): Add gRPC APIs for workflow management

Describe the proposal
Parent issue: #463
HTTP APIs for workflow management was added by #485, this issue is to add gRPC APIs for the same.

DaprWorkflowClient already implements this (as part of authoring), so no further work is required.
https://github.com/dapr/js-sdk/blob/main/src/workflow/client/DaprWorkflowClient.ts#L27


Handle invalid negative temperature reads

Handle the case when sysctl errorneously returns negative temperature values.

Applied a similar fix on 8822be67ce3085c30a1127960d6c8ae1d7eb1876


make the dependency to brdr- version less specific

at the moment a specific version of brdr is mandatory (brdr==0.1.0).
This has to be made less specific (brdr>=0.1.0) on release so minor releases can also be used, but still important to check the backwards compatibility

At the moment, the versioning of brdr has to stabilize before executing this. So we put this 'on hold'


OmitIfEmpty encoding option issue with documentation

I ran into an issue that was annoying to track down and I'm not sure I entirely get it.  I was using jsonenums as part of a nested struct slice, and explicitly setting the json field name & setting the omitifempty flag.  My observation was that if I built an instance of that struct explicitly setting the value to be iota 0 as documented in the shirtsize example project, the value during encoding would be removed entirely.  If I removed the omitifempty flag, the proper value would show up.  Likewise I could also work around it by just adding 1 to the iota const.  It may be worth further investigation and/or a simple documentation update to warn people about this.
I was able to track it as far as here in the golang encode library.  My gut is telling me somewhere there is a confusion between an iota value of 0 and a nil which is what I expect omitifempty to apply to.

Gosh... same issue there! :)


Suggestion: Enable optional customized http.Client for transmitter

I'm building an application which leverages the app insights go client and, in order to run the resulting application in a minimal container (i.e. one without an OS CA certificate store), I need the ability to programmatically include trusted CA certificates in the transmitter's http.Client.
To enable this, I was thinking of adding the option to include a *http.Client option in TelemetryConfig which can then be leveraged during Transmit to call the app insights endpoint.  If the value of the TelemetryConfig.Client option is nil, the call to newTransmitter would substitute the http.DefaultClient automatically.

This was merged. Thanks again.


Fixed class filtering to work with combined ZF1/ZF2 stacks.

EdpSuperluminal causes an error when a non-namespaced class happens to begin with "Zend", e.g. when using it in a combined ZF1/ZF2 stack.
This two-character fix solves that problem.

@EvanDotPro Would you mind tagging after this is merged?


Add docs for custom authentication provider

Since the new 1.x version of Feathers authentication uses passport under the hood. Any passport auth provider will work. So you can refer to this repo for instructions on how to write your own custom passport strategy.
If you are looking to customize one of our existing plugins this is now described in the authentication section of the docs. An example for local auth is here.


Manifest Yaml Files Need to Be Included in Install Archive

Describe the feature request
Currently, the manifest install files aren't present in the install files. This leads to things like:
$ istioctl manifest apply -f samples/pilot-k8s.yaml

from https://preliminary.istio.io/docs/setup/install/operator/ not working. We should include the YAML files in our release archive so that users can find them.
Describe alternatives you've considered
Additional context

@howardjohn can you fix this defect in the packaging?  I think you are or maybe already have done thiis.
If not, please reassign to someone that can for 1.4 or un-assign.

Note docker.save should be functional and match that of the other repositories now so the containers can additionally be packaged.
Cheers
-steve

What files do you want where? Put everything in operator repo samples/ under samples/operator?

Looking through the istio.io docs, the only referenced file in the operator repo is samples/pilot-k8s.yaml. That said, these are all samples for the IstioControlPlane.

the deploy directory needs to be put somewhere.  install/operator would be a good target for that.
The directory you proposed seems good for samples.
Cheers
-steve

https://github.com/istio/release-builder/pull/54 adds deploy under install/kubernetes/operator/deploy and samples under samples/operator


Fix indenting to 2 spaces

Oh and if we are fixing on 2 space indents we should communicate/document this somewhere


CTShowcase is missing symbols for arm64 architecutre

Our project is using multiple pods, including a few Swift-only pods, but for only CTShowcase we cannot compile our app because it is missing symbols for the arm64 architecture.
Ld <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/<Omitted App Name>.app/<Omitted App Name> normal arm64
    cd /Users/ispence/Development/fexp/<Omitted App Name>
    export IPHONEOS_DEPLOYMENT_TARGET=9.3
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.0.sdk -L<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/CTShowcase -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/CorePlot -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/FontAwesome.swift -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/KeychainAccess -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/MBProgressHUD -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/Realm -F<Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/RealmSwift -F/Users/ispence/Development/fexp/<Omitted App Name> -filelist <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Intermediates/<Omitted App Name>.build/Debug-iphoneos/<Omitted App Name>.build/Objects-normal/arm64/<Omitted App Name>.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/Frameworks -miphoneos-version-min=9.3 -dead_strip -Xlinker -object_path_lto -Xlinker <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Intermediates/<Omitted App Name>.build/Debug-iphoneos/<Omitted App Name>.build/Objects-normal/arm64/<Omitted App Name>_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fembed-bitcode-marker -fobjc-link-runtime -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos -Xlinker -add_ast_path -Xlinker <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Intermediates/<Omitted App Name>.build/Debug-iphoneos/<Omitted App Name>.build/Objects-normal/arm64/<Omitted App Name>.swiftmodule -ObjC -framework CTShowcase -framework CorePlot -framework FontAwesome_swift -framework KeychainAccess -framework MBProgressHUD -framework Realm -framework RealmSwift -framework WebKit -framework Realm -framework FortiStartUSBTransferProtocol -framework RealmSwift -framework Pods_<Omitted App Name> -Xlinker -dependency_info -Xlinker <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Intermediates/<Omitted App Name>.build/Debug-iphoneos/<Omitted App Name>.build/Objects-normal/arm64/<Omitted App Name>_dependency_info.dat -o <Omitted Path>-ejhfhvnxmtwdymafgcibplrmmegj/Build/Products/Debug-iphoneos/<Omitted App Name>.app/<Omitted App Name>

Undefined symbols for architecture arm64:
  "direct field offset for CTShowcase.CTShowcaseView.messageLabel : __ObjC.UILabel", referenced from:
      <Omitted App Name>.View1.viewWillAppear (Swift.Bool) -> () in View1.o
      <Omitted App Name>.View2.viewDidAppear (Swift.Bool) -> () in View2.o
  "direct field offset for CTShowcase.CTShowcaseView.titleLabel : __ObjC.UILabel", referenced from:
      <Omitted App Name>.View1.viewWillAppear (Swift.Bool) -> () in View1.o
      <Omitted App Name>.View2.viewDidAppear (Swift.Bool) -> () in View2.o
  "type metadata accessor for CTShowcase.CTShowcaseView", referenced from:
      <Omitted App Name>.ShowcaseManager.(createShowcaseForKey in _68DEBFFCBBE708EE30E4F374E35DB70F) (<Omitted App Name>.ShowcaseManager.ShowcaseKeys, title : Swift.String, message : Swift.String, completion : (Swift.Bool) -> ()?) -> CTShowcase.CTShowcaseView? in ShowcaseManager.o
  "CTShowcase.CTShowcaseView.__allocating_init (title : Swift.String, message : Swift.String, key : Swift.String?, dismissHandler : () -> ()?) -> CTShowcase.CTShowcaseView", referenced from:
      <Omitted App Name>.ShowcaseManager.(createShowcaseForKey in _68DEBFFCBBE708EE30E4F374E35DB70F) (<Omitted App Name>.ShowcaseManager.ShowcaseKeys, title : Swift.String, message : Swift.String, completion : (Swift.Bool) -> ()?) -> CTShowcase.CTShowcaseView? in ShowcaseManager.o
  "type metadata accessor for CTShowcase.CTStaticGlowHighlighter", referenced from:
      <Omitted App Name>.ShowcaseManager.(createShowcaseForKey in _68DEBFFCBBE708EE30E4F374E35DB70F) (<Omitted App Name>.ShowcaseManager.ShowcaseKeys, title : Swift.String, message : Swift.String, completion : (Swift.Bool) -> ()?) -> CTShowcase.CTShowcaseView? in ShowcaseManager.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

This issue only appears with the CTShowcase pod, and we can manually import the two swift files into the project as a workaround.
Our pod file does not make any changes to the build settings for the pod project, or pod targets.

That's weird. I've used this pod in a lot of different projects and haven't had any problems yet.
There aren't any special build settings in the podspec so it should work as it is. Can you send me a stripped down version of your XCode project (along with a podfile) that reproduces the issue so that I can have a look?

Gah!

Well, that's good to hear.


Error Take photo xaomi

when a photo is taken in a xaomi A1, the image is not saved and afterwards it doesn´t take any more photos

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


Make the task termination order deterministic

This PR adds support for making the task termination order deterministic when scaling down.
Please refer to #2264 for more details. (closes #2264)

@aaronlehmann Thank you for your feedback. PR is updated!

LGTM
Thank you for making the changes!

What's the current state of this PR? Would love to see this feature implemented.

@nishanttotla
Who else do I need approval from / what is the process left to get this PR merged?

@sungwonh I think first of all you need to rebase as there are conflicting files.

Rebased!

@anshulpundir updated according to your comments.


Warning fixes and other cleanups

Hi @mvdan, looks good! Thanks!
I would like to keep the (currently) unused test helper functions, so if you can revert deleting them I'll merge the rest of this PR 👍

@mvdan I still would like to pull this one in, but you would first have to rebase it and revert the part where you delete the unused test functions. If you can do that, that would be great and I'll merge this PR right after... Thanks!

I just went on holidays right after opening this, so give me a couple of days :)

Sure, no rush! Thx 😀

@svanharmelen done.


Menu for DecoratedWindow

The decorated window does not support the default menu - IntelliJ does have something as replacement as you can see in the following screenshots.
Is something like this also possible with this library? I think not... Please let me know if it is possible or consider this as a feature request.
Menu
Clicking the menu icon with the 3 lines opens the menu inside the decorated title bar.

You can put whatever you want in the window decoration, including buttons that have a text label and when clicked open a PopupMenu. We're not planning to implement this further for now, but contributions are welcome as usual

That's what I'm doing right now, but it behaves a little buggy... PopupMenu does not open immediately if it is placed inside the TitleBar - I always must move the mouse after clicking and only afterwards the popup opens.
Code looks like following:
TitleBar(Modifier.newFullscreenControls()) {
    Row(
        modifier = Modifier.align(Alignment.Start),
        verticalAlignment = Alignment.CenterVertically
    ) {
        Dropdown(
            modifier = Modifier.height(30.dp),
            menuContent = {
                selectableItem(
                    selected = false,
                    onClick = { }
                ) {
                    TitleMenuItem("Sub Menu", null)
                }
            }
        ) {
            TitleMenuItem("Test Menu", null, false)
        }
    }
}

@Composable
private fun TitleMenuItem(title: String, imageVector: ImageVector?, popup: Boolean = true) {

    val jewelTitleTheme = org.jetbrains.jewel.foundation.theme.JewelTheme.defaultTitleBarStyle
    val contentColor = org.jetbrains.jewel.foundation.theme.JewelTheme.contentColor
    val foreground = if (popup) contentColor else jewelTitleTheme.colors.content

    Row(
        horizontalArrangement = Arrangement.spacedBy(4.dp),
        verticalAlignment = Alignment.CenterVertically,
    ) {
        if (imageVector != null) {
            Icon(
                modifier = Modifier.size(30.dp).padding(4.dp),
                imageVector = imageVector,
                contentDescription = null,
                tint = foreground
            )
        } else {
            if (popup) {
                Spacer(modifier = Modifier.size(30.dp).padding(4.dp))
            }
        }
        Text(title)
    }
}

This should work — if mouse events are lost, this might be somewhat related to #368, but right now we don't have bandwidth to look into decorated window as we're focusing on other priorities. The primary maintainer of decorated windows is @devkanro but he's been unresponsive for months... We might have to deprecate the whole API if he doesn't come back to help because he's the only one familiar with it.


Did css-modules be removed?

I can't find it in  lastest version.

Yes. See https://github.com/davezuko/react-redux-starter-kit/issues/787 and https://github.com/davezuko/react-redux-starter-kit/pull/1000

@tiagoalvesdulce got that, thanks😀

But why? Does css modules isn't a better choice?