[HMR] connected but not reloading on html file changes

When running node server.js, webpack-dev-middleware and webpack-hot-middleware compile, and index.html opens with [HMR] connected being displayed in the console. However, when I change the index.html file and save, the page does not reload, forcing me to stop the server and run it again.
server.js
const express = require('express');
const webpackDevMiddleware = require('webpack-dev-middleware');
const webpackHotMiddleware = require('webpack-hot-middleware');
const webpack = require('webpack');
const webpackConfig = require('./webpack.config.js');
const bodyParser = require('body-parser');
var path = require('path');
const app = express();

const compiler = webpack(webpackConfig);

app.use(webpackDevMiddleware(compiler, {
  hot: true,
  filename: 'bundle.js',
  publicPath: '/dist/',
  stats: {
    colors: true,
  },
  historyApiFallback: true,
}));

app.use(webpackHotMiddleware(compiler, {
  log: console.log,
  path: '/__webpack_hmr',
  heartbeat: 10 * 1000,
}));

app.get('/', function(req, res) {
  res.sendFile(path.join(__dirname + "/src/index.html"));
});

const server = app.listen(3000, function() {
  const host = server.address().address;
  const port = server.address().port;

  console.info('==> 🌎 Listening on port %s. Open up http://localhost:%s/ in your browser.', port, port);
});

webpack.config.js
'use strict';

var path = require('path');
var webpack = require('webpack');

module.exports = {
  entry: [
    'webpack-hot-middleware/client?path=/__webpack_hmr&timeout=20000&reload=true',
    path.join(__dirname, '/src/main.js')
  ],
  output: {
    path: path.join(__dirname, 'build/'),
    filename: 'bundle.js',
    publicPath: '/assets'
  },
  plugins: [
    new webpack.HotModuleReplacementPlugin(),
    new webpack.NoEmitOnErrorsPlugin()
  ],
  module: {
    rules: [  /* Bunch of rules here */  ]
  }
};

A physical refresh through Chrome (v 60.0.3112.32) will update the page, but I would like the page to automatically reload on file change. Any help appreciated!
EDIT: Interestingly enough, when I make any other file change, like to my .scss files, HMR activates and the page reloads.

Found a sort of hack to this issue. Probably should have done some more research into HMR. Apologies and closing.
https://github.com/jantimon/html-webpack-plugin/issues/232


fix(babelify): Run babelify as a global transform when minifying

Since the uglify transform is run as global, it should also be the case for the babelify transform. Otherwise, it fails with ES6 modules.
Another option would be to always run babelify as a global transform.
Also refactored bundler.transform for uglify to have same arguments order as babelify.

Hi Jonathan.
Thanks for the pr.
I see that if we continue with Uglify global, this is the way to go.
What are your thoughts on keeping global?
On 14 Nov 2016 12:01 pm, "Jonathan Goldwasser"<EMAIL_ADDRESS>wrote:

Since the uglify transform is run as global, it should also be the
case for the babelify transform. Otherwise, it fails with ES6 modules.
Another option would be to always run babelify as a global transform.
Also refactored bundler.transform for uglify to have same arguments
order as babelify.

You can view, comment on, or merge this pull request online at:
https://github.com/FidelLimited/serverless-plugin-optimize/pull/14
Commit Summary

fix(babelify): Run babelify as a global transform when minifying

File Changes

M src/index.js
https://github.com/FidelLimited/serverless-plugin-optimize/pull/14/files#diff-0
(5)

Patch Links:

https://github.com/FidelLimited/serverless-
plugin-optimize/pull/14.patch
https://github.com/FidelLimited/serverless-
plugin-optimize/pull/14.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FidelLimited/serverless-plugin-optimize/pull/14, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGO-8Qat-jUkq2gILPQdchCzyf9Omknhks5q-HfHgaJpZM4KxaXL
.

Hi Gonçalo,
I would continue with Uglify global because this is the way to achieve the smallest package possible.
It could also be added as an option in serverless.yml.

See #15 for the second option.

Perfect Jonathan! I was about say that a global flag would be ideal. In the future we can add ignore array too, to be even more granular.
Going to merge the other one and close this one.


[WIP] feat: Handle app link intent for events

Fixes #1833

You have to pass the data in intent Bundle, not in viewmodel

Updated


correcting bug in method for locating xyz for md in Trajectory

This change fixes a bug in the well.Trajectory.xyz_for_md() that was causing a crash in particular circumstances when the measured depth was at the finish md of the trajectory.

Codecov Report

Merging #135 (0cb6811) into master (4d8cf9e) will increase coverage by 0.03%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   39.49%   39.53%   +0.03%
==========================================
  Files          50       50
  Lines       21410    21381      -29
==========================================
- Hits         8456     8453       -3
+ Misses      12954    12928      -26

Impacted Files
Coverage Δ

resqpy/well.py
33.28% <20.00%> (+0.03%)
:arrow_up:

resqpy/olio/simple_lines.py
42.60% <0.00%> (-0.50%)
:arrow_down:

resqpy/olio/transmission.py
75.70% <0.00%> (-0.04%)
:arrow_down:

resqpy/grid_surface.py
79.39% <0.00%> (-0.03%)
:arrow_down:

resqpy/model.py
62.02% <0.00%> (ø)

resqpy/grid.py
38.17% <0.00%> (+0.01%)
:arrow_up:

resqpy/olio/vdb.py
11.43% <0.00%> (+0.01%)
:arrow_up:

resqpy/lines.py
18.24% <0.00%> (+0.02%)
:arrow_up:

resqpy/fault.py
37.60% <0.00%> (+0.04%)
:arrow_up:

... and 7 more

Continue to review full report at Codecov.

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


Test should be revised

We redifine the function of the app.py. We need to rewrite the unit test, especially for the "token" part

The problem is caused by the folder name conflit.

Test case all be revised and done


Make "connect" and "read" timeouts properties instead of constructor arguments

Connect and read timeout values are currently specified as constructor arguments in the Java client. However, these values are not integral to the proxy instance and don't need to be immutable. As a result, they would be better represented as properties.

This is done.


Rollout restart the resources after applied changes

Overview
When config or relation data causes changes need to be applied such as certificate changes or version changes, be sure to rollout restart the deployment AFTER the installation is complete so that the new changes are picked up.
Details

the keystone-k8s-auth deployment isn't so good about restarting the webservice on changes to the certificate data.  It can handle changes to the configmap well enough, but its safer to just rollout new pods when these changes in config occur.
Add a new config option called extra-args allowing the juju admin to suppress or increase verbosity on the service.

@ggouzi I believe this addresses some of the issues you've seen where changes to certificate data aren't picked up until you restart the deployment


FAST.Farm - Invalid logical input for file

Hello,
I am working to run FAST.Farm with the sample primary input file provided (and other openFAST files from previous simulations), but am running into the following issue:

It appears that my value of "False" for "ChkWndFiles" is not being read correctly, and I'm not sure why.  As seen in the text file, I'm also using "1" for "Mod_AmbWind", so shouldn't ChkWndFiles be ignored anyways?

Thanks in advance!

Dear @ealmquist,
As with any input file processing error, you can always enable the Echo option to debug.
But from what I can tell, it looks like line 14 (WindFilePath) has accidentally been moved to the end of line 13 in your FAST.Farm input file, which is causing FAST.Farm to complain about line 15 (ChkWndFiles).
Best regards,

Hi @jjonkman,
Thank you for the quick response!  I'll be sure to use Echo next time - I'm still relatively unfamiliar with openFAST and didn't realize that was an option.
Thanks again,

Hello @jjonkman,
This issue is closed but the problem regarding sample primary input file (line 18 and 19) perseveres.
Thus, I ran into the same error and tumbled across this issue.
Best regards
Arnold

@ArnoldTUB, this error often occurs when the input files that you are using are a different version from the version of the code you are using. Make sure that the code you compiled is for the version of input files you have and make adjustments if they are not.


remove-poetry: an option to skip the version for every packages when updating the pyproject.toml file

Will go the other way, by default no version will be specified but there will be an option to add the packages versions


Bug 2024928: add IPv6 support to the exportNetworkFlows API

The anyOf stanzas - which indicate the addresses can be either IPv4
or IPv6 - must be added via a patch to the CRD.
Signed-off-by: Miguel Duarte Barroso<EMAIL_ADDRESS>

My attempt at updating the API as per what's indicated in this bz / RFE.
/cc @ricky-rav

My understanding is that:

IPFIX supports IPv6, so the new changes will enable users to specify IPv6 endpoints
the same applies to sFlow
NETFLOW only supports IPv6 starting from version v9. However, openvswitch uses netflow v5, which is only limited to IPv4.

Based on that, we might want to add the new API for netflow in order to be consistent across all three protocols, but  remove the ipv6 format, since it's not supported. We can add ipv6 support easily in the future, if ever ovs moves to a netflow a version >= v9.
@danwinship what do you think? What's your take on the new API?
(tagging you just because we discussed this on slack a while back )
Thanks!

I don't think we need this anymore, we have the configMap that will update in realtime?

https://github.com/openshift/enhancements/blob/master/enhancements/network/ovs-flow-export-configuration.md#task-1-setup-a-new-configmap-that-is-readable-by-the-cno

https://github.com/openshift/enhancements/blob/master/enhancements/network/ovs-flow-export-configuration.md#task-1-setup-a-new-configmap-that-is-readable-by-the-cno

@rbbratta please correct me if I'm wrong, but, from the info on that doc I get the impression this config map is limited to the ipfix collector type.
Don't we want to have configurable flow collectors also for netflow / sflow ? (right ... the netflow ovs uses does not feature ipv6 support, which brings us down to sflow).
 I'm next to clueless when it comes to observability / any of these protocols.

https://github.com/openshift/enhancements/blob/master/enhancements/network/ovs-flow-export-configuration.md#task-1-setup-a-new-configmap-that-is-readable-by-the-cno

@rbbratta please correct me if I'm wrong, but, from the info on that doc I get the impression this config map is limited to the ipfix collector type.
Don't we want to have configurable flow collectors also for ~netflow /~ sflow ? (right ... the netflow ovs uses does not feature ipv6 support, which brings us down to sflow).
 I'm next to clueless when it comes to observability / any of these protocols.

Yes, we should really defer to the NetObserv team as they are the only ones to use this.

Hi @maiqueb from OVS, we only use IPFIX flow collection.
Please also consider that this ConfigMap is reconciled by the Network Observability Operator so if you create/modify it manually, then the changes will be automatically reverted by the Operator, in case the Network Observability product is installed.

