my composer cant update latest version of hyperf packages (hyperf/utils)

hello this my composer.json, when i try to install packages with composer install or composer update its keep downloading hyperf/utils 2.0.0 instead of 2.0.8 and it will cause Arr:merge() error and cant run the server, whats the problem with my job?
{
  "name": "hyperf/hyperf-skeleton",
  "type": "project",
  "keywords": [
    "php",
    "swoole",
    "framework",
    "hyperf",
    "microservice",
    "middleware"
  ],
  "description": "A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and middlewares.",
  "license": "Apache-2.0",
  "require": {
    "php": ">=7.4",
    "ext-swoole": ">=4.5",
    "hyperf/cache": "~2.0.0",
    "hyperf/command": "~2.0.0",
    "hyperf/config": "~2.0.0",
    "hyperf/db-connection": "~2.0.0",
    "hyperf/framework": "~2.0.0",
    "hyperf/guzzle": "^2.0",
    "hyperf/http-server": "~2.0.0",
    "hyperf/logger": "~2.0.0",
    "hyperf/memory": "~2.0.0",
    "hyperf/process": "~2.0.0",
    "hyperf/redis": "~2.0.0",
    "hyperf/constants": "~2.0.0",
    "hyperf/model-cache": "~2.0.0",
    "ext-json": "*",
    "firebase/php-jwt": "^5.2",
    "hyperf/validation": "^2.0",
    "hyperf/session": "^2.0",
    "qing7777/hash": "^1.0",
    "hyperf/event": "^2.0"
  },
  "require-dev": {
    "swoole/ide-helper": "^4.5",
    "friendsofphp/php-cs-fixer": "^2.14",
    "mockery/mockery": "^1.0",
    "doctrine/common": "^2.9",
    "phpstan/phpstan": "^0.12",
    "hyperf/devtool": "~2.0.0",
    "hyperf/testing": "~2.0.0",
    "hyperf/watcher": "^2.0"
  },
  "suggest": {
    "ext-openssl": "Required to use HTTPS.",
    "ext-json": "Required to use JSON.",
    "ext-pdo": "Required to use MySQL Client.",
    "ext-pdo_mysql": "Required to use MySQL Client.",
    "ext-redis": "Required to use Redis Client."
  },
  "autoload": {
    "psr-4": {
      "App\\": "app/"
    },
    "files": []
  },
  "autoload-dev": {
    "psr-4": {
      "HyperfTest\\": "./test/"
    }
  },
  "minimum-stability": "dev",
  "prefer-stable": true,
  "extra": [],
  "scripts": {
    "post-root-package-install": [
      "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
    ],
    "post-autoload-dump": [
      "rm -rf runtime/container"
    ],
    "test": "co-phpunit -c phpunit.xml --colors=always",
    "cs-fix": "php-cs-fixer fix $1",
    "analyse": "phpstan analyse --memory-limit 300M -l 0 -c phpstan.neon ./app ./config",
    "start": "php ./bin/hyperf.php start"
  }
}

composer remove doctrine/common

does it works?

@limingxinleo Yes Thank you


Handle permissions and gps status

This patch contains two changes:

Return error when permissions are not set properly for wifi access.
In Android 6 and above, wifi networks scanning return empty SSID list
when GPS is turned off, so now it also asks to turn on GPS if it is disabled.

All these changes were merged from https://github.com/paraggarg37/WifiWizard/
Specifically from these commits:

added permissions for marshmallow
https://github.com/paraggarg37/WifiWizard/commit/47590ea6104e0abc183e592ab86eb3bdf89449ca#diff-71da7ed529b38209b2b0f4bfc226b3ec
added support for android 6
https://github.com/paraggarg37/WifiWizard/commit/eb2b9a69c4aa079bed1e0df53b64e035e22326dc#diff-71da7ed529b38209b2b0f4bfc226b3ec

Why Should This Be In Core?
I used WifiWizard on my Android 5 without problems, but when I deployed it on other people's phones for testing, it didn't work on some phones. It turned out to be either because of unset permissions or disabled GPS on Android >= 6. So these changes could save some troubles to WifiWizard users :)
Of course, one could use other plugins for checking permissions and GPS status, but I think it is nice to have it all included in WifiWizard itself.
Code parts to check
I was not sure, where to put these checks, so please just check if that makes sense to you:
public boolean execute(...) {
        ...
        if(!displayLocationSettingsRequest()){
            callbackContext.error("Android 6 and above Gps turned off");
            return true;
        }

        if(!checkCurrentPermissions()){
            callbackContext.error("permission not found") ;
            return true;
        }

Thanks a lot for maintaining WifiWizard2.
Michal

Oh, now I have tried the 3.0.0 branch and found out that this functionality is already there. Thanks a lot!

Thanks for submitting this PR, have you tried the version 3.0.0 branch by chance?  Permission handling was added in that branch.
I don't mind adding this for support in the old version of WifiWizard (version 2), but have you tested this yourself?  If so what have you tested it on?

Thanks, I have tested it with the 3.0.0 branch, but it didn't work the same way. I don't remember now, how it behaved, but I'll try it soon again and let you know.

Ok yeah this should only be for version 2.x so I changed the PR to that instead of master, as i'm about to merge 3.x into master since 2.x will no longer be supported/maintained in favor of 3.x+

Sure, that makes sense.

I am interested by this PR too. Any news ?

Sorry guys, I haven't tested the 3.0.0 branch yet.
@gontard, could you please test it? If you have Android >= 6, just create an example app with WifiWizard2 (branch 3.0.0) and try wifi scanning when the app doesn't have permissions to access location and when the GPS is turned off.

@arsenal942 only for the 2.1.x branch, this is already handled in the 3.x branch


Azure App Configuration Push Task@5: Undocumented breaking change with feature flags

With version 5 of AzureAppConfigurationPush it is no longer possible to push settings with the feature flag prefix, resulting in the following error: Key cannot start with the reserved prefix for feature flags.
The version 4 of the task works without issue:
- task: AzureAppConfigurationPush@4
  displayName: 'Feature flags - Development'
  inputs:
    azureSubscription: '${{ parameters.serviceConnection }}'
    AppConfigurationEndpoint: '$(appConfigurationEndpoint)'
    ConfigurationFile: '$(Pipeline.Workspace)/${{ parameters.artifactName }}/feature-flags-test.json'
    Separator: '-'
    Prefix: '.appconfig.featureflag/'
    Depth: '1'
    Label: 'Development'
    ContentType: 'application/vnd.microsoft.appconfig.ff+json;charset=utf-8'
    Strict: true

Contents of .json file:
{
  "MyFlagName": {
    "id": "MyFlagName",
    "description": "",
    "enabled": true,
    "conditions": {
      "client_filters": []
    }
  }
}

I cannot find this breaking change in the release notes of the task, so I don't know if this change was intentional or not.

Hello @supereddie, seems we'll need to update the release notes to document it as a breaking change. Apologies for any inconvenience caused. I'll send an update for that.

Since your test json is not using the correct schema that feature flag content type required, hence the MyFlagName would be treated as a normal key-value, turns out you were trying to add a feature flag prefix to a normal key, that's the reason it throws the error.

PR https://github.com/Azure/AppConfiguration/pull/762 has been merged in


The filename or extension is too long

Hello
I'm getting an error when trying to build this plugin https://github.com/SpecFlowOSS/SpecFlow.Rider/tree/upgrade-gradle on Windows 10 (If you want to try checkout the branch upgrade-gradle for the latest version of this plugin and gradle, it's failing as well on master)
build.gradle
    id 'org.jetbrains.kotlin.jvm' version '1.3.61'
    id 'org.jetbrains.intellij' version '0.7.2'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileKotlin'.
> java.io.IOException: Cannot run program "C:\Program Files\Java\jdk-15.0.2\bin\java": CreateProcess error=206, The filename or extension is too long

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 15s
2 actionable tasks: 2 executed

$ .\gradlew.bat --version

------------------------------------------------------------
Gradle 6.8.3
------------------------------------------------------------

Build time:   2021-02-22 16:13:28 UTC
Revision:     9e26b4a9ebb910eaa1b8da8ff8575e514bc61c78

Kotlin:       1.4.20
Groovy:       2.5.12
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          15.0.2 (Oracle Corporation 15.0.2+7-27)
OS:           Windows 10 10.0 amd64

$ java --version
java 15.0.2 2021-01-19
Java(TM) SE Runtime Environment (build 15.0.2+7-27)
Java HotSpot(TM) 64-Bit Server VM (build 15.0.2+7-27, mixed mode, sharing)

I also tried with other versions of java 11

Hi. Exception is thrown from kotlin-plugin, not from gradle-intellij-plugin. It looks like the issue https://youtrack.jetbrains.com/issue/KT-34487 and looks like it's fixed in Kotlin 1.4.
The problem might be in the mismatching Kotlin plugin version and Kotlin version that is used for compilation (taken from IntelliJ SDK if you do not define it explicitly). You may try to arrange versions.
Similar problem: https://discuss.kotlinlang.org/t/gradle-error-when-updating-kotlin-version/10184/2

Hi,
I was able to solve my problem, I tried to upgrade to Kotlin 1.4 but I was getting an error, the problem was an old version of rd-gen
Now it works (I upgrade to kotlin 1.4 and com.jetbrains.rd:rd-gen:0.1831.17)

got it, thank you for the update


E: Unable to locate package hhvm

2_Free Disk Space (Ubuntu).txt

@jlumbroso Is this repo still maintained?

Thanks @BenjaminX and @gruve-p!

Sorry @JacopKane, it is now:
https://github.com/jlumbroso/free-disk-space/releases/tag/v1.2.0

Sorry @JacopKane, it is now: https://github.com/jlumbroso/free-disk-space/releases/tag/v1.2.0

thank you


1.20.6 fix

Fix fog-distance, pack version and README for minecraft version 1.20.6.
Based on a code-snippet from themrpancake posted on Godlands.

It maybe is needed to indicate that this fix will make the rp only work on 1.20.6 +

