What about App Exposé for iPad?

What about App Exposé for iPad?

Could you elaborate on your request? Are you referring to the iPadOS 13+ feature that allows you to open multiple windows of the same app? In that case, it's a known issue that you can't run multiple virtual machines at once on iOS #9.

Could you elaborate on your request? Are you referring to the iPadOS 13+ feature that allows you to open multiple windows of the same app? In that case, it's a known issue that you can't run multiple virtual machines at once on iOS #9.

Right this would depend on #9 which will not be implemented due to the complexity and low payoff. Running multiple VM instances will probably not work anyways due to the memory restrictions by iOS. Maybe in a future where XPC is allowed on iOS or QEMU is massively refactored or we no longer depend on QEMU this may be possible...


HSEARCH-5067 Allow targeting entities by name in the Standalone POJO Mapper

https://hibernate.atlassian.net/browse/HSEARCH-5067

I addressed your comments, thanks!

merged! 🎉 😃


ci: add osv-scanner.toml file

Current behavior
Added a osv-scanner.toml file as required

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

@itsajay1029 CI went red due to the recent commit not being signed and I had to amend your commit, this was a minor fix.


Cannot assign requested address

Hello
I have a timer with 0.00001 sec interval , after a while I have this warning , why?

Warning: stream_socket_client(): unable to connect to tcp://<IP_ADDRESS>:2300 (Cannot assign requested address) in vendor/workerman/gateway-worker/src/Lib/Gateway.php on line 363

Open /etc/sysctl.conf and add
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 1

Run sysctl -p

Can you explain what is it? line by line

Explain it in english is too hard for me.  : )
I found a similar link hope that will help you.
https://redmine.lighttpd.net/projects/weighttp/wiki

Hi
I still get the same error, although I added lines listed above(except net.ipv4.tcp_tw_recycle = 1, because it is not available anymore)


database/gredis: Add hash field expiration support for Redis v7.4.0

Description
it is a new feature for Redis since v7.4.0.
see: https://redis.io/docs/latest/commands/hexpire/
Command:

[ ] HEXPIRE
[ ] HEXPIREAT
[ ] HEXPIRETIME
[ ] HPERSIST
[ ] HPEXPIRE
[ ] HPEXPIREAT
[ ] HPEXPIRETIME
[ ] HPTTL
[ ] HTTL

Additional
No response

@WankkoRee The gredis package will be deprecated in the future, it's suggested using third-party redis package directly.


[forwarder nss e2e test] Remove hardcoded stack

What does this PR do?

Remove leftover hardcoded stack in e2e test.
Motivation

Shouldn't have been pushed.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


KAFKA-2338: Warn on max.message.bytes change

Both TopicCommand and ConfigCommand warn if message.max.bytes increases
Log failures on the broker if replication gets stuck due to an oversized message
Added blocking call to warning.

@junrao your feedback has been incorporated

Thanks for the patch. LGTM


Maybe this works better on CI

This seems to break the build with
[ERROR] Failed to execute goal org.apache.camel:camel-package-maven-plugin:3.0.0-SNAPSHOT:generate-dataformats-list (generate) on project camel-core: Error loading dataformat model from camel-core. Reason: java.io.FileNotFoundException: /home/oscerd/workspace/apache-camel/camel/core/camel-core/target/camel-core-3.0.0-SNAPSHOT.jar/org/apache/camel/model/dataformat/zip.json (No such file or directory) -> [Help 1]
I have to revert


Nested keys in structured facts are incorrectly downcased

Puppet downcases fact names (see FACT-777) but any keys as part of hashes in structured facts are left as-is and accessible using their original, possibly mixed-case, names. rspec-puppet incorrectly downcases all hash keys in the facts hash, making it impossible to accurately test situations where mixed-case hash keys are expected in facts.

See PR #507 for a patch addressing this.

Closing this as the fix in #507 has been merged.


Migrating download utils to torchdata

Hello,
following Patrick's suggestion, I'm opening an issue here to discuss if the torchvision maintainers would be open to move the download utils upstream to torchdata. I'm the maintainer of a similar package which is modeled after torchvision to a large extent and would benefit greatly from such a move, much like torchaudio/text I would assume.
cc @pmeier

prototype datasets are currently on hold

Why is that if I may ask? Is there a place where your team defines a roadmap for torchvision?

benefits

The benefit would be not having to rely on torchvision for download utils and torchdata for datapipes, but just torchdata for all of that functionality.  I'm not sure I understand what you mean by saying that the users would have no touching points with torchdata, isn't the goal of torchvision/prototype to use datapipes?

Hi @biphasic

Why is that if I may ask? Is there a place where your team defines a roadmap for torchvision?

We came to the conclusion that for now, there are more suitable opportunities to improve data-loading speed in torchvision. We might revisit in the future. Re roadmap: we used to disclose those more actively, but recent events have made that difficult. To give you an idea, the rough roadmap for now is to 1) release the transforms V2 work 2) improve data-loading speed via improvements to Resize() 3) revamp video decoding utilities.
Going back to the original goal of this issue: any additional dependency comes with significant maintenance cost, and there's no immediate plan to take a dependency on torchdata. So as @pmeier already it's unlikely that we'll migrate our download functionality to torchdata (on top of the blockers @pmeier already mentioned).
Also @biphasic please note that while our download utils are effectively public, we really don't recommend that you rely on them in your library: those were introduced a long time ago as public but they should have been private from the beginning. We might deprecate and make them private in the future, so please migrate away from them if you can.
Regardless of whether torchvision relies on torchdata for download functionality, there shouldn't be anything preventing you from relying on torchdata on your side? The download functionalities over there are public, so perhaps this is a better alternative for you

Thanks a lot for the clarification @NicolasHug . While I understand that datapipes might not bring a big speed improvement, for me there's a big plus in their API. Would you say then there's a risk of torchdata not being actively developed anymore? In that case I might hold off as well then for the time being

Would you say then there's a risk of torchdata not being actively developed anymore

I don't think this is the case, but let me ping @ejguan and @NivekT who will be better suited to answer that

Related on need of a better / reliable download utility across PyTorch:

https://github.com/pytorch/pytorch/issues/68320
https://github.com/pytorch/pytorch/issues/73466
https://github.com/pytorch/pytorch/issues/91965

@biphasic just making sure you saw it: https://github.com/pytorch/data/#torchdata-see-note-below-on-current-status
Since torchdata development is paused, we won't be migrating to torchdata utils anytime soon, so I'll close this issue. Feel free to provide feedback for torchdata on https://github.com/pytorch/data/issues/1196

@NicolasHug thanks a lot for letting me know!


remove brackets on definition callout

Is there any way i can remove brackets from the definition callouts.
right now, plaintext:
> [!def] My Title
renders as:

Definition (My Title).

whereas what I want is:

Definition My Title

or even perhaps the option to:

Definition: My Title

What's the scoop?

This is not supported currently, but I have an idea of an update that lets you customize the format of definition callout title via CSS snippet. I'll try some.


Issues/66 81

This pull request is to resolve issues 66 and 81 - at least on the eLCI side. The function that maps emissions from the various NETL inventories to the federal elementary flow list (fedefl) will no use the mappings from the fedefl rather than the csv file previously contained in the data directory. This should close issue 66.
There is also a fix to issue 81 - flows with mapped UUIDs that do no exist are dropped from the final mapped dataframe to avoid populating openLCA with exchanges that will result in errors. The ultimate resolution to the problem will require updated mappings in the fedefl, so that no flows are dropped.

Hold of on merging this - I need to address one more issue with units. Right now, I think the dictionary processes don't properly account for the changing units.

Alright - this is ready to go now.
Along with the issues 66 and 81, this fixes a couple other things that I found while resolving these:

There's new coal and natural gas data that doesn't need to be mapped to the fedefl because they're from models using the fedefl.
There were two source of balancing authority names that resulted in some mismatches when going to link processes. Everything should eventually feed to the crosswalk provided in BA_Codes_930.xlsx
reducing the number of pd.concat info messages by adding sort=False to the concats I came across
Correcting a UUID for methane in hydro_upstream.py
Fixing some shortcuts I had taken regarding units and conversion factors for mapping flows.

@jump2conclusionsmatt we are trying to test the new flow mappings, but are having some issues. Did you commit coal_mining_lci.csv

I had not committed the new coal mining data yet. Should be up now. Checking to see if I missed any other data files.

With commit #505aae9 I modified setup.py to force install of a specific release of fedelemflowlist upon pip install. We should make sure that's the release that contains all the necessary mappings. @jump2conclusionsmatt @bl-young

We are currently testing the mapping file from this branch so we should have a final version to push to FEDEFL in the next couple of days (cc @hottleta)

I'm good with merging in this major update to the upstream data when you've checked it


Export .png version of logo with white text

Background
The current mock has a logo with dark text on a dark background. It might be easier to read if the text was white instead.

Logos are located here:
https://github.com/yochannah/code-is-science/tree/master/static/images
Task

Export new copies of the logos in the images/model-x folders to .pngs with white text for dark backgrounds. You probably want to open the svg copies and then export to png as they'll be highest quality.
Ensure that they are named clearly as the light text option.

To pick the task up

Comment on this issue to let people know you're working on it.
Fork this repo
Make the changes detailed above, and when ready, make a PR! (guidance here if needed: https://help.github.com/articles/creating-a-pull-request/ )
Bask in your awesomeness!

If you need help:
Mention me, @yochannah, tweet me @yoyehudi, or email<EMAIL_ADDRESS>

I'll work on this

Awesome! :) Ping me if you have any questions

Resolved by #24 <3


feat: add experimental spanner readChangeStreams

Adds the SpannerIO.readChangeStreams feature that will enable users to consume a change stream from Cloud Spanner.
This feature is under preview now, and can only be used for allowlisted customers.
When reading a change stream the users will be able to operate on a PCollection of DataChangeRecords, containing the modifications made to the database as well as the type of operation.
This PR contains the following modifications:

