v 2.0

I have improved the program by adding a graphical environment to it. Now it is much easier for the user to open videos, put the section that he wants to convert to gif and convert the video to gif.
It also has more options, they are in the configuration menu. The user will be able to use watermarks and text for the gifs, being able to choose the text, color and positioning of the same within the gif

Hi does your version of vdo2gif utilize my code in vdo2gif.py?

Hi does your version of vdo2gif utilize my code in vdo2gif.py?

Hi there. The program uses your script.
First you go from video to video with ffmpeg (in the output video it comes out with the program's configuration options)
With that video, your program is used to convert it to gif with the program's options.
Here is a video where you can see how it works.
https://www.tiktok.com/@hoopsearring4ever/video/6999397507683847430?lang=es&is_copy_url=0&is_from_webapp=v1&sender_device=pc&sender_web_id=6991107558728041989

Hi Thank you for replying i'm happy you improve the code, but there's one last question, does your version work offline?

Hi Thank you for replying i'm happy you improve the code, but there's one last question, does your version work offline?
The program uses an API made by me.

This API returns a file name of the format year_month_day_hour_minutes_seconds
This is to avoid overwriting the output of the gif in case of saving multiple gifs on the same video.
If you accept the pull request, I will send you a second pull with the improved code. The problem of the relative paths and operation in Windows and Linux is fixed, as well as some bugs that I ignored, I have been testing it and it no longer gives errors. Greetings, my name is Ramon, nice to meet you

Hi I think your project is really cool, but it has deviated so much from my original intended purpose which is don't need a GUI and completely work offline. While the first purpose for not need a GUI is till fulfilled, the second purpose is not. I request you made the whole project completely work offline and made a second pull request. I'm closing this PR for now.


Setting bot endpoint take too long time to propagate

Repro steps

Go to Azure Portal
Find a Bot Channel Registration
Go to Settings blade
Modify the messaging endpoint to a new URL

Expected
Within a few minutes, using Direct Line token to connect to the service, it should point to the new message endpoint.
Actual, it took 20-30 minutes to reflect the changes. This hurt dev RTT a lot because it took way longer than a coffee break. And there are no indications when the change is sync-ed to all of the servers. This negative anticipation could probably impact CSAT/DSAT.

This was a bug on the service side. This is now fixed


Homebrew cask for VSCode

Can we get a Homebrew cask published for VSCode to make it faster and more automated to install?

https://formulae.brew.sh/cask/visual-studio-code here you are.


There is no Android app support

Did you tryed implementing anbox arm64?

https://github.com/anbox
https://github.com/Sailfish-On-Vince/anbox

No, I haven't tried to setup anbox. I don't plan to do so either. But Anbox is open source software and if someone wishes to work on it, please do so.

Closing as stale. Absence of Android support is clearly stated in README.


[GlobalOptimization] Support SetEncoding on batch matmul cases with producer CastOpInterface ops

This PR completes the SetEncoding plumbing discussed in https://github.com/openxla/iree/issues/15214

We can split this into 2 PRs if that makes more sense. I put the changes together for now, since they are related.

We can split this into 2 PRs if that makes more sense. I put the changes together for now, since they are related.

Given that you already have two separate commits, can you split it into 2 PRs?

This PR has been split into https://github.com/openxla/iree/pull/15371 and https://github.com/openxla/iree/pull/15372 now


bugfix: check if the value passed to transition is a token and then use the token value

What is the Issue?
https://github.com/modulz/stitches/issues/175

What kind of change does this PR introduce?
This PR is a bug fix.

What is the current behavior?
In the current behavior, we do not set transition property values if a token is passed instead of a value.

What is the new behavior?
In the new behavior, we will first check if the value passed is a token and if it is then we will use the token value to set properties of transition.
In case it's a normal value, we will continue to use that value.

Checklist:

[x] Tests
[x] Ready to be merged
[x] Issue Linked?

@hadihallak I need some help here in understanding how to deal with this scenario
tokens: {
  transitions: {
     slow: 'all 1000ms'
  }
}

This gets converted into a css variable like the following:
transitions: { slow: 'var(--transitions-slow)' }

Now when it reaches our shorthand parser, how do I get the value of transition-property and transition-duration from it?
Right now If I tweak the regex of easingMatch to
const easingMatch = /(cubic-bezier|steps)\(.*\)|ease|ease-in|ease-out|ease-in-out|linear|step-start|step-end/;

It gets's assigned to transitionProperty: var(--transitions-slow)
What I actually need is
transitionProperty: all
transitionDuration: 1000ms

@vivek12345
Good catch. yeah, this is making me wonder if having the whole transition rule as a token is a good idea.
Here is what I'm currently thinking:
A. we rework how transition tokens are stored in the tokens object so that they reflect longhand properties
B. Instead of generating a token for the whole transition value, we generate tokens for the parsed shorthand rule so for this:
tokens: {
  transitions: {
     slow: 'all 1000ms'
  }
}

we would internally parse it into two tokens:
  --transitions-slow-property: 'all'
  --transitions-slow-duration: '1000ms'

so that then when the tokens are used we are able to infer the name from the value so if the token value was slow we would check if the user has a token with that name in their tokens so tokens.transitions[value] and if we found that the user defined a value there we would infer the preparsed tokens so if we want the duration token we would do
--transitions-${value}-duration
I think option B would provide the best experience but I'm also keen to know your opinion.
@peduarte what do you think?

My $0.02 - I'd prefer to set transition tokens longhand but combine them shorthand in the styles object: transition: all $slow $customEasing
This way you can have a few duration tokens and a few custom easing tokens without having to maintain tokens of every combo.
Not sure how feasible that is, though. I know transition property is kinda weird, and I haven't dug into the code.

Thank you for your inputs @hadihallak . After thinking about both the approaches
A) Seems easier for us but then the users would have to type all the tokens for long hand values
B) We can do this and I like this approach too, although I do have a question around it
In the second case will we also change our tokens to something like
transitions: {
    'slow-property: 'var(--transitions-slow-property)',
    'slow-duration': 'var(--transitions-slow-duration)'
},

If we do not do this then our transition token will continue to have the following structure
transitions: {
    slow: "all 1000ms"
},

In the above case then we would actually not be using css vars.
We can discuss if I have understood this incorrectly.
Also why do convert these values into vars? shorthand parser is anyway going to parse them then why add a css variable?

After giving this another thought as suggested by @hadihallak , here is one approach that I think we can try
When someone defines a transition token like the following
tokens: {
  transitions: {
     slow: 'all 1000ms'
  }
}

We will create two css variables for this
var(--transitions-slow-property)
var(--transitions-slow-duration)

Internally we will convert the tokens object into something like this
tokens: {
  transitions: {
     slow: {
       original: "all 1000ms",
       property: "all",
       duration: "1000ms"
     }
  }
}

With this,  in shorthand parser we will first check if a value is a token. So if someone passes value as "slow"
We will check tokens.transitions[value] and get an object consisting of the following structure
{
   original: "all 1000ms",
   property:  var(--transitions-slow-property),
   duration:  var(--transitions-slow-duration)
}

So now if a value exists in our token object we would parse the original value through chain parser and then when we are setting the value we will set the property like this:
css.transitionDuration = tokenValue ? tokenValue.duration : setChainedValue(css.transitionDuration, parsedValue);

Please help me understand if this approach sounds good

Have tried this with a sandbox here
https://codesandbox.io/s/react-stitches-forked-8rdye?file=/src/App.js
If the above approach looks good to us then I can update this PR with the changes.
For now the changes are in my forked repo
https://github.com/vivek12345/stitches/pull/5

@hadihallak any advice here?

/cc @jonathantneal

@vivek12345 Thank you so much for all of the hard work on this PR and apologies for the late response  🙏  my notifications are all over the place so missed this one.
Yeah this seems to be working very well 👍  but I'm also wondering if we can at the same time support the longhand tokens object that @imjoshellis mentioned 🤔
@jonathantneal what do you think? how do you think we should handle this?

In general, I like this, because I think eventually most properties will need to be parsed. I like that it’s creating a structure I suspect we could also apply to other properties. Is that right?
This is good stuff. 👍

One thing I hadn’t fully considered was that this current PR changes what the author has written, while the comment @vivek12345 represents something that preserves original intentions. Are you open to updating the PR so your latest suggestion may be reviewed more thoroughly?

@jonathantneal yes you are absolutely right on this. I will update the pr today. The reason I didn't update it before was to get some feedback around my approach.
Thank you for taking the time to review the approach and I will update the pr today.

Just wanted to pop in again and give a more clear description of the API I had imagined because I'm not sure if I was very articulate after re-reading my original comment.
With a tokens that looks like this:
tokens: {
  transitions: {
     slow: '1000ms',
     customEasing: 'cubic-bezier(.17,.67,.83,.67)'
  }
}

In the React styled composer, I could then do:
// ...
transition: "colors $slow $customEasing"

Which is similar to what I would naturally do as a workaround:
import {slow, customEasing} from '../cssVariables'

// ...
transition: `colors ${slow} ${customEasing}`

Hey, this is now working in the new beta canaries. Thanks