Hi @maiqueb from OVS, we only use IPFIX flow collection.
Please also consider that this ConfigMap is reconciled by the Network Observability Operator so if you create/modify it manually, then the changes will be automatically reverted by the Operator, in case the Network Observability product is installed.

I'm confused; I am trying to update the openshift API so it becomes possible to configure CNO, specifying IPv6 flow collectors.
AFAIU, CNO gets the flow configuration from the aforementioned config map **but also via the openshift api. Right ? @mariomac

@maiqueb yes we added the spec.exportNetworkFlows API first but then it is not dynamic enough since every time you change spec.exportNetworkFlows it re-renders the daemonset which deletes all the pods and causes network disruption.  This is bad.  It is also useless since real use cases need to set sampling, cacheMaxFlows and other specific parameters which the API doesn't support.
Roughly speacking, once Netobserv started actually trying to set things they added the ConfigMap so their operator can actually work https://github.com/openshift/cluster-network-operator/blob/master/pkg/network/ovn_kubernetes.go#L1090.

@rbratta @maiqueb let me mention that setting the ipfix export through our configmap also requires restarting the ovnkube nodes with the new export arguments. Under the hood, our map does not replace the current API spec but just uses it as a client: https://github.com/openshift/cluster-network-operator/blob/master/pkg/network/ovn_kubernetes.go#L315

@danwinship should I continue working on this API change given the discussion above ?
Who would be interested in the use case case enabled (configurable IPv6 flow collectors for sflow) ? AFAIU, the observability team only care about ipfix.