It exposes the SpannerIO.readChangeStream(...) functionality. Here we construct the internal pipeline composed of Impulse -> Initialize -> DetectNewPartitions -> ReadChangeStreamPartition -> PostProcessingMetrics.
It adds a DoFn to create the metadata table when the pipeline is deployed. This will be used to maintain internal state for the Connector. It can be seen in the InitializeDoFn class.
The InitializeDoFn uses a new class called NameGenerator that creates a random metadata table name to be used within the Connector.
It adds a DoFn to collect metrics as a final step in the Connector, the PostProcessingMetricsDoFn. This class will count the number of DataRecords produced, the stream time of a record from Cloud Spanner to the worker, and the total time that a record took from commit time in Spanner until it is emitted into the output PCollection.
Small bug fixes that changes the initial watermark timestamp from the current timestamp to the partition's start at timestamp.

I decided to leave the integration tests for another PR, to make this one smaller.

retest this please

Test failures are unrelated to this PR. I can see two failed tests:
GcpApiSurfaceTest. testGcpApiSurface
StructUtilsTest. testStructToBeamRowFailsTypesDontMatch
None of these were touched by us or should be affected by our changes. I will wait until there is a fix in master and pull those, but you can go ahead and review @pabloem

R: @pabloem


Flutter: 3.0.4 -> 3.3.3, flutter.dart: 2.17.5 -> 2.18.2, add a flutter2 package for "legacy" dependents

Description of changes
https://docs.flutter.dev/whats-new#aug-31-2022-flutter-vikings-edition-33-release
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Doesn't build currently:
$ nix-build /nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv
this derivation will be built:
  /nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv
building '/nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv'...
unpacking sources
unpacking source archive /nix/store/k0h6gcips67gj5r7ca1d7g99rdbbddcn-flutter_linux_3.3.0-stable.tar.xz
source root is flutter
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file flutter/.pub-cache/hosted/pub.dartlang.org/.cache/vector_math-versions.json
unpackPhase completed in 30 seconds
patching sources
applying patch /nix/store/2a5mrbr5scfvmbbjcfbn9ckac7bsyphz-disable-auto-update.patch
patching file bin/internal/shared.sh
patching file packages/flutter_tools/lib/src/runner/flutter_command_runner.dart
applying patch /nix/store/z2v0v71ba751ybmj3knf15lyybp13ny5-git-dir.patch
patching file dev/bots/prepare_package.dart
patching file packages/flutter_tools/lib/src/commands/downgrade.dart
patching file packages/flutter_tools/lib/src/version.dart
applying patch /nix/store/ym3mz067l0k2rri7vq6djjx72v1mklz8-move-cache.patch
patching file packages/flutter_tools/lib/src/asset.dart
patching file packages/flutter_tools/lib/src/cache.dart
patching file packages/flutter_tools/lib/src/artifacts.dart
patching file packages/flutter_tools/test/general.shard/artifacts_test.dart
patching script interpreter paths in ./bin/
./bin/cache/artifacts/gradle_wrapper/gradlew: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash"
./bin/flutter: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash"
./bin/dart: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash"
./bin/internal/update_dart_sdk.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash"
configuring
no configure script, doing nothing
building
/build/flutter/packages/flutter_tools /build/flutter
Resolving dependencies...
  pedantic 1.11.1 (discontinued replaced by lints)
Got dependencies!
/build/flutter
Info: Compiling without sound null safety
Error: Error when reading 'packages/flutter_tools/.packages': No such file or directory
Error: Couldn't resolve the package 'flutter_tools' in 'package:flutter_tools/executable.dart'.
packages/flutter_tools/bin/flutter_tools.dart:7:8: Error: Not found: 'package:flutter_tools/executable.dart'
import 'package:flutter_tools/executable.dart' as executable;
       ^
packages/flutter_tools/bin/flutter_tools.dart:10:14: Error: Method not found: 'main'.
  executable.main(args);
             ^^^^
error: builder for '/nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv' failed with exit code 254;
       last 10 log lines:
       > /build/flutter
       > Info: Compiling without sound null safety
       > Error: Error when reading 'packages/flutter_tools/.packages': No such file or directory
       > Error: Couldn't resolve the package 'flutter_tools' in 'package:flutter_tools/executable.dart'.
       > packages/flutter_tools/bin/flutter_tools.dart:7:8: Error: Not found: 'package:flutter_tools/executable.dart'
       > import 'package:flutter_tools/executable.dart' as executable;
       >        ^
       > packages/flutter_tools/bin/flutter_tools.dart:10:14: Error: Method not found: 'main'.
       >   executable.main(args);
       >              ^^^^
       For full logs, run 'nix log /nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv'.

I wanted to debug this by running buildPhase in a nix-shell for flutter, but for some reason that doesn't work:
$ nix-shell /nix/store/90vj9b32w9q9dx63b3d6kmfbx85cmvlk-flutter-3.3.0-unwrapped.drv
warning: Nix search path entry '/nix/store/mvpahh0v6r5hmvnbbj386b855qmshxna-source/overlays' does not exist, ignoring

[nix-shell:~/Documents/projects/nixpkgs]$ cd flutter

[nix-shell:~/Documents/projects/nixpkgs/flutter]$ buildPhase

I'll have to revisit this later, but help would be appreciated ^^

In https://github.com/NixOS/nixpkgs/pull/189338/commits/f6f07a86ff9fd063b6c7d76199ca0fa113d3fdb2 I added a removed import 'cache.dart' back in after it was previously removed in the PR for flutter 3.0.0 because substituting Cache.flutterRoot! with globals.fsUtils.homeDirPath!, '.cache', 'flutter', doesn't work directly because it results in a too long argument list. Leaving it as is works for flutter create and flutter run though 😅

I've tried this out with an existing app that's been updated to use the new flutter versions. flutter run, flutter pub get and dart's lsp server work without a hitch for me.
The builds for firmware-updater and fluffychat are broken again though:
error: builder for '/nix/store/xg95470ihsj0wbaaf8jvv60annxi3h7h-firmware-updater-unstable-deps-flutter-v3.3.2-x86_64-linux.tar.gz.drv' failed with exit code 1;
       last 10 log lines:
       > Downloading linux-x64/linux-x64-flutter-gtk tools...             2,420ms
       > Downloading linux-x64-profile/linux-x64-flutter-gtk tools...      1,512ms
       > Downloading linux-x64-release/linux-x64-flutter-gtk tools...      1,263ms
       >
       > 💪 Building with sound null safety 💪
       >
       > Building Linux application...
       > CMake is required for Linux development.
       > It is likely available from your distribution (e.g.: apt install cmake), or can be downloaded from https://cmake.org/download/
       > mv: cannot stat '.packages': No such file or directory
       For full logs, run 'nix log /nix/store/xg95470ihsj0wbaaf8jvv60annxi3h7h-firmware-updater-unstable-deps-flutter-v3.3.2-x86_64-linux.tar.gz.drv'.
error: 1 dependencies of derivation '/nix/store/gpql8ygm4x4n9r8hwc40m3k5cg1c864b-firmware-updater-unstable.drv' failed to build

