ActionView::Template::Error: undefined method `[]' for nil:NilClass

View details in Rollbar: https://rollbar.com/trystant/BOW/items/600/

NoMethodError: undefined method `[]' for nil:NilClass
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/lib/rails_admin/config/fields/base.rb", line 314, in form_default_value
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/views/rails_admin/main/_form_filtering_multiselect.html.haml", line 42, in _vendor_bundle_ruby_______gems_rails_admin_______app_views_rails_admin_main__form_filtering_multiselect_html_haml__3920970096128649439_70154718642900
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/template.rb", line 145, in block in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb", line 164, in block in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications/instrumenter.rb", line 20, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb", line 164, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/template.rb", line 333, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/template.rb", line 143, in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/partial_renderer.rb", line 339, in render_partial
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/partial_renderer.rb", line 310, in block in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/abstract_renderer.rb", line 39, in block in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb", line 164, in block in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications/instrumenter.rb", line 20, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb", line 164, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/abstract_renderer.rb", line 39, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/partial_renderer.rb", line 309, in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/renderer.rb", line 51, in render_partial
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/renderer/renderer.rb", line 25, in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/rendering_helper.rb", line 32, in render
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 10, in block in render_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers.rb", line 89, in non_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 10, in render_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/lib/rails_admin/config/fields/base.rb", line 217, in block in <class:Base>
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/lib/rails_admin/config/configurable.rb", line 66, in instance_eval
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/lib/rails_admin/config/configurable.rb", line 66, in block in register_instance_option
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/lib/rails_admin/config/proxyable/proxy.rb", line 29, in method_missing
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 69, in field_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 51, in block in input_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 38, in block in capture
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 202, in with_output_buffer
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_xss_mods.rb", line 5, in with_output_buffer_with_haml_xss
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 38, in capture
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 52, in capture_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/tag_helper.rb", line 106, in content_tag
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 69, in content_tag_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 50, in input_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 39, in block in field_wrapper_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 38, in block in capture
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 202, in with_output_buffer
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_xss_mods.rb", line 5, in with_output_buffer_with_haml_xss
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 38, in capture
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 52, in capture_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/tag_helper.rb", line 106, in content_tag
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb", line 69, in content_tag_with_haml
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 37, in field_wrapper_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 28, in block (2 levels) in fieldset_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 28, in collect
  File "/app/vendor/bundle/ruby/2.3.0/gems/rails_admin-0.6.7/app/helpers/rails_admin/form_builder.rb", line 28, in block in fieldset_for
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 38, in block in capture
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/helpers/capture_helper.rb", line 202, in with_output_buffer
  File "/app/vendor/bundle/ruby/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_xss_mods.rb", line 5, in with_output_buffer_with_haml_xss
  File "/app/vendor/bundle/ruby/2.3.0/g

Closing this due to # of occurrences and localized area of the bug.


Windows Explorer High CPU Usage

Hi, so after a day of use, I noticed that my CPU usage for file explorer is really high, even when file explorer is not in use by me

When I restart Shell, the file explorer CPU usage seems to go back to normal, but then it gradually increases back to high usage

You already know what my config file looks like, so could it be something in the config messing my CPU usage up?

Never mind, I think I may have found the problem, an application called "Flow Launcher" is causing the high usage when searching for directories, and the high usage does not stop after that, looks like I will have to find out on their side


why in the examples simple-producer have no queue declare and binding?

why the code in the examples simple-producer have no queue declare and binding? I try to run simple-producer at the first,at the end of the producer,I run simple-consumer,during the time,the message is losed.Only I run simple-consumer at first which have declare queue and binding can work.

Publishers are discouraged from (or at least not required to) declaring queues unless they also consume. Consumers are supposed to do that.


Agent fails after long time working

Test was started at 10 PM and works fine for several hours, morning whole of agent console was in error messages:

I'm sorry, but the error source is in underlying SIGAR library, which is dead project. I doubt anything can be done there...


sort function not work

i try to sort contours
let filename = format!("src/{}", "sp010.png");
let src = match imread(&filename, IMREAD_COLOR) {
    Ok(ok) => ok,
    Err(error) => {
        panic!("Fatal ERROR reading the image : {}. Is this file exist? Have you the right to read it? Is it empty? . Error : {:?}", filename, error)
    }
};
let temp = no_array().unwrap();
let mut dst = VectorOfMat::new();
let zero_offset = Point::new(7, 20);
let mut vec = VectorOfMat::new();
let mut gray_img = Mat::default().unwrap();
cvt_color(&src, &mut gray_img, COLOR_BGR2GRAY, 0).unwrap();
threshold(&gray_img.clone().unwrap(), &mut gray_img, 50., 255., THRESH_BINARY | THRESH_OTSU);

let thres_img = gray_img.clone().unwrap();

match find_contours(&thres_img, &mut vec, RETR_LIST, CHAIN_APPROX_NONE, zero_offset) {
    Ok(_ok) => {
        //  println!("[OK] find contours");
    }
    Err(error) => {
        //   println!("[KO] find contours: {}", error);
    }
};

sort(&vec, &mut dst, 0);

for cnt in vec.iter() {

   let area = contour_area(&cnt, false).unwrap();

}

Are you getting a specific error? Which one? Can you please explain what behavior you expect and what do you see? I also note that you don't check the result of sort. It might be returning an error, please do a sort(&vec, &mut dst, 0).unwrap() to check that.

it error on this
sort(&vec, &mut dst, 0).unwrap()
thread 'main' panicked at 'called Result::unwrap() on an Err value: Error { code: -215, message: "OpenCV(4.3.0) /tmp/opencv-20200616-49166-1dqpga1/opencv-4.3.0/modules/core/src/matrix_wrap.cpp:88: error: (-215:Assertion failed) 0 <= i && i < (int)v.size() in function 'getMat_'\n" }', src/main.rs:126:14

It's coming from within OpenCV, looks like dst argument is not sized properly. You should check the documentation link I posted earlier for some more info.

i think incorrect input   parameter for sort function
https://stackoverflow.com/questions/13495207/opencv-c-sorting-contours-by-their-contourarea

Have you managed to find out the correct arguments?


Support Multiple Hosts for a Route

As per this Twitter thread, I recently configured NGINX to support local development of a multi-tenant service.
The configuration is as follows...

To replicate this it seemed to required multiple routes, which for numerous tenant domains would be painful.

I understand it is planned to remove the requirement for the host in which case, path matching for all hosts would occur. However, we also need to match specific paths for each host to different services.

Would changing host to be an array solve the problem for you?

We have a similar scenario and changing host to be an array would solve it for us.

Yes it would @samsp-msft

@stevejgordon we expect many of our customers will use a programmatic approach to set up large deployments. Do you expect to stick with the config file approach long term?

https://github.com/microsoft/reverse-proxy/issues/164 proposes a grouping feature that could help here. In theory the above config could have everything grouped except for the route id and host.

@Tratcher For our scenario there could be a few hundred hosts all with the same route. We plan to use the programmatic approach, but wouldn't it be better to define the route once with a hosts array instead of creating the same route for each host?

@saithis from an implementation perspective there's a limit here based on what AspNetCore routing supports. Right now I think you can only specify zero or one host per route.
The config could still be array based but the implementation may have to copy that into multiple routes.
How many of these hosts could be consolidated using a single wildcard (*.example.com)? I think that's already supported by routing.

All of them are like customername.example.com and most of the time all but a few have the same route, but while we are rolling out a new release, we will switch them over one by one to a new route.
So maybe we could add a *.example.com host for the most used route and only add the others individually (if the proxy prioritises the individual routes over the wildcard one). But in the middle of upgrading, we would still have to add half of them individually.
Also if we rush the release out, then the config would change multiple times per minute until all customers are updated. So the fewer config objects we have to create, the better.

@stevejgordon we expect many of our customers will use a programmatic approach to set up large deployments. Do you expect to stick with the config file approach long term?

If it were just me, programmatic would appeal in some cases. However, much of this layer is managed by a systems team and there config would likely be preferred. That could change with something like YARP where it could become more of a dev service.
Right now we manage three sites for each client under their own domains which route to us. In some cases the three domains will be on the same hierarchy, but sometimes not. With hundreds of clients this grows quite rapidly.
For a simple local dev proxy I'd be happy to configure in code.
Offhand I'm not sure what our current NGINX configs looks like for prod. Everything is fronted by CloudFront and some host infoand client identifiers is stamped onto headers routed on from there. I'll see if I can get my hands on some more details on what that looks like in production at the moment.
We also have some Kong gateways in the chain for Auth requirements. Our infrastructure is quite complex as we're breaking a monolith down into microservices. So we have layers of routing as we migrate over. Over time we can simplify that.

@stevejgordon let me clarify. What I mean programmatically setting up routes is pulling them from a database or similar. It seems like anyone generating a large config file wouldn't be doing it by hand, they'd already have that data in some other source that you could pull or push from directly.

I can imagine a case where we have the domains stored somewhere such as a DB and there we also maintain a list of paths to services elsewhere and then we build the routes based on those. I guess we could equally pre-build a final route config in some store based on those sources as and when they change.

We think the scenario for the customer is better handled by programmatic route generation.
Moving to backlog as something to reconsider post v1.

Nevermind, multiple hosts per route is already a first class concept in aspnetcore routing.
https://github.com/dotnet/aspnetcore/blob/90511e60390b5aa74669d8b4f812a82a622a0feb/src/Http/Routing/src/HostAttribute.cs#L41
Bumping out of backlog for re-triage, this is worth supporting.


Update documentation for config

This PR sets up mkdocstrings for config documentation. I also added docstrings for all the parameters. Its a single page, so it's nicely ctrl-F-able 😅
See https://fwl-proteus.readthedocs.io/en/config-docs/config/ for how it looks.
I kept the old config page around too, because I still want to source it for validation in #200. I think it can be removed afterwards.
Closes #201

[x] Add some documentation for how to add a new config parameter.
[x] Adopt changes from #220 (Lbol -> lum_now)

@nichollsh Could you have a look at this? Feel free to push to this branch if you have any changes you want to make.