Rendering the tex string `"\left(\dots\right)" leads to a error

I tried to render the tex string
"\left(\dots\right)"

which works perfectly fine in regular LaTeX implementations. In KaTeX I got the following error:
KaTeX parse error: Expected '\right', got '\dots' at position 7: \left(\̲d̲o̲t̲s̲\right)

I'm using KaTeX out of Ember but this shouldn't make a difference as my Ember component just passes the string to the katex.render() function:
katex.render(tex, el, {
    displayMode: display
});

Oh, I just realized that \dots isn't supported by KaTeX. Feel free to close this issue unless you consider \dots not being supported an issue.

Yep, already #528.  Please use \cdots or \ldots until \dots gets implemented (or define a macro for \dots -> \ldots, which is what I do personally for now).

Thank you for your fast reply. That's what I'll do then.


Feat/dcmfoss 76

Implemented the exception handling system according to what was planned in the concept.
exceptions return a code, message and details.

Hi @Diogo12246,
could you please provide a better PR title, that describes what feature you add instead of just an issue number?


[vm/ffi] Introduce SizedNativeType

Split off from discussion on:

https://github.com/dart-lang/sdk/issues/54526

TODO:

[x] Use in  sizeOf and AllocatorAlloc.call.
[ ] Use in Struct/Union documentation and error messages.

I am wondering whether common operations or properties like Pointer<Uint8>.value, Pointer<Uint8> operator + (int offset) can also be added to SizedNativeType? This will simplify the usage like:
num getValue(int i0, int i1) {
  final ffi.Pointer<ffi.Uint8> pdata = dataPtr.$1;
  final (int, int, int) step = this.step;
  final MatType type = this.type;

  // https://github.com/opencv/opencv/blob/71d3237a093b60a27601c20e9ee6c3e52154e8b1/modules/core/include/opencv2/core/mat.inl.hpp#L894
  final ptr = pdata + i0 * step.$1;
  return switch (type.depth) {
    MatType.CV_8U => (ptr.cast<ffi.Uint8>() + i1).value,
    MatType.CV_8S => (ptr.cast<ffi.Int8>() + i1).value,
    MatType.CV_16U => (ptr.cast<ffi.Uint16>() + i1).value,
    MatType.CV_16S => (ptr.cast<ffi.Int16>() + i1).value,
    MatType.CV_32S => (ptr.cast<ffi.Int>() + i1).value,
    MatType.CV_32F => (ptr.cast<ffi.Float>() + i1).value,
    MatType.CV_64F => (ptr.cast<ffi.Double>() + i1).value,
    MatType.CV_16F => float16((ptr.cast<ffi.Uint16>() + i1).value),
    _ => throw UnsupportedError("Unsupported type: $type")
  };
}

As you can see, without common operations/fields defined in SizedNativeType, I have to test the desired pointer type to cast, but if they were defined, the above code can be simplified to:
num getValue<T extends ffi.SizedNativeType>(int i0, int i1) {
  final pdata = dataPtr.$1;
  final step = this.step;
  // https://github.com/opencv/opencv/blob/71d3237a093b60a27601c20e9ee6c3e52154e8b1/modules/core/include/opencv2/core/mat.inl.hpp#L894
  final ptr = pdata + i0 * step.$1;
  return (ptr.cast<T>() + i1).value;
}

I am wondering whether common operations or properties like Pointer<Uint8>.value, Pointer<Uint8> operator + (int offset) can also be added to SizedNativeType? This will simplify the usage like:

That will unfortunately not work. We cannot branch on the runtime type argument of Pointer. The type argument is always Never at runtime, because our goal is that a Pointer is just an int in the Dart runtime:

https://github.com/dart-lang/sdk/issues/50777

get it, thx~


RFP - Kugou

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://www.kugou.com/
Direct download URL for the software / installer : http://download.kugou.com/download/kugou_pc
Software summary / short description :
KuGou (Chinese: 酷狗音乐) is a Chinese music streaming and download service established in 2004 and owned by Tencent Music. It is the largest music streaming service in the world, with more than 450 million monthly active users.
Package Expectations
adding icons to the desktop

thanks for your help

Chocolatey package fails because Get-WebHeaders switch to HTTPS for download but the file can only been successfully downloaded in HTTP.
How to avoid to switch to HTTPS?

Invoke-WebRequest -Uri "http://download.kugou.com/download/kugou_pc" : It works as expected
Invoke-WebRequest -Uri "https://download.kugou.com/download/kugou_pc" : HTTP Status code 200 but It doesn't download the file.
cinst kugou -dv -s "."
(...)
WARNING: Url has SSL/TLS available, switching to HTTPS for download
Running Get-WebFileName -url 'https://download.kugou.com/download/kugou_pc' -defaultName 'kugouInstall.exe'
Using response url to determine file name. 'https://download.kugou.com/download/kugou_pc'
File name determined from url is 'kugou_pc'
Running Get-WebHeaders -url 'https://download.kugou.com/download/kugou_pc' -ErrorAction 'Stop'
Setting the UserAgent to 'chocolatey command line'
Request Headers:
'Accept':'/'
'User-Agent':'chocolatey command line'
Response Headers:
'Connection':'keep-alive'
'Keep-Alive':'timeout=20'
'Content-Length':'0'
'Content-Type':'text/plain'
'Date':'Thu, 15 Aug 2019 19:44:15 GMT'
'Server':'KugouCDN'

Sounds like the same issue we have with the nlite package.
Only way currently around it is to embedd the software (if the licensing and size allows it).
Issue related: https://github.com/chocolatey/choco/issues/1221
I will mark this issue as blocked for now.

@chtof Has there been any progress on this or are you waiting for https://github.com/chocolatey/choco/issues/1221 ?

I didn't find any license to allow to embed the package. Close as something like can't fix?


[WIP] Theta range

Closes #20
Checklist

[x] Tests are passing
[x] Docs were updated and workflow is passing
[ ] add Test

I think the current implementation does what you need because the two-argument atan function has only values in $[0,\pi]$ if and only if the first argument is not negative, which is always true for the transversal momentum.
With this, I would like to stay with the current implementation, because it is slightly faster than the usage of arccos, especially in coordinate systems that provide direct access to the transverse momentum.

I see what you mean for the range, it's likely correct. I'd add a test for it.
For the speed, I'd surprised to see that gain, but could well be I do not have an intuition.

Confirm that the range is what I want: I've added the test for the ranges.
Fill free to merge if happy


interface resolver

Hello,
I am trying to implement Node interface as per the relay spec.  @saward gave an example, and as I see in the starwars example,  I need to implement To* methods for all types which implements the interface. This makes the interface grow with the number of type implements it, and not able to split the resolver into multiple packages due to circular reference.
I wonder is it possible to check the method set of the concrete type, instead of the interface. In the below code, Node method of root resolver returns type resolver which implements NodeResolver interface (a single method), but has other methods to resolve the concrete type.
thank you,
bsr.
var Schema = `
schema {
    query: Query
}

interface Node {
    id: ID!
}

type Query {
    node(id: ID!): Node
}

type Human implements Node {
    id: ID!
}