In theory, customers could be using the raw netflow/sflow/ipfix API without using the observability operator. The API was originally added with the intention that it would be used directly by the customer, not that it would be consumed by another operator within OCP. But maybe we have moved away from that idea?
If we assume that some customers will want to actually export flow data from OCP (ie, not just analyze the flows with the tools that we give them, but actually export them to some OCP-external database to be analyzed there), then we should preserve (and perhaps extend) the existing API, and ensure that it interacts with the observability operator in a reasonable and clearly-documented way. This might mean that if you enable the observability operator that you cannot use the "raw" flow export feature, or it might mean that if you enable the observability operator, that we configure OVS to export flows to both the observability operator and to the user-configured flow collector(s). In the latter case, we might also want to change the way we update the OVS flow export config to be less disruptive, like the observability operator does.
If we assume that customers do not actually want to export flow data from OCP (or that, for some reason, we don't want to support them doing it, even though they do want to), then we would deprecate the existing API, and update both the API docs and the product docs to indicate that it was deprecated in favor of the observability operator.
(Another possibility would be that we could have OVS only export to the observability operator, but have the observability operator have the ability to re-export to user-defined flow collectors, but it doesn't seem like there are any benefits to that approach.)
Either way, if this PR was only being prioritized because we thought the observability operator needed it, and it turns out that they don't, then that might mean we don't care about this API change right now. (Though it would still be good to at least update the docs to clarify the interactions.)

Maybe there was a misunderstanding in some previous discussions that lead to some bad assumptions, or I didn't fully understood  last messages. Let me summarize the current behavior, just to verify that we are all in the same line:

If you enable the Network Observability Operator, you can still use the "raw" export feature without any restriction, this is, setting the {sflow,netflow,ipfix}-targets properties in the Operator Configuration. The NOO coexists well with it.
If you enable the Network Observability Operator, you cannot manually use the ovs-flows-config ConfigMap, as it has been created exclusively as a communication mechanism between the NOO and OVN-Kubernetes.
The ovs-flows-config controller uses, under the hood, the "raw" export feature mentioned in step 1, so any limitation on the raw export feature (e.g. having to restart ovnkube pods) is also a limitation in the NOO <-> OVN-K interaction by means of ovs-flows-config.

Maybe there was a misunderstanding in some previous discussions that lead to some bad assumptions, or I didn't fully understood last messages. Let me summarize the current behavior, just to verify that we are all in the same line:

If you enable the Network Observability Operator, you can still use the "raw" export feature without any restriction, this is, setting the {sflow,netflow,ipfix}-targets properties in the Operator Configuration. The NOO coexists well with it.
If you enable the Network Observability Operator, you cannot manually use the ovs-flows-config ConfigMap, as it has been created exclusively as a communication mechanism between the NOO and OVN-Kubernetes.
The ovs-flows-config controller uses, under the hood, the "raw" export feature mentioned in step 1, so any limitation on the raw export feature (e.g. having to restart ovnkube pods) is also a limitation in the NOO <-> OVN-K interaction by means of ovs-flows-config.

Given @mariomac 's answer above, I still see enough motivation to proceed with this API update since:

the NOO coexists with the {sflow,netflow,ipfix}-targets properties in the Operator Configuration
once NOO is enabled, the  ovs-flows-config ConfigMap cannot be used by the user
any limitation on the raw export feature (e.g. having to restart ovnkube pods) is also a limitation in the NOO <-> OVN-K interaction by means of ovs-flows-config


byobu: add gettext to nativeBuildInputs

Description of changes
This PR fixes crosscompile issues with byobu.
to reproduce:
nix build nixpkgs#pkgsCross.aarch64-multiplatform.pkgs.byobu
error: builder for '/nix/store/a2vr8a9bx385pcbxvi6bvnfjq20kyzlp-byobu-aarch64-unknown-linux-gnu-5.133.drv' failed with exit code 127;
       last 10 log lines:
       > make[2]: Leaving directory '/build/byobu-5.133/usr/bin'
       > make[1]: Leaving directory '/build/byobu-5.133/usr/bin'
       > make[1]: Entering directory '/build/byobu-5.133'
       > make[2]: Entering directory '/build/byobu-5.133'
       > make[2]: Nothing to be done for 'install-exec-am'.
       > make[2]: Nothing to be done for 'install-data-am'.
       > make[2]: Leaving directory '/build/byobu-5.133'
       > make[1]: Leaving directory '/build/byobu-5.133'
       > /nix/store/pi4nks092wm676by0xqh72rfcrfwf3bp-stdenv-linux/setup: line 133: msgfmt: command not found
       > /nix/store/pi4nks092wm676by0xqh72rfcrfwf3bp-stdenv-linux/setup: line 144: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/a2vr8a9bx385pcbxvi6bvnfjq20kyzlp-byobu-aarch64-unknown-linux-gnu-5.133.drv'.

Things done
The following command does now compile:
nix build .#pkgsCross.aarch64-multiplatform.pkgs.byobu

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

My First Pull request here, if something is missing please tell me.

Is it still required in buildInputs? We should also double check the use of perl and preferably set strictDeps.

thanks for the feedback,
I didn't found any evidence for perl usage in the build or in the source code, even debian does not have it as dep.
also strictDeps works without issue to compile.

Double checked the build output, and it seems that perl maybe still required as a buildInputs, since the shebang of lib/byobu/include/notify_osd is #!/usr/bin/perl (and there's another reference of perl in lib/byobu/include/mondrian, which has to be manually patched)

thanks again for the feedback,
pretty confused, can confirm that it includes "hidden" perl files, never trust github search,.... .
Also the debian/control, includes some perl deps. but they are not shown with apt show perl.
but anyway, will include perl for not breaking features.
they are also used in some keybindings, eg. should be included.
with buildInputs = [ perl ] it looks to replaces the shebangs in lib/byobu/include/notify_osd.
not quite sure how to fix lib/byobu/include/mondrian inline use of perl.
probably by adding the path to the wrapper?! other suggestions?

Since nobody ever complaint about that maybe just ignore it for now?


Aliases with group_by and select

Setup
Versions

Rust: rustc 1.63.0 (4b91a6ea7 2022-08-08)
Diesel: 2.0.0
Database: PostgreSQL 13
Operating System Linux (Ubuntu 22.04)

Feature Flags

diesel: postgres, uuid, chrono

Problem Description
I'm trying to add second alias to query with left_join and failing.
I have the following code which compiles fine:
let leafs = diesel::alias!(chunks as leafs);
let mut query = chunks::table
    .left_join(
        leafs.on(chunks::path
            .contains(leafs.field(chunks::path))
            .and(leafs.field(chunks::nchildren).eq(0))),
    )
    .group_by(chunks::id)
    .select((
        chunks::all_columns,
        sum(leafs.field(chunks::estimated).nullable()),
    ))
    .into_boxed();

But if I'm converting it to this, it fails to compile:
let (c, leafs) = diesel::alias!(chunks as c, chunks as leafs);
let mut query = c
    .left_join(
        leafs.on(c
            .field(chunks::path)
            .contains(leafs.field(chunks::path))
            .and(leafs.field(chunks::nchildren).eq(0))),
    )
    .group_by(c.field(chunks::id))
    .select((
        c.fields(chunks::all_columns),
        sum(leafs.field(chunks::estimated).nullable()),
    ))
    .into_boxed();

What are you trying to accomplish?
I'm trying to add alias for main self-referencing table to make query more complex later
What is the expected output?
It should compile :)
What is the actual output?
60 |             .select((
   |              ^^^^^^ the trait `ValidGrouping<AliasedField<c, chunks::columns::id>>` is not implemented for `AliasedField<c, chunks::columns::parent_id>`
60 |             .select((
   |              ^^^^^^ the trait `ValidGrouping<AliasedField<c, chunks::columns::id>>` is not implemented for `AliasedField<c, chunks::columns::path>`
60 |             .select((
   |              ^^^^^^ the trait `ValidGrouping<AliasedField<c, chunks::columns::id>>` is not implemented for `AliasedField<c, chunks::columns::label>`
... and so on for each field in chunk model

Are you seeing any additional errors?
Steps to reproduce
corresponding model is the following:
diesel::table! {
    use diesel::sql_types::*;
    use diesel_ltree::sql_types::*;

    chunks (id) {
        id -> Int8,
        parent_id -> Nullable<Int8>,
        path -> Ltree,
        label -> Text,
        estimated -> Int4,
        nchildren -> Int4,
    }
}

Checklist

[x] I have already looked over the issue tracker  and the disussion forum  for similar possible closed issues.

[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[x] This issue can be reproduced without requiring a third party crate

Thanks for reporting this bug. It seems like that this impl is not general enough. Likely it must be change in such a way that it accepts all combinations of AliasedFields that implement ValidGrouping on their own. https://github.com/diesel-rs/diesel/blob/9502a9fd3df61bcfd59c63fecb79e242802e99d6/diesel/src/query_source/aliasing/aliased_field.rs#L80-L86
As workaround you can list all columns explicitly in your group_by clause.

Thanks for explanation!
I'll try to create a PR, but I'm afraid I'm not competent enough in Rust to do it right and not break anything else :)

@mlesin What needs to be done is the following:

The linked impl needs to be changed to the following:

impl<S, C1, C2> ValidGrouping<AliasField<S, C1>> for AliasedField<S, C2>
where
    S: AliasSource,
    C1: Column<Table = S::Target>
    C2: Column<Table = S::Target>
    C2: ValidGrouping<C1, IsAggregate = is_aggregate::Yes>
{
    type IsAggregate = is_aggregate::Yes;
}

Add a test based on your example to check that the code is compiling
Open a PR with this changes

Thank you very much for fixing this!
Unfortunately I didn't have time to try to do it myself after your wonderful explanation, sorry :(


Twitch API Helix

Will this module be maintained for new Twitch API?

With Helix being a completely new API, and Kraken being deprecated, I think rather than try to integrate Helix into this module and have to rename the module and everything, I plan to maintain this module for Kraken and create a separate module for Helix.
Right now though Helix is still severely lacking key endpoints from Kraken, webhooks aren't implemented yet, and a lot of documentation is lacking, so I'm holding off creating a new module dedicated to Helix until there is sufficient need/demand. For those looking to play around with Helix right away before most of the features are there it is easy enough to just use the request module to do it.


I really wanted to try this package it looks really cool.  I can't get it installed though,

const { withExpo } = require("@expo/next-adapter");
const withPlugins = require("next-compose-plugins");
I am getting warnings about the require statements, I have ran yarn npm... deleted node modules.
I am trying to install into t3 create turbo because it has the trpc ready to go but I can't get those packages to work in the next.config.  I am on my own computer not my works so its windows and I'm running docker and its so slow.  Any suggestions.

There is a whole separate issue where someone is trying to install Solito into the t3 create turbo stack https://github.com/nandorojo/solito/issues/377
My recommendation would be either to review that thread and try to help with get that version of a t3-turbo-solito repo working, or flip the approach and try to start with Solito and add T3 back into the Solito stack.

i don’t have any useful info to go off of in this issue. you need to share what the errors are

I am facing something similar:
/** @type {import('next').NextConfig} */
const { withExpo } = require('@expo/next-adapter');
const { withTamagui } = require('@tamagui/next-plugin');
const withPlugins = require('next-compose-plugins');
const withImages = require('next-images');
const { join } = require('path');

process.env.IGNORE_TS_CONFIG_PATHS = 'true';
process.env.TAMAGUI_TARGET = 'web';
process.env.TAMAGUI_DISABLE_WARN_DYNAMIC_LOAD = '1';

const withTM = require('next-transpile-modules')([
  'solito',
  // add other packages here that need transpiling, such as moti
]);

module.exports = async (phase) => {
  /** @type {import('next').NextConfig} */
  const nextConfig = {
    images: {
      disableStaticImages: true,
    },
    modularizeImports: {
      '@tamagui/lucide-icons': {
        transform: `@tamagui/lucide-icons/dist/esm/icons/{{kebabCase member}}`,
        skipDefaultConversion: true,
      },
    },
    transpilePackages: [
      'solito',
      'react-native-web',
      'expo-linking',
      'expo-constants',
      'expo-modules-core',
    ],
    experimental: {
      // optimizeCss: true,
      scrollRestoration: false,
      legacyBrowsers: false,
    },
  };

  const plugins = [
    withTM,
    [withExpo, { projectRoot: __dirname }],
    withImages,
    withTamagui({
      config: './tamagui.config.ts',
      components: ['uikit', 'tamagui'],
      logTimings: true,
      disableExtraction: process.env.NODE_ENV === 'development',
      // experiment - reduced bundle size react-native-web
      // if this cause any issues, set to false, but to optimize size, use excludeReactNativeWebExports instead
      useReactNativeWebLite: true,
      shouldExtract: (path) => {
        if (
          path.includes(join('modules', 'app')) ||
          path.includes(join('modules', 'shared'))
        ) {
          return true;
        }
      },
    }),
  ];

  // has to be done w/o default config. Issue: https://github.com/cyrilwanner/next-compose-plugins/issues/59
  return withPlugins(plugins, nextConfig)(phase, { undefined });
};

package.json
 "solito": "^3.2.0",
 "next": "^13.0.6",
 "react": "18.2.0",
 "react-dom": "18.2.0",

Then get an error like this one:
warn  -     The root value has an unexpected property, projectRoot, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack).
warn  - See more info here: https://nextjs.org/docs/messages/invalid-next-config

Seems similar to this one: https://github.com/cyrilwanner/next-compose-plugins/issues/59

I'm wondering if you're on an old version of expo next adapter. If you're using Tamagui, I would follow their Next.js docs instead of using withPlugins, etc. You can also use transpilePackages from Next.js rather than nextTM now.

Those warnings are annoying, but the app still starts fine, so I'm closing this. I think you may need to upgrade expo/next-adapter to the latest version. There's no need to use withExpo if you're using withTamagui.


Make ProcessFactory work in JDK < 9 again

Codecov Report

Merging #42 into master will increase coverage by 0.89%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #42      +/-   ##
============================================
+ Coverage     73.09%   73.98%   +0.89%
- Complexity      461      462       +1
============================================
  Files            65       65
  Lines          1680     1680
  Branches        112      112
============================================
+ Hits           1228     1243      +15
+ Misses          391      375      -16
- Partials         61       62       +1

Impacted Files
Coverage Δ
Complexity Δ

...va/co/elastic/apm/impl/payload/ProcessFactory.java
78.72% <100%> (+27.65%)
0 <0> (ø)
:arrow_down:

...a/co/elastic/apm/report/ReportingEventHandler.java
100% <0%> (+8.33%)
9% <0%> (+1%)
:arrow_up:

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 fff08ae...4d7cfc7. Read the comment docs.


File nesting doesnt work for .test.ts

Type: Bug
I've tried multiple patterns: ${capture}.test.ts and `${basename}.test.${extname}.
Is there something special about .test.ts I'm not aware?
VS Code version: Code - Insiders 1.75.0-insider (6ed4d436a9b6ae131732f4e2a723868231f4473a, 2022-12-23T05:21:57.802Z)
OS version: Windows_NT x64 10.0.19042
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
AMD Ryzen 5 2600 Six-Core Processor             (12 x 3850)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.95GB (9.64GB free)

Process Argv
--crash-reporter-id d15abc04-2f14-48d4-98ba-287dac26245f

Screen Reader
no

VM
0%

Extensions (25)

Extension
Author (truncated)
Version

codesnap
adp
1.3.4

markdown-checkbox
bie
0.4.0

markdown-mermaid
bie
1.17.3

markdown-preview-github-styles
bie
1.0.1

dendron-paste-image
den
1.1.1

vscode-generate-getter-setter
DSK
0.5.0

prettier-vscode
esb
9.10.3

todo-tree
Gru
0.0.220

vscode-peacock
joh
4.2.2

regionfolder
map
1.0.18

git-graph
mhu
1.30.0

js-debug-nightly
ms-
2022.12.1417

powershell-preview
ms-
2022.12.1

vscode-typescript-next
ms-
5.0.202212230

indent-rainbow
ode
8.3.1

pester-test
psp
2022.3.3

vscode-thunder-client
ran
2.2.1

vscode-yaml
red
1.10.1

vscode-sort-json
ric
1.20.0

even-better-toml
tam
0.19.0

vscode-inline-values-powershell
Tyl
0.0.7

errorlens
use
3.6.0

vscode-icons
vsc
12.0.1

better-align
wwm
1.1.6

vitest-explorer
Zix
0.2.34

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12cf:30622697
fim-prod:30623723

    "explorer.fileNesting.patterns": {
        "*.ts": "${capture}.test.ts"
    },

Seems to do it for me.

So my problem was I was using a workspace and one of the individual folders in the workspace had a .vscode/settings.json that had file nesting defined that took precedence, and I wasn't seeing the changes. I didn't get a warning in the settings GUI interestnly enough like it normally does, not sure, but closing as "not an issue" and sorry to waste your time @lramos15, if nothing than to confirm that I was indeed crazy :)


Jinja<3.0 does not work with MarkupSafe>=2.0

The answer may simply be that only the latest version of jinja is expected to work, but I wanted to at least create this issue.
Version 2.11.3 only specifies a version of MarkupSafe>=0.23 with no upper bound. As of MarkupSafe v2.1.0, support for the method soft_unicode that Jinja depends on has been removed. Because there is no upper bound, when installing jinja<3.0, the latest version of MarkupSafe is pulled which is not compatible.

The reproduce, in a new python environment, install jinja2==2.11.3:
pip install jinja2==2.11.3
Then open a python shell and attempt to import import jinja2 to see the ImportError.
ImportError: cannot import name 'soft_unicode' from 'markupsafe' (/Users/grahamherceg/.pyenv/versions/jinja-test/lib/python3.9/site-packages/markupsafe/__init__.py)

Dependency versions should have an upper bound explicitly set to ensure compatibility as new versions are released.
Environment:

Python version: 3.9
Jinja version: 2.11.3

There are SO many issues on this topic already. TL;DR you should ping your transitive dependencies and not at a later point simply install an old version and expect it to work.

I wanted to at least create this issue

Be sure to search for previous issues first. This is a duplicate.

You are using an unsupported version of Jinja, please update to the latest version (3.1.2) if possible.
When writing an application, you must use a tool like pip-tools to pin your application's full dependency tree. This gives you reproducible deployments, allowing you to control when you get updates.


Allow setting og:site_name and application_name meta tags

I want to be able to pass siteName as a prop so the og:site_name and application_name meta tags get set in the document head.

To be resolved in v2


Can it be used without including Angular ?

Hi,
Yes it can be, but you won't have any advanced functionality. You can just use the CSS, but almost everything else is made with angular.


CGW-S-100 Impervious to Address Claim Attacks: re-work or expand to complete attack set?

The CGW-S-100 Impervious to Address Claim Attacks under AGW-S-002 Prevents DoS seems like the correct rooting of the requirement and prevention of that attack is desirable. I think the presence of this single attack in the set of requirements needs to be abstracted OR we need to complete the set of attacks under CAN.

To make matters more complicated, this is a J1939 attack, not a CAN attack per se.

If I understand correctly, the address claim attack uses a CAN protocol attack, which can't take place through a security gateway. So it might be better to re-word this requirement as "Prevent CAN protocol attacks", cite something that talks about the address claim attack / CAN protocol attacks. I could pull together some words on this if I can get a definitive description of the address claim attack.

@kentindell thank you, I agree with your stated understanding. Could you review the changes proposed in https://github.com/nmfta-repo/vcr-experiment/pull/27 ?


[DO NOT MERGE] Upgrade to rails 5

Best reviewed commit-by-commit as other wise it's a massive diff of all the things.  We've gone up to 5.0.2 and only bumped dependencies that we needed to do to get rails 5 compatibility, or silence deprecation warnings.
For: https://trello.com/c/8nO2Xyjc/158-migrate-to-rails-5-feedex-and-support

Prematurely flagged as DNM, because I thought I needed to wait for a new release of gds_zendesk, but that's merged and released now.  DNM flag removed.

Thanks @ikennaokpala - fixed typos in a rebase.

@h-lame the rebased version fixes the typos.


Any news about serial port

Hello VSCode
I use vscode for programing arduino
when will you solve this problem.
thank you.

ok thank you.


[Paypal-Payment] Update checkoutIdHelper class

Our CheckoutIdHelper class allows us to temporarily save the checkoutID, however there is a potential issue if a new payment request is initiated before the capturing payment has finished that is it may lead to incorrect checkout ID.

So i Store the checkout ID and order ID in a map using the order ID as the key and the checkout ID as the value. This way, we can associate a order ID with its corresponding checkout ID.
Use synchronized access to the map to avoid concurrency issues when setting and getting checkout IDs.
Additionally, to ensure that the order ID to checkout ID mapping is consistent across our application, i implement the Singleton pattern into checkoutIdHelper class.

This solution might not work if we have multiple insances of web server aka run on multiple nodes.
Actually now we have the checkout tables. Maybe we should create order after payment.

I know how to fix this and will create another PR to fix this issue.


Fix endpoint routing statefulness.

In the case that other middleware change the path of an HttpContext and cause middleware to re-invoke we used to short-circuit on second time through the middleware pipeline, now we allow routing to occur.
Added unit tests to validate the clearing of state.

#11233
Working on benchmarking this change...

🆙 📅  We're locking down our dev work early so I'd like to get this change in today and then benchmark next week (I won't have time to benchmark today). If benchmarking reveals issues I can get fixes in for them next week.

Basline:
dotnet run -- --server http://asp-perf-win:5001 --client http://ASP-PERF-LOAD:5002  -j C:\GitHub\Benchmarks\src\Benchmarks\benchmarks.plaintext.json -n EndpointPlaintext --self-contained -md --duration 60

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)
Errors

1,782,188
88
48
1.48
315
44.07
0.61
0

Current PR:

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)
Errors

1,665,631
89
100
1.54
336
76.55
0.42
0

Result: 6.54% less RPS
Without clearing Route data:

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)
Errors

1,762,419
90
132
1.5
366
76.94
0.7
0

Result: 1.11% less RPS
@davidfowl / @rynowak clearing RouteData looks to be super expensive, do you still want us to do that here? What are your thoughts on the above?

6% is too high. Can you just clear the route values (HttpContext.Request.RouteValues)

Can you just clear the route values (HttpContext.Request.RouteValues)

Did httpContext.Request.RouteValues?.Clear(); and got:

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)
Errors

1,747,154
88
68
1.55
372
85.94
0.53
0

Result: 1.97% less RPS
That being said it looks like it breaks a back compat test Invoke_BackCompatGetDataTokens_ValueUsedFromEndpointMetadata. Do we care?

That test will have to change regardless - the test expects that the middleware doesn't clean up anything - instead of capturing the values after the middleware unwinds, you'd have to capture them inside next()

Once build passes in this PR i'll merge. I'm assuming 1.97% is an acceptable amount.

It might make senses to get the IRouteValues feature so that it’s a noop if there’s no match. I believe route values is lazily allocated today

It might make senses to get the IRouteValues feature so that it’s a noop if there’s no match. I believe route values is lazily allocated today

It improves the baseline ever so slightly:

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)
Errors

1,749,948
89
96
1.41
330
68.73
0.29
0

Result: 1.81% less RPS


Website crash issue fixed.

The website crashed due to the image not being found now fixed, No more blank screen error.

Request completed.


Depend on ~> 1.0

Is the current version causing issues?

It doesn't match "1.1.0-beta".

❤❤❤


Update contribution notes

update the contribution note for the repo based on slack chat.

Sorry I edited a bit and seems I dismissed nick's review. Let's discuss later.


page indicator color change

How can I change page indicator color? I think this is needed feature as we all want to keep theme color everywhere.

@danish1023  Now you can change size, active and inactive color of page indicator using pageIndicatorStyle  prop. stay tuned more custom page indicator gonna land soon.


Misc improvements

@thorwhalen Thank you!
I don't see your comments in the commits, though.. Have you saved them?


Move all shared code to frontend/src/shared & divide types into separate folders

Moved backendTypes.ts from frontend/src to frontend/src/shared/types as separate files. All shared types are now imported from that folder, but they are divided into separate files that are imported via index.ts.
frontend/src/types.ts was removed, it had some calculation-functions which are now in shared/calculations.ts, as well as one type which is in types folder
fixed the copied types in reference validator to be correctly imported instead of copied

Merge this if you want, or if it disrupts your workflows too much you can leave it and I will merge after your group is done. But it'd be nice if you took a look at it in case you have opinions on any changes.

This seemed like a clear improvement.


Attempt to recover from Errors and RuntimeExceptions

There are several places where errors (OutOfMemoryError, for
instance) cause us not to return pooled buffers, and continue
a memory death spiral.

I have a server on 1.4.12.Final hitting OME issues every week or two. It is only using standard java servlets with some async requests (all blocking IO, no servlet read/write listeners). I don't see fixes in the changelog that look like smoking guns, so unsure if bumping the version is expected to fix my issue.
Relatedly I'd like to add JMX reporting on DefaultByteBufferPool, any chance you've looked into that?

Windows Build 2173 outcome was FAILURE using a merge of 0e16fd895c75ab3360748b4eb5f74ff81d0bc5f7
Summary: Tests passed: 2904, ignored: 618; exit code 1 Build time: 00:29:21

Windows Build 2174 outcome was FAILURE using a merge of 0e16fd895c75ab3360748b4eb5f74ff81d0bc5f7
Summary: Tests passed: 2904, ignored: 618; exit code 1 Build time: 00:28:14

Linux Build 2425 outcome was FAILURE using a merge of 32bfc58b206351bfaaf7caa33563db00f63aeeda
Summary: Tests failed: 1 (1 new), passed: 2986, ignored: 535 Build time: 00:20:04
Failed tests
io.undertow.server.handlers.ChunkedRequestTrailersTestCase.testChunkedRequestsWithTrailers[proxy][http2-clear-upgrade]: Connection: keep-alive
Content-Length: 26

foo: fooVal
bar: barVal]
> but was:<HTTP/1.1 [500 Internal Server Error
Connection: keep-alive
Content-Length: 0
]
>
expected:<HTTP/1.1 [200 OK
Connection: keep-alive
Content-Length: 26

foo: fooVal
bar: barVal]
> but was:<HTTP/1.1 [500 Internal Server Error
Connection: keep-alive
Content-Length: 0
]
>
	at io.undertow.server.handlers.ChunkedRequestTrailersTestCase.testChunkedRequestsWithTrailers(ChunkedRequestTrailersTestCase.java:137)
------- Stderr: -------
10:15:23,581 DEBUG (XNIO-1 I/O-4) [io.undertow.server.handlers.proxy] <ProxyHandler.java:531> Sending request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} to target localhost/<IP_ADDRESS>:8888 for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
10:15:23,581 DEBUG (XNIO-1 I/O-4) [io.undertow.server.handlers.proxy] <ProxyHandler.java:548> Sent request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} to target <IP_ADDRESS> for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
10:15:23,583 DEBUG (XNIO-1 I/O-4) [io.undertow.client.http.HttpClientExchange] <HttpClientExchange.java:87> request terminated for request to localhost/<IP_ADDRESS>:8888 /
10:15:23,583 DEBUG (XNIO-1 I/O-4) [io.undertow.client.http.HttpClientConnection] <HttpClientConnection.java:451> connection to localhost/<IP_ADDRESS>:8888 is being upgraded
10:15:23,583 DEBUG (XNIO-1 task-23) [io.undertow.request.error-response] <DelegatingBasicLogger.java:424> Setting error code 500 for exchange HttpServerExchange{ POST / request {X-Forwarded-Server=[default], Upgrade=[h2c], HTTP2-Settings=[], Connection=[Upgrade, HTTP2-Settings], Trailer=[foo, bar], X-Forwarded-Proto=[http], X-Forwarded-Port=[80], X-Forwarded-For=[<IP_ADDRESS>], Transfer-Encoding=[chunked], Host=[default], X-Forwarded-Host=[default]} response {}}: java.lang.RuntimeException
	at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1392)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:387)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

