(typo) launch.json config template "Edge: Attach" is named "Attach to Chrome"

VSCode Version: 1.47.2
OS Version: Windows 10

Steps to Reproduce:

Open launch.json
Select Add Configuration > Edge: Attach

This is what's added:
    {
      "name": "Attach to Chrome",
      "port": 9222,
      "request": "attach",
      "type": "pwa-msedge",
      "webRoot": "${workspaceFolder}"
    },

Should be "Attach to Edge". Just a little typo, but possibly confusing to anyone not paying attention when using the templates.

Sorry, missed this issue -- fixed in the latest builds


Fixing #26716 - GIFs were animating too fast on iOS

Submitting on behalf of @mk0116, who found the fix but has been (presumably) too busy to make the pull request.
See https://github.com/facebook/react-native/issues/26716#issuecomment-586537895

Summary

Certain GIFs have a zero'd property for kCGImagePropertyGIFUnclampedDelayTime, but a non-zero'd kCGImagePropertyGIFDelayTime property, so the second property should be used.
Changelog

[iOS] [Fixed] - Certain GIFs were animating too rapidly
Test Plan

I unfortunately don't have any non-trademarked GIFs to test, but someone in the issue thread may.

It was merged. 🎉

still happens on iphone13 pro max

RCTUIImageViewAnimated.m
NSTimeInterval duration = displayLink.duration * displayLink.frameInterval;
=>
NSTimeInterval duration = displayLink.targetTimestamp - displayLink.timestamp;


no Inpaint Anything tab in Runpod Stable Diffusion template

Hello Everybody,
First of all im a noob and very new to all this.
I am using RunPod Stable Diffusion version: v1.6.0, python: 3.10.12.
After having no Issues with Inpaint Anything on my PC (except gpu power). I tried to run it via cloud with Runpod Stable Diffusion template (runpod/stable-diffusion:web-ui-10.2.1.)
Then I installed Inpaint Anything from the extensions tab, normal procedure, unfortunately It wont show up in the img2img tab.
I looked at people having the same Issue here but none of the given solution would work for me.
Restart Pod, Removed othe Extension that could interfere, hidden Ui tab thing ...
Does someone have a clue? That would help me alot since I really like this tool.
I would love to provide the console message if someone could tell me where to find it since its kinda different unsing Runpod.
Thanks!

Click on the checkbox labeled ‘Inpaint Anything’, then click the ‘Apply and Restart UI’ button, and wait for the requirements to finish installing

Same problem here on Runpod. What did it for me was using the --enable-insecure-extension-access argument when launching.

Hi @bordi1111, in my case; some missing dependencies were causing the issue. You can try; connecting to your pod and navigating to the workspace/stable-diffusion-webui/extensions/sd-webui-inpaint-anything directory, there you will find install.py file. Look inside the file and try to install dependencies by pip install via terminal, Hope this helps 🤞🏽


Use .NET 5.0 SDK

Attempting to fix build.

Codecov Report

Merging #245 (ab83ce3) into master (735395f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #245   +/-   ##
=======================================
  Coverage   73.97%   73.97%
=======================================
  Files          65       65
  Lines        2728     2728
=======================================
  Hits         2018     2018
  Misses        710      710

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 735395f...ab83ce3. Read the comment docs.

@aseigler Ready for review. This just updates the SDK to 5.0.x and allows us to use .NET5.0 elsewhere. We're still targeting the same frameworks.


Fix for #12 - Coral Select with multiple values

Fixes https://github.com/wcm-io/io.wcm.wcm.ui.granite/issues/12

@rubnig  thanks for the contribution - looks good, but i think i found a small JS error fixed in https://github.com/wcm-io/io.wcm.wcm.ui.granite/pull/13/commits/6831badc161e854390849181b99aa551bb606c03 - please cross-check

This was a typo indeed, thanks for the cross check @stefanseifert!


Cloudfront cache is deleted every 1 second

Describe the bug
All assets return x-cache: Miss from Cloudfront, even after multiple refreshes. It only returns a cached version when a request is made less than one second after the previous one.
Environment
Default Gatsby app. The amplify console sets the infrastructure to Infrastructure: Gatsby-Amplify
Proof
Request the same asset with 2000ms interval, we always get a MISS:
while true; do curl -X HEAD -i https://master.dsvk1bi06ng1b.amplifyapp.com/ -s | grep -Fi x-cache; sleep 2; done
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront
x-cache: Miss from cloudfront

Request the same asset with 100ms interval, we only get a MISS every ~1second:
while true; do curl -X HEAD -i https://master.dsvk1bi06ng1b.amplifyapp.com/ -s | grep -Fi x-cache; sleep 0.1; done
x-cache: Miss from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Miss from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront
x-cache: Miss from cloudfront
x-cache: Hit from cloudfront
x-cache: Hit from cloudfront

To Reproduce
use this command from the terminal:
while true; do curl -X HEAD -i https://master.dsvk1bi06ng1b.amplifyapp.com/ -s | grep -Fi x-cache; sleep 2; done
Alternatively, you can go to the deploy url and refresh the page with the network inspector open.
Expected behavior
Cloudfront should only invalidate cache when a new deployment is made. For every request after the first one, it should return the cached version from the CDN, as mentioned here.

Sample code
I've created a demo repo to view the issue.

repo url
deployed link

I could also reproduce with a standard create-react-app.
https://master.d1qu22wwco4729.amplifyapp.com
https://github.com/thedgbrt/create-react-app

@thedgbrt The diagram in the blog post doesn't fully explain how our 'CDN' works - we have dual layer CDN distributions so what happens is that you're seeing the miss from the CDN Edge vs the CDN Origin. We have an issue reporting information correctly in the header responses which has led to confusion from other customers before as well. We will prioritize a fix for this soon. Hope that helps - thanks for the detailed explanation.

@swaminator thanks for the quick answer.
What I'm concerned about is response time. When I manage to hit the CloudFront cache, I get a response in 10-30ms, which is what I'm used to when using a CDN.
However when I don't hit it (that is, 99% of the time right now), it's in the 50-200ms range, and can go up to 500ms. For an SPA with code split between 10-20 files each page, this has a dramatic impact on user experience. I routinely have to wait 1-2 seconds for a simple page change that could be almost instant.
I don't know how much if that has to do with proper cache headers being set, or with the way amplify console fundamentally manages CDN responses. Is the fix that is being prioritized going to lower response times to expected CloudFront levels?