type Droid implements Node {
    id: ID!
}
`

type NodeResolver interface {
    ID() graphql.ID
}

type Resolver struct{}

func (r *Resolver) Node(ctx context.Context, args *struct{ ID graphql.ID }) (NodeResolver, error) {
  tp := getTypeFromID(args.ID)
  switch tp {
    case "human":
      return &HumanResolver{getHumanOnID(string(args.ID))}
    case "droid":
      return &DroidResolver{getDroidOnID(string(args.ID))}
    default:
      return nil, fmt.Errorf("no fetcher for %s", tp)
  }
}

You are right. The current way did not permit any splitting into packages because it would always cause a cyclic dependency.
I've been thinking about it for a bit and I've come up with a new approach, see a15deed. Notice that I did not modify graphql-go itself, it is only a better way to structure the Go types that still resolve the GraphQL types in the same way.
Does it look good to you?

thanks a ton for quick solution. I will try out in an hour, and get back to you. thanks again.

that works great. thank you.


Added best_of to non-TGI ignored parameters

Overview
The solution PR for the issue #1943.
While deploying an Inference Endpoint with a Default container type (non-TGI server), some parameters are ignored.
The best_of parameter should be ignored too.
Solution

Add best_of to ignored parameters.

Impact

Non-TGI servers will be able to respond when the user uses the best_of parameter.

Additional Information
NA

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

All green! I'm merging now :)


delete button

add a delete button to each event post. this should only be visible to admins and creator of the post.

first part done, still need to work on second part

done


Check duplicate auth process

Check whether the duplicate can be obtained from Discord, what will be logged etc.

Fixed so the duplicate information is logged (discord id). And that Management user duplicate show command will show only authenticated duplicates


Make My Tickets Screen

All  placed orders of the user should be displayed in this section
working on it :+1:

@iamareebjamal I was having some difficulty. I thought of showing the event name of all the orders under a user. So my endpoint looks something like this.
   @GET("/v1/users/{id}/orders=?include=event")
I am able to retrieve the list of  event ids correctly but what I want is the list of events.
The list of events are returned in the included block from the server.
I am not able to retrieve it in the app.
Could you please help

@iamareebjamal This is exactly what I did
but the error that I get in the logs is
                                                                                java.lang.IllegalArgumentException: field org.fossasia.openevent.general.order.OrderUnderUser.event has type org.fossasia.openevent.general.event.Event, got org.fossasia.openevent.general.event.EventId

Where

https://github.com/fossasia/open-event-android/compare/development...nikit19:myTickets?expand=1
@iamareebjamal This is just a rough implementation to see if I am able to get the correct values. That's why didn't send a PR.
Is my POJO OrderUnderUser correct?

Yes, seems fine

                                                                                java.lang.IllegalArgumentException: field org.fossasia.openevent.general.order.OrderUnderUser.event has type org.fossasia.openevent.general.event.Event, got org.fossasia.openevent.general.event.EventId
@iamareebjamal This is the error that I get. Could this mean that the event that I am referring to is of type eventId? but this does not make sense according to me

Where does this happen?

In the orderUser function, the request is not successful so I get this message in the logs

Paste the response you are getting


Adding Schema.org, Twitter Cards and JSON+LD

I read somewhere we can configure Schema.org using React Helmet. Is it true that ReflexJS Starter uses RH? How to add that data in config.js and add schema.org and JSON+LD for my website?
Also, I'm getting this message while checking for SEO :

We didn't detect any Twitter Card tags on your webpage

Thank you.

Yeah the meta tags package uses React Helmet. See https://github.com/reflexjs/reflex/blob/master/packages/gatsby-plugin-metatags/src/metatags.js#L26
To add JSON+LD support you will need to shadow this component and add it.
We might support it in the future but not right away.

Thanks, I shadowed the component. However, I'm not able to add one. I went through this : https://github.com/LeKoArts/gatsby-starter-prismic/blob/master/src/components/SEO/SEO.jsx , that describes adding Schema and BreadCrumb.

Are you seeing any errors? What have you tried?

Yes, ./use-metatags not defined, and so on.

You'll need to update the import paths. Example
- import { useMetatags } from "./use-metatags"
+ import { useMetatags } from "@reflexjs/gatsby-plugin-metatags/src/use-metatags"

Thanks, all undefined errors are gone. So, I've added following JSON element.
  const schemaHome = {
        "@context" : "http://schema.org",
        "@type" : "Organization",
        "name" : "TwistBlogg",
       "url" : "https://www.twistblogg.com",
       "logo": null,
       "sameAs" : [
         "https://www.twitter.com/twistblogg",
         "https://www.facebook.com/twistblogg",
         "https://www.pinterest.com/twistblogg",
         "https://www.mix.com/twistblogg",
         "https://www.instagram.com/aman_invictus/",
         "https://www.linkedin.com/in/amanbhattarai/"
         ],
        "address": {
          "@type": "PostalAddress",
          "streetAddress": "Amardeep Tole NawalParasi",
          "addressRegion": "Province 5",
          "postalCode": "33007",
          "addressCountry": "Nepal"
        }
      }

And in return,
<script type="application/ld+json">{JSON.stringify(schemaHome)}</script>

It is working fine for Homepage, now for posts, I need to convert type to Article and insert author, publisher, modified_date,published_date and image as in following link : https://github.com/LeKoArts/gatsby-starter-prismic/blob/master/src/components/SEO/SEO.jsx#L89
Is there any way to specify condition like https://github.com/LeKoArts/gatsby-starter-prismic/blob/master/src/components/SEO/SEO.jsx#L154 ?

Any updates?

Hmm there's no way to back reference a Post node from a Metatag node right now. I guess one thing you could do it is pass a custom og type for Post in your config then use this value to do a check in metatags.js.
// gatsby-config.js
{
  resolve: `@reflexjs/gatsby-plugin-metatags`,
  options: {
    types: [
      {
        type: `Post`,
        defaults: {
          og: {
            type: `post`,
          },
        },
      },
    ],
  },
},

// metatags.js
const [{ title, description, og, twitter }] = metatags
if (og.type === "post") {
// Add schema for post.
}

So I added following Schema,
if (og.type === "post") {
    const schemaPost = {
        "@context": "https://schema.org",
        "@type": "BlogPosting",
        "headline": "This will be title ( Help me retrieve it dynamically )",
        "image": "(The featured image for each post)",
        "publisher": {
          "@type": "Organization",
          "name": "TwistBlogg",
          "url": "https://www.twistblogg.com",
          "logo": {
            "@type": "ImageObject",
            "url": "(logo located in images folder)",
            "width": "1200",
            "height": "630"
          }
        },
        "url": "(my_post_address)",
        "datePublished": "2020-01-06T00:00:00.000Z",
        "dateCreated": "2020-01-06T00:00:00.000Z",
        "dateModified": "2020-01-06T00:00:00.000Z",
        "description": "(meta_description)",
        "author": {
          "@type": "Person",
          "name": "(author_name)",
          "url": "https://www.twistblogg.com"
        },
        "mainEntityOfPage": {
          "@type": "WebPage",
          "@id": "https://www.twistblogg.com/blog/"
        }
    }
  }

and used stringfy as,
<script type="application/ld+json">{JSON.stringify(schemaPost)}</script>

However, it throws me an error : schemaPost not defined (2 times). I tried by setting let schemaPost = null and as expected null was return while inspecting.
Also, I've specified comments in above JSON, how can I retrieve them dynamically?
Thank you and stay safe.

Can you paste in the whole file please?

If you mean metatags.js, here it is :
import * as React from "react"
import { Helmet } from "react-helmet"
import { absoluteUrl } from "@reflexjs/utils"
import { useMetatags } from "@reflexjs/gatsby-plugin-metatags/src/use-metatags"
import { MetatagImage } from "@reflexjs/gatsby-plugin-metatags/src/metatag-image"
import { useSiteMetadata } from "@reflexjs/gatsby-plugin-metatags/src/use-sitemetadata"

export const Metatags = ({ pathname = "/" }) => {
  const metatags = useMetatags(pathname)
  const site = useSiteMetadata()

  const helmetProps = {
    defer: false,
    title: site.title,
    titleTemplate: `%s | ${site.title}`,
    htmlAttributes: {
      lang: "en",
    },
  }

  const schemaHome = {
       "@context" : "http://schema.org",
       "@type" : "Organization",
       "name" : "TwistBlogg",
       "url" : "https://www.twistblogg.com",
       "sameAs" : [
         "https://www.twitter.com/twistblogg",
         "https://www.facebook.com/twistblogg",
         "https://www.pinterest.com/twistblogg",
         "https://www.mix.com/twistblogg",
         "https://www.instagram.com/aman_invictus/",
         "https://www.linkedin.com/in/amanbhattarai/"
         ],
        "address": {
          "@type": "PostalAddress",
          "streetAddress": "Amardeep Tole NawalParasi",
          "addressRegion": "Province 5",
          "postalCode": "33007",
          "addressCountry": "Nepal"
        }
      }

  if (og.type === "post") {
        const schemaPost = {
            "@context": "https://schema.org",
            "@type": "BlogPosting",
            "headline": "This will be title ( Help me retrieve it dynamically )",
            "image": "(The featured image for each post)",
            "publisher": {
              "@type": "Organization",
              "name": "TwistBlogg",
              "url": "https://www.twistblogg.com",
              "logo": {
                "@type": "ImageObject",
                "url": "(logo located in images folder)",
                "width": "1200",
                "height": "630"
              }
            },
            "url": "(my_post_address)",
            "datePublished": "2020-01-06T00:00:00.000Z",
            "dateCreated": "2020-01-06T00:00:00.000Z",
            "dateModified": "2020-01-06T00:00:00.000Z",
            "description": "(meta_description)",
            "author": {
              "@type": "Person",
              "name": "(author_name)",
              "url": "https://www.twistblogg.com"
            },
            "mainEntityOfPage": {
              "@type": "WebPage",
              "@id": "https://www.twistblogg.com/blog/"
            }
        }
      }

  if (!metatags) return <Helmet {...helmetProps} />

  const [{ title, description, og, twitter }] = metatags

  return (
    <React.Fragment>
      <Helmet {...helmetProps} title={title}>
        <link rel="canonical" href={absoluteUrl(pathname, site.siteUrl)} />
        <meta name="title" content={title} />
        <meta name="description" content={description || site.description} />
        <meta
          name="viewport"
          content="width=device-width,initial-scale=1,shrink-to-fit=no,viewport-fit=cover"
        />
        <script type="application/ld+json">{JSON.stringify(schemaHome)}</script>
        {og.type === "post" && <script type="application/ld+json">{JSON.stringify(schemaPost)}</script>}
        {site.title && <meta property="og:site_name" content={site.title} />}
        {og.title && <meta property="og:title" content={og.title} />}
        <meta property="og:url" content={absoluteUrl(pathname, site.siteUrl)} />
        {og.type && <meta property="og:type" content={og.type} />}
        {og.description && (
          <meta property="og:description" content={og.description} />
        )}

        {twitter.title && (
          <meta property="twitter:title" content={twitter.title} />
        )}
        {pathname && (
          <meta
            property="twitter:url"
            content={absoluteUrl(pathname, site.siteUrl)}
          />
        )}
        {twitter.description && (
          <meta property="twitter:description" content={twitter.description} />
        )}
        {twitter.card && (
          <meta property="twitter:card" content={twitter.card} />
        )}
      </Helmet>

      {/* Workaround for JSX inside Helmet. See https://github.com/nfl/react-helmet/issues/342 */}
      {og.image && (
        <MetatagImage property="og:image" imagePath={og.image} site={site} />
      )}
      {twitter.image && (
        <MetatagImage
          property="twitter:image"
          imagePath={twitter.image}
          site={site}
        />
      )}
    </React.Fragment>
  )
}

and here's my config.js,
{
      resolve: "@reflexjs/gatsby-plugin-metatags",
      options: {
        global: {
          title: "TwistBlogg - Get Premium Blogger Tutorials",
          description: "TwistBlogg is an information resource site focused on SEO, Blogging, Themes, Widgets, Guides related to Social Media and Web Apps.",
          image: "social media.webp",
        },
        types: [
        {
          type: `Post`,
          defaults: {
            og: {
              type: `post`,
             },
           },
        },
          `MdxPage`,
          `MdxPost`,
          {
            type: `PostTag`,
            defaults: {
              title: (tag) => {tag.name},
            },
          },
        ],
        paths: [
          {
            pathname: `/blog{,/**}`,
            defaults: {
              title: `Blog | TwistBlogg - Get Premium Blogger Tutorials`,
            },
          },
        ],
      }
    },

Can you try making this change?
- {og.type === "post" && <script type="application/ld+json">{JSON.stringify(schemaPost)}</script>}
+ {og.type === "post" && schemaPost && <script type="application/ld+json">{JSON.stringify(schemaPost)}</script>}

I'm still getting those warnings and errors.

const metatags = useMetatags(pathname)
const site = useSiteMetadata()
+ let schemaPost = {}

if (og.type === "post") {
-        const schemaPost = {
+       schemaPost = {

Sorry there's not much else I can do here.

OK, the above doesn't work as well.
So, I'm planning to add it without setting any condition? Now, I need help with extracting individual values dynamically. For instance, how to retrieve post title within metatags.js? Is it possible?

const metatags = useMetatags(pathname)

const [{ title, description, og, twitter }] = metatags

Thanks, can you help me retrieve the values of fields available in my schemaPost? I have added text for fields I want to retrieve values for.
https://github.com/reflexjs/reflex/issues/38#issuecomment-679587163

Any update?

You can get it from metatags. Do a console.log(metatags) and inspect the content. It has all the info (such as title, image, description..etc) for the nodes.

Ok thanks :) In case, ReflexJS supports type field, re-open this issue.


I have added the section "Note:" with an example

Inside that section i have provided the information that when one can use if without curly braces

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

As there has been no response from your end for a while, we are closing this PR.
Feel free to request this PR to be reopened or create a new PR, if you still wish to make the changes you originally added plus any additional change requests asked of you.  Also, remember to update your fork, so you have the latest version of master in case it has changed significantly.
Happy Coding!


cut off elements on Samsung S10e

As mentioned on your reddit post, I've attached a screen shot of where a couple of elements sre being cut off 😀

Amazing, thank you for the screenshot! I'll make sure this gets fixed in the next release

Fixed in v2.1. Please have a look at the latest build and let me know if you are still seeing this issue!


[MINOR] Fix indexer typos

Change Logs
Fix typos in HoodieIndexer class
Impact
Only comments and descriptions
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change
none
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

There are test failures, can you check in local whether they can test pass?


⚠ Bofrost.es has degraded performance

In d3bfa8b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1638 ms

Resolved: Bofrost.es performance has improved in c880c4d after 6 minutes.


Use correct admonitions

The current style of Notes etc does not look nice. There must be a wrong use of admonitions. Please check how to do this correctly.
Read Existing Documentation
I have checked the following places for the error:

[ ] OpenMS Documentation Troubleshooting
[ ] OpenMS API Developer FAQs

Create OpenMS Bug Report
I have created the bug report in OpenMS for any pipeline errors.

[ ] OpenMS Open Issues

Description of the documentation bug

[ ] I have attached screenshots of the incorrect documentation

Expected behaviour

OpenMS Installation

Version:

Additional context

How does this look?

https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#admonition-directives

Much better, thanks!

Ref: https://github.com/OpenMS/OpenMS-docs/issues/28.

Ref: https://github.com/OpenMS/OpenMS-docs/pull/30#issuecomment-1133884271.

Hint
Important
Note
Warning
Tip

[ ] Update contributing guidelines.

There is an alternative option for admonitions that render in Github also:
https://www.markdownguide.org/hacks/#admonitions
Hacks | Markdown Guide
Workarounds for things not officially supported by Markdown.

https://discord.com/channels/832282841836159006/969233556788359228/978459215716839464
+1.

We're good with this:
https://github.com/OpenMS/OpenMS-docs/commit/c23dcf14231c3c73b27ff3eced65aad48c4e5903.
(everywhere)


FancyZones: prevent WinHookEventProc reentrancy bugs by serializing e…

Summary of the Pull Request

postpone WinHookEvent processing until FancyZones::WndProc function by PostMessages
in theory, we might start removing mutexes from FancyZones class, e.g. starting by replacing it with null_mutex and test if it still works

PR Checklist

[x] Applies to #961, #2654

Validation Steps Performed

played with FZ with various settings turned on and off, added and removed VDs
unit tests passed

added improvements from #2654 as a separate commit

Works good


Better communicate search_data spatial filter behavior expectations: polygon/bbox have no effect on "global" datasets, polygon/bbox do not clip/subset data

A "global" dataset would be one where each granule covers the entire earth. How can we communicate to users when this is the case, and their polygon/bbox query is having no effect? Since we only receive the matching granules, how can we know for sure that every granule in a collection is global so we can know that the users' spatial filters are having no effect? Is there perhaps a boolean in the CMR metadata we can use?

Description:
I am encountering an issue while attempting to access the GHRSST MUR dataset using the Earth Access API. I have followed the tutorial provided to access the dataset, and everything seems to work correctly until I attempt to filter the data using a bounding box or polygon.
Here's the process I've followed:

I use the earthaccess.search_data function to search for the dataset, specifying the required parameters including short_name, temporal, and optionally bounding_box or polygon.

mur_results = earthaccess.search_data(short_name = 'MUR-JPL-L4-GLOB-v4.1',
                                      polygon = [(115.10, -31.44),(115.10, -32.77),(115.77, -32.77),(115.77, -31.44), (115.10, -31.44)])

Upon searching, the API returns the expected number of granules based on the temporal parameter.
However, when I attempt to open the granules using xr.open_mfdataset(earthaccess.open(mur_results), engine='h5netcdf'), my PC becomes unresponsive, and the process gets stuck.
and it shows like :

I have also used the bounding_box and get the same output
mur_results = earthaccess.search_data(short_name = 'MUR-JPL-L4-GLOB-v4.1',bounding_box = ('115.10','-32.77','115.77','-31.44'))
Additionally, when I examine the output, I notice that entire latitude (-90, 90) and longitude ((-180, 180 ) values seem to be included, indicating that the bounding box or polygon filter is not functioning correctly.
This issue is causing significant inconvenience and delays in accessing the dataset, as well as consuming a large amount of system resources.
Another thing, I saw in the rest of that tutorial, there has been applied a slice of the dataset to subset the data. Then what is the application of polygon or bounding_box  not clear to me.

Could you please investigate why the bounding box or polygon filter is not working as expected and provide guidance on how to resolve this issue? Thank you.

This behavior could definitely be documented more clearly.  My suggestion is that we do this in three places: the docstrings for search_data and search_datasets; in the user guide/how to section of the docs; and also in a more detailed reference section that documents the behavior of CMR.
It is important to note that the result is expected and correct.  What needs to be made clear in the documentation is that, as @mfisher87 notes, is that earthaccess is performing a spatial filtering of data granules and not a subsetting or clipping of the dataset to the bounds.  In the spatial filtered search, granules with bounding boxes that intersect the bounding box or polygon passed the search_data are returned.  For datasets and granules that cover the globe, any valid bounding box or polygon will intersect.  For datasets, such as some of the MODIS or ICESat-2 products, that are global in extent but have granules that cover a smaller region, the behavior of search_datasets and search_data will be different.  In these cases, passing a spatial filter to search_data will return only those granules with bounding boxes that intersect the region of interest but search_datasets would return MODIS and ICESat-2 for any region of interest because the bounds of the dataset are global.
An approach for documenting this behavior could be:
For the docstrings, add the following notes to search_data
Complete granules with spatial bounds that intersect **bounding_box**  or **polygon** are returned.

For search_datasets we could add
Datasets with spatial bounds that intersect **bounding_box**  or **polygon** are returned.

For the user guide we can include examples of searches for global and regional datasets for search_datasets; and examples of searches for data granules that cover a region of the dataset bounds (e.g. MODIS or ICESat-2).
We can include a deep dive in the reference documentation that can be linked to from the user guide.  @asteiker created a figure demonstrating the difference between a search filter and a subset for a tutorial
https://nasa-openscapes.github.io/earthdata-cloud-cookbook/examples/Earthdata-cloud-clinic.html
We could produce a similar diagram for a global dataset.

For the user guide we can include examples of searches for global and regional datasets for search_datasets; and examples of searches for data granules that cover a region of the dataset bounds (e.g. MODIS or ICESat-2).

I think pictures illustrating the selection would go a long way in the user guide!


  I can't exactly report a bug either because it is in the internal namespace :(
WHY UNITY, why did you have to make such a wonderful feature in the internal namespace!


Add Tests to the app

closes #3

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c23552d). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #12   +/-   ##
=========================================
  Coverage          ?   93.04%
=========================================
  Files             ?       22
  Lines             ?      187
  Branches          ?        0
=========================================
  Hits              ?      174
  Misses            ?       13
  Partials          ?        0

Impacted Files
Coverage Δ

quran_text/urls.py
100% <ø> (ø)

quran_text/apps.py
100% <100%> (ø)

quran_text/serializers.py
100% <100%> (ø)

quran_tafseer/views.py
73.33% <100%> (ø)

tafseer_api/urls.py
100% <100%> (ø)

quran_text/admin.py
100% <100%> (ø)

quran_text/views.py
100% <100%> (ø)

quran_text/__init__.py
100% <100%> (ø)

quran_text/models.py
100% <100%> (ø)

quran_tafseer/__init__.py
100% <100%> (ø)

... and 1 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 c23552d...539b6ed. Read the comment docs.


[ModuleInterface] Don't print extensions only for a nested #if

rdar://71350414

@swift-ci Please smoke test


Remove this empty statement

Mentioned in #648
Issues found: https://sonarcloud.io/project/issues?resolved=false&rules=csharpsquid%3AS1116&id=nikcio_lucenenet
When these are extra ; characters, they are most likely just typos. For labeled continue statements, we inconsistently use ; and { }, both which trigger this warning. For those, we should probably use the latter approach and add an inline comment /* LUCENENET: intentionally blank */ between the curly brackets.

Fixed in #730


Link to multi-tenant samples is not pointing to multi-tenant samples

Link to multi-tenant samples is not pointing to multi-tenant samples

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

ID: 326f7173-a654-fda7-2438-6905da3fdbef
Version Independent ID: 7dbc5a10-9d61-26e1-f532-973b4bdfae9a
Content: How to build an app that can sign in any Azure AD user - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-convert-app-to-be-multi-tenant.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@mahoekst
Thanks for your feedback! We will investigate and update as appropriate.

I agree that those appear unrelated. I think it should be this list instead. https://github.com/Azure-samples?utf8=✓&query=multiten
I made a pull request for approval by @rwike77
https://github.com/MicrosoftDocs/azure-docs-pr/pull/93033

it seems this is still not updated?

I feel the GitHub link provided as a comment here is much more relevant than the current link in the Wiki.


r/Place dataset download link is 404 (now on Kaggle)

It seems like the official download link from Reddit is no longer working. Does anybody know an alternative download location? Otherwise, is there a place to host the download for free/very cheap?
Here's the Reddit comment where I first heard that the download was no longer working.
UPDATE: I've just uploaded the trimmed 1GB version to Kaggle. It's the end product of the Trim and Format step, so it has everything you need to generate color and heat maps. It just doesn't have the hashed user IDs.
I'll leave the issue open for now so it's easy for people to find.

It seems like the download is working now! I've updated the documentation and I'm closing the issue now.


CFP: per-node identities

Cilium Feature Proposal
Is your feature request related to a problem?
Yes, currently it is not possible to allow/block access from/to nodes by their labels. The only way one can do that is by specifying remote-node identity, but this also allows access from nodes in remote clusters (in a clustermesh).
  ingress:
  - fromEntities:
    - remote-node

Describe the feature you'd like
It should be possible to allow/block only specific nodes by their labels in CNPs.
apiVersion: v1
kind: Node
metadata:
  labels:
    kubernetes.io/role: worker

(Optional) Describe your proposed solution
There are a few parts of the solution:

NodeManager currently doesn't have a way to allocate ID so we would need to extend the IPCache interface with a known method AllocateIdentity() which allocated IDs based on labels and this would be then pushed to ipcache. The current remote-node identity is hardcoded here and then inserted into ipcache so we could replace this with proper ID. The problem related to this is that ipToIdentityCache is a map of IPs and their identities so single IP can basically be present only once. It's a question how the upgrade path would look like and the case when users would want to have both options available. This
brings us to 2nd point.

For the upgrade path we would imo need a new flag - something like --enable-per-node-identity which would supersede the "old" remote-node entity, but I haven't thought this through properly how old and new way could work together (meaning both options supported at the same time).

CNP would need a new section to allow only specific labels unrelated to endpoints. The question is if it should be somehow related to user-defined-entities or this as these should also be referenced by labels even though they have nothing to do with Node objects. A easy solution would be to add something like fromNodes with the same LabelSelector as EndpointSelector uses.

  endpointSelector:
    matchLabels:
      k8s-app: backend
  ingress:
  - fromNodes:
    - matchLabels:
        kubernetes.io/role: worker

2. For the upgrade path we would imo need a new flag - something like --enable-per-node-identity which would supersede the "old" remote-node entity

We would also need to support an upgrade path without packet loss. So nodes running with the new mode would have to understand encapsulated packets coming in with a remote-node identity.

The current remote-node identity is hardcoded here and then inserted into ipcache so we could replace this with proper ID.

What would the node IDs look like in the datapath? Would you use a subset of bits to indicate node IDs? Which bits would you use?

I had briefly wondered about this, broadly I see two approaches:

Allocate global identities for nodes like how pod identities are allocated. Then all nodes learn about these identities.
Allocate local identities on each node for each other node's labels. Do not transmit these on the wire.

I'm not sure I have a strong opinion on either approach yet. Broadly, (2) is less likely to interfere with other agents or require certain behaviour from existing agents in the cluster. (1) can have some nice properties about being closer to the way that pod identities work. We could for instance have nodes allocate an identity for their own node on startup after syncing with k8s.
One of the eventual complexities is that in the datapath, we need to make some decisions about how to handle packets towards remote nodes, and today we do this using identities. If nodes all have different identities, then this function may become more complex:
https://github.com/cilium/cilium/blob/69e4c6974891c161300889596f2029e489dded02/bpf/lib/identity.h#L14
This could be done with some pre-defined bit patterns, or by adjusting this function to use a map to determine which identities represent nodes.

For the upgrade path we would imo need a new flag - something like --enable-per-node-identity which would supersede the "old" remote-node entity

We would also need to support an upgrade path without packet loss. So nodes running with the new mode would have to understand encapsulated packets coming in with a remote-node identity.

Be aware that at the same time, during upgrade there are nodes with both new and old versions. So when the node with the new version transmits a packet with its own identity to an old node, the old node needs to understand how to handle the traffic from the new node.

CNP would need a new section to allow only specific labels unrelated to endpoints. The question is if it should be somehow related to https://github.com/cilium/cilium/issues/3553 or https://github.com/cilium/cilium/issues/10349 as these should also be referenced by labels even though they have nothing to do with Node objects. A easy solution would be to add something like fromNodes with the same LabelSelector as EndpointSelector uses.

CiliumClusterwideNetworkPolicy already has a NodeSelector kinda like this, we could reuse this.
One more question for your use cases - are you interested in this for "which nodes can my pod access" or "which nodes can my nodes access"? The former would be configured in CNP, while the latter would be CCNP.

Allocate local identities on each node for each other node's labels. Do not transmit these on the wire.

Today, we sometimes need to transmit the remote-node identity on the wire when running tunneling mode and doing a request from hostns@node1 to pod@node2. It may not be too hard to fix by keeping REMOTE_NODE_ID there and teaching the receiving side to lookup the inner source IP in its ipcache when seeing REMOTE_NODE_ID.

Thanks a lot for the insights.. our usecase is mostly "which nodes can my pod access" (i.e. the CNP), but sure.. we would be super happy with CCNP as well.

Hi guys, if possible please assign to me :) I will shortly send a PR (currently working on e2e tests).


