synlig: 2023-11-28 -> 2024-08-07

Description of changes
Update synlig to head. Most notably, it compiles again against latest Yosys (0.43, but also 0.44), so the 'broken' clause can be removed.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 332956 run on x86_64-linux 1

1 package built:

yosys-synlig

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

yosys-synlig:

got build log for '/nix/store/6khh987rxbfvf6vklvml4212kpyk4cj0-yosys-synlig-2024-08-07' from 'daemon'
When evaluating attribute ‘yosys-synlig’:
warning: attribute-typo
A likely typo in the GIT_VERSION argument was found, did you mean version?
Near pkgs/development/compilers/yosys/plugins/synlig.nix:18:3:
   |
18 |   GIT_VERSION = "2024-08-07-fd4b2bd";
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md


entry point named with .js

why can't i name the entry point file with a the exension .js

Do you have --allowJs turned on?

Curious, why you have no .ts files in your sources?


Refactor format to allow streaming chunk writing

Now that I've begun integration in Sediment, I realized that I would prefer chunk data to be written as:

Chunk command byte
Length (4 bytes)
Data (Length bytes)
CRC (4 bytes)

By moving the CRC to the end, we can compute it on the fly, which would allow for a ChunkWriter type that could implement Write and allow buffered streaming chunk writing.

Oops, didn't realize I had written an issue for this. Implemented in 9946e274961d64ecb6e7b9aad848007f375b1f86.


shadcn-ui Input bug

When using the shadcn-ui input component, I receive a long error from react itself about how "React does not recognize the fieldState prop on a DOM element." The full error is as follows:

Warning: React does not recognize the `formState` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `formstate` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
    at input
    at eval (webpack-internal:///(ssr)/./components/ui/input.tsx:13:78)
    at eval (webpack-internal:///(ssr)/./node_modules/@radix-ui/react-slot/dist/index.mjs:42:23)
    at eval (webpack-internal:///(ssr)/./node_modules/@radix-ui/react-slot/dist/index.mjs:16:23)
    at eval (webpack-internal:///(ssr)/./components/ui/form.tsx:101:87)
    at div
    at eval (webpack-internal:///(ssr)/./components/ui/form.tsx:65:81)
    at Controller (webpack-internal:///(ssr)/./node_modules/react-hook-form/dist/index.esm.mjs:506:39)
    at FormField (webpack-internal:///(ssr)/./components/ui/form.tsx:28:25)
    at div
    at form
    at FormProvider (webpack-internal:///(ssr)/./node_modules/react-hook-form/dist/index.esm.mjs:146:13)
    at div
    at eval (webpack-internal:///(ssr)/./components/ui/card.tsx:58:84)
    at div
    at eval (webpack-internal:///(ssr)/./components/ui/card.tsx:18:77)
    at CardWrapper (webpack-internal:///(ssr)/./components/auth/card-wrapper.tsx:16:24)
    at LoginForm (webpack-internal:///(ssr)/./components/auth/login-form.tsx:23:74)
    at Lazy
    at InnerLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:241:11)
    at RedirectErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
    at RedirectBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
    at NotFoundBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/not-found-boundary.js:84:11)
    at LoadingBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:333:11)
    at ErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/error-boundary.js:159:11)
    at InnerScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:152:9)
    at ScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:227:11)
    at RenderFromTemplateContext (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/render-from-template-context.js:16:44)
    at Lazy
    at OuterLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:351:11)
    at Lazy
    at InnerLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:241:11)
    at RedirectErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
    at RedirectBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
    at NotFoundBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/not-found-boundary.js:84:11)
    at LoadingBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:333:11)
    at ErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/error-boundary.js:159:11)
    at InnerScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:152:9)
    at ScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:227:11)
    at RenderFromTemplateContext (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/render-from-template-context.js:16:44)
    at Lazy
    at OuterLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:351:11)
    at Lazy
    at div
    at InnerLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:241:11)
    at RedirectErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
    at RedirectBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
    at NotFoundErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/not-found-boundary.js:76:9)
    at NotFoundBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/not-found-boundary.js:84:11)
    at LoadingBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:333:11)
    at ErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/error-boundary.js:159:11)
    at InnerScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:152:9)
    at ScrollAndFocusHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:227:11)
    at RenderFromTemplateContext (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/render-from-template-context.js:16:44)
    at Lazy
    at OuterLayoutRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/layout-router.js:351:11)
    at Lazy
    at body
    at html
    at RedirectErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
    at RedirectBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
    at ReactDevOverlay (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/react-dev-overlay/internal/ReactDevOverlay.js:84:9)
    at HotReload (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/react-dev-overlay/hot-reloader-client.js:308:11)
    at Router (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/app-router.js:176:11)
    at ErrorBoundaryHandler (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/error-boundary.js:113:9)
    at ErrorBoundary (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/error-boundary.js:159:11)
    at AppRouter (webpack-internal:///(ssr)/./node_modules/next/dist/client/components/app-router.js:515:13)
    at Lazy
    at Lazy
    at rS (/home/jarza/Projects/authjs/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:15614)
    at rS (/home/jarza/Projects/authjs/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:15614)
    at ServerInsertedHTMLProvider (/home/jarza/Projects/authjs/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:21176)
Next.js Version 14.1.0
Yarn Version 1.22.21
ShadCN-UI Version 0.8.0
Using Next.js via yarn run dev

In addition, it seems that this may be a problem on my end. The line <Input {...field} placeholder='******' type='password' /> is problematic because ...field is
    field: ControllerRenderProps<{
        email: string;
        password: string;
    }, "password">;
    fieldState: ControllerFieldState;
    formState: UseFormStateReturn<{
        email: string;
        password: string;
    }>;
}

My question is, why is fieldState getting passed into this input?

@JarzaClay
Can you share the code related to this issue

import { z } from "zod";
import { useForm } from "react-hook-form";
import { zodResolver } from "@hookform/resolvers/zod";
import {
  Form,
  FormControl,
  FormField,
  FormItem,
  FormLabel,
  FormMessage,
} from "@/components/ui/form";
import { Input } from "@/components/ui/input";
import { Button } from "@/components/ui/button";
import { CardWrapper } from "@/components/auth/card-wrapper";
import { LoginSchema } from "@/schemas";

export function LoginForm() {
  const form = useForm<z.infer<typeof LoginSchema>>({
    resolver: zodResolver(LoginSchema),
    defaultValues: {
      email: "",
      password: "",
    },
  });

  function onSubmit(values: z.infer<typeof LoginSchema>) {}

  return (
    <CardWrapper
      headerLabel='Welcome back!'
      backButtonLabel='Create account.'
      backButtonHref='/auth/register'
      showSocial>
      <Form {...form}>
        <form onSubmit={form.handleSubmit(onSubmit)} className='space-y-6'>

            <FormField
              control={form.control}
              name='email'
              render={(field) => (
                <FormItem>
                  <FormLabel>Email</FormLabel>
                  <FormControl>
                    <Input
                      {...field}
<EMAIL_ADDRESS>                      type='email'
                    />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              )}
            />
            <FormField
              control={form.control}
              name='password'
              render={(field) => (
                <FormItem>
                  <FormLabel>Password</FormLabel>
                  <FormControl>
                    <Input {...field} placeholder='******' type='password' />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              )}
            />

          <Button type='submit' className='w-full'>
            Login
          </Button>
        </form>
      </Form>
    </CardWrapper>
  );
}

@JarzaClay
You forget to destructor the field value from the render function in FormField component
Here is the updated code

import { z } from "zod";
import { useForm } from "react-hook-form";
import { zodResolver } from "@hookform/resolvers/zod";
import {
  Form,
  FormControl,
  FormField,
  FormItem,
  FormLabel,
  FormMessage,
} from "@/components/ui/form";
import { Input } from "@/components/ui/input";
import { Button } from "@/components/ui/button";
import { CardWrapper } from "@/components/auth/card-wrapper";
import { LoginSchema } from "@/schemas";

export function LoginForm() {
  const form = useForm<z.infer<typeof LoginSchema>>({
    resolver: zodResolver(LoginSchema),
    defaultValues: {
      email: "",
      password: "",
    },
  });

  function onSubmit(values: z.infer<typeof LoginSchema>) {}

  return (
    <CardWrapper
      headerLabel='Welcome back!'
      backButtonLabel='Create account.'
      backButtonHref='/auth/register'
      showSocial>
      <Form {...form}>
        <form onSubmit={form.handleSubmit(onSubmit)} className='space-y-6'>

            <FormField
              control={form.control}
              name='email'
              render={({ field }) => (
                <FormItem>
                  <FormLabel>Email</FormLabel>
                  <FormControl>
                    <Input
                      {...field}
<EMAIL_ADDRESS>                      type='email'
                    />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              )}
            />
            <FormField
              control={form.control}
              name='password'
              render={({ field }) => (
                <FormItem>
                  <FormLabel>Password</FormLabel>
                  <FormControl>
                    <Input {...field} placeholder='******' type='password' />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              )}
            />

          <Button type='submit' className='w-full'>
            Login
          </Button>
        </form>
      </Form>
    </CardWrapper>
  );
}

@imopbuilder Thank you very much, this code works! I apologize for using your time. I don't frequently use deconstructors. ❤

I make the same mistake that forgot distructor the field from render callback parameter ! Thank a lot!


Typha tolerate node.cloudprovider.kubernetes.io/uninitialized taint

