fix(jsonrpsee): use proper tls feature, with custom tls cfg

depends on https://github.com/paritytech/jsonrpsee/pull/1419
fixes https://github.com/fedimint/fedimint/pull/5441#issuecomment-2161666413

fyi @tvolk131

I'm still unsure why CI is failing, and unable to download the new version 🤔


Revert e409112 @wordpress/scripts issue

The commit e409112 needs to be reverted once this PR has been released in an updated @wordpress/scripts release: https://github.com/WordPress/gutenberg/pull/19306

Fixed via f9a735a


no detected boxes on image

hi,
There was a problem running the darknet_ros_fp16 that no detected boxes on image.And the console output Object: ,it seem that there is no detection at all.How can i fix this problem?thank you!
ubuntu 20.04 ros2-foxy

Assuming you can run it on AlexeyAB/darknet and it doesn't work with my darkent_ros package,
If you are using a custom dataset, you will need to make changes to files like yolov4-tiny.yaml.
Please make sure that the ****.cfg and ****.weights used in the study are correctly named.

Hi, I have the same issue.
I think it's because I'm using a .pt file instead of a .weight. How can I transform .pt into the corresponding .weight file.


Remove uses_defaults from ServiceProviderConfig endpoint

This PR remove the uses_defaults attribute when return the JSON at the /ServiceProviderConfig. The response is now according to the schema as defined in https://datatracker.ietf.org/doc/html/rfc7643#section-5.
Find the discussion at https://github.com/RIPAGlobal/scimitar/issues/144.

RIPA couldn't survive the dire economic conditions caused by our current administration's ill-advised austerity-based approach to financial "management" and closed down a few weeks ago. I don't know if I'll be able to keep maintaining this software in my free time; I'd certainly have to fork it to my own repo and publish from there.
I'll look at this some time - probably new year - sorry for the delay; I'm sure you can understand it given the circumstances.


refactor(build): tsconfig

references #722
Removes dedicated tsconfig package in favor of a top-level base tsconfig.json that's shared across all packages in the workspace, ensuring all packages in the workspace start with a consistent base TypeScript configuration. This promotes consistency and reduces duplication. Each package still maintains it's own tsconfig.json, but uses inheritance to extend the top-level tsconfig.json and overrides compiler settings as necessary for the specific package.

This is another one, where the previous config seemed ok (and more standard to turborepo).

What's the status of this and #782? Should it be made merge-ready or close? @grod220 @turbocrime

I'm not seeing the benefit of these. Think we can close until we find a good reason later.


Improve handling of key material in KMS

Type of change

Refactoring

Description
These changes seek to minimise the number of copies of key material held in proxy process memory, and to not be so reliant on timely GC to clean up key material that is no longer referenced. Obviously it can't prevent the key material from existing in the plain within the proxy process, but we can seek to manage this material more carefully.

Move the DestroyableRawSecretKey to the kms module, so it can be used by KMS implementations
Use DestroyableRawSecretKey in the Kms interface and fix existing KMSes and tests.
Avoid creating a String containing the plaintext key material in the Hashicorp impl by having Jackson convert the Base64 data to a byte[] which we then wrap in a DestroyableRawSecretKey.
Additionally, zero the HTTP buffer after Jackson has done the deserialization.

Use DestroyableRawSecretKey in the Kms interface and fix existing KMSes and tests.

Can you tell me more the motivation for this part of the change?  We tend to prefer APIs defined in terms of  interfaces rather than concrete implementations so seeing DestroyableRawSecretKey (class) across the API saddens me.
Couldn't the API have remained in terms SecretKey?   Kms interfaces would have the obligation to return SecretKeys that are destroyable/support encoded, but exactly how they choose to do that is a choice for them.  Our Kms impls would use DestroyableRawSecretKey.

Couldn't the API have remained in terms SecretKey? Kms interfaces would have the obligation to return SecretKeys that are destroyable/support encoded, but exactly how they choose to do that is a choice for them. Our Kms impls would use DestroyableRawSecretKey.

If it was purely my decision I think I'd stick with using DestroyableRawSecretKey, but I've reverted this part. It's a bit of a compromise.

From the PoV of the API contract, SecretKey is necessary but not sufficient for the guarantee I'd like to make: That all our keys are destroyable and get destroyed as soon as they're no longer needed (which is determined by the caching configuration).

In terms of implementation it means we now end up copying the SecretKey provided by the Kms into a DestroyableRawSecretKey in the DekManager, where before we could just use it. It also means we're using the toDestroyableKey() method in the production code (before it was only tests), which means we now ought to log if a key destroy() failed (because that particular KMS didn't follow our advice; this just wasn't possible before). In turn this means we grow a dependency from the kms module to slf4j.

None of these things are deal-breakers, but I think the trade off is more nuanced than 'interface is better than class'.
I also removed the overriding of equals() and hashCode(). They were only used in the tests and the implementation was a bit icky: Calling destroy() would change the hashCode(), potentially breaking use of DestroyableRawSecretKey as HashMap keys.

Couldn't the API have remained in terms SecretKey? Kms interfaces would have the obligation to return SecretKeys that are destroyable/support encoded, but exactly how they choose to do that is a choice for them. Our Kms impls would use DestroyableRawSecretKey.

If it was purely my decision I think I'd stick with using DestroyableRawSecretKey, but I've reverted this part. It's a bit of a compromise.

From the PoV of the API contract, SecretKey is necessary but not sufficient for the guarantee I'd like to make: That all our keys are destroyable and get destroyed as soon as they're no longer needed (which is determined by the caching configuration).
In terms of implementation it means we now end up copying the SecretKey provided by the Kms into a DestroyableRawSecretKey in the DekManager, where before we could just use it. It also means we're using the toDestroyableKey() method in the production code (before it was only tests), which means we now ought to log if a key destroy() failed (because that particular KMS didn't follow our advice; this just wasn't possible before). In turn this means we grow a dependency from the kms module to slf4j.

None of these things are deal-breakers, but I think the trade off is more nuanced than 'interface is better than class'.
I also removed the overriding of equals() and hashCode(). They were only used in the tests and the implementation was a bit icky: Calling destroy() would change the hashCode(), potentially breaking use of DestroyableRawSecretKey as HashMap keys.

Thanks for the explanation. On balance, I have preference for the way the code is now, but if others feel strongly for DestroyableRawSecretKey being the API fine.


cmake: Update update_deps

CI Vulkan-Tools build queued with queue ID 1119.

CI Vulkan-Tools build queued with queue ID 1119.

CI Vulkan-Tools build # 1061 running.

CI Vulkan-Tools build # 1061 passed.