save initial layer in X for adata_pre

Submission type

[ ] This submission adds a new dataset
[ ] This submission adds a new method
[ ] This submission adds a new metric
[ ] This submission adds a new task
[ ] This submission adds a new Docker image
[ ] This submission fixes a bug (link to related issue: )
[ ] This submission adds a new feature not listed above

Testing

[ ] This submission was written on a forked copy of openproblems
[ ] Nextflow test pipeline is passing on this base branch of this pull
request (include link to passed test on NF Tower found in GitHub Actions summary: )
[ ] If this pull request is not ready for review (including passing the Nextflow test
pipeline), I will open this PR as a draft (click on the down arrow next to the
"Create Pull Request" button)

Submission guidelines

[ ] This submission follows the guidelines in our
Contributing document
[ ] I have checked to ensure there aren't other open Pull Requests for the
same update/change

PR review checklist
This PR will be evaluated on the basis of the following checks:

[ ] The task addresses a valid open problem in single-cell analysis
[ ] The latest version of master is merged and tested
[ ] The methods/metrics are imported to __init__.py and were tested in the pipeline
[ ] Method and metric decorators are annotated with paper title, year, author, code
version, and date
[ ] The README gives an outline of the methods, metrics and datasets in the folder
[ ] The README provides a satisfactory task explanation (for new tasks)
[ ] The sample test data is appropriate to test implementation of all methods and
metrics (for new tasks)