Description
Allow typha deployment to tolerate the taint set via kubelet when used with --cloud-provider=external flag. We need typha to be able to schedule as soon as possible on new nodes since calico-node relies on it.
Related issues/PRs
Related Slack thread:
https://calicousers.slack.com/archives/C0BCA117T/p1693469918340899
Todos
Someone should run the respective make target to generate manifests picking up this change.
Release Note
Add Typha Deployment tolerations to helm charts so that it can be scheduled on any nodes.

I think Typha and calico-node should have the exact same Tolerations since calico-node requires Typha to be up to come up itself.
Can a core-maintainer confirm that position please?

@lwr20 @coutinhop anything else we need from this prior to merge?
The one thing I can see is that tests are failing - @ffilippopoulos you need to run make generate to update generated files.

@lwr20 @coutinhop anything else we need from this prior to merge?

I don't think so, @lwr20 please correct me if I'm wrong.


adding attachment example

2 program examples:

uploading a local file
download a file via URL and attach it

i hope there are not too many typos

the only thing that's missing is multi files


Support buildStartedOn, buildFinishedOn in Go builder.

Add buildStartedOn and buildFinishedOn to metadata in the Go builder.
    "metadata": {
      "buildInvocationId": "<STRING>",
      "buildStartedOn": "<TIMESTAMP>",
      "buildFinishedOn": "<TIMESTAMP>",
      "completeness": {
        "parameters": true/false,
        "environment": true/false,
        "materials": true/false
      },
      "reproducible": true/false
    },

Ideally this would come by looking it up in the Github API. Maybe the start/finish time for the previous job can be determined somehow via the workflows or workflow run API?


Resolves #106, options page saves changes automatically

Every second I check if options changed, I don't know if this is the right approach. Maybe I should add listeners on every fields and save immediately. Text fields are a bit tricky because you need to wait for user to finish typing.

Checking every second is probably sufficient for most use cases, though ideally you'd want to use a listener on every field. I recommend creating a little framework that handles the callback so that you don't have lots of boilerplate (basically make an abstraction). It's a bit simpler knowing that the browser is Chrome, so you can rely on whatever behavior Chrome gives you.

I've create a little framework as suggested.
The usage is really simple, you just have to add  where you want.
This will create a save indicator for the input field:

I could even refine the code and create a simple Bootstrap plugin to add save indicators on input fields :smile:

Very cool! That looks great!

Options page are now embedded in a small popup and users need to scroll to see the save button.
This feature should improve the usability.


Update data loaders and migrate to new zarr

Ok, so a few things here. I think all logic regarding getting and setting tiles needs to be confined to data_utils/. Optimally all the metadata regarding imageWidth, imageHeight, minZoom, tileSize, and connections can be resolved in initZarr & initTiff. Right now we have no "standards" with the metadata, but this allows us to consolidate and resolve hardcoded logic in the same place. I like this direction for two reasons:

The configs for the source can be very minimal, simply urls and channel names.
It releases the need for the connections object returned init<Loader> to be the same for different types of data. The init<Datatype> function thus controls exactly what load<Datatype> receives. Therefore, if someone where inclined to write a custom loader for another tiled datatype, they could re-implement the logic and create a plugin. As long as someone has a "connection" object that they can query with x, y, z tile coordinates, they can return an array of TypedArray channels to be rendered.

Apologies for the mess with eslint-disables and leaving in the big commented block. Thanks for looking this over and for the suggestions!

@ilan-gold hopefully this is logic you are happy with for colors. It still feels like an antipattern to see this:
const colorOptions = [
  [255, 0, 0],
  [0, 255, 0],
  [0, 0, 255],
  [255, 128, 0]
];

// converting to
const coloVals = {
  "channel0": [255, 0, 0],
  "channel1": [0, 255, 0],
  "channel2": [0, 0, 255],
  "channel3": [255, 128, 0]
}

// back to in microscopy-layer-base.js
const colorOptions = [
  [1, 0, 0],
  [0, 1, 0],
  [0, 0, 1],
  [1, .5, 0]
];

I'd rather the Viewer layer be agnostic to the channel names somehow.

Looks like changelog needs be updated but otherwise this looks good.