Trying to provide a little more clarity until we've got a further solution. As @swaminator mentioned, your content is being cached and returned by our origin CDN, however you're seeing the response header from the closest edge CDN as a miss (which is by design), which is understandably confusing. The design is a bit more complex than alluded to, but in order to facilitate instant deployment changes (including invalidation of cached resources) and have as performant hosting as possible for all of our customers, we've implemented a dual layer CDN structure with an edge layer in-between. The response times you're seeing come from the brief edge layer invocation, before the content is then retrieved from the origin CDN (if it exists there, otherwise it is retrieved all the way from actual origin, which takes much longer). This round-trip time is several times faster than if we went straight to origin, and is still giving you the benefit of cached content (read; not re-serving from hosting origin if the file hasn't changed). We understand that certain customers (like in the example provided, with heavy code splitting) may want to optimize their edge CDN performance even further, and we are looking at a number of ways to provide this.
That said, your unmodified content is being cached and served from our origin CDN, the edge CDN response header just makes this confusing.

@cslogan-red what about being able to respond with 304 “not modified” for assets (for example my site.webmanifest file gets requested with a 200 status every time, despite the request header and response header etags matching) and also what if the instant deployment optimizations were bypassed if the cache headers are aggressive enough (e.g., "Cache-Control: public,max-age=31536000,immutable")?

@mrcoles we're considering a number of solutions for both the confusing initial response header from the edge CDN as well as tuning the edge CDN's performance that just need prioritization, we'll respond to this thread once we've implemented an update!

I can also see the following parameter in the request "public, must-revalidate, max-age=0". Is there any advancement or temporary solution for this ? Thank you for the good work

Hm, do you agree that is not the expected behavior that Chrome or any browser can not cache to disk any files provided by cloudfront, JS, CSS files and so on ?

have you tried something like this?
amplify.yml
version: 0.1
frontend:
  phases:
    preBuild:
      commands:
        - yarn
    build:
      commands:
        - yarn build
  customHeaders:
    - pattern: '/*.chunk.js'
      headers:
      - key: 'Cache-Control'
        value: 'public, max-age=31536000, immutable'

have you tried something like this?
amplify.yml

It works. 🥇  I have used `pattern: '**/*'` instead for more generality.

@arelaxend setting those Cache-Control headers can be super useful, but be careful you’re not caching content that you want to update at some later time. Doing pattern: '**/*' would set that Cache-Control header on your HTML files and other things that usually don’t want such extreme caching (usually you only want aggressive caching on just images, JS, CSS—especially if they have a content hash in their filename).
This doesn’t address the issue of how the CDN is not returning 304 not modified when request and response etag headers match (https://github.com/aws-amplify/amplify-console/issues/92#issuecomment-545609647)

Any update on this?
This should be fixed ASAP as cloudfront is considered broken

@masterofkfit @thedgbrt can you please let us know if you're still experiencing this as it should be resolved.

@swaminator why was this closed? I can still replicate this on a standard setup.

@robbie-thompson I had the same issue a few weeks ago and found a solution that works for me. I don't know if this is the "right" way, but it works. To cache the assets in the CloudFront cache I did the following:

Added these custom header to my customHttp.yml:

customHeaders:
- pattern: '**/*.html'
    headers:
      - key: Cache-Control
        value: 'public, max-age=0, s-maxage=60'
      - key: x-frame-options
        value: DENY
      - key: x-xss-protection
        value: 1; mode=block
  - pattern: '**/*[!.html]'
    headers:
      - key: Cache-Control
        value: 'public,max-age=31536000,immutable'
      - key: x-frame-options
        value: DENY
      - key: x-xss-protection
        value: 1; mode=block

Enable performance mode in the app settings in the Amplify console.
Redeploy the last version to create a new build with the custom headers and performance mode.

@robbie-thompson see performance mode docs for more info. We launched our redesigned hosting and deployment modules around the time this issue was closed, which removes the CDN sandwich I described earlier in this thread for a more standard and fine tuneable setup. By default, in "development mode", we expire the CDN cache every second to facilitate instantly showing deployed changes in origin, once you're in steady state, on say your Production branch that doesn't see deployed changes as regularly, enabling performance mode for that branch reconfigures the CDN timeout to be biased towards app performance at the sake of a delay between deployed changes appearing. Further, you can fine tune the behavior in addition by providing your own custom header overrides for specific paths, as @marco910 example shows.

@marco910 Thanks for this. But I have tried different this and multiple other variations also. But irrespective of the pattern always the last the cache-control gets applied to all the requests css, js and index. In the example which you provided its always applying the cache-control of the pattern '**/*[.html]' for everything. I am thinking that definitely something is wrong with amplify which is causing this. My live website is here

@mathan-xflowpay I'm facing currently a very similar issue that the cache is not being cleared after redeploying a new version of the site. If you change the content on a page and redeploy the site, do you see the changes on the page?

@marco910 I've tried adding your suggested customHttp.yml but I'm also not seeing any differences. When you say that your output directory was incorrect, what was it and what did you change it to? Maybe I'm doing something wrong too?
My files are as follows:
amplify.yml
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - nvm install 16.10.0
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
      - .next/cache/**/*

customHttp.yml
customHeaders:
  - pattern: /_next/static/**/*
    headers:
      - key: Cache-Control
        value: 'public, max-age=31536000, immutable'
      - key: x-frame-options
        value: DENY
      - key: x-xss-protection
        value: 1; mode=block
  - pattern: /_next/data/**/*
    headers:
      - key: Cache-Control
        value: 'public, max-age=0, s-maxage=0, must-revalidate'
      - key: x-frame-options
        value: DENY
      - key: x-xss-protection
        value: 1; mode=block
  - pattern: '**/*[.html]'
    headers:
      - key: Cache-Control
        value: 'public, max-age=0, s-maxage=0, must-revalidate'
      - key: x-frame-options
        value: DENY
      - key: x-xss-protection
        value: 1; mode=block

@Reselence When deploying a static generated (SSG) site to Amplify you need to apply a different output directory than for sites with server-rendering (SSR) or Incremental Site Regeneration (ISR). For SSG you need to use out and for sites with SSR and ISR .next.
These are my build settings for an SSG site:
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - npm run export
  artifacts:
    baseDirectory: out
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Please note that you have to change the build command to the command you specified in your package.json file. In my case, npm run export will run next build && next export. This will only work for SSG sites. For SSR and ISR sites you have to use next build so that Amplify detects this as sites with SSR/ISR.

@marco910 Ah that's an issue. I use an API route for a contact form, but API routes do not work with export. When building my site however, all pages except the API route are marked as static so I would have assumed that I could still control the cache properties.
Performance mode seems to work without a customHttp file, but I want to cache images etc for as long as possible since I will only update this site a couple times a year.
Is there no way to have control of the cache properties this way?

Ah that's an issue. I use an API route for a contact form, but API routes do not work with export. When building my site however, all pages except the API route are marked as static so I would have assumed that I could still control the cache properties.
Performance mode seems to work without a customHttp file, but I want to cache images etc for as long as possible since I will only update this site a couple times a year.
Is there no way to have control of the cache properties this way?

@marco910 Ah that's an issue. I use an API route for a contact form, but API routes do not work with export. When building my site however, all pages except the API route are marked as static so I would have assumed that I could still control the cache properties.
Performance mode seems to work without a customHttp file, but I want to cache images etc for as long as possible since I will only update this site a couple times a year.
Is there no way to have control of the cache properties this way?

@Reselence You can try to add the headers already in Next.js. Also can try using this in customHttp.yml:
customHeaders:
  - pattern: '**/*.{jpg|jpeg|png|svg|bmp|tiff|webp|avif|ico}'
    headers:
      - key: Cache-Control
        value: 'public, max-age=31536000, immutable'

Maybe you have to edit the pattern depending on the file types you're using on your site.

@marco910 Setting the headers for those file types actually worked, thank you. Although I'm a little concerned now as even my html and scripts are cached for that length even though the pattern only includes images.

@Reselence Sorry, my mistake. This patter should work:
**/*.{jpeg,jpg,svg,webp,avif,bmp,tiff,gif,png}

@Reselence (and for anyone's future reference) as noted in my earlier explanation; if you're not regularly deploying changes, real world there isn't much of a difference between the default and performance modes (we've designed it that way on purpose)
Performance mode guarantees closest edge node cache hits for the blanket 10 minute interval, however due to how all modern browsers and CloudFront CDN's handle 304 refresh hits on identical Etag headers, if your content hasn't changed in origin (no deployments), you'll see about the same performance in the standard mode for the most part.
The standard mode expires CDN cache every 2 seconds (with no caching on client), if content in origin hasn't changed, a request from client will look like; GET index.html, browser sends (via HTTP/2) Etag to CDN, CDN says, index.html expired, forwards Etag to origin, origin responds 304 - not modified, CDN forwards 304 to client - if copy doesn't exist on client, it's downloaded from edge CDN (not all the way from origin, and even though it's expired), but in most cases it will already exist on the client, Etag on client is identical, so it's reserved from client. That entire loop happens automatically in modern browsers behind the scenes via HTTP/2 - while the content on the client is rendered immediately, if that whole trip returns unmodified, then the client does not refresh resources in the browser, and performance is identical to performance mode.
The caveat is that occasionally that 304 loop will drop at a CDN edge node that fails to propagate the cached resources, and so a download from origin will be required (primary benefit of performance mode), but more or less you're getting the same result, which will be sufficient for most Amplify apps. (We host Amplify Admin on Amplify Console to prove its effectiveness, we do not use performance mode) Performance mode is encouraged only if you're regularly seeing high TTFB, and further you'll likely have to customize the Cache-Control header entirely for complex static site generator apps with thousands of cached resources.

@cslogan-red Thanks for the explanation! Very interesting to see how it all works.
My main objective right now is getting all files to have appropriate cache headers, which is something I'm struggling with. I'm having the same issue as @mathan-xflowpay where only the last pattern is taken into account for all content types, regardless of the pattern specified.
I've tried everything @marco910 suggested (thank you by the way) but I'm still left with the same issue.
I'm still new to server side things and AWS in general so I wanted to avoid creating an issue for this in case it was just me doing something incorrectly.

@Reselence like I said - the default mode without using performance mode or any cache control overrides via custom headers may be enough for your application, it's not a requirement to configure them, and performance is generally about the same. Many production apps run in this mode.
Most folks run into trouble when testing very long max-age (client) and s-maxage (CDN) values and assume a deployment will bust those caches - as noted in our docs, this is not the case, your individual app CDN's are not invalidated post-deployment for many reasons, it's an expensive operation, and it has global propagation ramifications. Instead, post-deployment, files are invalidated in cache based on the default Cache-Control headers we configure for you; once every 2 seconds (10 minutes in performance mode) As a fallback, we set the max-TTL on all files to 24 hours - this supercedes any value you provide.
This means if you set very long values for max-age or s-maxage via custom headers, make requests to your app (which applies the headers), and then realize that's not the correct configuration and deploy updates/change the headers - any files covered by your previous custom headers config must wait for the cache you set to expire (up to the 24 hour max-TTL limit) before new custom header or deployment changes will be reflected on those files. This is why we recommend to simply stick with the default configuration for most apps.
Additionally, custom headers are applied in top-down order from your custom header file; least specific selectors should be up top, however, if you have an overlapping less specific selector path with a more specific selector, CloudFront may choose to use the least specific selector and we cannot control this.
In short, recommendations for using Cache-Control custom headers:

Use the default standard mode that Amplify Console gives your app, which applies a global 2 second CDN cache invalidation Cache-Control header (with no caching on client). Due to my explanation above, performance will be similar to performance mode in most cases.
Only stop using standard mode once you've benchmarked a problem area.
We recommend enabling either performance mode or your own custom headers on a separate branch connected to Amplify Console that is heavily tested before deploying to your production environment.
If using custom headers, it's best to not use performance mode; accept the default 2 second CDN invalidation configuration, and only add the most specific custom header path overrides that you can, as opposed to a global path that may overlap with more fine-grained paths.

@cslogan-red
Thanks for the detailed explanation.
But the problem @Reselence and I are facing  is specific to image caching and I have my performance mode disabled. I am targeting only the images via this pattern ‘ **/*.{jpeg,jpg,svg,webp,avif,bmp,tiff,gif,png}’ in my customHttp.yml but still the cache control header given for this pattern is getting applied to every other js and index.html files also which is not expected.
Can you let us know why that is happening when the pattern is for only the images?
Also I have connected my another test branch to amplify to test the changes before going to production. Thanks for the suggestion :)

@mathan-xflowpay I believe the response header behavior is a long-standing issue that's been documented in prior GH issues and is actually a limitation of CloudFront itself, it ends up reflecting the last applied custom header value for all files, but that's just the header response value, not what's actually set on the file itself in the CDN and client. You should be able to set different file types to different (short) values to manually verify behavior.
I've looped in @Athena96 from the Console team to take a look this week and make sure this isn't a new regression.

@cslogan-red Thank you. Just to be clear this issue is happening only in the nextjs project and custom headers in my other projects work fine.
@Athena96 Happy to help if you need any details related to this issue.

We are aware of an issue with custom headers and SSR applications. The glob pattern is currently not honored and headers are applied to all assets regardless of your specified pattern. We have a fix on the pipeline, apologies for the inconvenience.

@ferdingler Thanks for the update. Can you also pls share the ETA on this?

I updated my Next.js app to SSR and ISR and facing now the same issue with custom headers where the last setting of the customHTTP.yml is applied to all files (CSS, HTML, JS etc.).
Does anyone have a solution for this, or is this an open long-term issue?

I'm finding this a bit confusing as to what the correct setup is for Nextjs ISR.
With no custom headers and performance mode off there seems to be no caching and load times are slower 1.2s, ISR works though.
With no custom headers and performance mode on caching seems to work and load times are down to 100ms but the ISR never regenerates the page.

Are there any updates on the issue with custom headers?
Just tried to deploy a site with custom header and the last header of the customHTTP.yml is applied to all files.
@dottodot That's true, it is confusing.
Static assets should have a Cache-Control of public, max-age=31536000, immutable and all other public, max-age=0, s-maxage=60, must-revalidate (or depending on your needs). When deploying a static generated Next.js site it works fine, but when using ISR it doesn't work anymore.


Pass the context to shouldStartForegroundService

[REQUIRED] Use case description
In order to implement androidx.media3.session.MediaButtonReceiver.shouldStartForegroundService, I need to inject something.  I can either use @AndroidEntryPoint or use @EntryPoint.   The former doesn't work because the dagger generated code overrides onReceive and androidx.media3.session.MediaButtonReceiver implementation of onReceive is final.   The latter doesn't because I don't have context needed to use the @EntryPoint.
Proposed solution
Where the androidx.media3.session.MediaButtonReceiver calls shouldStartForegroundService, it has a context.  In fact it uses when it calls ContextCompat.startForegroundService, in order to correctly implement shouldStartForegroundService I need same information.
Alternatives considered
Copying the code from androidx.media3.session.MediaButtonReceiver to implement my own (not a great option).
Note, this is with 1.5.0-rc01

Yup, that is a valid request. Thanks for the suggestion. We will pass the context, we get in onReceive to shouldStartForegroundService. We will update this issue when this lands in the main branch.

Yup, that is a valid request. Thanks for the suggestion. We will pass the context, we get in onReceive to shouldStartForegroundService. We will update this issue when this lands in the main branch.

Thank you.  That'll be very helpful.


docs: Improve documentation around createCompletion vs createChatCompletion

Error: invalid_request_error: This is a chat model and not supported in the v1/completions endpoint. Did you mean to use v1/chat/completions?
This is the feedback from ChatGPT 3.5 nowadays. out-of-date

Can you share some code to reproduce this issue?

const openAI = new OpenAI(apiKey);
const gptModel = 'gpt-3.5-turbo';
const completion = await openAI.createCompletion({
model: gptModel,
prompt: "The meaning of life is",
});
console.log(completion.choices);
Nothing special. It is just the /v1/completions has been replaced by /v1/chat/completions in the GPT 3.5 /4.0.
Needs only a minor change in the code.

We should make it clearer in the docs. Thank you for raising this issue!

We should make it clearer in the docs. Thank you for raising this issue!

we might aswell make a full doc site with pyro

Not a bad idea.

Another queestion, I have a web front end calling a REST function that uses the openAI.createChatCompletion();
But, it is not blocking. as a result, I get an error -  TypeError: Failed to fetch  in the browser and never manage to get an content back. It is using the Fresh framework. I am calling using fetch from the frontend to the REST API, which contains the openAI function.
At the same time, the same call to the same REST API from Postman works fine and without a hitch.
somehow the createChatCompletion just jumps over, despite the await or then chaining.
thanks

You you provide a github repo with a reproduction of the issue? It only has to include an API route.

Yes. I have a repo. https://github.com/raygao/uxig
In the /api/genStory/index.tsx, I call the genStory(body), which calls the openai.CreateChatCompletion( ...)
And, this is where I am having difficulties.

Also, the frontend.

In the code you provide, you return a string from /api/genStory/index.tsx. You can't do that, you must return a response. That's what the red squiggly line is under POST. You should change your handler to include
return new Response(results);

instead of
return results;

Thanks a lot for the help.
That hint solved the red squiggly line under the POST method.
However, the browser still has a Validation issue. see screenshots.
As soon as it calls the createChatCompletion, the fetch method fails. I am not understanding this.

Okay I think I found the bug. You fetch the api route using
const result = await fetch(url, theScenario);

when you should be doing
const result = await fetch(url, { body: theScenario });

Amazing how fast, you guys respond! Much appreciate for the help.
Actually, the solution is even simpler. I googled just now, after struggling it for 1 full day.
When I add the               event.preventDefault();    to my onclick() method, the issue magically disappear.
https://stackoverflow.com/questions/64619140/my-fetch-requests-are-being-canceled-and-i-dont-know-why

Nice, good to here that the bug is fixed!


Cannot adjust the padding between title and image

I cannot adjust the padding or margin between title and image, could you provide a api to adjust it? (The same to textSize)

change the padding in dimens


Course remains in crediting state with "DCC approved audit conversion"

Is there anything to be done after the DCC approves credit to audit conversion? Shouldn't the course me marked as audit? Also, is the DCC approval needed for conversion, or does advisor approval suffice?

For credit to audit conversion or audit to credit conversion, is DCC approval required or is adviser approval sufficient?
Currently,there are 2 issues:

These conversion request is not appearing on DCC's  active requests page for DCC to approve or reject.
The states are not changing after adviser's approval.

I want to know the intended flow whether to include DCC's approval or just update the enrolment type on adviser's approval.

DCC approval is needed for Audit to Credit or vice versa conversion. It needs to be listed in.

Added DCC approval for A/C and vice versa. Also for drop.
Once A/C is approved, student status changes to "Final State Approved".
A/C updated in participant table.
Once dropped, status changes to "DCC approved drop".


Error sending data: (12175)

Произошла ошибка безопасности If the error is due to a timeout, you can increase the response timeout in the general program settings.

A security error occurred If the error is timeout related, you can increase the response timeout in the general program settings.
Increasing the response timeout does not help. What is wrong?

What OS?

Hi
Win 7
Thank for helping!
Отправлено из Mail.ru для Android среда, 01 ноября 2023г., 08:47 +03:00 от HemulGM  @.*** :

What OS?
—
Reply to this email directly,  view it on GitHub , or  unsubscribe .
You are receiving this because you authored the thread. Message ID:  @ github . com>

This is a Win7 bug. Google "Windows 7 http tls error"


Fix linting errors

Fixed linting errors:
client\commonFramework\update-preview.js
  18:1  warning  Line 18 exceeds the maximum line length of 80  ma

server\utils\date-utils.js
  7:35  warning  Trailing spaces not allowed  no-trailing-spaces
  8:14  warning  Trailing spaces not allowed  no-trailing-spaces

Good catch -- we're usually so on top of linting I'm shocked that this snuck through!


Make the names of graph structs consistent

main
Now: SccGraph, MfGraph, MinCostFlowGraph

The name style of the struct is different.

Expected1: Scc(or SCC), MaxFlow, MinCostFlow

Short and readable.
Each struct name equals each file name.

Expected2: SccGraph, MaxFlowGraph, MinCostFlowGraph

Long but readable.
No other language library has adopted this idea.

Expected3: SccGraph, MfGraph, McfGraph

Too short, not readable (except for SccGraph).
These names are closest to the original C++ library.

All graph names need to be changed, but I prefer expected1.
Other data structures
In reference,

lang
struct, impl
file

Rust
Dsu
dsu
URL

Rust
SccGraph
scc
URL

Rust
MfGraph
maxflow
URL

Rust
MinCostFlowGraph
mincostflow
URL

Rust
Segtree
segtree
URL

Rust
LazySegtree
lazysegtree
URL

Rust
TwoSat
twosat
URL

Rust
ModInt
modint
URL

Other language libraries
In reference,

Lang
SCC
MaxFlow
MinCostFlow

C++
scc_graph
mf_graph
mcf_graph

C#
SccGraph
MFGraph/MaxFlow.cs
McfGraph/MinCostFlow.cs

Python
SCCGprah
MFGraph
MCFGraph

Rust
SccGraph
MfGraph
MinCostFlowGraph

Go
SccGraph
---
---

D
SccGraph
MfGraph
McfGraph

Java
SCC
MaxFlow
MinCostFlow

Kotolin
SCC
MaxFlow
MinCostFlow

Ruby
SCC
MaxFlow
MinCostFlow

Crystal
SCC
MaxFlow
MinCostFlow

This is just renaming the names, so it may be worth considering before the language update.

@TonalidadeHidrica @mizar I prefer "Expected2". What do you think?


Tower middleware for Hyper

The generic tower middleware cannot access data fields of request. We can create specific Hyper middleware, where Service<R: hyper::Request>.
The request looks like:
Request {
    method: GET,
    uri: /,
    version: HTTP/1.1,
    headers: {
        "host": "localhost:3000",
        "user-agent": "curl/7.78.0",
        "accept": "*/*",
    },
    body: Body(
        Empty,
    ),
}

metriki-warp can be sunset after this feature. Reqwest middleware can also benefit from this.


Redirect issue

I am not sure about this but after logging in I am being redirected to this url "http://localhost:4200/#/id_token". I am trying to redirect elsewhere in my angular app

Use the state param in the request to keep state across the redirect. Check the samples.

The sample just has window.location = "/"; in the signin-callback.html page?

perhaps the wrong sample: https://github.com/IdentityModel/oidc-client-js/blob/dev/samples/VanillaJS/public/code-identityserver-sample.js#L112 and in the call back the user has a state prop

Turns out it was not redirecting because the redirect url in my config.cs file was not pointing to the exact  location of the oidc-redirect page. I was missing the '/assets' in the path.
"http://localhost:4200/assets/oidc-login-redirect.html",


error: no kind "CertificateRequest" is registered for version "cert-manager.io/v1alpha2" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"

certificaterequest.cert-manager.io/myingress-cert  allways show waiting and the logs show belows:
error: no kind "CertificateRequest" is registered for version "cert-manager.io/v1alpha2" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
the cluster:
apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    email<EMAIL_ADDRESS>    server: https://acme-staging-v02.api.letsencrypt.org/directory
    privateKeySecretRef:
      name: example-issuer-account-key
    solvers:
    - http01:
        ingress:
          class: traefik

the ingress:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: "traefik"
    acme.cert-manager.io/http01-ingress-class: "traefik"
    cert-manager.io/cluster-issuer: "letsencrypt-staging"
  name: traefik-a-com
  namespace: default
spec:
  rules:
  - host: traefik.a.com
    http:
      paths:
      - backend:
          serviceName: myservice
          servicePort: 80
        path: /
  tls: # < placing a host in the TLS config will indicate a certificate should be created
  - hosts:
    - traefik.a.com
    secretName: myingress-cert # < cert-manager will store the created certificate in this secret.

Can you provide some more information here, and fill out the issue template?
Notably:

where are you seeing this error message?
what are you trying to do?
can you share the output of kubectl get crd | grep cert-manager.io?

Can you provide some more information here, and fill out the issue template?
Notably:

where are you seeing this error message?
kubectl get CertificateRequest -A
kubectl logs CertificateRequest XXXX

what are you trying to do?
i want to use cert-manager to autoly create a cert on ingress of traefik.
can you share the output of kubectl get crd | grep cert-manager.io?
[root@master ~]# kubectl get crd | grep cert-manager.io certificaterequests.cert-manager.io   2019-11-23T07:26:33Z certificates.cert-manager.io          2019-11-23T07:26:33Z challenges.acme.cert-manager.io       2019-11-23T07:26:31Z clusterissuers.cert-manager.io        2019-11-23T07:26:44Z issuers.cert-manager.io               2019-11-23T07:26:54Z orders.acme.cert-manager.io           2019-11-23T07:26:31Z [root@master ~]#

Can you provide some more information here, and fill out the issue template?
Notably:

where are you seeing this error message?
what are you trying to do?
can you share the output of kubectl get crd | grep cert-manager.io?

above show the answer.

[root@master ~]# kubectl logs certificaterequests/myingress-cert-2737322635

It's not possible to use kuebctl logs on a CertificateRequest resource - you should instead use kubectl describe to describe information about the resource. logs is meant to be used for Pod-like resources only :).
You can see more info on this process here: https://cert-manager.io/docs/faq/acme/


[Feature Request] Make it more portable

Hello,
I wanted to upgrade ScreenToGif (my favorite GIF recorder) but now it requires NET. I don't have admin rights on my laptop so I'm using ScreenToGif portable, but NET requires admin rights. That is sad.

Hi, ScreenToGif was never truly portable.
Older versions required .NET Framework 4.8, which was installed by default.
In order for it to be truly portable, the download size will go up to 78MB.
I could add that download option in future releases.

@NickeManarin
That would be cool. I don't care much about portability - but bundling ScreenToGif with the needed .NET6 files insetad of requiring a systemwide .NET6 install would be very welcome. Other popular software (such as paint.net) already go this way.

I am here to second that motion. Was quite surprised to see that I needed to install some additional .net software in order to use ScreenToGif. This is soo sad.
From a developer point of view, WHY do you need the newer .Net framework - What part of it, is it that you need ?

Right.
Let's use the right terms here, it's not sad, it's inconvenient for you guys (and I got your points). :)
I'll make it more convenient, not an issue.
Also, I don't need to explain myself as to why I did something with my project (but it's easy to guess why).