Could you give some context... when is _get_split() used? And what happens to the adata.X that it's overwriting? Could this be needed at a later point by another metric?

As the metrics functions require an adata_pre and adata_post output, we need to generate the adata_pre object as this doesn't get passed by the openproblems api. the _get_split function generates the pre-integration anndata object


Basic documentation

Update any docs in README.md

[ ] Document imports
[ ] Documen thow operators work over arrays of different sizes
[ ] Document colors


Restyle Main Page

The main page needs restyling to make the elements fit better
If you have different ideas than below, consult group chat and we can chat about it

Increase size of Carousel element to width of page and fit right underneath navbar
Increase padding of the featured trip description and the trip title
Update about us blerb and connect it to the backend
Add a dragon link link
Create a section for interested participant who want to be a trip leader (Iffy on this one, maybe should be a page on it own)

Finished main page styling updates, however left out interested participant section. Maybe that can be looked at again another time


"Caches are still outdated; something is seriously wrong"

What's wrong
When I run straight-freeze-versions, I get prompted:
Caches are outdated, reload init-file? (y or n)

No matter if I answer y or n, I always get the error:
straight--ensure-profile-cache-valid: Caches are still outdated; something is seriously wrong

Directions to reproduce

Start Emacs.
Wait a while.  It never happens on a fresh start of Emacs.  This might happen after I edit a file or pull changes to a repo in in ~/.emacs.d/straight/repos, but I'm not 100% sure.
Run M-x straight-freeze-versions.

Version information

Emacs version:
GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)

Operating system:
Debian 10.2 "Buster"

I got the same problem. But I restarted emacs and ran again and it worked.
Any way to solve this without a restart.
Emacs: 28.0.50
Straight:  Sun Aug 30 06:31:29 2020
Ubuntu: 18.04 4 LTS

Yep, it still happens for me.  Always works on a clean start, never works on a session that's been running a while.

Is it possible that under some circumstances, loading your user-init-file will not result in the straight.el bootstrap getting run again? That would cause this behavior if you had interactively invoked straight-use-package between Emacs startup and running straight-freeze-versions.

Also, you can work around the bug by saying "no" when it asks to reload your init-file the first time, right?

Also, you can work around the bug by saying "no" when it asks to reload your init-file the first time, right?

No, the error happens no matter what I answer.  The only workaround is to restart Emacs.

Is it possible that under some circumstances, loading your user-init-file will not result in the straight.el bootstrap getting run again?

Yes.  My configuration is large, so I broke it out into separate files which get REQUIREd by init.el.  Straight's bootstrap code is inside one of those files, so it wouldn't get evaluated again if the init file was reloaded.

That would cause this behavior if you had interactively invoked straight-use-package between Emacs startup and running straight-freeze-versions.

Possible, I have long-lived sessions and sometimes try out one thing or another.

the error happens no matter what I answer. The only workaround is to restart Emacs.

Based on the implementation of straight--ensure-profile-cache-valid, this seems impossible to me:
https://github.com/raxod502/straight.el/blob/d27ad625838a679e0184ddf327bfea62760ae2fe/straight.el#L5494-L5506
I have been surprised many times before, however. Would you mind double-checking, just to be sure that something inexplicable is happening?

Straight's bootstrap code is inside one of those files, so it wouldn't get evaluated again if the init file was reloaded.

Well, that's the problem. You need to change this for your configuration to be compatible with straight.el. I will update the documentation to be clear on this.

the error happens no matter what I answer. The only workaround is to restart Emacs.

Based on the implementation of straight--ensure-profile-cache-valid, this seems impossible to me:
I have been surprised many times before, however. Would you mind double-checking, just to be sure that something inexplicable is happening?

I'm not able to reproduce this now, perhaps it changed since I filed the original bug.  It definitely was happening at that time.

Straight's bootstrap code is inside one of those files, so it wouldn't get evaluated again if the init file was reloaded.

Well, that's the problem. You need to change this for your configuration to be compatible with straight.el. I will update the documentation to be clear on this.

Is it sufficient to put only the bootstrap code in there (this stuff), or does straight expect every STRAIGHT-USE-PACKAGE to be reevaluated when the init file is reloaded?

does straight expect every STRAIGHT-USE-PACKAGE to be reevaluated when the init file is reloaded?

It expects every form to be re-evaluated. The reason for this is that otherwise there would be no way to identify which straight-use-package calls were part of your init-file, and which were part of random interactive experiments. straight.el tracks what happens in the course of loading your init-file, but if straight-use-package calls happen after init time, it needs to eval your init-file again to see what happens and if anything has changed, otherwise it would just be guesswork about what should be written into the lockfile.

does straight expect every STRAIGHT-USE-PACKAGE to be reevaluated when the init file is reloaded?

It expects every form to be re-evaluated. The reason for this is that otherwise there would be no way to identify which straight-use-package calls were part of your init-file, and which were part of random interactive experiments. straight.el tracks what happens in the course of loading your init-file, but if straight-use-package calls happen after init time, it needs to eval your init-file again to see what happens and if anything has changed, otherwise it would just be guesswork about what should be written into the lockfile.