(Don't block on me, but happy to re-review, if that would be useful.)


If I use npm v7.x or later, do I need to install emotion?

Hello, thanks for this useful software !
The README.md says I need to install emotion, but if I am using npm v7.x or later, peerDependencies is also installed with it, so there seems to be no need to install it explicitly.

Hi @maroKanatani
Glad to hear that the tool is helpful! That's fine then! As long as the peer dependencies are installed, <DevTools /> should work as expected.


patch #34

#34 Added weather api using weather stack api and map box api

added weather feature

Please read the Contribution Guidelines first before raising a pull request.


These instructions keep an 18.04 VM in "creating state", with repeated "INFO Daemon Waiting for cloud-init to copy ovf-env.xml" in waagent logs

Running through "create-upload-ubuntu" instructions using a vanilla Ubuntu 18.04, results in the VM getting stuck in "Creating" with the following repeated error in the waagent logs:
2020/03/12 15:17:29.440366 INFO Daemon Waiting for cloud-init to copy ovf-env.xml to /var/lib/waagent/ovf-env.xml [1543 retries remaining, sleeping 1s]
2020/03/12 15:17:29.451162 WARNING Daemon cloud-init does not appear to be running

The workaround is to run the following fix script which will fix grub and cloud-init: https://github.com/Azure/Avere/blob/master/src/terraform/examples/securedimage/fixubuntuimage.sh.  This script fixes the differences between the reference cloud image, and the image created by the Ubuntu 18.04 service ISO.
Please update the generic Ubuntu steps with the extra fixes.  The customer unfortunately is not able to start from the reference Azure cloud image recommended at the top, so the generic steps help this type of customer.

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

ID: 4138584e-7488-4750-84b8-9e00bc3cf975
Version Independent ID: d750001e-90ab-e1ec-ab35-8ef9a4b556a9
Content: Create and upload an Ubuntu Linux VHD in Azure - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/create-upload-ubuntu.md
Service: virtual-machines-linux
GitHub Login: @mimckitt
Microsoft Alias: mimckitt

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

Thanks! @anhowe I've been trying to figure this out for porting an Ubuntu disk to Azure Stack and getting it to provision properly, will try the workaround!

@anhowe I had this issue and tried the fixubuntuimage.sh script and it did not resolve the problem. I did discover that by changing the following code change in /usr/lib/python3/dist-packagescloudinit/source/DataSourceAzure.py actually resolved my issue:
Used to match classes to dependencies
datasources = [

(DataSourceAzure, (sources.DEP_FILESYSTEM, )),

(DataSourceAzure, (sources.DEP_FILESYSTEM, sources.DEP_NETWORK)),
]

Adding "sources.DEP_NETWORK" resolved my issue which was DataSourceAzure was being returned as empty and cloud-init could not actually find the Azure datasource.

@danielsollondon could you help determine the right fix for this doc?

#reassign: @danielsollondon
@danielsollondon assigning this to you since you are working on all the image docs at the moment.

This does not solve the issue of the missing file.
To recreate the issue follow these steps:

Create a Ubuntu 18.04 VM Gen 1
Scale down the VM (Makes the VM unable to get an ip-address)
Shut down the OS
Snapshot the OS disk
Create a new hd from the snapshot, like shown here (https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-recovery-disks-portal-linux)
Swap the OS disks
Boot, and the issue is there

Solution:
Manually create the XML file, like shown here: https://thomasthornton.cloud/2020/04/16/cloud-init-does-not-appear-to-be-running-error-after-installing-walinuxagent/

We are currently cleaning up old issues and closing out items that are greater than 90 days old. If an issue is still present, please open a new feedback item on the document so we can prioritize correctly.
#please-close

@mimckitt Still an issue, tested today.

I still get a lot of traffic to my blog regarding the XML file from this issue - can we look at getting this fixed? I can happily assist were needed.

#reopen

#please-open
#reassign: @srijang
#assign: @linuxelf001

#assign: @srijang

Still a problem. Got here while migrating from GCP to Azure. Any news?

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing. We are closing this issue for now, but feel free to comment here as necessary. #please-close


#5115 icons fix

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Closes #5115
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 15 usd

@vikiival can we retry payment on this?

It was payed see comment above

It was payed see comment above

It failed though

It was payed see comment above

It failed though

Yup, sorry
It will be resolved by #5122

pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 5 USD/DOT ~ 4 $DOT
🧗 13Qx65nLd6SwdtjrRyuoEtp9CKXhF651xdHBPaXcvhwKm4N1
🔗 0x8fefa41c1f733e0c492edd9d55998f08e57ad2594e340a266559a130c8335fb6
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Documentation-functionality conflict

The documentation says that adding off and on to a toggle should not change the value of a bound property unless you 'overload' the label/value:

Finally, it is sometimes the case that rather than a true or false value the toggle is meant to move between two discrete, but non-boolean states. In order to support this functionality there is an overloaded form of setting the on and off properties which not only sets a "label" for the state but also a "value". In our "hey" versus "ho" example you might do the following:

Thus, it is expected that controller.toggled is a boolean value equal to true or false in the following situation:
{{x-toggle value=controller.toggled showLabel='true' off='Hey' on='Ho'}}

However, in v0.1.15 of ember-cli-toggle, controller.toggled is always equal to Ho or Hey when it should be equal to true or false, respectively.

This is fixed in v0.5.5

Great, thank you.


docs: Add -jauto to sphinx flags to improve doc build times

Reduce the amount of time it takes docs to build by utilizing -jauto
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

We've tried this before and there are issues with parallelism between sphinx/breathe (for the doxygen API processing).  See #8941

Alas, content isn't generated correctly when -j is specified.

curious how is the content broken?


SELECT entity with multiple GROUP BY returns partial result

I have 3 entities:
┌────────────┐
│ Commission │
│────────────│
│         id │        ┌──────────────┐
│   merchant │ *───>1 │     Merchant │
│     amount │        │──────────────│
└────────────┘        │           id │        ┌─────────┐
                      │      network │ *───>1 │ Network │
                      │         name │        │─────────│
                      │ currencyCode │        │      id │
                      └──────────────┘        │    name │
                                              └─────────┘

I'm trying to select the total commission amounts, for each network, grouped by currency.
This translates into GROUP BY network, merchant.currencyCode.
If I select Network.id only, it works fine:
SELECT n.id AS networkId, m.currencyCode, SUM(c.amount) AS amount
FROM Model\Network n
INNER JOIN Model\Merchant m WITH m.network = n
INNER JOIN Model\Commission c WITH c.merchant = m
GROUP BY n, m.currencyCode
ORDER BY n.name, m.currencyCode

+---------+----------+--------+
| Network | Currency | Amount |
+---------+----------+--------+
|       1 | EUR      |    100 |
|       1 | USD      |    200 |
|       2 | EUR      |    400 |
|       2 | GBP      |    300 |
|       3 | CAD      |    600 |
|       3 | USD      |    500 |
+---------+----------+--------+

Now if I select the Network entity:
SELECT n AS network, m.currencyCode, SUM(c.amount) AS amount
...

It still works fine when using HYDRATE_ARRAY:
+---------+----------+--------+
| Network | Currency | Amount |
+---------+----------+--------+
|       1 | EUR      |    100 |
|       1 | USD      |    200 |
|       2 | EUR      |    400 |
|       2 | GBP      |    300 |
|       3 | CAD      |    600 |
|       3 | USD      |    500 |
+---------+----------+--------+

But when using HYDRATE_OBJECT, it only returns the last result for each Network:
+---------+----------+--------+
| Network | Currency | Amount |
+---------+----------+--------+
|       1 | USD      |    200 |
|       2 | GBP      |    300 |
|       3 | USD      |    500 |
+---------+----------+--------+

I created a reproducible example in this repository:
https://github.com/BenMorel/doctrine-groupBy-bug
I could not find any documentation for this behaviour, which I believe is a bug, as it behaves differently based on the hydration mode, in addition to being counter-intuitive.

This is the expected behaviour, the object hydration returns exactly one object of each type, in this case overwriting the mixed result group by values.
I just checked and you are right about this not being documented, so I have added it to the docs for the next person: https://github.com/doctrine/doctrine2/commit/0c4f9a886682441628f895bda38bdbb3c1703900

Interesting, thanks. Is there any technical reason why it behaves this way? Would it be possible to create another object hydrator that would behave as I expected?
At the moment I have to retrieve Network ids instead, and do a separate SELECT ... WHERE id in(...) query to load the Networks separately.


Allow environment variables to set CLI defaults

Adds a few environment variable getters that allow to override the default value of some CLI options.
Fixes #754

@woodruffw I've not yet covered documenting the environment variables. Not sure what the best way would be to do it. A multi-line explanation in argparse.ArgumentParser(description) could be one possibility.

Thanks @bittner, this looks like a great initial set!

I've not yet covered documenting the environment variables. Not sure what the best way would be to do it.

Hmm, IMO it'd be fine to document it in the README alone, i.e. under the "Usage" section in a new sub-section above the "Exit codes" one: https://github.com/pypa/pip-audit?tab=readme-ov-file#exit-codes
(A short explainer that some flags honor the environment + a bullet list of each of them would be perfect.)


Fixed #928 by removing 'with' method from expect..to..receive statement

Fixed #928 by removing 'with' method from expect..to..receive statement
Upgraded 6 gems by rebuilding Gemfile.lock file multiple times.

Great, thanks!


[SMALLFIX]Add descriptions about achieving data locality on Spark with Tachyon

Add descriptions about achieving data locality on Spark with Tachyon

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7125/
Test PASSed.

@RongGu Thanks for the additional documentation, should we also include something about setting SPARK_LOCAL_HOSTNAME in spark-env?

@calvinjia Thanks for your comment. Yes, I have verified that setting SPARK_LOCAL_HOSTNAME also works. Acutally, the priority of "-h" is higher than setting SPARK_LOCAL_HOSTNAME in Spark. However, I agree with you on adding setting SPARK_LOCAL_HOSTNAME in our doc. It is more convinent.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7142/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7149/
Test PASSed.

LGTM, thanks!


further limit component loader reorder

Source
https://github.com/ArctosDB/dev/issues/51
Summary
That was possibly a bug, and it was possibly caused by multiple component loader reorder requests. Such updates have been limited to a single user per time period, but that is possibly not sufficient.
Possibly it would be better to remove user control altogether, there's clearly some sort of back-end/front-end/scheduler-API weirdness involved in allowing that to change, but priorities do change and I'm very hesitant to completely remove that ability unless forced.
https://dev.lucee.org/t/duplicate-scheduled-tasks/4086 - a very old, unsolved, non-replicable Lucee bug - describes behavior similar to that in the logs.
User Interface Changes
Component loader processing order updates will be allowed less frequently.
Data Structure Changes
None.

Is there a way to allow the loader to automatically prioritize small, faster requests over larger, slow ones? The primary reason for needing to change the processing order is to expedite a small, urgently needed process, such as a bulkload for a loan that needs to go out that day, over a larger, slow request that will clog up the pipeline for hours or days.


sang juars

selamat menikmati
file
https://github.com/acckoling-afk

tambahan url

py

file

file


[REF] replace deprecated carousel package

Deprecated "notice": https://github.com/meliorence/react-native-snap-carousel/issues/959
moving to: https://github.com/dohooo/react-native-reanimated-carousel

It works fine on ios simulator. Great job!


Update kit & adapter packages

This is causing a navigation issue related to the iframe relative URLs.

Updating kit on a different branch & I've already incorporated these changes


iTerm colors issues

I have a color issue in iTerm, tried different settings/profiles, could not get it work, on the default terminal macos app it works ok, so it's something related to iterm or my settings, do you have any suggestions?
Thank you for this great tool!

Hey @WladyX thanks a lot for reporting this issue
It looks like your iterm configuration is not supporting 256-color format. Ugit requires your terminal type to be xterm-256color. I am  not sure how to do this for iterm, but you can refer iterm2' FAQ and look for How do I get 256 color mode working in vim?
for testing try running the following command, echo $(tput bold)$(tput setaf 208)Bold orange$(tput sgr0)

Thank you @Bhupesh-V for getting back to me.
My iTerm is set to 256-colors, and your snippet looks just like in your screenshot, so that code looks as expected, but ugit does not. Any other ideeas? :)

Thank you @Bhupesh-V for getting back to me. My iTerm is set to 256-colors, and your snippet looks just like in your screenshot, so that code looks as expected, but ugit does not. Any other ideeas? :)
Later edit: I've installed a fresh MacOS VM and tried there with a fresh iterm profile/install. All worked as expected, but when i upgraded to the beta version (which i currently run on my laptop) then it broke the colors. So the colors break on the beta iTerm version.

Hey just to on same page, we are talking about iterm 2 beta here right?

Yes, iterm2 beta does not show the colors.


Error: "Body omitted because it contains binary data"

Using the template, I expect to see en=myCustomEventName in the Request Body, but instead I see the following message:
"Body omitted because it contains binary data".
However the event does indeed show up in the report at the endpoint.

Here is the configuration of my tag:

For the original GA4 tag, the "en=" variable does indeed appear in the request body.
PS: Thanks and congrats on this amazing tag. It is going to be extremely useful to me. I can't believe it doesn't exist by default.

Hi,
as far as I can see, everything works as expected? Request body inspection in the preview is indeed not very helpful but your request contained the parameter inside the body (at least once) and the template obviously changed the value when it arrived correctly at the endpoint (?)
If you want to see the new value as a get parameter, the incoming request should already contain it (with a different value for example).


Sending e-mail takes ages

Hey!
I've tried using the module, as I find it very annoying to write nicely formatted e-mails.
I tried using your example 1, so I just copied the code but replaced the EmailHeaders with my own values:
Email {
    EmailHeader -EmailHeader {
        EmailFrom -Address "OMITTED"
        EmailTo -Addresses "OMITTED"
        EmailServer -Server "OMITTED"
        EmailSubject -Subject "This is a test email"
    }
    EmailBody -FontFamily 'Calibri' -Size 15 {
        EmailText -Text "Hello"
        EmailText -LineBreak
        EmailTextBox {
            'Kind regards,'
            'Evotec IT'
        }
    }
}

When doing so, it takes a total of 42 seconds to 'complete'. I get no return so I don't actually know what happened, but when nothing returns I assume everything went fine. However no e-mail is actually sent, as I retrieve nothing in my inbox, either in spam or in the actual inbox.
Then I do the native way, with the same parameters on Send-MailMessage. So
Send-MailMessage -to "OMITTED" -from "OMITTED" -SmtpServer "OMITTED" -Subject "Hello2"

The command completes directly, and I get the email.

Why is it taking ages to send the e-mail? If I add -whatif it completes in under 0 seconds.
How can I troubleshoot why it's taking so long? I can't find support for CmdletBinding on the functions so I cannot get any verbose output or such.

EDIT: Spelling mistakes

You should try adding -Verbose -Suppress $false to the Email
It will tell you what's wrong. From what I see you probably need to set EmailServer -Server ... -Port 25 as the default is 587, and as I see you are using a relay of sorts right?

Ah, there was -Verbose support, didn't show up in the Intellisense, my bad.
I've added these parameters to Email:
$e = Email -Port 25 -Suppress $false -Verbose {
...
}