Next version (v2.36) will be distributed with a Full and Light package types.
The updater will know how to handle each installation mode.
Also, I'll distribute the app as an msix package.


ISPN-8114 Ignore failing test again

Test is still failing in master, it needs further looking into.

Integrated, thanks @galderz


Whisper - Sending message before request is accepted

How to reproduce:

Send request to user
Send message to that user
Accept the request

The message does not appear in his chat unless you refresh the page.

Still happened for me.
Refresh fixed it indeed.

Was not yet pushed to staging

Still happens

Moved to 1.7

The messages apear if you send more than 1 message before the request has been accepted.
If you send a request and then a message quickly after the other user doesn't get a request at all.


Accelerate Framework and how to use it

Hello!
I have an application that uses the Accelerate Framework and I'm wondering if there is a way to use it inside this Docker image? I'm aware that some stuff isn't ported over but information about package management etc isn't easy to find for Swift on Docker.
Thanks!

@FuzzOli87 Apologies for the delay in getting back to you.
I'm sorry to say that, AFAIK, Accelerate is a closed source library that provides API on top of several open source libraries: https://stackoverflow.com/questions/16432028/what-are-the-open-source-equivalents-of-apples-accelerate-framework-libraries
If I were you, I'd write an API compatible "Hackcelerate" Swift package that reimplements the parts of Accelerate that you need, leveraging BLAS/LAPACK and maybe a few other libs as necessary.
The Swift users mailing list would probably also have some ideas.
If you need any help getting any of these old C libs running under docker-swift, let us know!


