Proposal: 'configurator' field in package.json

tl;dr
Add a field to package.json that tells ESLint, Flow, other tools, where to look for configs.
Useful for zero-conf opinionated packages like create-react-app and standard.
  // ESLint will look for react-scripts/config/.eslintrc
  // Flow will look for react-scripts/config/.flowconfig
  "configurator": "react-scripts"

As a community, we’ve mostly solved the problem of nested, extendable configuration. ESLint does this really well, Babel also does this.
However, I think that this project gaining 4k stars in 4 days proves that there is a market for non-configurable opinionated tools hiding dependencies from the user. I’d like to give props to standard for being one of the first tools demonstrating this is a viable model (it doesn’t matter whether I agree with its choices).
The problem I‘m starting to see is that many amazing tools, like ESLint and Flow, don’t currently play very well with this approach out of the box.
Problem
ESLint
ESLint is very flexible but if you want IDE integration, you need to tell it where your config is.
This is why our otherwise zeroconf package.json now has to look like this:
{
  "name": "my-app",
  "version": "0.0.1",
  "private": true,
  "devDependencies": {
    "react-scripts": "0.1.0"
  },
  "dependencies": {
    "react": "^15.2.1",
    "react-dom": "^15.2.1"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "./node_modules/react-scripts/config/eslint.js" // 😁
  }
}

Yes, one extra field is not a high price, but it is already a bit frustrating that we have to hardcode ESLint there. We would like to treat it as an implementation detail, to the extent that it is reasonable. (e.g. eslint-ignore comments are fine, but putting paths to configs into user’s package.json is annoying)
Also, it doesn’t even solve the problem completely because ESLint will look for plugins relative to the project root, so any transitive plugin dependencies won’t be discovered with npm 2 (or in some cases, admittedly not likely with our tool, with npm 3). You can find the discussion about this in eslint/eslint#3458.
Flow
Flow poses a similar problem for us, although in a more unfortunate way. We can’t even tell Flow to look at a different config. When you run flow init, it creates .flowconfig in the project root, and that’s it. This is reasonable if the user plans to change it (which seems necessary for lib integrations), but we can’t even influence the default generated config in any way.  And unfortunately, for a number of reasons, the default generated config won’t work for create-react-app.
If you want Flow to work, you need to replace the config generated by flow init with this one:
[libs]
./node_modules/fbjs/flow/lib

[options]
esproposal.class_static_fields=enable
esproposal.class_instance_fields=enable

module.name_mapper='^\(.*\)\.css$' -> 'react-scripts/config/flow/css'
module.name_mapper='^\(.*\)\.\(jpg\|png\|gif\|eot\|svg\|ttf\|woff\|woff2\|mp4\|webm\)$' -> 'react-scripts/config/flow/file'

suppress_type=$FlowIssue
suppress_type=$FlowFixMe

And we don’t want to do this automatically because:

Many people don’t currently use Flow.
Our philosophy is to not generate a ton of configs in the user folder.
We want the config to be compatible with the current version of react-scripts, so if we generate Flow config before the person actually starts using Flow, by the time they start using it, their checks might fail because something changed on our side.

Solution?
I don’t know if there is a nice solution to this, but here is my proposal. This is how I want package.json to look:
{
  "name": "my-app",
  "version": "0.0.1",
  "private": true,
  "devDependencies": {
    "react-scripts": "0.1.0"
  },
  "dependencies": {
    "react": "^15.2.1",
    "react-dom": "^15.2.1"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "eject": "react-scripts eject"
  },
  "configurator": "react-scripts" // 😀
}

ESLint would then use react-scripts/config as the base directory for its regular config/plugin search mechanism. So it would look for .eslintrc, package.json, etc, in that directory, and resolve plugin modules relative to it. Since ESLint wants to stay configurable, it will also look for overrides in the current folder (and use its regular override mechanism), but this would just add configurator as a first-class citizen for providing configuration.
Similarly, Flow would look into that project when running flow init, and if it finds .flowconfig in react-scripts/config, it would use that instead of its default config. This gives us a way to own the default configuration even if the user is on their own. In the future, Flow could support merging ${configurator}/config/.flowconfig with local .flowconfig—similar to how ESLint would work if it implemented this feature.
This would benefit an ecosystem by fostering development of opinionated presets of preconfigured tools. If you’re a tool, honor configurator in package.json and try reading configuration from ${configurator}/config in addition to your normal lookup paths. If you’re a preset author, you can fork react-scripts or any other configurator, make some changes to it, and keep it simple to adopt your preset: just swapping configurator is all end users need to do.
What do you think? Am I missing something?

One thing I know about npm is it has a config option[1] inside the package.json that almost all of these modules SHOULD use, but don't. They create their own instance on the base object.
Maybe extend this, to check if $npm_package_config env var to see if it's a configurator project and handle that way.
I do like the idea of this though.
[1]: https://docs.npmjs.com/files/package.json#config

Yeah, it serves a different purpose though (we could probably use it for stuff like choosing ports in the future). What I suggest here is a way to “redirect” tool-specific configuration. You can use config and configurator side by side. I see how the naming could be a little confusing though but I don’t think it’s a big deal, and better naming is welcome!

I really like the idea though, I use package.json to set a lot of options for all these tools because I hate littering my directory with dot, yaml, and json files just for each tool I use. I'd totally help with pull requests to project implementing a configurator loader.

There's already a thousand ways that all those tools can figure out where to find the configuration, it's really unclear to me that adding yet another one is the right solution. Also, adding a hardcoded path to the config that the tools can read means that anybody can also read it and it's not a blackbox anymore.
Proposal instead:
Have the IDEs read package.json and if there's a script called eslint, then use it instead of the global eslint.
Then, we would add an opaque script that calls eslint with --config=opaquepath/eslintrc

@vjeux I don't think that solves the problem of the proliferation of information in the package.json that the user shouldn't need to worry about.  They will at a minimum end up seeing a script for eslint and a script for flow.  It also prevents IDE based tooling from doing any kind of inspecting of what your config is (e.g. IDEs could detect what indentation rules you use from eslint to auto-configure the behaviour of tab).

Have the IDEs read package.json and if there's a script called eslint, then use it instead of the global eslint.

I like the simplicity of this. I agree with @ForbesLindesay this doesn’t solve the config proliferation problem though so I‘m not sure it’s much better than the status quo. This is more or less what we’re doing anyway with eslintConfig field.
Also, this doesn’t solve the Flow issue, does it?

I think the idea would be that you would run react-scripts flow and that would cause us to call flow with whatever arguments flow needed in order to have the correctly configured options.  I'm not sure that would work very well though, especially with all flow's persistent server architecture quirks.

I'm not sure I understand the issue with flow being a server. If the IDE uses it as a server it is going to call it once with the options. If it uses it as a standalone tool it's going to call it multiple times. Having a wrapper that sets the config flag shouldn't change anything?
The goal here is to tell the IDE/CI... how to invoke the tools properly configured without letting them introspect the actual configuration. This way they don't end up relying on specifics.

The downside is that every IDE/plugin would need to implement this. So, for each of N tools (ESLint, Flow), there would be M plugins (Atom, Sublime), and NxM (ESLint for Atom, ESLint for Sublime, Flow for Atom, ...) integrations.
Whereas if we do this on the tool level, we only need the N tools to integrate this.

Would it? Don't those tools just effectively run ESLint? If the eslint binary can handle it, why would it be any extra work for IDEs?

Would it? Don't those tools just effectively run ESLint? If the eslint binary can handle it, why would it be any extra work for IDEs?

Sorry, I meant @vjeux’s proposal. Edited the message.

A different approach is used in Python packaging with a file in the package root named 'setup.cfg' into which tools can have have a section (or not) with their configurations: https://docs.python.org/3/distutils/configfile.html
When the tool is invoked it reads it's config from the setup.cfg.

@saschwarz This is very similar to how package.json configuration works now (you can find an example with eslintConfig in the post). But it means that user’s package.json gets bloated with configuration links that don’t matter if you use a zeroconf tool like create-react-app.

@vjeux The issue is that flow is way more complicated than just "run it once" or "run it many times".  There is flo which is the server/demon part and flow which is basically just a client for flo, but I think the IDEs might call directly into flo.  I'm not really certain of any of this, it just strikes me that the npm scripts approach could get very complex very fast, and as @gaearon suggests, all m * n plugins for IDEs and editors need to deal with that complexity, not just the n different linters and build tools.

@gaearon Sorry I wasn't being clear. I meant it as an additional file just for tool configs; the package.json would hold everything else: dependencies, user scripts, etc. One advantage of a separate tooling config file is it is likely to be the same across multiple projects for a user/organization.

I really dig the concept of abstracting away the build configurations.  Copy/pasting scripts to handle bundling or workflow management has been plaguing us since the days of grunt and gulp tasks.  react-scripts is a huge step in the right direction.  Great stuff guys.
Would it make sense to allow configurator to accept an object of tool directories?  This would allow users to stay with react-scripts where needed while easily mixing with other presets.
This may be unnecessary complexity, as default configs can still be used, but wanted to see what you guys thought.
Something like -
{
  "name": "my-app",
  "version": "0.0.1",
  "private": true,
  "devDependencies": {
    "react-scripts": "0.1.0",
    "other-scripts": "0.1.0"
  },
  "dependencies": {...},
  "scripts": {...},
  "configurator": { // 😀
    "flow": "react-scripts",
    "eslint": "other-scripts"
  }
}

@gaearon why not use npm config? https://docs.npmjs.com/files/package.json#config
{
  ...,
  "config": {
    "eslint": "react-scripts",
    "flow": "react-scripts"
  }
}

This feels like an oversimplification of the complexity of how tools interact with one another.
There is a place for extending configuration in just about every tool in existence, and the way those need to work vary between tool to tool.
If you are to avoid wrapping every tool in one of those gulp/grunt-* packages then there needs to be an open ended solution on how to extend config dynamically.

I agree with @thejameskyle there.
This seems like a potentially dangerous attempt to generalize from n = 1.
It's worth at least waiting to see how things pan out before promulgating a new standard that multiple tooling vendors would be expected to follow.

Good points. I think the problem is still worth exploring but I'd like to hear more alternative solutions for delegating configuration.


Upgrading to vue 2.7 broke vue-grid-layout

