plan to integrate testnet4

since testnet3 is unusable, is there a plan to utilize testnet4 as discussed here: https://github.com/bitcoin/bitcoin/pull/29775 ?

as an aside to this, I saw today that the latest version of Sparrow (v1.9.1) has integrated testnet4 https://x.com/SparrowWallet/status/1790312602918126026

We'll definitely run it as soon as it is in a release version of Bitcoin Core

@raphjaph Do you have plans for releasing support for testnet4? Bitcoin Core 28.0 was released recently.

As soon as I merge https://github.com/ordinals/ord/pull/3962 ord will be compatible with v28

@raphjaph I just tried running ord on testnet4 but bitcoind uses port 48332 by default. Setting that to 18332 results in this error:
Oct 23 01:43:12 testnet4-deployment sh[30535]: error: Failed to connect to Bitcoin Core RPC at `<IP_ADDRESS>:18332/`:  JSON error: invalid value: string "testnet4", expected bitcoin network encoded as a string

Might be an issue you'll need to reopen this for.

You'll have to change some parsing logic in the code, we look for testnet3 in places instead of testnet4. We're not going to officially support testnet4 until next year because we only want to support one testnet

testnet3 transactions fee are >4000 sats/vB, making it unusable because there are no faucets that give enough sats.
I've moved to testnet4, but now I need ord or unisat.io or ordinals.com to support testnet4.
I tried search-n-replace of testnet3 to testnet4 but the error persists.
Does anyone have a fork of ord that supports testnet4 today?

you could also try signet.  Thank you!
And it seems ordinals.com supports signet, https://signet.ordinals.com

#4135


Robust WebBLE UART + partial partial flashing service

Reliability work around WebBLE support. Once the device is paired, the editor will reconnect after reset and/or USB flashing and/or WebUSB flashing.

refactoring services
better handling of disconnection
automatic reconnection for UART
start of the partial flash service

@mmoskal ready for review