Update to compatibility with urql verson 4

There where some incompatible changes https://github.com/urql-graphql/urql/issues/3114

Published: https://www.npmjs.com/package/jotai-urql/v/0.6.0


[Site] Fixed image skewing

Signed-off-by: Nikhil Sharma<EMAIL_ADDRESS>Description
This PR fixes #228
Notes for Reviewers

Let me know if there are any other changes we can make.

Signed commits

[x] Yes, I signed my commits.

Thank you for this recording, @adithyaakrishna. 👍


Stack overflow in regexp matcher

Run Treadmill REPL
Type '(import :std/'
Get an error "error in process filter: Stack overflow in regexp matcher"

This was being caused by using an inefficient method for grabbing results from a REPL process buffer. Additionally, the communication between Emacs and Gerbil was extremely chatty — it sent every match and its "etymology", when the latter is only necessary if Company asks for meta about the match.
All of this has been fixed and Emacs no longer explodes on my machine. Please update both gerbil-treadmill and emacs-treadmill and verify that you no longer get an error.


Add initial support for WebAssembly Interface Types

This commit adds initial support for WebAssembly Interface
Types to wasmtime. This is all intended to be quite
experimental, so experimental in fact that even the name of the
proposal is still in flux. (this has otherwise been known as "host
bindings" or "webidl bindings" or "wasm bindings").
The goal of this commit is to start adding support the wasmtime set of
crates for WebAssembly Interface Types. A new wasmtime-interface-types
crate has been added with very basic support for dynamically invoking
and inspecting the various bindings of a module. This is in turn powered
by the wasm-webidl-bindings crate which is shared with the
wasm-bindgen CLI tool as a producer of this section.
Currently the only integration in wasmtime-the-binary itself is that
when passed the --invoke argument the CLI will now attempt to invoke
the target function with arguments as parsed from the command line
itself. For example if you export a function like:
fn render(&str) -> String

Then passing --invoke render will require one argument on the command
line, which is the first argument as a string, and the return value is
printed to the console. This differs from today's interpretation of
--invoke where it is a failure if the invoked function takes more than
one argument and the return values are currently ignored.
This is intended to also be the basis of embedding wasmtime in other
contexts which also want to consume WebAssembly interface types. A
Python extension is also added to this repository which implements the
wasmtime package on PyPI. This Python extension is intended to make it
as easy as pip3 install wasmtime to load a WebAssembly file with
WebAssembly Interface Types into Python. Extensions for other languages
is of course possible as well!
One of the major missing pieces from this is handling imported functions
with interface bindings. Currently the embedding support doesn't have
much ability to support handling imports ergonomically, so it's intended
that this will be included in a follow-up patch.
Co-authored-by: Yury Delendik<EMAIL_ADDRESS>

Some more logistical notes on this are:

There are three new builders of the Python extension all present on CI (Windows/Mac/Linux). The main thing to note here is that a nightly version of Rust is used (pinned for now to hopefully reduce breakage)
The Python extension is published to GitHub artifacts for releases in the same manner that the wasmtime binary itself is.
This is a sort of mass-import of what Yury/I have been working on. It's had some rounds of pre-review in preparation, but this is all likely to be in a state of flux for some time now!

@yurydelendik, @alexcrichton, @sunfishcode, and I have reviewed this over the last few days, so it's good to go!


Move lines up and down with multiple selections

It includes the merge of master and the resolution of the conflicts with the autoindent on line moves feature added recently.

@lpommers I'm sorry, I just realized I made the PR against master and not the move-lines-up-and-down-with-multiple-selections branch. Could you please merge back your master version into the branch? Or do you prefer I start a new PR instead?

@abe33 haha it's quite alright, I did notice it and thought it a bit odd, but decided to move it forward. I was actually trying to move merge my master back in but was getting several conflicts. perhaps a new PR would be simpler? :bow: thanks again for all the help with this issue :pray:

@lpommers done :)


Add Sponsor Martello

Branch
master
Trello Card
N/A
Description
Martello is now supporting cuHacking!  Also trying out the new sponsor label.
Tests
N/A

 Add Martello Sponsor Logo


Missing XMLData for documentation

Hi, I'm trying to build the documentation to fix a minor error, but it seems like the XML definitions are missing from this repository.
After npm install and npm run start I get the following error:
Failed to compile

./src/documentation/XMLDocumentation.js
Module not found: Can't resolve './data/XMLData' in './src/documentation'

This error occurred during the build time and cannot be dismissed.

Hi, Thanks for bringing this to my attention. The data directory that file is in inadvertently matched a rule in the root .gitignore file and I didn't notice. I've added a rule to the gh-pages/.gitignore file and committed XMLData.js in 42ed1eb

Hi, Thanks for bringing this to my attention. The data directory that file is in inadvertently matched a rule in the root .gitignore file and I didn't notice. I've added a rule to the gh-pages/.gitignore file and committed XMLData.js in 42ed1eb

Thanks, this works now :+1:

Thanks, this works now :+1:


Jongiddy/j2 templates

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

DCOS-ID JIRA title / short description.

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@alekspv please review and merge to the integration branch.
cc @vadymzagorodko @jongiddy @sergiimatusEPAM

👍 thanks


Update UI to reflect changes in Teams.

UI Changes

Add left column to reflect list of teams through TeamListPanel and TeamCard.
Add right column to reflect the details of the currently selected Team.

Notes

Styling for the left column to highlight the currently selected team not implemented yet.
Look out for styling and javadocs, naming may not have been the most consistent.

Fixes #41

Codecov Report
Base: 68.67% // Head: 66.58% // Decreases project coverage by -2.09% :warning:

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

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #37      +/-   ##
============================================
- Coverage     68.67%   66.58%   -2.10%
- Complexity      500      501       +1
============================================
  Files            96      101       +5
  Lines          1574     1649      +75
  Branches        169      178       +9