10:15:23,584 ERROR (XNIO-1 task-23) [io.undertow.request] <Connectors.java:392> UT005071: Undertow request failed HttpServerExchange{ POST / request {X-Forwarded-Server=[default], Upgrade=[h2c], HTTP2-Settings=[], Connection=[Upgrade, HTTP2-Settings], Trailer=[foo, bar], X-Forwarded-Proto=[http], X-Forwarded-Port=[80], X-Forwarded-For=[<IP_ADDRESS>], Transfer-Encoding=[chunked], Host=[default], X-Forwarded-Host=[default]} response {}}: java.lang.NullPointerException
	at io.undertow.server.handlers.ChunkedRequestTrailersTestCase$1.handleRequest(ChunkedRequestTrailersTestCase.java:80)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:356)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

10:15:23,585 DEBUG (XNIO-1 I/O-4) [io.undertow.server.handlers.proxy] <ProxyHandler.java:673> Received response ClientResponse{responseHeaders={content-length=[0]}, responseCode=500, status='', protocol=HTTP/2.0} for request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
10:15:23,586 DEBUG (XNIO-1 I/O-4) [io.undertow.request.error-response] <DelegatingBasicLogger.java:424> Setting error code 500 for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}: java.lang.RuntimeException
	at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1392)
	at io.undertow.server.handlers.proxy.ProxyHandler$ResponseCallback.completed(ProxyHandler.java:677)
	at io.undertow.server.handlers.proxy.ProxyHandler$ResponseCallback.completed(ProxyHandler.java:655)
	at io.undertow.client.http2.Http2ClientExchange.responseReady(Http2ClientExchange.java:134)
	at io.undertow.client.http2.Http2ClientConnection$Http2ReceiveListener.handleEvent(Http2ClientConnection.java:405)
	at io.undertow.client.http2.Http2ClientConnection$Http2ReceiveListener.handleEvent(Http2ClientConnection.java:357)