Should those packages use their own flutter versions to build and should a flutter_2 package be added? (https://github.com/NixOS/nixpkgs/pull/173200#issuecomment-1180170875)

Should those packages use their own flutter versions to build and should a flutter_2 package be added?

IMO, yes

I use the changes here in my config and it's working great so far.

Hey!
I do definitely think that a flutter_2 package should be added - this is the standard for a lot of packages (python_x from the top of my head).
Does this branch build currently? Do you have anything you need assistance with?

flutter builds currently, some packages depending on it do not.
I know roughly what would need to be done for the flutter_2 package, just
haven't got round to it. I'd accept patches or PRs to my PR if you want to
do the work for me ^^
Sláinte,
Rian Lindenberger
On Sun, 18 Sept 2022, 18:15 riceicetea, @.***> wrote:

Hey!
I do definitely think that a flutter_2 package should be added - this is
the standard for a lot of packages (python_x from the top of my head).
Does this branch build currently? Do you have anything you need assistance
with?
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/189338#issuecomment-1250340731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEF3ZHXGKMBCDI2GTYZ3SLDV6453TANCNFSM6AAAAAAQCU7UIM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I took the liberty of refactoring flutter/default.nix a bit to make it simpler to update.I added a package flutter2 to build firmware-updater and fluffychat with, which works great. I tested that both of those applications run on my nixos machine. I just started another run of  nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" and will tick the box when it doesn't report any errors, otherwise you'll hear from me again.

i don't know  if anything in this pr caused this but discovered this when doing a nixpkgs-review on a another pr
error: hash mismatch in fixed-output derivation '/nix/store/p7xlzhqarn1h4i3y2adqg0g1m5axyr57-fluffychat-1.2.0-deps-flutter-v2.10.5-x86_64-linux.tar.gz.drv':
         specified: sha256-1PDX023WXRmRe/b1L+6Du91BvGwYNp3YATqYSQdPrRY=
            got:    sha256-b4BSOTnA3118HnzG8knLxFBu9NVn5puG/XesacySo10=
            ```

@Artturin haven't looked into it, but just FYI the latest flutter update was https://github.com/NixOS/nixpkgs/pull/201564
this PR introduced a flutter2 package for older packages

i don't know if anything in this pr caused this but discovered this when doing a nixpkgs-review on a another pr
error: hash mismatch in fixed-output derivation '/nix/store/p7xlzhqarn1h4i3y2adqg0g1m5axyr57-fluffychat-1.2.0-deps-flutter-v2.10.5-x86_64-linux.tar.gz.drv':
         specified: sha256-1PDX023WXRmRe/b1L+6Du91BvGwYNp3YATqYSQdPrRY=
            got:    sha256-b4BSOTnA3118HnzG8knLxFBu9NVn5puG/XesacySo10=

That's completely irrelevant. The fluffychat needs to be updated.


The user is able to leave the current lobby he is part of on the home screen.

Corresponding commit in frontend:
https://github.com/sopra-fs24-group-32/sopra-fs24-group-32-client/commit/74a98f77520be38c6bf3d20e1c3bb18d8359311b


Persist complete application state

Instead of selecting some part of the application state that is persisted in the config file, the entire state should be selected, for example using redux-persist. Some parts, such as the formatters will require special handling, but most of the state should serialize nicely.

[ ] Load state
[ ] Save state
[ ] Handle formats separately
[ ] Figure out how to migrate/invalidate state on application updates

It appears redux-persist does have a different approach than I am looking for, so I am going to implement something more basic from scratch.


Duplicate repository definition

I am using the phandom-dsl_2.11:1.18.1 in my project.  The project is a multi module gradle project and one of the module is a cassandra module which uses the phandom library.  While compiling, I get the following error.
Processing of /Users/kuppas/.gradle/caches/modules-2/files-2.1/com.websudos/phantom-dsl_2.11/1.18.1/947cb508bedcbe1d05be074735746da4ce0dada7/phantom-dsl_2.11-1.18.1.pom failed:
    'repositories.repository.id' must be unique: bintraywebsudosossreleases -> https://dl.bintray.com/websudos/oss-releases/ vs https://dl.bintray.com/websudos/oss-releases/ in com.websudos:phantom-dsl_2.11:1.18.1

Looking at the pom (https://dl.bintray.com/websudos/oss-releases/com/websudos/phantom-dsl_2.11/1.18.1/:phantom-dsl_2.11-1.18.1.pom), it is clear that pom has duplicate repository definition for bintraywebsudosossreleases.
Thanks,
-Sridharan

Hi @skuppa,
You are free to check the build definition yourself inside SBT, I don't see any duplicates. Obviously the .pom is generated on the fly and I'm not sure which part of the pipeline deals with that, I would assume SBT. We don't have any man power to spend on this at present times.
Regards.

Hi @skuppa,
Can you please confirm if this still persists in the most recent version of phantom?
Regards.


feat: LR-50-land-deploy partial

Description
Only the deployments scripts for core land and sand.

got outdated, we decided to go with a different set of deploy scripts.


Show selected favicon on the Tab Rules page

On the "Tab Rules" page it shows the title/detection type/url fragment:

It might be nice to also include the chose favicon image so you can confirm what you've allocated to each listing easily.

Thanks @drnic for the suggestion. Will be available in 0.21.0, be sure to opt-in the new version toast inside the settings page in TM!
Best

Cool!

From: Syl<EMAIL_ADDRESS>Sent: Friday, October 27, 2017 12:18:29 AM
To: sylouuu/chrome-tab-modifier
Cc: Dr Nic Williams; Mention
Subject: Re: [sylouuu/chrome-tab-modifier] Show selected favicon on the Tab Rules page (#94)
Thanks @drnichttps://github.com/drnic for the suggestion. Will be available in 0.21.0, be sure to opt-in the new version toast inside the settings page in TM!
Best
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sylouuu/chrome-tab-modifier/issues/94#issuecomment-339681146, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAAAbDaSz3PnS-w1WNmoTmDFWmH16D__ks5swJS1gaJpZM4OxaNA.


Pub/Sub retry settings examples causing customer & support pain

Current sample retry settings here [1] set initialRpcTimeout = totalRpcTimeout, which effectively turns off retries. This has been causing almost daily escalations from major customers.  Please fix to say something more reasonable like

Duration totalTimeout = Duration.ofSeconds(600); // default: 10 seconds
Duration initialRpcTimeout = Duration.ofSeconds(1); // def

Also the mention of the defaults in the comments here is likely distracting.  That should be documented in the RetrySettings class documentation instead.
[1] https://github.com/googleapis/google-cloud-java/blob/master/google-cloud-examples/src/main/java/com/google/cloud/examples/pubsub/snippets/PublisherSnippets.java#L120

@kir-titievsky  PRs 6257 and 6258

closing via #6257 & #6258


endless loop at runtime for heightForRowAtIndexPath:

if I run this code from the documentation inside override func tableView(tableView: UITableView, heightForRowAtIndexPath indexPath: NSIndexPath) -> CGFloat I get stuck in an endless loop:
let cell = self.tableView(tableView, cellForRowAtIndexPath: indexPath)
if (cell.isKindOfClass(DatePickerCell)) {
    return (cell as! DatePickerCell).datePickerHeight()
}

I guess prior to returning from cellForRowAtIndexPath: the tableView calls heightForRowAtIndexPath: itself
It happens when using dequeueReusableCellWithIdentifier in cellForRowAtIndexPath:. A workaround would be to instantiate the cells instance like you did in the example and keep a reference to it...

hm... That would be up to the implementation of cellForRowAtIndexPath. I don't think cellForRowAtIndexPath should usually need the height, or at least it could fetch the height using a different method than calling heightForRowAtIndexPath.


Rm filepaths from automation files

Please review all files in the Automation-Reproducibility-compbio course, and point out if there are any filepaths, or user id on email addresses, if any.
Closes #54.
Here I am also addressing the issue with the gitignore files. Closes #56.

01-c-Best-practices-automation-for-scientists.pdf slides show user ID for path for where to clone repo to (slides labeled 60 and 61)
01-c-Best-practices-automation-for-scientists.pdf slide 66, screenshot of files shows user ID for files

This has been addressed here 4470fbe83b3bf0207f1112aba8e4f2ecaec535a9.

05-install-docker-manually.md, screenshot for step (4) create account still has user ID in email address

This was replaced on the image but it wasn't properly updated on the md file. It is now fixed here fc2fd6318667f9998a793a3718dc20ef1bffdb51


added utf-8 encoding method

added utf-8 encoding method to open targets.json

thanks for creating this project! it's really useful!


bug in analysis NumbaParallelSafetyWarning

Reporting a bug

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

When I run
@njit(parallel=True)
def while_for(n, max_iter=10):
    a = np.empty((n,n))
    i=0
    while i <= max_iter:
        for j in prange(len(a)):
            for k in prange(len(a)):
                a[j,k] = np.random.rand()
        i+=1
    return a
while_for(4)

I get the following warning
Variable i.3 used in parallel loop may be written to simultaneously by multiple workers and may result in non-deterministic or unintended results.
File "<ipython-input-44-a9dc46b8042f>", line 6:
def while_for(n, max_iter=10):
<source elided>
while i <= max_iter:
for j in prange(len(a)): ^ warnings.warn(NumbaParallelSafetyWarning(msg, loc))

When I replace @njit(parallel=True) with @njit it goes away.

Thanks for the report. As a guess, seems like that this is because i is a parfors var but unused in the loop nest. @DrTodd13 please could you take a look? Thanks.

@sklam @stuartarchibald The parfor code detects races in a parallel region by looking for assignments to variables that are live-out of the region that are not reductions.  I think that SSA is doing the following with the variable i.
def while_for(n, max_iter=1):
    a = np.empty((n,n))
    i=0
    #i2 = i
    while i <= max_iter:
        #i3 = i2
        for j in prange(len(a)):
            #i4 = i3
            for k in range(len(a)):
                #i4 = i4
                a[j,k] = np.random.rand()
            #i3 = i4
        i+=1
        #i1 = i3 + 1
        #i2 = i1
    return a

So, inside the parallel region we have i.3 = i.4 and i.3 is live-out.  It doesn't seem like i.3 and i.4 are necessary for the SSA transformation.  Maybe they were just added for consistency of the SSA code.
Thus, the solution here is to not have SSA generate those variables or extend parfor race detection to trace the assignments and if it ends up being a cycle (like in this case i3 -> i4 -> i3) involving only SSA versions then it isn't a race.  In general, it seems like analysis could be easier in general if SSA had a minimization property (the only SSA versions created are actually necessary).
Thoughts?

Yes, I can confirm that the SSA implementation is failing on the minimization property. I think I did the iterated domfront wrong.


Venue invite assignment: catch error "Already assigned" when trying to update the status label

It seems the post process function fails when it tries to change the label of the edge and the pre-process validation fails. This usually happens when the process function fails and we click on retry. I suggest to catch the errors from the pre-process function and continue with the process.

https://api2.openreview.net/logs/process?id=W2QgRH18nrpP0j


superset_init exited with code 127 when docker compose

A clear and concise description of what the bug is.
Expected results
After running docker compose successfully, i can log in with default user "admin"
Actual results
there were errors when running "docker compose up"
superset_init            | /usr/bin/env: ‘bash\r’: No such file or directory superset_init exited with code 127
therefore there was no exsiting user in database, the web page showed error message "invalid login"
Screenshots

How to reproduce the bug

git clone
run "docker compose up"
access http://localhost:8088, login with default user admin with password admin
See error

Environment
Superset version
git log
commit 31e4a90440885c5e0100408e65fedc33786240db (HEAD -> master, origin/master, origin/HEAD)
Author: Kamil Gabryjelski<EMAIL_ADDRESS>Date:   Fri Oct 16 23:23:21 2020 +0200

    Fix overflowing tab's styling in TabbedSqlEditors (#11303)

commit 94e23bfc82613bbca9c6d4c55766836597907b3e
Author: Beto Dealmeida<EMAIL_ADDRESS>Date:   Fri Oct 16 11:10:39 2020 -0700

    feat: export databases as a ZIP bundle (#11229)
    * Export databases as Zip file
    * Fix tests
    * Address comments
    * Implement mulexport for database
    * Fix lint
    * Fix lint

commit 8863c939ad01fe1e065ce60edc93a683e6828d80
Author: Grace Guo<EMAIL_ADDRESS>Date:   Fri Oct 16 10:54:35 2020 -0700

    fix: should update last_modified_time in client-side after save dash

Log from docker-compose:
 sudo docker-compose up
Password:
Creating network "incubator-superset_default" with the default driver
Pulling redis (redis:3.2)...
3.2: Pulling from library/redis
f17d81b4b692: Pull complete
b32474098757: Pull complete
8980cabe8bc2: Pull complete
58af19693e78: Pull complete
a977782cf22d: Pull complete
9c1e268980b7: Pull complete
Digest: sha256:7b0a40301bc1567205e6461c5bf94c38e1e1ad0169709e49132cafc47f6b51f3
Status: Downloaded newer image for redis:3.2
Pulling db (postgres:10)...
10: Pulling from library/postgres
babf97a3f00a: Pull complete
0526c44df6ea: Pull complete
b2466ee00e96: Pull complete
77c605d60192: Pull complete
76b14ab41842: Pull complete
440f557fff31: Pull complete
30bba27806f4: Pull complete
a4e155509054: Pull complete
ff8228dd9c6c: Pull complete
687446f7ecc1: Pull complete
8e3cd5a196d7: Pull complete
ed343704369a: Pull complete
bd793ab304ef: Pull complete
09d7b347c7d5: Pull complete
Digest: sha256:8f14682f49a66eb10dd97a3336224e6136b33179e9569cd7d1bd999f40355e55
Status: Downloaded newer image for postgres:10
Building superset
Step 1/6 : FROM preset/superset:dev
dev: Pulling from preset/superset
57df1a1f1ad8: Pull complete
71e126169501: Pull complete
1af28a55c3f3: Pull complete
03f1c9932170: Pull complete
65b3db15f518: Pull complete
3e3b8947ed83: Pull complete
38d9e7938097: Pull complete
724043f425e0: Pull complete
6cf90f3f5863: Pull complete
edf25eb9d2b0: Pull complete
740ed84b7f65: Pull complete
05d98899a8f4: Pull complete
3d0fdfa7128c: Pull complete
3d6fdaed5e07: Pull complete
d090585fbc19: Pull complete
ce1602e661a1: Pull complete
ad0d92a16866: Pull complete
066f8beef4e0: Pull complete
bf533094ddbe: Pull complete
7e3ee9ff7cfd: Pull complete
Digest: sha256:c863401a29d49b4fd76da253e405ebfa7874f020c89d42452824a222a4341df0
Status: Downloaded newer image for preset/superset:dev
 ---> ef470253aa82
Step 2/6 : COPY ./requirements/*.txt ./docker/requirements-*.txt /app/requirements/
 ---> 15af643e194c
Step 3/6 : COPY ./setup.py ./MANIFEST.in /app/
 ---> 3805e6828862
Step 4/6 : USER root
 ---> Running in 3f020100dfb2
Removing intermediate container 3f020100dfb2
 ---> 80c5c1516ca7
Step 5/6 : RUN cd /app     && pip install -e .     && pip install -r requirements/docker.txt     && pip install -r requirements/requirements-local.txt || true
 ---> Running in db7376d28af5
Obtaining file:///app
Requirement already satisfied: backoff>=1.8.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.10.0)
Requirement already satisfied: bleach<4.0.0,>=3.0.2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.2.1)
Requirement already satisfied: cachelib<0.2,>=0.1.1 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.1.1)
Requirement already satisfied: celery!=4.4.1,<5.0.0,>=4.3.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (4.4.7)
Requirement already satisfied: click<8 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (7.1.2)
Requirement already satisfied: colorama in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.4.3)
Requirement already satisfied: contextlib2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.6.0.post1)
Requirement already satisfied: croniter>=0.3.28 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.3.34)
Requirement already satisfied: cryptography>=2.4.2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.1.1)
Requirement already satisfied: flask<2.0.0,>=1.1.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.1.2)
Requirement already satisfied: flask-appbuilder<4.0.0,>=3.0.1 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.0.1)
Requirement already satisfied: flask-caching in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.9.0)
Requirement already satisfied: flask-compress in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.5.0)
Requirement already satisfied: flask-talisman in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.7.0)
Requirement already satisfied: flask-migrate in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.5.3)
Requirement already satisfied: flask-wtf in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.14.3)
Requirement already satisfied: geopy in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.0.0)
Requirement already satisfied: gunicorn<20.1,>=20.0.2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (20.0.4)
Requirement already satisfied: humanize in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.6.0)
Requirement already satisfied: isodate in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.6.0)
Requirement already satisfied: markdown>=3.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.2.2)
Requirement already satisfied: msgpack<1.1,>=1.0.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.0.0)
Requirement already satisfied: pandas<1.2,>=1.1.2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.1.2)
Requirement already satisfied: parsedatetime in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.6)
Requirement already satisfied: pathlib2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.3.5)
Requirement already satisfied: polyline in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.4.0)
Requirement already satisfied: python-dateutil in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.8.1)
Requirement already satisfied: python-dotenv in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.14.0)
Requirement already satisfied: python-geohash in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.8.5)
Requirement already satisfied: pyarrow<1.1,>=1.0.1 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.0.1)
Requirement already satisfied: pyyaml>=5.1 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (5.3.1)
Requirement already satisfied: retry>=0.9.2 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.9.2)
Requirement already satisfied: selenium>=3.141.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.141.0)
Requirement already satisfied: simplejson>=3.15.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (3.17.2)
Requirement already satisfied: slackclient==2.5.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (2.5.0)
Requirement already satisfied: sqlalchemy<2.0,>=1.3.16 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (1.3.19)
Requirement already satisfied: sqlalchemy-utils<0.37,>=0.36.6 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.36.8)
Requirement already satisfied: sqlparse==0.3.0 in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.3.0)
Requirement already satisfied: wtforms-json in /usr/local/lib/python3.7/site-packages (from apache-superset==0.999.0.dev0) (0.3.3)
Requirement already satisfied: packaging in /usr/local/lib/python3.7/site-packages (from bleach<4.0.0,>=3.0.2->apache-superset==0.999.0.dev0) (20.4)
Requirement already satisfied: six>=1.9.0 in /usr/local/lib/python3.7/site-packages (from bleach<4.0.0,>=3.0.2->apache-superset==0.999.0.dev0) (1.15.0)
Requirement already satisfied: webencodings in /usr/local/lib/python3.7/site-packages (from bleach<4.0.0,>=3.0.2->apache-superset==0.999.0.dev0) (0.5.1)
Requirement already satisfied: kombu<4.7,>=4.6.10 in /usr/local/lib/python3.7/site-packages (from celery!=4.4.1,<5.0.0,>=4.3.0->apache-superset==0.999.0.dev0) (4.6.11)
Requirement already satisfied: pytz>dev in /usr/local/lib/python3.7/site-packages (from celery!=4.4.1,<5.0.0,>=4.3.0->apache-superset==0.999.0.dev0) (2020.1)
Requirement already satisfied: billiard<4.0,>=<IP_ADDRESS> in /usr/local/lib/python3.7/site-packages (from celery!=4.4.1,<5.0.0,>=4.3.0->apache-superset==0.999.0.dev0) (<IP_ADDRESS>)
Requirement already satisfied: vine==1.3.0 in /usr/local/lib/python3.7/site-packages (from celery!=4.4.1,<5.0.0,>=4.3.0->apache-superset==0.999.0.dev0) (1.3.0)
Requirement already satisfied: natsort in /usr/local/lib/python3.7/site-packages (from croniter>=0.3.28->apache-superset==0.999.0.dev0) (7.0.1)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.7/site-packages (from cryptography>=2.4.2->apache-superset==0.999.0.dev0) (1.14.3)
Requirement already satisfied: Jinja2>=2.10.1 in /usr/local/lib/python3.7/site-packages (from flask<2.0.0,>=1.1.0->apache-superset==0.999.0.dev0) (2.11.2)
Requirement already satisfied: Werkzeug>=0.15 in /usr/local/lib/python3.7/site-packages (from flask<2.0.0,>=1.1.0->apache-superset==0.999.0.dev0) (1.0.1)
Requirement already satisfied: itsdangerous>=0.24 in /usr/local/lib/python3.7/site-packages (from flask<2.0.0,>=1.1.0->apache-superset==0.999.0.dev0) (1.1.0)
Requirement already satisfied: PyJWT>=1.7.1 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (1.7.1)
Requirement already satisfied: prison<1.0.0,>=0.1.3 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (0.1.3)
Requirement already satisfied: marshmallow-enum<2,>=1.5.1 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (1.5.1)
Requirement already satisfied: marshmallow<4,>=3 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (3.8.0)
Requirement already satisfied: marshmallow-sqlalchemy<1,>=0.22.0 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (0.23.1)
Requirement already satisfied: Flask-SQLAlchemy<3,>=2.4 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (2.4.4)
Requirement already satisfied: Flask-Login<0.5,>=0.3 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (0.4.1)
Requirement already satisfied: email-validator<2,>=1.0.5 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (1.1.1)
Requirement already satisfied: Flask-OpenID<2,>=1.2.5 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (1.2.5)
Requirement already satisfied: Flask-JWT-Extended<4,>=3.18 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (3.24.1)
Requirement already satisfied: apispec[yaml]<4,>=3.3 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (3.3.2)
Requirement already satisfied: jsonschema<4,>=3.0.1 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (3.2.0)
Requirement already satisfied: Flask-Babel<2,>=1 in /usr/local/lib/python3.7/site-packages (from flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (1.0.0)
Requirement already satisfied: brotli in /usr/local/lib/python3.7/site-packages (from flask-compress->apache-superset==0.999.0.dev0) (1.0.9)
Requirement already satisfied: alembic>=0.7 in /usr/local/lib/python3.7/site-packages (from flask-migrate->apache-superset==0.999.0.dev0) (1.4.3)
Requirement already satisfied: WTForms in /usr/local/lib/python3.7/site-packages (from flask-wtf->apache-superset==0.999.0.dev0) (2.3.3)
Requirement already satisfied: geographiclib<2,>=1.49 in /usr/local/lib/python3.7/site-packages (from geopy->apache-superset==0.999.0.dev0) (1.50)
Requirement already satisfied: setuptools>=3.0 in /usr/local/lib/python3.7/site-packages (from gunicorn<20.1,>=20.0.2->apache-superset==0.999.0.dev0) (50.3.0)
Requirement already satisfied: importlib-metadata; python_version < "3.8" in /usr/local/lib/python3.7/site-packages (from markdown>=3.0->apache-superset==0.999.0.dev0) (1.7.0)
Requirement already satisfied: numpy>=1.15.4 in /usr/local/lib/python3.7/site-packages (from pandas<1.2,>=1.1.2->apache-superset==0.999.0.dev0) (1.19.2)
Requirement already satisfied: py<2.0.0,>=1.4.26 in /usr/local/lib/python3.7/site-packages (from retry>=0.9.2->apache-superset==0.999.0.dev0) (1.9.0)
Requirement already satisfied: decorator>=3.4.2 in /usr/local/lib/python3.7/site-packages (from retry>=0.9.2->apache-superset==0.999.0.dev0) (4.4.2)
Requirement already satisfied: urllib3 in /usr/local/lib/python3.7/site-packages (from selenium>=3.141.0->apache-superset==0.999.0.dev0) (1.25.10)
Requirement already satisfied: aiohttp>3.5.2 in /usr/local/lib/python3.7/site-packages (from slackclient==2.5.0->apache-superset==0.999.0.dev0) (3.6.2)
Requirement already satisfied: pyparsing>=2.0.2 in /usr/local/lib/python3.7/site-packages (from packaging->bleach<4.0.0,>=3.0.2->apache-superset==0.999.0.dev0) (2.4.7)
Requirement already satisfied: amqp<2.7,>=2.6.0 in /usr/local/lib/python3.7/site-packages (from kombu<4.7,>=4.6.10->celery!=4.4.1,<5.0.0,>=4.3.0->apache-superset==0.999.0.dev0) (2.6.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.7/site-packages (from cffi!=1.11.3,>=1.8->cryptography>=2.4.2->apache-superset==0.999.0.dev0) (2.20)
Requirement already satisfied: MarkupSafe>=0.23 in /usr/local/lib/python3.7/site-packages (from Jinja2>=2.10.1->flask<2.0.0,>=1.1.0->apache-superset==0.999.0.dev0) (1.1.1)
Requirement already satisfied: dnspython>=1.15.0 in /usr/local/lib/python3.7/site-packages (from email-validator<2,>=1.0.5->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (2.0.0)
Requirement already satisfied: idna>=2.0.0 in /usr/local/lib/python3.7/site-packages (from email-validator<2,>=1.0.5->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (2.10)
Requirement already satisfied: python3-openid>=2.0 in /usr/local/lib/python3.7/site-packages (from Flask-OpenID<2,>=1.2.5->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (3.2.0)
Requirement already satisfied: attrs>=17.4.0 in /usr/local/lib/python3.7/site-packages (from jsonschema<4,>=3.0.1->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (20.2.0)
Requirement already satisfied: pyrsistent>=0.14.0 in /usr/local/lib/python3.7/site-packages (from jsonschema<4,>=3.0.1->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (0.16.1)
Requirement already satisfied: Babel>=2.3 in /usr/local/lib/python3.7/site-packages (from Flask-Babel<2,>=1->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (2.8.0)
Requirement already satisfied: Mako in /usr/local/lib/python3.7/site-packages (from alembic>=0.7->flask-migrate->apache-superset==0.999.0.dev0) (1.1.3)
Requirement already satisfied: python-editor>=0.3 in /usr/local/lib/python3.7/site-packages (from alembic>=0.7->flask-migrate->apache-superset==0.999.0.dev0) (1.0.4)
Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.7/site-packages (from importlib-metadata; python_version < "3.8"->markdown>=3.0->apache-superset==0.999.0.dev0) (3.2.0)
Requirement already satisfied: chardet<4.0,>=2.0 in /usr/local/lib/python3.7/site-packages (from aiohttp>3.5.2->slackclient==2.5.0->apache-superset==0.999.0.dev0) (3.0.4)
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.7/site-packages (from aiohttp>3.5.2->slackclient==2.5.0->apache-superset==0.999.0.dev0) (1.5.1)
Requirement already satisfied: multidict<5.0,>=4.5 in /usr/local/lib/python3.7/site-packages (from aiohttp>3.5.2->slackclient==2.5.0->apache-superset==0.999.0.dev0) (4.7.6)
Requirement already satisfied: async-timeout<4.0,>=3.0 in /usr/local/lib/python3.7/site-packages (from aiohttp>3.5.2->slackclient==2.5.0->apache-superset==0.999.0.dev0) (3.0.1)
Requirement already satisfied: defusedxml in /usr/local/lib/python3.7/site-packages (from python3-openid>=2.0->Flask-OpenID<2,>=1.2.5->flask-appbuilder<4.0.0,>=3.0.1->apache-superset==0.999.0.dev0) (0.6.0)
Requirement already satisfied: typing-extensions>=3.7.4; python_version < "3.8" in /usr/local/lib/python3.7/site-packages (from yarl<2.0,>=1.0->aiohttp>3.5.2->slackclient==2.5.0->apache-superset==0.999.0.dev0) (<IP_ADDRESS>)
Installing collected packages: apache-superset
  Attempting uninstall: apache-superset
    Found existing installation: apache-superset 0.999.0.dev0
    Uninstalling apache-superset-0.999.0.dev0:
      Successfully uninstalled apache-superset-0.999.0.dev0
  Running setup.py develop for apache-superset
Successfully installed apache-superset
WARNING: You are using pip version 20.2.3; however, version 20.2.4 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
Obtaining file:///. (from -r requirements/base.txt (line 8))
Obtaining file:///. (from -r requirements/docker.txt (line 9))
Requirement already satisfied: aiohttp==3.6.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 9)) (3.6.2)
Requirement already satisfied: alembic==1.4.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 10)) (1.4.3)
Requirement already satisfied: amqp==2.6.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 11)) (2.6.1)
Requirement already satisfied: apispec[yaml]==3.3.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 12)) (3.3.2)
Requirement already satisfied: async-timeout==3.0.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 13)) (3.0.1)
Requirement already satisfied: attrs==20.2.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 14)) (20.2.0)
Requirement already satisfied: babel==2.8.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 15)) (2.8.0)
Requirement already satisfied: backoff==1.10.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 16)) (1.10.0)
Requirement already satisfied: billiard==<IP_ADDRESS> in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 17)) (<IP_ADDRESS>)
Requirement already satisfied: bleach==3.2.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 18)) (3.2.1)
Requirement already satisfied: brotli==1.0.9 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 19)) (1.0.9)
Requirement already satisfied: cachelib==0.1.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 20)) (0.1.1)
Requirement already satisfied: celery==4.4.7 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 21)) (4.4.7)
Requirement already satisfied: cffi==1.14.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 22)) (1.14.3)
Requirement already satisfied: chardet==3.0.4 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 23)) (3.0.4)
Requirement already satisfied: click==7.1.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 24)) (7.1.2)
Requirement already satisfied: colorama==0.4.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 25)) (0.4.3)
Requirement already satisfied: contextlib2==0.6.0.post1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 26)) (0.6.0.post1)
Requirement already satisfied: croniter==0.3.34 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 27)) (0.3.34)
Requirement already satisfied: cryptography==3.1.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 28)) (3.1.1)
Requirement already satisfied: decorator==4.4.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 29)) (4.4.2)
Requirement already satisfied: defusedxml==0.6.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 30)) (0.6.0)
Requirement already satisfied: dnspython==2.0.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 31)) (2.0.0)
Requirement already satisfied: email-validator==1.1.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 32)) (1.1.1)
Requirement already satisfied: flask-appbuilder==3.0.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 33)) (3.0.1)
Requirement already satisfied: flask-babel==1.0.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 34)) (1.0.0)
Requirement already satisfied: flask-caching==1.9.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 35)) (1.9.0)
Requirement already satisfied: flask-compress==1.5.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 36)) (1.5.0)
Requirement already satisfied: flask-jwt-extended==3.24.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 37)) (3.24.1)
Requirement already satisfied: flask-login==0.4.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 38)) (0.4.1)
Requirement already satisfied: flask-migrate==2.5.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 39)) (2.5.3)
Requirement already satisfied: flask-openid==1.2.5 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 40)) (1.2.5)
Requirement already satisfied: flask-sqlalchemy==2.4.4 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 41)) (2.4.4)
Requirement already satisfied: flask-talisman==0.7.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 42)) (0.7.0)
Requirement already satisfied: flask-wtf==0.14.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 43)) (0.14.3)
Requirement already satisfied: flask==1.1.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 44)) (1.1.2)
Requirement already satisfied: geographiclib==1.50 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 45)) (1.50)
Requirement already satisfied: geopy==2.0.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 46)) (2.0.0)
Requirement already satisfied: gunicorn==20.0.4 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 47)) (20.0.4)
Requirement already satisfied: humanize==2.6.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 48)) (2.6.0)
Requirement already satisfied: idna==2.10 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 49)) (2.10)
Requirement already satisfied: importlib-metadata==1.7.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 50)) (1.7.0)
Requirement already satisfied: isodate==0.6.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 51)) (0.6.0)
Requirement already satisfied: itsdangerous==1.1.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 52)) (1.1.0)
Requirement already satisfied: jinja2==2.11.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 53)) (2.11.2)
Requirement already satisfied: jsonschema==3.2.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 54)) (3.2.0)
Requirement already satisfied: kombu==4.6.11 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 55)) (4.6.11)
Requirement already satisfied: mako==1.1.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 56)) (1.1.3)
Requirement already satisfied: markdown==3.2.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 57)) (3.2.2)
Requirement already satisfied: markupsafe==1.1.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 58)) (1.1.1)
Requirement already satisfied: marshmallow-enum==1.5.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 59)) (1.5.1)
Requirement already satisfied: marshmallow-sqlalchemy==0.23.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 60)) (0.23.1)
Requirement already satisfied: marshmallow==3.8.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 61)) (3.8.0)
Requirement already satisfied: msgpack==1.0.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 62)) (1.0.0)
Requirement already satisfied: multidict==4.7.6 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 63)) (4.7.6)
Requirement already satisfied: natsort==7.0.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 64)) (7.0.1)
Requirement already satisfied: numpy==1.19.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 65)) (1.19.2)
Requirement already satisfied: packaging==20.4 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 66)) (20.4)
Requirement already satisfied: pandas==1.1.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 67)) (1.1.2)
Requirement already satisfied: parsedatetime==2.6 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 68)) (2.6)
Requirement already satisfied: pathlib2==2.3.5 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 69)) (2.3.5)
Requirement already satisfied: polyline==1.4.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 70)) (1.4.0)
Requirement already satisfied: prison==0.1.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 71)) (0.1.3)
Requirement already satisfied: py==1.9.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 72)) (1.9.0)
Requirement already satisfied: pyarrow==1.0.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 73)) (1.0.1)
Requirement already satisfied: pycparser==2.20 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 74)) (2.20)
Requirement already satisfied: pyjwt==1.7.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 75)) (1.7.1)
Requirement already satisfied: pyparsing==2.4.7 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 76)) (2.4.7)
Requirement already satisfied: pyrsistent==0.16.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 77)) (0.16.1)
Requirement already satisfied: python-dateutil==2.8.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 78)) (2.8.1)
Requirement already satisfied: python-dotenv==0.14.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 79)) (0.14.0)
Requirement already satisfied: python-editor==1.0.4 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 80)) (1.0.4)
Requirement already satisfied: python-geohash==0.8.5 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 81)) (0.8.5)
Requirement already satisfied: python3-openid==3.2.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 82)) (3.2.0)
Requirement already satisfied: pytz==2020.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 83)) (2020.1)
Requirement already satisfied: pyyaml==5.3.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 84)) (5.3.1)
Requirement already satisfied: retry==0.9.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 85)) (0.9.2)
Requirement already satisfied: selenium==3.141.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 86)) (3.141.0)
Requirement already satisfied: simplejson==3.17.2 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 87)) (3.17.2)
Requirement already satisfied: six==1.15.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 88)) (1.15.0)
Requirement already satisfied: slackclient==2.5.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 89)) (2.5.0)
Requirement already satisfied: sqlalchemy-utils==0.36.8 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 90)) (0.36.8)
Requirement already satisfied: sqlalchemy==1.3.19 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 91)) (1.3.19)
Requirement already satisfied: sqlparse==0.3.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 92)) (0.3.0)
Requirement already satisfied: typing-extensions==<IP_ADDRESS> in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 93)) (<IP_ADDRESS>)
Requirement already satisfied: urllib3==1.25.10 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 94)) (1.25.10)
Requirement already satisfied: vine==1.3.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 95)) (1.3.0)
Requirement already satisfied: webencodings==0.5.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 96)) (0.5.1)
Requirement already satisfied: werkzeug==1.0.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 97)) (1.0.1)
Requirement already satisfied: wtforms-json==0.3.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 98)) (0.3.3)
Requirement already satisfied: wtforms==2.3.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 99)) (2.3.3)
Requirement already satisfied: yarl==1.5.1 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 100)) (1.5.1)
Requirement already satisfied: zipp==3.2.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/base.txt (line 101)) (3.2.0)
Requirement already satisfied: gevent==20.9.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 10)) (20.9.0)
Requirement already satisfied: greenlet==0.4.17 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 11)) (0.4.17)
Requirement already satisfied: psycopg2-binary==2.8.6 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 12)) (2.8.6)
Requirement already satisfied: redis==3.5.3 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 13)) (3.5.3)
Requirement already satisfied: zope.event==4.5.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 14)) (4.5.0)
Requirement already satisfied: zope.interface==5.1.0 in /usr/local/lib/python3.7/site-packages (from -r requirements/docker.txt (line 15)) (5.1.0)
Requirement already satisfied: setuptools>=3.0 in /usr/local/lib/python3.7/site-packages (from gunicorn==20.0.4->-r requirements/base.txt (line 47)) (50.3.0)
Installing collected packages: apache-superset
  Attempting uninstall: apache-superset
    Found existing installation: apache-superset 0.999.0.dev0
    Uninstalling apache-superset-0.999.0.dev0:
      Successfully uninstalled apache-superset-0.999.0.dev0
  Running setup.py develop for apache-superset
Successfully installed apache-superset
WARNING: You are using pip version 20.2.3; however, version 20.2.4 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements/requirements-local.txt'
WARNING: You are using pip version 20.2.3; however, version 20.2.4 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
Removing intermediate container db7376d28af5
 ---> 211a9f2b109f
Step 6/6 : USER superset
 ---> Running in 90000f87368e
Removing intermediate container 90000f87368e
 ---> 87833fdd0d0e

[Warning] One or more build-args [NPM_BUILD_CMD] were not consumed
Successfully built 87833fdd0d0e
Successfully tagged incubator-superset_superset:latest
WARNING: Image for service superset was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Building superset-init
Step 1/6 : FROM preset/superset:dev
 ---> ef470253aa82
Step 2/6 : COPY ./requirements/*.txt ./docker/requirements-*.txt /app/requirements/
 ---> Using cache
 ---> 15af643e194c
Step 3/6 : COPY ./setup.py ./MANIFEST.in /app/
 ---> Using cache
 ---> 3805e6828862
Step 4/6 : USER root
 ---> Using cache
 ---> 80c5c1516ca7
Step 5/6 : RUN cd /app     && pip install -e .     && pip install -r requirements/docker.txt     && pip install -r requirements/requirements-local.txt || true
 ---> Using cache
 ---> 211a9f2b109f
Step 6/6 : USER superset
 ---> Using cache
 ---> 87833fdd0d0e

[Warning] One or more build-args [NPM_BUILD_CMD] were not consumed
Successfully built 87833fdd0d0e
Successfully tagged incubator-superset_superset-init:latest
WARNING: Image for service superset-init was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
 To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Building superset-tests-worker
Step 1/6 : FROM preset/superset:dev
 ---> ef470253aa82
Step 2/6 : COPY ./requirements/*.txt ./docker/requirements-*.txt /app/requirements/
 ---> Using cache
 ---> 15af643e194c
Step 3/6 : COPY ./setup.py ./MANIFEST.in /app/
 ---> Using cache
 ---> 3805e6828862
Step 4/6 : USER root
 ---> Using cache
 ---> 80c5c1516ca7
Step 5/6 : RUN cd /app     && pip install -e .     && pip install -r requirements/docker.txt     && pip install -r requirements/requirements-local.txt || true
 ---> Using cache
 ---> 211a9f2b109f
Step 6/6 : USER superset
 ---> Using cache
 ---> 87833fdd0d0e

[Warning] One or more build-args [NPM_BUILD_CMD] were not consumed
Successfully built 87833fdd0d0e
Successfully tagged incubator-superset_superset-tests-worker:latest
WARNING: Image for service superset-tests-worker was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating superset_cache ... done
Creating superset_db    ... done
Creating superset_app          ... done
Creating superset_node         ... done
Creating superset_init         ... done
Creating superset_tests_worker ... done
Creating superset_worker       ... done
Attaching to superset_db, superset_cache, superset_tests_worker, superset_app, superset_node, superset_init, superset_worker
superset_db              |
superset_db              | PostgreSQL Database directory appears to contain a database; Skipping initialization
superset_db              |
superset_db              | 2020-10-19 02:15:20.315 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
superset_db              | 2020-10-19 02:15:20.315 UTC [1] LOG:  listening on IPv6 address "::", port 5432
superset_db              | 2020-10-19 02:15:20.676 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
superset_db              | 2020-10-19 02:15:21.309 UTC [25] LOG:  database system was shut down at 2020-10-18 18:43:00 UTC
superset_db              | 2020-10-19 02:15:21.641 UTC [1] LOG:  database system is ready to accept connections
superset_cache           | 1:C 19 Oct 02:15:15.405 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_cache           |                 _._
superset_cache           |            _.-``__ ''-._
superset_cache           |       _.-``    `.  `_.  ''-._           Redis 3.2.12 (00000000/0) 64 bit
superset_cache           |   .-`` .-```.  ```\/    _.,_ ''-._
superset_cache           |  (    '      ,       .-`  | `,    )     Running in standalone mode
superset_cache           |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
superset_cache           |  |    `-._   `._    /     _.-'    |     PID: 1
superset_cache           |   `-._    `-._  `-./  _.-'    _.-'
superset_cache           |  |`-._`-._    `-.__.-'    _.-'_.-'|
superset_cache           |  |    `-._`-._        _.-'_.-'    |           http://redis.io
superset_cache           |   `-._    `-._`-.__.-'_.-'    _.-'
superset_cache           |  |`-._`-._    `-.__.-'    _.-'_.-'|
superset_cache           |  |    `-._`-._        _.-'_.-'    |
superset_cache           |   `-._    `-._`-.__.-'_.-'    _.-'
superset_cache           |       `-._    `-.__.-'    _.-'
superset_cache           |           `-._        _.-'
superset_cache           |               `-.__.-'
superset_cache           |
superset_cache           | 1:M 19 Oct 02:15:15.624 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
superset_cache           | 1:M 19 Oct 02:15:15.624 # Server started, Redis version 3.2.12
superset_cache           | 1:M 19 Oct 02:15:15.624 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
superset_cache           | 1:M 19 Oct 02:15:15.624 * DB loaded from disk: 0.000 seconds
superset_cache           | 1:M 19 Oct 02:15:15.624 * The server is now ready to accept connections on port 6379
superset_node            | npm WARN using --force I sure hope you know what you are doing.
superset_init            | /usr/bin/env: ‘bash\r’: No such file or directory
superset_init exited with code 127
superset_app             |  * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app             |  * Environment: development
superset_app             |  * Debug mode: on
superset_app             |  * Running on http://<IP_ADDRESS>:8088/ (Press CTRL+C to quit)
superset_app             |  * Restarting with stat
superset_app             |  * Debugger is active!
superset_app             |  * Debugger PIN: 306-869-333
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_tests_worker    | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) could not connect to server: Connection refused
superset_tests_worker    |      Is the server running on host "localhost" (::1) and accepting
superset_tests_worker    |      TCP/IP connections on port 5432?
superset_tests_worker    | FATAL:  no pg_hba.conf entry for host "<IP_ADDRESS>", user "superset", database "test"
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/13/e3q8)
superset_tests_worker    | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_tests_worker exited with code 1
superset_worker          | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app             | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_app             |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_app             | <IP_ADDRESS> - - [19/Oct/2020 02:16:05] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [19/Oct/2020 02:16:05] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [19/Oct/2020 02:16:05] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [19/Oct/2020 02:16:05] "GET /health HTTP/1.1" 200 -
superset_worker          | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_worker          |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_worker          | [2020-10-19 02:16:07,501: INFO/MainProcess] Connected to redis://redis:6379/0
superset_worker          | [2020-10-19 02:16:07,518: INFO/MainProcess] mingle: searching for neighbors
superset_worker          | [2020-10-19 02:16:08,572: INFO/MainProcess] mingle: all alone
superset_worker          | [2020-10-19 02:16:08,613: INFO/MainProcess] celery@4c62ee98fca2 ready.
superset_app             | <IP_ADDRESS> - - [19/Oct/2020 02:16:36] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [19/Oct/2020 02:16:36] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [19/Oct/2020 02:17:06] "GET /health HTTP/1.1" 200 -

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