open igv-webapp site (https://igv.org/app/), but this web is not displayed correctly.

Hi IGV team, I try to open igv-webapp site (https://igv.org/app/), but this web is not displayed correctly.
I use the edge browser, and I also tried chrome browser.

Best regards,
sunhuaibo

Is this because I can‘t enable ”Enabling Google access“？

Blocking google access could be a problem,  but the more immediate problem is you aren't able to load many required files, for example the bootstratp css and js.    If you can't load these files you won't be able to use https://igv.org/app.

Thinks

Closing as there is nothing we can do about this.


introduces KubeAPIReadinessChecker used by startup monitor to assess Kube API server readiness/health condition

this PR implements the following checks

doETCDHealthCheck for performing an HTTP check against healthz/etcd endpoint

doKubeHealthCheck for performing an HTTP check against health?verbose=true endpoint to assess overall Kube API condition

xref: openshift/enhancements#833

/assign @sttts

LGTM

/retest
/lgtm
/approve

/retest


[Migrated] Zappa should not arbitrarily exclude docutils.

Originally from: https://github.com/Miserlou/Zappa/issues/1829 by danverbraganza

Context
You might write a Lambda that has an actual, runtime dependency on docutils. Perhaps a service that interprets ReST, or surfaces its own autodocs at runtime.
Currently, Zappa excludes that module.
This exclusion was added in https://github.com/Miserlou/Zappa/commit/672d85fa9c94d349ae8b56b1242d04cb7264f341
This exclude could be easily overridden in excludes today.
Expected Behavior
Zappa should not zip-exclude docutils.
Actual Behavior
Zappa does zip-exclude docutils.
Possible Fix
Allow docutils
~Pull Request Incoming.~
https://github.com/Miserlou/Zappa/pull/1830
I'm leaning towards this because I believe that docutils is rare as an... "accidental" dependency of real Python projects. I'm willing to be convinced otherwise.
Allow minify to be set.
The alternative implementation would be to actually plumb through "minify" through from args, so that it can be disabled when needed. This alternative is a good idea anyway, but I think it doesn't defeat the arguments that excluding docutils is peculiar.
Steps to Reproduce

In your serverless function, have import docutils
Watch it die.

Your Environment

Zappa version used: Present in Zappa 0.48.1
Operating System and Python version: Linux, 3.6
The output of pip freeze:
At least:
docutils==0.14

minify enabling: https://github.com/zappa/Zappa/pull/986


Titles with pipe character break permalink creation

These titles translate into unusable permalinks which 404
https://alonetone.com/joeoctave2/tracks/afo-kedi-||-crudemusik.com

Is it possible these permalinks were changes by the migration without expiring the cache? In other words, did you flush memcached on the server?

Ah, the problem is the dot in the permalink and not the pipes. Rails routing thinks it's a format.

I tried to change the constraints for the request path segment but that broke the MP3 URL because that actually uses the dot to include the format. Instead I decided to disallow dots from the permalink. PR incoming in 3… 2… 1….


[Microsoft.App] Remove unsupported values from unreleased MaintenanceConfiguration resource type

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

We missed to include https://github.com/Azure/azure-rest-api-specs/pull/31285 to https://github.com/Azure/azure-rest-api-specs/pull/31066

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.App

We already get arm sign off in https://github.com/Azure/azure-rest-api-specs/pull/31285. The api version 2024-10-02-preview is just merged and never release any SDK released. There should be no breaking change.

/azp run


[BUG] Azure-Docker is not finding any Functions

Investigative information
Please provide the following:

Timestamp: February 2nd, 2024, 08:00
Function App name:
Function name(s) (as appropriate): ping, translate, parse_video_trigger
Core Tools version: 4.0.5455

Repro steps
Provide the steps required to reproduce the problem:

func init
add new HTTP/blob triggers
build a docker image and run it with docker run -it --rm -e  -p 8080:80  <imgtag>
no functions detected in output logs.

Expected behavior
Provide a description of the expected behavior.
all functions should be discovered

Actual behavior
No Job-Functions found, but when I ran the function using func start all of the functions were recognized and working when I called them locally.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module-related issues.
azure-functions==1.18.0
azure-functions-durable==1.2.8

Related information
Provide any related information
My docker file:
FROM mcr.microsoft.com/azure-functions/python:4-python3.11-slim

ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
    AzureFunctionsJobHost__Logging__Console__IsEnabled=true \
    AzureWebJobsFeatureFlags=EnableWorkerIndexing

RUN apt-get update && apt-get install -y ffmpeg gcc portaudio19-dev python-all-dev libmagic-dev ca-certificates sox && rm -rf /var/lib/apt/lists/*

COPY requirements.txt /
RUN pip install --no-cache-dir -r /requirements.txt
RUN pip install --global-option='build_ext' --global-option='-I/usr/local/include' --global-option='-L/usr/local/lib' pyaudio==0.2.14

COPY . /home/site/wwwroot

I also tried following the suggestions such as adding different combinations of environment variables in other similar issues such as:
https://github.com/Azure/azure-functions-python-worker/issues/1384
https://stackoverflow.com/questions/75519932/azure-function-python-model-2-in-docker-container
The only difference for me from those is that I'm using Python 3.11 I guess?

Hi @yovelcohen
I followed the repro steps listed using the provided requirements.txt and dockerfile content, but didn't have the same issue. I tried with HTTP triggers and using a Durable Functions app.
I did need to add the AzureWebJobsStorage environment variable to my Dockerfile. Can you try adding that and see if that fixes the issue?
ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
    AzureFunctionsJobHost__Logging__Console__IsEnabled=true \
    AzureWebJobsFeatureFlags=EnableWorkerIndexing  \
    AzureWebJobsStorage=...


added COMPASS env variable

mongoose is connecting to Atlas || compass. In my local compass I've named the database something different than yours and it has to be changed every time there is a push.
On Jul 24, 2023 at 11:42 AM -0700, Kirk @.***>, wrote:

@BanditHeelerPDX commented on this pull request.
What is the COMPASS variable being used for? Since we have independent .env files - none of us will have the other half of this code and there is no info in the commit comment.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


move auth routes to /dashboard

Moved the following routes inside /dashboard so that we can run a proxy to those routes when the site moves to webflow.
https://livepeer.studio/dashboard/register
https://livepeer.studio/dashboard/login
https://livepeer.studio/dashboard/forgot-password
https://livepeer.studio/dashboard/verify
https://livepeer.studio/dashboard/verify-new-email

Maybe let's add redirects for the old routes on this app too, so this can be deployed incrementally prior to the Webflow change?

@iameli I put these in place. Are there any others I missed?

@adamsoffer Ah nice I missed that. Will redirects using that mechanism keep query strings in place? Because that'll be needed for email verification and stuff to work. Assuming it does, we're probably good

@adamsoffer Ah nice I missed that. Will redirects using that mechanism keep query strings in place? Because that'll be needed for email verification and stuff to work. Assuming it does, we're probably good

@iameli just made an update to the redirects to ensure query strings are still in place.


README on npm broken

As of january 2023, https://www.npmjs.com/package/start-server-and-test does not show the readme anymore

@fwolfst
This is probably not specific to this package and it has been observed happening from time to time. It's a problem with the https://www.npmjs.com/ website (or the Cloudflare CDN), so it can't be fixed here. See also the discussion ...

https://github.com/npm/feedback/discussions/840

It's currently working for me. In case it's a cache problem, you can try reloading your browser with Shift + F5. That may fix it for you.


Kubernetes: set secret immutable by default for version >= 1.21

Fixes #1090
Signed-off-by: Furkan<EMAIL_ADDRESS>Co-authored-by: Batuhan<EMAIL_ADDRESS>Co-authored-by: Erkan<EMAIL_ADDRESS>

Not sure whether setting immutable: true by default is good practice or not. Feel free to drop your feedback here, so we can add smth like --immutable flag to trigger the condition.


numbering patches for few versions

https://github.com/yalov/SpeedUnitAnnex/releases
the patch v<IP_ADDRESS> (KSP 1.4.5) does not show up in the ckan version list.
the patch v<IP_ADDRESS> (KSP 1.5.1) got 1.4.0-1.4.9 range

Actually the one that got indexed is <IP_ADDRESS>, but it got listed as <IP_ADDRESS> because that's the version it has on GitHub.

The bot only looks at the first asset in a release. Don't try to combine multiple releases into one.

I separated them, will they be scanned without epoch?
I already was combining 1.1.3/1.1.4 before, and it was ok...

<IP_ADDRESS> will be scanned by the bot the next time it runs. <IP_ADDRESS> will need to be added manually, I'll take care of that in a couple of minutes.
1.1.3 and 1.1.4 were indexed from SpaceDock, where those versions were not combined:

(You switched to GitHub after that, in #6422.)

ok, thanks

@HebaruSan  <IP_ADDRESS> appears, but has not right ksp version (not 1.5.0-1.5.9), will it be updated later or also need to be changed manually?

Give the bot 4 more hours to run.


Java 11

DO NOT MERGE: need #35 to be merged first.

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


feat: Minor optimization for contact synchronization

Description
This PR does a minor improvement to the contact synchronization by converting the matching from O(nm) to O(n+m). This won't be much effective on small sets of dhis2 users and rapidpro users, but will be effective on large sets.

Close stale PR.


⚠ Bofrost.at has degraded performance

In 75adff4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1299 ms

Resolved: Bofrost.at performance has improved in 0c50bcb.


Demo for DeSci Boston (Sunday)

2 min video
Homepage demo
"Python script, runs great locally, takes forever, have to upload stuff"
"Dataset is on IPFS"
"Watch me take the existing script (containerize it), and now execute it on Bacalhau, and look! It did all this work that normally took 1h and did it in 1 minute (sharding)!"
"Plus, it stored data on Filecoin/IPFS making it reusable"

saving time with ingress/egress
my complicated script ran somewhere else

https://filecoinproject.slack.com/archives/C02RLM3JHUY/p1660740489937529


Adds ButterBean and Hybrid Core frameworks

This adds the two frameworks that I manage: ButterBean and Hybrid Core.

Thanks for PR-ing! For the hybrid framework, could you please come up with a descriptive description. It should be a short one liner that will help developers to understand what's in the box. Though I'd love to have themes with superpowers :)

I thought about "Does a lot of cool sh*t", but figured that might not be appropriate. :)
I'll think on it. Maybe something along the lines of "Theme development toolbox."

@justintadlock "Theme development toolbox." is good. Please update, and I'll merge.

@justintadlock the frameworks are now listed on the site https://includewp.com/
Here's the Hybrid page: https://includewp.com/hybrid-core/#focus
The scraper didn't find any matching plugins/themes on .org for ButterBen. It could be one of the following:

The framework isn't used by any .org plugin / theme.
The framework is loaded using TGMPA (not yet recognized by IncludeWP).
Something wrong with the thumbprint.

If you know there's a plugin/theme using it for sure, please share the URL so we can check why it wasn't recognized.

ButterBean 1.0 actually just got officially released today.  I'll have a plugin in the repo that uses it before the end of the week.


Build for Mac and Windows in Github Actions

description

[ ] describe solution here ..

checklist

[ ] compiles (cabal v2-build or stack build)
[ ] tests run successfully (cabal v2-test or stack test)
[ ] documentation added
[ ] link to an issue
[ ] add milestone (the current sprint)

for macOS depends on #609

Thank you @newhoggy, I'm testing fixes for macOS and Windows in a different branch on top of this one.


Updating pnpm flags in example tests.

We're no longer locking to pnpm@6 in our example tests. Instead they are using, the version in the example itself.
Our examples are on pnpm@8. It looks like the pass-through flagging for pnpm run has changed.

Continuing to move through changes to our examples tests. Getting a lot more passes now!
Merging past failing yarn tests now...


Fallback divine gemstone stats (feedback?)

This temporarily solves the issue, but I would like some feedback.
Basically in game there's some DIVINE rarity items that aren't supposed to exist, mostly dungeon armor like Necron or Shadow Assassin, example:
https://sky.shiiyu.moe/stats/Bucklez/Coconut#Armor

What I think happened is that admins didn't expect/know this items existed so they didn't code in the values for DIVINE stats in gemstone that can't be applied to Divan's Drill (the only item that should have DIVINE rarity as of right now).
In game that item gems use the value as if the item was a a mythic rarity, so as a temporarily solution I coded that if the item is DIVINE and we are missing the gemstone stat value it tries to fallback to MYTHIC.
What do you think?
Instead of doing this we could just hardcode the "fake/temp" values where they are missing, so like Flawless Sapphire will give the same stats in both mythic and divine. But doing this will probably mean that in the future we might not be sure which values were added temporarily and which are the definitive ones... with the risk of forgetting to update some.

This https://discord.com/channels/738971489411399761/739600697057607783/888100138822799460 confirms my theory

i think the fallback would work fine. do you think admins would revert these items?

i think the fallback would work fine. do you think admins would revert these items?

Not sure honestly, like they didn't revert exotics yet... but they reverted started warden helmets recently so who knows.


Update to the new toolbox icon

This uses the fluent ui icon, which is under the MIT license, so we are free to modify it.
Also removed reference to the noun project

Please also add a text file in the assets folder that explains including URI and names of where you obtained the icons you used to create your images.


Make command handler reflection more flexible

Hi
I want to write a small event souring framework based on the laravel 5 command and event system.
For that framework I want to have Aggregate classes, which handle multiple commands and events for their type, for example UserAggregate should have:
public handle(RegisterUser $command);
public handle(SignUserIn $command);
But the reflection to search the command handler searches for a "[command name]Handler" class.
And there is no way to change this, correct? (Nothing found in the documentation)
Kind regards

Unfortunately we cannot process support requests here, thought is is definitely configurable. Take a look at the internals of Dispatcher::simpleMapping and just replicate that to suit what you need.

https://github.com/laravel/framework/blob/5.0/src/Illuminate/Bus/Dispatcher.php#L371

Thanks, this would be a great hint for the docs.


Introduce 'username' as a unique field in place of ObjectId in all user related routes

username is a more appropriate field for every user to remember. For example, when visiting a user profile, someone might enter telemetryblog.in/{at}utkarsh.pant and expect to see that profile page. Thus all back end routes should be updated to match the case when username is known.

Completed and working.


Problem to list files when deploy

Hey guys, really good work with this lib, it was being very useful to my project.
I´m facing a problem for weeks and have no solution yet. I would like to ask anyone who can help me with this.
I have a FTP server with so many files in there, my goal is to build a interface for manipulate these files. I want to search, download and delete specific files. I´m using Node to create a Express application that get the files on FTP and send them to my frontend builded with Vue.
My local tests are working very well, as I want. However, when I deploy my server (already tested different plataforms) I cannot reach any file. I can connect with the FTP and the server return a positive response, but when I use Get method on the source directory all I get is an empty array. There isn´t any error or exception, it just returns nothing.
I´ll let here the config of my connection and the method I´m using. Any doubts, don´t hesitate to talk to me, I´ll be so grateful with your help.
const info = {
    host: process.env.FTP_HOST,
    user: process.env.FTP_USER,
    password: process.env.FTP_PASSWORD,
    connTimeout: 21000,
    pasvTimeout: 21000,
    pasv: true
}

export async function listRaw(): Promise<Conteudo[]> {
    const ftp = new PromiseFtp();

    return new Promise((resolve, reject) => {
        ftp.connect(info)
            .then(function(serverMsg) {
                console.log(serverMsg);

                return ftp.list("/");
            })
            .then(function(list: Conteudo[]) {
                ftp.end();

                if (!list) {
                    return;
                }

                resolve(list);
            });
    });
}

I recently discover the problem is in our FTP server. It only accepts connection from regional IP´s, when I deploy my app, the virtual machine is on other country and the FTP block it.
I´ll let it here, in case of helping someone else.


Create laurea.txt

Another pull request for Laurea was done just few days ago and the domain is working now


lint: IFD detection

“Input from derivation” means that a nix build generates a .nix file (e.g. through downloading it with fetchFromGitHub and then importing that.
This clogs the evaluator, so usually it’s not a good idea.
IFD nix files have the property that they come from /nix/store/…, which means we can detect that where we construct LogDatum::CopiedSource.
cc @Jeschli

We explicitly should support IFD and handle it nicely.

Both are not at odds with each other, not allowing IFD is policy, so a linter is still valuable.

We have two issues about better IFD support:

https://github.com/target/lorri/issues/31
https://github.com/target/lorri/issues/22


Customizing the sty;es behavior of header (rmdp-header-values)

Hi. I need the month and year selectors become dropdown. Something like image below. Is there a way to achieve this? Thanks in advance

No, Unfortunately, this is not possible :(


Add github-actions to greet everytime a pr is merged successfully

Is your feature request related to a problem? Please describe.
No such problem
Describe the solution you'd like
I would like to add github-actions to send greetings to all the new contributors who are contributing to this project for the first time.
Resource that i would like to use -
actions/first-interaction@v1

Go ahead @AB-san

Okay, I changed the issue title. go ahead with this

Okay, I changed the issue title. go ahead with this

Okay ,sure


[DO NOT MERGE] VA List Api version edit

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@talhers @yaakoviyun

Automation for azure-sdk-for-js

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

Reassigning due to some other deliverables

@t-robalt LGTM - but what's the purpose of deleting a bunch of examples?

@jianghaolu The List method of database and managed database moved to other api-versions, so their examples in 2018-060-01 are no longer necessary

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

@jianghaolu @jaredmoo was this supposed to be merged?

Yep, the code should have reached production by now.
Sent from Outlook

מאת: Deepak Shankargouda<EMAIL_ADDRESS>נשלח: יום חמישי 01 נובמבר 2018 19:42:54
אל: Azure/azure-rest-api-specs
עותק: Yaakov Iyun; Mention
נושא: Re: [Azure/azure-rest-api-specs] [DO NOT MERGE] VA List Api version edit (#4257)
@jianghaoluhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjianghaolu&data=02|01|yaiyun%40microsoft.com|f9bae65aba284278574a08d640217436|72f988bf86f141af91ab2d7cd011db47|1|0|636766909755353960&sdata=sT%2F3DiwFoVj%2BjxS68QTHGc1tI9%2BAwy6OyrXecBztkKE%3D&reserved=0 @jaredmoohttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjaredmoo&data=02|01|yaiyun%40microsoft.com|f9bae65aba284278574a08d640217436|72f988bf86f141af91ab2d7cd011db47|1|0|636766909755353960&sdata=XnAikyaA%2B0ClgkRm5qfvHFHErgBXAiwVPtuzgRF9KnQ%3D&reserved=0 was this supposed to be merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F4257%23issuecomment-435120083&data=02|01|yaiyun%40microsoft.com|f9bae65aba284278574a08d640217436|72f988bf86f141af91ab2d7cd011db47|1|0|636766909755363969&sdata=ePAWxQ9yQaJmMN409Xjg%2BQNNglg4KdCpKJlT1afpPEM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALNgub5go2bB2W-QCrLjSMQX60e2EI4vks5uqzKegaJpZM4XtLng&data=02|01|yaiyun%40microsoft.com|f9bae65aba284278574a08d640217436|72f988bf86f141af91ab2d7cd011db47|1|0|636766909755363969&sdata=khmXiF6humGz8XO%2FY6YD%2F62Q5medes5j2E2Beax6bfU%3D&reserved=0.

Thanks for confirming, I was concerned because of the title of the PR 👍


Corrected introduction to range field lookups docs.

"There are three" has been untrue since 24b9f5082344a127147266dd52d5d2dcd1c9cb44.

Thanks :+1:


Formalize annotated name parsing in DASH.

Use a normalized way to parse the annotated name in p4 files.
This change will not change any generated files as shown below.
r12f@r12f-dl380:~/data/code/sonic/DASH/dash-pipeline
$ diff SAI/SAI/experimental/ ~/data/code/sonic/DASH-exp/dash-pipeline/SAI/SAI/experimental/

r12f@r12f-dl380:~/data/code/sonic/DASH/dash-pipeline
$ diff SAI/lib ~/data/code/sonic/DASH-exp/dash-pipeline/SAI/lib

Hi @r12f I appreciate this work, but it might be a step in the wrong direction. I am wondering if we really ought to deprecate the P4 entity naming convention e.g. "@name(x|y)" entirely and follow-through on https://github.com/sonic-net/DASH/issues/276 where we agreed that long-term, we should not use a naming convention at all, instead use explicit annotations e.g. "@Sai[a=b,x=y]".
@marian-pritsak took initial steps towards this in https://github.com/sonic-net/DASH/pull/358. See https://github.com/sonic-net/DASH/blob/main/dash-pipeline/bmv2/README.md#p4-annotations-for-sai-code-generation also.
That being said, if this is just cleanup and uniformization, I see no objections to it, but it is kind of perpetuating a convention we'd rather abandon.
Please take a look at the conversation tail above and let us know what you think!

Hi @chrispsommers , yes. I totally agree with you! This is just a clean up work in case things get even worse and we should definitely move the annotation to use @Sai instead.
And thanks for sharing the docs! Once this is done, I will try to make the work to move these annotations to @Sai as the next step.

in case things get even worse
LOL!

OK, with that in mind, I am in favor of this. Thanks for considering taking the annotations in the right direction when time allows. We all appreciate the energy you are bringing to this project!

np at all! and I also really appreciated reviewing this PR in the weekend too!

in case things get even worse
LOL!

I cannot believe myself used almost half of day just trying to sort the naming out..... XD


Fix: add the cross-env package to dependencies

add the cross-env package to dependencies
[√ ] Bug Fix
[ ] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[√ ] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[ ] Tests for the changes have been added

Description
please describe the changes that you are making
for features, please describe how to use the new feature
please include a reference to an existing issue, if applicable
Does this PR introduce a breaking change?
[ ] Yes
[√ ] No

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

@huan Can you review it for me when you have time?

Please make sure the following requirements have been met for your PR before we can continue reviewing it:

You have signed the CLA by clicking the [CLA | not signed yet] button from the comments.
The PR has passed all the CI tests and turns green. (you can execute all tests locally by running npm test)

@huan
Thank you for your reply.
The CLA has been completed, but the github actions test has not yet been completed.

Hi @timor-m , I think the cross-env and npm-run-all will be installed even without the direct dependencies. Please correct me if I'm wrong.
This PR includes many unrelated changes, including the version upgrade. Upgrading the version to the latest stable version is great, but the best practice would be to create a separate PR to do that.
I will close this PR for now, and you are welcome to create an new one by following the best practices.


[occm] API requests & Loadbalancer reconciliation metrics

What this PR does / why we need it:
This PR implements metrics for loadbalancer reconciliations:

cloudprovider_openstack_reconcile_duration_seconds
cloudprovider_openstack_reconcile_total
cloudprovider_openstack_reconcile_errors_total

and metrics for OpenStack API requests:

openstack_api_request_duration_seconds
openstack_api_requests_total
openstack_api_request_errors_total

Which issue this PR fixes(if applicable):
fixes #912
Special notes for reviewers:

Metrics are exposed to https://localhost:10258/metrics.
I would recommend to add the following arguments when running OCCM.
--authorization-always-allow-paths=/metrics
--secure-port=10258

Release note:

[openstack-cloud-controller-manager] Added metrics support for loadbalancer reconciliations and OpenStack API requests.

Sean Schneeweiss<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

/ok-to-test

/retest

openlab/cloud-provider-openstack-multinode-csi-migration-test is failing maybe because of:

Events:
  Type     Reason       Age                  From                                                               Message
  ----     ------       ----                 ----                                                               -------
  Warning  FailedMount  56s (x10 over 5m5s)  kubelet, ubuntu-xenial-citynetwork-citynetwork-openlab-0000145850  MountVolume.SetUp failed for volume "pods-cloud-data" : hostPath type check failed: /var/lib/cloud/data is not a directory
  Warning  FailedMount  47s                  kubelet, ubuntu-xenial-citynetwork-citynetwork-openlab-0000145850  Unable to attach or mount volumes: unmounted volumes=[pods-cloud-data], unattached volumes=[csi-cinder-node-sa-token-d8qlb kubelet-dir pods-cloud-data pods-probe-dir secret-cinderplugin socket-dir registration-dir]: timed out waiting for the condition

openlab/cloud-provider-openstack-e2e-test-csi-cinder and openlab/cloud-provider-openstack-acceptance-test-csi-cinder are failing with:

/bin/bash: line 84: /var/lib/cloud/data/instance-id: No such file or directory

openlab/cloud-provider-openstack-acceptance-test-csi-manila is failing with:

Setting up the hosts
... this takes a few seconds (logs at logs/devstack-gate-setup-host.txt.gz)
./safe-devstack-vm-gate-wrap.sh: line 578: /tmp/ansible/bin/ara: No such file or directory
gzip: /home/zuul/workspace/logs/ara: No such file or directory
*** FAILED with status: 127

/test cloud-provider-openstack-acceptance-test-csi-cinder

/test /test cloud-provider-openstack-acceptance-test-csi-cinder

/test cloud-provider-openstack-acceptance-test-csi-cinder

@seanschneeweiss Fixed the following failure in openlab

/bin/bash: line 84: /var/lib/cloud/data/instance-id: No such file or directory

/test cloud-provider-openstack-e2e-test-csi-cinder

@ramineni Great news, thank you very much.
/test cloud-provider-openstack-acceptance-test-csi-manila

@ramineni could you trigger the missing tests? Seems that I cannot do that without running a retest.

/test pull-cloud-provider-openstack-check

/test cloud-provider-openstack-acceptance-test-csi-manila

@seanschneeweiss Adding it as separate comment should do the trick, combining with comments doesn't work sometimes. try that maybe works

/test cloud-provider-openstack-acceptance-test-csi-manila

The test cloud-provider-openstack-acceptance-test-csi-manila seems to be failing with
2020-09-02 12:08:25.150904 | ubuntu-bionic | Successfully installed virtualenv-16.7.10
2020-09-02 12:08:26.114344 | ubuntu-bionic | Running virtualenv with interpreter /usr/bin/python3.6
2020-09-02 12:08:26.584279 | ubuntu-bionic | Traceback (most recent call last):
2020-09-02 12:08:26.584584 | ubuntu-bionic |   File "/usr/local/lib/python3.6/dist-packages/virtualenv.py", line 24, in <module>
2020-09-02 12:08:26.584690 | ubuntu-bionic |     import distutils.spawn
2020-09-02 12:08:26.584883 | ubuntu-bionic |   File "/usr/local/lib/python3.6/dist-packages/_distutils_hack/__init__.py", line 83, in create_module
2020-09-02 12:08:26.585760 | ubuntu-bionic |     return importlib.import_module('setuptools._distutils')
2020-09-02 12:08:26.585971 | ubuntu-bionic |   File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
2020-09-02 12:08:26.587034 | ubuntu-bionic |     return _bootstrap._gcd_import(name[level:], package, level)
2020-09-02 12:08:26.587208 | ubuntu-bionic | ModuleNotFoundError: No module named 'setuptools'

This seems to be related to an old pip issue https://github.com/pypa/pip/issues/6264.
A workaround according to https://github.com/pypa/setuptools/issues/2353#issuecomment-684452550 could be to add export SETUPTOOLS_USE_DISTUTILS=stdlib before pip3 install when executed by devstack-vm-gate-wrap.sh#L513.
So maybe it would be required to add export SETUPTOOLS_USE_DISTUTILS=stdlib to the cmd section of the install-devstack zuul-job to workaround.

/test cloud-provider-openstack-multinode-csi-migration-test

/test cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

@seanschneeweiss thanks for working on this PR, as I'm not very familiar with the best practice of introducing metrics support to the k8s service, it may take some time for me to review. I'm happy if other people from the maintainer team are confident for this.

/test cloud-provider-openstack-acceptance-test-csi-manila

/test cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

/test cloud-provider-openstack-acceptance-test-csi-manila

/test cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

/test cloud-provider-openstack-acceptance-test-lb-octavia

@lingxiankong is this PR ready to be merged, or is anything missing I could provide?

/lgtm
@seanschneeweiss Do you mind adding some doc for this?

@seanschneeweiss Do you mind adding some doc for this?

@lingxiankong Should the documentation be added to a new markdown file e.g. /docs/metrics.md or to the existing /docs/using-openstack-cloud-controller-manager.md? Should I create a separate PR? Is there any existing documentation related to this, or maybe a template/guideline?

/approve
I think we can do a followup PR and not blocking this..

@seanschneeweiss please help to create a new PR related the doc and we can follow up discussion there, thanks

@seanschneeweiss Do you mind adding some doc for this?

@lingxiankong Should the documentation be added to a new markdown file e.g. /docs/metrics.md or to the existing /docs/using-openstack-cloud-controller-manager.md? Should I create a separate PR? Is there any existing documentation related to this, or maybe a template/guideline?

@seanschneeweiss @sbueringer I think this is missed. Could you add the doc on how to use this . Adding new file docs/metrics.md sounds good to me , and link it from the main doc.  You could receive more comments once you propose the PR. @lingxiankong do you have any other suggestions?

Agree with @ramineni, besides, I'd like to see several things in the doc:

What metrics are supported? Which binaries are related?
How to config (if applicable) to make the metrics work? How to get metrics?
Metric examples

I will create the PR soon, thank you for the feedback.


Add openvpn access groups resource

resource - https://openvpn.net/cloud-docs/developer/openvpn-api.html#UUID-c0946de0-43ab-347e-b5db-4836cb02dea9
api is available

@vladimir-kozyrev @michaelfmnk can I work on this?

there is an open issue, which is for service and accessgroups - #14
I see that the changes for service is already being added. hence raised a new issue for just accesgroups. let me know if I should close this and continue the discussion on #14

@iamunni feel free to work on this. :)
There are no objections from me.

@vladimir-kozyrev awesome. can you assign this issue to me

there is some issue with the GET /api/beta/access-groups api . I'm getting the following error from yest. Tried with a new account, started showing the issue after working for for couple of times

have send a mail to<EMAIL_ADDRESS>so far no response. waiting for updates from them

@dsommers would you be able to help me out here

no reply from openvpn team

Hello there! Apologies for late response. We have been working on this at the side of OpenVPN, and I think we managed to prepare a fix. Now, we are working to do the release. I will update you early next week where we are.

Hey! Here is the PR#60 with added usergroups resource. It would be great if you could take a look and see if it has everything you need.

@michaelfmnk PR#60 is for user-groups. this issue is for access-groups

@dlenart-openvpn awesome

@dlenart-openvpn hey is the fix released?

@unnirapido hello there! Not really. We have been lately working on user groups support, and did not manage to prepare access groups within same release as well. But we continue work on this, and will let you know once this is ready. Should not take more than 2-3 weeks.

@dlenart-openvpn is the fix released now?

We've published new version of Terraform Provider to Registry: https://registry.terraform.io/providers/OpenVPN/cloudconnexa/latest
Going forward only https://registry.terraform.io/providers/OpenVPN/cloudconnexa/latest will be developed.
Please give new provider a try, hopefully it will fix your issue.
In case if problem persists - please open new "Issue" (https://github.com/OpenVPN/terraform-provider-cloudconnexa/issues)
Sorry for inconvenience.


Questions about prefix_length and suffix_length

Hello author, thank you for your great work！
I have some questions about In-betweening and Motion expansion:
How should --prefix_length and --suffix_length be specified?
For example, I used a 1200-frame action during training. I want to use in-betweening 0-400 frames and 800-1200 frames to generate 400-800 frame actions. How should --prefix_length and --suffix_length be specified?
--prefix_length 400 --suffix_length 800?
Or something else?
Looking forward to your reply

Oh, I found the answer in parser_utils.py.
Thanks again for the great work!


Rename Bitmap::len to Bitmap::bit_len

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
#1231 was caused by a somewhat confusingly named method on Bitmap
Describe the solution you'd like
Rename the method to avoid future confusion
Describe alternatives you've considered
Document the method extensively

Do we still need to rename it, as the documentation has been improved? If so, I would like to solve this issue.


NoSQL Challages

Hi Guys,
me and a few colleges of mine have wanted to use the JuiceShop to demonstrate NoSQL Injection Attacks. To Do this we have implemented a MongoDB Integration to JuiceShop using a prebuild MongoDB loaded via npm.
The MongoDB is used to store comments for the products. There are 2 challenges regarding NoSQL Injections at the moment.
This was implemented a few Months ago there were some problems with the libraries that should be solved by now.
During OWASP Summit i'd like to update these integration. I dont know if it will be done by the end of it / if it is in a state to get merged by the end of it.
The branch with the current features can be found here:
Feature Branch
I'm always open for feedback on the idea and the features.
Have a good time at the Summit

I remember that one... somehow slipped through... It requires a separate DB running, so probably not possible the easy way with single Dockerfile, right? You built in a way where the additional challenges are only available if you find a running NoSQL DB at an expected URL, right?

The MongoDB now runs in the same Container as the the Applications.
The Process get started by the Node Server itself.
The challenge disabling is still in the current implementation, but more a relict of the times where the MongoDB was external. Probably not even really needed when the Database always gets installed with the Application.

Oh, this is awesome news! No docker compose needed? 🎉

Yup

It'd be great if you could rebase your changes to develop branch. That's easiest to merge them, when it's ready! Let me know if you need any assistance!

Ok i will try that.
And yes i might need some assistance on that never did any rebasing before 😅

Looks there are a few conflicts occuring between your branch and the main repo (no matter if develop or master). It might be easier in the end if you fork freshly and re-apply your changes/enhancements. Sorry for that, but merging might probably be even less fun.

Ok no problem I will do so.
I haven't had any time to work on it during the week, i gonna look into updating the code during the weekend


Add reactions fields to activity

Couldn't find docs for this, but here's a sample request (in prod):
{
  "replyToId":"abcd",
  "from":{
    "aadObjectId":"...",
    "id":"..."
  },
  "timestamp":"2020-11-24T09:15:15.6739656Z",
  "channelId":"msteams",
  "reactionsAdded":[
    {
      "type":"heart"
    }
  ],
  "conversation":{
    "tenantId":"...",
    "conversationType":"personal",
    "id":"..."
  },
  "serviceUrl":"https://smba.trafficmanager.net/emea/",
  "type":"messageReaction",
  "channelData":{
    "legacy":{
      "replyToId":"..."
    },
    "tenant":{
      "id":"..."
    }
  },
  "recipient":{
    "id":"...",
    "name":"Skoach"
  },
  "id":"..."
}

Here are the docs for this: https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#activity-object
The activity object contains those reactions which has this schema https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#activity-object


0.46 Breaks app with firebase/angularfire (0.45 works fine)

Short description of the problem:
My firebase/angularfire app builds and works fine with app-scripts 45. After I installed 46 I got the following error: Cannot find namespace 'firebase' and the app won't build/work.
After rolling back to 45 everything works as expected again.
What behavior are you expecting?
I expect to have app-scripts 46 to work with Firebase just as 45 did.
Steps to reproduce:

Clone repository https://github.com/gigocabrera/MoneyLeash2
Install app-scripts 45 and ionic serve
Now install app-scripts 46 and ionic serve

Which @ionic/app-scripts version are you using?
I'm using 45 because 46 breaks my app

Try to set firebase to Version 3.3.0. That fixed the Problem for me (after deleting node_modules, www, tmp and then a fresh npm install).

Hi
Try updating angularfire to beta.6
https://github.com/angular/angularfire2/blob/master/CHANGELOG.md
imports: add firebase imports to all places that reference firebase namespace (c3a954c), closes #525

Setting firebase to 3.3.0, angularfire to beta.6 and app-scripts to 46 did the trick. Thank you very much @Chris1308 and @tja4472


supporting attrs to escape : or . attributes

related with issue supporting . (dot) and : (colon) syntax to add support with string. Added one test case to make sure it work and it passed.
However, I had issue with TS where the TS Language not reading attrs in HtmlTag ,can anyone review / improve this ? thank you

I implemented it myself at 95b7b121bc9091df2b5131d4c729929bccb7dc9b


Use Ganache instead of TestRPC

Ganache is the new TestRPC. It could be greate to update the readMe and the packages with this new name

Technically ganache-cli, right? In any case, I'm happy to accept a PR for this.

Yes it is ganache-cli ;) It's very similar to testRpc, I think only the name was changed

The cave-at here is that the ci broke for some reason (I think having to do with (headless) chrome https://travis-ci.org/Quintor/angular-truffle-box/builds/317636274 )
The easiest way to verify that ganache-cli doesn't break anything is to fix the integration test and then update the versions.

I fixed the ci issue in #30


fix recording url tag with wrong port

Fix

[ ] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.
The default port is -1 in URI, now use empty string instead of the default value.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

sorry, I had a mistake and recommit now. please review again, thx.

sorry, I had a mistake and recommit now. please review again, thx.

sorry, I had a mistake and recommit now. please review again, thx.

You just did a force push, I can't see what you changed. Could you be clear about that?

sorry, I had a mistake and recommit now. please review again, thx.

You just did a force push, I can't see what you changed. Could you be clear about that?


fix: replace path seperator in getName

I have a  same problem with #21 using this theme.
Fix an error by a different path seperator between fullFileName and process.cwd() in Windows.

Anyway, for fixing this problem, I cloned this repository and run yarn install,
However, this is my fist time using yarn and I'm not sure that I installed the packages correctly.
I had problem installing packages(like eslint-config-fuks), so I'm worried little bit.

sorry :(
fixed v4.0.1


Fix symbols

Coverage remained the same at 83.972% when pulling 557a851d5f31f933ed057d84c4c04d60c47e8c4f on update_fk_api into a50660657ffb27ee7659cfc5d4b834ae5a9af299 on master.

Coverage remained the same at 83.972% when pulling 4a1a92a13c32bf61cb65c7e4a8ad95c0f1ad5c7b on update_fk_api into a50660657ffb27ee7659cfc5d4b834ae5a9af299 on master.

Coverage increased (+0.5%) to 84.495% when pulling 4a1a92a13c32bf61cb65c7e4a8ad95c0f1ad5c7b on update_fk_api into a50660657ffb27ee7659cfc5d4b834ae5a9af299 on master.

Coverage increased (+0.5%) to 84.495% when pulling 7607bbb05328d1b855dc868701f1fc7be6a1e399 on update_fk_api into a50660657ffb27ee7659cfc5d4b834ae5a9af299 on master.


tf.contrib.learn.estimator each call to predict() reloads the model

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
None
Environment info
Operating System:
OSX & Ubuntu 14.04
If possible, provide a minimal reproducible example - Explanation
Each call to estimator.predict() completely reloads the model, which is very slow. Is there any mechanism to maintain the model in GPU/memory for consecutive calls?
I understand that large arrays can be passed to the function for simultaneous predictions, but my use case is for slowly arriving data which must be processed quickly. Is there a mechanism for decreasing the 'start-up' time of this function?
What other attempted solutions have you tried?
Looked through API docs & source code for alternative solutions

I discussed this issue briefly with Martin Wicke on the mailing list: https://groups.google.com/a/tensorflow.org/forum/#!topic/discuss/rOP4VKcfphg .
It seems that this use case is not supported OOB.
The ability to persistently load a model into memory for multiple predict calls would be a very useful enhancement.

Hi @ashern
Did you find a workaround? Anything that prevents reloading the model on each predict call?

I have modified estimator.py (Added my own predict function in BaseEstimator class). It's working for me. It's available here for anyone's use.

In case someone else runs into this, predict can take a generator as a parameter.
Here's a class that wraps an estimator with a generator. This means you can make multiple calls to predict without reloading the graph.
https://github.com/marcsto/rl/blob/master/src/fast_predict.py

Thanks Marc - that is exactly the pattern I was describing.
On Wed, Jul 5, 2017 at 11:29 PM, Marc Stogaitis<EMAIL_ADDRESS>wrote:

In case someone else runs into this, predict can take a generator as a
parameter.
Here's a class that wraps an estimator with a generator. This means you
can make multiple calls to predict without reloading the graph.
https://github.com/marcsto/rl/blob/master/src/fast_predict.py
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/4648#issuecomment-313285476,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfepRW_VN0yIX-XX6tJKv5qW8viTha7ks5sLFSJgaJpZM4KJnBY
.

Hi Marc, with the deprecation of sklearn compatibility in recent versions, how do you see the changes? I tried wrapping the estimator with SKCompat to keep using x as argument but then I have problems down the line. It seems to me that keeping input_fn open as a generator would make perfect sense, especially for big data (not relying only on parsing TFrecords and such)

Hi guys, I have trained my cnn model with tf.estimator and tf.data API. Model's input is an one-shot iterator. The relative model files(ckpt, meta, index) have been saved in model_dir. Now I want to predict one or more images' label using the trained model.
Any instructions for this?

@j3ven7 I wrote a example use tf.estimator, whick separate the train and predict process in different python file. You can see secsilm/understaing-datasets-estimators-tfrecords. There is a chinese README.md, but the two main python files are cifar10_estimator_dataset.py for train and cifar10_estimator_dataset_predict.py for predict.
Hope it helps you.

@secsilm Does the code you wrote address the issue regarding the model re-loading on each predict? Or is this strictly a tutorial on how to train and predict?

@j3ven7 I don't know whether it's a right solution or not. I combine 10 images to an numpy array and pass it to the predict function in my code. But the point is, I think tensorflow will reload the model in different run. Might not solve your problem? For reference only. 😄

I updated fast_predict2.py to support tensorflow 1.4 and later. I hope it helps!
https://github.com/marcsto/rl/blob/master/src/fast_predict2.py

@marcsto  fast_predict test file is still old, can u please fix it.Any idea on how can we pass pandas df to it

Thanks to @marcsto, I got this working for a DNNClassifier that's using several numeric feature columns. I found it a bit tricky to figure out exactly how to set up the generator, so there's a gist here:
https://gist.github.com/mikeoconnor0308/521ae2eb1555edc6550014ce0500e6a2

I tried to find a shorter solution and came out with a generator function which is fed using the build-in send() function:
def inference_generator(estimator):
    predictor_input = yield # wait here until send()
    predict_input_fn = lambda: predictor_input # input func just returns a single numpy array
    predictor = estimator.predict(input_fn=predict_input_fn, predict_keys=['features'])
    yield next(predictor) # yield for the first time
    while True:
        predictor_input = yield
        yield next(predictor)

So, here is how to use it:
gen = inference_generator(my_estimator)
next(gen) # start generator
# generator with an numpy array (do it as often as you want to)
result = gen.send(np.ones([1, 16, 16, 3], dtype=np.float32))

@mikeoconnor0308 @marcsto thanks, this is exactly the issue I've been facing!

another way can work around this problem,  you can define a "input_fn" with a dataset , and you can use dataset.from_generator(generator, ****),  in the definition of 'generator' you can use yield after read from outside queue , such as Kafka。and estimator predict also return an generator. You can get the result from the predict result generator supply to the caller

@marcsto I tried using your script and wanted the model to use a batch size of more than 1 and hence changed - .batch(1) to .batch(batch_size).
For some reason the model does not receive new input on subsequent calls and the outputs from the model are completely destroyed on any call after the first call. If I send the same input in subsequent calls as the first call, then the output is fine. I am guessing there is some kind of flushing out of data that I need to do but I am not sure why that would be needed. Any pointers?


STs spam logs with sh.command.process.streamwriter: DEBUG logs

The nose output log is spammed with:
sh.command.process.streamwriter: DEBUG: <Command '/usr/bin/docker run ...(86 more)' call_args {'bg': False, 'timeo...(476 more)>.<Process 13798 ['/usr/bin/docker', 'run', '--privileged', '-v', '/home/calico/workspace/docker-fvs:/code', '--name', 'host', '-tid', 'jpetazzo/dind']>.stdin: received no data

I've already fixed this on libnetwork-rebased

Closing as already fixed


[CELEBORN-929][INFRA] Add dependencies check CI

What changes were proposed in this pull request?
As title
Why are the changes needed?
As title
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA

GA passed, PTAL. cc @pan3793 @waitinfuture

thanks for the review. @SteNicholas @waitinfuture @pan3793
merging to main(v0.4.0).


Home

Currently missing is the map. I will create a follow-up PR for this.

the cancelled checks for Node.js CI / build (12.x) (pull_request) can be ignore since this was the old pipeline. the new pipeline PR is working as intended.


Implement Clone for EntityFetch

Objective
This:
use bevy::prelude::*;

fn main() {
    App::new()
    .add_system(test)
    .run();
}

fn test(entities: Query<Entity>) {
    let mut combinations = entities.iter_combinations_mut();
    while let Some([e1, e2]) = combinations.fetch_next() {
        dbg!(e1);
    }
}

fails with the message "the trait bound bevy::ecs::query::EntityFetch: std::clone::Clone is not satisfied".
Solution
It works after adding the naive clone implementation to EntityFetch. I'm not super familiar with ECS internals, so I'd appreciate input on this.

Since the access in EntityFetch is read-only, this should be safe. I don't think we've had any use for this before, but your example should definitely be supported.

OptionFetch fails similarly, and I added an implementation for ChangeTrackersFetch for good measure.

bors r+

bors r+


patternise primordia/anlage

if these can be logically-defined using develops_into, some missing definitions will be auto-generated (to improve dashboard compliance)
X that develops_into some Y
where X is 'anlage', 'primordium' or similar and Y is a later version of the same structure (would not need to be final mature form, but perhaps should strive for this where possible?)

not possible to logically define all of these right now - sticking to SC axioms
might in future be possible to move some to equivalentTo


feature request to get cxxt integration

Note: for support questions, please join our Discord server

I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)

Expected result (what you hoped would happen)

Actual result (unexpected outcome)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
I think it is nicer to have Cxxt library to get all the tickers from the world.

Hey @jjhesk
there is currently a pull request for exactly that;
https://github.com/askmike/gekko/pull/1365

great, any updates for this?

@jjhesk did you even read @mattS00 's message?

@greenbigfrog i read @mattS00 ‘s comment as well but i dont quite get it, so apologies :) I checked the PR and it’s status is Open.
So does that mean:
a.) it’s still a work in progress,
b.) it’s done but wont be available until the next release, or
c.) ...something else?
Thanks!


V2.0.2

Removed asserts that throw errors when out of range values passed into set() and fill().
Out of range values now adjusted to closest accepted values.

Tony Reviewed.  Passes tests in test gist.


Should we package the Discourse Beta branch?

Currently we package the Discourse Stable branch in Nixpkgs. Some questions I'd like to discuss:

Should we instead only package the Beta branch?
Or, should we package both? (If yes, should we maintain parallel plugins for both branches?)
Or, should we keep only packaging Stable?

Some background

An official description of the Discourse branches: https://meta.discourse.org/t/updates-always-come-before-release-notes/88919/7
Upstream recommends following the Beta branch as a good default https://meta.discourse.org/t/please-dont-pressure-self-installers-to-be-on-beta-branch/32237/2?u=ryantm

You are free to choose what’s right for you, but we recommend that people follow the betas unless they are extremely risk averse.

Beta is the default branch you get when you install Discourse from with Docker.
All the professionally hosted (by upstream) instances of Discourse follow the Beta branch.
https://discourse.nixos.org is using Discourse Beta branch.
I am also using Discourse Beta branch in my deployments.

Discussion
I think we should focus our efforts on only packaging the Beta branch to more closely follow upstream and what we are deploying. I'd be in favor of having instructions for how someone could package the Stable branch themselves, but I wouldn't want to keep maintaining that version personally.
cc @talyz @dpausp

I'm fine with packaging Beta instead, since that seems to be what most other projects would consider their stable version anyway. I don't see any reason to package both - that would be a lot of work and would potentially require version checking in the module, etc.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/discourse-nixos-module-planned-version-packaging-policy-change/16375/1

Yes, makes sense to just package beta versions. I have been using them for some years without serious problems.


Events not working with Server-side rendering

I'm following the tutorial on VS2010, when I tried to change to server-side rendering it seems like the events are not rendering (onSubmit and I tried with onClick as well) .

Same here.
I tried to bind to onChange on an input element and it doesn't work with server-side rendering at all.
Will it be fixed or is there a workaround? Seems like a really important feature. :+1:

Are there any updates on this one?

Same. onClick just doesn't render with vNext and server side rendering

Do you have an example of some code that's not working properly and how you're adding the event handlers?

React render has to be called also on the client side to attach the events... I have not used react.Net, but it is the same with plain react with node server side rendering... it just creates the html and the render has to be called client side also (react will compare the rendering results and not re-render on the dom, effectively taking advantage of server side rendering)

I just pulled the latest tutorial code from this repository and the server side rendering fails to bind the events. The problem is with remarkable.
If you strip out all the markdown bits then it works as expected. I think remarkable just complicates the tutorial and should be removed to simplify it. I'm happy to do this if it's a good idea. There's some broken formatting to tidy up too.
P.S. To run the tutorial on your installed framework, e.g. ASP.NET 1.0.1 (rather than 1.0.0), simply delete the global.json file.

Closing issues older than a year, please re-open if you think this is still relevant.


[ovs-cni] Apply ovs-cni.yaml fail

Hi,
We would like to set up ovs-cni.yaml on K8S. Below is our command:
kubectl apply -f ovs-cni.yaml
but found that the ovs-cni pod crash
kubectl get pod --all-namespaces
kube-system            ovs-cni-amd64-sg5c2                         0/1     CrashLoopBackOff   1          7s
and the container log is below
kubectl logs -f ovs-cni-amd64-sg5c2 -n kube-system --all-containers
I1012 03:18:41.081822       1 main.go:44] Found the OVS socket
F1012 03:18:41.082910       1 main.go:56] Failed to create a new marker object: Error creating the ovsdb connection: failed to connect to ovsdb error: dial unix /host/var/run/openvswitch/db.sock: connect: connection refused
Could you help to check this problem?
Please refer the attachment for our cni-ovs.yaml.
cni-ovs.txt
Thanks,
Willie

Hello @willie-hsueh-666 ,
do you have Open vSwitch installed and running on your host? It is a prerequisite for ovs-cni.
If so, in which version?
Would you try using the latest release v0.14.0?

Hi @phoracek
Yes, we already installed the Open vSwitch and running on our host.
The version is below
ovs-vsctl (Open vSwitch) 2.14.90
DB Schema 8.2.0
Thanks,
Willie

Please use the recent version v0.14.0, the one you use was built against quite an old version of OVS.
Also, would you verify that /var/run/openvswitch/db.sock really has the OVS socket on your host? Log in to the host and call:
ovs-vsctl --db unix:///var/run/openvswitch/db.sock show


#8 Replace deprecated defines

Fixes #8
Work submitted by @skliper CLA on file.

Submitted by @skliper , CLA on file
Testing:

make ENABLE_UNIT_TESTS=TRUE SIMULATION=native prep
Built on linux with -DCFE_OMIT_DEPRECATED_6_6 with no build errors
make test passed (except osal_timer_UT which occasionally fails on linux)
cFS executes and loads apps with no issues

Needs to compile with all deprecated elements removed.  Preference is to do this based on the compile switch implemented by Babelfish ticket 324, but manual check may be required in the meantime.

Rebased on master and updated commit message.


[Refactor] Erase Youtube category

File Name
/database/youtube
Reason for Refactoring the Code
Changes proposed
Maybe we can think about dissolving Youtube Category, moving each of its links to the categories that fit each subject of each link that is in there.
Reason
Users will most probably search content based on their interest subjects, like "design" or "frontend"... And Ytb is not a subject, it is one of the platforms from which we are taking content to insert inside those subjects.
Example
See Languages > C Programming > CodeWithHarry. This link seems to be in the right place, though it doesn't, at the same time. It is a ytb link, so it could be inside Youtube > WebDevelopment as well and it would not be wrong. There are plenty of other cases that could illustrate this problem. It seems to me youtube channels should be all just like CodeWithHarry, in its repective section, and none inside a Youtube category.
I'm interested in working on it, if this change seems plausible.
Checklist

[X] I have checked the existing issues.
[x] I have read the Contributing Guidelines.
[X] The changes don't break the code and don't introduce new functionality.
[X] I am willing to work on this issue (optional).

I am up for this change

@GabrielBittar i think its gonna be a good practice. What about the links who don't have any category? are we going create new category and subcategory?

@GabrielBittar i think its gonna be a good practice. What about the links who don't have any category? are we going create new category and subcategory?

Yes, this seems to be the best approach, creating the new cats/subs in those cases.
Since the issue looks alright, I intend to start working on this as soon as assigned.

@rupali-codes
Please assign him if it's okay. This would be useful imo.

@GabrielBittar you're assigned.

@GabrielBittar you're assigned.

Ok! Thanks, I'll start working on it.

During work, found the unused DSA folder with DSAYouTube.json. Also found Resources > dsa.json. Total of 3 links. I took the liberty, to send these links to data_structures > dsa_tutorials and data_structures > dsa_articles, since there is ady this category for them. I'm communicating since this is not part of the discussed issue, so if you guys think this should not be done, please alert me so I don't send these changes.

During work, found the seemingly unused DSA folder with DSAYouTube.json. Also found Resources > dsa.json. Total of 3 links. I took the liberty to send these links to data_structures > dsa_tutorials and data_structures > dsa_articles, since there is ady this category for them. I'm communicating since this is not part of the discussed issue, so if you guys think this should not be done, please alert me so I don't send these changes.

Put them together in the same category but create different subcategory as mentioned :)

Are you done @GabrielBittar ?

Are you done @GabrielBittar ?

No, I'm working on it.

Oh no problem
On Fri, 6 Sept, 2024, 11:00 pm GabrielBittar, @.***>
wrote:

Are you done @GabrielBittar https://github.com/GabrielBittar ?
No, I'm working on it.
—
Reply to this email directly, view it on GitHub
https://github.com/rupali-codes/LinksHub/issues/2474#issuecomment-2334516838,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP333TAVZMWVNQGKWXYJQILZVHRE3AVCNFSM6AAAAABMW6PJUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGUYTMOBTHA
.
You are receiving this because you commented.Message ID:
@.***>


Add missing duration error summary

Related issues

For #146
Description

Added the description for the duration error message that I missed out on.

Codecov Report

Merging #203 (238c67d) into master (ea8bf7a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #203   +/-   ##
=========================================
  Coverage     71.61%   71.61%
  Complexity      560      560
=========================================
  Files            94       94
  Lines          1878     1878
  Branches        202      202
=========================================
  Hits           1345     1345
  Misses          447      447
  Partials         86       86

Continue to review full report at Codecov.

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


Suggestion for pip update problem

This PR is a suggestion for the stable pip update dependencies problem

Looks good.  Could you check which of the dependencies can be satisfied by using distribution packages and using virtualenv --system-site-packages?

I'll merge these fixes in #135, as much as possible


Add temp value generators for all common property types

This allows some form of temporary value generation to happen for any kind of strange key types. Fixes Issue #2087.

:ship: :it:


pool_2d() got an unexpected keyword argument 'ws'

#The following github code is not consistent with keras 2.0.0.
I ran cifar10_cnn.py from examples. It is giving error in calling pool_2d(). Function arguments do not seem to be consistent.
Kindly check this.
curl -sSL https://github.com/fchollet/keras/raw/master/examples/cifar10_cnn.py | python
Using Theano backend.
x_train shape: (50000, 32, 32, 3)
50000 train samples
10000 test samples
/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/backend/theano_backend.py:1703: UserWarning: ['filter_dilation'] are now deprecated in tensor.nnet.abstract_conv.conv2d interface and will be ignored.
filter_dilation=dilation_rate)
Traceback (most recent call last):
File "", line 45, in
File "/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/models.py", line 455, in add
output_tensor = layer(self.outputs[0])
File "/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 545, in call
output = self.call(inputs, **kwargs)
File "/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/layers/pooling.py", line 154, in call
data_format=self.data_format)
File "/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/layers/pooling.py", line 217, in _pooling_function
pool_mode='max')
File "/home/abhijeet/miniconda2/lib/python2.7/site-packages/keras/backend/theano_backend.py", line 1833, in pool2d
mode='max')
TypeError: pool_2d() got an unexpected keyword argument 'ws'

In theano 0.8, I believe the argument is ds. It seems that the code is intended for theano 0.9.

okay...i will check and close the issue if that is the case.

Any progress?

Updating to the latest version of Theano via
pip install --upgrade --no-deps git+git://github.com/Theano/Theano.git

worked for me.

Sorry for not updating.
Installed latest version of Theano and it worked for me. Though i had some different issue with 'sudo'.
Thanks @AvantiShri @vadimnazarov for help.
Closing the issue.

Unfortunately, I have the same problem as mentioned above.
Trying to run the tutorial example taken from
https://elitedatascience.com/keras-tutorial-deep-learning-in-python
I obtained the following error:
Using Theano backend.
WARNING (theano.gof.cmodule): WARNING: your Theano flags gcc.cxxflags specify an -march=X flags.
It is better to let Theano/g++ find it automatically, but we don't do it now
Traceback (most recent call last):
File "keras-proba.py", line 37, in
model.add(MaxPooling2D(pool_size=(2,2)))
File "/home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/keras/models.py", line 455, in add
output_tensor = layer(self.outputs[0])
File "/home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/keras/engine/topology.py", line 554, in call
output = self.call(inputs, **kwargs)
File "/home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/keras/layers/pooling.py", line 154, in call
data_format=self.data_format)
File "/home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/keras/layers/pooling.py", line 217, in _pooling_function
pool_mode='max')
File "/home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/keras/backend/theano_backend.py", line 1856, in pool2d
mode='max')
TypeError: pool_2d() got an unexpected keyword argument 'ws'
Theano version:
Name: Theano
Version: 0.9.0.dev2
Summary: Optimizing compiler for evaluating mathematical expressions on CPUs and GPUs.
Home-page: http://deeplearning.net/software/theano/
Author: LISA laboratory, University of Montreal
Author-email<EMAIL_ADDRESS>License: BSD
Location: /home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/Theano-0.9.0.dev2-py2.7.egg
Requires: numpy, scipy, six
Keras version:
Name: Theano
Version: 0.9.0.dev2
Summary: Optimizing compiler for evaluating mathematical expressions on CPUs and GPUs.
Home-page: http://deeplearning.net/software/theano/
Author: LISA laboratory, University of Montreal
Author-email<EMAIL_ADDRESS>License: BSD
Location: /home/michael/anaconda2/envs/pcs_theano_2/lib/python2.7/site-packages/Theano-0.9.0.dev2-py2.7.egg
Requires: numpy, scipy, six

Updating to the latest version of Theano via
pip install --upgrade --no-deps git+git://github.com/Theano/Theano.git
worked for me.
👍 5
it works for me too. thx

@vadimnazarov @OOMMYY  i upgrade the theano,but it show me

ValueError: You are tring to use the old GPU back-end. It was removed from Theano. Use device=cuda* now. See https://github.com/Theano/Theano/wiki/Converting-to-the-new-gpu-back-end(gpuarray) for more information.

How do solve it?  Thanks.

I use anaconda, how can I update it? pip is nouse

conda install -c conda-forge theano=0.9.0
I use this command and solve the problem.
My environment is win10 + pychrom + keras (theano backend )

conda install -c conda-forge theano=0.9.0
I use this command on my Mac OS X, still not solved the problem:
TypeError: pool_2d() got an unexpected keyword argument 'ws'
Mac OS X EI Capitan
Keras    2.0.6, backend is  theano 0.9
Python 					2.7.13
Anaconda 				4.3.1


Add Data Models For Recordings

Still need tasks and tests for recording credits (and roles).  Seed some recording credit roles.


Additional export certificate options

The ability to export a certificate without the private key would be helpful.  Specifically for certificates that are being generated with CSR's which do not have a private key stored in lemur.  The addition of a export option inside of openssl for pkcs8 would be helpful, for these types of situations.
Additionally the option to export a certificate using openssl(pkcs8) with/without both the private key and chain would be nice.  This would then be useful for certificates that are not generated via CSR, and do have a stored private key.

I agree this would be a nice-to-have feature. We currently don't have the cycles to work on this, so I've marked it as help-wanted.
Thank you.

I have


Embedded SAPI support (php.ini)

Support for embedded sapi - configuring specific for sapi php.ini as it is only thing I think is needed in this case.
Checked on RedHat and Debian. Fingers crossed for Suse & FreeBSD.

Sorry it took to so long to review this. Looks good. :+1:


Disable acrylic material (temporarily) when opacity is set to 100%

If the opacity is set to 100%, the background becomes solid instead of 'fully opaque acrylic'. If the opacity is below 100% the acrylic material is re-enabled (depending on the user's settings).
Validation Steps Performed
I updated two unit tests to reflect the change in behavior and manually tested the transition from <100% opacity to 100% opacity (and vice versa) on win11.

Steps in video:

Start with 100% opacity and acrylic material enabled.
Decrease opacity and observe acrylic effect.
Increase opacity back to 100% and disable the acrylic effect.
Decrease opacity and notice that acrylic effect is no longer there.

(Apologies for the poor quality of the gif...)
Closes #12880

Extracted from commit message

(Apologies for the poor quality of the gif...)


Add CMake option to enable best practices layer

Description
This PR adds a the new VKB_VALIDATION_LAYERS_BEST_PRACTICES CMake option to enable the best practices validation layer part. This was a separate layer some time ago, but has since been merged into the validation layers. Having a toggle for this lets developers enable that part of the layers via cmake.
General Checklist:
Please ensure the following points are checked:

[x] My code follows the coding style

[x] I have reviewed file licenses

[x] I have commented any added functions (in line with Doxygen)

[x] I have commented any code that could be hard to understand

[x] My changes do not add any new compiler warnings

[x] My changes do not add any new validation layer errors or warnings

[x] I have used existing framework/helper functions where possible

[x] My changes do not add any regressions

[x] I have tested every sample to ensure everything runs correctly

[x] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[x] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[x] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

LGTM, but curious, how is this necessary now, #245 suggested these messages should already have been visible? Oh, it looks like it required the user enabling some settings externally, whereas this PR enables them programmatically 👍

I deliberately didn't change how and when the general layer flag is enabled and just expanded the way that the GPU assisted layer works.
But sure, I could integrate all of your feedback and rescope the PR. Will take a look at that.


release jenkins-3.5.3-2.150.1

Does this release add support for edgelb? Just like it has it for marathon-lb

@cisco1115 This release doesn't officially add support for Edge-LB but it can be made to work with a customized configuration involving:
dcos package describe --app --render --options=<your_custom_jenkins_options>.json jenkins > jenkins-marathon.json

Edit jenkins-marathon.json to cleanup any configuration artifacts and clauses (e.g., remove Marathon-LB HAPROXY_<> labels) so that they don't interfere with Edge-LB.
dcos marathon app add jenkins-marathon.json


Remove sub-modules under package/

This is to

simplify codes
add more flexibility, for example to package more than one backends into the bundle jar, if we support that in future

Please also change the jenkins.

Yes. and as well as arrow's GHA CI. Please help me approve this so I can make the upgrade in short time.


Add the ability to dump content from test responses.

When writing functional tests, it's often handy to see what the test is seeing. This method helps by dumping the content of the last response. It does a check to see if the content is JSON, and if it is, it outputs the decoded values instead of the response string.
Example usage:
$this->visit('/home')->dump();

:+1:

I just noticed this dd() the contents of the response. Can we do something better?
This could stop the tests running without throwing an error if it comes before a failing test.

True, but this method should never actually be committed given it's only a helper for while developing.
Having said that, the Symfony Dumper can be used without exiting. Something like this:
public function dump()
{
    $content = $this->response->getContent();

    $json = json_decode($content);

    if (json_last_error() === JSON_ERROR_NONE) {
        $content = $json;
    }

    (new Dumper())->dump($content);
}

I'd leave this decision to whatever @taylorotwell feels is best.

:+1: it'd be nice to know what the data is, especially when using Faker. Helps debug tests.

So this attempts to dump JSON array out, otherwise will just dump out HTML?

Yep, correct. It just seemed smart to dump the JSON in a nicely formatted way, considering this is a very common use case, and also because Laravel automatically converts arrays/objects to JSON when returned as a response.

@shehi Fair point, I actually got the dump() method idea from Laracasts' Intuitive Integration Testing series, so this method must have been removed in either 5.0 or 5.1.  It seemed to make sense, so I added it back in this PR.
Adding a getResponse() method is a great idea. I'd suggest even going a step further and also adding a getContent() method, which would of course be a shortcut to $this->response->getContent(). Or, more in keeping with the current API, maybe it should just be content().

@reinink : Thanks. I would vote against getContent(): it's something you can achieve by one method call, no point in cluttering the codebase with it.


Django processor

Django compiler and packager (including tests).
The Django compiler is quite similar to the Jinja one, with the difference being mainly the addition of the staticfiles wrapper: this means loading the staticfiles dependency in top_of_page; it also means the assets don't need the version appended, as this is handled by the wrapper at render time if necessary (we use hash-based cache-busting on our service).
Done:

[x] Create compiler
[x] Create packager
[x] Write tests

To do:

[ ] Create publisher (separate git repo or pypi.python.org package?)

One thing we'd really like to see for each new template that we provide is to have an integration test. There's a README which (hopefully) explains this: https://github.com/alphagov/govuk_template/blob/master/integration_tests/README.md
Is this something that you'd be prepared to do?

Yeah, I'm happy to have a go at that.

Here's the integration test, which has already highlighted one issue (now fixed!) with the template tag default filter syntax :)
I've had to use sudo in the build.sh script to install Django -- is that ok?

Is there any way you could do this in a virtualenv instead? If Travis does it automatically as you say in 380a121, it should work fine.

Looks like using sudo might be the only option here. If Travis was set up for Python we might have access to virtualenv, but in this case we don't automatically -- not really an option anyway, seeing as the core code is Ruby!
The only way we could force Django to be installed in a virtualenv seems to require sudo-ing the install of virtualenv itself, then instantiating the environment so we can run pip install Django without sudo -- this would just add more complexity IMO.
Travis seems to run completely isolated build machines anyway (http://docs.travis-ci.com/user/ci-environment/#Overview), so is this a huge problem? If no other suggestion I'll revert to using sudo pip install Django.
Any further input appreciated -- these things are not really what I'm best at, I feel like I'm stabbing in the dark a little here! :-/

Is this good to go, or do we require a publisher be put in place before this can be merged?
If so, as per question in original PR: should this publish to git repo (which needs creating -- I don't have write access on alphagov), or publish as Pypi package?

@froddd thanks for doing the work on this - apologies for the delay in getting it merged.
With regard to adding a publisher: when the version is next bumped, a tgz will be uploaded to https://github.com/alphagov/govuk_template/releases. If you need it to be published elsewhere then, someone would need to add a publisher class to do that.

@froddd this will be released as v0.16.0 once this is merged: https://github.com/alphagov/govuk_template/pull/178


Failed to upload file to Object Storage.

I'm still getting this issue 99% of the time.
I would have re-opened the issue but I don't appear to have the ability to.

Please provide a set of reproducible steps.
Check the CONTRIBUTING.md for an example.

Login to dataplatform.ibm.com
Select my project
Select the load tab on the right pane
Drag a file into the pane or click browse and choose a file

The upload will start as normal. Progress meter will proceed but occasionally will jump back to the beginning. After it jumps back to the beginning a few times, it will stop and present the error "Failed to upload file to Object Storage."
As I mentioned in #11, I'm not sure if I'm in the right place for this issue. If I'm not, a) sorry and b) where should I be?

This issue still persists. Is there any update on this or where I should be asking about this? Many thanks.

Thanks. I opened one: Ticket number: CS0031486

Can you invite me into your project? My email is<EMAIL_ADDRESS>

@JohnnyKam I tried but got this message "You cannot add<EMAIL_ADDRESS>to this restricted project. You can only add a member of your company (if your company has federated SAML with IBM Cloud) or a member of the project creator's IBM Cloud account.
To add members of the project creator's IBM Cloud account, you must be a member of that account."
I can barely parse that.

In the header can you click on manage > account > users.

This will take you into IBM cloud, where you can invite me into your account. Once I'm in the account you should be able to add me as a collaborator in your project.

Okay, you're invited to the account. I'll add you as a collaborator once you're in. Thanks.

@JoshBoluga Please add me as a collaborator

What browser and OS are you using? I was able to upload the files into object storage without any issues

I'm using macOS High Sierra 10.13.4 and Safari 11.1. I've also tried Chrome which produced the same behaviour.

I can't seem to reproduce it in Safari 11 or Chrome 66 or Firefox

it seems like it's working for you now @JoshBoluga so I'm going to close this issue.
Feel free to reopen it if you face this problem again.

Hi, how did you manage to fix it? I am getting the same error 100% of the time
"Failed to upload file to Object Storage."

I am having the same problem and I don't know what to do

@JoshBoluga @nadamakram how large are the files you are trying to upload?

It's 5.60 MB
If it's big for Watson studio, Is there another way to upload?
On Tue, Sep 18, 2018, 2:42 PM Nick Bourdakos<EMAIL_ADDRESS>wrote:

@JoshBoluga https://github.com/JoshBoluga @nadamakram
https://github.com/nadamakram how large are the files you are trying to
upload?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/watson-developer-cloud/visual-recognition-coreml/issues/18#issuecomment-422376308,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeWFgsBfgdECaM8n-ZKo02QZEBTnSsbkks5ucOojgaJpZM4TMixR
.

I have the exact same issue on MacOS too ... Is there any solution ?

I discovered that the problem is my subscription is limited so I can't use
that big size.
On Wed, Sep 18, 2019, 10:03 PM Ronanb3<EMAIL_ADDRESS>wrote:

I have the exact same issue on MacOS too ... Is there any solution ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/watson-developer-cloud/visual-recognition-coreml/issues/18?email_source=notifications&email_token=AHSYLAU7JIHYFZI7462QEN3QKKCQPA5CNFSM4EZSFRI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7BI2UQ#issuecomment-532843858,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHSYLAVCCLDS2E37GPQLMRDQKKCQPANCNFSM4EZSFRIQ
.

I do have the same problem is there any solution .....my csv file is about 14 MB.

i have the same prolem and my (Zip file) is just 85 Mo ,and our internet upload is good........any solutions?

I have the same problem and my (Zip file) is just 25 MB ,and our internet upload is good.


Primer throws error on install

Description
Install primer in vite, create box component, primer throws error
Uncaught TypeError: Cannot read properties of null (reading 'define')
    at ./node_modules/<EMAIL_ADDRESS>(relative-time-element-define.js:9:1)
    at __webpack_require__ (bootstrap:19:1)
    at<EMAIL_ADDRESS>(RelativeTime.js:5:1)
    at __webpack_require__ (bootstrap:19:1)
    at<EMAIL_ADDRESS>(index.js:70:20)
    at __webpack_require__ (bootstrap:19:1)
    at ./src/content_script.tsx (content_script.tsx:16:17)
    at __webpack_require__ (bootstrap:19:1)
    at startup:4:1
    at __webpack_require__.O (chunk loaded:23:1)

Steps to reproduce

Install primer in vite project (or any project)
run local server
view developer console.

Version
v35.24.0
https://github.com/benschac/primer-example - example repo where I reproduced the error.
Browser
Chrome

Hi there @benschac! 👋 Thanks so much for taking the time to make this issue!
I pulled down the repo you shared and ran:

yarn to install dependencies
yarn dev to run the development server

And unfortunately I could not see the error that you are describing. Are there any additional steps that I should take or anything I should change to re-create the error? Thanks!

what version of node are you using?
On Thu, Apr 6, 2023 at 11:03 AM Josh Black @.***> wrote:

Hi there @benschac https://github.com/benschac! 👋 Thanks so much for
taking the time to make this issue!
I pulled down the repo you shared and ran:

yarn to install dependencies
yarn dev to run the development server

And unfortunately I could not see the error that you are describing. Are
there any additional steps that I should take or anything I should change
to re-create the error? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/primer/react/issues/3128#issuecomment-1499216873, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AATDCI7W5ZQ2YSYZEI4HQTDW73LN5ANCNFSM6AAAAAAWVQM5PM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Benjamin

@benschac good question, I'm currently on v16.17.1

It was something with my webpack config, I wasn't able to reproduce it in
any other environment.
On Thu, Apr 6, 2023 at 12:37 PM Josh Black @.***> wrote:

@benschac https://github.com/benschac good question, I'm currently on
v16.17.1
—
Reply to this email directly, view it on GitHub
https://github.com/primer/react/issues/3128#issuecomment-1499337335, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AATDCIZFNZWPI2KASYK6ZBTW73WOFANCNFSM6AAAAAAWVQM5PM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Benjamin