Windows Build 2176 outcome was FAILURE using a merge of 32bfc58b206351bfaaf7caa33563db00f63aeeda
Summary: Tests failed: 1 (1 new), passed: 2908, ignored: 613 Build time: 00:28:47
Failed tests
io.undertow.server.handlers.ChunkedRequestTrailersTestCase.testChunkedRequestsWithTrailers[proxy][http2-clear-upgrade]: Connection: keep-alive
Content-Length: 26

foo: fooVal
bar: barVal]
> but was:<HTTP/1.1 [500 Internal Server Error
Connection: keep-alive
Content-Length: 0
]
>
expected:<HTTP/1.1 [200 OK
Connection: keep-alive
Content-Length: 26

foo: fooVal
bar: barVal]
> but was:<HTTP/1.1 [500 Internal Server Error
Connection: keep-alive
Content-Length: 0
]
>
	at io.undertow.server.handlers.ChunkedRequestTrailersTestCase.testChunkedRequestsWithTrailers(ChunkedRequestTrailersTestCase.java:137)
------- Stderr: -------
18:22:43,020 DEBUG (XNIO-1 I/O-7) [io.undertow.server.handlers.proxy] <ProxyHandler.java:531> Sending request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} to target localhost/<IP_ADDRESS>:8888 for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
18:22:43,021 DEBUG (XNIO-1 I/O-7) [io.undertow.server.handlers.proxy] <ProxyHandler.java:548> Sent request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} to target <IP_ADDRESS> for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
18:22:43,022 DEBUG (XNIO-1 I/O-7) [io.undertow.client.http.HttpClientExchange] <HttpClientExchange.java:87> request terminated for request to localhost/<IP_ADDRESS>:8888 /
18:22:43,023 DEBUG (XNIO-1 I/O-7) [io.undertow.client.http.HttpClientConnection] <HttpClientConnection.java:451> connection to localhost/<IP_ADDRESS>:8888 is being upgraded
18:22:43,023 DEBUG (XNIO-1 task-26) [io.undertow.request.error-response] <DelegatingBasicLogger.java:424> Setting error code 500 for exchange HttpServerExchange{ POST / request {X-Forwarded-Server=[default], Upgrade=[h2c], HTTP2-Settings=[], Connection=[Upgrade, HTTP2-Settings], Trailer=[foo, bar], X-Forwarded-Proto=[http], X-Forwarded-Port=[80], X-Forwarded-For=[<IP_ADDRESS>], Transfer-Encoding=[chunked], Host=[default], X-Forwarded-Host=[default]} response {}}: java.lang.RuntimeException
	at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1392)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:387)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

18:22:43,026 ERROR (XNIO-1 task-26) [io.undertow.request] <Connectors.java:392> UT005071: Undertow request failed HttpServerExchange{ POST / request {X-Forwarded-Server=[default], Upgrade=[h2c], HTTP2-Settings=[], Connection=[Upgrade, HTTP2-Settings], Trailer=[foo, bar], X-Forwarded-Proto=[http], X-Forwarded-Port=[80], X-Forwarded-For=[<IP_ADDRESS>], Transfer-Encoding=[chunked], Host=[default], X-Forwarded-Host=[default]} response {}}: java.lang.NullPointerException
	at io.undertow.server.handlers.ChunkedRequestTrailersTestCase$1.handleRequest(ChunkedRequestTrailersTestCase.java:80)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:356)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

18:22:43,029 DEBUG (XNIO-1 I/O-7) [io.undertow.server.handlers.proxy] <ProxyHandler.java:673> Received response ClientResponse{responseHeaders={content-length=[0]}, responseCode=500, status='', protocol=HTTP/2.0} for request ClientRequest{path='/', method=POST, protocol=HTTP/1.1} for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}
18:22:43,030 DEBUG (XNIO-1 I/O-7) [io.undertow.request.error-response] <DelegatingBasicLogger.java:424> Setting error code 500 for exchange HttpServerExchange{ POST / request {Trailer=[foo, bar], Transfer-Encoding=[chunked], Host=[default]} response {}}: java.lang.RuntimeException
	at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1392)
	at io.undertow.server.handlers.proxy.ProxyHandler$ResponseCallback.completed(ProxyHandler.java:677)
	at io.undertow.server.handlers.proxy.ProxyHandler$ResponseCallback.completed(ProxyHandler.java:655)
	at io.undertow.client.http2.Http2ClientExchange.responseReady(Http2ClientExchange.java:134)
	at io.undertow.client.http2.Http2ClientConnection$Http2ReceiveListener.handleEvent(Http2ClientConnection.java:405)
	at io.undertow.client.http2.Http2ClientConnection$Http2ReceiveListener.handleEvent(Http2ClientConnection.java:357)

I can reproduce this error on master


Checkpoint 2 submission

@andela-nandaa Here's my submission for checkpoint 2

Current coverage is 80.45%

Branch #1 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


Use table prefix over explicit table name per model

Thanks for the PRs but this includes them all as it looks like your other commits have been pushed to your new branch. Could you fix this and the others and I'll merge them :smiley:

Thank you @deanperry, @adamcooke and everyone who has contributed to this so far.
These are now split up and should be ready to go. Sorry about the combined PRs, was hoping the last could be accepted as I couldn't run tests w/o the allow other DBs update, so things were fairly interdependent.
Have a good one and let me know if you need anything else for these!


116 add delete functionality

I conformed to the Pipeline by removing all unused imports changed controller functions to be async and return , this involved removing return statements with response objects, disabled a linter error requiring await, and made each controller match the async handler type


ModuleNotFoundError

I use pip3 install notion and python3 <myscript>
but i got
ModuleNotFoundError: No module named 'notion.client'; 'notion' is not a package
from notion.client import NotionClient

# Obtain the `token_v2` value by inspecting your browser cookies on a logged-in session on Notion.so
client = NotionClient(token_v2="daf3c6be-7944-4132-8b82-035310947d89")

# Replace this URL with the URL of the page you want to edit
page = client.get_block("https://www.notion.so/840b383b9c924efc9cfe3858159098ad")

print("The old title is:", page.title)

# Note: You can use Markdown! We convert on-the-fly to Notion's internal formatted text data structure.
page.title = "The title has now changed, and has *live-updated* in the browser!"

Traceback (most recent call last):
  File "notion.py", line 1, in <module>
    from notion.client import NotionClient
  File "/Users/nissen/code/notion/notion.py", line 1, in <module>
    from notion.client import NotionClient
ModuleNotFoundError: No module named 'notion.client'; 'notion' is not a package

I'm getting the same -- it works if I do the following in a python REPL, but not if I run the same commands in a script. I'm running both through Poetry, so I don't think it's a library path issue.
import notion
import notion.client
client = notion.client.NotionClient(token_v2=<TOKEN>)

Ah, you did the same thing that I did -- since your file is notion.py, Python looks for the Notion client stuff in that file, instead of the library. Rename the file and it'll work

I did the same thing too 😂

I did the same thing too 😂

Ah, you did the same thing that I did -- since your file is notion.py, Python looks for the Notion client stuff in that file, instead of the library. Rename the file and it'll work

I've got same problems when I import notion or notion.client.
My python file name is not 'notion.py' as well. Do you have other recommendation?

Thanks @neildryan I did the same thing too before finding this issue.
Probably the same for #253


[BACKLOG-40498] Added code changes in VFS dialog box in PDI to align browse button with Root path.

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 29m 39s
Build command:
mvn clean verify -B -e -Daudit -Djs.no.sandbox -pl \
plugins/connections/ui

:ok_hand: All tests passed!
Tests run: 5, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Support for Falcon 180B

It would be nice to support this recent, large model.

Blog: https://falconllm.tii.ae/falcon-models.html
Base model: https://huggingface.co/tiiuae/falcon-180B
Chat model: https://huggingface.co/tiiuae/falcon-180B-chat

We should enable fsdp and quantization during inference so that this can be run


Panic when too many point lights exist

Bevy version
bevy 0.6
Operating system & version
Windows 10
What you did
I created a simple system like this:

fn setup(
    mut commands: Commands,
) {
    commands.spawn_bundle(PointLightBundle {
        point_light: PointLight {
            color: Color::WHITE,
            ..Default::default()
        },
        transform: Transform::from_rotation(Quat::from_euler(EulerRot::XYZ, 0., 15., 30.)).with_translation(Vec3::Y * 3.),
        ..Default::default()
    });
}

and added it to the app like so app.add_system(setup);. This lead to the creation of an additional point light every frame
What you expected to happen
I'd expect the lights to eventually start getting ignored, but the system to keep running
What actually happened
The app ran for 255 frames, and panicked on frame 256 with the following error:
thread 'main' panicked at 'index out of bounds: the len is 256 but the index is 256', *PATH*\.cargo\registry\src\github.com-1ecc6299db9ec823\bevy_pbr-0.6.0\src\render\light.rs:650:9
Additional information
For my situation, I fixed things by moving to a startup system. However, this should not result in a panic either way.

Thanks for the report. I see what the problem is and I have indirectly fixed it in my branch that implements storage buffer support for point lights as I make sure to only take the first 256 lights to write into the uniform buffer when storage buffers are not supported. See here for more information: https://github.com/bevyengine/bevy/issues/3605 It would probably be better to only take at most 256 lights from the iterator, when there is a hard limit to adhere to.


Remove vendor-prot.scss file

@RishabhJain2018 i would like to work on this issue, can you assign it to me?


Bump the scala-storage version to 7.19.0

This should get us parallelism in the bag replications, which make them a bit faster and more efficient.
Closes https://github.com/wellcometrust/platform/issues/3727

(Failing Travis is because I accidentally pushed to master first, which triggered a build that I’ve cancelled.)


Broken links in the time travel docs

Docs: https://arkivanov.github.io/MVIKotlin/time_travel.html
There are broken links in the "Time travel client app for desktop" section.

Moved to https://github.com/arkivanov/MVIKotlin/issues/4


output df and raw data sample

Wouldn't it be nice to have samples each time you launch?

It should be a __repr__ for Items.
Like .head(), .tail() and .sample(5)