are running this on windows or did you clone the repo on a windows file system? This is likely your issue https://stackoverflow.com/a/29045187/13977852

oh yes, i clone this repo on windows and copy the folder to linux box, i'll try to clone in linux and try it again

this is extactly because of cloning code on windows, fixed this by removing the windows style line ending.

this is extactly because of cloning code on windows, fixed this by removing the windows style line ending.

how to remove the windows style line ending? which files should be modified? thank you

this is extactly because of cloning code on windows, fixed this by removing the windows style line ending.

how to remove the windows style line ending? which files should be modified? thank you

Just perform the git clone inside your linux bix instead of cloning at your windows


Terraform Enterprise Role Assumption Error (Role Chain Error in sub module)

Bug Description
We are currently using Terraform Enterprise (TFE) to manage Terraform in multiple accounts. Theres is a central TF role in the TF build account. Then there are terraform roles in every sub account that are assumed by the main build role. When workspaces are made in Terraform enterprise, the provider has the role in the sub accounts and this role has the permissions to execute the terraform code. However, when trying to run the AFT module, because there is a provider block assuming the AWSControlTowerExecution role for the logging and audit account, the original context of the workspace assumed role is lost, and the main TFE role tries to assume this role and is blocked because it is not a trusted entity.
To summarize:
Normal TFE use:
Main TFE Role A in Account A -> Assumes TFE Role B in Account B -> Terraform executes for Account B
Expected Behavior when running AFT Module:
Main TFE Role A in Account A -> Assumes TFE Role B in Account B (In AFT Mngmt Acc) -> Role B assumes AWSControlTowerExecution role in logging/audit accounts and executes terraform code
Actual Behavior when running AFT Module:
Main TFE Role A in Account A -> Assumes TFE Role B in Account B (In AFT Mngmt Acc) -> Role A tries to assume AWSControlTowerExecution role in logging/audit accounts and is blocked because only the AFT Mngmt Account is the trusted entity
And I cannot add Account A as a trusted entity to AWSControlTowerExecution because of mandatory guardrails set by control tower.
Relevant logs: 'api error AccessDenied: User: arn:aws:sts::x-x-x-x:assumed-role/(Role A) is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::x-x:role/AWSControlTowerExecution'
Also should be noted that the provider used to run the AFT module uses Role B in the AFT mngmt account, but Terraform Enterprise still uses the main TFE (Role A) to assume providers in submodules.
Any recommendations on how to deal with this?