@stefsmeets I am happy with this now! Thanks for the quick work in getting this setup. I updated the docstrings to provide some more information and improve the formatting. I also added some reference data on a new page, since it's useful for knowing what values to set in the [star] section of the configuration file. I also uploaded a PDF with a table outlining the spectral file options.

Nice work @nichollsh ! Looks good to me, could you approve the PR so that it can be merged?


[Uniswap] Safe balances not fetching correctly on optimism

Description
There are some issues with the Uniswap safe app on this chain causing random 'cuts' when fetching the safe balances.
Steps to reproduce

On an optimism safe go to the Uniswap safe app.
Mock a swap without actually performing it (see attached video).

Expected result
No issues fetching safe balances.
Obtained result
Balances fail to be fetched consistently causing issues:
(left is safe-app & right one is via wallet connect safe app)
https://user-images.githubusercontent.com/92332710/196912266-8c17f25c-c460-4311-aaca-4a484acd521d.mp4
Error in console:

App was updated by the uniswap team and is working now 😄
We will re-add it to the list too.


Package dependencies and The inferred type of ... cannot be named without a reference to ...

TypeScript Version:  3.3.0-dev.20190119

Search Terms: inferred type, cannot be named, reference, package, dependency
This isn't really a traditional bug report. Mostly a PSA of some sort.
Code
The dependencies of interest are,

My project has a direct dependency to "A"
My project has a direct dependency to "B"
"A" has a direct dependency to "B"

Before updating,

My project has 1.0.0 of package "A" (older version)
My project has 2.51.1 of package "B" (older version)
1.0.0 of package "A" has 2.51.1 of package "B" (older version)

After updating package "A",

My project has 1.0.1 of package "A" (newer patch version, bug-fix, no .d.ts changes)
My project has 2.51.1 of package "B" (older version)
1.0.1 of package "A" has 2.51.2 of package "B" (newer patch version, bug-fix, no .d.ts changes)

There's a package version mismatch here.
My project has 2.51.1 of "B" but the package I updated has 2.51.2 of "B".

In the newer version of "A" and "B", no .d.ts files were added/removed/modified.

Expected
Before updating, the project compiled.
So, the rationale is that after updating a patch version, the project should still compile.
Actual
After updating, the project stopped compiling.
tsc crashed; out-of-memory exception.
VS Code gave me the error,

The inferred type of ... cannot be named without a reference to node_modules/A/node_modules/B

Workaround
The workaround is to just update "B" to 2.51.2 in my project. After doing so, everything compiles again.
It seems like package versions matter to TypeScript when it comes to transitive dependencies. Even if it's a patch version and no .d.ts files are added/removed/modified.
Related Issues: #29221

It'd be great to have a concrete way to repro the OOM exception

@RyanCavanaugh we are bumping into this issue in an Aurelia app we are building.
It has appeared after upgrade from TS 3.1.x (now on 3.4.5).
For us the problem is exposed with declaration:true when we yarn link different packages together for dev.
I've been trying to put together a repro for you and have got something although it's not perfect (problem is only visible via VS Code and I havent been able to determine the difference in the CLI build).
If you clone https://github.com/simonfox/repro-plugin-one and https://github.com/simonfox/repro-plugin-two and run yarn for both. And then in plugin-one run yarn link plugin-two. Then you will see the issue in src/features/feature-one/actions.ts (you may need to reload the VS Code window after linking).

Oh and probably importantly considering this seems to be exposed via symlinks, I am on Windows 10

Same here on Windows 10 x64 Pro.
I have created directory junction with D:\>mklink /j p D:\projects.
It works in D:\projects, but does fail in D:\p.

@simonfox you found any workaround?

@nthypes no sorry

Getting same error here 😩

Sorry, guys I never did create a minimal repro for this.
But if you are getting assignability errors, it may have to do with classes with private properties, or unique symbols, which are nominally typed.
I still need to go ahead and make a repro for the assignability thing but I'm on holiday at the moment =x
Not sure if I can repro the OOM anymore, though