Thank you so much for this fix! I was really needing something that worked in the new version and supports armor trims!
The only issue I have right now is that Custom Model data only appears as the dyed color :(
Is there a fix for this?

I found out the issue! I did not add a 2nd layer to my leather armor in the .json file. For anyone who has the same issue, you can refer to the following:
ruby_boots.json


feat(ast_tools): Move tsify custom types to estree attribute macro

Part of #6347

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6934  👈
#6933
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ottomated and the rest of your teammates on  Graphite

Merge activity

Oct 27, 9:40 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


^ wrote test for issue #6

I checked a problem in issue #6 and wrote a test. Everything works correctly

The .idea directory has been added with this PR.


Middleware (maybe) not working

Hey @wesdu
I'm trying to use your library but even after installation and add "django_istio_opentracing.middleware.Middleware", to the application settings, which is running in Kubernetes + Istio, I'm not able to see new spans on the Jaeger, I'm only able to see spans related to Istio Proxy. There is something I'm missing here?

any detail? Are you using requests ?

I have a very complex application and I'm trying to get all requests passing through, going to the database, other systems, and so on. The application uses requests in some places but even the requests that use it I'm not able to see into the Jaeger from Istio installation. Let me explain what I did until now...

I've added the configuration below to settings

from config.settings.base import MIDDLEWARE

MIDDLEWARE += [
    "django_istio_opentracing.middleware.Middleware",
]

After that I made several requests to the application but I'm only able to see the Istio related tracing

If you are using requests to make request


angular-bootstrap CLI builder

Just as there is manual web-based builder to chose angular-bootstrap components to download. I would like to have it automated in our gulp build process. Is there a simple CLI tool that takes arguments like modal, typehead and builds the source and minified file with only those components?

Nope, there is no specific CLI and we don't plan to have one (at least not now). To automate things you can still clone this repo and run the build on your end.


Additional logs zed upload

To have better understanding of behavior inside zedUpload we can improve logs

Do we use logs anywhere in here? These are libraries; no guarantee that logs are setup or that they are running somewhere that can print out.


Configuration update

Convert the .yml config to .json for future updates.
Use this .json during the cleaning process to make sure:

maximum retention period applied
PAN file restrictions applied (e.g. ad1 not to be processed)

Using the same .json during the report making process to make sure:

only LAs that have signed up to the DPIA have their data processed
retention applied depending on the use case e.g. 11 years PAN, 6 years SUFFICIENCY
file restrictions applied per use case
column restrictions applied per use case

Hello Patrick,
The issue that I brought to your attention earlier is an issue with the code: Within the apply_retention() function in transform.py, this code doesn't work:
    for table_name in data:
        table = data[table_name].copy()
        data_container[table_name] = table[
            table[year_column] > current_year - retention_period
        ].copy()

        data_container[table_name] = table[
            table[la_column].isin(signed_las)
            ].copy()

Because data_container is re-referencing table.copy() for the signed_las check, it nullifies the result of the first check where it applies retention period.
By testing a modified json that should filter out 2020 files, you can see that it never does. But if you comment out lines 177-179, the code does then remove 2020 files.

Thanks Michael, I have pushed some changes now that should fix this. I did a quick end to end test and it looks like it's working as expected now.


Arcade Physics collisions optimizations

This PR

Adds a new feature

When colliding physics groups with the search tree enabled, there was an unnecessary intersection test for each body returned by the search.

When doing an overlap collision, there was an unnecessary intersection test for each pair of overlapping bodies.

👍


Prepared tests for issues 37-40

#37, #38, #39, #40

This is more of an FYI, no code is changed, this PR only adds 4 tests that are all set to skip as they fail right now


Incomplete Docu

What version of Traefik are you using (traefik version)?
docker - traefik:latest
What is your environment & configuration (arguments, toml...)?
Trafik (proxy.yaml)
version: "3.0"

services:
  traefik:
    image: traefik
    networks:
     - proxy
    command: --web --docker.swarmmode --docker.domain=berndklaus.at --docker.watch --docker.endpoint=unix://var/run/docker.sock
    ports:
      - "80:80"
      - "8080:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      #- ./traefik.toml:/etc/traefik/traefik.toml
    deploy:
      mode: global
      placement:
        constraints:
          - node.role == manager

networks:
  proxy:
    external: true

WhoamI (whoami.yaml)
networks:
  proxy:
    external: true
root@swarm1:~# cat whoami.yaml
version: "3"
services:
  web:
    image: emilevauge/whoami
    networks:
      - proxy
    deploy:
      labels:
        - "traefik.port=80"
        - "traefik.docker.network=proxy"
        - "traefik.frontend.rule=Host:whoami.berndklaus.at"
      replicas: 3

networks:
  proxy:
    external: true

What i wanna do:
Would like to enable SSL (Letsencrypt Support).
I'm new to traefik, and i do miss information:

on howto add an costum configuration (.toml) within a docker compose swarm
list of commands available. (I'm not able to exec into the container)
do i need a costum configuration to enable Letsencrypt?
if i do use a costum config, does the from docker backend generated config changes extend the costum config or otherwrite them?

May someone can help me ;)

I am having the exact same problem. How to enable letsencrypt with a docker deploy setup?

I found an example here #750, (specifying options on the traefik commandline) but it would require traefik to be restarted when adding a letsencrypt domain.

Ok, I got it to work with the following config:
version: "3"
services:
  proxy:
    image: traefik
    command: --web --docker --docker.swarmmode --docker.domain=docker.localhost --docker.watch --logLevel=DEBUG --entryPoints='Name:http Address::80 Redirect.EntryPoint:https' --entryPoints='Name:https Address::443 TLS' --acme.entryPoint=https<EMAIL_ADDRESS>--acme.storage=/etc/traefik/acme/acme.json --acme.domains=odoo.xxxxxx.com,viz.xxxxxx.com,backend.xxxxxx.com
    networks:
      - proxy
    ports:
      - 80:80
      - 443:443
      - 8080:8080
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - traefikdata:/etc/traefik/acme
    deploy:
      placement:
        constraints:
          - node.labels.env == prod
          - node.role == manager

volumes:
  traefikdata:
    driver: local-persist
    driver_opts:
      mountpoint: /data/traefik

networks:
  proxy:
    driver: overlay

Though, auto-redirect from 80 to 443 doesn't work yet.

Alright, auto-redirect works if you specify deploy labels like this:
    deploy:
      labels:
        - traefik.port=8080
        - traefik.backend=monitor_viz
        - traefik.docker.network=proxy
        - traefik.frontend.rule=Host:viz.xxxxx.com
        - traefik.frontend.entryPoints=http,https

You need to specify both http and https as entrypoints.

HY @raarts , thanks for the Update. Amazing!

Note for keeping the downloaded certificated I used a host-mount with the local-persist driver. This means you still cannot move the treafik container around easily. Also treafik needs to run an a manager node. I prepared all my manager nodes with a /data/traefik directory.

Thanks for the hint!!
I'll use this with a portworx shared volume across hosts in the swarm: https://github.com/Berndinox/swarm_portworx

@Berndinox @raarts if you think the documentation needs some upgrade, your help is welcome :)

@emilevauge  atm i do not feel confident enough to do, but may i will.. ;)
All the docu is arround the toml.conf, but i think there should be more about docker specific things:

how to create a traefik service in swarm
best practices for configuring traefik inside docker
real world examples (?)

BR

@emilevauge https://github.com/emilevauge,  @Berndinox
https://github.com/Berndinox I have cloned the repo, and am looking at
learning how to extend the docs. No  promises though.
On Thu, Feb 9, 2017 at 9:29 AM, Berndinox<EMAIL_ADDRESS>wrote:

@emilevauge https://github.com/emilevauge atm i do not feel confident
enough to do, but may i will.. ;)
All the docu is arround the toml.conf, but i think there should be more
about docker specific things:

how to create a traefik service in swarm
best practices for configuring traefik inside docker
real world examples (?)

BR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containous/traefik/issues/1091#issuecomment-278577372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADBXxdqgLfvlUeX_NGvqzkbjPFcZc_iGks5ras5egaJpZM4Lz52x
.

@raarts i got one other question, would it also work if i do not persist the acme folder into a volume.
Cause when i scale the traefik service the same volume is mapped multiple times, and so i got doubled entries for my subdomains. thanks :)

I don't think that will work. I think there are two approaches, (1) is to make sure only one container runs per host. Docker deploy does not support affinity yet, but you can claim for example cpu1 so docker will have no choice but to find another host*). (2) define two services traefik and traefik-letsencrypt, the first one is for scaling, has letsencrypt disabled, and mounts the volume read-only, and the second one has letsencrypt enabled, maybe even has proxying disabled, mounting read-write and isn't scaled.
*) Of course if you have multiple hosts, you still need one location to  keep your data, so if you control the hosts, you can create a shared filesystem, using nfs or smbfs or something, and let the hosts mount those shares, the containers won't know or care. If you don't control the hosts, then I have no solution other than spending money on shared-storage-in-the-cloud somewhere, and using a volume driver.

Hy @raarts,  i'd like the read only approach, however with compose v3 ready only volumes are not possible jet?!?
I tested the following setup:
version: '3'

services:
  whoami1:
    image: jwilder/whoami
    deploy:
      replicas: 1
      restart_policy:
        delay: 10s
        max_attempts: 10
        window: 60s
    volumes:
      - data:/data

  whoami2:
    image: jwilder/whoami
    deploy:
      replicas: 1
      restart_policy:
        delay: 10s
        max_attempts: 10
        window: 60s
    volumes:
      - data:/data:r

volumes:
  data:
    driver: local-persist
    driver_opts:
      mountpoint: /mnt/glusterfs/docker/whoami