@mosh313 thank you for reaching out.
During AFT deployment, AFT uses CT management account as the 'hub' account from where the role assumption takes place into respective accounts ( CT management account is 'Account A' in this case ).
Additionally, the AWSControlTowerExecution role in all the target accounts in a CT environment trust the CT management account by default, and you should not need to edit the AWSControlTowerExecution role manually.
Please may you clarify if you are failing to do the initial deployment of AFT in your CT environment?
Also, AFT deployment requires you to have AdministratorAccess permissions into the CT management account which vends an AFT module that establishes all infrastructure necessary to orchestrate your AFT requests. Can you confirm that you have AdministratorAccess to the CT management account while performing the AFT deployment?
It would be great if you could elaborate your use case more to help us assist you better.


Add floquet and floquet_t

Closes DYN-231
Add Floquet solvers and associated tests. The API as it stands now supplies two functions: floquet and floquet_t for obtaining the floquet modes (and associated quasienergies) at t=0, and obtaining the floquet modes at other times t, respectively. I'm not thrilled about the name floquet_t, nor the name of e.g. the respective integrator FloquetIntegrator_t, so any suggestions for better names are welcome.

Quick comment raised by @BenjaminDAnjou: jnp.linalg.eig is only supported on the CPU backend for now (see https://github.com/google/jax/issues/1259). This jax issue is live since 2019, so I don't think we can expect progress on this front.
Is there any other way to compute the Floquet basis @dkweiss31? Otherwise, maybe we could perform the workaround suggested in the linked issue, that is callback to the CPU implementation of jnp.linalg.eig using external callbacks. Note that this is also what PyTorch does for eig on GPU.

Thanks for this, I hadn't appreciated that eig is only supported on CPUs. I'm not aware of another robust numerical technique for computing the floquet modes. Happy to try out the callbacks workaround

For information, the people in my group who know more than me about these implementations seem to think that implementing the callback workaround in the most sensible thing to do.

Hey @gautierronan , thank you very much for this review and for the significant simplifications you introduced. I am very happy with all of your proposed changes and will write up an example for T batching shortly.
I had been working with jax 0.4.29, and upgraded based on your comment that the vectorized option in pure_callback is deprecated. On updating how we call pure_callback I ran into issues with my tests hanging, which is apparently a known issue for jax > 0.4.31 https://github.com/jax-ml/jax/issues/24255. It seems however that there is an implementation of eig for GPU in the works https://github.com/jax-ml/jax/pull/24663 that should hopefully be merged soon. I propose then to just use jax.numpy.linalg.eig for now, and then make updates once the new GPU implementation is available.

Sounds great, thanks very much @gautierronan !


fix: test and bump deps

bump deps verison
fix test and lint

Codecov Report
Attention: 97 lines in your changes are missing coverage. Please review.

Comparison is base (219fced) 61.13% compared to head (335ef6a) 61.16%.
Report is 33 commits behind head on main.

Files
Patch %
Lines

src/tree/src/TreeNode.tsx
28.00%
17 Missing and 1 partial :warning:

src/tree/src/keyboard.tsx
0.00%
18 Missing :warning:

src/_utils/dom/download.ts
11.11%
8 Missing :warning:

src/tree-select/src/TreeSelect.tsx
0.00%
8 Missing :warning:

src/flex/src/Flex.tsx
77.41%
4 Missing and 3 partials :warning:

src/data-table/src/utils.ts
0.00%
6 Missing :warning:

src/date-picker/src/panel/use-dual-calendar.ts
0.00%
6 Missing :warning:

src/data-table/src/DataTable.tsx
28.57%
5 Missing :warning:

src/date-picker/src/panel/monthrange.tsx
20.00%
4 Missing :warning:

src/date-picker/src/utils.ts
50.00%
4 Missing :warning:

... and 7 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5542      +/-   ##
==========================================
+ Coverage   61.13%   61.16%   +0.02%
==========================================
  Files        1096     1107      +11
  Lines       23465    23593     +128
  Branches     6147     6167      +20
==========================================
+ Hits        14346    14430      +84
- Misses       7535     7579      +44
  Partials     1584     1584

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

build:site 挂了需要处理一下


Patches automagic expects newline after SourceX: lines

SpecFileParseError: Error parsing .spec file 'openstack-sahara.spec': Failed to append PatchXXXX: lines
Either fix this or document this requiremnt in the resulting error message.

Confirmed, I've just hit this in keystonemiddleware, workaround:
Source0:        https://pypi.python.org/packages/source/k/%{pypi_name}/%{pypi_name}-%{version}.tar.gz
+
BuildArch:      noarch

Other bugs related to PatchXXXX parsing: #15, #18

Other bugs related to PatchXXXX parsing: #15, #18

I hit this again today, in a package that had the following:
...
Source31: cool-library-1.0.tar.gz
Provides: bundled(cool-library) = 1.0

Swapping the ordering of the lines so that Source31: was the final line before the newline allowed rdopkg to parse the .spec file correctly.


Brightness jumps

When changing the brightness down, from maybe 200, when you get to 239, (or 240) it jumps to 249. Then after you press right again, it goes to 003. It also happens in reverse, but I didn’t care to get the numbers.

I did that on purpose so that it doesn't take 10 years to scroll through all the numbers. Release the key and press the other way.


feat: add docker-compose file for testing

Currently I want to test a full integration circle with the block explorer as well.

@solidnerd are you still working on this PR? Currently it only contains a copy of another docker compose file, right?

@Echsecutor  let's close it.


importing data_generation.square_sequences failing

I am getting following when I try import, any idea???
[root@localhost PyTorchStepByStep]# python3 -c "import data_generation.square_sequences"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'data_generation.square_sequences'

I made similar boilerplate code dir1/dir1a.py and it works:
python3 -c "import dir1.dir1a"
[root@localhost PyTorchStepByStep]# cat dir1/dir1a.py

def dir1a():
    print("dir1a:")

[root@localhost PyTorchStepByStep]# git remote -v
origin  https://github.com/dvgodoy/PyTorchStepByStep.git (fetch)
origin  https://github.com/dvgodoy/PyTorchStepByStep.git (push)
[root@localhost PyTorchStepByStep]# pwd
/root/gg/git/codelab/gpu/ml/tf/tf-from-scratch/3/PyTorchStepByStep

/root/gg/git/codelab/gpu/ml/tf/tf-from-scratch/3/PyTorchStepByStep
[root@localhost PyTorchStepByStep]# uname -r
6.1.77kernel_org
[root@localhost PyTorchStepByStep]# cat /etc/os-release | grep -i cent
NAME="CentOS Stream"
ID="centos"
PRETTY_NAME="CentOS Stream 9"
CPE_NAME="cpe:/o:centos:centos:9"
HOME_URL="https://centos.org/"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
[root@localhost PyTorchStepByStep]# pip3 list | grep torch
pytorch-triton-rocm 2.1.0+dafe145982
torch               2.2.0.dev20231209+rocm5.7
torchaudio          2.2.0.dev20231209+rocm5.7
torchbench          0.1                        /root/gg/git/benchmark
torchvision         0.17.0.dev20231209+rocm5.7

Hi @ggankhuy ,
The file you're trying to import is this one: https://github.com/dvgodoy/PyTorchStepByStep/blob/master/data_generation/square_sequences.py
However, it looks like the subfolder data_generation and its file square_sequences.py are missing in the folder where you're running the import command. That's why you're getting this error.
Perhaps it would be best to start fresh in a different folder and clone the full repo:
git clone https://github.com/dvgodoy/PyTorchStepByStep.git
Once the full repo is cloned, all subfolders and their files should be available in your local setup, and you shouldn't get that error anymore.
Hope it helps!
Best,
Daniel

Files are not missing but in one environment it works but in another environment (container) it does not. What i found out is that in a non-working environment, I added dummy/empty init.py file in data_generation folder and it worked.  I recall long ago init.py must be there. I moved on however still not sure why working case did not need init.py.

Hello everyone,
I have been experiencing the same issue trying to run the file in Google Collab.

The import runs through, but get the warning "Import could not be resolved".

This leads to the following errors:

Hi @dalgurnawi
Thank you for reporting this error in figure 8 of Chapter 8.
I've just fixed that and pushed it to the repo. If you start a new Colab session for this notebook, it should work now.
This error was unrelated to the import issue, it happened because of a deprecated attribute in Numpy. Even though Colab shows you that "could not be resolved" message, the generate_sequences() was still successfully imported.
Please let me know if you find any other errors, I really appreciate it :-)
Best,
Daniel