That's unfortunate; my config is >4KLOC and I'm not jazzed about changing it, so I'm either going to have to live with the issue or abandon straight.
Instead of reloading the whole init file, what do you think about one or the other of:

Using called-interactively-p, or
Having a separate command (like straight-try-package) for the case where you want to demo a package without committing?

Unfortunately, both of your suggestions rely on the user remembering things. In my experience, this will never happen in the real world. As a concrete problem, my workflow for adding packages to my configuration is to write the (straight-use-package ...) form first, and then evaluate it with C-M-x. That would bypass both of your proposed checks.
I have to say, I'm not sure I understand why the config updates would be a burden. For example, you could just add a snippet of code at the top of your init-file to remove all your config's features from the features list. Then you can keep using require and it will work with straight.el.

This thread is being closed automatically by Tidier because it is labeled with "waiting on response" and has not seen any activity for 90 days. But don't worry—if you have any information that might advance the discussion, leave a comment and I will be happy to reopen the thread :)

Is (use-package foo :straight foo) enough to trigger this? I was under the impression that use-package only requires on the second call?

Can you be more specific about what you mean by "the reload"?


Microsoft.Data.SqlClient 4.1.0 error - provider: SSL Provider, error: 0 - The target principal name is incorrect

I met this
SqlError: 'A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.)'    Source: 'Framework Microsoft SqlClient Data Provider' Number: -2146893022 State: 0 Class: 20 Procedure: '' LineNumber: 0 Server: 'sql'
when I establish a connection from SharePoint to SQL server. SharePoint is using Microsoft.Data.SqlClient lib while SQL Server is still using System.Data.SqlClient.
I create a self-signed cert on sql server and import it to SharePoint server, set 'Force Encryption' to Yes and 'Trust Server Certificate' to Yes of both SQL Server network configuration and sql native client 11.0 configuration via SSCM.
Is it possible that sql server version isn't compatible with Microsoft.Data.SqlClient lib version?

@qizu0302 most probably the certificate is not made correctly.

Subject should be the FQDN of the machine. You can define other or friendly names as extensions.
System.Data.SqlClient and Microsoft.Data.SqlClient are client side libraries, so SQL server cannot use either of them. SSMS 18 is using S.D.SqlClient while SSMS 19 has switched to M.D.SqlClient.
As a test set the Force Encryption to False/No and add Encrypt=false to your connection string to see if you are able to get connection.

Previously SharePoint used S.D.SqlClient, but I'm working on replacing the lib with M.D.SqlClient now, so I need to verify my work. I use sql server 2019 with version 15.0.4223.1 and SSMS 18 in my lab.
Below is my self-signed cert, sql server's fqdn is 'sql.contoso.local'

Given the configuration, can the encrypted connection be established successfully?

@qizu0302 SQL Server 2019 uses TDS protocol to communicate with drivers such as M.D.SqlClient or S.D.SqlClient or JDBC or other drivers. It does not uses client side library. However, SSMS 18 is using S.D.SqlClient on the background to get connection from SQL Server and SSMS 19 is using M.D.SqlClient for that matter. S.D.SqlClient is in servicing mode and is not accepting fixes or adding new features. It only accepts security related fixes, however M.D.SqlClient is active ADO.NET library and continuously improves and adds new features.
that being said, you need to go to the Details tab and make sure that couple of things are correct:
A self signed certificate for SSL server authentication looks like below. Keep in mind this is for localhost and you need to change the IP address in the text extension
New-SelfSignedCertificate -Subject "CN=<FQDN>" -KeyAlgorithm RSA -KeyLength 2048 -CertStoreLocation "cert:\LocalMachine\My" -TextExtension @("<IP_ADDRESS>={text}DNS=localhost&IPAddress=<IP_ADDRESS>&IPAddress=::1") -HashAlgorithm “SHA256” -Type SSLServerAuthentication -Provider “Microsoft RSA SChannel Cryptographic Provider”

subject is same FQDN of the server.
make sure cert store location is correct.
make sure correct text extension is selected along with IP addresses.
make sure Type is SSLServerAuthentication
make sure provider is Microsoft RSA SChannel Cryptographic Provider

Then you need to import the certificate and make sure it is the active certificate in the section highlighted inside the below image

Appreciate your reply! It seems this kind of cert works now.

@qizu0302 you are welcome. Keep that in mind that this kind of certificates do not provide any trust value oppose to CA (certificate authority) issued certs. These kind of certificates are good for developers and testing purposes.
I am closing the issue as resolved.


Update hover state for the menu component to make it more readable for Universal Design

As follow up to this slack discussion it appears that the hover state of the menu component is not seen on a low contrast screen. For a better readability suggested action are:

[ ] change the weight of the text
[ ] update the navigation token

Material Design, Carbon and Altassian uses the same pattern for menus.
And here is the WCAG documentation

Material Design, Carbon and Altassian uses the same pattern for menus.
And here is the WCAG documentation

Ready for review @lucasveil. I added a new text style for Navigation/Menu Title hover in the design tokens here And used this new text style for the hover state of the Menu Item here

Nice work. Approved for me @BirteThornquist


Cannot read properties of undefined (reading 'startsWith')