[#117325229] Add support for specific http check attributes

#117325229 Make Terraform Pingdom provider generate HTTPS checks
What
Pingdom API supports define several specific attributes for HTTP checks, but go-pingdom doesn't manage them.
This functionality will be later used for This functionality will be later used for https://github.com/alphagov/paas-terraform-provider-pingdom/pull/1
How review test this?
See commits for implementation details.
You can run the test suite by running:
go get -d github.com/russellcardullo/go-pingdom
cd $GOPATH/src/github.com/russellcardullo/go-pingdom
git remote add alphagov git@github.com:alphagov/paas-go-pingdom.git
git fetch alphagov
git checkout feature/specific_http_check_attributes

go get ./...

make test

Who?
Anyone but @keymon or @jimconner

The README still says "This currently only supports working with basic HTTP and ping checks."

Thx
On 19 April 2016 at 16:38, saliceti<EMAIL_ADDRESS>wrote:

The README still says "This currently only supports working with basic
HTTP and ping checks."
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/alphagov/paas-go-pingdom/pull/1#issuecomment-211983713

--
Regards
Hector Rivas | GDS / Multi-Cloud PaaS


[UI] Design Configurator: Component dropdown should open downwards

Current Behavior
In the Design Configurator (http://localhost:9081/configuration/patterns), the component list opens upwards.

Desired Behavior
This list should open downwards.

Contributor Guides and Resources

🎨 Wireframes and designs for Meshery UI in Figma
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Can I work on this issue? @leecalcote

Sounds real good.

@sidd-oo Any updates? Need help with this?

@sidd-oo Any updates? Need help with this?

Sorry for the delay, I am on it.  @Chadha93

@sidd-oo any progress or blockers here?

@Chadha93 you can assign this to me

@Chadha93 you can assign this to me

Sure, thanks for heads up  @Harshit-Dandriyal


False positive for react/prop-types props validation (stateless component)

I'm getting an error for a prop missing in props validation, when the prop is included the prop-types, similar to #258.

eslint version v3.2.2
eslint-plugin-react v6.0.0

Here's the error:
% eslint test.js

/Users/lauren/Projects/eslint-error/test.js
  10:31  error  'onChange' is missing in props validation  react/prop-types

✖ 1 problem (1 error, 0 warnings)

Here's the code:
import React       from "react";
import Slider      from "./slider";

const StatelessCell = props =>

         props.onChange(e)} />
        <Slider value={props.severity}
            onClick={severity => props.onChange({severity})} />
        <Slider value={props.severity}
            onClick={severity => props.onChange({severity})} />

;

StatelessCell.PropTypes = {
    severity: React.PropTypes.number,
    onChange: React.PropTypes.func.isRequired,
};

export default StatelessCell;

Here's my .eslintrc.json:
{
    "env": {
        "browser": true,
        "es6": true,
        "node": true
    },
    "extends": [
        "eslint:recommended",
        "plugin:react/recommended"
    ],
    "parserOptions": {
        "ecmaFeatures": {
            "experimentalObjectRestSpread": true,
            "jsx": true
        },
        "sourceType": "module"
    },
    "plugins": [
        "react"
    ],
    "rules": {
        "no-console": [
            "error",
            {
                "allow": ["warn", "error"]
            }
        ],
        "indent": [
            "error",
            "tab",
            {
                "SwitchCase": 1
            }
        ],
        "linebreak-style": [
            "error",
            "unix"
        ],
        "quotes": [
            "error",
            "double"
        ],
        "semi": [
            "error",
            "always"
        ],
        "no-unused-vars": [
            "error",
            {
                "vars": "all",
                "argsIgnorePattern": "^_$"
            }
        ],
        "comma-dangle": [
            "error",
            "always-multiline"
        ],
        "no-shadow": [
            "error", { "hoist": "never" }
        ]
    }
}

I get the same, and also a displayName missing error too:
import React, {
  PropTypes,
} from 'react';

import {
  NavigationExperimental,
  StyleSheet,
  View,
} from 'react-native';

import Tab from './tab';
import withNavigate from './with-navigate';

const {
  PropTypes: NavigationPropTypes,
} = NavigationExperimental;

const TabList = withNavigate(props => {
  return (
    <View style={styles.tabs}>
      {props.navigationState.routes.map(renderTab(props))}
    </View>
  );
});

const renderTab = props => {
  return (route: Object, index: number): ReactElement => {
    return (
      <Tab
        key={route.key}
        route={route}
        selected={props.navigationState.index === index}
      />
    );
  };
};

TabList.displayName = 'TabList';
TabList.propTypes = {
  navigationState: NavigationPropTypes.navigationState.isRequired,
  navigate: PropTypes.func.isRequired,
};

const styles = StyleSheet.create({
  tabs: {
    flex: 1,
    flexDirection: 'row',
  },
});

export default TabList;

I'm using the react/recommended config

+1

+1

+1

Please do not comment with "+1", it adds noise and adds no value - please show your support by adding a reaction emoji to the original post. I'll delete all the existing +1 comments, and any future ones.
Thanks for participating!

From the original question, is it possible there's a capitalization issue?
StatelessCell.PropTypes vs StatelessCell.propTypes

@dobesv wow, I think you've nailed it - @laurenkt if you capitalize it propTypes, does your problem go away?

Yes! That's it! Can't believe that one passed me by for most of a year.. doh. I'll close this now. Thanks everyone.


AssertionError: Unhandled Option

Hi Jack,
Nice work.  In port_force.py, an extra : is needed between h and t:
opts, args = getopt.getopt(sys.argv[1:], "ht:p:u:P:", ["help", "target", "port", "user=", "pass="])

Thanks for catching that, and thank you for contributing!
I just pushed out the fix.
Cheers!


Reuse Panoptes User and Project IDs for Subscriber and List IDs

Current Behavior: The daily listmonk sync job drops current subscribers and lists, importing new values with IDs that are incremented to ever-higher values. The downsides to this: links between campaigns and lists are broken, causing campaigns to error when accessed or cloned after a sync; analytics are also broken after the initial day of reporting due to broken links to deleted resources.
Desired Behavior: Re-use Panoptes IDs for users and projects as subscriber and list IDs in listmonk.  Panoptes already ensures that IDs of both types are unique so they should be valid for listmonk internal use.  Panoptes-based IDs will allow day-to-day continuity for list IDs, making it so linkages are not broken in the sync.  Panoptes-based subscriber IDs are also more meaningful in logs providing direct and easy mapping to Panoptes users.
NOTE: non-project lists (announcements, NASA, beta lists) all need to be handled as special cases with fixed IDs because they don't have corresponding Panoptes project IDs.
Attn: @zwolf

Specifics regarding IDs
users->subscribers: use zooniverse user ID for subscriber ID
project->lists: use zooniverse project ID for list ID, but for announcements / beta / nasa use integers like 9XXXXX (e.g. 900001)

Final task related to this issue: now that #4 provides us consistent list and subscriber IDs, we can relax some of the table truncations currently carried out in the sync.  Currently, the CASCADE option is leading to the following table truncations:

listmonk.truncate_subscribers_table: subscribers, subscriber_lists, campaign_views, link_clicks, bounces
listmonk.truncate_lists_table: lists, subscriber_lists, campaign_lists
listmonk.truncate_subscriber_lists_table: subscriber_lists

Only the three main tables, (subscribers, lists, subscriber_lists), need to be truncated. All others are OK (and preferred!) to persist across each sync.


add copyAllToNewFile

Merged - thanks! :+1: This will ship with v0.3.1.

No probs - thanks for giving it a home

Any time. If you have any suggestions or features... you know where to send 'em. :smile:


update german translation

Thanks for the update. I don't know if you noticed but there are 33 commits in your pull-request. Only the last one is relevant.


go.mod, vendor: bump github.com/go-openapi/strfmt to v0.20.2

This will also bump the transitive dependency
go.mongodb.org/mongo-driver to v1.5.1 in order to fix CVE-2021-20329
Ref. https://github.com/advisories/GHSA-f6mq-5m25-4r72

AKS is the only failing test and it's failing presumably because of an AKS infrastructure issue. Given this is a security fix, I'll thus merge this PR.


Prioritize more integration testing pipelines before merging PRs on tidb

Now, before merging a PR in the tidb repository, several pipelines are triggered to validate and ensure the quality of the PR. These pipelines typically consume fewer resources and have shorter execution times.

build
unit-test
check
check_dev2
mysql-test

Meanwhile, after the PR merge, more integration testing pipelines will be triggered based on the newly merged commit to ensure the code quality of the master branch. These integrated tests typically have high concurrency, require significant resources, and take a relatively long time to execute.

integration-br-test
mysql-connector-test
integration-sequelize-test
integration-prisma-test
integration-python-orm-test
tiflash-test
integration-copr-test
sqllogic-test
integration-mysql-test
integration-jdbc-test
integration-ddl-test
integration-common-test
common-test
e2e-test

For the pipelines that must be run before merging PRs, in order to ensure efficiency and user experience of PR merging, we have put forward the following requirements.

The stability of test cases is extremely important. The stability of testing should not be lower than 95%. Unstable test cases need to be fixed within one day.
Reasonable resource consumption, it is recommended to not exceed 8 cores and 16GB for resource allocation.
The execution time should be reasonable, preferably less than 15 minutes. If it exceeds half an hour, the development experience will significantly decrease.

@purelind
Any updates?
if it is not finished, please move it to next milestone.

done


Added 'per shard' HTTP query handler

WHAT: This PR adds a “per shard” HTTP query handler and endpoint.
WHY: We use this at Square to populate our graphite frontend with all of our metrics. We do it “per shard” instead of querying for “all” at once is because a large request for all metrics at once gave us all sorts of problems with GC, request timeouts, etc.
HOW: Added a HttpShardedMetricsHandler.java class that takes in a shard number and a corresponding endpoint in HttpMetricsIngestionHandler.java.
Not sure if this would be useful in general, but I thought I'd open this so you guys can take a look. Let me know what you think!

Coverage decreased (-0.3%) to 78.323% when pulling 53232f126ca4c3fb609b118129e036762b58d74f on DanielNi:http-metrics-shard-handler into dcdf3e33fbe4d7b12b1cb6575ae389ddccd9517b on rackerlabs:master.

Other than the comment I had, everything else looks good.

Coverage decreased (-0.3%) to 78.345% when pulling 5c8f9f5a0bd595fc6c40374e66017689ccbaa2f3 on DanielNi:http-metrics-shard-handler into dcdf3e33fbe4d7b12b1cb6575ae389ddccd9517b on rackerlabs:master.

I am not sure I like exposing the notion of "shard" to the Blueflood API. To me, shard is an internal grouping of work for blueflood nodes. But I will discuss this with my team and get back to you.

That makes sense; our intent with this endpoint was to quickly query for all metrics in Blueflood without the associated problems with such a large request. If there is a better way to do this without exposing the concept of "shard" I would love to hear it!

There is also /metrics/search API which is powered by elastic search, using which you can query for all metrics belonging to a tenant. It supports glob search.

@DanielNi , that's funny.... because yesterday while discussing this with my team, I came across a similar thought... You could write a Java standalone program that queries Cassandra directly, maybe? I don't know how exactly you would be consuming the output of this.
I take it you guys don't use ElasticSearch ? We have a python project:
https://github.com/rackerlabs/blueflood-graphite-finder
that maybe is doing the same thing as what you are doing. We use this to serve Grafana a drop down list of metric names. Internally, it uses /v2.0/{tenantId}/metric_name API. I am failing to find the docs for this tho... I'll get back to you on this.

We don't use ElasticSearch, but we have a Java layer in between Blueflood and Graphite (that queries this endpoint) which seems to do something similar to blueflood-graphite-finder. I'll have to look into the API some more, but I think modifying this layer to talk to Cassandra directly might be the way to go.
Thanks for the suggestions! Feel free to close this PR if it's no longer relevant.

Closing PR as we have discussed this feature is best implemented outside Blueflood.


After latest UI fixes steam client enters an update loop (gamescope-session)

With commit  1d4fd86882bed4aa42a925edccf44cb3e90aee90 the steam client enters an unending update loop. You have to stop steam-patch for the loop to cease. I haven't suffered it with the desktop client.
Yesterday it worked fine and survived a couple of reboots. Today the first boot was ok too. Now every boot/change to gamescope-session is affected.
Using a binary compiled before the mentioned commit the steam client does not enter the update loop.
 I'll fix it within this week.

thank you steam-patch is amazing and we appriciate your work on this

It's solved in this fork https://github.com/corando98/steam-patch
It also solves https://github.com/Maclay74/steam-patch/issues/6 , adds GPU Clock slider, etc.

@corando98 would you mind to merge it?
I don't think it makes much sense to maintain two repositories for the same purpose?

@Maclay74 I'll clean up the branch a bit more then merge if that is fine with you, need a couple more testing to see that it's good.

Sure, take your time. Thanks for your work, it's very impressive and helpful!

Hey @corando98, how is going? Do you think we can merge your changes?


Sqlite Load Extension Error

Hi,
Im getting this error:
https://github.com/ezored/ezored/runs/2701829983?check_suite_focus=true#step:12:1296

[ 71%] Building CXX object source_subfolder/CMakeFiles/SQLiteCpp.dir/src/Statement.cpp.o
/Users/runner/.conan/data/sqlitecpp/3.1.1/_/_/build/518d5483cdb53cc130fd28cdad883cd2b4d0a54f/source_subfolder/src/Database.cpp:213:11: error: use of undeclared identifier 'sqlite3_load_extension'
[ 85%] Building CXX object source_subfolder/CMakeFiles/SQLiteCpp.dir/src/Transaction.cpp.o
    ret = sqlite3_load_extension(getHandle(), apExtensionName, apEntryPointName, 0);
          ^
1 error generated.
make[2]: *** [source_subfolder/CMakeFiles/SQLiteCpp.dir/src/Database.cpp.o] Error 1

This is strange because with version "2.5.0" the problem don't happen, but only with "3.1.1".
And it only have problem when compile for iOS:

Can you help me?

Hi,
Fixed in conan python file to disable it by variable passed to sqlite3.

Hi,
We need an option to sqlitecpp to disable load_extension. We have one to sqlite3 and we need one for sqlitecpp.

I made a patch here:
https://github.com/conan-io/conan-center-index/pull/7486

And a patch locally here:
https://github.com/SRombauts/SQLiteCpp/pull/338


Typo in the description

Greetings!
It says "Chýtrá palice" instead of "Chytrá palice". It really makes me feel uneasy and ruins the user experience.
Thanks for the fix!

Thanks, fixed.


Problem with Java 8 LocalDateTime

I have a Scope class like that
class Scope implements Serializable {
        private String scope;
        private Status status;
        private LocalDateTime expiresAt;
        // ...
 }

and use it to map with a PostgreSQL jsonb column
class Approval implements Serializable {
    @Type(type = "jsonb")
    @Column(columnDefinition = "jsonb")
    private Set<Scope> scopes;
    // ...
}

It works but the data store in jsonb column was
[
  {
    "scope": "all",
    "status": "APPROVED",
    "expiresAt": [2018, 9, 14, 9, 35, 28, 909000000]
  }
]

I think it would be better to use ISODate format on that case.

You can use a custom ObjectMapper for that.


add pipeline trigger #22

I think it can be straight-up merged but leaving it up for review.

Mentiones #22

And to trigger it only on master merge? It's not a test it's a deploy job

Closed in favor of #52


PolarMesh basic realization

The 3D angular mesh could be realized with https://en.wikipedia.org/wiki/Lebedev_quadrature


errro when i use npm prisma generate

does anyone help to resolve this error? if you've been through this

Have you tried commenting out some of the @@map usages to see if that can remove the error? What do your debug generated files look like?

Closing due to no response to help troubleshooting


fix link errors on camel-website

I want to make sure is this the right way to fix link errors in camel-website

@zregvart can you please review?

This should work I think, might be better to use xref instead to make it easier to rearrange the content in the future. There's a bit on that in the Antora documentation.
@Nayananga can you take a look at xref and see if we can use it instead?

@zregvart , @oscerd  I did some changes in #2986 can you please check?


Update 7.0 docs to point to duende 6.0 upgrade docs

We are updating to Duende Identity server 6.x (currently 6.0.4 but probably will be 6.1x) as part of 7.0, can we document the potential dataschema issues that users may run into: https://docs.duendesoftware.com/identityserver/v6/upgrades/v5.2_to_v6.0/
Something like: "We're updating to the latest supported Identity Server in our extensions. Either don't use the extensions and use their configuration methods or update your schema and use our helpers""
See https://github.com/dotnet/aspnetcore/issues/41315 for more context
This affects anyone that uses Microsoft.AspNetCore.ApiAuthorization.IdentityServer which also includes some of the auth variants of Spa/Blazor templates
Edit by @Rick-Anderson below

We decided on sticking with 6.0.4 for 7.0 due to 6.1 having a database schema update https://docs.duendesoftware.com/identityserver/v6/upgrades/v6.0_to_v6.1/

Above from this comment

Associated WorkItem - 61487

Blazor:  https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-identity-server - cc @guardrex
Not Blazor, gRPC, or SignalR

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/identity-api-authorization
https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-mongo-app
https://learn.microsoft.com/en-us/aspnet/core/security/authentication/mfa
https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-web-api

@HaoK  given

We decided on sticking with 6.0.4 for 7.0 due to 6.1 having a database schema update https://docs.duendesoftware.com/identityserver/v6/upgrades/v6.0_to_v6.1/

Above from this comment
What do we need to update for .NET 7?

Since this seems to be a migration concern and because the Blazor doc doesn't refer to Duende versions, I don't think this is actionable for the Blazor doc. Let me know if I've misinterpreted this.

@HaoK  closing this. Let me know if doc's need update.


Heroku deploy error: sh: 1: roadhog: not found

roadhog not found

Environment(required) | 环境（必填）

roadhog version（roadhog版本） : ^2.4.5
Nodejs and Npm version（Nodejs 和 Npm 版本）: v10.8.0
Operating environment (OS High Sierra) and its version（操作系统版本）: 10.13.4
DVA : ^2.4.0

What did you do? Please provide steps to re-produce your problem.（请提供复现步骤）

I followed the steps for creating app build roadhog build.
Then yarn run analyze worked well.

$ cross-env ESLINT=none ANALYZE=true roadhog build
Build completed in 95.336s

Compiled successfully.

File sizes after gzip:

  1001.81 KB  dist/index.190bee36.js
  72.16 KB    dist/js/webflow.js
  54.63 KB    dist/index.30a56509.css
  13.33 KB    dist/css/billeasy.webflow.css
  9.38 KB     dist/css/webflow.css
  2.6 KB      dist/css/normalize.css

So decided to push on heroku app git push heroku master.

remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        engines.node (package.json):  >=8.0.0
remote:        engines.npm (package.json):   unspecified (use default)
remote:
remote:        Resolving node version >=8.0.0...
remote:        Downloading and installing node 10.9.0...
remote:        Using default npm version: 6.2.0
remote:
remote: -----> Restoring cache
remote:        Loading 2 from cacheDirectories (default):
remote:        - node_modules
remote:        - bower_components (not cached - skipping)
remote:
remote: -----> Building dependencies
remote:        Installing node modules (package.json)
remote:        audited 51849 packages in 27.82s
remote:        found 4 moderate severity vulnerabilities
remote:        run `npm audit fix` to fix them, or `npm audit` for details
remote:
remote: -----> Caching build
remote:        Clearing previous node cache
remote:        Saving 2 cacheDirectories (default):
remote:        - node_modules
remote:        - bower_components (nothing to cache)
remote:
remote: -----> Pruning devDependencies
remote:
remote:        ><EMAIL_ADDRESS>uninstall node_modules/husky
remote:        > node ./bin/uninstall.js
remote:
remote:        husky
remote:        uninstalling Git hooks
remote:        done
remote:
remote:        removed 2469 packages and audited 2561 packages in 34.513s
remote:        found 0 vulnerabilities
remote:
remote:
remote: -----> Build succeeded!
remote: -----> Discovering process types
remote:        Procfile declares types     -> (none)
remote:        Default types for buildpack -> web
remote:
remote: -----> Compressing...
remote:        Done: 163.7M
remote: -----> Launching...
remote:        Released v9
remote:        https://reactor-dashboard.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
To https://git.heroku.com/reactor-dashboard.git
   8b2d7b4..b105b72  master -> master

What do you expected?（预期的正常效果）
No error and expected Working build just like local.
What happen?（发生了何种非正常现象）

Then heroku logs --tail

2018-08-31T10:17:21.124907+00:00 app[web.1]:
2018-08-31T11:21:31.287992+00:00 heroku[web.1]: State changed from crashed to starting
2018-08-31T11:21:48.516181+00:00 heroku[web.1]: Starting process with command `npm start`
2018-08-31T11:21:52.598464+00:00 heroku[web.1]: Process exited with status 1
2018-08-31T11:21:52.614800+00:00 heroku[web.1]: State changed from starting to crashed
2018-08-31T11:21:52.408351+00:00 app[web.1]:
2018-08-31T11:21:52.408371+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2018-08-31T11:21:52.408373+00:00 app[web.1]: > ESLINT=none roadhog server
2018-08-31T11:21:52.408374+00:00 app[web.1]:
2018-08-31T11:21:52.431811+00:00 app[web.1]: sh: 1: roadhog: not found
2018-08-31T11:21:52.440402+00:00 app[web.1]: npm ERR! file sh
2018-08-31T11:21:52.440740+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-08-31T11:21:52.441291+00:00 app[web.1]: npm ERR! syscall spawn
2018-08-31T11:21:52.441029+00:00 app[web.1]: npm ERR! errno ENOENT
2018-08-31T11:21:52.451204+00:00 app[web.1]: npm ERR<EMAIL_ADDRESS>start: `ESLINT=none roadhog server`
2018-08-31T11:21:52.451381+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-08-31T11:21:52.451728+00:00 app[web.1]: npm ERR!
2018-08-31T11:21:52.458969+00:00 app[web.1]: npm ERR! Failed at the<EMAIL_ADDRESS>start script.
2018-08-31T11:21:52.459180+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-08-31T11:21:52.488476+00:00 app[web.1]:
2018-08-31T11:21:52.490456+00:00 app[web.1]: npm ERR!  Need Help.

Found my solutions, i was doing all wrong because i had no idea how to deploy react. So all i was doing before is pushing all files to server (not the /dist folder which is totally wrong).
For production deploy we must deploy only build folder(/dist) which is generated by yarn build or npm run build.

Run yarn build for production build. It will generate /dist folder which is production build.
Create an Express JS server to serve your production build
touch server.js
In server.js, copy/paste the following code:  // server.js

  const express = require('express');
  const path = require('path');

  const port = process.env.PORT || 8080;
  const app = express();

  app.use(express.static(path.join(__dirname, '/dist')));

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

  app.listen(port);

In your package.json file, change the start script to the following:
start: "node server.js".
Remove "start": "cross-env ESLINT=none roadhog dev" & "precommit": "npm run lint-staged" (only for production push add it back for development).
Open .gitignore file add following code:  #.gitignore
  src/*
  public/*

In .gitignore file, remove /dist(only for production push add it back for development).
This will only push production build to server rather than all files.

Sorry for the trouble. @sorrycc
Before closing this issue a small request to you guys please update build & deploy procedure on ant-pro docs. It will surely helpful for new users a lot.
~Thank you.


after saving cropped image it losing the  ID of the origin element

after saving cropped image it losing the  ID of the origin element

I know :)
See https://github.com/MattKetmo/darkroomjs/issues/59#issuecomment-176753119


Backstage Working Group - DevOps Automation - Mar 16, 2023

Date
Thursday, Mar 2 2023 - 11am ET; 3pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people
[ ] Display FINOS Antitrust Policy summary slide
[ ] Approve previous meeting minutes
[ ] Review DevOps SIG project board
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/99355753984?pwd=c1RxLzNWN0dWck1aeTlQRUxrN0ZBdz09
Meeting ID: 993 5575 3984
Passcode: 991230
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Hello 👋🏻

hello


Question about value_pe

In the file, rope/value_pe/init.py

It seems the value embedding is rotated twice in line 230 and line 234.
From my understanding, only one rotation is enough.
Please let me know whether I misunderstood this.
Thanks.

Thanks. It's a bug

Fixed it here https://github.com/labmlai/annotated_deep_learning_paper_implementations/commit/09d09379c2169eac06662e17cb9969dc6e48e36a


Cannot match route when creating new RPC service

With version 1.0.4 when you create a new RPC service the route is initially not matchable unless you put a forward slash preceding your route name. The problem is in the module.config.php
Replicate this by creating a new RPC service, in my case with the service name updateWeather and route to match as update-weather.
Below is generated module.config.php snippet. Note that the route is missing a preceding forward slash. By default trying to access /update-weather does not match a route, adding the forward slash makes the route valid.
Obviously I didn't add the slash when I should have however there was no indication I should and the REST services create the route for you with the slash. There should be validation that the route starts with a slash or one added for you.
            'sarah.rpc.update-weather' => array(
                'type' => 'Segment',
                'options' => array(
                    'route' => 'update-weather',
                    'defaults' => array(
                        'controller' => 'sarah\\V1\\Rpc\\UpdateWeather\\Controller',
                        'action' => 'updateWeather',
                    ),
                ),
            ),

@cookejames I had the same issue also with RPC sevices. The auto-generated code did not added the slash for the route

This repository has been closed and moved to laminas-api-tools/api-tools-admin; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-admin/issues/45.


DRILL-6320: Fixed License Headers

Overview
There were several issues with license headers before this change:

We used the apache-rat-plugin to check licenses which was not thread safe. So when doing concurrent builds of submodules with mvn -T 2C clean install it could fail.
The apache-rat-plugin did not check all files for licenses and did not provide a warning for the files it skipped.
It allows inconsistent formatting of license headers.
It allowed license headers to be in java doc comments. This is problematic since we don't want the license to be included in every documentation page when we decide to publish java docs.

All of these issues were fixed by moving to the license-maven-plugin. I have reformatted all the license headers and manually verified the headers on each file to make sure they are correct. Now every file in the project is checked for a license except for some shell scripts that do not have file extensions in their names. Also none of the license headers are in java doc comments now!!!!
Important Note
This change bumped up the required version of maven from 3.0.1 to 3.3.1 . This is because maven introduce a very useful feature in 3.3.1 which is the ${maven.multiModuleProjectDirectory} property. This property holds the absolute path to the base directory of the project's root module regardless of which submodule the maven command is executed from. This property is used to define the path of the license header file and allows us to check license headers even when our current working directory is a sub module of the project.
Before this change is merged we need to update Drill's jenkins CI to maven 3.3.1 or later.

Abhishek has already updated jenkins to the latest maven. So we should be clear to merge after review is done.

@ilooner since mix required maven version has changed, please update install.md as well.

-1 on removing apache-rat maven plugin. It is an Apache plugin to invoke "Release Audit Tool". More plugins can be added to check license headers if they do a better job in addition to apache-rat.
Both apache-rat and any other license verification plugins can be disabled by default (this will allow to run mvn -T 2C clean install if necessary) and only enabled in Travis CI.

@arina-ielchiieva Updated INSTALL.md
@vrozov Added the rat plugin back. Disabled license checking for both rat and the license-maven-plugin by default and enabled it for travis

@arina-ielchiieva In Apex we use special git user Apex Dev<EMAIL_ADDRESS>to make format only changes. I'd recommend doing the same for Drill.

@arina-ielchiieva @vrozov I'll split the change into two commits. One with a change to the pom files and install.md . Another attributed to<EMAIL_ADDRESS>with all the formatting changes.

@arina-ielchiieva fixed

@vrozov @arina-ielchiieva Addressed comments.

LGTM, @ilooner please double check that Apache source distribution can be built with '-Drat.skip=false -Dlicense.skip=false':

build with -P apache.release -Dgpg.skip=true
extract created source .tar.gz or .zip to a temp directory
build with apache-rat and license check enabled (you may need to add more files to the license check exclusion).

@vrozov followed your instructions. Building the source distribution with license checks enabled works.

+1, thanks for making the changes!

@arina-ielchiieva or @Ben-Zvi would it make sense to merge this in earlier before the batch commits later in the week? the number of files changes are large so don't want @ilooner to have to rebase each time.


Convert span to ReadableSpan before sending to span processor

Currently when Span ends it sends the whole self to the span processor. Span Processor expects the span to be ReadableSpan but in fact the span that is being sent is a whole object with methods etc. I think we should send only an object in correct format. We could have for example a private function "_serialize" or "_toReadableSpan" which will send only required data and nothing more. We should also think about sealing the data so it cannot be modified.
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#interface-definition

As a SpanProcessor gets the real span in onStart it's not really a protection.
I could imagine that there are SpanProcessor implementations which add some property to the span received in onStart for pure internal use. Or if modification of the span should be avoided they could use it as key in a Map/WeakMap which is effective the same problematic scenario as they get something different in onEnd and want find their data.
Most likely they could use the SpanContext instead the span but if we intend to protect our spans it would be also needed to create a read only copy of them.
I assume a deep copy + sealing of all spans is quite costly.
Passing sealed/frozen objects to users is in my opinion not what one expects. Usually I assume that I can always add a private symbol to an object.
And still this doesn't protect 100% for missues as a SpanProcessor could simply monkey patch this part of the SDK to skip this sealing/deep copy.
We are in JavaScript world and if people want to shoot themself in their foot they will always find a way to do this.
How is this done in other languages?

@Flarna you weren't at last sig meeting. We won't be sealing the object, but we will map the values so only this what is required will be sent and nothing more. currently we are sending the whole span which is more then only a readable span.
The sealing / freeze is something we can discuss but we agreed that this might be too costly to do it.

So this means the object passed to onStart is never passed to onEnd?

So this means the object passed to onStart is never passed to onEnd?

if you look closely you will see that even the type of those 2 functions is different.

So this means the object passed to onStart is never passed to onEnd?

Hmm I didn't think about this before. IMO that might be a dealbreaker. A span processor needs to be able to use onEnd to clean up things done in onStart. If a different object is sent a WeakMap can't be used.

if you look closely you will see that even the type of those 2 functions is different.

The type can be different to encourage users not to modify the span or call functions in onEnd, but IMO it's not a problem to not match exactly as long as it matches the type at least.

Well the spec says that onEnd it should readable object, modification should not be allowed.

The spec also says exceptions are allowed in cases where it isn't practical. deep freeze may be quite costly.

Well, a SpanProcessor could use a Map<TraceId, Map<SpanId, Span>> or simialar to find back to the span. It's quite some overhead but it would effect only SpanProcessors which have the need for this.

deep freeze on my machine for 1k spans with 1 attribute takes around 5ms-6ms

const { BasicTracerProvider } = require('./build/src');
const provider = new BasicTracerProvider();

const tracer = provider.getTracer('test');

const span = tracer.startSpan('span');
span.setAttribute('test', 'value1');

const start = new Date().getTime();
function deepFreeze(obj) {

  // Retrieve the property names defined on obj
  var propNames = Object.getOwnPropertyNames(obj);

  // Freeze properties before freezing self
  propNames.forEach(function(name) {
    var prop = obj[name];

    // Freeze prop if it is an object
    if (typeof prop == 'object' && prop !== null)
      deepFreeze(prop);
  });

  // Freeze self (no-op if already frozen)
  return Object.freeze(obj);
}
for (let i = 0, j = 1000; i < j; i++) {

  const readableSpan = deepFreeze(span);
}
const end = new Date().getTime();

console.log(end - start, 'ms');

source for deep freeze
https://developer.mozilla.org/pl/docs/Web/JavaScript/Referencje/Obiekty/Object/freeze

Well, a SpanProcessor could use a Map<TraceId, Map<SpanId, Span>> or simialar to find back to the span seen in onStart. It's quite some overhead but it would effect only SpanProcessors which have the need for this.

This could be a memory leak in the case span is not ended

Well, a SpanProcessor could use a Map<TraceId, Map<SpanId, Span>> or simialar to find back to the span seen in onStart. It's quite some overhead but it would effect only SpanProcessors which have the need for this.

This could be a memory leak in the case span is not ended

That's the reason why I prefer to set a private symbol in such cases.
I still don't understand what the benefit of freezing/creation of a fresh readable span is. Which problem does/should this solve?
The SpanProcessor is the thing between SDK and Exporter. Even if it gets only deep frozen spans it can deep clone, modify and pass the modified span to exporter. An evil SpanProcessor can even discard/invent spans as needed.
IMHO doing this doesn't protect from misuse but adds overhead and risk of surprises for users.
But if there is consensus to go this path I will not block it.
There is a reason why I'm not a big fan of read-only/freezing: A while ago I added a read-only property to EventEmitter in node. It seemed to be the right to set it read-only as modification of this would be always wrong. It turned out that this broke quite something (see https://github.com/nodejs/node/pull/30932#discussion_r379679982), was reverted and added again as "normal", writable property.

Well, a SpanProcessor could use a Map<TraceId, Map<SpanId, Span>> or simialar to find back to the span seen in onStart. It's quite some overhead but it would effect only SpanProcessors which have the need for this.

This could be a memory leak in the case span is not ended

According to spec the main purpose of onStart is to keep reference to the span. This is because you can then do some periodic export. But you can't use a WeakMap for that because WeakMap is not iterable object and thus is useless for such purpose. So you have to save reference in some array / map object anyway to be able to iterate over it periodically. Based on that having scenario that you are keeping a reference just to check for something when spans ends sounds unrealistic for me and it would not make any sense. This way if anyone wants to implement any extra logic for periodic export of unfinished spans will have to deal with such problem anyway and exporting the exactly the same object as in onStart doesn't sound for me as a realistic scenario.

I still don't understand what the benefit of freezing/creation of a fresh readable span is. Which problem does/should this solve?
The SpanProcessor is the thing between SDK and Exporter. Even if it gets only deep frozen spans it can deep clone, modify and pass the modified span to exporter. An evil SpanProcessor can even discard/invent spans as needed.
IMHO doing this doesn't protect from misuse but adds overhead and risk of surprises for users.

As a user I would read spec which says that when span is ended it is only readable and cannot be changed. Imagine now a scenario where you have multiple span processors or/and exporters etc. and one of such will modify the span. It will suddenly affect all processors and spans. If you freeze span it cannot be modify and thus nothing strange can happen. You have the same with badge I can guess that it was similar approach with that and similar reasons.

FWIW I implemented already a SpanProcessor sending non finished spans to our backend. It uses a Set to hold the spans to send regularly. To avoid leaks for never ended spans I wipe out all spans older then ~2h.
Currently I rely on onStart() and onEnd() providing the same span, different objects would result in two entries in my Set.
As mentioned above this can be fixed by replacing the single Set by a more complex, significant slower construct.
Object.freeze() doesn't break the identity so this would work without changes.
But considering the overhead I would vote for an opt-in.
if someone wonders why we send in progress spans to our backend: it allows to correlate the whole span tree early even if there is a long running span somewhere in the middle. e.g. ShortSpan1 => LongSpan2 => ShortSpan3
In this case our backend knows about LongSpan2 early and can show the whole tree and not after e.g. 1.5h when it's ended.


x1062—As a PO (Minal), I want users to record probe hybridisation end time for tracking of Xenium

Select Probe hybridisation QC from Probe hybridisation option from the labwork menu.
Select work number.
Scan in labware.
The labware must have had probe hybridisation already recorded on it.

Probe hybridisation comments (editable on config page) — zero, one or more per section (with apply all)
e.g.

section detached
issue with thermal cycler

Select hybridisation completed date/time (hh:mm) (default to current time, must be in the past).

(The labware should not be discarded by this operation.)

@seenanair
When I tried to complete the operation I got the below error and wouldn’t let me save

Even though the clock on my computer is 8:17 it wasn’t letting me do 8:14
So tried a different time again and got it needed be to 8:03 or earlier, see below:

When I tried to go before 8:03 I got the message to say its before its previous operation, which makes sense:

@KatyTudor  would it be easy for you to have a quick look

Hi @KatyTudor , we updated UAT, could you please test again, thanks


Backdoor attack HuggingFace Model Automatic Speech Recognition via HuggingFaceClassifierPytorch ART

Hello(s)  Dear,  @f4str , @GiulioZizzo , @beat-buesser !  is it possible to dynamically parameterize the face of the classifier HuggingFaceClassifierPyTorch otherwise, it doesn't seem as dynamic as the other ART classifiers because it has very fixed channels! I'd like to use this classifier to launch backdoor attacks on Hubert models, Wav2Vec2 etc.,
I've already managed to poison them (see attached image Wav2vec2 model), now I'd like to train them on this poisoned data, but I'm having problems with reshaping the data to fit the classifier, see attached error.
print(x_train.shape, "shape")

(2500, 124, 129, 1) shape

print(y_train.shape, "shape")

(2500,) shape

# Load the Wav2Vec2 processor and model
from transformers import Wav2Vec2ForCTC, Wav2Vec2Processor
from art.estimators.classification.hugging_face import HuggingFaceClassifierPyTorch

input_shape=(124, 129, 1)
num_labels=len(commands)

model = transformers.AutoModelForAudioClassification.from_pretrained(
    'facebook/wav2vec2-base-960h',
    ignore_mismatched_sizes=True,
    num_labels=num_labels
)
optimizer = torch.optim.Adam(model.parameters(), lr=1e-4)
loss_fn = torch.nn.CrossEntropyLoss()

hf_model = HuggingFaceClassifierPyTorch(
    model=model,
    loss=loss_fn,
    optimizer=optimizer,
    input_shape=(124, 129, 1),
    nb_classes=num_labels,
    clip_values=(0, 1),
)

[<ipython-input-23-80daec27e4d9>](https://localhost:8080/#) in <cell line: 15>()
     13 loss_fn = torch.nn.CrossEntropyLoss()
     14
---> 15 hf_model = HuggingFaceClassifierPyTorch(
     16     model=model,
     17     loss=loss_fn,

18 frames
[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/conv.py](https://localhost:8080/#) in _conv_forward(self, input, weight, bias)
    304                             weight, bias, self.stride,
    305                             _single(0), self.dilation, self.groups)
--> 306         return F.conv1d(input, weight, bias, self.stride,
    307                         self.padding, self.dilation, self.groups)
    308

RuntimeError: Expected 2D (unbatched) or 3D (batched) input to conv1d, but got input of size: [1, 1, 124, 129, 1] ```

Hi @OrsonTyphanel93,
Thanks for bringing this up!
So HuggingFaceClassifierPyTorch will try and perform a forward pass to determine the model structure - something that is often needed for poisoning attacks and defences. To do so a dummy input sample will be created based on the supplied input_shape. In which case, if the model expects 1D inputs the input_shape should just be the sequence length: i.e. without any batching.
The code snippet below should work.
What's the motivation in your case which requires the input_shape to be different compared to the standard Wav2Vec2ForCTC format? Perhaps it is a use-case we have not considered and we can look into supporting it.
`
model = transformers.AutoModelForAudioClassification.from_pretrained(
'facebook/wav2vec2-base-960h',
ignore_mismatched_sizes=True,
num_labels=2)
input_values = np.random.normal(size=1000)
_ = HuggingFaceClassifierPyTorch(
model=model,
loss=torch.nn.CrossEntropyLoss(),
optimizer=torch.optim.Adam(model.parameters(), lr=1e-4),
input_shape=input_values.shape,
nb_classes=2,
)
`

Closing because of inactivity, please reopen if still current.


Minimum Requirements

I think it would be pretty good to know the minimum requirements for a KVM needed to properly run this project. :)

Hi, have you encountered any issues running this project? Minimum requirements are really minimal, you should get away with no problem with a 512MB VM (most of the RAM is for the os really, hopper doesn't consume almost anything)


Atomic hotswapping in JIT mode

May conflict with #2745 or #2750, so please merge those first.

Writing the GOT entries needs to be delayed until after relocations have been performed and the memory has been marked as executable for code or read only for read only data.

Writing the GOT entries needs to be delayed until after relocations have been performed and the memory has been marked as executable for code or read only for read only data.

@eggyal has implemented this. Thanks!

I think I may have made a mess here... 3e11bd8 is undoing much of 2d9190d.  While the result is that GOT updates are correctly deferred, which is what we needed for bjorn3/rustc_codegen_cranelift#1166, it likely isn't doing what's needed for hot swapping.  Let me take another look.

r? @abrown ?


id collisions

the current ID generation results in 1-2 character strings, ultimately leading to collisions
since web crypto has good support, maybe we can switch to using builtins for generating uuids, with a simple polyfill fallback

Collisions are ultimately acceptable, as long as the collision rate within a single day for a single site is less than one percent. Even though the IDs are completely random and not persisted in the browser, we don't want to give the impression that they could hide PII, so the shorter the better.

i think that's great, i haven't thought about it that way. i would find it more intuitive (and consistent) if the id was a fixed (albeit short) length, i am thinking 4-6 characters. thoughts?

Fixed length would be an improvement


Fix: API console too busy when code in controller files are executed - esm and cjs templates.

This pull request makes the following changes

Fix https://github.com/code-collabo/node-mongo/issues/17

General checklist

[x] File or folder now contains changes as specified in the issue i worked on
[x] I have linked the issue I worked on to this pull request submitted by me

Testing checklist

[x] Only esm and cjs controller files are edited
[x]  Success console message now short and without \n
[x]  Error console message stays like it was, but without \n
[x]  I certify that I ran my checklist

Ping @code-collabo/node-mongo-api-boilerplate-templates

@Ifycode Awaiting review.

I changed them to .env files to test the console messages.


Add support for topology-aware traffic routing

How to categorize this PR?

/area high-availability
/area networking
/kind enhancement
What this PR does / why we need it:
The PR adds support for topology-aware traffic routing.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/6718
Special notes for your reviewer:
✅ This PR depends on https://github.com/gardener/etcd-druid/pull/485
Release note:

A new feature gate called `TopologyAwareRouting` is introduced to `gardenlet` and `garden-operator`. `TopologyAwareRouting` enables topology-aware traffic routing in garden or seed clusters using the Kubernetes feature `TopologyAwareHints`. For more details, see [Topology-aware Traffic Routing](https://github.com/gardener/gardener/blob/TBD/docs/usage/topology_aware_routing.md).

/test pull-gardener-e2e-kind

/assign

/assign

make generate in prow failed with:
Generating CRDs for resources.gardener.cloud group
Generate github.com/gardener/gardener/pkg/operation/botanist/component/resourcemanager/mock
../../resource_manager.go:90:13: pattern assets/crd-resources.gardener.cloud_managedresources.yaml: no matching files found
../resource_manager.go:90:13: pattern assets/crd-resources.gardener.cloud_managedresources.yaml: no matching files found
prog.go:14:2: no required module provides package github.com/gardener/gardener/pkg/operation/botanist/component/resourcemanager: go.mod file not found in current directory or any parent directory; see 'go help modules'
prog.go:12:2: no required module provides package github.com/golang/mock/mockgen/model: go.mod file not found in current directory or any parent directory; see 'go help modules'
2023/01/13 14:06:37 Loading input failed: exit status 1
pkg/operation/botanist/component/resourcemanager/mock/doc.go:15: running "mockgen": exit status 1

I could only guess that it is potentially caused by a parallel generation of the GRM CRD and the mocks. Locally make generate-sequential is successful for me.
/test pull-gardener-unit

I addressed all comments except the one for rework with a webhook approach (ref https://github.com/gardener/gardener/pull/7191#discussion_r1085032036) and one dependent comment.

I adapted the PR to use a Seed setting instead of a feature gate. Example usage from extensions (or enablement of topology-aware Services in the extensions) - https://github.com/gardener/gardener-extension-provider-aws/pull/703.

/test pull-gardener-e2e-kind

Now that the PR was reworked, could you please split the changes into several reasonable commits? Now that the approach is a different, the history including the changes related to earlier PR feedback are not that important anymore, I believe.

I can work on splitting the changes into several. I assume that it will take time and won't be that trivial for some cases.
What is the reason behind request? To improve the reviewing experience?
I would appreciate if similar requests are raised in in the beginning as soon as possible. The PR was created as a single-commit one in the beginning and I added new commits for addressing review feedbacks. It could be raised in the beginning that the PR should be split into multiple commits.

I can work on splitting the changes into several. I assume that it will take time and won't be that trivial for some cases.

It doesn't have to be perfect, so don't spend too much time for it now that it's "already late". Just a few commits for the separate parts in this PR already help to navigate.

What is the reason behind request? To improve the reviewing experience?

Right.

I would appreciate if similar requests are raised in in the beginning as soon as possible. The PR was created as a single-commit one in the beginning and I added new commits for addressing review feedbacks. It could be raised in the beginning that the PR should be split into multiple commits.

You're right, I could have mentioned it in the first review round, but I overlooked it. Anyways, how does this "timing" part matter? It would have been the "same work" as it's now - splitting a big bulk of changes into smaller commits.
Apart from that, you know that we had pretty long discussions about this subject matter years back when we worked on large feature like ManagedSeeds and ManagedSeedSets. Since this time, almost every PR that is "significantly" large comes with multiple commits to ease the review process and speed it up.

/hold
as I noticed an issue that has to be resolved after the merge of https://github.com/gardener/gardener/commit/81795ed9aa52da5f5194ddb05bd7ac0bf2c39d35 (the etcd-{role}-client Service annotations would be overwritten by the logic from this PR)...

/unhold

@rfranzke , thanks for the reviews and help on addressing the comments! I believe I addressed all the comments.

/lgtm


Consider a Noop Initializer when mirage is not enabled in a build

Hey, first off, thank you for all the great work!
I just came across an issue where one of my apps initializers had to run before the ember-cli-mirage initializer (to seed momentjs with a predefined "now"). Doing so created a scenario where everything would be fine in both the test and development builds (all tests green), but the apps production build would fail due to a missing initializer. I did some investigating and I believe it happens for the following reason:
In development/test builds ember will catch missing initializers that are referenced in an initializers "before" and "after" keys, however because mirage is excluded when its enabled flag is set to false, it is able to pass the assertions and then it disappear in a production build.
To get around the issue I am currently conditionally setting the before key in my apps initializer based on the ember-cli-mirage enabled configuration value. While this works, it seems like it would be better if consumers didn't have to think about this detail. One way to handle this could involve a noop initializer for the cases where mirage is excluded from the builds.
Please let me know what you think
Thanks!

Agreed. We should always have an initializer, it should just do nothing when not included...

@rwjblue thank you for the quick reply. If there is no immediate rush, then I would be up for attempting a PR for this. It looks like the initializer is already set up to handle the case where mirage is disabled, so I imagine there just needs to be a higher degree of specificity when excluding files from the build tree?

Seems reasonable, though I haven't recently reviewed the build configuration here so am not 100% certain.

Ok, I will take a look at it and see how far I can get. Thanks again.


some style changes in contenttypes

OK?

If you're going to do this, it would be nice to be more systematic about it. Are you using any tools to find non-hanging indents?

Actually no, is there ant tools for that?

I'm not sure about tools -- it seems like something that pep8/flake8 could do but I didn't find anything after a quick search. Anyway, I'm not happy to merge a single change in a file (fields.py) when there are other unfixed instances of that same issue in the same file. So as I said, let's find a way to be more systematic. Ideally with a tool that can automate the changes.

yes that should be the better way

For this PR, how about reverting the change to fields.py for now and removing all usage of from django import http in Django?

sounds sensible to me

https://github.com/django/django/pull/8114 new pr


[BUG] Issue in pulling metrics from more then 2 graphite node , Unable to fetch

I am running graphite cluster with three nodes ( working in docker environment)
below are my graphite local_setting
for Node 1:
CLUSTER_SERVERS = ["<IP_ADDRESS>:8081", "<IP_ADDRESS>:8081"]
REMOTE_STORE_FETCH_TIMEOUT = 300   # Timeout to fetch series data
#REMOTE_STORE_FIND_TIMEOUT = 2.5  # Timeout for metric find requests
REMOTE_STORE_RETRY_DELAY = 60    # Time before retrying a failed remote webapp
#REMOTE_FIND_CACHE_DURATION = 300 # Time to cache remote metric find results
REMOTE_PREFETCH_DATA = True
CARBONLINK_HOSTS = ["<IP_ADDRESS>"]
CARBONLINK_TIMEOUT = 1.0
USE_WORKER_POOL = True
POOL_MAX_WORKERS = 10

For Node 2:
CLUSTER_SERVERS = ["<IP_ADDRESS>:8081", "<IP_ADDRESS>:8081"]
## Rest same as Node 1

For Node 3:
CLUSTER_SERVERS = ["<IP_ADDRESS>:8081", "<IP_ADDRESS>:8081"]
## Rest same as Node 1

I am using Grafana as fornt-End, When I use 2 Node only everything works fine but as soon as I switched to three node cluster I am starting facing issue while getting data. Below are the logs which i got
020-07-30,10:38:42.816 :: Timed out after 300.000278s for fetch for ['*.collectd.memory']
2020-07-30,10:38:42.817 :: Timed out after 300.000224s for fetch for ['*.statsd.memory']

Environment (please complete the following information):

OS flavor: Ubuntu
Graphite-web version - 1.1.5
Django/Python version - 2.0.13/Python3.6

@AshishVerma7690 : yes, that setup is possible and should work - graphite-web emits '?local=1' parameter when calling CLUSTER_SERVERS and they should lookup only local files and not create any loops.
But I personally always prefer 2 tier setup - why not setup Node1 as requestor for other 3 nodes, e.g.
CLUSTER_SERVERS = ["<IP_ADDRESS>:8081","<IP_ADDRESS>:8081","<IP_ADDRESS>:8081", ]
and use Node2, Node3 only for reading local files and serve them to Node1 requests', i.e.
CLUSTER_SERVERS = []

Will try to reproduce 3 node setup with cross requests, when I'll have time later, though, as I said it should work.

@deniszh  In my scenario, I am not certain how many graphite node will be there, it will be a run time value. User can scale up nodes and also scales down. Also my data is distributed through multiple graphite node.
As of now I am fetching data using grafana-ui (running in same docker with graphite - Node 0)  which fetch from cluster nodes.

In my scenario you're on same scalability as in your setup, it's just less complex, hence less error prone to complex bugs, similar to this one.

In my scenario you're on same scalability as in your setup, it's just less complex, hence less error prone to complex bugs, similar to this one.

In your scenario, you are using Node1 for read purpose, but what happen if the node1 itself goes down?

In your scenario, you are using Node1 for read purpose, but what happen if the node1 itself goes down?

If you want to protect from this scenario you need to set another node with absolutely same setup as node0 and put read requests there, using load balancer or DNS. In your setup you need to do similar thing anyway.
As I said, it's 2-tier system - first tier of N nodes are contains no data, they're just getting requests from 2nd tier and render them to users. And 2nd tier of M nodes only serving data from WSP files (but not spending resources for render data):
NodeT1-1:
CLUSTER_SERVERS = ["NodeT2-1", "NodeT2-2", "NodeT2-3"..."NodeT2-M"]
NodeT1-2:
CLUSTER_SERVERS =  ["NodeT2-1", "NodeT2-2", "NodeT2-3"..."NodeT2-M"]
...
NodeT1-N:
CLUSTER_SERVERS =  ["NodeT2-1", "NodeT2-2", "NodeT2-3"..."NodeT2-M"]
NodeT2-1:
CLUSTER_SERVERS = []
NodeT2-2:
CLUSTER_SERVERS = []
NodeT2-3:
CLUSTER_SERVERS = []
...
NodeT2-M:
CLUSTER_SERVERS = []
In your setup this 2 roles are mixed, which is not bad per se - but just can add complexity to setup.
Also, in 2 tier setup you can replace 2nd tier nodes e.g. with go-carbon with carbonserver enabled - and system will still be working.
Your setup also should work, I'm just want to let you know that you can try different setup, which will decrease complexity and improve your results. It's not better or worse  - it's just another way which you can try.
But you're right - in general case two tier setup can require more nodes - 5 instead of 3 in your case. And in your setup you can use same nodes - in case of 2 tier setup they probably should differ.

I can not use 2 Tier setup( 1 for reading & 1 for writing ) as  the graphite nodes are selected on run time using HAProxy. So I don;t know which is going to be my read node.

Hi @AshishVerma7690 ,
sorry, I can't reproduce problem with latest Graphite.
I created simple 3 node cluster with similar configuration - relay, consistant hashing with RF=2 and every node reads data from other 2 nodes - https://github.com/graphite-project/graphite-test-docker/blob/master/cluster/docker-compose.yml
For me this setup works fine. I run haggar for some time (it's Graphite load generator) and then count metric on every node with
http://localhost:81/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
http://localhost:82/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
http://localhost:83/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
It gives me proper result - monotonically increase number.

You can also set REMOTE_EXCLUDE_LOCAL = True in your local_settings.py and use the same CLUSTER_SERVERS on all hosts.  Graphite will automatically detect which of the IPs is local and only send the remote render requests to the other 2.

Hi @AshishVerma7690 ,
sorry, I can't reproduce problem with latest Graphite.
I created simple 3 node cluster with similar configuration - relay, consistant hashing with RF=2 and every node reads data from other 2 nodes - https://github.com/graphite-project/graphite-test-docker/blob/master/cluster/docker-compose.yml
For me this setup works fine. I run haggar for some time (it's Graphite load generator) and then count metric on every node with
http://localhost:81/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
http://localhost:82/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
http://localhost:83/render/?format=json&target=countSeries(haggar.agent.0.metrics.*)&from=-1min
It gives me proper result - monotonically increase number.

Ok I am able to get the desired result , but a new problem arrives now. I am now working with 6 node cluster and a lot of metrics .everything works fine if we collect data of last 15 min but as soon as I go for last 7 days data It hung up( It takes too much of time).
Can we do anything to reduce this time period?

working fine using cluster server


Can't install mezzanine for python35

Issue description
I get this message:
running build_ext
Traceback (most recent call last):
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/settings.py", line 13, in <module>
    import tinymce.settings
ImportError: No module named 'tinymce'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "nix_run_setup.py", line 8, in <module>
    exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
  File "setup.py", line 18, in <module>
    zip_safe=False,
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 159, in run
    self.with_project_on_sys_path(self.run_tests)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 140, in with_project_on_sys_path
    func()
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 180, in run_tests
    testRunner=self._resolve_as_ep(self.test_runner),
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/main.py", line 93, in __init__
    self.parseArgs(argv)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/main.py", line 123, in parseArgs
    self._do_discovery([])
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/main.py", line 228, in _do_discovery
    self.test = loader.discover(self.start, self.pattern, self.top)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/loader.py", line 341, in discover
    tests = list(self._find_tests(start_dir, pattern))
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/loader.py", line 398, in _find_tests
    full_path, pattern, namespace)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/loader.py", line 475, in _find_test_path
    tests = self.loadTestsFromModule(package, pattern=pattern)
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 38, in loadTestsFromModule
    tests.append(self.loadTestsFromName(submodule))
  File "/nix/store/abvccgrm8ipq568xy2a3101z739n7rsa-python3-3.5.2/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
    module = __import__(module_name)
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/views.py", line 29, in <module>
    from filebrowser_safe.settings import *
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/settings.py", line 17, in <module>
    DEFAULT_URL_TINYMCE = settings.STATIC_URL + "grappelli/tinymce/jscripts/tiny_mce/"
  File "/nix/store/q8a7dl0h4k9bs81jfr3fn1yq7mynxax7-python3.5-Django-1.10.2/lib/python3.5/site-packages/django/conf/__init__.py", line 53, in __getattr__
    self._setup(name)
  File "/nix/store/q8a7dl0h4k9bs81jfr3fn1yq7mynxax7-python3.5-Django-1.10.2/lib/python3.5/site-packages/django/conf/__init__.py", line 39, in _setup
    % (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting STATIC_URL, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
builder for ‘/nix/store/zvh08g6pd78lwfw0p8h4i8f9g6ajhalz-python3.5-filebrowser_safe-0.3.6.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/hf4nzqppwy1dfkg2ng0m4pxss4wqrsbn-python3.5-mezzanine-3.1.10.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/hf4nzqppwy1dfkg2ng0m4pxss4wqrsbn-python3.5-mezzanine-3.1.10.drv’ failed

It seems that the original problem is related to the filebrowser_safe package.
Steps to reproduce
nix-build '<nixpkgs>' -A python35Packages.mezzanine
There is no problem for python27
Technical details

System: NixOS: 17.03pre94121.210b3b3 (Gorilla) and on master
Nix version: nix-env (Nix) 1.11.4
Nixpkgs version: 17.03pre94121.210b3b3

@lsix knows more about Django on Nix.

But a first step would be to add the tinymce module

I’ll look into that ASAP

I have a PR (#20019) related to this issue.
At this point, mezzanine WILL NOT WORK with python-3.5. The mezzanine version we have is using django-1.6 which does not support python-3.5 (see .https://docs.djangoproject.com/en/1.10/releases/1.6/).
We will need to update mezzanine version in nixpkgs at some point to fix this properly.

@lsix okay, thanks!

can this be closed?

No, from current master I've received the same problem for python35:
running build_ext
Traceback (most recent call last):
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/settings.py", line 13, in <module>
    import tinymce.settings
ImportError: No module named 'tinymce'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "nix_run_setup.py", line 8, in <module>
    exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
  File "setup.py", line 18, in <module>
    zip_safe=False,
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 159, in run
    self.with_project_on_sys_path(self.run_tests)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 140, in with_project_on_sys_path
    func()
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 180, in run_tests
    testRunner=self._resolve_as_ep(self.test_runner),
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/main.py", line 93, in __init__
    self.parseArgs(argv)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/main.py", line 123, in parseArgs
    self._do_discovery([])
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/main.py", line 228, in _do_discovery
    self.test = loader.discover(self.start, self.pattern, self.top)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/loader.py", line 341, in discover
    tests = list(self._find_tests(start_dir, pattern))
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/loader.py", line 398, in _find_tests
    full_path, pattern, namespace)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/loader.py", line 475, in _find_test_path
    tests = self.loadTestsFromModule(package, pattern=pattern)
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/site-packages/setuptools/command/test.py", line 38, in loadTestsFromModule
    tests.append(self.loadTestsFromName(submodule))
  File "/nix/store/y23hsampcyaad80f126482zpzpw8jspv-python3-3.5.2/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
    module = __import__(module_name)
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/views.py", line 29, in <module>
    from filebrowser_safe.settings import *
  File "/tmp/nix-build-python3.5-filebrowser_safe-0.3.6.drv-0/filebrowser_safe-0.3.6/filebrowser_safe/settings.py", line 17, in <module>
    DEFAULT_URL_TINYMCE = settings.STATIC_URL + "grappelli/tinymce/jscripts/tiny_mce/"
  File "/nix/store/jxw9yiqqzmi511f8gv0mgz0i5pb04yrs-python3.5-Django-1.10.2/lib/python3.5/site-packages/django/conf/__init__.py", line 53, in __getattr__
    self._setup(name)
  File "/nix/store/jxw9yiqqzmi511f8gv0mgz0i5pb04yrs-python3.5-Django-1.10.2/lib/python3.5/site-packages/django/conf/__init__.py", line 39, in _setup
    % (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting STATIC_URL, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
builder for ‘/nix/store/3188gzsrwa73blm33fb50ak719f4611h-python3.5-filebrowser_safe-0.3.6.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/dwxm15sw7a4inxcmc77fb9acdbahi7fn-python3.5-mezzanine-3.1.10.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/dwxm15sw7a4inxcmc77fb9acdbahi7fn-python3.5-mezzanine-3.1.10.drv’ failed

It is a filebrowser_safe problem.

However, it works for python33:
[14:07] igor@nixos-pc nixpkgs (master) $ nix-shell -I nixpkgs=~/nixpkgs -p python33Packages.mezzanine
[14:07] igor@nixos-pc nixpkgs (master) [nix-shell] % python3
Python 3.3.6 (default, Oct 12 2014, 07:03:57)
[GCC 5.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import mezzanine
>>> from mezzanine import utils
>>>


Remove self-assignment

Is there a reason for this assignment or can it be removed?
https://github.com/pallets/jinja/blob/274eff178d1dedcedf488a586f414a03952ac733/jinja2/_compat.py#L67

Looks like a leftover from this:
https://github.com/pallets/jinja/commit/28c7488224102aea5cc5045a837c88e3820d86ba#diff-65d3fed441e0bee9895176265b373c3bL50
I doubt it's needed.. maybe just to be explicit?

It's assigning a built-in to a local variable, so that from ._compat import intern works. Removing it would mean it would only be locally defined for Python 3, and would fail to import on Python 2.


Discuss with original maintainer a plan to migrate existing data, issues or more

The original repo is still going to attract a bunch of attention; so if we can get everything pointing here / issues turned off that might be handy.

I spent a bit of time looking at this; and its annoying that the RiotGames rbenv cookbook is the only one on the supermarket.
I pushed an v0.7.3 release tag; but it'd be good to publish this somewhere people can get the fixes easily.

Maybe @fnichol can add a DEPRECATED section in the original cookbook's README.

@CloCkWeRX If it makes sense, I could transfer fnichol/chef-rbenv to chef-rbenv/chef-rbenv which would maintain the git clone urls, issues, etc. The downside is that there would be some git work to take the work here back to the older repo and that this repo name would have to be renamed to something else (for the transfer to work anyway).
Would this straight move help things or muddy the waters further? @josacar's has a way to go as well with making it clear on the original repo

Agreed with @fnichol , we can replay all the work here later, but we will not lose track of pending issues or PRs


Added entities modifier to code block

If you output HTML here (inside the code block) then it gets rendered by the browser rather than outputting it. Added an entities modifier means the user sees the HTML itself, as you'd expect in a code block.

Good one, thanks!


job name shouldn't be tied to the job history

When I rename my job, I'd like to keep the job's history. Having a separate display name would work, or keeping track of history using another ID.

Moved to concourse/concourse#1128


MEM Endpoint Security - Defender Firewall - Allow Microsoft Teams ?

Please update article with instructions on how to add Teams exception to Windows Defender Firewall with MEM (Intune) Windows 10 management.
It's counter intuitive that admins have to run powershell scripts to create firewall exceptions for Microsoft's own products.

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

ID: 6457d204-d229-9154-28fd-ca9bbb4bddcd
Version Independent ID: f5d82846-41cb-3548-6997-ce23bd8f89c6
Content: Get clients for Microsoft Teams - Microsoft Teams
Content Source: Teams/get-clients.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@TechTrooper  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@TechTrooper Thank you for reaching out and helping improve MS Docs. Please have a look at this link and let me know if it helps

https://docs.microsoft.com/windows/security/threat-protection/windows-firewall/create-windows-firewall-rules-in-intune

@TechTrooper Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


use in operator for argv to prevent provision error

I got following error on OSX (Python 2.7.10) by running vagrant up:
==> default: ++ python /srv/zulip/provision.py
==> default: Traceback (most recent call last):
==> default:   File "/srv/zulip/provision.py", line 55, in <module>
==> default:
==> default: if sys.argv[1] == "--travis":
==> default: IndexError
==> default: :
==> default: list index out of range

I changed the way of checking --travis arg.

Automated message from Dropbox CLA bot
@nemeth, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here and update the thread so we can consider merging your code.

Since the original change introducing the bug had been reverted, I squashed this fix into that commit when merging it again.  Thanks for the contribution!


Package dependencies

As far as I can see, the Suggests dependencies of a package are not included in the docker containers. Would you consider adding these? It would be nice to be able to run all examples and vignette code of the packages available in a container.

Unfortunately we are short staffed right now and can't get to this. I'd accept a patch/pull request if you want to submit one.

Sorry for the delayed response.  In generally we wanted to have just the basic necessities provided.  Adding all the suggested packages could make the docker images very large and unmanageable.  We feel like the user can add the suggested packages as needed after loading the docker container.


Clients should send oadrRegisterReport even when no reports are registered

Hello,
I think I've found a bug in the clients. According to the OpenADR 2.0b specs, a VEN (and a VTN, but I haven't tested it yet, I'm implementing a VEN) should sent a METADATA report even when it doesn't support any reporting capabilities, for informing the VTN that it doesn't have any.
Maybe I'm doing it wrong, but it doesn't seem to send anything if no reports are registered.
Any comments?

You may be right; I think this needs to be added to the client code.


Change old style strings to f strings

Changed older style strings to f strings for ping, netperf, and netperf_pps benchmarks
I also changed netperf_pps.py to netperf_pps_benchmark.py to make it consistent with all of the other files

I reverted all of the logging statements to use %.
I split the netperf commands into multiple lines in a way that hopefully increases readability.

I reverted all of the logging statements to use %.
I split the netperf commands into multiple lines in a way that hopefully increases readability.

I have also tested each benchmark to make sure they still function the same, including each of the flags that have logic affected by this change.

I have also tested each benchmark to make sure they still function the same, including each of the flags that have logic affected by this change.

LGTM - thanks!!

LGTM - thanks!!

So we're trying to pre-clean some of the existing linter issues in https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/commit/c7406e65b15a8037e450d316053c0c886df2a1fe which I think means you'll need to remerge?

So we're trying to pre-clean some of the existing linter issues in https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/commit/c7406e65b15a8037e450d316053c0c886df2a1fe which I think means you'll need to remerge?


[BUG] Emissive textures doesn't save

Describe the bug
GO with emissive they are not being loaded after save.
To Reproduce
Steps to reproduce the behavior:

Go to a GO with textures
Put him an Emissive Texture
Save and Load
See error

Expected behavior
Emissive texture being loaded properly.

I'll assign this bug to @raulgolzalezupc

Is this still happening @JorxSS ?

Not anymore we can close it


Hard code config values that may lead to network instability

We had some nodes report the following error:
1:04PM ERR Stopping peer for error err="received message exceeds available capacity: 1900008 < 1900544" module=p2p peer={"Data":{},"Logger":{}}

This comes about because some nodes have a MaxTxBytes set to 1.9MB and others to 7.9MB. This difference means that some transactions get accepted to some mempools but not to others.
Proposal
Hard code config values that may lead to network instability. Specifically this means to hardcode MaxTxBytes. There may be other parameters we may want to consider

closing as we have timeouts that overwritten in v3


Changed order of Update and Delete button in post.ejs and added Choose file option in compose.ejs

Changed order of Update and Delete button in post.ejs and added Choose file option in compose.ejs

Also need to add .env file and also we can use routers to declutter app.js

ok

wait issue open krta


how to understand unlabeled frames vs temporal context frames?

hi, lightning pose team
As the tutorial mentions, both base model and context model make use of unlabeled frames but context model utilizes temporal context frames.
so what is the difference and relation between unlabeled frames vs temporal context frames? Are temporal context frames derived from unlabeled frames?

dali.base.train.sequence_length - number of unlabeled frames per batch in regression and heatmap models (i.e. “base” models that do not use temporal context frames)

dali.context.train.batch_size - number of unlabeled frames per batch in heatmap_mhcrnn model (i.e. “context” models that utilize temporal context frames); each frame in this batch will be accompanied by context frames, so the true batch size will actually be larger than this number

Thanks for the question @Wulin-Tan - let me know if this clears things up:
temporal context frames
Temporal context frames refer to the frames that come directly before/after a given labeled frame. Specifically, we consider the 2 frames before and 2 frames after each labeled frame, and the 5-frame chunk is processed all at once to produce pose estimates for the central, labeled frame. Importantly, the temporal context frames do not require labels; we only need labels for the central frame.
To utilize temporal context frames you must set the model.model_type parameter in the config file to heatmap_mhcrnn.
unsupervised losses
Using the unsupervised losses is a second, complementary way to introduce unlabeled frames into the training process. Unsupervised losses are computed on chunks of unlabeled videos. These videos can be the same ones that the labeled frames come from; they can also be completely different videos (as long as the experimental setup is the same) or a mix between the two.
To utilize the unsupervised losses you must set the model.losses_to_use parameter in the config file to be a non-empty list (more info here). The size of the unlabeled batches is governed by dali.base.train.sequence_length.
combining the two
Because the temporal context frames and the unsupervised losses act independently (one requires a modification of the network architecture, the other requires a modification of the loss), the two can be combined seamlessly. This means that, for labeled data, chunks of 5 frames are used to predict the pose of the central frame, which can then be compared to the ground truth. At the same time, the unlabeled video data also uses 5-frame chunks to create a prediction for the central frame. In this case we do not have ground truth data, and therefore the unsupervised losses are computed on those predictions.
As a concrete example, imagine you set the unlabeled batch size to be 10 (using dali.context.train.batch_size). If we index the frames starting from zero, we have frames {0, ..., 9}. The model will not be able to form a prediction for the first and last two frames. We cannot make a prediction on frame 0 because that requires frames -1 and -2, which we do not have access to in the batch (as well as frames 1 and 2, which we do in fact have access to). However, we can start to form a prediction on frame 2, which requires frames {0, 1, 2, 3, 4}. Likewise, we can form predictions for frames 3-7. We cannot form predictions for frames 8 and 9, which requires later frames which we do not have access to in the batch. [Therefore the minimum accepted value for dali.context.train.batch_size is 5 - this will create a single prediction on the central frame.]

Hi, @themattinthehatt
Thank you for your detailed explanation! That's pretty good for me to understand LP.
My understanding is as follows: (please correct me if I am wrong)

In DLC, usually smoothing (interpolation or imputation) for the unconfident prediction would be done after new videos prediction. But in LP, this smoothing is incorporated as part of the training.
Regarding the prediction, most algorithm including DLC, would do frame by frame. But LP constructs kinds of a 'sliding window' network, named TCN in LP, to include the neighboring information for prediction.
In LP, both base and temporal models made use of unsupervised loss / unlabeled frames during training for smoothing, but when it goes to prediction, only temporal models make use of 2+1+2 frame information.
by the way, in your preprint, Figure 2: Exploiting unlabeled videos in pose estimation model training, plus your explanation, helps me a lot in understanding.

Yes that all sounds correct! Just to be a bit more precise on your point 3, I would say that both the base and TCN models can use unsupervised losses, but they don't necessarily have to (remember that the model architecture - base or TCN - is controlled in the config file by model.model_type, whereas the unsupervised losses are controlled by model.losses_to_use). Each of these will contribute to smoother predictions in their own way. The TCN will make for smoother predictions becasuse it can look forward and backward in time to localize keypoints better. The unsupervised loss (specifically the "temporal" loss) will penalize large jumps in the predictions. I should also mention here that we played around with the temporal loss quite a bit and it doesn't actually work well if you try to set small numbers for the allowed temporal jumps (in losses.temporal.epsilon). The temporal loss is much more effective if epsilon is large (we use 20 pixels for frames that are 400x400, for example, but this will depend on your experimental setup). In this case the loss will penalize really large jumps, but it won't remove small jitters in the predictions (see EKS comment below for a better way to deal with small jitter).
And then yes, at prediction time the base model only processes one frame at a time, whereas the TCN model will make use of 2+1+2 frame information.
I would also recommend checking out the ensemble kalman smoother (EKS) package when you get a chance - this allows you to actually enforce temporal smoothness on the predictions, and we have found it to work very well across a lot of datasets. This post-processor will definitely do a good job of removing jitter in your predictions.


Unexpected result using your example of converting 36 hours to "best" units

console.log(convert(36, 'h').to('days').toString());
'1.5'

console.log(convert(36, 'h').to('days'));
1.5

console.log(convert(36, 'h').to('best').toString());  // your example of using 'best'
'1.4999999999999998d'

console.log(convert(36, 'h').to('best'));
{
  quantity: 1.4999999999999998,
  unit: 'd',
  toString: ƒ ()
}

Hi! Thanks for making the report, I'm currently not feeling super well at the moment, but I should be able to take a look at it in a few days/this weekend.
The reason this behavior happens is because the math used internally is very slightly different when you convert to the best unit, hence the inconsistent results. I can likely fix this fairly easily by just making a call to the main conversion code when converting to the best unit, instead of having two separate implementations.

:tada: This issue has been resolved in version 4.14.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Change template and plugin details, taking not the array but the payload

@tonysnowboardunderthebridge I cannot find the place in meraki where it uses /package-manager/stackables/available/${id} request. Maybe you can point me.

@ivan-tymoshenko my fault, I forget that on meraki we don't call the api for single endpoint but we will send the props directly to the template/plugin detail.


Why limit Push-To-Talk to a specific window?

If you are using Teamspeak with a PTT-hotkey then you probably want to send the key to any window as long as TS is running in the background.
Minor issues:

Save the PPT-hotkey in the settings?
Do not change the overall enabled state on changes to the PTT settings?

I don't remember exactly why I made it like that. I think it was because (some) games wouldn't detect a virtual key press if it was pressed globally, but it worked when I used the current method. I may look into it.

That totally makes sense; especially if the push-to-talk key is only relevant to the one game you are playing. But with an application like Teamspeak, which accepts the key on any foreground application it might come in handy to be able to turn this limit off. Think of games with a separate launcher in a different window; you probably want to speak there too?

I'm not sure what you mean by separate launcher?

Two windows: a launcher for preparing and matchmaking and a second application; the actual game that only gets opened once a match is found.
The point is, that one might want to use the ptt functionality on different windows.
A simple option to choose whether to limit the ptt key would be a nice feature. (allow empty selection in the list box)

Sounds like a good idea, I'll add the functionality today

Could you potentially compile an updated version? If not, show us how to compile it? I'm very interested in this but I need this update since it's not working in PUBG for some reason.


linux-iot2050: The green light is out of control when panic occurs

The green light is out of control when panic occurs.
it should be off then.
Indicates that the green light is off when panic.Add configuration
to the device tree to fix it.
Signed-off-by: chao zeng<EMAIL_ADDRESS>

Should go into a separate patch: It does not use upstream mechanisms, and the modified patch is actually a clean upstream backport.

Use one standlone patch to fix this issue.


Newer OS Such as 14 on S24 Doesn't allow install. App isn't compatible with your Phone.

I'm a big fan of Powerslide and other RatBag\DTR derivatives and was very happy to see and even use this remake on older versions of android. But now on my S24 Android 14 One UI 6.1, it shows a "App isn't compatible with your Phone." error when attempting to install the 1.18 apk version from moddb. I understand if you've moved on and away from this project, but i would be grateful if someone can update this to be compatible with modern Android and phones.
Thanks,

Issue reproduced on S23, seems new version of android doesn't support armeabi-v7a


Massive simplification and lazy loading

Hi :)
some bugs 🐛

QABCD show data available, I can download the manifest for one sample (also the project says in the count overview that it consists of 1 sample), but if I go to the sample view I see only samples with no status information (project view != sample view)

I was looking over the UI in portal-testing and the following caught my attention:

[ ]  Project Title Column is too big, we restricted it to give the statuses space
[ ] Alignment der Statuse header should be in one line (is now in two), maybe because of the title

Further comments:

I think we should move projects with 0 samples to the bottom of the list. Otherwise you might only see new projects which do not have  status information. I am not sure how we can make that easier for a customer or maybe we should check back with them
I think its not good to show 'Information not available'. Its very confusing. Cant we assume that their metadata was registered? I think its good to not count those samples to the status samples in the project overview. But it does not add up to show them in the sample view.

Hi :)
some bugs 🐛

QABCD show data available, I can download the manifest for one sample (also the project says in the count overview that it consists of 1 sample), but if I go to the sample view I see only samples with no status information (project view != sample view)

This is due to the fact that one artificial sample was added to the project in the sample tracking database at some point. This sample does not exist. This is a testing artefact.

I was looking over the UI in portal-testing and the following caught my attention:

[ ]   Project Title Column is too big, we restricted it to give the statuses space
[ ]  Alignment der Statuse header should be in one line (is now in two), maybe because of the title

Further comments:

I think we should move projects with 0 samples to the bottom of the list. Otherwise you might only see new projects which do not have  status information. I am not sure how we can make that easier for a customer or maybe we should check back with them
I don't think we can do this as this was the primary problem of loading all data before visualization. We need to take the openbis data as base.

I think its not good to show 'Information not available'. Its very confusing. Cant we assume that their metadata was registered? I think its good to not count those samples to the status samples in the project overview. But it does not add up to show them in the sample view.
Sadly, I deployed it in production and there is no information available for a lot of projects and samples. This should not be the case as I understood it but it is the case for some reason. Once again a mismatch between openbis and sampletracking exists that should not exist.

Follow-up comment:
Also I think we should remove projects with 0 samples completely from the list (0/0 samples)