Files are not missing but in one environment it works but in another environment (container) it does not. What i found out is that in a non-working environment, I added dummy/empty init.py file in data_generation folder and it worked. I recall long ago init.py must be there. I moved on however still not sure why working case did not need init.py.

Hi @ggankhuy ,
The __init__.py file turns it into a package, so I guess that addressed whatever was the issue in the container. Even in Colab, we get the "could not be resolved" message but the functions are imported nonetheless.
The reason why I used these separate files as imports was to keep code that's not related to the main topic (such as data generation and plots) out of the way.
I'm glad to hear you managed to make both environments work :-)
Best,
Daniel

Not sure if to discuss in separate issue, i started off in ch9 where in p229:

It says "in the 1st square, drawing started at top right corner and in the sequence CDAB in clockwise direction. But from 9.3, i am not seeing instead 1st square's title above says "counterclockwise and started off with 4321 if clockwise. Is it typo? I am completely lost here.
I could related this to randomness of the data generation while writing the text vs. time illustration was made but seed should make it deterministic is it not??

Hi @ggankhuy ,
I am sorry for the confusion, you're absolutely right, the text it should have been updated to the THIRD square for the sentence to make sense. The third square in Figure 9.3 (not the first one, that was a mistake) is the one corresponding to the description:

This square starts (node 1) on the top-right corner and numbering follows a clockwise order.
The numbers denote the sequence in which the nodes are drawn. If we're trying to use two nodes (source sequence) to predict the other two (target sequence), the source is always going to be 1 and 2, and the target is always going to be 3 and 4.
But we may start at any of the four corners, right?
In Figure 9.1 I "labeled" the corners using letters (see screenshot for the clockwise one):