============================================
+ Hits           1081     1098      +17
- Misses          447      503      +56
- Partials         46       48       +2

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/logic/LogicManager.java
65.21% <0.00%> (-9.79%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
87.50% <0.00%> (-1.60%)
:arrow_down:

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/TeamCard.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/ui/TeamDetailsCard.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/ui/TeamDetailsPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/TeamListPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/AddressBook.java
87.50% <100.00%> (-1.98%)
:arrow_down:

...in/java/seedu/address/storage/JsonAdaptedTeam.java
72.41% <0.00%> (-5.37%)
:arrow_down:

... and 4 more

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

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


ppx_irmin: implicitly depend on Base

Temporarily solution to Travis CI errors caused by the latest release of Ppxlib. A better solution would be to just require the latest version, but other packages in the repository are not compatible with it (see https://github.com/mirage/irmin/pull/1063).

Travis is happy 🎉


[analyzer] Implement function tearoff equality corner cases

This is the analyzer specific version of https://github.com/dart-lang/sdk/issues/46834, which has the details. It seems likely that there is no work to do here, because the analyzer configurations are passing the tests.

P3 only based on this being a theoretical problem and our tests passing; we should still confirm this is OK.

@eernstg - is this part of the constructor tearoff work?
cc @srawlins

@devoncarew

is this part of the constructor tearoff work?

Leaf and I discussed this. There should not be a need to guard this feature by an experiment flag, but it would be good if it can fit into the schedule with the October milestone.

@srawlins  - pinging this issue. This is currently part of the work we expect to ship for the next stable - branching in ~8 days. Do you expect to have this done by then (or should we re-plan)?


Why aren't key classes exported?

I want to specialize GFs on key types, like private/public keys. Why isn't, for example, IRONCLAD::RSA-PRIVATE-KEY exported? Should consumers of these keys be agnostic to the kind of key?

The public/private key types could indeed be useful for users' generic functions.
Done in commit b37613704605685a8c80579ebfb18a5363232407.

Thanks! This is useful so that, for instance, a generic function can't accidentally accept a public key for signage, or a private key for verification.


Create Anthony Lewis

Can you add my school
acad.txt

@AnthonyMLewis Anthony I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


HADOOP-17794. Add a sample configuration to use ZKDelegationTokenSecretManager in Hadoop KMS

JIRA: HADOOP-17794
Documented the following parameters:
hadoop.kms.authentication.zk-dt-secret-manager.enable
hadoop.kms.authentication.zk-dt-secret-manager.kerberos.keytab
hadoop.kms.authentication.zk-dt-secret-manager.kerberos.principal
hadoop.kms.authentication.zk-dt-secret-manager.zkConnectionString
hadoop.kms.authentication.zk-dt-secret-manager.znodeWorkingPath
hadoop.kms.authentication.zk-dt-secret-manager.zkAuthType

They are required when setting up multiple KMS instances.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 39s

trunk passed

+1 :green_heart:
mvnsite
0m 34s

trunk passed

+1 :green_heart:
shadedclient
45m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 22s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 23s

the patch passed

+1 :green_heart:
shadedclient
13m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

62m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3190/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3190

Optional Tests
dupname asflicense mvnsite codespell

uname
Linux c1256f465fc6 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 194aa0c6be7fa73e1c92bba4922f8193d24af0c7

Max. process+thread count
674 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-kms U: hadoop-common-project/hadoop-kms

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3190/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m 45s

trunk passed

+1 :green_heart:
mvnsite
0m 36s

trunk passed

+1 :green_heart:
shadedclient
57m 42s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 26s

the patch passed

+1 :green_heart:
shadedclient
17m 46s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

79m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3190/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3190

Optional Tests
dupname asflicense mvnsite codespell

uname
Linux e1a1755ad4cd 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4b6c0fdb072a7d1861fb9e9e3f8dbc9ec2855e7b

Max. process+thread count
721 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-kms U: hadoop-common-project/hadoop-kms

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3190/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Merged it. Thanks for your contribution, @aajisaka!

Thank you @tasanuma.


CUDA error: an illegal memory access was encountered

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (3.x).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
master branch https://github.com/open-mmlab/mmdetection
Environment
mask2former pytorch需要什么版本，我的是1.7.0 ,CUDA11.4
总报错 CUDA error: an illegal memory access was encountered
Reproduces the problem - code sample
NO
Reproduces the problem - command or script
NO
Reproduces the problem - error message
NO
Additional information
NO

Please provide more information. Illegal memory access maybe caused by many different reasons. One common reason is the number of classes is incorrect when you train your own dataset.


Revert "Ezyweb updates Sep 2018"

Reverts microweber/microweber#491

sorry merged into wrong branch. can you send PR for the dev branch


Support For getDevices API

Hey there,
First off, love what you're doing! Please keep up the good work!
I was wondering if there was any plan to support the OT.getDevices API documented here?:
https://tokbox.com/opentok/tutorials/publish-stream/js/#set_camera_mic
Or if there was another way we could go about specifying using the back camera for example?

+1 for support in Cordova plugin

I really do not that getDevices in the Cordova plugin too! (..)
I would like to connect a Bluetooth microphone instead of the internal iOS/Android mic.
Does anybody know how to do that in a Cordova App?


DSND-3109: Add delta at to delete delta test data

This PR updates the tests to ensure the consumer can handle a delta_at field on an incoming delete delta.
DSND-3109

CI: Security warnings found!


Prepare next dev cycle v1.35.1-dev

/kind bug
It seems that when the release-v1.35 branch was created, the VERSION file was not updated accordingly. (cc @kris94)
Hence, this leads release of v1.35.1 to fail - ref https://concourse.ci.gardener.cloud/teams/gardener/pipelines/gardener-release-v1.35/jobs/release-v1.35-release-job/builds/1.
Release note:

NONE

/hold

/unhold
Many thanks to @AndreasBurger (for removing the empty release commit that was leftover from the failed release run) and to @timebertt (for fixing the v1.35.0 images).


Inspirational Visualization / Tool examples in the wild

To inform our prototype design process, we want inspirational examples that we can draw from about how we could present our data. These can be:

Visualizations from other projects
Mockups
Real-life demos, like the one we made for our survey landing page: http://housinginsights.org/tool/

Coordinate with the data dictionary ticket ( #38 ) and read the project overview for the types of data sources we will want to be representing.

Check out housinginsights.org/resources/inspiration for a list of relevant websites


Exclude recent intermediate images when doing cleanup

Recent ones must be excluded because they might be being used in other
builds running simultaneously.
Fixes #481

/test-all


Show more detailed warning message when account eth is too low for fee

Expected: Show how much more ETH is required for transaction fee if account already has ETH
Actual: Message states to add ETH to account even though account already has ETH

addressed by: #321


non extraction of french title from page 2 of pdf file

Grobid don't extract the french title of Inria research report.
Maybe it's because it is on page 2 with other french metadata like abstract and keywords...
Does it possibile to retreive theses information for Hal ?
i put pdf file for example
RR-9099-1.pdf
Alain

Hello Alain!
Yes this would be very hard to extract because, somehow, all the metadata "slots" are already filled by the English metadata.
One solution is to run GROBID on the PDF after removing the first 3 pages - of course then you won't have the English metadata... and you will have to merge the biblio records afterwards :/


helm rollback returns release not found

Tried helm rollback couple of times before.
I am getting the error below, when I try to rollback again.
Error: release: not found

I am able to see the same release with helm list but not able to helm rollback.
Output of helm version: v3.11.2
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.5", GitCommit:"804d6167111f6858541cef440ccc53887fbbc96a", GitTreeState:"clean", BuildDate:"2022-12-08T10:15:02Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.5-gke.1200", GitCommit:"4eb57372b0f0ac0023caca078161b75185febeef", GitTreeState:"clean", BuildDate:"2023-06-01T19:55:11Z", GoVersion:"go1.19.9 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform: GKE

@prashant-shahi please show the whole process.

When I deleted the history versions of the release and kept only the latest version of the release, I encountered the error when doing "helm rollback xxx".
Please check if your release has any historical versions.

https://github.com/helm/helm/pull/12290


BNB Transaction error

I'm trying to send 0.01 bnb to an address and I'm generating a raw transaction using this example
https://github.com/trustwallet/wallet-core/blob/master/android/app/src/androidTest/java/com/trustwallet/core/app/blockchains/binance/TestBinanceTransactionSigning.kt
when I'm trying to broadcast the transaction in this link
https://bscscan.com/pushTx
I'm getting this error
Unable To Broadcast Txn : {"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"rlp: too few elements for types.LegacyTx"}}
This is my code
`       val privateKey =
PrivateKey("private_key".toHexBytes())
val address = BINANCE.deriveAddress(privateKey)
Log.e("address", address.toString())
val publicKey = privateKey.getPublicKeySecp256k1(true)
    val signingInput = Binance.SigningInput.newBuilder()
    signingInput.chainId = "Binance-Chain-Nile"
    signingInput.accountNumber = 4355033
    signingInput.sequence = 1

    signingInput.privateKey = ByteString.copyFrom(privateKey.data())

    val token = Binance.SendOrder.Token.newBuilder()
    token.denom = "BNB"
    token.amount = 10000

    val input = Binance.SendOrder.Input.newBuilder()
    input.address = ByteString.copyFrom(AnyAddress(publicKey, BINANCE).data())
    input.addAllCoins(listOf(token.build()))

    val output =  Binance.SendOrder.Output.newBuilder()
    output.address = ByteString.copyFrom(AnyAddress("bnb16urwafzcvusuw7kdvc8ptaay55zjnw0jeccvr2", BINANCE).data())
    output.addAllCoins(listOf(token.build()))

    val sendOrder = Binance.SendOrder.newBuilder()
    sendOrder.addAllInputs(listOf(input.build()))
    sendOrder.addAllOutputs(listOf(output.build()))

    signingInput.sendOrder = sendOrder.build()

    val sign: SigningOutput = AnySigner.sign(signingInput.build(), BINANCE, SigningOutput.parser())
    val signBytes = sign.encoded.toByteArray()
    Log.e("tx", signBytes.toHex())`

Is there any problem in my code?

The sample is for Binance chain, not Binance Smart Chain, while you tried to push to BSC.  BC and BSC are quite different.  For BSC, it is very similar to Ethereum; see the Eth samples.


Investigate alternatives to publishing artifacts via logging commands in the Arcade SDK

[ ] This issue is blocking
[ ] This issue is causing unreasonable pain

Currently, the publishing infrastructure in the Arcade SDK uses the Artifact upload logging commands to publish intermediate artifacts to the PackageArtifacts and BlobArtifacts containers.
https://github.com/search?q=repo%3Adotnet%2Farcade+artifact.upload&type=code
Artifacts uploaded via this mechanism skip the scans that the 1ES pipeline templates enforce on each artifact upload.
We should look into alternatives that allow the 1ES templates to scan the artifacts the Arcade SDK produces

Move makes even more sense now that I've noticed some of our code e.g. in dotnet-helix-machines (see VstsBuildContextLogger in particular) also uses ##vso[artifact.upload ...] logging commands.

[ ] Start a conversation with 1ES

[ ] If 1ES doesn't have the bandwidth here, start a conversation with AzDO

[ ] Come up with a design (in case we need to implement a solution in an emergency)
[ ] determine priority after the above items are complete

Also see chat from the "Publishing Artifacts Alternatives" meeting.


Module parse failed: Unexpected token

Hello,
Thank you for your project -- I am running into an issue when using a package in expo  which contains simple-common-utils as a dependency. I have been diving into babel and webloaders to no avail...
I am wondering if you can offer any guidance on the matter
`./node_modules/simple-common-utils/js/StaticUtils.js 2:20
Module parse failed: Unexpected token (2:20)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| export default class StaticUtils {

static colorNames = {
|     aliceblue: 0xf0f8ffff,
|     antiquewhite: 0xfaebd7ff,

`

Hello,
Glad you find it useful.
The only thing I can imagine is that the word static introduces the confusion. Try commenting out everything and declare a dummy static field.
I will add this file to my expo project tomorrow and will update you about the result.

@RobinBobin Thanks for the quick response -- I agree static is suspect..
The strange thing is, I can still run the project if I copy the entire StaticUtils.js to my root directory. My current thinking is that webpack is not applied to /node_modules
So far I haven't been able to get around it with "ignore" in babel config. I'm interested to hear how your testing goes.
This is specifically with react-native-google-drive-api-wrapper

Hmm... And why aren't you using expo-google-sign-in?

I guess you've already seen this: https://www.npmjs.com/package/expo-google-drive-api-wrapper. Sadly, this is an old version. It would be interesting for me to convert my current version to expo but I don't have much spare time for that 🙁.


Add deployment instructions and scripts

This PR includes adds instructions to README.md for how this release can be deployed with BOSH.
We've also added some scripts and an ops file to make the setup process easier.
This is intended to be a rough first stab at this. It doesn't attempt to be robust or cover all edge cases (and it explicitly turns off Eirini-based staging). We figured that even if folks run into problems running these scripts, it may help to have them for reference, and we can improve the quality over time.
Thanks,
Jen + @jspawar

After discussing with Vlad, his comment doesn't block this PR. I will merge this. Feel free to address it in a separate PR if you want to.


Problem connecting to printer on armhf version

Hi folks !
I'm struggling to connect a K8200 printer to a rpi3 running repetier-server 0.86.2 armhf.
Everything works fine on a PC with the 0.86.2 windows version, but on the Rpi i'm stuck on the second step of the printer setup.
I define my firmware, Marlin, my baudRate at 250000, then I tried every port that seems involved (/dev/serial/by-id/usb-FTDI_FT231X_USB_UART_DA00DDXD-if00-port0, /dev/serial/by-path/platform-3f980000.usb-usb-0:1.2:1.0-port0, /dev/tty/USB0, /dev/tty/AMA0, )
but whatever I may try, I'm stuck on "En attente de connexion", that forbids me to go to step 3, and to see my printer connected.
I tried to use the reset button on the printer board, as unplugging-plugging the USB, with no more luck.
/var/lib/Repetier-Server/logs/server.log don't shown any error.
Note : CartesianVirtual port works fine !
What else can I do ? Is there other relevant logs anywhere ?

Did you use our pi image or just install the server?
One reason might be that user repetierserver is not member of group dialout which is required to connect on linux systems. Normally setup adds user to group but had users where this failed and having similar problems.

Thank you Mr. repetier for putting me back on the right track !
It was indeed a permission issue on /dev/ttyUSB0, that I temporary solved with : chmod 777 /dev/ttyUSB0
(this trick didn't survive a reboot)
Strange thing, I tried to fix this permanenlty using :
sudo adduser repetierserver dialout
sudo adduser repetierserver tty

it seems to be effective, as stated in my /etc/group file:

tty:x:5:repetierserver,pi
dialout:x:20:pi,repetierserver,
but didn't solve the permission issue.

Anyway, I'm fine with the chmod trick, so we can close this ticket :)

Thank you Mr. repetier for putting me back on the right track !
It was indeed a permission issue on /dev/ttyUSB0, that I temporary solved with : chmod 777 /dev/ttyUSB0
(this trick didn't survive a reboot)
Strange thing, I tried to fix this permanenlty using :
sudo adduser repetierserver dialout
sudo adduser repetierserver tty

it seems to be effective, as stated in my /etc/group file:

tty:x:5:repetierserver,pi
dialout:x:20:pi,repetierserver,

but didn't solve the permission issue.
Anyway, I'm fine with the chmod trick, so we can close this ticket :)

Why adding group pi? Who is the owner of the serial? For me it is dialout
crw-rw----  1 root dialout 166,   0 Nov 11 08:11 ttyACM0


Robot 3.1.2: rebot --merge not working for tests failed with different reason

We use below command for merging tests after re-run -
rebot --outputdir results --output merged.xml --nostatusrc --merge --noncritical skipped results/original.xml results/rerun.xml
It used to work fine with the Robot Framework version we used previously i.e. 3.0.2
After upgrading Robot Framework to 3.1.2, we face below issue.
In re-run, when test fails with a different reason then, the final report after merging gives two entries in the Robot report as shown in below screenshot.

But, when test fails with same reason in re-run then, result is getting merged as shown in below image.

Can anyone please address this issue?

This should not happen. Please provide a simple executable example demonstrating the issue so that we can investigate it.


TELESTION-473 Use DATA_DIR in logger sample

Use the configurations data directory instead of the PWD to save the log messages.

Current dependencies on/for this PR:

main

PR #421   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 26, 6:34 PM: @pklaschka merged this pull request with Graphite.


Add subtyping between CalledMethodsPredicate annotations

Based on a reviewer's suggestion in the paper. This is a rare case, but should resolve that TODO nicely and makes the design much more elegant.

@mernst this is ready for your review again

My only slight concern here is taking the dependence on the SMT solver.  Does it have a lot of transitive deps?  Having lots of dependencies can occasionally lead to weird issues with annotation processors that users have a hard time working around, e.g., if another processor depends on a different version of some library.  So I generally try to minimize 3rd-party dependencies for annotation processors.

There are two possibly-dangerous dependencies in the dependency tree for the solver:

Guava, which it has set to 28.0-jre. That's probably fine - everything already depends on Guava anyway.
org.checkerframework:checker-qual:2.5.2, which is a very old version of the qualifier libraries. That's presumably only a dependency because they have annotations, so using a later version should be fine.

Javaparser's only dependency is on the JDK.

Ok, sounds good.  One other question.  Since we are pulling in an SMT solver, can we get rid of this dependency?
    // For the @CalledMethodsPredicate evaluation
    implementation "org.springframework:spring-expression:5.1.7.RELEASE"

There might be downsides to using the SMT solver for this (ugly, slower, etc.).  Just thought I'd ask.

Probably. I'll look into it and make a second PR if it makes sense.

@mernst I've addressed your comments. I think I could refactor this even more to make the interface cleaner between the rest of the checker and the evaluator, but I'm going to wait on that until I do a PR that removes the SPEL dependency, which will be a follow-up to this one.

I'd like to cut a new release before this change lands.  I plan to do so tonight.  I will comment again when that is done

Ok, I've cut release 0.1.7 and pushed it to Maven Central


fixed typo "city" -> "state"

Noticed "region" line was set to "city", maybe copy-paste error from line 189?
According to Apple docs for CNPostalAddress it seems this field is called "state"?  I left the resulting property name as "region" so as to not make a breaking change for anyone currently using it.

Let me know if I am wrong in either of those assumptions.

What does the android implementation put into this field?  Ideally we want to keep the functionality the same

I think android has both city and state https://developer.android.com/reference/android/provider/ContactsContract.CommonDataKinds.StructuredPostal.html hence the confusion. We may have to perform a breaking change to get to a lowest-common-denominator api.

I mean what does the android implementation do in this project?

Here: https://github.com/rt2zz/react-native-contacts/blob/master/android/src/main/java/com/rt2zz/reactnativecontacts/ContactsProvider.java#L337
Looks like city and region are supported.  Can we do the same in iOS?

Looking at the android docs, "region" is equivalent to "state".  I don't see a separate "state" field in the Android docs:

REGION
A state, province, county (in Ireland), Land (in Germany), departement (in France), etc

I've assigned the IOS "state" field to "region" in the receiving object (which was already there in the previous code) so it should match the android implementation and no fields are added/removed from the user's perspective.

Sorry to bother, but was that previous explanation acceptable?  If not, how can I clear it up or make changes to the code that would make it okay to merge?  Thanks.

Things should be obvious. If the android docs lack state but instead mention region then the api response should have region even if it returns state and region. The api exposed by this library should be the union of both apis.
@hsubox76 please review (and optionally link me to the) android docs and make the appropriate changes. Submit a matching change to https://github.com/morenoh149/react-native-contacts-test for extra consideration. Thanks for the effort.

Changed to add both state and region (with identical data) in both IOS and Android.
Android docs
StructuredPostal class has region but not state
IOS docs
CNPostalAddress has state but not region
Resulting react-native-contacts object will contain both state and region properties, with identical data (from whichever field that native OS has populated).


Evaluation parallele bug fix

Evaluation batch parallel processing bug fixed
Bug: https://github.com/Agenta-AI/agenta/issues/1358

@aakrem @mmabrouk

@vishalvanpariya Thanks a lot for the PR!
@aybruhm I think there is a confusion in the issue number. The issue that @aakrem has created is for a different feature (the one that you have cited). However this PR resolves another bug, right now we are not calling LLM apps in batches as we say we do! Each batch calls are made in sequence and not in parallel as they should be. This is why evaluation is taking an eternity for long test sets.
So to summarize, this does not close #1358 , however it fixes a bug without an issue right now.
Can you please review the code @aybruhm accordingly. Thank you!

Thanks again for the PR @vishalvanpariya ! If I understand correctly, we are adding nest_asynco to be able to nest run_batch calls. Is there a way to change the logic so that we don't have the problem and we don't need to use nest_asyncio? It seems nest_asyncio.apply() patches asyncio which I am not very keen to as it might have side effects (what are your thoughts @aybruhm ?)

Yes, you're right. I am also concerned about patching the event loop as it may result in unpredictable behaviour.
@vishalvanpariya here's what I suggest doing:
async def run_batch(start_idx: int):
        # ... (existing code up to the loop)

        tasks = []  # Store the tasks for parallel execution
        for index in range(start_idx, end_idx):
            task = asyncio.create_task(run_with_retry(
                uri,
                testset_data[index],
                parameters,
                max_retries,
                retry_delay,
                openapi_parameters,
            ))
            tasks.append(task)

        # Gather results of all tasks
        results = await asyncio.gather(*tasks)
        for result in results:
            list_of_app_outputs.append(result)
            print(f"Adding outputs to batch {start_idx}")

Thank you a lot @vishalvanpariya ! We have fixed the bug in a different PR. It should be live in the next oss release in an hour or so. Sorry it took so long

@all-contributors please add @vishalvanpariya for code

Thanks @mmabrouk


clarify section header in Quickstart article

Although the article title doesn't specify AdventureWorksLT, AdventureWorksLT is what's created by its instruction.  If this article is dedicated to AdventureWorksLT, then please add another article that instructs how to create other databases.  Thanks.

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

ID: 3da2d20f-0457-b8af-2f72-84741e8cb81b
Version Independent ID: 3bcd4ccd-9b70-65d0-a720-57fd9a566767
Content: Create a single database - Azure SQL Database
Content Source: articles/sql-database/sql-database-single-database-get-started.md
Service: sql-database
Sub-service: single-database
GitHub Login: @sachinpMSFT
Microsoft Alias: ninarn

Thanks for the feedback! We are currently investigating and will update you shortly.

@rootsmusic The result of what is getting created depends on the data source you are using in the additional settings portion of the creation. The values being Sample, Blank and Backup.
When Sample is used it only creates the AdventureWorksLT is created.

When you use the blank as the option, it just creates the shell of the DB and you can create your schema and tables in this blank DB. This link explains the same in detail.
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-design-first-database#create-a-blank-single-database

The last option is to restore a geo replicated back up from a Azure server and use the same. Here is the link about geo replicated backups
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-recovery-using-backups#geo-restore

Hope this helps. Please get back to us if any other question.

The result of what is getting created depends on the data source you are using in the additional settings portion of the creation. The values being Sample, Blank and Backup.

@NavtejSaini-MSFT, please clarify the section header  that its section is to "create a single database using AdventureWorksLT".  I also suggest adding another section about using backup data sources (I was looking to learn how to create a single database from the backup version of AdventureWorks2016.bak).  Thanks.

@rootsmusic Currently the restore from .bak files is not supported for the Azure SQL single DB. If you use the Sample Data source while creation it will always create the AdventureWorksLT.
This idea is present in our User Voice channel for Azure SQL. You can up vote the same.
https://feedback.azure.com/forums/217321-sql-database/suggestions/14904228-backup-and-restore-azure-database-to-and-from-bak
You have two options now to do what is needed:

Create a Azure SQL Managed instance and restore the bak file. As above link tells you this is possible in Managed instances now. Below link explains that in detail.
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-get-started-restore

If there is an obligation to use Azure SQL Single DB, restore the back up on your local SQL server(if you have that) or create a SQL VM in azure and use it to restore this back up and use following methods to export it to your single DB server.
Here is link to create the VM:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/quickstart-sql-vm-create-portal
Here is the link for different methods to export the restored DB on VM to move to Azure SQL Single DB
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-single-database-migrate

@rootsmusic We are going ahead and closing this thread. Hope the threads in comment above must have helped you.


Port autoscale learning rate feature from mmclassification

The --autoscale-lr  switch for training in mmclassification is really handy. This pull request copies the code for that feature from mmclassification

 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.

After submitting this I think I realized that this feature is broken in mmclassification and so this pull request which uses the same implementation is also broken: I think the point at which it tries to scale the learning rate is after a separate process has already been launched for each GPU, so it always thinks it's running on a single GPU and scales accordingly. I think this would be a really useful feature so you don't have to manually keep the learning rate adjust for the number of GPUs, but I think the implementation that I took from mmclassification isn't the way to do it.


Leaderboard Issue

@DelhinRharl
Hey there!!

[ ] You have implemented all the requirements and the code is perfectly functional. Good Job

Thanks!


printrun: unstable-2015-03-10 -> 1.6.0

Motivation for this change
From unstable git to latest release.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Readme says Python 3 is required. Will you change python27Packages to python3Packages and check everything works as expected?

@prusnak I think Python 3 version is the current master branch (unreleased), while this bump is related to 1.x branch that still uses Python 2.

Tested it and works (this package mess up with nixpkgs env so I can't post build results).
BTW, all binaries have .py extension, ideally this should be renamed, but it is better to do it in another PR.

I think with the package being around for a number of years with .py names, renaming at this stage might break people's workflow. Don't know what the best practice would be, inclined to leave as is until the next major release (likely on python3).

The commit message is still wrong:
printrun -> unstable-2015-03-10 -> 1.6.0
Should be:
printrun: unstable-2015-03-10 -> 1.6.0

The commit message is still wrong:
printrun -> unstable-2015-03-10 -> 1.6.0
Should be:
printrun: unstable-2015-03-10 -> 1.6.0

Note that 1.6.0 is over 3 years old hence #90272

Note that 1.6.0 is over 3 years old hence #90272


Player cannot paddle boats in water

Boats cannot be controlled while in water.
Version: 1.0.1+1.20
Geyser MC: 2.1.1-SNAPSHOT

Unable to reproduce. Please send a full log

https://github.com/onebeastchris/Hurricane-Fabric/commit/7c6296e99fcb2461c1e7d9c3f6ff56b183279e5b
fixed in this commit; will backport & upload to modrinth in a minute. Thanks for reporting!


Add a Sample folder and project

Show how to apply set up the attribute to work with a Controller action and (separately) an Ardalis.ApiEndpoint
See some examples here in a similar version: https://github.com/fooberichu150/composite-model-binding/blob/main/WebAppNetCore/Controllers/DemoController.cs

Assigning my self, will make a MR. Thank you @ardalis .


Evaluation appears zero success rate

Dear Allen,
I want to evaluate the policy performance just by ddpm pre-training, without fine-tuning. So I choose the lift task, because it seems easier than other tasks from robomimic. But when I run the lift-img experiment and borrow the config from cfg/robomimic/eval/can/eval_diffusion_mlp_img.yaml, I just change the env_name and set use_ddim=False, I get the zero success rate after training 8000 epoches.
I didn't change other code. Can you share the evaluate config of the lift-img task for ddpm pre-training, I don't know what's the problem causing this error.
These are my training and evaluating configs .
defaults:
  - _self_
hydra:
  run:
    dir: ${logdir}
_target_: agent.pretrain.train_diffusion_agent.TrainDiffusionAgent

name: ${env}_pre_diffusion_mlp_img_ta${horizon_steps}_td${denoising_steps}
logdir: ${oc.env:DPPO_LOG_DIR}/robomimic-pretrain/${name}/${now:%Y-%m-%d}_${now:%H-%M-%S}_${seed}
train_dataset_path: ${oc.env:DPPO_DATA_DIR}/robomimic/${env}-img/train.npz

seed: 42
device: cuda:0
env: lift
obs_dim: 9  # proprioception only
action_dim: 7
denoising_steps: 100
horizon_steps: 4
cond_steps: 1
img_cond_steps: 1

wandb:
  entity: ${oc.env:DPPO_WANDB_ENTITY}
  project: robomimic-${env}-pretrain
  run: ${now:%H-%M-%S}_${name}

shape_meta:
  obs:
    rgb:
      shape: [3, 96, 96]  # not counting img_cond_steps
    state:
      shape: [9]
  action:
    shape: [7]

train:
  n_epochs: 8000
  batch_size: 256
  learning_rate: 1e-4
  weight_decay: 1e-6
  lr_scheduler:
    first_cycle_steps: 8000
    warmup_steps: 100
    min_lr: 1e-5
  save_model_freq: 500

model:
  _target_: model.diffusion.diffusion.DiffusionModel
  predict_epsilon: True
  denoised_clip_value: 1.0
  network:
    _target_: model.diffusion.mlp_diffusion.VisionDiffusionMLP
    backbone:
      _target_: model.common.vit.VitEncoder
      obs_shape: ${shape_meta.obs.rgb.shape}
      num_channel: ${eval:'${shape_meta.obs.rgb.shape[0]} * ${img_cond_steps}'} # each image patch is history concatenated
      cfg:
        patch_size: 8
        depth: 1
        embed_dim: 128
        num_heads: 4
        embed_style: embed2
        embed_norm: 0
    img_cond_steps: ${img_cond_steps}
    augment: True
    spatial_emb: 128
    time_dim: 32
    mlp_dims: [512, 512, 512]
    residual_style: True
    cond_dim: ${eval:'${obs_dim} * ${cond_steps}'}
    horizon_steps: ${horizon_steps}
    action_dim: ${action_dim}
  horizon_steps: ${horizon_steps}
  obs_dim: ${obs_dim}
  action_dim: ${action_dim}
  denoising_steps: ${denoising_steps}
  device: ${device}

ema:
  decay: 0.995

train_dataset:
  _target_: agent.dataset.sequence.StitchedSequenceDataset
  use_img: True
  dataset_path: ${train_dataset_path}
  horizon_steps: ${horizon_steps}
  max_n_episodes: 100
  cond_steps: ${cond_steps}
  img_cond_steps: ${img_cond_steps}
  device: ${device}

defaults:
  - _self_
hydra:
  run:
    dir: ${logdir}
_target_: agent.eval.eval_diffusion_img_agent.EvalImgDiffusionAgent

name: ${env_name}_eval_diffusion_mlp_img_ta${horizon_steps}_td${denoising_steps}
logdir: ${oc.env:DPPO_LOG_DIR}/robomimic-eval/${name}/${now:%Y-%m-%d}_${now:%H-%M-%S}_${seed}
base_policy_path: ${oc.env:DPPO_LOG_DIR}/robomimic-pretrain/lift_pre_diffusion_mlp_img_ta4_td100/2024-11-15_16-23-35_42/checkpoint/state_8000.pt
robomimic_env_cfg_path: cfg/robomimic/env_meta/${env_name}-img.json
normalization_path: ${oc.env:DPPO_DATA_DIR}/robomimic/${env_name}-img/normalization.npz

seed: 42
device: cuda:0
env_name: lift
obs_dim: 9  # proprioception only
action_dim: 7
denoising_steps: 100
horizon_steps: 4
cond_steps: 1
img_cond_steps: 1
act_steps: 4

n_steps: 300  # each episode takes max_episode_steps / act_steps steps
render_num: 0

env:
  n_envs: 50
  name: ${env_name}
  best_reward_threshold_for_success: 1
  max_episode_steps: 300
  save_video: False
  use_image_obs: True
  wrappers:
    robomimic_image:
      normalization_path: ${normalization_path}
      low_dim_keys: ['robot0_eef_pos',
                    'robot0_eef_quat',
                    'robot0_gripper_qpos']
      image_keys: ['robot0_eye_in_hand_image']
      shape_meta: ${shape_meta}
    multi_step:
      n_obs_steps: ${cond_steps}
      n_action_steps: ${act_steps}
      max_episode_steps: ${env.max_episode_steps}
      reset_within_step: True

shape_meta:
  obs:
    rgb:
      shape: [3, 96, 96]  # not counting img_cond_steps
    state:
      shape: [9]
  action:
    shape: [7]

model:
  _target_: model.diffusion.diffusion.DiffusionModel
  predict_epsilon: True
  denoised_clip_value: 1.0
  network:
    _target_: model.diffusion.mlp_diffusion.VisionDiffusionMLP
    backbone:
      _target_: model.common.vit.VitEncoder
      obs_shape: ${shape_meta.obs.rgb.shape}
      num_channel: ${eval:'${shape_meta.obs.rgb.shape[0]} * ${img_cond_steps}'} # each image patch is history concatenated
      img_h: ${shape_meta.obs.rgb.shape[1]}
      img_w: ${shape_meta.obs.rgb.shape[2]}
      cfg:
        patch_size: 8
        depth: 1
        embed_dim: 128
        num_heads: 4
        embed_style: embed2
        embed_norm: 0
    augment: True
    spatial_emb: 128
    time_dim: 32
    mlp_dims: [512, 512, 512]
    residual_style: True
    img_cond_steps: ${img_cond_steps}
    cond_dim: ${eval:'${obs_dim} * ${cond_steps}'}
    horizon_steps: ${horizon_steps}
    action_dim: ${action_dim}
  horizon_steps: ${horizon_steps}
  obs_dim: ${obs_dim}
  action_dim: ${action_dim}
  denoising_steps: ${denoising_steps}
  device: ${device}

Hey! This is a bit odd, so you pre-trained a new policy, right?
I also suggest trying out an earlier checkpoint. I recently fixed the issue of slow pre-training so if you are using the recent main branch, image training should only need 1000-2000 epochs to reach very high success rate.
I also suggest recording the video and see the behavior. Let me know how it goes!

I just ran this eval config (without DDIM) on the original checkpoint with the current main branch, and it showed 73% success rate
defaults:
  - _self_
hydra:
  run:
    dir: ${logdir}
_target_: agent.eval.eval_diffusion_img_agent.EvalImgDiffusionAgent

name: ${env_name}_eval_diffusion_mlp_img_ta${horizon_steps}_td${denoising_steps}
logdir: ${oc.env:DPPO_LOG_DIR}/robomimic-eval/${name}/${now:%Y-%m-%d}_${now:%H-%M-%S}_${seed}
base_policy_path: ${oc.env:DPPO_LOG_DIR}/robomimic-pretrain/lift/lift_pre_diffusion_mlp_img_ta4_td100/2024-07-30_22-24-35/checkpoint/state_2500.pt
robomimic_env_cfg_path: cfg/robomimic/env_meta/${env_name}-img.json
normalization_path: ${oc.env:DPPO_DATA_DIR}/robomimic/${env_name}-img/normalization.npz

seed: 42
device: cuda:0
env_name: lift
obs_dim: 9
action_dim: 7
denoising_steps: 100
cond_steps: 1
img_cond_steps: 1
horizon_steps: 4
act_steps: 4
use_ddim: False
ddim_steps: 5

n_steps: 300  # each episode takes max_episode_steps / act_steps steps
render_num: 0

env:
  n_envs: 50
  name: ${env_name}
  best_reward_threshold_for_success: 1
  max_episode_steps: 300
  save_video: False
  use_image_obs: True
  wrappers:
    robomimic_image:
      normalization_path: ${normalization_path}
      low_dim_keys: ['robot0_eef_pos',
                     'robot0_eef_quat',
                     'robot0_gripper_qpos']
      image_keys: ['robot0_eye_in_hand_image']
      shape_meta: ${shape_meta}
    multi_step:
      n_obs_steps: ${cond_steps}
      n_action_steps: ${act_steps}
      max_episode_steps: ${env.max_episode_steps}
      reset_within_step: True

shape_meta:
  obs:
    rgb:
      shape: [3, 96, 96]
    state:
      shape: [9]
  action:
    shape: [7]

model:
  _target_: model.diffusion.diffusion.DiffusionModel
  predict_epsilon: True
  denoised_clip_value: 1.0
  randn_clip_value: 3
  #
  use_ddim: ${use_ddim}
  ddim_steps: ${ddim_steps}
  network_path: ${base_policy_path}
  network:
    _target_: model.diffusion.mlp_diffusion.VisionDiffusionMLP
    backbone:
      _target_: model.common.vit.VitEncoder
      obs_shape: ${shape_meta.obs.rgb.shape}
      num_channel: ${eval:'3 * ${img_cond_steps}'} # each image patch is history concatenated
      img_h: ${shape_meta.obs.rgb.shape[1]}
      img_w: ${shape_meta.obs.rgb.shape[2]}
      cfg:
        patch_size: 8
        depth: 1
        embed_dim: 128
        num_heads: 4
        embed_style: embed2
        embed_norm: 0
    augment: False
    spatial_emb: 128
    time_dim: 32
    mlp_dims: [512, 512, 512]
    residual_style: True
    img_cond_steps: ${img_cond_steps}
    cond_dim: ${eval:'${obs_dim} * ${cond_steps}'}
    horizon_steps: ${horizon_steps}
    action_dim: ${action_dim}
  horizon_steps: ${horizon_steps}
  obs_dim: ${obs_dim}
  action_dim: ${action_dim}
  denoising_steps: ${denoising_steps}
  device: ${device}

Thanks a lot, I will check out the code.

No worries!
No I never tried to pre-train with DDIM. I don't think pre-training with DDIM is a common practice? or if it works at all. I think pre-training with DDPM is totally fine.

Thanks a lot!!!


[AMBARI-23231] Server service_check does not get executed for new mpacks (dsen)

What changes were proposed in this pull request?
When running service check on client component that is not part of the service, the script name should be passed from the service metainfo that initiated the service check.
Also reverted client service checks skipping condition, this should be handled by metainfo changes
How was this patch tested?
Manually

Closing PR as it is over 6 months old.


Release/2.17.2

This release contains one change:

Fixes issue where Cardholder Name input field in headless would not accept spaces

Release checklist:

[x] Bump the version in .podspec file
[x] Commit and push change to release/2.17.2
[x] Add tag 2.17.2
[ ] Release via Spinnaker
[ ] Validate release on Cocoapods


Create ECS

Hi all,
starting from the predicate that our image exists (from ECR or docker hub), can we imagine a constructor that would take as argument the name of the image and, optionally, the cpu, the ram and the number of occurrences (etc. ?) and that would return as output the associated public ip :
service: my-app

provider:
    name: aws

plugins:
    - serverless-lift

constructs:

    # Include Lift constructs here

    my-service:
        type: ecs
        image: 'gotenberg' # from Docker hub for example

we could also specify a security group to complete the whole

Thanks for those details.
I think supporting ECS is out of the scope of serverless applications, and so out of Lift itself. But this is a perfect use case for custom constructs (#52).

and I'm waiting for it ;)


add blah.py script

it will rehash and update tools.json based on tools_source.json manifest file
Objects for each new tool MUST already exist in  tools.json

@Jason2866 pls check this out

@vortigont A big thank you from me, for the done work. With a quick look over it, everything needed seems to be there nkw. A few not needed entrys. But deleting stuff is quickly done. Will do the little work left.

to rehash a new tool from a release, need just update the url in tools.json, add "rehash":true key:val and run tool_rehash.py script. Hope this helps to automate it in future

@vortigont Yes, thanks a lot for the python tool. I had already a look at the tool code and noticed that it is very usefull to update or calculate the needed hash and size values!


Add unit tests for SAML profile adapter

Towards #2001

Praise: Thank you for doing this and increasing our test coverage! I think other than Shane's comments this looks good to me!

Please see the above non blocking comments


openning win form

how do i open the win form part of the source files (meaning the visual interface like you do with vb.net projects)

In the solution, press res.rc and it would bring you a list of resources, dialogs are probably the closest thing to winforms there

You don't, Windows Forms (WinForms) is a .NET technology so only available from .NET languages (VB.NET, C#, Managed C++) but WinFile is a traditional Win32 application written in C (with a little C++ added over the years)
However you can try the Dialog Editor to edit some of the dialogs but you're not going to be able to edit the main interface without playing around with C


Move db related basic functions to models/db

Since models becomes more and more big, splitting it becomes a task to refactor.
This PR create a new subpackage models/db and move common database functions to that package.
The next PRs should create business logic related subpackages of models and move related codes there. i.e. Moving all models/issue*.go to models/issues/.

Codecov Report

Merging #17075 (dbd002d) into main (b74a0f9) will decrease coverage by 0.00%.
The diff coverage is 68.75%.

@@            Coverage Diff             @@
##             main   #17075      +/-   ##
==========================================
- Coverage   45.28%   45.28%   -0.01%
==========================================
  Files         771      773       +2
  Lines       86767    86828      +61
==========================================
+ Hits        39293    39316      +23
- Misses      41119    41166      +47
+ Partials     6355     6346       -9

Impacted Files
Coverage Δ

cmd/cmd.go
44.18% <0.00%> (ø)

cmd/convert.go
0.00% <0.00%> (ø)

cmd/doctor.go
0.00% <0.00%> (ø)

cmd/dump.go
0.91% <0.00%> (ø)

cmd/migrate.go
0.00% <0.00%> (ø)

cmd/migrate_storage.go
0.00% <0.00%> (ø)

models/db/convert.go
0.00% <ø> (ø)

models/db/log.go
31.70% <ø> (ø)

models/db/sequence.go
0.00% <0.00%> (ø)

models/db/sql_postgres_with_schema.go
0.00% <ø> (ø)

... and 183 more

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 b74a0f9...dbd002d. Read the comment docs.