solved with Module resolution:
{
  "compilerOptions": {
    "baseUrl": ".", // This must be specified if "paths" is.
    "paths": {
      "graphql-compose": ["node_modules/graphql-compose/"]
    },
   // ...
}

Happens when we have conflicting versions of a package installed. A temporary solution would be to remove the package mentioned from peer dependencies of the plugin giving the error.

Same bug TS 3.7.2. The APP uses some REACT stuff imported indirectly (APP has no direct REACT dependency) via intermediary LIB.
TypeScript complains some REACT interface passed indirectly through LIB cannot be named without a reference to LIB/node_modules/REACT.
Temporary  solution: set declaration: false in tsconfig.json.
P.S. Dependency structure
APP
  has dependency to LIB (npm link)
  does not has REACT dependency and does not uses REACT stuff directly, but
  imports some react stuff from LIB.

LIB in TS compiled to JS and D.TS
  has dependency to REACT (normal node_modules way)
  exposes some React stuff

Well, this is similar, though not related to package versions. Instead it seems to happen when actually referenced packages are located outside of the project folder.
Here's a repro for Typescript 3.7.5
https://github.com/jeffrson/pnmp_vs_yarn_typescript
It works for npm and yarn, but fails with pnpm and yarnv2. Disable creation of declarations "fixes" it somewhat, as well as appending the type:
export const test: Router
in index.ts.

Hello, I had the same issue!
As a POC, I created a repository dedicated to this issue, to show how it is happening!
Repository: https://github.com/nogueira7egend/ts-symlink-error/
Please check it and follow the instructions that are on README!
Best regards

I ran into the same issue after linking packages in a yarn workspace
in my case, I was referencing React and it was being picked up as a global type rather than as an import
i.e. import * as React from 'react'
changing the name so it doesn't refer to a global alias fixed my issue
i.e. import * as R from 'react'

I have the same issue on a pnpm workspace,
I have 2 type of React Apollo hooks exported :
first exported hook function whit react tsx format like below which is so fine without any errors :
import { useQuery } from "@apollo/react-hooks";
import {
  getCategoryUnits,
  getCategoryUnitsVariables,
  getCategoryUnits_getCategory,
  GQL_GET_CATEGORY_UNITS
} from "@satek/resolvers";
import ApolloClient from "apollo-client";
import React from "react";

interface ParsingProps {
  data: getCategoryUnits_getCategory;
}

interface ErrorProps {
  errMsg: string;
}

interface Components {
  error: React.FC<ErrorProps>;
  loading: React.FC<{ type: "DotsHide" | "DotsShake" | "Circle" }>;
  parsing: React.FC<ParsingProps>;
}

export function useCategoryCategoriesQuery<
  C extends Components,
  V extends getCategoryUnitsVariables
>(components: C, variables: V, client: ApolloClient<object>) {
  let Response: React.ReactElement | null = null;
  const Error = components.error;
  const Loading = components.loading;
  const Parsing = components.parsing;

  const { loading, error, data } = useQuery<
    getCategoryUnits,
    getCategoryUnitsVariables
  >(GQL_GET_CATEGORY_UNITS, {
    variables,
    client
  });
  if (loading) {
    Response = <Loading type="DotsHide" />;
  } else if (error) {
    Response = <Error errMsg={error.message} />;
  } else if (data) {
    Response = <Parsing data={data.getCategory} />;
  }
  return { Response };
}

and other hook function like below which just export data and throw this error The inferred type of 'useCreateCategoryMutate' cannot be named without a reference to '.pnpm/registry.npmjs.org/@apollo/react-hooks/3.1.3_0db28cdd7967d177805e183f143598ec/node_modules/@apollo/react-common'. This is likely not portable. A type annotation is necessary.ts(2742)
import { useMutation } from "@apollo/react-hooks";
import {
  createCategory,
  createCategoryVariables,
  getCategoriesVariables,
  GQL_CREATE_CATEGORY,
  GQL_GET_CATEGORIES
} from "@satek/resolvers";
import ApolloClient from "apollo-client";

export function useCreateCategoryMutate<V extends getCategoriesVariables>(
  variables: V,
  client: ApolloClient<object>
) {
  const [createCategoryMutate, result] = useMutation<
    createCategory,
    createCategoryVariables
  >(GQL_CREATE_CATEGORY, {
    client,
    update: (store, { data: createCategoryMutate }) => {
      if (createCategoryMutate!.createCategory.organization!.id) {
        variables.organizationId = createCategoryMutate!.createCategory.organization!.id;
      }
      const { getCategories }: any = store.readQuery({
        query: GQL_GET_CATEGORIES,
        variables
      });
      store.writeQuery({
        query: GQL_GET_CATEGORIES,
        variables,
        data: {
          getCategories: [
            createCategoryMutate!.createCategory,
            ...getCategories
          ]
        }
      });
    }
  });
  return {
    createCategoryMutate,
    result
  };
}

I had the same issue and i solved it by changing the name of some declaration file d.ts to the actual name of the component I am trying to add types too so in my case it was:
before: @types/styled.d.ts
after @types/styled-components.d.ts
where styled-components is the full npm package name
and the error is gone

I solved it by move project position to a clean folder which has no parent node_modules/. For example, if
npm install @textile/js-http-client
cd node_modules/@textile/js-http-client/
npm install
./node_modules/.bin/tsc

will get error:
src/modules/account.ts:53:3 - error TS2742: The inferred type of 'sync' cannot be named without a reference to '@textile/js-http-client/node_modules/web-streams-polyfill'. This is likely not portable. A type annotation is necessary.

53   sync(apply?: boolean, wait?: number) {

but if
mv node_modules/@textile/js-http-client/ ../
cd ../js-http-client/
npm install
./node_modules/.bin/tsc

everything is OK.

Got similar error in Lerna mono-repo with yarn workspace

Work-around was to disable aws-appsync package hoisting in my package.json
{
  "workspaces": {
    "nohoist": [
      "**/aws-appsync"
    ]
  }
}

Yep, just like everyone else is hinting, this problem happens when a dependency that is linked into the project (f.e. with npm link, or the yarn/pnpm/etc linking tools) contains the same dependency as the project does.
In this case, the dependency is not de-duped, and exists in two places: in the project's node_modules, and in node_module/linked-dependency/node_modules.
For some reason, VS Code (TypeScript?) is preferring the nested dependency, even if they have the same version number, and (for some reason) introducing this weird error.
One way that I get around the problem is, instead of linking a project (which is a difficult thing not to do if you are relying on workspace tools like yarn/npm), to put that dependency's ref/hash in the dependent's package.json, so that npm install will install the dependency from VCS (f.e. from a branch that has the work-in-progress changes). In this case, there's no error, as NPM will successfully de-dupe the duplicate dependencies.
I haven't observed if this issue happens with duplicate dependencies in non-linked projects (f.e. which could happen if the duplicate dependencies have incompatible versions and can not be de-duped).

Same issue here. With Typescript 4.1.5.
I wonder why ist this still open, since it's created on February 2019 :D

There are workarounds for this, though none of which I have liked. In my case, importing the package whose type was used and is considered "private" gets around this.
For example, if you had defined a type in package X called ExampleA that referenced type ExampleB in package Y, and it complained that it references private type ExampleB from node_modules/Y, you can do
import "Y";

This will, however, not work if you use that package only as a dev dependency.
A workaround would be to use import type but that does not allow side-effect imports  (e.g. import type "Y" is not valid)
You could import the type that causes the issue, such as
import type { ExampleB } from "Y";

Again though, none of these are that pretty. I hope that a better solution can be proposed here because it makes more advanced types absolutely worthless or introduces ugly code with necessary comments pointing to this issue :disappointed:

In our case we used yarn workspaces and there were two packages with same dependency.
difference was that in one case package had dependency with version ^1.2.3 and second had "*"
and that * got added when version less than ^1.2.3 existed
I'm not able to replicate exact steps here but eventually yarn was installing version that's below ^1.2.3 and this error helped to catch the issue.

Got also a similiar error at a lerna monorepo, using only npm (no yarn workspaces).
The actual issue was that i've had @types/react installed only in one package, but used the typings in multiple packages, thus with lerna hoist it only was existing in /packages/node_modules/packageB and not in /node_modules.
After adding it to the other depending packages, e.g. in devDependencies and as optional peer-dependency, the error was solved.
Example of the additions in e.g. packageA:
{
    "devDependencies": {
        "@types/react": "^16.8.6 || ^17.0.0"
    },
    "dependencies": {
    },
    "peerDependencies": {
        "@types/react": "^16.8.6 || ^17.0.0"
    },
    "peerDependenciesMeta": {
        "@types/react": {
            "optional": true
        }
    },
    "publishConfig": {
        "access": "public"
    }
}

I also have a problem like this inside a monorepo, and just reinstalling the deps with yarn solves it. It's happened a few times. Don't know it could be something to do with the yarn.lock file getting out of sync after merging branches or something. The regenerated lock filed always shows a diff around the package referenced in the TS error.
Don't really understand what's going on but hope that helps someone.

I got similar issue in a yarn workspace package project that: ... cannot be named without a reference to 'react-bootstrap/node_modules/@types/react'.
Solved by moving "@types/react": "*" from peerDependencies section to devDependencies in package.json

I restarted the damn IDE and it disappeared :/

Try with:
{
  "compilerOptions": {
    "preserveSymlinks": true
  }
}

Credits to @imcuttle
https://github.com/microsoft/TypeScript/issues/42873#issuecomment-1007540868

"preserveSymlinks": true doesn't resolve all errors that I have. I also use pnpm and typescript together. Previously I used yarn and typescript and everything was fine.
Now, I have The inferred type of 'configSchema' cannot be named without a reference to '@pnpm-test/core-config/node_modules/yup/lib/string'. This is likely not portable. A type annotation is necessary. and have no idea how to resolve that.
I also set declaration: false for testing purposes but had no luck having it working.

Try with:
{
  "compilerOptions": {
    "preserveSymlinks": true
  }
}

Credits to @imcuttle #42873 (comment)

It does work for me. thanks so much.

Try with:
{
  "compilerOptions": {
    "preserveSymlinks": true
  }
}

Credits to @imcuttle #42873 (comment)

It does work for link errors using pnpm. thank you very much.

Not work, caused more types errors.

The "preserveSymlinks": true fix this but break others.
With it turned on, TypeScript cannot resolve transient types.
e.g. @types/react-router-dom uses react-router. But TS cannot resolve it as react-router is not add as a direct dependency, so it resides in <rootDir>/node_modules/.pnpm/....

Closing this for clarity since I'd prefer new issues to misconfiguration questions and banal observations of issue age.
To recap, you get this error when the declaration emitter can't synthesize a legal-looking import path for a file it needs create an explicit import for in order to name a type that was indirectly referenced. It's another way of saying "You can't get there from here".
The declaration emitter is not 100% perfect and it may be possible for a human to write a path that actually is legal in these situations.
If you get this error, generally the best thing to do is to write an import in the erroring file to the module that the declaration emitter is trying to reference. If you can't do this because there's no legal way to do it in your program, then, well, there's your problem -- you're asking tsc to do something impossible.
If you can write an import path that works, generally speaking this is considered a TS bug, though in some cases the module paths are so edge-case that we're not willing to generate them by default. You can log a (minimal) bug outlining the file path that should have been generated but wasn't, and we can take a look.
Happy coding!


fix bug when logging failed e2e stories

Proposed changes:

Fix error when logging failed end-2-end stories during e2e evaluation

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

Thanks for raising this issue, we'll give it a review as soon as possible


Inverted flame graphs

Is there an existing proposal for this?

[X] I have searched the existing proposals

Is your feature request related to a problem?
The Fil profiler has the ability to generate inverted flame graphs. In a normal flame graph, the roots are thread entry points, the children of any given node are the functions called by that node, and the leaf nodes are functions that allocated memory but did not call any functions that allocated memory. This can result in duplicated leaf nodes, if there are multiple call stacks that lead to a particular function that performs allocations. In an inverted flame graph, the roots are the functions that allocated memory, and the children of any given node represent the percentage of any of that node's allocations that can be attributed to a particular caller.
As Fil's documentation describes it:

The second graph shows the reverse callgraph, from f() upwards.
Why is the second graph useful? If f() is called from multiple places, in the first graph it will show up multiple times, at the bottom.
In the second reversed graph all calls to f() will be merged together.

Describe the solution you'd like
We should implement this idea, as it can sometimes be very helpful in analyzing where memory is being spent in aggregate.
Alternatives you considered
No response

@ivonastojanovic is taking this with #439. Could you please comment on this issue Ivona so that I can assign it to you?

Hey, a comment :)


Trying to use both the Norwegian and Danish app at the same time causes one to not function

I am Norwegian, but I am studying in Denmark. Trying to have both Smittestopp apps active at the same time causes one to say it's not activated.
Steps to reproduce:

Download both the Norwegian and Danish Smittestopp apps
Activate both

One of them should now say that it's not active

Hi I just tried to reproduce this on my own phone. When the Danish is active the Norwegian one is put to inactive, this after a warning telling that you can only have on exposure notification warning at the time, so you have to choose whether the Norwegian or the Danish one is set to active. In this case I set the Danish to active and then the Norwegian one was set to inactive. Do you not get the warning telling you can only have one app to notify you at the time? And in that warning the possibility to switch between the Norwegian and the Danish app?

Hi I just tried to reproduce this on my own phone. When the Danish is active the Norwegian one is put to inactive, this after a warning telling that you can only have on exposure notification warning at the time, so you have to choose whether the Norwegian or the Danish one is set to active. In this case I set the Danish to active and then the Norwegian one was set to inactive. Do you not get the warning telling you can only have one app to notify you at the time? And in that warning the possibility to switch between the Norwegian and the Danish app?

Hello @AlfHou,
Thank you for your issue! However, this is not something that we developers have control over. Both on iOS and Android only one app can be active at time. This is a restriction set by Apple and Google.

Hello @AlfHou,
Thank you for your issue! However, this is not something that we developers have control over. Both on iOS and Android only one app can be active at time. This is a restriction set by Apple and Google.

@pavshr that's what I feared. I think this is a big drawback in the solution, but I totally understand that you can't do anything about it.
@CUSL78 I can see the warning, however I don't think I found a easy solution to switch which app to use, other than uninstalling the Norwegian one and installing it againg later.

@pavshr that's what I feared. I think this is a big drawback in the solution, but I totally understand that you can't do anything about it.
@CUSL78 I can see the warning, however I don't think I found a easy solution to switch which app to use, other than uninstalling the Norwegian one and installing it againg later.

@AlfHou
You can keep the Norwegian app and have it as inactive. In this case when you make it active again and when it will perform next pull from server, it will catch up all of the keys for the days it has been inactive (up to two weeks in the past). If you delete it, and then install again after some time, your next pull will be done only for the day when the app was installed.

@AlfHou
You can keep the Norwegian app and have it as inactive. In this case when you make it active again and when it will perform next pull from server, it will catch up all of the keys for the days it has been inactive (up to two weeks in the past). If you delete it, and then install again after some time, your next pull will be done only for the day when the app was installed.


Interested in a new version of a logo?

Saw the current one. I was charmed. Made a vector version. Here is a PNG of it. Let me know if you want the SVG for your project.

Thought I would say thank you for crediting me on the project page. Much appreciation.

You're welcome :)


[Snyk] Upgrade puppeteer from 20.8.3 to 20.9.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade puppeteer from 20.8.3 to 20.9.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 2 days ago, on 2023-07-20.

Release notes

Package name: puppeteer

20.9.0 - 2023-07-2020.9.0 (2023-07-20)
Miscellaneous Chores

puppeteer: Synchronize puppeteer versions

Dependencies

The following workspace dependencies were updated

dependencies

puppeteer-core bumped from 20.8.3 to 20.9.0
@ puppeteer/browsers bumped from 1.4.5 to 1.4.6

20.8.3 - 2023-07-1820.8.3 (2023-07-18)
Miscellaneous Chores

puppeteer: Synchronize puppeteer versions

Dependencies

The following workspace dependencies were updated

dependencies

puppeteer-core bumped from 20.8.2 to 20.8.3

    from puppeteer GitHub release notes

Commit messages

Package name: puppeteer

03adf41 chore: release main (#10577)
25e3371 chore: implement isIncognito (#10595)
6c9306a feat: add autofill support (#10565)
c14f9b6 chore: implement typed Locators, expects, and internal contexts (#10573)
dcc08aa chore(deps): Bump word-wrap from 1.2.3 to 1.2.4 (#10590)
bf6304e fix: restore proxy-agent (#10569)
54c6ff2 docs: clarify the path attribute of InstalledBrowser (#10588)
830f926 feat: roll to Chrome 115.0.5790.98 (r1148114) (#10584)
caa81c0 chore(ng-schematics): remove experimental suffix for Node (#10585)
c7f3fb2 test: enable addScriptTag tests (#10583)
d71836e test: remove obsolete expectations (#10581)
3b4ff2a test: enable waitForXPath tests (#10580)
b032b62 test: skip headful tests in headless modes (#10578)
b03d7bb chore: update test command (#10576)
88439f9 fix: update the target to ES2022 (#10574)
a419abf test: unskip style tag tests (#10572)
1f08c54 chore(deps): Bump actions/setup-node from 3.6.0 to 3.7.0 (#10559)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

coverage: 99.245%. remained the same when pulling dde93bcd8818c41753fd226623729d253eb57a7a on snyk-upgrade-5dc88f4cad68c9c88b8ebd47e5496ca2 into f776f077c23f6be470634a84f369c898c7f2169b on master.

updated in 2.6.0


Generic path handling for CLI

In my first attempt to use the py2puml CLI, I encountered an import problem similar to #21. When I tried to use a relative path for the path argument, the fix from #40 didn't help because the source directory was not in the current directory.
I wrote a small patch for cli.py that fixed the problem for me:
--- a/py2puml/cli.py
+++ b/py2puml/cli.py
@@ -9,11 +9,6 @@ from py2puml.py2puml import py2puml

 def run():
-    # adds the current working directory to the system path so that py2puml can import them
-    current_working_directory = str(Path.cwd().resolve())
-    if current_working_directory not in path:
-        path.append(current_working_directory)
-
     argparser = ArgumentParser(description='Generate PlantUML class diagrams to document your Python application.')

     argparser.add_argument('-v', '--version', action='version', version='py2puml 0.7.2')
@@ -21,4 +16,10 @@ def run():
     argparser.add_argument('module', metavar='module', type=str, help='the module name of the domain', default=None)

     args = argparser.parse_args()
+
+    # add the directory containing the package to the system path so that py2puml can import it
+    directory = str(Path(args.path).parent.resolve())
+    if directory not in path:
+        path.append(directory)
+
     print(''.join(py2puml(args.path, args.module)))

Obviously I'm not aware of all the use cases, but I wonder if the CLI argument list could be simplified: If the order of arguments was changed, may be the path argument might not be required if the package was installed or the source directory (with the package's name) was contained in the current directory. If the current directory happened to be a project directory (i.e. contains setup.py or equivalent), may be the project could be the default and no argument would be required at all.

hi @mforkel, thank you for reporting your difficulties to use py2puml in an unusual way. Your issue is a little bit similar to https://github.com/lucsorel/py2puml/issues/29.
Like many other code quality tools, py2puml is meant to be used within the "usual" structure of a Python project (see https://docs.python-guide.org/writing/structure/#sample-repository and the discussion in another issue: https://github.com/lucsorel/py2puml/issues/29), which is in the root folder of the project (that you version in git), sibling to the folder containing the production code (this is the name of the root package of your Python digital service or library), sibling to the the tests/ folder containing the automated tests.
The fix you suggested would break more usual cases so I won't include it. If you can, refactor the structure of your project to match the one advised by the official Python documentation. Your other suggestions (changing the order of parameters, potentially removing one when they are redundant) are interesting, so I will link them from the original issue and mark this one as a duplicate. I am sorry, I don't have free time to implement it for now (not enough free time); but contributions are welcome.
Duplicate of https://github.com/lucsorel/py2puml/issues/29.

Hi @lucsorel, thanks for your reply. Obviously, its your decision whether you include my patch or not. Nevertheless, there are two remarks I'd like to make.
I'm not sure my project structure is that unsual. Some projects use the flat layout, other use the src layout (see https://packaging.python.org/en/latest/discussions/src-layout-vs-flat-layout/). I prefer the src layout because of its advantages for editable installs. And if you search for this topic, it seems I'm not the only one who uses that layout. It seems to be an ongoing debate.
Right now, py2puml's CLI is geared towards the flat layout and does not support the src layout. To run it from the root directory of my project (the directory containing setup.py) I created the patch. As far as I can tell, the patched CLI behaves just like before in a flat layout. But I might be missing something here. So may be you could explain a little what you mean by "the fix you suggested would break more usual cases"?

I agree that there are other project layouts.
The issue with the suggested patch is that it breaks the usage on other project layouts (7 unit tests break). As I said beforehand, there is another way of handling this case mentioned in #29 but it is not on the roadmap for now (freetime available and project priority) :smiley:

it breaks the usage on other project layouts (7 unit tests break).

I'm sorry to hear that. And a little surprised. Because I ran the tests in a clone of your repository before I submitted the patch and I ran them again today (without pulling inbetween). On both occasions, all tests passed. Could you may be give me an example of a test that failed and quote the error, so I can determine what might be the trouble with my setup? Thanks in advance!

my bad, adding the following block before parsing the arguments breaks some tests, but adding them after the arguments parsing does not:
    # add the directory containing the package to the system path so that py2puml can import it
    directory = str(Path(args.path).parent.resolve())
    if directory not in path:
        path.append(directory)

I agree that the patch does the trick for some project setups, but it just does not make sense to me to pass a filepath to the CLI and to ask the CLI to include its parent path to the system imports. Why not the parent's parent's one?
It would be more explicit to support py2puml . . to scan the current directory, or to support calls like py2puml this-module.py; but I lack time for that.


Bump WASI version to 0.2.1

This PR updates the WASI version to 0.2.1 and also updates the associated tool wit-bindgen to support parsing the new syntax.

The cargo fmt check fails after this PR (https://github.com/bytecodealliance/wit-bindgen/pull/971) because we no longer use rustfmt to format the generated code, so I removed the corresponding CI.


Add --passes all to generate all test-suites

This will avoid us having to change the CI file everytime we want to add new passes to the project

We should instead rename the --passes argument to --pass to only allow one testsuite at a time to be generated. No one runs this tool without going through the automation anyway


feat: XSB discover launch hot cleanup

:tada: This PR is included in version 1.4.0-dev.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add notice to clear-pr-merge-commit-message

Replaces and closes https://github.com/refined-github/refined-github/pull/5967
Part of https://github.com/refined-github/refined-github/issues/5155

This is the minimum we can do to make the feature louder since it overrides the user’s settings.
Test URLs
This PR
Screenshot

cc @yakov116 @JelteF @karfau

Good (better now then never 😀)


Authority should be in uri format - Error when testing ProvisionUserToCRM

When testing the logic app function ProvisionUserToCRM, the following exception is thrown:
"System.ArgumentException: 'authority' should be in Uri format\r\nParameter name: authority\r\n   at Microsoft.IdentityModel.Clients.ActiveDirectory.Authenticator.DetectAuthorityType(String authority)\r\n   at Microsoft.IdentityModel.Clients.ActiveDirectory.Authenticator..ctor(String authority, Boolean validateAuthority)\r\n   at Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext..ctor(String authority)\r\n   at Submission#0.d__2.MoveNext() in D:\home\site\wwwroot\ProvisionUserToCRM\run.csx:line 131\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Submission#0.d__1.MoveNext() in D:\home\site\wwwroot\ProvisionUserToCRM\run.csx:line 57"

Issue resolved. Tip: double check the configuration values for your logic app methods.


Batch detrend

Request: Add detrending to the Batch Edit tool.
Rationale: It's very common to dump in a whole bunch of measurements taken with the same tool/conditions and therefore, the detrend will be the same for all.
<Sorry if I've submitted this request before --- I searched but couldn't find it.>

This is already possible. (Indeed has been possible since the very beginning.)


Token is Passed in Header?

Am I reading your plugin correctly that the token is being based in the Header rather than as a query param?

Nevermind, apparently I'm mildly brain damaged. I see that the Header should work. Just not sure what I'm doing wrong elsewhere.


Installer - API & Types Definition Update 5/5 (Feedback)

Technical Story
As a PANIC UI developer, I want to have proper “types” (TS interfaces, classes and types) and API calls (made to the real endpoints), so I can understand the code better and finish off each step in the installer.
Description
We tackled the work in the new installer in a very asynchronous way, meaning that when we were implementing parts of the frontend we didn't have real endpoints & types available to be consumed, and basically we had to mock logic (types, API calls, etc.) as necessary to get the ticket requirements done.
Now we have our types (TS interfaces, classes and types) ready to be consumed across the UI logic, so we need to go end-to-end in the installer code and update the props/vars/consts/params/etc to use the proper type's definition located at panic/entities/ts. This ticket covers the Feedback step only.

types: check panic/entities/ts folder
API: check the swagger.json file under panic/api/src

If you spot anything "off" in the data types and/or API, please make a note and raise your concern asap, so we discuss and fix it accordingly.
Requirements

Ticket scope: Feedback step only
Update all type definitions for entities to use the equivalent present at panic/entities/ts
Update all API calls as necessary
Everything related to code being updated/amended must be hard-tested, to ensure that the functionality remains stable. Any issue/bug must be resolved before merging this ticket.
Remove deprecated code as required.

Type update example

Acceptance criteria
Checking PANIC UI source code
Given: The PANIC developer checks the source code for the installer
When: The code is shown
Then: The developer can verify that all types definitions are using the ones present at panic/entities/ts and all API calls are being made to the real endpoints

Waiting API real data to test

The scope of this ticket covers the page both during installation and when updating configurations.

Some notes:

Retrieve config on componentWillLoad by passing config ID as prop

This is blocked for the time being as we need to wait until or previous steps are done.

Restarting this ticket from scratch as there were a lot of changes in the code-base since the last time I was working on it.


internal/gitrepo: extract git functions from pkg/project

The goal is to move logic back from "pkg/project" to the "internal/*" packages and expose in "pkg/project" back only necessary public functions.

@sourishkrout please let me know if any of the moved public functions are used by other packages and should be still exposed.


Deleting top-level keys

Hi!
Is it possible to delete top-level keys (i.e. from a bucket)?
If so, this doesn't seem to be exported through any of the APIs (Java/TypeScript).

My understanding is that a key is neither created nor deleted.  Initially it has the “bottom “ value for its data type.  Resetting it to “bottom “ is the closest you get to “delete “.  This is by design :-)
                    Marc

Le 28 févr. 2018 à 14:55, João Neto<EMAIL_ADDRESS>a écrit :
Hi!
Is it possible to delete top-level keys (i.e. from a bucket)?
If so, this doesn't seem to be exported through any of the APIs (Java/TypeScript).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

There has been some discussion of whether it would be interesting to
support delete or not -- I am in favor of supporting it :-)
Could you share with us the use case where it would be interesting to have
delete.
Thanks,
Nuno
On Wed, Feb 28, 2018 at 7:58 PM, Marc Shapiro<EMAIL_ADDRESS>wrote:

My understanding is that a key is neither created nor deleted. Initially
it has the “bottom “ value for its data type. Resetting it to “bottom “ is
the closest you get to “delete “. This is by design :-)
Marc

Le 28 févr. 2018 à 14:55, João Neto<EMAIL_ADDRESS>a écrit :
Hi!
Is it possible to delete top-level keys (i.e. from a bucket)?
If so, this doesn't seem to be exported through any of the APIs
(Java/TypeScript).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SyncFree/antidote/issues/325#issuecomment-369344981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJZR8vywTVD4AjCM4F4FMp430ZRLgfXGks5tZaG4gaJpZM4SWsIn
.

Hi Marc & Nuno! Thanks! :)
I guess Roger asked about the possibility (https://github.com/LightKone/antidote-rest-server/issues/11); probably without any specific use-case in mind (more in terms of testing).
My understanding is that the reset operation will only revert the value of the object back to its zero-value, but won't change the type of the object (i.e. the beatles key which represents the set of members of the band cannot be changed later into representing a counter of how many beatles we find in our music store).
A few questions:

Why are the semantics for keys in a bucket different from keys in a map?
What are the limitations in providing a setKeyType(CRDT_TYPE) sort of operation? Probably due to nasty effects when having concurrent operations (e.g. counter.increment() || set.add("ringo")?

What if instead of mapping (key)-->(object) we map (key, crdtType)-->(object)?

This allows multiple CRDT object types per key
Operations on different CRDTs won't conflict (as they are applied to different objects)

I mean, it's just a suggestion. One that probably makes Antidote more complex without any real use-case backing it.
Was just wondering if my thinking was OK, or there's something I'm not considering.

Hey,
the semantics of keys in buckets and maps are mainly different because the map has been designed much later and with more insight. I agree that we should try to align the semantics of both 👍
Personally, I am not in favour of offering a "delete" operation where the semantics differ from a reset. I think it would mess up the semantics of concurrent modification and deletion.
We should discuss whether a key is always mapped to a specific type (in which case your setKeyType(...) operation would be very useful), or if we can have the same key with different type (which has the better concurrency semantics, but might be confusing for the programmer?).
We have discussed both in the past, but didn't come to a conclusion.


Is it possible to intercept requests for mocking a fake back end?

I'm trying to use addFullRequestInterceptor to intercept the requests as is mentioned here https://github.com/2muchcoffeecom/ngx-restangular/issues/95 however all it seems to be able to do is just modify the request headers and then send it out anyway.
There doesn't seem to be a way to actually block the real request and replace the body with mock data.
The docs for addFullRequestInterceptor seem fairly light - https://github.com/2muchcoffeecom/ngx-restangular#addfullrequestinterceptor
addResponseInterceptor is no good also, as its doesn't happen until after the actual response from the server.
Any ideas?

+1

Hi!
There is no such ability in Restangular, but you can use Angular way to fake requests. Angular HttpBackend is used inside Restangular.


Fixed width for BlockCounter

Without this, BlockCounter is continuously changing width
unnecessarily. With a fixed width BlockCounter, visual output doesn't
change more than strictly necessary. At current window min size, this
width fits up to 9 digits, which is enough to fit all of main, test
and signature networks.
You can spot the difference these changes add by creating two dummy
data directories and bootstrapping one with this change and
bootstrapping the other one without this change.

Blocks counter label is anchored to window height,
not to blocks counter height. Set draft.

This is a dummy component just to show how to bind to the current block height. Not actually something that was designed and eventually it will be removed. I'd say there is no point in this change.

Yes. From https://github.com/bitcoin-core/gui-qml/pull/31#issue-982034917:

adds a prototype of QML object which displays block tip height

@katesalazar
If you are interested in QML app, you could also look into https://github.com/BitcoinDesign/Bitcoin-Core-App


feat: add congrats page

Summary by Sourcery
Add a 'Congrats' page to the dashboard that is shown when users complete all questions, and update the navigation logic to redirect to this page when appropriate.
New Features:

Introduce a new 'Congrats' page that is displayed when a user has answered all questions.

Enhancements:

Update navigation logic to redirect users to the 'Congrats' page when there are no more questions to answer.


VssConnection behind firewall / proxy

Is it possible to have an example on how to use a VssConnection object behind a proxy?
Considering this sample (.NET Core 2.1.X):
VssCredentials credentials = new VssBasicCredential("", "<pat>");
VssConnection connection = new VssConnection(new Uri("https://dev.azure.com/<organization>"), credentials);
ProjectHttpClient client = connection.GetClient<ProjectHttpClient>();
var project = await client.GetProject("<project>");

works fine anywhere except behind a (corporate) proxy where I get the following error:

I tried to play with WebRequest.Proxy and VssHttpMessageHandler.DefaultWebProxy without any success. The lack of documentation on these libraries is a serious pain the neck!

Anyone? Thanks.

The easiest way to have these libraries use a web proxy is to add this sections to your web/app config file in the configuration section:
<system.net>

</system.net>

Below code should resolve your issue.
VssHttpMessageHandler.DefaultWebProxy = new WebProxy(new Uri("[Your proxy URL]:[Port]"), true, new string[] { "[Your Devops URL]" }, CredentialCache.DefaultCredentials);
var handler = new VssHttpMessageHandler(new VssBasicCredential(string.Empty, config[Constants.VstsPat]),
new VssClientHttpRequestSettings() { BypassProxyOnLocal = true, SuppressFedAuthRedirects = true, AllowAutoRedirect = true }
);
var connection = new VssConnection(accountUri, handler, null);

@mjwoodsphx, thanks for the suggestion but the XML "app.config" approach didn't work in a .NET Core console app.
@subbu152, I was missing the VssClientHttpRequestSettings part when I played with VssHttpMessageHandler.DefaultWebProxy. It now works like a charm. Thanks a lot!

@mjwoodsphx, thanks for the suggestion but the XML "app.config" approach didn't work in a .NET Core console app.
@subbu152, I was missing the VssClientHttpRequestSettings part when I played with VssHttpMessageHandler.DefaultWebProxy. It now works like a charm. Thanks a lot!

You are welcome. Glad to know it worked for you. 👍

@subbu152 i am trying to connect using https://proxy.server.com:8989 and i am getting https scheme does not supported by .net. if i use http: then also it is not working can you help me on this. I am using .net framework
Please help


nix utilities not passing command line arguments to derivations that use lib.setFunctionArgs

Problem
nix-shell and nix-build seem to ignore function arguments set with lib.setFunctionArgs, so they do not provide command line arguments to derivations defined using the function. If those utilities were to respect lib.setFunctionArgs,  I could write an enhanced callPackage which would automatically provide both command line and calling site overrides.
To Reproduce
I have listed a simple nix expression labeled "repl.nix", below. It contains six derivations I use to call an underlying package function, my-pkg-f. Here, my-pkg-f, represents a package and the 6 other my-pkg- derivations represent ways they might be included into <nixpkgs>.
The package has a shellHook that echos its input attribute, "name", and it also installs a script which does the same. I show the result of trying to override the "name" attribute through command line calls to nix-shell. Both the shellHook and nix-build installed script behave the same, but I only list calls to nix-shell here.
Calls to the first two derivations, my-pkg-0 and my-pkg-1, show the baseline of callPackages. my-pkg-0 uses the default name defined by my-pkg-f, and my-pkg-1 uses the callPackage extra argument option passed to it. Neither override arguments, because neither of them are actually functions.
> nix-shell --argstr name "cmd-arg" -A my-pkg-0 ./repl.nix
hello my-pkg-f
> nix-shell --argstr name "cmd-arg" -A my-pkg-1 ./repl.nix
hello my-pkg-1

The command for my-pkg-2 shows that I am able to override "name" when the expression is a function that explicitly gives a default.
> nix-shell --argstr name "cmd-arg" -A my-pkg-2 ./repl.nix
hello cmd-arg

Finally, the call to my-pkg-3 shows that the argument must be explicitly mentioned--defining a function with {...} does not catch the command line argument.
> nix-shell --argstr name "cmd-arg" -A my-pkg-3 ./repl.nix
hello my-pkg-f

Its not nice to have to explicitly re-name function arguments at the callPackages call site when I want the arguments to be modifiable on the command line. So for callPackages-2 I re-wrote callPackages so that instead it creates a function with all arguments listed by lib.setFunctionArgs. Having done that, I would expect the following two shell calls to result in hello cmd-arg. However, they don't:
> nix-shell --argstr name "cmd-arg" -A my-pkg-2-0 ./repl.nix
hello my-pkg-f
> nix-shell --argstr name "cmd-arg" -A my-pkg-2-1 ./repl.nix
hello my-pkg-1

repl.nix:
let pkgs = (import <nixpkgs>) {};
in  with builtins;
rec {
  inherit (pkgs) callPackage lib makeOverridable;
  my-pkg-0 = callPackage my-pkg-f {};
  my-pkg-1 = callPackage my-pkg-f { name = "my-pkg-1" ;};
  my-pkg-2 = s@{name ? "my-pkg-2"} : callPackage my-pkg-f  s;
  my-pkg-3 =<EMAIL_ADDRESS>: callPackage my-pkg-f  s;

  my-pkg-2-0 = callPackage-2 my-pkg-f {};
  my-pkg-2-1 = callPackage-2 my-pkg-f { name = "my-pkg-1" ;};

  my-pkg-f = { name ? "my-pkg-f", writeScriptBin, symlinkJoin}:
    symlinkJoin rec{
      inherit name;
      paths = [hello-pkg];
      hello-pkg = writeScriptBin "runHelloPkg.sh" say-hello;
      shellHook = say-hello;
      say-hello = ''echo hello ${name}'';
      };

  callPackage-2 = fn : over :
    let f = if lib.isFunction fn then fn else import fn;
        f' =<EMAIL_ADDRESS>: makeOverridable f (auto//over//args);
        arg-def =  lib.functionArgs f
                // lib.mapAttrs (_: _: true) (auto//over);
        auto = intersectAttrs (lib.functionArgs f) pkgs;
    in lib.setFunctionArgs f' arg-def ;
}

Additional context
Entering nix repl ./repl.nix shows the difference that I believe is the cause of my woes. I suspect the utilities check if my-pkg-2-0 is a function by using the builtins version.
nix-repl> lib.functionArgs my-pkg-2-0
{ name = true; symlinkJoin = true; writeScriptBin = true; }

nix-repl> builtins.functionArgs my-pkg-2-0
error: 'functionArgs' requires a function, at (string):1:1

Metadata
> nix run nixpkgs.nix-info -c nix-info -m
[1 copied, 0.0 MiB DL]
 - system: `"x86_64-linux"`
 - host os: `Linux 4.15.0-66-generic, Ubuntu, 18.04.3 LTS (Bionic Beaver)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.2.2`
 - channels(tcook): `""`
 - channels(root): `"nixpkgs-20.03pre201329.f1682a7f126, nsrlpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

@trevorcook Note that lib.setFunctionArgs is a nixpkgs abstraction, and not something that is built-in into Nix. So it is kinda expected that nix-build CLI doesn't understand it.
It can only understand builtins.* and __functor stuff (with caveats).
But there is another issue. builtins.functionArgs and lib.functionArgs are not the same. I'd even say, it is unfortunate name clash. See below:
   # let's define a function...
nix-repl> f = { arg1 }: arg1

   # .. and some attrset we'll use as an argument to that function
nix-repl> args = { arg1 = "hello"; }

   # also, let's create a functor from that stuff, for further experiments
nix-repl> f2 = lib.setFunctionArgs f args

   # now we can state a law: f x = f2 x where x is polymorphic to { arg1 }
nix-repl> f { arg1 = "hello world"; }
"hello world"
nix-repl> f2 { arg1 = "hello world"; }
"hello world"

   # but at same time, builtins.functionArgs f   !=  builtins.functionArgs f2
   # even more, lib.functionArgs f   !=  lib.functionArgs f2
nix-repl> lib.functionArgs f
{ arg1 = false; }

nix-repl> lib.functionArgs f2
{ arg1 = "hello"; }


Flipper doesn't clear previous views when used inside a recyclerView

I've implemented FlipperLayout in part of a layout of items presented in a recyclerView. My problem is that the flipper shows images of other items. I've tried using removeAllViewsInLayout() when binding, and before adding the new views, but now the flipper just remains empty. I've also tried to use clearDisappearingChildren() which didnt help either. Any tips on how to use inside a recyclerview?

@Tsabary I request you please update your library to our latest v1.6.0 by adding
implementation 'com.github.technolifestyle:AutoImageFlipper:1.6.0' in your app level build.gradle file. Post that you can refer to this section for your issue https://github.com/therealshabi/AutoImageFlipper#usage-with-the-recyclerview
If you have any other issues, please do tell me

Since there was no further activity on this issue, I've closed this.


Fix IDE0090: Simplify new expression part 5

src\Microsoft.PowerShell.CoreCLR.Eventing\
https://docs.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0090

Opened codefactor-io/codefactor#26 for spurious SA100 rule violations.


Initial module ordering cannot be configured.

As title says initial module ordering cannot be controlled, not effected by order at which they are added via initial construction.

2a2f00c3551b64dd2dd4cdd944748afb4c1754f6


fix(template): update devDependencies

I've used this template a few times and needed to manually move these dependencies over, so I thought I'd update the template for the next person.
All testing and TypeScript dependencies should be in devDependencies. I'm not too sure if any of the workbox dependencies can move over, so I figured I'd leave them as is.

Hello!
This follows the convention at https://github.com/facebook/create-react-app/blob/bb64e31a81eb12d688c14713dce812143688750a/packages/cra-template/template.json#L3-L8, which lists the packages in dependencies, not devDependencies.
If that canonical template is changed, I'm happy to have this switched over as well.

Hi Jeff,
I went on a bit of a deep-dive into the history of imports for CRA - didn't see all of the prior discussions regarding devDependencies and dependencies before. It seems like there are some conversations ongoing about certain dependencies, so I'll be interested to see how that progresses.
Closing this for now and will reopen if the template changes in the future, thanks for taking a look!


App depending on c++ DLLs works from command line, but not when installed as service

I have an application compiled as x64 that is dependent on some C++ DLLs (don't know if that detail's inconsequential or not!). When I run it from the command line it works as expected, but when installed as a service doesn't seem to do anything. There's logging in my ServiceControl to note when it starts and stops, but nothing is written when it's installed. The last thing that's logged is in Program.cs after the call to HostFactory.Run.
Also, if I install this as a service on my development machine it works.
Is there a way that I can debug this, e.g. tracing for Topshelf?

OK, this wasn't really my issue. I believe this is related to another issue. The application was running, but failing due to a DB schema mismatch. It wasn't logging anything and nothing was being inserted to the database so I couldn't see anything happening.


introduce Paint::scale(float sx, float sy);

not quite necessary.

keep this if it's necessary later.


nixos-unstable channel not updating

https://howoldis.herokuapp.com shows a channel, 10 days old.
http://hydra.nixos.org/job/nixos/trunk-combined/tested#tabs-constituents shows a successful build 3 days ago, which is http://hydra.nixos.org/build/56231260
(Sorry, I know too little about hydra to diagnose this further.)

Duplicates https://github.com/NixOS/nixpkgs/issues/27381

To be clear, I'm confident there is some other reasons why the channel doesn't update ATM, but Hydra's UI won't show why.


Fast Tractography Streamline Search

Title
Fast Tractography Streamline Search.

Hierarchical search using a space partitioning tree (binary search tree / KD-tree ).
Using an adapted distance measure (Entry-wise matrix distance).

Leaders
Etienne St-Onge ( estonge in mattermost)
Collaborators
No response
Brainhack Global 2021 Event
Brainhack Montreal
Project Description
Create a repository for a Fast tractography / streamline search method.
And develop useful scripts / methods.
Link to project repository/sources
https://github.com/StongeEtienne/tractography-search
Goals for Brainhack Global

Find an optimized space partitionning tree that can be adapted (Nanoflann).
Adapt distances adapted for tractography streamlines (L21 entry-wise).
Create, adapt and optimize the search function,  (C++, with python "binder").
Discuss & choose a Library architecture / structure.
Create usefull scripts to search streamlines within a tractogram.
Clustering algorithms using a sparse distance matrix.

Good first issues

issue one:  Discuss about the project (how can you help with this project or learn about tractography).
issue two:  Code or improve functions to search for similar streamlines.
issue three:  Create scripts and utlity functions.

Communication channels
https://mattermost.brainhack.org/brainhack/channels/tractography-search
Skills

Python : Any level (want to learn python for diffusion / tractography ?)
Python : Intermediate (want to do streamline clustering ?)
C++ : Intermediate (want to improve / optimize "core" functions)

Onboarding documentation
No response
What will participants learn?
How to interact with streamlines / tractography in python. (Dipy / ScilPy / Tractoflow)
Data to use
No response
Number of collaborators
3
Credit to collaborators
To define !
Image

Type
method_development
Development status
0_concept_no_content
Topic
connectome, diffusion, tractography
Tools
DIPY
Programming language
C++, Python
Modalities
DWI
Git skills
1_commit_push
Anything else?
No response
Things to do after the project is submitted and ready to review.

[ ] Add a comment below the main post of your issue saying: Hi @brainhackorg/project-monitors my project is ready!
[ ] Twitter-sized summary of your project pitch.

@StongeEtienne let me know if I should put this on the website by pinging @brainhackorg/project-monitors

@Remi-Gau
Feel free to do it, if you want or think it will be useful to others, (or to give more visibility)

OK will do.
One small suggestion: would be good to create actual issues on your repo to provide a "forum" to guide new comers and answer their questions.


HotFix: actions view error

HotFix: actions view error

Codecov Report

Merging #952 (cf8ed6f) into master (ebd3d1a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #952   +/-   ##
=======================================
  Coverage   57.14%   57.14%
=======================================
  Files           1        1
  Lines          70       70
  Branches       18       18
=======================================
  Hits           40       40
  Misses         30       30

Continue to review full report at Codecov.

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


0.12.1 docker image

Hey looking to update the LNBits app on Umbrel.
In the past you've had tagged images under either lnbitsdocker/lnbits or lnbitsdocker/lnbits-legend. This latest release seems to just sit under latest, and also looks like only 0.12.0 has been published not 0.12.1.
Happy to go forward with just the latest tag image, but just wanted to let you guys know in case you haven't realised.

hey, we are now using lnbits/lnbits. lnbitsdockeris deprecated and it was accidently pushed tolnbitsdocker/lnbits`

ah i see, thanks.
sure thing, this is my TG


Add Street Litter Detection Project & Dataset

Description

Added a Street Litter Detection project with images collected from Falkirk, Scotland, and Punalur, India.
Motivation and Context

This dataset and the code might help with future works on Street Litter Detection in Scotland. The project solves one of the ongoing research topic in Computer Vision: Object Detection

How Has This Been Tested?

The project was run locally after making the changes

The docker-container was used to run the project locally.

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thank you for your contribution! 🙂


How do you provision the first cluster where Das Schiff is running?

Hello!
Das Schiff is awesome project, there is a question though on how to setup the initial k8s cluster, where Das Schiff will be running. Do you simply use managed k8s (e.g. EKS)?

Hi,
that is also a CAPI-based cluster. We usually start with a KIND cluster somewhere (Bastion host, local laptop), crete the mgmt cluster and then pivot that over so the mgmt cluster controls itself

@MaxRink thanks a lot for the fast reply! -)


fix: Credential saved successfully message rendered off-screen

Signed-off-by: serenahacker<EMAIL_ADDRESS>

This issue closes #545


Reverse proxys not working for Netdata and Glances

(Are you asking for help with using Caddy? Please use our forum instead: https://caddy.community. If you are filing a bug report, please take a few minutes to carefully answer the following questions. If your issue is not a bug report, you do not need to use this template. Thanks!)
1. What version of Caddy are you using (caddy -version)?
Caddy 0.10.0
2. What are you trying to do?
iam trying to setup reverse proxy's for netdata and glances but currently in the latest version both netdata and glances will not load their UI's. even with the current rules setup caddy does not properly allow the proxys to work.
3. What is your entire Caddyfile?
netdata.domain.com {
    proxy / localhost:19999
}

 rewrite {
        if {>Referer} has /glances
        to /glances/{path}
    }

        # The code below gives you a tiny level of security requiring a username/password before Caddy will let you connect to it

        basicauth /glances Username Password

        proxy /glances <IP_ADDRESS>:61208 {                # https://github.com/nicolargo/glances
        without /glances
                transparent
        }

4.  Please paste any relevant HTTP request(s) here.
Moved Permanently.
Moved Permanently.
(paste curl command, or full HTTP request including headers and body, here)
curl chmuranet.io/glances
curl netdata.chmuranet.io
6. What did you expect to see?
ether an 200 ok response or at least some html
7. What did you see instead (give full error messages and/or log)?
Moved Permanently.
Moved Permanently.
Netdata: for the web interface all i see is the splash screen when netdata loads up.
Glances:  ether get 404 not found or no such file exists
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?

install the latest version of caddy.
ether install glances or netdata
then try creating an reverse proxy rule for your domain for ether netdata or glances.
Done

Hey, thanks for filling out the issue template. This is probably a duplicate of #1604 - if you think it is different, feel free to re-open this!
Fix should be going out next week sometime.

its mostly the same issue but i was seeing if their was an current workaround, but oh well it can wait for now i guess.


Feature Request: Ability to add additional comments when answering the question "Add the output to the chat? "

Issue
It would be nice to be able to add an additional prompt or comment when answering the question "Add the output to the chat? ", as often I have some preferences in how to solve an issue.
That's it.
Thanks!
Version and model info
All versions.

Thanks for trying aider and filing this issue.
You can always use control-c to interrupt the LLM if it's going down a wrong path and you need to give it more instructions.

Yes, but if the error message of the !python script.py command is
extensive, copying both the error/output and adding some comments can
involve a significant amount of scrolling with issues around keeping the
right text selected likely.
having a way to reply yes, and  would result in a nice
flow.
Let me know whether I should make a short recording of what i'm
encountering.
On Fri, 12 Jul 2024 at 11:13, paul-gauthier @.***>
wrote:

Thanks for trying aider and filing this issue.
You can always use control-c to interrupt the LLM if it's going down a
wrong path and you need to give it more instructions.
—
Reply to this email directly, view it on GitHub
https://github.com/paul-gauthier/aider/issues/815#issuecomment-2225161450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAX7BVZRHYUQEBSUD4FR3BDZL6M4NAVCNFSM6AAAAABKPWYZPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRVGE3DCNBVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Bjorn Heijligers
+31620106733

You can now specify additional instructions when answering that question.

Awesome! You rock.
I really appreciate the work you put in adding chat-modes, ipynb support
and benchmarking various results. Kudos to you
On Thu, 22 Aug 2024 at 19:10, paul-gauthier @.***>
wrote:

You can now specify additional instructions when answering that question.
—
Reply to this email directly, view it on GitHub
https://github.com/paul-gauthier/aider/issues/815#issuecomment-2305250734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAX7BV5FPNYHEEOXBBB3OWTZSYLQDAVCNFSM6AAAAABKPWYZPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBVGI2TANZTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Bjorn Heijligers
+31620106733


v<IP_ADDRESS>: relax bound on deepseq to the one shipped with GHC 8.0

The current lower bound deepseq >= 1.4.3 for v<IP_ADDRESS> is needlessly restrictive and excludes building with GHC 8.0 in some cases, e.g.: https://github.com/agda/agda/runs/5495421153?check_suite_focus=true
Agda-2.6.3$ cabal build -w ghc-8.0.2 -f +enable-cluster-counting
Resolving dependencies...
Error: cabal: Could not resolve dependencies:
...
[__1] trying: Agda:+enable-cluster-counting
[__2] trying: text-icu-<IP_ADDRESS> (dependency of Agda +enable-cluster-counting)
[__3] trying: template-haskell-<IP_ADDRESS>/installed-<IP_ADDRESS> (dependency of
Agda)
[__4] next goal: pretty (dependency of Agda)
[__4] rejecting: pretty-<IP_ADDRESS>/installed-<IP_ADDRESS> (conflict: text-icu =>
deepseq>=<IP_ADDRESS>, pretty => deepseq==<IP_ADDRESS>/installed-<IP_ADDRESS>)
[__4] rejecting: pretty-<IP_ADDRESS>, ..., pretty-<IP_ADDRESS> (conflict: template-haskell =>
pretty==<IP_ADDRESS>/installed-<IP_ADDRESS>)
[__4] fail (backjumping, conflict set: Agda, pretty, template-haskell, text-icu)

text-icu-<IP_ADDRESS> builds fine with deepseq-1.4.2 (shipped with GHC 8.0):
$ cabal install -w ghc-8.0.2 text-icu-<IP_ADDRESS> --constraint='deepseq==1.4.2.*' --allow-older=text-icu:deepseq
...
[38 of 38] Compiling Data.Text.ICU    ( Data/Text/ICU.hs, dist/build/Data/Text/ICU.o )
ld: warning: directory not found for option '-L/opt/homebrew/opt/icu4c/lib'
Installing library in ...

So the lower bound should be relaxed...

Tests won't build with deepseq-1.4.2 since it doesn't have NFData Ordering instance. But #34 could be merged if we really need GHC 8.0.

I made a revision of just the library deps, to allow deepseq >= 1.4.2: https://hackage.haskell.org/package/text-icu-<IP_ADDRESS>/revisions/
According to my experiments, it might also be sound for the test-suite, but I don't need the relaxation there.

Perhaps NFData Ordering instance is no longer necessary. I've relaxed lower bounds in
https://github.com/haskell/text-icu/commit/e972f7c94c6569857da95be24825eb7b89f0fab4 (accidentally linked it to #71 instead of #72).

Ok, I made the lower bound of the test-suite conform to that of the library---by removing the bound.  Published revision 2 on hackage.

Did the same in sources for future releases.


BeamNG.drive abysmal performance with DXVK enabled

I get stable 25-30 fps when running the game without DXVK. With DXVK enabled max fps triples (depends on map) but the game freezes and drop frames every second making it literally unplayable. I tried with some other wine version and the results were similar.
Software information
BeamNG.drive, 1980x1080 high preset
System information

GPU: GTX 1060 3GB
Driver: 440.44
Wine version: Proton 4.11 (Tested with several others same issue)
DXVK version: 1.5

Apitrace file(s)

Could not capture unfortunately..

Log files

d3d9.log: [Empty file]

d3d11.log:
BeamNG.drive.x64_d3d11.log

dxgi.log:
BeamNG.drive.x64_dxgi.log

Sorry I did not mentioned it earlier, I am Pop OS 19.10 with the the pre-installed proprietary nvidia drivers

I know others had this problem before and it's not a DXVK issue. No idea how to fix it though.

My specs are as follows:

CPU: Intel i5 7400
GPU: GTX 1060 3GB
RAM: 16GB 2400HZ Single Channel

I think this more than enough for this game to perform decent as it works fine in windows
Also this frametimes graph pretty much describes my problem....

Can you try lowering texture quality or something to reduce VRAM utilization?
wined3d benefits from very sophisticated memory management in OpenGL drivers, whereas DXVK's memory management is fairly stupid, and on Nvidia, there's the added difficulty that the amount of VRAM allocated by other applications (Steam, web browser running in the background) is not available to DXVK either, so 2.2GB could be too much already.

Ok it seems that I have solved the issue. The culprit was IRQBALANCE which is enabled by deault in Pop OS (dunno about other distros). TBH I stumbled upon this by pure luck while looking into cpufreq gnome extension.
I disabled irqbalance using sudo apt-get remove irqbalance
Rebooted once and the issue is COMPLETELY gone !!
I am a happy man now :)

I suggest you put this info in the faq section, might help some other people...
Some some threads regarding this...
http://konkor.github.io/cpufreq/faq/#irqbalance-detected
https://github.com/konkor/cpufreq/issues/48
https://github.com/pop-os/default-settings/issues/60

Huh, interesting. This sounds like a very system-specific problem however, even on systems with irqbalance active.
You might still be running out of VRAM however, 381MB sysmem seems a bit high just for constant buffers + staging buffers alone. Just in case performance still isn't where you'd expect.

I am certainly not the only one having this problem, some on Ubuntu 18.04 was having the same problem..
https://askubuntu.com/questions/1067866/ubuntu-18-04-steam-games-frame-rate-drop
Anyways thanks for trying to help, dxvk works great too !!


Attempt to: Fix docker pushing, caching, and upgrade actions

Tried using https://github.com/overmindtech/buildkit-cache-dance to cache volume stuff - avoided this. too much magic.
Upgrades build-push-action (less explicit about buildx)
Upgrades meta action (tries using latest setup + semver setup)
Fixes branch/master ref

Hopefully this actually pushes now while testing. Will pin back at main after.

2s docker build with the cache is pretty sweet


Disable Hue groups for new setups

Breaking change

Proposed change

Hue groups don't have unique IDs (#31002), hence they cannot be put in the entity registry or device registry. They are also kinda useless as Hue can be controlled via groups in Home Assistant.
So moving forward, all new set ups of Hue will disable Hue groups. They can always be enabled again via configuration.yaml.
Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

Hi Balloob,
wont this effect the activate_scene, which needs the hue_group?
  set_hue_scene:
    alias: 'Set Hue scene'
    sequence:
      service: hue.hue_activate_scene
      data_template:
        group_name: >
          {{ states('input_select.hue_groups')}}
        scene_name: >
          {{ states('input_select.hue_scenes')}}

wouldn't it be better to add the hub-id to the hue_groups? That way we could even use the groups over multiple hubs.
thanks.

No this won't impact that service, as that service uses the data directly from the API.


Deprecate "Configuring Tugboat" section of docs:

Verify that all "Configuring Tugboat" content is explained elsewhere in the docs, and if not, expand docs
Remove "Configuring Tugboat" from the site
Add "Configuring Tugboat" pages to .htaccess

Verified "Configuring Tugboat" content carried over to other pages in the docs, created temp "Visual Diffs" page to capture that content, added Configuring Tugboat page to .htaccess, removed the directory & deleted references from SUMMARY.md, and pushed to new-docs.


Support newOrderRespType and fix onFailure routing in BinanceApiCallbackAdapter

Thanks for this library! I'm currently using it in my Scala project and I want to share some improvements.
Binance added newOrderRespType on their V3 API, allowing API clients to specify the desired response format by choosing between ACK/RESULT/FULL. FULL makes Binance return full details on the newly created order, including executedQty and fills, which in turn contain price, qty and commission. This enables you to calculate the (average) fill price for market orders. (fixes #105)
binance-java-api did not support this functionality yet. I also added error routing to BinanceApiCallbackAdapter, which previously threw any exceptions rather than calling onFailure of the wrapped BinanceApiCallback. Now you can actually catch exceptions when using the async API.

Useless for new limit orders. We need it when checking on existing orders.

@personalityson: unfortunately, Binance REST API still does not offer that feature. The only way to get trade/fill details on historic orders is by requesting the trade history for the relevant symbol and then cursor-surfing through it until you find trades with that particular order ID. 😥
Far from efficient, but the only way to get it done. The endpoint is GET /api/v3/myTrades. Every symbol-specific request has a (rate limiting) weight of 5, but you can end up with a 150+ weight if you don't pass a symbol at all, which gets you throttled pretty quickly. v4 should have a filter for order ID.
I noticed in the Telegram group for developers that this is a much requested feature among users of their API. @binance-exchange should prioritize this over listing more shitcoins.
In my application I decided to reduce the excess of calls to /api/v3/myTrades by caching recent results, so that 'getTradesForOrder' can search through there. It works.


Can't see workloads after moving namespace to another project

Rancher versions: 2.0 master 1/21
Steps to Reproduce:

As Admin create a cluster
Create two projects
In first project, add two workloads to a namespace
Move the namespace to the second project
Go to workloads page

Results:  Can't see the workloads, if I move it back to original project, they show back up.

appears to be fixed. no single code change was made to fix this, but a ton of changes were made in this area; looks to me like one of them addressed this bug.

Version - 2.0 master 3/4
Verified fixed


Pull request #94 causes http.ErrBodyReadAfterClose

I have experienced a bug that is mentioned by @faulkner in #94 (https://github.com/getsentry/sentry-go/pull/94/files#r373130154)

This introduces a new bug. If ioutil.ReadAll returns an error the body is left in a closed state, so reading the body later results in a http.ErrBodyReadAfterClose, so instead of the original error getting sent to Sentry you end up just getting http: invalid Read on closed Body with no way of knowing what the original error was.

According to a follow-up comment, this would be addressed in #117. But that issue was closed without any code changes and I don't see any other issues opened to keep track of this bug.

@lagren I have a WIP that will address that (this) and #96.

@lagren could you please try with master?
I'm planning to cut v0.6.0 soon.


Support developing in IE 9

I have created a new reactjs project using create-react-app and am finding it's not working on IE10 & IE9. I have done a lot of research and it led me to using polyfills, which I have done with many of my other Rails on React app, but I'm finding it not working with this project created via create-react-app.
Here's the error:
SCRIPT5009: 'Map' is undefined
I notice this error is related to ES6's new Map() function.
So, here's what I've done in my code in an attempt to make it work:
import './polyfill';
import React from 'react';
import ReactDOM from 'react-dom';
import App from './App';
import { BrowserRouter } from 'react-router-dom';
import 'bootstrap/dist/css/bootstrap.min.css';

const app = (
  <BrowserRouter basename={process.env.PUBLIC_URL}>
    <App />
  </BrowserRouter>
);

ReactDOM.render(app, document.getElementById('root'));

Polyfill.js:
import 'core-js/es6/map';
import 'core-js/es6/set';
import 'core-js/fn/object/assign';

This isn't working. I'm not sure what else to try. I've tried a lot of other polyfill imports as well and continue to get the same error.
Any help would be appreciated!

Sorry for hijacking the thread but I'm facing the same problem.
Is this a bug report?
Yes
Environment
node v10.13.0
yarn v1.12.3
create-react-app v2.1.1
Steps to Reproduce

Create React application using npx create-react-app my-app
Add react-app-polyfill using yarn add react-app-polyfill
Change the first line of src/index.js to import 'react-app-polyfill/ie9';
Open IE9 or IE10 and load the application

Expected Behavior
The application should work. No errors should be present in the console and the spinning React logo should be displayed.
Actual Behavior
A white screen is displayed and there is an error in the console: SCRIPT5009: 'Map' is undefined

For some reason the added polyfills for the older browsers are ignored. Please provide more info how to integrate them properly into a React app or investigate ths issues if the steps are corrent.
Thanks in advance!

Only when executing yarn start. When the application is built for production, the polyfills are loaded and  everything works as expected.

It is a known limitation that the dev server does not support IE9. We're working on adding this.

@ivoborisov I have also got sucked into this problem recently, and I can't wait the release of 3.0 to develop in IE 9, so I spent hours to fix it locally.
This problem is caused by react-dev-utils/webpackHotDevClient provided by CRA to bring better user experience. The custom webpackHotDevClient introduced chalk module accidentally which in turn have a dependency of ansi-style module, and the final module used es6 Map feature which sucks in IE 9. Unfortunately, webpackHotDevClient is loaded prior to the polyfilled app code, so IE 9 complaines that 'Map' is undefined.
Fix:
Eject CRA locally and then locate the entry config in config/webpack.config.dev.js .

exchange the position of the two entries OR
use the stock client OR
remove the chalk code in react-dev-utils/webpackHotDevClient (chalk seems unnessesary)

@ivoborisov I have also got sucked into this problem recently, and I can't wait the release of 3.0 to develop in IE 9, so I spent hours to fix it locally.
This problem is caused by react-dev-utils/webpackHotDevClient provided by CRA to bring better user experience. The custom webpackHotDevClient introduced chalk module accidentally which in turn have a dependency of ansi-style module, and the final module used es6 Map feature which sucks in IE 9. Unfortunately, webpackHotDevClient is loaded prior to the polyfilled app code, so IE 9 complaines that 'Map' is undefined.
Fix:
Eject CRA locally and then locate the entry config in config/webpack.config.dev.js .

exchange the position of the two entries OR
use the stock client OR
remove the chalk code in react-dev-utils/webpackHotDevClient (chalk seems unnessesary)

受教,但是这种方式解决了map问题,但是又会出现以下这个问题,请问有解决方案么?

react-app-polyfill includes only specific features from core-js. If you need others you must include it manually - e.g. import core-js/es/object/set-prototype-of.

Just in case helps someone while a better solution arrives, we found something that works for us for the time being. Basically we have to run the app in non-ES6 environments and unless applying this hack we had to run the app in prod mode all the time, and this means wasting a lot of time.
Basically what we did was to mock the ES6 stuff in use in the app BEFORE any other script gets loaded in development mode. In public/index.html:
`

`
I know this doesn't look so promising because we are not actually loading any polyfill for Map and Set so we could have problems with third parties relaying on them, but as far as we know this could happen, it helps us running the app in development mode.

I solved this using the core-js polyfill library. You can check the details of the solution on this stack overflow answer.
PS: I have to use import 'core-js/es/**' instead of /es6/;

I'm experiencing this when developing for Opera 12.16 (the world of Smart TV web browsers are based on rather much older browsers than desktops are). Here are the first lines of my index.tsx:
import 'react-app-polyfill/ie9'; // Provides Map, which Opera 12.16 lacks
import 'react-app-polyfill/stable';

Both my development and production browserslist fields specify "opera >= 12.16".
When I run yarn run start, Opera throws an error on the new Map call mentioned in the first two comments. As mentioned by @Timer and @lujb, it's due to the devtools.

It is a known limitation that the dev server does not support IE9/11.

As it's a known limitation, some guidance to that effect would have been very much appreciated in the Supported Browsers and Features documentation. But this is just a whinge.
As for when I run yarn run build and navigate to the website, the browser immediately crashes with no explanation. I can't give any more details because it doesn't provide any.
I'm really surprised that, given that the devtools do not respect browser compatibility, create-react-app doesn't provide an optional 'polyfills' entry point that can be assured to run before anything like the devtools?

Thanks for your note in #5336, I am going to close this as a duplicate of it.