PS C:\Windows\system32> $e

Status Error                                                                  SentTo
------ -----                                                                  ------
 False Exception calling "Send" with "1" argument(s): "Failure sending mail."

VERBOSE: Get-Resources - Location: Header - Feature: Main Online: False
VERBOSE: Get-Resources - Location: Header - Feature: MainFlex Online: False
VERBOSE: Get-Resources - Location: Header - Feature: MainImage Online: False
VERBOSE: Get-Resources - Location: Header - Feature: MainLink Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: Main Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainFlex Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainImage Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainLink Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: Main Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainFlex Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainImage Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: MainLink Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: Default Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: DefaultHeadings Online: True
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: Fonts Online: True
VERBOSE: Add-HTMLStyle - Adding link https://fonts.googleapis.com/css?family=Roboto|Hammersmith+One|Questrial|Oswald
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: FontsAwesome Online: True
VERBOSE: Add-HTMLStyle - Adding link https://use.fontawesome.com/releases/v5.14.0/css/all.css
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: Default Online: False
VERBOSE: Get-Resources - Location: HeaderAlways - Feature: DefaultHeadings Online: False
VERBOSE: Add-HTMLStyle - Reading file from C:\Axians\1HRPlusAccountManagement\Modules\PSWriteHTML\0.0.120\Resources\CSS\headings.css
VERBOSE: Get-Resources - Location: FooterAlways - Feature: Main Online: True
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainFlex Online: True
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainImage Online: True
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainLink Online: True
VERBOSE: Get-Resources - Location: FooterAlways - Feature: Main Online: False
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainFlex Online: False
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainImage Online: False
VERBOSE: Get-Resources - Location: FooterAlways - Feature: MainLink Online: False
VERBOSE: Get-Resources - Location: Footer - Feature: Main Online: False
VERBOSE: Get-Resources - Location: Footer - Feature: MainFlex Online: False
VERBOSE: Get-Resources - Location: Footer - Feature: MainImage Online: False
VERBOSE: Get-Resources - Location: Footer - Feature: MainLink Online: False
VERBOSE: Email - Time to send: 0 days, 0 hours, 0 minutes, 42 seconds, 553 milliseconds

Not the wiser with the error message however, as I can send e-mails to that same server with same parameters with Send-MailMessage.

You cant mix Email -Port with EmailServer -Server. You should add port to emailserver command.

Yep - Just realized it myself. Tested and it worked fine.
My mistake, didn't understand that the default port was 587.
Thanks for the help ❤


Allow calling heartbeat from eachMessage handler

This is a small improvement for a pain-point I have had for a while where I have often had to 'eject' out to an eachBatch handler just to gain access to the heartbeat function.
Sometimes consumers have to do a lot of work for individual messages in a topic and in these scenarios it makes sense to have access to the heartbeat function to avoid the session timeout and keep the consumer alive.

Could you please write a test that makes use of this? It's pretty simple, but it's more to prevent regression. It would also be good if you could update the docs with the new property.

Will do. Also need to get the existing tests to pass


dns python

i have this message when i make pip :
root@vps232903:~# pip install dsnpython
Downloading/unpacking dsnpython
Could not find any downloads that satisfy the requirement dsnpython
Cleaning up...
No distributions at all found for dsnpython
Storing debug log for failure in /root/.pip/pip.log
did you know why ??
Best Regards
Lesnox

Hi, you probably want "dnspython" rather than "dsnpython", but I am not quite sure what you are doing..

On 4 Jan 2016, at 21:40, lesnox<EMAIL_ADDRESS>wrote:
i have this message when i make pip :
root@vps232903:~# pip install dsnpython
Downloading/unpacking dsnpython
Could not find any downloads that satisfy the requirement dsnpython
Cleaning up
No distributions at all found for dsnpython
Storing debug log for failure in /root/pip/piplog
did you know why ??
Best Regards
Lesnox
—
Reply to this email directly or view it on GitHub.

Oh sport for that bug :/


