Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates

Build/Submit details page URL
https://expo.dev/accounts/pixelkoduje/projects/novenna-pompejanska-app/builds/af225074-98e5-4b59-b7bc-a34c234874d6
Summary
After adding expo-updates the project won't build. Android and iOS. The strangest thing is that there is not even an error. He just stands at that line, then stands until the 45 minute build is complete. (before adding, it took about 9 minutes to build, so 100% it shouldn't take more than 45 minutes after adding expo-updates)
The weirdest thing is that it only crashes when building a production app. At the time of building, the "development client" passes without a problem.
More specifically, it crashes without error on this line:
Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates
I am uploading the iOS build logs of the production app.
... To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

› Compiling expo-keep-awake Pods/ExpoKeepAwake » ExpoKeepAwake-dummy.m

› Packaging expo-keep-awake Pods/ExpoKeepAwake » libExpoKeepAwake.a

› Executing expo-keep-awake Pods/ExpoKeepAwake » Copy generated compatibility header

› Compiling expo Pods/Expo » Expo-dummy.m

› Compiling expo Pods/Expo » EXAppDefinesLoader.m

› Compiling expo-linear-gradient Pods/ExpoLinearGradient » ExpoLinearGradient-dummy.m

› Packaging expo-linear-gradient Pods/ExpoLinearGradient » libExpoLinearGradient.a

› Executing expo-linear-gradient Pods/ExpoLinearGradient » Copy generated compatibility header

› Compiling expo-head Pods/ExpoHead » ExpoHead-dummy.m

› Packaging expo-head Pods/ExpoHead » libExpoHead.a

› Executing expo-head Pods/ExpoHead » Copy generated compatibility header

› Compiling expo-splash-screen Pods/EXSplashScreen » EXSplashScreenViewNativeProvider.m

› Packaging expo Pods/Expo » libExpo.a

› Compiling expo-splash-screen Pods/EXSplashScreen » EXSplashScreenViewController.m

› Compiling expo-splash-screen Pods/EXSplashScreen » EXSplashScreenService.m

› Compiling expo-splash-screen Pods/EXSplashScreen » EXSplashScreenModule.m

› Compiling expo-splash-screen Pods/EXSplashScreen » EXSplashScreen-dummy.m

› Compiling expo-notifications Pods/EXNotifications » NSDictionary+EXNotificationsVerifyingClass.m

› Compiling expo-notifications Pods/EXNotifications » EXUserFacingNotificationsPermissionsRequester.m

› Compiling expo-notifications Pods/EXNotifications » EXSingleNotificationHandlerTask.m

› Compiling expo-notifications Pods/EXNotifications » EXServerRegistrationModule.m

› Compiling expo-notifications Pods/EXNotifications » EXPushTokenModule.m

› Compiling expo-notifications Pods/EXNotifications » EXPushTokenManager.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationsEmitter.m

› Compiling expo-notifications Pods/EXNotifications » EXNotifications-dummy.m

› Packaging expo-splash-screen Pods/EXSplashScreen » libEXSplashScreen.a

› Compiling expo-notifications Pods/EXNotifications » EXNotificationSchedulerModule.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationPresentationModule.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationPermissionsModule.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationCenterDelegate.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationCategoriesModule.m

› Compiling expo-notifications Pods/EXNotifications » EXNotificationBuilder.m

› Compiling expo-notifications Pods/EXNotifications » EXLegacyRemoteNotificationPermissionRequester.m

› Compiling expo-notifications Pods/EXNotifications » EXBadgeModule.m

› Compiling expo-notifications Pods/EXNotifications » EXBackgroundRemoteNotificationConsumer.m

› Compiling expo-notifications Pods/EXNotifications » EXBackgroundNotificationTasksModule.m

› Packaging expo-notifications Pods/EXNotifications » libEXNotifications.a

› Compiling expo-font Pods/EXFont » EXFontScalersManager.m

› Compiling expo-font Pods/EXFont » EXFontScaler.m

› Compiling expo-font Pods/EXFont » EXFontManager.m

› Compiling expo-font Pods/EXFont » EXFontLoaderProcessor.m

› Compiling expo-font Pods/EXFont » EXFontLoader.m

› Compiling expo-font Pods/EXFont » EXFont.m

› Compiling expo-font Pods/EXFont » EXFont-dummy.m

› Packaging expo-font Pods/EXFont » libEXFont.a

› Compiling expo-file-system Pods/EXFileSystem » EXTaskHandlersManager.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionUploadTaskDelegate.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionTaskDispatcher.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionTaskDelegate.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionResumableDownloadTaskDelegate.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionHandler.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionDownloadTaskDelegate.m

› Compiling expo-file-system Pods/EXFileSystem » EXSessionCancelableUploadTaskDelegate.m

› Compiling expo-file-system Pods/EXFileSystem » EXFileSystemLocalFileHandler.m

› Compiling expo-file-system Pods/EXFileSystem » EXFileSystemAssetLibraryHandler.m

    'requestImageDataForAsset:options:resultHandler:' is deprecated: first deprecated in iOS 13 [-Wdeprecated-declarations]