If we start at the top-right corner (that was "labeled" C), we'll follow CDAB. In this particular example, C=1, D=2, A=3, B=4 because we started on C.
As you mentioned, this mistake was probably due to redrawing the figures which, unfortunately, is never guaranteed to be 100% reproducible whenever PyTorch versions change.
I hope this helps! Once again, I apologize for the confusion.
Thank you for pointing this out.
Best,
Daniel

ok, seems third one seems to match well.  i know i started directly from ch9 so might have skipped over definition of ABCD/1234 meaning, but it seems:
ABCD=[lower left, upper left, upper right, lower right]
1234= just tells the sequence where it starts and which direction, it does not really map one-by-one 1234 to ABCD.
Thanks


Implement 'Clear History' button in Settings

Resolved by https://github.com/RioBus/ionic/pull/45.


Adds exercising of the latest config option to the integration test suite

Extends the integration test with another method to exercise setting the 'latest' config option to true post deployment, and ensures that:

the docker.io package is removed
the lxc-docker page is installed

This does nothing for versioning as that appears to be difficult to track given the speed of docker's upstream release cycle, and will break the tests on package upgrade.
Has some minor style cleanup's to satisfy pyflakes on existing tests snuck in to the PR

@whitmo  @mbruzek   Can I get your eyes on this?