Shared Volume accross hosts is a gluster volume. Docker inspect show RW (Read and Write) on both containers.
Also appending the config with "read_only: true" is ignored.
:(

For read-only I think you need to append :ro
On Sun, Feb 12, 2017 at 5:10 PM, Berndinox<EMAIL_ADDRESS>wrote:

Hy @raarts https://github.com/raarts, i'd like the read only approach,
however with compose v3 ready only volumes are not possible jet?!?
I tested the following setup:
version: '3'
services:
whoami1:
image: jwilder/whoami
deploy:
replicas: 1
restart_policy:
delay: 10s
max_attempts: 10
window: 60s
volumes:
- data:/data
whoami2:
image: jwilder/whoami
deploy:
replicas: 1
restart_policy:
delay: 10s
max_attempts: 10
window: 60s
volumes:
- data:/data:r
volumes:
data:
driver: local-persist
driver_opts:
mountpoint: /mnt/glusterfs/docker/whoami
Shared Volume accross hosts is a gluster volume. Docker inspect show RW
(Read and Write) on both containers.
Also appending the config with "read_only: true" is ignored.
:(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containous/traefik/issues/1091#issuecomment-279228503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADBXxTDLgDVIMLYZt3jt8OiBXHw53Ccyks5rby8EgaJpZM4Lz52x
.

Thanks for sharing!


Enhancement: Table output

Please note that this also incorporates:

Fix: Fixes issue with creating tag pages for nested tags
Enhancement: Shows full link name instead of *

These needed to be included for the table output to work properly. Both of these are also available in separate pull requests.
Enhancement: Table output

Outputs links in tables instead of lists
Wildcard tag pages have separate tables for different links

Please note that tags that were used in bullet lists with additional bullets under them (hiearchically) create additional table rows on tag pages. i'd like to keep them in the same table cell using <br /> tags, but I haven't figured out how to do that yet.

Haha I've altered this same part of code, but using a Quote Callout, and grouping them by file.

I think that since we're 2 making changes on this part of the output, it's the author decision & style.
Thinking out loud, just some ideas:
A more complex way to make everybody happy would be to give the choice to the user between multiple content formatters. Or maybe even loading a user-written .js file to do the formatting

Haha I've altered this same part of code, but using a Quote Callout, and grouping them by file.

I think that since we're 2 making changes on this part of the output, let's wait for the author decision & personnal touch.
Thinking out loud, just some ideas: A more complex way to make everybody happy would be to give the choice to the user between multiple content formatters. Or maybe even loading a user-written .js file to do the formatting

@GerkinDev I'll take a look at your changes, and I'm working on create a "Link output method" setting and trying to encase my changes accordingly. I'm not sure allowing a user-written .js file is a good idea off the bat though; it could work, but I don't know how much might break if it's really bad code.


Day cell override

This patch allows for taking control over the exact content of a day cell. Like this, additional information can be rendered into the day cell (daily price information in my case).
This patch contains no BC breaks.

Coverage remained the same at 100.0% when pulling<PHONE_NUMBER>a19707f601b200100f11c3a4ef18e0 on elHornair:day_cell_override into 4f3037d2404387b011614163c7fa673cda45971d on charliekassel:master.


Add the boiler plate for the modify and terminate workflows

Add the boilierplate code for the modify and terminate. The details still need to be filled in.

This looks great! For whatever reason, we set speed as a fixed input, so our modify won't be able to change that, will it? Either way, this is perfect for our needs, approving and merging!


PRAGMA key shall use quotes for key value

Currently library does not allows to use any symbols except alphanumeric. Although it shall be supported according to SQLCipher documentation: https://www.zetetic.net/sqlcipher/sqlcipher-api/#PRAGMA_key
For instance now it's impossible to use keys like in this example:
PRAGMA key = "x'2DD29CA851E7B56E4697B0E1F08507293D761A05CE4D1B628663F411A8086D99'";

it's merged. Thanks @torwald-sergesson  for the fix.


Create React App 4.0 alpha caches ESLint config on first run and ignores later changes. This prevents React 17 from compiling without React import unless you modify the config before first run.

Describe the bug
When attempting to run Create React App 4.0 alpha with React 17 without
an explicit React import (as 17 no longer needs it), in order to avoid
ESLint errors, users are instructed to add ESLint config rules
to package.json so it looks like this:
  "eslintConfig": {     "extends": [       "react-app",       "react-app/jest"     ],     "rules": {       "react/jsx-uses-react": "off",       "react/react-in-jsx-scope": "off"     }   },
The problem is that currently, the initial ESLint configuration is cached
when the user  first runs npm start or yarn start, so if the user attempts
to make this modification after running a project for the first time,
the modifications will be ignored, and ESLint will continue to use
the cached config, preventing compilation by throwing this error:
'React' must be in scope when using JSX  react/react-in-jsx-scope
The current workaround I've been using, as this also affects version 3.4.3
when setting EXTEND_ESLINT=true, is to change line 345 (React Scripts 3.4.3)
or line 363 (React Scripts 4.0.0-next.98) in
./node_modules/react-scripts/config/webpack.config.js from cache=true to cache=false.
Environment

System:
OS: Windows 10 10.0.19041
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Binaries:
Node: 14.12.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.19041.423.0
Internet Explorer: 11.0.19041.1
npmPackages:
react: ^17.0.0-rc.3 => 17.0.0-rc.3
react-dom: ^17.0.0-rc.3 => 17.0.0-rc.3
react-scripts: 4.0.0-next.98 => 4.0.0-next.98+025f2739
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

npx create-react-app@next --scripts-version=@next --template=cra-template@next my-app && cd my-app

yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>

yarn start

CTRL-C to kill app

delete import React from 'react' from top of my-app/src/App.js

yarn start (should throw an error from eslint)

add the following under eslintConfig in package.json to fix the error:
"rules": {    "react/jsx-uses-react": "off",    "react/react-in-jsx-scope": "off"  }

run yarn start again, and the error still occurs

(It runs as expected if you modify a component after modifying ESLint config.)
(It will also work again if you change cache to false in ./node_modules/react-scripts/config/webpack.config.js.)
(The behavior is identical when using npm instead of yarn.)
Expected behavior

I expect the app to run normally.
Actual behavior

Browser output:
Failed to compile.
./src/App.js
Line 6:5:    'React' must be in scope when using JSX  react/react-in-jsx-scope
Line 7:7:    'React' must be in scope when using JSX  react/react-in-jsx-scope
Line 8:9:    'React' must be in scope when using JSX  react/react-in-jsx-scope
Line 9:9:    'React' must be in scope when using JSX  react/react-in-jsx-scope
Line 10:16:  'React' must be in scope when using JSX  react/react-in-jsx-scope
Line 12:9:   'React' must be in scope when using JSX  react/react-in-jsx-scope
Reproducible demo

N/A - A fresh install would fix it, as the problem is in the cached files, and I can't reproduce that without uploading the entire node_modules directory.
The main problem is that this bug will cause an almost fresh application to fail,
and the user won't have any idea what caused it.
This is also a problem with using EXTEND_ESLINT on the current stable version of CRA. But I think this is a
much more significant problem, because extending ESLint right now is an experimental feature, and it isn't expected
to work perfectly.
But with this, if someone tries to add React 17 to a project and use its intended features, it will fail to compile
unless they modify package.json before the first run, and they'll probably just think it's buggy,
as there won't be any indication why it's failing.

I realized I was wrong about what was actually happening. The ESLint config isn't itself being cached, it's just the result of linting is being cached. So if you modify a src file after modifying the config, it will use the new ESLint config, but it will ignore config changes if you only change the config. It also seems to revert and used the cached result if you change the file back to a state in which it was already linted. So if I remove the import line, run it, then modify the config to turn those errors off, it will still have the same errors, but if I change the file again, it will relint it.
I think this will cause a lot of confusion. I don't really know if this could be considered a CRA issue now. Maybe it's an issue with eslint-loader or webpack. But I think maybe caching should be turned off if there isn't a way to force ESLint to check its own config, as anyone who encounters an error then tries to fix it by editing the config will probably end up frustrated.

Hello,
Sorry but how did you fix this? I'm getting the exact same thing after trying the new CRA.
src\App.js
  Line 6:5:    'React' must be in scope when using JSX  react/react-in-jsx-scope
  Line 7:7:    'React' must be in scope when using JSX  react/react-in-jsx-scope
  Line 8:9:    'React' must be in scope when using JSX  react/react-in-jsx-scope
  Line 9:9:    'React' must be in scope when using JSX  react/react-in-jsx-scope
  Line 10:16:  'React' must be in scope when using JSX  react/react-in-jsx-scope
  Line 12:9:   'React' must be in scope when using JSX  react/react-in-jsx-scope

@robertwt7 did you end up fixing it? Running into this myself.

June still having this issue

Adding those rules to your package.json (or whatever eslint config you are using)
//...
  "eslintConfig": {
    "extends": "react-app",
    "rules": {
      "react/jsx-uses-react": "off",
      "react/react-in-jsx-scope": "off"
    }
  },
//...

and running the app with the env variable EXTEND_ESLINT=true did the trick for me.


Crash on otherwise vanilla 1.12.1 profile

https://pastebin.com/MswhCHpH
Game window doesn't even get a chance to open, the launcher quickly crashes due to an asm transformer using an invalid class def: net.minecraft.block.BlockFire

Seems like I forgot to update some mappings. Should be an easy fix.

Try version 1.1.4.

Working now, thanks!


fix issue #998

I check the issue #998  and test it on simple API server, the issue belongs to "httpclient" and after update the "httpclient" version, the issue has fixed

I have fix the issue in ConcurrentSkipList and update gradle, the Travis CI build failed because of java version.
can you change the CI? @smarek

Travis CI configuration is stored in file /.travis.yml, you can update it along in PR next time
Also next time you can squash your commits into one commit, or I'll have to squash them on merging PR.
I've submitted Travis and SDK compatibility fixes, so update your local development, so you base on latest master in next PR.
Thank you for your hard work

I will take care of commits next time.
thanks for tips and update travis.yml.


No validation is done for 'dependencies'

No validation is done for this config. Tests will fail with error if this is not configured.
https://github.com/diptopandit/vscode-snort3-test-adapter/blob/f99f351ab72b770d07edfaf3382d2feb0587a075/src/snort3Test.ts#L218

Fixed with 17eed1e945601ea7fbca253571a1c60fc5fc0c87


how to test

hi, i've read that u are searching someone that can help u test the module, how can i contact u?

Hi, Im currently working on some stuff outside programming. Im probably going to finish this but I dont have an ETA yet. There is not much left apart from writing some connectors to actually do stuff and writing the docs.
You can actually clone and install this module as a normal module, you can enable each of the current experimental functions just adding the module in your config.js file:
		{
			module: "MMM-HomeKit",
			position: "fullscreen_above",
		},

After doing this you can use another computer (whitelisted in your MM2 machine or RPI) to access the control panel to setup Homekit devices: ip:8080/homekit/ then configuring devices should be really easy.
Depending on the reflections of your screen your Iphone may not recognize the Homekit QR code. If this is the case you can just touch "I cannot find my accessory" and you can enter the number manually

Hi, tried to install but it doesn’t even load MagicMirror :(, fixed deleting from config file

Il giorno 12 lug 2024, alle ore 02:35, Fabrizio @.***> ha scritto:
{
module: "MMM-HomeKit",
position: "fullscreen_above",
},


Resources for folks on the other side of the table?

This is an awesome resource for people looking to polish their skills for when they go into interviews.
Are there any plans to add some resources for the interviewers? IE, the brand new tech lead who needs to hire a junior but has no idea what kinds of questions to ask, or the manager who doesn't know a ton but needs to find just the right dev for their open position.

Oh yes that's in the works. To be fair, there's more demand for resources for interviewees rather than interviewers, so that'll be the focus for now. But it's something we're definitely keeping in mind 😎

Awesome!
I totally understand that there are more folks looking for help being interviewees, rather than interviewers, but knowing it's on the roadmap is great :smile:

www.dafacaipw.com  老哥换个友链吗？
联系QQ：1297532431

Some brief resources here - https://techinterviewhandbook.org/interviewer-cheatsheet/


feat: support password managers RELEASE

fixes https://github.com/descope/etc/issues/4430
1password:
https://github.com/descope/descope-js/assets/11805663/fe5ea2c2-99cf-47ce-9f8a-56f643c2cb1f
Safari:
https://github.com/descope/descope-js/assets/11805663/a1a0eb47-7d5e-4b13-98b6-1adaaca35b27
Chrome:
https://github.com/descope/descope-js/assets/11805663/1bef9a0c-9899-41e9-96a7-837e2c311252

Well done !!!


Fix t-SNE plot

re: https://github.com/msmbuilder/osprey/issues/125
Also added a test and tried to reorganize the plotting methods into their own module.
Sent from my :airplane:. Sorry for the brevity or unusual tone.

Not sure why travis isn't checking this PR...


Terminal won't open

Environment
Windows build number:19013
Windows Terminal version (if applicable): I can't look it up :(

Any other software? No

Steps to reproduce
I've somehow gotten Windows Terminal into an interesting error state. Sorry I don't know how to reproduce this error. Looking more to see if I can collect any traces or anything for your team to help identify this.

I click on the Windows Terminal and it starts up

No Window pops up (I checked with Alt+Tab)
Try to close Terminal and see a 'Not responding' message

Expected behavior
Windows Terminal should open up.
Actual behavior
Windows Terminal doesn't open.

More info:
I tried to open WSL from a regular Console window and it was stuck. My WSL service was in a stuck state.
My guess is that Terminal was polling my WSL instance to get my distros, but since that was stuck Terminal ended up stuck. I restarted and my WSL service was fixed, and Terminal was fixed as well.

@craigloewen-msft I bet this is #3987, right?

Yeah that's very very likely what it was. Feel free to close this if you're tracking it over in #3987 as that would fix my issue.

k cool, thanks Craig
/dup #3987

Reinstall Terminal, try to turn off Settings-Rendering-Use the new text renderer("AtlasEngine) may help.


mailgun integration

Note, the api tokens uploaded in 7083f03 will not work. It's put in as a placeholder


CleanMyMac X 5.0.2

CleanMyMac X is all-in-one package to awesomize your Mac. It cleans megatons of junk and makes your computer run faster. Just like it did on day one. CleanMyMac X chases junk in all corners of your macOS. It cleans unneeded files, like outdated caches, broken downloads, logs, and useless localizations. You can remove tons of clutter that lurks in iTunes, Mail, Photos, and even locate gigabytes of large hidden files. Mac cleaning tools in CleanMyMac X will cut the extra weight in seconds.


Redix does not provide any error message and just exit here

https://github.com/whatyouhide/redix/blob/59224955c788745a2b82b916d19919ec594b53bd/lib/redix/connection.ex#L85C4-L85C21
It would be a better user experience if before exit we had an error or we could return error instead of just exit

That EXIT is propagating the exit reason of the Redix process and exits the caller process with that reason.
However, yes, we can make it a little bit better. Something like:
exit({:redix_exited_during_call, reason})

Thoughts? I'd appreciate a PR on this, I don't really have any bandwidth right now 🙃


[Bug]: SyntaxError: Unexpected identifier 'assert'

What happened?
When running the command npx preevy init, I encountered the following error:
SyntaxError: Unexpected identifier 'assert'
Add screenshots

Steps to reproduce the behavior

Open a terminal or command prompt.
Run the command npx preevy init.
The error SyntaxError: Unexpected identifier 'assert' is displayed.
Run the command preevy init.
The same error SyntaxError: Unexpected identifier 'assert' is displayed.

Expected behavior
expected the Preevy project initialization process to start without any errors. However, instead of the expected behavior, I encountered the SyntaxError: Unexpected identifier 'assert' error.[1]
What OS are you seeing the problem on?
MacOS
Additional context
while installing i received this:
npm install -g preevy
⠼
⠦
npm warn deprecated<EMAIL_ADDRESS>this library is no longer supported
npm warn deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated<EMAIL_ADDRESS>This package has moved to @smithy/util-waiter

added 766 packages in 2m```

nodejs version:
node -v
v22.1.0

### Record

- [X] I agree to follow this project's Code of Conduct

Hi @ShivamB25

Can you try with Node.js v18.19.1? You can use nvm to easily switch between Node.js versions.
If this doesn't work, can you please run DEBUG='*' preevy init --debug and copy the full trace details?

Looks related to the latest changes in Node.js 22: https://github.com/nodejs/node/pull/52104

thank you


Make it possible to have multiple statements in a query tab, but execute only selected one.

Done in https://github.com/smurfpandey/mysqlweb/commit/367933f0eaf6cb383acef458df45fe8bed378eb5


Want to add "Two Shuffled Sequences" Problem in Codeforces.

Is your feature request related to a problem? Please describe.
This is the problem question in Codeforces and I want to add the solution of this in C++.
Problem Link: Two Shuffled Sequences
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

@Amit366 @Ayush7614 please assign this issue to me.


working with md files

I have updated to Astro 2.0 and Content Collections. Is there some documentation on how to work with md files?  Fe. if I switch from english to spanish I want my posts (md files) to switch to spanish as well. Hope it makes sense.
thanks

I second this. I am going to need this as well.

I created two folders for the blog for the languages and changed the spread of the slug for the route itself, it worked fine, so I don't even need to generate the pages with the cli of this project, example.
I wish there was something of its own in this project for that.

actually we do not need to generate in content folder
there your files with different translations, try structure like this
content/blog/en/
content/blog/fr/

then you can filter blog content like this
import i18next from "i18next";

const currentLang = i18next.language;

const blogEntries = await getCollection("blog", ({ data, id }) => {
  return id.startsWith(`${currentLang}/`);
});

when you open site.com/en/blog it should take posts from blog with English translation

That is the idea I had in mind, yes.


Clarity, spelling and punctuation changes in the docs.

Just a few small changes to more the docs more clear.

This is great!


IntelliSense always suggests "<?php" when in HTML

Every time I close an HTML tag in a PHP file, IntelliSense suggests <?php as next string.

This is distracting when writing HTML: When I want to enter a linebreak, I first have to remove the suggestion before hitting Enter.
Is there a possibility to remove this particular suggestion?
(Using PHP IntelliSense V1.2.1 in Visual Studio Code 1.11.2 on Windows 10, php.suggest.basic is set to false)

This is because we need to set the triggerCharacters to > because a sequence like -> is not supported. See https://github.com/Microsoft/language-server-protocol/issues/138

Just found the responsable code line: https://github.com/felixfbecker/php-language-server/blob/master/src/CompletionProvider.php#L281
I would prefer to have the first condition removed:
} else if ($pos == new Position(0, 0)) {

My question is: Am I the only one who is annoyed by this? (Or am I the only one editing HTML in PHP files ?)

I don't understand how removing that condition would help

Sorry, I didn't make myself clear. Currently, the conditions are like this:
        } else if ($node instanceof Node\Stmt\InlineHTML || $pos == new Position(0, 0)) {

If I understand this correctly, the <?php-completion triggers on InlineHTML nodes and when the cursor is at the beginning of a document.
I propose to remove the first condition, so that line would only trigger on the second condition:
} else if ($pos == new Position(0, 0)) {

Before opening a pull request I would like to understand why this line is how it is and whether my propsal is actually wanted.

The line is how it is to propose a new opening tag inside HTML. That is as designed. The issue is just that the autocomplete pop up all the time because we need to set > as a trigger character.

Yes, so before we go around in further circles: Do you think my request to remove this autocomplete is reasonable and that I should try my hands on a pull request to remove it?

I don't think so, that is as designed - Microsoft needs to fix the trigger characters

Hello.... I am having this issue as well and it is annoying to be honest. Is there a workaround or something?

Express your need for this on https://github.com/Microsoft/language-server-protocol/issues/138 :)

Okay. I hope they do whatever is needed soon. Thanks.

Thanks for directing me here @felixfbecker - hopefully MS gets this fixed soon!

@felixfbecker same this happening to me. But i don't think this is microsoft language issue because when i turn off the intellisense then there is no <?php suggestion. And after turn this on, this is keep starts showing.
I don't know the structure and process of intellisense so i am helpless.
Sir if you can fix it then please. :)

Keep throwing the pressure on that issue: https://github.com/Microsoft/language-server-protocol/issues/138 - if there is enough annoyance maybe the Microsoft can prioritize fixing that.

Ya, for example sometimes in php file we also include html, so the trigger for auto completion or IntelliSense should only work inside php tag (). If this is by design from vscode, then we should make a request for it.

this also happen in vscode. the suggestion for ).
The problem doesn't happen after the extension has been disabled.

You already did it.

Just came here to voice my displeasure. IMHO this suggestion needs to be removed until it can be turned into an option.
It suggests <?php when I type literally any character.
This is a somewhat useless suggestion, anyway. Nobody is saving an appreciable amount of time by <?php being autocompleted. I am (we all are, I suspect), however, wasting time by having to clean up all the times I forget to hit escape and this garbage gets inserted.

Since we have no alternatives i would like to vote to remove <?php sugestion until we have news from Microsoft/language-server-protocol#138
It is annoying so much everyone.

@renoirfaria It is already implemented?

Nice. The feature was never needed in my opinion

@jens1o it is? I am telling it since my Atom IDE keeps suggesting it.

@renoirfaria https://github.com/atom/ide-php/issues/47 It still needs to support the feature ;)

Could you please tosh it? It is so annoying that one can barely work with it.

I will keep updating this thread with the new snippet to remove/comment until it's fixed:
Remove/comment these lines as of 12/20
https://github.com/felixfbecker/php-language-server/blob/9eea26df711920a7e04d4894fc4b9263ee783e11/src/CompletionProvider.php#L176-L181

Is it supposed to be fixed? Because it sure aren't for me...

@Jensen0710 Yes it is, but vscode still doesn't support it.

Same for me, the problem of the suggest persists.

Still not sure why you don't just remove the lines I outlined? Nobody is saving time by having <?php auto-suggested. We are WASTING time having to hit escape or click out of the suggestion every time we type an HTML tag. @felixfbecker can you explain why you can't just remove this?
https://github.com/felixfbecker/php-language-server/blob/9eea26df711920a7e04d4894fc4b9263ee783e11/src/CompletionProvider.php#L176-L181

I would be fine with a PR defaulting to not propose it inside HTML if the CompletionContext was not sent (I think the suggestion at the very beginning of the file should be kept as that is reasonable).

I'm going to do this now, so I don't get my notifications spammed with this (overstated) issue.

The vscode developers introduced the CompletionContext themselves, but you can always express to them that there is a desire to have it implemented

@felixfbecker @jens1o Sorry to bother you, I'm new to VS Code. So we have to wait for the fix, to consider this issue really solved? 🙂

From a language server standpoint, assuming a spec compliant client, there is no issue in the language server.
From a vscode user perspective, you'll either need to wait until vscode implements the parameter, or help out on the workaround I suggested.

@felixfbecker I'd basically never expect the <?php in the html context, except for possibly at the beginning of a file. The only other time it might be expected is immediately after switching from php context to html context via ?>. Generally tho, the suggestion of <?php even in those cases is of limited advantage.

That tinny <?php thing is of minor importance when there is a gazillion of others to take care of. On the contrary, when it pops up at the most inappropriate moments it can cause mistakes. Please remove it permanently.

As the person who opened this issue I would like everybody to please relax. Pull requests are on their way.
You can upvote on the issue itself if you're bothered by the current behaviour.
@felixfbecker Thanks for you work and patience.

@felixfbecker I am using Atom. This should illustrate why the <?php suggestion is irritating. Should I hit enter to try to get to a new line, I will end up with <div<?php

@bcorcoran what version of ide-php do you use?

Latest, I literally just updated a few minutes ago.

Could you please still tell me the version number

0.7.5

Is that an automatic suggestion or did you invoke it with Cmd+Space? Could you post LSP logs?

It's automatic. How do I get LSP logs?

I don't know, I don't use Atom

Anyway, the solution is to delete/comment out the lines I have been posting. In the rare case that a <?php suggestion would be useful, I am happy to type it out manually rather than deal with it being suggested for literally any html tag. Sorry for being irritating about this, but it's an irritating issue.

rather than deal with it being suggested for literally any html tag

There should be no more autotriggered suggestions on the > in a client like Atom ide-php v0.7.5 (which should send CompletionContext) not in VS Code (which sends no CompletionContext). This is unit tested in the language server. To help you further I would have to see LSP logs.

It triggers with any < and doesn't go away if you type other characters. That was what I was trying to illustrate with the screenshot.

Type <

Type anything else

I think the <?php suggestion should go away if you don't type <?php

I see that you also get a suggestion for div. Does that disappear if you don't type div? If not, then that sounds more like an Atom issue


Redux setup is not correct

Unfortunately, the Redux setup in this example project is not correct. It's still using the legacy Redux createStore API, using "hand-written" reducer logic with separate action constants, and following an outdated folder structure.  Today we teach and recommend using "modern Redux" using our official Redux Toolkit package, the React-Redux hooks API, and a "feature folder" structure with a single "slice" file of Redux logic per feature.
Please see the "Redux Essentials" tutorial and the Redux Style Guide best practices page in our docs for our recommended approaches:

https://redux.js.org/tutorials/index
https://redux.js.org/style-guide/style-guide

@markerikson Thanks for bringing this to my attention. The new setup seems far neater to use!
I have removed the old redux structure and added an example with redux-toolkit in #17.

Great, thanks!


Only upload to docker hub on master branch

Coverage remained the same at 98.938% when pulling 54bdb659d8fd73a9e3c1c05521693721a6c575f2 on fix_travis_build_v102 into c412384581a6dc7915cda4082198c1c0ab38a6cd on master.


Uglifier runs into problems with certain combination of modern JS syntax (await, destructuring, Promise.all)

Hi there,
Version (4.2.0)
My JS compressor settings are this:
  config.assets.js_compressor = Uglifier.new({
    harmony: true, # Required for ES6 scripts
    output: {
      comments: :none, # Remove absolutely every comment
      max_line_len: 512, # Automatically wrap minified lines to 512 characters
    }
  })

On rake assets:precompile I get this error:
excluded from capture: DSN not set
rake aborted!
Uglifier::Error:

After a lot of trial and error and debugging I was able to deduce the issue to be this syntax:
var [defaultsRes, selectedData] = await Promise.all(reqs);

The code ran as expected in development but could not be handled by the prod uglifier settings (noted above). Switching to the following fixed things for me:
var responses = await Promise.all(reqs);
var defaultsRes = responses[0];
var selectedData = responses[1];

Thanks!

Anything happening on this issue? I just ran into the same problem. No error message or line number so I had to remove pieces of my JS code to narrow down where Uglifier failed. Turned out to be a destructuring statement.


⚠ ClamAV has degraded performance

In 43af981, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 95 ms

Resolved: ClamAV performance has improved in 6e55468.


The internals of class="modal" are not removed on closeModal()

Reproduction:
Taking code from documentation

Modal Header

A bunch of text

            Agree

opening modal by js
var mId = '#modal1'
// open modal
$(mId).openModal({dismissable: false});
// wait for something here
setTimeout(function(){}, 3000);
// close modal
$(mId).closeModal();

Expected behaviour:
After some delay modal should be complitely close including the content
What does happen now:
Modal background disapearing though content stay on screen and even more, it ignores click and does not respond at all

This does not reproduce on the documentation page

https://gist.github.com/osleg/b715082fad240f386f4f
Here is complete code I'm using,
the /get_gif path returning json with {'success': true, 'file': 'filename.gif'}
on openModal({dismissible: true);
http://storage4.static.itmages.ru/i/15/0324/h_1427166001_1357066_df8b8c1d47.png
On closeModal(); this is what happening
http://storage1.static.itmages.ru/i/15/0324/h_1427166018_8476242_0ea445cb17.png

Not a bug, my mistake wasn't passing modal ID to function on setTimeout()


Do not enable default-tls unconditionally

This reverts 4be1d1eb9fba62ddd6cc7cf53058b6bce3d66c7c and make it more convenient to build taplo-common without explicitly providing a feature.
Fixes #553

Package versions should be updated at the same time? Or would you work on another PR for releasing?

Package versions should be updated at the same time? Or would you work on another PR for releasing?

If I can avoid dealing with the release process I would prefer. I don't have too much time to invest. And actually before releasing it would probably be nice to update the Cargo.lock file to stop using yanked versions.
warning: package `ahash v0.7.6` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `ahash v0.8.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `crossbeam-channel v0.5.6` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked


flutter_test timeout logic - addTime - positive is flaky

This has been failing on and off since at least https://github.com/flutter/engine/pull/27787 on 2021-07-29.
#44     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:0:0)
#49     Invoker._onRun.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:386:9)
#50     Invoker._guardIfGuarded (package:test_api/src/backend/invoker.dart:429:15)
#51     Invoker._onRun.<anonymous closure> (package:test_api/src/backend/invoker.dart:385:7)
#58     Invoker._onRun (package:test_api/src/backend/invoker.dart:384:11)
#59     LiveTestController.run (package:test_api/src/backend/live_test_controller.dart:153:11)
#60     RemoteListener._runLiveTest.<anonymous closure> (package:test_api/src/backend/remote_listener.dart:257:16)
#65     RemoteListener._runLiveTest (package:test_api/src/backend/remote_listener.dart:256:5)
#66     RemoteListener._serializeTest.<anonymous closure> (package:test_api/src/backend/remote_listener.dart:209:7)
#84     _GuaranteeSink.add (package:stream_channel/src/guarantee_channel.dart:125:12)
#85     new _MultiChannel.<anonymous closure> (package:stream_channel/src/multi_channel.dart:159:31)
#89     CastStreamSubscription._onData (dart:_internal/async_cast.dart:85:11)
#123    new _WebSocketImpl._fromSocket.<anonymous closure> (dart:_http/websocket_impl.dart:1150:21)
#131    _WebSocketProtocolTransformer._messageFrameEnd (dart:_http/websocket_impl.dart:338:23)
#132    _WebSocketProtocolTransformer.add (dart:_http/websocket_impl.dart:232:46)
#142    _Socket._onData (dart:io-patch/socket_patch.dart:2166:41)
#151    new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1702:33)
#152    _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1213:14)
(elided 125 frames from class _RawReceivePortImpl, class _Timer, dart:async, dart:async-patch, and package:stack_trace)

The test description was:
  flutter_test timeout logic - addTime - positive
════════════════════════════════════════════════════════════════════════════════════════════════════

00:06 +0 -1: flutter_test timeout logic - addTime - positive [E]
  Test failed. See exception logs above.
  The test description was: flutter_test timeout logic - addTime - positive

00:06 +0 -1: Some tests failed.

Looking at commits since 2021-06-21, I see:

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4736/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4735/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4722/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4698/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4650/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4373/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Web Framework tests/4371/overview

Previous issue: https://github.com/flutter/flutter/issues/18507

This is a framework test thats been flaky in our presubmits. @goderbauer I am not sure if we have seen this test in CI in the framwork. cc @Hixie as the original test author.

Do we have complete logs anywhere? What's the actual exception? (The logs above seem truncated.)

Ah here we go:
Back to build
Raw log | Switch to full mode | Login
▌23:12:48▐ STARTING ANALYSIS
════════════════════════════════════════════════════════════════════════════════
Running smoketests...
▌23:12:48▐ RUNNING: cd .; bin/cache/artifacts/engine/linux-x64/flutter_tester --help
▌23:12:48▐ ELAPSED TIME: 0.086s for bin/cache/artifacts/engine/linux-x64/flutter_tester --help in .
▌23:12:48▐ RUNNING: cd dev/automated_tests; ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/pass_test.dart
▌23:13:03▐ ELAPSED TIME: 15.288s for ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/pass_test.dart in dev/automated_tests
▌23:13:03▐ RUNNING: cd dev/automated_tests; ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/fail_test.dart
▌23:13:07▐ ELAPSED TIME: 3.689s for ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/fail_test.dart in dev/automated_tests
▌23:13:07▐ RUNNING: cd dev/automated_tests; ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/timeout_pass_test.dart
Shuffling test order with --test-randomize-ordering-seed=20210824

00:00 +0: loading /b/s/w/ir/x/w/flutter/dev/automated_tests/test_smoke_test/timeout_pass_test.dart
00:01 +0: loading /b/s/w/ir/x/w/flutter/dev/automated_tests/test_smoke_test/timeout_pass_test.dart
00:02 +0: loading /b/s/w/ir/x/w/flutter/dev/automated_tests/test_smoke_test/timeout_pass_test.dart
00:02 +0: flutter_test timeout logic - addTime - positive
00:03 +0: flutter_test timeout logic - addTime - positive
00:04 +0: flutter_test timeout logic - addTime - positive
00:05 +0: flutter_test timeout logic - addTime - positive
00:06 +0: flutter_test timeout logic - addTime - positive
00:06 +0: flutter_test timeout logic - addTime - positive
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TimeoutException was thrown running a test:
TimeoutException after 0:00:04.000000: The test exceeded the timeout. It may have hung.
Consider using "tester.binding.addTime" to increase the timeout before expensive operations.

When the exception was thrown, this was the stack:
#2      AutomatedTestWidgetsFlutterBinding._checkTimeout (package:flutter_test/src/binding.dart:1176:26)
#22     AutomatedTestWidgetsFlutterBinding.runTest (package:flutter_test/src/binding.dart:1215:29)
#23     testWidgets.<anonymous closure> (package:flutter_test/src/widget_tester.dart:169:24)
#24     Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:199:19)
#27     Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:0:0)
#32     Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:197:13)
#33     Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:180:48)
#34     Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:257:15)
#35     Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:254:14)
#40     Invoker._waitForOutstandingCallbacks (package:test_api/src/backend/invoker.dart:254:5)
#41     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:397:17)
#44     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:0:0)
#49     Invoker._onRun.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:386:9)
#50     Invoker._guardIfGuarded (package:test_api/src/backend/invoker.dart:429:15)
#51     Invoker._onRun.<anonymous closure> (package:test_api/src/backend/invoker.dart:385:7)
#58     Invoker._onRun (package:test_api/src/backend/invoker.dart:384:11)
#59     LiveTestController.run (package:test_api/src/backend/live_test_controller.dart:153:11)
#60     RemoteListener._runLiveTest.<anonymous closure> (package:test_api/src/backend/remote_listener.dart:257:16)
#65     RemoteListener._runLiveTest (package:test_api/src/backend/remote_listener.dart:256:5)
#66     RemoteListener._serializeTest.<anonymous closure> (package:test_api/src/backend/remote_listener.dart:209:7)
#84     _GuaranteeSink.add (package:stream_channel/src/guarantee_channel.dart:125:12)
#85     new _MultiChannel.<anonymous closure> (package:stream_channel/src/multi_channel.dart:159:31)
#89     CastStreamSubscription._onData (dart:_internal/async_cast.dart:85:11)
#123    new _WebSocketImpl._fromSocket.<anonymous closure> (dart:_http/websocket_impl.dart:1150:21)
#131    _WebSocketProtocolTransformer._messageFrameEnd (dart:_http/websocket_impl.dart:338:23)
#132    _WebSocketProtocolTransformer.add (dart:_http/websocket_impl.dart:232:46)
#142    _Socket._onData (dart:io-patch/socket_patch.dart:2166:41)
#151    new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1702:33)
#152    _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1213:14)
(elided 125 frames from class _RawReceivePortImpl, class _Timer, dart:async, dart:async-patch, and package:stack_trace)

The test description was:
  flutter_test timeout logic - addTime - positive
════════════════════════════════════════════════════════════════════════════════════════════════════

00:06 +0 -1: flutter_test timeout logic - addTime - positive [E]
  Test failed. See exception logs above.
  The test description was: flutter_test timeout logic - addTime - positive

00:06 +0 -1: Some tests failed.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ERROR: Last command exited with 1 (expected: zero).
Command: ../../bin/flutter test --test-randomize-ordering-seed=20210824 --local-engine /b/s/w/ir/x/w/recipe_cleanup/builder/src/out/host_debug_unopt test_smoke_test/timeout_pass_test.dart
Relative working directory: dev/automated_tests
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This is LogDog
Rendering took 0.14s

Looks like for some reason this no-op test takes six seconds (!!!) to run. The fix is probably just to change the additionalTime on line 11 of timeout_pass_test.dart to 20000 milliseconds instead of 2000.
We can also just remove this test entirely, since we don't actually use the initialTimeout feature in practice. In fact maybe we should just remove the whole addTime logic entirely, since we don't use it. IIRC it predates our policy of just not having timeouts.

Tree is red today because of this. Bumping priority of this issue. The AI per Ian is that the test must go.

This made the tree red again just now. There is another job running and this issue will be fixed pending the linked PR.

PR is ready to go modulo an updated review of the test.dart changes (which were made after the first review to handle flakiness that the fix would otherwise have introduced).


Kudu sync fails because of Windows file path length issue

Kudu sync on our production azure environment fails when syncing the different node module dependencies because of the Windows file path length (255 chars) limit issue. Whats weird this happens only on the prod azure environment and does not on the dev and test instances.  @shanselman - we had a conversation on Twitter about this.

this could be happening due to the length of the site name, one is probably longer and that puts it over the edge.

The target site here is the wwwroot/. This actually started happening in our dev environment as well. Here is the exact exception that we are seeing when the deploy script executes.
node_modules\http-signature\README.md'
Copying file: 'node_modules\bower\node_modules\bower-registry-client\node_modules\request\node_modules\http-signature\lib\index.js'
Omitting next output lines...
Processed 1456 files...
Processed 2621 files...
Processed 3476 files...
Processed 4499 files...
Processed 5705 files...
Processed 6708 files...
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
An error has occurred during web site deployment.
Kudu Sync to Target failed

What is the deepest path that your site uses? It may be hitting the length limit described in the error message.

249 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padleft/node_modules/lodash._createpad/node_modules/lodash.repeat/package.json
249 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/LICENSE.txt
250 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/package.json
251 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padleft/node_modules/lodash._createpad/node_modules/lodash.repeat/LICENSE.txt
252 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padleft/node_modules/lodash._createpad/node_modules/lodash.repeat/package.json
249 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padleft/node_modules/lodash._createpad/node_modules/lodash.repeat/README.md
249 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/index.js
252 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/LICENSE.txt
253 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/package.json
250 ./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/README.md
./node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-profiler/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/node_modules/lodash.padright/node_modules/lodash._createpad/node_modules/lodash.repeat/package.json

Given this, it's clearly exceeding the limit, as this length doesn't include the base directory. One thing you can try is npm dedupe, and potentially getting rid of deep things that aren't needed.
Closing here since this is an OS limitation, and not anything specific to Kudu.

We did try dedupe but that did not fix the issue. So to get around the problem since our site is relatively small, currently we are writing directly to the wwwroot instead of writing to repository location in azure and then kudu syncing the files to wwwroot (which is where we ran into this issue).

I'm surprised that this works, as the path limit is the same. Well, 'wwwroot' has 3 characters fewer than 'repository', so if you're right at the edge, that could explain it.


Investigating the 30min when there were no blocks

There were no blocks between June 2 00:45 01:15 UTC i.e., 10 missed slots. Looking at the history, this has been the biggest gap between two blocks so far:

slots between two blocks
count

10
1

9
2

8
3

7
18

6
41

5
161

4
485

3
1662

2
6144

From the logs of a few blockproducers who volunteered, i did not see any block production failure. In one of the logs I saw that there were two catchup failures around the same time when there were no blocks.
2021-06-02T00:35:07Z {"timestamp":"2021-06-02 00:35:06.522021Z","level":"Fatal","source":{"module":"Init__Coda_run","location":"File \"src/app/cli/src/init/coda_run.ml\", line 603, characters 2-26"},"message":"Unhandled top-level exception: $exn\nGenerating crash report","metadata":{"exn":{"commit_id":"a42bdeef6b0c15ee34616e4df76c882b0c5c7c2a","sexp":["monitor.ml.Error",["Pipe_lib.Strict_pipe.Overflow(\"primary transitions\")"],["Raised at file \"src/lib/pipe_lib/strict_pipe.ml\", line 258, characters 34-79","Called from file \"src/pipe.ml\", line 873, characters 10-13","Called from file \"src/job_queue.ml\" (inlined), line 131, characters 2-5","Called from file \"src/job_queue.ml\", line 171, characters 6-47","Caught by monitor coda"]],"backtrace":["Raised at file \"src/lib/pipe_lib/strict_pipe.ml\", line 258, characters 34-79","Called from file \"src/pipe.ml\", line 873, characters 10-13","Called from file \"src/job_queue.ml\" (inlined), line 131, characters 2-5","Called from file \"src/job_queue.ml\", line 171, characters 6-47"]},"host":"<IP_ADDRESS>","peer_id":"12D3KooWDnnZTV2Su5Sx7g6pDHYh8QNKbSzZhqsSLrfTMfLqWvMD","pid":13,"port":8812}} Another instance of this was reported here  #8738
This exception occurs when the primary transactions pipe for blocks from the network, which has a fixed capacity but is determined by network traffic at the time of starting up, fills up. It could be due to multiple blocks in a short period of time and some delay in processing those blocks that causes the pipe to overflow. It could be that multiple nodes crashed with around the same time- ones that had small capacity?
if a node restarts and does not bootstrap(start from persisted state), the pipe capacity is smaller than that of the nodes that bootstrap from a clean slate. Explains why not all the nodes crash at the same time when there is a lot of block traffic.

Based on this graph between slots missed and transactions included in a block (both fee transfers and user commands), it is not clear to me if gossip traffic could have been a contributor to this. There are quite a few missed slots (>= 5 consecutive) even with lesser traffic. And in our seed logs or a few community logs, there were no rejected blocks either (which could indicate delay due to gossip latency?)

We no longer have the logs for this. Closing.


performance_test: 2.3.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository performance_test to 2.3.0-1:

upstream repository: https://gitlab.com/ApexAI/performance_test.git
release repository: https://github.com/ros2-gbp/performance_test-release.git
distro file: humble/distribution.yaml
bloom version: 0.12.0
previous version for package: 1.2.1-1

I am not very experienced with bloom. Should the performance_test/doc/version entry also be updated to 2.3.0-1? I don't really understand why it is still 1.2.1-1.

I am not very experienced with bloom. Should the performance_test/doc/version entry also be updated to 2.3.0-1? I don't really understand why it is still 1.2.1-1.

In almost all circumstances, the doc branch should match the source branch (there are cases where it makes sense for them to be different, but they are fairly uncommon).  So I'd update it to be master in this case.

Thanks @clalancette . I changed it to master, and I'll do the same on the other two MRs.

You might not have access, since you're not a maintainer. I reran jobs.

It looks like we're still getting CI errors:

Thanks @audrow . Why would we get that CI error on this MR only, and not the other two? They're all pointing to the same tag, and package.xml does exist:
https://gitlab.com/ApexAI/performance_test/-/blob/master/performance_test/package.xml?ref_type=heads

I am not sure 🤔

@audrow Let's try to isolate it, I suppose. I'll revert the rolling commit, and open a new MR for it. Maybe the humble will pass and rolling will fail, or maybe they will pass independently :shrug:

@audrow the new MR has the same problem, but at least this MR is now green.


Correction for raw affiliation Univ Rennes, Inria, CNRS, IRISA, INSERM, Empenn U1228 ERL, F-35042, Rennes, France; CHU Rennes, Department of Radiology, F-35033, Rennes, France.

Correction needed for raw affiliation Univ Rennes, Inria, CNRS, IRISA, INSERM, Empenn U1228 ERL, F-35042, Rennes, France; CHU Rennes, Department of Radiology, F-35033, Rennes, France.
raw_affiliation_name: Univ Rennes, Inria, CNRS, IRISA, INSERM, Empenn U1228 ERL, F-35042, Rennes, France; CHU Rennes, Department of Radiology, F-35033, Rennes, France.
new_rors: 015m7wh34;00myn0z94;05qec5a53;02hp31992
previous_rors: 015m7wh34;00myn0z94;05qec5a53
works_examples: W4309629727
contact: ec4a689625379158364cdc8df919624a:d5ad50eecb074fb231dd1b25d4d1d906 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Any reason for us to be able to choose host/port?

const (
	host = "data.logentries.com"
	port = 443
)

I glanced over the documentation around the different ports, etc., and this endpoint with port of 443 seemed to be the way to go if you wanted to use TLS.
I can't imagine why anyone would want to send in an insecure fashion (except for speed maybe?), but maybe there are other benefits that I'm not seeing right now.
If you want this changed... to be added as params for the New function call, for example... just reply and let me know or submit a pull request and I'll be happy to check it out.

actually, i wrote my own logentries hook, and we connect as udp and on an unsecure channel, because we use these logs only for metrics and there is no reasons at all those logs should  slow our apps.
so speed over security can be good sometimes i guess

Ah, great point! Seems like an excellent example of something that wouldn't need any security. I'll look into adding it in the coming week.
Thanks for your input :)

Sorry, I a delay on getting to this; working through a write issue that seems related to timeouts: #2


Automatic Proxy Configuration produces error

Tried creating a profile where the only settings are to enable automatic proxy configuration and receive the error:
Invalid value for key: ProxyAutoConfigEnable in payload domain: com.apple.SystemConfiguration of type:appleManifest

Value: https://example.com/pacfile.pac

Verify you have entered a correct value.

It looks like the Automatic Proxy Configuration URL setting is using the same key as Enable Automatic Proxy Configuration i.e. ProxyAutoConfigEnable
Not sure what the correct key is, ProxyAutoConfigURLString?

Thank you, yes you are correct. That key was duplicated, and incorrect. I've fixed this and uploaded it to the manifest repo. If you have beta 3 you can go into Preferences > Payloads and click on "Update Now", then "Update" and you should get the new manifest and be able to build your profile correctly.


[BIOMAGE-938] Improve UI responsiveness by eliminating unnecessary renders

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-938
Link to staging deployment URL
https://ui-marcellp-ui359.scp-staging.biomage.net/
Links to any Pull Requests related to this
N/A
Anything else the reviewers should know about the changes here
In addition, some components relied on experimentId in their useEffect hooks. As experimentId is now a prop that is automatically assigned to all pages it is unnecessary and causes two calls instead of one (one on initial render, one when experimentId changes, i.e. immediately after). This is now eliminated in cases where experimentId was the only dependency to a useEffect hook.
Changes
Code changes
Deleted the carousel component as we did not use it for anything and it was terrible for both layout and performance. UI feels much faster now.
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[x] Unit tests written
[x] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[x] Relevant Github READMEs updated
[x] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[x] Photo of a cute animal attached to this PR

Can we have this changes as a hotfix? It would greatly improve current user experience

@aerlaut yes we can. Let me set it up as such as well.


Update applications.yaml

Adapt Opensearch internal URL

That needs to be changed here https://github.com/shopware/paas-meta/blob/main/platformsh-env.php#L328


Robotium RC: Add method to get all views if passed view id maps multiple views

From<EMAIL_ADDRESS>on August 16, 2013 22:54:14
What steps will reproduce the problem? 1. Invoke getView method only return the first match view. What is the expected output? What do you see instead? Expected: add one method to get all views if passed view id maps multiple views.
Original issue: http://code.google.com/p/robotium/issues/detail?id=499

From<EMAIL_ADDRESS>on August 16, 2013 23:52:01
The scenario is,
There's multiple imageView belong to the same id. What should i do to click the specific one?
BTW, if there anyway to get the attributes of component, like regular Robotium can do ?

From<EMAIL_ADDRESS>on August 21, 2013 12:19:44
Normally, we try to match the Robotium API wherever we can.  I see there is a matching proposed function in Robotium:
getView(id, index); http://robotium.googlecode.com/svn/doc/com/jayway/android/robotium/solo/Solo.html#getView(int, int) But that we do not have the matching API in RemoteControl . http://safsdev.sourceforge.net/doc/com/jayway/android/robotium/remotecontrol/solo/Solo.html So this is something we do need to rectify.
Concerning getting the attributes of objects in RemoteControl like Robotium:
Of course, we do not have direct objects on the remote control side.  And while mirroring the Robotium API, we don't have or provide too many additional APIs beyond what would be available to Robotium users in the default RobotiumTestRunner.
However, if you switch to using the SAFSTestRunner instead of the RobotiumTestRunner you can then you have a good amount of additional functionality that goes beyond normal RobotiumRC.  These are provided by two key API classes:
SAFS Driver Commands
SAFS Engine Commands  (lots of GET stuff in here!) http://safsdev.sourceforge.net/doc/org/safs/android/remotecontrol/SAFSDriverCommands.html http://safsdev.sourceforge.net/doc/org/safs/android/remotecontrol/SAFSEngineCommands.html In order to use the SAFSTestRunner, if you have not already done so, you should install the Overlay made available on 2013.08.09 at: http://sourceforge.net/projects/safsdev/files/Robotium RemoteControl/2013.07.12/ Keep in mind, this Overlay can only be applied on top of the 2013.07.12 Release of Robotium RemoteControl .
Carl Nagle
SAS Research & Development
Planning, Operations and Strategy
General Applications and Tools
<EMAIL_ADDRESS>Status: Accepted
Owner<EMAIL_ADDRESS>

From<EMAIL_ADDRESS>on August 22, 2013 08:52:41
The reason to mention this is, i feel using RobitumRC very depends on provided methods, it's hard to finish some jobs as flexible as regular Robotium.

From<EMAIL_ADDRESS>on September 04, 2013 08:32:48
I have added the requested support for getView(id, index) and it will be available in the next release. http://safsdev.sourceforge.net/doc/com/jayway/android/robotium/remotecontrol/solo/Solo.html#getView(int, int) The next release of RobotiumRC will be either later this week, or (possibly) next week alongside an anticipated tentative release of core Robotium.
Carl Nagle
SAS Research & Development
Planning, Operations and Strategy
General Applications and Tools
<EMAIL_ADDRESS>Status: Fixed


⚠ Secret Website 3 has degraded performance

In 4ca31b1, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2266 ms

Resolved: Secret Website 3 performance has improved in 07edffd.


fix(iroh-net): return Poll::Pending when we have no relay URL or direct addresses in poll_send

Description
closes #2226
Breaking Changes

Notes & open questions

Change checklist

[ ] Self-review.
[ ] Documentation updates if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

We won't ever call a waker in that case, so I'm wondering if not maybe Poll::Ready(Ok(0)) makes more sense?
Would have to check the quinn source though to see how this behaves for each variant I guess.

We won't ever call a waker in that case, so I'm wondering if not maybe Poll::Ready(Ok(0)) makes more sense?

Thank you yes. Here is what I'm confused by. If we never end up sending those messages and keep returning Ok(0), aren't we just going to keep attempting to send those same messages over and over again & never make any progress? Potentially blocking other messages that are trying to be send on other connections? Is the answer here to just drop the messages for that nodeID on the floor & report that we sent them?
My more aggressive thought would be that we should keep the error, since ending up in a state where we have no address for the given node ID should never happen. And when it does happen, people will file bug reports because an error occurred 😂

Edit: alternatively, if discovery moved into the MagicSock, we could actually store the waker here and wake once we discovered a relay or direct addr. That's more future thoughts though, let's first fix the current "killing the endpoint" situation.

I've actually been converted to "We shouldn't move discovery into MagicSock". My reasoning is two-fold:

the separation of concerns is actually a nice boundary to help reason about what is "discovery" and what is "connectivity". It also helps with communicating to the user. If discovery fails or no addresses exist, we can error before we attempt to connect.
If two node have previously had a connection and one node changes its addresses, we already have healing mechanisms in place to communicate those changes using Disco messages and the relay. Also, since we don't prune addresses while the endpoint is running, we should never get into a case where we previously had a connection to a node and then suddenly have no addresses for that node.

I wrote more thoughts about this here: https://www.notion.so/number-zero/Connections-Discovery-and-Migration-9c34bad7dba24f80b20275ac78bdf202

My more aggressive thought would be that we should keep the error since ending up in a state where we have no address for the given node ID should never happen. And when it does happen, people will file bug reports because an error occurred 😂

We can't unfortunately because this error kills the quinn endpoint, not only the connection.
I will check the quinn source what it does if we return Ready(Ok(0)). If that leads to retrying in a loop, then we should likely report the data as sent even though it isn't - this will then make the connection time out after 10s.

Also, since we don't prune addresses while the endpoint is running

We do prune unused addresses while running.

I think I'm going down the "pretend we sent it, but it got lost somewhere in the internet tubes".  With pending you indeed never install a waker.
IIUC correctly Quinn quinn has a per-endpoint send buffer (per connection in 0.11), so returning pending will block everything in that buffer, including other connections.

We can't unfortunately because this error kills the quinn endpoint, not only the connection.

I know 😈

I will check the quinn source what it does if we return Ready(Ok(0)). If that leads to retrying in a loop, then we should likely report the data as sent even though it isn't - this will then make the connection time out after 10s.

In all seriousness though—it does retry in a loop, so then reporting the data as sent is the way to go. TY!!!

We do prune unused addresses while running.

Ahh, let me rephrase. We never prune to 0, we only prune if there are like 30 entries.


[tool_crash] FileSystemException: Exists failed, OS Error: The device is not ready., errno = 21

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Exists failed, OS Error: The device is not ready.
, errno = 21
#0      _Directory.existsSync (dart:io/directory_impl.dart:94:7)
#1      ForwardingFileSystemEntity.existsSync (package:file/src/forwarding/forwarding_file_system_entity.dart:43:33)
#2      ErrorHandlingDirectory.existsSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:497:22)
#3      _runSync (package:flutter_tools/src/base/error_handling_io.dart:597:14)
#4      ErrorHandlingDirectory.existsSync (package:flutter_tools/src/base/error_handling_io.dart:496:12)
#5      PubDependencies.isUpToDate (package:flutter_tools/src/flutter_cache.dart:102:57)
<asynchronous suspension>
#6      Cache.updateAll (package:flutter_tools/src/cache.dart:591:11)
<asynchronous suspension>
#7      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1243:7)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1140:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:288:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:236:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>

[✓] Flutter (Channel stable, 2.8.1, on Microsoft Windows [version 10.0.19045.3693], locale fr-FR)
    • Flutter version 2.8.1 at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (1 year, 11 months ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\src\flutter\bin\cache\dart-sdk
    • Platform android-UpsideDownCakePrivacySandbox, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 2021.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[✓] VS Code, 64-bit edition (version 1.84.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.76.0

[✓] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 119.0.6045.161
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 119.0.2151.72

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+16
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 77d935af4db863f6abd0b9c31c7e6df2a13de57b
Plugins
connectivity-3.0.6
connectivity_for_web-0.4.0+1
connectivity_macos-0.2.1+2
fluttertoast-8.0.9
path_provider-2.0.11
path_provider_android-2.0.20
path_provider_ios-2.0.11
path_provider_linux-2.1.7
path_provider_macos-2.0.6
path_provider_windows-2.0.7
shared_preferences-2.0.15
shared_preferences_android-2.0.12
shared_preferences_ios-2.1.1
shared_preferences_linux-2.1.1
shared_preferences_macos-2.0.4
shared_preferences_web-2.0.4
shared_preferences_windows-2.1.1
url_launcher-6.1.5
url_launcher_android-6.0.17
url_launcher_ios-6.0.17
url_launcher_linux-3.0.1
url_launcher_macos-3.0.1
url_launcher_web-2.0.6
url_launcher_windows-3.0.1
webview_flutter-3.0.4
webview_flutter_android-2.8.14
webview_flutter_wkwebview-2.7.5

Closing this as a duplicate of https://github.com/flutter/flutter/issues/81146


Stylet.Start doesn't uninstall itself?

Tested with 1.1.20...

VS2015 says:
Uninstall-Package : Package 'Stylet.Start' to be uninstalled could not be found in project 'Sandbox'At
C:\Documents\projects\Sandbox\packages\Stylet.Start.1.1.20\tools\install.ps1:312 char:1
+ Uninstall-Package Stylet.Start
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Uninstall-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.UninstallPackage
   Command

Time Elapsed: 00:00:00.0107569
Successfully installed 'Stylet.Start 1.1.20' to StyletStartSandbox
Executing nuget actions took 481.51 ms
========== Finished ==========
Time Elapsed: 00:00:04.1394740

VS2017 deadlocks (there's a NuGet issue - I've lost it - which fixes it, but I'm not sure whether the fix was released).


[peft] Update test_reward_trainer.py to fix tests

Since we are requiring peft >= 0.4.0
This check fails when peft_version = "0.10.0"

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Build TFLite with Flex Ops without Bazel

Tensorflow Version: 2.4.0-dev20200712
OS: Ubuntu 18.10
(tensorflow/tensorflow docker)
Hello
Followed these instructions (C++ section) in the past to build a shared libtensorflowlite.so library
https://www.tensorflow.org/lite/guide/ops_select
Add the TensorFlow ops delegate library dependency to the build dependencies: tensorflow/lite/delegates/flex:delegate.

Problem is now I'm running into compatibility issues when I upload to the target device..
Few questions:
(1) How can I build a static library using the bazel pipeline? I used the --config monolithic flag but upon linking it still requires a newer glibc than my system supports
bazel build --config=elinux_aarch64 --cpu=aarch64 --config=monolithic --cxxopt=--std=c++14 --define=with_select_tf_ops=true -c opt //tensorflow/lite:libtensorflowlite.so
(2) How can I add the same flex op dependency to the makefile in lite/tools in order to build the lib without Bazel?

What TF version you are using?

What TF version you are using?

2.4.0-dev20200712
Adding to my original post

@thaink - would you happen to be able to support with my question (2) above?

(1) We don't provide a rule to build static library via Bazel now. Doesn't shared library work for you? Could you share why?
(2) We don't have this path either.
If you want to build libtensorflowlite.so with Flex support, please apply the following patch.
https://github.com/terryheo/tensorflow/commit/cdb8f3045669ea7adcd7ac4b115b01f13f7dad6e

Hi @terryheo -
The problem is that the aarch64 toolchain that is provided uses a glibc version that is incompatible with my target. I was hoping to circumvent this through building the library statically . The shared library works for running on the host.
Do you have any suggestions? I tried to configure a new toolchain but ran into issues mid-compilation that wasn't so obvious for me to debug.
Thanks for the patch

I see.
I'm wondering which target OS platform you're using. (also glibc version of the target) If it's popular, I might need to consider supporting it.
You can try new toolchain by referring https://github.com/tensorflow/tensorflow/commit/4961f18733ca3967198393abf419e14476b4a85c#diff-f37bff3c4001d49511871eb70980dc27 change. But right, it's not trivial to do it.

It's an aarch64 linux target with glibc of 2.26.
Is it not trivial to add the flex dependency to the Makefiles as it is for a Bazel-based build?

I see.
To build Flex delegate, it needs to build TF kernels. So until we have a way to build TF framework with Makefile, it's very difficult to build Flex delegate with Makefile.

@aselva-eb,
As commented by the developer, please try to build TF Kernels and go for the Flex delegate.
If you're using Bazel or CMake to build TensorFlow Lite interpreter, you can enable Flex delegate by linking a TensorFlow Lite Flex delegate shared library. You can build it with Bazel as the following command.
bazel build -c opt --config=monolithic tensorflow/lite/delegates/flex:tensorflowlite_flex
Also please take a look at this official document link for the reference. Thank you!


error while packing images over 1024 file in windows

Traceback (most recent call last):
  File "E:/Code/PythonCode/UnpackGui/main.py", line 46, in <module>
  File "E:/Code/PythonCode/UnpackGui/main.py", line 41, in repackpng
  File "C:\Python27\lib\site-packages\PyTexturePacker\MaxRectsBinPacker\MaxRectsBinPacker.py", line 96, in pack
  File "C:\Python27\lib\site-packages\PyTexturePacker\Utils.py", line 47, in load_images_from_dir
  File "C:\Python27\lib\site-packages\PyTexturePacker\Utils.py", line 25, in load_images_from_paths
  File "C:\Python27\lib\site-packages\PyTexturePacker\ImageRect.py", line 33, in __init__
  File "C:\Python27\lib\site-packages\PyTexturePacker\ImageRect.py", line 52, in load_image
  File "C:\Python27\lib\site-packages\PIL\Image.py", line 2312, in open
IOError: [Errno 24] Too many open files: 'newgui/distract.png'

The bug is fixed, but I forgot to subimit the new release to pypi. Now the release version on pypi is updated.
Use

pip install --upgrade PyTexturePacker
to updrade the package.

BTW, thanks 4 your star.


Logger is not working as expected

Hi everyone,
Right now, I'm implementing outlier detection for tabular data locally (refactor_development). However, I have some troubles with the logger as I only get warnings or worse printed.
Right after the logger is created, I execute following code
print(self._logger.logger)
self._logger.debug("test")
self._logger.info("test")
self._logger.warning("test")
self._logger.error("test")
self._logger.critical("test")

resulting in
<Logger Client-AutoPyTorch:3fda52af-7b68-11eb-917d-88d7f6d56325:1 (DEBUG)>
[WARNING] [2021-03-02 16:02:06,587:Client-AutoPyTorch:3fda52af-7b68-11eb-917d-88d7f6d56325:1] test
[ERROR] [2021-03-02 16:02:06,587:Client-AutoPyTorch:3fda52af-7b68-11eb-917d-88d7f6d56325:1] test
[CRITICAL] [2021-03-02 16:02:06,587:Client-AutoPyTorch:3fda52af-7b68-11eb-917d-88d7f6d56325:1] test

Would appreciate if you have some ideas what's wrong here.

Setting logging.StreamHandler in logging.yaml to DEBUG fixed it.