› Compiling expo-file-system Pods/EXFileSystem » EXFileSystem.m

› Compiling expo-file-system Pods/EXFileSystem » EXFileSystem-dummy.m

› Compiling expo-file-system EXFilePermissionModule.m

› Compiling expo-manifests Pods/EXManifests » EXManifests-dummy.m

› Packaging expo-file-system Pods/EXFileSystem » libEXFileSystem.a

› Executing expo-constants Pods/EXConstants » [CP-User] Generate app.config for prebuilt Constants.manifest

› Packaging expo-manifests Pods/EXManifests » libEXManifests.a

› Executing expo-manifests Pods/EXManifests » Copy generated compatibility header

› Compiling expo-application Pods/EXApplication » EXProvisioningProfile.m

› Compiling expo-application Pods/EXApplication » EXApplication.m

› Compiling expo-application Pods/EXApplication » EXApplication-dummy.m

› Packaging expo-application Pods/EXApplication » libEXApplication.a

› Compiling expo-constants Pods/EXConstants » EXConstantsService.m

› Compiling expo-constants Pods/EXConstants » EXConstantsInstallationIdProvider.m

› Compiling expo-constants Pods/EXConstants » EXConstants-dummy.m

› Packaging expo-constants Pods/EXConstants » libEXConstants.a

› Compiling expo-av Pods/EXAV » EXVideoView.m

› Compiling expo-av Pods/EXAV » EXVideoPlayerViewController.m

› Compiling expo-av Pods/EXAV » EXAudioSessionManager.m

› Compiling expo-av Pods/EXAV » EXAudioSampleCallback.mm

› Compiling expo-av Pods/EXAV » EXAudioRecordingPermissionRequester.m

› Compiling expo-av Pods/EXAV » EXAVPlayerData.m

› Compiling expo-av Pods/EXAV » EXAV.m

› Compiling expo-av Pods/EXAV » EXAV-dummy.m

› Compiling expo-av Pods/EXAV » EXAV+AudioSampleCallback.mm

› Compiling expo-av Pods/EXAV » CallbackWrapper.mm

› Compiling expo-av Pods/EXAV » AudioSampleCallbackWrapper.mm

› Packaging expo-av Pods/EXAV » libEXAV.a

› Executing expo-constants Pods/EXConstants » Copy generated compatibility header

› Executing expo-av Pods/EXAV » Copy generated compatibility header

› Compiling expo-eas-client Pods/EASClient » EASClient-dummy.m

› Packaging expo-eas-client Pods/EASClient » libEASClient.a

› Executing expo-eas-client Pods/EASClient » Copy generated compatibility header

› Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates

For administration, I am sending a link to build:
https://expo.dev/accounts/pixelkoduje/projects/novenna-pompejanska-app/builds/af225074-98e5-4b59-b7bc-a34c234874d6
And a built version for Android (with the same functions) - the production version is also not built for Android.
https://expo.dev/accounts/pixelkoduje/projects/nowenna-pompejanska-app/builds/2409695c-4231-41a6-bf53-134cb785ed4f
Managed or bare?
Managed
Environment
npx expo-doctor
 Check package.json for common issues
✔ Validate global prerequisites versions
✔ Validate Expo Config
✔ Check compatible dependency versions for the installed Expo SDK
✔ Check for incompatible packages
✔ Check for conflicting global packages in project
✖ Verify prebuild support package versions are compatible

Detailed check results:

Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  (for more info, run: npm why @expo/config-plugins)
Advice: Upgrade dependencies that are using the invalid package versions.

One or more checks failed, indicating possible issues with the project.

npx expo-env-info
  expo-env-info 1.0.5 environment info:
    System:
      OS: Windows 10 10.0.19045
    Binaries:
      Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
      Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
      npm: 8.3.0 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
    npmPackages:
      @expo/metro-config: ^0.10.6 => 0.10.6
      @expo/webpack-config: ^18.0.1 => 18.0.1
      expo: ^49.0.0 => 49.0.0
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.72.3 => 0.72.3
      react-native-web: ~0.19.6 => 0.19.6
    Expo Workflow: managed

Error output
No response
Reproducible demo or steps to reproduce from a blank project
null

I got the same problem

@KULTI1995 did you managed to solve it?

Related: https://forums.expo.dev/t/eas-ios-build-hangs-on-generate-app-manifest/69917

I have the same exact issue

1

Guys even i am gettin a very similar error, when i run my expo builds locally :
[RUN_FASTLANE] › Packaging expo-manifests Pods/EXManifests » libEXManifests.a
[RUN_FASTLANE] › Executing expo-constants Pods/EXConstants » [CP-User] Generate app.config for prebuilt Constants.manifest

I've faced almost same issue, I tried many solutions (different version, clean install node_modules, remove .expo | DerivedData etc) but not fixed, at last restarting my PC solved the problem (in my case).
I don't know what was the specific cause but FYI restarting your PC may solve the problem.

any solutions? I have this in expo dev console:
Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates

❌  error: Cannot resolve @babel/runtime/helpers/interopRequireDefault

❌ Metro encountered an error:
Cannot resolve @babel/runtime/helpers/interopRequireDefault
Learn more: https://docs.expo.dev/build-reference/troubleshooting

and more detailed in logs:
/Users/expo/workingdir/build/apps/mobile/.cache/metro"
error: Cannot resolve expo-updates
Error: Cannot resolve expo-updates
Error: Cannot resolve expo-updates
    at /Users/expo/workingdir/build/apps/mobile/node_modules/@nx/expo/plugins/metro-resolver.js:33:15
    at resolveRequest (/Users/expo/workingdir/build/apps/mobile/node_modules/@expo/cli/build/src/start/server/metro/withMetroResolvers.js:97:24)

@bleonaima Hey, did you find any solutions? I have the same as @KULTI1995.

Hey hey! I have the same issue Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates. Tried to update was-cli to the latest version, restarted PC:) nothing worked :(((  eas-cli/7.8.2    "expo": "~49.0.15",  "expo-updates": "~0.18.19". Did you find any solutions?

Upgrading the babel package to "@babel/core": "^7.20.12" resolved the issue for me.

Hi, Please I'm experiencing this issue. I have tried updating my babel/core, no success.

having exactly same issue expo sdk 51

any updates? I also have the same problem › Executing expo-constants Pods/EXConstants » [CP-User] Generate app.config for prebuilt Constants.manifest

any updates? I also have the same problem › Executing expo-constants Pods/EXConstants » [CP-User] Generate app.config for prebuilt Constants.manifest

i've solved it.
Two ways.
1st: empty ~/.bash_profile
2st: cause i'm using zsh.
so, change these:
mv ~/.bash_profile ~/.bash_profile_2
touch ~/.bash_profile

to edit ~/.zshrc, replace ~/.bash_profile with ~/.bash_profile_2
source ~/.bash_profile_2

then, for bash, it will use ~/.bash_profile, ~/.bash_profile is empty file.
for zsh, it can use ~/.bash_profile_2

This is still an issue FYI


Key-Value DB using LevelDB

Getting started to integrate Level DB with the existing code as described in #544

@kautukkundan I suppose this is implemented in #619? Feel free to close if that's the case.


after restart a single storage pod, lead not balanced

after restart a single storage pod, operator do balance leader, but leader still not balanced.

check operator log, may be the action too early，from ready to restart storaged pod to do balance leader,only less than 500ms's interval.

since we know, do balance leader may not archive the aim for once, may be we should do some check and repeat.
Your Environments (required)
operator镜像：reg.vesoft-inc.com/cloud-dev/nebula-operator:snap-1.35
How To Reproduce(required)
Steps to reproduce the behavior:
1. with 3 zones and each zone with 3 storaged;
2. create 2 space;
3. restart one storaged pod `kubectl -n nebula annotate sts nebulav-storaged nebula-graph.io/restart-ordinal="8"`
4. pay attention to operator log and check storaged leader distribution. eg: show hosts.

Expected behavior
after restart , leader keep balanced

补充：当3个zone，每个zone分别只有1个sotraged时，重启了一个storaged后，虽然在两个space中都完成了 balance leader，但最终结果，依旧是不均匀。

相关balance操作的日志：

checked with snap-1.37, still has the problem

discues offline: remind user to do balance data by hand；later do optimize.

@abby-cyber

https://github.com/vesoft-inc/nebula-operator/pull/507


Electron-417 (Reposition active notifications whenever the config is updated)

Description
A few sentences describing the overall goals of the pull request's commits. Describe the problem or feature in addition to a link to the ELECTRON-417
Approach
How does this change address the problem?
Problem with the code:

Notification was being closed whenever the notification configuration is updated

Fix:

Repositioning active notification whenever the config is updated

Spectron test results
Electron-417 — Spectron.pdf
Unit test results
Electron-417 — Unit Tests.pdf
Open Questions if any and Todos

[X] Unit-Tests
[X] Documentation
[X] Automation-Tests
When solved, check the box and explain the answer.

@VikasShashidhar Please review.


[feat]State Language Support

DSL for state machine definition and impl
reference

seata  https://seata.io/zh-cn/docs/user/saga.html#State-language-referance
amazon  https://states-language.net/spec.html

Saga in Seata provide a state machine definition interface for user. It is flexible but very complex, and the complexity make saga not frequently used in Seata.
DTM's saga is far more frequently because of the simplicity of saga, and less work compared to TCC.Saga in DTM also provide advanced feature to handle complex work. So far, Saga can handle all the problem of DTM's user. If you have a well defined real problem, we can have a discuss about the problem and workout a solution together.

A detailed explanation can be found here: https://dtm.pub/practice/saga.html#saga-设计原则


Location Tool: Show Org Incidents

Problem
When creating organization Primary and Secondary response areas, knowing the incidents they have deployed to is really useful.
Solution

List incidents.
Create a checkbox that displays all of the incident location shapes in an alternate color (e.g. red, green, etc.) different from the color the tool uses to create new shapes.

Screen Shot

Awesome. And I saw geofences for the incidents as well. This is great.


Respect container memory limits

Apologies if this isn't the best place for this issue.
I've noticed that with docker 17.12.0-ce and the mongo:3.4.1 image, memory limits imposed on the container are not "respected" by mongo. What I mean by this is that mongo seems to not recognize the memory limit and tries to use the full memory of the host system.
This leads to bad things happening when memory fills up - mongo starts spilling into swap and performance slows to a crawl.

I considered explicitly limiting the cache size for WiredTiger, but that's no good because the file-system cache is still unbounded.
Any ideas for a workaround?

Hey @rueberger !
I'm working around this issue too, but I still looking for a workaround, without success.
Perhaps, do you had found the way to fix this behaviour?
My lab on Kubernetes:
Sharding Cluster: 1 replica set Config Servers (3 servers), 1 Shard (1 replica set, 3 servers + 2 arbiters) and 2 mongos.
Thanks,
Ronald E.

I haven't had any issues for a while, but I'm not really sure what changed. Now running mongo:3.6, with the following mongo.conf:
storage:
  dbPath: /data/db
  wiredTiger:
    engineConfig:
         cacheSizeGB: 6

and a container memory limit of 10G. Hope that helps.


Search for "a takumi doi" is wrongly parsed

From https://rt.inspirehep.net/Ticket/Display.html?id=1055601:
An author's last name is doi, but the search for a takumi doi returns no results as doi gets interpreted as a keyword to search for a DOI. This should be fixed to allow searches for people whose names are keywords.

Same bug as #1239


vendor problem.

Describe the bug
colcon build.
To Reproduce
CMake Error at CMakeLists.txt:17 (find_package):
By not providing "Findepd_onnxruntime_vendor.cmake" in CMAKE_MODULE_PATH
this project has asked CMake to find a package configuration file provided
by "epd_onnxruntime_vendor", but CMake did not find one.
Could not find a package configuration file provided by
"epd_onnxruntime_vendor" with any of the following names:
epd_onnxruntime_vendorConfig.cmake
epd_onnxruntime_vendor-config.cmake

Add the installation prefix of "epd_onnxruntime_vendor" to
CMAKE_PREFIX_PATH or set "epd_onnxruntime_vendor_DIR" to a directory
containing one of the above files.  If "epd_onnxruntime_vendor" provides a
separate development package or SDK, be sure it has been installed.

epd_ros2_ws/src/easy_perception_deployment/onnxruntime.repos
find the repo.   just not documented well.

Hi @flydragon2018 , currently the only explanation and setup instructions are documented in this PR https://github.com/ros-industrial/easy_perception_deployment/pull/60. Sorry about the inconvenience.

thanks for reply.


Traefik 2.0 on Docker Host Network; Router will redirect instead of reverse proxy

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
I configured reverse proxy Pritunl website using Traefik 2.0.

What did you expect to see?
Pritunl website loading correctly.
What did you see instead?
On client side, I am being redirected to localhost url (<IP_ADDRESS>:5400/login) instead of server url example.com/login. This is working correctly in Traefik 1.7 backends.
Output of traefik version: (What version of Traefik are you using?)

Version:      2.0.0
Codename:     montdor
Go version:   go1.13
Built:        2019-09-16T17:35:17Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
servers.yml
http:
  routers:
    vpn:
      rule: "Host(example.net)"
      service: vpn
      tls: {}

  services:
    vpn:
      loadBalancer:
        servers:
        - url: "https://<IP_ADDRESS>:5400/"

Docker-Compose.yml
version: '3.3'

services:
  reverse-proxy:
    image: traefik:latest # The official Traefik docker image
    command: --providers.docker
    ports:
      - "80:80"     # The HTTP port
      - "443:443"   # The HTTPS port
      - "8080:8080"   # Dashboard port
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock" # So that Traefik can listen to the Docker events
      - "./traefik.yml:/traefik.yml"
      - "./acme.json:/acme.json"
      - "./servers.yml:/servers.yml"
    labels:
      - "traefik.enable=true"
    network_mode: host
    restart: always

traefik.yml
global:
  checkNewVersion: false
  sendAnonymousUsage: false
serversTransport:
  insecureSkipVerify: true
entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"
  traefik:
    address: ":8080"
providers:
  docker:
    watch: true
    endpoint: "unix:///var/run/docker.sock"
    defaultRule: "Host(`example.net`)"
  file:
    watch: true
    filename: "/servers.yml"
api:
  insecure: true
  dashboard: true
  debug: false
certificatesResolvers:
  account:
    acme:
      email<EMAIL_ADDRESS>      storage: "/acme.json"
      httpChallenge:
        entryPoint: web
      tlsChallenge: {}

To me it sounds more like a config issue rather than a traefik bug.  I think the key question is this: it sounds like it's Pritunl does the redirection, not traefik (traefik would not know to redirect to /login since it does not appear anywhere in the configuration), so why Pritunl is redirecting to that address? When you find out this, you are likely to make progress in resolving this.

As @andrewsav-datacom said, the redirect looks triggered by the backend service, not by Traefik itself. Do you mind switching to the community forum to get further help from the community, as this is not a bug with Traefik itself. Thanks a lot for your understanding and helping us having a good issue triage!

Hello,
While not a bug, this issue is related to Traefik and its interface with services. For future reference, I have managed to find out the solution to this problem, which is enabling passHostHeader option.
`http:
routers:
vpn:
rule: "Host(example.net)"
service: vpn
tls: {}
services:
vpn:
loadBalancer:
passHostHeader: true
servers:
- url: "https://<IP_ADDRESS>:5400/"`


Flexmock now has a module with exceptions

The tests are failing with the latest flexmock because of line:
https://github.com/containerbuildsystem/osbs-client/blob/1b5823ec62be281cea8e096a034997ff86cdab86/tests/test_api.py#L11
should now be:
from flexmock import flexmock
from flexmock.exceptions import MethodCallError

See https://github.com/flexmock/flexmock/blob/master/CHANGELOG.md#release-0110

Fixed in the linked PR.

Thank you for reporting this


README

As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

I updated the README file and now can view a professional README that provides information on the project and how to use it.


run windows plan build test in docker

Signed-off-by: Matt Wrock<EMAIL_ADDRESS>

In the end we didn't need this one


MassInstallAction: Install the GitHubActionsCI workflow on this repository

This pull request sets up the GitHubActionsCI workflow on this repository. cc: @christopher-dG

Hmm, it seem Python needs something special to work on GHA?


Loading imagenet-1k validation split takes much more RAM than expected

Describe the bug
Loading into memory the validation split of imagenet-1k takes much more RAM than expected. Assuming ImageNet-1k is 150 GB, split is 50000 validation images and 1,281,167 train images, I would expect only about 6 GB loaded in RAM.
Steps to reproduce the bug
from datasets import  load_dataset

dataset = load_dataset("imagenet-1k", split="validation")

print(dataset)

"""prints
Dataset({
    features: ['image', 'label'],
    num_rows: 50000
})
"""

pipe_inputs = dataset["image"]
# and wait :-)

Expected results
Use only < 10 GB RAM when loading the images.
Actual results

Using custom data configuration default
Reusing dataset imagenet-1k (/home/fxmarty/.cache/huggingface/datasets/imagenet-1k/default/1.0.0/a1e9bfc56c3a7350165007d1176b15e9128fcaf9ab972147840529aed3ae52bc)
Killed

Environment info

datasets version: 2.3.3.dev0
Platform: Linux-5.15.0-41-generic-x86_64-with-glibc2.35
Python version: 3.9.12
PyArrow version: 7.0.0
Pandas version: 1.3.5
datasets commit: 4e4222f1b6362c2788aec0dd2cd8cede6dd17b80

My bad, 482 * 418 * 50000 * 3 / 1000000 = 30221 MB ( https://stackoverflow.com/a/42979315 ).
Meanwhile 256 * 256 * 50000 * 3 / 1000000 = 9830 MB. We are loading the non-cropped images and that is why we take so much RAM.


Uncaught NoAnnotationError {_nativeError: ZoneAwareError}

My angular 2 (v 2.0) project using webpack was working until I try to integrate ng2-bootstrap-modal, which requires me to upgrade everything to a newer version. Since then, I trapped in a rabbit hole. Now, I got everything to (almost) the latest, and my npm start doesn't show any error, however, my project doesn't start up. The browse log shows me the follow error:
NoAnnotationError
_nativeError
:
Error: Cannot resolve all parameters for 'Parser'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'Parser' is decorated with Injectable. at NoAnnotationError.BaseError [as constructor] (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1244:31) [<root>] at new NoAnnotationError (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1568:20) [<root>] at _dependenciesFor (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2410:19) [<root>] at resolveReflectiveFactory (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2289:28) [<root>] at resolveReflectiveProvider (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2314:86) [<root>] at Array.map (native) [<root>] at resolveReflectiveProviders (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2323:52) [<root>] at Function.ReflectiveInjector.resolve (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2542:20) [<root>] at Function.ReflectiveInjector.resolveAndCreate (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2575:83) [<root>] at JitCompilerFactory.createCompiler (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:113:2), <anonymous>:27952:78) [<root>] at PlatformRef_._bootstrapModuleWithZone (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8071:61) [<root>] at PlatformRef_.bootstrapModule (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8058:25) [<root>] at eval (eval at <anonymous> (http://localhost:3000/bundle/main.js:5:2), <anonymous>:4:53) [<root>] at Object.<anonymous> (http://localhost:3000/bundle/main.js:5:2) [<root>]
message
:
"Cannot resolve all parameters for 'Parser'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'Parser' is decorated with Injectable."
originalStack
:
"Error: Cannot resolve all parameters for 'Parser'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'Parser' is decorated with Injectable.↵    at ZoneAwareError (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:2319:2), <anonymous>:917:33)↵    at NoAnnotationError.BaseError [as constructor] (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1244:31)↵    at new NoAnnotationError (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1568:20)↵    at _dependenciesFor (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2410:19)↵    at resolveReflectiveFactory (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2289:28)↵    at resolveReflectiveProvider (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2314:86)↵    at Array.map (native)↵    at resolveReflectiveProviders (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2323:52)↵    at Function.ReflectiveInjector.resolve (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2542:20)↵    at Function.ReflectiveInjector.resolveAndCreate (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2575:83)↵    at JitCompilerFactory.createCompiler (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:113:2), <anonymous>:27952:78)↵    at PlatformRef_._bootstrapModuleWithZone (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8071:61)↵    at PlatformRef_.bootstrapModule (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8058:25)↵    at eval (eval at <anonymous> (http://localhost:3000/bundle/main.js:5:2), <anonymous>:4:53)↵    at Object.<anonymous> (http://localhost:3000/bundle/main.js:5:2)"
stack
:
"Error: Cannot resolve all parameters for 'Parser'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'Parser' is decorated with Injectable.↵    at NoAnnotationError.BaseError [as constructor] (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1244:31) [<root>]↵    at new NoAnnotationError (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1568:20) [<root>]↵    at _dependenciesFor (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2410:19) [<root>]↵    at resolveReflectiveFactory (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2289:28) [<root>]↵    at resolveReflectiveProvider (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2314:86) [<root>]↵    at Array.map (native) [<root>]↵    at resolveReflectiveProviders (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2323:52) [<root>]↵    at Function.ReflectiveInjector.resolve (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2542:20) [<root>]↵    at Function.ReflectiveInjector.resolveAndCreate (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2575:83) [<root>]↵    at JitCompilerFactory.createCompiler (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:113:2), <anonymous>:27952:78) [<root>]↵    at PlatformRef_._bootstrapModuleWithZone (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8071:61) [<root>]↵    at PlatformRef_.bootstrapModule (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8058:25) [<root>]↵    at eval (eval at <anonymous> (http://localhost:3000/bundle/main.js:5:2), <anonymous>:4:53) [<root>]↵    at Object.<anonymous> (http://localhost:3000/bundle/main.js:5:2) [<root>]"
zoneAwareStack
:
"Error: Cannot resolve all parameters for 'Parser'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'Parser' is decorated with Injectable.↵    at NoAnnotationError.BaseError [as constructor] (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1244:31) [<root>]↵    at new NoAnnotationError (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:1568:20) [<root>]↵    at _dependenciesFor (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2410:19) [<root>]↵    at resolveReflectiveFactory (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2289:28) [<root>]↵    at resolveReflectiveProvider (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2314:86) [<root>]↵    at Array.map (native) [<root>]↵    at resolveReflectiveProviders (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2323:52) [<root>]↵    at Function.ReflectiveInjector.resolve (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2542:20) [<root>]↵    at Function.ReflectiveInjector.resolveAndCreate (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:2575:83) [<root>]↵    at JitCompilerFactory.createCompiler (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:113:2), <anonymous>:27952:78) [<root>]↵    at PlatformRef_._bootstrapModuleWithZone (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8071:61) [<root>]↵    at PlatformRef_.bootstrapModule (eval at <anonymous> (http://localhost:3000/bundle/vendor.js:119:2), <anonymous>:8058:25) [<root>]↵    at eval (eval at <anonymous> (http://localhost:3000/bundle/main.js:5:2), <anonymous>:4:53) [<root>]↵    at Object.<anonymous> (http://localhost:3000/bundle/main.js:5:2) [<root>]"
__proto__
:
Object

It sounds like some of the components are missing Injectable, but which one? How do I find it out? Migrating to Angular2 is becoming a nightmare.

@miliu99 , I think this is not zone.js issue, please post it in stackoverflow.

@miliu99 did you solve it?


Add continous export dialog history

Using ChatGPT, resume the dialog history  to have context of the previous dialog history. In this way we can manage the conext window  minimazing the losing information.

While we sadly didn't had the time to implement the context window optimization, we've succesfully implemented the continous robot interaction monitoring.
Hence I'm closing this issue.


VoodooHdaSettingsLoader dose not work

OS: 10.13.6 (17G2112)
appVersion: VoodooHDA-2.9.2-Clover-V14
issue:
start VoodooHdaSettingsLoader failed （same as root）
exception ： 2019-12-09 18:07:37.809 VoodooHdaSettingsLoader[655:7069] Couldn't load settings file (file opening problem: not here, or read protected)

VoodooHdaSettingsLoader is useless anyway, it was introduced in the old VoooDoo Installer but not adapt to the new VodooHDA
You can delete it I will remove in the next release


Blinking cursor

Any option to disable cursor blinking?
Also, how to increase the font size for the file explorer.

Please do not combine multiple issues into a single.
It is currently not supported to increase the font size of the file explorer, you can zoom in the entire workspace.
Cursor blinking is not supported.

cursor blinking can now be disabled thanks to #500 from @Protectator
@anothergituser Please create a new issue for the other half (font size of explorer) or use zoom in.


[FEATURE] is it having incoming video call notification? if not ,any solution for that?

Incoming call notification is not included in this SDK. You can use CallKit(iOS) and ConnectionService(Android) to display the call screen. You can read about the complete process here.


Update mac-schedule-scan.md

Made changes to the document w.r.t schedule scan and fixed Edits and date/time issues
per issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/10152

@JohanFreelancer9 Please copy review

Learn Build status updates of commit 6000c3e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/defender-endpoint/mac-schedule-scan.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@siosulli Please merge this PR. Thanks


Theme settings incorrectly refreshed

This bug can be explained in two different scenarios. One without 3rd party themes installed (as is the default) and one with 3rd party themes installed. Bug is in master, 2.0RC and dev.
Without:
Under display settings when you select a non-default (e.g. dark) redbasic schema and click submit, the schema is correctly loaded, but the theme settings are incorrectly refreshed. It shows the default Focus schema again (note: the changed schema is loaded). When checking the logs and the database all seems fine. So it looks only a display issue in the theme settings.
With 3rd party themes:
The difference with the description above is that when you select a redbasic schema (e.g. dark) and click submit, the theme settings refreshes, but jump back to the first theme in the theme drop-down list. Without 3rd party themes it is doing of course the same, but it has only one theme.
But this situation has more consequences, because after it jumps back to another theme the schema drop-down is empty (that is correct with this 3rd party theme) and the  'Custom theme settings' are also empty (also correct). But the user selected e.g. redbasic:dark and has to specifically select first the redbasic theme and then the dark schema again to get the Custom theme settings back.
Also note that selecting another 3rd party it refreshes correctly.

Oops I clicked the wrong button. Anyway, I've made a screencast, but I can't upload it here, so please see: https://hubzilla.nl/cloud/jeroenpraat/dev/themesettingsbug.webm

This is fixed in 2.2. Thanks Mario!

oops


[epoll] Reactor does not register interest in some cases. Issue introduced after read_with/write_with commit.

I updated to the latest smol on a pet project that uses UnixStream for communication and I notice that in some cases communication was getting stuck on epoll_wait.
I did bisect on smol and the first bad commit is 76aa1ea654a322d0abaf4291dde2eb5d89c50205.
I also created a minimal reproducible example: https://github.com/oblique/smol-epoll-issue
Something that I noticed is that if I switch from UnixStream to TcpStream, the bug is not reproducible anymore.
To reproduce it do:

Clone smol-epoll-issue
Run: cargo run --bin server
Run: cargo run --bin client
Client will start printing some text
After some seconds text printing will get stuck

Thanks! This is an important case (where both read and write would block) that should probably be added to the test suite of smol itself.
@stjepang I believe we need to reregister the interest when previously we are interested in both readable and writable, but only one of them is emitted, because we are still interested in the other:
(Maybe this will fix #136 too.)
diff --git a/src/reactor.rs b/src/reactor.rs
index c5cd338..6ba4b65 100644
--- a/src/reactor.rs
+++ b/src/reactor.rs
@@ -293,6 +293,15 @@ impl ReactorLock<'_> {
                             if ev.writable {
                                 ready.append(&mut wakers.writers);
                             }
+
+                            if !(wakers.writers.is_empty() && wakers.readers.is_empty()) {
+                                self.reactor.sys.reregister(
+                                    source.raw,
+                                    source.key,
+                                    !wakers.readers.is_empty(),
+                                    !wakers.writers.is_empty(),
+                                )?;
+                            }
                         }
                     }

I tried this patch and it fixes the problem.


Fix incorrect dyno-jedis dependency version

As mentioned in https://github.com/Netflix/conductor/issues/290, the dependency for dyno-jedis needs to be 1.5.6+
Recent upgrade of dyno-queues-redis from 1.0.6 to 1.0.7 has downgraded dyno-jedis to 1.4.7 causing the issue #290.
Explicitly adding the dependency in redis-persistence/build.gradle to the latest (1.5.9, same as dyno-core) fixes the issue

thanks @v1r3n
one more thing: the 1.8.0 release is currently unusable because of this issue, is it possible to make a new 1.8.1 release soon?


auto switch to selected month when focused

I'm having the same problem with this guy
http://stackoverflow.com/questions/42506840/airbnb-react-date-range-picker-only-showing-current-month-calendar-not-selected
which the calendar did not go to the selected month when opening up. For example current month is February, I selected May, after that I try to reopen, the calendar is still in February, isn't that it should be at May?

+1, I have similar issue

Sounds like this would be solved by using initialVisibleMonth, as described in this answer.


Report spring 6

Create inventory report, still in progress (need your help for something).
Separate shipment from reports, add total shipment orders to the order reprot.
Fix old bugs related to order report.

The definition of InventoryReportItem is wrong. In order to use objects of the class in a table, the class has to be defined as a proper Java "bean": The getters and setters return and take values, not properties and you also need to have methods that return the properties themselves.


add the crypto test

增加crypto包下的单元测试

Codecov Report

Merging #81 into master will increase coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #81     +/-   ##
=========================================
+ Coverage   44.67%   44.88%   +0.2%
=========================================
  Files         158      162      +4
  Lines       13910    13990     +80
=========================================
+ Hits         6214     6279     +65
- Misses       7125     7131      +6
- Partials      571      580      +9

Impacted Files
Coverage Δ

g/util/grand/grand.go
91.11% <0%> (-4.45%)
:arrow_down:

g/container/garray/garray_normal_string.go
70.99% <0%> (-1.21%)
:arrow_down:

g/crypto/gaes/gaes.go
80.95% <0%> (ø)

g/crypto/gcrc32/gcrc32.go
100% <0%> (ø)

g/crypto/gmd5/gmd5.go
77.77% <0%> (ø)

g/crypto/gsha1/gsha1.go
75% <0%> (ø)

g/container/garray/garray_normal_int.go
73.41% <0%> (+1.2%)
:arrow_up:

g/os/gtimer/gtimer_entry.go
89.53% <0%> (+3.48%)
:arrow_up:

Continue to review full report at Codecov.

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

@pibigstar 覆盖率还差一点，加油


Make Markers in Annotations Public

This could eliminate code duplication in Chisel. It's [probably] impossible to have complete code-share for Chisel and Firrtl annotations since the Chisel objects are very different than Firrtl's Named things, but at least sharing the marker in the marker pattern (for example, see DontTouchAnnotation) would be somewhat better.

Will be made obsolete by annotations refactor

Related to #704

made obsolete by #721


Deleting all rows

Hello.
First of all , I would like to thank you for this package.
Is there a direct method for deleting all rows without selecting them?

// Assign the stateManager as a variable in the onLoaded event callback as shown below.
child: PlutoGrid(
  columns: columns,
  rows: rows,
  onChanged: (PlutoOnChangedEvent event) {
    print(event);
  },
  onLoaded: (PlutoOnLoadedEvent event) {
    stateManager = event.stateManager;
  },
),

// And you can call the stateManager from a button or a function to delete all rows as shown below.
stateManager.removeRows(stateManager.rows);

If not, please contact me again.
Thank you.

Thanks !!


chore!: remove library v3

This PR removes the V3 of the library.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)
[X] Will this cause breaking changes to existing Java or Kotlin integrations? If so, ensure the commit has a BREAKING CHANGE footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/

Added ! to the PR title to indicate breaking change, but will need to manually add this to the squashed commit message.

Added ! to the PR title to indicate breaking change, but will need to manually add this to the squashed commit message.

I have rebased from main and squashed all the commits into a single one with the exclamation symbol, let me know if this works out.


will update the selector to target only items in the html.dark-mode

Solves the bug mentioned in this PR #39
Sorry about not noticing.

No worries. I didn't notice either.


7.9 seems to not have been properly released public repositories

Ran into issue #282 which is already solved in 7.9 which unfortunately is not available in any decent public repositories so it can be used.
There's is an issue with 7.9 not being available however:
https://search.maven.org/artifact/org.bsc.maven/confluence-reporting-maven-plugin
https://mvnrepository.com/artifact/org.bsc.maven/confluence-reporting-maven-plugin
Strangely enough I was able to fetch 7.9-SNAPSHOT and can confirm that the fix solves the issue with "%" in md files. (also figured out the "%%" workaround)
I would like however to use 7.9 and not 7.9-SNAPSHOT or 7.8+%% workaround so please lookinto the issue with 7.9 not being available

Hello @elisedlund-ericson thanks for the feedback
It seems strange to me, I will check on the Sonatype side

Hi @Elisedlund-ericsson fix it!
the 7.9 official release is available from pubic Sonatype repo as usual

verified it!
thanks for the quick turnaround time 🥇


fs/partition: Make read_partition_block callable outside ptable

Summary
Impact
Code refectory, no real change
Testing

LGTM. Not related to this PR, but shouldn't parse_ptable_partition also be declared on fs/partition/partition.h? The declaration is currently in fs/partition/fs_partition.c, which does not make much sense to me.

Good pointer, update too.


Update new image registry path

What type of PR is this?
/kind failing-ci
What does this PR do / why we need it:
To fix CI failure, Updating new test container registry path
Which issue(s) this PR fixes:
Fixes - CI failure due to deprecated test container registry
How to test changes / Special notes to the reviewer:
CI should pass

/kind failing-ci

CI will still fail because openshift CI job config still uses the master branch docker file which has the deprecated image registry path. So merging it forcefully cc_ @wtam2018


DesignWare drivers cleanup

@tbursztyka +1 for USB driver changes, could you open a own PR for that?

@jfischer-phytec-iot Well, I think this PR is now in a ready state.
I just wonder why it's annoying me with  the dma driver, since the former name based on "cavs" was not covered by the codeowners file anyway.


Fixed issue

Fixes #172
Added sample products.

Hey, I just contributed to the code and pushed it but why the bot says this PR has 0 quantified lines of changes

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

Looks good!

Thank You


Allow renaming of old stored chats in chat history

As title says. Being able to rename the chats would be most helpful.

Good idea - will implement this soon