Store / Compactor UI do not work in airgapped environments

Thanos, Prometheus and Golang version used:
0.12.1
Object Storage Provider:
N/A
What happened:
Unable to load store-endpoint:/loaded/
What you expected to happen:
Able to see UI
How to reproduce it (as minimally and precisely as possible):
Try UI without an internet connection
Full logs to relevant components:
GET https://www.gstatic.com/charts/loader.js net::ERR_NAME_NOT_RESOLVED

It looks like all JS is bundled in with the apps apart from this library.

Anything else we need to know:

Valid bug IMO, we want engineers to debug blocks while on airplane! (:
cc @prmsrswt

A quick solution would be to self-host the charts library. We can add the loader.js file with other libraries in /pkg/ui/static/vendor/ directory.
If you like I can submit a quick PR for this.

Sounds good to me!

I found that locally storing the charts library is against their TOS. https://developers.google.com/chart/interactive/faq#offline
So I think we need to migrate to some other library.

Still todo (:
On Sun, 31 May 2020 at 09:24, stale[bot]<EMAIL_ADDRESS>wrote:

Hello 👋 Looks like there was no activity on this issue for last 30 days.
Do you mind updating us on the status? Is this still reproducible or
needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for next week, this issue will be closed (we
can always reopen an issue if we need!). Alternatively, use remind command
https://probot.github.io/apps/reminders/ if you wish to be reminded at
some point in future.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/issues/2539#issuecomment-636439261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVA3O3KABDH6YTLHZFSKYDRUIH3FANCNFSM4MT3VMVQ
.


Add E2E tests and fix webpack 5 errors formatting

📦 Published PR as canary version: 0.1.2-canary.10.f98776f.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v0.1.2 :rocket:


Add and use getter

This change is

Codecov Report

Merging #1023 (2fd05d9) into main (39e78e7) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1023      +/-   ##
==========================================
- Coverage   66.91%   66.85%   -0.06%
==========================================
  Files          51       51
  Lines        6220     6210      -10
  Branches     6220     6210      -10
==========================================
- Hits         4162     4152      -10
  Misses       1679     1679
  Partials      379      379

Files
Coverage Δ

crates/blockifier/src/execution/entry_point.rs
94.68% <100.00%> (+0.02%)
:arrow_up:

.../blockifier/src/transaction/account_transaction.rs
94.26% <100.00%> (-0.13%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Ao.markerClusterGroup is not a function

Hello, thanks for the good library.
I had a problem, after the project is build, an error occurs.
For the assembly, I use cli

If you could provide more context (e.g., code, package.json, etc.), that would help with trying to figure out what's going on. There's also a 504 error, which may mean that a dependency is not loading and is causing the issue.

Closing this as never heard back.


Added github actions

This PR adds some basic github actions which effect the master and dev branches.
Action (1) On PR, the test suite is run before merging.
Action (2) On a merged PR or push to repo, the documentation is regenerated.
Github actions is a little complicated but very powerful. I imagine this will not be the first iteration of actions we use. I think the best way we can stress test these actions is to use them.

Seems to run the tests just fine!


The "qr_task" can't be created successful when the wifi is openning(AP) (IDFGH-1351)

Hi All:
I open the wifi(AP) as below:
wifi_init_softap();
vTaskDelay(100 / portTICK_PERIOD_MS);
http_server_init();
Then I created the qr_reco task as below:
xTaskCreate( qr_recognize, "qr_recognize", 102460, &camera_config, 8, &xTask4);
But the task responsed "-1", maybe not enough memory. The depth is "102460", but when I created a task which depth is "1024*20", it could work well. Does the wifi cost lots of memory? So what can I do next ? Thanks ! :D

Do not use such a huge stack, use heap memory with malloc and use wrover with external ram if necessary.

How to use the external ram ? Because the QR task needs the huge stack, if smaller, it will overflow. Use the external ram maybe the only way. but I can't find it in "make menuconfig". How ?
Thanks :P

Are you using this https://github.com/m5stack/m5stack-cam-psram

Yes, so the task is very huge. When I open the Wifi. I can't create the qr task.

They say it should work with psram, so you should open an issue on their repo if it is not working

@Herwey if you are using quirc library, you may need to look into the image segmentation function which it uses. Replace the recursive segmentation function with a queue-based one, and the stack size requirements will become much more reasonable.
In any case, yes, the issue is that the task creation fails because there isn't a free continuous region of RAM large enough to place the stack.

Emmm, how to replace the Replace the recursive segmentation function... I'm a new beginner :D

Closing as this is an (old) issue with m5stack-cam-psram project, rather than an issue with ESP-IDF itself.
If further assistance with this project is needed, suggest either opening an issue on their project or starting a discussion on the https://esp32.com forum.