Version
2.7.0
Reproduction link
codepen.io/collection/GoZoMJ
Steps to reproduce
After opening the second code pen from the collection (version 2.7) you will see a grid of numbered rectangular gray panes.
Try dragging them around with the mouse or resizing them by the lower right corner.
What is expected?
The rectangular panes should be draggable and resizable with the mouse.
What is actually happening?
Panel dragging and resizing doesn't work.
It does work if vue 2.6.14 is used, like in the first code pen from the collection.

Please open the issue in vue-grid-layout


Add ADS1015 support to ads111x lib.

ADS101x is a faster version of ADS111x ADC, with lower precision.
This change provides basic support for device, by defining sample rates used by ADS101x and providing new ads101x_get_value() function with proper 4-bit shift to obtain actual ADC value.

Thank you!


Add Babel (JavaScript transpiler) packages to nodePackages

These patches add to nodePackages many packages from NPM for the
JavaScript "transpiler" Babel, specifically —

babel-cli,
babel-eslint,
babel-polyfill,
Babel's "presets", and
Babel's many "transforms".

Additionally, the regeneration of the generated nodePackages files
resulted in the pbkdf2 package being updated.
I have tested the added Babel packages per nixpkgs manual section 10.1
("Making patches"), on a NixOS system on the nixos-unstable channel
with build sandboxing enabled.

Some of the packages are OK for inclusion (e.g. babel-cli), but for others I'm not entirely sure whether they should be in Nixpkgs.
In principle, we should only include end-user NPM packages in Nixpkgs (such as command-line tools), but not any libraries or plugins, unless they are used by non-NPM packages in Nixpkgs.
The biggest reason why we should exclude libraries/plugins is that NPM dependencies compose differently depending on their contexts. This is something npm2nix did not simulate very well. In contrast, node2nix does dependency management differently (and more accurately) and makes the inclusion of libraries more expensive.
The second reason why not all packages can be included, is because node2nix composes entire dependency trees in one derivation, so it makes no sense to refer to them the "Nix way".
If you want to know more about NPM dependency "simulation" in Nix: I have written an elaborate blog post about this a while ago: http://sandervanderburg.blogspot.com/2016/02/managing-npm-flat-module-installations.html
Typically, babel plugins are supposed to be installed as devDependencies of a development project. A better workflow would be to directly use node2nix on a package.json file of a development project.
Consult the README.md file of node2nix for more information on how to use node2nix in development projects. I think section: 'Adding additional/global NPM packages to a packaging process' is particularly important -- it describes how to use grunt and grunt plugins. I think the same workflow applies to babel (and its corresponding plugins).
I also think that using node2nix on a package.json file is much more convenient than manually composing Nix expressions that refer to NPM library packages in Nixpkgs.
So to summarize: if you intend to use Nix for a Node.js development project, use node2nix directly on the project to provide it the libraries it needs.

Ah. My apologies for filing this PR without understanding nixpkgs' NPM packaging.

Are linters like htmlhint appropriate for inclusion?

@8573 Yes that is a command-line utility


labgrid-exporter: export FTDIs with multiple separate interfaces

Some FTDIs pop up as multiple USB interfaces on the host system. Let's export there as well. This could've been done in the userconfig.yaml, but it's more convenient to just do this here centrally.
We'll just export the main interface and three more and assume 4 FTDIs is enough for everybody.

This is exactly the same setup we are already using in production on our lab system. LGTM


Prefix the names of methods that create a new object with "new_".

Sometimes a method named after a type of object is a lookup function, and sometimes it's a creation function. This is inconsistent. Methods named after objects should be assumed to look up that object unless prefixed with "new_".

Nevermind it, I fixed this another way in 596cea9643d8e02dc0b48d43e95a3fecc8292e9d.


Fix build when TCP is disabled

Description
This PR fixes build when USE_TCP option is disabled and SUPPORT_SELECT_FUNCTION or DHCP_HOOK are enabled.
Test Steps
Run build test with all options enabled except for USE_TCP.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks @bjsowa for checking out the dev/IPv6_integration branch and for this PR, however this change along with other configuration related build fixes are done as part of the PR#855 and is currently undergoing review. Please check if this fixes the issue.

Thanks @bjsowa for checking out the dev/IPv6_integration branch and for this PR, however this change along with other configuration related build fixes are done as part of the PR#855 and is currently undergoing review. Please check if that fixes the issue.

I checked the PR and it seems to fix this issue. I'll also make sure it works on the next release candidate.

Hi @bjsowa , The branch dev/ipv6_integration branch supports both IPv4 and IPv6. I was curious if the product that you are working on uses IPv6 and if it would be okay for you to share your feedbacks and suggestions on IPv6 functionality.

Sorry to disappoint you but we are currently not using IPv6 in our project. I just wanted to consume the stack with CMake using FetchContent and also use a taggged version, so I decided to use V4.0.0-rc2 which is based on dev/IPv6_integration branch.

Thanks


import-analysis false positive

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[X] Read the docs.
[X] Use Vite >=2.0. (1.x is no longer supported)

Describe the bug
When including svelte in dependencies I get the message:

Internal server error: Deep import "svelte/internal" should be avoided because dependency "svelte" has been pre-optimized. Prefer importing directly from the module entry:
import { ... } from "svelte"
If the used import is not exported from the package's main entry and can only be attained via deep import, you can explicitly add the deep import path to "optimizeDeps.include" in vite.config.js.

However, my app doesn't directly use anything from svelte/internal, so I'm surprised I would be getting this message. The svelte/internal stuff is only used by the svelte library itself
Reproduction
Check out https://github.com/benmccann/vite-svelte and move svelte from devDependencies to dependencies
System Info

vite version: 2.0.0-beta.36
Operating System: Ubuntu
Node version: 14.8.0
Package manager (npm/yarn/pnpm) and version: npm 6.14.11

It seems putting Svelte in devDependencies is fine. Here's an explanation: https://github.com/rixo/svelte-hmr/issues/24#issuecomment-765232063

It seems putting Svelte in devDependencies is fine. Here's an explanation: https://github.com/rixo/svelte-hmr/issues/24#issuecomment-765232063

The svelte-generated code does import svelte/internal, but moving to devDeps works too.

The svelte-generated code does import svelte/internal, but moving to devDeps works too.


Fix GcNotification tests on Mac.

@Tratcher

Hi @cesarbs, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:


Force grpclib to be at least 0.4.8rc2

This release candidate fixes an important bug when using IPv6 addresses.
Fixes #1003.

I will release v1.0.0rc701 with this. I don't think we should merge it to v1.x.x yet, as once a final release is out, we don't need to put the rc in the dependencies. But we need to put it for now as we don't accept rcs implicitly.


no data in rabbitmq

Hello,
This is my setup:
chirpstack-gateway-bridge

cat docker-compose.yml

version: '3.6'
networks:
  loranet:
    external: true
services:
  chirpstack-gateway-bridge:
    image: chirpstack/chirpstack-gateway-bridge:3.14.0
    container_name: gatewaybridge
    hostname: gatewaybridge
    restart: always
    logging:
      options:
        max-size: "10m"
        max-file: "3"
    ports:
      - "1700:1700/udp"
    volumes:
      - ./chirpstack-gateway-bridge.toml:/etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
    networks:
      loranet:

udp-packet-forwarder

cat docker-compose.yml

version: '3.6'
networks:
  loranet:
    external: true
services:
  udp-packet-forwarder:
    image: rakwireless/udp-packet-forwarder:v1.1.3
    container_name: udpforwarder
    hostname: udpforwarder
    restart: always
    logging:
      options:
        max-size: "10m"
        max-file: "3"
    privileged: true
    volumes:
      - ./global_conf.json:/app/global_conf.json:ro
    environment:
      MODEL: "RAK7371"
      MODULE: "RAK5146"
      CONCENTRATOR: "SX1303"
      HAS_GPS: "0"
      INTERFACE: "USB"
      GATEWAY_EUI: "26E804FFFE7093C0"
      SERVER_HOST: "gatewaybridge.loranet"
      SERVER_PORT: "1700"
      RADIO_DEV: "/dev/ttyACM0"
      GATEWAY_EUI_NIC: "usb0"
      BAND: "us_902_928"
    networks:
      loranet:

RabbitMQ mqtt plugin is enabled, where I see the connection established from chirpstack-gateway-bridge container. A queue is created mqtt-subscription-66C0A7FC63D30000qos0 which confirms successful creation of all the containers.
But when I send data from lora devices I do not see any data received by chirpstack-gateway-bridge or rabbitmq

Yes, logs are inline below. When I use mqtt-explorer client it shows the data but nothing persists in RabbitMQ.
udp-packet-forwarder docker logs

JSON up: {"rxpk":[{"jver":1,"tmst":516259720,"chan":0,"rfch":0,"freq":903.900000,"mid": 8,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-33,"lsnr":12.8,"foff":140,"rssi":-33,"size":19,"data":"QGwIAEiAMgAC2umcXqTCSN9dwA=="}]}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

INFO: Received pkt from mote: 4800086C (fcnt=51)

JSON up: {"rxpk":[{"jver":1,"tmst":536259394,"chan":6,"rfch":1,"freq":905.100000,"mid": 8,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-31,"lsnr":14.5,"foff":144,"rssi":-31,"size":19,"data":"QGwIAEiAMwACFJhLSo74gxmR6g=="}]}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms

##### 2022-07-19 23:33:58 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 2
# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 2 (38 bytes)
# PUSH_DATA datagrams sent: 3 (656 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 540833080
# SX1302 counter (PPS):  0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Invalid time reference (age:<PHONE_NUMBER> sec)
# no valid GPS coordinates available yet
##### END #####