Version: 5.13.2
Setup: Running the mockserver client in cypress against a mockserver docker container
Logs
cypress_1     |        "after each" hook for "gets location information by latitude and longitude: unauthorised":
cypress_1     |      TypeError: Cannot read properties of undefined (reading 'startsWith')
cypress_1     |
cypress_1     | Because this error occurred during a `after each` hook we are skipping the remaining tests in the current suite: `A reverse geocode`
cypress_1     |       at makeRequest (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:9335:91)
cypress_1     |       at Object.reset (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:9959:20)
cypress_1     |       at eval (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8836:53)
cypress_1     |       at step (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8820:23)
cypress_1     |       at Object.eval [as next] (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8801:53)
cypress_1     |       at eval (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8795:71)
cypress_1     |       at new Promise (<anonymous>)
cypress_1     |       at ./cypress/integration/reverse-geocode.spec.ts.__awaiter (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8791:12)
cypress_1     |       at Context.eval (http://app:9014/__cypress/tests?p=cypress/integration/reverse-geocode.spec.ts:8833:36)
cypress_1     |

It looks like there is a fix for this in master, but no release has been done for several months.
Would it be possible to publish a new version?

In the meantime i've downgrade to 5.11.2 which works correctly, but does have several vulnerabilities

There will be release in the next week, I'll close this ticket.


capabilities are unclear

However, I must say that very critical info for first-time users is still unavailable or very vaguely documented. For example, I still have no clue what sort of analysis can be obtained from this page : https://github.com/coala-analyzer/coala-bears/wiki/Available.... I can see a bunch of Bears but that's your terminology. I would rather prefer a brief summary of the tool's analysis or atleast a link to the static analyzer which a specific bear wraps over. For e.g. "AlexBear" - I honestly have no clue what that or 90% of the other bears end up doing with my source code.
You have put so much effort in the implementation, please improve clarity/coverage of documentation.

from https://news.ycombinator.com/reply?id=11535990&goto=item%3Fid%3D11531718

see also https://docs.google.com/spreadsheets/d/1ZJTe1nFsWuKxVdRgHOlpKNI1cLHb4QgY7aAq9tOaa9w/edit?usp=sharing for capabilities

Filed https://github.com/coala-analyzer/coala-bears/issues/332 about the bear-quality-offensive we have planned but not yet written down for this release.

Hey where exactly would you want this info about the bears? a gist or something?

I have no idea, ideally coala-bears#332 would be done and then we'd generate a website from that or so :P
Actually yesterday night I thought about this, we can do it right now:
write a little python script that collects all bears and outputs all it's info as markdown, we use that to generate a neat website somewhere and link to that from our website

i'll do this tonight, i was just gathering info now :) if you want this to be done right away, please assign someone else

no this is more of a long term thing actually but very important

this got way better by now with the https://github.com/coala-analyzer/bear-docs

Closing issue in old repo.
I think https://coala.io/#/languages has mostly covered this, but it is still 'bear'-focused, so https://github.com/coala/landing-frontend/issues/250 covers that problem.


Dark scrollbars over dark syntax themes in macOS (only in editor)

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When using a dark syntax theme, the scrollbars in macOS are too dark to be seen correctly. This only happens in the editor (1). For the tree view (2), for example, the color of the scrollbars is as expected (light themed).

Steps to Reproduce

Select When scrolling setting in macOS Preferences > General > Show scroll bars.
Select a dark syntax theme in Atom.

Expected behavior: Editor uses light scrollbar on syntax themes with dark backgrounds.
Actual behavior: Editor uses dark scrollbar on syntax themes with dark backgrounds, rendering them almost invisible.
Reproduces how often: I've test it with all default UI and syntax themes combinations and problem persists.
Versions
Atom    : 1.19.2
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0
apm  1.18.4
npm  3.10.10
node 6.9.5 x64
python 2.7.10
git 2.11.0
OS: macOS Sierra 10.12.6

I can reproduce with 1.19.3 on macOS 10.12.6 - does seem related if not the same as https://github.com/atom/atom/issues/15442 so we'll see if this issue is fixed when https://github.com/atom/atom/issues/15442 is resolved.

A quick update: in 1.19.5 there are no scrollbars at all following the same steps.

@haidran Scrollbars not showing up at all was reported in https://github.com/atom/atom/issues/15442 that has been fixed now and will be released in the next hotfix release.
@rsese Can you test the latest artifact to see if this issue has been fixed now that #15442 is merged?

Hmmm, I went back and tested things out and see that this particular issue isn't a regression (or at least not from 1.18.0), the scrollbars looks pretty much the same with One Dark and the macOS scroll bars set to When Scrolling.

scroll bar
1.18
1.19.6

editor

tree view

I think I might have tagged as a regression prematurely because of the cross-ref from https://github.com/atom/atom/issues/15442?
Is this maybe more of a theme issue?  I also found this older Discuss thread that seems related where folks are trying to style the scrollbar because it's too dark:
https://discuss.atom.io/t/scrollbars-on-osx/27683

@rsese Thank you for the investigation :bowing_man: Removing the regression label for now. Tagging @simurai since this looks like a theme issue and the One Dark themes are used :zap:


Using getCombatants in the Raidemulator, the result does not contain the properties provided by the new version of OverlayPlugin.

（This article is from Translation Software）
Description
I can't get the results of the new version of OverlayPlugin/OverlayPlugin (maybe 0.19.14+) call: "getCombatants".
For example "WeaponId" or some other new attribute.
The data printed in the simulator is the old version.
https://github.com/OverlayPlugin/OverlayPlugin/pull/168
Environment
OverlayPlugin.dll <IP_ADDRESS>
CactbotOverlay.dll <IP_ADDRESS>
Raidemulator https://quisquous.github.io/cactbot/ui/raidboss/raidemulator.html?OVERLAY_WS=ws://<IP_ADDRESS>:10501/ws
I tried Clone Cactbot and then npm start and it was the same
Log
In Raidemulator Log
{
  ID:<PHONE_NUMBER>,
  Name: "オメガM",
  Level: 90,
  PosX: 99.99,
  PosY: 99.99,
  PosZ: 0,
  Heading: 0,
  CurrentHP: 8931831,
  MaxHP: 13707136,
  CurrentMP: 10000,
  MaxMP: 10000,
  OwnerID: 0,
  BNpcNameID: 12257,
  BNpcID: 15720,
}

In Combat Log
{
  ID:<PHONE_NUMBER>,
  OwnerID: 0,
  Type: 2,
  MonsterType: 0,
  Status: 0,
  ModelStatus: 0,
  AggressionStatus: 0,
  TargetID:<PHONE_NUMBER>,
  IsTargetable: false,
  Job: 0,
  Name: "オメガ",
  CurrentHP: 44,
  MaxHP: 44,
  PosX: 100,
  PosY: 100,
  PosZ: -5.456968e-12,
  Heading: -1.57336116,
  Radius: 0.5,
  Distance: null,
  EffectiveDistance: null,
  Effects: [],
  BNpcID: 9020,
  CurrentMP: 0,
  MaxMP: 0,
  Level: 1,
  BNpcNameID: 7636,
  WorldID: 65535,
  CurrentWorldID: 65535,
  NPCTargetID:<PHONE_NUMBER>,
  CurrentGP: 0,
  MaxGP: 0,
  CurrentCP: 0,
  MaxCP: 0,
  PCTargetID: 0,
  IsCasting1: 0,
  IsCasting2: 0,
  CastBuffID: 0,
  CastTargetID: 0,
  CastDurationCurrent: 0,
  CastDurationMax: -36893490000000000000,
  TransformationId: 0,
  WeaponId: 0,
  PartyType: 0,
  WorldName: null,
}

The values returned in RaidEmulator for getCombatants have always been approximations and only the values that are actively used are emulated.
WeaponId can't currently be emulated because that information isn't available from the network log file produced by FFXIV_ACT_Plugin.
I have plans to add something better as a custom OverlayPlugin-level log line but it's still in the rough draft state.


Landscape view seems not working fine

I moved out phone on left and seems it's not working fine

Hi, this should be fixed in v2 or v3 of the preview. Which version are you using at the moment?

Already v3 preview version

Ok, weird. Can you try wget https://github.com/741g/android-emulator-m1-preview/releases/download/7123544/sdk-repo-darwin_aarch64-emulator-7123544.zip ?

It's the same for me.


Types for events 2

Can now strongly type events and all of the event types have interfaces.
Here's how it should be used
await connector.on(
    SubscriptionEventName.MarketCreated,
    async (arg: MarketCreated): Promise<void> => {
      expect(arg).toHaveProperty(
        'extraInfo',
        '{"description": "yesNo description 1", "longDescription": "yesNo longDescription 1", "tags": ["yesNo tag1-1", "yesNo tag1-2", "yesNo tag1-3"]}'
      );
.....
.....

Note that in the callback the argument is typed specifically to the event by the author.

closes #2619


Fixing mixed device types in input Tensors of torch.lerp on release 2.6

🐛 Describe the bug
Release 2.6 got failures because the cpu "weight" , https://github.com/pytorch/pytorch/blob/release/2.6/test/test_binary_ufuncs.py#L3473, we could need to cherry-pick the lerp fixing in this PR to 2.6 release branch, https://github.com/intel/torch-xpu-ops/pull/1144.
FAILED test_binary_ufuncs_xpu.py::TestBinaryUfuncsXPU::test_lerp_xpu_complex128 - RuntimeError: iter.device(arg).is_xpu() INTERNAL ASSERT FAILED
FAILED test_binary_ufuncs_xpu.py::TestBinaryUfuncsXPU::test_lerp_xpu_complex64 - RuntimeError: iter.device(arg).is_xpu() INTERNAL ASSERT FAILED
FAILED test_binary_ufuncs_xpu.py::TestBinaryUfuncsXPU::test_lerp_xpu_float32 - RuntimeError: iter.device(arg).is_xpu() INTERNAL ASSERT FAILED
FAILED test_binary_ufuncs_xpu.py::TestBinaryUfuncsXPU::test_lerp_xpu_float64 - RuntimeError: iter.device(arg).is_xpu() INTERNAL ASSERT FAILED
Versions
2.6

Rel


ROX-23946: Factor out email template from vulnerability reporting

Description
Prerequisite to factor out delivery destinations from Vulnerability Reports to reuse in Compliance Reports.
Changes

Create EmailTemplate.utils.ts

Move maximum lengths from useReportFormValues.tsx file and leave what is specific to vulnerability reports.
Move reusable validations from emailTemplateFormUtils.ts file and leave what is specific to vulnerability reports.
Rename variables for consistency with NotifierConfiguration type.

Create EmailTemplateForm.tsx

Rename variables for consistency with NotifierConfiguration type.

Move and rename EmailTemplateModal.tsx

Replace reportParameters with optional renderTemplatePreview prop.
Rename variables for consistency with NotifierConfiguration type.
Factor out form.
Conditionally render tabs.

Edit DeliveryDestinationsForm.tsx

Import from Components/EmailTemplate folder.
Factor out renderTemplatePreview which is specific to vulnerability reports.

Edit emailTemplateFormUtils.ts

Move reusable validations.

Edit useReportFormValues.tsx

Move reusable lengths and validations.

Checklist

[x] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn lint in ui
yarn build in ui and then compute branch - master for the following

wc build/static/js/*.js
main.js 0 = 4633558 - 4633558
total 353 = 11601343 - 11600990
ls -al build/static/js/*.js | wc
files 0 = 173 - 173

yarn start in ui

Manual testing
Prerequisite: create at least one collection.
Create e-mail notifiers on the fly.

Create 3 reports with various combinations of defaut or custom destinations or template.

Verify payload and response of POST /v1/notifiers request.
Verify review details.
Verify payload and response of POST /v2/reports/configurations request.

Edit the first report and ditto items 2 and 3 above.

EmailTemplateModal Edit tab

EmailTemplateModal Preview tab and CVEs found toggle

EmailTemplateModal Preview tab and CVEs not found toggle

EmailTemplateModal with EmailTemplateForm only (that is, without renderTemplatePreview prop, which compliance reports probably not have)

DeliveryDestinationsDetails

EmailTemplatePreview

Integration testing
Uh, oh! No tests. Yet.

/test ocp-4-15-ui-e2e-tests

/test ocp-4-15-ui-e2e-tests


How to add new camera instances?

I want to test a configuration with two new camera instances, e.g, a left front camera and right front camera.
I am working with SVL simulator and ApolloAuto.
At this moment, I have already done these:
1, Add two new camera instances in the SVL simulator. Change the rotation angle parameters of the two cameras.
2, Add new toppic pubslished to ApolloAuto, and create all the other config files needed.
3, Launch the obstacle detection pipeline (SMOKE algorithm) and enable debug. From the debug output, I can see the two images are in the right viewpoint and the algorithm is working fine.
The intrinsic parameters of these two camera instances are copied from the front camera, this should be fine.
The big question is the extrinsic parameters. I do not know how to get it. But the make the pipeline run, I have just copied them from the front camera. I know these configs are not correct, they are just in correct format.
So how should I get them?
Another question, I found that both the extrinsic and intrinsic parameter file of the default front camera has been changed after I launched a camera module pilepline. Does this mean some internal process has modified these parameters automatically? Does this mean I do not need to specify them manually? What is underline logic they are modifed?

@ywangwxd
Another question, I found that both the extrinsic and intrinsic parameter file of the default front camera has been changed after I launched a camera module pilepline. Does this mean some internal process has modified these parameters automatically?

when you choose the vehicle in dreamview. it will auto modify the config according to the vehicle type. It actually copies the corresponding configuration to the corresponding path, so you need to confirm whether these internal and external parameters are what you want


Fix build failure source plugin

I think actually this dependency upgrade broke things
https://github.com/spring-cloud/spring-cloud-build/pull/277
I am not sure why, but I reverted the train and so far the build looks pretty good.

Thanks for the investigation here.  I agree that eventually we want to upgrade, but there isn't much harm in staying where we are for now and IMO is preferable to making the changes to work around the issue in this PR.
I think it is worth opening an issue with Spring Boot with the details above and see if they have some thoughts on this.  My guess is that we are not the only ones running into this and maybe they have some suggestions.

I merged the change in spring cloud build, once the build finishes and the snapshots are available you can test things out.  It should only take a few minutes for the build to finish


Sending a solution won't clear the text editor

Problem:
After sending a solution to a question, the text editor is not cleared, content is cached and still displays when returning to the question later on.
Reason:
Kind of ruins it for the student if they want to rechallenge them selves with the same question.
Screenshot:

@xarielah What if the student wants to change or add details to their solution?
Should I add submissions like in Leetcode?

@xarielah What if the student wants to change or add details to their solution?
Should I add submissions like in Leetcode?

I'm not too familiar with submissions on Leetcode but maybe having an edit button on the solution that'll load the contents of the solution into the editor or  transform the solution post into an editor and when the user saves the changes it'll update the content?
Btw I would advice having optimistic updates, it will make the interaction in general much smoother

@xarielah ok I will think about how to implement it.
Where do you think i should use optimistic updates? On which components?

@xarielah ok I will think about how to implement it.
Where do you think i should use optimistic updates? On which components?

I would support implementing it where ever theres an interaction of a user and an asynchronous operation such as updating the solution, adding a question, liking, commenting etc...

@noams24 Btw wanted to also add here, that Next and react basically is all about caching the state, being reactive but only when ever you set it to be.
For example (might be better to open as another issue or enhencment) I commented and someone's solution, switched between "שאלה" and "פתרונות" tabs, didn't see the comment counter change untill I refreshed.

@noams24 Btw wanted to also add here, that Next and react basically is all about caching the state, being reactive but only when ever you set it to be. For example (might be better to open as another issue or enhencment) I commented and someone's solution, switched between "תיאור" and "פתרונות" tabs, didn't see the comment counter change untill I refreshed.

Thanks for noticing, I fixed it using react query invalidation. Should work fine now

@xarielah

I added submissions.
Now you can delete your submission or copy an old one to your editor.
Let me know what you think.

@xarielah I close this issue for now, if you have another idea to improve please let me know


[Feature] Support CPU training

Reference: https://github.com/open-mmlab/mmdetection/pull/7016

Should we also modify somewhere in the documents ?

Should we also modify somewhere in the documents ?

Let me check


run from arbitrary directories

This PR allows running the examples from arbitrary directories. This is handy as I now registered the package (should be merged in a few days) after which users can install it and run it locally with:
julia>using InteractiveGeodynamics
julia> RisingSphere()
julia> Convection()
julia> RayleighTaylor()

To be added:

[ ] change axes of the plot

Just for the record, this branch freezes when calling RisingSphere() in Windows and WSL with 1.9.0. Works fine on mac with 1.9.3.

Wouldn't it be better to move the GUI models folders into src/ since they are part of a module?

Not sure if this function is used often or not, but it is  type stable because values is changing type (the size is a type in this case) inside a loop. Since tb is a NTuple, the compiler does actually have all the information needed, just need to be rewritten as e.g.
function get_values_textboxes(tb::NTuple{N, T}) where {N,T}
    values = ntuple(Val(N)) do i
        Base.@_inline_meta
        textb = tb[i]
        parse(Float64,textb.displayed_string[])
    end
    return values
end

thanks for your comments @albert-de-montserrat - I have implemented them all & deleted obsolete files where appropriate


minor typo in "a-tour-of-textile.md"

file:

a-tour-of-textile.md

search: Gateway address: <IP_ADDRESS>:5050

should only find 1 match

replace: Gateway address: <IP_ADDRESS>:9090

as this is the cmd output after restarting the daemon to accept a config change to the gateway port

thanks for your edits. retired the tour for now, so easy solution. :)


precheck unclear error message

Steps to reproduce

fastlane deliver init for any app
fastlane deliver --force

Expected result:
Successful upload with some kind of success message
Actual result:
For the user it looks like the build failed, and it wasn't successful, it took me a while to figure that out

Yeah, good call @KrauseFx, let's make this more friendly, especially if we're not failing, maybe we can change these lines to yellow and add something like "deliver was successful 👍 "
"Even though we found potential problems, things look good 👍 "

Sounds great 👍


OpeoNodes.java:179-182: Correct parsing of WriteField...

The puzzle 80-fdb09a33 from #80 has to be resolved:
https://github.com/objectionary/opeo-maven-plugin/blob/047fb364eb191178695fb5f13bcd0668f3429eaf/src/main/java/org/eolang/opeo/compilation/OpeoNodes.java#L179-L182
The puzzle was created by @volodya-lombrozo on 18-Jan-24.
Estimate: 90 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd the puzzle #153 is still not solved.

@0pdd the only puzzle #153 is solved here.


Where to obtain app name and app ID

Hi,
I am a bit confused as to where the API KEY is obtained from for a particular infusionsoft portal such as fd1212.infusionsoft.com
I created an app at https://keys.developer.infusionsoft.com/apps/ and that has a App name and a client id and secret associated with it.
When I tried the fd1212 and the client ID of the app I created in the developer portal, I got the message
xmlrpc.client.Fault: <Fault 2: '[InvalidKey]Invalid Key'>
So I am not sure if I am missing something here?
Any help would be appreciated.

I'm not at a computer right now, and I don't have links for ya, but I may
be able to set you on the right path: this library interfaces with
Infusionsoft's XML-RPC API, which is becoming their legacy API. I believe
you can create keys for it in the admin section of your app. It will be one
single hex token, maybe 32 chars.
Infusionsoft is pursuing a REST API, using OAuth for authentication. It
uses a client ID and a secret key. At time of writing, a lot of
functionality exists in the XML-RPC API which is not yet available through
the REST API. However, the REST API does support webhooks, so you can get
notified on certain events, such as contact creation or update. (Though, in
my experience, it batches updates and only shoots them out every few
minutes.)
Cheers!
On Fri, Sep 22, 2017, 17:17 Tharshan Muthulingam<EMAIL_ADDRESS>wrote:

Hi,
I am a bit confused as to where the API KEY is obtained from for a
particular infusionsoft portal such as fd1212.infusionsoft.com
I created an app at https://keys.developer.infusionsoft.com/apps/ and
that has a App name and a client id and secret associated with it.
When I tried the fd1212 and the client ID of the app I created in the
developer portal, I got the message
xmlrpc.client.Fault: <Fault 2: '[InvalidKey]Invalid Key'>
So I am not sure if I am missing something here?
Any help would be appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theY4Kman/infusionsoft-client/issues/10, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AACEMCxK9rbzJjKkW7C2ObfyapkKdzMWks5slCPagaJpZM4PhQBA
.

The infusionsoft XML RPC uses OAuth2 as well, according to the docs
https://developer.infusionsoft.com/docs/xml-rpc/#authentication

Oh, I guess I'm not up on the times! Well, to be candid, I won't be working
with Infusionsoft professionally for much longer, so I doubt I'll start
writing the code for OAuth.
I'd be happy to review and accept pull requests ;) Or if you're a bribing
man, I might be swayed if you hand draw yourself riding on a unicorn and
post a picture of it.
Cordially,
Yakko
On Sat, Sep 23, 2017, 15:18 Tharshan Muthulingam<EMAIL_ADDRESS>wrote:

The infusionsoft XML RPC uses OAuth2 as well, according to the docs
https://developer.infusionsoft.com/docs/xml-rpc/#authentication
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/theY4Kman/infusionsoft-client/issues/10#issuecomment-331664147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACEMCErVN-A0tUC4TDUOtumufIBoA2oks5slVmAgaJpZM4PhQBA
.

That's fair enough, I am doing the OAuth token process in my app already. I just wanted to point out that the XML RPC requires an access token as far as I know.
To
https://api.infusionsoft.com/crm/xmlrpc/v1?access_token=123abc

I think if this can be provided then the rest of your library would work.


blog: Add blogpost for user namespaces in 1.25

Signed-off-by: Rodrigo Campos<EMAIL_ADDRESS>For KEP: https://github.com/kubernetes/enhancements/issues/127
cc @giuseppe @katcosgrove

Hi from the Comms team! Just a reminder that the Ready to Review deadline for feature blogs is Tuesday, August 16. You will also be assigned a publication date. Is there anything we can do to help you right now?

Can we assign a publication date anyway, to make the remaining work easier?

@sftim who decides the publication date?
As I mentioned to @katcosgrove on slack, I happen to be unavailable now and unsure when I'll be back to work on this (might be close to a month).

Who decides the publication date?

For the post-release blog article series, that's the release comms team.

@katcosgrove would you like to assign (or suggest) a date for this article?

Removing some wrong labels.
/remove-area release-eng
/remove-language fr ja pt vi zh
/remove-sig release

@rata, this PR must target the main branch? Could you change the merge base, rebase locally, and force-push?
(if you're not sure about those steps, another option is to open a new PR and add a comment here that lets us find the new PR)

closing in favour of https://github.com/kubernetes/website/pull/36416
/close


Translation for AGOL/Portal

Hi,
Is there a timeframe for the next release when the changes made in commit https://github.com/Esri/geoportal-server-harvester/commit/78d5575cb086407de418bf5e1bb2e33f9821c475 to enable translation of metadata to ArcGIS might become available?
Thanks.
David

We are working on a release of the Catalog application currently. After that, we will work on a release of the harvester. You may build the app from the source code directly to get access to this particular feature.


TestThreadExitThread: fix messages and wait timeout for the windows CI

Looks like for the windows x86_86 CI host 100ms is too small for a thread to terminate so let's wait for longer and decrease the number of loops.

@akallabeth @mfleisz @awakecoding Please approve that PR so that we can unblock other pending PR failing in the CI because of TestThreadExitThread...


Error in script on hostname switch

When running the script, it throws a hostname error
hostname: invalid option -- 's'
Resulting snapshots don't have hostname listed.
zroot/ROOT/void@zfs-auto-snap_frequent-2022-02-25-0215  1.75M      -     6.15G  - zroot/ROOT/void@zfs-auto-snap_frequent-2022-02-25-0230  1.69M      -     6.15G  - zroot/ROOT/void@backup--20220226-074835                  984K      -     7.34G  - zroot/home@zfs-auto-snap_frequent-2022-02-25-0215       13.2M      -      109G  - zroot/home@zfs-auto-snap_frequent-2022-02-25-0230
hostname --help on Void linux doesn't show any options, but references GNU core utils if that matters.

This should be fixed in 253b1cc, which pipes hostname into awk rather than assuming a short-name switch.

Closing. Should have closed on last comment. Should have linked issue in commit. I'm new to both Git and GitHub.


Access token: refactor JWT interfaces

coverage: 80.583%. remained the same when pulling 2376e44f405edbc3f8db6129ea36317f191460be on dissoupov into 1d2c0d7fecd323a0ce89d51f67e50af3575742e4 on main.


set speed of the encode

I am trying to figure out how to speed up my conversions. Is there a second option to adjust the speed of the crf factor set. Like in handbrake you can set the rf but then you can adjust the preset from ultrafast to placebo. Is this what the option video profile is for? if so what are the options for that? If not is there another way to accomplish this?
Thanks

video-bitrate and video-crf are pretty much the only options, changing the profile might result in faster encodes but not directly equivalent. You may also use preopts / postopts to add in more specific options to ffmpeg to try to reduce times