Hello @manycoding do you mean to add __repr__ to
https://github.com/scrapinghub/arche/blob/master/src/arche/readers/items.py#L16 ?

@kishan3 Yes, and after we can use it in #168


chore(deps): update dependency react-router to v5

This PR contains the following updates:

Package
Type
Update
Change

react-router
peerDependencies
major
2.8.1 -> 5.1.2

react-router
devDependencies
major
2.8.1 -> 5.1.2

react-router
dependencies
major
3.2.6 -> 5.1.2

Release Notes

ReactTraining/react-router
v5.1.2
Compare Source
List of commits
Bugfixes

Fix lingering <Link ref> error on React 15 (#6954)

v5.1.1
Compare Source
List of commits
Bugfixes

Fix issue with useParams reading from null object (#6940)
Fix regression passing ref to functional components in React <= 16.2 (#6934)
Fix regression passing empty string to matchPath (#6941)

v5.1.0
Compare Source
Read the blog post
List of commits
Features

Add useParams, useLocation, useHistory, and useRouteMatch hooks (d6224d6)
Add support for forwardRef in <Link> (b5528ed)
Add support for functions in <Link to> and <NavLink to> (#5331, #5368)
Add <Link component> API (#5437)

Bugfixes

Don't render <Route children> elements when the <Route> does not match (9665659)

v5.0.1
Compare Source
Changes
Updates

Reduced component depth in withRouter() HOC. (10d78bb)
Changed misleading warning when withRouter is used outside a Router (10d78bb)
Reduced install size and bundle size by switching to mini-create-react-context (992af48)

Bugfixes

Fixed display name for router context consumer and provider (6a99c93)
Fixed infinite loop caused by Redirect in some scenarios (017f692 and 2ce1d32)
Fixed license issue for react context polyfill (f9849c8, then 992af48)
Fixed Redirect throwing an exception in StaticRouter without context (3ccbd19)
Fixed regression in matchPath that caused an exception for empty paths (7bd1407)
Fixed page reload when an exception was thrown in Link onClick (82ce94c)
Fixed warning about createRef or useRef values in wrappedComponentRef when using withRouter() (56c829b)
Fixed withRouter() wrapped component inside NavLink not working properly (a38ef04)
Fixed CJS build - previously, incorrect exports were emitted (caa9950)

Thanks to @StringEpsilon for putting this list together. Enjoy!
v5.0.0
Compare Source
Note: While this does have a major version bump, it is actually a minor release. We screwed up some of the dependency version selection in 4.3.1, which necessitated a major bump. See this blog post for details.
⚠ Upgrade Warning ⚠
Please ensure you have upgraded both react-router and react-router-dom (react-router-native for RN users) to the exact same version. If different versions of those two packages are in your application, you will get errors when using <Link> and other react-router-dom-specific components. You can ensure you have the correct versions of both packages in your app using npm ls react-router react-router-dom.
Breaking Changes

Since the old context API is no longer used, any access to the old context will fail. Use of the react router context is not supported, please use  withRouter() or a <Route/> instead.
Due to the new context API, mixing of imports will now result in an exception:

// Be careful, this won't work anymore!
import BrowserRouter from 'react-router-dom/BrowserRouter';
import { Route } from 'react-router-dom';

<BrowserRouter>
  <Route />
</BrowserRouter>

Refactor as follows:
// These are both from the same build and use the same context object
// so there won't be a mismatch :)
import { BrowserRouter, Route } from 'react-router-dom';

In development mode, we now throw an error when using 2 different builds (see b2c6fa0), i.E. combining CJS imports with ESM imports.

New Features

<Route /> now supports an array of paths - #5889 (thanks @baronswindle)

<Route path={["/BigApple", "/NYC", "NewYork"]} component={NewYork} />

Full Changelog

<Route /> now supports multiple child nodes when using react >= 16.0.
Migrated to new react context API, with a polyfill for react versions < 16.2
Removed deprecated lifecycle methods componentWillMount and componentWillReceiveProps
Introduced more warnings in development builds
Changed build-process to rollup:

Smaller build size
Package now includes pre-minified files
Package now consists of single-file builds that include all modules.

Upgraded to history 4.9.0
Per file imports are deprecated and will be removed in a future major version. For now, a warning will be logged.
Made sure that react router conforms to react <StrictMode/>
Fixed <Link /> not working properly with target="_self" - #6138 (thanks @ericyang89)
Fixed  prop-type warning when using forwardRef - #6417 (thanks @frehner and @eXon)
Added support for createRef in  - #6567 (thanks @gcangussu)
Removed use of eval in development to be compliant with unsafe-eval CSP - #6611
Migrated to babel-preset-env
Improved testing infrastructure to improve developer workflow
Several docs improvements - #6410 (thanks @justsml)

v4.3.1
Compare Source
Just a patch to fix an accidental move of warning from a normal dependency to a devDependency, which was causing issues with installation.
v4.3.0
Compare Source
The major new things of this release are Redirect with params (see #5209) and the new generatePath API. We also cleaned up the code with Prettier, so browsing through it should be more enjoyable.
One other thing to mention, while I have your attention, is the deprecation of react-router-redux. It's no longer maintained and has a number of fundamental problems (particularly around time travel). Integrating Redux and the DOM History API is challenging because they don't maintain the same semantics and the resulting integration is error prone. Getting to the router context will be easier in future versions of React Router, so the main motivations for needing it will be going away. So, while I would advise against trying to integrate the two, for those that still want this functionality can turn to libraries like @supasate's connected-react-router.
Changes

Use the pretty option in generatePath (#6172 by @sibelius)
aria-current has incorrect value "true" (#6118 by @brandonrninefive)
Redirect with parameters (#5209 by @dlindenkreuz)
Fix with missing pathname: <Link to="?foo=bar"> (#5489 by @pshrmn)
Escape NavLink path to allow special characters in path. (#5596 by @esiegel)
Expose generatePath (#5661 by @rybon)
Use named import of history module. (#5589 by @RoboBurned)
Hoist dependencies for smaller UMD builds (#5720 by @pshrmn)
Remove aria-current from navLink when inactive (#5508 by @AlmeroSteyn)
Add invariant for missing "to" property on <Link> (#5792 by @selbekk)
Use Prettier on the code (e6f9017 by @mjackson)
Fix pathless route's match when parent is null (#5964 by @pshrmn)
Use history.createLocation in <StaticRouter> (#5722 by @pshrmn)

v4.2.0

Aug 23, 2017

Re-run Redirect on props update (#5162 by @alexilyaev)
Prevent remounts on routes with the same component in renderRoutes (#5430 by @artywhite)
Case sensitive routes (#5438 by @paustria)
Use direct imports in platform packages (#5095 by @ruiaraujo)
Add optional otherProps argument renderRoutes (#5137 by @jharris4)
Bump hoist-non-react-statics (#5347 by @roderickhsiao)
3x build speed improvements on CI (ea1212a by @timdorr)
Use Jest for testing (172dc16 by @mjackson)
Explicit error using Route outside of Router (#4939 by @eXon)
react-router-native Link improvements (#4816 by @benstepp)
aria-current on NavLink (#4708 by @JasonEtco)
Make AndroidBackButton a generic BackButton component (#5295 by @DonnieWest)
Access Link's underlying node via innerRef (#5294 by @danielberndt)
Return null from react-router-native DeepLinking if children is undefined (#5278 by @seekshiva)
Warn when using the history prop on a pre-configured Router (#5151 by @Aprillion)
Fix memory leak in ConnectedRouter during server side rendering (#5203 by @klis87)
Reorder NavLink activeClassName/className priority (#5109 by @carloluis)
Change react-native BackAndroid to BackHandler (#5093 by @SeanGroff)
Fix react-router-native StackRouter (#5071 by @kafein)

v4.1.1
Compare Source

Apr 12, 2017

Fixes for the various PropTypes related issues.

Note: This work is still ongoing, as the React team still has some outstanding issues to figure out themselves. Keep an eye on this issue and the prop-types repo for updates as we all work through this craziness.
v4.1.0
Compare Source

Apr 11, 2017

Add wrappedComponent to the component returned by withRouter
Add wrappedComponentRef prop to the component returned by withRouter
Add non-react static methods and properties of the wrapped component to the component returned by withRouter

v4.0.0
Compare Source

Mar 10, 2017

Released! No code changes from 4.0.0-beta.8

v3.2.6
Compare Source

Upgrade hoist-non-react-statics/react-is to support newer React APIs (#7182 by @henryqdineen)

v3.2.5
Compare Source

Fix React version detection for UNSAFE_ lifecycles (fixes issues with React 16.10) (#6961 by @henryqdineen)
Add element shape for Link's innerRef prop (#6886 by @nescalante)

v3.2.4
Compare Source

Add UNSAFE_ prefixes to deprecated lifecycle methods (#6883 by @bishwei)

v3.2.3
Compare Source
This release includes the missing UMD build from the 3.2.2. Sorry about that!
v3.2.2
Compare Source

React 16.6 support (#6806 by @arthur791004)
Access <Link>s underlying node via innerRef (#6340 by @pascalduez)

v3.2.1
Compare Source

React 16.3 support

v3.2.0
Compare Source

React 16 support

v3.0.5
Compare Source

Manually set displayName for components
Async hooks could be removed during simultaneous server requests (#4941 by @s-yadav)

v3.0.4
Compare Source

Fixes for React 15.5 deprecation warnings

v3.0.3
Compare Source

Fix webpack-related anonymous function issue (#4857 by @alisd23)
Fix usage with babel-plugin-transform-remove-prop-types (#4505 by @oliviertassinari)
Remove references to Link hash/query/state props (#4377 by @insin)

v3.0.2
Compare Source

Re-add module entry to package.json

v3.0.1
Compare Source

Pass transition hook's arguments correctly (#4123 by @arkist)
Fix index routes inside async pathless routes (#4147 by @taurose)
'to' maybe undefined (#4216 by @panzj)
Fix withRouter error when used without a Router (#4295 by @dropfen)
Adding support for escaped parentheses in Route Paths (#4202 by @sebastiandeutsch)

v3.0.0
Compare Source
🎉  The 100th release of React Router! 🎉
This release removes all the deprecation warnings from v2.x along with some bugfixes.
While the focus of this project is shifting towards the component-based v4, this branch will be maintained indefinitely!
Bug fixes will continue to be accepted. We are not going to leave anyone hanging and want to assure you that v3 development will be alive and well.
Changes

Oct 24, 2016

Removed
Bugfix: Cancel pending enter/change hooks on location change (#4063)

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


AWS elastic beanstalk files

Thanks for sharing this project.  I'm trying to setup something similar and looking at this project as an example.  I've read the Deployment wiki which mentions elastic beanstalk files however I don't see any checked into this repository.  Was wondering whether that's on purpose or are all those EB files not supposed to be checked in?  I guess I'm looking for examples.  If you could add some that would be great, if not then references to examples would help as well.

These files are generated by the Amazon eb CLI utility. You can see i've explicitly ignored these files from git, here:
https://github.com/0xadada/dockdj/blob/master/.gitignore#L34
I don't want them in the repo, because they could potentially vary from deploy to deploy, and even contain secrets.


Are FTP transfers possible?

Is it possible to download an IOS for example from an ftp server using netdev? ive tried with the below
        try:
            async with netdev.create(**conn[0], timeout=5) as ios:
                print('starting process on device {}.'.format(router_hostname))
                upload_ios = await ios.send_command('copy<EMAIL_ADDRESS>flash:')
        except:
            error = 'unable to connect to {} - {}'.format(conn[0]['host'], router_hostname)
            print(error)
            results.append(error)

debugging gives the below output
INFO:netdev:Host <IP_ADDRESS>: Reading until prompt or pattern
INFO:netdev:Host <IP_ADDRESS>: Disconnecting
INFO:netdev:Host <IP_ADDRESS>: Cleanup session
INFO:netdev:Host <IP_ADDRESS>: Exiting from configuration mode
INFO:netdev:Host <IP_ADDRESS>: Checking configuration mode
INFO:netdev:Host <IP_ADDRESS>: Reading until pattern
DEBUG:netdev:Host <IP_ADDRESS>: Reading pattern: LAB\-01\-R.*?(\(.*?\))?[\>|\#]
unable to connect to <IP_ADDRESS> - LAB 01

im guessing at this stage its not possible?
Thanks

Hello!
Yes, it's possible! In your example may be a problem in an interactive command copy ftp. Do you have file prompt quiet applied? Can you post the output of this command from ssh?

Thanks that works!


[Feature Request] Switch tab by click at top edge of window when maximized

Description of the new feature/enhancement
currently, when I maximize the window, and I cannot switch tab by click the top edge, which is inconvenient, and I have to move my mouse a little down to switch. in other product such as chrome, the tab table is against the top edge.

This gets annoying at times when working with different tabs and you have to do some back and forth tasks.

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2541 for more discussion.
/dup #2541


Can't add subdomain

I tried to add the subdomain to my vercel website, but it says this:

Photo: https://imgur.com/a/wtdR0nr

Strange, i will try to rollback the merge as it might be needed to update the vercel domain before updating the dns record...

The problem is, I can't add it as domain on vercel, because it says that some one else uses this domain

Try updating the domain on vercel now that the dns record no longer exists

I tried it, but it still says it

Strange, could be that it is taking time to update the internal records in the vercel database or the dns records havent fully updated yet. And that is only in case it is due to that reason.

Yes, that could be it, I answer you when I have time if it worked

Same issue!

It's literally there for all domains, someone added *.mod.land I guess

Same issue with netlify

Cloudflare dont like netfly and vercel


unconfirmed text of CJK IME collapse to one character in Integrated Terminal

The same root cause as https://github.com/Microsoft/vscode/issues/24557 and we need to fix this in Integrated Terminal (xterm.js) as well. We need to adopt next version of xtermjs once https://github.com/sourcelair/xterm.js/pull/632 is merged.

Due to functional regressions elsewhere with the proposed fix let's just live with the bad behavior until Chromium gets upleveled.

I believe this is fixed as we're no longer on Chromium 55/56


Translation of Webpart

Hi, sorry that this is only a question but i dont know where to tell this ;-)
Is there anyway to translate the webpart to another question? For the content i can use my own repository but i would like to translate the Webpart.
Thanks

The code for the web part is not publically available so there is no way for you to translate it.  The version 4 release that includes multilingual capabilities will give you translation for 8 languages, details here: https://docs.microsoft.com/en-us/office365/customlearning/custom_featureupdates


Rounding error while printing solution of "Exercise: Custom Controlled Rx gate" in docs/tutorials/educators/intro.ipynb

Description of the issue
In file docs/tutorials/educators/intro.ipynb, section Exercise: Custom Controlled Rx gate, the exercise requires you to customize a controlled Rx gate. The solution code provided for the exercise is
#@title Expand to view the solution
"""Defining a custom controlled cirq.Rx gate."""
class CRx(cirq.TwoQubitGate):
    def __init__(self, theta):
        self.theta = theta

    def _unitary_(self):
        return np.array([
            [1, 0, 0, 0],
            [0, 1, 0, 0],
            [0, 0, np.cos(self.theta/2), -1j * np.sin(self.theta/2)],
            [0, 0, -1j * np.sin(self.theta/2), np.cos(self.theta/2)]
        ])

    def _circuit_diagram_info_(self, args):
        return '@', 'Rx({}π)'.format(self.theta / np.pi)

# Print out its unitary.
print(np.around(cirq.unitary(CRx(0.5 * np.pi))))

If you run this solution code, it will return
[[1.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 1.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 1.+0.j 0.-1.j]
 [0.+0.j 0.+0.j 0.-1.j 1.+0.j]]

which is not a unitary matrix.
This is because of the use of function np.around without specifying number of decimals:
print(np.around(cirq.unitary(CRx(0.5 * np.pi))))

so it will round the decimal to one digit.
Cirq version
0.10.0

Thank you for catching this.
I've renamed the title as the solution of the exercise is correct (i.e. the custom CRx gate defined is correct) but printing the unitary matrix of this custom gate has a rounding error.


Cmake Error

My os is ubuntu 20.04.An error occurred when I executed the command "cmake -DCMAKE_BUILD_TYPE=Release ..
".CMake Error at CMakeLists.txt:81 (find_library):
Could not find McCalib using the following names:
Please provide a clear and concise description of what the issue / bug is.

Hi @hongche63, glad to find you using MC-Calib! Can you help me assess the problem by providing me more details about the error? Also, did you find the provided docker command working instantaneously?

Thanks for your reply, the problem is solved.But when I detect my fishimages dataset,the bug is appeared
../modules/calib3d/src/fisheye.cpp:713: error: (-215:Assertion failed) !objectPoints.empty() && !imagePoints.empty() && objectPoints.total() == imagePoints.total() in function 'calibrate'
my fishimage's size is 960*600 and the square_size is 0.02423,one of my fishimage is as follows

my calib_param_synth.yms is setted as follows
%YAML:1.0
######################################## Boards Parameters ###################################################
number_x_square: 10         # number of squares in the X direction
number_y_square: 7         # number of squares the Y direction
resolution_x: 960          # horizontal resolution in pixel
resolution_y: 600          # vertical resolution in pixel
length_square: 0.004        # parameters on the marker (can be kept as it is)
length_marker: 0.003        # parameters on the marker (can be kept as it is)
number_board: 1            # number of boards used for calibration (for overlapping camera 1 is enough ...)
boards_index: []           # leave it empty [] if the board index are ranging from zero to number_board; example of usage boards_index: [5,10] <-- only two board with index 5/10
square_size: 0.02423         # size of each square of the board in cm/mm/whatever you want
############# Boards Parameters for different board size (leave empty if all boards have the same size) #################
number_x_square_per_board: []
number_y_square_per_board: []
square_size_per_board: []
######################################## Camera Parameters ###################################################
distortion_model: 1             # 0:Brown (perspective) // 1: Kannala (fisheye)
distortion_per_camera : []         # specify the model per camera, #leave "distortion_per_camera" empty [] if they all follow the same model (make sure that the vector is as long as cameras nb)
number_camera: 2           # number of cameras in the rig to calibrate
refine_corner: 1           # activate or deactivate the corner refinement
min_perc_pts: 0.5           # min percentage of points visible to assume a good detection
cam_params_path: "None"   # file with cameras intrinsics to initialize the intrinsic, write "None" if no initialization available
fix_intrinsic: 0 #if 1 then the intrinsic parameters will not be estimated nor refined (initial value needed)
######################################## Images Parameters ###################################################
root_path: "../data/Blender_Images/fishimages_l_r/Images/"
cam_prefix: "Cam_"
keypoints_path: "None" # "None" #
######################################## Optimization Parameters #############################################
quaternion_averaging: 1    # use Quaternion Averaging or median for average rotation
ransac_threshold: 10       # RANSAC threshold in pixel (keep it high just to remove strong outliers)
number_iterations: 1000    # Max number of iterations for the non linear refinement
######################################## Hand-eye method #############################################
he_approach: 0 #0: bootstrapped he technique, 1: traditional he
######################################## Output Parameters ###################################################
save_path: "../data/Blender_Images/fishimages_l_r/Results/"
save_detection: 1
save_reprojection: 1
camera_params_file_name: "" # "name.yml"

Thank you very much for using MC-Calib. This error occurs because the board cannot be detected. Based on the image you have shared, it seems that you are not using the charucoboards generated by MC-Calib for this calibration, hence the inability to detect it. Please refer to Step 1 in the calibration procedure explained in the README of this repository. If you use the proper boards, it should work very well for your use case.
Additionally, regarding your configuration file, the parameters resolution_x and resolution_y represent the resolution of the calibration board you intend to generate, not the image resolution of the camera you are calibrating.
I hope this helps. Please do not hesitate to contact us if you encounter any additional issues.

Thank you very much for your reply.If I use the board that not charuco but rather checkboard.how I modified apps/calibrate/calibrate.cpp

Thank you very much for your reply. If I use the board not charuco but rather checkerboard.How I edited the calibrate.cpp

This toolbox has been specifically designed to work using fiducial markers. I am afraid the required modifications will be too complex, and it will also make MC-Calib unable to work when multiple checkerboards are used. So I would just recommend you to print yet another board if possible


Most Inst* types don't satisfy the Instruction interface?

Most Inst* types (e.g, InstAdd) don't satisfy the instruction interface; here are the few that do:
https://github.com/mewmew/l/blob/935e562f92c3ad2bd406e7c262c0497afaddcce8/ir/sumtypes.go#L116-L120
And therefore won't fit into the (*BasicBlock).Insts field? https://github.com/mewmew/l/blob/935e562f92c3ad2bd406e7c262c0497afaddcce8/ir/basic_block.go#L20-L29
Am I missing something? How far off is this from being able to be used? I'd like to help, if I can with a reasonably small time investment.
I see also that Insts can't be used as values, so it's not clear how to build the IR at the moment.

Just found my way to https://godoc.org/github.com/mewmew/l/ir#LocalDef, which answers part of the question :)
https://github.com/mewmew/l/blob/935e562f92c3ad2bd406e7c262c0497afaddcce8/ir/instruction.go#L15-L21

This is obviously it.

Hi @pwaller. Glad you found it. Yes, you are right, LocalDef is indeed the way to go. The basic idea being that not every instruction is a value. So LocalDef is used to distinguish this fact.
Good catch though, I'll add this to the documentation of value.Value to make it more clear for future use.


Implement Debug for http::response

All types should implement Debug where possible.

thanks, merged: 56e636616668264a681c684a91cc249577de7ec8


Profiles empty

Hi @dbrent-amazon , I came to this page because I need some help. I already read the amazon advertising docs but there's no part of the docs that help me solve my issue. I followed everything, from setting up the account access to all apis, and even implemented the LWA in frontend side. Using sandbox its all good, since sandbox allows to create a profile(both seller and vendor) I can test all endpoint to get dummy data using the created profileid in sandbox. But when I switch to real endpoint, the profiles has no result. I have a potential customer with seller account and we tried to test the LWA in our frontend, it authorised my app, no errors returned, and it return the correct profile information about the seller, but I dont see any information that relates to a profile id. The only fields it returned are customer id, email and name(its also in LWA docs, so the returned data are correct). I can confirm my potencial customer has campaigns, hes doing it for more than a year, and he even give me  access to his google data studio dashboard that shows all his data, like Sponsored Products, Sponsored Brand, search terms etc. Is there any additional steps that needs to be done? Thanks

Did you find a solution to this @ianrussel ?

@saleweaver yes. If you encountered same issue you need to create a ticket in thier jira support because it is related to setting your credentials


Remove badges until red status is fixed

Since https://github.com/kubernetes/test-infra/issues/9628 isn't yet
fixed, the badges are all red even though the most recent runs were
successful.
Even once that is fixed, the badges could still become red from failure
on PRs.
Removing for now since they are making us look bad for no good reason XD
At least we still get the report card:

That’s okay, you have a good point:)


proposal: mime/multipart.Reader should use sync.Pool and reuse bytes.Buffers to reduce memory allocation pressure

https://github.com/golang/go/blob/59413d34c92cf5ce9b0e70e7105ed73a24849b3e/src/mime/multipart/formdata.go#L59
We have a upload server using req.ParseMultipartForm. GOGCTRACE  tells us gabarage collector takes 8% cpu usage and the heap profile tells us mine/multipart.Reader.ReadForm allocates lots of memory.

Thank you @SunRunAway for reporting the issue.
Would you mind elaborating more on what you would like to have this issue to solve?

hi, @odeke-em
I've send a CL. https://go-review.googlesource.com/c/56990

One small issue is that we try to avoid using a sync.Pool for buffers that are ever observed by user space. So if Reader calls some arbitrary io.Reader's Read method to fill in the buffer, it should not go back into the pool, to avoid a dangling pointer bug in that Reader from corrupting some future unrelated call.

@rsc Sorry, I cannot understand. Could you give an example please?

Alternative fixes would involve making the multipart.Reader re-usable by supporting a Reset method and store a bytes.Buffer as well as a buffer for io.CopyBuffer inside it for re-use. So the http library can do the re-use and pooling on request level.

Hi, do you have any suggestion to do or decision about this issue & CL?

One small issue is that we try to avoid using a sync.Pool for buffers that are ever observed by user space. So if Reader calls some arbitrary io.Reader's Read method to fill in the buffer, it should not go back into the pool, to avoid a dangling pointer bug in that Reader from corrupting some future unrelated call.

This restriction sounds strange. It is based on a weird corner case that should never happen in real code. How many io.Reader implementations exist in the wild that keep references to buffer memory passed into Read call and then modify this memory after returning from Read call? I think the number of such io.Readers is close to 0. Additionally, race detector should detect such cases.

It is based on a weird corner case that should never happen in real code.

In general all reasons not to perform optimizations fall into that category. I'd still like to keep bad code in one package from causing mysterious failures in an unrelated package, and that's the motivation for the restriction I described.
On the other hand it sounds like you have a significant opportunity to make your server faster. The question is whether there's a way to do it at a slightly higher level and avoid the possible corruption in buggy code.

Alternative fixes would involve making the multipart.Reader re-usable by supporting a Reset method and store a bytes.Buffer as well as a buffer for io.CopyBuffer inside it for re-use. So the http library can do the re-use and pooling on request level.

The multipart.ReadForm has a for loop to handle more than one file, if do it in the http library the bytes.Buffer stored in multipart.Reader could be used by multiple files. The code may be complex.
Another con is the re-use cycle will persist until the http library calls MultipartForm.RemoveAll() wether the file stored in temperary file or not.

Per https://github.com/golang/go/issues/21516#issuecomment-325471155 above, do you have a revised API suggestion?


Improve performance of bbe::String quite a bit (~35%) with reducing logic in growIfNeeded

Good work! :+1:


[BUG] Harvester's VM Config Form, SSH Key section overfills tag area

Describe the bug
UI Based, SSH Key that gets displayed in SSH Key tag on Editing of VM Basics section overflows from the contained HTML element
To Reproduce
Steps to reproduce the behavior:

Go to Advanced -> SSH Keys
Create an SSH Key in Default namespace with a title of something like "caddy-ssh-key"
Create a VM, leverage that SSH Key
Navigate to Edit that VM, notice that the Basics -> SSHKey section is overfilled with SSH Key title

Expected behavior
The contents of the SSHKey displayed on Basics of form to not overfill tag area
Environment

Harvester ISO version:  Version: v1.1-a72900af-head  (03/01/23 - v1.1 head)
Underlying Infrastructure: Baremetal, 3 Node ThinkCentre Cluster w/ NVMe Drives

Additional context
Similar to:
https://github.com/harvester/harvester/issues/3527
Supporting Screenshot:

This looks good, in v1.1.2-rc3 - thanks for the fix @n313893254 :smile:
I'll go ahead and close this out:


Vector Search - Azure Cosmos DB for MondogDB - Invalid json for creating vector index

Json's missing a comma after nProbes

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

ID: 5e53e4aa-c504-448b-9598-419eda127192
Version Independent ID: 79fdea2a-5317-4996-a2b1-57662c2b9aa0
Content: Vector Search - Azure Cosmos DB for MongoDB vCore
Content Source: articles/cosmos-db/mongodb/vcore/vector-search.md
Service: cosmos-db
Sub-service: mongodb-vcore
GitHub Login: @gahl-levy
Microsoft Alias: gahllevy

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

@animalnots, this code sample has now been updated and the issue is resolved in the latest version (which is slightly different).
#please-close


Configurable tag name for the vault signs.

Example: [<name>]. Idea by mc_tech on spigot.org

Fixed on 399a2af3f207838a45e69784e6d3ba955ea34b68


Fixed "maximum recursion depth exceeded" issue in custom component

This fixes a RecursionError in the custom component.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 374, in _async_add_entity
    suggested_object_id = entity.name
  File "/config/custom_components/mercedesmeapi/resources.py", line 74, in name
    return f"{self._vin}_{self.name}"
  File "/config/custom_components/mercedesmeapi/resources.py", line 74, in name
    return f"{self._vin}_{self.name}"
  File "/config/custom_components/mercedesmeapi/resources.py", line 74, in name
    return f"{self._vin}_{self.name}"
  [Previous line repeated 986 more times]
RecursionError: maximum recursion depth exceeded

Thank you so much!


[WIP] Versioning pipeline fix

Description
This commit allows to launch both unit/integration and e2e tests related
to a tagged codebase.
Fixes #(issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Pull Request Test Coverage Report for Build 308324193

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 47.779%

Totals

Change from base Build 302096135:
0.04%

Covered Lines:
6238

Relevant Lines:
13056

💛  - Coveralls


Typo in instructions.md

Hey,
there is a little typo at line 55 in the instructions.md. The last 2 words ... prodiction envorinment.. Should be production environment.

PR Please


Cannot instantiate std.container.Array with immutables or consts as T

maidenphil reported this on 2014-08-04T18:39:48Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=13254
Description
Using dmd distribution 2.065. This does not compile:

std.container.Array!(immutable(dchar)) array;

Error:

The error seems to be caused because Array.Payload uses destroy on an immutable type and that makes the compiler cry. I see that the code has been updated to support "elaborate destructors", but I don't think it will prevent the problem.

Thx!

maidenphil commented on 2014-08-06T19:12:55Z
(In reply to Phil Lavoie from comment #0)
> Using dmd distribution 2.065. This does not compile:
>
> std.container.Array!(immutable(dchar)) array;
>
> Error:
>
> The error seems to be caused because Array.Payload uses destroy on an
> immutable type and that makes the compiler cry. I see that the code has been
> updated to support "elaborate destructors", but I don't think it will
> prevent the problem.
>
> Thx!

If a struct can have an elaborate destructor and be const/immutable at the same time, this seems like it will not compile.


Investigate E2E tests CI inconsistency

For some reason our E2E tests fail randomly during CI. We need to try to understand what is happening so that we don't need to be rerunning the same test suite over and over again until it passes successfully.

https://github.com/Stand-With-Crypto/swc-web/actions/runs/9862474116/job/27233131553 example


Remove AbstractLocalVariable::getNode()

Type: refactoring
AbstractLocalVariable::getNode() was a bit of an odd ball, it doblede as null check and an unwrapper depending on where it was uded, in actuality there was only one spot that it was needed and it somewhat obscures the types (dealt with in the PHPStan 4 PR) and had incorrect return values. Instead I have remove the function and unwrapped the node in the place it was actual needed. So at this point the function no longer serves a purpose.

Thanks :)


Add @Security to route group or middleware

I've a route group that uses a route middleware to authorize users. It'd be easier to add @Security tag to the group or to the middleware somehow, rather than to each route specified in the group.
Something like this.
@Security ApiKey
privateGroup := srv.Group("/private")

Framework : gin

@nnanto
I'm afraid it's not possible at the moment since swag doesn't parse annotations/comments in the function body and doesn't analyze in any way the definition of the function or variable the annotation text was written.
Such an Implementation may require swag to analyze your go code flow, assemble it, and apply this kind of general tag you are speaking about. This will introduce more code complexity, computational time, and memory usage.