JSON up: {"stat":{"time":"2022-07-19 23:33:58 GMT","lati":23.99595,"long":-103.12665,"alti":0,"rxnb":2,"rxok":2,"rxfw":2,"ackr":100.0,"dwnb":0,"txnb":0,"temp":29.6}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms

INFO: Received pkt from mote: 4800086C (fcnt=52)

JSON up: {"rxpk":[{"jver":1,"tmst":556258129,"chan":4,"rfch":1,"freq":904.700000,"mid": 9,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-33,"lsnr":13.2,"foff":141,"rssi":-32,"size":19,"data":"QGwIAEiANAACRsm988NsKGMCmg=="}]}
INFO: [up] PUSH_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

##### 2022-07-19 23:34:28 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 1
# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 1 (19 bytes)
# PUSH_DATA datagrams sent: 2 (412 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 570834526
# SX1302 counter (PPS):  0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Invalid time reference (age:<PHONE_NUMBER> sec)
# no valid GPS coordinates available yet
##### END #####

JSON up: {"stat":{"time":"2022-07-19 23:34:28 GMT","lati":23.99595,"long":-103.12665,"alti":0,"rxnb":1,"rxok":1,"rxfw":1,"ackr":100.0,"dwnb":0,"txnb":0,"temp":29.6}}
INFO: [up] PUSH_ACK received in 0 ms
ERROR: wrong coding rate (0) - timestamp_counter_correction

INFO: Received pkt from mote: 4800086C (fcnt=53)

JSON up: {"rxpk":[{"jver":1,"tmst":576258777,"chan":2,"rfch":0,"freq":904.300000,"mid": 8,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-33,"lsnr":9.2,"foff":144,"rssi":-33,"size":19,"data":"QGwIAEiANQAC1mUlPNEs0/V0rA=="}]}
INFO: [up] PUSH_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

INFO: Received pkt from mote: 4800086C (fcnt=54)

JSON up: {"rxpk":[{"jver":1,"tmst":596259419,"chan":5,"rfch":1,"freq":904.900000,"mid": 9,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-46,"lsnr":12.5,"foff":140,"rssi":-46,"size":19,"data":"QGwIAEiANgACSLljynfEB0YT8g=="}]}
INFO: [up] PUSH_ACK received in 0 ms

Gateway bridge docker logs

time="2022-07-19T23:34:14.109669444Z" level=info msg="integration/mqtt: publishing event" event=up qos=1 topic=gateway/66c0a7fc63d30000/event/up uplink_id=8edd1c5d-1c4e-45bf-8bb4-096f5756bf5e
time="2022-07-19T23:34:28.683682628Z" level=info msg="integration/mqtt: publishing event" event=stats qos=1 stats_id=bfbf277a-f731-4206-bd50-6eae89a94020 topic=gateway/66c0a7fc63d30000/event/stats
time="2022-07-19T23:34:34.107818012Z" level=info msg="integration/mqtt: publishing event" event=up qos=1 topic=gateway/66c0a7fc63d30000/event/up uplink_id=cbfda073-0f29-47f6-a8eb-8ee396817f21
time="2022-07-19T23:34:54.111437729Z" level=info msg="integration/mqtt: publishing event" event=up qos=1 topic=gateway/66c0a7fc63d30000/event/up uplink_id=c864f139-156b-44c5-bae6-1b93d90cdfbb
time="2022-07-19T23:34:58.677749907Z" level=info msg="integration/mqtt: publishing event" event=stats qos=1 stats_id=33e9a53c-81bc-410f-b1df-579ae5832e42 topic=gateway/66c0a7fc63d30000/event/stats

{
  "phyPayload": "QGwIAEiANAACRsm988NsKGMCmg==",
  "txInfo": {
    "frequency": 904700000,
    "modulation": "LORA",
    "loRaModulationInfo": {
      "bandwidth": 125,
      "spreadingFactor": 10,
      "codeRate": "4/5",
      "polarizationInversion": false
    }
  },
  "rxInfo": {
    "gatewayID": "ZsCn/GPTAAA=",
    "time": null,
    "timeSinceGPSEpoch": null,
    "rssi": -32,
    "loRaSNR": 13.2,
    "channel": 4,
    "rfChain": 1,
    "board": 0,
    "antenna": 0,
    "location": null,
    "fineTimestampType": "NONE",
    "context": "ISfTUQ==",
    "uplinkID": "jt0cXRxORb+LtAlvV1a/Xg==",
    "crcStatus": "CRC_OK"
  }
}

{
  "phyPayload": "QGwIAEiANQAC1mUlPNEs0/V0rA==",
  "txInfo": {
    "frequency": 904300000,
    "modulation": "LORA",
    "loRaModulationInfo": {
      "bandwidth": 125,
      "spreadingFactor": 10,
      "codeRate": "4/5",
      "polarizationInversion": false
    }
  },
  "rxInfo": {
    "gatewayID": "ZsCn/GPTAAA=",
    "time": null,
    "timeSinceGPSEpoch": null,
    "rssi": -33,
    "loRaSNR": 9.2,
    "channel": 2,
    "rfChain": 0,
    "board": 0,
    "antenna": 0,
    "location": null,
    "fineTimestampType": "NONE",
    "context": "IlkC2Q==",
    "uplinkID": "y/2gcw8pR/ao647jloF/IQ==",
    "crcStatus": "CRC_OK"
  }
}

Binding amp.topic with this routing key gateway.*.*.* helped fix the issue.
{"gatewayID":"ZsCn/GPTAAA=","state":"ONLINE"}

Binding amp.topic with this routing key gateway...* helped fix the issue.
{"gatewayID":"ZsCn/GPTAAA=","state":"ONLINE"}


User location

Prototype run 2

What issue does this resolve?

It retrieves user's location
On Wed, Oct 4, 2017 at 12:49 AM, Jesse Hartloff<EMAIL_ADDRESS>wrote:

What issue does this resolve?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yinyifu/cse442_watch/pull/24#issuecomment-334049077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQQ-nUU-tKV655Jxmq29GpUgUFJBJmvlks5sow5pgaJpZM4PiG39
.


uploader: module removal

INCOMPATIBLE Removes uploader module that it is not needed since
ACID database backend and new Invenio-Records module is in use.
(addresses #3283)

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

that it is not needed

INCOMPATIBLE Removes uploader module that is not needed anymore as per the new ACID database backend and the new Invenio-Records module.


Intro to Ruby

Link: https://github.com/UofTCoders/studyGroup/tree/gh-pages/lessons/rubyIntro
Author: Jenna Blumenthal
Description: A beginner-level introduction to the programming language Ruby

+1 :)


Use system FFI and expat

Just the Python 2.7 fixes from https://github.com/docker-library/python/pull/357

What does this fix?
Are the versions bundled with python too old to be useful? Are the versions in Alpine 3.6, 3.7, and 3.8 actually better?

It's the same fix you made here: https://github.com/docker-library/python/pull/205 Just added to Python 2.7. The same issue came up when running the tests for PGO in https://github.com/docker-library/python/pull/357 during the build. Python 2.7 segfaulted while testing ctypes.

The Debian versions didn't segfault, so I didn't change them.


Handle package.json browser object value

When browser is an object in package.json, it contains entries for libraries that should not be loaded by the browser. These should be mapped so that they end up in the systemjs config just like an override. So for package.json "browser":
"name": "some-package",
"browser": {
  "base64url": false,
  "bs58": false
}

We should automatically end up with the same result as adding this manual override:
  "bedrock": {
    "systemjs": {
      "packages": {
        "some-package": {
          "main": "lib/index.js",
          "defaultExtension": "js",
          "map": {
            "base64url": "@empty",
            "bs58": "@empty"
          }
        },

Of course, if we discover that we don't need systemjs anymore, we should avoid doing this work.

Closing as handled by webpack now.


Adds side-by-side diff for images

This adds a basic image diff and prints the width of the images (before and after). This is part of what was requested in #6255 .
Screenshot:

The side-by-side view for images will be active regardless whether split view is active or not.

Codecov Report

Merging #6784 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #6784      +/-   ##
==========================================
- Coverage   40.99%   40.97%   -0.03%
==========================================
  Files         421      421
  Lines       58054    58070      +16
==========================================
- Hits        23802    23794       -8
- Misses      31086    31110      +24
  Partials     3166     3166

Impacted Files
Coverage Δ

modules/templates/helper.go
46.59% <0%> (-2.08%)
:arrow_down:

routers/repo/pull.go
36.09% <0%> (-0.04%)
:arrow_down:

modules/log/router.go
90% <0%> (-2.5%)
:arrow_down:

modules/log/event.go
64.46% <0%> (-1.53%)
:arrow_down:

routers/repo/view.go
42.02% <0%> (-1.02%)
:arrow_down:

Continue to review full report at Codecov.

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

Probably better would be to have Width: 1156, Height: 412 instead of W: 1156, H: 412
Also what will happen with very large images?

The images are embedded how they were uploaded in the repository, i.e. in their full dimensions.
The width is limited by width: 100% in .diff-file-box.file-content img which is already present.

If it's not too hard, I'd request adding a size below each image. Would be useful to compare size optimizations:

If it's not too hard, I'd request adding a size below each image. Would be useful to compare size optimizations

I'll look into that. :) I assume that the filesystem library is able to do that.

There we go. :)

@lafriks Done :)

conflicted

You CSS for some reason does not include autoprefixer rules. Can you rebase against master again and do
rm -rf node_modules
npm install
make css

Thanks, that fixed it.

conflicted

need @jonasfranz 's approval

What happens if I commit big images? We should maybe not open those if they're too big.

What happens if I commit big images? We should maybe not open those if they're too big.

Big as in file size?
Not sure why file size would be an issue. I guess travelling programmers which rely on cellular network with limited bandwidth or traffic volume would welcome not loading a 5 MB image. Is this a use case Gitea generally considers?
Big as in large dimensions? See:

The images are embedded how they were uploaded in the repository, i.e. in their full dimensions.
The width is limited by width: 100% in .diff-file-box.file-content img which is already present.

I don't see the need for a file size limit. It's the responsibility of the developer to not commit overly large files imho. There is no inherent performance issue for big images as there is for big diffs.

@jonasfranz please re-review

@saitho Please resolve the conflicts.
@jonasfranz Since they are two image medias, they will be loaded asynchrony by web browser. They will not block the main page loading when review.

conflicted
When I create a new empty repository and commit an image in the first commit, there will  be a corrupted old image. (see screenshot and code)

Okay. I'll do that on the weekend, as the PR isn't relevant for 1.9.0. ;)
Jonas Franz<EMAIL_ADDRESS>schrieb am Di., 9. Juli 2019, 22:21:

@jonasfranz requested changes on this pull request.
In routers/repo/pull.go
https://github.com/go-gitea/gitea/pull/6784#discussion_r301776142:

ctx.Data["RawPath"] = setting.AppSubURL + "/" + path.Join(headTarget, "raw", "commit", endCommitID)

ctx.Data["BeforeSourcePath"] = setting.AppSubURL + "/" + path.Join(baseTarget, "src", "commit", startCommitID)

Missing check? What happens if there is no startCommitID because it's the
first commit? (see my last comment)
In routers/repo/pull.go
https://github.com/go-gitea/gitea/pull/6784#discussion_r301776180:

ctx.Data["RawPath"] = setting.AppSubURL + "/" + path.Join(headTarget, "raw", "commit", endCommitID)

ctx.Data["BeforeSourcePath"] = setting.AppSubURL + "/" + path.Join(baseTarget, "src", "commit", startCommitID)
ctx.Data["BeforeRawPath"] = setting.AppSubURL + "/" + path.Join(baseTarget, "raw", "commit", startCommitID)

same
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/pull/6784?email_source=notifications&email_token=ABXUS7SZ677NYBA2C4CCDA3P6TXNVA5CNFSM4HI5BMVKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB55UPXA#pullrequestreview-259737564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXUS7SGVLDQFQH7JBKNVR3P6TXNVANCNFSM4HI5BMVA
.

Hey there. Sorry for the long delay.
Wasn't really motivated to work on Gitea - now I am. :)

2. When I create a new empty repository and commit an image in the first commit, there will  be a corrupted old image. (see screenshot and code)
   ![Screenshot_2019-07-09 geissler](https://user-images.githubusercontent.com/5757182/60919844-063e0500-a297-11e9-9304-4f0343286b00.png)

This happens when the image is newly added to the repository (i.e. is not in the index of the base commit). Fixed by only displaying the image if it exists in the base commit index.

Ready for review @jonasfranz

Could this PR have latest master merged in and CI restarted? Looks like CI problems are not from this PR.

Since @jonasfranz didn't response this one for a month and there are two approvals on this, I think we can merge this one when CI PASS.

@lunny @lafriks It looks like the tests I've added to the UTF functions are quite problematic. They fail only from time to time. I guess it's a LOCALE setting. Can a specific LOCALE be forced in the Makefile for the tests? Something like LOCALE=en_US.UTF-8 or any other, as long as it is always the same.

Otherwise, I'd remove most of the UTF8 tests. I don't think they're that much important.

make L-G-T-M work


Issue on page /notebooks/tutos/tuto_search_location_tile.html

Hello, when I downloaded sentinel-L1C data in cop_dataspace using EODAGA, some images were downloaded as xxx.safe.zip, but some were downloaded as XXX.SAFE, and these files became unavailable when I manually added the.zip suffix to.safe. How can I make all downloads in XXX.SAFE.zip format?

Hello @YUEWONHUI and thanks for submitting this issue.
If you check the logs, after having downloaded each file without zip extension, you should see a message like
2023-11-06 14:12:00,371 eodag.plugins.download.http      [WARNING ] (http             ) Downloaded product is not a Zip File. Please check its file type before using it

These files have a problem on Copernicus Dataspace side, and seem incomplete or corrupted.
EODAG removes the extension after downloading them to show that they are not zipfiles.
I also tried to download one of these files from https://dataspace.copernicus.eu/browser and also got an issue: download restarts when reaching 99% and finally fails later with a 401 error.
You can try to download these corrupted files from another provider.


GATE-3652: Teams rule setting for untrusted cert passthrough

Add new teams rule setting option: untrusted_cert
(To be added after cloudflare-go change https://github.com/cloudflare/cloudflare-go/pull/1214)

acceptance tests all passing
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareTeamsRule" -timeout 120m -parallel 1
=== RUN   TestAccCloudflareTeamsRuleBasic
--- PASS: TestAccCloudflareTeamsRuleBasic (12.51s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	13.555s


fix could not push down filter through cte producer sometimes

pick from master #35463
commit id<PHONE_NUMBER>cc3f9b6523ef7054eb1abdb9d0e7d8
when consumer side eliminate some consumers from plan, the size of consumers is wrong. so we cannot push down some filter in producer side. this PR fix this problem by update consumer set after rewrite outer side

run buildall


HOTKEY_CAPTURE_BUTTON doesn't do anything

I noticed this while doing all the other hotkey changes I've been working on, but didn't want to muddle PRs. case HOTKEY_CAPTURE_BUTTON doesn't do anything other than break.
I'm guessing it should state.buttons |= options.switchTpShareForDs4 ? GAMEPAD_MASK_A2 : GAMEPAD_MASK_S1, to reflect how we made the button consistent and pushed the TP/Share toggle into the PS4 report.

This issue is blocked by #360 as I broke the feasibility of the intended fix.

Addressed in https://github.com/OpenStickCommunity/GP2040-CE/pull/394 --- just waiting for a release to close this.

This has been rolled into RC, closing issue


TypeScript build error on strict=true

I'm consuming chain-registry 1.20.0 with "strict": true in my tsconfig.json which leads to the following error:
node_modules/@chain-registry/types/types/chains.d.ts:177:9 - error TS2411: Property 'rpc' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

177         rpc?: {
            ~~~

node_modules/@chain-registry/types/types/chains.d.ts:182:9 - error TS2411: Property 'rest' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

182         rest?: {
            ~~~~

node_modules/@chain-registry/types/types/chains.d.ts:187:9 - error TS2411: Property 'grpc' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

187         grpc?: {
            ~~~~

node_modules/@chain-registry/types/types/chains.d.ts:192:9 - error TS2411: Property ''evm-http-jsonrpc'' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

192         'evm-http-jsonrpc'?: {
            ~~~~~~~~~~~~~~~~~~

node_modules/@chain-registry/types/types/chains.d.ts:197:9 - error TS2411: Property ''grpc-web'' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

197         'grpc-web'?: {
            ~~~~~~~~~~

node_modules/@chain-registry/types/types/chains.d.ts:202:9 - error TS2411: Property 'wss' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

202         wss?: {
            ~~~

node_modules/@chain-registry/types/types/chains.d.ts:207:9 - error TS2411: Property 'sidechains_rpc' of type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[] | undefined' is not assignable to 'string' index type '{ address: string; provider?: string | undefined; archive?: boolean | undefined; }[]'.

207         sidechains_rpc?: {
            ~~~~~~~~~~~~~~

Found 7 errors in the same file, starting at: node_modules/@chain-registry/types/types/chains.d.ts:177

This is my tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es5",
    "esModuleInterop": true,
    "moduleResolution": "node",
    "declaration": true,
    "outDir": "./dist",
    "strict": true,
    "preserveConstEnums": true
  },
  "include": [
    "src/**/*"
  ]
}

While the error could be fixed by the consuming project by using "skipLibCheck": true, I thought it might not be a bad idea if chain-registry type definition was also honoring strict.
The change doesn't seem too painful to make it comply.
Basically in types/types/chains.d.ts we need to change this line:
        [key: string]: {
            address: string;
            provider?: string;
            archive?: boolean;
        }[];

By that one (not the undefined at the end):
        [key: string]: {
            address: string;
            provider?: string;
            archive?: boolean;
        }[]|undefined;

By the way, are the types generated for the project or hand written? Because the address, provider, archive block could have its own subtype to be reused and make the code more readable (I would be happy to PR).

can you make a PR? we're happy to accept it — @chain-registry/types is where you can make these hand-written changes

Thanks for the guidance, I eventually looked into it, see https://github.com/cosmology-tech/chain-registry/pull/98
The weird thing is I couldn't reproduce the TypeScript error in strict mode while compiling from the repo even though it's the same TypeScript version that I was using when I initially got the error. And I can consistently reproduce the error when chain-registry is a project dependency. Fixed the error in the PR anyway and also applied some trivial refactoring

Ah you had it all figured out already, I just spent about 20 minutes coming to the exact same conclusion. The fix wasn't quite so simple though, @chain-registry/interfaces turned out to not be the right package (maybe it was when the answer was given originally). I needed @chain-registry/v2-types, which in turn meant I needed @chain-registry/v2 in place of chain-registry. Then I needed to update all my code because the new package changed to camel case variable names and changed some field members.
Couldn't find any docs on v2 at all, ended up looking at the package.json in this repo to even figure out what the name of the package was, so it was a bit painful. Now though it all works, compiles fine, and I like the camel case vars much better so it's looking good!
By the way, it likely compiles in the repo but not in your project because they set "strictNullChecks": false in their tsconfig.json. This tells TypeScript not to enforce null or undefined type checks.


How to define a file format?

I'm playing with the snippets plugin and it uses files with .snippets extension, e.g. python.snippets. Its format is similar to a Makefile, i.e. lines must be indented with a tab (\t). However, in my settings I have tabtospaces set to true. In my settings.json I wanted to add it as an exception:
{
    "*.go": {
        "tabtospaces": false
    },
    "*.snippets": {
        "rmtrailingws": false,
        "tabtospaces": false
    },
    "rmtrailingws": true,
    "tabstospaces": true,
}

However, when I edit a .snippets file, these settings are ignored. With Go files, these settings work. However, a Go file is recognised as an ft:go file, while a .snippet is treated as ft:unknown. What is the solution in this case?
Update:
I found out how to define a filetype. In ~/.config/micro/syntax, I added a file called snippets.yaml with this content:
filetype: snippets

detect:
    filename: "\\.snippets$"

rules:
    - pass: ""

Now, when I open for instance python.snippets, at the bottom it's recognized as "ft:snippets". However, when I press TAB, still 4 spaces are inserted, though I have the following in settings.json:
{
    "*.snippets": {
        "rmtrailingws": false,
        "tabtospaces": false
    },
    "rmtrailingws": true,
    "tabstospaces": true,
}

You have a typo: tabtospaces should be tabstospaces. :)
And you shouldn't need to define your own file format, i.e. it's not a problem that you see ft:unknown, since "*.snippets": { ... } should work regardless (since it is based simply on the file name, not on the recognized file type). I've just checked that it works for me (as long as your typo is fixed).

@dmaluka Thanks a lot! I didn't understand what was wrong with it. After correcting the typo, it worked like a charm.


Move Conversion into it's own class

Simplify import path
import static com.aol.cyclops2.types.foldable.ConvertableSequence.Conversion.LAZY;

Merged


Come up with a list of tasks related to sharing code between v1 and v2

[ ] Release google-cloud-errors 1.0
[ ] Add google-cloud-errors as dependency to google-cloud-core
[ ] Release google-cloud-core 1.5 (with errors and config fixes)
[ ] Update veneer gem dependency on google-cloud-core to ~> 1.5

Initial list:

Gax errors
Configs

Release google-cloud-errors
Right now, the only thing that the cloud generator adds is a dependency on google-cloud-errors, and wrap all the GRPC::BadStatus errors raised by the RPC methods with a Google::Cloud::Error error object.
Release google-cloud-core
All microgenerator configuration is implemented using the Config module in gapic-common. The changes in googleapis/google-cloud-ruby#4541 are needed for the gapic-common configuration objects to use the google-cloud-core configuration objects. We need a new core gem released and all microgenerator veneer gems updated to set the new version as the minimum.


FancyZones always reverts to one of the presets after a system reboot.

Microsoft PowerToys version
0.74.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones, FancyZones Editor
Steps to reproduce

Create a custom layout.
Apply it to every monitor (in my case two) and on every virtual desktop (in my case three desktops. In total applied six times).
Wait for patch tuesday. This is when I notice it, since I never reboot otherwise.
After the reboot, all monitors on all virtual desktops have lost their custom layout and are now using one of the presets, the last one on the right, priority grid.

This behavior has been around since FancyZones first appeared.
(I really love FancyZones and hope this issue can be fixed)
✔ Expected Behavior
I expect FancyZones no keep my custom applied layout for all monitors on all virtual desktops.
❌ Actual Behavior
My custom layout is still present but all monitors now use a preset layout instead.
Other Software
Windows 11 Pro
22H2
2022-10-02
22621.2428
Windows Feature Experience Pack 1000.22674.1000.0

/bugreport

This problem does not occur if I restart the system. It can be a combination of a PowerToys update and then a reboot, often in conjunction with a Windows update. I'll try to pinpoint when it happens.

Hi @pontusbredin, thank you for providing additional information.
I've looked into your report, and it appears that the IDs of the monitors are being changed by the system, causing FancyZones to identify them as new and apply default layouts. It's a known issue, but we have limited control, as we rely on the information provided by the system.
I'm going to close this issue as a duplicate to centralize the thread.
Thank you for understanding.
/dup https://github.com/microsoft/PowerToys/issues/16370


SparcClient without config file fails

The most basic instantiation of a python client SparcClient without a config file fails:
In [3]: client = SparcClient()
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
Cell In[3], line 1
----> 1 client = SparcClient()

File ~/.pyenv/versions/3.12.2/envs/sparc-3.12.2/lib/python3.12/site-packages/sparc/client/client.py:55, in SparcClient.__init__(self, config_file, connect)
     53     config.read(config_file)
     54     logging.debug(str(config))
---> 55 current_config = config["global"]["default_profile"]
     57 logging.debug("Using the following config:")
     58 logging.debug(str(config[current_config]))

File ~/.pyenv/versions/3.12.2/lib/python3.12/configparser.py:941, in RawConfigParser.__getitem__(self, key)
    939 def __getitem__(self, key):
    940     if key != self.default_section and not self.has_section(key):
--> 941         raise KeyError(key)
    942     return self._proxies[key]

    KeyError: 'global'

@athril - something to consider. We should definitely fix the docs to make sure a basic "ready to go" config file is available. But possibly also revisit the earlier design decision to require a config file?

Thanks @nickerso. I have posted this on our team Slack, in case the GitHub notification is not seen.

Good point @mhalle! Thank you for bringing this,
A fix is ready for the review @nickerso .


11 create common cssstyles file

Authors:
What does this PR contain?
How did you test these changes?
Attach images (if applicable)
Closes #11

Hi Kei, I edited the PR body to have a template; could you and your partner fill it out? Next time you can submit a PR using the /pr command in slack for it to autogenerate the template :)


Error installing Microsoft.VisualStudio.BlazorExtension VSIX

I have VS2017 community preview and when I tried to install Microsoft.VisualStudio.BlazorExtension.VSIX,.
I get the following even after installing I installed Razor Language services VSIX
Install Error : Microsoft.VisualStudio.ExtensionManager.MissingReferencesException: This extension cannot be installed because the following references are missing:
-Microsoft.VisualStudio.RazorExtension (Razor Language Services)
at Microsoft.VisualStudio.ExtensionManager.EngineUtilities.EnsureNoMissingReferences(IEnumerable1 missingRefs)    at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.ExtensionRequiresAdditionalOperationForInstall(InstallableExtensionImpl extension, IInstalledExtensionList modifiedInstalledExtensionsList, Boolean isNestedExtension, InstallFlags flags, Boolean& performExtensionUpdate)    at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallInternal(InstallableExtensionImpl extension, InstallFlags installFlags, IDictionary2 extensionsInstalledSoFar, List1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, IProgress1 progress, Version targetedVsVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.BeginInstall(IInstallableExtension installableExtension, InstallFlags installFlags, AsyncOperation asyncOp, Version targetedVsVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallWorker(IInstallableExtension extension, InstallFlags installFlags, AsyncOperation asyncOp)

Do you have VS 2015 15.7-preview1 with the Web Workload?
If that's the case could you please provide the log file (should be linked from the error dialog).

I get the following even after installing I installed Razor Language services VSIX

This should be included by the Web Workload, you don't need to do any extra steps to install the Razor tools

Here is the log file.
VSIXInstaller_0ed3da71-55a0-4572-a1c0-1babcdcec624.log

The logs definitely don't show the Razor extension as present. Can you check whether or not the Razor extension is present at:
C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\PREVIEW\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\Microsoft\RazorLanguageServices\

Just to triple-check, I'm talking about the "ASP.NET and Web Development" workload, seen here:

You can see this from clicking Modify on the Visual Studio Installer

I don't see the Razor extension in the directory you mentioned. Here is what I have installed in VS

If you went to the VS gallery and installed this I think you will have to repair. That extension is for an ancient version of VS and will break things.
You should definitely see the Razor extension at C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\PREVIEW\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\Microsoft\RazorLanguageServices\

It says
This extension is already installed to all applicable products.
Let me repair and see

Yes, and to clarify, after repair you should be able to install the Blazor extension. You SHOULD NOT need to install anything extra for Razor.

Thankyou. After Repairing VS. install of Blazor extension worked.

Great!


make html missing

Hi,
Great course!
I got stuck watching this video here. That's because I believe you forgot to mention how to build the HTML using make html. In other words, the folder _build is still empty after watching Make a sphinx site. Perhaps you forgot to record that part?
Either way, I found your post here
I am also creating my guide using conda to help me through the training. Please check here
Thanks again!!
Cheers
Fernando

Hi, in this course I show the use of a livereload script. You run it and then, as you edit your content, it re-runs Sphinx and tells the browser to update the page.

Thanks!


(#38): Don't prompt for deletion if there aren't any branches to delete.

Connects #38.

Oops. Sorry, I didn't merge to develop. I'll re-open the PR.


Upgrade the version of the Basic authenticator

Upgrade the version of the Basic authenticator

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Hasanthi Dissanayake seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6427136761

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6427136761
Status: success


Markdown & Repeater Bugs

Package
filament/filament
Package Version
v3.0.97
Laravel Version
v10.28.0
Livewire Version
v3.0.8
PHP Version
PHP 8.1.24
Problem description
MarkdownEditor  - has problems displaying code and console errors.
Repeater - console errors
Expected behavior
everything is clear
Steps to reproduce
shown in video
https://github.com/filamentphp/filament/assets/36602392/8d016e88-26b3-4b50-baa8-1d2ad9ae71c0
https://github.com/filamentphp/filament/assets/36602392/6e8b835e-4543-4c74-9b5b-71b6a43a63c4
Reproduction repository
https://github.com/movicat/filament-demo
Relevant log output
No response

These are unrelated issues, ideally they should have been put in separate issues.
Also, I don't think we are going to be able to fix the markdown editor, it's probably just a bug with EasyMDE.

Also, the console errors on the select are harmless and don't actually impact the functionality of the component?

I cannot reproduce exactly what you are typing into the markdown editor to get that behaviour.
The console errors are Livewire related and harmless to the functionality of the page, they will be fixed in due course.

I got the same problem when using the spatie translatable. The functionality of the field stops working you can no longer select words and the cursor always shows at the start.


Expose a method to manually close the connection to redis

Hey !
Here's a little PR to add a method to the client extension in order to add the possibility to manually close the connection to Redis in case it's not garbage collected in time and thus leak stale connection to redis

Released as 1.0.0 (I made the bump as we're using it in production for a while and it's stable enough)


Unnecessary warning in pure Flow project

Describe the bug
Using 24.4-SNAPSHOT and running a pure Flow project, I get this in the server log:
WARN 24788 --- [nio-8080-exec-2] .r.RouteUnifyingIndexHtmlRequestListener : Failed to find views.json under /Users/tepi/Downloads/drawer/./frontend/generated
Originated somewhere in com.vaadin.hilla.route.RouteUnifyingIndexHtmlRequestListener
Expected-behavior
When I only have Flow views, I do not expect this kind of warning.
Reproduction
Run any pure Flow app and open a view with browser
System Info
24.4-SNAPSHOT

Let's change the verbosity of this message to debug.


Reword Unknown Intent description

I would propose rewording the description below to: "Action to perform when user input is unrecognized OR if none of the 'on intent recognition' triggers match recognized intent."

The reason for that is that the users input may have been recognized but none of the triggers fired.

This ask is a schema modification. Transferring to botbuilder-dotnet


Upgrade to wasmvm v1.3

Backport #1296
Todos:

[ ] use new checksum function in gov_tx.go instead of sha256.Sum256(raw); check for other places
[ ] Update go.mod
[ ] Update download links and checksum in Dockerfile
[ ] Update compatibility matrix
[ ] Use StoreCodeUnchecked in state sync

Closed by #1529 #1523 #1521 #1519 #1518 #1516 #1510


fixed undefined reference to _write on Teensy 3.6

This PR fixes undefined reference to _write when using Teensy 3.6.:
Building in release mode Compiling .pio/build/teensy36/src/firmware.ino.cpp.o Compiling .pio/build/teensy36/lib9e7/micro_ros_arduino/wifi_transport.cpp.o Linking .pio/build/teensy36/firmware.elf /home/ubuntu/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/lib/armv7e-m/fpu/libc.a(lib_a-writer.o): In function _write_r':
writer.c:(.text._write_r+0x12): undefined reference to _write' collect2: error: ld returned 1 exit status *** [.pio/build/teensy36/firmware.elf] Error 1
I managed to build and upload a the pub-sub demo from the examples folder.

Can you add a support line in the readme in the Community-contributed boards section?

Hey @pablogs9, I added the support line in the README.
Btw, I managed to build, upload and run the demo shown above using PlatformIO. I documented my progress here and was wondering where's the best way to link this for users who are intereseted in this setup?
Thank you!

@mergify backport foxy main


provisioning postgres does not set env

when I provisioned a postgres db for my node app, it failed to set environment valuables,  says Error setting app env: undefined
and it does not allow me to set the variables myself. says undefined:1 Uncaught (in promise) Timed out waiting for deployment completion
I restarted the whole server, it did not help. I removed the database and did it again, still the same.
flynn-host debug info: https://gist.github.com/8c1323586dd36930884418c951fd97b7

possibly related to #2822

when I scale down web worker to 0, it works fine. interesting

@hadifarnoud this looks like the deployment (which happens when you set an environment variable) is timing out on the client side, but it most likely succeeded after a while. Can you check if the environment variables exist using the CLI (i.e. flynn env)?
We have a number of issues relating to deployment timeouts, we need to improve the situation.

the env were not set. I did check with CLI and the app was not working because of env were not set.

@hadifarnoud ok, can you try setting the environment variables using the CLI (flynn env set KEY=VAL)? Please post the full output here if it fails.

the output was the same Error setting app env: undefined

This is still a problem with the latest version of Flynn. But, if you scale down to 0 web workers, both creation and deleting of a resource succeeds without any errors, and a lot faster than with 1+ workers.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


Fix experiment ID in the experiment-management docs

One of the experiment IDs in the experiment-management section seems to be wrong/out of date.

Thanks @alvaropp !


No indication of skipped tests in main docs

'Running the tests' does not mention xit or xdescribe, and the installation steps currently gets you jasmine-node v1.14.3 which does not mark xit tests as skipped. The readme for the exercise does mention xit and describe, however someone who has already done the same exercise on another track (such as myself!) may go straight for the exercise and miss these details.
Test output from jasmine-node v1.14.3 suggests that you have completed an exercise even if it contains xit tests:
jasmine-node .
.

Finished in 0.005 seconds
1 test, 1 assertion, 0 failures, 0 skipped

jasmine-node v2 informs you that xit tests have been skipped:
jasmine-node .
.--

Finished in 0.004 seconds
3 Tests, 0 Failures, 2 Skipped

Should the installation instructions be updated to have npm install jasmine-node@2 -g? (I'm not very experienced with JavaScript so am unaware of any potential issues this could cause since it's beta). docs/TESTS.md should also be updated to mention xit and xdescribe.

If jasmine-node v2 is in beta, I'd rather keep v1.14.3. But I agree on updating docs/TESTS.md to include a note about xit and xdescribe.
Do you want to update that doc file? If so, I'd include the comment before the title "Making Your First Node Module". If not, don't worry, it's fine. I'm sure your idea will help lots of people.

@mienaikage did not respond, hence I went ahead and did it along with some other changes.


Design improvements

Some design changes that improve readability and UX. Taken from #13 and https://www.reddit.com/r/ArkEcosystem/comments/74fxq7/explorer_my_view_redesign/.

Great, i liked all the improvements! 👍🏻 +5


add relay fix

Coverage increased (+0.04%) to 63.615% when pulling 6c0d6418000570faed0b60074742ddb9bd452b85 on rendezvous into 1857327b15edf5299ab7ffeb8f32a476d798650e on master.


ux-input goes outside of specified size when full-width class is applied

I'm submitting a bug report

Library Version:
0.3.0

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
6.2.0

NPM Version:
3.8.9

Browser:
all

Language:
TypeScript 2.4

Current behavior:
When the ux-input has the full-width class applied, the input can go outside of the container.
Expected/desired behavior:
The input element should not extend past the ux-input element.

Issue moved to aurelia/ux-components #4 via ZenHub


Built binary can't be used in other directories than project root

OS: Void Linux (glibc) (same issue on musl)
I'm trying to package it but the binary I built looks like not "portable", it only works under the project root.
compile: (same output as just go bulid -o wakapi)
$ GO111MODULE=on go build -v .
# github.com/mattn/go-sqlite3
sqlite3-binding.c: In function 'sqlite3SelectNew':
sqlite3-binding.c:128049:10: warning: function may return address of local variable [-Wreturn-local-addr]
128049 |   return pNew;
       |          ^~~~
sqlite3-binding.c:128009:10: note: declared here
128009 |   Select standin;
       |          ^~~~~~~

run after built, before cp config.default.yml config.yml:
$ ./wakapi
2021-04-25T04:32:45.057836903Z [ERROR] failed to find config file at 'config.yml'
panic: failed to find config file at 'config.yml'

goroutine 1 [running]:
github.com/emvi/logbuch.(*StandardFormatter).Pnc(0xc00000e0d8, 0xccd1d1, 0x22, 0xc000198be0, 0x1, 0x1)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/standard_formatter.go:59 +0x8e
github.com/emvi/logbuch.(*Logger).Fatal(0xc0000d6180, 0xccd1d1, 0x22, 0xc000198be0, 0x1, 0x1)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/logger.go:132 +0xb3
github.com/emvi/logbuch.Fatal(...)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/funcs.go:55
github.com/muety/wakapi/config.mustReadConfigLocation(0xc000159980, 0xc000198bc0)
        /home/username/src/wakapi/config/config.go:309 +0xfc
github.com/muety/wakapi/config.Load(0xcb75b0, 0x7, 0x41bd97)
        /home/username/src/wakapi/config/config.go:343 +0xd7
main.main()
        /home/username/src/wakapi/main.go:92 +0x5

works fine after cp config.default.yml config.yml.
throws error when I move the binary along with config.yml to another directory and run it
2021-04-25T04:38:33.465365349Z [ERROR] unexpected end of JSON input
panic: unexpected end of JSON input

goroutine 1 [running]:
github.com/emvi/logbuch.(*StandardFormatter).Pnc(0xc0000a60c0, 0xcc85a9, 0x1c, 0x0, 0x0, 0x0)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/standard_formatter.go:57 +0xc5
github.com/emvi/logbuch.(*Logger).Fatal(0xc0000f8180, 0xcc85a9, 0x1c, 0x0, 0x0, 0x0)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/logger.go:132 +0xb3
github.com/emvi/logbuch.Fatal(...)
        /home/username/go/pkg/mod/github.com/emvi/logbuch@v1.1.1/funcs.go:55
github.com/muety/wakapi/config.readColors(0xcb75b0)
        /home/username/src/wakapi/config/config.go:301 +0x167
github.com/muety/wakapi/config.Load(0xcb75b0, 0x7, 0x41bd97)
        /home/username/src/wakapi/config/config.go:349 +0x265
main.main()
        /home/username/src/wakapi/main.go:92 +0x5e

# Adapt config to your needs
$ cp config.default.yml config.yml
$ vi config.yml

# Build the executable
$ go build -o wakapi

# Run it
$ ./wakapi

And I'm a bit confused by this, config.yml file is not required at compile time, right? if so then maybe change the order to this in README
# Build the executable
$ go build -o wakapi

# Adapt config to your needs
$ cp config.default.yml config.yml
$ vi config.yml

# Run it
$ ./wakapi

Thanks for your feedback. You're right, the config file is not required at compile time as this would contradict its whole purpose. However, a few other static assets are, one example being data/colors.json or views/*.tpl.html. Those files are compiled into the binary. However, to ease the development process, these files are still attempted to be loaded from your local file system while you are in dev mode. Switching to env: prod should resolve your issue and make the application boot up even if the binary is separated from its code.

if so then maybe change the order to this in README

I'll update it.

Switching to env: prod should resolve your issue

Yes setting ENVIRONMENT=prod or env: prod solved the issue. I'll use sed to edit config.yml before build wakapi.
How does the GitHub workflow builds it as a production build instead of development build?

I got it. ENVIRONMENT=prod or env: prod does not make a difference on builds. but it changes the behavior of wakapi binary at runtime to load extra files or not.

Exactly! Glad you were able to figure it out.


CSRF token not sent to Django

When trying to send an Inertia POST request to Django from Vue, it fails with a 403 error saying that the CSRF token is not included.

I know there is some setup in the main.js file before createInertiaApp() for axios, but this doesn't appear to be sent to Django.

What do I need to do to send the CSRF token with all POST/PUT/PATCH requests?

Any time I try to send a POST request, it displays the above message. Comment out django.middleware.csrf.CsrfViewMiddleware in settings.py and it works fine

@MichaelNZ85 What is the code used for making the POST request?

Any update on this?

I found this issue via a linked issue on the main repo.
https://github.com/inertiajs/inertia-django/pull/15
This PR will make sending the token automatic and includes docs on how to setup the front end side to recognize the token name and location. Hopefully that will make this process easier!

Thanks @BrandonShar. @MichaelNZ85 Can you please check with the latest version of inertiajs/inertia-djangoand let me know if that solves your issue?

Yes, that fixed it. Thank you very much!


Missing data/config.yml

I'm trying to build unused using a straight stack install, and I get the following breakage:
$ stack install unused
Run from outside a project, using implicit global project config
Using resolver: lts-6.14 from implicit global project's config file: /home/endgame/.stack/global-project/stack.yaml
unused-<IP_ADDRESS>: configure
unused-<IP_ADDRESS>: build

--  While building package unused-<IP_ADDRESS> using:
      /home/endgame/.stack/setup-exe-cache/x86_64-linux/setup-Simple-Cabal-<IP_ADDRESS>-ghc-7.10.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS> build --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
    Logs have been written to: /home/endgame/.stack/global-project/.stack-work/logs/unused-<IP_ADDRESS>.log

    Configuring unused-<IP_ADDRESS>...
    Building unused-<IP_ADDRESS>...
    Preprocessing library unused-<IP_ADDRESS>...
    [ 1 of 45] Compiling Common           ( src/Common.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Common.o )
    [ 2 of 45] Compiling Unused.CLI.ProgressIndicator.Types ( src/Unused/CLI/ProgressIndicator/Types.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/ProgressIndicator/Types.o )
    [ 3 of 45] Compiling Unused.CLI.Util  ( src/Unused/CLI/Util.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/Util.o )
    [ 4 of 45] Compiling Unused.CLI.Views.AnalysisHeader ( src/Unused/CLI/Views/AnalysisHeader.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/Views/AnalysisHeader.o )
    [ 5 of 45] Compiling Unused.CLI.Views.GitSHAsHeader ( src/Unused/CLI/Views/GitSHAsHeader.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/Views/GitSHAsHeader.o )
    [ 6 of 45] Compiling Unused.CLI.Views.NoResultsFound ( src/Unused/CLI/Views/NoResultsFound.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/Views/NoResultsFound.o )
    [ 7 of 45] Compiling Unused.CLI.Views.Error ( src/Unused/CLI/Views/Error.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/Views/Error.o )
    [ 8 of 45] Compiling Unused.CLI.ProgressIndicator.Internal ( src/Unused/CLI/ProgressIndicator/Internal.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/ProgressIndicator/Internal.o )
    [ 9 of 45] Compiling Unused.CLI.ProgressIndicator ( src/Unused/CLI/ProgressIndicator.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/CLI/ProgressIndicator.o )
    [10 of 45] Compiling Unused.Cache.FindArgsFromIgnoredPaths ( src/Unused/Cache/FindArgsFromIgnoredPaths.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/Cache/FindArgsFromIgnoredPaths.o )
    [11 of 45] Compiling Unused.Regex     ( src/Unused/Regex.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/Regex.o )
    [12 of 45] Compiling Unused.Util      ( src/Unused/Util.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/Util.o )
    [13 of 45] Compiling Unused.Projection.Transform ( src/Unused/Projection/Transform.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/Projection/Transform.o )
    [14 of 45] Compiling Unused.Projection ( src/Unused/Projection.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/Projection.o )
    [15 of 45] Compiling Unused.ResultsClassifier.Types ( src/Unused/ResultsClassifier/Types.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/ResultsClassifier/Types.o )
    [16 of 45] Compiling Unused.ResultsClassifier.Config ( src/Unused/ResultsClassifier/Config.hs, .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/Unused/ResultsClassifier/Config.o )

    /tmp/stack9786/unused-<IP_ADDRESS>/src/Unused/ResultsClassifier/Config.hs:22:23:
        Exception when trying to run compile-time code:
          data/config.yml: openBinaryFile: does not exist (No such file or directory)
        Code: FE.embedFile "data/config.yml"
        In the splice: $(FE.embedFile "data/config.yml")

I suspect that data/config.yml isn't being marked for distribution somehow, as the same build within a git checkout of unused completes without error.

@jack-trikeapps ah, nice catch! You're correct, I was able to verify this locally too. I attempted a fix with https://github.com/joshuaclayton/unused/commit/80aa7aa9501b005522b96da6200011db2bb9ca7d
I've pushed a new version; still waiting for everything to update externally, but when they do, you should be able to stack install unused-<IP_ADDRESS>. If that works, mind closing this issue?
If you have any other experience with Stack, are you aware of a way to verify this would have worked before pushing up to Stack? I'm still new to Haskell+Stack and if there's a way I could have caught this sooner, I'd appreciate any insight 😄!

(I also verified on http://hackage.haskell.org/package/unused-<IP_ADDRESS>/src/ vs http://hackage.haskell.org/package/unused-<IP_ADDRESS>/src/ that the new dist contains the data file, so it should be good once the indices get updated)

@jack-trikeapps just verified install from Stack itself just now; going to close this. Please reopen if you continue to run into issues, and thank you so much for reporting this!

Verified working, thank you. Leaving closed.


Payload says in dev mod when run with NODE_ENV=production node server.js

Link to reproduction
No response
Environment Info
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 9.9.0
Relevant Packages:
  payload: 3.0.0-beta.98
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:21 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T8103
  Available memory (MB): 8192
  Available CPU cores: 8

Describe the Bug
Payload says in dev mod but NODE_ENV=production
Reproduction Steps

build payload app in standalone mode
run with command NODE_ENV=production node .next/standalone/server.js
visit any payload pages
log says:

It looks like you've run Payload in dev mode, meaning you've dynamically pushed changes to your database.

If you'd like to run migrations, data loss will occur. Would you like to proceed?

Adapters and Plugins
postgresAdapter

This is not depended on whether you run your app with NODE_ENV=development or NODE_ENV=production.
You most likely copied the development database to the prod. In development, we use database push instead of migrations and the thing is that we can't mix them. This is described in the docs https://payloadcms.com/docs/beta/database/postgres#prototyping-in-development-mode
You can remove all the rows from the payload_migrations with batch= -1 like this:
DELETE FROM payload_migrations WHERE batch=-1

Then the warning should go out.


Update plugin-email-ext.yml

The email-ext plugin shows as up for adoption, I would like to re-adopt the plugin to provide fixes going forward.
Link to GitHub repository
https://github.com/jenkinsci/email-ext-plugin
When modifying release permission
List the GitHub usernames of the users who should have commit permissions below:

@slide_o_mix

This is needed in order to cut releases of the plugin or component.
If you are modifying the release permission of your plugin or component, fill out the following checklist:

### Release permission checklist (for submitters)
- [ ] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to [accounts.jenkins.io](https://accounts.jenkins.io/).
- [ ] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.
- [ ] I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) of the plugin or component team to approve this request.

When enabling automated releases (cd: true)
Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.
Link to the PR enabling CD in your plugin

### CD checklist (for submitters)
- [ ] I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

### Reviewer checklist
- [ ] Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.
- [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
- [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently `@Wadeck`) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

@basil As current developer


bundle.js ignored

I understand this is probably because most people use bundle.js for packaging... but oh god this took me 20 minutes of time wasting to figure out what was going wrong with my editor.
Do we need to special case this?
Doesn't everyone separate their source folders from distribution anyway?
In which case, if this is an issue, they can just do standard src/.
All the other defaults:

node_modules/*, .min.js, bundle.js, coverage/

I don't think would ever get in the way.

发自我的小米手机http://m.browser.baidu.com/
发自我的小米手机http://m.browser.baidu.com/
发自我的小米手机http://m.browser.baidu.com/
On Daniel Cousens<EMAIL_ADDRESS>Jan 11, 2017 19:14 wrote:
I understand this is probably because most people use bundle.js for packaging... but oh god this took me 20 minutes of time wasting to figure out what was going wrong with my editor.
Why do we need to special case this?
Doesn't everyone separate their source folders from distribution anyway?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/feross/standard/issues/743, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AX0fd4SS8jWHZWQiBgaCyH6yhp7Yxf2Aks5rRLmRgaJpZM4Lgdhq.

Sorry you lost 20 minutes. That's always frustrating. 😢
I have lots of repos that generate bundle.js and I usually never have a src/ folder for small projects. I personally appreciate having bundle.js as a default ignore. I've also never heard about anyone else running into this issue before.
That said, I agree that out of all the defaults bundle.js is the only one that could theoretically cause trouble if someone accidentally uses that name. The other ignores will almost never be a problem.
I think the usefulness outweighs the potential for confusion, given the prevalence of bundle.js but open to other people's thoughts.

@feross I know it would be a bit special case like,  but maybe don't ignore if the file is deliberately specified on the command line?
standard bundle.js

Just being a no-op was especially confusing,  but alas.

Or perhaps hint at what is ignored in a verbose mode?

@dcousens Yeah, these are both reasonable suggestions. Right now there's no way to override the built-in ignores.

发自我的小米手机http://m.browser.baidu.com/

@feross ha,  bitten by this again since I started using the beta (had previously removed it from my ignore globally installed version).

I agree bundle.js shouldn't be ignored by default. I was trying to lint source code for a node project and had a file with that name that was being overlooked without me even knowing about it. Naming a webpack/browserify output file bundle.js is just a weird front-end trend (similar to naming the output folder dist) that doesn't really have any reasoning behind it. I don't think it should be assumed as standard practice. If you are outputting to bundle.js, it should be in your gitignore anyway, which will make standardjs ignore it.
Maybe it would make more sense to ignore files ending in .bundle.js?

I'm re-opening this issue as @jsonmaur's argument that folks using bundle.js are likely to have it listed in their .gitignore makes sense to me. I'd like to run a test to see how many repos this change would break.

No repos failed when I removed bundle.js from the default list of ignored files. Let's ship this in standard 14. 💪


Crash...

Hello,
This may be my fault (almost certainly is) but it may be enlightening.  I'll triple-check my code.
So first, from the Generation step down to the GA # 4 has a minimum is from my Callback routine.
Interestingly, it looks like it doesn't get called for the next few generations, and then the crash comes.
My setup is:
	var ga = gago.Generational(MakeNewVectorFunc(NUM, -0.1, 0.1))
	ga.NPops = 5
	ga.PopSize = 250
	ga.Speciator = gago.SpecKMedoids{
		K:             10,
		MinPerCluster: 10,
		Metric:        l1Distance,
		MaxIterations: 5,
	}
	ga.Callback = checkStats
	ga.Initialize()

I stole the l1Distance bodily from your source... I'll tell you where to send the ransom money :-)
here's the backtrace info:
Generation step took 3m14.626519066s
GA has 5 Populations.
GA 0 has 250 individuals.
GA # 0 has a minimum 4302236.000000000000, maximum 20046975.000000000000
GA 1 has 250 individuals.
GA # 1 has a minimum 4387752.000000000000, maximum 20046975.000000000000
GA 2 has 250 individuals.
GA # 2 has a minimum 4315952.000000000000, maximum 20046975.000000000000
GA 3 has 250 individuals.
GA # 3 has a minimum 4276399.000000000000, maximum 20046975.000000000000
GA 4 has 250 individuals.
GA # 4 has a minimum 4256291.000000000000, maximum 20046975.000000000000
Best fitness at generation    5: 3675431.000000
Best fitness at generation    6: 3675431.000000
Best fitness at generation    7: 3675431.000000
Best fitness at generation    8: 3675431.000000
panic: runtime error: index out of range

goroutine 65 [running]:
github.com/MaxHalford/gago.SpecKMedoids.Apply(0xa, 0xa, 0x146ed90, 0x5, 0xc42324a000, 0xfa, 0xfa, 0xc420014e70, 0x0, 0x0, ...)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/speciation.go:60 +0x754
github.com/MaxHalford/gago.(*SpecKMedoids).Apply(0xc42000c220, 0xc42324a000, 0xfa, 0xfa, 0xc420014e70, 0x0, 0x0, 0x0, 0x0, 0x0)
        <autogenerated>:85 +0xa0
github.com/MaxHalford/gago.(*Population).speciateEvolveMerge(0xc4200e8240, 0x1627a40, 0xc42000c220, 0x16279c0, 0xc42000c180, 0x1, 0x3)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/ga.go:181 +0x77
github.com/MaxHalford/gago.(*GA).Enhance.func1(0x8, 0x146f890)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/ga.go:142 +0x97
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc420010480, 0xc422890150)
        /Volumes/Second/Chris/hacks/gofigure/src/golang.org/x/sync/errgroup/errgroup.go:58 +0x57
created by golang.org/x/sync/errgroup.(*Group).Go
        /Volumes/Second/Chris/hacks/gofigure/src/golang.org/x/sync/errgroup/errgroup.go:66 +0x66
exit status 2

Hey! Can you make sure you have pulled the latest version? I got this issue a few days ago and it due to the fact that some species would only have 1 individual. I fixed this by implementing rebalanceClusters which ensures that species/clusters have at least k individuals.

So git today says:
538 [github.com/MaxHalford/gago]
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean

Should I be looking at a different branch?
When I look at the gago.a file under $GOPATH/pkg/, it's got today's date; I nuked it and redid the go install in that directory.
But when I run the code I get (I think) the same error:
panic: runtime error: index out of range

goroutine 63 [running]:
github.com/MaxHalford/gago.SpecKMedoids.Apply(0xa, 0xa, 0x146ed90, 0x5, 0xc420bbe000, 0xfa, 0xfa, 0xc420816000, 0x11c3, 0x6, ...)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/speciation.go:60 +0x754
github.com/MaxHalford/gago.(*SpecKMedoids).Apply(0xc42008a1e0, 0xc420bbe000, 0xfa, 0xfa, 0xc420816000, 0x3fb999999999999a, 0xc42007cdb0, 0x1629780, 0xc42008a260, 0x7ff0000000000000)
        <autogenerated>:85 +0xa0
github.com/MaxHalford/gago.(*Population).speciateEvolveMerge(0xc4200f8200, 0x1627a40, 0xc42008a1e0, 0x16279c0, 0xc42008a0a0, 0x1, 0x3)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/ga.go:181 +0x77
github.com/MaxHalford/gago.(*GA).Enhance.func1(0x8, 0x146f890)
        /Volumes/Second/Chris/hacks/gofigure/src/github.com/MaxHalford/gago/ga.go:142 +0x97
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc420818080, 0xc4200141e0)
        /Volumes/Second/Chris/hacks/gofigure/src/golang.org/x/sync/errgroup/errgroup.go:58 +0x57
created by golang.org/x/sync/errgroup.(*Group).Go
        /Volumes/Second/Chris/hacks/gofigure/src/golang.org/x/sync/errgroup/errgroup.go:66 +0x66
exit status 2

and a quick check says:
$ ag -l rebalanceClusters
distance.go
distance_test.go
speciation.go

So I think I'm up to date.
Thanks!

Ok I will look into it and I'll get back to you! It's something to do with speciation so if you're in a hurry I would simply not use it for the moment.

Hey! Can you try to do the same with the fix-speciation branch? I didn't do anything crazy but it should at least fix the error you got. If it doesn't then I would like to have a look at your code if possible.
Tell me how it goes :)

HA! My code is impervious to your puny bug fixes! :-)
So, thanks very much for being willing to brave the code; here's a tar file with (I believe) all the source, and an example input file.
Command line to run it:
go run main.go learnGATwo input_for_nn.uniq.10k.csv whatever.out

And, for the record, this is an experiment, I realize it won't finish in my lifetime ("Genetic Algorithms run in Geological Time" :-)

Hey, I cded into the tar file you gave and installed cobra, however when I ran the command you gave me I got the following error message: cmd/learnGATwo.go:45: undefined: RootCmd in RootCmd.AddCommand.
Any idea why?

Whoops, sorry, my bad.
First, download this root.go file, put it in the cmd directory, and then add its dependencies:
go get github.com/mitchellh/go-homedir
go get github.com/spf13/viper

Then it should work.  I tried it in a bare ubuntu VM, and it worked there.
Thanks again for the help!

Okay it's better but I'm still getting an error: panic: open input_for_nn.uniq.10k.csv: no such file or directory. Maybe you versioned a CSV or something :). We're getting there!

Wow, I'm just the king of fail these days... sorry!
Use this command line instead:
go run main.go learnGATwo temp_data/input_for_nn.uniq.10k.csv whatever.out

Great it's working, I'm running it now :). Do you remember after how many generations you crashed?

Hi Max,
Not very many... It just took a few minutes.
-- chris

On Jul 14, 2017, at 4:07 AM, Max Halford<EMAIL_ADDRESS>wrote:
Great it's working, I'm running it now :). Do you remember after how many generations you crashed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Okay it took some debugging but I found the cause of the error. The master branch now includes the fix. I ran your example for over 15 minutes and didn't get any crash.
I'll let you let tell me if I can close this issue or not :)

Fantastic!  That does seem to have fixed things... thanks again.


Chrissmallrnamap

Combined median and read maps

@chamaelj closing this PR. I will keep the chrissmalrnamap branch until the end of your internship.
I reopen the PR from the smallrnamap2 branch.


Update for Cycle Unified

Just a straightforward port to Cycle Unified. It still uses RxJS, and the Electron version is unchanged.
I haven't used it yet, but the tests are passing.

Cycle now uses xstream internally, so all sources must be adapted to xstream, as explained in the migration guide. It's a hard requirement of the current Cycle.
I also already ported the all library to xstream - other PR coming soon ;). The advantage is that xstream is much smaller than Rx.

Thanks for explaining and for getting this up-to-date.


Adjust row height by font size in PickerIOS

[x] Explain the motivation for making this change.
[x] Provide a test plan demonstrating that the code is solid.
[x] Match the code formatting of the rest of the codebase.
[x] Target the master branch, NOT a "stable" branch.

Motivation (required)
There is a problem where setting a bigger fontSize in PickerItem style
clips the top and bottom of the text.
This solves that problem by computing the row height using the font
size.
Test Plan (required)
Create a PickerIOS component and set a larger font size (e.g. 50). The row height will grow accordingly.
Example with fontSize=50: Screenshot

@shergin I chose it by trial and error. This value made the view look the most natural.
I tried to find out which is the default margin in UIPickerView but it's not documented and stepping through the disassembled UIKit doesn't show any obvious constant for margin/padding.

Okay, but... Default row height is 40 (Right?), the default font size is 21 (Right?), so 21 + 8 = 21 != 40, so it means we change/break default styling. 🤔
Was it intentional?
Should we use 19 instead of 8?

@shergin you're right, it makes sense. It actually looks way better with a 19 offset

@alin23 I am sorry for the delay, should we still merge this?

@shergin Sorry for closing this, I just took for granted what the bot said and thought that the file was removed/refactored somehow.
Yes, I still think this needs to be merged. I got a request from another react-native user to merge this into master so I guess it would be a good idea to do this.
Default usage didn't seem to be affected or changed in any way in my previous tests. As long as I didn't change the default font size, everything looked the same.

@alin23 why auto row height with font size？ it is correct？ If i use a few PickerIOS ， fontSize is different， row height is catastrophic。 like this image

@ldhios indeed, I didn't take into consideration that the columns could have different font sizes, thus breaking the alignment. It might not be correct, but it is better than clipping the text.

@alin23 Thanks for you reply in time。 Can you help me fix my issues？

@ldhios I'm sorry but I haven't developed in Obj-C or React Native in a while. A workaround would be to hide those separators by setting the separatorColor to transparent or same as the background color.


storybook-react-native + react-native-web

Issue details
If I use a basic native component everything works great. But I'm trying to use storybook with react-native & react-native-web and I always get:
can't find variable: document

Steps to reproduce
Just try to create an story for a react-native-web and run storybook-react-native ... zero-issues when I'm running the same story in storybook-react.
Please specify which version of Storybook and optionally any affected addons that you're running
    "@storybook/react": "^3.3.12",
    "@storybook/react-native": "^3.3.12",

Screenshots / Screencast / Code Snippets (Optional)

Isn't react native web supposed to run in a browser? You probably need to use @storybook/react for web–targeted components

Their official storybook example uses @storybook/react though:
https://github.com/necolas/react-native-web/blob/0.5.1/website/package.json

"React Native for Web" brings the platform-agnostic Components and APIs of React Native to the Web.

Pretty sure it's not supposed to be for RN or else it wouldn't be calling document


ci: automate release using semantic-release

Several test releases were created on the automate-release branch while experimenting with configuring semantic release and the github releases and visual studio code extension release process.
These have all been deleted manually github releases, tags and marketplace extension versions.

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


Correct way to use patch method to update resources?

Hey, I have a question here, can someone help?
https://stackoverflow.com/questions/62358406/how-to-update-resources-with-patch-method-using-openapi-correctly

I would use formats such as JSON Patch or JSON Merge Patch, which do not directly use your Person schema/representation.
You can think of a translation from the Person schema as having taken place but that translation can happily drop the required constraint on omitted properties.

Please let us know if the above does not answer your question, and we can re-open this issue.


UNIX time stamp in data frame not correct type

Description of issue:
When creating a pd.DataFrame from an Array and specify False for the datetime argument. If the datetime_format parameter is set to 'UNIX' the resulting value in the data frame is a str which is not a very useful type for a  Unix time stamp
Expected behaviour:
I think it would make much more sense if the value was cast to a float in this case
Actual behaviour:
time values are str
Complete self contained example of issue:
from async_v20 import OandaClient
import asyncio
client = OandaClient(datetime_format='UNIX')
loop = asyncio.get_event_loop()
run = loop.run_until_complete
rsp = run(client.get_candles('EUR_USD'))
df = rsp.candles.dataframe(datetime=False)
df.time[0]
Out[5]: '1513677115.000000000'  # str
type(df.time)
Out[6]: pandas.core.series.Series
type(df.time[0])
Out[7]: async_v20.definitions.primitives.DateTime

A standard python float does not have the required accuracy
>>> t = '1513677115.123456789'
>>> float(t)
...<PHONE_NUMBER>.1234567

Which means a numpy.float64 might be in order, but I don't want to add another dependency. Need to have a think, It might not be worth it.

Here's me playing around with different types. I realized a  numpy.float64 doesn't provide the accuracy required either.
I'm thinking the internal representation needs to be an int this won't drop accuracy and will allow for conversion to a pd.Timestamp in a much cleaner way than is currently being done.

Well I ended up inverting the problem, so that all DateTime objects from OANDA are stored as pd.Timestamps
Converting objects to JSON will require you to pass the desired datetime_format string ( the Response object will do this for you).
Ultimately the changes will provide more flexibility allowing users to control what datetime_format they want to work with. Even after OANDA has sent the JSON data.
Although the changes do not affect the public API as specified in the documentation I will be bumping the major version.

version 5.0.0b0 implements these changes. see documentation