the bot does not send a graph((

When the trigger is triggered, the bot sends a message, but there is no graph.
I did all the testing. everything works except Graphs.
The URL, username and password are correct. Checked by going to the web interface. Using the link in the test http://<IP_ADDRESS>//chart3.php?period=3600&name=ololo&width=900&height=200&graphtype=0&legend=1&items[0][itemid]=23706&items[0][sortorder]=0&items[0][drawtype]=5&items[0][color]=00CC00 , the graph is displayed correctly, but it does not come in a telegram

Test private message  https://pastebin.com/XBHyQxNa
Test group message    https://pastebin.com/5b0kasEL
zbxtg_settings.py         https://pastebin.com/Fm6Eav5w
Test Graphs Message  https://pastebin.com/9nGTkwqb
Validate server's URL   https://pastebin.com/KQKRAyHA
4.

Those tests are useless.(((

what other data do you need? I will do


github.com/Uberi/speech_recognition

Have you taken a look at https://github.com/Uberi/speech_recognition ? Isn't it a replacement choice?!

i used it , i think it is just recognition ,no timeline or other thing. forgive my english

Hi, ok thank you for letting me know. I looked and they are also only
offering a free trial of the service... So it is not a long term solution.
Thank you for your software!
On 29 Jun 2016 10:26, "Yue Zhang"<EMAIL_ADDRESS>wrote:
i used it , i think it is just recognition ,no timeline or other thing.
forgive my english
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/agermanidis/autosub/issues/21#issuecomment-229304943,
or mute the thread
https://github.com/notifications/unsubscribe/AESI9Qb-IStZlVkFDmLiR9VN18P1aFPUks5qQjpbgaJpZM4IklrV
.

i used it , i think it is just recognition ,no timeline or other thing. forgive my english

Trial? The code is available in a public repo!


Update codyCommit

Resolves https://github.com/sourcegraph/jetbrains/issues/191.
New commits to the agent:
Handle connection close events with no prior errors or messages (#2391)
Hide LLM dropdown for enterprise users (#2393)
Chat: Honor enterprise token limits (#2395)
Update "Start New Chat" button label casing (#2385)
set more conservative limit for gpt-3.5-turbo to stay under window limit (#2386)
VS Code: Release 1.0.0 (#2377)
Update Marketplace README with new gifs, free/pro info, and NLS (#2357)
HACK: Work around rate limiting errors by parsing the SSE message and reverse-engineering the headers (#2375)
chat: display CTA to create new chat when context limit reached (#2374)
Chat: Re-add /edit and /doc commands (#2373)
Autocomplete: format completions on accept (#2327)
Update rate limit error messages for Cody Pro users (#2364)
Chat: use the correct user tier in the upsell event (#2372)
set context window limit by model (#2371)
Chat: send `openLLMDropdown:clicked` only on dropdown open (#2370)
docs: update dev docs to include `pnpm build` (#2369)
Embeddings: Display accurate percent done; do not toast continued embeddings failure (#2368)
Fix code smell icon (#2367)
Chat: Add Mixtral as a chat model (#2307)
VSCode: Roll cody-engine to v5.2.12792 (#2359)
docs: update docs to new url (#2283)
VSCode: Fix local embeddings e2e test to specifically check that *embeddings* are indexed (#2358)
chat: use search context by default (#2325)
Agent: enable source maps in `pnpm agent` (#2334)
change nls label to beta (#2351)
VS Code: Release 0.18.6 (#2349)
Remove mention of Free/Pro from marketplace (#2347)
Chat: Fix settings menu not opening on click (#2346)
Chat Context: Provide relative path as current file (#2344)
Chat: Fix chat panel titles (#2345)
Update the marketplace readme to match product features (#2280)
Agent: skip file system tests on Windows for now (#2341)
Agent: add test case to accept autocomplete (#2337)
Edit: Update the changelog with a bunch of missed fixes from the last release (#2340)
Custom Commands: Filter out insert and edit commands from chat input (#2339)
Chat: Fix cody icon font usage (#2336)
Agent: implement `vscode.workspace.fs` (#1716)
Autocomplete: remove stop sequences for dynamuc multliline completions (#2326)
Autocomplete: log raw error in the development env (#2323)
Autocomplete: fix invalid position (#2324)
Agent: enable source maps in tests (#2333)
Remove complete command from CLI (#2332)
update pr-auditor token (#2321)
Autocomplete: remove `scminput` from the autocomplete languages setting default value (#2322)
Chore: Skip flaky agent chat cancellation test (#2320)
Update walkthrough to match product features (#2279)
Clean up VS Code Extension Settings (#2278)
VSCode: Make embeddings errors visible, resume indexing on restart (#2265)
Add V2 telemetry to remaining Cody events (#2060)
Chat: Fix reset recipe (#2313)
Autocomplete: Don't show loading spinner when rate limited (#2314)
Fix rate limit number being displayed (#2312)
Chore: Remove some GHA `ifs` that didn't work (#2299)
VS Code: Release 0.18.5 (#2308)
Commands: Include /test (#2305)
telemetry-v2: fix splitSafeMetadata to generate acceptable type (#2273)
Edit: Fix doc command jumping unnecessarily (#2296)
Edit: Flush diffs on apply (#2304)
Edit: Fix malformed comments from doc command with selection (#2290)
Chat: Update welcome message (#2298)
Chat: Add tooltip to disabled chat model selector (#2294)
Edit: Do not scroll into view on complete (#2297)
Fix keyDown:Paste:clicked events (#2293)
remove rg-based local keyword context fetcher (#2295)
Simple chat: Bring back chat telemetry (#2291)
Settings: Remove the "Simple Chat Context" setting (#2286)
Update rate limit error wording for Cody Pro users (#2287)
Chat: Remove Chat Suggestions setting that no longer works (#2284)
Settings: Relabel "symf Context" as "Search Context" (#2285)
Chat: Add support for cody.chat.preInstruction in the new preamble (#2255)
use context.globalStorageUri for symf indexes (#2271)
Add cody-pro-jetbrains feature flag (#2274)
Chat: Edit button to rename history chats (#1818)
VS Code: Release 0.18.4 (#2268)
Do not await `showSetupNotification` (#2267)
VS Code: Release 0.18.3 (#2262)
Autocomplete: Add Experimental hot streak mode (#2118)
Disable gzip compression for SSE streams (#2251)
Only search relative paths when @-mentioning files in chat (#2241)
JetBrains: Fix missing context files in the chat response (#2211)
Chat: Update chat icon and transcript gradient (#2254)
Add a Chat Settings button in Chat panels (#2117)
Replace "Sign Out" with an account dialog (#2233)
VSCode: Local Embeddings should pick up initial access token (#2247)
VSCode: Fix local embeddings status for non-git workspaces, git repos w/out remotes (#2235)
Fix pre-release version numbers not being correctly detected (#2240)
Handle context file searching using forward slashes on Windows (#2215)
VS Code: Release 0.18.2 (#2234)
Update CHANGELOG.md (#2232)
Mark Upgrade/Usage links as dot-com only (#2219)
Update CHANGELOG.md (#2226)
plg: display errors when autocomplete rate limits trigger (#2135)
Search: Only show search instructions on hover or focus (#2212)
Fix "Release Notes" label & link for pre-releases in sidebar (#2210)
send sigkill to symf when extension exits (#2225)
Adding endpoint for fetching feature flag (#2204)
Fix symf index dir on Windows (#2207)
symf: support cancelling index (#2202)
Don't duplicate @-filenames when pressing tab if the whole string has been typed (#2218)
Allow dotfiles to be included in context files list (#2209)
Reset feature flags when switching through logins (#2182)
Add rate limit upgrade for code edits (#2201)
Fix cursor blink issue and ensure proper chat initialization synchronization (#2193)
VSCode: Do not parse Windows file paths as URIs (#2197)
VSCode: Send `embeddings/initialize` to the local embeddings controller (#2183)
Chat: Improve Pro upgrade CTA styles (#2175)
Update intro chat message to be clear about coding questions (#2187)
VS Code: Release 0.18.1 (#2177)
Autocomplete: Remove top_k when using temperature (#2178)
fix: chat show up in tree view on submit (#2171)
Fix rate limit messages for short time spans (#2152)
ensure error message makes it through to chat view (#2176)
Enable symf-based context for chat (cody.experimental.symfContext) (#2166)
Add missing changelogs (#2174)
Chat: Improve slash command heading padding (#2173)
chore: Bump up macOS e2e runner instance size (#2145)
chat: fix abort (#2159)
chat: always include selection in enhanced context (#2144)
VS Code: Release 0.18.0 (#2111)
support custom commands in simple chat (#2153)
Chat: update embeddings and codebase identifiers (#2130)
chore: Speed up at-file-selection e2e test (#2146)
update enhance context display copy (#2086)
Fix isRateLimitError (#2151)
chore: Simplify new-history-ui e2e test to deflake (#2147)
Chat: Update message input placeholder to mention slash commands (#2142)
Chat: Reduce size of chats list blank copy (#2137)
Search: Style and UX improvements to the search panel (#2138)
Chat: Fix message input overlapping with enhanced context button (#2141)
enable cody.experimental.simpleChatContext by default (#2120)
feat: display error in webview for simple chat (#2132)
Chat: Speed up chat panel debounce w/ trigger on leading edge too (#2126)
Link to new Cody feedback URL (#2113)
Chat: Fix infinite loop when searching for symbols (#2114)
fix: invert notification toggle logic (#2122)
chore(deps): update dependency stylelint to ^15.11.0 (#2119)
change: enable new chat and search UIs by default (#2079)

Test plan

test everything possible

It is impossible to test it right now b/c of the issue with the agent (PLG Rate limiting error messages are currently broken).

tested. works!

Can you briefly describe what changes have been made with this update / add this to commit msg? You mentioned that you have a script that prints commits since the last version bump.
It doesn't block me in any way, but I think it would speed-up testing. I tried using GH compare/, but it seems to work only for branches or tags.

I updated the PR description with the commits list.

It seems that everything are working fine (except for the context issues), but I've noticed that we now have a massive amount of this in the logs:
2023-12-15 17:26:54,488 [  68629]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/

On the main branch, this entry only appears during the first launch of the project.
Should we be concerned about this?

It seems that everything are working fine (except for the context issues which we are aware of), but I've noticed that we now have a massive amount of this in the logs, during normal usage:
2023-12-15 17:26:54,488 [  68629]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/

On the main branch, this log only appears during the first launch of the project.
Should we be concerned about this?

I guess it happens for repositories that are not indexed by Sourcegraph.

I'm verifying this on the sourcegraph repo, so it should be indexed by definition. :smile: Interestingly, the status icon indicates that the context has been correctly recognized.

2023-12-15 17:44:50,217 [ 184047]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:44:53,632 [ 187462]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:44:55,896 [ 189726]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:44:57,367 [ 191197]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:01,677 [ 195507]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:03,687 [ 197517]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:03,694 [ 197524]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:04,975 [ 198805]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:17,695 [ 211525]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:21,015 [ 214845]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:28,805 [ 222635]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:28,939 [ 222769]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:28,945 [ 222775]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:30,626 [ 224456]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:31,312 [ 225142]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:35,757 [ 229587]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:48,246 [ 242076]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:48,701 [ 242531]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:49,339 [ 243169]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:49,816 [ 243646]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/
2023-12-15 17:45:50,294 [ 244124]   WARN - #c.s.c.a.CodyAgent - No Git repository for URI file:///home/exigo/projects/sourcegraph/


Function z_swap_next_thread() missing coverage in sched.c

Describe the bug
Function z_swap_next_thread() missing coverage in sched.c.
struct k_thread *z_swap_next_thread(void)
{
#ifdef CONFIG_SMP
return next_up();
#else
return _kernel.ready_q.cache;
#endif
}
When using qemu_x86, this line "return _kernel.ready_q.cache;" cannot be coveraged.  Function z_swap_next_thread only used in do_swap() which is called when enable CONFIG_USE_SWITCH.
To Reproduce
Steps to reproduce the behavior:
twister -p qemu_x86 --coverage -T tests/kernel
Expected behavior
It's probably dead code that should be removed.
Environment (please complete the following information):
OS: ubuntu1~18.04
Toolchain zephyr-sdk-0.12.1

You should try qemu_x86_64

You should try qemu_x86_64

I've tried qemu_x86_64. The branch "return next_up();" was covered.
My concern is branch "return _kernel.ready_q.cache;" is not covered.

My concern is branch "return _kernel.ready_q.cache;" is not covered.

also when you disable SMP?

Firstly, I saw our module coverage report which run command "twister -p qemu_x86 --coverage -T module-list -x=CONFIG_ASSERT=n -C". The else branch "return _kernel.ready_q.cache;" is not covered."
Then, I run "twister -p qemu_x86_x64 --coverage -T tests/kernel/sched" to test SMP situation. The if branch "return next_up();" is covered.
So I think the else branch is redundant. I'm not sure these tests are enough.

you should not edit comments, add your comment below.

hen, I run "twister -p qemu_x86_x64 --coverage -T tests/kernel/sched" to test SMP situation. The if branch "return next_up();" is covered.

you need to disable SMP to get to this, qemu_x86 and qemu_x86_64 use swap vs switch, so you have to test without SMP to get to this.

Thank you very much for telling me the reason of this problem！
I run “twister -p qemu_x86_64 --coverage -T tests/kernel/sched/ -x=CONFIG_SMP=n ”, then the else branch "return _kernel.ready_q.cache;" is covered."
I'm sure this issue can be closed now.


"First Property must be task" in VSCode for valid pipeline

Here is the docs for conditional insertion:
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/templates?view=azure-devops#conditional-insertion
Here is what VSCode looks like if you do this:

The pipeline is valid:

FYI, this is covered here #187

Ok closing as a duplicate.  Can't believe that's been open for 2 years! 😂


How to achieve text after training model

@gagan3012 I have run the codes in your Trainer.ipynb file
The command in your collab is this
keywords=["ski", "mountain", "sky"]
model.predict(keywords)

But I wouldlike to predict text for the same.
How do I do it after training as you did.

The current problem while trying this is if you used GPU to train the model, you have to use it like so.
keywords=["ski", "mountain", "sky"]
model.predict(keywords, use_gpu=False)

TypeError: Trainer.init() got an unexpected keyword argument 'gpus'
could you explain this error when running this line:
model.train(train_df=train_df, test_df=eval_df, batch_size=4, max_epochs=10, use_gpu= False ,tpu_cores= 8)


correct electron-version flag

I had to make this flag name adjustment for electron-packager to run

Cool, thanks! Here is commit in the packager that renamed cli argument https://github.com/electron-userland/electron-packager/commit/b633f8935c20604f8947af40a584d9812e1fdacd


Feature request: Support for hyperlinks between schema components

Is there a rendering mode where you have only top-level fields for each component but with nested components presented as hyperlinks? Something similar to Kubernetes API spec or html mode of openapi-generator?
When you have a lot of components, such feature would make API learning process a bit quicker. Currently it just shows the corresponding part of the schema, which introduces lot of redundancy: if component B is nested inside component A, you will get two entries: one for component A, including sub-component B, and another entry for B. It will me repeated ever more if component B is used in many places.
Having hyperlinks would allow to list all the definitions much more concisely in cases when same components are reused in multiple places. My suggestion is to have the same tree-like UI in method description section but have table-like UI with hyperlinks in the components section (show-components="true").

I forwarded this to our UX team. Do not expect a quick turn around  on this as many UX decisions are driven by our internal user feedback process. also this has been categorized as a low-priority issue.

UX team came back on this, they would like to keep the experience  consistent across the app.
However, if your schema is too complex then you may use schema-expand-level = 1 to limit it from expanding all the nodes


Kernel: fixed an unnecessary loop iteration in the allocator

name: PR template
about: Submit changes to Menix
title: ''
labels: ["pending"]
assignees: ''

What does this PR change?

Tick the applicable box:

[ ] Add new feature

[ ] Feature iteration

[ x] Bug Fix

[ ] Security changes

[ ] Tests

[ ] Documentation

[ ] General Maintenance

Reason for adding a new feature

Checklist

[x] I followed the style considerations for this project
[x] I have added tests to my feature to prove my changes work
[x] I have added documentation explaining what this new feature does
[x] I abide by the security policy of the project

Links

Fixes:

[x ] DONE

This fixes an unnecessary loop iteration in the allocator
Documentation

No documentation needed

[ ] DONE

Fixed in bb66833


passing mediatorConnectionsInvite does not provide best DX

I'm really a fan of the mediatorConnectionsInvite, but the flow it introduces is a bit quirky IMO.
On first launch I want to provide the mediatorConnectionsInvite to connect to the mediator. It will then connect and set the mediator as default. All good. Next launch I don't want to pass the mediatorConnectionsInvite because I'm already connected and have it assigned as default mediator.
Now I need to track outside of the agent whether I already connected to this mediator.
What if, on startup, we first look up the mediation/connection record and see if the invitation (or the keys, or something else) matches and if so do not connect, because we're already connected.
cc @burdettadam

I am glad we are at this discussion. I think checking if we have created a connection with the provided invitation before attempting to reconnect is the way to go. We should probably check if the connection was accepted and if a request for mediation has been granted, and then set that mediator as default.
Do we track the invitation a connection is made with. then we could search all connections for one that has a matching invite.
If we get all mediated connections and search for a connection created by that invitation, we will implicitly know if a connection has been made and mediation granted.
I think this feature (multiple restarts with the same mediatorConnectionsInvite config does not produce multiple mediated connections) is needed and I have no bias in how we implement it.

Fixed in #419


Urgent: DPS breaks after upgrade to docker-ce version >25

What is Happening / What is expected

Please describe how to reproduce the issue with a minimal example
Upgrade docker-ce to version 25 and above, DSP will stop working due to outdated client API version.

client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

Describe what you expected to happen and why
upgrade client libs to meet the dependencies of docker API

Specs

OS: Debian Bullseye
Docker Version: 25
DPS Version: docker image latest (0f1a63d45c2f)
Attach DPS Log file

WAR c.m.d.dnsconfigurator.DnsConfigurators            l=58   m=lambda$configurationHook$0      status=failedToConfigureAsDefaultDns, path=/host/etc/systemd/resolved.conf,/host/et
c/resolv.conf,/etc/systemd/resolved.conf,/etc/resolv.conf, msg=Status 400: client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version
com.github.dockerjava.api.exception.BadRequestException: Status 400: client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

Same problem here when docker version is >= 25
On another machine, where I have docker 24.0.7 build afdd53b4e3, all works fine.

@friimaind yeah, the issue is starting to become very clear here. Thanks for your report. I'd guess that it'll be an easy fix for someone with a solid knowledge of Java. Still, this project seems to be abandoned and no longer maintained. Maybe anybody out there who wants to maintain and fix a Java application? ^^

+1. I have same issue. Hoping for  someone with java knowledge to update the client API.

+1. I have same issue. Hoping for someone with java knowledge to update the client API.

Same problem here when docker version is >= 25

Getting the same exception with Docker version 25.0.1, build 29cf629 on Ubuntu 20.04.5 LTS

For those having the issue with docker version > 25, please check this [thread  ] (https://stackoverflow.com/questions/37242217/access-docker-container-from-host-using-containers-name) of fnkr. This is an ideal alternative.
Thanks,

Same problem :)
paul@behemoth ~> docker --version
Docker version 25.0.1, build 29cf629

aul@behemoth ~ [SIGINT]> docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock defreitas/dns-proxy-server
13:59:46.536 [main           ] INF com.mageddo.dnsproxyserver.config.Configs         l=166  m=build                           status=configuring, configFile=/app/conf/config.json
13:59:46.538 [main           ] INF com.mageddo.dnsproxyserver.docker.EventListener   l=33   m=onStart                         status=binding-docker-events, dockerConnected=false
13:59:46.538 [main           ] INF c.mageddo.dnsproxyserver.server.dns.UDPServerPool l=31   m=start                           Starting UDP server, addresses=/<IP_ADDRESS>:53
13:59:46.542 [Thread-4       ] INF com.mageddo.dnsproxyserver.server.dns.TCPServer   l=50   m=start0                          status=tcpServerStarting, port=53
13:59:46.542 [main           ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=32   m=start                           status=startingDnsServer, protocol=UDP_TCP, port=53
13:59:46.542 [main           ] INF com.mageddo.http.WebServer                        l=134  m=start                           status=startingWebServer, port=5380
13:59:51.540 [Thread-2       ] WAR c.m.d.dnsconfigurator.DnsConfigurators            l=58   m=lambda$configurationHook$0      status=failedToConfigureAsDefaultDns, path=/host/etc/systemd/resolved.conf,/host/etc/resolv.conf,/etc/systemd/resolved.conf,/etc/resolv.conf, msg=Status 400: client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

com.github.dockerjava.api.exception.BadRequestException: Status 400: client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

	at com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:237)
	at com.github.dockerjava.core.DefaultInvocationBuilder.get(DefaultInvocationBuilder.java:202)
	at com.github.dockerjava.core.DefaultInvocationBuilder.get(DefaultInvocationBuilder.java:74)
	at com.github.dockerjava.core.exec.ListContainersCmdExec.execute(ListContainersCmdExec.java:44)
	at com.github.dockerjava.core.exec.ListContainersCmdExec.execute(ListContainersCmdExec.java:15)
	at com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21)
	at com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
	at com.mageddo.dnsproxyserver.docker.DpsContainerManager.findDpsContainer(DpsContainerManager.java:99)
	at com.mageddo.dnsproxyserver.docker.DpsContainerManager.findDpsContainerIP(DpsContainerManager.java:113)
	at com.mageddo.dnsproxyserver.dnsconfigurator.DpsIpDiscover.findDpsIP(DpsIpDiscover.java:25)
	at com.mageddo.dnsproxyserver.dnsconfigurator.DnsConfigurators.findIpAddr(DnsConfigurators.java:70)
	at com.mageddo.dnsproxyserver.dnsconfigurator.DnsConfigurators.lambda$configurationHook$0(DnsConfigurators.java:50)
	at java.base@19.0.2/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
	at java.base@19.0.2/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
	at java.base@19.0.2/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
	at java.base@19.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base@19.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base@19.0.2/java.lang.Thread.run(Thread.java:1589)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:775)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:203)

I have created a PR with the fix. Not sure if it will get merged so I have created a release on my fork and a docker image ghcr.io/thisisqasim/dns-proxy-server

I have created a PR with the fix. Not sure if it will get merged so I have created a release on my fork and a docker image ghcr.io/thisisqasim/dns-proxy-server

Thanks @ThisIsQasim , your image is working good in my case.
OS: Pop!_OS 22.04 LTS
Docker: version 25.0.1, build 29cf629

Any update?

3.16.1 is out. Can anyone confirms it fixes the issue?

Fixed for me


Updates store method on api class

store method updated to add data by whats in the request… and not via $model::create(attr) since this caused unknown attributes index issues later during the json serialize response process.

Coverage increased (+0.2%) to 51.756% when pulling 453ebef805d49643c1b33ee0621ecca8c3e7ea92 on surgiie:bug_fix_on_store_add_data into 771da8f9ded465b5a709ddfcb4e7da1a10ec750b on dialinno:dev.

I'll pull it in, but this will get changed back to similar to how it was before at some point.
The models may fenangle some data before they send it back, and you'd never see that.  An example of this would be mutated properties. Perhaps we have a full_name on a Model, constructed from first and last. You'd never see that in the response, because we're just echoing back the request data.


/?_bhlid=2b1d8561f5a0f3824a46900b2e0635c4b24e65fe

Example URLs:
https://www.theogrowth.com/?_bhlid=2b1d8561f5a0f3824a46900b2e0635c4b24e65fe

Bad params:

_bhlid

Additional context:
This is a tracking link from the Beehiiv tracking/marketing tool

Also, thank you so much for building tidy-url!


add arbitrary variable replacement in docs, use for sdk version

Proposed changes:

add ability to replace whatever variables we like
replace sdk version instead of pinning .0
close #5809

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@akelad what's up with this PR?


Mention Brussels talk

Hello :-)
Because I often recommend this tool to Git newcomers, it would be great if the website referred to the talk.
Cheers!

You're welcome, and thanks for merging :-)


Trouble with buttons

When including buttons on a page, e.g. I tried:
{{md-btn text='Button' action='debug'}}
{{md-btn text='Button' icon='mdi-action-favorite' action='debug'}}
{{md-btn text='Button' icon='mdi-action-favorite' iconPosition='right' action='debug'}}
{{md-btn icon='mdi-action-favorite' action='debug' buttonType='floating'}}
{{md-btn text='Flat button' action='debug' buttonType='flat'}}
{{md-btn-submit icon='mdi-content-send' iconPosition='right' text='Submit'}}
{{md-btn text='Large button' action='debug' buttonType='large'}}
{{md-btn text='Disabled button' isDisabled=true}}

Uncaught Error: Could not find module 'ember-new-computed' imported from 'ember-cli-materialize/components/md-btn'

Sounds like an npm issue. Try removing your node_modules folder and npm install

No go - rm -rf node_modules && npm cache clean && npm install, getting the same error :(

$ ember -v
version: 0.2.3
node: 0.12.0
npm: 2.7.6

DEBUG: -------------------------------
vendor.js:14605 DEBUG: Ember      : 1.11.1
vendor.js:14605 DEBUG: Ember Data : 1.0.0-beta.16.1
vendor.js:14605 DEBUG: jQuery     : 2.1.3
vendor.js:14605 DEBUG: -------------------------------

ok I can reproduce this now. Will have a fix ready shortly

:+1:  Thanks!
I will keep an eye on this thread :)

Found the problem. You can unblock yourself right now by using this in your package.json
"ember-cli-materialize": "https://github.com/truenorth/ember-cli-materialize.git#dependencies",

I will submit a PR for the fix shortly, and cut a new release

Thanks for the quick fix! Looks like I am away to the races :)

@brandonparsons ok you can point to https://github.com/sgasser/ember-cli-materialize.git#0.13.4 until @sgasser pushes the new release to NPM.
Running the blueprint again will add all other addon dependencies to your package.json
ember g ember-cli-materialize


scheduler: move to k8stopologyawareschedwg/k8sschedulerconfig-api

this is to remove the last dependency to k8s.io/kubernetes in application code.

hold please

obsoleted by https://github.com/k8stopologyawareschedwg/deployer/pull/225


FTCellConfiguration not working.

I want to change text color and font. For that i have tried below code but it's not working.
let cellConfiguration = FTCellConfiguration()
cellConfiguration.textColor = .black
cellConfiguration.textFont = UIFont.init(name: Fonts.AvenirRegular, size: 14.0)!
cellConfiguration.textAlignment = .left

var cellConfigurationArray: [FTCellConfiguration]?
cellConfigurationArray?.append(cellConfiguration)

FTPopOverMenu.showForSender(sender: sender, with: activeEmployeeOption, menuImageArray: [], cellConfigurationArray: cellConfigurationArray, done: { (selectedIndex) -> () in
    print(selectedIndex)
})

No crash with above code but color & font not working.
OR
FTPopOverMenu.showForSender(sender: sender, with: activeEmployeeOption, menuImageArray: [], cellConfigurationArray: [cellConfiguration], done: { (selectedIndex) -> () in
     print(selectedIndex)
})

If i use above line of code then app getting crash with Fatal error.
Fatal error: Index out of range: file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-1<IP_ADDRESS>/swift/stdlib/public/core/ContiguousArrayBuffer.swift, line 444
Will anyone please guide me why it's not working or let me know the steps to change it.
Thanks

try this

@liufengting , thanks for you comment. i am using pod 'FTPopOverMenu_Swift', '~> 0.2.0' and getting error with below line.
let configuration = FTConfiguration()
'FTConfiguration' initializer is inaccessible due to 'internal' protection level


Using latest version when there is also an entry that includes the version

Example: cookiecutter
bom.json
PyYAML appears twice, once with "latest" and once with the version, as does requests. I think it makes more sense to only output the entry with a real version, rather than assuming a different version should be included when we can't provide any useful information about what that version is or if it's even a thing.
The bom also includes several nonsense entries, including packages with the following names:
{%
Click{%
pytest{%
ERROR: Invalid requirement: '{% extends "base-requirements.jinja" %}' (from line 1 of C:\Users\user\SampleProjects\python\cookiecutter\tests\test-templates\extends{{cookiecutter.project_slug}}\requirements.txt)
ERROR: Invalid requirement: {% if cookiecutter.command_line_interface|lower == 'click' -%}
main.py: error: no such option: -%

@cerrussell I don't know what the expected behavior must be for such template projects. Since there are a number of errors generated while trying to build, the virtualenv is in a state where it is messed up, so the bom is incomplete. This is mentioned in the log.

@prabhu What about this part

PyYAML appears twice, once with "latest" and once with the version, as does requests. I think it makes more sense to only output the entry with a real version, rather than assuming a different version should be included when we can't provide any useful information about what that version is or if it's even a thing.

Is my suggestion reasonable? This happens so frequently, often with the root component, and could be easily remedied.

@cerrussell, do you have another repo to reproduce this? For both component and root component?

@prabhu Here's an example where it's the root component.
scrapy-bom-ubuntu-latest.json


The environment created by vue-cli cannot determine the type of async function

Version
3.5.0
Reproduction link
https://github.com/vuejs/vue-cli/issues/3653
Environment info
 System:
    OS: macOS 10.14.3
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
    Yarn: 1.13.0 - ~/.nvm/versions/node/v10.15.3/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm
  Browsers:
    Chrome: 73.0.3683.75
    Firefox: 65.0.1
    Safari: 12.0.3
  npmGlobalPackages:
    @vue/cli: 3.5.0

Steps to reproduce
mounted() {
let str = Object.getPrototypeOf(this.test1).constructor;
console.log(str);  // ƒ Function() { [native code] }
},
methods: {
async test1() {
}

}
What is expected?
Solve this problem
What is actually happening?
Unable to determine type

Still no reproduction.

https://github.com/babel/babel/issues/4691
https://github.com/babel/babel/issues/7767
https://github.com/babel/babel/issues/8642
Unless you turn off babel transpiling, there's no way to distinguish a async function from normal functions.


kaboom option scale has an issue.

Hi,
Apparently, in v3000, when kaboom is initialized with options of width and height values and adding scale value that is not 1, canvas size and game elements correctly changes according to the scale option.  However,  when debug.inspect = true, hovering over the area where the game elements were originally located when scale was 1, element description pops up.   This phenomenon was found when onClick event was applied to a game object with kaboom scale option, and the event was registered outside of the the area of the game element sprite.
Playground for v3000 shows the issue, but playground for v2000 didn't have problem.    The following code was used to test the phenomenon.
kaboom({
	width: 1200,
	height: 600,
	scale: 0.4,
})

loadSprite("bean", "/sprites/bean.png")

const player = add([
	sprite("bean"),
	pos(120, 80),
	rotate(0),
	anchor("center"),
	area(),
	"player"
])

onClick("player",()=>{
	debug.log("clicked")
})

debug.inspect = true;

Yeah that's a regression, 54ba685ef02542ee619433f62dab80840979886f this should fix it


Extraordinary number of drawcalls with labels contain lots of characters

Draw an label control with 1000 of characters would be consume more than 1000 draw call(s) in current version of godot engine, every character consume an draw-call, and other control like Sprite9Frame consume 9 draw-calls
perhaps add sprite-batcher optimization for canvas_item draw can fix this problem.

This number of draw calls is not much of a problem in OpenGL. Batching is not really necesary.
If you are seeing performance issues, it's most likely due to the way Godot draws the characters (it's kinda inefficient).
It needs to be done in a way where setting up array states is more efficient, but this is a little difficult in GLES2. We'll be doing a rewrite of all this after 2.1 is out, so a simple benchmark (drawing a large text?) we can use as reference could be very useful.

Why is 1000 draw calls not a problem in OpenGL? I remember having frame drops on tablets with only 100 draw calls with a previous project on Unity.

It depends on how the draw calls are done. In Godot (for 2D) they should be
fairly cheap.
There is also another problem with text, which is that font textures are
generated on the fly if you use DynamicFont. If characters come from
different textures, there is no possibility of batching them. I still think
this is something that should be easy to optimize in 3.0, so some sort of
demo would be very appreciate.
On Thu, Jul 21, 2016 at 6:36 PM, Marc<EMAIL_ADDRESS>wrote:

Why is 1000 draw calls not a problem in OpenGL? I remember having frame
drops on tablets with only 100 draw calls with a previous project on Unity.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/5838#issuecomment-234391617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2yY8rWwbhKlTtrQzWb77aQ-LfsGKks5qX-ZagaJpZM4JRxDJ
.

This should not be a problem in the GLES3 renderer anymore, but it's difficult to fix for a GLES2 backend (as many phones need this). I will leave it open but might be better to eventually wait for phones to get better than fixing this.


Requesting review

Here's the imxrt1062-fcb-gen from the teensy4-rs project. It's more advanced than the original crate, and it's gone through a rename. I'm looking for some early feedback before we start considering it.
How's the name? I went with boot-gen because it generates data structures required for booting. I changed it from fcb-gen, which had meant "firmware configuration block" (FCB). I was abusing that term. The FCB is a specific data structure in the serial NAND boot process. I confused the abbreviation with FlexSPI configuration block (FCB), which is general to all serial FLASH boot data structures. But, if we stick with fcb-gen, we can't extend the crate to include SEMC (parallel FLASH) booting! boot-gen is all I could think of. (I also want to play with IVT and DCD hooks in this crate, and the generic name leaves us open to that possibility.)
How's the feature-flag utilization? We require a feature flag, just as we require a feature flag in the RAL crate. The feature flags don't do much, since we only support the most common feature: an FCB for serial NOR FLASH over FlexSPI.
Will it actually work with the iMXRT1011 EVK board? I studied the 1010 reference manual, and compared it to the 1060 reference manual and implementation. I found a few discrepancies, and I accounted for them behind feature flags. From my understanding, this crate should be ready to generate a 1011's FCB for serial NOR flash boot.
Finally, and maybe most importantly, is this all too much? Seems like a lot of overhead to generate a byte array. I justify it by saying the approach is self-documenting, and it could help defend against silly programming errors. It's the opposite of the Teensy approach, which hard-codes the array. Let me know if this all seems too complex for what it's actually doing.

First I think this is a nice way of doing this. Looking at how the NXP SDK does it with some compiler specific attributes on a C struct, which may-or-may not pan out depending on how you configure it, I think this method provides a very easy method of doing things and can be checked at compile time using the builder interface. Bravo. NXP themselves call it a boot header I believe in their SDK, this being a generator for that, the name makes sense.
I don't think its that much overhead, its part of the chip itself. One thing to keep in mind is that in the NXP SDK the boot header is disabled when running from ram presumably for debugging, not sure if that's something that's easy to account for, probably easy enough to document and use a application specific feature flag for perhaps.

I think it might be helpful to specify how much of this
https://community.nxp.com/docs/DOC-341317
This project tackles in the readme, and what the goals are.
All of it?
I don't know, it would be nice to have digital signing of images too at some point far in the future.

Thanks for the thoughts! We'll stick with this approach, unless we feel a good reason to change. Like you mentioned, it's should give us a good path forward for adding other capabilities.
I've made some changes to the API. I realized that the approach I was proposing wouldn't be backwards-compatible. If we kept with the current pattern, we would end up making more public fields, and users would be required to add those fields, else suffer breaking changes. I've changed the API to follow a real builder. Let me know if the previous API was favorable.
Also thanks for the guide link. I'll keep NXP SDK conventions in mind as we move forward.

I was also considering an approach that resembled
use imxrt_boot::serial_flash::*;

#[link_section = ".whatever.you.want"]
#[no_mangle]
pub static YOUR_FCB_NAME: FCB = fcb! {
    read_sample_clock_source: ReadSampleClockSource::LoopbackFromDQSPad,
    cs_hold_time: CSHoldTime(0x01),
    cs_setup_time: CSSetupTime(0x02),
    column_address_width: ColumnAddressWidth::OtherDevices,
    device_mode_cfg_enabled: 0,
    wait_time_cfg_commands: 0,
    s_flash_a1_size: SerialFlashSize::new(0x0020_0000),
    // Other fields...
};

The library exposes the FCB type, which looks like
#[repr(C)]
pub struct FCB {
    #[doc(hidden)]
    pub _tag: u32,
    #[doc(hidden)]
    pub _version: u32,
    #[doc(hidden)]
    pub _reserved0: [u8; 4],
    pub read_sample_clock_source: ReadSampleClockSource,
    pub cs_hold_time: CSHoldTime,
    pub cs_setup_time: CSSetupTime,
    pub column_address_width: ColumnAddressWidth,
    pub device_mode_cfg_enabled: u8,
    #[doc(hidden)]
    pub _reserved1: [u8; 1],
    // Other fields...
}

The fcb!() macro would handle the initialization of the hidden fields, and provide a compile-time interface for defining the FCB. The FCB memory is laid out just as we need it. This is the "how it might be done in C" approach. This skips the whole build.rs process to auto-generate code. Users are responsible for defining the symbol name and link section.
I didn't finish prototyping this, so I'm not sure if it would work or scale. Just putting it out there in case anyone wants to consider it!


IDENTITY-7381 IdP Initiated Login/logout - Error

The flow is working fine for all SP initiated requests (login and logout), however, its not the case with IdP initiated. SAML requests reach /commonauth URL, however, it throws an error as below:
Context does not exist. Probably due to invalidated cache	More
TID[-1234] [IS] [2017-12-26 17:00:12,826] ERROR
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
Context does not exist. Probably due to invalidated cache
Find below the SP metadata XML with the external IdP
<?xml version="1.0"?>
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" validUntil="2017-11-07T17:29:39Z" cacheDuration="PT604800S" entityID="jobs.clientdomain.com">
<md:SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="false" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
<md:KeyDescriptor use="signing">
<ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:X509Data>
<ds:X509Certificate>$KEY</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</md:KeyDescriptor>
<md:KeyDescriptor use="encryption">
<ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:X509Data>
<ds:X509Certificate>$KEY</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</md:KeyDescriptor>
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://wso2-domain/commonauth"/>
<md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat>
<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://wso2-domain/commonauth" index="1"/>
</md:SPSSODescriptor>
</md:EntityDescriptor>

Labels
Type: Improvement
Priority: Normal
Severity: Major
Estimated Complexity: Moderate
Issue migrated from: https://wso2.org/jira/browse/IDENTITY-7381

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


fix(nuxt): ignore manifest when prerendering

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/24487
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
We manually copy manifest, so it shouldn't be prerendered. This ensures we don't prerender them even if a link to the manifest is detected in the rendered HTML.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@2820dfe). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #24504   +/-   ##
=======================================
  Coverage        ?   58.65%
=======================================
  Files           ?        5
  Lines           ?      861
  Branches        ?       46
=======================================
  Hits            ?      505
  Misses          ?      356
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

It still doesn't work in 3.9.0, but I can solve this problem with configuration:
nitro: {
    prerender: {
      ignore: ['/manifest.json']
    }
}


native shuffle reader seems has bug for array type

Describe the bug
when using array_agg to support collect_list function (PR https://github.com/oap-project/gluten/pull/2526) . I can get array result from stage 1, but the shuffle reader seems can't identify the array type
To Reproduce
Steps to reproduce the behavior:

pull the pr #2526
run ut in GlutenDataFrameAggregateSuite
print result from array_agg in WholeStageResultIterator::next()

gluten outputgluten output

[ROW ROW<n2_0:ARRAY<INTEGER>,n2_1:ARRAY<INTEGER>>: 1 elements, no nulls]
[ROW ROW<n2_0:ARRAY<INTEGER>,n2_1:ARRAY<INTEGER>>: 1 elements, no nulls]
0: {1 elements starting at 0 {1}, 1 elements starting at 0 {2}}
0: {2 elements starting at 0 {2, 3}, 2 elements starting at 0 {2, 4}}

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

This may be not shuffle read bug.
write row vector write row vector [ROW ROW<n2_0:ARRAY,n2_1:ARRAY>: 1 elements, no nulls]
shuffle read type ROWbuf:VARBINARY,buf:VARBINARY
Maybe this hasaggregate needs post projection.
https://github.com/oap-project/gluten/blob/main/backends-velox/src/main/scala/io/glutenproject/execution/HashAggregateExecTransformer.scala#L857C23-L857C42

I caught the root reason. Will fix it. @jinchengchenghh, thank you for giving some clues.

@PHILO-HE did we close this already? If so, we can paste PR link here and close this issue. Thanks!

We have one PR to fix this issue. This issue is fixed, but still have some inconsistent issue for some inputs.
https://github.com/oap-project/gluten/pull/2669


Add DNSPod DNS Provider

What this PR does / why we need it:
Support DNSPod DNS Provider.
Special notes for your reviewer:
Copied from xenolf lego package, and tested in my local cluster.
Add DNSPod DNS Provider

/ok-to-test

/assign @munnerz
To add one DNS provider is easy, but still need some modifications from xenolf/lego.
Is there any way to just declare the dns provider and use xenolf/lego directly without copy and modify?

Any plan to merge this PR?

@hemslo thanks for the PR.
At present, no it's not possible due to some hardcoded dependencies on other packages (our util package) that are incompatible with cert-manager.
This looks good to me. Would you also be willing to add yourself as a reviewer for future changes to this part of the codebase? Our infrastructure may then request reviews from you when files in the dnspod directory change.
If you could add a file named OWNERS in the dnspod directory with:
reviewers:
- hemslo

We've not previously requested this, but with the addition of many more dns providers that we do not have our own provisions for testing, it'd be useful to have a few people noted that can be pinged on changes here 😃

@munnerz sure, OWNERS file added. Currently I use my fork's docker image in my cluster, looking forward to using official one after PR merged.

/test e2e v1.7

Hope to add support to dnspod.

I need this!

/retest

really need this.
dnspod is the most popular in china.

/retest

Maybe it's time for merging.

First of all, thanks for this pull request and for your time working on it.
As you may have seen in the latest release notes, we have added a DNS01 provider extension
mechanism to cert-manager that allows out-of-tree DNS01 providers to be
built, including an example repository
to act as a template for how to implement your own providers.
At this time, we don't have the bandwidth nor means to maintain and automatically
test this DNS01 provider, and so I'm going to close this PR and ask that you
port your changes over to the new webhook example format in order to allow
anyone to use your new provider without needing to have it accepted into
the cert-manager codebase.
If in future your plugin has a wide user base and sufficient testing, we
may consider accepting it into the cert-manager project. The exact process
for this is still to be worked out, and we'd like to work with the community
to determine how we should best publish plugins for users :smile:
Again, thank you for your time, and I look forward to hearing your feedback
on the new DNS provider plugin feature!

@hemslo have you write a DNS01 provider extension for DnsPod? please.

@chenmin1992 not yet, but you can also use ACME-DNS as an alternative.

@hemslo thank you man, I found this https://github.com/qqshfox/cert-manager-webhook-dnspod, I will try it.


Debuginfo locals

TODO

[ ] Undo testing changes
[ ] Correct debuginfo for non-mutable references and pointers
[ ] Use DW_TAG_param
[ ] Handle DW_AT_location for CPlaceInner::Addr

cc https://github.com/bjorn3/rustc_codegen_cranelift/issues/166

I am going to merge this with local debuginfo generation disabled to prevent bitrotting.